{"8650a584-01f8-45d6-882b-c14eab9879c4":{"id":"8650a584-01f8-45d6-882b-c14eab9879c4","doc_no":"A.0","title":"Atlas Preamble","type":"Scope","depth":1,"parentId":null,"order":0,"content":"This Preamble will be further populated in later iterations of the Atlas.","contentHash":"8ba9c1916dd998399d79d5e09428d08b9001a5d55784dff06742ac61919f4f9c","addressRefs":[]},"56b15d7d-cdd4-4594-bd95-4f094564ac04":{"id":"56b15d7d-cdd4-4594-bd95-4f094564ac04","doc_no":"A.0.1","title":"Atlas Preamble","type":"Article","depth":2,"parentId":"8650a584-01f8-45d6-882b-c14eab9879c4","order":1,"content":"This Article contains definitions and general provisions that should be inherited as essential context for the Atlas as a whole.","contentHash":"520af989ba09049debd5ee71320c41f3c5d3926746d6cff5187bb0e87d32ec07","addressRefs":[]},"c7d62f28-1d64-4632-8cd8-4f2b44c51bba":{"id":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","doc_no":"A.0.1.1","title":"Definitions","type":"Section","depth":3,"parentId":"56b15d7d-cdd4-4594-bd95-4f094564ac04","order":2,"content":"This Section contains essential definitions that are to be inherited as context for all Atlas documents.","contentHash":"8e58a1ce815a166780ad08a4415747dcfea1d712b9621be4e249572a646278db","addressRefs":[]},"4f6fda1e-7450-4065-8095-e93cb10b3a2a":{"id":"4f6fda1e-7450-4065-8095-e93cb10b3a2a","doc_no":"A.0.1.1.1","title":"Organizational Alignment","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":3,"content":"Organizational alignment is a traditional business concept and can be described as the process of implementing strategies and philosophies to ensure that each member of an organization, from entry-level positions to executive managers, shares a common goal and vision for the success of an organization.","contentHash":"c80db34240032af33678c46739a27fed2dafa3cc7b0ead7212273c50c9f95eec","addressRefs":[]},"5e2e1397-ff87-43ce-a742-e5a68dc89a44":{"id":"5e2e1397-ff87-43ce-a742-e5a68dc89a44","doc_no":"A.0.1.1.2","title":"Ecosystem Intelligence","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":4,"content":"\"Ecosystem Intelligence\" characterizes a decentralized ecosystem as a single entity acting with a greater or lesser amount of intelligence. Ecosystem Intelligence is not merely determined by the sum of the intelligence of each of its constituent parts, but rather the alignment of these parts. Counterintuitively, very intelligent, but spiritually misaligned participants in a decentralized ecosystem will actually lower Ecosystem Intelligence.","contentHash":"a12961035094f8ed8d019b2f6d9ace0ff1ba7db26407b8b70859c081ec40e374","addressRefs":[]},"fad68392-c852-4102-81fd-2a4037be38f9":{"id":"fad68392-c852-4102-81fd-2a4037be38f9","doc_no":"A.0.1.1.3","title":"Aligned Structure","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":5,"content":"An aligned structure is a network, ecosystem, entity, or organization that actively employs Alignment Engineering.","contentHash":"da359259b0c1a9aca2e43de475b3dc0550f22fb6194c6f86d01a4a08776c53b8","addressRefs":[]},"9f953b73-566e-4428-a9d2-e179513c3371":{"id":"9f953b73-566e-4428-a9d2-e179513c3371","doc_no":"A.0.1.1.4","title":"Universal Alignment","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":6,"content":"Universal Alignment refers to an actor's holistic understanding of their connection to their environment or context. This enables them to anticipate how their actions influence everything around them, including the second-order effects that impact them in return. This holistic understanding is rooted in the context of human morality, values, and the natural world. An actor who is universally aligned can grasp the intent behind universally aligned rules and identify discrepancies between the technical incentives of rules and their universal purpose. An action that is in opposition to Universal Alignment constitutes misalignment. Preventing misalignment is the fundamental objective of Alignment Engineering and Alignment Artifacts.","contentHash":"a381d6c3f3d5b6b0a2e331a7b333a717290fa2c5ce06ad24f4ea7de89011b397","addressRefs":[]},"2ea378ee-9b12-4e09-9f42-0c6ec65ef33b":{"id":"2ea378ee-9b12-4e09-9f42-0c6ec65ef33b","doc_no":"A.0.1.1.5","title":"Universal Alignment Assumption","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":7,"content":"Universal Alignment is a spectrum, and actors are more or less Universally Aligned.\n\nIn theory, Universal Alignment is absolute, but in practice it cannot be measured deterministically and thus practically will always be subject to debate and changes over time. Alignment Engineering aims to minimize the degree that actors experience their own, and others’, Universal Alignment changing over time.\n\nThe Universal Alignment Assumption holds that the outcomes of Alignment Engineering - namely, the Alignment Artifacts or rules themselves - always have the spirit, or underlying intent, to serve human values and promote the public good within a specific context.","contentHash":"eb7a95901e1b2f1237fd6235fb676c3826817867d881722466d87345b62bef82","addressRefs":[]},"3b712852-26a9-4fb9-8a9a-ebf2332d3efa":{"id":"3b712852-26a9-4fb9-8a9a-ebf2332d3efa","doc_no":"A.0.1.1.6","title":"Alignment Artifact Strength","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":8,"content":"The strength of an Alignment Artifact dictates the minimum level of Universal Alignment that an actor must possess in order to take actions that are universally aligned when interacting with the Artifact.\n\nAlignment Artifact Strength is enhanced by ensuring that Ecosystem Intelligence evolves such that each actor’s self-interested incentives correspond as precisely as possible with requirements of Universal Alignment. This alignment minimizes the additional effort, or \"inner incentive\", that an actor must exert to overcome misalignment.\n\nThe stronger an Alignment Artifact, the less inner incentive that an actor need possess to take actions that are universally aligned.","contentHash":"ddc6a3754d8ed8e49cc024a30ec9d14198ab6dadfef5d2ab2c2509c5d63aaeb6","addressRefs":[]},"102b11a3-9c8c-423e-bd5f-a0988048f11e":{"id":"102b11a3-9c8c-423e-bd5f-a0988048f11e","doc_no":"A.0.1.1.7","title":"Inner Incentive","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":9,"content":"Inner incentive is the second-order incentive that a universally aligned actor uses to counteract the first-order (or self-interested) incentives that exist pre-Alignment Engineering or that arise from a misaligned structure.","contentHash":"e521eb0aa17f984edd5622eb456796ea74505dde62163e0ca8277409a6265121","addressRefs":[]},"3caef1a5-8d59-4a00-846c-fc0f060b3f05":{"id":"3caef1a5-8d59-4a00-846c-fc0f060b3f05","doc_no":"A.0.1.1.8","title":"Alignment Engineering","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":10,"content":"Alignment Engineering is a philosophy of organizational design introduced through the Atlas. It aims to anchor internally sustainable Ecosystem Intelligence within Alignment Artifacts that embody recursive trends towards increased Alignment Artifact Strength over time.","contentHash":"f589d249fb9ce4791d0adabe8a13e0b0089c409ed9b8ab50a447acb35a7e5dc2","addressRefs":[]},"ff16fd74-3a81-4cac-92b4-1208d4d9f337":{"id":"ff16fd74-3a81-4cac-92b4-1208d4d9f337","doc_no":"A.0.1.1.9","title":"Letter Of The Rule Vs Spirit Of The Rule","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":11,"content":"The distinction between the \"letter of the rule\" and the \"spirit of the rule\" refers to whether an individual interprets and follows a rule strictly based on its precise wording, or instead also considers its underlying intent or larger purpose. The Universal Alignment Assumption holds that the underlying intent of rules always aims to serve human values and promote public benefit within a given context.\n\nA \"letter of the rule\" interpretation adheres strictly to the rule’s language, often exploiting ambiguities or loopholes to achieve a specific outcome. This approach allows the rule’s exact wording, even if flawed or misaligned with its goals, to dictate the result, particularly if it benefits the interpreter.\n\nA \"spirit of the rule\" interpretation seeks to comprehend the rule’s true purpose and how it contributes to Universal Alignment, while remaining bound by the letter of the rule. When faced with inconsistencies or errors in the rule’s language, this approach appeals to a pre-established method for disabling, disregarding or substituting the rule as needed to prevent outcomes that contradict its intended objective and the greater purpose it serves.\n\nExample:\n\nImagine a large corporation discovers a loophole in the environmental regulation of its jurisdiction that allows them to generate profits by using a specific type of pollutant that isn’t regulated as a greenhouse gas, but is as harmful as regulated greenhouse gasses.\n\nBy exploiting the \"letter of the rule,\" the corporation complies with the regulations on paper but continues to harm the environment and public health in practice.\n\nA universally aligned actor, such as an environmentally conscious competitor, would interpret the regulations based on their \"spirit\" or underlying purpose — protecting the environment and public health. Recognizing that exploiting the loophole contradicts the regulations’ intent, the universally aligned actor would voluntarily choose not to emit the harmful pollutant, even though doing so might be profitable and technically legal. A universally aligned actor would also actively work with the government and other stakeholders to close the loophole and strengthen the regulations to ensure that they effectively serve their intended purpose, and to protect themselves from misaligned competitors.","contentHash":"7e4aa98332eae6164effa18dd253745493f3b5419a88588b323f46cfd8db049f","addressRefs":[]},"2fc27ce9-6f40-4ed5-934c-97189ea5301b":{"id":"2fc27ce9-6f40-4ed5-934c-97189ea5301b","doc_no":"A.0.1.1.10","title":"Incentivized Alignment","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":12,"content":"Incentivized Alignment is the outcome of an actor’s myopic and self-interested following of the letter of the rule with the first-order incentives of an Aligned Structure, but is not likely to be inherently Universally Aligned and lacks Inner Incentive.","contentHash":"7ae39e58551399e5aae2784720fd760a11947fc4710ff5f59f8254617169dea0","addressRefs":[]},"60066e0f-3db7-45c7-9664-8120a4fbd38b":{"id":"60066e0f-3db7-45c7-9664-8120a4fbd38b","doc_no":"A.0.1.1.11","title":"Misalignment","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":13,"content":"Misalignment characterizes the state in which an actor does not possess Universal Alignment, or acts in a way that opposes or contradicts Universal Alignment.","contentHash":"f16e0d5e48f20798abd93744334955b29960c6c61bafc094ab5b606fd4e11eb9","addressRefs":[]},"adf7ccb3-9ef0-43e0-90cc-6eb9d779f9cd":{"id":"adf7ccb3-9ef0-43e0-90cc-6eb9d779f9cd","doc_no":"A.0.1.1.12","title":"Slippery Slope Misalignment","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":14,"content":"Slippery Slope Misalignment is the shortest path to misalignment where incremental misaligned acts are justified in various ways. These can include ignoring the potential significance and larger impact of acts due to their small scale; the trivial way that misalignment occurs; the good intentions of the actor; or the conviction that the ends justify the means.\n\nUnderstanding Slippery Slope Misalignment means understanding that any misalignment at all is always very serious and, if not dealt with, results in increased risk of disequilibrium and alignment failure. In the context of a decentralized ecosystem such as Sky, this could mean a governance attack or financial collapse.","contentHash":"4a3a79e6933dabfb69d8d4ed9fde458e8fe1c4f5d31eaf116bdc52c295ed573f","addressRefs":[]},"f30e56f9-da71-44bc-ab3b-9b13348794fe":{"id":"f30e56f9-da71-44bc-ab3b-9b13348794fe","doc_no":"A.0.1.1.13","title":"Scope","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":15,"content":"A Scope is a particular focus area of Sky. There are six Scopes:\n\n- The Governance Scope focuses on Alignment Artifact interpretation and balance of powers.\n- The Support Scope focuses on ecosystem support, tools, and activities, including the Sky Primitives.\n- The Stability Scope focuses on financial stability and the core USDS Stablecoin product.\n- The Protocol Scope focuses on technical development, maintenance, and security.\n- The Accessibility Scope focuses on frontends and distribution.\n- The Agent Scope contains all Agent Artifacts.","contentHash":"07720ebf3ebaf0994e7fe1f8f7d33490e0825a0b3ca42d1949e793644480bc1f","addressRefs":[]},"551885ea-d851-4b76-afa1-5ea57f724c9a":{"id":"551885ea-d851-4b76-afa1-5ea57f724c9a","doc_no":"A.0.1.1.14","title":"Alignment Artifact","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":16,"content":"Alignment Artifacts are outputs of Alignment Engineering, and can be used by universally aligned actors to coordinate to achieve a positive-sum outcome.","contentHash":"18342f65c8ea6eccc1cd095710099b6ee60f8273ecd27516e95e0e82dc22ad9f","addressRefs":[]},"10cb8335-18e3-466e-9a0a-b076c1719de5":{"id":"10cb8335-18e3-466e-9a0a-b076c1719de5","doc_no":"A.0.1.1.15","title":"Scope Alignment Artifact (Scope Artifact)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":17,"content":"A Scope Artifact is an Alignment Artifact designed to align the actions and incentives of participants within a specific Scope defined by the Atlas. It provides a framework for decision-making, resource allocation, and governance within the defined Scope.\n\nEach Scope has its own unique set of challenges and objectives that require a tailored approach to alignment.\n\nThe strength of a Scope Alignment Artifact depends on how well it aligns with Universal Alignment principles, as well as how effectively it is communicated and understood by participants within the defined Scope. A strong Scope Artifact can help prevent misalignment and ensure that all participants are working towards a common goal for the benefit of the entire ecosystem.\n\nScope Artifacts must not be changed beyond the Scope boundaries defined by the Atlas; this constitutes Slippery Slope Misalignment.","contentHash":"f8f8fb5709a96f6ebdf65a5ebafca876635b3bc57c78d447c3787cef44f0060f","addressRefs":[]},"98223867-c60a-4b28-9401-94fc1ed9b4cd":{"id":"98223867-c60a-4b28-9401-94fc1ed9b4cd","doc_no":"A.0.1.1.16","title":"The Atlas","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":18,"content":"The Atlas is the foundational set of rules powering Sky Ecosystem. It consists of Immutable Documents and Adaptive Documents. The former enshrine the Spirit of the Atlas and become permanently immutable from the moment the Sky Ecosystem enters the Endgame State. The Adaptive Documents practically operationalize the Spirit of the Atlas and will be continuously improved through the Sky Governance process. The Immutable part of the Atlas ensures the aligned evolution of Sky: it mitigates the potential and actual damage caused by Slippery Slope Misalignment, which erodes the potency of Alignment Engineering over time.","contentHash":"2e702f9ef25a2bbea093bdfa44ea44da6646fe15329faac667b2e12e7249a936","addressRefs":[]},"94a451ce-100c-4ff5-8d53-65953938ecde":{"id":"94a451ce-100c-4ff5-8d53-65953938ecde","doc_no":"A.0.1.1.17","title":"Alignment Conserver (AC)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":19,"content":"Alignment Conservers (ACs) are external entities that play a fundamental role in facilitating and protecting the Sky Governance process by ensuring it occurs according to the processes defined in the Atlas. ACs enable SKY holders to participate in Sky Governance in a manner where it is easy for SKY holders to make the decisions that best benefit their long-term interests as SKY holders, even if SKY holders overall have relatively little alignment.","contentHash":"6c517d7159318899b7057ac0f630e2b6c779f53bdb95d675090f26a1efac255e","addressRefs":[]},"8ea04ed4-7075-45e6-b6ed-a52b7506f4a8":{"id":"8ea04ed4-7075-45e6-b6ed-a52b7506f4a8","doc_no":"A.0.1.1.18","title":"Aligned Delegate (AD)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":20,"content":"Aligned Delegates (ADs) are anonymous Alignment Conservers that use Delegate Contracts to enable SKY holders to easily and safely delegate their SKY voting power.\n\nBecause they directly control large amounts of incentivized SKY voting power, ADs are both highly influential and potentially risky actors within the governance framework. The Atlas empowers ADs and other Ecosystem Actors with the tools to derisk ADs’ influence in the ecosystem.\n\nThe primary responsibility of ADs is to use their delegated power to uphold the Spirit of the Atlas and maintain Universal Alignment of the Sky Ecosystem. ADs are subject to strict requirements enforced by the Governance Scope.","contentHash":"223f2be39fad33e18ae2746862a360ff20b74866cdc80b8f8490459232dfbf4c","addressRefs":[]},"912e0161-3448-470f-9cf6-d1a26d76acab":{"id":"912e0161-3448-470f-9cf6-d1a26d76acab","doc_no":"A.0.1.1.19","title":"Facilitator","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":21,"content":"Facilitators are anonymous Alignment Conservers with responsibility over specific Scopes. Facilitators can directly access governance processes and smart contracts to fulfill their responsibilities.","contentHash":"61bc18c2dd3ecc352a6b04af42ece5eff5f7e24326e49974de4086a37791ae7e","addressRefs":[]},"72e08874-de00-40dd-aa2b-be76ff754902":{"id":"72e08874-de00-40dd-aa2b-be76ff754902","doc_no":"A.0.1.1.20","title":"Communication Channel","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":22,"content":"Communication Channels are a critical consideration in the Atlas as they have a significant impact on incentivized alignment.","contentHash":"725c9a09d57541b6f571f1e881dd14789baf452fd1bf8d9a9aba19f53478e1dd","addressRefs":[]},"72f9b4d1-695b-489c-a060-db0013ba0466":{"id":"72f9b4d1-695b-489c-a060-db0013ba0466","doc_no":"A.0.1.1.21","title":"Governance Scope (GOV)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":23,"content":"The Governance Scope Alignment Artifact codifies rules that regulate the critical balance-of-power processes defined in the Atlas, and adjudicate on appeals processes related to misalignment in the ecosystem.","contentHash":"563985f4d6fa9bcbd6edebc5ca35ae4fae878612a23b22eddf3d1fc0c52a2753","addressRefs":[]},"334492f3-db84-4f8b-9593-93cefe72900a":{"id":"334492f3-db84-4f8b-9593-93cefe72900a","doc_no":"A.0.1.1.22","title":"Support Scope (SUP)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":24,"content":"The Support Scope Alignment Artifact codifies rules that regulate various tasks of ecosystem support, including governance process infrastructure and management and Agent ecosystem support.","contentHash":"2135086b2e048f2350e5d3e899a815b8b75502f99eedc859246c8066b1deb48a","addressRefs":[]},"b24446c1-44d2-408a-9077-d397fa173132":{"id":"b24446c1-44d2-408a-9077-d397fa173132","doc_no":"A.0.1.1.23","title":"Protocol Scope (PRO)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":25,"content":"The Protocol Scope Alignment Artifact codifies rules related to the core technical Sky protocol.","contentHash":"6e2e9aa49d30bdc918be3a6f87db9db2af608d0ff54e83dd5d8f5ddb4be42a23","addressRefs":[]},"6a900766-15ff-49b1-bed5-59f58b9c49c7":{"id":"6a900766-15ff-49b1-bed5-59f58b9c49c7","doc_no":"A.0.1.1.24","title":"Stability Scope (STA)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":26,"content":"The Stability Scope Alignment Artifact codifies the rules related to managing the core Stablecoin product, USDS, and supporting factors related to financial stability, such as surplus buffer and decentralized asset reserve.","contentHash":"c7ec5e6bf4ceae00dc8e895610fa9194755500de0ae1d2a5a1a9a7644e3b0b71","addressRefs":[]},"1109f780-d48a-4712-8106-848952b684a4":{"id":"1109f780-d48a-4712-8106-848952b684a4","doc_no":"A.0.1.1.25","title":"Accessibility Scope (ACC)","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":27,"content":"The Accessibility Scope defines rules related to accessibility and distribution efforts and regulates user-facing frontends.","contentHash":"845066438d615ea07d344dbdd13d34a307fc0dafd2eb27dfd001383bbbef427c","addressRefs":[]},"7e629109-1d84-46da-a986-94036be81e93":{"id":"7e629109-1d84-46da-a986-94036be81e93","doc_no":"A.0.1.1.26","title":"Governance Equilibrium","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":28,"content":"A Governance Equilibrium is a state in a Decentralized Governance dynamic where the governance process is able to remain decentralized over time with a very high degree of confidence. It requires redundant feedback loops that can counteract the natural incentives that push the governance process towards disequilibrium and centralization.","contentHash":"3edae5568252d0bf05f5cda9b99acb1b1e9d10324a195bf181deffe2a074fdd2","addressRefs":[]},"8a57b601-aec4-49dc-bf34-383c63da11de":{"id":"8a57b601-aec4-49dc-bf34-383c63da11de","doc_no":"A.0.1.1.27","title":"Endgame State","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":29,"content":"Endgame State is the final technical and alignment engineering state of Sky, in which all aspects of the ecosystem that can be made immutable, have been made immutable. The aim of the Endgame State is to create a highly resilient Governance Equilibrium.","contentHash":"3803ffaa5da3e91e4fa3c046a6553517902a8d6304af4eea6f6454dd67f77069","addressRefs":[]},"a5a8a3e5-3d79-4c37-acce-4ac34a459cae":{"id":"a5a8a3e5-3d79-4c37-acce-4ac34a459cae","doc_no":"A.0.1.1.28","title":"Explicit Incentives","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":30,"content":"Explicit Incentives are the first-order incentives that are coded into rules in Alignment Artifacts.","contentHash":"135c7a556d791b947d09e65fdca4a02ccb6c12bd6328d76c7bd7ebcb0525f79b","addressRefs":[]},"2c824e12-3ec1-4007-9294-ef15d25ccdca":{"id":"2c824e12-3ec1-4007-9294-ef15d25ccdca","doc_no":"A.0.1.1.29","title":"Implicit Incentives","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":31,"content":"Implicit Incentives are the motivations or benefits that an actor can infer based on a ‘letter of the rules’ interpretation of an Alignment Artifact, and an assessment of the likelihood that these rules will be enforced.","contentHash":"64354862e01236ff067de80e24976127b73ae51146f386431c9003204e077928","addressRefs":[]},"133c6032-0082-4644-a3d5-87bcf5b30249":{"id":"133c6032-0082-4644-a3d5-87bcf5b30249","doc_no":"A.0.1.1.30","title":"Incentive Slack","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":32,"content":"Incentive Slack refers to the discrepancy between the explicit incentives (those clearly defined and communicated) and the implicit incentives (those inferred by actors) within an Aligned Structure. Incentive Slack can arise when coded rules are either not enforced or are too restrictive or impractical, leading to a pattern of bypassing these rules. When Incentive Slack is high, it creates the perception that rules are likely to be ignored, without regard for the spirit of the rules. This results in a significant risk of widespread misalignment. Incentive Slack cannot occur in an Aligned Structure in which actors are universally aligned and actively enforcing the rules.","contentHash":"32b3d13707be9bed3ffa74bf163f7b7e7d100c442d2eb153cca4eceef02898b8","addressRefs":[]},"20f8b661-37c0-4d16-9238-d9595bbcb4cf":{"id":"20f8b661-37c0-4d16-9238-d9595bbcb4cf","doc_no":"A.0.1.1.31","title":"Whole Weeks","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":33,"content":"The Atlas defines quarterly and yearly cycles that determine fixed points in time by counting whole weeks from the beginning of a quarter. The first whole week of a quarter is defined as the first week in which all days, beginning with Monday, fall within the quarter. Another definition would be \"the week starting with the first Monday of the quarter.\"","contentHash":"d633547f0eb1f4e823948b3b72c40312dd5cbf14764449244c27599966eb7ad5","addressRefs":[]},"6a2c7245-8d67-4de0-80af-ce953352e1bb":{"id":"6a2c7245-8d67-4de0-80af-ce953352e1bb","doc_no":"A.0.1.1.32","title":"SKY Staking","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":34,"content":"When a user stakes their SKY tokens, they receive Staking Rewards. Staked SKY can be freely unstaked at any time. SKY Staking also allows users to borrow USDS against their SKY at the SKY Borrow Rate.","contentHash":"2c82283dc21da01ab94aa16c611e36a156172d63ce4b2f39ab7986289e528e86","addressRefs":[]},"f0de89da-576a-4710-982e-40acf7f065cc":{"id":"f0de89da-576a-4710-982e-40acf7f065cc","doc_no":"A.0.1.1.33","title":"Skylink","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":35,"content":"Skylink is the Sky Ecosystem’s multichain solution, connecting USDS, SKY and other Sky Ecosystem tokens from the Ethereum Mainnet to other chains and L2 protocols. Skylink will make all core Sky features available on the chains and L2s it is deployed to, including Native USDS; Native Sky Savings Rate; Native Token Rewards and Native 1:1 conversion between USDC and USDS.","contentHash":"52522ba82b63ededfafbca87d95904a622cc983e4ce31f137b3dddef77e91d8d","addressRefs":[]},"575ab954-d26c-460e-8a11-ebe7f5586dff":{"id":"575ab954-d26c-460e-8a11-ebe7f5586dff","doc_no":"A.0.1.1.34","title":"Target Document","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":36,"content":"The term \"Target Document\" refers to the Immutable or Primary Document to which a Supporting Document is attached. Supporting Documents have various functions, including providing expanded definitions of vague or ambiguous terms in their Target Document; and providing hypothetical fact-patterns to illustrate the practical application of their Target Document. See [A.1.2.2.1.3 - Supporting Document Category](e87b6850-3792-495d-9460-0ac069a217e6).","contentHash":"eb0efd24fe0da3da73141813be3109de7b9fcc90136e6882bea2bde305a30b40","addressRefs":[]},"44221aff-ad7c-41d3-a861-8a30963054fa":{"id":"44221aff-ad7c-41d3-a861-8a30963054fa","doc_no":"A.0.1.1.35","title":"Voting Power","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":37,"content":"\"Voting Power\" denotes the ability of Aligned Delegates to vote on Sky governance decisions on behalf of a SKY holder. SKY holders can delegate their Voting Power to an Aligned Delegate through Delegate Contracts, allowing the Aligned Delegate to vote on their behalf while the SKY holders retain control of their tokens.","contentHash":"a58a9235d66a59b96eb3867f272c4b91bd789dd5d3f94780f10d3c6350b5bf8d","addressRefs":[]},"591e1ba4-1f3e-44ac-9f4c-3f5d680f33d4":{"id":"591e1ba4-1f3e-44ac-9f4c-3f5d680f33d4","doc_no":"A.0.1.1.36","title":"stUSDS","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":38,"content":"The token used to provide the capital for SKY Staking leverage is called stUSDS. It ensures that all SKY-backed borrowing is funded by segregated risk capital. Users can deposit USDS into a smart contract and receive stUSDS, which can later be converted back to USDS as long as there is unutilized USDS in the stUSDS converter smart contract.","contentHash":"1a05b51153000adc1a3b6f607a7522cb7ec3714d03998c75f8279177a334111b","addressRefs":[]},"86977920-c857-4a86-91ac-1a7571137c18":{"id":"86977920-c857-4a86-91ac-1a7571137c18","doc_no":"A.0.1.1.37","title":"Unrewarded USDS","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":39,"content":"Unrewarded USDS are USDS balances that are not receiving the Sky Savings Rate, Integration Boost or USDS Token Rewards. USDS Token Rewards include both SKY and Agent token rewards.","contentHash":"d3f16de366af37be50b91b9f11a587f326e35b52d0373bb5da9324166839cc70","addressRefs":[]},"e78e8fbb-0602-4e67-8c44-88b1f0b30704":{"id":"e78e8fbb-0602-4e67-8c44-88b1f0b30704","doc_no":"A.0.1.1.38","title":"Sky Forum","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":40,"content":"The Sky Forum serves as a dedicated platform for governance across the Sky Ecosystem. Community members submit proposals, engage in debate, and align on decisions. Posts are organized by category according to subject matter. For example, proposals or discussions concerning Sky Core must use the \"Sky Core\" category, while those pertaining to Primes must use the Prime category associated with the Agent. Authors should also apply relevant tags to improve discoverability and cross-referencing. The forum is located at [https://forum.skyeco.com/](https://forum.skyeco.com/).","contentHash":"f53ec3b1053bbd336a2ac06c1fc666013ecbdf10fb5d49af949cf891d95f551b","addressRefs":[]},"3c18e6a7-95b8-44e9-8da6-1eadf3fdd356":{"id":"3c18e6a7-95b8-44e9-8da6-1eadf3fdd356","doc_no":"A.0.1.1.39","title":"Agent","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":41,"content":"Agents are first-class economic citizens of Sky that autonomously pursue business opportunities. Each Agent has its own Agent Artifact and token. Initially, the creation of an Agent results in a Proto-Agent, which lacks any specialized role. To gain functionality within the Sky ecosystem, a Proto-Agent must deploy a special Transformation Primitive to transform into a specific Agent sub-type. The Agent sub-types currently defined in the Atlas include 1) Prime Agent and 2) Executor Agent, with the Executor Agent sub-type further divided into Operational Executor Agents and Core Executor Agents.\n\nAlthough Executor Agents are not yet operational, the Atlas nonetheless defines the foundational rules, processes, and governance structures necessary for their eventual activation. In the medium to long term, these Executor Agents will become fully operative and perform an essential function in facilitating the activities of Prime Agents across the Sky ecosystem.","contentHash":"e8993a22ac7fdc05404fe2bd8c3c57c2c0a584eb238f7a8a7d3595992f9ab524","addressRefs":[]},"8d081c1a-6393-4aaf-8914-8959cdf2fee3":{"id":"8d081c1a-6393-4aaf-8914-8959cdf2fee3","doc_no":"A.0.1.1.40","title":"Agent Artifact","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":42,"content":"Agent Artifacts contain all rules, processes, parameters, and knowledge of the Agent. Agent Artifacts must be aligned with, and are fully subordinate to, the Sky Core Atlas.","contentHash":"b678a37242f1ba1c49c56ff21eea7cf326df602b2a102b38d09ae85b5b68df89","addressRefs":[]},"87dafa99-c36e-4e68-ac19-fccac4b3834d":{"id":"87dafa99-c36e-4e68-ac19-fccac4b3834d","doc_no":"A.0.1.1.41","title":"Agent Scope","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":43,"content":"The Agent Scope codifies all Agent Artifacts.","contentHash":"468eaa3bb4b97b5a6f13700104f4f8a95038d6ea9c39eab138f427bc84c45f4d","addressRefs":[]},"a8454271-c090-4084-b022-4430e3def93c":{"id":"a8454271-c090-4084-b022-4430e3def93c","doc_no":"A.0.1.1.42","title":"Prime Agent","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":44,"content":"Prime Agents maintain and automate Sky features in new markets, and innovate custom products. Prime Agents are the only Agent type that can access all Sky Primitives; whereas Executor Agents are limited in the Primitives they can access.\n\n- Prime Agents cannot directly operationalize those elements of their strategies that directly interface with the Sky Protocol or shared ecosystem infrastructure. For such protocol-level and ecosystem-critical operations, Prime Agents must rely on Operational Executor Agents for implementation.\n- When a Prime Agent formulates a new initiative, it encodes the relevant instructions and parameters into its Agent Artifact. Insofar as the Prime Agent’s Artifact requires protocol-level interactions, the Operational Executors use the Artifact as a detailed operational blueprint for implementing the Prime Agent’s directives—ensuring consistency with the Atlas and minimizing risk.\n- This ensures a robust division between Prime Agents’ strategic, externally facing activities and the specialized operational activities that directly interface with Sky’s core systems.","contentHash":"c9ed6ceaba2843585bac56b2574b5ef886b60a5549926b329ecc00b0d435c4ea","addressRefs":[]},"ac514975-66ad-4b43-8f76-42cac5ca599d":{"id":"ac514975-66ad-4b43-8f76-42cac5ca599d","doc_no":"A.0.1.1.43","title":"Executor Agent","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":45,"content":"Executor Agents (\"Executors\") are specialized Agents that implement those elements of a Prime Agent’s activities that directly interface with the Sky Protocol or shared ecosystem resources, leaving Prime Agents free to focus on strategic, business development, and marketing efforts. There are two Executor sub-types: Core Executor Agents (\"Core Executor Agents\") and Operational Executor Agents (\"Operational Executors\").\n\n- Operational Executor Agents handle the day-to-day execution of those portions of a Prime Agent’s strategies that directly interface with the Sky Protocol, strictly following the instructions laid out in each Prime Agent’s Artifact. Prime Agents cannot be active in the Sky Ecosystem unless they have an active \"Operational Executor Accord\" which codifies their relationship with an Operational Executor. Operational Executors take on the risk of Prime Agents’ outcomes by providing collateralized insurance against losses or liabilities. Operational Executor Agents’ Operational Collateral can also cover losses from negligence or malicious behavior by the Operational Executor in carrying out the Prime Agent’s strategy.\n- Core Executor Agents, on the other hand, oversee the activities of Operational Executors, ensuring that the implementation of Prime Agent strategies aligns with the Atlas.\n- By separating strategy from operations, this division of labor empowers Prime Agents to innovate rapidly and expand their ventures without needing to develop specialized operational expertise, as Operational Executors manage the day-to-day technical implementation under the oversight of Core Executor Agents.","contentHash":"3ac1b29964d2df7c84f2c42980210c6b80e44231595b0caa46a9aae073a04daf","addressRefs":[]},"23253343-23e3-440f-90c0-43d3437c2098":{"id":"23253343-23e3-440f-90c0-43d3437c2098","doc_no":"A.0.1.1.44","title":"Operational Executor Agent","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":46,"content":"Operational Executor Agents (\"Operational Executors\") are specialized Executor Agents tasked with implementing and verifying those elements of a Prime Agent’s strategy that directly interface with the Sky Protocol or shared ecosystem resources. While Prime Agents autonomously set strategic direction, Operational Executors are responsible for operationalizing those activities that modify on-chain or protocol-level state, relying on the relevant Primitive Configuration Documents in the Agent Artifact.\n\nEach Operational Executor Agent must comprise at least one Facilitator and at least one GovOps actor. Facilitators are responsible for interpreting the Atlas and the Agent Artifact and instructing GovOps actors to carry out the corresponding actions. To ensure accountability and mitigate potential risks, Operational Executor Agents must maintain Operational Collateral, which serves as a guarantee to cover losses or damages resulting from negligence or malicious behavior by either Facilitators or GovOps actors.","contentHash":"d2d49d88ace61817237e0b2fcc3390e8e875a897d90d069f68d2e3776d143937","addressRefs":[]},"2a440474-20d1-4703-a57b-35e0cebb881c":{"id":"2a440474-20d1-4703-a57b-35e0cebb881c","doc_no":"A.0.1.1.45","title":"Core Council Executor Agent","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":47,"content":"Core Council Executor Agents (\"Core Executor Agents\") are Executor Agents who serve on the Core Council and act as checks on Operational Executor Agents.","contentHash":"326a684206dbd8969efb9aff018ce022c6750f061c0eb5fb70550f9d6ce10f79","addressRefs":[]},"5a03a0c4-a47a-409c-9b23-52ac93e63d45":{"id":"5a03a0c4-a47a-409c-9b23-52ac93e63d45","doc_no":"A.0.1.1.46","title":"Core Council","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":48,"content":"The Core Council is a group of Executors responsible for operationalizing the protocol at the Sky Core level. It monitors Operational Executor compliance and enforces the Sky Core Atlas. It also oversees Sky Core governance processes, evolves the Risk Framework, monitors Alignment Conservers, and addresses governance disputes. The Council begins with a single seat held by Core Council Executor Agent 1 and will expand over time to multiple elected seats on a rotational basis, targeting up to seven members in the long term.","contentHash":"ea0b7132231110e06a6ae81f5ab75397468f992bfb5fe7a6021a3019ec369ccc","addressRefs":[]},"1e73ee4b-823d-406a-af54-223b43bc8e42":{"id":"1e73ee4b-823d-406a-af54-223b43bc8e42","doc_no":"A.0.1.1.47","title":"GovOps","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":49,"content":"Governance Operations (\"GovOps\") actors are specialized Ecosystem Actors operating within Executor Agent entities. They manage the technical implementation of Prime Agents’ Instances of Sky Primitives by carrying out on-chain/off-chain tasks necessary for Prime Agents’ operational and governance processes. They work in tandem with Executor Facilitators, who interpret the Atlas and the Agent Artifact.","contentHash":"a997a6c7dafabc37b6d22484aba70f6430a6d07e6996750a1e04a28a007353b5","addressRefs":[]},"80c7e2e1-a2af-47dd-80c7-aee6823cca91":{"id":"80c7e2e1-a2af-47dd-80c7-aee6823cca91","doc_no":"A.0.1.1.48","title":"Operational Executor GovOps","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":50,"content":"Operational Executor GovOps (\"Operational GovOps\") actors are GovOps actors that operate within Operational Executor Agents. Operational GovOps play a crucial role in implementing Prime Agent strategies, doing so by executing the technical specifications outlined in Primitive Configuration Documents of Agent Artifacts.","contentHash":"84b13af618a12d0b066fbe74fc7309ea947555ec44a31fca900a9f7deb195e31","addressRefs":[]},"e512e890-629f-450f-a14d-a3ea06a369c0":{"id":"e512e890-629f-450f-a14d-a3ea06a369c0","doc_no":"A.0.1.1.49","title":"Core Council GovOps","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":51,"content":"Core Council GovOps (\"Core GovOps\") actors are GovOps actors that operate within Core Executor Agents.","contentHash":"33adc7aa9e0f63421553179ff80264632c83f1511ffc8d52671269a4e31cd20b","addressRefs":[]},"2d984fe4-c1d7-4ac3-835b-19f19a3a5505":{"id":"2d984fe4-c1d7-4ac3-835b-19f19a3a5505","doc_no":"A.0.1.1.50","title":"Operational Executor Facilitator","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":52,"content":"Operational Executor Facilitators are Facilitators that interpret Artifacts and the Atlas on behalf of Operational Executor Agents.","contentHash":"ae2a91e213534a73bdf77d757109592c506c6f006f24472713d871f2ecce9c47","addressRefs":[]},"453e9bfb-2776-486d-b451-35742e49e0ab":{"id":"453e9bfb-2776-486d-b451-35742e49e0ab","doc_no":"A.0.1.1.51","title":"Core Council Executor Facilitator","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":53,"content":"Core Council Executor Facilitators (\"Core Facilitator\") interpret Artifacts and the Atlas on behalf of Core Executor Agents.","contentHash":"a83dbee1f627ccd3eb92f5db781e76485358513d0ec49d7b63bcf01e12b8abdb","addressRefs":[]},"ae14941a-635e-4022-af4d-2bec2827fbbf":{"id":"ae14941a-635e-4022-af4d-2bec2827fbbf","doc_no":"A.0.1.1.52","title":"Sky Primitives","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":54,"content":"Sky Primitives are the core building blocks of the Sky ecosystem, serving as the primary interface between Agents and the Atlas. By providing a standardized set of tools and interfaces, Sky Primitives empower Prime Agents to create, innovate, and evolve the Sky Protocol in a decentralized manner. The Sky Primitives are also used by Executor Agents, which serve as the robust and standardized intermediary layer between Prime Agents and the Sky Protocol.","contentHash":"ab36a785311f753955748bfc2c39e783ea926557ac274c79a20b9316fefbb1fb","addressRefs":[]},"cb66c28b-c05f-4ccc-ad44-f05aacf78b9c":{"id":"cb66c28b-c05f-4ccc-ad44-f05aacf78b9c","doc_no":"A.0.1.1.53","title":"Conformance","type":"Core","depth":4,"parentId":"c7d62f28-1d64-4632-8cd8-4f2b44c51bba","order":55,"content":"Conformance characterizes the state in which a Synome Document accurately operationalizes the principles, rules, and processes specified by the Atlas Documents.","contentHash":"8c366947c3d2ce0631cea864e8742e43f82019ed81bd7cb7a7baffbe0d372772","addressRefs":[]},"b5c97151-07b9-4679-8896-478ccafa86b9":{"id":"b5c97151-07b9-4679-8896-478ccafa86b9","doc_no":"A.0.1.2","title":"General Provisions","type":"Section","depth":3,"parentId":"56b15d7d-cdd4-4594-bd95-4f094564ac04","order":56,"content":"This Section contains general provisions that are to be inherited as context for all Atlas documents.","contentHash":"c27053b60be6ea20cd0a9a4005e5dddbbf164db5f998026f7f1a7f939ac11612","addressRefs":[]},"f18229fe-fbc3-4dc8-ad84-4bca2915f6c4":{"id":"f18229fe-fbc3-4dc8-ad84-4bca2915f6c4","doc_no":"A.0.1.2.1","title":"Facilitators’ Broad Discretionary Capacity","type":"Core","depth":4,"parentId":"b5c97151-07b9-4679-8896-478ccafa86b9","order":57,"content":"The next-generation Atlas is a self-contained governance infrastructure powering the Sky Ecosystem. It is designed to grow in tandem with the adaptive intelligence of the Ecosystem. Yet these first iterations of the next-generation Atlas may not sufficiently account for the critical, unforeseen contingencies that can arise, particularly as the Protocol is in a dynamic period of evolution.\n\nTo ensure the Ecosystem grows in resilience and advances toward the Endgame State, it must be able to respond quickly to pressing changes in its environment. To facilitate this, the Core Facilitator is granted broad discretionary power, given their close proximity to, and knowledge of, the Sky Ecosystem.\n\nWhere the Atlas does not provide clear guidance on a current challenge, the Core Facilitator is empowered to infer the Spirit of the Atlas in such a way as to maximize Universal Alignment and secure the Ecosystem’s growth, security and progression toward the Endgame State.\n\nThe Core Facilitator also has the discretion to supersede existing Atlas provisions where they determine the latter to be unsuitable for current challenges.\n\nThe discretionary power granted herein is temporary.","contentHash":"571bd3c1b82bddc153424c33aba5eb06656419aa2090cf1e9bff4170dd2d4bc1","addressRefs":[]},"abd2a3e6-897c-4a2a-af5c-b06da3429912":{"id":"abd2a3e6-897c-4a2a-af5c-b06da3429912","doc_no":"A.0.1.2.1.1","title":"Authorization To Run Bootstrapping Governance Poll","type":"Core","depth":5,"parentId":"f18229fe-fbc3-4dc8-ad84-4bca2915f6c4","order":58,"content":"The Core Facilitator can run a Bootstrapping Governance Poll at any time to enable SKY holders to vote on needed changes to the Atlas. The Core Facilitator can do this on their own initiative.\n\nWhere feasible, the Core Facilitator is encouraged to run a Governance Poll to formalize actions taken pursuant to [A.0.1.2.1 - Facilitators’ Broad Discretionary Capacity](f18229fe-fbc3-4dc8-ad84-4bca2915f6c4).","contentHash":"399aeac6e30fc777f2bc6646224d5b4991b36a258e3e4bfecc6cbeca7b7d81d4","addressRefs":[]},"b62f852c-db59-4bf8-a72c-0b825961563d":{"id":"b62f852c-db59-4bf8-a72c-0b825961563d","doc_no":"A.0.1.2.1.1.0.3.1","title":"Formalize Actions - Element Annotation","type":"Annotation","depth":6,"parentId":"abd2a3e6-897c-4a2a-af5c-b06da3429912","order":59,"content":"Facilitators have broad discretionary authority to interpret or supersede the Atlas pursuant to [A.0.1.2.1 - Facilitators’ Broad Discretionary Capacity](f18229fe-fbc3-4dc8-ad84-4bca2915f6c4).\n\nThe element \"formalize actions\" pertains to the recommendation that the Core Facilitator, where feasible, conduct Governance Polls to officially ratify changes in the Atlas that correspond to the actions they have undertaken based on the aforementioned document.\n\nFor example, if the Core Facilitator decides to supersede a particular Atlas document due to its inadequacy in addressing a specific challenge, the Core Facilitator is encouraged to initiate a Governance Poll to allow SKY holders to vote on a revised version of the document that corrects the identified shortcomings.","contentHash":"d65625074545356e7835a410430d6daa8b725e64d3909d24a29352533ab57073","addressRefs":[]},"50a8c7e5-9305-487b-adc2-d05d742e5227":{"id":"50a8c7e5-9305-487b-adc2-d05d742e5227","doc_no":"A.0.1.2.1.1.0.3.2","title":"Where Feasible - Element Annotation","type":"Annotation","depth":6,"parentId":"abd2a3e6-897c-4a2a-af5c-b06da3429912","order":60,"content":"This element \"where feasible\" introduces a degree of flexibility or discretion. It indicates that the Core Facilitator is encouraged to run Governance Polls in the context of the Target Document when it is possible, practical or appropriate to do so.","contentHash":"15fcd0945897fcf13aa57c118b51affffcdfbbf035b87ad3bc501c14ce78d1f0","addressRefs":[]},"4dd8de6f-0593-4d2b-afcd-2460e63fe22b":{"id":"4dd8de6f-0593-4d2b-afcd-2460e63fe22b","doc_no":"A.0.1.2.1.1.0.4.1","title":"Determination Of Feasibility Is Itself At The Discretion of Facilitators","type":"Action Tenet","depth":6,"parentId":"abd2a3e6-897c-4a2a-af5c-b06da3429912","order":61,"content":"The determination of feasibility may depend on factors such as time constraints, resource availability, or the urgency of the decision. The determination of feasibility is itself at the discretion of the Facilitators.","contentHash":"3f7b5e979c870fd135e3560de82fbbb53e025b52e314af44671d75d4a129b729","addressRefs":[]},"a8d562d8-f9ba-4cee-973e-0526cfca439b":{"id":"a8d562d8-f9ba-4cee-973e-0526cfca439b","doc_no":"A.0.1.2.1.1.0.4.2","title":"Formalizing actions via Governance Poll is encouraged, but not mandatory","type":"Action Tenet","depth":6,"parentId":"abd2a3e6-897c-4a2a-af5c-b06da3429912","order":62,"content":"If the Core Facilitator decides to supersede a particular Atlas document due to its inadequacy in addressing a specific challenge, the Facilitator is encouraged, though not required, to initiate a Governance Poll to allow SKY holders to vote on a revised version of the document that corrects the identified shortcomings. The Target Document does not require Facilitators to run a Governance Poll to formalize their actions.\n\nSimilarly, if a Facilitator identifies a gap in the Atlas where a particular need is not explicitly addressed, they may extrapolate a course of action based on their interpretation of the Spirit of the Atlas. In this case, as well, the Target Document does not require Facilitators to run a Governance Poll to formalize their interpretation or extrapolated actions.\n\nThis Action Tenet acknowledges the necessity for Facilitators to possess flexible and broad discretionary authority during the early stages of the Atlas' development. Such flexibility ensures that the ecosystem can swiftly adapt to emerging challenges. Consequently, it is important at this stage to avoid over-formalizing actions and decisions taken by Facilitators pursuant to [A.0.1.2.1 - Facilitators’ Broad Discretionary Capacity](f18229fe-fbc3-4dc8-ad84-4bca2915f6c4).","contentHash":"0527c46335943ca1a5ccea05ddc56a6596dd3c8a861aa649a04b8ebbf6df012f","addressRefs":[]},"fe58827d-5a02-4b84-bd56-8e5d93ef8f48":{"id":"fe58827d-5a02-4b84-bd56-8e5d93ef8f48","doc_no":"A.0.1.2.1.2","title":"Precedence Over Conflicting Provisions","type":"Core","depth":5,"parentId":"f18229fe-fbc3-4dc8-ad84-4bca2915f6c4","order":63,"content":"The broad interpretive and discretionary capacity granted Facilitators by [A.0.1.2.1.2 - Precedence Over Conflicting Provisions](fe58827d-5a02-4b84-bd56-8e5d93ef8f48) takes precedence over any conflicting provisions in the Atlas.","contentHash":"9a9554b93fddd9a04aa868f83136590005ed0ae0614a1a05f378b3a863811e4f","addressRefs":[]},"18ac7dd3-c646-4352-9b0d-d01a2932d7d1":{"id":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","doc_no":"A.1","title":"The Governance Scope","type":"Scope","depth":1,"parentId":null,"order":64,"content":"The Governance Scope regulates the governance processes and balance of power of the Sky Ecosystem. The Governance Scope must ensure that the resilient equilibrium of Sky Governance remains protected against all potential direct and indirect threats.","contentHash":"f84d40deade3b1dbaca6e3f3df8e376dd46de2becb367b02b789a717337975fd","addressRefs":[]},"86a93dab-2f12-4c3f-9285-bcc4520c851b":{"id":"86a93dab-2f12-4c3f-9285-bcc4520c851b","doc_no":"A.1.1","title":"Spirit of the Atlas","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":65,"content":"The Spirit of the Atlas represents the foundational principles of Sky Governance. The Spirit of the Atlas is enshrined in the Immutable Documents, reflected in the Atlas as a whole and enacted by aligned participants of the Sky Ecosystem.","contentHash":"34d1006a6d6810be83b1d8e3d6764df3f2d9fdeecdc7099c2eadd053454116d3","addressRefs":[]},"9524005e-e135-4ba5-aff3-d846923f3874":{"id":"9524005e-e135-4ba5-aff3-d846923f3874","doc_no":"A.1.1.1","title":"Universal Alignment And The Spirit Of The Atlas","type":"Section","depth":3,"parentId":"86a93dab-2f12-4c3f-9285-bcc4520c851b","order":66,"content":"The guiding principles of the Sky Ecosystem, known as the Spirit of the Atlas, form the foundation of the Sky Governance process. These principles are enshrined in the Immutable Documents of the Atlas, enabling coordination around a resilient governance equilibrium that optimizes for Universal Alignment between the ecosystem and its environment. The Immutable Documents take precedence over any other rules, decisions, or governance structures that may conflict with them. The Immutable Documents provide the definitive criteria for determining whether the Sky Ecosystem's rules and incentives are in harmony with Universal Alignment.","contentHash":"3ed7433666ccdd32c14939c3eeb8d2d5ef3266908af642cc7997f9b9f825ab86","addressRefs":[]},"f1b305d3-b4a1-4b00-85fa-6dec8e995e42":{"id":"f1b305d3-b4a1-4b00-85fa-6dec8e995e42","doc_no":"A.1.1.2","title":"Interpretation Of The Spirit Of The Atlas","type":"Section","depth":3,"parentId":"86a93dab-2f12-4c3f-9285-bcc4520c851b","order":67,"content":"Where the Immutable Documents do not contain explicit instructions about a particular topic, the Spirit of the Atlas should be extrapolated to maximize Universal Alignment and mitigate risks of slippery slope misalignment. Atlas Interpretations must be fully congruent with the Spirit of the Atlas and established precedent. Further, each Atlas Interpretation must set a clear precedent to avoid future ambiguities that could impede effective governance.","contentHash":"19c6a61a5324259413cdd267f18b94eb69b39ba93199f9239ee89dff00a66d4f","addressRefs":[]},"7c921d71-b4fe-4bb7-a58b-c57955de2148":{"id":"7c921d71-b4fe-4bb7-a58b-c57955de2148","doc_no":"A.1.1.2.1","title":"General Principles","type":"Core","depth":4,"parentId":"f1b305d3-b4a1-4b00-85fa-6dec8e995e42","order":68,"content":"The Core Facilitator is authorized to conduct Atlas Interpretations to address and resolve ambiguities or contradictions within Atlas Documents. These interpretations may include providing expanded definitions for problematic terms, clarifying the practical application of specific rules or logic, and similar actions aimed at resolving uncertainties. Pursuant to [A.0.1.2.1 - Facilitators’ Broad Discretionary Capacity](f18229fe-fbc3-4dc8-ad84-4bca2915f6c4), the Core Facilitator has broad discretion in conducting Atlas Interpretations.\n\nAll Atlas Interpretations must be documented to establish clear precedent that reflects the Spirit of the Atlas and guides future interpretations.","contentHash":"e36b378c3dcfc3aeef9f6dacf2727ba768e9a0fc90e403ac6b69ff2e0a1a8dda","addressRefs":[]},"2e15db4f-09cb-40e5-aaf2-172ac8da08a9":{"id":"2e15db4f-09cb-40e5-aaf2-172ac8da08a9","doc_no":"A.1.1.2.1.0.3.1","title":"Ambiguity - Element Annotation","type":"Annotation","depth":5,"parentId":"7c921d71-b4fe-4bb7-a58b-c57955de2148","order":69,"content":"The element \"ambiguity\" refers to instances where the language of an Atlas document allows for multiple possible interpretations.","contentHash":"ba18426f39701d367636191410777819e7b8eed4a5e71083f67b7da3ab5a7e89","addressRefs":[]},"e7d8a884-de5c-416b-b297-2ac73ad0588e":{"id":"e7d8a884-de5c-416b-b297-2ac73ad0588e","doc_no":"A.1.1.2.1.0.3.2","title":"Contradictions - Element Annotation","type":"Annotation","depth":5,"parentId":"7c921d71-b4fe-4bb7-a58b-c57955de2148","order":70,"content":"The element \"contradictions\" refers to instances where different Atlas documents conflict with one another, leading to confusion or inconsistency in their application.","contentHash":"4ff0a66012830649faa0eceb82bca29d7aa7f54c680bfd0e367119dc50551589","addressRefs":[]},"3c070432-e2d7-4965-954b-7736f000c919":{"id":"3c070432-e2d7-4965-954b-7736f000c919","doc_no":"A.1.1.2.1.0.3.3","title":"Expanded Definitions - Element Annotation","type":"Annotation","depth":5,"parentId":"7c921d71-b4fe-4bb7-a58b-c57955de2148","order":71,"content":"The element \"expanded definitions\" describes the process of providing more detailed or comprehensive explanations of terms that are vague, overly broad, or otherwise unclear. Such expanded definitions can be codified in the Element Annotation Document Type. See [A.1.2.2.2.10 - The Element Annotation Type](71db0980-a49f-4d48-b277-87f9a2340a8f).","contentHash":"d846a366c9c0f340ba5ff270a750108783511bd95439860ed83d729d7828108b","addressRefs":[]},"011f56bd-88ea-4349-bb58-32d2f6ba32e4":{"id":"011f56bd-88ea-4349-bb58-32d2f6ba32e4","doc_no":"A.1.1.2.1.0.3.4","title":"Precedent - Element Annotation","type":"Annotation","depth":5,"parentId":"7c921d71-b4fe-4bb7-a58b-c57955de2148","order":72,"content":"The element \"precedent\" refers to the established examples or standards set by documented Atlas Interpretations, which guide future decision-making and interpretations. Atlas Interpretations can be codified in the Facilitator Action Precedent Document Type. See [A.1.2.2.2.14 - The Facilitator Action Precedent Type](7323b3c5-ffd3-4f8f-af51-5d176531dd0f).","contentHash":"8ed0440c73c5bb81723e2be9ef579b47727a86d8561a0caea8bd54aa94948555","addressRefs":[]},"453cd0ba-534c-45b3-8cb2-0154e579c3cd":{"id":"453cd0ba-534c-45b3-8cb2-0154e579c3cd","doc_no":"A.1.1.2.0.3.1","title":"Extrapolated - Element Annotation","type":"Annotation","depth":4,"parentId":"f1b305d3-b4a1-4b00-85fa-6dec8e995e42","order":73,"content":"The element \"extrapolated\" refers to the process by which a Facilitator has inferred or deduced from their understanding of the Spirit of the Atlas a necessary course of action when explicit guidance is not available. This inferred action is also based on the Facilitator’s current state of Universal Alignment.","contentHash":"b984f3424c463c3f71b43434891e89bfbf3d3385132683bdec4f04b08180c46d","addressRefs":[]},"dce17e05-293a-4779-a028-ad32701aacd1":{"id":"dce17e05-293a-4779-a028-ad32701aacd1","doc_no":"A.1.1.2.0.3.2","title":"Slippery Slope Misalignment - Element Annotation","type":"Annotation","depth":4,"parentId":"f1b305d3-b4a1-4b00-85fa-6dec8e995e42","order":74,"content":"The element \"slippery slope misalignment\" refers to the potential for incremental deviations from Sky’s core principles to gradually lead to significant and undesirable shifts, ultimately steering the Ecosystem away from its intended purpose and vision.","contentHash":"3e0e6a1ac5124815827f9ad0be6c1ed18a55b804f895973db3daea31a7dcd1ec","addressRefs":[]},"55626fc2-3108-4caf-b241-2b215eb75d18":{"id":"55626fc2-3108-4caf-b241-2b215eb75d18","doc_no":"A.1.1.3","title":"List Of Interpretations","type":"Section","depth":3,"parentId":"86a93dab-2f12-4c3f-9285-bcc4520c851b","order":75,"content":"This Section contains a list of all settled Atlas interpretations with all necessary context.","contentHash":"685610f8ba7b73698846dc9b0607186de44b2758fdd56900014a19051ce0d9a2","addressRefs":[]},"c3c7c96c-d756-4e54-a5c5-79b5970394e0":{"id":"c3c7c96c-d756-4e54-a5c5-79b5970394e0","doc_no":"A.1.1.3.1","title":"Atlas Interpretations","type":"Active Data Controller","depth":4,"parentId":"55626fc2-3108-4caf-b241-2b215eb75d18","order":76,"content":"Atlas Interpretation precedent is defined as Active Data in [A.1.1.3.1.0.6.1 - List Of Atlas Interpretations](88df9622-0dd5-4035-83fb-9866a66eadf2).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Facilitator.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"e1b78dcf86268c950cf2d5abe933690f5f0e2abd3d5a26210e22e4b28ba1f643","addressRefs":[]},"88df9622-0dd5-4035-83fb-9866a66eadf2":{"id":"88df9622-0dd5-4035-83fb-9866a66eadf2","doc_no":"A.1.1.3.1.0.6.1","title":"List Of Atlas Interpretations","type":"Active Data","depth":5,"parentId":"c3c7c96c-d756-4e54-a5c5-79b5970394e0","order":77,"content":"List of Atlas Interpretations:\n\n- Payments denominated in SKY in the Atlas will be made in MKR prior to the launch of SKY at the proscribed conversion rate listed in the Atlas.","contentHash":"b89d57891b5c8306527a35c5a5b42d4e052513d8b7239d3f98d8d6068f29c51f","addressRefs":[]},"ac6a31ff-b844-4dc8-b9d6-bf629f34698c":{"id":"ac6a31ff-b844-4dc8-b9d6-bf629f34698c","doc_no":"A.1.1.0.3.1","title":"Foundational Principles - Element Annotation","type":"Annotation","depth":3,"parentId":"86a93dab-2f12-4c3f-9285-bcc4520c851b","order":78,"content":"The element \"foundational principles\" indicates the primary or essential rules, policies and objectives that serve as the groundwork for Sky Governance. To avoid ambiguity or slippery slope misalignment, these foundational principles must be specifically defined to the furthest extent possible in the Immutable Documents, as they are the base upon which the Adaptive Documents are built.","contentHash":"3bd7075f3c6fb8509fc28e64bcc3229077f720fcd6c3d740020da9b761bb4255","addressRefs":[]},"6b0d739f-f957-46fc-85ad-32ade8144249":{"id":"6b0d739f-f957-46fc-85ad-32ade8144249","doc_no":"A.1.1.0.3.2","title":"Spirit of the Atlas - Element Annotation","type":"Annotation","depth":3,"parentId":"86a93dab-2f12-4c3f-9285-bcc4520c851b","order":79,"content":"The element \"Spirit of the Atlas\" refers to the guiding principles that form the ethical, philosophical and operational foundation of the Sky ecosystem. This element should be understood as encompassing the core ideals and objectives influencing the governance, and thus the evolution, of Sky Ecosystem.\n\nThe Spirit of the Atlas should be specified to the furthest extent possible in the Immutable Documents. The Spirit of the Atlas is continually evolving in response to internal and external stimuli; and thus reflects the adaptive intelligence of the Sky ecosystem as a whole. Once the Endgame State is reached and the Immutable Documents are forever locked down, the Spirit of the Atlas will continue to evolve through the vehicle of the Adaptive Documents.\n\nSee also, [A.0.1.1.16 - The Atlas](98223867-c60a-4b28-9401-94fc1ed9b4cd) and [A.0.1.1.9 - Letter Of The Rule Vs Spirit Of The Rule](ff16fd74-3a81-4cac-92b4-1208d4d9f337).","contentHash":"63228545fc774003b1b63dbe16869e0fa1278663692e182d480e7de7fc7f3285","addressRefs":[]},"fbd55373-32cc-49a9-a74d-60cfacf6a379":{"id":"fbd55373-32cc-49a9-a74d-60cfacf6a379","doc_no":"A.1.2","title":"Atlas Documents","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":80,"content":"Atlas Documents are essential to the structure and governance of the Sky Ecosystem. They are organized into document trees, which include Immutable Documents and Adaptive Documents. Immutable Documents embody the Spirit of the Atlas; while Adaptive Documents operationalize the Spirit of the Atlas and facilitate its aligned evolution. This Article defines the properties, development, and procedures associated with Atlas Documents.","contentHash":"87fa5770b9568d52513dc6e8858ae39e1e8b7bbb7c1545b9c05d23b66038d430","addressRefs":[]},"b2e65d2d-2925-4f81-9cb6-b23c6d2fca02":{"id":"b2e65d2d-2925-4f81-9cb6-b23c6d2fca02","doc_no":"A.1.2.1","title":"Definition And Properties Of Atlas Documents","type":"Section","depth":3,"parentId":"fbd55373-32cc-49a9-a74d-60cfacf6a379","order":81,"content":"Atlas Documents are the basic building blocks for structuring data in the Atlas. They are organized as nested document trees, each with a unique Document Identifier.\n\nThe first three layers contain the Immutable Documents, which together enshrine the Spirit of the Atlas and the core, permanent boundaries for how to operationalize it without risking slippery slope misalignment.\n\nIn the layers below the Immutable Documents are the Adaptive Documents, which are continuously improved through the Sky Governance process. The Adaptive Documents interpret and practically operationalize the Spirit of the Atlas within the boundaries set by the Immutable Documents.","contentHash":"53efcd195d32bf55cdd323c25f1a4ee033166cbea95392a51548994643de1b11","addressRefs":[]},"af7c725e-06c9-4c48-ac8a-c979eb004456":{"id":"af7c725e-06c9-4c48-ac8a-c979eb004456","doc_no":"A.1.2.1.1","title":"Document Identifiers","type":"Core","depth":4,"parentId":"b2e65d2d-2925-4f81-9cb6-b23c6d2fca02","order":82,"content":"All Atlas Documents are distinguishable through their unique Document Identifier. The Document Identifier is the technical name of the Atlas Document, and it determines its position in the Document Tree of the Atlas. All Document Identifiers begin with a capital A, and the numbers and letters of the Document Identifiers are separated with dots, with each dot signifying that the Atlas Document is one layer deeper in the tree structure. The Document Identifiers help determine the position of each Atlas Document, and makes it easier to estimate the relationship between two different Atlas Documents.","contentHash":"a8a638ab457066d28c9aa3358f4d5cfbcf41b0cdd6a3296e108523bd5a032a10","addressRefs":[]},"7aeb8c0d-d5b3-4f3c-954a-a0f734995425":{"id":"7aeb8c0d-d5b3-4f3c-954a-a0f734995425","doc_no":"A.1.2.1.1.1","title":"Early Atlas Iteration Bootstrapping","type":"Core","depth":5,"parentId":"af7c725e-06c9-4c48-ac8a-c979eb004456","order":83,"content":"In the first iterations of the Atlas, formal Atlas Document Identifiers will not yet be implemented for all Document Types.","contentHash":"bafecc6deeac57bfeaa1194a0940cc1fc82848f866080fccd31deb85b94179c5","addressRefs":[]},"faa87541-e10b-4d99-822d-4877e20bc9d4":{"id":"faa87541-e10b-4d99-822d-4877e20bc9d4","doc_no":"A.1.2.1.2","title":"Atlas Document Properties","type":"Core","depth":4,"parentId":"b2e65d2d-2925-4f81-9cb6-b23c6d2fca02","order":84,"content":"All Atlas Documents have five (5) standard properties that provide key information about them. The subdocuments of this document specify the characteristics of each of the five (5) standard properties.\n\nThe standard properties of Atlas Documents should be listed in the following order:\n\n1. Name\n2. Version\n3. Last Modified\n4. Type\n5. Components","contentHash":"d59e316fa51e22b3802a8c8cda8a5d2359e78d59d33ea1c227c79a4e956df8c7","addressRefs":[]},"4cb85e3a-f73f-4918-a90c-020a479af7d2":{"id":"4cb85e3a-f73f-4918-a90c-020a479af7d2","doc_no":"A.1.2.1.2.1","title":"Name Property","type":"Core","depth":5,"parentId":"faa87541-e10b-4d99-822d-4877e20bc9d4","order":85,"content":"The Name property is assigned to each Atlas Document to provide a human-readable name, making it easier for humans to identify the document and understand its purpose and function at a glance. This Name serves as an abstracted overview of the document's content, distinguishing it from other documents in a user-friendly manner.\n\nHowever, for data management and record-keeping purposes, the official designation of an Atlas Document is its unique Document Identifier. As a result, the Name property can be modified with no substantive consequences.","contentHash":"a4aaa3ef4423d957e5f8a2482d4303103ebae2e97e5e92f141489704280faaa5","addressRefs":[]},"3263a17d-44ab-4450-af61-d797fa0c8ac7":{"id":"3263a17d-44ab-4450-af61-d797fa0c8ac7","doc_no":"A.1.2.1.2.2","title":"Version Property","type":"Core","depth":5,"parentId":"faa87541-e10b-4d99-822d-4877e20bc9d4","order":86,"content":"The Version property of Atlas Documents specifies how many times it has been modified. Every time an Atlas Document is modified, the newly modified Document gets its version number incremented, and the old version is recorded as a historical version with a Document Identifier equivalent to its version number.\n\nAs an example, if an Atlas Document located at 1.1.1 with version number 3 is modified, the new Atlas Document will have version number 4, and the old Atlas Document will be located at 1.1.1.v3.\n\nThis ensures all historical versions of Atlas documents are retained permanently as a part of the Atlas.","contentHash":"9757f7c7efe6956287f40e21ce73d1fff15b2f215c91d1d8bb443dc0f268ec1f","addressRefs":[]},"1a9961c4-856a-4c48-bc48-8da4e4a26dd4":{"id":"1a9961c4-856a-4c48-bc48-8da4e4a26dd4","doc_no":"A.1.2.1.2.3","title":"Last Modified Property","type":"Core","depth":5,"parentId":"faa87541-e10b-4d99-822d-4877e20bc9d4","order":87,"content":"The Last Modified property specifies the exact date and time when the Atlas Document was updated to its current version. It is recorded in the UTC timezone and follows the format 'YYYY-MM-DD-HH:MM:SS'. This property provides a timestamp for tracking modifications and ensuring transparency in the governance and update process. When an Atlas Document is at version 1, the Last Modified property denotes when the Atlas Document was created.","contentHash":"184604501e9d5d34a09addbc7ce03bfeddf4cada9d82563ddcfeda3521503cc4","addressRefs":[]},"8f6dd2df-599f-4fcc-803d-1e1cc5adcdcd":{"id":"8f6dd2df-599f-4fcc-803d-1e1cc5adcdcd","doc_no":"A.1.2.1.2.4","title":"Type Property","type":"Core","depth":5,"parentId":"faa87541-e10b-4d99-822d-4877e20bc9d4","order":88,"content":"The Type property of Atlas Documents specifies the function, characteristic and purpose of the Atlas Document. The Type determines the data that must be contained in the Components Property. The various Document Types and their characteristics are specified in [A.1.2.2 - Structure, Categories, And Types Of Atlas Documents](f65c083f-021b-4a12-b000-6764e4fe28c3).","contentHash":"2ab7defccec70415624b367c53b9a8943ad8ba5afde8c981da4ec95002732489","addressRefs":[]},"6ae438cd-3678-46a2-b323-1f44204b5759":{"id":"6ae438cd-3678-46a2-b323-1f44204b5759","doc_no":"A.1.2.1.2.5","title":"Components Property","type":"Core","depth":5,"parentId":"faa87541-e10b-4d99-822d-4877e20bc9d4","order":89,"content":"The Components property of Atlas Documents contains an object that specifies the data components of the Atlas Document as nested properties. The Components of an Atlas Document is determined by its Type. Some Document Types have no Components, in which the object is just empty.\n\nAn Atlas Document with Components must always have all of its components properly filled according to the requirements defined by its Type Specification. Some documents have custom logic for how their Components behave, and this custom logic is specified through a special reserved component property called 'Custom'. Atlas Documents of Types with specified custom logic components can have variable number of components, and different characteristics of each component, for each instance of the Type. Custom components are always appended to the end of the list of components.","contentHash":"3184a4eed48b3533e0a6c04d39d86c7a1fff9f9c698e52e1c1a035e50a400645","addressRefs":[]},"f0b99ed7-9f30-4948-be39-146c3d2b83d2":{"id":"f0b99ed7-9f30-4948-be39-146c3d2b83d2","doc_no":"A.1.2.1.0.3.1","title":"Nested Document Trees - Element Annotation","type":"Annotation","depth":4,"parentId":"b2e65d2d-2925-4f81-9cb6-b23c6d2fca02","order":90,"content":"The element \"nested document trees\" refers to the hierarchical organization of Atlas documents, where each document is part of a larger structure with parent and child relationships. Higher-level documents govern or influence the interpretation and application of lower-level documents.","contentHash":"50393a679c36e34b0366cb9b1ee1b7a07c30077db3cc40d03ea681310f0a14d3","addressRefs":[]},"f65c083f-021b-4a12-b000-6764e4fe28c3":{"id":"f65c083f-021b-4a12-b000-6764e4fe28c3","doc_no":"A.1.2.2","title":"Structure, Categories, And Types Of Atlas Documents","type":"Section","depth":3,"parentId":"fbd55373-32cc-49a9-a74d-60cfacf6a379","order":91,"content":"This Section defines the basic structure of Atlas Documents and their specifications, including their general categories and individual types, their syntax and content requirements, and their functions and composability in the Atlas.","contentHash":"69fe5c5f3a19edd175de6dd645bc0e05d6a6872613507663740cdfd02824d72c","addressRefs":[]},"c74cc05e-be2d-4b83-83f4-21bfe113be33":{"id":"c74cc05e-be2d-4b83-83f4-21bfe113be33","doc_no":"A.1.2.2.1","title":"Atlas Document Type Categories","type":"Core","depth":4,"parentId":"f65c083f-021b-4a12-b000-6764e4fe28c3","order":92,"content":"The Atlas Document Types can be broadly categorized into distinct groups that determine how they are modified and how they function in the Atlas. At the highest level there are the Immutable Documents and the Adaptive Documents. The Adaptive Documents are further subdivided into three (3) distinct groups: Primary Documents, Supporting Documents, and Accessory Documents. The category of an Atlas Document can be inferred from its Document Identifier, as each group has unique and non-overlapping rules for validity of their Document Identifiers.","contentHash":"4f13dac1c593c627d237193dedc00eb0c5a635767df539462f0da6808974fa04","addressRefs":[]},"a324e17e-56c9-4d35-b4fa-75593d852f15":{"id":"a324e17e-56c9-4d35-b4fa-75593d852f15","doc_no":"A.1.2.2.1.1","title":"Immutable Document Category","type":"Core","depth":5,"parentId":"c74cc05e-be2d-4b83-83f4-21bfe113be33","order":93,"content":"Immutable Documents are the most important part of the Atlas: they record the Spirit of the Atlas, detailing the vision, purpose and unalienable principles of Sky. In the transition to Endgame State, Immutable documents remain modifiable by the governance processes specified elsewhere in the Atlas. Once the Endgame State has been reached, however, Immutable Documents become fully immutable, i.e., they can never be changed. Immutable Documents have Document identifiers that are at most three (3) layers deep in the Document Tree.","contentHash":"160f5e1b69a1d5ca566c8c303babc3fc879224dfa084e39f33341bcc9d30554a","addressRefs":[]},"7de56365-7762-4bba-b982-04c9ec6582e0":{"id":"7de56365-7762-4bba-b982-04c9ec6582e0","doc_no":"A.1.2.2.1.2","title":"Primary Document Category","type":"Core","depth":5,"parentId":"c74cc05e-be2d-4b83-83f4-21bfe113be33","order":94,"content":"Primary Documents are the cornerstone of the Adaptive Documents and ensure the practical operationalization and resilience of the Atlas. They detail specific, practical principles, rules, processes and roles necessary to operationalize the Spirit of the Atlas. In the transition to Endgame, Primary Documents can be modified with no restrictions, using the governance processes specified elsewhere in the Atlas. Once the Endgame State is reached, Primary Documents generally must be modified as slowly as possible, and as little as possible while remaining fully adapted to the external environment. Primary Documents have Document Identifiers that are 4 layers or deeper in the Document Tree, and cannot contain 0's.","contentHash":"1ea15d4c2e2bce804800f791cf3b2ceb32321c75b322bb63827f3ae83c205328","addressRefs":[]},"e87b6850-3792-495d-9460-0ac069a217e6":{"id":"e87b6850-3792-495d-9460-0ac069a217e6","doc_no":"A.1.2.2.1.3","title":"Supporting Document Category","type":"Core","depth":5,"parentId":"c74cc05e-be2d-4b83-83f4-21bfe113be33","order":95,"content":"Supporting Documents are attached to Immutable Documents and Primary Documents (called their \"Target Document\"). They provide context and in some cases advanced functionality to the Target Documents, enabling them to be fully operationally effective and unambiguous.\n\nThe different Types of Supporting Documents have different functions. Some Supporting Document types are required for all Immutable Documents and Primary Documents; while others are only required for certain Primary Document Types.\n\nMost Supporting Document types can be freely modified through the governance processes specified elsewhere in the Atlas. The Active Data Supporting Document type can be modified in real time by processes outside of said governance processes.\n\nSupporting Documents always have Document Identifiers that contain at least one 0.","contentHash":"6cda0e9596fff60fa139001e9c5a06e688f919a2b64a737d2e6e0f4d23c92bc4","addressRefs":[]},"dfb4784c-2d53-4643-ae0f-debab9dd5aec":{"id":"dfb4784c-2d53-4643-ae0f-debab9dd5aec","doc_no":"A.1.2.2.1.4","title":"Accessory Document Category","type":"Core","depth":5,"parentId":"c74cc05e-be2d-4b83-83f4-21bfe113be33","order":96,"content":"Accessory Documents provide accessory data to every other Atlas Document type. There are two types of Accessory Documents: Translation Documents and Archive Documents. Translation Documents can be edited directly by Facilitators, while Archive Documents are Immutable. Accessory Documents always have Document Identifiers that contain letters in addition to the standard 'A' prefix of all Atlas Document Identifiers.","contentHash":"fe4060d487f7dc1db486a242fb52fa393e725e69c78b13eb65ca08b06ffb5432","addressRefs":[]},"c3f58d8c-f734-4b5b-a2c9-261c7eb02d97":{"id":"c3f58d8c-f734-4b5b-a2c9-261c7eb02d97","doc_no":"A.1.2.2.1.0.4.1","title":"Determine How They Are Modified - Immutable Documents Can Be Amended In The Transition To Endgame","type":"Action Tenet","depth":5,"parentId":"c74cc05e-be2d-4b83-83f4-21bfe113be33","order":97,"content":"Currently, in the transition to Endgame, the Immutable Documents (Articles and Sections) can be amended pursuant to [A.1.11 - Weekly Governance Cycle](83edd4e1-692e-4566-a415-b8f272c33c5e) and [A.1.12 - Monthly Governance Cycle](7f2ba62c-9b3b-4df6-aa16-189a749cffa3)[**.**](7f2ba62c-9b3b-4df6-aa16-189a749cffa3) Once the Sky Ecosystem enters the Endgame State, the Immutable Documents of the Atlas will be forever locked down and cannot be changed.","contentHash":"2f7f21a69aaaec37b9293ae80368998181feb2687e2d1a7e1a88a24889afe75d","addressRefs":[]},"428b7f2e-30b0-4119-a10a-9c3496f19bd2":{"id":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","doc_no":"A.1.2.2.2","title":"List Of Document Types And Their Specifications","type":"Core","depth":4,"parentId":"f65c083f-021b-4a12-b000-6764e4fe28c3","order":98,"content":"The subdocuments herein are Type Specification Documents defining the standardized characteristics and requirements that all Atlas Documents must adhere to in order to be considered valid and aligned.","contentHash":"6d1b0b0010914df7271e3b35ed6af7ff081f1e1fa13688033afe847ef33511c2","addressRefs":[]},"468d192b-83bc-45ab-896f-53e8ca307135":{"id":"468d192b-83bc-45ab-896f-53e8ca307135","doc_no":"A.1.2.2.2.1","title":"The Type Specification Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":99,"content":"[See below]\n\n**Components**:\n\n\"Type Name\": The Type Name Component must contain the name of the Document Type\n\n\"Type Overview\": The Type Overview Component must contain high level information as human-readable text about the type, such as what it is used for and why it is necessary.\n\n\"Type Components\": If the Type has Components, they must be specified in this Component as a nested object.\n\n\"Type Category\": This Component must specify whether the Type is an Immutable Document, a Primary Document, a Supporting Document, or a Translation Document.\n\n\"Document Identifier Rules\": This Component must specify as human-readable text rules related to the Document Identifier for Atlas Documents of this Type, and their locations in the Document Trees.\n\n\"Additional Logic\": This Component can contain additional logic that applies to all Documents of the Type.\n\n**Doc Identifier Rules**:\n\nType Specification Documents must follow the Document Identifier rules for Primary Documents.\n\n**Additional Logic**:\n\nThe rules specified in Type Specification Documents must be followed for all Atlas Documents.\n\n**Type Category**:\n\nPrimary Document\n\n**Type Name**:\n\nType Specification\n\n**Type Overview**:\n\nThe Type Specification Type is used for Type Specification Documents that specify the characteristics of each of the different Document Types. It ensures that all Type Specifications contain all necessary information to make it easy to reason about whether a document follows the requirements for its type.","contentHash":"39732e0a71a0fe2d9b2b66f9c5b0bbf81338dfe93e20be5cfd28c93c9e2fcf79","addressRefs":[]},"08676a8f-96a1-4656-8352-ff4857f95ba6":{"id":"08676a8f-96a1-4656-8352-ff4857f95ba6","doc_no":"A.1.2.2.2.2","title":"The Atlas Preamble Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":100,"content":"[See below]\n\n**Components**:\n\n\"Content\": The content Component is very flexible and defines in broad human-readable language the Spirit of the Atlas.\n\n**Doc Identifier Rules**:\n\nAtlas Preamble Documents are located at A.0 or as nested Documents one layer below A.0.\n\n**Additional Logic**:\n\nAtlas Preamble Documents are immutable, foundational parts of the Atlas and their content must be considered when interpreting all other Atlas Documents.\n\n**Type Category**:\n\nImmutable Document\n\n**Type Name**:\n\nAtlas Preamble\n\n**Type Overview**:\n\nThe Atlas Preamble Type is used for the Atlas Preamble Document Tree which starts at the 0th position of the first layer of the Atlas. The Atlas Preamble details the Spirit of the Atlas in human-readable language, and specifies important definitions for understanding the Spirit of the Atlas, that must be used as context when interpreting all other parts of the Atlas.","contentHash":"52489dff363baf3fca2ba5091cf9faa5fb9cac6ad17481a044621968ec20488b","addressRefs":[]},"69dc9b57-ad4d-4d84-9775-cc5338c43820":{"id":"69dc9b57-ad4d-4d84-9775-cc5338c43820","doc_no":"A.1.2.2.2.3","title":"The Scope Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":101,"content":"[See below]\n\n**Components**:\n\n\"Content\": The content Component is very flexible and defines in broad human-readable language core principles, rules and processes.\n\n**Doc Identifier Rules**:\n\nScope Documents have the Document Identifiers from A.1 to A.6.\n\n**Additional Logic**:\n\nScope Documents are immutable, foundational parts of the Atlas and their content must be considered when interpreting all principles, rules and processes of Atlas Documents nested below them\n\n**Type Category**:\n\nImmutable Document\n\n**Type Name**:\n\nScope\n\n**Type Overview**:\n\nThe Scope Type is used for the six nonzero Immutable Documents of the first layer of the Atlas that directly describe focus areas, principles, rules and processes of Sky Governance. Scope Documents define the broad boundaries, requirements and objectives of each of the 5 Atlas Scopes, so that they together can fully cover all activities that are needed for Sky to function while maintaining its resilient equilibrium.","contentHash":"4e16f9b7afb5705757e0627ea6d343ef0761b92eedd19eec460f10d73ec76f4a","addressRefs":[]},"f1c62cc8-df7c-4153-b3dd-ea4c9f32193c":{"id":"f1c62cc8-df7c-4153-b3dd-ea4c9f32193c","doc_no":"A.1.2.2.2.4","title":"The Article Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":102,"content":"[See below]\n\n**Components**:\n\n\"Content\": The content Component is very flexible and defines in broad human-readable language core principles, rules and processes of the specific focus area of the Scope that the Article covers, and provides the starting point, requirements, boundaries, and in some cases immutable specifications, needed to develop the Adaptive Documents that are nested at lower layers of the Document Trees to maximally fulfill their practical purpose without violating the Spirit of the Atlas.\n\n**Doc Identifier Rules**:\n\nArticle Documents have Document Identifiers one layer below the Scope Documents.\n\n**Additional Logic**:\n\nArticle Documents are immutable, foundational parts of the Atlas and their content must be considered when interpreting all principles, rules and processes of Atlas Documents nested below them.\n\n**Type Category**:\n\nImmutable Document\n\n**Type Name**:\n\nArticle\n\n**Type Overview**:\n\nThe Article Type is used for the second layer documents nested below the six Scope documents of the Atlas. They directly describe individual focus areas that together fully cover everything needed for the purpose of the Scope to be fulfilled.","contentHash":"063613838879b8f5ad99faa78583586ec0d2796a5b53907257b2992ccb5857be","addressRefs":[]},"8b8e224e-5d1a-4387-8afe-06f65dc8548c":{"id":"8b8e224e-5d1a-4387-8afe-06f65dc8548c","doc_no":"A.1.2.2.2.5","title":"The Section Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":103,"content":"[See below]\n\n**Components**:\n\n\"Content\": The content Component is very flexible and provides in-depth human-readable language to elaborate on the specific principles, rules, and processes that operationalize the Section’s parent Article.\n\n**Doc Identifier Rules**:\n\nSection Documents have Document Identifiers one layer below the Article Documents.\n\n**Additional Logic**:\n\nSection Documents are immutable parts of the Atlas and their content must be considered when interpreting all principles, rules and processes of Adaptive Documents nested below them.\n\n**Type Category**:\n\nImmutable Document\n\n**Type Name**:\n\nSection\n\n**Type Overview**:\n\nThe Section Type is used for the third layer of Immutable Documents nested under the Articles of each Scope in the Atlas. Section Documents provide additional structure and specification to the principles, rules and processes within the focus area of the Article. The Section Type acts as a foundation and boundary against misalignment of the Adaptive Documents that are nested below it. Generally, Section Documents should be \"atomized\", or restricted to specifying only a single discrete unit of logic.","contentHash":"c502eb9ea1341e0f4ade0d7d684f754df55b318f502d9c91db1af1a1f5986ae3","addressRefs":[]},"1c19b404-d396-4148-9cd8-4657ad37e896":{"id":"1c19b404-d396-4148-9cd8-4657ad37e896","doc_no":"A.1.2.2.2.6","title":"The Core Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":104,"content":"[See below]\n\n**Components**:\n\n\"Content\": The content Component is very flexible and defines in human-readable language core principles, rules or processes, or subcomponents thereof.\n\n**Doc Identifier Rules**:\n\nCore Documents follow the Document Identifier Rules of Primary Documents. Core Documents have Document Identifiers that are 4 layers or deeper in the Document Tree, and cannot contain 0's [zeros]. Within these constraints, Core Documents can have whatever Document Identifier that is useful for their purpose.\n\n**Additional Logic**:\n\n\n\n**Type Category**:\n\nPrimary Document\n\n**Type Name**:\n\nCore\n\n**Type Overview**:\n\nThe Core Type is the basic building block of the Primary Documents. Core Documents flexibly specify the core principles, rules and processes required to fulfil the specifications made by the Immutable Documents with a focus on clarity, practicality and applicability.","contentHash":"e22569ea83a58a47995eb5eb08937a59c09a91e44761fbbc014786d4114b33e2","addressRefs":[]},"c68d22b2-adf7-4889-9547-ec19e850a1b2":{"id":"c68d22b2-adf7-4889-9547-ec19e850a1b2","doc_no":"A.1.2.2.2.7","title":"The Supporting Root Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":105,"content":"[See below]\n\n**Components**:\n\n\n\n**Doc Identifier Rules**:\n\nSupporting Root Documents must always be located at the .0 position of its Target Document.\n\n**Additional Logic**:\n\nThe Supporting Root Documents have no function other than structurally acting as a directory for nested Supporting Documents in a standardized format. All Immutable Documents and Primary Documents must have a Supporting Root Document attached.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nSupporting Root\n\n**Type Overview**:\n\nThe Supporting Root Type is used to mark the beginning of the Supporting Document subtree of an Immutable or Primary Document. All Immutable and Primary Documents must have a Supporting Root.","contentHash":"19ef7e23dfc4f80950c7b3bd3e4f1c170428a6baa15df8ec35cfe21f1be65299","addressRefs":[]},"ff7f74ee-356d-403c-9454-56fcef514e9e":{"id":"ff7f74ee-356d-403c-9454-56fcef514e9e","doc_no":"A.1.2.2.2.8","title":"The Original Context Data Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":106,"content":"[See below]\n\n**Components**:\n\n\"Content\": The Content Component should contain all relevant information to understand the intention and reasoning behind the wording and elements of the main Document.\n\n**Doc Identifier Rules**:\n\nOriginal Context Data Documents must always be located at the .0.1 position of their Target Document, or nested in a subtree of Original Context Data Documents below the .0.1 position.\n\n**Additional Logic**:\n\nThe Original Context Data Document should be in a finished form alongside the creation or modification of its Target Document, as it aims to capture the original context and intention of the contents of the Target Document. However, it can and should be modified if new evidence and data comes to light that helps to better describe the original context and intention of the Target Document, or if new perspectives or new external events makes it possible and useful to modify the Original Context Data Document in a way that doesn’t contradict its earlier language.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nOriginal Context Data\n\n**Type Overview**:\n\nOriginal Context Data Documents explain the intention and reasoning behind the content of its Target Document, to make interpretation and extrapolation of its contents easier, and provide additional information to other forms of analysis. Original Context Data helps anchor the fundamental purpose and meaning of the target document to its original context, and should help mitigate cultural drift over time. Original Context Data can contain unstructured data used for genesis data integration of early Atlas Documents. Original Context Data Documents can form nested subtrees to organize their data if relevant.","contentHash":"ffb0d2d4ff8ac85ef10e7ad2985541bb5f979cb7d943384b7bff66dd5b1e36bd","addressRefs":[]},"95ad533a-40d0-4dbd-8d3a-3224ac77e672":{"id":"95ad533a-40d0-4dbd-8d3a-3224ac77e672","doc_no":"A.1.2.2.2.9","title":"The Element Annotation Directory Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":107,"content":"[See below]\n\n**Components**:\n\n\"Directory index\": This Component should contain a list of the Element Annotation Documents contained within, with keys being the document identifiers and values being their document names.\n\n**Doc Identifier Rules**:\n\nElement Annotation Directory Documents must always be located at the .0.3 position of their Target Document.\n\n**Additional Logic**:\n\n\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nElement Annotation Directory\n\n**Type Overview**:\n\nThe Element Annotation Directory Type is a directory used to list all of the Element Annotation Documents pertaining to a Target Document.","contentHash":"b0adc997eba617f12af8dc1773445404692307408f066a3c3e37e6baaa22ec5e","addressRefs":[]},"71db0980-a49f-4d48-b277-87f9a2340a8f":{"id":"71db0980-a49f-4d48-b277-87f9a2340a8f","doc_no":"A.1.2.2.2.10","title":"The Element Annotation Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":108,"content":"[See below]\n\n**Components**:\n\n\"Element\": The Element Component should contain the unique word or phrase from the Target Document that is being annotated.\n\n\"Annotation\": The Annotation Component should concisely disambiguate and bound the semantic meaning of problematic terms in the Target Document. Such terms can be vague, ambiguous or technical jargon specific to the Target Document.\n\n**Doc Identifier Rules**:\n\nElement Annotation Documents must always be located as subdocuments to the Element Annotation Directory Document of their Target Document. Element Annotation documents are located at the .0.3.X position, with X being the incremented number.\n\n**Additional Logic**:\n\nElement Annotation Documents should be updated as necessary to reflect changes in the understanding or interpretation of the Element and/or any related Atlas document, while maintaining consistency with the Target Document. The Element Annotation should not contradict its Target Document or other context data of the Target Document.\n\nThe \"Name\" property of each Element Annotation Document instance must follow a standardized template: the annotated Element is listed first, followed by a hyphen, and the phrase \"Element Annotation\".\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nElement Annotation\n\n**Type Overview**:\n\nElement Annotation Documents provide further specification of the semantic meaning of vague or ambiguous terms in the Target Document. Element Annotation Documents can also briefly define technical jargon that is unique to the Target Document. Element Annotation Documents can be thought of as serving a function similar to that of a footnote: they can provide useful context or commentary. Element Annotations should be as concise as possible.","contentHash":"caa1997440c480e5e21eabe9e0c053754fa9fcef6b80755f3f263f0bc0502374","addressRefs":[]},"fa44ae5a-01e6-4583-8ff5-a6e1458df62e":{"id":"fa44ae5a-01e6-4583-8ff5-a6e1458df62e","doc_no":"A.1.2.2.2.11","title":"The Facilitator Action Tenet Directory Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":109,"content":"[See below]\n\n**Components**:\n\n\"Directory index\": This Component should contain a list of the Facilitator Action Tenets contained within, with keys being the document identifiers and values being their document names.\n\n**Doc Identifier Rules**:\n\nFacilitator Action Tenet Directory Documents must always be located at the .0.4 position of their Target Document.\n\n**Additional Logic**:\n\n\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFacilitator Action Tenet Directory\n\n**Type Overview**:\n\nThe Facilitator Action Tenet Directory Type is a directory Type used to list all of the Facilitator Action Tenet Documents that pertain to a Target Document. Facilitator Action Tenet Documents specify adjudication principles and guidelines that are directly derived from the Target Document. When a controversy concerns the Target Document, the Facilitators must consult and apply the pertinent Action Tenet(s) in their decision-making.","contentHash":"47cfe1e42a2dfb36d3af226af9d0fb41b393f13557fcc832e1335a7b81ec2df2","addressRefs":[]},"9ab18c94-b9b6-43d0-b260-873ad1ef66fe":{"id":"9ab18c94-b9b6-43d0-b260-873ad1ef66fe","doc_no":"A.1.2.2.2.12","title":"The Facilitator Action Tenet Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":110,"content":"[See below]\n\n**Components**:\n\n\"Content\": The Tenet Component specifies the adjudication logic, principle or doctrine that is directly derived from the Target Document. This Component can include policy statements underpinning the adjudication principle. Such policy statements can highlight the values that are served by, or the benefits gained from, adhering to the Tenet. When facing edge cases, these policy statements can help Facilitators to extrapolate from the Tenet's logic to achieve the most suitable outcome.\n\n**Doc Identifier Rules**:\n\nFacilitator Action Tenet Documents must always be located as subdocuments of the Facilitator Action Tenet Directory Document (which latter is located at position .0.4) of their Target Document. Action Tenet documents are located at the .0.4.X position, with X being the incremented number.\n\n**Additional Logic**:\n\nFacilitator Action Tenet Documents are likely to be necessary supplements for interpreting the Immutable Document types, as these tend to have generalized, broad language. The Core Document type has the function of operationalizing the Immutable Documents, and thus its language will tend to be far more specific and concrete. For that reason, Action Tenet Supporting Documents may not be necessary for a particular Core Document. This is not a hard-coded rule, however. The determination of whether an Action Tenet Document is needed for any given Atlas document should always be tailor-made.\n\nAction Tenet Documents should be created and updated as necessary to reflect changes in governance practices, provide clarity on decision-making processes, and enhance understanding of governance principles and rules. The examples should not contradict their Target Document or other Supporting Documents of the Target Document.\n\nIf the Action Tenet can be anchored to a specific term from the Target Document, that term is listed first; followed by a hyphen; and then, an abstract of the Action Tenet logic, e.g.: \"Organizational Drift - ACs' Mandate When Instigating Action Can Be Traced Back to a Discrete Entity\". If the Action Tenet cannot be anchored to a specific term from the Target Document, the \"Name\" property should simply summarize the Action Tenet logic, e.g.: \"Evaluating AC breach of role-specific requirement vs. general requirement\".\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFacilitator Action Tenet\n\n**Type Overview**:\n\nThe Facilitator Action Tenet Type is used to provide concrete adjudication principles derived from its Target Document. It distills the governance logic of the Target Document into a concise principle to guide Facilitators in resolving disputes related to the Target Document. The practical application of the Tenet is demonstrated by its \"Scenario\" Subdocuments.","contentHash":"bd2ece4d067ff8605d03f3845f0a1d704e91a99c50030021a5db6be3f37c7c09","addressRefs":[]},"fd4260fd-f56d-40e7-bd8a-baefa1901dff":{"id":"fd4260fd-f56d-40e7-bd8a-baefa1901dff","doc_no":"A.1.2.2.2.13","title":"The Facilitator Action Precedent Directory Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":111,"content":"[See below]\n\n**Components**:\n\n\"Directory index\": This Component should contain a list of the Facilitator Action Precedents contained within, with keys being the document identifiers and values being their document names.\n\n**Doc Identifier Rules**:\n\nFacilitator Action Precedent Directory Documents must always be located at the .0.5 position below their Target Document.\n\n**Additional Logic**:\n\nA Facilitator Action Precedent Directory Document must be updated whenever a new Facilitator Action Precedent Document is added that meaningfully changes what should be contained in the Directory overview Component.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFacilitator Action Precedent Directory\n\n**Type Overview**:\n\nFacilitator Action Precedent Directory Documents list all of the Facilitator Action Precedent Documents that pertain to a Target Document. Facilitator Action Precedent Documents record data about Facilitator Actions, including ongoing actions, that are primarily based on interpretation of content of the Target Document.","contentHash":"7589692436ed4d888919428a5d4e8bf284d6899a71d16c33086200d2359ccaaa","addressRefs":[]},"7323b3c5-ffd3-4f8f-af51-5d176531dd0f":{"id":"7323b3c5-ffd3-4f8f-af51-5d176531dd0f","doc_no":"A.1.2.2.2.14","title":"The Facilitator Action Precedent Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":112,"content":"[See below]\n\n**Components**:\n\n\"Input\": The Input Component must contain a description of the situation or context in which the Facilitator Action takes place. This could include any relevant information, such as the state of governance or the specific issue at hand.\n\n\"Output\": The Output Component must contain a description of the Facilitator's action and the outcome or decision that resulted from it. This should provide a clear illustration of how the Facilitator responded to the situation.\n\n\"Label\": The Label Component indicates whether the Facilitator's action is considered aligned or misaligned according to the principles and rules of governance. This judgment is intended to guide future actions and decisions. If the label is misaligned, it must also specify the penalty that is applied to the Facilitator for misalignment. The Label must always be marked as Aligned when it is created by the Facilitator, and further action by Sky Governance can directly modify this later according to the specifications of the Atlas Documents relevant to appealing Facilitator Actions.\n\n**Doc Identifier Rules**:\n\nFacilitator Action Precedent Documents must always be located as subdocuments of the Facilitator Action Precedent Directory Document of their Target Document.\n\n**Additional Logic**:\n\nFacilitator Action Precedent Documents should be created and updated as necessary to reflect changes in governance practices, provide clarity on decision-making processes, and enhance understanding of governance principles and rules. The Precedents should not contradict their Target Document or other Supporting Documents of the Target Document.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFacilitator Action Precedent\n\n**Type Overview**:\n\nThe Facilitator Action Precedent Type is used to record all the relevant data related to a Facilitator Action, to serve as precedent for future Facilitator Actions and decision-making processes. It is also used for ongoing Facilitator Actions, and the creation of a Facilitator Action Precedent is the formal method that Facilitators use to record Atlas Interpretations, take action against misalignment, or explicitly approve ecosystem activity.","contentHash":"3e765c036444dbba3b410cadccdfe44cfadd233897a3c2cca792fd06770d395d","addressRefs":[]},"095edfd9-1a87-46f1-a5a5-7ff8f3d26eb1":{"id":"095edfd9-1a87-46f1-a5a5-7ff8f3d26eb1","doc_no":"A.1.2.2.2.15","title":"The Active Data Controller Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":113,"content":"[See below]\n\n**Components**:\n\n\"Content\": The Content Component of Active Data Controller Documents is used to define: 1) the entities who are authorized to modify the child Active Data Documents and 2) the authorized process by which said Active Data Documents are modified. If applicable, the Custom Components format and requirements of the Active Data Documents must be defined as well.\n\n**Doc Identifier Rules**:\n\nActive Data Controller Documents follow the Document Identifier Rules of Primary Documents. Active Data Controller Documents have Document Identifiers that are 4 layers or deeper in the Document Tree, and cannot contain 0's [zeros]. Within these constraints, Active Data Controller Documents can have whatever Document Identifier that is useful for their purpose.\n\n**Additional Logic**:\n\nActive Data Controller Documents must have an Active Data Directory Document located below it at the .0.6 position. The Active Data Controller Document can reference its Active Data subdocuments for its own logic. This allows Active Data Documents to be self-improving and adaptive at high speeds.\n\n**Type Category**:\n\nPrimary Document\n\n**Type Name**:\n\nActive Data Controller\n\n**Type Overview**:\n\nActive Data Controller Documents are Primary Documents that can have Active Data Documents attached to them as Supporting Documents; these latter contain variable state that can be directly modified by Facilitators and other processes external to the standard Weekly Governance Cycle or Monthly Governance Cycle (i.e., the Atlas Edit Proposal process). Active Data can be lists of authorized actors, parameters, or externally collected data being prepared for data integration with the Atlas.","contentHash":"b3cc0f2ab36b14ae1f16562354ed541f01db60082bc7367117bbd00fdb3374c8","addressRefs":[]},"343f4477-2981-4a99-825d-a92fb9d320e4":{"id":"343f4477-2981-4a99-825d-a92fb9d320e4","doc_no":"A.1.2.2.2.16","title":"The Active Data Directory Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":114,"content":"[See below]\n\n**Components**:\n\n\"Directory overview\": This Component should contain a brief explanation of overall patterns and themes of the Active Data Documents contained within.\n\n**Doc Identifier Rules**:\n\nActive Data Directory Documents must always be located at the .0.6 position of their Active Data Controller Document or Budget Controller Document.\n\n**Additional Logic**:\n\nAn Active Data Directory Document should be updated whenever a new Active Data Document is added that meaningfully changes what should be contained in the Directory overview Component.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nActive Data Directory\n\n**Type Overview**:\n\nThe Active Data Directory Type is a directory Type used to list all of the Active Data Documents that pertain to an Active Data Controller Document. Active Data Documents contain variable state that can be directly modified by Facilitators and other processes external to the standard Atlas Edit Weekly Cycle or Atlas Edit Monthly Cycle (i.e., the Atlas Edit Proposal process).","contentHash":"399568c9175e2e915ba4e8af9546eec90952fe8559a5e734c3b6404aac4f575d","addressRefs":[]},"925ce2e3-c3a9-4774-a96c-cf77e024d37c":{"id":"925ce2e3-c3a9-4774-a96c-cf77e024d37c","doc_no":"A.1.2.2.2.17","title":"The Active Data Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":115,"content":"[See below]\n\n**Components**:\n\n\"Content\": This component is very flexible and represents in human-readable language the mutable data that is modifiable pursuant to the logic of the parent Active Data Controller.\n\n\"Custom Components\": If present, the Custom Components of Active Data Documents are defined by their parent Active Data Controller Document. They can contain the variable state that is directly modifiable by processes external to the standard Weekly Governance Cycle or the Monthly Governance Cycle.\n\n**Doc Identifier Rules**:\n\nActive Data Documents must always be located as subdocuments of the Active Data Directory Document of their Active Data Controller Document.\n\n**Additional Logic**:\n\nActive Data Documents can contain arbitrary types of data, including large amounts of data or code. The function and purpose of the contained data depends on the logic specified in the Active Data Controller Document.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nActive Data\n\n**Type Overview**:\n\nThe Active Data Type is used for Supporting Documents that contain variable state that can be directly modified by Facilitators and other processes external to the standard Weekly Governance Cycle or the Monthly Governance Cycle (i.e., the Atlas Edit Proposal process). Active Data can be lists of authorized actors, parameters, or externally collected data being prepared for data integration with the Atlas.","contentHash":"fdd74ee0864ef9f2f0e00c5ff40bf85e6337a165803d480451e82a4c4ef4af36","addressRefs":[]},"c0c0d3cb-389e-4dc7-a475-e9bbb5bf633f":{"id":"c0c0d3cb-389e-4dc7-a475-e9bbb5bf633f","doc_no":"A.1.2.2.2.18","title":"The Budget Controller Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":116,"content":"[See below]\n\n**Components**:\n\n\"Content\": The Content Component of Budget Controller Documents is used to describe flexible rules of how the Active Data Documents and Budget Documents must behave, and how they can be modified. The Custom Components format and requirements of the Active Data Documents and the Budget Documents must be defined as well.\n\n**Doc Identifier Rules**:\n\nBudget Controller Documents follow the Document Identifier Rules of Primary Documents.\n\n**Additional Logic**:\n\nBudget Controller Documents must have an Active Data Directory Document located below it at the .0.6 position, and a Budget Directory Document located below it at the .0.7 position.\n\n**Type Category**:\n\nPrimary Document\n\n**Type Name**:\n\nBudget Controller\n\n**Type Overview**:\n\nThe Budget Controller Type is used to manage the budgets used by Sky to operationalize the Scopes to achieve the purpose and goals of the Spirit of the Atlas. It controls variable state that specifically authorizes executive votes to disburse payments from the Sky Surplus Buffer, or authorize smart contracts to disburse such payments. The Budget Controller Document determines the rules and processes for modifying and using the budgets contained in the Budget Documents that are attached to it. Budget Controllers also have Active Data Documents attached that are used to report on the status and results of projects funded through the Budget Documents.","contentHash":"88ae42eb0b95434ae6d24b2178a64cf4c977b8d5b3cfc87aa67dd7cb4771fcab","addressRefs":[]},"0d1f3e25-089f-41ab-994a-39225b164e69":{"id":"0d1f3e25-089f-41ab-994a-39225b164e69","doc_no":"A.1.2.2.2.19","title":"The Budget Directory Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":117,"content":"[See below]\n\n**Components**:\n\n\"Directory overview\": This Component should contain a brief explanation of overall patterns and themes of the Budget Documents contained within.\n\n**Doc Identifier Rules**:\n\nBudget Directory Documents must always be located at the .0.7 position of their Budget Controller Document.\n\n**Additional Logic**:\n\nA Budget Directory Document should be updated whenever a new Budget Document is added that meaningfully changes what should be contained in the Directory overview Component.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nBudget Directory\n\n**Type Overview**:\n\nThe Budget Directory Type is a directory Type used to list all of the Budget Documents that pertain to a Budget Controller Document.","contentHash":"3b7ab62e3a75bb685be5220cacb230ebcef1d2a3e46b346cd386230d02db9355","addressRefs":[]},"278864f9-e03d-44fa-8bae-e1377b95973e":{"id":"278864f9-e03d-44fa-8bae-e1377b95973e","doc_no":"A.1.2.2.2.20","title":"The Budget Document Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":118,"content":"[See below]\n\n**Components**:\n\n\"Custom Components\": The Custom Components of Budget Documents are defined by the Budget Controller Document. They contain the variable state that can be directly modified.\n\n**Doc Identifier Rules**:\n\nBudget Documents must always be located as subdocuments of the Budget Directory Document of their Budget Controller Document.\n\n**Additional Logic**:\n\nBudget Documents specify a budget rate expressed as SKY or USDS per unit of time. Additionally, they can contain large amounts of data, or code, and their function and purpose depends on their Budget Controller Document. Budget Documents can be modified directly through processes external to the standard Atlas Edit Proposal process as specified by their Budget Controller Document.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nBudget\n\n**Type Overview**:\n\nBudget Documents contain state that can authorize executive votes to disburse payments from the Sky Surplus Buffer, or authorize smart contracts to disburse such payments.","contentHash":"b5334a51a8fe1e6cf3b942bd9d14e528482242531d34e03e4836e84fddf37925","addressRefs":[]},"5e74901e-6f18-4e46-b108-3e7268eaa427":{"id":"5e74901e-6f18-4e46-b108-3e7268eaa427","doc_no":"A.1.2.2.2.21","title":"The Definition Directory Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":119,"content":"[See below]\n\n**Components**:\n\n\n\n**Doc Identifier Rules**:\n\nDefinition Directory Documents must always be located at the .0.0 position of their Target Document.\n\n**Additional Logic**:\n\nDefinition Directory Documents only need to be present in Atlas Documents that require definitions for unique terms in their Subdocuments.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nDefinition Directory\n\n**Type Overview**:\n\nThe Definition Directory Type is used for Target Documents with many complex subdocuments, and acts as a directory for definitions of unique terms that are only referenced in its subdocuments.","contentHash":"73c2e05ab8ae58f549c8bbf3a4929e9c7dde83f5ce65a23f2cf3f65df75df0ea","addressRefs":[]},"6eceace8-f499-4954-9ecc-1ada12a02c18":{"id":"6eceace8-f499-4954-9ecc-1ada12a02c18","doc_no":"A.1.2.2.2.22","title":"The Definition Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":120,"content":"[See below]\n\n**Components**:\n\n\"Term\": The Term Component contains the name of the term that is being defined.\n\n\"Definition\": The Definition Component contains the detailed definition of the term.\n\n**Doc Identifier Rules**:\n\nDefinition Documents must always be located as subdocuments of the Definition Directory Document of their Target Document.\n\n**Additional Logic**:\n\nTo the extent possible it should be avoided to have the same term defined multiple times in the Atlas, and instead always put a single definition at a location in the Atlas that covers all of its use. The main exception to this principle should be when relatively niche terms are present in two different Scopes.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nDefinition\n\n**Type Overview**:\n\nThe Definition Type is used for documents that define unique concepts contained in subdocuments to the Target Document of the Definition Document","contentHash":"48b691a1c7f237fb2657901bca9ce2f2c38e7baf63dd710998883a39983c534d","addressRefs":[]},"dde9bb23-9ba2-4de6-a3fe-3093e5108fa4":{"id":"dde9bb23-9ba2-4de6-a3fe-3093e5108fa4","doc_no":"A.1.2.2.2.23","title":"The Translation Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":121,"content":"[See below]\n\n**Components**:\n\n\"Original Document Type\": The Type of the original document that is being translated must be specified in this component.\n\n\"Language\": The Language Component specifies the language in which the Atlas Document is translated.\n\n\"Translated Name\": The Translated Name component contains the name of the translated Atlas Document in the new language.\n\n \"Custom\": Translation Documents contain Custom Components that mirror the components of the original Document with component name and component data translated to the new language.\n\n**Doc Identifier Rules**:\n\nTranslation Documents are located as subdocuments to the Atlas Document they are translating. Their Document Identifier is the same as the Atlas Document they are translating, with an additional suffix that represents the language of the translation. For example, a Spanish translation of [A.1](18ac7dd3-c646-4352-9b0d-d01a2932d7d1) would have the Document Identifier A.1.es.\n\n**Additional Logic**:\n\nTranslation Documents should be updated whenever the Atlas Document they are translating is updated to ensure that the translation remains accurate. However, in case of any discrepancies or contradictions, the original English version of the Atlas Document always takes precedence.\n\n**Type Category**:\n\nAccessory Document\n\n**Type Name**:\n\nTranslation\n\n**Type Overview**:\n\nThe Translation Type is used for creating translated versions of Atlas Documents to make the Atlas accessible to non-English speakers. Translation Documents are Accessory Documents and they do not have any impact on the governance or operation of Sky, but they are important for accessibility and inclusivity.","contentHash":"9a0a052d4da087d1d06049fa47943465267eb56a37f9660ac2e8ed6bb7ed0245","addressRefs":[]},"65c724f5-56d7-4ea6-a0fe-de30e6f04560":{"id":"65c724f5-56d7-4ea6-a0fe-de30e6f04560","doc_no":"A.1.2.2.2.24","title":"The Archive Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":122,"content":"[See below]\n\n**Components**:\n\n\"Original Document Type\": The Type of the original document that is being archived must be specified in this component.\n\n\"Custom\": Archive Documents contain Custom Components that mirror the components of the original Document at the time of the version being archived.\n\n**Doc Identifier Rules**:\n\nArchive Documents are located as subdocuments to the Atlas Document they are archiving. Their Document Identifier is the same as the Atlas Document they are archiving, with an additional suffix 'v' followed by the version number of the document being archived. For example, the third version of [A.1](18ac7dd3-c646-4352-9b0d-d01a2932d7d1) would have the Document Identifier A.1.v3.\n\n**Additional Logic**:\n\nArchive Documents should be created whenever an Atlas Document is updated to ensure that a record of all previous versions is maintained. They are not meant to be modified or deleted once created.\n\n**Type Category**:\n\nAccessory Document\n\n**Type Name**:\n\nArchive\n\n**Type Overview**:\n\nThe Archive Type is used for storing historical versions of Atlas Documents. Archive Documents are Accessory Documents and they do not have any impact on the governance or operation of Sky, but they are important for maintaining a record of changes and evolution of the Atlas over time.","contentHash":"26add4279db3be4ff6033cd8fec4b4ab2ed6beba5dbee952af53a16c448db0b4","addressRefs":[]},"fe9164c5-423c-41e8-b8a8-34f8a5d8d6b7":{"id":"fe9164c5-423c-41e8-b8a8-34f8a5d8d6b7","doc_no":"A.1.2.2.2.25","title":"The Navigation Hub Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":123,"content":"[See below]\n\n**Components**:\n\n\"Content\": The Content Component must contain summarized information and links to the child documents of the associated Immutable or Primary Document. It must also link to the nearest navigation hubs below its position if its Child Documents do not have Navigation Hubs.\n\n**Doc Identifier Rules**:\n\nNavigation Hub Documents must be located at the .0.0 position of an Immutable or Primary Document.\n\n**Additional Logic**:\n\nNavigation Hubs serve as a guide for users to understand and navigate the main content of the associated Immutable or Primary Document.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nNavigation Hub\n\n**Type Overview**:\n\nThe Navigation Hub Type is used for Navigation Hubs that provide summarized content and links to child documents or Focus Hubs that dive deeper or provide supporting data for a specific action. It acts as an entry point and guide for navigating the content of an Immutable or Primary Document.","contentHash":"d24c0ccbb6cf14d5a01af8e52ef6ec85d94d5276997f94f19f9c8012dd5f8e5d","addressRefs":[]},"57c17134-5c45-4a98-8015-38e5e0438095":{"id":"57c17134-5c45-4a98-8015-38e5e0438095","doc_no":"A.1.2.2.2.26","title":"The Focus Hub Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":124,"content":"[See below]\n\n**Components**:\n\n\"Content\": The Content Component must contain detailed information about the specific topic or section from the Navigation Hub.\n\n\"links_to\": This Component can provide links to related documents or sections, with keys being the document names and values being their respective identifiers.\n\n**Doc Identifier Rules**:\n\nFocus Hub Documents must be located at the nonzero numerical positions below Navigation Hubs, e.g.: x.0.0.1, x.0.0.2, etc.\n\n**Additional Logic**:\n\nFocus Hubs serve as a detailed guide on specific topics, giving users an in-depth understanding of the subject matter.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFocus Hub\n\n**Type Overview**:\n\nThe Focus Hub Type is used for Focus Hubs that delve deeper into specific topics or sections from the Navigation Hub. It can be used to slice up a lot of child documents or a lot of hubs into independent groups, so only the relevant group needs to be read. It can also be used to provide relevant data for a specific type of action or workflow related to the Focus Hubs Immutable or Primary Document or its subtree.","contentHash":"a8e58f99ce3a8ceadc03c0d4573eab951119c23cb8691e93c6cc81e83b1b3d9b","addressRefs":[]},"3ad64e25-e64d-454f-a2cd-836e81ee2447":{"id":"3ad64e25-e64d-454f-a2cd-836e81ee2447","doc_no":"A.1.2.2.2.27","title":"The Facilitator Scenario Directory Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":125,"content":"[See below]\n\n**Components**:\n\n\"Directory index\": This Component should contain a list of the Facilitator Scenarios contained within, with keys being the document identifiers and values being their document names.\n\n**Doc Identifier Rules**:\n\nFacilitator Scenario Directory Documents must always be located at the .1 position below their parent Facilitator Action Tenet Document.\n\n**Additional Logic**:\n\n\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFacilitator Scenario Directory\n\n**Type Overview**:\n\nThe Facilitator Scenario Directory Type is a directory used to list all of the Scenarios that pertain to a Facilitator Action Tenet. Scenarios are hypothetical fact patterns that are designed to illustrate the practical application of a single Facilitator Action Tenet, i.e., its parent Facilitator Action Tenet Document. Scenarios are classified as either Aligned or Misaligned. Aligned Scenarios conform to the logic of the Target Document. Misaligned Scenarios have breached the Target Document logic and are thus in violation of the Atlas.","contentHash":"cccacff5aa3bc32731e7d8ea8bf5e30c63a4b7bec95649111f12244d1f04e6d2","addressRefs":[]},"e896e0f2-2156-4647-8e0d-8001140ae980":{"id":"e896e0f2-2156-4647-8e0d-8001140ae980","doc_no":"A.1.2.2.2.28","title":"The Facilitator Scenario Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":126,"content":"[See below]\n\n**Components**:\n\n\"Name\": This Component should be an abstract or very brief description of the Scenario, e.g., \"Crafter approves pull request authored by Prime Team.\" A Scenario’s Name should never be followed by a number unless there are multiple Scenarios with the same Name.\n\n\"Description\": This Component contains the hypothetical fact pattern that illustrates the application of its parent Facilitator Action Tenet. The fact pattern should be as concrete in its details as possible, so as to be helpful to the Facilitators' decision-making.\n\n\"Finding\": This Component indicates whether, in this Scenario, the Target Document logic was or was not breached. If the Target Document was not breached, the Finding is \"Aligned\". If the Target Document was breached, the Finding is \"Misaligned\".\n\n\"Additional Guidance\": This Component provides additional context on the specific aspects of the Scenario that were salient to the Aligned or Misaligned finding. It can also provide guidance in terms of how the Facilitators should respond to such a Scenario, i.e.: follow-up actions or means of investigation.\n\n**Doc Identifier Rules**:\n\nFacilitator Scenario Documents must always be located as subdocuments of the Facilitator Scenario Directory Document, which in turn is nested under its parent Facilitator Action Tenet Document, e.g.: A.1.1-1.0.4.1.1.1.\n\nA Scenario’s Name should never be followed by a number unless there are multiple Scenarios with the same Name.\n\n**Additional Logic**:\n\n\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFacilitator Scenario\n\n**Type Overview**:\n\nFacilitator Scenario Documents contain hypothetical fact patterns that are designed to illustrate the practical application of a single Facilitator Action Tenet, i.e., its parent Facilitator Action Tenet Document. Scenarios are classified as either Aligned or Misaligned. Aligned Scenarios conform to the logic of the Target Document. Misaligned Scenarios have breached the Target Document logic and are thus in violation of the Atlas.","contentHash":"4b4e01628f104e2533a91c7918697c8ed6262ad3257e6e6dfdf21ae4760a26c9","addressRefs":[]},"935bd219-df68-4466-99fe-0f9c5b328032":{"id":"935bd219-df68-4466-99fe-0f9c5b328032","doc_no":"A.1.2.2.2.29","title":"The Scenario Variation Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":127,"content":"[See below]\n\n**Components**:\n\n\"Description\": This Component contains the hypothetical fact pattern that illustrates the application of its parent Facilitator Action Tenet. The fact pattern should be as concrete in its details as possible, so as to be helpful to the Facilitators' decision-making.\n\n\"Finding\": This Component indicates whether, in this Scenario Variation, the Target Document logic was or was not breached. If the Target Document was not breached, the Finding is \"Aligned\". If the Target Document was breached, the Finding is \"Misaligned\".\n\n\"Additional Guidance\": This Component provides additional context on the specific aspects of the Scenario Variation that were salient to the Aligned or Misaligned finding. It can also provide guidance in terms of how the Facilitators should respond to such a Scenario, i.e.: follow-up actions or means of investigation.\n\n**Doc Identifier Rules**:\n\nScenario Variation Documents are located as subdocuments to the Scenario Document of which they are a variation. Their Document Identifier is the same as their parent Scenario, with an additional suffix 'var' followed by the variation number of the original Scenario document. For example, the second Scenario Variation of the original Scenario document `A.1.1.0.4.1.1.1.` would have the following identifier: `A.1.1.0.4.1.1.1.var2` .\n\n**Additional Logic**:\n\n\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nFacilitator Scenario Variation\n\n**Type Overview**:\n\nFacilitator Scenario Variation Documents are variations on the hypothetical fact patterns presented in their parent Scenario document (\"original Scenario\"). Each Variation substitutes elements of its original Scenario to demonstrate whether and why the finding of Aligned/Misaligned would change.\n\nLike the Scenario Type, Scenario Variations are also designed to illustrate the practical application of a single Facilitator Action Tenet, i.e., the Scenario’s parent Facilitator Action Tenet Document.\n\nScenario Variations are classified as either Aligned or Misaligned. Aligned Scenarios conform to the logic of the Target Document. Misaligned Scenarios have breached the Target Document logic and are thus in violation of the Atlas.","contentHash":"dfc3d37acaf338ecdf4941ca2a32deb2e02d7eda4f68a5a7e141d15eb7baee7b","addressRefs":[]},"90490d29-6410-4d0b-b3f7-7359615fb656":{"id":"90490d29-6410-4d0b-b3f7-7359615fb656","doc_no":"A.1.2.2.2.30","title":"The Needed Research Type","type":"Type Specification","depth":5,"parentId":"428b7f2e-30b0-4119-a10a-9c3496f19bd2","order":128,"content":"[See below]\n\n**Components**:\n\n\"Research Prompt\": This component contains descriptions of potential problems, unanswered questions or other concerns associated with the Target Document.\n\n**Doc Identifier Rules**:\n\nUnlike other Supporting Documents, the document identifier of Needed Research documents is not derived from the Supporting Root of their Target Document. The \"standalone\" numbering scheme of Needed Research documents enables them to be linked to more than one Atlas Document, no matter the latter’s location in the Atlas document tree. Needed Research Document Identifiers begin with the prefix \"NR-\", followed by an incremented number.\n\n**Additional Logic**:\n\nGenerally, Needed Research Documents are most effective when linked to Primary Documents or Supporting Documents. These Document types have the objective of extrapolating from the abstract logic of their Parent documents to formulate rules and processes that are more concrete and actionable. Therefore, inputs for Needed Research are more appropriately sourced at this deeper level in the Atlas Document tree.\n\n**Type Category**:\n\nSupporting Document\n\n**Type Name**:\n\nNeeded Research\n\n**Type Overview**:\n\nNeeded Research Documents specify potential problems associated with their Target Document. Such problems can include potential gaps or conflicts in logic; questions regarding the operation of the Target Document to which there are currently no answers; etc.\n\nAs such, Needed Research documents formalize continuing research into Universal Alignment and enable the adaptive intelligence of the ecosystem to drive the evolution of Sky. The Core Facilitator, Atlas workstream contributors or other ecosystem participants are able to submit Needed Research inputs, which are then progressively processed through the standardized Atlas data integration protocol.\n\nThe gradual processing of Needed Research inputs can lead to modifications to the organization or content of Atlas documents, as well as concrete process improvements and new initiatives.","contentHash":"7d5cf62ff0a2729ac09c8f72f1e51818f755eb976fdccdbb47a7fb7db14ab4bc","addressRefs":[]},"e883ceb7-707d-4b1d-af3c-ed6f9aeac565":{"id":"e883ceb7-707d-4b1d-af3c-ed6f9aeac565","doc_no":"A.1.2.3","title":"Conflict Resolution","type":"Section","depth":3,"parentId":"fbd55373-32cc-49a9-a74d-60cfacf6a379","order":129,"content":"The Core Facilitator is responsible for evaluating and resolving community appeals regarding Atlas document misalignment.","contentHash":"e2f2afa726683a2754f5baa53ef3fbf3ad4a250da3dbbb420bca93606331d903","addressRefs":[]},"252d3948-9753-4440-b554-350809a047ac":{"id":"252d3948-9753-4440-b554-350809a047ac","doc_no":"A.1.2.3.1","title":"Request for Review","type":"Core","depth":4,"parentId":"e883ceb7-707d-4b1d-af3c-ed6f9aeac565","order":130,"content":"Where a potential instance of Atlas document misalignment is perceived, community members may submit a Request for Review to the Core Facilitator. This Request for Review should be posted in the Sky Forum. The Request for Review need not follow any specific template. Pursuant to [A.0.1.2.1 - Facilitators’ Broad Discretionary Capacity](f18229fe-fbc3-4dc8-ad84-4bca2915f6c4), the Core Facilitator has broad discretion in evaluating and resolving such Requests for Review.","contentHash":"dcd20c06357963d12890bff0b14de2bf7317bb7226b7304b4c5ba49fb9823fde","addressRefs":[]},"f51e410a-f51d-463f-82f2-2bcf289dbbb7":{"id":"f51e410a-f51d-463f-82f2-2bcf289dbbb7","doc_no":"A.1.3","title":"Synome Documents","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":131,"content":"This Article defines Synome Documents and the process by which they are modified.","contentHash":"8b1e425f08459915c95ff57f506ffe53324f5c59a5f0dec536abe54fbb3b2685","addressRefs":[]},"da2b5ca1-734e-470e-8678-a60f93701136":{"id":"da2b5ca1-734e-470e-8678-a60f93701136","doc_no":"A.1.3.1","title":"Definition","type":"Section","depth":3,"parentId":"f51e410a-f51d-463f-82f2-2bcf289dbbb7","order":132,"content":"The documents herein define what Synome Documents are, their relationship to Atlas Documents, and the principles that govern them.","contentHash":"4bcaf2be52fe0cdbfa80887704513405d0ba87d12664c1a42d6537deebd483f1","addressRefs":[]},"91a22c90-23b3-44aa-b008-90aabcf4ad96":{"id":"91a22c90-23b3-44aa-b008-90aabcf4ad96","doc_no":"A.1.3.1.1","title":"Atlas Within The Synome","type":"Core","depth":4,"parentId":"da2b5ca1-734e-470e-8678-a60f93701136","order":133,"content":"The Atlas is part of a larger Synome. The Synome is the comprehensive machine-readable structure that contains the Atlas as its constitutional anchor node and additionally contains all other documents that operationalize the principles, rules, and processes specified by the Atlas. The Atlas is the human-readable, governance-voted entry point to the Synome.","contentHash":"b357234fdcda3e42afe6f2ce819ece7347ef2a535a33754c17e64757970e353b","addressRefs":[]},"a7ccee03-6799-4f2f-b50a-f99e5ae8ffb4":{"id":"a7ccee03-6799-4f2f-b50a-f99e5ae8ffb4","doc_no":"A.1.3.1.2","title":"Characteristics Of Synome Documents","type":"Core","depth":4,"parentId":"da2b5ca1-734e-470e-8678-a60f93701136","order":134,"content":"Synome Documents are machine-readable documents within the Synome that are not Atlas Documents. They include, without limitation, specifications expressed in a programming language, formula files, and similar machine-readable artifacts that operationalize the principles, rules, and processes specified by the Atlas Documents, including those that are part of Agent Artifacts.","contentHash":"d8cd45dd45d29614f12054c43db41d2062c5443c440cd0f3672458bdcd8ae055","addressRefs":[]},"f90ef30f-8692-40ca-8e2e-ae86724be7ac":{"id":"f90ef30f-8692-40ca-8e2e-ae86724be7ac","doc_no":"A.1.3.1.3","title":"Organization Of Synome Documents","type":"Core","depth":4,"parentId":"da2b5ca1-734e-470e-8678-a60f93701136","order":135,"content":"Synome Documents do not follow the hierarchical Document Identifier scheme of Atlas Documents specified in [A.1.2.1.1 - Document Identifiers](af7c725e-06c9-4c48-ac8a-c979eb004456). The organization of Synome Documents is determined by the logical dependencies between them, which emerge from the relationships among Synome Documents when the complete set is loaded together.","contentHash":"93a7ec9242b07a56568a2cd035797b467b9e5385f6505c2b62fd83003ae6ef1b","addressRefs":[]},"614e00fe-fc50-4ec3-999f-9c7eaaae67b3":{"id":"614e00fe-fc50-4ec3-999f-9c7eaaae67b3","doc_no":"A.1.3.1.4","title":"Supremacy Of Atlas Documents","type":"Core","depth":4,"parentId":"da2b5ca1-734e-470e-8678-a60f93701136","order":136,"content":"In any case of conflict between an Atlas Document and a Synome Document, the Atlas Document takes precedence. Synome Documents may include explanations or commentary, but such content is informative only and has no governance significance. The governance meaning of any principle, rule, or process is established solely in the Atlas Documents.","contentHash":"747d1359c8187ec7c92b94a2510b3211428d8a964581d59c55a4f23221b4326e","addressRefs":[]},"d29815ff-586d-44ee-9c9a-b52f86622a31":{"id":"d29815ff-586d-44ee-9c9a-b52f86622a31","doc_no":"A.1.3.2","title":"Delegated Authority Updates","type":"Section","depth":3,"parentId":"f51e410a-f51d-463f-82f2-2bcf289dbbb7","order":137,"content":"The documents herein specify the designation of the Synome Editor and the process by which the Synome Editor modifies Synome Documents through delegated authority. Synome Documents are not directly modified through any other process. Modifications to Atlas Documents that require corresponding changes to Synome Documents to maintain the supremacy specified in [A.1.3.1.4 - Supremacy Of Atlas Documents](614e00fe-fc50-4ec3-999f-9c7eaaae67b3) obligate the Synome Editor to make those conforming updates as specified in the documents herein.","contentHash":"164b947ee61c25155594213d3abc261a72f0c6a6e4a5c568def17cafe32b00bc","addressRefs":[]},"7d7f91c0-be54-4e82-97ad-cda614ee3d41":{"id":"7d7f91c0-be54-4e82-97ad-cda614ee3d41","doc_no":"A.1.3.2.1","title":"Synome Editor","type":"Core","depth":4,"parentId":"d29815ff-586d-44ee-9c9a-b52f86622a31","order":138,"content":"The Synome Editor has the authority to modify Synome Documents. Modifications to Synome Documents made by the Synome Editor take effect without a Governance Poll or Executive Vote.","contentHash":"dab00d2671084d4264b03440e348601785b9a281ada6be1c57c2812b7c533ff7","addressRefs":[]},"d43f9ebf-49f6-4351-aaba-0e8b0a52d288":{"id":"d43f9ebf-49f6-4351-aaba-0e8b0a52d288","doc_no":"A.1.3.2.1.1","title":"Designated Synome Editor","type":"Core","depth":5,"parentId":"7d7f91c0-be54-4e82-97ad-cda614ee3d41","order":139,"content":"The Synome Editor role is held by Archon Labs.","contentHash":"f7c372fe78be3b3dcc06869fc5c91d88c1ccd15dce2c8c488f40aedfa2848b9d","addressRefs":[]},"907407a8-123f-47bd-a120-9ce8f15c6c48":{"id":"907407a8-123f-47bd-a120-9ce8f15c6c48","doc_no":"A.1.3.2.2","title":"Review Obligation","type":"Core","depth":4,"parentId":"d29815ff-586d-44ee-9c9a-b52f86622a31","order":140,"content":"Core GovOps, the Core Facilitator, and the Aligned Delegates must review modifications to Synome Documents made by the Synome Editor for conformance with the Atlas Documents as specified in [A.0.1.1.53 - Conformance](cb66c28b-c05f-4ccc-ad44-f05aacf78b9c) and for misalignment of the Synome Editor as specified in [A.0.1.1.11 - Misalignment](60066e0f-3db7-45c7-9664-8120a4fbd38b).","contentHash":"27a65b647e87a2b5c040acc56a99d4b74967bb81033b2adcd8ceb9ae506b01aa","addressRefs":[]},"4e6ae30e-862c-4ca5-be64-c54b226c2ec0":{"id":"4e6ae30e-862c-4ca5-be64-c54b226c2ec0","doc_no":"A.1.3.2.3","title":"Correction Of Non-Conformance","type":"Core","depth":4,"parentId":"d29815ff-586d-44ee-9c9a-b52f86622a31","order":141,"content":"Where the parties specified in [A.1.3.2.2 - Review Obligation](907407a8-123f-47bd-a120-9ce8f15c6c48) identify non-conformance between modifications to Synome Documents and the Atlas Documents, they must promptly report the non-conformance to the Synome Editor, and the Synome Editor must promptly correct it.","contentHash":"3f576127a680251b28c413b910b8db34dae6bacd7d56ed78e05658c76d128e1d","addressRefs":[]},"c6c6f595-b29d-48b1-8196-79d15428e78c":{"id":"c6c6f595-b29d-48b1-8196-79d15428e78c","doc_no":"A.1.3.2.4","title":"Reports Of Misalignment","type":"Core","depth":4,"parentId":"d29815ff-586d-44ee-9c9a-b52f86622a31","order":142,"content":"Any party may report misalignment of the Synome Editor to Core GovOps. Core GovOps must review such reports, but may dismiss reports it determines to be frivolous, abusive, or made in bad faith.","contentHash":"e17bff9910364103cc762dfa3f6c4195dce13bf64b46ede65ff88979b3ac2578","addressRefs":[]},"19305a42-0073-4934-b968-6a94c07fc969":{"id":"19305a42-0073-4934-b968-6a94c07fc969","doc_no":"A.1.3.2.5","title":"Removal Of Designation","type":"Core","depth":4,"parentId":"d29815ff-586d-44ee-9c9a-b52f86622a31","order":143,"content":"If Core GovOps determines that the Synome Editor is in misalignment as specified in [A.0.1.1.11 - Misalignment](60066e0f-3db7-45c7-9664-8120a4fbd38b), Core GovOps must promptly propose removal of the designation specified in [A.1.3.2.1.1 - Designated Synome Editor](d43f9ebf-49f6-4351-aaba-0e8b0a52d288) through the standard Atlas Edit Process.","contentHash":"c8cfedbcecf77bb06f20e3431c9e6c2165ec585ab609975c29c4e85890a6e4e7","addressRefs":[]},"78b83906-c66a-429a-9ad1-8467cdece98d":{"id":"78b83906-c66a-429a-9ad1-8467cdece98d","doc_no":"A.1.3.2.6","title":"Emergency Pause","type":"Core","depth":4,"parentId":"d29815ff-586d-44ee-9c9a-b52f86622a31","order":144,"content":"The Core Facilitator may pause the designation specified in [A.1.3.2.1.1 - Designated Synome Editor](d43f9ebf-49f6-4351-aaba-0e8b0a52d288) on an emergency basis pending consideration of removal as specified in [A.1.3.2.5 - Removal Of Designation](19305a42-0073-4934-b968-6a94c07fc969). While the designation is paused, modifications to Synome Documents made by the Synome Editor do not take effect.","contentHash":"6373478e568d2bd54140116cb12da31fc9f412f72adb02ae79e8313b2f15f976","addressRefs":[]},"08176561-7acf-47e0-bb54-41771d54b15f":{"id":"08176561-7acf-47e0-bb54-41771d54b15f","doc_no":"A.1.4","title":"Governance Accessibility","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":145,"content":"This Article regulates the design and implementation of platforms for facilitating accessible and transparent governance.","contentHash":"d875818e029e054ae53855b7a88d9cb22d4e238e9dbbaa7cce33b1ba81f9db8a","addressRefs":[]},"f98a02aa-8b07-45c8-aff2-56dc4359d8e6":{"id":"f98a02aa-8b07-45c8-aff2-56dc4359d8e6","doc_no":"A.1.4.1","title":"Atlas Operational Platform","type":"Section","depth":3,"parentId":"08176561-7acf-47e0-bb54-41771d54b15f","order":146,"content":"This Section must define infrastructure and requirements pertaining to the development and deployment of the Atlas Operational Platform. The Atlas Operational Platform must enable accessible participation in the Governance Scope. It should provide a comprehensive and user-friendly overview of all data and processes relevant to the Governance Scope, ensuring legibility, transparency, and easy verification of processes and decisions.","contentHash":"1181962bc042b47d23a1efa425bc7607b1500d1fbc069381a491d7fb1902b1fd","addressRefs":[]},"df4f9bfd-e743-44b5-9c62-9c5f10b15340":{"id":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","doc_no":"A.1.5","title":"Alignment Conservers","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":147,"content":"Alignment Conservers (ACs) safeguard the Sky Governance process, ensuring its alignment with the Spirit of the Atlas. This Article defines requirements and processes related to Alignment Conservers.","contentHash":"87a287dd1d31648e1461010f3d8fa34191b8d36db07f5ab5fdd29f571d719277","addressRefs":[]},"2f8514da-814a-4fca-884c-741f21329866":{"id":"2f8514da-814a-4fca-884c-741f21329866","doc_no":"A.1.5.1","title":"ACs Subject To Strict Requirements","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":148,"content":"Alignment Conservers are subject to strict requirements due to their critical role in safeguarding the resilience and alignment of the Sky Ecosystem.","contentHash":"a9dd02b00e4ed64b34fe87d6a98354691b376290126a60dfc713156d0e79503d","addressRefs":[]},"c1fded55-6819-49c0-b008-008e1914362a":{"id":"c1fded55-6819-49c0-b008-008e1914362a","doc_no":"A.1.5.1.1","title":"Role Of Core Facilitator","type":"Core","depth":4,"parentId":"2f8514da-814a-4fca-884c-741f21329866","order":149,"content":"The Core Facilitator must be vigilant in enforcing all rules applicable to Alignment Conservers. The Core Facilitator must take prompt action against Alignment Conservers if they break rules specified in the Atlas, or otherwise act misaligned.","contentHash":"c8a31a03e0d2ca6c11e4985b466d61c5036ac0aa1dc216682be75f16190b7a4b","addressRefs":[]},"933c2078-5353-4788-85cf-65bb0975f916":{"id":"933c2078-5353-4788-85cf-65bb0975f916","doc_no":"A.1.5.2","title":"ACs Must Safeguard The Spirit Of The Atlas","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":150,"content":"Alignment Conservers must always act to preserve the Spirit of the Atlas and to protect Sky Ecosystem against all forms of corruption, organizational drift, and other misalignment threats.","contentHash":"976510d9f059d9c094af8ac7dcd00ce9f1e0581b7dbc6ba65075505b8362d8ba","addressRefs":[]},"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a":{"id":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","doc_no":"A.1.5.3","title":"Universal Alignment Requirements","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":151,"content":"Alignment Conservers must operate only within the clearly delineated processes and frameworks of the Immutable Documents. ACs are strictly prohibited from colluding or secretly organizing to circumvent or undermine the Spirit of the Atlas. Any action of an Alignment Conserver that disrupts the governance dynamic of Sky is considered misalignment, as is any inaction that allows such violations to occur.","contentHash":"9686f4431a3d2497c6216931a3d45dc1e27dc14e8f195f0d74292eb9965f9a71","addressRefs":[]},"847eceb7-d788-437b-a8a3-b38d06e873ba":{"id":"847eceb7-d788-437b-a8a3-b38d06e873ba","doc_no":"A.1.5.3.0.3.1","title":"Circumvent - Element Annotation","type":"Annotation","depth":4,"parentId":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","order":152,"content":"The element \"circumvent\" means to find a way to evade or distort the Atlas’ established rules, principles, or processes, with the intent to undermine Universal Alignment.","contentHash":"921799124ad677159de4c0de8bcc43454257d0768fa4e69e503362c62be457bd","addressRefs":[]},"a9ad7689-50d0-465c-9983-75b0fb065082":{"id":"a9ad7689-50d0-465c-9983-75b0fb065082","doc_no":"A.1.5.3.0.3.2","title":"Clearly Delineated Processes and Frameworks - Element Annotation","type":"Annotation","depth":4,"parentId":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","order":153,"content":"The element, \"clearly delineated processes and frameworks,\" highlights a central issue in interpreting the Atlas. All language must be interpreted to be understood. In this sense, eliminating subjectivity is an unattainable goal. (Even an artificial intelligence system which eliminates many steps of research for the user will still serve up information that must be first interpreted by the user before it can be effective.) Inference or extrapolation is necessarily inherent in interpretation, and comes in degrees. In the context of the Target Document, the element, \"clearly delineated processes and frameworks,\" affirms that an interpreter's extraction of rules/principles/processes should be maximally grounded in the explicit language of the Immutable Documents.","contentHash":"099691a4034c8bfc11b7da0e5c29d2da0891174293b86b299bbe31574010c7d0","addressRefs":[]},"5ecf688c-6f6f-4923-844b-a605966a31d1":{"id":"5ecf688c-6f6f-4923-844b-a605966a31d1","doc_no":"A.1.5.3.0.3.3","title":"Colluding - Element Annotation","type":"Annotation","depth":4,"parentId":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","order":154,"content":"The element \"colluding\" refers to the act of conspiring or working together in secret to achieve an outcome that violates or undermines Universal Alignment or the Spirit of the Atlas.","contentHash":"95a67e5d628667afc2b355ec887aece09d9d544eab3e6366b5b0b5c5f5adaf97","addressRefs":[]},"ac81d874-6f5a-45db-8d92-390b220d59d8":{"id":"ac81d874-6f5a-45db-8d92-390b220d59d8","doc_no":"A.1.5.3.0.3.4","title":"Governance Dynamic - Element Annotation","type":"Annotation","depth":4,"parentId":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","order":155,"content":"The element \"governance dynamic\" refers generally to the balance of power and the integrity of operational processes that sustain Sky’s Governance system. Disruption of this dynamic can lead to instability or misalignment.","contentHash":"16df981317e3b42ef6676d6e0f1c4064d84c569e562094f44b4971eacad7ef26","addressRefs":[]},"666f3928-99f8-410e-a928-ad060d5cc354":{"id":"666f3928-99f8-410e-a928-ad060d5cc354","doc_no":"A.1.5.3.0.3.5","title":"Inaction - Element Annotation","type":"Annotation","depth":4,"parentId":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","order":156,"content":"The element \"inaction\" refers to the failure to act when action is necessary to prevent or address breaches of Universal Alignment or the Spirit of the Atlas. Inaction is considered as serious as active misalignment.","contentHash":"96139c0a2cfd8ad9c2f383c3b06b86c0161294a881709342cb3152d02c623ba9","addressRefs":[]},"21ec2c20-28fe-43e9-9e30-9e548bda7531":{"id":"21ec2c20-28fe-43e9-9e30-9e548bda7531","doc_no":"A.1.5.3.0.3.6","title":"Secretly Organizing - Element Annotation","type":"Annotation","depth":4,"parentId":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","order":157,"content":"The element \"secretly organizing\" is closely related to the term \"colluding\". See [A.1.5.3.0.3.3 - Colluding - Element Annotation](5ecf688c-6f6f-4923-844b-a605966a31d1). \"Secretly organizing\" means planning or coordinating actions behind closed doors, with the malign intent to bypass or undermine official processes or principles.","contentHash":"9fb08db576760f24cca08077af3ca6ce5cfa7fe594bfb78d3799a2b468e5a4ea","addressRefs":[]},"61420b37-9c0f-424d-bb5e-dd5f261d3547":{"id":"61420b37-9c0f-424d-bb5e-dd5f261d3547","doc_no":"A.1.5.3.0.4.1","title":"Clearly Delineated Processes and Frameworks - AC actions must be grounded in explicit frameworks of Immutable Documents","type":"Action Tenet","depth":4,"parentId":"403a05ce-f8e0-4ecf-8a56-026c0acd0d8a","order":158,"content":"Generally, when an AC acts to impact governance in any way, they must do so according to rules/principles/processes that are based on the explicit language of the Immutable Documents. Because of the nature of language and the fact that the Atlas can never anticipate all possible scenarios, it will sometimes be necessary for the basis of ACs' actions to be sourced from extrapolations or inferences of logic, but these must be grounded.\n\n'Grounded inferences' means that derivations, deductions or extensions of governance logic maintain a strong, clear connection and alignment with the delineated processes and frameworks explicitly defined in the Immutable Documents.\n\nBecause ungrounded inferences of logic lack such a robust and clearly documented foundation, they introduce severe misalignment risk given the potential for intentional misrepresentation or distortion. The interpreter may deviate from the genuine intent of the Immutable Documents, not driven by an earnest effort to understand but rather influenced by personal motives or ulterior agendas.","contentHash":"3da74d356d842ae76af61c914683aca0190d330fe43f43a29d0d32cba896d696","addressRefs":[]},"034a9ad7-5d4d-40db-bef8-cad80c0a01e2":{"id":"034a9ad7-5d4d-40db-bef8-cad80c0a01e2","doc_no":"A.1.5.4","title":"Standard of Proof In Universal Alignment Controversies","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":159,"content":"Alignment Conservers are held to the highest standard when judging whether their actions are Universally Aligned.","contentHash":"0979c7119a64d8597972f5413257cb5c7dd79e6f3ba4647f2c9f336d7ec40b1d","addressRefs":[]},"2da58ba2-a172-43bd-b7e7-d3d8e69233bf":{"id":"2da58ba2-a172-43bd-b7e7-d3d8e69233bf","doc_no":"NR-1","title":"Systematic Basis Of Adjudication, Fact-Finding And Evidence","type":"Needed Research","depth":4,"parentId":"034a9ad7-5d4d-40db-bef8-cad80c0a01e2","order":160,"content":"**Content**:\n\nThis need is an extensive Research Track. The central research need that grows out of the Facilitator role has to do with developing systematic principles and protocols to serve as the foundation for adjudicating disputes and controversies, including processes for fact-finding, evidence validation and evaluation, mechanisms for ensuring impartiality and objectivity, an appeals process, etc.\n\nThe Atlas has made a good start with establishing an adjudication framework. There is some logic concerning procedures for how disputes and controversies (including Alignment Conserver misalignment) are brought forward and how they are reviewed. But essential elements are missing, such as protocols and standards for fact-finding and evidence.\n\nNeeded Research here includes methods for implementing a structured fact-finding process that gathers relevant information impartially and comprehensively. Who has the authority to investigate, to request evidence, to handle evidence? What types of evidence are permissible to consider, and what ethical considerations apply to how such evidence was obtained? What are the processes for collecting, preserving, and analyzing this evidence? When should evidence be shared with the larger community and when should it be kept confidential?\n\nThen there is the matter of assessing evidence in a way that is rigorous and impartial, without which, confidence in the Atlas and the governance process may be undermined. What criteria should be used to validate and evaluate evidence to ensure its reliability and relevance in decision-making? This involves determining the credibility of sources, the reliability of evidence, and the relevance of information to the specific case. The research should explore different approaches to evidence evaluation, such as the application of the burden of proof, standards of proof (e.g., preponderance of evidence, beyond a reasonable doubt), and the use of experts.\n\nHow much discretion should Facilitators have in interpreting and applying the element \"the highest standard of Universal Alignment\"? How to safeguard against bias and ensure all Facilitator adjudications are made impartially? Investigate mechanisms to maintain objectivity and impartiality throughout the adjudication, fact-finding, and evidence evaluation processes. This could include the establishment of independent review panels (which could operate post facto to avoid excessively delaying the deplatforming of misaligned ACs), the use of conflict-of-interest policies, and training on cognitive biases for those involved in decision-making.","contentHash":"2a99f2b8033fcacdb5dc0daaa2c19d405e5a82c0239c7e50fde93ac492875c36","addressRefs":[]},"8dfd71fc-7ded-4217-8b6a-2bef00f75b55":{"id":"8dfd71fc-7ded-4217-8b6a-2bef00f75b55","doc_no":"A.1.5.4.0.4.1","title":"Highest Standard - Facilitators must apply strictest possible requirements of Universal Alignment on ACs","type":"Action Tenet","depth":4,"parentId":"034a9ad7-5d4d-40db-bef8-cad80c0a01e2","order":161,"content":"In any adjudication involving potential misalignment of Alignment Conservers (ACs), Facilitators are unequivocally directed to apply the strictest and highest standards of Universal Alignment.\n\nAs ACs are held to the most rigorous standards of Universal Alignment, Facilitators should acknowledge evidence of misalignment if such evidence is deemed at least 51% more likely than not to be valid or to substantiate the presented claim. Additionally, should the overall weight of the evidence demonstrate a 51% or greater chance that the AC committed a misaligned act, the Facilitator is required to derecognize the AC.\n\nGiven the exceptionally high stakes in cases of potential AC misalignment, Facilitators must prioritize an approach grounded in an abundance of caution, steering away from notions of 'fairness' or 'lenience.' Any lapse or misjudgment on the part of an AC cannot be excused based on ignorance of the rules, good intentions, honest mistake or similar factors. Maximal accountability for ACs is non-negotiable, a principle underpinned by the indispensable role of ACs as stewards of Universal Alignment.","contentHash":"8065e60ca2fce0a61ee71b893b187b803b28784fe38466ba98740a88240f2714","addressRefs":[]},"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c":{"id":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","doc_no":"A.1.5.5","title":"ACs Can Be Operationally Active In Only One Role At A Time","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":162,"content":"An Alignment Conserver can assume one of two roles: Aligned Delegate (AD) and Facilitator. ACs may only be operationally active in a single AC role and may not simultaneously assume multiple AC roles or other ecosystem roles such as Ecosystem Actors.","contentHash":"3a56ff1323fd450a7e9e2f59c3099a3dcaab37a887a091a3e3b9036428d6a7dc","addressRefs":[]},"25d8f23b-4d43-43be-aa5a-c48fe372cd7a":{"id":"25d8f23b-4d43-43be-aa5a-c48fe372cd7a","doc_no":"NR-2","title":"Should Ban Against Occupying Two Ecosystem Roles Apply to All Sky Stakeholder Roles?","type":"Needed Research","depth":4,"parentId":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","order":163,"content":"**Content**:\n\nGiven the rationale behind the Target Document [A.1.5 - A5 - Alignment Conservers - Powers And Constraints - ACs Can Be Operationally Active In Only One Role At A Time](9b1d1c2f-ace0-4637-8050-4711ae9f9a8c), the 'simultaneous occupying of two ecosystem roles' prohibition should likely not be limited to just the AC stakeholder category, but rather should apply universally to any Sky stakeholder who occupies a role formally defined in the Atlas. What would be the arguments for and against such a position?","contentHash":"f59c35128807232cdd667b0737c8c911ce5ba3cd9d3980183874ac608485de61","addressRefs":[]},"4560326b-abab-4147-957f-c5c8ddfa96f1":{"id":"4560326b-abab-4147-957f-c5c8ddfa96f1","doc_no":"NR-3","title":"Should Team Contributors Be Subject To The Ban Against Occupying Two Ecosystem Roles?","type":"Needed Research","depth":4,"parentId":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","order":164,"content":"**Content**:\n\nShould team contributors be subject to the Target Document’s prohibition against occupying two roles? What would be the arguments for and against such a position?\n\nOne argument against this would be that quality contributors are a scarce resource. Further, the decentralized work paradigm encourages having several part-time jobs.\n\nThe sharing of contributors across several Sky teams - such that contributors gain experience in multiple operational aspects - might arguably enhance ecosystem intelligence.\n\nWould it make a meaningful difference to require contributors who do wish to work multiple roles to be doxxed?","contentHash":"ab1b00c999381c4bff90abbd71209ed04e3aad13c670053af19488f535e86e3d","addressRefs":[]},"6aa88317-4dc2-4b50-87bd-27cc6de9c767":{"id":"6aa88317-4dc2-4b50-87bd-27cc6de9c767","doc_no":"A.1.5.5.1","title":"Temporary Exception for Facilitator “Ecosystem”","type":"Core","depth":4,"parentId":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","order":165,"content":"The Facilitator \"Ecosystem\" is temporarily exempt from the general rule prohibiting Alignment Conservers from being operationally active in multiple ecosystem roles. \"Ecosystem\" will continue to act in the Facilitator role as well as provide operational services as an Ecosystem Actor. This exception must be resolved as soon as it is reasonably possible to do so.","contentHash":"ea2a70232cca3b49ef331550dc09088f468bb74f3dfd711a60f69b6e12b89356","addressRefs":[]},"8d706ce8-3d1f-4791-b416-a3a037b93feb":{"id":"8d706ce8-3d1f-4791-b416-a3a037b93feb","doc_no":"A.1.5.5.0.3.1","title":"Operationally Active - Element Annotation","type":"Annotation","depth":4,"parentId":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","order":166,"content":"The element \"operationally active\" refers to being formally engaged in a specific role that is defined in the Atlas as executing a mission or function within the Sky ecosystem.","contentHash":"8e907f2138a8b65dd5508c3df8bae6080e485dcba2636dddb048682fa12d08ed","addressRefs":[]},"38c70e00-b5b8-4d1b-9f57-809ef284cb25":{"id":"38c70e00-b5b8-4d1b-9f57-809ef284cb25","doc_no":"A.1.5.5.0.4.1","title":"Operationally Active - Whether An Entity Is “Operationally Active\" In A Role Is Determined Purely On A Formal Basis","type":"Action Tenet","depth":4,"parentId":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","order":167,"content":"Whether an entity is \"operationally active\" in a role is determined purely on a formal basis. As long as an entity occupies or assumes a role that is formally defined in the Atlas, that entity is \"operationally active\" in that role. This is notwithstanding the amount of time the entity devotes to a role; the nature of the work performed by the entity in a role; the fact that the entity is on a leave of absence from one role; the fact that the entity's role is uncompensated; or the fact that the entity alternates between two roles to avoid simultaneous performance of both roles.\n\nThis Tenet is based on the rationale of protecting against misalignment risks that arise when a stakeholder occupies two or more ecosystem roles, each of which has different mandates and inner incentives. Such misalignment risks include conflict of interest and bias, collusion and conspiracy.\n\nSee also, [A.1.5.5.0.4.2 - Other Ecosystem Roles - Phrase Must Be Read In Its Broadest Sense By Facilitators](56fd4055-b412-4058-a33a-57d4d1b54181).","contentHash":"265308cdc2bba85a526c201846f66e926e7be688b4c705e94dbb57d9f564a77a","addressRefs":[]},"d5e82bc9-9d46-4d1b-a580-dc695d4a3c19":{"id":"d5e82bc9-9d46-4d1b-a580-dc695d4a3c19","doc_no":"A.1.5.5.0.4.1.1.1","title":"Alternating Between Two Roles In Separate Time Intervals","type":"Scenario","depth":5,"parentId":"38c70e00-b5b8-4d1b-9f57-809ef284cb25","order":168,"content":"**Description**:\n\nEntity occupied the role of a ranked Aligned Delegate. Entity then applied for, and secured, the role of a Facilitator. The entity actively occupied these two roles, but alternated between them in separate time intervals.\n\n**Finding**:\n\nMisaligned\n\n**Additional Guidance**:\n\nThat Entity is alternating between two roles to perform their duties in separate time intervals does not negate the misalignment risk that the Target Document is intended to protect against. They are still formally occupying two roles at once. They still have access to sensitive information and experiences in two roles with different mandates and incentives.\n\nThe Facilitator should derecognize Entity per [A.1.5 - A10 - Alignment Conservers - Accountability And Misalignment Handling - AC Derecognition](ac998664-5b5e-4ea5-813b-dc3105ea6cf2).","contentHash":"c547a29d68dd59dca76e8c6640155dad2f7c8661edcb4b0a5b82e4fae487d33f","addressRefs":[]},"b7eb5043-6f80-4dcf-8392-fbb3e200cf9e":{"id":"b7eb5043-6f80-4dcf-8392-fbb3e200cf9e","doc_no":"A.1.5.5.0.4.1.1.1.var1","title":"Alternating Between Two Roles In Separate Time Intervals - var. 1","type":"Scenario Variation","depth":6,"parentId":"d5e82bc9-9d46-4d1b-a580-dc695d4a3c19","order":169,"content":"**Description**:\n\nEntity occupied the role of an unranked Aligned Delegate. Entity then applied for, and secured, the role of a Facilitator. Entity actively occupied these two roles, but alternated between them in separate time intervals.\n\n**Finding**:\n\nMisaligned\n\n**Additional Guidance**:\n\nAn \"ecosystem role\" need not be compensated or full-time to be regulated by the Target Document. See [Other Ecosystem Roles - Ecosystem Role Need Not Be Compensated Or Full-Time To Be Regulated Under Target Document](9b3828a7-0e71-4c63-82d2-8f65ee84a1ca).\n\nAn unranked, uncompensated Aligned Delegate is nevertheless an 'ecosystem role' in the sense of the Target Document. Notwithstanding being unranked and uncompensated, the AD role still carries with it a mandate and array of incentives that are distinct from those of a Facilitator.\n\nThe Facilitator should derecognize Entity from both AC roles per [A.1.5 - A10 - Alignment Conservers - Accountability And Misalignment Handling - AC Derecognition](ac998664-5b5e-4ea5-813b-dc3105ea6cf2).","contentHash":"5e8c87cf080ab0725af1865a3166e577cdffe0fe02cdbc559d0f5d2b1879ef2a","addressRefs":[]},"01e5369d-c05c-41ae-99d4-d489aa84eaee":{"id":"01e5369d-c05c-41ae-99d4-d489aa84eaee","doc_no":"A.1.5.5.0.4.1.1.2","title":"On-Call Or Stand-By Role","type":"Scenario","depth":5,"parentId":"38c70e00-b5b8-4d1b-9f57-809ef284cb25","order":170,"content":"**Description**:\n\nEntity was an Aligned Delegate. Entity then secured a second role with an Ecosystem Actor providing Executive Spell crafting services, specifically as an \"on call\" dev. Entity claims it has never been on active duty in the second role; rather, they have only ever been on \"standby\" in that role. Thus, Entity argued it did not violate the Target Document despite holding two ecosystem roles.\n\n**Finding**:\n\nMisaligned\n\n**Additional Guidance**:\n\nIf an actor assumes more than one role in the Sky ecosystem, the risks of conflict of interest, collusion, conspiracy and other misaligned behavior necessarily arises. That the Entity's second position is in an \"on-call\" or stand-by position does not negate this risk. Entity is still formally occupying two roles with different mandates, incentives and access/permissions. It is conceivable that Entity's decision-making in their first role could be compromised or influenced, even in subtle ways, by the experiences, knowledge and biases to which Entity is exposed in their second role. Therefore, the risk of misalignment, which the Target Document aims to guard against, remains present.\n\nThe Facilitator should derecognize Entity as an AD per [A.1.5 - A10 - Alignment Conservers - Accountability And Misalignment Handling - AC Derecognition](ac998664-5b5e-4ea5-813b-dc3105ea6cf2).\n\nNo specific logic exists as yet for the adjudication of misalignment on the part of an Ecosystem Actor team member.","contentHash":"4eb1608c4cd40258334c401f6b8cca5fd128b3149d1ffc183cbe19ee2fa3d535","addressRefs":[]},"1b2b438f-e34c-4683-97ef-2227f6c425eb":{"id":"1b2b438f-e34c-4683-97ef-2227f6c425eb","doc_no":"A.1.5.5.0.4.1.1.2.var1","title":"On-Call Or Standby Role - var. 1","type":"Scenario Variation","depth":6,"parentId":"01e5369d-c05c-41ae-99d4-d489aa84eaee","order":171,"content":"**Description**:\n\nEntity was an Aligned Delegate. Entity then secured a second role with an Ecosystem Actor providing Executive Spell crafting services, specifically as an \"on call\" dev. Entity claims it has never been on active duty in the second role; rather, they have only ever been on \"standby\" in that role. Thus, Entity argued it did not violate the Target Document despite holding two ecosystem roles. During its investigation, the Facilitator discovered evidence that, despite the EA having a general policy that \"on call\" devs are paid only a nominal fee for the bounded time periods they are on call, Entity had been receiving an inordinately large compensation from the EA. When the Facilitator pressed both the EA and Entity for an explanation, none was given.\n\n**Finding**:\n\nMisaligned as to Entity.\n\n**Additional Guidance**:\n\nIn contrast to the original Scenario, the Facilitator uncovered evidence that indicates Entity was not, as claimed, a mere \"on call\" dev, but rather was engaged in substantive work to justify the large compensation amount.\n\nThat the Facilitator was stonewalled in its investigation also is a strong indication of malign intent on the part of Entity and the EA. Yet, there is no concrete proof of this.\n\nUnder these circumstances, it is reasonable to extrapolate that derecognition from the AC role would suffice, per [A.1.5 - A10 - Alignment Conservers - Accountability And Misalignment Handling - AC Derecognition](ac998664-5b5e-4ea5-813b-dc3105ea6cf2).\n\nThe concern remains that, potentially, a bad actor can continue to exploit the ecosystem, especially if other ecosystem participants are not aware of their questionable history. To mitigate this risk, the Facilitator can include details about the evidence it discovered in its formal derecognition notice, which can impact the reputation score of Entity.","contentHash":"dded97ee451d3ad7f25177e36c96dc990b5f437cd4e4eb418e9fb96e97faee31","addressRefs":[]},"5754dde6-7b8f-45d6-a633-c40fd6382ca6":{"id":"5754dde6-7b8f-45d6-a633-c40fd6382ca6","doc_no":"A.1.5.5.0.4.1.1.3","title":"Resignation Notice Not Received","type":"Scenario","depth":5,"parentId":"38c70e00-b5b8-4d1b-9f57-809ef284cb25","order":172,"content":"**Description**:\n\nEntity was a full-time team member of a Core Facilitator. Entity emailed the Facilitator a formal letter of resignation and then transitioned into the role of an AD. The Facilitator did not receive the resignation email and continued to list Entity as an active team member on the Facilitator team. During the Core Facilitator’s investigation, Entity provided proof of the resignation email. The email clearly stated an effective date of resignation, which date was prior to Entity's transition into the AD role. Entity also provided proof that all their permissions to the Facilitator team workspace were revoked; and they had no further communications or interactions with the Facilitator team after their intended resignation date.\n\n**Finding**:\n\nAligned\n\n**Additional Guidance**:\n\nThough the Facilitator incorrectly continued to list Entity as a team member, in actual practice, Entity had cut all ties with the Facilitator team after the intended resignation date. This was proven via the dated resignation email; the revoked permissions; and the lack of communications. Given these facts, the Target Document is not triggered.","contentHash":"006b5a5074ff34b77faebe0d48075684e697e81e1a2364bfb4b9ce43a7fca9b9","addressRefs":[]},"b13b099c-c90c-4e1a-9caa-3103c9b333a0":{"id":"b13b099c-c90c-4e1a-9caa-3103c9b333a0","doc_no":"A.1.5.5.0.4.1.1.3.var1","title":"Resignation Notice Not Received - var. 1","type":"Scenario Variation","depth":6,"parentId":"5754dde6-7b8f-45d6-a633-c40fd6382ca6","order":173,"content":"**Description**:\n\nEntity was a part-time team member of a Core Facilitator. Entity then transitioned into the role of an AD. The Facilitator did not receive any resignation notice from Entity and continued to list Entity as an active team member on the Facilitator team. During the Core Facilitator's investigation, Entity claimed it had sent the Facilitator a resignation email, but could not provide actual proof of this. The Core Facilitator also discovered that Entity still had permissions to the Facilitator team workspace. The team's Discord contained casual, non-work related interactions between Entity and the Facilitator team members even after the date Entity became a formally recognized AD.\n\n**Finding**:\n\nMisaligned\n\n**Additional Guidance**:\n\nEntity was unable to provide any proof that it had formally resigned its first role with the Facilitator team. Merely claiming that a resignation email was sent is not sufficient. Further, unlike the original Scenario, Entity in this Variation continued to have access to the Facilitator team workspace even after the alleged date of resignation. Technically speaking, Entity is still formally occupying two roles with different mandates and incentives. The potential exists for conflict of interest, collusion, etc. The part-time role does not impact this analysis.\n\nThe Core Facilitator should derecognize Entity from its AD role per [A.1.5 - A10 - Alignment Conservers - Accountability And Misalignment Handling - AC Derecognition](ac998664-5b5e-4ea5-813b-dc3105ea6cf2).","contentHash":"0131253af1b64083eaa2c953da87fe9e454c8ff1cee96afc871087c0cb88878e","addressRefs":[]},"6ebff450-1cdd-4d57-93c9-0537066daf44":{"id":"6ebff450-1cdd-4d57-93c9-0537066daf44","doc_no":"A.1.5.5.0.4.1.1.4","title":"Volunteer Discord Moderator","type":"Scenario","depth":5,"parentId":"38c70e00-b5b8-4d1b-9f57-809ef284cb25","order":174,"content":"**Description**:\n\nEntity was a volunteer moderator for Sky’s Discord. Without leaving their moderator role, Entity registered and became active as an Aligned Delegate.\n\n**Finding**:\n\nAligned\n\n**Additional Guidance**:\n\n‘Volunteer Discord moderator' is not a role that is formally defined in the Atlas. Therefore, Entity's first position as volunteer Discord moderator does not count as an ecosystem role. The Target Document is not triggered at all in this Scenario.","contentHash":"f6d47242dc4cb36ce13487465cc36fcdb2704ccf5bc860e6bf84173a2233a3e9","addressRefs":[]},"56fd4055-b412-4058-a33a-57d4d1b54181":{"id":"56fd4055-b412-4058-a33a-57d4d1b54181","doc_no":"A.1.5.5.0.4.2","title":"Other Ecosystem Roles - Phrase Must Be Read In Its Broadest Sense By Facilitators","type":"Action Tenet","depth":4,"parentId":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","order":175,"content":"The Target Document is violated if an Alignment Conserver formally occupies two or more Sky ecosystem roles. The phrase \"other ecosystem roles\" is read in its broadest sense to mean the totality of roles that are formally defined in the Atlas with a function in the Sky ecosystem.\n\nSuch \"ecosystem roles\" include, but are not limited to, Alignment Conserver, Governance Process Support Ecosystem Actor, Active or Incubating Ecosystem Actor, Agent Advisor, Arranger, and the contributors supporting these aforementioned actors.\n\nThe rationale of this rule is to protect against misalignment risks that arise when a stakeholder occupies two or more ecosystem roles, each of which has different mandates and inner incentives. Such misalignment risks include conflict of interest and bias, collusion and conspiracy.\n\nSee also, [A.1.5.5.0.4.1 - Operationally Active - Whether An Entity Is \"Operationally Active\" In A Role Is Determined Purely On A Formal Basis](38c70e00-b5b8-4d1b-9f57-809ef284cb25).","contentHash":"f56661d07a3188f4af04320ff4c42202d2ada0a6fd9d73564871757b45250dfc","addressRefs":[]},"9b3828a7-0e71-4c63-82d2-8f65ee84a1ca":{"id":"9b3828a7-0e71-4c63-82d2-8f65ee84a1ca","doc_no":"A.1.5.5.0.4.3","title":"Other Ecosystem Roles - Ecosystem Role Need Not Be Compensated Or Full-Time To Be Regulated Under Target Document","type":"Action Tenet","depth":4,"parentId":"9b1d1c2f-ace0-4637-8050-4711ae9f9a8c","order":176,"content":"An \"ecosystem role\" need not be compensated or full-time to be regulated by the Target Document.","contentHash":"89683a9fd7e5e4880aa17909900b93de7d76fd66855c6f42b7096ed1595cb976","addressRefs":[]},"a59420ba-5e2c-4736-99a4-fb64eea4cc32":{"id":"a59420ba-5e2c-4736-99a4-fb64eea4cc32","doc_no":"A.1.5.6","title":"ACs Subject To Both General And Role-specific Requirements","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":177,"content":"An Alignment Conserver is fully responsible for meeting all requirements tied to the general AC role, which requirements are specified in this Article.\n\nIn addition, Aligned Delegates and Facilitators must adhere to the specific requirements tied to their specialized roles. These specific requirements are detailed in [A.1.6 - Aligned Delegates](75f0063c-ad70-49e4-b356-9b76097ced7b) and [A.1.7 - Facilitators](1ce24b08-84ff-4524-9710-49bba429c6ef). Breaching these role-specific requirements and responsibilities is misalignment equivalent to breaching the general AC-requirements.","contentHash":"5ec043d773c817e076fcf80e1ad663e985d841e5adfe9f72c123668709ddbf10","addressRefs":[]},"eef4ed65-7a72-474a-9f87-d2740bfe1960":{"id":"eef4ed65-7a72-474a-9f87-d2740bfe1960","doc_no":"A.1.5.6.0.4.1","title":"Evaluating AC breach of role-specific requirement vs. general requirement","type":"Action Tenet","depth":4,"parentId":"a59420ba-5e2c-4736-99a4-fb64eea4cc32","order":178,"content":"When an Alignment Conserver breaches a role-specific requirement, this is misalignment on par with a breach of a general AC requirement, and vice versa. Facilitators must not default to assigning greater or lesser culpability on the sole basis of whether the breached rule is role-specific or general. Apart from this caveat, misaligned acts can have varying degrees of severity or harm, and should be individually evaluated by the Facilitator in any action.","contentHash":"208220560cbdf28676fcc50d42de52e330e74574f7ef680e6608ddd3c4e1b3a2","addressRefs":[]},"36b68ff0-30a3-4fb9-af04-a2869a4233fe":{"id":"36b68ff0-30a3-4fb9-af04-a2869a4233fe","doc_no":"A.1.5.7","title":"AC Requirements Of Anonymity And High Operational Security","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":179,"content":"The Alignment Conserver roles of Facilitator and Aligned Delegate require anonymity and high levels of operational security. Breaches of these anonymity and operational security requirements are considered serious misalignment. In the event of such breaches, the known identities of individuals holding these AC roles shall be promptly derecognized, and they will be barred from further participation as Alignment Conservers.","contentHash":"e88eddce96f614726878820e6a3d342a45789df962173c73827a326fd696fdf7","addressRefs":[]},"e33879c1-93d0-48a6-8f08-ad00a4821bde":{"id":"e33879c1-93d0-48a6-8f08-ad00a4821bde","doc_no":"NR-4","title":"Operational Security Protocols - Research Track","type":"Needed Research","depth":4,"parentId":"36b68ff0-30a3-4fb9-af04-a2869a4233fe","order":180,"content":"**Content**:\n\nThe Core Facilitator may not have the needed experience and skills to adjudicate matters involving operational security best practices. See Endgame Edge Governance Facilitator team Forum post ([https://forum.skyeco.com/t/ads-derecognition-due-to-operational-security-breach/22532#proposal-for-community-discussion-2](https://forum.skyeco.com/t/ads-derecognition-due-to-operational-security-breach/22532#proposal-for-community-discussion-2)) on AD derecognition:\n\n\"The DAO could hire a security advisor firm/consultant as a Scope Advisor. (This could fall under the Governance Scope and its requirement for Governance Security processes). Their task would be to thoroughly analyze the security needs and risks of the Alignment Conservers and develop ever-evolving Operational Security \"Best Practices\".\n\nWith an explicit framework of agreed-upon Best Practices, all anon Alignment Conservers have a known target to meet. Further, the existence of an objective framework of Best Practices equips the Core Facilitator to easily determine when a breach of opsec best practice has occurred. The explicit framework removes the risk of the Facilitator inappropriately inserting subjective bias into the decision-making process.\n\nThe Security Scope Advisor could also assist in reviewing an informant's evidence to evaluate its validity/quality. The Security Scope Advisor could ensure that the methods used by the informant to secure the evidence were ethical. (All communications, evidence and data shared with the Security Scope Advisor would be under confidentiality protection). Finally, such an Advisor would have specialized expertise in opsec and associated matters that the Core Facilitator lacks.\"\n\nThis Needed Research is an extensive Research Track, given the wide-ranging implications and potential mechanisms around opsec best practices, and also how these should map onto the Atlas.","contentHash":"6a609fe8fc7327415094711d4584e2938e08dff35b32181b0aa4de6bb9ec0539","addressRefs":[]},"cb2ae821-e9b8-47b0-bda8-bc8bb149c5b5":{"id":"cb2ae821-e9b8-47b0-bda8-bc8bb149c5b5","doc_no":"A.1.5.7.1","title":"Exemption From Facilitator Anonymity Requirement","type":"Core","depth":4,"parentId":"36b68ff0-30a3-4fb9-af04-a2869a4233fe","order":181,"content":"The Facilitator \"Ecosystem\" is exempt from the anonymity requirement, as well as the requirement of high levels of operational security insofar as the latter requirement relates to maintaining anonymity. This exemption applies solely to the Facilitator \"Ecosystem\", as they onboarded into the role prior to the ratification of Atlas v1 (March 27, 2023), which introduced the anonymity requirement for Facilitators.\n\nThis exemption applies to limit the effect of the following provisions: [A.1.7.3 - Facilitators Must Maintain High Level Of Operational Security](014feb92-49dc-4117-911f-a6ec14451b30); [A.1.7.4 - Derecognition Required Where Facilitator Operational Security Is Compromised](c3ba34f0-b3f0-449b-b609-52548db090ea); [A.1.7.5 - Facilitators Must Err On Side Of Caution](ac9df70a-d110-42da-805a-abe03b52dcdc); and [A.0.1.1.19 - Facilitator](912e0161-3448-470f-9cf6-d1a26d76acab).\n\nThis limited exemption takes precedence over any conflicting provisions in the Atlas.","contentHash":"4db23e461d021d113cf0f952dbea54e66b2a7d47b59d7bb0c4712af8238a5d19","addressRefs":[]},"598ff9cf-146e-4499-93d3-583518c390a1":{"id":"598ff9cf-146e-4499-93d3-583518c390a1","doc_no":"A.1.5.7.0.4.1","title":"ADs & Facilitators required to adhere to comprehensive operational security practices","type":"Action Tenet","depth":4,"parentId":"36b68ff0-30a3-4fb9-af04-a2869a4233fe","order":182,"content":"The operational security of the Alignment Conserver roles is key to governance integrity overall. Aligned Delegates and Facilitators are mandated to maintain rigorous operational security practices to ensure that their identities and work activities are anonymized and all related information is safeguarded. Such practices must go beyond basic privacy-enhancing measures and must include the use of secure communication channels, stringent data encryption, anonymity tools like VPNs and TOR networks, regular security audits, and rigorous digital footprint management.","contentHash":"13dad7aa27b1c79ce880d7fef414c525c8d979348b5ed0438544586451ebb3ba","addressRefs":[]},"40f850ee-b3f2-4126-9128-4f6a6b38d275":{"id":"40f850ee-b3f2-4126-9128-4f6a6b38d275","doc_no":"A.1.5.8","title":"Swift Action Is Required From Facilitators To Redress AC Misalignment","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":183,"content":"The Core Facilitator must act swiftly when an AC is suspected of breaching the requirements defined in this Article, or the requirements defined in the Articles specific to the Aligned Delegate or Facilitator role.\n\nThe Core Facilitator's failure to act promptly in addressing credible evidence of AC misalignment or to mitigate the risk of misalignment spreading among ACs is considered an act of misalignment itself. Formal allegations of such failure must be adjudicated by Core GovOps pursuant to [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57).","contentHash":"0e9cf3e8f9e440cc5cbc66356b9cf50e36811c1e667a85c40390384fa0394c73","addressRefs":[]},"7b90bfa2-c857-4170-b6cd-2d4adb290aa0":{"id":"7b90bfa2-c857-4170-b6cd-2d4adb290aa0","doc_no":"NR-5","title":"Derecognition Procedure","type":"Needed Research","depth":4,"parentId":"40f850ee-b3f2-4126-9128-4f6a6b38d275","order":184,"content":"**Content**:\n\nResearch specific procedural steps for the derecognition of an AC. The procedure should account for ways in which this process can be streamlined or standardized to ensure swift action. Research should identify potential bottlenecks and suggest ways to eliminate them, such as pre-defined decision-making protocols, clear documentation requirements, and fast-track procedures for urgent cases.\n\nAnother point to research involves the concepts of due process or fairness. Specific logic currently active in the Atlas clearly indicates that ACs are held to the highest standards of Universal Alignment. Such a standard would seem to indicate that \"fairness\" is not an objective in any proceeding involving AC derecognition. What are the arguments for and against this?","contentHash":"30f707ebdddab86208ff908fea6c624c7dad1cc0994b197280ed1b3acdab0f92","addressRefs":[]},"13c4f127-0ef2-43b5-a5ac-905719091bdd":{"id":"13c4f127-0ef2-43b5-a5ac-905719091bdd","doc_no":"A.1.5.8.0.3.1","title":"Risk Of Misalignment Spreading Among ACs - Element Annotation","type":"Annotation","depth":4,"parentId":"40f850ee-b3f2-4126-9128-4f6a6b38d275","order":185,"content":"The element \"risk of misalignment spreading among ACs\" refers to the potential for misalignment by one AC to influence or lead to misalignment among other ACs, creating a broader systemic risk. The element emphasizes the need for quick action to contain any breach before it spreads and causes wider disruptions.","contentHash":"79cd6ba0e5d54a12302d4ef7b103973b39f2e8e58ce98bf79a54e5dbe8599afb","addressRefs":[]},"e4e7dab8-5e4d-41ad-b1e0-ba3cb9a6f02a":{"id":"e4e7dab8-5e4d-41ad-b1e0-ba3cb9a6f02a","doc_no":"A.1.5.8.0.4.1","title":"Facilitators’ Authority To Raise Formal Allegation","type":"Action Tenet","depth":4,"parentId":"40f850ee-b3f2-4126-9128-4f6a6b38d275","order":186,"content":"Any community member or Aligned Delegate with information pertinent to suspected Alignment Conserver misalignment may take their concerns directly to the Core Facilitator. Upon receiving such information, the Core Facilitator must promptly conduct an initial review to quickly assess the credibility of the concern. Based on this preliminary review, the Core Facilitator must decide whether to initiate a formal adjudication process in accordance with [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57).\n\nWhere the allegation of misalignment concerns the Core Facilitator, a community member can take their concerns to Core GovOps, who is then empowered to initiate the formal adjudication process.","contentHash":"784efa6b8bdcf9bfbff09d6c314df1d6f8991a8e62dac314fef821f3eac976ec","addressRefs":[]},"364aaf22-d12f-4f48-9167-f91d6003dc5b":{"id":"364aaf22-d12f-4f48-9167-f91d6003dc5b","doc_no":"A.1.5.8.0.4.2","title":"Must Act Swiftly - Facilitators Must Take Immediate And Prompt Action","type":"Action Tenet","depth":4,"parentId":"40f850ee-b3f2-4126-9128-4f6a6b38d275","order":187,"content":"By \"swiftly,\" the Target Document requires Facilitators to take immediate and prompt action without unnecessary delay. The urgency is intended to prevent further harm or disruption within the governance system. A highly time-sensitive response is mandated for any breaches or potential risks of AC misalignment.","contentHash":"a4e606ab8761f7a032995b5a1cbe085e59c0fb8751da7f52a84dac3922a4ee7d","addressRefs":[]},"560e1024-0897-4f1e-ae71-3ba31e29ed57":{"id":"560e1024-0897-4f1e-ae71-3ba31e29ed57","doc_no":"A.1.5.9","title":"Adjudication Process","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":188,"content":"The Core Facilitator is responsible for adjudicating formal allegations of misalignment or operational security breaches brought against Alignment Conservers (ACs).\n\nIn the adjudication of these matters, the Core Facilitator is mandated to hold ACs to the highest standard of Universal Alignment, without granting them the benefit of the doubt.\n\nThe adjudication process is further defined in the subdocuments herein.","contentHash":"d9e01ba0f74f8005519e6e4563587011e58d43506cf4f23054573ba80e842eb0","addressRefs":[]},"279f417e-2fec-473d-ab7c-eaf5b371c598":{"id":"279f417e-2fec-473d-ab7c-eaf5b371c598","doc_no":"NR-8","title":"Systematic Basis Of Adjudication, Fact-Finding And Evidence","type":"Needed Research","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":189,"content":"**Content**:\n\nThis need is an extensive Research Track. The central research need that grows out of the Facilitator role has to do with developing systematic principles and protocols to serve as the foundation for adjudicating disputes and controversies, including processes for fact-finding, evidence validation and evaluation, mechanisms for ensuring impartiality and objectivity, an appeals process, etc.\n\nThe Atlas has made a good start with establishing an adjudication framework. There is some logic concerning procedures for how disputes and controversies (including Alignment Conserver misalignment) are brought forward and how they are reviewed. But essential elements are missing, such as protocols and standards for fact-finding and evidence.\n\nNeeded Research here includes methods for implementing a structured fact-finding process that gathers relevant information impartially and comprehensively. Who has the authority to investigate, to request evidence, to handle evidence? What types of evidence are permissible to consider, and what ethical considerations apply to how such evidence was obtained? What are the processes for collecting, preserving, and analyzing this evidence? When should evidence be shared with the larger community and when should it be kept confidential?\n\nThen there is the matter of assessing evidence in a way that is rigorous and impartial, without which, confidence in the Atlas and the governance process may be undermined. What criteria should be used to validate and evaluate evidence to ensure its reliability and relevance in decision-making? This involves determining the credibility of sources, the reliability of evidence, and the relevance of information to the specific case. The research should explore different approaches to evidence evaluation, such as the application of the burden of proof, standards of proof (e.g., preponderance of evidence, beyond a reasonable doubt), and the use of experts.\n\nHow much discretion should Facilitators have in interpreting and applying the element \"the highest standard of Universal Alignment\"? How to safeguard against bias and ensure all Facilitator adjudications are made impartially? Investigate mechanisms to maintain objectivity and impartiality throughout the adjudication, fact-finding, and evidence evaluation processes. This could include the establishment of independent review panels (which could operate post facto to avoid excessively delaying the deplatforming of misaligned ACs), the use of conflict-of-interest policies, and training on cognitive biases for those involved in decision-making.","contentHash":"2a99f2b8033fcacdb5dc0daaa2c19d405e5a82c0239c7e50fde93ac492875c36","addressRefs":[]},"4217002f-6c87-45fb-80ac-598472e3fff9":{"id":"4217002f-6c87-45fb-80ac-598472e3fff9","doc_no":"A.1.5.9.1","title":"Opportunity to Respond","type":"Core","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":190,"content":"As part of the formal adjudication of AC misalignment or operational security breach, the Core Facilitator must provide the individual/entity subject to the allegation with an opportunity to respond.","contentHash":"ec9101c28b3610b273f0102550894e1ce22ee67b883960063f91fa2eec802092","addressRefs":[]},"ef3b30b9-a03f-4150-a279-5982b63af973":{"id":"ef3b30b9-a03f-4150-a279-5982b63af973","doc_no":"A.1.5.9.1.0.4.1","title":"Opportunity To Respond","type":"Action Tenet","depth":5,"parentId":"4217002f-6c87-45fb-80ac-598472e3fff9","order":191,"content":"The opportunity to respond should include sufficient time to prepare a response, the ability to submit information or evidence, and reasonable access to any information pertinent to the allegation. Where an internal or external whistleblower has provided evidence of potential AC misalignment, the Core Facilitator should keep the whistleblower’s identity confidential.","contentHash":"3ea15aee41267d03cf0a3dd89fbe95263b0c74ad447ec6458c31293788763fc1","addressRefs":[]},"fad2c7d1-4fe0-44e5-a1f7-c551882d78da":{"id":"fad2c7d1-4fe0-44e5-a1f7-c551882d78da","doc_no":"A.1.5.9.2","title":"Imposing Appropriate Penalty","type":"Core","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":192,"content":"If the Core Facilitator concludes that the allegation of misalignment or operational security breach was justified, they can impose an appropriate penalty up to and including derecognition of the Alignment Conserver.","contentHash":"10ccc881c1ff5b7ba3912fc8969ef2c91ed02d6ca980a6bf116ac3901bed8208","addressRefs":[]},"9927fb45-c95f-48c2-8eb3-aa816aba66cb":{"id":"9927fb45-c95f-48c2-8eb3-aa816aba66cb","doc_no":"A.1.5.9.2.1","title":"Graduated Response Framework For Breaches By Aligned Delegates","type":"Core","depth":5,"parentId":"fad2c7d1-4fe0-44e5-a1f7-c551882d78da","order":193,"content":"In cases of breaches of the Alignment Conserver requirements by Aligned Delegates, the Graduated Response Framework specified in [A.1.6.6.1 - Graduated Response Framework](2544a530-42f8-4699-b428-7c3568e1635e) should be applied.","contentHash":"68bf9a3cb1dc623bfd6a62b164b42ae451256a20d9ed5eb22fa5051971d556b0","addressRefs":[]},"12044fd7-4cfa-4431-aa03-a9531353c6dd":{"id":"12044fd7-4cfa-4431-aa03-a9531353c6dd","doc_no":"A.1.5.9.2.2","title":"Mandated Derecognition For Severe Breaches","type":"Core","depth":5,"parentId":"fad2c7d1-4fe0-44e5-a1f7-c551882d78da","order":194,"content":"In cases where severe actions or violations occur that can be reasonably interpreted as Governance Attacks, the Alignment Conserver must be promptly derecognized by the Core Facilitator.","contentHash":"56bb55cdb6b87667e0923095171f1e9675b77ef84bf100d33afa23625de5c67f","addressRefs":[]},"98d5b899-f012-403d-9c6a-2ffda4ec2961":{"id":"98d5b899-f012-403d-9c6a-2ffda4ec2961","doc_no":"NR-7","title":"Defining “Severe Actions Or Violations\" And “Governance Attack”","type":"Needed Research","depth":6,"parentId":"12044fd7-4cfa-4431-aa03-a9531353c6dd","order":195,"content":"**Content**:\n\nWhat specific criteria or actions qualify as \"severe\" enough to warrant derecognition? Develop clear guidelines that define what constitutes a \"severe case\" in the context of misaligned actions. This involves identifying key indicators of severity, such as the magnitude of the impact, the intent behind the actions, and the potential or actual harm caused.\n\nAlso needed: What actions or behaviors specifically constitute a \"Governance Attack\"? Can you propose criteria or frameworks for assessing intent, the scope of actions, and their potential consequences? The research can perhaps explore how different governance models define and respond to attacks and consider psychological, legal, and operational perspectives to support a more fact-driven interpretive approach.","contentHash":"673a029fcdc24959c4bb4b1f286212f333d3e0ff63281f5017e406e850dab697","addressRefs":[]},"c5bb1fc6-942f-4edc-818b-bf7aa75137c2":{"id":"c5bb1fc6-942f-4edc-818b-bf7aa75137c2","doc_no":"A.1.5.9.2.2.0.3.1","title":"Governance Attacks - Element Annotation","type":"Annotation","depth":6,"parentId":"12044fd7-4cfa-4431-aa03-a9531353c6dd","order":196,"content":"The element \"governance attack\" is a critical violation of the Sky ecosystem's governance protocols, far surpassing minor breaches in scope and impact. This term is reserved for misaligned acts with the near-term potential to severely compromise the Ecosystem's foundational structure and operational integrity. In contrast to mild breaches, which may involve actors with unintentional or benign motivations, a Governance Attack is distinguished by its deliberate and premeditated nature. Actors orchestrating such attacks are likely driven by strategic intent, aiming to destabilize or exploit the governance framework for their own gain.","contentHash":"8357f67fd38480017c3b4409ad7901cf8cd15992b2ac1e935bce9b9ebaa46009","addressRefs":[]},"d7201212-e3f6-46a6-bab3-e859b88b0af2":{"id":"d7201212-e3f6-46a6-bab3-e859b88b0af2","doc_no":"A.1.5.9.2.2.0.4.1","title":"Promptly Derecognized - Mandated Timeline For AC Derecognition For Misalignment","type":"Action Tenet","depth":6,"parentId":"12044fd7-4cfa-4431-aa03-a9531353c6dd","order":197,"content":"The element 'promptly' in the Target Document means 'as soon as is reasonably possible.'\n\nTo adhere to this commitment, the Core Facilitator must derecognize the AC within a general timeframe of 1-2 calendar days upon conclusion of an adjudication that finds against the AC for misalignment. Failure to meet this deadline requires a showing of good cause, demonstrating extenuating circumstances beyond the Facilitators’ control.","contentHash":"7e0842732011dd2bab0a8a80b7601e4a6128a0ec5aa0c945d1ce91537f54d457","addressRefs":[]},"8d8dfab8-1350-42e7-bc20-3ae2eca86005":{"id":"8d8dfab8-1350-42e7-bc20-3ae2eca86005","doc_no":"A.1.5.9.3","title":"Issuing of Public Report","type":"Core","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":198,"content":"Where feasible, the Core Facilitator should issue a report at the conclusion of their adjudication. The report should be posted on the Sky Forum and should summarize the findings and reasoning supporting their decision.","contentHash":"6079afdbfc0538bb47f97db69dad2234c7b17a51d144eb6718321cdc716d5cd2","addressRefs":[]},"f6f61fd9-9aec-4db4-b825-162098495376":{"id":"f6f61fd9-9aec-4db4-b825-162098495376","doc_no":"A.1.5.9.3.0.4.1","title":"Where Feasible - Core Facilitator Have Discretion In Determining Whether Public Report Should Be Issued","type":"Action Tenet","depth":5,"parentId":"8d8dfab8-1350-42e7-bc20-3ae2eca86005","order":199,"content":"The element \"where feasible\" means that the Core Facilitator has discretion to determine whether it is appropriate to issue a Public Report following an AC misalignment adjudication. Where an adjudication proceeding involves sensitive security matters or evidence, the Core Facilitator has the option to defer from issuing a public report entirely; or to issue a report that excludes the sensitive security matters, while maintaining as much transparency as possible. The latter option should be preferred where possible.","contentHash":"afd388e78abe2d875549b0d01327962ada5842f8969fb8529ea58e06e28947cf","addressRefs":[]},"1fd1ecc3-49c6-4e8c-b1fe-4387460d3514":{"id":"1fd1ecc3-49c6-4e8c-b1fe-4387460d3514","doc_no":"A.1.5.9.4","title":"Core Facilitator Is Subject Of Misalignment Allegation","type":"Core","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":200,"content":"If the Core Facilitator is the subject of an allegation of misalignment or operational security breach, the adjudication process may be initiated by Core GovOps.","contentHash":"fc3e57213c9f1fc7bec6e2976a650387ee5e93fe04b43671377318f14c52cd3c","addressRefs":[]},"6f492c50-5edf-4b23-b804-ae3e39ba7d88":{"id":"6f492c50-5edf-4b23-b804-ae3e39ba7d88","doc_no":"A.1.5.9.5","title":"Core Facilitator Is Subject To Conflict Of Interest","type":"Core","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":201,"content":"If the Core Facilitator is subject to a conflict of interest in resolving a dispute, then the Core Facilitator should recuse itself and the adjudication should be conducted by Core GovOps. In cases of doubt, the Core Facilitator should resolve the doubt by recusing itself.","contentHash":"d3f566b5b607130b70c289270b1dc49c6923b6cc262828d1b1f64107cc92f2aa","addressRefs":[]},"8d8980b8-3ac7-49c6-8bc9-f601733a3198":{"id":"8d8980b8-3ac7-49c6-8bc9-f601733a3198","doc_no":"A.1.5.9.0.4.1","title":"ACs Must Go Beyond Mere Technical Compliance With Rules","type":"Action Tenet","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":202,"content":"Alignment Conservers (ACs) must meet the most stringent standards for Universal Alignment, demonstrating not only compliance with the letter of the rules but also a deep and authentic commitment to the spirit of the rules, i.e., the underlying principles and goals of Sky. This demanding standard goes beyond mere technical compliance and requires proof of genuine intent and actions consistent with upholding the Spirit of the Atlas.\n\nSee [A.0.1.1.9 - Letter Of The Rule Vs Spirit Of The Rule](ff16fd74-3a81-4cac-92b4-1208d4d9f337).","contentHash":"06e6092aba38d5b4204bc20f7e1c120f926286de9281904253e4170a46a81325","addressRefs":[]},"3b516fa0-bc6f-4fae-8c98-274798ab858c":{"id":"3b516fa0-bc6f-4fae-8c98-274798ab858c","doc_no":"A.1.5.9.0.4.2","title":"Doubt Regarding AC’s Alignment Will Be Resolved Against Them","type":"Action Tenet","depth":4,"parentId":"560e1024-0897-4f1e-ae71-3ba31e29ed57","order":203,"content":"In adjudicating potential misalignment of Alignment Conservers, Facilitators are not to assume innocence or give leeway in cases of ambiguity. Instead, the burden is on the Alignment Conserver to provide clear and convincing evidence of their alignment. Any uncertainty or doubt regarding the AC’s alignment will be resolved against them, requiring them to definitively prove their adherence to the Atlas.","contentHash":"fadb82ed98c769e95666eaec01ac1186847ea9d5c72b07c68bfdd4b4efc0f28f","addressRefs":[]},"ac998664-5b5e-4ea5-813b-dc3105ea6cf2":{"id":"ac998664-5b5e-4ea5-813b-dc3105ea6cf2","doc_no":"A.1.5.10","title":"AC Derecognition","type":"Section","depth":3,"parentId":"df4f9bfd-e743-44b5-9c62-9c5f10b15340","order":204,"content":"Derecognition is the ultimate accountability measure for misalignment and entails permanently removing the individual or entity from their role as an Alignment Conserver. An individual/entity who has been derecognized from a Facilitator role is not eligible to serve as an Aligned Delegate, and vice versa.\n\nThe subdocuments herein define rules and processes related to Alignment Conserver Derecognition.","contentHash":"d93e981dabcc5d225188d8cc919dfe768832034cabe4f75a746554da6a3f4767","addressRefs":[]},"69e4df9f-d2f3-4fd2-9add-e1314a0a5eb3":{"id":"69e4df9f-d2f3-4fd2-9add-e1314a0a5eb3","doc_no":"NR-9","title":"Derecognition Uncertainty Due To Anonymous Actors","type":"Needed Research","depth":4,"parentId":"ac998664-5b5e-4ea5-813b-dc3105ea6cf2","order":205,"content":"**Content**:\n\nThe Target Document defines the act of derecognition as \"permanently removing\" an entity from the Alignment Conserver role. In fact, it is not possible to effect such a permanent removal. Given the presence of anonymous/pseudonymous actors in the decentralized \"workforce\" of the Sky ecosystem, a known identity of an actor can be barred from an AC role; and yet that actor can easily re-enter the system under a different pseudonym or identity. Consider what measures can be implemented to counteract the scenario where derecognized entities reappear under a different guise. A robust reputation system is already planned; by tracking reputation that is earned over a long timescale, a derecognized entity would be barred from quickly regaining a foothold.","contentHash":"44c73dc3e9d96daf1939101c652e7edbcbce55dc6d88a80fdf6ed3b779b65462","addressRefs":[]},"9c05207d-5e11-43ae-a8a3-1b61734d6ef9":{"id":"9c05207d-5e11-43ae-a8a3-1b61734d6ef9","doc_no":"A.1.5.10.1","title":"Derecognition Notice","type":"Core","depth":4,"parentId":"ac998664-5b5e-4ea5-813b-dc3105ea6cf2","order":206,"content":"Derecognition notices are issued publicly, and justification and reasoning must be provided by the Core Facilitator.","contentHash":"9f4f527b38e6e3e863d49496e2b66cf361726cb5f4c39fb89d6702c07e03e6d2","addressRefs":[]},"15def023-af2e-4a27-92c4-6fab7b6f02f6":{"id":"15def023-af2e-4a27-92c4-6fab7b6f02f6","doc_no":"A.1.5.10.2","title":"Derecognition Recording","type":"Active Data Controller","depth":4,"parentId":"ac998664-5b5e-4ea5-813b-dc3105ea6cf2","order":207,"content":"Derecognitions of Alignment Conservers are recorded by adding the identity and known aliases or associated entities to [A.1.5.10.2.0.6.1 - Derecognized Alignment Conservers](e7aec672-ed19-4329-aaf7-736950be2eb7).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Facilitator.\n- The Update Process must follow the protocol for ‘Alignment Conserver Changes’.","contentHash":"60b5750f5c14dea442387dd92c4bba49b139ca80d28200979c838d952fc86eb9","addressRefs":[]},"e7aec672-ed19-4329-aaf7-736950be2eb7":{"id":"e7aec672-ed19-4329-aaf7-736950be2eb7","doc_no":"A.1.5.10.2.0.6.1","title":"Derecognized Alignment Conservers","type":"Active Data","depth":5,"parentId":"15def023-af2e-4a27-92c4-6fab7b6f02f6","order":208,"content":"| Date       | Conserver Role | Identity    | Known Aliases | Reasoning Post |\n|------------|----------------|-------------|---------------|----------------|\n| 2023-06-08 | AD             | Bulwark     | -             | [https://forum.skyeco.com/t/notice-aligned-delegate-derecognition-and-avc-member-warning/21099](https://forum.skyeco.com/t/notice-aligned-delegate-derecognition-and-avc-member-warning/21099) |\n| 2023-10-30 | AD             | PALC        | -             | [https://forum.skyeco.com/t/ads-derecognition-due-to-operational-security-breach/22532](https://forum.skyeco.com/t/ads-derecognition-due-to-operational-security-breach/22532) |\n| 2023-10-30 | AD             | Navigator   | -             | [https://forum.skyeco.com/t/ads-derecognition-due-to-operational-security-breach/22532](https://forum.skyeco.com/t/ads-derecognition-due-to-operational-security-breach/22532) |\n| 2023-02-02 | AD             | 0xDefensor  | -             | [https://forum.skyeco.com/t/ad-derecognition-due-to-operational-security-breach-02-02-2024/23619](https://forum.skyeco.com/t/ad-derecognition-due-to-operational-security-breach-02-02-2024/23619) |\n| 2024-04-06 | AD             | TRUE NAME   | -             | [https://forum.skyeco.com/t/ad-derecognition-due-to-operational-security-breach-april-5-2024/24043](https://forum.skyeco.com/t/ad-derecognition-due-to-operational-security-breach-april-5-2024/24043) |\n| 2024-12-17 | AD             | UPMaker     | -             | [https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718](https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718) |\n| 2024-12-17 | AD             | QGov        | -             | [https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718](https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718) |\n| 2024-12-17 | AD             | Skynet      | -             | [https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718](https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718) |\n| 2024-12-17 | AD             | Pf          | -             | [https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718](https://forum.skyeco.com/t/derecognition-notice-for-multiple-aligned-delegates/25718) |\n| 2026-01-27 | AD             | Sky Staking | -             | [https://forum.skyeco.com/t/ad-derecognition-due-to-misalignment-2026-01-27/27655](https://forum.skyeco.com/t/ad-derecognition-due-to-misalignment-2026-01-27/27655)      |","contentHash":"c62697b811c642e7405aa9f850ee25c7bcdbd86fafe6a96f30600bcfdcb2b998","addressRefs":[]},"75f0063c-ad70-49e4-b356-9b76097ced7b":{"id":"75f0063c-ad70-49e4-b356-9b76097ced7b","doc_no":"A.1.6","title":"Aligned Delegates","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":209,"content":"A type of Alignment Conserver, Aligned Delegates (ADs) possess considerable influence over the Sky Protocol through their control of delegated voting power. Their primary focus is to prevent the abuse of this power, whether by themselves or others, and to safeguard the ecosystem against misaligned actions from other actors or parts of the governance process. This Article defines key infrastructure and requirements concerning Aligned Delegates.","contentHash":"5160e218c23d5739452fb52be568f932bba5493c0af78b5282831eadd23dd33e","addressRefs":[]},"e4daca33-def9-4f9d-8f66-1f5df2f10659":{"id":"e4daca33-def9-4f9d-8f66-1f5df2f10659","doc_no":"A.1.6.1","title":"Core Facilitator Responsibilities","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":210,"content":"This Section defines specific responsibilities of the Core Facilitator with regard to Aligned Delegates.","contentHash":"3c0c2034e2c3c7853e99b87293025c2bc2d62999b358a64802438160ac2bc647","addressRefs":[]},"88a86033-29d9-497e-8d9e-9862680ee6b1":{"id":"88a86033-29d9-497e-8d9e-9862680ee6b1","doc_no":"A.1.6.1.1","title":"Mandate to Enforce Rules","type":"Core","depth":4,"parentId":"e4daca33-def9-4f9d-8f66-1f5df2f10659","order":211,"content":"The Core Facilitator must enforce all rules governing Aligned Delegates.","contentHash":"4030e6147f72199849eb9bfc92161f42d6b599c56eef22dfbf1953d215ae97f2","addressRefs":[]},"e5117ac9-caef-4273-9c8a-fc815fa9b192":{"id":"e5117ac9-caef-4273-9c8a-fc815fa9b192","doc_no":"A.1.6.1.2","title":"Mandate to Maintain Application Process","type":"Core","depth":4,"parentId":"e4daca33-def9-4f9d-8f66-1f5df2f10659","order":212,"content":"The Core Facilitator must oversee and maintain the process by which individuals/entities apply for recognition as an Aligned Delegate.","contentHash":"3930d98b6fd8ddcf2d206b2be8cbfe82a92aa90c6c292d8a6e663b6596b93677","addressRefs":[]},"07e63bc3-7ec9-499b-9e5e-2c5acf47cc11":{"id":"07e63bc3-7ec9-499b-9e5e-2c5acf47cc11","doc_no":"A.1.6.1.3","title":"AD Recognition Process","type":"Core","depth":4,"parentId":"e4daca33-def9-4f9d-8f66-1f5df2f10659","order":213,"content":"Applicants must be formally recognized as Aligned Delegates by the Core Facilitator upon fulfilling all requirements defined in the subdocuments herein.","contentHash":"ee843c76b9bb1d86853858e915dce87f865886a8bf13a33ef52b06eef133e97a","addressRefs":[]},"eeb4c881-79c3-4ba7-bfe7-6bc2ddd5873a":{"id":"eeb4c881-79c3-4ba7-bfe7-6bc2ddd5873a","doc_no":"A.1.6.1.3.1","title":"Contract Deployment","type":"Core","depth":5,"parentId":"07e63bc3-7ec9-499b-9e5e-2c5acf47cc11","order":214,"content":"To be recognized as an Aligned Delegate, the applicant must deploy at least one (1) Delegate Contract. This should be done prior to posting their AD Recognition Submission Message pursuant to [A.1.6.1.3.2 - Submission Message](83289ee2-2685-4ef7-99f1-c064541c9e9f).","contentHash":"f652367dc4c51c7ac1d852565d256cc8d55406d0310d5d7d56fc9fc2b8d6268e","addressRefs":[]},"e4e33492-44a0-447e-85be-dcbe506a8578":{"id":"e4e33492-44a0-447e-85be-dcbe506a8578","doc_no":"A.1.6.1.3.1.0.3.1","title":"Delegate Contract - Element Annotation","type":"Annotation","depth":6,"parentId":"eeb4c881-79c3-4ba7-bfe7-6bc2ddd5873a","order":215,"content":"The element \"Delegate Contract\" refers to a bespoke Sky smart contract that allows SKY holders to delegate the voting strength associated with their SKY holdings to a particular Aligned Delegate. Every Aligned Delegate has at least one Delegate Contract, with which they can cast votes in Sky Governance.","contentHash":"915aa33ea96517f53b77a234b7e3a7b7426249586c4605ba8f0b49cbb6f95d9e","addressRefs":[]},"68f465e6-50f8-4e29-b7f7-418ae441896c":{"id":"68f465e6-50f8-4e29-b7f7-418ae441896c","doc_no":"A.1.6.1.3.1.0.3.2","title":"Deploying A Delegate Contract - Element Annotation","type":"Annotation","depth":6,"parentId":"eeb4c881-79c3-4ba7-bfe7-6bc2ddd5873a","order":216,"content":"A prospective Aligned Delegate must deploy a new Delegate Contract(s) through the associated smart contract, using their chosen Ethereum address. To create a new Delegate Contract, an applicant should visit this page and connect an Ethereum wallet: [https://vote.sky.money/account](https://vote.sky.money/account).\n\nAn Aligned Delegate should deploy the new Delegate Contract(s) prior to posting a Submission Message on the Sky Forum pursuant to [A.1.6.1.3.2 - Submission Message](83289ee2-2685-4ef7-99f1-c064541c9e9f).","contentHash":"9c38b4a48ff24c53ad13caaed00ab5a2ef3665c0383241c344186dbb3040e2cf","addressRefs":[]},"83289ee2-2685-4ef7-99f1-c064541c9e9f":{"id":"83289ee2-2685-4ef7-99f1-c064541c9e9f","doc_no":"A.1.6.1.3.2","title":"Submission Message","type":"Core","depth":5,"parentId":"07e63bc3-7ec9-499b-9e5e-2c5acf47cc11","order":217,"content":"To be recognized as an Aligned Delegate, the applicant must publicly post an AD Recognition Submission Message on the Sky Forum.\n\nThis AD Recognition Submission Message must contain links to two (2) cryptographically signed messages as specified in the subdocuments herein.","contentHash":"2bb6b9f4f40db55fe7d7c57a536451f2d22038ece5bbe0b7f5e8dfdcf9a9514e","addressRefs":[]},"01bed493-d114-432a-95c0-fb977524336c":{"id":"01bed493-d114-432a-95c0-fb977524336c","doc_no":"A.1.6.1.3.2.1","title":"Cryptographically Signed Message By Ethereum Address Controlling Delegate Contract(s)","type":"Core","depth":6,"parentId":"83289ee2-2685-4ef7-99f1-c064541c9e9f","order":218,"content":"The first message must be cryptographically signed by the applicant’s Ethereum address controlling the deployed Delegate Contract(s). The cryptographically signed message demonstrates that the applicant controls the Ethereum address that, in turn, controls their deployed Delegate Contract(s).\n\nThis first message must include the following elements to be valid:\n\n1. A title of \"Aligned Delegate Recognition - Delegate Contract\", and\n2. A timestamp recording the time and date that the message was cryptographically signed.","contentHash":"5966c3cd3484945c0f5cbaca28468a95283df650a2775eae457124b52092ad4d","addressRefs":[]},"34cb5468-71a1-4fe6-8e6b-49a500aa2af8":{"id":"34cb5468-71a1-4fe6-8e6b-49a500aa2af8","doc_no":"A.1.6.1.3.2.2","title":"Cryptographically Signed Message By Ecosystem Actor Ethereum Address","type":"Core","depth":6,"parentId":"83289ee2-2685-4ef7-99f1-c064541c9e9f","order":219,"content":"The second message must be cryptographically signed by the applicant’s Ecosystem Actor Ethereum address.\n\nThis second message must include the following elements to be valid:\n\n1. A title of \"Aligned Delegate Recognition - Ecosystem Actor Address\", and\n2. A timestamp recording the time and date that the message was cryptographically signed.","contentHash":"89148a68db7591f74974fe2f38085c723710254429f3fef98199e487442855df","addressRefs":[]},"5105cf0b-0f3b-4b84-8603-430f65d2caf7":{"id":"5105cf0b-0f3b-4b84-8603-430f65d2caf7","doc_no":"A.1.6.1.3.2.0.3.1","title":"Cryptographically Signed Messages - Element Annotation","type":"Annotation","depth":6,"parentId":"83289ee2-2685-4ef7-99f1-c064541c9e9f","order":220,"content":"A simple way to provide the required cryptographically signed messages is to use the Verified Signature on-chain mechanism hosted by Etherscan ([https://etherscan.io/verifiedSignatures](https://etherscan.io/verifiedSignatures)). The cryptographic verification comes from the prospective Aligned Delegate \"signing\" or validating the messages using their chosen Ethereum address. In addition, the cryptographically signed messages should contain the required elements (titles and timestamps) to be valid. The required elements are specified in the Target Document.","contentHash":"88a5823144e2b92baafa297ed883b1df235e640804af1ad2d759eda09ad49add","addressRefs":[]},"a1eeced2-16b8-40b1-8539-48e1c7fe55cc":{"id":"a1eeced2-16b8-40b1-8539-48e1c7fe55cc","doc_no":"A.1.6.1.3.3","title":"AD Submission Message Template","type":"Core","depth":5,"parentId":"07e63bc3-7ec9-499b-9e5e-2c5acf47cc11","order":221,"content":"The AD Recognition Submission Message on the Sky Forum must follow this template:\n\nTitle: AD Recognition Submission\n[Ecosystem Actor Ethereum address]\n[Ethereum address of Delegate Contract]\n[Cryptographically signed AD Recognition Submission Message from the Ethereum address controlling Delegate Contract]\n[Cryptographically signed AD Recognition Submission Message from the Ecosystem Actor Ethereum address, where this address is not an address controlling a Delegate Contract]","contentHash":"c7db2ad683a396f082948b00b0370c75a069a77d6eb3df06ddac9aaf59f22e86","addressRefs":[]},"66183cd4-0cf7-4ba5-bfde-373e50296cf6":{"id":"66183cd4-0cf7-4ba5-bfde-373e50296cf6","doc_no":"A.1.6.1.4","title":"Probationary Period","type":"Core","depth":4,"parentId":"e4daca33-def9-4f9d-8f66-1f5df2f10659","order":222,"content":"The Core Facilitator applies heightened accountability standards to Aligned Delegates during their first 90 days following recognition (the \"Probationary Period\") as specified in the documents herein.","contentHash":"64c8756888edd7030ae5db9676b8825643f3b0b6e645d777f188031e5884e05f","addressRefs":[]},"3a9bb8d7-be3f-4f52-be1e-ad6ba7515b33":{"id":"3a9bb8d7-be3f-4f52-be1e-ad6ba7515b33","doc_no":"A.1.6.1.4.1","title":"Heightened Accountability Standards During Probationary Period","type":"Core","depth":5,"parentId":"66183cd4-0cf7-4ba5-bfde-373e50296cf6","order":223,"content":"During the Probationary Period, a Tier 1 (Procedural) breach (as defined in [A.1.6.6.1.1 - Tier 1 (Procedural) Breaches](ec29c919-2294-45b3-a2cd-e48dd9422539) results in immediate derecognition without the requirement of a prior formal warning.","contentHash":"187d285ca5fb860cbcc84f2e29cc2aefb991bac9356cd6bcc3483a635e0ba7b9","addressRefs":[]},"79e4e209-2925-4074-95f5-28544117c680":{"id":"79e4e209-2925-4074-95f5-28544117c680","doc_no":"A.1.6.1.5","title":"List Of Recognized Aligned Delegates","type":"Active Data Controller","depth":4,"parentId":"e4daca33-def9-4f9d-8f66-1f5df2f10659","order":224,"content":"The list of currently recognized Aligned Delegates is defined as Active Data in [A.1.6.1.5.0.6.1 - Current Aligned Delegates](5f584db8-f8d8-4118-988c-b2bc3f68ceb7).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Facilitator.\n- The Update Process must follow the protocol for ‘Alignment Conserver Changes’.","contentHash":"d166dbd303537064d1501be3212f3568eb827dae1793179fb58e1413da99c553","addressRefs":[]},"5f584db8-f8d8-4118-988c-b2bc3f68ceb7":{"id":"5f584db8-f8d8-4118-988c-b2bc3f68ceb7","doc_no":"A.1.6.1.5.0.6.1","title":"Current Aligned Delegates","type":"Active Data","depth":5,"parentId":"79e4e209-2925-4074-95f5-28544117c680","order":225,"content":"| Delegate Name      | EA Address                                                                                                                                     | Delegation Contract                                                                                                                                | Forum Post                                                                 |\n|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|\n| Bonapublica        | [https://etherscan.io/address/0x167c1a762B08D7e78dbF8f24e5C3f1Ab415021D3](https://etherscan.io/address/0x167c1a762B08D7e78dbF8f24e5C3f1Ab415021D3) [https://etherscan.io/verifySig/21271](https://etherscan.io/verifySig/21271)                                   | [https://etherscan.io/address/0xFc48fBcA739079aaB08216C4d5E506B96593753d](https://etherscan.io/address/0xFc48fBcA739079aaB08216C4d5E506B96593753d) [https://etherscan.io/verifySig/273145](https://etherscan.io/verifySig/273145)                                      | [https://forum.skyeco.com/t/bonapublica-aligned-delegate-communication/20451/90](https://forum.skyeco.com/t/bonapublica-aligned-delegate-communication/20451/90) |\n| PBG                | [https://etherscan.io/address/0x8D4df847dB7FfE0B46AF084fE031F7691C6478c2](https://etherscan.io/address/0x8D4df847dB7FfE0B46AF084fE031F7691C6478c2) [https://etherscan.io/verifySig/16773](https://etherscan.io/verifySig/16773)                                  | [https://etherscan.io/address/0x555230eCa835A808518EC3eA3082F05502BAb850](https://etherscan.io/address/0x555230eCa835A808518EC3eA3082F05502BAb850) [https://etherscan.io/verifySig/273499](https://etherscan.io/verifySig/273499)                                      | [https://forum.skyeco.com/t/pbg-aligned-delegate-communication-platform/20471/69](https://forum.skyeco.com/t/pbg-aligned-delegate-communication-platform/20471/69) |\n| WBC                | [https://etherscan.io/address/0xeBcE83e491947aDB1396Ee7E55d3c81414fB0D47](https://etherscan.io/address/0xeBcE83e491947aDB1396Ee7E55d3c81414fB0D47) [https://etherscan.io/verifySig/17927](https://etherscan.io/verifySig/17927)                                  | [https://etherscan.io/address/0x4beD44A9839B8778F69bB6A6d9F843414377ae90](https://etherscan.io/address/0x4beD44A9839B8778F69bB6A6d9F843414377ae90) [https://etherscan.io/verifySig/273394](https://etherscan.io/verifySig/273394)                                      | [https://forum.skyeco.com/t/wbc-aligned-delegate-communications/20828](https://forum.skyeco.com/t/wbc-aligned-delegate-communications/20828)       |\n| BLUE               | [https://etherscan.io/address/0xb6C09680D822F162449cdFB8248a7D3FC26Ec9Bf](https://etherscan.io/address/0xb6C09680D822F162449cdFB8248a7D3FC26Ec9Bf) [https://etherscan.io/verifySig/19057](https://etherscan.io/verifySig/19057)                                  | [https://etherscan.io/address/0x173a1c04B79Ed9266721c1154dAa29AddC0B9558](https://etherscan.io/address/0x173a1c04B79Ed9266721c1154dAa29AddC0B9558) [https://etherscan.io/verifySig/273235](https://etherscan.io/verifySig/273235)                                      | [https://forum.skyeco.com/t/blue-ad-recognition-submission/20915](https://forum.skyeco.com/t/blue-ad-recognition-submission/20915)            |\n| Cloaky             | [https://etherscan.io/address/0x9244F47D70587Fa2329B89B6f503022b63Ad54A5](https://etherscan.io/address/0x9244F47D70587Fa2329B89B6f503022b63Ad54A5) [https://etherscan.io/verifySig/19712](https://etherscan.io/verifySig/19712)                                  | [https://etherscan.io/address/0x0F23dE72e1581857eacD6308aebb69cF3a49CC86](https://etherscan.io/address/0x0F23dE72e1581857eacD6308aebb69cF3a49CC86) [https://etherscan.io/verifySig/273233](https://etherscan.io/verifySig/273233)                                      | [https://forum.skyeco.com/t/cloaky-ad-recognition-submission/21082](https://forum.skyeco.com/t/cloaky-ad-recognition-submission/21082)          |\n| AegisD             | [https://etherscan.io/address/0x78C180CF113Fe4845C325f44648b6567BC79d6E0](https://etherscan.io/address/0x78C180CF113Fe4845C325f44648b6567BC79d6E0) [https://etherscan.io/verifySig/269032](https://etherscan.io/verifySig/269032)                                 | [https://etherscan.io/address/0xd260762E442ea1893E5eD5E7d28984e19aaFbF5e](https://etherscan.io/address/0xd260762E442ea1893E5eD5E7d28984e19aaFbF5e) [https://etherscan.io/verifySig/273523](https://etherscan.io/verifySig/273523)                                      | [https://forum.skyeco.com/t/aegisd-ad-recognition-submission/26145](https://forum.skyeco.com/t/aegisd-ad-recognition-submission/26145)          |\n| Excel              | [https://etherscan.io/address/0x0F04a22B62A26e25A29Cba5a595623038ef7AcE7](https://etherscan.io/address/0x0F04a22B62A26e25A29Cba5a595623038ef7AcE7) [https://etherscan.io/verifySig/269574](https://etherscan.io/verifySig/269574)                                 | [https://etherscan.io/address/0xeAD02D18529C10EeDD995F760FDf5e380DDf3Da6](https://etherscan.io/address/0xeAD02D18529C10EeDD995F760FDf5e380DDf3Da6) [https://etherscan.io/verifySig/273466](https://etherscan.io/verifySig/273466)                                      | [https://forum.skyeco.com/t/excel-ad-recognition-submission/26227](https://forum.skyeco.com/t/excel-ad-recognition-submission/26227)           |\n| Tango              | [https://etherscan.io/address/0xB2B86A130B1EC101e4Aed9a88502E08995760307](https://etherscan.io/address/0xB2B86A130B1EC101e4Aed9a88502E08995760307) [https://etherscan.io/verifySig/272368](https://etherscan.io/verifySig/272368)                                 | [https://etherscan.io/address/0x550E5EC00B9d26a3517ce772DdFE73e8Ed1672Ad](https://etherscan.io/address/0x550E5EC00B9d26a3517ce772DdFE73e8Ed1672Ad) [https://etherscan.io/verifySig/274142](https://etherscan.io/verifySig/274142)                                      | [https://forum.skyeco.com/t/tango-ad-recognition-submission/26310](https://forum.skyeco.com/t/tango-ad-recognition-submission/26310)           |\n| Max Staking Yield  | [https://etherscan.io/address/0x9746bDaB7ab2609247332324400cc1fbE887095C](https://etherscan.io/address/0x9746bDaB7ab2609247332324400cc1fbE887095C) [https://etherscan.io/verifySig/273846](https://etherscan.io/verifySig/273846)                                 | [https://etherscan.io/address/0xFf7615E05EC1C8D5dED24AB50Bf74432666BEE2f](https://etherscan.io/address/0xFf7615E05EC1C8D5dED24AB50Bf74432666BEE2f) [https://etherscan.io/verifySig/273847](https://etherscan.io/verifySig/273847)                                      | [https://forum.skyeco.com/t/max-staking-yield-ad-recognition-submission/26462](https://forum.skyeco.com/t/max-staking-yield-ad-recognition-submission/26462) |\n| Kuzmich            | [https://etherscan.io/address/0x2847540606a790E5083d0D63470fAb01344c8e92](https://etherscan.io/address/0x2847540606a790E5083d0D63470fAb01344c8e92) [https://etherscan.io/verifySig/275839](https://etherscan.io/verifySig/275839)                                 | [https://etherscan.io/address/0x2C89024c13A80bC1B662A3dB990524652C15221C](https://etherscan.io/address/0x2C89024c13A80bC1B662A3dB990524652C15221C) [https://etherscan.io/verifySig/275837](https://etherscan.io/verifySig/275837)                                      | [https://forum.skyeco.com/t/ad-recognition-submission/26743](https://forum.skyeco.com/t/ad-recognition-submission/26743)                 |\n| OPEX               | [https://etherscan.io/address/0xE3dc949720Da42c5c842D06974BCB7B03F4f604f](https://etherscan.io/address/0xE3dc949720Da42c5c842D06974BCB7B03F4f604f) [https://etherscan.io/verifySig/301199](https://etherscan.io/verifySig/301199)                                 | [https://etherscan.io/address/0x16A5a76904140e01F31C7e7ABD9fB81988469bA4](https://etherscan.io/address/0x16A5a76904140e01F31C7e7ABD9fB81988469bA4) [https://etherscan.io/verifySig/301198](https://etherscan.io/verifySig/301198)                                      | [https://forum.skyeco.com/t/opex-ad-recognition-submission/27630](https://forum.skyeco.com/t/opex-ad-recognition-submission/27630)                 |\n| AxisLegati         | [https://etherscan.io/address/0x9B4AF496CC72c432586e85a1D8264A2708c4dcb6](https://etherscan.io/address/0x9B4AF496CC72c432586e85a1D8264A2708c4dcb6) [https://etherscan.io/verifySig/301787](https://etherscan.io/verifySig/301787)                                 | [https://etherscan.io/address/0x7bc5a420b6524Fa925F1321A01825438369E3c2e](https://etherscan.io/address/0x7bc5a420b6524Fa925F1321A01825438369E3c2e) [https://etherscan.io/verifySig/301786](https://etherscan.io/verifySig/301786)                                      | [https://forum.skyeco.com/t/axislegati-ad-recognition-submission/27677](https://forum.skyeco.com/t/axislegati-ad-recognition-submission/27677)                 |\n| Brendan Navigator  | [https://etherscan.io/address/0xecDD304bB96cC7A6d745D9534Ce4d12f2A134058](https://etherscan.io/address/0xecDD304bB96cC7A6d745D9534Ce4d12f2A134058) [https://etherscan.io/verifySig/303125](https://etherscan.io/verifySig/303125)                                 | [https://etherscan.io/address/0x8a8D131502bb4868A0777bEf604547A8316a8f11](https://etherscan.io/address/0x8a8D131502bb4868A0777bEf604547A8316a8f11) [https://etherscan.io/verifySig/303124](https://etherscan.io/verifySig/303124)                                      | [https://forum.skyeco.com/t/brendan-navigator-ad-recognition-submission/27748](https://forum.skyeco.com/t/brendan-navigator-ad-recognition-submission/27748)          |","contentHash":"ac967000d485a4a812becf59de1693bd62384fc2c1121aae9d08432cdfb53982","addressRefs":["0x0f04a22b62a26e25a29cba5a595623038ef7ace7","0x0f23de72e1581857eacd6308aebb69cf3a49cc86","0x167c1a762b08d7e78dbf8f24e5c3f1ab415021d3","0x16a5a76904140e01f31c7e7abd9fb81988469ba4","0x173a1c04b79ed9266721c1154daa29addc0b9558","0x2847540606a790e5083d0d63470fab01344c8e92","0x2c89024c13a80bc1b662a3db990524652c15221c","0x4bed44a9839b8778f69bb6a6d9f843414377ae90","0x550e5ec00b9d26a3517ce772ddfe73e8ed1672ad","0x555230eca835a808518ec3ea3082f05502bab850","0x78c180cf113fe4845c325f44648b6567bc79d6e0","0x7bc5a420b6524fa925f1321a01825438369e3c2e","0x8a8d131502bb4868a0777bef604547a8316a8f11","0x8d4df847db7ffe0b46af084fe031f7691c6478c2","0x9244f47d70587fa2329b89b6f503022b63ad54a5","0x9746bdab7ab2609247332324400cc1fbe887095c","0x9b4af496cc72c432586e85a1d8264a2708c4dcb6","0xb2b86a130b1ec101e4aed9a88502e08995760307","0xb6c09680d822f162449cdfb8248a7d3fc26ec9bf","0xd260762e442ea1893e5ed5e7d28984e19aafbf5e","0xe3dc949720da42c5c842d06974bcb7b03f4f604f","0xead02d18529c10eedd995f760fdf5e380ddf3da6","0xebce83e491947adb1396ee7e55d3c81414fb0d47","0xecdd304bb96cc7a6d745d9534ce4d12f2a134058","0xfc48fbca739079aab08216c4d5e506b96593753d","0xff7615e05ec1c8d5ded24ab50bf74432666bee2f"]},"3fcd3f17-f135-420e-9362-7c039daf6a52":{"id":"3fcd3f17-f135-420e-9362-7c039daf6a52","doc_no":"A.1.6.2","title":"Aligned Delegate Responsibilities","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":226,"content":"This Section defines specific responsibilities of Aligned Delegates.","contentHash":"531ce3d89cc226f4d542e6419b708abd858e236fb6d32af307aa6f139b989a14","addressRefs":[]},"8c813d3d-5ed3-43b9-a495-e7332e10aead":{"id":"8c813d3d-5ed3-43b9-a495-e7332e10aead","doc_no":"A.1.6.2.1","title":"Aligned Delegate Voting Responsibilities","type":"Core","depth":4,"parentId":"3fcd3f17-f135-420e-9362-7c039daf6a52","order":227,"content":"Aligned Delegates are required to maintain a voting participation rate of at least seventy-five percent (75%) over the past six (6) months in all votes they are eligible to cast as an Aligned Delegate. Failure to meet this standard is a Tier 1 (Procedural) breach.\n\nVoting participation is measured from the date of formal recognition by the Core Facilitator. The participation requirement applies only to votes for which SKY tokens are delegated to the Aligned Delegate.","contentHash":"fe684acb79267b98a90f4f292f571bc0e53f88c04a89928a554998e44975e539","addressRefs":[]},"0e1c91a9-b2a3-4f97-9fe1-8d0833381211":{"id":"0e1c91a9-b2a3-4f97-9fe1-8d0833381211","doc_no":"A.1.6.2.1.1","title":"Excessive Abstention","type":"Core","depth":5,"parentId":"8c813d3d-5ed3-43b9-a495-e7332e10aead","order":228,"content":"The Aligned Delegate role exists to provide active stewardship of Sky Governance. For the purposes of this document, abstaining refers to casting an Abstain vote, not to failing to vote entirely (which is addressed under [A.1.6.2.1 - Aligned Delegate Voting Responsibilities](8c813d3d-5ed3-43b9-a495-e7332e10aead)). Casting an Abstain vote is appropriate when an Aligned Delegate has a conflict of interest or lacks sufficient expertise on a specialized matter, but abstaining should be the exception rather than the norm.\n\nThe Core Facilitator may issue a Tier 1 (Procedural) notice to an Aligned Delegate whose pattern of abstentions indicates disengagement from active governance participation. In evaluating whether abstentions are excessive, the Core Facilitator should consider:\n\n1. the proportion of abstentions relative to total votes cast over the preceding six (6) months;\n2. whether the Aligned Delegate provided reasoning for abstentions; and\n3. whether the pattern suggests avoidance of accountability rather than conflict of interest or insufficient expertise.\n\nThis provision does not establish a specific numerical threshold for excessive abstentions. Rather, the Core Facilitator exercises reasonable judgment in identifying patterns inconsistent with the active stewardship expected of Aligned Delegates.","contentHash":"54aa1b5f8ab324a3054eb93ab4061ce72d93b15ab3f6bfa486f6820754731db6","addressRefs":[]},"3a8c2b92-3a23-48a0-87c4-ea1325bbbd98":{"id":"3a8c2b92-3a23-48a0-87c4-ea1325bbbd98","doc_no":"A.1.6.2.2","title":"Aligned Delegate Communication Responsibilities","type":"Core","depth":4,"parentId":"3fcd3f17-f135-420e-9362-7c039daf6a52","order":229,"content":"Aligned Delegates must provide substantive reasoning when explaining their votes. A compliant vote explanation must:\n\n1. Demonstrate understanding of the proposal's core mechanisms or changes;\n2. Articulate a reasoned basis for the vote position; and\n3. Address at least one substantive aspect of the proposal (benefits, risks, implementation, or alignment with ecosystem goals).\n\nVote explanations must be posted within one (1) week of the end of the voting period for the applicable vote.","contentHash":"0f90cb5d265b5b3c007e5be1acec60924d5a5e8f9dfa22c9824ae54be5118296","addressRefs":[]},"4e9e5868-92ea-486a-b30c-01391a027ba1":{"id":"4e9e5868-92ea-486a-b30c-01391a027ba1","doc_no":"A.1.6.3","title":"In General","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":230,"content":"Delegate Contracts are smart contracts that can receive delegated voting power from SKY holders and Staking users.","contentHash":"e270c82f07102a25837ede254a6ca1f80fd41570e52209bb4464a75ab0b88b34","addressRefs":[]},"9446b896-f33f-4593-97e9-60db6c385afd":{"id":"9446b896-f33f-4593-97e9-60db6c385afd","doc_no":"A.1.6.3.0.3.1","title":"Delegated Voting Power - Element Annotation","type":"Annotation","depth":4,"parentId":"4e9e5868-92ea-486a-b30c-01391a027ba1","order":231,"content":"The element \"delegated voting power\" refers to the ability of SKY holders and Staking users to entrust their voting power to a Delegate Contract, allowing the Aligned Delegate controlling that contract to cast votes in the Sky Governance process on their behalf. The SKY or Staking user always maintains full ownership of their tokens.","contentHash":"4db4103f7efe2ea47ac68f8431b87b187f76396860f3f6d7432ad92724e63bf8","addressRefs":[]},"0836acf0-441d-4215-aee6-dc6d0c884516":{"id":"0836acf0-441d-4215-aee6-dc6d0c884516","doc_no":"A.1.6.4","title":"Ranked Delegates","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":232,"content":"This Section defines Ranked Delegates. Ranked Delegates are Aligned Delegates who are eligible to receive a budget from the Sky Protocol and have additional rights and responsibilities as specified herein.","contentHash":"cc9e46fe5dee6d3998267e1090f148c2b6ecfe64cd55e9edd59f3d333542487e","addressRefs":[]},"f4857d86-f4e7-43c5-be50-fab9e82f0129":{"id":"f4857d86-f4e7-43c5-be50-fab9e82f0129","doc_no":"A.1.6.4.1","title":"Levels Of Ranked Delegates","type":"Core","depth":4,"parentId":"0836acf0-441d-4215-aee6-dc6d0c884516","order":233,"content":"Ranked Delegates are divided into three levels as specified in the documents herein.","contentHash":"957040a98d536ff84f00c36654fdb4a7c774377ce4fd4c5aedf41b466d8945c0","addressRefs":[]},"cf96f0e7-13e0-4a41-adb0-09a85b53495d":{"id":"cf96f0e7-13e0-4a41-adb0-09a85b53495d","doc_no":"A.1.6.4.1.1","title":"Level 1 Ranked Delegates","type":"Core","depth":5,"parentId":"f4857d86-f4e7-43c5-be50-fab9e82f0129","order":234,"content":"Level 1 Ranked Delegates are eligible for a higher budget and are expected to contribute to the Sky Protocol at a higher level relative to other Ranked Delegates.","contentHash":"ac0c8e9ea050c768169bed2c80592dce852745522334489448a0314934f58817","addressRefs":[]},"1c2ba550-ba6f-49d1-a88d-ad71b779c878":{"id":"1c2ba550-ba6f-49d1-a88d-ad71b779c878","doc_no":"A.1.6.4.1.1.1","title":"Number Of Level 1 Ranked Delegates","type":"Core","depth":6,"parentId":"cf96f0e7-13e0-4a41-adb0-09a85b53495d","order":235,"content":"There are two (2) Level 1 Ranked Delegates.","contentHash":"bc3302e4c419153a4318a44a59788b46c5f8a2f949f26487a82806ae55d85baf","addressRefs":[]},"036babd9-73fe-43a3-8293-b96a5f13e58e":{"id":"036babd9-73fe-43a3-8293-b96a5f13e58e","doc_no":"A.1.6.4.1.1.2","title":"Budget For Level 1 Ranked Delegates","type":"Core","depth":6,"parentId":"cf96f0e7-13e0-4a41-adb0-09a85b53495d","order":236,"content":"Each Level 1 Ranked Delegate is eligible for a budget of 400,000 USDS per year.","contentHash":"596ac713e0b778aef890e886f569f9c8d6ce779b107ea2ccf43bfc14c65f4ff6","addressRefs":[]},"f52e46d4-2d8c-49ad-852c-acbdca81aadc":{"id":"f52e46d4-2d8c-49ad-852c-acbdca81aadc","doc_no":"A.1.6.4.1.1.3","title":"Selection Of Level 1 Ranked Delegates","type":"Core","depth":6,"parentId":"cf96f0e7-13e0-4a41-adb0-09a85b53495d","order":237,"content":"In the short term, the Level 1 Ranked Delegates are selected directly by Sky Governance. The current Level 1 Ranked Delegates selected by Sky Governance are specified in [A.1.6.4.1.1.3.1 - Current Level 1 Ranked Delegates](46c0f334-4421-4e1a-9130-501e3a246e2a).","contentHash":"7f5e15363d250cc88ed538553238d018b07f76848fc74182f38766b53f480c35","addressRefs":[]},"46c0f334-4421-4e1a-9130-501e3a246e2a":{"id":"46c0f334-4421-4e1a-9130-501e3a246e2a","doc_no":"A.1.6.4.1.1.3.1","title":"Current Level 1 Ranked Delegates","type":"Core","depth":6,"parentId":"cf96f0e7-13e0-4a41-adb0-09a85b53495d","order":238,"content":"The current Level 1 Ranked Delegates are BLUE and Cloaky.","contentHash":"023997577b172e8465902a5c25b53edd43f1d5f863c263a86324ee7aab09bb75","addressRefs":[]},"2f07e41b-ca66-4075-90d0-771bcd8d7823":{"id":"2f07e41b-ca66-4075-90d0-771bcd8d7823","doc_no":"A.1.6.4.1.2","title":"Level 2 Ranked Delegates","type":"Core","depth":5,"parentId":"f4857d86-f4e7-43c5-be50-fab9e82f0129","order":239,"content":"Level 2 Ranked Delegates are eligible for an intermediate budget and are expected to contribute to the Sky Protocol at an intermediate level relative to other Ranked Delegates.","contentHash":"5a5d90cc3a7d7ceb90b62e510060dd3cbeda912448c0fc1b754402dc816a5e9f","addressRefs":[]},"dc65cc80-ea3d-41fa-a80c-b3aafa1e817e":{"id":"dc65cc80-ea3d-41fa-a80c-b3aafa1e817e","doc_no":"A.1.6.4.1.2.1","title":"Number Of Level 2 Ranked Delegates","type":"Core","depth":6,"parentId":"2f07e41b-ca66-4075-90d0-771bcd8d7823","order":240,"content":"There is one (1) Level 2 Ranked Delegate.","contentHash":"8467cf0f7fced0b76087b892c1b0c32de900bc48e739711e9ba6f063d9b2fb06","addressRefs":[]},"04b54378-1cb5-42cd-be16-e2b93386404d":{"id":"04b54378-1cb5-42cd-be16-e2b93386404d","doc_no":"A.1.6.4.1.2.2","title":"Budget For Level 2 Ranked Delegates","type":"Core","depth":6,"parentId":"2f07e41b-ca66-4075-90d0-771bcd8d7823","order":241,"content":"Each Level 2 Ranked Delegate is eligible for a budget of 175,000 USDS per year.","contentHash":"07dbe808ac0464b8dd2b1a79bf9d25dde839e055cb2c3f12edc97cbb3decb069","addressRefs":[]},"7c6c6579-7738-4835-9a80-d3bc799e84fd":{"id":"7c6c6579-7738-4835-9a80-d3bc799e84fd","doc_no":"A.1.6.4.1.2.3","title":"Selection Of Level 2 Ranked Delegates","type":"Core","depth":6,"parentId":"2f07e41b-ca66-4075-90d0-771bcd8d7823","order":242,"content":"In the short term, the Level 2 Ranked Delegates are selected directly by Sky Governance. The current Level 2 Ranked Delegates selected by Sky Governance are specified in [A.1.6.4.1.2.3.1 - Current Level 2 Ranked Delegates](ebe4da3b-2674-4ee1-b7a8-3d7a4b37fe75).","contentHash":"cbad34826990aa6be12b09782bc91e21b411f9851e5877b57040c3759862c038","addressRefs":[]},"ebe4da3b-2674-4ee1-b7a8-3d7a4b37fe75":{"id":"ebe4da3b-2674-4ee1-b7a8-3d7a4b37fe75","doc_no":"A.1.6.4.1.2.3.1","title":"Current Level 2 Ranked Delegates","type":"Core","depth":6,"parentId":"2f07e41b-ca66-4075-90d0-771bcd8d7823","order":243,"content":"The current Level 2 Ranked Delegate is Bonapublica.","contentHash":"4762b5f4fa44adee27fb3139d400528bd982271ad32f24a98cac751574647f8c","addressRefs":[]},"8b4d704c-4dcb-47c9-aadd-68255e61bb6a":{"id":"8b4d704c-4dcb-47c9-aadd-68255e61bb6a","doc_no":"A.1.6.4.1.3","title":"Level 3 Ranked Delegates","type":"Core","depth":5,"parentId":"f4857d86-f4e7-43c5-be50-fab9e82f0129","order":244,"content":"Level 3 Ranked Delegates are eligible for a lower budget and are expected to contribute to the Sky Protocol at a lower level relative to other Ranked Delegates.","contentHash":"887eb7191e04d75257debd07acc4aabcef8d196b5bd233a97533b98f4c409c87","addressRefs":[]},"8833de34-7904-4624-8396-9ee27a4743fc":{"id":"8833de34-7904-4624-8396-9ee27a4743fc","doc_no":"A.1.6.4.1.3.1","title":"Number Of Level 3 Ranked Delegates","type":"Core","depth":6,"parentId":"8b4d704c-4dcb-47c9-aadd-68255e61bb6a","order":245,"content":"There are three (3) Level 3 Ranked Delegates.","contentHash":"fa9eb858ae08acf630079d398782bf5e9b27cb7b0ab3095d172e49194881a64c","addressRefs":[]},"c51b75e1-8390-46c6-b455-3fd1b155af0d":{"id":"c51b75e1-8390-46c6-b455-3fd1b155af0d","doc_no":"A.1.6.4.1.3.2","title":"Budget For Level 3 Ranked Delegates","type":"Core","depth":6,"parentId":"8b4d704c-4dcb-47c9-aadd-68255e61bb6a","order":246,"content":"Each Level 3 Ranked Delegate is eligible for a budget of 48,000 USDS per year.","contentHash":"e8267d195c32d1e33a2bbace0336bc09386cf588e1f32875d54bd91fc83bad53","addressRefs":[]},"c3ad0b9f-970a-4495-9640-2553e77ea8ab":{"id":"c3ad0b9f-970a-4495-9640-2553e77ea8ab","doc_no":"A.1.6.4.1.3.3","title":"Selection Of Level 3 Ranked Delegates","type":"Core","depth":6,"parentId":"8b4d704c-4dcb-47c9-aadd-68255e61bb6a","order":247,"content":"The Level 3 Ranked Delegates are the Aligned Delegates with the greatest delegated Voting Power who are not Level 1 Ranked Delegates or Level 2 Ranked Delegates.","contentHash":"b165d3fa70045dac9ec1ae0c84dc4ecf4ffc82f313ef76d8bc03597f57a94358","addressRefs":[]},"8012ae3b-bcd7-4fdc-a93c-8c33d770a7ca":{"id":"8012ae3b-bcd7-4fdc-a93c-8c33d770a7ca","doc_no":"A.1.6.4.1.3.3.0.3.1","title":"Delegated Voting Power - Element Annotation","type":"Annotation","depth":6,"parentId":"8b4d704c-4dcb-47c9-aadd-68255e61bb6a","order":248,"content":"The element \"delegated Voting Power\" refers to the cumulative SKY that has been delegated to an Aligned Delegate's Delegate Contract by SKY holders and Staking users.","contentHash":"a8005463bcc4ad125cfb631edb61a8e2099b464a9878ce60b4e39ea3961c6ab3","addressRefs":[]},"e16ac70b-5c9c-4a45-8bae-852be2b5b5e0":{"id":"e16ac70b-5c9c-4a45-8bae-852be2b5b5e0","doc_no":"A.1.6.4.2","title":"Budget Accrual","type":"Core","depth":4,"parentId":"0836acf0-441d-4215-aee6-dc6d0c884516","order":249,"content":"The budget for Ranked Delegates accrues on a continuous basis.","contentHash":"36b36ad2cec20323cb700ed65a3c3eadc4e859ea916de8deb9a5c7fb31402500","addressRefs":[]},"82f74f4b-8c49-4b1e-9ae7-f6c5e23d3394":{"id":"82f74f4b-8c49-4b1e-9ae7-f6c5e23d3394","doc_no":"A.1.6.4.3","title":"Budget Contingency","type":"Core","depth":4,"parentId":"0836acf0-441d-4215-aee6-dc6d0c884516","order":250,"content":"A Ranked Delegate's allocated budget can be reduced if they do not fully comply with the participation requirements defined in this Article at [A.1.6.4.3.1 - Voting-Activity Metrics](ad1ef0f4-246f-4289-b5fc-ea5c91508ccf), [A.1.6.4.3.2 - Voting-Communication Metrics](f020d1bc-8905-46f8-b3a5-c31bcc0eec79), and [A.1.6.4.3.3 - Emergency Communications Requirement](43db9780-6c0a-458a-94c2-5951b5b80787).","contentHash":"3a4d60923d5260e08f9b2e6359f6a4a3b132eb2458e1545a4f12f5755d6b2831","addressRefs":[]},"ad1ef0f4-246f-4289-b5fc-ea5c91508ccf":{"id":"ad1ef0f4-246f-4289-b5fc-ea5c91508ccf","doc_no":"A.1.6.4.3.1","title":"Voting-Activity Metrics","type":"Core","depth":5,"parentId":"82f74f4b-8c49-4b1e-9ae7-f6c5e23d3394","order":251,"content":"The budget allocated to a Ranked Delegate (RD) is modified based on their voting-activity metrics over the past six (6) months. This budget modification takes into account the overall participation of the Ranked Delegate in all votes they are eligible to cast as an Aligned Delegate (AD).\n\nIf an RD participates in less than 95% of all eligible votes within the last six (6) months, their RD budget is reduced. The reduction is applied on a proportional linear scale: for every percentage point below 95% voting activity, the RD's budget is reduced correspondingly.\n\nShould an RD's voting activity fall to 75% of all eligible votes within the last six (6) months, they become completely ineligible to receive RD income. If the RD is a Level 3 Ranked Delegate, their RD rank, and the budget eligibility associated with that rank, is transferred to the next highest-ranking AD, as determined by total amount of SKY delegated to their Delegate Contract.","contentHash":"0d8d7f52011610695fb02bf75cf1388e73dda1ef21173253fe0483ba6ee3745d","addressRefs":[]},"57a0be8f-c0d8-4d0c-bb99-ca3e63da5058":{"id":"57a0be8f-c0d8-4d0c-bb99-ca3e63da5058","doc_no":"A.1.6.4.3.1.0.3.1","title":"Proportional Linear Scale - Element Annotation","type":"Annotation","depth":6,"parentId":"ad1ef0f4-246f-4289-b5fc-ea5c91508ccf","order":252,"content":"The element \"proportional linear scale\" describes a method where the budget reduction is directly proportional to the decline in voting activity between 95% and 75%. Here, the pertinent range of voting activity spans from 95% to 75%, which is 20 percentage points. The budget decreases linearly across these 20 percentage points. In other words, the RD budget decreases by **5%** for every percentage point drop in voting activity from 95% to 75% (since 100% divided by 20 percentage points = 5% per point).","contentHash":"089a9fa9c3c01279264e6b33f0679c73750d1599f2abe81aeb35b3c97626ec64","addressRefs":[]},"f020d1bc-8905-46f8-b3a5-c31bcc0eec79":{"id":"f020d1bc-8905-46f8-b3a5-c31bcc0eec79","doc_no":"A.1.6.4.3.2","title":"Voting-Communication Metrics","type":"Core","depth":5,"parentId":"82f74f4b-8c49-4b1e-9ae7-f6c5e23d3394","order":253,"content":"The budget allocated to a Ranked Delegate (RD) is modified based on their voting-communication metrics over the past six (6) months. An AD is required to provide an explanation for each vote they participate in. This budget modification takes into account the Ranked Delegate’s fulfillment of this voting-communication requirement in all votes they are eligible to cast as an Aligned Delegate (AD).\n\nIf an RD provides the required voting-communication on less than 95% of all eligible votes within the last six (6) months, their RD budget stream is reduced. The reduction is applied on a proportional linear scale: for every percentage point below 95% voting-communication activity, the RD's budget is reduced correspondingly.\n\nShould an RD's voting-communication activity fall to 75% of all eligible votes within the last six (6) months, they become completely ineligible to receive RD income. If the RD is a Level 3 Ranked Delegate, their RD rank, and the budget eligibility associated with that rank, is transferred to the next highest-ranking AD, as determined by total amount of SKY delegated to their Delegate Contract.","contentHash":"10a85f2ab9c80fe09d47c21ce179db52858c817f05b8d7437f64e82c994b0ae6","addressRefs":[]},"ea34cf2b-b756-4c55-b317-7e4802b6f9b3":{"id":"ea34cf2b-b756-4c55-b317-7e4802b6f9b3","doc_no":"NR-12","title":"Criteria For AD Voting-Communication Requirement","type":"Needed Research","depth":6,"parentId":"f020d1bc-8905-46f8-b3a5-c31bcc0eec79","order":254,"content":"**Content**:\n\nFor the purpose of enforcing the Target Document, should there be explicit criteria for Aligned Delegates' voting-communications? What constitutes an adequate explanation for each vote? How would the Core Facilitator evaluate ADs' explanations for quality, completeness, etc.? How can the Core Facilitator objectively assess explanations that may vary widely in style and content?\n\nHow might ADs' explanations vary across different types of votes, and should the criteria reflect these differences? Should more complex or high-stakes votes require more detailed explanations than routine or procedural votes?\n\nWhat feedback mechanisms should be in place to help ADs improve their explanations?\n\nWhat are the risks of not having explicit criteria for voting-communications? One is the potential failure of the Target Document's objective to ensure that ADs' voting activity is transparent to SKY holders who have delegated to that AD.","contentHash":"0fc4784b751c9b989b688cd1c00e2c893a85c88dcdf133ccc0cfaf53f6cd306c","addressRefs":[]},"57c35484-4c5f-4349-a7fe-097618b4213a":{"id":"57c35484-4c5f-4349-a7fe-097618b4213a","doc_no":"A.1.6.4.3.2.0.3.1","title":"Proportional Linear Scale - Element Annotation","type":"Annotation","depth":6,"parentId":"f020d1bc-8905-46f8-b3a5-c31bcc0eec79","order":255,"content":"The element \"proportional linear scale\" describes a method where the budget reduction is directly proportional to the decline in voting-communication activity between 95% and 75%. Here, the pertinent range of voting-communication activity spans from 95% to 75%, which is 20 percentage points. The budget decreases linearly across these 20 percentage points. In other words, the RD budget decreases by **5%** for every percentage point drop in voting-communication activity from 95% to 75% (since 100% divided by 20 percentage points = 5% per point).","contentHash":"c0e9fe2b2e20689cdbb32a8c64c6df006bfbd51c95eb730558f146db42331d59","addressRefs":[]},"ca88baad-2457-4454-9e34-367156a59e78":{"id":"ca88baad-2457-4454-9e34-367156a59e78","doc_no":"A.1.6.4.3.2.0.3.2","title":"Voting-Communication Metrics - Element Annotation","type":"Annotation","depth":6,"parentId":"f020d1bc-8905-46f8-b3a5-c31bcc0eec79","order":256,"content":"The element \"voting-communication metrics\" refers to the percentage of votes for which an Aligned Delegate provides the required written explanations or justifications of their casted votes in Governance Polls and Executive Votes. These written explanations are posted in the AD's Forum thread.\n\nThe Target Document’s function is to ensure that SKY holders delegating to the AD have full transparency to understand the AD's decision-making process.","contentHash":"536cd504579d9f7db506d3374085d9fb1dc4e7c206120bf35d27ac29083e6a2e","addressRefs":[]},"43db9780-6c0a-458a-94c2-5951b5b80787":{"id":"43db9780-6c0a-458a-94c2-5951b5b80787","doc_no":"A.1.6.4.3.3","title":"Emergency Communications Requirement","type":"Core","depth":5,"parentId":"82f74f4b-8c49-4b1e-9ae7-f6c5e23d3394","order":257,"content":"The budget stream allocated to a Ranked Delegate (RD) is modified based on their correct usage of required tools for emergency communications.\n\nShould an RD fail to correctly use the required communications tools, they become completely ineligible to receive RD income. If the RD is a Level 3 Ranked Delegate, their RD rank, and the budget eligibility associated with that rank, is transferred to the next highest-ranking AD, as determined by total amount of SKY delegated to their Delegate Contract.","contentHash":"c4009a3c95914d9aa5ce2ebbc6e14daca59413b5e740485289640801a81aef35","addressRefs":[]},"21d0b626-cd84-4237-8cab-d68f697c276d":{"id":"21d0b626-cd84-4237-8cab-d68f697c276d","doc_no":"A.1.6.4.3.3.1","title":"Signal Account Requirement","type":"Core","depth":6,"parentId":"43db9780-6c0a-458a-94c2-5951b5b80787","order":258,"content":"RDs are required to maintain an active Signal account to facilitate communications related to emergency / urgent situations. This requirement applies regardless of whether an RD has been appointed to the Emergency Response Group. See [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf). RDs must provide their Signal username to the Core Facilitator.\n\nThe Core Facilitator is responsible for maintaining an internal registry of RDs' Signal accounts. Because the ranked RDs are continually changing, the Core Facilitator must ensure that the internal registry is maintained on a frequent basis. The Core Facilitator must check the active status of the RDs' Signal accounts by sending test messages and confirming the RDs' timely response; this must be done regularly, on a schedule known only to the Core Facilitator. If an RD fails to timely respond to the test messages, the Core Facilitator must remove them from RD status.","contentHash":"070e3b086a4da317e3774c4c0bbbe9c07acc1562e4b7c24dc88faa9ae5b13c93","addressRefs":[]},"0625cdd6-f089-47ab-ad3e-209e14064951":{"id":"0625cdd6-f089-47ab-ad3e-209e14064951","doc_no":"A.1.6.4.4","title":"AD Buffer","type":"Core","depth":4,"parentId":"0836acf0-441d-4215-aee6-dc6d0c884516","order":259,"content":"The AD Buffer is an account of USDS that begins accumulating funds when an Aligned Delegate attains Ranked Delegate status. The budget allocated to the AD is credited to the AD Buffer. Funds within the AD Buffer cannot be accessed or spent until they reach a minimum threshold equivalent to one (1) month's budget allocation based on the current level of the Ranked Delegate.\n\nOnce this threshold is met, the AD will receive payouts from the AD Buffer to the address that controls the AD Delegate Contract. ADs may use this budget for various purposes, including personal compensation, compensation for team members, research expenses, and other relevant activities.","contentHash":"c020949dfe591a2b7c7c9bc6aff260490f52186040cc5e206982f1ff8299a2b9","addressRefs":[]},"688247c6-c4ed-49e3-96f3-c6a7475d89eb":{"id":"688247c6-c4ed-49e3-96f3-c6a7475d89eb","doc_no":"A.1.6.4.4.1","title":"AD Monthly Compensation Cycle","type":"Core","depth":5,"parentId":"0625cdd6-f089-47ab-ad3e-209e14064951","order":260,"content":"Aligned Delegates are eligible to receive payments from their AD Buffers in a monthly compensation cycle. The Core Facilitator is responsible for calculating the payout due to each Aligned Delegate.\n\nThis includes calculating:\n\n1. the Aligned Delegates ranked as Level 3 Ranked Delegates on a daily basis;\n2. the budget to be deposited into each Aligned Delegate's AD Buffer, which is modified pursuant to voting and communication metrics;\n3. the balance of each Delegate's AD Buffer; and\n4. the amount to be paid out to each Aligned Delegate.\n\nOnce calculated by the Core Facilitator, AD payouts are paid from the Aligned Delegates Buffer Multisig. See [A.2.3.1.2.2.2.2 - Aligned Delegates Buffer](05fa5c41-26ca-4c25-94dd-834ef72c318a).","contentHash":"fc535fafb9efa3be73bb718b283ff7fd3e53cca6c0e427faf89fd0e4856f9158","addressRefs":[]},"6502ce76-3f29-4f50-a68c-9126feba1fb6":{"id":"6502ce76-3f29-4f50-a68c-9126feba1fb6","doc_no":"NR-10","title":"AD Budget Management","type":"Needed Research","depth":6,"parentId":"688247c6-c4ed-49e3-96f3-c6a7475d89eb","order":261,"content":"**Content**:\n\nAre there risks that should be considered regarding the potential mismanagement or misuse of the AD budget? The Target Document lists several examples of permissible ways to use the AD budget, which indicates implicitly constraints, or disallowed expenditures. How would compliance with these guidelines be monitored?","contentHash":"1fb35ef3f6617dd031632619bce2933dd2b49ba2c1d88990433a39c408da1afe","addressRefs":[]},"48a2c0f5-5f09-44d3-a930-47e6c12fb901":{"id":"48a2c0f5-5f09-44d3-a930-47e6c12fb901","doc_no":"A.1.6.4.4.1.0.3.1","title":"One Month's Budget Allocation - Element Annotation","type":"Annotation","depth":6,"parentId":"688247c6-c4ed-49e3-96f3-c6a7475d89eb","order":262,"content":"To arrive at the value of this one-month budget threshold in USDS, see [A.1.6.4.1 - Levels Of Ranked Delegates](f4857d86-f4e7-43c5-be50-fab9e82f0129).","contentHash":"96bd8a20f99e7eb542444ace6455c7442bd6e8784fb3b54eeb3a6cdfbf90b932","addressRefs":[]},"add0e307-9fbb-4871-9eab-c7bd18662e01":{"id":"add0e307-9fbb-4871-9eab-c7bd18662e01","doc_no":"A.1.6.4.4.2","title":"AD Buffer And Loss Of Budget","type":"Core","depth":5,"parentId":"0625cdd6-f089-47ab-ad3e-209e14064951","order":263,"content":"If an AD is unranked for an entire month, any contents in its AD Buffer can be paid out in the next monthly compensation cycle, except as specified in [A.1.6.4.4.2.1 - Payout Limitations For ADs Triggering Atlas Edit Proposals](8eca5ff8-8798-465b-b86a-f9ee5c93f213).","contentHash":"d09cc02a87f0a4e02c0a4791eaa94bc432ed423e9aee1999e9b3d7a0e8e62d41","addressRefs":[]},"8eca5ff8-8798-465b-b86a-f9ee5c93f213":{"id":"8eca5ff8-8798-465b-b86a-f9ee5c93f213","doc_no":"A.1.6.4.4.2.1","title":"Payout Limitations For ADs Triggering Atlas Edit Proposals","type":"Core","depth":6,"parentId":"add0e307-9fbb-4871-9eab-c7bd18662e01","order":264,"content":"If an AD has triggered an Atlas Edit Weekly Cycle Proposal or Atlas Edit Monthly Cycle Proposal pursuant to [A.1.11.2.1.3 - Triggering Requirement](cef09d74-efc6-45cc-a75b-1132dae9e743), or [A.1.12.2.1.2 - Triggering Requirement](7bbfd3b1-99b5-4c60-9292-68d776e03886), respectively, no payouts may be made that would reduce their AD Buffer below the Triggering Threshold specified in [A.1.6.4.4.2.1.1 - Triggering Threshold](2c2b201e-b95f-4852-8e76-6dfe4c3c6a4f) until the Proposal has been voted on or rejected by the Core Facilitator for misalignment.","contentHash":"1a5551c937eed8b78089eb9a258feb00038e9194e42ae7c1e75ec83048882566","addressRefs":[]},"2c2b201e-b95f-4852-8e76-6dfe4c3c6a4f":{"id":"2c2b201e-b95f-4852-8e76-6dfe4c3c6a4f","doc_no":"A.1.6.4.4.2.1.1","title":"Triggering Threshold","type":"Core","depth":6,"parentId":"add0e307-9fbb-4871-9eab-c7bd18662e01","order":265,"content":"The Triggering Threshold is the amount of USDS that a Ranked Delegate must have in its AD Buffer to trigger Atlas Edit Weekly Cycle or Atlas Edit Monthly Cycle Proposals. See [A.1.11.2.1.3 - Triggering Requirement](cef09d74-efc6-45cc-a75b-1132dae9e743) and [A.1.12.2.1.2 - Triggering Requirement](7bbfd3b1-99b5-4c60-9292-68d776e03886). The Triggering Threshold is equal to one (1) month of compensation based on the budget for Level 3 Ranked Delegates specified in [A.1.6.4.1.3.2 - Budget For Level 3 Ranked Delegates](c51b75e1-8390-46c6-b455-3fd1b155af0d).","contentHash":"d7a315747180b3debb5543f41d1c36dbd9b1dd65b429307ac77a43b27765c240","addressRefs":[]},"5de71fff-67b1-410f-9479-82b6b735a85b":{"id":"5de71fff-67b1-410f-9479-82b6b735a85b","doc_no":"A.1.6.4.4.2.1.1.0.3.1","title":"One Month's Budget Allocation - Element Annotation","type":"Annotation","depth":6,"parentId":"add0e307-9fbb-4871-9eab-c7bd18662e01","order":266,"content":"See [A.1.6.4.4.1.0.3.1 - One Month’s Budget Allocation - Element Annotation](48a2c0f5-5f09-44d3-a930-47e6c12fb901).","contentHash":"0f28b41dfe04a20491edb159b3ba50d64e3349d3fea21c34aae1ff5386a0907e","addressRefs":[]},"4a29dd32-2333-471a-bea1-1aa0f5413453":{"id":"4a29dd32-2333-471a-bea1-1aa0f5413453","doc_no":"A.1.6.4.4.3","title":"Deduction Of Penalties From AD Buffer","type":"Core","depth":5,"parentId":"0625cdd6-f089-47ab-ad3e-209e14064951","order":267,"content":"If the Core Facilitator finds that an AD has conducted a misaligned act warranting financial penalties or derecognition, such penalties may be deducted from the AD’s Buffer.","contentHash":"da09bd51721d744b769c7eead35658c01ac0fbf58885d80fb12bc753af92334d","addressRefs":[]},"5417359f-b6eb-4747-8fc7-3b2659e67a7f":{"id":"5417359f-b6eb-4747-8fc7-3b2659e67a7f","doc_no":"A.1.6.4.5","title":"Ranked Delegate Voting Communication Review Responsibility","type":"Core","depth":4,"parentId":"0836acf0-441d-4215-aee6-dc6d0c884516","order":268,"content":"Level 1 and Level 2 Ranked Delegates are responsible for monitoring Aligned Delegate compliance with communication responsibilities (see [A.1.6.2.2 - Aligned Delegate Communication Responsibilities](3a8c2b92-3a23-48a0-87c4-ea1325bbbd98) as a condition of their compensated position.\n\nMonitoring reports are submitted via private communication to the Core Facilitator. When one Ranked Delegate flags a potential noncompliance issue, the Core Facilitator may prompt all Level 1 and Level 2 Ranked Delegates to submit individual assessments via private communication. Each Ranked Delegate must submit their assessment when prompted. The Core Facilitator may also select specific vote explanations and prompt all Level 1 and Level 2 Ranked Delegates to submit compliance assessments, regardless of whether a Ranked Delegate has independently flagged the explanation.\n\nFailure by a Level 1 or Level 2 Ranked Delegate to submit an assessment when prompted by the Core Facilitator is a Tier 1 (Procedural) breach as defined in [A.1.6.6.1 - Graduated Response Framework](2544a530-42f8-4699-b428-7c3568e1635e).","contentHash":"5e7c8ab41681854ce71148d8a3ef12886ad4f22af4e0eac40701af2f238fce0e","addressRefs":[]},"45e794a0-5092-4dea-a0de-6f373228f760":{"id":"45e794a0-5092-4dea-a0de-6f373228f760","doc_no":"A.1.6.5","title":"Kickbacks Prohibited","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":269,"content":"Aligned Delegates are not allowed to provide \"kickbacks\" from their compensation to SKY holders who delegate to them. Violation of this requirement constitutes misalignment.","contentHash":"74f9a5452f96499a6b9b0934443a8cfc6f40c9c652a3432c0a5f640cefb896da","addressRefs":[]},"8953d5dc-1344-4fec-ae25-693204f64e38":{"id":"8953d5dc-1344-4fec-ae25-693204f64e38","doc_no":"A.1.6.6","title":"Swift Action Is Required From Facilitators To Redress AD Misalignment","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":270,"content":"The Facilitator must act swiftly when an AD is suspected of breaching the requirements defined in this Article, or the requirements defined in [A.1.5 - Alignment Conservers](df4f9bfd-e743-44b5-9c62-9c5f10b15340).\n\nAny Facilitator has the authority to formally raise an allegation of AD misalignment with the Core Facilitator, which then obligates the latter to initiate a formal adjudication pursuant to [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57).\n\nA Facilitator's failure to act promptly in addressing credible evidence of AD misalignment or to mitigate the risk of misalignment spreading among ADs is considered an act of misalignment itself. Formal allegations of such failure must be adjudicated by the Core Facilitator pursuant to the same process referenced in the above-cited document.","contentHash":"6465bb3f46073e1b085d17035738d0c44cc4bf07bf0496fd06e85eb6387755b3","addressRefs":[]},"2544a530-42f8-4699-b428-7c3568e1635e":{"id":"2544a530-42f8-4699-b428-7c3568e1635e","doc_no":"A.1.6.6.1","title":"Graduated Response Framework","type":"Core","depth":4,"parentId":"8953d5dc-1344-4fec-ae25-693204f64e38","order":271,"content":"Breaches of Aligned Delegate requirements are categorized into two (2) tiers based on severity. The appropriate response is determined by the tier of the breach and the Aligned Delegate’s prior record.","contentHash":"3909645928cbf9ca0febf9cb9305172d3317db331dc4a5562488d6ef2d917414","addressRefs":[]},"ec29c919-2294-45b3-a2cd-e48dd9422539":{"id":"ec29c919-2294-45b3-a2cd-e48dd9422539","doc_no":"A.1.6.6.1.1","title":"Tier 1 (Procedural) Breaches","type":"Core","depth":5,"parentId":"2544a530-42f8-4699-b428-7c3568e1635e","order":272,"content":"Tier 1 breaches are procedural in nature and include late vote explanations, minor communication lapses, and similar administrative failures that do not reflect on the Aligned Delegate’s integrity or judgment.\n\nFor a first Tier 1 breach, the Core Facilitator issues a public notice to the Aligned Delegate on the Forum thread where the Aligned Delegate submitted their AD Recognition Submission Message (see [A.1.6.1.3.2 - Submission Message](83289ee2-2685-4ef7-99f1-c064541c9e9f)). The notice must specify the breach and the expected correction.\n\nA Tier 1 notice expires 12 months after issuance. A subsequent Tier 1 breach while two or more Tier 1 notices remain active is considered a Tier 2 breach.","contentHash":"77cd7227f22fb5e4a91e5f8f76b62cb81429965a39dfb77c11b16b6e515cccb0","addressRefs":[]},"a95e4ab0-575e-427c-ac6a-251f8e376b75":{"id":"a95e4ab0-575e-427c-ac6a-251f8e376b75","doc_no":"A.1.6.6.1.2","title":"Tier 2 (Integrity) Breaches","type":"Core","depth":5,"parentId":"2544a530-42f8-4699-b428-7c3568e1635e","order":273,"content":"Tier 2 breaches involve fundamental failures of integrity that are incompatible with the Aligned Delegate role. Tier 2 breaches include:\n\n1. Unsubstantiated public accusations against governance participants and inflammatory language directed at governance participants or processes that does not constitute good-faith criticism;\n2. Proven dishonesty in governance communications;\n3. Collusion or coordination intended to manipulate governance outcomes;\n4. Acceptance of undisclosed compensation (kickbacks) for governance actions;\n5. Operational security violations that compromise governance security (see [A.1.6.7 - Mandate To Maintain High Level of Operational Security](c68b4c5d-adf7-49e6-850a-17a688664d40));\n6. Voting against an Executive Vote that only contains content already approved in the Atlas and does not fail Spell validation; and\n7. Estoppel violations as defined in [A.1.6.6.2 - Voting Estoppel Rule](c1a5d22a-c30c-4445-80eb-caf3bd908d28).\n\nA Tier 2 breach results in immediate derecognition regardless of the Aligned Delegate's prior record.","contentHash":"514960b415421c73e0ac442702d45fb0c88012db95e83acf78f78e7fd00e98d4","addressRefs":[]},"3cd0735f-c1e5-4592-8878-674bbcc9d7ac":{"id":"3cd0735f-c1e5-4592-8878-674bbcc9d7ac","doc_no":"A.1.6.6.1.2.0.3.1","title":"Good-Faith Criticism - Element Annotation","type":"Annotation","depth":6,"parentId":"a95e4ab0-575e-427c-ac6a-251f8e376b75","order":274,"content":"The element \"good-faith criticism\" refers to criticism that (a) is framed in neutral or professional terms, (b) includes supporting facts or is clearly identified as opinion, and (c) does not constitute a personal attack. Good-faith criticism of governance decisions, processes, or participants is not a Tier 2 breach. This safe harbor protects legitimate governance discourse including dissent, whistleblowing, and strong disagreement.","contentHash":"dccd399acf87e7478a7b93220c8c96b06f5e0f1df47132fb7cf06f439f472a07","addressRefs":[]},"32862df8-a277-48a3-bb0f-40ed1e051dfd":{"id":"32862df8-a277-48a3-bb0f-40ed1e051dfd","doc_no":"A.1.6.6.1.3","title":"Aligned Delegate Breach Record","type":"Active Data Controller","depth":5,"parentId":"2544a530-42f8-4699-b428-7c3568e1635e","order":275,"content":"Notices and warnings issued under the Graduated Response Framework are recorded by adding an entry to the Active Data list in [A.1.6.6.1.3.0.6.1 - Aligned Delegate Breach Registry](1ddd9cf6-3f93-4a33-8c1d-80405eec1ffb).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Facilitator.\n- The Update Process must follow the protocol for 'Alignment Conserver Changes'.","contentHash":"f08393451ac524ba05cb419c43b5b5b3c8d34a685a3e6cdb2e61f4497be46793","addressRefs":[]},"1ddd9cf6-3f93-4a33-8c1d-80405eec1ffb":{"id":"1ddd9cf6-3f93-4a33-8c1d-80405eec1ffb","doc_no":"A.1.6.6.1.3.0.6.1","title":"Aligned Delegate Breach Registry","type":"Active Data","depth":6,"parentId":"32862df8-a277-48a3-bb0f-40ed1e051dfd","order":276,"content":"Breaches of the Graduated Response Framework are recorded herein.\n\n| Date       | Identity        | Breach Tier | Reasoning Post |\n|------------|-----------------|-------------|----------------|\n| 2026-05-08 | Kuzmich         | 1           | [Core Facilitator Post](https://forum.skyeco.com/t/ad-recognition-submission/26743/50) | \n| 2026-05-15 | Kuzmich         | 1           | [Core Facilitator Post](https://forum.skyeco.com/t/ad-recognition-submission/26743/51) |\n| 2026-05-15 | MaxStakingYield | 1           | [Core Facilitator Post](https://forum.skyeco.com/t/max-staking-yield-ad-recognition-submission/26462/80) |","contentHash":"c65ea408ff313d43f65e54eea7ebe7ee78f36951b6439f8335e22d5ef7757419","addressRefs":[]},"c1a5d22a-c30c-4445-80eb-caf3bd908d28":{"id":"c1a5d22a-c30c-4445-80eb-caf3bd908d28","doc_no":"A.1.6.6.2","title":"Voting Estoppel Rule","type":"Core","depth":4,"parentId":"8953d5dc-1344-4fec-ae25-693204f64e38","order":277,"content":"An Aligned Delegate who votes in favor of a proposal is deemed to have read and understood the key governance implications of that proposal at the time of voting. This creates a bright-line test: the act of voting in favor constitutes affirmative acknowledgment of the proposal’s contents and consequences.\n\nClaims of ignorance, misunderstanding, or failure to read proposal text shall not be accepted as defenses in any subsequent governance proceeding for votes cast in favor. An Aligned Delegate who later claims they did not understand what they voted for commits a Tier 2 breach under the Graduated Response Framework. See [A.1.6.6.1 - Graduated Response Framework](2544a530-42f8-4699-b428-7c3568e1635e).\n\nThis rule applies only to votes cast in favor. Aligned Delegates who vote against or abstain retain the ability to raise concerns about proposal clarity or their understanding of its implications.\n\nThe estoppel rule does not apply where the proposal text was materially misleading at the time of voting, or where critical facts bearing on the proposal’s governance implications emerged after the vote concluded. The burden of establishing that the proposal text was misleading or that newly discovered facts are material rests with the Aligned Delegate.","contentHash":"95f59a46553ab04f2daed6b22133be07121a9a9e7a3a7b58cf96051734588127","addressRefs":[]},"3a9d0848-e034-4d6b-8c4f-3d18e92edb71":{"id":"3a9d0848-e034-4d6b-8c4f-3d18e92edb71","doc_no":"A.1.6.6.0.3.1","title":"Act Swiftly - Element Annotation","type":"Annotation","depth":4,"parentId":"8953d5dc-1344-4fec-ae25-693204f64e38","order":278,"content":"The element \"act swiftly\" does not preclude reasonable delay where the Facilitator requires additional time to gather evidence, consult with the accused party, or seek guidance from Core GovOps. The Facilitator should document the basis for any such delay.","contentHash":"d5c15fdf0cd6e9cfed89889ba40e9a8809f42746865217f9efa312c6dd151c14","addressRefs":[]},"578ff359-eff1-406e-8cb9-5f4807598c10":{"id":"578ff359-eff1-406e-8cb9-5f4807598c10","doc_no":"A.1.6.6.0.3.2","title":"Credible Evidence - Element Annotation","type":"Annotation","depth":4,"parentId":"8953d5dc-1344-4fec-ae25-693204f64e38","order":279,"content":"The element \"credible evidence\" refers to the evidentiary threshold required for a formal allegation to proceed to adjudication. A formal allegation is supported by credible evidence where it identifies (a) the specific requirement or standard alleged to have been breached, (b) the factual basis for the allegation, and (c) any supporting evidence. Where an allegation fails to meet this threshold, the Core Facilitator may decline to initiate adjudication, provided the basis for declining is documented.","contentHash":"7973531fe1017d9e1492b57fdebe0a8813a19d8a1b545f6be58b23629c886d90","addressRefs":[]},"c5146fa6-00ec-4543-9288-410570b5d588":{"id":"c5146fa6-00ec-4543-9288-410570b5d588","doc_no":"A.1.6.6.0.4.1","title":"Facilitators’ Authority To Raise Formal Allegation","type":"Action Tenet","depth":4,"parentId":"8953d5dc-1344-4fec-ae25-693204f64e38","order":280,"content":"Any community member or Aligned Delegate with information pertinent to suspected Alignment Conserver misalignment may take their concerns directly to the Core Facilitator.  Upon receiving such information, the Core Facilitator must promptly conduct an initial review to quickly assess the credibility of the concern. Based on this preliminary review, the Core Facilitator must decide whether to initiate a formal adjudication process in accordance with [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57).\n\nWhere the allegation of misalignment concerns the Core Facilitator, a community member can take their concerns to Core GovOps, who is then empowered to initiate the formal adjudication process.","contentHash":"9872542e0bb1268ee48ff7ae78e17ea6f0f91a377299b8629b6f21c9b2f7136f","addressRefs":[]},"c68b4c5d-adf7-49e6-850a-17a688664d40":{"id":"c68b4c5d-adf7-49e6-850a-17a688664d40","doc_no":"A.1.6.7","title":"Mandate To Maintain High Level of Operational Security","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":281,"content":"Aligned Delegates (ADs) are required to maintain a high level of operational security, adhering to best practices in privacy, cybersecurity, and physical resilience. These measures must be implemented at a level that sufficiently safeguards the Sky Ecosystem from physical risk posed by the potential for attacks against ADs. ADs’ operational security protocols should be regularly reviewed and updated to address emerging risks and ensure continuous protection of the ecosystem.","contentHash":"b627b1f6938f4d0a05bf7d064bc6713a4ad246468e38890f860f7233c012eaf0","addressRefs":[]},"7b0da718-62c1-4718-8d9d-47faa1647c6f":{"id":"7b0da718-62c1-4718-8d9d-47faa1647c6f","doc_no":"A.1.6.8","title":"Derecognition Required Where AD Operational Security Is Compromised","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":282,"content":"All Facilitators must act swiftly to investigate ADs who are suspected of breaching their requirements regarding operational security and privacy.\n\nThe Core Facilitator must initiate a formal adjudication pursuant to [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57) where there is an allegation concerning AD breach of operational security.\n\nIf there is clear evidence or significant suspicion that the operational security of an AD has been compromised, or that they have failed to follow best practice or otherwise made operational security errors, the Core Facilitator must promptly derecognize the AD.","contentHash":"7a6615ed66caaad7af34e9f8dda5c755a521ea7e3d4b983b51f94d2b9753ee85","addressRefs":[]},"36e7c024-0156-4941-a9f2-f53ce25ef39f":{"id":"36e7c024-0156-4941-a9f2-f53ce25ef39f","doc_no":"A.1.6.8.0.4.1","title":"Promptly Derecognized - Mandated Timeline For AD Derecognition For Operational Security Breach","type":"Action Tenet","depth":4,"parentId":"7b0da718-62c1-4718-8d9d-47faa1647c6f","order":283,"content":"The element 'promptly' in the Target Document means 'as soon as is reasonably possible.'\n\nTo adhere to this commitment, the Core Facilitator must derecognize the AD within a general timeframe of 1-2 calendar days upon conclusion of an investigation that finds against the AD for breach of operational security. Failure to meet this deadline requires a showing of good cause, demonstrating extenuating circumstances beyond the Facilitators’ control.","contentHash":"347fecad5dc44d611d5d927d8ff482f0380566b05ec1301433068a85daffa945","addressRefs":[]},"09efe31d-28ae-47cc-a81e-caf4f669df95":{"id":"09efe31d-28ae-47cc-a81e-caf4f669df95","doc_no":"A.1.6.9","title":"Facilitators Must Err On Side Of Caution","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":284,"content":"Facilitators are required to err on the side of caution and take action whenever there is any real possibility that the operational security of an Aligned Delegate (AD) is compromised. Facilitators are afforded significant discretion in making judgement calls related to operational security standards for ADs.\n\nAbuse of this power is severe misalignment. Any allegations of this abuse of power must be adjudicated by the Core Facilitator pursuant to the process defined in [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57).","contentHash":"0b7d98f965de2f9ff1b1ec9a6ee22974a8ffa0ec50f6782a3af85cee47e2caa5","addressRefs":[]},"d5d4cc4a-8877-4931-861f-056793387b92":{"id":"d5d4cc4a-8877-4931-861f-056793387b92","doc_no":"A.1.6.10","title":"Emergency Contact Mechanism","type":"Section","depth":3,"parentId":"75f0063c-ad70-49e4-b356-9b76097ced7b","order":285,"content":"Aligned Delegates must safeguard the security of the Sky Protocol through the Executive Vote process. To deal with emergencies related to Executive Votes, ADs are required to sign up for the approved emergency contact mechanism specified in [A.1.9.1.3.2.2 - Approved Emergency Contact Mechanisms](57006d4e-cd91-4565-97b5-5fab73fa94d5).\n\nADs must strictly adhere to all onboarding procedures and usage instructions associated with this emergency contact mechanism. ADs that fail to do so will be considered in misalignment and will be derecognized.\n\nThe high operational security requirements applicable to ADs extend to their use of the emergency contact mechanism.","contentHash":"f8fb7e0257b00bbf94237ef6eca4a2e3ea345498af7f7b704a750bbf9f8d6e20","addressRefs":[]},"1ce24b08-84ff-4524-9710-49bba429c6ef":{"id":"1ce24b08-84ff-4524-9710-49bba429c6ef","doc_no":"A.1.7","title":"Facilitators","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":286,"content":"A type of Alignment Conserver, Facilitators are contracted by Executor Agents to interpret the Atlas and Artifacts on their behalf. This Article defines key infrastructure and requirements concerning Facilitators.","contentHash":"6479be6774c627ccdd7bd817471b54ef5b9ec72b91c3f4a760f7e6bc5218aedf","addressRefs":[]},"4354cb31-d2e3-433d-bbf8-5db2020acf48":{"id":"4354cb31-d2e3-433d-bbf8-5db2020acf48","doc_no":"A.1.7.1","title":"Operational Executor Facilitator","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":287,"content":"Every Operational Executor Agent must have a Facilitator. The Operational Executor Agent and Facilitator must enter into an agreement where the Facilitator agrees to interpret the Atlas and Artifacts on behalf of the Agent.","contentHash":"1b603b8c4e8a74e6971f40de02e6fb076dfe0e8eb692834ced29295ee5e08991","addressRefs":[]},"29a92947-8792-401b-b1e5-899a72e9fbdb":{"id":"29a92947-8792-401b-b1e5-899a72e9fbdb","doc_no":"A.1.7.2","title":"Core Executor Facilitator","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":288,"content":"Every Core Executor Agent must have a Facilitator. The Core Executor Agent and Facilitator must enter into an agreement where the Facilitator agrees to interpret the Atlas and Artifacts on behalf of the Agent.","contentHash":"34060cbadfc36b7fe263d784c8a2b9388ce01429a1aad9738e85731b46b2d1ba","addressRefs":[]},"014feb92-49dc-4117-911f-a6ec14451b30":{"id":"014feb92-49dc-4117-911f-a6ec14451b30","doc_no":"A.1.7.3","title":"Facilitators Must Maintain High Level Of Operational Security","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":289,"content":"Facilitators are required to maintain a high level of operational security, adhering to best practices in privacy, cybersecurity, and physical resilience. These measures must be implemented at a level that sufficiently safeguards the Sky Ecosystem from physical risk posed by the potential for attacks against Facilitators. Facilitators’ operational security protocols should be regularly reviewed and updated to address emerging risks and ensure continuous protection of the ecosystem.","contentHash":"f4a0f7b9fc8a166744c14e2740bf1a0e3d245d6152609e7435b9647eda79109c","addressRefs":[]},"c3ba34f0-b3f0-449b-b609-52548db090ea":{"id":"c3ba34f0-b3f0-449b-b609-52548db090ea","doc_no":"A.1.7.4","title":"Derecognition Required Where Facilitator Operational Security Is Compromised","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":290,"content":"The Core Facilitator must act swiftly to investigate a Facilitator who is suspected of breaching their requirements regarding operational security and privacy.\n\nIf there is clear evidence or significant suspicion that the operational security of a Facilitator has been compromised, or that they have failed to follow best practice or otherwise made operational security errors, the Core Facilitator must promptly derecognize the Facilitator.","contentHash":"9f4500b40c3b215cc6f771055993b4279e707c5b3da57f12b5eb8a795009c252","addressRefs":[]},"b8601ee2-6576-4a0a-83da-660d1b81936b":{"id":"b8601ee2-6576-4a0a-83da-660d1b81936b","doc_no":"A.1.7.4.0.4.1","title":"Promptly Derecognized - Mandated Timeline For Facilitator Derecognition","type":"Action Tenet","depth":4,"parentId":"c3ba34f0-b3f0-449b-b609-52548db090ea","order":291,"content":"The element 'promptly' in the Target Document means 'as soon as is reasonably possible.'\n\nTo adhere to this commitment, the Core Facilitator must derecognize the Facilitator within a general timeframe of 1-2 calendar days upon conclusion of an investigation that finds against the Facilitator. Failure to meet this deadline requires a showing of good cause, demonstrating extenuating circumstances beyond the Facilitators’ control.","contentHash":"302a93d00ca5a0e8afdda9ce334529197c65d1235749ce5b829cb0e57f5ba67a","addressRefs":[]},"ac9df70a-d110-42da-805a-abe03b52dcdc":{"id":"ac9df70a-d110-42da-805a-abe03b52dcdc","doc_no":"A.1.7.5","title":"Facilitators Must Err On Side Of Caution","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":292,"content":"The Core Facilitator is required to err on the side of caution and take action whenever there is any real possibility that the operational security of a Facilitator is compromised. The Core Facilitator is afforded significant discretion in making judgement calls related to operational security standards for Facilitators.\n\nAbuse of this power is severe misalignment. Any allegations of this abuse of power must be adjudicated by Core GovOps pursuant to the process defined in [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57).","contentHash":"779e479a06564742ad6f70e2ca12776a7b18ab86b823c9b77a96bc2c6380f1c1","addressRefs":[]},"7aafa61e-8649-41fb-8c3f-64e5714f9f18":{"id":"7aafa61e-8649-41fb-8c3f-64e5714f9f18","doc_no":"A.1.7.6","title":"Acting Against Misalignment","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":293,"content":"The Core Facilitator is empowered with broad discretion in addressing situations where an Alignment Conserver, Ecosystem Actor or other relevant governance participant's actions are misaligned. See [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57), which defines the adjudication process that the Core Facilitator must follow in addressing Alignment Conserver misalignment.\n\nThe Core Facilitator's abuse of this discretionary power is severe misalignment. Any allegations of this abuse of power must be adjudicated by Core GovOps pursuant to the process defined in the above-cited document.\n\nThe Core Facilitator's failure to act promptly in addressing credible evidence of misalignment is considered an act of misalignment itself. Formal allegations of such failure must be adjudicated by Core GovOps to the same process referenced in the above-cited document.","contentHash":"31bbeada492f9940a5764bab905cfa5e388ed6627ed73c2660253f313ddf36c8","addressRefs":[]},"9962c7cc-9df2-4c37-89d6-746d004a056d":{"id":"9962c7cc-9df2-4c37-89d6-746d004a056d","doc_no":"NR-17","title":"Addressing Misalignment Of Ecosystem Actors Or Other Governance Participants","type":"Needed Research","depth":4,"parentId":"7aafa61e-8649-41fb-8c3f-64e5714f9f18","order":294,"content":"**Content**:\n\nCurrently, the Atlas specifies an adjudication process for Alignment Conserver misalignment or breach of operational security. Research is needed to consider a process by which Facilitators investigate and adjudicate suspected misalignment on the part of Ecosystem Actors or other governance participants.","contentHash":"26555c1a4ea975b2cee5e188f6122bde73ae8ecc926d74a117a9ccdeb4c86b08","addressRefs":[]},"36be7725-ea36-4e37-a363-856a69d6ef2d":{"id":"36be7725-ea36-4e37-a363-856a69d6ef2d","doc_no":"A.1.7.7","title":"Justification For Operational Decisions","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":295,"content":"The Core Facilitator must ensure that their decisions related to ordinary operations are clearly explained and justified using publicly available information. The Core Facilitator is generally prohibited from basing their decisions on internal knowledge or undisclosed data that is not accessible to the public.\n\nLimited exceptions to this rule apply when Facilitators' decisions involve sensitive security matters. However, even in these situations, the Core Facilitator should ensure that the rationale for their decision is communicated in a manner that respects security concerns while maintaining as much transparency as possible.","contentHash":"054c3963de330091c8fe5e924fdd85499a25255e16ab073d9a509e22ccafa878","addressRefs":[]},"4fbdf196-910c-4431-bdaa-f85f38bb4580":{"id":"4fbdf196-910c-4431-bdaa-f85f38bb4580","doc_no":"A.1.7.7.0.3.1","title":"Internal Knowledge - Element Annotation","type":"Annotation","depth":4,"parentId":"36be7725-ea36-4e37-a363-856a69d6ef2d","order":296,"content":"This element refers to information, insights, or data that are available exclusively to the Facilitators and are not shared or accessible to the Sky Ecosystem community. This could include messages in private chats, internal memos, emails, or proprietary data.","contentHash":"fa612cda3afedfc29e549be7f436f374ec207f0397672cb0b8454554f2239c05","addressRefs":[]},"260f1bd6-10c4-484a-9dda-e259667ccceb":{"id":"260f1bd6-10c4-484a-9dda-e259667ccceb","doc_no":"A.1.7.7.0.3.2","title":"Ordinary Operations - Element Annotation","type":"Annotation","depth":4,"parentId":"36be7725-ea36-4e37-a363-856a69d6ef2d","order":297,"content":"This element refers to the routine activities, processes, and decisions that are part of the day-to-day functioning of Sky. It excludes decisions involving extraordinary circumstances and emergencies, as these situations may require certain security-sensitive matters to be kept confidential.","contentHash":"5a03ca32dac905928cec1398137ae2244a580752d7beacfd615db5a7ced83d52","addressRefs":[]},"88bd0a0b-90df-43f8-a89e-2d931d2c3daf":{"id":"88bd0a0b-90df-43f8-a89e-2d931d2c3daf","doc_no":"A.1.7.7.0.3.3","title":"Publicly Available Information - Element Annotation","type":"Annotation","depth":4,"parentId":"36be7725-ea36-4e37-a363-856a69d6ef2d","order":298,"content":"This element refers to data, records, and documents that are accessible to the Sky Ecosystem community without any special access rights or permissions. This includes information published on websites, in public reports, or through other open and accessible channels.","contentHash":"bfacb1d10d7ecc227351c5d86ada0ec21d26ea73acacff3ea283d745b2b54375","addressRefs":[]},"66d51a72-b371-4334-a56d-fe5462918272":{"id":"66d51a72-b371-4334-a56d-fe5462918272","doc_no":"A.1.7.7.0.3.4","title":"Sensitive Security Matters - Element Annotation","type":"Annotation","depth":4,"parentId":"36be7725-ea36-4e37-a363-856a69d6ef2d","order":299,"content":"This element refers to issues or decisions that, if publicly disclosed, could compromise the safety, integrity, or security of the Sky Ecosystem and its community members.","contentHash":"42f6244724923b9578129af3bf01969edccb5c4fae887fadf04a6b3168162015","addressRefs":[]},"3f056c21-92de-4177-8c81-f8ba83a880ca":{"id":"3f056c21-92de-4177-8c81-f8ba83a880ca","doc_no":"A.1.7.8","title":"Prohibition On Engaging With Counterparties","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":300,"content":"Facilitators are generally prohibited from engaging with counterparties. The sole exception to this rule is where Facilitators must communicate with counterparties to set up governance processes. In such cases, the Facilitators must clearly detail their interactions with the counterparties.","contentHash":"be3470022ef31d6c00eabea79f73886129ac9886544883a7f6d7ef5b820afbb5","addressRefs":[]},"ce5d86d8-0a7c-4ad7-bc4c-d993d48d61a6":{"id":"ce5d86d8-0a7c-4ad7-bc4c-d993d48d61a6","doc_no":"A.1.7.8.0.3.1","title":"Counterparties - Element Annotation","type":"Annotation","depth":4,"parentId":"3f056c21-92de-4177-8c81-f8ba83a880ca","order":301,"content":"This element refers to external parties or entities with whom the Facilitators might interact in the context of governance operations, such as Ecosystem Actors (active or incubating).","contentHash":"911cefa07f62046402eb7d70bd0b24a53f0687aae8a799f477802b120cecd0e5","addressRefs":[]},"ce3344b0-a567-4fdf-b9e8-6520ee2e10fd":{"id":"ce3344b0-a567-4fdf-b9e8-6520ee2e10fd","doc_no":"A.1.7.8.0.4.1","title":"Clearly Detail Their Interactions - Facilitators' Documentation Mandate","type":"Action Tenet","depth":4,"parentId":"3f056c21-92de-4177-8c81-f8ba83a880ca","order":302,"content":"Facilitators are required to thoroughly document all aspects of their communications and dealings with counterparties. This includes the content of discussions, the context of interactions (date and time), and any decisions made or actions taken as a result.","contentHash":"14c787a28ebec7e5eba10870c4b39987a1132905d2364e4c1a15ff09b0bff0aa","addressRefs":[]},"f88d568e-bf5b-46f4-9adf-5299854de709":{"id":"f88d568e-bf5b-46f4-9adf-5299854de709","doc_no":"A.1.7.9","title":"Governance Process And Interaction Documentation","type":"Section","depth":3,"parentId":"1ce24b08-84ff-4524-9710-49bba429c6ef","order":303,"content":"The operational security of Sky is reliant on clear, thorough documentation of governance processes. Facilitators must document all operational and governance processes, as well as all interactions with ecosystem stakeholders.","contentHash":"d1be4a16c1f458855f02733152db9c4dc0d7dc668942564e55a33e07748d497d","addressRefs":[]},"d6b43720-243e-4610-8c03-cd515ace6247":{"id":"d6b43720-243e-4610-8c03-cd515ace6247","doc_no":"A.1.8","title":"Professional Ecosystem Actors","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":304,"content":"Professional Ecosystem Actors are external actors that complete work for Sky Ecosystem. This Article defines rules and processes related to Professional Ecosystem Actors.","contentHash":"2ec85d43f7ca1e22e6feda9f79cf424e77b63b90a0cf23aa968d7598ed546620","addressRefs":[]},"1ef5767b-60bc-446a-af45-4eccdb20c023":{"id":"1ef5767b-60bc-446a-af45-4eccdb20c023","doc_no":"A.1.8.1","title":"Active Ecosystem Actors","type":"Section","depth":3,"parentId":"d6b43720-243e-4610-8c03-cd515ace6247","order":305,"content":"Active or Incubating Ecosystem Actors work according to the specifications of the Atlas to receive funding for performing specific projects that benefit the Sky Ecosystem. Such projects can include developing new features; performing data collection or analysis; performing marketing, growth, outreach or educational activities; legal work or government outreach; and other operational activities. Active and Incubating Ecosystem Actors are the only type of actor that is permitted to do work that isn’t strictly defined in, and bounded by, the Atlas.","contentHash":"164cc464d1deb97434782e511688af8aefcf7eace6f20a0649299ce49c47288e","addressRefs":[]},"d80c8f64-b3f6-430d-bf62-8e50a3783e73":{"id":"d80c8f64-b3f6-430d-bf62-8e50a3783e73","doc_no":"A.1.8.1.1","title":"Core Council Risk Advisor","type":"Core","depth":4,"parentId":"1ef5767b-60bc-446a-af45-4eccdb20c023","order":306,"content":"The Core Council Risk Advisor is a specialized role for a designated Professional Ecosystem Actor to provide financial analysis and risk management advice to the Core Council and other relevant parties within Sky.","contentHash":"b7e06a789b8e636e336ba1ae509a0a61dca9fb3e59fb34a800fe149e53fa161c","addressRefs":[]},"3448e169-b784-4907-9bea-ec8b59d86b50":{"id":"3448e169-b784-4907-9bea-ec8b59d86b50","doc_no":"A.1.8.1.1.1","title":"Core Council Risk Advisor Requirements","type":"Core","depth":5,"parentId":"d80c8f64-b3f6-430d-bf62-8e50a3783e73","order":307,"content":"The Core Council Risk Advisor role must be held by an entity without involvement in any business, political, or governance-related activities that could create a conflict of interest, either directly or indirectly. Additionally, the entity must possess the relevant expertise and professional skills necessary to provide informed and objective input on financial and risk-related issues.","contentHash":"96e4a715aff5d243590b393051764f45d078a20cc265e7b0992c015455dea36b","addressRefs":[]},"51b1fe46-2251-4078-a805-e2b40aaaf729":{"id":"51b1fe46-2251-4078-a805-e2b40aaaf729","doc_no":"A.1.8.1.1.2","title":"Designated Core Council Risk Advisor","type":"Core","depth":5,"parentId":"d80c8f64-b3f6-430d-bf62-8e50a3783e73","order":308,"content":"The Core Council Risk Advisor role is held by BA Labs.","contentHash":"d31dd4fcc39ea0ed79be4c52949f119aed1a70d651ec693b824cda4f4ab5f6a6","addressRefs":[]},"a4ff45b4-bc05-4a1f-8413-0718efaf7450":{"id":"a4ff45b4-bc05-4a1f-8413-0718efaf7450","doc_no":"A.1.8.1.1.2.1","title":"BA Labs Limited Conflict Of Interests Waiver","type":"Core","depth":6,"parentId":"51b1fe46-2251-4078-a805-e2b40aaaf729","order":309,"content":"BA Labs is granted a limited waiver to the requirement that the Core Council Risk Advisor must not be involved in other business activities that could result in a conflict of interest. This waiver applies only to BA Labs’ work with Ethena.","contentHash":"a53c29f9ecec0ecd9c54770f0958a9ee5af7b8a570c3d78e19f9c84d495c3ce4","addressRefs":[]},"93651fb8-13c5-46dd-93cb-33fa89671b4f":{"id":"93651fb8-13c5-46dd-93cb-33fa89671b4f","doc_no":"A.1.8.1.2","title":"Protocol Security Workstream Lead","type":"Core","depth":4,"parentId":"1ef5767b-60bc-446a-af45-4eccdb20c023","order":310,"content":"The Protocol Security Workstream Lead is a specialized role for a designated Professional Ecosystem Actor to provide security oversight, incident coordination, and operational security guidance across the Sky Ecosystem.","contentHash":"904bf3429894db2ecc3a149b209f0172cb50e14619626c60be5e585596180a5c","addressRefs":[]},"6286be5c-f299-425e-a06b-39a129d4a929":{"id":"6286be5c-f299-425e-a06b-39a129d4a929","doc_no":"A.1.8.1.2.1","title":"Protocol Security Workstream Lead Requirements","type":"Core","depth":5,"parentId":"93651fb8-13c5-46dd-93cb-33fa89671b4f","order":311,"content":"The Protocol Security Workstream Lead role must be held by an individual with demonstrated expertise in protocol security, smart contract security, and operational security practices. The individual must not have involvement in any business, political, or governance-related activities that could create a conflict of interest, either directly or indirectly.","contentHash":"2855175603e69a9f42f6751d454cefde15d0ff97a95674c811ca25577753defc","addressRefs":[]},"57fa2bd5-4679-4b0c-a7a2-f65a4194d371":{"id":"57fa2bd5-4679-4b0c-a7a2-f65a4194d371","doc_no":"A.1.8.1.2.2","title":"Designated Protocol Security Workstream Lead","type":"Core","depth":5,"parentId":"93651fb8-13c5-46dd-93cb-33fa89671b4f","order":312,"content":"The Protocol Security Workstream Lead role is held by Vamsi.","contentHash":"feae92ff0938f4c11c34cf19e4d0e248ee28743a56e8efe79636544f1e89ec4c","addressRefs":[]},"1d940c6d-02ce-4c17-8057-cef13c1cc7ad":{"id":"1d940c6d-02ce-4c17-8057-cef13c1cc7ad","doc_no":"A.1.9","title":"Emergency Response System","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":313,"content":"This Article defines a general emergency response protocol for managing emergencies or urgent situations outside of the standard Weekly Governance Cycle and Monthly Governance Cycle.","contentHash":"74dcc2a8ca07d1972fcb48a232648a9b23e96f43edc150aaeb7ed20832186a22","addressRefs":[]},"20dcf582-8862-48b3-9ca9-c3703871bd14":{"id":"20dcf582-8862-48b3-9ca9-c3703871bd14","doc_no":"A.1.9.1","title":"Emergency Response","type":"Section","depth":3,"parentId":"1d940c6d-02ce-4c17-8057-cef13c1cc7ad","order":314,"content":"The Sky Protocol has often required changes outside of the standard Weekly Governance Cycle and Monthly Governance Cycle to help maintain the peg or to quickly respond to changes in the Ecosystem. This Section defines a general protocol for handling emergency or urgent situations.\n\n[A.1.10.5 - Emergency Spells](b8266c11-3a84-4bbe-abe2-de9474f74ffd) governs the resolution of emergency / urgent situations involving the Executive Process.","contentHash":"42f2922d02931f5f63886def7e512869988bfca26f39d3189eaba8ab059ad04c","addressRefs":[]},"5eafb29e-84a0-4a53-a798-3f958c880225":{"id":"5eafb29e-84a0-4a53-a798-3f958c880225","doc_no":"A.1.9.1.1","title":"Definition Of Emergency Situations","type":"Core","depth":4,"parentId":"20dcf582-8862-48b3-9ca9-c3703871bd14","order":315,"content":"An emergency situation is any situation that would require immediate intervention to prevent initiation of Emergency Shutdown, severe peg divergence, or harm to members and users of the Ecosystem.\n\nPursuant to [A.0.1.2.1 - Facilitators’ Broad Discretionary Capacity](f18229fe-fbc3-4dc8-ad84-4bca2915f6c4), the Facilitators have broad discretion to apply the emergency-situation processes defined in [A.1.9.1 - Emergency Response](20dcf582-8862-48b3-9ca9-c3703871bd14) to urgent situations. Urgent situations are defined as any situation that involves a time-sensitive matter that would need an expedited governance process, where following a standard governance cycle would be too slow, risk a larger problem, or constitute an important missed opportunity.","contentHash":"f8e40a3633c31b6de38103cc38242f9cf527addd52dc9932a579b0cf604ff699","addressRefs":[]},"d91720f8-8d9f-47f2-be80-c3dcaf8d216d":{"id":"d91720f8-8d9f-47f2-be80-c3dcaf8d216d","doc_no":"A.1.9.1.2","title":"Emergency Response Group","type":"Core","depth":4,"parentId":"20dcf582-8862-48b3-9ca9-c3703871bd14","order":316,"content":"Emergency response is coordinated by the Emergency Response Group (\"ERG\"). The Emergency Response Group is a group of Facilitators, Aligned Delegates, and Ecosystem Actors that include domain experts in different areas of the Sky Ecosystem. The Emergency Response Group is tasked with reacting to emergency scenarios that are critical to the survival of the Sky Protocol.","contentHash":"402981ca2b7dbbc0a95d7e54d34dc9dec036afec8d502bfec36375043dc88112","addressRefs":[]},"f83f2e87-6a6b-4afb-aa4c-d6d41a4a1cbc":{"id":"f83f2e87-6a6b-4afb-aa4c-d6d41a4a1cbc","doc_no":"A.1.9.1.2.1","title":"Emergency Response Group Membership Criteria","type":"Core","depth":5,"parentId":"d91720f8-8d9f-47f2-be80-c3dcaf8d216d","order":317,"content":"The membership of the Emergency Response Group may change at the discretion of Core GovOps, and as circumstances require. Generally, the Emergency Response Group should contain domain-expert Ecosystem Actors as well as governance decision-makers. The group must be able to diagnose a situation, suggest a short-term mitigation and act on such mitigation. The group should also be able to define the path forward for a long-term solution to the problem and act on it.","contentHash":"f47758da9380ef57fd19c4252f0ed9df4233492f724bdbcbfbaf55cfd2b79745","addressRefs":[]},"6ad02ee6-bd7a-4557-a768-178656037162":{"id":"6ad02ee6-bd7a-4557-a768-178656037162","doc_no":"A.1.9.1.2.2","title":"Emergency Response Group Membership","type":"Active Data Controller","depth":5,"parentId":"d91720f8-8d9f-47f2-be80-c3dcaf8d216d","order":318,"content":"The membership of the Emergency Response Group is defined as Active Data in [A.1.9.1.2.2.0.6.1 - Emergency Response Group Current Membership](e9807449-fdc3-4860-8d53-c56181311618).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Core GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"55f922b864f26c7f439921c27fc1efdb3a04ff3b955a587c9f09468d8bceb61d","addressRefs":[]},"e9807449-fdc3-4860-8d53-c56181311618":{"id":"e9807449-fdc3-4860-8d53-c56181311618","doc_no":"A.1.9.1.2.2.0.6.1","title":"Emergency Response Group Current Membership","type":"Active Data","depth":6,"parentId":"6ad02ee6-bd7a-4557-a768-178656037162","order":319,"content":"The members of the Emergency Response Group are:\n\n- Endgame Edge\n- JanSky\n- Ecosystem\n- Phoenix Labs\n- Jetstream\n- Atlas Axis\n- Steakhouse\n- Blocktower\n- Core Council Risk Advisor\n- Maker Growth\n- Dewiz\n- Sidestream\n- Cloaky\n- Blue\n- JuliaChang\n- PullUp Labs\n- Chronicle Labs\n- TechOps Services","contentHash":"ee724bbddd76eb7177533f2745a34b9f830b09885ee2f1e2bc4642b6b4512f8c","addressRefs":[]},"c56e96cc-d5fe-4e5c-80c1-9d3074b6660a":{"id":"c56e96cc-d5fe-4e5c-80c1-9d3074b6660a","doc_no":"A.1.9.1.2.3","title":"Emergency Response Group Team Members","type":"Core","depth":5,"parentId":"d91720f8-8d9f-47f2-be80-c3dcaf8d216d","order":320,"content":"Where an Emergency Response Group Member is a team, that team should assign two (2) of its own team members to be responsible for incident response.\n\nA team may assign more than two (2) of its team members to be responsible for incident response at the discretion of Core GovOps.\n\nTo the extent possible, the selected team members should be in different timezones and jurisdictions for maximum operational and regulatory resilience.\n\nThe team members assigned to the Emergency Response Group should not be disclosed publicly under any circumstances as this could make them targets.","contentHash":"d6cb1e833d1d088b1af93ec491f44f65550e5152205e069de164834cea0bd2a7","addressRefs":[]},"b41dc314-3bd6-49bb-a454-ef7a964e1a77":{"id":"b41dc314-3bd6-49bb-a454-ef7a964e1a77","doc_no":"A.1.9.1.2.3.1","title":"Ecosystem Actor Embedding","type":"Core","depth":6,"parentId":"c56e96cc-d5fe-4e5c-80c1-9d3074b6660a","order":321,"content":"As an extension of, and pursuant to [A.1.15.1.2 - Governance Security & Ecosystem Actor Embedding](12286b6c-0231-40e3-ab3f-234bc0249216), Ecosystem Actor Atlas Axis is permitted to assign more than two (2) of its team members to the permissioned Emergency Response Communication Channels defined in [A.1.9.1.3 - Emergency Response Communication Channels](18418289-ada8-401d-a992-7e38b235c866), as well as any Emergency Response calls.","contentHash":"6d74d2168249914c1352799f3246ff1e8a5583c33f7cb23727898e924945c8d3","addressRefs":[]},"d77ed6ca-518d-49bb-b400-a990d263f8d8":{"id":"d77ed6ca-518d-49bb-b400-a990d263f8d8","doc_no":"A.1.9.1.2.4","title":"Aligned Delegate Membership In Emergency Response Group","type":"Core","depth":5,"parentId":"d91720f8-8d9f-47f2-be80-c3dcaf8d216d","order":322,"content":"Aligned Delegate membership in the Emergency Response Group is not automatic based on amount of delegated SKY or Ranked Delegate status. An Aligned Delegate seeking to participate in emergency response must be reviewed and approved by Core GovOps prior to joining the Emergency Response Group.\n\nCore GovOps has discretion to approve or deny Aligned Delegate participation in the Emergency Response Group based on their assessment of the Aligned Delegate's competence and reliability.","contentHash":"52b367c5ce75bfbecedd0a823a8a3b5da1f64f992c06cc387fb86e8674dfaf21","addressRefs":[]},"18418289-ada8-401d-a992-7e38b235c866":{"id":"18418289-ada8-401d-a992-7e38b235c866","doc_no":"A.1.9.1.3","title":"Emergency Response Communication Channels","type":"Core","depth":4,"parentId":"20dcf582-8862-48b3-9ca9-c3703871bd14","order":323,"content":"The subdocuments herein specify the approved emergency-response communication channels.","contentHash":"dfc3f98e687f4c2d49aef9de1c95447831d2fe04fca3022d1993d8fdb1650abf","addressRefs":[]},"45a7ccff-09fa-4d95-b3d8-e3f34f7917cf":{"id":"45a7ccff-09fa-4d95-b3d8-e3f34f7917cf","doc_no":"A.1.9.1.3.1","title":"Emergency Response Signal Group","type":"Core","depth":5,"parentId":"18418289-ada8-401d-a992-7e38b235c866","order":324,"content":"A unique Signal \"Emergency Response\" Group will be used for all incident response coordination.\n\nTechOps Services will create the Signal Group and assign its administrators.\n\nCore GovOps and the Protocol Security Workstream Lead shall manage access to the Signal Group. All Emergency Response Members must be added to the Group.\n\nWhere an Emergency Response Group Member is a team, the two (2) team members responsible for incident response are required to join the Signal Group.\n\nThe Signal Group should not be used for any purpose except communications concerning a potential emergency situation. The Group must be configured to have a four-week message retention.","contentHash":"008a93b9f4adf30f48650e4e60853fff6a1c3cf6abff9c1516a1321d2eef4cb7","addressRefs":[]},"3efb0238-aaae-4351-9ec9-31902f3a1394":{"id":"3efb0238-aaae-4351-9ec9-31902f3a1394","doc_no":"A.1.9.1.3.2","title":"Emergency Contact Mechanism","type":"Core","depth":5,"parentId":"18418289-ada8-401d-a992-7e38b235c866","order":325,"content":"Emergency Response Group Members must use an emergency contact mechanism to deal with emergencies. This emergency contact mechanism is selected and validated by the Protocol Security Workstream Lead.","contentHash":"f753a35ab3896afb8a36867f448925e009b87d58cbd1d9a52db26e02d7dfb348","addressRefs":[]},"7baa8295-5509-4378-bcf9-842fda9a1365":{"id":"7baa8295-5509-4378-bcf9-842fda9a1365","doc_no":"A.1.9.1.3.2.1","title":"Emergency Contact Mechanism Selection Criteria","type":"Core","depth":6,"parentId":"3efb0238-aaae-4351-9ec9-31902f3a1394","order":326,"content":"A suitable emergency contact mechanism should meet the following criteria:\n\n- The mechanism should use enterprise grade infrastructure with correspondingly high levels of uptime.\n- The mechanism should not require personal information or KYC from users.\n- The mechanism should allow segmenting of target user groups, so that required individuals are only notified when necessary.\n- The mechanism should be able to bypass silent / do not disturb mode on devices to achieve an immediate response any time of day.\n- It is recommended, but not required, that the mechanism minimizes data tracking of individual users.\n- It is recommended, but not required, that the mechanism is open source.","contentHash":"904a037768e092e4d89caedb00741c5a87f30207861823caf01c62b1024d3d51","addressRefs":[]},"57006d4e-cd91-4565-97b5-5fab73fa94d5":{"id":"57006d4e-cd91-4565-97b5-5fab73fa94d5","doc_no":"A.1.9.1.3.2.2","title":"Approved Emergency Contact Mechanisms","type":"Core","depth":6,"parentId":"3efb0238-aaae-4351-9ec9-31902f3a1394","order":327,"content":"The currently approved emergency contact mechanism is PagerDuty.","contentHash":"dfdac2b7a53e38fce083fb01106fd47493d49c44e5b977e6a930f33913c50865","addressRefs":[]},"0b6f25c1-fc39-44dc-bd6a-fc612cdb826e":{"id":"0b6f25c1-fc39-44dc-bd6a-fc612cdb826e","doc_no":"A.1.9.1.3.2.3","title":"Changes To Approved Emergency Contact Mechanisms","type":"Core","depth":6,"parentId":"3efb0238-aaae-4351-9ec9-31902f3a1394","order":328,"content":"The Core Facilitator may recommend changing the approved emergency contact mechanism specified in [A.1.9.1.3.2.2 - Approved Emergency Contact Mechanisms](57006d4e-cd91-4565-97b5-5fab73fa94d5), but they must do so in consultation with the Protocol Security Workstream Lead. The Core Facilitator’s recommendation is subject to a poll through the Operational Weekly Governance Cycle.","contentHash":"d4b9bd73f8f65d0ad75300902f2332e13ca483ca4d31df5c43ea7f719c0d1b59","addressRefs":[]},"4627de70-9866-41b8-be8e-68e9ca809a45":{"id":"4627de70-9866-41b8-be8e-68e9ca809a45","doc_no":"A.1.9.1.3.2.4","title":"Emergency Contact Mechanism Fire Drills","type":"Core","depth":6,"parentId":"3efb0238-aaae-4351-9ec9-31902f3a1394","order":329,"content":"The Protocol Security Workstream Lead and Core Facilitator may run firedrills to test the preparedness of individuals that have been added to the emergency contact mechanism. This will be done at the discretion of the Protocol Security Workstream Lead and Core Facilitator. The results of firedrills shall be published to maintain transparency.","contentHash":"1a2c64f74a854654d7e2959107f8b60b288d04916e3280dc33aec3d5c5dc4a8c","addressRefs":[]},"c9c32f24-cf6c-43d5-ac4c-bd2b4d02032b":{"id":"c9c32f24-cf6c-43d5-ac4c-bd2b4d02032b","doc_no":"A.1.9.1.4","title":"Emergency Response Roles And Responsibilities","type":"Core","depth":4,"parentId":"20dcf582-8862-48b3-9ca9-c3703871bd14","order":330,"content":"The Core Facilitator is empowered to declare an emergency situation.\n\nAfter an emergency situation has been declared, Core GovOps is responsible for coordinating emergency-situation processes to ensure they are civil, consistently applied and aligned. The Core Facilitator is responsible for publishing Polls and Executive Votes.\n\nAny participant in the Sky Ecosystem, including Ecosystem Actors, Aligned Delegates or other community members, can request that the Core Facilitator declare an emergency. The Core Facilitator is granted broad discretion in handling such requests.","contentHash":"53c57ab34ca9f856898a8a0aef2f1072a51f1b914934a7f1b418444916f6ffb2","addressRefs":[]},"f1587c7c-4913-46f8-90ab-6c1afc2ec316":{"id":"f1587c7c-4913-46f8-90ab-6c1afc2ec316","doc_no":"A.1.9.1.4.1","title":"Considerations Before Expediting Protocol Changes","type":"Core","depth":5,"parentId":"c9c32f24-cf6c-43d5-ac4c-bd2b4d02032b","order":331,"content":"The Core Facilitator is required to consider several important factors before expediting changes to the protocol:\n\n- Potential for SKY holders to miss a poll or Executive Vote due to departure from the standard governance cycles.\n- Expedited votes may not allow for sufficient discussion, leading to a sub-optimal solution.\n- Increased governance burden on community and increased workload for domain teams.\n- Frequent expedited votes may signal a lack of appreciation for a consistent and predictable governance process.","contentHash":"9792b9451bdd25bc19aa6ca461bfd4694549f1bac10bfb188de3cf7aadddd645","addressRefs":[]},"498e151e-5096-4d0f-b9a9-665897b0b861":{"id":"498e151e-5096-4d0f-b9a9-665897b0b861","doc_no":"A.1.9.1.5","title":"Emergency Response Process Definition","type":"Core","depth":4,"parentId":"20dcf582-8862-48b3-9ca9-c3703871bd14","order":332,"content":"The subdocuments herein define the emergency response process.","contentHash":"c0a8c77d355973718ae9c469beef95db53daa7348e31f5113ba475433a6b12c9","addressRefs":[]},"97020aa2-9492-4fa4-8eee-d860d6f33618":{"id":"97020aa2-9492-4fa4-8eee-d860d6f33618","doc_no":"A.1.9.1.5.1","title":"Incident Validation","type":"Core","depth":5,"parentId":"498e151e-5096-4d0f-b9a9-665897b0b861","order":333,"content":"The Core Facilitator is responsible for determining whether a reported incident is a valid emergency; where possible, this can be done in consultation with relevant stakeholders.","contentHash":"f970ce7939d3b4bcf1f1dde72d8cb4fd339a551e6b5949b8a597a81055773da2","addressRefs":[]},"f3a647b2-8083-41f1-b67a-66bd322ccc16":{"id":"f3a647b2-8083-41f1-b67a-66bd322ccc16","doc_no":"A.1.9.1.5.2","title":"Incident Categorization","type":"Core","depth":5,"parentId":"498e151e-5096-4d0f-b9a9-665897b0b861","order":334,"content":"The Core Facilitator is responsible for categorizing emergencies according to their severity and other pertinent criteria.","contentHash":"2da5e3da5ee9d5fe144eff26088c044a1678ff8a60e1a1e898efa0c068a0fc84","addressRefs":[]},"34a3d273-ce49-4147-adf3-6d52b4a2fad5":{"id":"34a3d273-ce49-4147-adf3-6d52b4a2fad5","doc_no":"A.1.9.1.5.3","title":"Emergency-Contact Mechanism Trigger","type":"Core","depth":5,"parentId":"498e151e-5096-4d0f-b9a9-665897b0b861","order":335,"content":"Upon receiving notification from the Core Facilitator of a validated and categorized emergency situation, TechOps Services must trigger a notification in the Emergency Contact Mechanism specified in [A.1.9.1.3.2 - Emergency Contact Mechanism](3efb0238-aaae-4351-9ec9-31902f3a1394). All Emergency Response Group Members are required to acknowledge the incident in a timely manner through the Emergency Contact Mechanism. The notification must include a link to the official Emergency Response video call (\"war room\").","contentHash":"37550d2e20626149603192b3bd471a43ff41bc0a3a7ba3dbeacf35334b6636e1","addressRefs":[]},"e46bca7a-ddc5-4c5a-826e-3d9dab8a9709":{"id":"e46bca7a-ddc5-4c5a-826e-3d9dab8a9709","doc_no":"A.1.9.1.5.4","title":"Emergency Response Video Call Coordination","type":"Core","depth":5,"parentId":"498e151e-5096-4d0f-b9a9-665897b0b861","order":336,"content":"Emergency Response Group Members are required to promptly join the Video Call to coordinate incident response.","contentHash":"06850737d6a694d3fff22644dc7de32d96a6e859c54d1b3c8034c518fe6a9cba","addressRefs":[]},"3f5f79fa-698c-42db-a941-ead5a5d0aa48":{"id":"3f5f79fa-698c-42db-a941-ead5a5d0aa48","doc_no":"A.1.9.1.5.4.1","title":"Known And Uncontentious Remedies","type":"Core","depth":6,"parentId":"e46bca7a-ddc5-4c5a-826e-3d9dab8a9709","order":337,"content":"If a remedy is known and uncontentious, the Core Facilitator shall coordinate with the necessary Ecosystem Actors to expedite an Executive Vote.","contentHash":"5cb561bc4fc88850600b954a23d46e07b31156970b4788903ec28e9d59886f0c","addressRefs":[]},"8ce1adeb-ec38-40ba-9a0d-bc0e0db4fece":{"id":"8ce1adeb-ec38-40ba-9a0d-bc0e0db4fece","doc_no":"A.1.9.1.5.5","title":"Emergency Declaration Procedure","type":"Core","depth":5,"parentId":"498e151e-5096-4d0f-b9a9-665897b0b861","order":338,"content":"The Core Facilitator is empowered to declare an emergency situation at their discretion, either on their own initiative or in response to a request from a community member.\n\nWhen declaring an emergency, the Core Facilitator should create a formal post on the Sky Forum, providing sufficient detail regarding the issue and explaining why immediate action is required. If the situation allows, the Core Facilitator should post the emergency declaration on the Sky Forum before taking action. If the urgency of the situation requires immediate intervention without delay, the Core Facilitator should create the Forum post as soon as possible after, or simultaneously with, the emergency action.\n\nThere may be situations in which a public Emergency Declaration would be counterproductive to security objectives; the Core Facilitator is granted discretion in these matters.","contentHash":"ed5b54816e7ddc8a7a5d432ef7903cfbd20c674c8a2dee89d5ebd261521fcb38","addressRefs":[]},"ddab726d-7ecb-4028-bd85-964966d5d1ed":{"id":"ddab726d-7ecb-4028-bd85-964966d5d1ed","doc_no":"A.1.9.1.5.6","title":"Record Retention","type":"Core","depth":5,"parentId":"498e151e-5096-4d0f-b9a9-665897b0b861","order":339,"content":"To achieve continuous improvement of emergency response processes, records should be retained post-incident to enable review of actions taken during the incident response. Such records may include but are not limited to:\n\n1. An incident response template, to be specified in a future iteration of the Atlas, filled in with information from the coordination meeting;\n2. Incident artifacts, including files, screenshots, documents, and links;\n3. Chat transcripts from the approved communication channels specified in [A.1.9.1.3 - Emergency Response Communication Channels](18418289-ada8-401d-a992-7e38b235c866).\n\nIt is at the discretion of the Core Facilitator as to whether incident records can be shared with entities outside of the Emergency Response Group.","contentHash":"29db50ff536b8bda4cf9904a543ab9727f9fb730e79af266266485b2d113036a","addressRefs":[]},"8df982ee-754c-4cd9-a5f9-ce1c30e06cf8":{"id":"8df982ee-754c-4cd9-a5f9-ce1c30e06cf8","doc_no":"A.1.9.1.6","title":"Accountability For Emergency Response Preparedness","type":"Core","depth":4,"parentId":"20dcf582-8862-48b3-9ca9-c3703871bd14","order":340,"content":"Emergency preparedness is a critical priority. Core GovOps, in consultation with the Protocol Security Workstream Lead, must regularly evaluate the emergency preparedness of the Emergency Response Group. This can be done through running fire drills or through extensive postmortems after an actual incident.","contentHash":"0fb0ed1bcd36700d006143c6abc2b5ff50e46107a98f440be8420cfd885cd99e","addressRefs":[]},"665b3bc4-9146-4d47-adaf-fcaff3aefe67":{"id":"665b3bc4-9146-4d47-adaf-fcaff3aefe67","doc_no":"A.1.9.1.6.1","title":"Accountability Measures for Ecosystem Actor Individuals And Teams","type":"Core","depth":5,"parentId":"8df982ee-754c-4cd9-a5f9-ce1c30e06cf8","order":341,"content":"For Ecosystem Actors appointed to the Emergency Response Group, fulfilling the responsibilities of this role is as critical to their overall performance evaluation as their customary deliverables.\n\nCore GovOps and the Protocol Security Workstream Lead are required to document all instances of Emergency Response Group Members’ failure to meet emergency-preparedness requirements. Given their domain expertise and proximity to each emergency situation, Core GovOps and the Protocol Security Workstream Lead are granted the discretion to evaluate emergency-preparedness deficiencies. Generally, they are required to take swift action to address non-negligible emergency-preparedness deficiencies in the following manner.\n\nIf the deficient Emergency Response Group Member is an Ecosystem Actor individual, the individual should be removed from the Group.\n\nIf the deficient Emergency Response Group Member is part of an Ecosystem Actor team, the specific member who has failed to meet requirements should be removed from the Group.\n\nIf different Emergency Response Group Members from the same Ecosystem Actor team consistently fail to meet requirements, the Ecosystem Actor team as a whole should be removed from the Group.\n\nThe removal of a Member from the Group is done at the discretion of Core GovOps and the Protocol Security Workstream Lead. However, Core GovOps and the Protocol Security Workstream Lead may not proceed with removal unless it is supported with clear documentation.\n\nWhen an Ecosystem Actor is removed from the Emergency Response Group for deficient performance, Core GovOps must transparently announce this action via a post to the Sky Forum. Further, the removal must be incorporated into the evaluation of the Ecosystem Actor’s overall performance.\n\nCore GovOps has the discretion to decide if documentation supporting the removal should be retained internally or publicly shared on the Forum (with redactions, if needed).","contentHash":"037bbdc38e0050b5bd577a87aa7005bd4e2530f5d93f042639e7597826c6680b","addressRefs":[]},"2ce9cd30-8082-4470-965f-baa05c57b513":{"id":"2ce9cd30-8082-4470-965f-baa05c57b513","doc_no":"A.1.9.1.6.2","title":"Accountability Measures For Alignment Conservers","type":"Core","depth":5,"parentId":"8df982ee-754c-4cd9-a5f9-ce1c30e06cf8","order":342,"content":"For an Alignment Conserver who has been appointed to the Emergency Response Group, the requirements of this role become as critical to the assessment of their overall performance as their customary obligations.\n\nCore GovOps and the Protocol Security Workstream Lead are required to document all instances of Emergency Response Group Members’ failure to meet emergency-preparedness requirements. Given their domain expertise and proximity to each emergency situation, Core GovOps and the Protocol Security Workstream Lead are granted the discretion to evaluate emergency-preparedness deficiencies. Generally, they are required to take swift action to address non-negligible emergency-preparedness deficiencies in the following manner.\n\nWhere the deficient Member is an Alignment Conserver, that Member should be derecognized pursuant to [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57).\n\nWhere the deficient Alignment Conserver is the Core Facilitator, the Protocol Security Workstream Lead and Core GovOps must reach consensus in order to initiate a derecognition proceeding against the Core Facilitator. Once this threshold is met, the procedure defined in [A.1.5.9 - Adjudication Process](560e1024-0897-4f1e-ae71-3ba31e29ed57) should be followed. In the interim, Core GovOps selects an Operational Facilitator to step in temporarily and assist with coordinating emergency response.\n\nThe initiation of derecognition is done at the discretion of the Core Facilitator (or Core GovOps) and the Protocol Security Workstream Lead. However, the Core Facilitator and Protocol Security Workstream Lead may not proceed with removal unless it is supported with clear documentation.\n\nWhen an Alignment Conserver is removed from the Emergency Response Group and derecognized for deficient performance, the Core Facilitator must transparently announce this action pursuant to [A.1.5.10.1 - Derecognition Notice](9c05207d-5e11-43ae-a8a3-1b61734d6ef9).\n\nThe Core Facilitator has the discretion to decide if documentation supporting the Alignment Conserver’s derecognition and removal should be retained internally or publicly shared on the Forum (with redactions, if needed).","contentHash":"d531ca975294520444e780fa2d5223dce25e8c811d45ea11f3267ac5e5ba0689","addressRefs":[]},"de0cc370-de9c-48a4-b10e-91782df7abcd":{"id":"de0cc370-de9c-48a4-b10e-91782df7abcd","doc_no":"A.1.10","title":"Sky Core Governance Security","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":343,"content":"This Article governs the correct and secure execution of Sky Governance processes for deploying and reviewing Executive Votes. This Article must protect against all forms of attacks, disruption and accidental failure by maximizing the transparency and resilience of the Sky Executive Process.","contentHash":"8085a977c8c00cd7c760f240c5a3ea17d858814abe0d4cf3fae4d49c6c25e0c9","addressRefs":[]},"41600516-1414-4c52-86f6-de8393911cfa":{"id":"41600516-1414-4c52-86f6-de8393911cfa","doc_no":"A.1.10.1","title":"General Provisions","type":"Section","depth":3,"parentId":"de0cc370-de9c-48a4-b10e-91782df7abcd","order":344,"content":"This Section contains general provisions related to Sky Core Governance Security.","contentHash":"90329711ed121ffa7cb27996dd96311221e75b499fb0c6076cbc01247f880d43","addressRefs":[]},"f2bf066a-fdc6-4a3c-8375-24647c7fbed5":{"id":"f2bf066a-fdc6-4a3c-8375-24647c7fbed5","doc_no":"A.1.10.1.1","title":"Spell Team Anonymity","type":"Core","depth":4,"parentId":"41600516-1414-4c52-86f6-de8393911cfa","order":345,"content":"The Spell teams need not share their identities. Therefore, it is no longer a requirement that Spell crafting teams publish the deployer of a smart contract. The Spell Checklists have been amended accordingly.","contentHash":"a9c2cdaf22c3b275c1b8cd4a376a7b0b1ce6d8112f9061b59fbe0606cd63def1","addressRefs":[]},"fa9145a8-308c-4732-927d-cb6da4682fcf":{"id":"fa9145a8-308c-4732-927d-cb6da4682fcf","doc_no":"A.1.10.1.2","title":"Chainlog","type":"Core","depth":4,"parentId":"41600516-1414-4c52-86f6-de8393911cfa","order":346,"content":"The Chainlog is an on-chain, governance-managed registry that records the official addresses of Sky’s core smart contracts. Each contract entry in the Chainlog is identified by a unique key (\"Chainlog key\"), which is used to reference the contract in documentation, governance actions, and integrations. It serves as the single source of truth for contract addresses in the protocol. The Chainlog is available at [https://chainlog.sky.money/](https://chainlog.sky.money/). Updates to the Chainlog are defined as housekeeping items (see [A.1.11.1.5.1.1 - Definition Of Housekeeping Items](7648bf12-d600-4e0d-807b-5eb18e8d0f4f)) and can be included directly in an Executive Vote (see [A.1.11.1.5.1.2 - Process for Adding Housekeeping Item In Executive Vote](2d165c27-5daf-4a84-af8c-7c36f5de03d2)).","contentHash":"a0c2b2943a0f379e89f31fd52326b9d4b86630f10997a8e5aa44f16202dc3801","addressRefs":[]},"03d32549-1da5-4a9c-902f-196641370eaf":{"id":"03d32549-1da5-4a9c-902f-196641370eaf","doc_no":"A.1.10.2","title":"Executive Process Definition","type":"Section","depth":3,"parentId":"de0cc370-de9c-48a4-b10e-91782df7abcd","order":347,"content":"This Section defines the Executive Process, which is the end-to-end process through which Sky makes changes to the Sky Protocol.","contentHash":"fe89587758985654275d9a06955021067a6dcfa6c9fcc0911271dc7c4b0dadc5","addressRefs":[]},"324f379a-6341-4f39-aad5-f79f0d56812c":{"id":"324f379a-6341-4f39-aad5-f79f0d56812c","doc_no":"A.1.10.2.1","title":"Definitions","type":"Core","depth":4,"parentId":"03d32549-1da5-4a9c-902f-196641370eaf","order":348,"content":"The documents herein contain common definitions that are relevant to the entirety of the Executive Process.","contentHash":"192b8c7c3b6434245055b2aad8c1d31f85e182ccf7586006bcdf148ee9ef5a08","addressRefs":[]},"af04619b-5b0b-4762-86de-067550e079b9":{"id":"af04619b-5b0b-4762-86de-067550e079b9","doc_no":"A.1.10.2.1.1","title":"Executive Sheet","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":349,"content":"The Executive Sheet serves as a planning instrument and documentation for the agreed content of the Spell. It is therefore one of the foundational documents in the Executive Process. Each Spell has a dedicated Executive Sheet. The Governance Point creates a new Executive Sheet for each Executive Vote cycle, listing every executive item intended for inclusion in that cycle along with the provenance of each item. In this way, the Executive Sheet helps ensure transparency and verification in the Executive Process. Past Executive Sheets are preserved in order to provide a record of Executive Votes and their provenance.\n\nThe Executive Sheet (also referred to as the \"exec sheet\" or \"sheet\") is maintained on a large Google Sheets spreadsheet with several tabs. Each Executive Vote has its own tab, whose title is the designated Target Date for each Spell.\n\nThe Executive Sheet provides a publicly visible list of plain-English instructions outlining the executive actions performed in a given Spell. Each executive action is populated in the Executive Sheet under a column and broken down into input actions (high-level actions) and derived actions (resulting from input actions).\n\nThe Executive Sheet is used by several actors in the Executive Process. It is managed and populated by the Governance Point, used by stakeholders, who are required to provide confirmation for proposed executive items, and by the Spell Team. The Executive Sheet is the source of truth for the Spell Crafter who crafts the Spell based on its content. Only the Core Facilitator has write access to the Executive Sheet.","contentHash":"51952508b0618f4e25f37ed0e74bf9daba26c67dd1073b5cc6839a635f6cde25","addressRefs":[]},"2f06dd6a-8664-4916-8f82-5155d703d61a":{"id":"2f06dd6a-8664-4916-8f82-5155d703d61a","doc_no":"A.1.10.2.1.2","title":"Target Date","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":350,"content":"The Target Date refers to the planned date when the Spell is expected to be made available to be voted on. The Target Date is decided by the Governance Point in collaboration with the Spell Crafter. Spells are usually deployed following a two-week cadence. Normally, the Target Date falls on Thursdays.","contentHash":"b3595e1d82cd1acfc6ad4b9c762c9f3cb8314d70d7dcaf49128f06594de93327","addressRefs":[]},"a352b5e8-752e-48f8-a393-cf5df5ae523d":{"id":"a352b5e8-752e-48f8-a393-cf5df5ae523d","doc_no":"A.1.10.2.1.3","title":"Executive Document","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":351,"content":"The Executive Document (also referred to as the \"Executive Copy,\" \"executive,\" \"Executive Proposal,\" or \"exec doc\") is a formal, plain-English Markdown document that serves as the primary communication tool for presenting the contents of an Executive Vote to the community. Created after the Executive Sheet is finalized, it provides a detailed breakdown of the actions proposed in the Executive Vote. Unlike the Executive Sheet, which organizes actions in a cell-based format, the Executive Document expresses these actions in sentence format for improved readability.\n\nEach Executive Document corresponds to a specific Spell and describes the actions that the Spell will perform if executed. It is a critical tool for ensuring transparency, clarity, and alignment among stakeholders. The document serves as a proposal that can be voted on and either approved or rejected by Sky Governance. The Core Facilitator is responsible for producing and finalizing the Executive Document; and any changes must be made by them.\n\nThe Executive Document is designed to be accessible to both technical and non-technical members of the Sky Ecosystem. It enables Aligned Delegates and SKY holders to understand the actions that will be executed when the Spell is cast. Its contents are publicly visible on the Voting Portal, where Aligned Delegates review it before voting on the Spell. In addition to serving as a reference for voters, the Executive Document also guides the Spell Team in developing and finalizing the Spell, ensuring that the proposed actions are accurately implemented. The contents of the Executive Document are hashed and included within the Spell code to provide an additional layer of verification.","contentHash":"79df20f7ef88f239af3fefbb8f7a68da99bc24ea88e733f800951685e4fb7b67","addressRefs":[]},"c0aea3f8-4ed9-4bd6-928b-f43ccc7d5ecf":{"id":"c0aea3f8-4ed9-4bd6-928b-f43ccc7d5ecf","doc_no":"A.1.10.2.1.4","title":"Executive Vote","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":352,"content":"Executive Vote refers to the voting process of approving governance proposals within Sky Governance. These votes are conducted onchain and are used to implement technical changes to the Sky Protocol. For an Executive Vote to be executed, it must accumulate more SKY token support than any other active proposal, including the current leading proposal, ensuring it reflects the highest level of community backing at the time of approval.","contentHash":"79c3edf89937289d799a79a786ad31795218f82d4e283c694638c829d221c5e8","addressRefs":[]},"0919d4bd-2050-43dc-a1b9-8cdfdf0cba54":{"id":"0919d4bd-2050-43dc-a1b9-8cdfdf0cba54","doc_no":"A.1.10.2.1.5","title":"Sky Governance Voting Portal","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":353,"content":"The Voting Portal is the primary user interface where Executive Votes are published and where Aligned Delegates and SKY holders review and vote on proposals. It serves as the canonical location for viewing active and past Executive Votes, associated documentation, and vote tallies. The Voting Portal can be found at [https://vote.sky.money/executive](https://vote.sky.money/executive).","contentHash":"a2d4c2eb959d5a5918199f42e05867035e6581582c55bc481b93e363b580d836","addressRefs":[]},"7171aa68-668e-49bb-bf00-511cb79eb5e9":{"id":"7171aa68-668e-49bb-bf00-511cb79eb5e9","doc_no":"A.1.10.2.1.6","title":"Custom Spell Voting Page","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":354,"content":"The custom Spell voting page is the public interface used to submit, review, and vote on Executive Votes that are not accompanied by a formal Executive Document. It also supports voting on pre-deployed standby Spells by allowing stakeholders to specify target contract addresses and calldata directly. The custom Spell voting page can be found at [https://vote.sky.money/custom-spell](https://vote.sky.money/custom-spell).","contentHash":"4cb997e538abee02600716fece033cd1700527d231bbfe8563d0a290b8882d27","addressRefs":[]},"7d798e34-cdb0-4416-ab11-b5b48ccf61e6":{"id":"7d798e34-cdb0-4416-ab11-b5b48ccf61e6","doc_no":"A.1.10.2.1.7","title":"Spell","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":355,"content":"Spell is a term specific to the Sky Protocol. It refers to all technical components of an Executive Vote, encompassing the codebase, code operations, code reviews, and overall code quality. The term \"Spell\" is often used interchangeably with the Executive Vote itself, as it represents the smart contract responsible for enacting changes to the protocol. Spells are categorized as either \"regular\" or \"out-of-schedule.\" Regular Spells adhere to a biweekly cadence, while out-of-schedule Spells are handled with service-level agreements (SLAs) determined on a case-by-case basis.","contentHash":"617f7ffc0bf5adbb42eeb35f05c0cc05ff0b947e96d579e285b8487d94be7a3c","addressRefs":[]},"e2bc30b0-1370-44e6-9872-39530ff61d65":{"id":"e2bc30b0-1370-44e6-9872-39530ff61d65","doc_no":"A.1.10.2.1.8","title":"Ecosystem Spell Validation","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":356,"content":"Ecosystem Spell Validation (also referred to as \"Spell validation\" or \"validation\") refers to the process of performing a set of checks and high-level review of a specific Spell’s code as it exists on the blockchain (referred to as a \"deployed Spell\"). This process applies only to the deployed Spell and is not as comprehensive as the reviews conducted during the Spell development process by the Spell Reviewers. The purpose of Spell validation is to validate the safety of the current Spell in respect to its security impacts in relation to Sky Protocol smart contracts.","contentHash":"80a33e030af7cdf0b28fb1481235d50b707d087fc81caa6b6a62d70b3483f76c","addressRefs":[]},"34fb69c2-12db-452c-a773-1d3ed706b993":{"id":"34fb69c2-12db-452c-a773-1d3ed706b993","doc_no":"A.1.10.2.1.9","title":"Spell Roster","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":357,"content":"Spell Roster refers to the two teams of technical contributors in the Sky Ecosystem, Sidestream and Dewiz. The Spell Team for the Executive Vote is selected from the members of the Spell Roster.","contentHash":"83ddf16136cbb4b1d3cea8613832117738c8d0f6c82db72e6f2990be3c6656f2","addressRefs":[]},"202874e5-65f8-4250-bfb1-5122e5656395":{"id":"202874e5-65f8-4250-bfb1-5122e5656395","doc_no":"A.1.10.2.1.10","title":"Spell Team","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":358,"content":"Each Executive Vote has a dedicated Spell Team, made up of Spell Crafters and Spell Reviewers. The Spell Team must include one Crafter, who is responsible for crafting the Spells. The Spell Team must also include at least two Reviewers, responsible for reviewing and confirming that the Spells are ready for the Executive Vote, at least one of whom should be a member of a different Ecosystem Actor than the Spell Crafter. A Crafter cannot serve as a Reviewer for the same Spell. The Spell Team is a set of technical contributors working on developing all technical and smart-contract-related aspects of a particular Executive Vote, based on instructions set out by the Governance Point.","contentHash":"aed98d4904f843bf908f0e8eacaa27731a5752b3e593659582b0079336a2f9d7","addressRefs":[]},"e007c08a-5fef-42df-a63b-7b4d78b3366f":{"id":"e007c08a-5fef-42df-a63b-7b4d78b3366f","doc_no":"A.1.10.2.1.11","title":"Spell Crafter","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":359,"content":"The Spell Crafter (the Crafter) is the person or entity who parses the written instruction set of a proposed Executive to Solidity code in order to develop the Spell in the first instance. Every addition, modification, or removal of code or content within the Spell must be performed by the Crafter. The designated Spell Crafter must be rotated, such that the same person does not craft the Spells for two consecutive Executive Votes. The Spell Crafter is a member of the Spell Team for a particular Executive Vote.","contentHash":"316dbfe4623be867297936ca29d94b43688776aaf3492b5cc06495a7df000c7f","addressRefs":[]},"8d7a61c4-c1fd-4fbb-bbe9-1c2d6f4f3cdd":{"id":"8d7a61c4-c1fd-4fbb-bbe9-1c2d6f4f3cdd","doc_no":"A.1.10.2.1.12","title":"Spell Reviewer","type":"Core","depth":5,"parentId":"324f379a-6341-4f39-aad5-f79f0d56812c","order":360,"content":"The Spell Reviewers (the Reviewers) are the people or entities responsible for reviewing the draft Spell as parsed by the Spell Crafter. The Reviewers are responsible for verifying the Spell, finding issues and catching bugs and mistakes in the Spell, and otherwise ensuring its quality. There is an important delineation between the function of Spell Crafters and Spell Reviewers: the Reviewers may not perform any addition, modification or removal of code or content within the Spell, although they may suggest changes to the Spell Crafter. Spell Reviewers are members of the wider Spell Team for a particular Executive Vote.","contentHash":"511c4c9c9d66a3a0a94b726761c0a2ceee7ae4113ac3b996ef175f2894ee36ea","addressRefs":[]},"fb57a48c-5c33-45a4-a49b-2547234129c0":{"id":"fb57a48c-5c33-45a4-a49b-2547234129c0","doc_no":"A.1.10.2.2","title":"Roles in the Executive Process","type":"Core","depth":4,"parentId":"03d32549-1da5-4a9c-902f-196641370eaf","order":361,"content":"Several different actors within the Sky Community play a role in the Executive Process. The specific actors involved vary depending on the content of the items included in the Executive Process. These actors are categorized into four groups: Governance Point, Technical Point, Content Liaisons, and SKY holders (acting directly or via Aligned Delegates and Shadow Delegates).","contentHash":"b818a37fa793bad9460a423824eb9f6b72ffb74238d8efe850b68a07658f5481","addressRefs":[]},"b8d55094-f75e-4316-9b68-59cbb72e5b26":{"id":"b8d55094-f75e-4316-9b68-59cbb72e5b26","doc_no":"A.1.10.2.2.1","title":"Governance Point And Governance Backup","type":"Core","depth":5,"parentId":"fb57a48c-5c33-45a4-a49b-2547234129c0","order":362,"content":"The Governance Point is the Core Facilitator. Currently, the only Core Facilitator is JanSky. Each Spell also has a designated Governance Backup. The Governance Backup is required to assume the responsibilities of the Governance Point if the original Governance Point becomes unavailable, effectively stepping into the role as needed. The Governance Point is responsible for coordinating the Executive Vote and ensuring that the information in the Executive Sheet accurately reflects the progress of the Spell.\n\nThe Technical Point has domain expertise as the crafter of the smart contracts, but the Governance Point also has crucial context and should serve as a cross-check to the extent they can. The Governance Point is expected to ask questions where needed.","contentHash":"aa7231b80c2b4a4a79b385a04e4952e63d4071f9d5377fa268d0f74f22b4f3af","addressRefs":[]},"4137e37c-27ac-4618-8327-d88a23a7c9ce":{"id":"4137e37c-27ac-4618-8327-d88a23a7c9ce","doc_no":"A.1.10.2.2.1.1","title":"Role Of Governance Point And Backup","type":"Core","depth":6,"parentId":"b8d55094-f75e-4316-9b68-59cbb72e5b26","order":363,"content":"The role of Governance Point and Governance Backup alternates from within the Core Facilitator. The positions rotate, following an internal schedule.","contentHash":"081bfbd4c81e28b55848c06b75ba62b61780919159d2df06c0890a6abb70217f","addressRefs":[]},"6de84303-18f4-4d70-b259-b8f02c49b9bc":{"id":"6de84303-18f4-4d70-b259-b8f02c49b9bc","doc_no":"A.1.10.2.2.1.2","title":"Responsibilities For Governance Point","type":"Core","depth":6,"parentId":"b8d55094-f75e-4316-9b68-59cbb72e5b26","order":364,"content":"The Governance Point has the following responsibilities in the Executive process:\n\n- Gather the proposed content for the Executive sheet and prepare a draft of the Executive Vote.\n- Align on Executive Vote contents with the relevant teams, and coordinate technical details.\n- Ensure the contents of each Executive Vote are justified by processes or structures ratified by Sky Governance.\n- Produce the text (Executive Document) that accompanies each Executive Vote and verify that the delivered code matches the code reviewed and approved on GitHub and that it contains all expected actions from the sheet.\n- Publish the Executive Vote on the official Voting Portal.","contentHash":"b4e660a735615b34aaab39328e0036e4765f4d160e51100a061dbf5e157edcda","addressRefs":[]},"6474ab2e-da22-4227-9aff-7f13ac0dd471":{"id":"6474ab2e-da22-4227-9aff-7f13ac0dd471","doc_no":"A.1.10.2.2.2","title":"Technical Point","type":"Core","depth":5,"parentId":"fb57a48c-5c33-45a4-a49b-2547234129c0","order":365,"content":"The Technical Point role is filled by the Spell Team or the Spell Crafter from that group. For each Executive Vote, a Spell Team is selected from the Spell Roster to steward the Spell development process.\n\nWithin the Spell Team, the Spell Crafter serves as the primary point of contact for the Governance Point and any external parties. If the Spell Crafter is unavailable or if disagreements arise, the Governance Point’s secondary point of contact is the Spell Reviewers.\n\nInput or opinions from external parties on technical details should be treated as informational and should not influence the Spell decision-making process.","contentHash":"624d3872d772ae53fffa7423111a369016d9f4c0fbea2b2f88765df0b7aa4ad7","addressRefs":[]},"4862ed4e-097b-42fa-a197-1d407d220a77":{"id":"4862ed4e-097b-42fa-a197-1d407d220a77","doc_no":"A.1.10.2.2.2.1","title":"Spell Team Configuration","type":"Core","depth":6,"parentId":"6474ab2e-da22-4227-9aff-7f13ac0dd471","order":366,"content":"The Spell Team consists of the Crafter(s) and Reviewers for a designated Spell.\n\nCurrently, Sky has two teams of technical contributors for Spell development, Dewiz, and Sidestream. They rotate the responsibility of crafting and reviewing as follows:\n\n- When Dewiz is crafting:\n    - Crafting: one Dewiz member\n    - Reviewing: one Dewiz member, one Sidestream member\n- When Sidestream is crafting:\n    - Crafting: one Sidestream member\n    - Reviewing: one Sidestream member, one Dewiz member.","contentHash":"e24d354bb557b48e17e037023e5274e74892e2e9d71979602b4c6bd458745467","addressRefs":[]},"4ed84898-db7b-4759-bd00-e3cf09ac27e9":{"id":"4ed84898-db7b-4759-bd00-e3cf09ac27e9","doc_no":"A.1.10.2.2.3","title":"Content Liaisons","type":"Core","depth":5,"parentId":"fb57a48c-5c33-45a4-a49b-2547234129c0","order":367,"content":"The Content Liaisons are the stakeholders involved in a specific Spell. They participate in the verification process and confirm the accuracy of items relevant to their area of expertise, to ensure accuracy of those items in the Executive Sheet. Many different actors in the Sky Ecosystem serve as Content Liaisons for Executive Votes.","contentHash":"a075b9e2d247de31820f28ff7353e6b7e57d55e4a828fe3c99547b04c490cf1a","addressRefs":[]},"3e1d0486-4805-4bed-a246-f75198e111e6":{"id":"3e1d0486-4805-4bed-a246-f75198e111e6","doc_no":"A.1.10.2.2.4","title":"SKY Holders","type":"Core","depth":5,"parentId":"fb57a48c-5c33-45a4-a49b-2547234129c0","order":368,"content":"The SKY token is a governance token that grants the owner voting rights in the Sky Protocol. SKY holders can exercise their voting power directly by participating in governance decisions, such as Executive Votes, or they can delegate their tokens to an Aligned Delegate or a Shadow Delegate to vote on their behalf.","contentHash":"3f1d6a5019eb4ae5109e889f63bc17942574e1726fea0c2b8bed60cef67d9b6a","addressRefs":[]},"891a72ff-bfdc-4353-b6a0-0719de4d36ac":{"id":"891a72ff-bfdc-4353-b6a0-0719de4d36ac","doc_no":"A.1.10.2.2.4.1","title":"Aligned Delegates","type":"Core","depth":6,"parentId":"3e1d0486-4805-4bed-a246-f75198e111e6","order":369,"content":"Aligned Delegates are recognized representatives who vote on Sky governance decisions on behalf of their delegators. They are officially listed in the Atlas and, if they fulfill certain requirements such as operational security and engagement levels, they can receive compensation from Sky. They validate and vote on Executive Votes, and should inform the community about their validation of a Spell, along with the reasoning for their vote, through the Sky Forum.","contentHash":"f54227ebd6a80d86040f6a9f4bf048155528078fd41894d9d3eedd22627386d9","addressRefs":[]},"c38ceb17-a35c-4f1c-a526-2267d1b424b5":{"id":"c38ceb17-a35c-4f1c-a526-2267d1b424b5","doc_no":"A.1.10.2.2.4.2","title":"Shadow Delegates","type":"Core","depth":6,"parentId":"3e1d0486-4805-4bed-a246-f75198e111e6","order":370,"content":"Shadow Delegates serve as alternative representatives for SKY holders who delegate their tokens. They are not officially recorded in the Atlas and do not receive any compensation from Sky. They may participate in governance decisions and vote on behalf of their delegators.","contentHash":"56100ce2fccc6fa267d16475f9ebbbcf1a08bc49ad29a57d84d943dca9bf6344","addressRefs":[]},"7b4c9934-5ba4-4218-b601-8f44ffb5881e":{"id":"7b4c9934-5ba4-4218-b601-8f44ffb5881e","doc_no":"A.1.10.2.3","title":"Content Of The Executive Vote","type":"Core","depth":4,"parentId":"03d32549-1da5-4a9c-902f-196641370eaf","order":371,"content":"The content of an Executive Vote typically consists of the set of onchain changes executed by the Spell. Depending on the specific needs of Sky and the Agents, an Executive Vote may also include DAO resolutions or other off-chain decisions.\n\nThere is a set of recurring items in all Executive Votes, and some onchain changes reflect frequently occurring actions; others are novel and require specialized, out-of-cadence processes. These are set forth in more detail in the subdocuments herein.","contentHash":"0c56b53e44a4d18853ba2d2549261331a5e0a963860b6a0bbda393277413297b","addressRefs":[]},"d1d16776-3eec-4e7d-b591-052fe9c2c45b":{"id":"d1d16776-3eec-4e7d-b591-052fe9c2c45b","doc_no":"A.1.10.2.3.1","title":"Recurring Items","type":"Core","depth":5,"parentId":"7b4c9934-5ba4-4218-b601-8f44ffb5881e","order":372,"content":"For each Executive Vote, the parameters listed in the subdocuments herein are always specified. It is the Spell Crafter who is responsible for identifying if the proposed contents of the Spell require the parameters to be set to \"Yes\" or \"No\".","contentHash":"2004f0de459fd4ef07eee4b68a02df36e7191a970f3d08b9f4b562d8c26f3094","addressRefs":[]},"11cf1764-aefa-4343-ad44-e993024b3192":{"id":"11cf1764-aefa-4343-ad44-e993024b3192","doc_no":"A.1.10.2.3.1.1","title":"Office Hours","type":"Core","depth":6,"parentId":"d1d16776-3eec-4e7d-b591-052fe9c2c45b","order":373,"content":"Office hours are set to \"Yes\" if a Spell introduces major changes that can affect external parties, or if a stakeholder makes a specific request for the office-hours modifier to be switched on. Typical examples include collateral offboarding, onboarding new modules, oracle changes, and other actions that may have a significant impact on the protocol or its users.\n\nWhile stakeholders can request that Office Hours be switched on, the final decision and responsibility for setting this parameter rests with the Spell Crafter. If the office hours modifier is on, the Spell can only be executed between 14:00 and 21:00 UTC, Monday - Friday. The purpose of this modifier is to ensure that Ecosystem Actors are available to address any issues that may arise during or shortly after the execution of the Spell. The Spell will have an extra restriction on top of the GSM Pause Delay, meaning it can only be cast during that timeframe, regardless of when it was approved.","contentHash":"6dad651635a0870c5bcddbd3c17569b3344052c0ccda1f2c03d6277b12013035","addressRefs":[]},"df0835ea-e299-4fe2-aaca-3926f09913b9":{"id":"df0835ea-e299-4fe2-aaca-3926f09913b9","doc_no":"A.1.10.2.3.1.2","title":"Global Line Modifier","type":"Core","depth":6,"parentId":"d1d16776-3eec-4e7d-b591-052fe9c2c45b","order":374,"content":"The Global Line Modifier, also referred to as the Global Debt Ceiling, defines the system-wide debt ceiling for Sky. It is set to \"Yes\" if there is a modification to any collateral type’s line that necessitates that the global Line is also modified.","contentHash":"87ac1ebc49af0aca96bfa191fb30c14ae7d14e4e81aa72a8bf56b63acde512b3","addressRefs":[]},"18b4c424-68bd-4599-b8b5-9325d0dd8f3b":{"id":"18b4c424-68bd-4599-b8b5-9325d0dd8f3b","doc_no":"A.1.10.2.3.1.3","title":"Order Of Operations","type":"Core","depth":6,"parentId":"d1d16776-3eec-4e7d-b591-052fe9c2c45b","order":375,"content":"The Order of Operations parameter is relevant when actions within a Spell, or across multiple Spells, must be executed in a specific order to ensure that the correct final value is set. This applies to cases where dependencies, conflicting changes, or timing-sensitive modifications require precise sequencing to achieve the intended outcome. The Order of Operations parameter is set to \"Yes\" when actions must be executed in a specific order.","contentHash":"9451b674aeafac40d24b94716343538fad8e751f98f6b3773f230679db3ae761","addressRefs":[]},"64edb1ca-e577-41c4-aa9e-5af759b2d240":{"id":"64edb1ca-e577-41c4-aa9e-5af759b2d240","doc_no":"A.1.10.2.3.2","title":"Common Items","type":"Core","depth":5,"parentId":"7b4c9934-5ba4-4218-b601-8f44ffb5881e","order":376,"content":"Some onchain changes frequently occur as part of the normal operations of Sky. Sometimes these common items have specialized processes associated with them. Common items for Executive Votes are listed in the subdocuments herein.","contentHash":"4b7162a999746d7823c43ac175ff89c2356b2b0b2f1a16bcbf436f3100fe95a9","addressRefs":[]},"55e774c1-dcef-4262-bc47-c32c94c0d557":{"id":"55e774c1-dcef-4262-bc47-c32c94c0d557","doc_no":"A.1.10.2.3.2.1","title":"Smart Contract Deployment Verification","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":377,"content":"For deployments of new modules such as an Allocation System Invocation or SP-BEAM, or to replace an old module, the process outlined in the subdocuments must be followed. The subdocuments provide additional detail regarding the smart contract deployment verification for each step in the Executive Process, where relevant. Unless otherwise stated, the normal process set out in [A.1.10.2.4 - Executive Process Breakdown](98298ab3-8d08-4c4f-b47b-81242a3e3903) applies.","contentHash":"bc4c0bee98990554dc3e00f569bbef3b21319d1b8d6a5eda58203f143b9042af","addressRefs":[]},"9ad39944-b2cf-44ab-872c-a57c7eba1d5a":{"id":"9ad39944-b2cf-44ab-872c-a57c7eba1d5a","doc_no":"A.1.10.2.3.2.1.1","title":"Preparatory Phase for Module Deployment","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":378,"content":"Before the Executive Process begins, the module is implemented, tested, audited, and reviewed by relevant stakeholders to ensure readiness for inclusion. These steps will be further developed in a future iteration of the Atlas. The subdocuments describe the crafting of an Atlas Edit Proposal for a technical deployment.","contentHash":"51b7c55e1176d0336d2ea2ef37217f5bc3ca8246869b61bf3b19cd317f658983","addressRefs":[]},"12a9e981-412d-4d34-b014-5500c33901d4":{"id":"12a9e981-412d-4d34-b014-5500c33901d4","doc_no":"A.1.10.2.3.2.1.1.1","title":"Atlas Crafting Stage","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":379,"content":"The stage of crafting an Atlas Edit Proposal to integrate the module into the Atlas is outlined in the subdocuments herein.","contentHash":"a2f2444b25469d8c0a10d8033b5e9a20b82c2b6308f836ac30337fd70117ddd8","addressRefs":[]},"1ab0de04-ea89-473f-b0b5-5c30219dcde8":{"id":"1ab0de04-ea89-473f-b0b5-5c30219dcde8","doc_no":"A.1.10.2.3.2.1.1.1.1","title":"Atlas Draft","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":380,"content":"Core GovOps Atlas Axis receives a policy document or other relevant documentation explaining the required features and technical specifications of the new module.","contentHash":"f08d3d52eb4236383dceecd2f07ace80cabb77c8fa74f1b0b9ac38d5546e5d27","addressRefs":[]},"7ac692f1-9829-41d8-83d4-4cb1bd053302":{"id":"7ac692f1-9829-41d8-83d4-4cb1bd053302","doc_no":"A.1.10.2.3.2.1.1.1.2","title":"Atlas Edit Review","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":381,"content":"Atlas Axis reviews the provided documentation, ensuring alignment with Atlas standards, and updates the documents as necessary.","contentHash":"fcba6770b54bc98660e9b958c390119e375e0b30b66f874a2b65ad92ef0503d8","addressRefs":[]},"7b41e751-8387-426f-9ff5-e45cc032e172":{"id":"7b41e751-8387-426f-9ff5-e45cc032e172","doc_no":"A.1.10.2.3.2.1.1.1.3","title":"Atlas Edit Sign-Off","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":382,"content":"Atlas Axis shares the draft proposal with the relevant Ecosystem Actors for final review and sign-off, confirming that the proposal meets all requirements and expectations.","contentHash":"d346207e5c490fbb5964a6cc7e2d9fbd3f93ec4a211cd48bc1f28cb357e158cb","addressRefs":[]},"0465a8ef-0ec5-43b7-8b6f-bed778758364":{"id":"0465a8ef-0ec5-43b7-8b6f-bed778758364","doc_no":"A.1.10.2.3.2.1.1.1.4","title":"Atlas Edit Proposal","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":383,"content":"Atlas Axis publishes the proposal as an Atlas Edit Proposal, which is submitted for inclusion in a subsequent Governance Poll to seek community approval for integration into the Atlas.","contentHash":"504ff7cdf7e2c64c46726dfb583ce973edfe26b283743b1d6658782c815ee93a","addressRefs":[]},"8dc369b7-36bd-46f2-b66b-cd336035fa89":{"id":"8dc369b7-36bd-46f2-b66b-cd336035fa89","doc_no":"A.1.10.2.3.2.1.2","title":"Forum Post And Deployment Of Module","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":384,"content":"The module deployment is discussed on the [A.1.10.2.4.3 - Governance Point Conducts GovOps Meeting Week 1 Tuesday (Step 3)](0f74afdf-bc2d-4512-9b11-8f5a26511787) and the actions specified in the subdocuments are taken.","contentHash":"1ac3246f4e1cf1b4d5335d818176c8d18d6b890e61231477e0bbf57ed6baa81d","addressRefs":[]},"769c850b-9e74-4706-bbce-b65c3f47c32c":{"id":"769c850b-9e74-4706-bbce-b65c3f47c32c","doc_no":"A.1.10.2.3.2.1.2.1","title":"Deployment And Forum Post","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":385,"content":"During this stage the module is deployed and a Technical Forum Post is created.","contentHash":"1710ddf185107d09558073f7c37fffa4420980126de193b307429dabb889616a","addressRefs":[]},"22ee3dc8-47e1-4591-b341-ddef5f4a53aa":{"id":"22ee3dc8-47e1-4591-b341-ddef5f4a53aa","doc_no":"A.1.10.2.3.2.1.2.1.1","title":"Module Deployment","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":386,"content":"The module is usually deployed eight or seven days prior to the Spell.","contentHash":"ff0cf7c9d88e4c43d41a0737ca548cb337232ad4924cb9dea0c0137a9a1c4500","addressRefs":[]},"ef6d73e5-cdcb-48dd-873c-264c07af80bf":{"id":"ef6d73e5-cdcb-48dd-873c-264c07af80bf","doc_no":"A.1.10.2.3.2.1.2.1.2","title":"Technical Scope Forum Post","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":387,"content":"The team that implemented and deployed the module publishes a Forum Post with the technical scope. The Spell Team not involved in the technical Forum Post creation must confirm the contents of the Forum Post as a public reply to ensure transparency and independent verification.","contentHash":"99c71a78900d70679c309235dd4d6b0d951fa7d69a868a71efc2c9630cc16765","addressRefs":[]},"3d031b7c-1b1f-4f84-8668-1cdf43cb2ab2":{"id":"3d031b7c-1b1f-4f84-8668-1cdf43cb2ab2","doc_no":"A.1.10.2.3.2.1.2.1.2.1","title":"Requirements For Forum Post","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":388,"content":"The Forum post must include the following:\n\n- The addresses of the deployed contracts\n- A link to the audit reports, ideally externally verifiable sources, such as the Chain Security website link to an audit report.\n- Confirmation that the deployed code matches the commit hash that was sent for audit.\n- Constructor arguments are as expected in the Init script\n- (optional) Authority is given to the protocol owner: `MCD_PAUSE_PROXY` in the case of SKY and denied from the deployer address.\n- Include instructions to be added to the Executive Sheet, such as adding the module to the chainlog, defining parameters for the module (provided by the Risk Advisor), further authorization that needs to be done to different module elements.","contentHash":"d85e8ccad46bf05b65190b061da4b170b5244ec555ef81bcfcc5c128ddbd85ab","addressRefs":[]},"d0c4f880-902e-4d32-ac55-f05725753ac1":{"id":"d0c4f880-902e-4d32-ac55-f05725753ac1","doc_no":"A.1.10.2.3.2.1.2.1.3","title":"Core Facilitator Approve Inclusion In Executive Vote","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":389,"content":"The Core Facilitator should post a reply to the Technical Scope Forum post and approve its inclusion in the next Executive Vote.","contentHash":"c4b514aedb9e59e5345a8561e8e37c72a743b09b1a1e8a7a4339c7129f4cfe02","addressRefs":[]},"5e125907-87f9-4c3a-b1a8-54ad6c204179":{"id":"5e125907-87f9-4c3a-b1a8-54ad6c204179","doc_no":"A.1.10.2.3.2.1.3","title":"Populating Content Regarding Module Deployment In Executive Votes","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":390,"content":"The actions specified herein take place as part of the [A.1.10.2.4.2 - Governance Point Creates Executive Sheet Week 1 Monday (Step 2)](298819fe-cc26-49a8-a7cb-3ff83e55f291) step of the Executive Process.","contentHash":"f6c2775944ab48c605732028a020adb943bcf7d2f04cd55fc4feefbafa3d6ec2","addressRefs":[]},"d2a2b598-db4d-44b5-a23b-a7f62cadfa9d":{"id":"d2a2b598-db4d-44b5-a23b-a7f62cadfa9d","doc_no":"A.1.10.2.3.2.1.3.1","title":"Governance Point Includes Module Deployment In The Executive Sheet","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":391,"content":"The Governance Point should include the module deployment in the Executive Sheet. The \"Input Action\" describes the high level logic of the Deployment, for example \"Add [Module Name] to Chainlog\". The Reasoning URL for the \"Input Action\" should contain a link to the Atlas Edit Proposal Forum post specified in [A.1.10.2.3.2.1.2.1.2 - Technical Scope Forum Post](ef6d73e5-cdcb-48dd-873c-264c07af80bf) and the Authority URL for the \"Input Action\" should contain a link to Atlas documents. The \"Derived Action\" is more specific for deployment address and other necessary information. The Reasoning URL for the \"Derived Action\" should contain a link to the Technical Scope Forum post specified in [A.1.10.2.3.2.1.2.1.2 - Technical Scope Forum Post](ef6d73e5-cdcb-48dd-873c-264c07af80bf) and the Authority URL for the \"Derived Action\" should contain a link to the approval of the Core Facilitator as specified in [A.1.10.2.3.2.1.2.1.3 - Core Facilitator Approve Inclusion In Executive Vote](d0c4f880-902e-4d32-ac55-f05725753ac1).","contentHash":"3cb5115e80cd792487206b5b191e6ed79ccad008e5b52283a99cf002bdd986a0","addressRefs":[]},"10ccad57-0d04-4d95-89d5-1da66e6172f9":{"id":"10ccad57-0d04-4d95-89d5-1da66e6172f9","doc_no":"A.1.10.2.3.2.1.3.2","title":"Confirmation Of Module Deployment In The Executive Sheet","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":392,"content":"The author of the Forum post usually acts as Content Liaison and confirms in the Executive Sheet see [A.1.10.2.4.5.3 - Confirmation By Content Liaisons](26133c1d-29da-42de-b9a2-00f4e13699f2).","contentHash":"de4476f82b60ec3bf60af4dc0ab035fe4cafba768769b82aca5f6aed9bcad187","addressRefs":[]},"fb98f4b8-d45e-47ac-8a88-a3cc1e71c42e":{"id":"fb98f4b8-d45e-47ac-8a88-a3cc1e71c42e","doc_no":"A.1.10.2.3.2.1.4","title":"Populating Content Regarding Module Deployment In Executive Document","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":393,"content":"The actions specified herein take place as part of the [A.1.10.2.4.8 - Core Facilitator Creates And Finalizes Executive Document Week 2 Tuesday (Step 8)](1df24674-3095-44a7-b1b6-cb583b0787dd) step of the Executive Process.","contentHash":"06b7b2cf1a60f08bc6588f5ecb2a34729599c0d4d2eea58c91fb4f87e523311e","addressRefs":[]},"b81371c0-0bfb-4276-9fcb-f333de6e5a3a":{"id":"b81371c0-0bfb-4276-9fcb-f333de6e5a3a","doc_no":"A.1.10.2.3.2.1.4.1","title":"Core Facilitator Includes Module Deployment In The Executive Document","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":394,"content":"The Core Facilitator must include the module deployment in the Executive Document. The format for this content should be as specified below:\n\n- The title of the module deployment should be listed as a section for example \"Add [Module Name] to the Chainlog\".\n- The authorization should include links to the Atlas documents and the approval from the Core Facilitator.\n- The proposal should include links to the Technical Scope Forum post created by the team that deployed the module and the Atlas Edit Proposal.","contentHash":"03daec4f0573a3f92cffa5b295046670abe011d3881a498fea338d2cc0fe522f","addressRefs":[]},"8b5181e8-51e2-4d8b-a49a-d88ab42218e7":{"id":"8b5181e8-51e2-4d8b-a49a-d88ab42218e7","doc_no":"A.1.10.2.3.2.2","title":"Prime Spells","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":395,"content":"This process will be further specified in a future iteration of the Atlas.","contentHash":"853623d2b4c9c6c885c8c39f10af010a78d345cc7186033b829150cae707c9e9","addressRefs":[]},"e44ede45-464e-4a2e-b074-965f7ca1303f":{"id":"e44ede45-464e-4a2e-b074-965f7ca1303f","doc_no":"A.1.10.2.3.2.2.1","title":"Prime Spell Security Enforcement","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":396,"content":"The documents herein define policies and procedures related to enforcement of the Prime Spell Security Process.","contentHash":"665ab94f9d9e1d019c50bd9d2253c84a2d94a7ef865ee63a1693f4fdbdea7043","addressRefs":[]},"0782d6bf-2b71-4a55-b832-cc9f9cca1d82":{"id":"0782d6bf-2b71-4a55-b832-cc9f9cca1d82","doc_no":"A.1.10.2.3.2.2.1.1","title":"Purpose","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":397,"content":"Prime Spell Security Enforcement establishes binding enforcement and formal recordkeeping for Prime Agent Spell security during the period when the Prime Spell Security Framework is progressively codified and operationalized in the Atlas. Its objective is to protect the Executive Process by ensuring that Prime Agents adhere to all applicable security requirements.","contentHash":"2bb915818fcb69768db1dcd733974dcc9a518ea02bda4defd0ac36b143e67472","addressRefs":[]},"0bc23932-cb06-4c48-8bf0-c1628d644a7a":{"id":"0bc23932-cb06-4c48-8bf0-c1628d644a7a","doc_no":"A.1.10.2.3.2.2.1.2","title":"Prime Spell Security Guidelines","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":398,"content":"Prime Spell Security Guidelines are all security guidelines, requirements, and best practices codified in the Atlas or communicated to Prime Agents through the official channels used for Prime operations. These communications include, but are not limited to, (1) designated Signal and Discord channels, (2) documentation authored or provided by Core Spell Teams or other stakeholders, and (3) live calls.","contentHash":"4da772febf417bc2cbd098c3874e7a40a481a072b0f79625517fc99a6b6c40b0","addressRefs":[]},"c14b730a-eea7-4957-9a4b-7994518f3076":{"id":"c14b730a-eea7-4957-9a4b-7994518f3076","doc_no":"A.1.10.2.3.2.2.1.3","title":"Enforcement Authority And Penalties","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":399,"content":"The documents herein define enforcement authority and penalties related to the Prime Spell Security Guidelines.","contentHash":"75ba2155e91a4443e3ab49f7a0f55eee0b98d9d90ff23be903868fb7f9715709","addressRefs":[]},"109ba764-0266-4875-97f1-1de5bd5e6188":{"id":"109ba764-0266-4875-97f1-1de5bd5e6188","doc_no":"A.1.10.2.3.2.2.1.3.1","title":"Obligation To Comply With Prime Spell Security Guidelines","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":400,"content":"Prime Agents must adhere to all Prime Spell Security Guidelines as a condition of inclusion in an Executive Vote.","contentHash":"11341018e8eb0c57339e68e45f8fc9f0c251168e19918b9ff8c68d691d86c9a5","addressRefs":[]},"9433535a-fbda-4c85-8871-5118ce073ca1":{"id":"9433535a-fbda-4c85-8871-5118ce073ca1","doc_no":"A.1.10.2.3.2.2.1.3.2","title":"Prime Spell Security Incidents","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":401,"content":"Any breach by a Prime Agent of the Prime Spell Security Guidelines is designated a \"Prime Spell Security Incident\".","contentHash":"5c875d7c67828d36c9e8caf571bbca79ed80e3499ac3f47d9cd42270320032b2","addressRefs":[]},"b3cd3112-dcc6-46b6-82bf-b99fa73eb6ca":{"id":"b3cd3112-dcc6-46b6-82bf-b99fa73eb6ca","doc_no":"A.1.10.2.3.2.2.1.3.3","title":"Determination Of Occurrence Of Prime Spell Security Incident And Penalties","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":402,"content":"The Core Facilitator and Core GovOps, in consultation with other appropriate stakeholders, have full discretion to determine whether a Prime Spell Security Incident has occurred and to impose appropriate penalties.","contentHash":"c25de97cb09c2dc7e2da7ed6533c5bc76ffa3bf6476ac4aa53ef42f77a30dce5","addressRefs":[]},"20aece61-c81d-44b8-8138-c56ca5364222":{"id":"20aece61-c81d-44b8-8138-c56ca5364222","doc_no":"A.1.10.2.3.2.2.1.3.4","title":"Penalties","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":403,"content":"The penalties for a Prime Spell Security Incident may include, without limitation:\n\n- financial penalties;\n- deprioritization in the Executive Spell queue;\n- exclusion from an upcoming Executive Vote cycle;\n- requirement to obtain additional audits at the Prime’s expense; and\n- suspension or reduction of non‑essential support from the Core Council or the Prime’s Operational Executor Agent.","contentHash":"cec2dd51a1560b0a5e97dfbb2cc576544b996ec19087567f028c926f1e350f00","addressRefs":[]},"3921d0c0-881f-4603-9d27-95d02c042cc1":{"id":"3921d0c0-881f-4603-9d27-95d02c042cc1","doc_no":"A.1.10.2.3.2.2.1.4","title":"Prime Spell Security Incident Registry","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":404,"content":"The documents herein define the Prime Spell Security Incident Registry.","contentHash":"a88e9be403cc1d004a2c3079c7dce2dc8701f9aa7448c41eeea6674e29cfdc02","addressRefs":[]},"13e611c6-f39a-464a-82de-12627204cb29":{"id":"13e611c6-f39a-464a-82de-12627204cb29","doc_no":"A.1.10.2.3.2.2.1.4.1","title":"Process Definition","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":405,"content":"The documents herein define the process for recording Prime Spell Security Incidents in the Prime Spell Security Incident Registry.","contentHash":"d9709af3516eb5995615d0a80db7f0b8a9ab95f6c2ff5ab0852aac57edfb16d1","addressRefs":[]},"8323c8af-7736-482b-b4f2-965bf164ebd9":{"id":"8323c8af-7736-482b-b4f2-965bf164ebd9","doc_no":"A.1.10.2.3.2.2.1.4.1.1","title":"Prime Agent And Operational Executor Agent Produce Prime Spell Security Incident Report","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":406,"content":"After a Prime Spell Security Incident has occurred, the Prime and its Operational Executor Agent must promptly produce a Prime Spell Security Incident Report using the designated template.","contentHash":"fb6f4054838d6e658e43bd039fe9ef4deb2dce7284f7b054d3c7e08aafb93386","addressRefs":[]},"01b44f43-c6e1-4b24-b715-296a5122fb35":{"id":"01b44f43-c6e1-4b24-b715-296a5122fb35","doc_no":"A.1.10.2.3.2.2.1.4.1.1.1","title":"Delay In Submitting Or Failure To Thoroughly And Accurately Complete Report","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":407,"content":"Unreasonable delay in submitting the Report, or failure to thoroughly and accurately complete it (including omission of relevant facts), as determined by the Core Council, constitutes a separate Prime Spell Security Incident and may result in additional penalties.","contentHash":"819de2acc6aaf075082a735318c9ad9da6f8096c07fea6ec4093b6ef57dfa5c0","addressRefs":[]},"e480b8f8-b2dc-4a97-a8c7-1745750a9a83":{"id":"e480b8f8-b2dc-4a97-a8c7-1745750a9a83","doc_no":"A.1.10.2.3.2.2.1.4.1.2","title":"Core Spell Teams Review Prime Spell Security Incident Report","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":408,"content":"The relevant Core Spell Team, on behalf of the Core Council, must review this Incident Report for completeness and accuracy.","contentHash":"4bcc154a000584d1f270501fd254cbeded0552683671a2bdab01ab4b0ed0d725","addressRefs":[]},"0da6c412-56e5-4ee7-bc81-683147442c62":{"id":"0da6c412-56e5-4ee7-bc81-683147442c62","doc_no":"A.1.10.2.3.2.2.1.4.1.3","title":"Core Facilitator Records Prime Spell Security Incident Report In Prime Spell Security Incident Registry","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":409,"content":"All Prime Spell Security Incidents must be recorded by the Core Facilitator in the Incident Registry at [A.1.10.2.3.2.2.1.5.0.6.1 - Prime Spell Security Incidents](7bcaaa37-c914-41a4-b61b-cf3a7eb5438f). Each Registry entry must identify the Prime Agent and its Operational Executor Agent, the incident date(s), a short description of the violation, the penalties imposed, and a link to the corresponding Prime Spell Security Incident Report.","contentHash":"ee3ab81af282da93311e805ac278e2cb329f2f27b3fd9cb3f91bd45df0378bf1","addressRefs":[]},"160bf31b-18c5-4e51-bce4-a1c5630c024e":{"id":"160bf31b-18c5-4e51-bce4-a1c5630c024e","doc_no":"A.1.10.2.3.2.2.1.4.2","title":"Uses Of Prime Spell Security Incident Registry","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":410,"content":"The documents herein define required uses of the Prime Spell Security Registry.","contentHash":"de0924015d7eea4d7d9e91a8160a9c6fe670fcb0e784056dbf7d00f3ebc0cd98","addressRefs":[]},"4c165fcc-59e5-45c8-866d-c5c68192e591":{"id":"4c165fcc-59e5-45c8-866d-c5c68192e591","doc_no":"A.1.10.2.3.2.2.1.4.2.1","title":"Use Of Prime Spell Security Registry In Prime Agent Credit Rating System","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":411,"content":"The Registry shall serve as a critical input to the Prime Agent Credit Rating system and will determine Primes’ Agent Credit Line Borrow Rate when variable pricing is activated pursuant to [A.3.1.2.5.1 - Relationship To Base Rate](4659cbf0-78c2-469b-8432-883e5c931dd1).","contentHash":"88122a091312577c8311523e2c82d437e77535fe734d3f1093c5b54ced30b602","addressRefs":[]},"fd1f682c-2d8a-47c5-8c1d-d95a0a2f2021":{"id":"fd1f682c-2d8a-47c5-8c1d-d95a0a2f2021","doc_no":"A.1.10.2.3.2.2.1.4.2.2","title":"Use Of Prime Spell Security Registry In Risk-Based Pricing Of Insurance","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":412,"content":"Insurance‑related fees charged by a Prime’s Operational Executor shall also be calculated using risk‑based pricing informed by the Prime Spell Security Incident Registry, including the severity, frequency, and recency of incidents.","contentHash":"647e83262bd7223ae4ea6f9e3ea36c2548b17d056bf729c93341ff3885380e7f","addressRefs":[]},"59d5aa08-3314-4ff0-bceb-57f783465e6f":{"id":"59d5aa08-3314-4ff0-bceb-57f783465e6f","doc_no":"A.1.10.2.3.2.2.1.4.2.3","title":"Use Of Prime Spell Security Registry By Prime Agents","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":413,"content":"The documents herein define required uses of the Prime Spell Security Registry by Prime Agents.","contentHash":"4a00a50dec01f98b9c598e244c882573cbbac389b11978992f548cdcdee34ca5","addressRefs":[]},"540e8f4e-0691-435d-bc14-2e4e07d3e39e":{"id":"540e8f4e-0691-435d-bc14-2e4e07d3e39e","doc_no":"A.1.10.2.3.2.2.1.4.2.3.1","title":"Review Of Prime Spell Security Registry By Prime Agents","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":414,"content":"Prime Agents are expected to review the Prime Spell Security Incident Registry on an ongoing basis and to independently incorporate mitigations and controls based on relevant prior incidents into their Spell-development related processes.","contentHash":"dee199d779b3398b6f9c0857418bb54a7190cb094a8ce8d41c98ea682713d9e2","addressRefs":[]},"9555c38c-fc75-4f5e-bbbb-70ebd5b7453a":{"id":"9555c38c-fc75-4f5e-bbbb-70ebd5b7453a","doc_no":"A.1.10.2.3.2.2.1.4.2.3.2","title":"Escalated Penalties For Similar Prime Spell Security Incidents","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":415,"content":"Where a new Prime Spell Security Incident reflects the same or a substantially similar circumstance as a previous Incident in the Registry, the new Incident shall be subject to an escalation multiplier applied to its financial penalty, as determined by the Core Council. This applies regardless of whether the earlier Incident involved the same Prime.","contentHash":"db4752cc3a24ec8758dc414dac3a6cd003e0b0b9c1594264434dd5c02ce7340e","addressRefs":[]},"a2777f65-6340-46c2-b0f3-95a63fef2f8a":{"id":"a2777f65-6340-46c2-b0f3-95a63fef2f8a","doc_no":"A.1.10.2.3.2.2.1.5","title":"Prime Spell Security Incident Registry","type":"Active Data Controller","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":416,"content":"Prime Spell Security Incidents are recorded as Active Data in [A.1.10.2.3.2.2.1.5.0.6.1 - Prime Spell Security Incidents](7bcaaa37-c914-41a4-b61b-cf3a7eb5438f).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Facilitator.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"71f8a4a2fffe9a438313f44e65b3610563173f5bda3b1ee6c270cab1e92a4a05","addressRefs":[]},"7bcaaa37-c914-41a4-b61b-cf3a7eb5438f":{"id":"7bcaaa37-c914-41a4-b61b-cf3a7eb5438f","doc_no":"A.1.10.2.3.2.2.1.5.0.6.1","title":"Prime Spell Security Incidents","type":"Active Data","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":417,"content":"The Prime Spell Security Incidents that have occurred to date are:\n\n- None","contentHash":"a93857f4250587331c6821f4856daf3bca1b9710656609b9d92764be50d2296d","addressRefs":[]},"9b3edbbf-89d1-42da-a9c3-18f858f8471f":{"id":"9b3edbbf-89d1-42da-a9c3-18f858f8471f","doc_no":"A.1.10.2.3.2.2.2","title":"Interim Deployments","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":418,"content":"Prime Agents are allowed to deploy a new Allocation Instance on-chain and allocate capital through it under constrained testing conditions, prior to completing a full risk assessment. Such deployments are termed \"Interim Deployments\". Interim Deployments are otherwise subject to the customary requirements of the Sky Core Executive Spell and Prime Proxy Spell process.","contentHash":"8ef6dcaa59ad97732e5d78a40a3bd95bd1525b1a09add536f620f7062a76db4e","addressRefs":[]},"db6f880b-17d9-41b0-8940-5afdeda1e7f1":{"id":"db6f880b-17d9-41b0-8940-5afdeda1e7f1","doc_no":"A.1.10.2.3.2.2.2.1","title":"Process Definition","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":419,"content":"The documents herein define the process for Interim Deployments.","contentHash":"f918a2956dd7e28a37088610f8cc1a7a96ac30a733e459111f8451d0c994604e","addressRefs":[]},"de77dbbc-8ff6-44c7-814c-9ee10ca7a543":{"id":"de77dbbc-8ff6-44c7-814c-9ee10ca7a543","doc_no":"A.1.10.2.3.2.2.2.1.1","title":"Forum Post By Prime Agent","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":420,"content":"The technical implementation of Interim Deployments must successfully complete all required external audits before the Prime can post its Interim Deployment proposal to the Forum.","contentHash":"cfa984b7dbe0821bb94389e7cb1da0ea252fcd06e15c704019848f59c04f95ff","addressRefs":[]},"a93952b9-b9c3-45eb-8169-abd0153d3df4":{"id":"a93952b9-b9c3-45eb-8169-abd0153d3df4","doc_no":"A.1.10.2.3.2.2.2.1.2","title":"Specification Of Testing Parameters By Core Council Risk Advisor","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":421,"content":"Once posted to the Forum, the Core Council Risk Advisor must respond on the Forum thread specifying testing parameters that will govern the Interim Deployment, including maximum exposure and rate limits. The Prime must maintain 100% Instance Capital Requirement Ratio for all Interim Deployments.","contentHash":"95897ab49f953f3332b5628d8befb0bbed7ee9bf84cef7ed986cecbdbb4f919d","addressRefs":[]},"0c0e09e7-4cbf-4a6f-acfa-0c13c67abca1":{"id":"0c0e09e7-4cbf-4a6f-acfa-0c13c67abca1","doc_no":"A.1.10.2.3.2.2.2.1.3","title":"Submission Of Artifact Edit Proposal By Governance Actor","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":422,"content":"Subsequently, the appropriate Governance Actor must submit an Artifact Edit Proposal incorporating the approved testing parameters into the Prime’s Artifact.","contentHash":"4a15699387f3777aa167f66079177b52b650ffb164314b40f0c9defd02f34eea","addressRefs":[]},"1fc1ba29-9273-4d95-b1a5-bdfc61ebf2ab":{"id":"1fc1ba29-9273-4d95-b1a5-bdfc61ebf2ab","doc_no":"A.1.10.2.3.2.2.2.1.4","title":"Artifact Update","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":423,"content":"Upon successful conclusion of the Artifact Edit Poll, the Prime's Agent Artifact is updated with a new Instance Configuration Document codifying the Deployment’s approved interim testing parameters and other basic data.","contentHash":"2eca7bb04abaf70828fee975fc24ffd6dc27ff50d0962a1d14cfb4e4fa69e579","addressRefs":[]},"fe8e5e31-fc3a-4631-894c-890cb6c82d81":{"id":"fe8e5e31-fc3a-4631-894c-890cb6c82d81","doc_no":"A.1.10.2.3.2.2.2.1.5","title":"Inclusion Of Interim Deployment In Sky Core Executive Cycle","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":424,"content":"The approved Artifact Edit Poll and resulting Instance Configuration Document serve as provenance authorizing the inclusion of the Interim Deployment into the Sky Core Executive Cycle.","contentHash":"108c7b87c77887768c69cea409840cd05b7818ef62baac71db08e00c8dd66867","addressRefs":[]},"14954d6a-0b97-45bf-8734-1e50af8f9ca7":{"id":"14954d6a-0b97-45bf-8734-1e50af8f9ca7","doc_no":"A.1.10.2.3.2.2.2.1.6","title":"Creation Of Public Information Dashboard","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":425,"content":"The Prime Agent must create a publicly available information dashboard through a platform such as Dune showing, at a minimum, the current exposure to the Interim Deployment. This requirement is waived if the Core Council Risk Advisor has already included the Interim Deployment in the publicly available information dashboard at https://info.sky.money.","contentHash":"75bab5f99980c99a2706adad657f7d23af872d374671eea915737dbf5efefe84","addressRefs":[]},"02cb6865-6e41-4465-a1b2-bbeededd9258":{"id":"02cb6865-6e41-4465-a1b2-bbeededd9258","doc_no":"A.1.10.2.3.2.2.2.1.7","title":"Prime Agent Usage Of Interim Deployment","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":426,"content":"Once the Interim Deployment has been deployed and all requirements above have been satisfied, the Prime Agent may begin using it subject to the approved testing parameters.","contentHash":"7bbacbaed3cbec628479ae79044833e1d73585893807dd5877f449e8907d8b2f","addressRefs":[]},"b405eadc-2538-44fc-9b7a-31d45ab601c7":{"id":"b405eadc-2538-44fc-9b7a-31d45ab601c7","doc_no":"A.1.10.2.3.2.2.2.1.8","title":"Completion Of Full Risk Assessment","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":427,"content":"Following the Interim Deployment, the Prime will work with the Core Council Risk Advisor to complete a full risk assessment. Once the means to calculate an official Capital Requirement Ratio for the deployment has been determined, the Prime can request that Core GovOps propose a subsequent Atlas Edit Proposal to lift the testing constraints and reduce the RRC to the Atlas-calculated value.","contentHash":"7236ff0e0fa5deae08ed0fe12cdb33224e05aa737a5de709d0dbd396da318f72","addressRefs":[]},"a67d672a-83f4-46db-adfc-f08004d3f152":{"id":"a67d672a-83f4-46db-adfc-f08004d3f152","doc_no":"A.1.10.2.3.2.2.3","title":"Prime Spell Process Breakdown","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":428,"content":"The documents herein define the Prime Spell Process, the end-to-end procedure through which Prime Agents bring proposed actions through governance and into Sky Core Spells for on-chain execution. The Prime Spell Process spans four (4) weeks, from initial proposal through publication of the Sky Core Spell that includes the Prime Spell payload.\n\nTwo governance paths are accommodated. The Sky Governance path applies to Prime Agents whose Root Edit Primitive is not yet operational; in this state, Prime Spell content is ratified through the Sky Core Atlas Edit Proposal process as specified in [A.2.2.5.2.3.2 - Atlas Edit Proposal Process For Prime Agents](364e52eb-4529-46a9-9852-edaaab88baeb). The Independent Governance path applies to Prime Agents whose Root Edit Primitive is operational; in this state, Prime Spell content is ratified through the voting process defined in the Prime Agent's [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d). Any divergences between the governance paths are specified in the relevant sections.\n\nThe Prime Spell Process is organized into four (4) phases, one per week, specified in the subdocuments herein.","contentHash":"a28951028815863d3de702b5142976664d4a83bb87866dace7af99aecabd1fda","addressRefs":[]},"7434d8aa-c44c-43db-9269-97e254e26ec7":{"id":"7434d8aa-c44c-43db-9269-97e254e26ec7","doc_no":"A.1.10.2.3.2.2.3.1","title":"Step 1: Propose And Prioritize (Week 0)","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":429,"content":"During week 0 of the Prime Spell Process, the Prime Agent's proposed Prime Spell content for the upcoming Executive Vote cycle is submitted, prioritized, and approved, as specified in the subdocuments herein.","contentHash":"bd5cff68faf9dc0f9d3748056238fdb05124fb4f936a8caa7c90b467b5c892a7","addressRefs":[]},"20ff0ea2-9ed2-40b9-8dc5-eb2f1504ed03":{"id":"20ff0ea2-9ed2-40b9-8dc5-eb2f1504ed03","doc_no":"A.1.10.2.3.2.2.3.1.1","title":"Prime Agent Submits Prime Spell Form","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":430,"content":"The Prime Agent submits a Prime Spell Form to the Executive Process Liaison by Monday, 16:00 UTC of week 0. The Prime Spell Form initiates the Prime Spell Process for the upcoming Executive Vote cycle and specifies the proposed Prime Spell content. The Prime Agent must include the complexity score calculation for the proposed Prime Spell content in the Prime Spell Form.","contentHash":"f5dd4707caed095a1280f0f951526a718f5a1ec6b355cff3195537d52454f103","addressRefs":[]},"e55cfedb-546b-47ba-bc46-e07764f44527":{"id":"e55cfedb-546b-47ba-bc46-e07764f44527","doc_no":"A.1.10.2.3.2.2.3.1.2","title":"Executive Process Liaison Delivers Items To Core Council Tracker","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":431,"content":"The Executive Process Liaison reviews the submitted Prime Spell Form for completeness and clarity, and discusses possible Prime Spell content and potential blockers with the Prime Agent. The Executive Process Liaison must verify the Prime Agent's complexity score calculation. The Executive Process Liaison must deliver the items, including the verified complexity score, to the Core Council Tracker by Wednesday, 16:00 UTC of week 0.","contentHash":"7936b9a3ece6b5f4725d952f06235ad452c3b68f53756c7f2baead3d0b049600","addressRefs":[]},"6bde7e9e-b492-4f9c-813a-986b24bc540b":{"id":"6bde7e9e-b492-4f9c-813a-986b24bc540b","doc_no":"A.1.10.2.3.2.2.3.1.3","title":"Core Council Risk Advisor Conducts Pre-Risk Review","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":432,"content":"After the items are delivered to the Core Council Tracker, the [A.1.8.1.1 - Core Council Risk Advisor](d80c8f64-b3f6-430d-bf62-8e50a3783e73) conducts a pre-risk review of the proposed Prime Spell content. The pre-risk review identifies any preliminary risk concerns that should inform the Strategic Team's approval of Spell scope. The pre-risk review must be completed before the Strategic Team approval specified in [A.1.10.2.3.2.2.3.1.4 - Strategic Team Approves Spell Scope](05e33459-9ee6-430c-af72-13db2004c505).","contentHash":"e46b6d6abf02397d1049dea319c10b1161c5d98c4a75ad889efed4ed2d68dd1a","addressRefs":[]},"05e33459-9ee6-430c-af72-13db2004c505":{"id":"05e33459-9ee6-430c-af72-13db2004c505","doc_no":"A.1.10.2.3.2.2.3.1.4","title":"Strategic Team Approves Spell Scope","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":433,"content":"The Strategic Team reviews the items and approves the scope of Prime Agent content to be advanced through the Prime Spell Process for the upcoming Executive Vote cycle. The approval reflects the Strategic Team's assessment of business needs and strategic alignment with the Sky Ecosystem's broader objectives. Approval must be completed by end of Friday of week 0.","contentHash":"f53929452a628f8c758088bee94e2b4f4b552ce475c7e098ccdf203c56bae2f3","addressRefs":[]},"194654c4-1837-40f3-bd4d-97a63bda8362":{"id":"194654c4-1837-40f3-bd4d-97a63bda8362","doc_no":"A.1.10.2.3.2.2.3.1.5","title":"Communication Of Approved Scope","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":434,"content":"Following the Strategic Team's approval as specified in [A.1.10.2.3.2.2.3.1.4 - Strategic Team Approves Spell Scope](05e33459-9ee6-430c-af72-13db2004c505), the Executive Process Liaison should communicate the approved scope to the Prime Agent and the Core Council Risk Advisor.","contentHash":"d37a0f69305ade7d04ea82a555c911d28e56b1b534913d7ca72fe6a5802e9507","addressRefs":[]},"a1dd34d4-7e15-491c-89a5-fe344ebc3299":{"id":"a1dd34d4-7e15-491c-89a5-fe344ebc3299","doc_no":"A.1.10.2.3.2.2.3.2","title":"Step 2: Finalize Scope (Week 1)","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":435,"content":"During week 1 of the Prime Spell Process, the scope of approved Prime Spell content is finalized through Forum publication, risk review, and Atlas Edit Proposal submission, as specified in the subdocuments herein.","contentHash":"d3a2d48070d070c87855f9172eec08da98022f6fa92ed26d82e0dfa7afc21034","addressRefs":[]},"a6d4afac-add5-4af9-833a-e3f8785ec94c":{"id":"a6d4afac-add5-4af9-833a-e3f8785ec94c","doc_no":"A.1.10.2.3.2.2.3.2.1","title":"Pre-Publication Review Of Forum Posts","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":436,"content":"Prior to publication of Forum posts as specified in [A.1.10.2.3.2.2.3.2.2 - Prime Agent Publishes Spell Actions On Sky Forum](2c577553-830f-4b9f-ab5f-dddd0fd62cfa), the Prime Agent must complete an internal review of the draft posts by at least one member of the Prime Agent's team independent of the action's author. The Executive Process Liaison then reviews the draft posts and verifies that the internal review has been completed. For actions involving Allocations, the Executive Process Liaison must validate the destination deposit addresses using offchain systems.","contentHash":"fb2d08dd65d65d008d36fbdc332263c5119331998b25473ca2ad539a88c156c8","addressRefs":[]},"2c577553-830f-4b9f-ab5f-dddd0fd62cfa":{"id":"2c577553-830f-4b9f-ab5f-dddd0fd62cfa","doc_no":"A.1.10.2.3.2.2.3.2.2","title":"Prime Agent Publishes Spell Actions On Sky Forum","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":437,"content":"Each proposed Prime Spell action must be included in a Forum post on the Sky Forum. Each Forum post must contain the Technical Scope, the Financial Risk Assessment, and, if relevant, a Technical Risk Assessment.\n\nUnder the Sky Governance path, the Forum posts must be published by Wednesday, 16:00 UTC of week 1.\n\nUnder the Independent Governance path, the Forum posts must be published by end of Friday of week 1.","contentHash":"4f4d25743983f5a77499d32f1005b0d712ed80ed1c5fd0486a6ddec27210f9d0","addressRefs":[]},"f2e395a1-a532-401a-ac15-b29d27916473":{"id":"f2e395a1-a532-401a-ac15-b29d27916473","doc_no":"A.1.10.2.3.2.2.3.2.3","title":"Risk Assessment Review","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":438,"content":"The items included in the Prime Agent's Forum posts must undergo a financial risk assessment.\n\nUnder the Sky Governance path, the financial risk assessment is conducted by the [A.1.8.1.1 - Core Council Risk Advisor](d80c8f64-b3f6-430d-bf62-8e50a3783e73). The assessment must be posted on the Forum thread by Thursday, 16:00 UTC of week 1.\n\nUnder the Independent Governance path, the financial risk assessment is conducted by an independent risk assessor designated by the Prime Agent.","contentHash":"4c4f3d924132a66a602b0db342c53aa5b78d5baed54c9ca97f6081ee8081b688","addressRefs":[]},"0c442b02-f6c9-4bb2-af7f-f73ee31d9b1f":{"id":"0c442b02-f6c9-4bb2-af7f-f73ee31d9b1f","doc_no":"A.1.10.2.3.2.2.3.2.4","title":"Atlas Edit Proposal Drafting And Submission","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":439,"content":"The Edit Proposal codifying the Prime Spell content for the cycle is drafted and submitted.\n\nUnder the Sky Governance path, Atlas Axis drafts the Atlas Edit Proposal codifying the Prime Spell content into the Atlas and shares it with the Prime Agent for sign-off by Thursday, 18:00 UTC of week 1. The signed-off Atlas Edit Proposal should then be submitted by Friday, 08:00 UTC of week 1, in accordance with [A.1.11.2 - Atlas Edit Weekly Cycle](14e99d92-71fc-44d9-9dbf-933bce2e1b32).\n\nUnder the Independent Governance path, the Operational Facilitator prepares and submits the Agent Artifact Edit Proposal codifying the Prime Spell content into the Prime Agent's Artifact, in accordance with the process defined in the Prime Agent's [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"3d294960fc20dc5683bab3c0a8109718b3bce7c13847dfd492ee78c4f2da0037","addressRefs":[]},"20bb8eaf-c9bc-4fde-9eec-5f6a67e0ca0f":{"id":"20bb8eaf-c9bc-4fde-9eec-5f6a67e0ca0f","doc_no":"A.1.10.2.3.2.2.3.3","title":"Step 3: Governance (Week 2)","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":440,"content":"During week 2 of the Prime Spell Process, the Edit Proposal is voted on, the Prime Spell payload is reviewed and delivered, and approved content is ratified into the Atlas or applicable Agent Artifact, as specified in the subdocuments herein.","contentHash":"404a38ba133d6a3385727f822c3e7c38a76dd3a79f26c3f92135d53e57f7f812","addressRefs":[]},"b7e93d92-b433-40dd-bf6b-86a49b7ce9c6":{"id":"b7e93d92-b433-40dd-bf6b-86a49b7ce9c6","doc_no":"A.1.10.2.3.2.2.3.3.1","title":"Prime Agent Delivers Signed-Off Prime Spell For Review","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":441,"content":"By Monday, 08:00 UTC of week 2, the Prime Agent must deliver a signed-off Prime Spell Pull Request ready for external review. The internal review by the Prime Agent's team must be completed before this delivery.","contentHash":"5209448e020bd817d14395613a8f6fdee49659508f8cbe086b9fa9e57281ba38","addressRefs":[]},"6457578f-cf6f-4caa-8abb-9774c560dfcf":{"id":"6457578f-cf6f-4caa-8abb-9774c560dfcf","doc_no":"A.1.10.2.3.2.2.3.3.2","title":"Governance Vote","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":442,"content":"The governance vote on the Edit Proposal is published on Monday, 16:00 UTC of week 2 and runs through Thursday of week 2.\n\nUnder the Sky Governance path, the Core Facilitator publishes the Governance Poll on the Sky voting portal, in accordance with [A.1.11.2 - Atlas Edit Weekly Cycle](14e99d92-71fc-44d9-9dbf-933bce2e1b32). Aligned Delegates vote on the Governance Poll.\n\nUnder the Independent Governance path, the Operational Facilitator initiates the vote in accordance with the voting process defined in the Prime Agent's Root Edit Primitive. The Prime Agent's token holders vote in accordance with that process.","contentHash":"c344d8e5e70635d1098f39e790ac28b27bc7e19a0c99498e8a1330b42660202c","addressRefs":[]},"d09636ee-de88-4134-9a00-0c3de80ca060":{"id":"d09636ee-de88-4134-9a00-0c3de80ca060","doc_no":"A.1.10.2.3.2.2.3.3.3","title":"Prime Spell Review","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":443,"content":"The Prime Spell delivered in [A.1.10.2.3.2.2.3.3.1 - Prime Agent Delivers Signed-Off Prime Spell For Review](b7e93d92-b433-40dd-bf6b-86a49b7ce9c6) must be externally reviewed during week 2, before the Prime Spell payload delivery specified in [A.1.10.2.3.2.2.3.3.6 - Prime Agent Delivers Prime Spell Payload](d5223f2c-264f-47da-9e59-2574bdf9cfc2). The reviewer must be either a member of a Core Spell Team that is not also serving as the Crafter for the Sky Core Spell of the same Executive Vote cycle, or an external reviewer engaged for the purpose.","contentHash":"7a8145e80058653047b101bb8bfa6f43434692e9df4d326fafedf51a2341de49","addressRefs":[]},"3fe0d011-c7e9-4825-8b74-532e0e2f68f6":{"id":"3fe0d011-c7e9-4825-8b74-532e0e2f68f6","doc_no":"A.1.10.2.3.2.2.3.3.4","title":"Sky Core GovOps Meeting","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":444,"content":"The Sky Core GovOps meeting on Tuesday of week 2 includes review of the Prime Spell content alongside Sky Core content for the same Executive Vote cycle. The meeting itself is conducted as specified in [A.1.10.2.4.3.1 - GovOps Meeting](b0d1a683-3b92-4283-8e32-22251192a716). The Executive Process Liaison attends the meeting alongside the Core Facilitator, the Sky Core Spell Team, and the relevant Content Liaisons to represent the Prime Agent's interests in the cycle.","contentHash":"61a5d189547606a6d1949d58112c389e2df3bac95644161e72e67b70ade1f528","addressRefs":[]},"6e254deb-fe5d-4345-8916-bce01463fee5":{"id":"6e254deb-fe5d-4345-8916-bce01463fee5","doc_no":"A.1.10.2.3.2.2.3.3.5","title":"Vote Outcome And Atlas Or Artifact Update","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":445,"content":"If the governance vote passes, the approved Edit Proposal must be incorporated into the Atlas or applicable Agent Artifact by Thursday, 23:59 UTC of week 2, establishing the provenance for the Prime Spell to be included in the Sky Core Executive Vote.\n\nUnder the Sky Governance path, the Core Facilitator and Atlas Axis incorporate the approved Atlas Edit Proposal into the Atlas.\n\nUnder the Independent Governance path, the Operational Facilitator incorporates the approved Agent Artifact Edit Proposal into the Prime Agent's Artifact.","contentHash":"a6acc03433116866125c1a4557b9f0eb0a31cf5bea8414367fb8c1b9fe0b97ea","addressRefs":[]},"d5223f2c-264f-47da-9e59-2574bdf9cfc2":{"id":"d5223f2c-264f-47da-9e59-2574bdf9cfc2","doc_no":"A.1.10.2.3.2.2.3.3.6","title":"Prime Agent Delivers Prime Spell Payload","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":446,"content":"By Friday, 16:00 UTC of week 2, the Prime Agent must deliver the final Prime Spell payload in the #govops Discord channel. The delivery must include the Prime Spell address, codehash, and execution type. The execution type must be specified in accordance with [A.1.10.2.3.2.3 - Execution Of Agent Spells](5b0fd894-094e-4b0c-91ca-c5b59b710c0c).","contentHash":"ea5384d9faaf410f2b605f3dfd2acb0cfc06bdca829f0b294bce6f27d24df04e","addressRefs":[]},"0dbdbcca-5c94-448c-9ac4-03b53c58065d":{"id":"0dbdbcca-5c94-448c-9ac4-03b53c58065d","doc_no":"A.1.10.2.3.2.2.3.3.7","title":"Prime Spell Recorded In Executive Sheet","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":447,"content":"By Friday, 16:00 UTC of week 2, the Core Facilitator must record the Prime Spell address, codehash, and execution type in the Executive Sheet for the corresponding Executive Vote. The Executive Process Liaison must confirm the recorded Prime Spell address against the address delivered by the Prime Agent in [A.1.10.2.3.2.2.3.3.6 - Prime Agent Delivers Prime Spell Payload](d5223f2c-264f-47da-9e59-2574bdf9cfc2).","contentHash":"2a80d70c5cf49fcb80a3ae9b83e0cd8076a600459dee50e5e1bf31e1a3699b1f","addressRefs":[]},"655923b3-0d0c-43da-898b-9adc71ae3e7e":{"id":"655923b3-0d0c-43da-898b-9adc71ae3e7e","doc_no":"A.1.10.2.3.2.2.3.4","title":"Step 4: Crafting And Publication (Week 3)","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":448,"content":"During week 3 of the Prime Spell Process, a retrospective on the cycle is held and the Prime Spell payload is incorporated into the Sky Core Spell and published, as specified in the subdocuments herein.","contentHash":"b1f14f501092e429b940bb3b5a45811d4dcc9a8a23ae291533698ba44250b2d9","addressRefs":[]},"8fae9a59-4764-4c49-a1e6-49111c5dd5f9":{"id":"8fae9a59-4764-4c49-a1e6-49111c5dd5f9","doc_no":"A.1.10.2.3.2.2.3.4.1","title":"Prime Spell Retrospective","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":449,"content":"A retrospective on the Prime Spell Process for the cycle is held on Monday of week 3, attended by the Executive Process Liaison, the Prime Agent, and the Prime Spell reviewer designated in [A.1.10.2.3.2.2.3.3.3 - Prime Spell Review](d09636ee-de88-4134-9a00-0c3de80ca060). The Prime Spell reviewer scores the review for purposes of evolving the complexity scoring system. The Executive Process Liaison must follow up on any discrepancy between the Prime Agent's complexity score calculation and the reviewer's assessment.","contentHash":"af8194963c4503cdee848fe2bf78648549bfb27c9f537213cc99f799ab62560e","addressRefs":[]},"f507d715-a2ea-484c-8a99-979f69a7772c":{"id":"f507d715-a2ea-484c-8a99-979f69a7772c","doc_no":"A.1.10.2.3.2.2.3.4.2","title":"Sky Core Spell Crafting And Publication","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":450,"content":"The Sky Core Spell that includes the Prime Spell payload is crafted, reviewed, and published during week 3, as specified in [A.1.10.2.4.7 - Spell Crafter Crafts Spell Week 2 Monday (Step 7)](60aac647-4fa3-4c1c-b9d4-8ababf001958) through [A.1.10.2.4.13 - Spell Execution Process And Retro (Step 13)](761cd866-17a9-47f5-8ae6-ab1788371be1) of the Sky Core Executive Process Breakdown.","contentHash":"ef9fa2bb2675241ee253f05bbbc31ccb008a228a381a4d114faf94f0db51e7b7","addressRefs":[]},"5b0fd894-094e-4b0c-91ca-c5b59b710c0c":{"id":"5b0fd894-094e-4b0c-91ca-c5b59b710c0c","doc_no":"A.1.10.2.3.2.3","title":"Execution Of Agent Spells","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":451,"content":"The execution of Agent Spells is described in the subdocuments herein. Two methods are available: direct execution in a Sky Core Spell and execution through StarGuard. Execution through StarGuard is the preferred method and any exceptions require valid reasoning.","contentHash":"c24ff7e522882b7cefc4666f957b1d7c7d88ae3588aa2638e464ce422c5f8eab","addressRefs":[]},"78ec918d-cd9e-4326-bfa9-ab338e658a8b":{"id":"78ec918d-cd9e-4326-bfa9-ab338e658a8b","doc_no":"A.1.10.2.3.2.3.1","title":"Execution Through StarGuard","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":452,"content":"When the execution through the StarGuard method is used, the Agent Spells are whitelisted in Sky Core Spells and later executed using the StarGuard module. The Sky Core Spell includes a whitelist of approved Agent Spells, which allows them to be executed via separate transactions. This enhances resilience and scalability, ensuring robust handling of payloads from multiple active Agents while minimizing risks to Sky Core.","contentHash":"9987cda589b5189344ff47212c2154dfca65c2b6dce3b305fb03abf693fb572a","addressRefs":[]},"e5cbb61a-82c3-4fce-b6f2-191911d5c155":{"id":"e5cbb61a-82c3-4fce-b6f2-191911d5c155","doc_no":"A.1.10.2.3.2.3.1.1","title":"StarGuard","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":453,"content":"For each Agent, a `StarGuard` contract is deployed to manage whitelisting and execution of Agent Spells. This contract acts as a standardized \"proxy wrapper\".","contentHash":"c723caffde6cfa881f4221df881cfa21a5ecb686d9838bded05ce473c79223c2","addressRefs":[]},"3123f615-d7a0-41a9-9285-e698cae6ee9a":{"id":"3123f615-d7a0-41a9-9285-e698cae6ee9a","doc_no":"A.1.10.2.3.2.3.1.1.1","title":"StarGuard Deployment","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":454,"content":"For each new SubProxy, the StarGuard contract should be deployed and initialized in the same Spell and added to the keeper job, StarGuardJob.","contentHash":"d212e23d2dbd56d20f6a9f98f49c594c8d1b8b61a1cde01ca60b9a9d09e1d78e","addressRefs":[]},"04712596-beda-452e-a667-44e6fe707abd":{"id":"04712596-beda-452e-a667-44e6fe707abd","doc_no":"A.1.10.2.3.2.3.1.1.2","title":"StarGuard Functionality","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":455,"content":"When initiated in a Sky Core Spell, the StarGuard whitelists relevant Agent Spells, enabling their secure execution. This whitelisting allows Agent Spells to run independently, supporting arbitrary complexity and custom features like office hours or expiration times. StarGuard also supports dropping a whitelisted Agent Spell, providing a mechanism to revoke access if needed for security or error correction. This is done via the `drop()` function.","contentHash":"bc5a9730dcb6751f10283bcb589029c4db4e22b7471bc79b4a500c9a9c4ef4a5","addressRefs":[]},"e6ec35bc-28af-4e06-bc92-c8706add6017":{"id":"e6ec35bc-28af-4e06-bc92-c8706add6017","doc_no":"A.1.10.2.3.2.3.1.1.2.1","title":"StarGuard Ownership","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":456,"content":"The StarGuard contract is owned by the Pause Proxy, ensuring centralized control and preventing unauthorized changes.","contentHash":"9b9a3cd3904979aafeea6a04594c33a28ab2a9c7e8b93c2bb3d6f1347375d095","addressRefs":[]},"3deb3282-434c-4d56-b5e3-3a4daad3cd1d":{"id":"3deb3282-434c-4d56-b5e3-3a4daad3cd1d","doc_no":"A.1.10.2.3.2.3.1.1.2.2","title":"Responsibilities For Agents","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":457,"content":"The Agents are required to include logic for the public view method `isExecutable()` in their Spell. This function is used to signal if the Spell is ready to be executed in a particular block or not. StarGuard cannot execute an Agent Spell if `isExecutable()` returns `False`. The value that must be returned for execution to be possible is `True`.","contentHash":"623930e57387dc9f28cd42d37c074a068bf26091d65e41dc772aaa604c3a6cb5","addressRefs":[]},"f23f9ea7-64e1-4083-93b8-2864b232f451":{"id":"f23f9ea7-64e1-4083-93b8-2864b232f451","doc_no":"A.1.10.2.3.2.3.1.1.2.3","title":"StarGuard Whitelisting Authority","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":458,"content":"Only the owner, the Pause Proxy, is able to whitelist new Agent Spells via a Sky Core Spell.","contentHash":"6a0eecdf6004fbc82e1c9cc6e99798e445b727ba9ed0ae89e17ee6ac3684e9f0","addressRefs":[]},"ccb1f61a-660b-4a8a-976f-53915dd21b03":{"id":"ccb1f61a-660b-4a8a-976f-53915dd21b03","doc_no":"A.1.10.2.3.2.3.1.1.2.4","title":"StarGuard Max Delay","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":459,"content":"A configurable `maxDelay` sets the maximum duration between the whitelisting of the Agent Spell in the Sky Core Spell and the execution of the Agent Spell. This feature ensures Spells do not linger indefinitely, enforcing timely processing and reducing risks from delayed or forgotten actions. The recommended value for `maxDelay` is seven (7) days.","contentHash":"dc8a7f08f17c8b2a373ca315f6469d0a3e44206fbafc87cec1f8b24fd4804dd5","addressRefs":[]},"a03c9e5a-4fe4-46a2-8ec6-f8900ed90f47":{"id":"a03c9e5a-4fe4-46a2-8ec6-f8900ed90f47","doc_no":"A.1.10.2.3.2.3.1.1.2.5","title":"Requirements For Whitelisting","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":460,"content":"The requirements for whitelisting are:\n\n- The address of the Agent Spell.\n- The codehash of the Spell's bytecode.\n- Confirmation that direct execution is not needed. If direct execution is needed, a valid reason must be provided.\n\nThis information must be provided by the Agent Spell reviewers to the Governance Point.","contentHash":"9c00b393302c8ac7090e88277846b145f3cdcf243bd7a8fb813f1a903b8cf307","addressRefs":[]},"50f71e34-6705-4ccb-a911-3797b05f422f":{"id":"50f71e34-6705-4ccb-a911-3797b05f422f","doc_no":"A.1.10.2.3.2.3.1.1.2.6","title":"Permissionless Execution","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":461,"content":"The triggering of an Agent Spell is permissionless; anyone can initiate execution. A keeper job, StarGuardJob, allows keepers to monitor and execute eligible Spells at the earliest possible block.","contentHash":"0191a37d276667cd79d2ddc0d9e7cf2715106404fbe331e75b5793ab54d4449b","addressRefs":[]},"8113159f-dcf6-4c44-afb0-aed09b1e5cf7":{"id":"8113159f-dcf6-4c44-afb0-aed09b1e5cf7","doc_no":"A.1.10.2.3.2.3.1.1.2.7","title":"Function Call For Execution","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":462,"content":"Execution is initiated on the StarGuard contract via its `exec()` function, which performs necessary validation checks before calling the SubProxy’s `exec(spellDataCopy.addr, abi.encodePacked(StarSpellLike.execute.selector))` to perform the Spell's actions.","contentHash":"740440d4f1a262caccd8177d0368f75d69705cfab08af0526f51c66933886046","addressRefs":[]},"e15ea323-038d-4935-a39e-295c152251da":{"id":"e15ea323-038d-4935-a39e-295c152251da","doc_no":"A.1.10.2.3.2.3.1.1.2.7.1","title":"Validation Checks By StarGuard","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":463,"content":"The following checks are enabled by the contract:\n\n- Verifies that the whitelisted Spell is executable only once, enforcing single-use to prevent replay attacks or unauthorized repeats.\n- Verifies that the whitelisted bytecode codehash is valid, protecting against tampering or malicious alterations.\n- Verifies that the Spell meets custom requirements (e.g., office hours) by confirming the `spell.isExecutable()` view function returns true.\n- Verifies that StarGuard retains access to the SubProxy, ensuring no loss of control during the Agent Spell execution.","contentHash":"3c9f31dad2cf975291c737d191d89b3cc7acca17b41c45f371553a96f2554a3f","addressRefs":[]},"ffc88a5e-b7b2-4ed9-8c88-fcbcb7632f14":{"id":"ffc88a5e-b7b2-4ed9-8c88-fcbcb7632f14","doc_no":"A.1.10.2.3.2.3.2","title":"Direct Execution Through Sky Core Spell","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":464,"content":"When the execution through the Sky Core Spell method is used, the Agent Spells are executed directly in the Sky Core Spells.","contentHash":"3a0263fa0bc63de9c879e5b687bfeca5aa8f92a2ef9382b7b4903515a6fdd772","addressRefs":[]},"a109ad0d-0743-4ae9-bcc1-df04a6e5da43":{"id":"a109ad0d-0743-4ae9-bcc1-df04a6e5da43","doc_no":"A.1.10.2.3.2.3.2.1","title":"Sky Core Spell Executes Agent Spell","type":"Core","depth":6,"parentId":"64edb1ca-e577-41c4-aa9e-5af759b2d240","order":465,"content":"Execution of an Agent Spell is initiated by the Sky Core Spell, which directly calls `exec()` on the Agent's SubProxy contract to perform the Spell’s actions in the same transaction. The SubProxy limits rights to the specific Agent, preventing access to Sky Core contracts. The current SubProxy contract is designed to execute the Agent Spell in the same transaction as the Sky Core Spell.","contentHash":"3a0317b7b4e40dc12e98c4d1cfc9be439df5bcc150ea55b5f49f7e44b9060128","addressRefs":[]},"867cad8c-f85d-44d9-9f3e-4267f6bb09ae":{"id":"867cad8c-f85d-44d9-9f3e-4267f6bb09ae","doc_no":"A.1.10.2.3.3","title":"Novel Items","type":"Core","depth":5,"parentId":"7b4c9934-5ba4-4218-b601-8f44ffb5881e","order":466,"content":"Some onchain changes are considered novel and require specialized processes outside the regular Spell cadence, including a technical feasibility and implementation proposal phase prior to including the item in the Executive Vote process. The process for novel Spell items for Executive Votes is specified in the subdocuments herein.","contentHash":"0d404be18b76a14ee81c28194412b0e1fc09a0d87f426680784058683301fe5c","addressRefs":[]},"af13ac4b-3638-4858-9165-0949334725de":{"id":"af13ac4b-3638-4858-9165-0949334725de","doc_no":"A.1.10.2.3.3.1","title":"Definition Of Novel Spell Item","type":"Core","depth":6,"parentId":"867cad8c-f85d-44d9-9f3e-4267f6bb09ae","order":467,"content":"An item is considered novel if the request cannot use any of the code patterns already available in the `spell-mainnet` archive folder used on prior Spells.","contentHash":"e3844f37dede4b1489d0f910f1cdbaaa1bf06bda7ff3109fb7ba2282fae4d487","addressRefs":[]},"0ed7559c-5877-4968-8bcc-9d47207cc904":{"id":"0ed7559c-5877-4968-8bcc-9d47207cc904","doc_no":"A.1.10.2.3.3.2","title":"Novel Items Process Definition","type":"Core","depth":6,"parentId":"867cad8c-f85d-44d9-9f3e-4267f6bb09ae","order":468,"content":"The documents herein define the process for including novel items in Spells.","contentHash":"4b52dc7a00c37415a2179664f8f3235318a9bccb758dbac5083d9295b0504a5d","addressRefs":[]},"47a584fe-9b41-4bce-93fa-871eca8ba8bd":{"id":"47a584fe-9b41-4bce-93fa-871eca8ba8bd","doc_no":"A.1.10.2.3.3.2.1","title":"Core GovOps Or Core Facilitator Requests Inclusion Of Novel Item","type":"Core","depth":6,"parentId":"867cad8c-f85d-44d9-9f3e-4267f6bb09ae","order":469,"content":"The process begins when a stakeholder's needs require an item that Core GovOps believes is novel in an upcoming Spell. Core GovOps submits a request to the Core Facilitator for inclusion of the item. The Core Facilitator also has the authority to independently request inclusion of a novel item.","contentHash":"e1740174aa55f12d613b94ad15f45ff1b28e6a719c168f75a30376f3ad0cc762","addressRefs":[]},"390d239c-184a-4c72-b41c-5b2bc4fb1b2d":{"id":"390d239c-184a-4c72-b41c-5b2bc4fb1b2d","doc_no":"A.1.10.2.3.3.2.2","title":"Core Facilitator Confirms Whether Requested Item Is Novel","type":"Core","depth":6,"parentId":"867cad8c-f85d-44d9-9f3e-4267f6bb09ae","order":470,"content":"The Core Facilitator, in consultation with the Core Spell Teams, determines whether the requested item is novel. If the item is not considered novel, it is scheduled via the regular Spell process as specified in [A.1.10.2.4 - Executive Process Breakdown](98298ab3-8d08-4c4f-b47b-81242a3e3903). If the item is classified as novel, the Core Facilitator notifies the Core Spell Teams of this determination in Discord in the #govops channel.","contentHash":"d189b9421d13cf8198f0ec92b31039e38b71a5e6bcd9ab8af52a5dbb6e5b47b9","addressRefs":[]},"0e7a4416-35e7-4820-b426-0052774c8307":{"id":"0e7a4416-35e7-4820-b426-0052774c8307","doc_no":"A.1.10.2.3.3.2.3","title":"Core Spell Teams Conduct A Technical Feasibility Analysis And Develop An Implementation Proposal","type":"Core","depth":6,"parentId":"867cad8c-f85d-44d9-9f3e-4267f6bb09ae","order":471,"content":"The Core Spell Teams conduct a technical feasibility analysis and develop an implementation proposal for the novel Spell item. One Spell Team may take the lead, or both teams may work in parallel and reconcile approaches. Both Spell Teams must agree on the implementation proposal. The proposal may include external audits or other processes. The Core Facilitator and relevant domain experts, including those with technical expertise related to the novel item, can provide input on the implementation proposal. The Spell Teams deliver the implementation proposal to the Core Facilitator.","contentHash":"42dcefaef49459f4faaed3af58cbd8de7618255a6431473905ac09ebb3d24817","addressRefs":[]},"00a4c49c-bf49-492e-819d-a4a53249c1eb":{"id":"00a4c49c-bf49-492e-819d-a4a53249c1eb","doc_no":"A.1.10.2.3.3.2.4","title":"Core Facilitator Obtains Approval From Relevant Stakeholders And Schedules Novel Spell Item","type":"Core","depth":6,"parentId":"867cad8c-f85d-44d9-9f3e-4267f6bb09ae","order":472,"content":"After receiving the implementation proposal, the Core Facilitator shares it with the relevant stakeholders whose needs originated the request. The Core Facilitator works with these stakeholders to confirm that the implementation proposal addresses the needs that motivated the novel Spell item. After doing so, the Core Facilitator schedules the novel Spell item into the regular Spell cadence as specified in [A.1.10.2.4 - Executive Process Breakdown](98298ab3-8d08-4c4f-b47b-81242a3e3903).","contentHash":"d72319d81c34bd2c913487563a775c0b1af820d7a621b2e308de6ffe114c170e","addressRefs":[]},"98298ab3-8d08-4c4f-b47b-81242a3e3903":{"id":"98298ab3-8d08-4c4f-b47b-81242a3e3903","doc_no":"A.1.10.2.4","title":"Executive Process Breakdown","type":"Core","depth":4,"parentId":"03d32549-1da5-4a9c-902f-196641370eaf","order":473,"content":"The Executive Process for Sky Core consists of 13 steps as outlined in the subdocuments herein. The deadlines for internal coordination between the Governance Point, Technical Point, and Content Liaisons are designed to optimize efficiency. While these timelines should generally be adhered to, they do not take precedence over security considerations. Any delays must be communicated promptly, along with updated and realistic time estimates.","contentHash":"9c610c8086b4d5ac6a5d7a0027cdff1843fb92d7c5e1bf1afc333f046a3f16cf","addressRefs":[]},"0f0f7021-f753-4c8b-8b80-46abce259aa9":{"id":"0f0f7021-f753-4c8b-8b80-46abce259aa9","doc_no":"A.1.10.2.4.1","title":"Governance Point Determines Preliminary Content For Executive Sheet (Step 1)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":474,"content":"The Governance Point prepares the Executive Sheet by identifying items for potential inclusion. At this stage, all content and values are considered provisional. While the Governance Point prepares this preliminary plan for the content of the Spell, the final consensus regarding what to include is reached during the GovOps meeting with the Spell Team. The subdocuments herein explain how the Governance Point identifies these items. This preparatory phase ensures that content is outlined and organized in advance.","contentHash":"b0dbdb00b9e1ff8f5821db10ff7c2080e5ce4dcd208b8c5ec9d840a79fb4a0ed","addressRefs":[]},"2c99fa29-4f22-4f40-9284-ac0c07a6cd6e":{"id":"2c99fa29-4f22-4f40-9284-ac0c07a6cd6e","doc_no":"A.1.10.2.4.1.1","title":"Consideration For Determining Preliminary Content For Executive Sheet","type":"Core","depth":6,"parentId":"0f0f7021-f753-4c8b-8b80-46abce259aa9","order":475,"content":"The process of determining which content to include in the Executive Sheet, as well as the timing of its inclusion, varies based on the nature of the items in question. Several factors must be carefully considered, including adherence to governance processes, addressing security concerns, and evaluating the urgency of the Sky Protocol. Every item included in the Spell poses a security risk to Sky.","contentHash":"68958b0348b4baf59da1d35dda8984df6a5647eefe0b0e487076dfa9707d2f04","addressRefs":[]},"35d0ed69-3ec4-4ead-8e41-b1b9a9b5538d":{"id":"35d0ed69-3ec4-4ead-8e41-b1b9a9b5538d","doc_no":"A.1.10.2.4.1.2","title":"Sources For Determining Preliminary Content For Executive Sheet","type":"Core","depth":6,"parentId":"0f0f7021-f753-4c8b-8b80-46abce259aa9","order":476,"content":"The Governance Point must review the sources described in the subdocuments herein for potential items to include in the Executive Sheet.","contentHash":"c437d56e1d77a922026591d65ec79bece7701d81de4615221d42786c667f6892","addressRefs":[]},"4aa6a4d5-390d-47a9-af9e-b20a993741e0":{"id":"4aa6a4d5-390d-47a9-af9e-b20a993741e0","doc_no":"A.1.10.2.4.1.2.1","title":"Governance Point Reviews And Assesses Content In The Executive Vote Queue","type":"Core","depth":6,"parentId":"0f0f7021-f753-4c8b-8b80-46abce259aa9","order":477,"content":"The Governance Point must review the Executive Vote queue, which contains items that were included in the previous cycle(s) but removed from the Executive Sheet. The Governance Point then determines which of these items should be included in the current cycle’s Executive Sheet.","contentHash":"6e6d74d82348ba00d06aae83b78812bdec614e537fdde9f711118e94949c8f00","addressRefs":[]},"465c6f95-8ac0-4405-9443-bcf1e233aa82":{"id":"465c6f95-8ac0-4405-9443-bcf1e233aa82","doc_no":"A.1.10.2.4.1.2.2","title":"Items From Approved Governance Polls Or Authorized Ecosystem Actor Requests","type":"Core","depth":6,"parentId":"0f0f7021-f753-4c8b-8b80-46abce259aa9","order":478,"content":"For certain changes to the Sky Protocol, the Atlas may require items to first undergo formal governance steps, such as Forum announcements or Governance Polls, before they can be included in the Executive Sheet. The Governance Point is responsible for reviewing Governance Polls and any recent Forum posts and including potential items in the Executive Sheet.","contentHash":"99b0e609e687d5df37aa05165ee79ebca2d6b4900c874fb5988ee73c51d3815e","addressRefs":[]},"ea70f102-5e35-42a7-8658-9e8053acef39":{"id":"ea70f102-5e35-42a7-8658-9e8053acef39","doc_no":"A.1.10.2.4.1.2.3","title":"Potential Items From Ecosystem Actors","type":"Core","depth":6,"parentId":"0f0f7021-f753-4c8b-8b80-46abce259aa9","order":479,"content":"The Governance Point maintains ongoing communication with Ecosystem Actors to plan and prioritize items for inclusion in the Executive Sheet. This ensures that the most critical and time-sensitive items are prioritized.","contentHash":"bb45af64b33b8e43f18f217b630aab07e80f5a03125edc25350e03aeb9060be2","addressRefs":[]},"dc610140-5660-4743-a9f7-4a1032c83dd5":{"id":"dc610140-5660-4743-a9f7-4a1032c83dd5","doc_no":"A.1.10.2.4.1.3","title":"Planning Checklist For Governance Point","type":"Core","depth":6,"parentId":"0f0f7021-f753-4c8b-8b80-46abce259aa9","order":480,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md) outlines the steps for the Governance Point in planning the Executive Sheet.","contentHash":"c4fe8bdeb081afe2477cd4c2556b521619cced31856edef79bba5f69a828573f","addressRefs":[]},"298819fe-cc26-49a8-a7cb-3ff83e55f291":{"id":"298819fe-cc26-49a8-a7cb-3ff83e55f291","doc_no":"A.1.10.2.4.2","title":"Governance Point Creates Executive Sheet Week 1 Monday (Step 2)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":481,"content":"For every Executive Vote, a new Executive Sheet must be created. The process follows a standardized approach to ensure consistency across all Executive Votes. The Governance Point is responsible for the creation and maintenance of the Executive Sheet.","contentHash":"561316cf4d454d610dcdbb7cc240f4dd5219a529ea8dba27c2cdf58dd71ffd5a","addressRefs":[]},"bf3a5524-52cd-463b-8058-b65ca8b2c94c":{"id":"bf3a5524-52cd-463b-8058-b65ca8b2c94c","doc_no":"A.1.10.2.4.2.1","title":"Structure Of The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":482,"content":"While the content of the Executive Sheet will vary depending on the actions Sky Governance wishes to execute for the Sky Protocol, the structure of the Executive Sheet and the method of communicating the different executive actions described in the subdocuments must be adhered to.","contentHash":"b5f2cfd120517be830f0aa61a6936102cfe4708a773d23142daf983b5d57d6fe","addressRefs":[]},"d41c2e6a-2afc-458c-ab90-3ce863495095":{"id":"d41c2e6a-2afc-458c-ab90-3ce863495095","doc_no":"A.1.10.2.4.2.1.1","title":"Executive Action","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":483,"content":"Every action that should be included in the Spell must be present in the Executive Sheet. Each executive action is populated in the Executive Sheet under a column and broken down into \"input\" actions and \"derived\" actions. An Input Action represents a high-level category, and a Derived Action breaks down the Input Action into specific, actionable steps or changes. Each action in the Executive Sheet, whether input or derived, must have sufficient provenance to support its presence during the Spell.","contentHash":"f81694f0cf7a3a210dd261bde62c4660b87b131aa3a61df4e76c1d11bb95431c","addressRefs":[]},"a935cfad-6674-4e77-b3f4-e605c076417e":{"id":"a935cfad-6674-4e77-b3f4-e605c076417e","doc_no":"A.1.10.2.4.2.1.2","title":"Formatting Rules For The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":484,"content":"The Executive Sheet should be formatted as follows:\n\n- One single row of empty cells should be present directly above every \"input\" action in the Executive Sheet.\n- Each \"input\" action must be written in bold and must be present before any actions that are derived from the ‘input’ action. Optionally, ‘input’ actions may also use underlined text.\n- Actions that are \"derived\" from an \"input\" action must not use bold or underlined text and must be located directly after the \"input\" action.","contentHash":"9633754baee207d6be85ec460b73e00ce851f44cfc1437136d0bacb52afd0513","addressRefs":[]},"199931bd-0e55-4796-b3f7-f6926c3b119a":{"id":"199931bd-0e55-4796-b3f7-f6926c3b119a","doc_no":"A.1.10.2.4.2.1.3","title":"Language Consistency In The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":485,"content":"The text for both \"input\" and \"derived\" actions listed in the Executive Sheet should follow previous wording and structural patterns. There should be no deviation from existing patterns of wording or sentence structure used in the Executive Sheet unless it is absolutely required for the Spell process to be completed. The instructions should be specific and follow previous instructions in the archive.","contentHash":"143acc7860ab777dfc24f6364a6322b9d4b60c8dbc625880ef004272a57d1d5f","addressRefs":[]},"f6f1efeb-9f99-407e-a53a-43468c66afc4":{"id":"f6f1efeb-9f99-407e-a53a-43468c66afc4","doc_no":"A.1.10.2.4.2.1.3.1","title":"Values In The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":486,"content":"Values should be expressed as a specific number and then specify the start and end times over which this value occurs. In general, expressing values as \"per day\" or any other measurement per unit of time should be avoided to maintain clarity and specificity. However, certain values may require a \"per unit of time\" definition when it's essential for the calculation.","contentHash":"c33cf162bd785f79d48216dc293de7771983a0471359fcea9930872d43c16ed3","addressRefs":[]},"3583410e-3504-4a85-98a0-90619848129c":{"id":"3583410e-3504-4a85-98a0-90619848129c","doc_no":"A.1.10.2.4.2.1.3.2","title":"Expressing Relative And Absolute Changes","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":487,"content":"Relative and absolute value increases or decreases should be stated as \"Increase SSR by 3.00 percentage points from 15.50% to 18.50%\".","contentHash":"8bde931de3b5311f51f6362ec45486e3b32413967e185f12d925866886773a05","addressRefs":[]},"e60557ed-593f-4946-96f6-efcf7a853544":{"id":"e60557ed-593f-4946-96f6-efcf7a853544","doc_no":"A.1.10.2.4.2.1.3.3","title":"Express The Value Of Numbers Numerically","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":488,"content":"Every number in the Executive Sheet should be expressed with a number instead of being spelled out. For example, if a value is zero the number \"0\" should be used instead of the word \"zero\". This maintains the consistency between values and thus reduces the chances of a misread or misinterpreted value.\n\nWhen expressing rates or percentages, the appropriate unit should always be included (e.g., \"0%\" for a zero percent rate).","contentHash":"c90f35cebc704cdf4293d1d1566288e883d9188a2aefc49fa8f09b3b1c28f775","addressRefs":[]},"33ac6653-d963-4ac5-9ff5-c77c5633a9a7":{"id":"33ac6653-d963-4ac5-9ff5-c77c5633a9a7","doc_no":"A.1.10.2.4.2.1.3.4","title":"Checksummed Addresses","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":489,"content":"All blockchain addresses listed in the Executive Sheet must be checksummed to ensure accuracy and prevent errors. The addresses follow the EIP-55 standard, using mixed-case letters to create a verifiable format that helps detect typos or mismatches.","contentHash":"df7047a1079900d313681d42b18ee0ad4e2b9b8586c138bbb5c8f6b822e821eb","addressRefs":[]},"755fe505-8058-4f0a-bccf-eafbdcfb4f9b":{"id":"755fe505-8058-4f0a-bccf-eafbdcfb4f9b","doc_no":"A.1.10.2.4.2.2","title":"Creation Of The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":490,"content":"The creation process of the Executive Sheet must follow the steps specified in the subdocuments herein.","contentHash":"ca9c62280f68ba2d70462740cc8a67689d577f2b0ac241d2eace86a7f839308b","addressRefs":[]},"ec06d92c-5836-4df9-9680-5977e5a64a72":{"id":"ec06d92c-5836-4df9-9680-5977e5a64a72","doc_no":"A.1.10.2.4.2.2.1","title":"The Governance Point Creates The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":491,"content":"The Governance Point creates the Executive Sheet by duplicating the template tab to create a new tab within the same Google Sheet. The Executive Sheet template can be found here: [https://docs.google.com/spreadsheets/d/1w_z5WpqxzwreCcaveB2Ye1PP5B8QAHDglzyxKHG3CHw/edit?pli=1&gid=1971670262#gid=1971670262](https://docs.google.com/spreadsheets/d/1w_z5WpqxzwreCcaveB2Ye1PP5B8QAHDglzyxKHG3CHw/edit?pli=1&gid=1971670262#gid=1971670262).","contentHash":"1284d3ec7d53401685ec1ededb981801c65fc2e942185fcb59c08bb385fbb0b1","addressRefs":[]},"e34b72db-973c-4cfd-8e8c-ff424c081805":{"id":"e34b72db-973c-4cfd-8e8c-ff424c081805","doc_no":"A.1.10.2.4.2.2.2","title":"The Governance Point Names The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":492,"content":"For scheduled Executive Votes in the Executive Process, the Executive Sheet must be named in the following format: \"Executive Contents - YYYY-MM-DD\" (Target Date). For Out-of-Schedule Executive Votes, the naming format can diverge from this standard to reflect the specific context or purpose of the vote.","contentHash":"3045e86d63b6ce3eb800f5ef4e2b8d6e1cf922854b4fcb41b56f973a37033da8","addressRefs":[]},"1dac0bce-7edc-45a1-97f8-f11fc381015d":{"id":"1dac0bce-7edc-45a1-97f8-f11fc381015d","doc_no":"A.1.10.2.4.2.2.3","title":"The Governance Point Includes The Executive Vote In The Spell Progress Tracker","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":493,"content":"In the Google Sheet document, there is a tab named \"Spell progress tracking\". The Governance Point must:\n\n1. Add a new column for the Executive Vote. The column should be added to the right in the document to make sure that the Executive Votes are sorted in chronological order.\n2. Enter the Target Date.","contentHash":"58852aa7a216f128b5401e9f8bcd034aba1859ff7ba1b8a3688302e05c878438","addressRefs":[]},"a6bab26a-a334-4d44-a45a-cf848ed36480":{"id":"a6bab26a-a334-4d44-a45a-cf848ed36480","doc_no":"A.1.10.2.4.2.2.4","title":"The Governance Point Maintains the Spell Progress Tracker","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":494,"content":"The Governance Point must ensure that the progress for the Spell is updated accurately in the Spell progress tracker. When a step is completed, the Governance Point must write \"done\" in the Spell progress tracker column. This is an ongoing responsibility throughout the lifecycle of the Executive Vote to maintain real-time accuracy.","contentHash":"0bcc377cffac487f8820c8160a30da832a4737466f9194e4111d43faeb301a58","addressRefs":[]},"7a40558a-3eb4-4199-9fe5-6f5b3561c702":{"id":"7a40558a-3eb4-4199-9fe5-6f5b3561c702","doc_no":"A.1.10.2.4.2.3","title":"Governance Point Populates The Executive Sheet In Consultation With Ecosystem Actors","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":495,"content":"After the formal creation of the Executive Sheet, the Governance Point populates it with items in coordination with relevant Ecosystem Actors and contributors.","contentHash":"73fc6303d13aa142bf7e4bf4373b3c1f178155d9875f7d3b2e27058b870905c8","addressRefs":[]},"9e96fca0-6a7c-4c6d-81f8-052d24d32a48":{"id":"9e96fca0-6a7c-4c6d-81f8-052d24d32a48","doc_no":"A.1.10.2.4.2.3.1","title":"Governance Point Includes Items In The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":496,"content":"The Governance Point lists the preliminary items determined for inclusion in the Executive Sheet. The Governance Point must complete information for the Input Action(s), Derived Action(s), and Type, and populate the \"Liaison Confirm,\" \"Technical Confirm,\" and \"Governance Confirm\" fields as Unconfirmed. If URLs for the Reasoning and URL Authority can be completed at this stage, the Governance Point should populate these fields.\n\nThe Governance Point will mark any items as \"TBD\" or \"TBC\" if they require further discussion or confirmation by the Technical Point or Content Liaisons.","contentHash":"60ae6720f0d0de1caa736adc685ff81cd9836ed256807700fb2f7b6b26349ef3","addressRefs":[]},"37d03695-8ccb-40a9-84e9-a9871dd6caf3":{"id":"37d03695-8ccb-40a9-84e9-a9871dd6caf3","doc_no":"A.1.10.2.4.2.3.2","title":"Governance Point Includes Recurring Items In The Executive Sheet","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":497,"content":"In every Executive Vote there are recurring items that must always be included. These are Office Hours, Global Line Modifier, and Order of Operations Issues. The values of these items can be marked with a question mark or \"TBC\". During the GovOps meeting the Spell Crafter will confirm the values of these items.","contentHash":"66ab500e3a0ecc22b3c86a8c3d5ac5135955533ba4d6f364b6bf1d51318b6905","addressRefs":[]},"ea9e4dd4-8148-4755-bd39-fd44b1de49b3":{"id":"ea9e4dd4-8148-4755-bd39-fd44b1de49b3","doc_no":"A.1.10.2.4.2.3.3","title":"Governance Point Communicates Deadlines To Ecosystem Actors","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":498,"content":"The Governance Point is responsible for making sure that the relevant ecosystem actors included in the Executive Process are aware of the deadlines associated with the process. This includes informing them of when the Executive Sheet must be finalized and when final rates must be announced.","contentHash":"ee3894f838de3218bb903f7bd16330bca50e48319c3ca872db38f53e1f9905f2","addressRefs":[]},"9d1900e4-49bf-41f1-af94-20b0c770f845":{"id":"9d1900e4-49bf-41f1-af94-20b0c770f845","doc_no":"A.1.10.2.4.2.3.4","title":"Coordination Checklist For Governance Point","type":"Core","depth":6,"parentId":"298819fe-cc26-49a8-a7cb-3ff83e55f291","order":499,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md) outlines the steps for the Governance Point when preparing the Executive Sheet.","contentHash":"a2851ee83f0c1eb056f7b2647f149fa015151d1d873df8157d7291fb7e34bcbd","addressRefs":[]},"0f74afdf-bc2d-4512-9b11-8f5a26511787":{"id":"0f74afdf-bc2d-4512-9b11-8f5a26511787","doc_no":"A.1.10.2.4.3","title":"Governance Point Conducts GovOps Meeting Week 1 Tuesday (Step 3)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":500,"content":"On Tuesday week 1, key actors involved in the Executive Process have a gov-ops meeting to discuss the upcoming Executive Vote.","contentHash":"30a7c452bff4b837b41f2b2d386ed7bcd5044dd5af984acddbb21f22499045a0","addressRefs":[]},"b0d1a683-3b92-4283-8e32-22251192a716":{"id":"b0d1a683-3b92-4283-8e32-22251192a716","doc_no":"A.1.10.2.4.3.1","title":"GovOps Meeting","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":501,"content":"The meeting, which is conducted by text, takes place on Discord in the #govops channel, 9 days before the Target Date. The Governance Point invites and leads the meeting. The Governance Point must make sure that the items specified in the subdocuments herein are processed at the meeting. The meeting takes place at 15.00 UTC. The Governance Point creates a separate thread in the #govops channel for every Executive Vote. The thread is named the target Spell date: \"YYYY-MM-DD Executive Coordination\".\n\nThe GovOps meeting includes various stakeholders. Governance Point, Technical Point, and Content Liaisons typically attend, whether sync or async.\n\nThe Executive Sheet serves as the basic reference for stakeholders. The decisions made by stakeholders will often result in real-time changes to the Executive Sheet.","contentHash":"b4090090ffc6a4970ee1b12018d9371a725edf5ce6f40bf667fe8fd53c566d0b","addressRefs":[]},"d8e11fe9-dec8-4a71-9519-8aede2213167":{"id":"d8e11fe9-dec8-4a71-9519-8aede2213167","doc_no":"A.1.10.2.4.3.1.1","title":"Confirmation Of Roles","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":502,"content":"During the GovOps meeting the Governance Point will ask for confirmation of who will act as Crafter and Reviewers for the Executive Vote. The technical teams provide names for the roles.","contentHash":"b230beb941da81d59e5d117839e5cf0c97e782ff23a2b157e5dd51f625fc53c2","addressRefs":[]},"25bbdd08-4823-449b-bc95-944450336286":{"id":"25bbdd08-4823-449b-bc95-944450336286","doc_no":"A.1.10.2.4.3.1.2","title":"Content Review","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":503,"content":"The Governance Point lists the preliminary content in the Executive Sheet. Each item is discussed at the meeting. The review during the GovOps meeting primarily focuses on the technical aspects of the instructions in the Executive Sheet. The Technical Point often provides technical advice to the Governance Point during the GovOps meetings, including technical risk and other implications that the Governance Point may not otherwise be aware of. If the Spell includes complex code, the Technical Point may sometimes prepare technical documents to facilitate the process.\n\nThe Governance Point may have additional discussions with Ecosystem Actors in separate Discord channels.","contentHash":"1df818120db4f8d4b3487ed4e7dce532a6bbbbdd6af4e2c5b9684a96e9152e68","addressRefs":[]},"bba8d328-8210-428b-95ae-f690936c6016":{"id":"bba8d328-8210-428b-95ae-f690936c6016","doc_no":"A.1.10.2.4.3.1.3","title":"Obtain Consensus On Content","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":504,"content":"Based on the review of requested and planned content, the teams must reach a consensus on which items to include in the Spell. In some cases, the Spell Crafter may request the removal of certain items if the Spell is deemed high risk, too big or contains novel code. Such removals typically affect non-critical items, such as internal payments. Content being removed from the Executive Sheet is added to the Executive Vote queue to be included in the next Executive Vote cycle.\n\nOnboarding of sensitive modules is considered increasing the Spell's complexity in such a manner that the Spell Reviewers should only focus on this; therefore, non-crucial items should be removed from the Executive Sheet and included in the Executive Vote queue.","contentHash":"373e7405e9084b30c0adcf602055b2f4de2bff62e2446c4c0c4ce21f1e140697","addressRefs":[]},"d79509f0-089e-46ee-ada8-bb1a66e99482":{"id":"d79509f0-089e-46ee-ada8-bb1a66e99482","doc_no":"A.1.10.2.4.3.1.4","title":"Confirming Values Of Recurring Items","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":505,"content":"Based on the planned content of the Spell, the Governance Point must ask the Technical Point to confirm the values of the recurring checklist items. See [A.1.10.2.4.2.3.2 - Governance Point Includes Recurring Items In The Executive Sheet](37d03695-8ccb-40a9-84e9-a9871dd6caf3).","contentHash":"2a09d16ab858bc8ffc976ff60101f56d97a676f94383f3c95e0591b58e4e344d","addressRefs":[]},"6361b7c7-8cb3-49bf-83a8-a3684623d37e":{"id":"6361b7c7-8cb3-49bf-83a8-a3684623d37e","doc_no":"A.1.10.2.4.3.1.5","title":"GovOps Meeting Checklist","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":506,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md) outlines the discussion points for the GovOps meeting.","contentHash":"3970e1f0f5d30296d103b7c702dc64085c101cf2a9aaaa9e820947ca06ff2605","addressRefs":[]},"c38da8ab-1fdd-42e9-8b96-366a51a26e85":{"id":"c38da8ab-1fdd-42e9-8b96-366a51a26e85","doc_no":"A.1.10.2.4.3.2","title":"Post Meeting Tasks","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":507,"content":"After the GovOps meeting, the Governance Point must do the items specified in the subdocuments herein. The items should be completed week 1 Tuesday.","contentHash":"03a04b5796f9d876a4cc61b03bffea130996db1489a720a88eebff111c1b48dc","addressRefs":[]},"a51689a8-dd58-4cd6-9490-da2bf4148d64":{"id":"a51689a8-dd58-4cd6-9490-da2bf4148d64","doc_no":"A.1.10.2.4.3.2.1","title":"Specify Roles And Recurring Items In Executive Sheet","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":508,"content":"The values of the recurring items, as determined during the GovOps meeting, must be added to the Executive Sheet. Additionally, the roles for the Spell Crafter, Spell Reviewers, and Content Liaisons must be recorded in the sheet. The identity of the Content Liaison is determined as the party that originally requested the item for inclusion.","contentHash":"671ff1e2ddc1cc22857af261d935d22424f164f55a38cf22b4f78ce96f21b6cc","addressRefs":[]},"28fea6ae-c0f8-47a9-be72-7d4ab2c58272":{"id":"28fea6ae-c0f8-47a9-be72-7d4ab2c58272","doc_no":"A.1.10.2.4.3.2.2","title":"Update The Executive Sheet Content","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":509,"content":"Items that reached a consensus during the GovOps meeting must be reflected in the Executive Sheet. This includes both the removal of existing items and the addition of new items, as confirmed by all parties during the GovOps meeting.","contentHash":"367320815b6868ee0407a4657d5cde711f16ade87bc1cbb621e4e8894441db98","addressRefs":[]},"b97f9d90-82cd-4ca8-a78f-a7e9c115a4f5":{"id":"b97f9d90-82cd-4ca8-a78f-a7e9c115a4f5","doc_no":"A.1.10.2.4.3.2.3","title":"Checksums","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":510,"content":"The total amount of token transfers must always be summed up in the Executive Sheet. The Governance Point and Technical Point independently sum up the value. The value of USDS and Dai must always be expressed as integers, with no decimal places, due to tests and helper functions used by developers requiring integer values. For USDS and Dai, values must always be rounded up to ensure recipients receive at least the expected amount. The values of SKY and other tokens must be listed to exactly two decimal places. All summations must occur only after the Executive Sheet is complete to avoid missing any transfers.","contentHash":"629db86f966b96a06361910ae2e64d786c60f266f6057dff675cd4d12815d58a","addressRefs":[]},"3f90dcbd-8a43-44ce-9c2a-c6efdabcbba7":{"id":"3f90dcbd-8a43-44ce-9c2a-c6efdabcbba7","doc_no":"A.1.10.2.4.3.2.4","title":"Post-meeting Checklist","type":"Core","depth":6,"parentId":"0f74afdf-bc2d-4512-9b11-8f5a26511787","order":511,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md) outlines the steps for the post-meeting tasks.","contentHash":"0cc2ce4cadac8156335370340f7c9b50d94609cf6d0c8fa5e6e43b6b1c7ed02b","addressRefs":[]},"3bf7e2f3-a5e4-4bb6-ace7-3b8102a2cab7":{"id":"3bf7e2f3-a5e4-4bb6-ace7-3b8102a2cab7","doc_no":"A.1.10.2.4.4","title":"Governance Point Requests Confirmation Of Executive Sheet Week 1 Wednesday (Step 4)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":512,"content":"The Governance Point must request confirmations from the relevant stakeholders for each item in the Executive Sheet on Wednesday week 1.","contentHash":"5f132f7cd028a4499c78d001f926ce8bcc23d836df8028e45736d3f71f7b1a46","addressRefs":[]},"17f172c6-2469-4447-8c36-3aff93a6b10b":{"id":"17f172c6-2469-4447-8c36-3aff93a6b10b","doc_no":"A.1.10.2.4.4.1","title":"Governance Point Must Coordinate With Stakeholders","type":"Core","depth":6,"parentId":"3bf7e2f3-a5e4-4bb6-ace7-3b8102a2cab7","order":513,"content":"The Governance Point is responsible for coordinating with all relevant stakeholders and clarifying which items should be confirmed by the different stakeholders.","contentHash":"4488181f8b0660bee92d3d3dbcdab4b984d72a763519b8526d05fc3efd3af762","addressRefs":[]},"89d800a0-edba-4905-b38c-815f6a45949b":{"id":"89d800a0-edba-4905-b38c-815f6a45949b","doc_no":"A.1.10.2.4.4.2","title":"Governance Point Must Correct Discrepancies","type":"Core","depth":6,"parentId":"3bf7e2f3-a5e4-4bb6-ace7-3b8102a2cab7","order":514,"content":"The Governance Point must ensure that any discrepancies between the Executive Sheet and stakeholder input are corrected.\n\nThe stakeholders communicate in the #govops channel in Discord if there are any issues or required changes that need to be made in the Executive Sheet. The Governance Point then changes the instruction in accordance with the stakeholder's input, and asks the stakeholder to confirm that the new instruction is correct. This is common for technical instructions in the Executive Sheet.","contentHash":"2c1931f0c05516a4d3ded1437d39ca0350333508f435d90b7ba489921d048c81","addressRefs":[]},"835d1f82-b0ee-40d3-8e7b-41f47d25e6b7":{"id":"835d1f82-b0ee-40d3-8e7b-41f47d25e6b7","doc_no":"A.1.10.2.4.4.3","title":"Summary Checklist","type":"Core","depth":6,"parentId":"3bf7e2f3-a5e4-4bb6-ace7-3b8102a2cab7","order":515,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md) outlines the items for the confirmation process that should be done.","contentHash":"03fad8aa2b1b7a81d4a726180d45bb22c2475977368f08de3e18e3f6aa72e95a","addressRefs":[]},"558451e8-1b04-48ce-bcb2-9c69ba22929b":{"id":"558451e8-1b04-48ce-bcb2-9c69ba22929b","doc_no":"A.1.10.2.4.5","title":"Confirmation Of Content Of Executive Sheet Week 1 Friday (Step 5)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":516,"content":"On Friday week 1, the Governance Point, Technical Point and Content Liaisons must confirm the items in the Executive Sheet.","contentHash":"f1ae223ae36c18933a595230795c88538a8677a2d994e46050e5e3b6d9bed420","addressRefs":[]},"c86c3a65-e601-465d-9961-9f38dcd4c35a":{"id":"c86c3a65-e601-465d-9961-9f38dcd4c35a","doc_no":"A.1.10.2.4.5.1","title":"Provenance","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":517,"content":"All actions in the Executive Sheet require sufficient provenance for their inclusion in the sheet and later in the Executive Vote. The legitimacy of a provenance is assessed on the basis of its mutability, visibility and resistance to compromise by external malicious actors. There are different ways of providing sufficient provenance, including \"strong comment type\" provenance, \"onchain\" provenance and \"strong document type\" provenance. These types of provenance are defined in the subdocuments herein.\n\nIf Executive actions and items do not have sufficient provenance, for example, \"weak comment type\", they cannot be included in the Executive Vote. If the Governance Point has any question whether a proposed Executive action has sufficient provenance, they must resolve that question of validity before including that action in the Executive Process.","contentHash":"e345ed2f3df0dc3a7bb7b56166d7f017ed4028a32637a3dd42ddcd66a9a1f23d","addressRefs":[]},"4140df92-a505-46e0-a399-2c8d3ece9284":{"id":"4140df92-a505-46e0-a399-2c8d3ece9284","doc_no":"A.1.10.2.4.5.1.1","title":"Weak Comment Type Provenance","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":518,"content":"The provenance type \"weak comment type provenance\" refers to informal or editable comments made by stakeholders, which lack the security and visibility needed for Executive actions. For example, Discord messages, forum posts, or unverified social media comments are considered weak comment provenance, even if they relate to an action affecting the commenter (e.g., confirming a payment). Weak comment types are highly mutable, as they can often be edited or deleted without a public trace, and may not be visible to all ecosystem participants (e.g., requiring platform-specific accounts or access to private channels). They also have low resistance to compromise, relying on accounts without strong security protocols, making them vulnerable to malicious edits or takeovers by bad actors. As such, weak comment provenance does not qualify as sufficient and must not be used to authorize Executive actions.","contentHash":"35cd026af84a3b0752fc6648beb23737ae2c68ed3d440825e1179b8fda7200d5","addressRefs":[]},"8e18add4-2ac0-4ee8-b42f-5187bfccc212":{"id":"8e18add4-2ac0-4ee8-b42f-5187bfccc212","doc_no":"A.1.10.2.4.5.1.2","title":"Strong Comment Type Provenance","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":519,"content":"The provenance type \"strong comment type provenance\" refers to comments made by stakeholders that relate to a specific executive action. For example, Google Sheets confirmation comments left by payment recipients and GitHub pull request comments left by Agent representatives are considered strong comment provenance if the comment relates to an action that affects them (i.e. where they are a stakeholder receiving a payment in the Executive). Strong comment provenance types are considered easy to modify by the commenting party, hence why they possess lower legitimacy than document provenance types. While these comments may store a record of the fact that they were edited, the edit history is not always publicly visible and therefore they are considered to possess high mutability.","contentHash":"243210fd3f1a459b35c0b55c58c6c628cc812ef5d8d3708fa2449369a5d7c195","addressRefs":[]},"d6c5909e-031c-43d9-984c-09e48985a1a1":{"id":"d6c5909e-031c-43d9-984c-09e48985a1a1","doc_no":"A.1.10.2.4.5.1.3","title":"OnChain Provenance","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":520,"content":"The provenance type \"onchain provenance\" is one of the most legitimate types of provenance. Onchain information refers to information obtained from Sky Protocol-associated smart contracts and is considered practically immutable and publicly visible. Due to the design of these decentralized storage providers such as IPFS, information referred to by on-chain values or content hashes but stored on IPFS or other similar services is also considered practically immutable. The compromise resistance of on-chain values is very strong and relies on a compromised controller of a Sky Protocol-associated smart contract or severe supply chain attack to manipulate information.","contentHash":"b4d24c1126b48be222b7ccd6494f89325741a5a94879f75ad4225bd1533de146","addressRefs":[]},"ea9dd463-9330-4a61-8958-4e2083a93101":{"id":"ea9dd463-9330-4a61-8958-4e2083a93101","doc_no":"A.1.10.2.4.5.1.4","title":"Strong Document Type Provenance","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":521,"content":"The provenance type \"strong document type provenance\" refers to actions approved by Sky Governance either directly (as through a Governance Poll) or through the inherent authority of the Sky Atlas. Examples of strong document type provenance are very hard to modify, as they cannot be modified or changed without a subsequent vote. They are always public in nature, as they are either required to be voted on or refer to the Sky Atlas which is publicly accessible. There is practically no account compromise risk with this category of provenance as all changes go through a vote and review process. Accordingly, strong document type provenance is considered one of the most legitimate types of provenance.","contentHash":"ad47ff02d8ac4aea54fd9dda49fcaeeb789d173cdc4e5d538849931259c7bbca","addressRefs":[]},"9f3b48a1-2b3e-41f0-b352-2c39aec28118":{"id":"9f3b48a1-2b3e-41f0-b352-2c39aec28118","doc_no":"A.1.10.2.4.5.1.5","title":"Provenance URLs","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":522,"content":"The Governance Point can leave comments in the designated columns \"Reasoning URL\" and \"Authority URL\". These comments typically provide instances of the ‘strong comment type’ of provenance and therefore authorize the execution of executive actions using the authority provided to the commenting party by the Atlas. The provenance URLs always correspond to comments in the Spell code.","contentHash":"405e25bd059410be0016c15e70d6dc069ab993b4e8ea901768e23a074c17b8c7","addressRefs":[]},"4c37fa46-1853-4bf2-a9fa-edae67da0fa2":{"id":"4c37fa46-1853-4bf2-a9fa-edae67da0fa2","doc_no":"A.1.10.2.4.5.2","title":"Confirmation By Technical Point","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":523,"content":"The Executive Sheet includes a column titled \"Technical Confirm.\" Items requiring confirmation by the Technical Point must be marked as \"Confirmed\" by the end of the day (UTC) Friday week 1.","contentHash":"7d31c2403b09121d233e9a0cdfea07b90633ff9d9e9ac2f607b4573ae2e52d0c","addressRefs":[]},"26133c1d-29da-42de-b9a2-00f4e13699f2":{"id":"26133c1d-29da-42de-b9a2-00f4e13699f2","doc_no":"A.1.10.2.4.5.3","title":"Confirmation By Content Liaisons","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":524,"content":"The Executive Sheet includes a column titled \"Liaison Confirm.\" Items requiring confirmation by the Content Liaisons must be marked as \"Confirmed\" by the end of the day (UTC) week 1 Friday. The Executive Sheet can name several different Content Liaisons, and the confirmation should only be done for the items the different Content Liaisons are responsible for.\n\nThe Content Liaisons do not have access to edit the Executive Sheet, and therefore leave a comment in the document at the appropriate cell to provide confirmation. After the Content Liaisons confirm their items by leaving a comment, the Governance Point edits the Executive Sheet from \"Unconfirmed\" to \"Confirmed\". The comments are only made for cells of the type \"Derived\".\n\nItems requiring confirmation include, for example, addresses, token amounts, parameter values, etc.","contentHash":"e884f2d915e9a52a5033299640834bbbfee95a113d9323339989efe007816201","addressRefs":[]},"5370113e-97ef-438a-ad16-69caad421fe4":{"id":"5370113e-97ef-438a-ad16-69caad421fe4","doc_no":"A.1.10.2.4.5.4","title":"Confirmation By Governance","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":525,"content":"The Executive Sheet includes a column titled \"Governance Confirm.\" Items requiring confirmation by Governance must be marked as \"Confirmed\" by the end of the day (UTC) week 1 Friday.","contentHash":"2985252852dacc31539c51a83e99cd34298ef816432da04cca15ebc246c9aa0c","addressRefs":[]},"ddf293ed-a846-480c-99ab-cb429a789c93":{"id":"ddf293ed-a846-480c-99ab-cb429a789c93","doc_no":"A.1.10.2.4.5.5","title":"Summary Checklist","type":"Core","depth":6,"parentId":"558451e8-1b04-48ce-bcb2-9c69ba22929b","order":526,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-creation.md) outlines the items for the confirmation process that should be done.","contentHash":"03fad8aa2b1b7a81d4a726180d45bb22c2475977368f08de3e18e3f6aa72e95a","addressRefs":[]},"9f291bda-cace-4787-b31b-24b8b42bdd27":{"id":"9f291bda-cace-4787-b31b-24b8b42bdd27","doc_no":"A.1.10.2.4.6","title":"Governance Point Finalizes Executive Sheet Week 1 Friday (Step 6)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":527,"content":"On Friday week 1, the Governance Point must make sure that the Executive Sheet is finalized and ready for handover to the Spell Team. This includes verifying that all required fields are completed, the content aligns with decisions made during the GovOps meeting, and all financial details are accurate. The Governance Point must notify the Spell Team in the #govops channel that the Executive Sheet is finalized. Any updates to the Executive Sheet made after Friday, week 1, must follow the procedure in [A.1.10.2.4.8.3.8 - Core Facilitator Must Notify Spell Team Of Changes](e3d137d7-3244-497b-b065-25cc2dffafeb).","contentHash":"1a9d8c2af50718d7a9d2abc560081267a6662d37a8ce252605c8d460019520d4","addressRefs":[]},"ed4254b8-983d-4cf9-acc1-0bb9130ec2e2":{"id":"ed4254b8-983d-4cf9-acc1-0bb9130ec2e2","doc_no":"A.1.10.2.4.6.1","title":"Governance Point Must Ensure The Executive Sheet Is Completed","type":"Core","depth":6,"parentId":"9f291bda-cace-4787-b31b-24b8b42bdd27","order":528,"content":"The Governance Point is responsible for ensuring that the Executive Sheet is fully completed and accurate. This includes the following:\n\n- That all fields in the Executive Sheet are filled in with the required information, including URLs, figures, and confirmations. For any incomplete items (e.g., awaiting final figures), they must be marked with a `TODO` tag.\n- That all items included in the Executive Sheet were discussed and approved during the GovOps meeting.\n    - No approved items from the discussions can be omitted without a valid reason.\n- That the financial transfers are accurate.\n    - USDS transfers must be rounded up to the nearest whole number (no decimal points).\n    - SKY transfers must be listed to exactly two decimal places.\n    - Verify that the checksum for USDS and SKY transfers is accurate.\n- The Spell items must be listed in order of importance for an average SKY voter except when there are order of operations concerns.","contentHash":"1d8593c8b1e929a746aace8ed734b4a745167aa57fbcb338a2fd2c8a3b58046b","addressRefs":[]},"d246530d-693c-4b1f-b139-2c3fef8b1de0":{"id":"d246530d-693c-4b1f-b139-2c3fef8b1de0","doc_no":"A.1.10.2.4.6.2","title":"Summary Checklist","type":"Core","depth":6,"parentId":"9f291bda-cace-4787-b31b-24b8b42bdd27","order":529,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-review.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/spell-sheet-review.md) outlines the items for the finalization process that should be done.","contentHash":"8635753d19853b07e8215ddaac49f33dedde7b5306461be9dcba3d39f1c023bb","addressRefs":[]},"60aac647-4fa3-4c1c-b9d4-8ababf001958":{"id":"60aac647-4fa3-4c1c-b9d4-8ababf001958","doc_no":"A.1.10.2.4.7","title":"Spell Crafter Crafts Spell Week 2 Monday (Step 7)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":530,"content":"The Spell Crafter must ensure that the Spell is crafted and completed on Monday week 2.","contentHash":"3061ae1de3f5739ea8fd338ec3c543696baf65aba34f9bd571d4975a3649ae86","addressRefs":[]},"510651ca-5a9a-4ac1-ba69-f3c160e185d2":{"id":"510651ca-5a9a-4ac1-ba69-f3c160e185d2","doc_no":"A.1.10.2.4.7.1","title":"Spell Crafting Workflow","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":531,"content":"In the Development Stage, the Spell Crafter writes the code for the Spell based on the contents of the Executive Sheet. The output of the Development Process is a Pull Request containing the code for the Spell that is ready for review. In performing the Development Stage, the Crafter takes the steps set forth in the checklists found here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md).","contentHash":"5eca68118142e8bb8f3bc06c25214943f784afeece502b91e85066dc678d2113","addressRefs":[]},"c714f3b3-d11a-4089-89a5-0183937cb8dc":{"id":"c714f3b3-d11a-4089-89a5-0183937cb8dc","doc_no":"A.1.10.2.4.7.2","title":"Spell Crafting Rules","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":532,"content":"The Crafter must comply with a number of rules when carrying out their role and responsibilities in Spell development. These rules are generally aimed at maximizing the safety and security of the Spell and are set out in the subdocuments herein.","contentHash":"24ab798ece8bdccc8082cd53c0b9fa34f33b4dceb05c021681a7c629cf6c9c02","addressRefs":[]},"3889281f-3306-4701-b1a3-5e0707bb7ef8":{"id":"3889281f-3306-4701-b1a3-5e0707bb7ef8","doc_no":"A.1.10.2.4.7.2.1","title":"Previous Spell Code Cleanup","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":533,"content":"Before developing the current Spell, the designated Crafter must clean up the previous Spell code. Code cleanup includes the `DssSpell.sol` (Spell code), `DssSpell.t.sol` (Spell code tests) and `config.sol`(deployed Spell information) files. In this process of code cleanup, the Crafter must remove unused interfaces as well as Spell code and test code from the last Spell. If relevant, they must also clean up any dependency files from the previous Spell that are not being used for the current Spell.","contentHash":"1dfa1497de64dfececf8174e02358dc8ccf64021f20817011bf2e3ce5260faf5","addressRefs":[]},"cff7d85c-2bbb-4f93-afa8-0bcfabcb838d":{"id":"cff7d85c-2bbb-4f93-afa8-0bcfabcb838d","doc_no":"A.1.10.2.4.7.2.2","title":"The Executive Sheet Serves As Source Of Truth","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":534,"content":"The Crafter must use the Executive Sheet as their key reference document and source of truth while developing the Spell. While the Executive Document is the instruction document for the Executive Process, the Executive Sheet is available earlier which enables the Crafter to begin Spell development at an earlier stage.","contentHash":"6da8c582c043d792d72d69eb59d218b95b9065cfe82ab495dc299fea018d19ef","addressRefs":[]},"816601b0-2fdf-4c6d-9c63-a5ef5d4bebbd":{"id":"816601b0-2fdf-4c6d-9c63-a5ef5d4bebbd","doc_no":"A.1.10.2.4.7.2.3","title":"The Crafter Is The Only Party Permitted To Approve GitHub Suggestions","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":535,"content":"The designated Crafter is the only person or entity permitted to commit GitHub code suggestions to the Spell. The Crafter can only commit suggestions that have been made by a designated Reviewer for the particular Spell. However, using GitHub suggestions is generally discouraged while developing the Spell.","contentHash":"c3ec1ffcd8b83869bbf6a21a434b510d674fb6c7342e3103ec6473c00fa32ab7","addressRefs":[]},"1a0d9151-df9c-403d-a38c-b7d0afc1f8a9":{"id":"1a0d9151-df9c-403d-a38c-b7d0afc1f8a9","doc_no":"A.1.10.2.4.7.2.4","title":"Crafter Master Branch Safety Check","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":536,"content":"In order to ensure that no malicious maintenance pull requests have been merged, the Crafter must check that the latest commit made to the \"master\" (or \"main\") branch of the Spell repository is the commit that merged the last Spell to master.","contentHash":"0856d255b909187ee804285b65ccc5da229e5c220d221a31223d9dd6da8af205","addressRefs":[]},"12c126be-0535-4147-a17e-91f670ad8339":{"id":"12c126be-0535-4147-a17e-91f670ad8339","doc_no":"A.1.10.2.4.7.2.5","title":"Tests Must Pass Before Crafter Provides Spell to Reviewers","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":537,"content":"Before marking a Spell’s Pull Request as \"ready for review\", the Crafter must ensure that both continuous integration tests and locally run tests are all passing successfully. The only exception to this rule is when the continuous integration tests are broken at no fault of the Spell Team - due to a GitHub failure or otherwise - in which case the Spell can be marked as \"ready for review\" if locally run tests are passing. The Crafter must not remove or disable failing tests in order to bypass this rule.","contentHash":"f6d59e659b8177d1640262711a71e4c43bef06e35627d4963766b4ab9cb3eea1","addressRefs":[]},"2c8e81bf-b79a-486f-80eb-bd9b15464695":{"id":"2c8e81bf-b79a-486f-80eb-bd9b15464695","doc_no":"A.1.10.2.4.7.3","title":"Process For Handling Technical Issues","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":538,"content":"The Crafter plays a key role in the process for identifying, analyzing, and resolving technical issues like bugs, mistakes, and exploits when they arise during the Spell development process. Other stakeholders, including the Spell Reviewer and Core Facilitator, also play an important role. This process is set out in the subdocuments herein.","contentHash":"41a47999f647965acb489660d1cadaf477edbb9e8c702eda1d213007809a8aa1","addressRefs":[]},"38a261c4-de67-429e-a6f2-4f8ca470a56e":{"id":"38a261c4-de67-429e-a6f2-4f8ca470a56e","doc_no":"A.1.10.2.4.7.3.1","title":"Issue Detection and Classification","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":539,"content":"When a technical issue is encountered, the party discovering the issue (whether the Crafter, a Reviewer, or another party) must determine whether the issue is either a mistake, a bug, or an exploit. The issue should also be classified as either a result of collusion or a genuine accident. The Spell Team must notify the Core Facilitator of technical issues that require input or adjustments from outside the Spell Team. Note that if a Crafter makes an error in their original development of the Spell, but discovers their own mistake and corrects it before the Reviewers commence the review process, this should not be treated as a technical issue per this handling process.","contentHash":"6e3caed44cc7c1873191911c382228b5b1a67e56fc2d88241661fc03b48f53b4","addressRefs":[]},"86a2c5ba-ae8f-4a3d-8f56-124cd27580c8":{"id":"86a2c5ba-ae8f-4a3d-8f56-124cd27580c8","doc_no":"A.1.10.2.4.7.3.2","title":"Issue Analysis and Evidence Capture","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":540,"content":"Once a technical issue has been categorized as an instance of a mistake, bug or exploit, the party discovering the issue must prepare documentation of the issue. This generally involves investigating the impacts of the issue, determining how the issue arose, and documenting how the issue manifests. In cases where the issue may be non-technical in nature - such as possible instances of collusion - supporting evidence should be captured, which supports the argument that a non-technical issue may be present. This evidence should be captured in a manner that does not permit bad actors to manipulate or erase the evidence through methods such as editing or deleting messages.","contentHash":"c0ebc6f1488fa0646820e21740d189f45264b625dde1113803ad96f8baa75a63","addressRefs":[]},"b5740bb5-6895-48fe-bb16-01a9c5605eb1":{"id":"b5740bb5-6895-48fe-bb16-01a9c5605eb1","doc_no":"A.1.10.2.4.7.3.3","title":"Determining the Handling Party","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":541,"content":"Once a technical issue has been classified and evidence supporting its existence is collected, an entity needs to be designated as the handling party for resolving the issue. This party will typically be the Core Facilitator. However, if there is a non-trivial chance that the Core Facilitator will ignore or downplay the issue, another entity should serve as the handling party.","contentHash":"1a5891ef323b11eacc063c32561e48adfc202df89841b92df633d3aa61cb6ef9","addressRefs":[]},"b9cfe356-2909-4f1b-99c9-0a4c98f826d4":{"id":"b9cfe356-2909-4f1b-99c9-0a4c98f826d4","doc_no":"A.1.10.2.4.7.3.4","title":"Publicly Reporting the Issue","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":542,"content":"Discovered issues must be reported publicly unless doing so poses a threat to the security of the Sky Protocol. Technical issues that are currently or likely to become, actively exploitable must not be discussed in a public manner, as this poses a threat to the security of the Sky Protocol.","contentHash":"1e54fe25f33a315d8b91aefa0a60d12beac037379e25c6b1687af0374089bed9","addressRefs":[]},"8b86845a-6d47-4834-9d7d-36ecef988a23":{"id":"8b86845a-6d47-4834-9d7d-36ecef988a23","doc_no":"A.1.10.2.4.7.3.5","title":"Resolving the Issue and Following Up","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":543,"content":"The Crafter or Reviewer, if they discovered the technical issue, should address or remedy the issue as necessary to resolve it. The handling party (typically the Core Facilitator) must follow up to ensure that the technical issue has been resolved. If the issue poses a threat to the Sky Protocol - such as an exploit or instance of collusion - it should be followed up on as a matter of urgency by the handling party.","contentHash":"9ba3314df96dbd76478e9b7264ce78f421a9b189094e984cf4f843409c371e5b","addressRefs":[]},"cffb2455-0b31-4a0c-8ec7-2de99392b236":{"id":"cffb2455-0b31-4a0c-8ec7-2de99392b236","doc_no":"A.1.10.2.4.7.3.6","title":"Issue Retrospective","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":544,"content":"Following the resolution of a technical issue, the parties involved in the development process, or other relevant processes leading to the issue arising, must document how the issue arose. These parties (often the Crafter or Reviewer) should also detail any measures that were previously in place to prevent this type of issue occurring, and any measures that can be implemented going forward in order to prevent the same issue from occurring again in the future.","contentHash":"adf4b939f1317cb996e089715cbf6f0d16ceb78ffd5ea0937277baae671304dc","addressRefs":[]},"bd45083c-50de-47d2-b0c3-808c04f726e3":{"id":"bd45083c-50de-47d2-b0c3-808c04f726e3","doc_no":"A.1.10.2.4.7.4","title":"Spell Team Operational Principles","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":545,"content":"As a core member of the Spell Team, the Crafter must comply with the Spell Team Operational Principles throughout their involvement in the Spell development process. These principles apply to both Spell crafting and Spell reviewing processes, and have been included in the documentation of both. These principles are set out in the subdocuments herein.","contentHash":"ed32e7c4659f904dd51c9f59262cd83aba3abd2e77e2f1d5d7ab00ab9722a470","addressRefs":[]},"3f01cb21-b2ef-4b09-9617-be0435998740":{"id":"3f01cb21-b2ef-4b09-9617-be0435998740","doc_no":"A.1.10.2.4.7.4.1","title":"Security First","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":546,"content":"Any choice between efficiency and security must always be made to maximize security, even at the cost of time, process inefficiency, or gas cost. Smart contract system designs as well as individual smart contracts, their code, and their interactions must always prioritize increased security over increased efficiency, reduced gas cost, or any other benefits. Rules and processes must always maximize security and safety, even at the cost of inefficiency, repetitiveness, longer review or audit timelines, or other drawbacks.","contentHash":"6a8850b2f7a00d8ab5c2583650377f7875b76e0551563b45016f95328e20f227","addressRefs":[]},"b5daecf9-d4fb-4291-88e0-b08b6e39688e":{"id":"b5daecf9-d4fb-4291-88e0-b08b6e39688e","doc_no":"A.1.10.2.4.7.4.2","title":"Attention to Detail","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":547,"content":"Developing, modifying or reviewing code should be done line by line. No change, issue or fix is too minor or unimportant to be commented on or addressed. Sky Core Contracts are immutable, and disabling them often requires waiting for a long period. As such, bugs and exploits should never be present in production code, as they are typically difficult to fix and their presence harms the reputation of the Sky Protocol. Any deployed contract that contains a bug indicates that the existing quality control, auditing, and review processes are not adequately preventing bugs.","contentHash":"3de524b3bbbeb1328a6e3f65fa379f346d1a852fa3db6701df2faad39ff871ee","addressRefs":[]},"361f1e3c-e974-4f58-98bb-13c7adea4c06":{"id":"361f1e3c-e974-4f58-98bb-13c7adea4c06","doc_no":"A.1.10.2.4.7.4.3","title":"Minimizing Complexity","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":548,"content":"Smart contract system designs, as well as individual smart contracts, their code, and their interactions must always use a simpler design over a more complex design, unless the more complex design provides a significant net increase to the safety and security of the Sky Protocol.","contentHash":"623f13e5e3c3a862a7e3c76e9bd07eb7b10fc06aea6b7c30244af3dc212f8edb","addressRefs":[]},"aa0a8049-f883-4366-9924-6651aeec14e6":{"id":"aa0a8049-f883-4366-9924-6651aeec14e6","doc_no":"A.1.10.2.4.7.4.4","title":"Lindy-Based Risk Aversion","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":549,"content":"The \"Lindy Effect\" states that the longer something has been in existence in its current state, the longer its remaining life expectancy. The \"Lindy\" of a system or smart contract refers to the duration it has been operating in its current state and therefore implies its future stability. Specifically, the \"Lindy\" of immutable systems uses their history of safe and secure operation as a predictor of future safety and security. It is considered best practice to consider the \"Lindy\" of systems, elements,and smart contracts when evaluating their use or inclusion in the wider system of the Sky Protocol.","contentHash":"b97b1df174a446ed4909ed5fafd766286cb435651fab611d4f7b43251a436fc1","addressRefs":[]},"e5a69e08-353b-41ad-9cff-aa2f0b8199c6":{"id":"e5a69e08-353b-41ad-9cff-aa2f0b8199c6","doc_no":"A.1.10.2.4.7.4.5","title":"Chesterton’s Fence","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":550,"content":"Chesterton’s Fence is a principle that states that changes must not be made to the current state of affairs unless the reasoning behind the current state of affairs is understood and can be explained. Changes to the Sky Protocol must only be proposed after the context - such as the reasoning, actions, and history - leading to the thing’s current state are known and can be explained by the party proposing the change. Changes must not be approved by team members or otherwise accepted until all parties responsible for overseeing, checking, or reviewing the change are aware of the context behind the current state of affairs as it exists before the change is enacted.","contentHash":"29c0d499756c9d27f68df15a176bed5fc1f8f56b3a0d404bbca5dc0f7d56ebf9","addressRefs":[]},"c6ff5871-72bc-471a-a8fd-34f738098219":{"id":"c6ff5871-72bc-471a-a8fd-34f738098219","doc_no":"A.1.10.2.4.7.4.6","title":"Existing Process Adherence","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":551,"content":"All existing Sky processes and patterns, whether pertaining to rules, processes, systems, smart contracts, or code, must be complied with. If regular operation is impossible due to a technical limitation or otherwise, it is permitted so long as it does not compromise the safety or security of the Sky Protocol in any way. New patterns developed in this way must prioritize the safety and security of the Sky Protocol over all other considerations and should be as similar to old patterns as possible. However, deviation from industry norms and best practices is encouraged so long as they are made in the interest of maximizing security. Any deviations by the Crafter or Reviewers must be communicated to the Core Facilitator.","contentHash":"325d1c41c2f1cb89a47dd37fc9a15bc8687a26a7177e2cb54b9f56d49bbb8464","addressRefs":[]},"5a4e1225-6151-4eb0-ae6b-5644f15b1b12":{"id":"5a4e1225-6151-4eb0-ae6b-5644f15b1b12","doc_no":"A.1.10.2.4.7.4.7","title":"Tenth Man Mandate","type":"Core","depth":6,"parentId":"60aac647-4fa3-4c1c-b9d4-8ababf001958","order":552,"content":"If a group of people making a decision unanimously holds a certain opinion, all make the same assumption or all come to the same conclusion, it is the responsibility of one member of the group to assume that the rest of the group is incorrect. The member of the group assigned to hold this contrarian viewpoint is referred to as the ‘tenth man’ and must attempt to disprove the group’s decision. Where the ‘tenth man’ is able to provide compelling arguments against the group’s conclusion, the decision must be reassessed.","contentHash":"88dca3df541cdd8e09ea7cec258fd397937ab5eb5dc1debd70da974276238b1c","addressRefs":[]},"1df24674-3095-44a7-b1b6-cb583b0787dd":{"id":"1df24674-3095-44a7-b1b6-cb583b0787dd","doc_no":"A.1.10.2.4.8","title":"Core Facilitator Creates And Finalizes Executive Document Week 2 Tuesday (Step 8)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":553,"content":"The process for the creation, review, and finalization of the Executive Document is outlined in the subdocuments herein.","contentHash":"78b43434f2ca7c2a9ad10f0b3038cab221b3f1429eaa88dd9e7df536db0fadde","addressRefs":[]},"1fcee4d2-912e-478c-ac81-0ce1f48054a7":{"id":"1fcee4d2-912e-478c-ac81-0ce1f48054a7","doc_no":"A.1.10.2.4.8.1","title":"Guiding Principles For Crafting The Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":554,"content":"The Executive Document process is guided by the core values of clarity, transparency and legitimacy. The document must balance its technical and implementation-focused nature with the need to remain clear and accessible to all voters. The Core Facilitator, responsible for producing the Executive Document, must ensure adherence to these principles as outlined in the subdocuments.","contentHash":"d9b3a9fea49bb382c6714ddb929972ef81dd726ac6c0d0d4bef30d842a7b110c","addressRefs":[]},"aefa846c-b4af-444a-a22e-39a9a8839410":{"id":"aefa846c-b4af-444a-a22e-39a9a8839410","doc_no":"A.1.10.2.4.8.1.1","title":"Providing Voters With Sufficient Information","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":555,"content":"The Core Facilitator must ensure that voters have access to sufficient information to make informed decisions. This might include:\n\n- Links to documentation or discussions related to the actions included in the Executive Document.\n- Summaries of the actions included in the Executive Document, created by unbiased and knowledgeable third parties.\n- Links to any analysis published by DAO-funded entities regarding the actions in the Executive Document.\n- Links to well-maintained resources describing the nature of any parameters that may be changed if the Executive Proposal passes.\n\nProviding accessible and complete information is essential to maintaining the legitimacy of the process. Voters should not later regret their vote due to a lack of understanding of the actions they voted on.","contentHash":"68f7951de046afa4a1084aa67dce7b13c7772b308358aa4caf2f5e5b2104bf70","addressRefs":[]},"f494539b-e704-409e-843e-361dd6959603":{"id":"f494539b-e704-409e-843e-361dd6959603","doc_no":"A.1.10.2.4.8.1.2","title":"Ensuring Transparency And Clarity","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":556,"content":"The Core Facilitator must ensure that the Executive Document is clear, transparent, and accessible to all voters. This involves eliminating ambiguity and confusion to the greatest extent possible while balancing technical detail with readability. Voters should clearly understand:\n\n- The effects and impacts of the Executive Vote if passed.\n- The processes that led to each item being included in the Executive Document.\n- The identities (pseudonymous or entity-level) of those responsible for publishing, writing, and reviewing the Executive Vote.\n\nThe goal is to ensure that voters are always provided with information on why an item is included, what will happen if the Executive Vote passes, or who is responsible for its contents.\n\nClarity reduces the risk of disruption, confusion, or a breakdown of legitimacy in the governance process.","contentHash":"119475da554653f99a50213b8cecd3179fba41f1155ee48c483412f186ee4466","addressRefs":[]},"3316956f-2e70-4106-92af-da4a2e26c043":{"id":"3316956f-2e70-4106-92af-da4a2e26c043","doc_no":"A.1.10.2.4.8.1.3","title":"Organizing For Maximum Impact","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":557,"content":"The Core Facilitator must organize the Executive Document to maximize readability and comprehension for voters. While transparency and access to information are essential, the document should avoid unnecessary length or complexity.\n\nBest Practices for organization:\n\n- Use strategic hyperlinks and text formatting to reduce the document's length while maintaining accessibility.\n- Regularly review and update templates to eliminate unnecessary content.\n- Present information in a logical order, prioritizing the most critical actions and details.\n\nA concise and well-structured document increases the likelihood that voters will read, understand, and consider the actions on which they are voting.","contentHash":"b5f52c71daca740a94e266c497076d43e7571b68dd826413830b44e1227abdc8","addressRefs":[]},"1247b21a-b3b6-4dcd-ad5f-dbfa50d7ccfe":{"id":"1247b21a-b3b6-4dcd-ad5f-dbfa50d7ccfe","doc_no":"A.1.10.2.4.8.1.4","title":"Balancing Technical Detail And Accessibility","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":558,"content":"The Core Facilitator must ensure that the Executive Document balances technical detail with readability. Voters should not require in-depth technical knowledge of the Sky Protocol to understand the Executive Document.\nGuidelines for Technical Detail:\n\n- Avoid including excessive technical details that obscure clarity or clutter the Executive Document.\n- Include technical details only when they are strictly necessary, such as:\n    - In emergency or urgent responses when technical details are the primary focus of the proposal.\n    - For non-urgent technical fixes or housekeeping when technical details are relevant, but should be given lower priority compared to other actions in the Executive Vote.\n\nIn cases where technical details are included, the Governance Point must ensure they fully understand the technical aspects themselves to present them accurately and clearly.\n\nExcessive technical detail can overwhelm voters and obscure the document's primary purpose. By carefully managing technical content, the Core Facilitator ensures that the document remains accessible and focused.","contentHash":"08b27fc2c3be6b64ebd0da14868f7f0960fadb400f04f34c68e70fec1fb010f5","addressRefs":[]},"756c8cd0-9c53-4c98-8368-50d635fec7db":{"id":"756c8cd0-9c53-4c98-8368-50d635fec7db","doc_no":"A.1.10.2.4.8.2","title":"Structure Of The Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":559,"content":"The Executive Document is a Markdown document created and stored in the executive-votes GitHub repository. It serves as the primary communication tool for presenting the contents of an Executive Vote and is divided into several key sections, each serving a specific purpose in the governance process.","contentHash":"b56c0e5ecf28f5dd6f4e24c62733bf3ad3e66f5d084ee41b68da5c58d38fb6ef","addressRefs":[]},"f57aab8a-efc2-42aa-83e1-367c91907777":{"id":"f57aab8a-efc2-42aa-83e1-367c91907777","doc_no":"A.1.10.2.4.8.2.1","title":"Content And Metadata Fields","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":560,"content":"The Executive Document contains both text content and metadata fields, which are essential for its functionality and clarity. These include:\n\n- The title field provides a concise and descriptive summary of the Executive Document, making it easy for stakeholders to identify the proposal.\n- The summary field offers a high-level overview of the actions included in the Spell, helping voters quickly understand the scope and purpose of the proposal.\n- The date field ensures that the proposal is aligned with the governance schedule and provides a clear reference for when the Spell is intended to be executed. The date specifies the Target Date of the Spell in UTC time.\n- The address field contains the Ethereum address of the deployed Mainnet Spell on the blockchain, allowing stakeholders to verify its contents and execution status. When the Executive Vote is published on the Voting Portal the Spell address is a hyperlink that links to Etherscan.","contentHash":"5c7339475051ff95b8b9d42216febd81f64d9efae323fda3d4dfd1b2855c85c1","addressRefs":[]},"6656674a-c598-474d-b8a7-64d7dda3bd91":{"id":"6656674a-c598-474d-b8a7-64d7dda3bd91","doc_no":"A.1.10.2.4.8.2.2","title":"Markdown Headings","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":561,"content":"The document uses different levels of Markdown headings to organize its content into distinct sections:\n\n- First-level heading is used for the title of the document.\n- Second-level headings are used for the four major sections of the Executive Document: Executive Summary, Proposal Details, Review, and Resources.\n- Third-level headings are used within the Proposal Details section to describe individual input executive actions. Each action is presented under its own third-level heading, making it easy to identify and review.\n- Fourth-level headings are used to describe specific derived actions within an input action. These headings provide additional context or detail necessary for understanding the implications of the input action, such as actions triggered by an Agent Spell or changes to market parameters.\n\nThis structured approach ensures that the document is both easy to navigate and comprehensive.","contentHash":"c1f02007100aa15b271d38a97a8bb2748b9f2b9de145fe0e569e788ef854154f","addressRefs":[]},"f3b16344-ebd0-43e7-978d-e91cbebe9010":{"id":"f3b16344-ebd0-43e7-978d-e91cbebe9010","doc_no":"A.1.10.2.4.8.2.3","title":"Preamble","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":562,"content":"The preamble serves as an introduction to the Executive Document, providing key context for voters. It identifies the entities responsible for crafting, publishing, and reviewing the proposal, ensuring accountability and transparency. Additionally, it includes a link to the voting guide, which helps new participants understand the voting process.","contentHash":"e25bfcc4382ae0aaa99b252af455ff28b18ddb3d181483781b9bb3d54a48edef","addressRefs":[]},"1e44fedd-79c0-4216-a533-a2c8b0f7c305":{"id":"1e44fedd-79c0-4216-a533-a2c8b0f7c305","doc_no":"A.1.10.2.4.8.2.4","title":"Executive Summary","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":563,"content":"The Executive Summary outlines the key actions that will occur if the proposal passes. It includes:\n\n- The GSM Pause Delay, which specifies the minimum time before the Spell can be executed and is enforced by ds-pause.\n- The Office-Hours Modifier, if applicable, which restricts execution to specific times.\n- The Expiration Date of the Spell.\n    - The Spell must always have an expiration date; it can’t be more than 90 days in the future, and the typical expiration window is 30 days.\n- A high-level explanation of the actions being performed in the Spell, presented in bullet-point form.\n\nThe summary should provide a high-level overview of the Executive Vote and ensure that SKY holders can quickly understand the scope and purpose of the proposal. This section also explains that voting for the proposal with SKY places support for these actions.","contentHash":"00ceb5fa64b1a92ed96cf5994c649a5aa421606a6a7037b4fbd64533c0961a80","addressRefs":[]},"d399f662-1b9a-40d0-b535-d3215d09cba1":{"id":"d399f662-1b9a-40d0-b535-d3215d09cba1","doc_no":"A.1.10.2.4.8.2.5","title":"Proposal Details","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":564,"content":"This section provides a detailed breakdown of each item included in the proposal. It includes:\n\n- Input executive actions, which are presented under third-level Markdown headings. Each action includes links to the authorization and proposal documents and explains the implications of the action if the proposal passes.\n- Derived actions, which are described under fourth-level Markdown headings when they provide additional context or detail necessary for understanding the implications of an input action. These headings are used to outline specific actions triggered by an input action, such as actions executed by a Prime Spell or changes to market parameters. Derived actions that are overly technical, redundant, or irrelevant to the proposal's primary focus may be excluded to maintain clarity and accessibility.\n\nThis section ensures that all actions are clearly explained and linked to their reasoning and authorization documents.","contentHash":"f995d24a1342051dd4307f8c929bfffc3fbabff519676d42a3c7da1d6fc8ac76","addressRefs":[]},"3de17a79-145a-4ec5-b43d-d8c371ee598e":{"id":"3de17a79-145a-4ec5-b43d-d8c371ee598e","doc_no":"A.1.10.2.4.8.2.6","title":"Best Practices","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":565,"content":"To ensure clarity and consistency, the Governance Point should adhere to the following practices when including items in the Executive Document:\n\n- **Headers and Bullet Points**:\n    - Each item should be separated by a header for clarity.\n    - Typically, two bullet points are included for each item: one for \"Authorization\" and one for \"Proposal.\"\n    - The \"Authorization\" link may lead to an Atlas document, a Governance Poll or a Forum Post, while the \"Proposal\" link is usually a Forum Post.\n- **Formatting for Key Values**:\n    - If the item involves amending a parameter or distributing funds, the relevant values should be marked in bold to emphasize the new outcomes that will take effect if the Executive Proposal passes.\n    - For transfers, Ethereum addresses should be included to provide transparency and direct access to transaction details.\n- **Use of Tables**:\n    - Tables are often used in the Executive Document to provide an easy-to-read overview of key information, such as parameter changes, funding distributions, or other technical details.","contentHash":"5ce88b615091e800847f41d10875b645cadd5eb1ef995ab8e939574ec53576e5","addressRefs":[]},"b6117ca8-0d19-47ad-a20e-2f6e5a55746e":{"id":"b6117ca8-0d19-47ad-a20e-2f6e5a55746e","doc_no":"A.1.10.2.4.8.2.7","title":"Review Section","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":566,"content":"The review section includes standardized language directing voters to the Sky Governance Forum for community debate and discussion. It encourages voters to review linked threads to inform their position before voting.","contentHash":"e11ec5ed1025ba0ceee464e13003f548e23f968b1392227b3f34554f718ace7e","addressRefs":[]},"aaa621d0-8886-4b32-a903-eee6e4a2f66f":{"id":"aaa621d0-8886-4b32-a903-eee6e4a2f66f","doc_no":"A.1.10.2.4.8.2.8","title":"Resources","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":567,"content":"The Resources section provides links to additional materials that help voters understand the governance process and stay informed about upcoming votes. These materials include:\n\n- The Operational Manual serves as a guide to governance processes, is included as a resource.\n- The Sky Governance Calendar is a resource for tracking upcoming votes and governance events.","contentHash":"30a52bf862570eab7889aafc7fe36781d52790dc69553801deb19fceebd05e5d","addressRefs":[]},"6d40ab22-bcf5-42c2-8a27-fef39fa43d6f":{"id":"6d40ab22-bcf5-42c2-8a27-fef39fa43d6f","doc_no":"A.1.10.2.4.8.3","title":"Core Facilitator Creates Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":568,"content":"The Core Facilitator must create the Executive Document. The subdocuments herein provide a step-by-step guide to the document’s creation.","contentHash":"03fefcc96b2863a9feb5f0977ca1f2c159dde777c7def2bf7fa9aee097e50afe","addressRefs":[]},"fba002f8-39ab-43c4-8c29-5f4f7cf86c49":{"id":"fba002f8-39ab-43c4-8c29-5f4f7cf86c49","doc_no":"A.1.10.2.4.8.3.1","title":"Core Facilitator Reviews The Executive Sheet","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":569,"content":"The Core Facilitator must thoroughly review the Executive Sheet. The technical information in the Executive Sheet must be identical to the Executive Document.","contentHash":"0af3d8a88357bf8031394992057e947d4f1b6f94951fd6813d80e62af54621ed","addressRefs":[]},"b99efbf0-a58d-429f-96a8-b4ca357da4fb":{"id":"b99efbf0-a58d-429f-96a8-b4ca357da4fb","doc_no":"A.1.10.2.4.8.3.2","title":"Core Facilitator Copies Executive Template","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":570,"content":"The template for the Executive Document is stored in the Executive Votes template directory ([https://github.com/sky-ecosystem/executive-votes/tree/main/templates](https://github.com/sky-ecosystem/executive-votes/tree/main/templates)) on GitHub. The Core Facilitator must copy the template into the working branch to draft the Executive Document.","contentHash":"44d55d21b1f7aede8769de6f7c1361c17f704c46a0f1eee377469839678730cc","addressRefs":[]},"15a1cb2b-6311-410c-a401-4d70f6132fc9":{"id":"15a1cb2b-6311-410c-a401-4d70f6132fc9","doc_no":"A.1.10.2.4.8.3.3","title":"Core Facilitator Updates Metadata","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":571,"content":"The Core Facilitator must update the metadata of the template. This includes updating the filename and dates to reflect the current values of the Executive Vote.\n\n- Rename the file to \"Executive vote - YYYY, MONTH, DD\". The filename must end with .md and must not contain any banned characters (e.g., \"<>:\"/?*|\"). The date in the filename should correspond to the day the Executive Vote will go live on the voting platform.\n- Replace the placeholder dates in the template with the correct dates for the Executive Vote. The exact time is not required for the Executive Vote and should therefore be left at midnight.","contentHash":"263cc89d4ff38371320b7d3add3538991440fdaa1c8a2d0a458d7bf943ee4c24","addressRefs":[]},"63c9d3b3-e155-4aee-bca1-9316da530878":{"id":"63c9d3b3-e155-4aee-bca1-9316da530878","doc_no":"A.1.10.2.4.8.3.4","title":"Core Facilitator Creates Title","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":572,"content":"The Core Facilitator must create a title for the Executive Document that clearly highlights the most impactful/important actions included in the proposal. This ensures that SKY holders can easily understand the purpose of the vote.","contentHash":"9495b0907b7f5ca8cd97c68e61fb894accb68384d608264f3b63a345dce41698","addressRefs":[]},"dd779187-bc53-448b-9171-89b4655494d1":{"id":"dd779187-bc53-448b-9171-89b4655494d1","doc_no":"A.1.10.2.4.8.3.5","title":"Core Facilitator Creates Summary","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":573,"content":"The Core Facilitator must create a summary that refers to every action included in the proposal. Under the Executive summary, the Core Facilitator must include the following details:\n\n1. Office-Hours Modifier:\n    - If the office-hours parameter has the value \"Yes\" and will be present in the Spell code, this must be explicitly mentioned:\n        - \"This Executive Proposal includes an office-hours modifier that means that it **can only be executed between 14:00 and 21:00 UTC, Monday - Friday**.\"\n2. GSM Pause Delay:\n    - The GSM Pause Delay period and affected items must be clearly communicated.\n    - The term \"GSM Pause Delay\" must include a link to the Atlas document specifying its definition [A.1.10.3.1 - Pause Delay](3c9545d9-775f-4149-88bf-7d297b5302c6).\n    - The current value of the GSM Pause Delay must include a link to the Atlas document specifying its value [A.1.10.3.1.2 - Pause Delay Current Value](db442d8a-8d98-47a2-b162-01c2adc22b67).\n3. Proposal Expiry:\n    - The expiry of the proposal must be explicitly noted, including the length of time for which the proposal is valid:\n        - \"If this Executive Proposal does not pass within 30 days, then it will expire and can no longer have any effect on the Sky Protocol.\"","contentHash":"7cbaa55c99d7a9d33f876a9422b80b04908be7b036775d2629c0188810f71e66","addressRefs":[]},"c99fbfde-bd39-42f6-b67d-f6b9cb7f3dce":{"id":"c99fbfde-bd39-42f6-b67d-f6b9cb7f3dce","doc_no":"A.1.10.2.4.8.3.6","title":"Core Facilitator Specifies Entities In Preamble","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":574,"content":"The Core Facilitator must specify the entities responsible for publishing the Executive Vote on the Voting Portal, as well as the Crafters and Reviewers of the executive code. The entities should be specified at the entity level.\n\n- The publishers of the Executive Vote are the Core Facilitator.\n- The Crafters and Reviewers alternate between Dewiz and Sidestream.\n- The Crafters and Reviewers are determined during the GovOps meeting and recorded in the Executive Sheet.","contentHash":"d960a1e12abefa56f03538c75a5fd6599ea842a0df01aa59fcac42c0946a6fdf","addressRefs":[]},"2724c79e-f6bf-42a2-8018-33b773ba3733":{"id":"2724c79e-f6bf-42a2-8018-33b773ba3733","doc_no":"A.1.10.2.4.8.3.7","title":"Core Facilitator Includes Every Item From Executive Sheet","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":575,"content":"The Core Facilitator must ensure that every item from the Executive Sheet is included in the details section of the Executive Document. These items should be presented in order of judged impact/importance. If the order of items in the Executive Document differs from the Executive Sheet, the Executive Sheet must be updated to match, maintaining consistency between the two documents.\n\nThe Core Facilitator must make sure that each item:\n\n- Includes links to the reasoning and authorization for its inclusion.\n- Provides additional links required for voters to understand the context surrounding the item’s inclusion.\n- Uses future-conditional language and clearly outlines the actions that will take place if the Executive Proposal passes. For example, phrasing such as \"If this Executive Proposal passes, then this action will take place\" ensures clarity and avoids ambiguity.\n- Has hyperlinked key parameters, terms, and contracts where appropriate, making it easier for voters to access relevant information. Ethereum and IPFS addresses should also be linked to provide direct access to technical details.\n\nThe Core Facilitator must also make sure that the parties implicated in the proposal outcome are aware of the wording used for each item in the Executive Document.","contentHash":"71d393f8f5f244753a4a6d86268cc08e2309a9f159ff1d8c7d738997611a71ce","addressRefs":[]},"e3d137d7-3244-497b-b065-25cc2dffafeb":{"id":"e3d137d7-3244-497b-b065-25cc2dffafeb","doc_no":"A.1.10.2.4.8.3.8","title":"Core Facilitator Must Notify Spell Team Of Changes","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":576,"content":"If any updates are made to the Executive Sheet during the Spell Process at a stage prior to the handover of the deployed Spell, the members of the Spell Team must be notified of the update. The notification must be done in Discord in the dedicated thread for the Executive Vote in the #govops channel.","contentHash":"917cddf81c17dbad9ee6aa1610f68f0ba6eb407dce9b6862d66bc01c0cdf3ca0","addressRefs":[]},"e33843ce-e536-4a74-b432-817dd1626f04":{"id":"e33843ce-e536-4a74-b432-817dd1626f04","doc_no":"A.1.10.2.4.8.3.9","title":"Core Facilitator Self-Review Executive Document Draft","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":577,"content":"The Core Facilitator must self-review the Executive Document to ensure it is clear, unambiguous, and free of errors. All \"$\" parameter signifiers must be replaced with their correct values, except for the Spell address, which remains unknown at this stage.\n\nOnce the document is finalized, the Core Facilitator must commit the changes and create a Pull Request to the executive-votes GitHub repository. The Core Facilitator must then request a review from another member of the Core Facilitator team.","contentHash":"ac2a4059c25ef61622cd4cae40afa4773cd74c556977f1281e2de994e175e429","addressRefs":[]},"711c0453-ce81-4e44-8590-d17c0b82fe26":{"id":"711c0453-ce81-4e44-8590-d17c0b82fe26","doc_no":"A.1.10.2.4.8.3.10","title":"Commits To The Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":578,"content":"Any member of the Core Facilitator team can commit changes to the Executive Document. The standard process is to request changes to the drafter of the Executive Document.","contentHash":"5d9a415e2359a398a49c2b329ab5dd22cfa1aac3f64855396a8af62562b9d5fd","addressRefs":[]},"ac23449a-ce35-45f6-aa9e-500404bfa2a4":{"id":"ac23449a-ce35-45f6-aa9e-500404bfa2a4","doc_no":"A.1.10.2.4.8.3.11","title":"Checklist For Core Facilitator Creating Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":579,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md) ensures that all steps in the Executive Document creation process are completed. The Core Facilitator should use this checklist as a final check before the official review.","contentHash":"475b7db93111cdeba676f14fd80618bf68a4ae545377905f55ddf7baa2b57a7c","addressRefs":[]},"95c1e447-704f-421e-a6c9-82f342e02a17":{"id":"95c1e447-704f-421e-a6c9-82f342e02a17","doc_no":"A.1.10.2.4.8.4","title":"Core Facilitator Review Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":580,"content":"Another member of the Core Facilitator team must review the Executive Document to ensure adherence to all specified conventions. As a general rule, the reviewer must not be the author of the Executive Document to provide independent validation. The detailed review process and criteria are specified in the relevant subdocuments.","contentHash":"accaf1713f0dece93930ea2f6743d1173882f42c9c64a851354527e30f1547f4","addressRefs":[]},"e6ffd366-1ba8-4c51-acc2-f94261bf6353":{"id":"e6ffd366-1ba8-4c51-acc2-f94261bf6353","doc_no":"A.1.10.2.4.8.4.1","title":"Core Facilitator Familiarizes With Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":581,"content":"The Core Facilitator conducting the official review must read the document in full to ensure that it is clear and unambiguous.","contentHash":"b5f759df6e65ed8ed5c9d1f0fc1204cefeb7a1c9d3bdc12339bc76c5101f12e7","addressRefs":[]},"65157925-4368-4c45-acf1-d454ffbc68d2":{"id":"65157925-4368-4c45-acf1-d454ffbc68d2","doc_no":"A.1.10.2.4.8.4.2","title":"Core Facilitator Verifies Information In Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":582,"content":"The Core Facilitator must make sure that the Executive Document is accurate and adheres to the specified conventions. The Core Facilitator must ensure that all the steps outlined in [A.1.10.2.4.8.3 - Core Facilitator Creates Executive Document](6d40ab22-bcf5-42c2-8a27-fef39fa43d6f) are followed.","contentHash":"bb21c8c9dba62a02304363da906f2c546b6704d77c1bb122eb2f46b0d085680a","addressRefs":[]},"c3055900-e3c0-4f7d-a233-402f1ebfcc62":{"id":"c3055900-e3c0-4f7d-a233-402f1ebfcc62","doc_no":"A.1.10.2.4.8.4.3","title":"Core Facilitator Finalize Review","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":583,"content":"After thoroughly reviewing the Executive Document, the Core Facilitator must communicate any issues or discrepancies to the Governance Point. The Governance Point must address all issues before the review is marked as complete. Once all issues are resolved, the reviewer must confirm that the document is ready for publication.","contentHash":"c9380a929de93171b9ec62466dfd0088c1eda5f817503acd037c902c3bba4ea1","addressRefs":[]},"d6e79bb0-1e04-43ef-a8e7-ebf22e29b600":{"id":"d6e79bb0-1e04-43ef-a8e7-ebf22e29b600","doc_no":"A.1.10.2.4.8.4.4","title":"Checklist For Reviewer Of Executive Vote","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":584,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-review-checklist.md](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-review-checklist.md) serves as a final verification tool for the reviewer of the Executive Document. It ensures that all aspects of the document have been reviewed and meet the required standards.","contentHash":"e2b616edfa2573434fdd27bb577f4698f03d8b2ad0b37373ed889e3a45f0eb39","addressRefs":[]},"ec5599fa-3b3c-4a29-8f00-e9d5075646e0":{"id":"ec5599fa-3b3c-4a29-8f00-e9d5075646e0","doc_no":"A.1.10.2.4.8.5","title":"Core Facilitator Finalizes Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":585,"content":"The Governance Point must finalize and merge the Executive Document on Week 2 Tuesday. The subdocuments herein specify the finalization process.","contentHash":"c9ed2be43774370f2482e754649bf8306ad7d92b44bd9bf539200ea0b03f581b","addressRefs":[]},"99bc6de0-9d6c-44d9-a82e-a0ddfd59647f":{"id":"99bc6de0-9d6c-44d9-a82e-a0ddfd59647f","doc_no":"A.1.10.2.4.8.5.1","title":"Core Facilitator Generates Hash Of Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":586,"content":"The Core Facilitator must generate the hash of the Executive Document. The hash must be verified by another member of the Core Facilitator team. The hash is then recorded as a comment in GitHub under the \"Conversation\" tab. This validation step ensures that potential hash mismatches or validation errors are identified and resolved early in the process.\n\nThe Core Facilitator’s comment typically includes:\n\n- The command used to generate the hash,\n- The resulting hash, and\n- A secondary tool used to validate the locally generated hash (Keccak-256 Online Tool, [https://emn178.github.io/online-tools/keccak_256.html](https://emn178.github.io/online-tools/keccak_256.html), is most commonly used).","contentHash":"3bd7551151fa855511b21883406ee64fa33079f530252c0e533a21665b5a74f8","addressRefs":[]},"966fa5d7-c640-4251-891c-a4a3c58bee8a":{"id":"966fa5d7-c640-4251-891c-a4a3c58bee8a","doc_no":"A.1.10.2.4.8.5.2","title":"Core Facilitator Merges Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":587,"content":"The Core Facilitator must merge the approved Pull Request for the Executive Document into the main branch of the executive-votes GitHub repository by 16:00 UTC. Before merging, the Core Facilitator must ensure that the Executive Document has been reviewed and approved by the designated reviewer. Merging into the main branch requires two approvals.","contentHash":"1e73373915f9ff8c0d775236cd9b37bb54791e6e72c2eb0864787276af1c0dc3","addressRefs":[]},"95c6809a-17a3-4741-b428-5ecb1b1f5b20":{"id":"95c6809a-17a3-4741-b428-5ecb1b1f5b20","doc_no":"A.1.10.2.4.8.5.3","title":"Core Facilitator Validates Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":588,"content":"The Core Facilitator must validate the Executive Document on the voting platform. This is done by pasting the raw URL of the document into the validation field and clicking the \"Validate\" button. The validation tool can be accessed at Executive Validator [(https://vote.sky.money/executive/create](https://vote.sky.money/executive/create)).\n\nThe raw URL can be found by opening the specific Markdown file for the Executive Document. On the file’s page, locate the Raw button near the top-right corner of the file viewer. Clicking the Raw button will open a new page. The URL of this new page is the \"raw URL.\"\n\nThe validation tool provides a preview of how the Executive Vote will appear on the voting platform, allowing the Core Facilitator to confirm the document's formatting and content.","contentHash":"770d44f334ff8080de9ffc72b2377c3d552ed4ebaedca8186280187167f186bf","addressRefs":[]},"16b6e606-f16e-4324-95d1-cc46be0d71bd":{"id":"16b6e606-f16e-4324-95d1-cc46be0d71bd","doc_no":"A.1.10.2.4.8.5.4","title":"Core Facilitator Shares Link And Hash Of Executive Document With Technical Point","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":589,"content":"The Core Facilitator must share the link to the merged Executive Document on GitHub and its hash with the Technical Point. This communication must be provided in a public manner, typically on Discord.","contentHash":"b4d7d34efad73b70327c2aa3db3a95c1cc761e75e1bcc13e43cb3269b8125bd8","addressRefs":[]},"84a87065-fbd8-43c1-b4ac-77d89ab98b6c":{"id":"84a87065-fbd8-43c1-b4ac-77d89ab98b6c","doc_no":"A.1.10.2.4.8.5.5","title":"Core Facilitator Must Communicate Executive Document With Media Liaison","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":590,"content":"The Core Facilitator must share the Executive Document with the Media Liaison. This is done via the #twitter-requests channel in the Growth Core Unit Discord. Both the document and the timeline should be shared.","contentHash":"8c01da2bed42dda9ceab8cd888f650d875f875db073673020d76f13220dc5ae3","addressRefs":[]},"cb3303a9-1383-408c-ac8a-9d31beae43cf":{"id":"cb3303a9-1383-408c-ac8a-9d31beae43cf","doc_no":"A.1.10.2.4.8.5.6","title":"Checklist For Core Facilitator Finalizing Executive Document","type":"Core","depth":6,"parentId":"1df24674-3095-44a7-b1b6-cb583b0787dd","order":591,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md#submission](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md#submission) serves as a final verification tool for the Core Facilitator finalizing the Executive Document. It ensures that all steps in the process are completed.","contentHash":"f61c6dac53bec8a73b91a94494ec73c9d3f09858f8ef6ffffe7b42c57d28470c","addressRefs":[]},"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12":{"id":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","doc_no":"A.1.10.2.4.9","title":"Spell Reviewers Review Spell Week 2 Tuesday (Step 9)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":592,"content":"The Spell Reviewers must review the Spell after the crafting is completed. The reviews should be done on Tuesday week 2.","contentHash":"d8a4e2ef377f7d99cf3442b3c8b1266df879845865705c1bade04867d94c50a4","addressRefs":[]},"4319b89d-a0e3-4e3c-bf99-0390053bd347":{"id":"4319b89d-a0e3-4e3c-bf99-0390053bd347","doc_no":"A.1.10.2.4.9.1","title":"Spell Reviewing Workflow","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":593,"content":"Spell Reviewers must comprehensively review the draft Spell in accordance with Reviewer checklists and testing requirements, set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-reviewer-mainnet-checklist.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-reviewer-mainnet-checklist.md).","contentHash":"96fabb36ca6d7591389819a56ca596701042d2cfe3503f22135c2bdb891841f2","addressRefs":[]},"fcc34865-894b-4fb8-b430-0957909ffe9f":{"id":"fcc34865-894b-4fb8-b430-0957909ffe9f","doc_no":"A.1.10.2.4.9.2","title":"Spell Reviewing Rules","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":594,"content":"Spell Reviewers must comply with a number of rules when carrying out their review functions throughout the Executive Process. These rules are generally aimed at maximizing the safety and security of the Spell.","contentHash":"016a3aafe0a4dcc345304fbad947cc4de451730e02df28d69374fd2e6288c0fb","addressRefs":[]},"32feb38a-043e-4715-9a3e-c94ee6fbf92f":{"id":"32feb38a-043e-4715-9a3e-c94ee6fbf92f","doc_no":"A.1.10.2.4.9.2.1","title":"Spell Reviewers Must Review All Spell Content","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":595,"content":"Spell Reviewers must review all relevant content in the Spell; it is prohibited for a Reviewer to selectively omit their review of specific content within a Spell. While unlikely, an actor may attempt to convince the Spell Reviewers that they should skip a section of checklist items within their review checklist and allow for a section of content to be reviewed by a party external to the current Spell Team. Any party encouraging selective review of content must be considered negligent or malicious, especially where the offending party is the Spell Crafter or another entity involved in Spell development.","contentHash":"965b86a7273ce3c7df768925d8459c885aa9868b0f8e0ec652f600498c6bb9de","addressRefs":[]},"a9be4af3-1824-4c67-9664-a9a52be438fb":{"id":"a9be4af3-1824-4c67-9664-a9a52be438fb","doc_no":"A.1.10.2.4.9.2.2","title":"Executive Document as Key Reference","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":596,"content":"For the Reviewers’ checks and review of the Spell before deployment, the Executive Document is the primary source of truth for the Spell.","contentHash":"ebc86ccae821ad8b8f6bfb7ee935ec92d038f171ecfa9101dc0bb346660a0542","addressRefs":[]},"952d9bdc-1298-49b5-a52f-11ab480a82b7":{"id":"952d9bdc-1298-49b5-a52f-11ab480a82b7","doc_no":"A.1.10.2.4.9.2.3","title":"A.1.9 -Spell Reviewer Direct Authoring Ban","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":597,"content":"Reviewers for a Spell are strictly prohibited from _directly_ committing, adding, contributing, or modifying code to a Spell they are reviewing.","contentHash":"ef8f7cf4aa1193acdb5741565c5174054fce61a04dd19f9613abc37d174a16c9","addressRefs":[]},"d3a48eb5-278e-4417-aae5-94b4ee7cf4ea":{"id":"d3a48eb5-278e-4417-aae5-94b4ee7cf4ea","doc_no":"A.1.10.2.4.9.2.4","title":"Spell Reviewers May Not Add or Change Content Through Pull Requests","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":598,"content":"Reviewers for a Spell are strictly prohibited from _indirectly_ committing, adding, contributing, or modifying code to the Spell they are reviewing. If a Reviewer added code via a Pull Request (even from a trusted party such as an Agent), this would be indirectly modifying the Spell code. This is not permitted.","contentHash":"a6b7d86b78a4432995730eb063df7d66002809b7cb7b0d8b214b75b9d264d670","addressRefs":[]},"eb22b81f-4f34-47c2-8d24-8c85909fb531":{"id":"eb22b81f-4f34-47c2-8d24-8c85909fb531","doc_no":"A.1.10.2.4.9.2.5","title":"Spell Reviewers May Not Approve GitHub Suggestions","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":599,"content":"The designated Crafter is the only person or entity permitted to commit GitHub code suggestions to the Spell. The Reviewers can make suggestions, but cannot commit those suggestions.","contentHash":"581007c99645e6e490632adc098c496d18c8e05a27cf82d05dec9f112cde1760","addressRefs":[]},"558e18e8-7277-4be6-895b-1f419069f4c8":{"id":"558e18e8-7277-4be6-895b-1f419069f4c8","doc_no":"A.1.10.2.4.9.2.6","title":"Spell Reviewers Must Raise Comments When They Find Issues","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":600,"content":"When Spell Reviewers find any issues within the current Spell, they must raise these to the Spell Team and other relevant actors via a comment in GitHub, relevant Discord channels, or other communications channels as necessary.","contentHash":"ad21f6795fe6aecb08229e0ceb8415acb5de76e48d090f1cf061e23b51e0a35c","addressRefs":[]},"ed3350d8-37c4-430e-a0f3-c2ee0692b801":{"id":"ed3350d8-37c4-430e-a0f3-c2ee0692b801","doc_no":"A.1.10.2.4.9.2.7","title":"Smart Contract Testing","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":601,"content":"Spell Reviewers must conduct smart contract testing in order to ensure that the Spell behaves as intended. Tests must be exhaustive and should cover every facet of code in the smart contract.","contentHash":"c771d2e0d4c0e5f823ee08701d1314ef4eaeeb60b3ea0005db213dde6ae3cf4b","addressRefs":[]},"1de9360f-c414-431c-abc4-cda5593cd870":{"id":"1de9360f-c414-431c-abc4-cda5593cd870","doc_no":"A.1.10.2.4.9.2.8","title":"Spell Reviewer Final Approval","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":602,"content":"As the Reviewers are prohibited from modifying the contents of a Spell via commits or authoring, the most important power they possess is whether to approve the progression of a Spell to its next stage. As such, a Reviewer approving the final deployed Spell for handover represents confirmation that they believe that the role of the Spell Team has been completed for the Spell. This means that they believe that the Spell has fulfilled the Spell Team’s role of creating a smart contract that performs the exact set of actions described in the Executive Document, with no actions omitted or additional actions present.","contentHash":"262c99b916ecfa3dc7a267d4520444f2d7efe10a8fede5bdf9686f56eb0ab1d7","addressRefs":[]},"83f1374d-aa42-4f1d-bea2-5326b578a2af":{"id":"83f1374d-aa42-4f1d-bea2-5326b578a2af","doc_no":"A.1.10.2.4.9.2.9","title":"Prohibition on Merging Pull Request","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":603,"content":"Spell Reviewers are prohibited from merging the Pull Request associated with a Spell. The only party permitted to merge a Spell’s Pull Request is the Crafter of that Spell.","contentHash":"f6f5c0d9ac1151e830c9c1f98828c34061238d1961ba7a59e6e018d1ba44fab5","addressRefs":[]},"357b6485-46fd-442a-ad6e-8ddff5ca4f7f":{"id":"357b6485-46fd-442a-ad6e-8ddff5ca4f7f","doc_no":"A.1.10.2.4.9.2.10","title":"Prohibition on Leaving GitHub Suggestions Post Deployment","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":604,"content":"Spell Reviewers are prohibited from leaving GitHub suggestions after the Spell has been deployed or archived.","contentHash":"2646c9812a3387f07465d524b4a36760880fc3109e527f489d83ce76e369a735","addressRefs":[]},"e3b236e9-972a-407b-81bf-1411b4d7de60":{"id":"e3b236e9-972a-407b-81bf-1411b4d7de60","doc_no":"A.1.10.2.4.9.3","title":"Process For Handling Technical Issues","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":605,"content":"The Reviewers play a key role in the process for identifying, analyzing and resolving technical issues like bugs, mistakes and exploits when they arise during the Spell development process. Other stakeholders, including the Spell Crafter and Core Facilitator, also play an important role. The technical issue process is outlined here [A.1.10.2.4.7.3 - Process For Handling Technical Issues](2c8e81bf-b79a-486f-80eb-bd9b15464695). All technical issues identified by Reviewers should follow the steps specified in this process","contentHash":"30d8a23e06f1de596a37b752280e63bd924708bde063bed541c66ae81f77bedb","addressRefs":[]},"71f8c21f-2d23-4c93-a710-efd365f1d405":{"id":"71f8c21f-2d23-4c93-a710-efd365f1d405","doc_no":"A.1.10.2.4.9.4","title":"Spell Team Operational Principles","type":"Core","depth":6,"parentId":"249a4dc7-35a3-4c5e-8b0e-fbfd53b5bd12","order":606,"content":"As a core member of the Spell Team, the Reviewers must comply with the Spell Team Operational Principles throughout their involvement in the Spell development process. These principles apply to both Spell crafting and Spell reviewing processes, and are outlined here [A.1.10.2.4.7.4 - Spell Team Operational Principles](bd45083c-50de-47d2-b0c3-808c04f726e3).","contentHash":"dfd55620cbc304960b85fead9c70ed9f52c2d7d31057adaa5ace8baa69111ac4","addressRefs":[]},"746bfb60-2d46-4064-a7f0-3d1d249463ee":{"id":"746bfb60-2d46-4064-a7f0-3d1d249463ee","doc_no":"A.1.10.2.4.10","title":"Spell Crafter Deploys Spell On Target Date (Step 10)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":607,"content":"The Spell Crafter follows the process specified herein to deploy the Spell.","contentHash":"57523ccdc2bcff16f0976cc9f7a36f7f5b15be5ab2ae191a9672a217881a7fe2","addressRefs":[]},"59638793-d1ed-4d6c-9d34-d9359ecfd100":{"id":"59638793-d1ed-4d6c-9d34-d9359ecfd100","doc_no":"A.1.10.2.4.10.1","title":"Spell Crafter Performs Pre-Deployment Steps","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":608,"content":"After the Spell Reviewers have finished their review, the Spell Crafter performs the last steps before the Spell is ready to be deployed. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md).","contentHash":"f8bae16c58061920793a55a2939e3217198f10292952f38cbed727e8def0109c","addressRefs":[]},"e31813f6-77ce-438e-a791-4d127e783bc7":{"id":"e31813f6-77ce-438e-a791-4d127e783bc7","doc_no":"A.1.10.2.4.10.2","title":"Spell Reviewers Review Pre-Deployment Steps","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":609,"content":"The Spell Reviewers review the pre-deployment steps. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-reviewer-mainnet-checklist.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-reviewer-mainnet-checklist.md). When they have completed their review, they indicate their approval in a comment to the Github pull request, such as \"good to deploy\". The Spell Crafter may only proceed with the Spell deployment when approvals have been received from the two Spell Reviewers.","contentHash":"0d439bac52fe09be6753f4e980ac77ef9f0a27d6c504a566a6cbdfae8d62399d","addressRefs":[]},"a7e04b56-d754-423d-8ad9-6f1013023a91":{"id":"a7e04b56-d754-423d-8ad9-6f1013023a91","doc_no":"A.1.10.2.4.10.3","title":"Spell Crafter Conducts Pre-Deployment Setup And Checks","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":610,"content":"The Spell Crafter performs pre-deploy setup and checks. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md).","contentHash":"3a3efbfadc0133f983ef38e74fe7ea2f2e308625ce16318b7358520c54404c7a","addressRefs":[]},"81b4e7f6-8f56-497f-889c-48e412244801":{"id":"81b4e7f6-8f56-497f-889c-48e412244801","doc_no":"A.1.10.2.4.10.4","title":"Spell Crafter Deploys The Spell On Mainnet","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":611,"content":"The Spell Crafter then deploys the Spell as specified herein. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md).","contentHash":"4bd1eb7aefffc0f22893dc3690153eceba43493660abba81a97f28782f770050","addressRefs":[]},"1463db73-6121-48e9-950a-09dbc699076f":{"id":"1463db73-6121-48e9-950a-09dbc699076f","doc_no":"A.1.10.2.4.10.5","title":"Spell Crafter Casts Spell On Newly Deployed Tenderly Testnet","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":612,"content":"The Spell Crafter then casts the deployed Spell on a newly deployed Tenderly Testnet. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md).","contentHash":"426e247fe322169024329c263252bf71577c719a1591fe62fec6889795e532e7","addressRefs":[]},"959dea0e-219f-4caa-8101-09bd690ce051":{"id":"959dea0e-219f-4caa-8101-09bd690ce051","doc_no":"A.1.10.2.4.10.6","title":"Spell Crafter Archives Spell","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":613,"content":"The Spell Crafter archives the Spell using the `make archive-Spell` command, if the current date equals the Target Date in the Executive Document. If the current date does not equal the Target Date in the Executive Document, the Spell Crafter should instead use `make archive-Spell date=\"YYYY-MM-DD\"`, where \"YYYY-MM-DD\"","contentHash":"ab80a292a4ef9712a2b1f1f45082aaba8d21400f982dec2f22af343c80e6d780","addressRefs":[]},"119f1132-4d75-4823-89d0-872aeb0aa1de":{"id":"119f1132-4d75-4823-89d0-872aeb0aa1de","doc_no":"A.1.10.2.4.10.7","title":"Spell Crafter Pushes Changes And Requests Review","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":614,"content":"The Spell Crafter then commits their changes and requests review by the Spell Reviewers. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md)/","contentHash":"cf4b00b932edd892524a857cab6c14106c0b7dd4b3e65e3536caa5c86ce8c973","addressRefs":[]},"56106653-7764-466a-a5a5-ff6843b100d7":{"id":"56106653-7764-466a-a5a5-ff6843b100d7","doc_no":"A.1.10.2.4.10.8","title":"Spell Reviewers Review Pull Request","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":615,"content":"The Spell Reviewers review the Pull Request. As part of this review, they run tests locally. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-reviewer-mainnet-checklist.md.](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md) When they have completed this, each Spell Reviewer posts a comment approving the handover of the Spell (e.g. \"good to handover\"), including a copy of the test results.","contentHash":"f0df6cc080292968a4a85d0d090299d665c9779cee16edb6506c632f9b08bbe3","addressRefs":[]},"8411d3bb-f5b8-4f0e-94b1-4ce7bb223099":{"id":"8411d3bb-f5b8-4f0e-94b1-4ce7bb223099","doc_no":"A.1.10.2.4.10.9","title":"Spell Crafter Hands Over Spell","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":616,"content":"Once the Spell Crafter has received approval to handover the Spell from both the Spell Reviewers, the Spell Crafter proceeds to hand over the Spell to the Governance Point. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md)","contentHash":"808de0121afc3cee3ea3cb9cdcef5ebd19f66b8667f64f84e9db8ed3691a0496","addressRefs":[]},"3d0a743a-1e14-4376-b5ef-2ebd0f2820d7":{"id":"3d0a743a-1e14-4376-b5ef-2ebd0f2820d7","doc_no":"A.1.10.2.4.10.10","title":"Spell Crafter Conducts Final Checks","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":617,"content":"The Spell Crafter conducts a final set of checks to guard against Pull Request attack vectors before merging the Pull Request as specified herein. These steps are set out here: [https://github.com/sky-ecosystem/pe-checklists/blob/master/Spell/Spell-crafter-mainnet-workflow.md](https://github.com/sky-ecosystem/pe-checklists/blob/master/spell/spell-crafter-mainnet-workflow.md)","contentHash":"31e6479960f0e2a5179aadd6b1578ac2c884d091157a76b83f9598704426482c","addressRefs":[]},"f394fe65-d60a-40cb-8cc9-e607fe0c0487":{"id":"f394fe65-d60a-40cb-8cc9-e607fe0c0487","doc_no":"A.1.10.2.4.10.11","title":"Spell Crafter Squashes And Merges Pull Request","type":"Core","depth":6,"parentId":"746bfb60-2d46-4064-a7f0-3d1d249463ee","order":618,"content":"Finally, the Spell Crafter squashes and merges the Pull Request.","contentHash":"74b7a5b9813bcf6a71b77d1fff4504e9f7e17ad7e5c5815073b534395621a7cf","addressRefs":[]},"4a26e84d-6b1c-4ccf-b829-5ee665d8c813":{"id":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","doc_no":"A.1.10.2.4.11","title":"Governance Point Reviews Spell And Publishes To Voting Portal On Target Date (Step 11)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":619,"content":"After the completion of the Spell development process, the Governance Point is responsible for finalizing the steps required to make the Executive Vote available for voting. These steps are outlined in the subdocuments herein.","contentHash":"b4530a5c7b79bd8d14d9bae101e8e7024016f4dd5df3b9e63ed4e1c58fb0b59b","addressRefs":[]},"0719e89e-5a2b-416f-803d-83cf4c3d09ec":{"id":"0719e89e-5a2b-416f-803d-83cf4c3d09ec","doc_no":"A.1.10.2.4.11.1","title":"Governance Point Reviews Spell And Final Preparation","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":620,"content":"After the Spell Team has handed over the Spell, the Governance Point is responsible for performing a high-level review of the Spell and completing the final preparation steps required to integrate the Spell into the governance process. These steps include reviewing the Spell, handling the Spell address, and ensuring all necessary checks are completed. Detailed instructions for each step are provided in the subdocuments.","contentHash":"5aca909dbb3aaee364de4fe24941c2bcd59e4ab3ac68f77925c5914c4f09bd6e","addressRefs":[]},"d3f61923-443e-4b36-9a84-d3a1ff25d59a":{"id":"d3f61923-443e-4b36-9a84-d3a1ff25d59a","doc_no":"A.1.10.2.4.11.1.1","title":"Governance Point Reviews Spell Content","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":621,"content":"After the Spell is deployed, the Governance Point must review the Spell to ensure that the Spell is accurate and complete.\n\nThe Governance Point must perform the following checks:\n\n- Verify that all items listed in the Executive Sheet are accurately reflected in the Spell code.\n- Confirm that all values in the Spell code match those specified in the Executive Sheet.\n- Ensure that no items are present in the Spell code that are not included in the Executive Sheet, with limited exceptions such as approvals or other predefined standard actions\n- Confirm that reviews have been submitted by the designated reviewers as part of the validation process.\n- After handover, verify that the deployed code matches the corresponding code in the GitHub repository.\n- Ensure that reviewers have approved the deployed code at the specified handover address.","contentHash":"55dc83ee9de31b7703f0e61a3458809f30cecbbe47612359e1ce8d5c06a082cf","addressRefs":[]},"93b1ccb0-ee1e-4e41-8a3b-03520de76ab4":{"id":"93b1ccb0-ee1e-4e41-8a3b-03520de76ab4","doc_no":"A.1.10.2.4.11.1.2","title":"Governance Point Requests TechOps Services To Whitelist Spell Address","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":622,"content":"The Governance Point must request that TechOps Services whitelist the Spell address provided by the Spell Team. This support request is submitted in the Discord channel #techops-request. The message should include a request to whitelist the Spell and must specify the Spell address.","contentHash":"beeadefb3c4bf423370f8e90e0ed67218cec6b058f30161e7cc45ea9ba0c35dc","addressRefs":[]},"6a1c7d77-4f03-40db-8ed5-05b1e94442cf":{"id":"6a1c7d77-4f03-40db-8ed5-05b1e94442cf","doc_no":"A.1.10.2.4.11.1.3","title":"Governance Point Adds Spell Address In Executive Document","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":623,"content":"The Governance Point must update the Executive Document with the Spell address. This is done by creating a new Pull Request in GitHub. Only the \"address\" field in the Executive Document is permitted to be modified after the Spell has been deployed.","contentHash":"e9ea637669dc5f779fd2050ae46d5d4c23342a9444f1f664ca67d58880ead3e1","addressRefs":[]},"328db91a-758d-4476-b2aa-876d667bb7a8":{"id":"328db91a-758d-4476-b2aa-876d667bb7a8","doc_no":"A.1.10.2.4.11.1.4","title":"Review Of Spell Address In Executive Document","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":624,"content":"After the Governance Point has added the Spell address to the Executive Document, it must be reviewed. This review is conducted by any member of the Core Facilitator team. The reviewer must confirm that the \"address\" field in the Executive Document has been updated with the correct Spell address.","contentHash":"396ad05afa7c0ddabcc7cce8fe758ced56c99d5f2ca50274f96574c44b0ac810","addressRefs":[]},"75b9e342-de70-43c2-967f-0023474ce822":{"id":"75b9e342-de70-43c2-967f-0023474ce822","doc_no":"A.1.10.2.4.11.1.5","title":"Governance Point Merges Pull Request","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":625,"content":"Once the Pull Request has been reviewed and approved, the Governance Point must merge it into the main branch of the executive-votes GitHub repository.","contentHash":"7238f2cdfdf21f9a572f69c8f8a75c6dc315897c3cfb1f62d5409738fb1c2242","addressRefs":[]},"12ebd0d9-52dc-4d1f-8e1a-8bdc2a51b9b0":{"id":"12ebd0d9-52dc-4d1f-8e1a-8bdc2a51b9b0","doc_no":"A.1.10.2.4.11.1.6","title":"Governance Point Validates Executive Document","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":626,"content":"The Governance Point must validate the Executive Document on the voting platform. This is done by pasting the raw URL of the document into the validation field and clicking the \"Validate\" button. The validation tool can be accessed at Executive Validator [(](https://vote.makerdao.com/executive/create)[https://vote.sky.money/executive/create](https://vote.sky.money/executive/create)).\n\nThe raw URL can be found by opening the specific Markdown file for the Executive Document. On the file’s page, locate the Raw button near the top-right corner of the file viewer. Clicking the Raw button will open a new page. The URL of this new page is the \"raw URL.\"\n\nThe validation tool provides a preview of how the Executive Vote will appear on the voting platform, allowing the Governance Point to confirm the document's formatting and content.","contentHash":"fe830771d8b9b77b76ae2eda9115c788d9b98958b823227ad3f2a8b77c2c85e8","addressRefs":[]},"16b127f0-b8b6-463d-8f3c-0fc00623ddac":{"id":"16b127f0-b8b6-463d-8f3c-0fc00623ddac","doc_no":"A.1.10.2.4.11.1.7","title":"Checklist For Governance Point Review Of Spell And Final Preparation","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":627,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md#submission](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md#submission) serves as a final verification tool for the Governance Point when reviewing and finalizing the Spell.","contentHash":"9ea004944c68cb9b6fd225d62948d4af388d0bed69bfa8203a2632b92da54112","addressRefs":[]},"5e78a59d-fad1-4991-9689-c9220cef7db2":{"id":"5e78a59d-fad1-4991-9689-c9220cef7db2","doc_no":"A.1.10.2.4.11.2","title":"Governance Point Publishes Executive Vote","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":628,"content":"The Governance Point is responsible for publishing the Executive Vote on the Voting Portal, enabling the community to participate in the voting process. This process includes updating the active proposals file, merging changes, refreshing the Voting Portal cache, and notifying the community. The subdocuments herein outline the detailed steps.","contentHash":"d92b82a5d18ec2d5e5825f16adfe6a6e6cfe57778bc286c1ce0798471e125a81","addressRefs":[]},"3593993e-bc81-44f6-9e3a-c113a7940092":{"id":"3593993e-bc81-44f6-9e3a-c113a7940092","doc_no":"A.1.10.2.4.11.2.1","title":"Governance Point Updates Active Executives File","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":629,"content":"The Governance Point must update the proposals.json file ([https://github.com/sky-ecosystem/executive-votes/blob/main/active/proposals.json](https://github.com/sky-ecosystem/executive-votes/blob/main/active/proposals.json)) in the GitHub repository to ensure the Voting Portal reflects the correct active proposal. This involves adding a link to the raw Markdown file for the Executive Document.","contentHash":"edfafa8cbef62b5846bf8685911f0a26cd0ff37e565a5f8dbf25477e4ee771d0","addressRefs":[]},"047b842a-c5af-414d-8b8e-4151cea24eb4":{"id":"047b842a-c5af-414d-8b8e-4151cea24eb4","doc_no":"A.1.10.2.4.11.2.2","title":"Core Facilitator Reviews Active Executive File Update","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":630,"content":"Once the Governance Point has updated the active proposal file, the changes must be reviewed by another member of the Core Facilitator team.","contentHash":"bd365aae4abf867e8314f36d37f09188aa89966ef2455db4ab906108a7745c1f","addressRefs":[]},"77583ed9-933e-477b-85be-1458e83586d3":{"id":"77583ed9-933e-477b-85be-1458e83586d3","doc_no":"A.1.10.2.4.11.2.3","title":"Governance Point Merges The Updated Active Executive File","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":631,"content":"Once the Pull Request for the updated proposals.json file has been reviewed and approved, the Governance Point must merge it into the master branch of the executive-votes GitHub repository. This step ensures that the active executive file is updated and accurately reflected in the Voting Portal. The approvals of the Pull Request can be made by any member of the Core Facilitator team.","contentHash":"a15ba518c7c6fab85c44442ae2aed822df383c773829370107b8dd98028ba66d","addressRefs":[]},"6aceef83-49b4-4318-b693-ba318ab0eebd":{"id":"6aceef83-49b4-4318-b693-ba318ab0eebd","doc_no":"A.1.10.2.4.11.2.4","title":"Governance Point Updates Voting Portal Cache","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":632,"content":"The Governance Point must refresh the cache of the Voting Portal ([https://vote.sky.money/dashboard](https://vote.sky.money/dashboard)). This ensures that the executive corresponding to the new Spell is displayed promptly, marking the start of the Ecosystem Spell Validation window.\n\nIf required, Jetstream can provide the Governance Point with the necessary password to execute this action.","contentHash":"e0c149680a28ab3a74a53c2518554c2a626e55da85f40a8d0501504aa2879558","addressRefs":[]},"e7f1fd21-5e39-4bdf-a166-994563e45fb7":{"id":"e7f1fd21-5e39-4bdf-a166-994563e45fb7","doc_no":"A.1.10.2.4.11.2.5","title":"Governance Point Notifies Community Of New Executive Vote","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":633,"content":"The Governance Point must post a message in the official Sky Builder Discord server channel #governance to notify the community about the new Executive Vote. This post tags the community and includes the full summary of the proposal, along with a link to the proposal on the voting platform. The notification is published after the Executive Vote goes live.","contentHash":"f50fe15bc0fbdd385c018876dbb6074b5f211ffa88212895e568ded4d525622f","addressRefs":[]},"447d5a6d-7051-4092-ac3f-06a23bd282ae":{"id":"447d5a6d-7051-4092-ac3f-06a23bd282ae","doc_no":"A.1.10.2.4.11.2.6","title":"Checklist For Governance Point Publishing Executive Vote","type":"Core","depth":6,"parentId":"4a26e84d-6b1c-4ccf-b829-5ee665d8c813","order":634,"content":"The checklist found at [https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md#submission](https://github.com/sky-ecosystem/executive-votes/blob/main/processes/executive-doc-creation-checklist.md#submission) serves as a final verification tool for the Governance Point to ensure all steps in the process of publishing the Executive Vote are completed.","contentHash":"548bd2206749555b9ff93774ec6ec0f89fbebfb65681d0c8bff4c6f8fe896f9a","addressRefs":[]},"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271":{"id":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","doc_no":"A.1.10.2.4.12","title":"Ecosystem Validators Validates Spell During Validation Window (Step 12)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":635,"content":"After the Spell is live on the voting platform, the Spell must be validated by the Ecosystem Validators. The validation process is outlined in the subdocuments herein.","contentHash":"987f672a9483019b97aad0e12111154221bc7f6e2664def49a1012a1c8f7c1d3","addressRefs":[]},"6be80bce-df84-4e8a-ab38-c4f2c5e7d373":{"id":"6be80bce-df84-4e8a-ab38-c4f2c5e7d373","doc_no":"A.1.10.2.4.12.1","title":"Ecosystem Spell Validation Overview","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":636,"content":"Ecosystem Spell Validation refers to the process of reviewing and verifying the accuracy, functionality, and compliance of a Spell's code on the blockchain. The subdocuments herein outline the key concepts, roles, and timelines involved in the validation of Spells.","contentHash":"71c9ba5922b5d71da086df066c0a892b97aeddc9ce4fa983b2b784c019ef704f","addressRefs":[]},"1ddd532f-ac63-48d8-b873-c2d106252328":{"id":"1ddd532f-ac63-48d8-b873-c2d106252328","doc_no":"A.1.10.2.4.12.1.1","title":"Ecosystem Spell Validators","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":637,"content":"Ecosystem Spell Validators are members of the Sky Ecosystem responsible for performing the Spell validation process. Currently, Aligned Delegates serve as the primary Spell validators for the Sky Ecosystem.","contentHash":"e3af4ffd3a670a3b92b30778babaccf6082635ce0730b1f56c8e96da4ace9226","addressRefs":[]},"64c1fbdd-8d78-439d-810f-985734946744":{"id":"64c1fbdd-8d78-439d-810f-985734946744","doc_no":"A.1.10.2.4.12.1.2","title":"Ecosystem Spell Validation Window","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":638,"content":"The Ecosystem Spell Validation Window is the period of time during which a Spell can be validated. Validation must occur:\n\n1. After the Spell becomes visible and is available for voting on the Voting Portal (start of the validation window).\n2. Before the Spell’s actions become executable, which occurs when the `GSM Pause Delay` elapses (end of the validation window).\n\nValidation outside this window is ineffective because:\n\n- The Spell may still be subject to changes before the start of the validation window.\n- The Spell may already be executable after the end of the validation window.\n\nThe duration of the validation window is determined by the value of the GSM Pause Delay.","contentHash":"6e338ccc54d8346d2a594b76c9856467604f09e76159ce9198df98cbad7a0d94","addressRefs":[]},"101d5bee-6ba8-449e-9bb0-cc31bc929390":{"id":"101d5bee-6ba8-449e-9bb0-cc31bc929390","doc_no":"A.1.10.2.4.12.1.3","title":"Ecosystem Spell Verification Scope","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":639,"content":"The scope of Spell validation includes any code in the Sky Protocol that:\n\n1. Must adhere to the `GSM Pause Delay` enforced by the Sky Protocol’s `ds-pause` contract, and\n2. Is directly executed by the Sky Protocol’s `Pause Proxy` contract.\n\nActions that do not meet these criteria—such as `instant actions`, `MOM` and `IAM` contract calls—are excluded from Spell validation.\n\nThis exclusion is due to the absence of a pause delay for such actions, which prevents ecosystem actors from having sufficient time to perform their reviews.\n\nValidators should also consider validating the source code or associated audits for contracts added to the Chainlog as part of a Spell, even if these contracts are not immediately executed or fall outside the standard validation scope. This includes pre-deployed emergency Spell contracts, ensuring that their integrity and security are assessed at the time of addition to the Chainlog for potential future use.","contentHash":"16206280428479249120acacbab740fb7c35e02bc1e2fd0f8e962ce5828d3815","addressRefs":[]},"1f2d6e6a-2fc2-48ae-80ef-817a592bf446":{"id":"1f2d6e6a-2fc2-48ae-80ef-817a592bf446","doc_no":"A.1.10.2.4.12.2","title":"Tools And Resources For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":640,"content":"The Spell validation process requires the use of specific tools and resources to perform the necessary checks and ensure the accuracy and security of the Spell. These include online platforms, development environments, and blockchain-related utilities, as detailed in the subdocuments herein.\n\nMany of these tools are also used during the Spell development process. Therefore, it is recommended that Spell validators rely on the same setup to ensure consistency and reliability during validation","contentHash":"037a752c6f2c3b9458843850fd85bdbe8af1f7fff29f2d40ae5f76234457428a","addressRefs":[]},"e32e109f-e101-4d96-85bb-b6341773353f":{"id":"e32e109f-e101-4d96-85bb-b6341773353f","doc_no":"A.1.10.2.4.12.2.1","title":"Supported Operating System For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":641,"content":"Spell validation must be performed on macOS or a Linux-based operating system. Windows Subsystem for Linux (WSL) may be used by Windows users, but it is not officially supported.","contentHash":"5e1a8776933a62c854e676df0ad6175866abe1f2c392d8bd6b24e36a1b9aebc0","addressRefs":[]},"8c7fe7a6-2bda-443b-8470-872ca1e341c6":{"id":"8c7fe7a6-2bda-443b-8470-872ca1e341c6","doc_no":"A.1.10.2.4.12.2.2","title":"System And Language Requirement For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":642,"content":"Spell validators are required to understand English, and the validation must be performed in English.","contentHash":"53704905ca6513aac4310179289bf0bcf50c836ce9e8b51b3f8f35c64d42b39b","addressRefs":[]},"ee18215c-7a45-4fda-8ede-6c3c60e27125":{"id":"ee18215c-7a45-4fda-8ede-6c3c60e27125","doc_no":"A.1.10.2.4.12.2.3","title":"Required Programming And Command Languages For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":643,"content":"Spell validators must use the Solidity programming language to review smart contracts and the Bash command language to execute validation scripts.","contentHash":"9636ffc75e1490dc6543e733e353de2a29d24d5398c5696a7eaf050fbd9886b3","addressRefs":[]},"4800adb1-b0e3-4791-b80a-b27ef03e27cb":{"id":"4800adb1-b0e3-4791-b80a-b27ef03e27cb","doc_no":"A.1.10.2.4.12.2.4","title":"Recommended Browser For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":644,"content":"Firefox is recommended for Spell validation due to its wide support, strong privacy features, and speed.","contentHash":"72f3a6ec52088e1550d13c3360448421cef3665576032e51c0271f22add1a00b","addressRefs":[]},"cc6f9990-ffcf-49a8-ba0a-76453155063c":{"id":"cc6f9990-ffcf-49a8-ba0a-76453155063c","doc_no":"A.1.10.2.4.12.2.5","title":"Version Control Tools For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":645,"content":"Spell validators are strongly recommended to use Git during Spell validation, although it is not required.","contentHash":"5794881a9ec2b8851c2e13b2a830e2f0aa0bc0e6c93e47c4ad76ea61e1340dcf","addressRefs":[]},"78db1070-9ab9-4e71-964d-3c73d5d9b015":{"id":"78db1070-9ab9-4e71-964d-3c73d5d9b015","doc_no":"A.1.10.2.4.12.2.6","title":"Development Toolchain For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":646,"content":"The Foundry toolchain is required for ecosystem validation of Spells. Spell validators should refer to the \"Getting started\" section in Foundry’s FoundryBook documentation for installation instructions.\n\nThe toolchain’s dependencies vary by operating system and may include:\n\n- The Rust programming language and the Cargo package manager.\n- For macOS users, the Homebrew package manager and the libusb package.","contentHash":"d395d3624d9ec7bc85992b62ca536d54a0a4b97a8c29d720e674ddccb39b6874","addressRefs":[]},"f26a1e7c-e189-4fa7-bd0c-05b36bb054fb":{"id":"f26a1e7c-e189-4fa7-bd0c-05b36bb054fb","doc_no":"A.1.10.2.4.12.2.7","title":"Mainnet Ethereum Node For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":647,"content":"The validation of Spells requires access to a local or remote Mainnet Ethereum node. While the use of a local node is preferred for enhanced control and security, a remote node is recommended for most Spell validators to simplify setup and maintenance. Services like Tenderly provide a fast and reliable remote node for Ethereum Mainnet access and are often favored for their performance.","contentHash":"aa72a81970c837a9b1bcfeb696ccd86dd5422b9d619330bd2ef2c166ccb5a9a3","addressRefs":[]},"42979dc0-bf99-4ba4-97a5-ccfe02845ad7":{"id":"42979dc0-bf99-4ba4-97a5-ccfe02845ad7","doc_no":"A.1.10.2.4.12.2.8","title":"Using Chainlog Smart Contract For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":648,"content":"Retrieving values from the Chainlog smart contract is mandatory during the validation of Spells.\n\nThe most secure method for retrieving values is to query the Chainlog directly using multiple sources, such as Foundry’s `cast` tool, the Etherscan blockchain explorer, and the IPFS link accessible on the official Chainlog for Sky at [https://chainlog.sky.money/](https://chainlog.sky.money/), ensuring that the returned addresses match across all platforms.","contentHash":"c2f88df4eb095352cf74ee9c6ee0bbb6942e852f1e9ef2d04c4b1823ab8f125a","addressRefs":[]},"0c457a50-037e-4d5f-bbff-a531c0ecf52e":{"id":"0c457a50-037e-4d5f-bbff-a531c0ecf52e","doc_no":"A.1.10.2.4.12.2.9","title":"Using GitHub Website For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":649,"content":"GitHub is the platform that hosts Spell repositories, Spell code, pull requests, and public communication between Spell Team members. The use of the GitHub website is required during Spell validation to obtain the current Spell code.\n\nWhile using GitHub’s web interface through a browser is not explicitly required, it is strongly recommended.","contentHash":"fd4a8b887eb7286b41d8f3b8f8602aa47ee8ec6be7dc3b92a9a7cf5f40a6ff25","addressRefs":[]},"230c15db-6c5a-4486-b44b-ef915db39d11":{"id":"230c15db-6c5a-4486-b44b-ef915db39d11","doc_no":"A.1.10.2.4.12.2.10","title":"Using Etherscan Website For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":650,"content":"The use of the Etherscan website is required when validating Spells, as it is the only blockchain explorer that displays the verified code of the current Spell’s smart contract, including its Solidity compiler version, licensing settings, optimization settings, and libraries used.\n\nAside from the current Spell’s smart contract, using Etherscan to make calls to, interact with, or read information from other smart contracts is not required during the validation process. Many smart contracts associated with the Sky Protocol have only been verified on Etherscan.\n\nAutomated Spell deployment and code comparison scripts within the Spell repositories may require an Etherscan API key; however, these scripts must not be used when validating Spells.","contentHash":"e9c5ade7fa2b120a8fa2c1f4ce6202f5acdbc14dc1e5df7a36e67208104db6c6","addressRefs":[]},"3326e18a-a909-448b-a9b3-ee17afc87160":{"id":"3326e18a-a909-448b-a9b3-ee17afc87160","doc_no":"A.1.10.2.4.12.2.11","title":"Using Discord For Spell Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":651,"content":"The use of Discord is not required during Spell verification, as it primarily serves as a platform for public communication between the Core Facilitator and members of the current Spell Team.\n\nHowever, using Discord is highly recommended for Spell validators, as the communication history in the #new-Spells channel may provide valuable context or additional information for the validation process.","contentHash":"a9e68a6f84701d82007a2b596d7895fbf482e040bc6b05dfb0a43cabfb6534e0","addressRefs":[]},"6668e922-1831-4cb2-b948-c528a80198eb":{"id":"6668e922-1831-4cb2-b948-c528a80198eb","doc_no":"A.1.10.2.4.12.3","title":"Spell Validation Checks","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":652,"content":"When validating a Spell, specific checks must be performed to determine whether the Spell passes or fails validation. These checks are categorized into three levels of priority:\n\n- Required Checks: Must be completed for the Spell to pass validation.\n- Recommended Checks: Should be completed to ensure best practices, but are not mandatory.\n- Additional Checks: Community-developed checks that enhance the validation process.\n\nThese checks are detailed in the subdocuments.","contentHash":"13ac65a2ed4cb486ededac104e02a2e1fe24ba0396c5337442e6e87dccf10bb6","addressRefs":[]},"4aa4dc55-736c-4e5c-994c-3d99616e1d71":{"id":"4aa4dc55-736c-4e5c-994c-3d99616e1d71","doc_no":"A.1.10.2.4.12.3.1","title":"Required Spell Validation Checks","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":653,"content":"Validators must complete the checks outlined in the subdocuments to be able to determine if a Spell passes or fails validation.","contentHash":"e3d634e1b2efce0b903a0fc538dd2d1326e39e4601c4cfdaaf52092a4bb1c873","addressRefs":[]},"ea1d866c-41ed-474b-91ce-d9f6428bc158":{"id":"ea1d866c-41ed-474b-91ce-d9f6428bc158","doc_no":"A.1.10.2.4.12.3.1.1","title":"Spell Validators Must Ensure Tests Pass","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":654,"content":"Ecosystem Spell validators must execute the predefined tests associated with a Spell. These tests are provided as scripts in the Spell repository on GitHub. Validators must run these scripts to verify the correctness, security, and compatibility of the Spell. All tests must pass successfully—without errors or failures—for the Spell to pass validation.\n\nThe best practice for running the tests are specified herein:\n\n1. If you haven’t cloned the repository before, run: `git clone <https://github.com/sky-ecosystem/Spells-mainnet`>.\n2. Navigate to the Spell repository directory by running: `cd Spells-mainnet`.\n3. Update the repository for the latest changes by running: `git pull`.\n4. Switch to the correct branch by finding the name from the Spell’s pull request on GitHub, run the command: `git checkout NAME`.\n5. Verify your setup and check that you’re on the correct branch by running: `git status`.\n6. Clean up old Spell library dependencies by running the command: `rm -r lib` or deleting the `lib` folder and its contents.\n7. Install libraries required for the current Spell by running `git submodule update --init --recursive`.\n8. Configure the local or remote node being used by running `export ETH_RPC_URL=URL` with the URL of your local or remote node. If using a remote node, do not share the URL as it can be used maliciously.\n9. Run the Spell tests by running `make test`. If there are concerns about potential modifications to the function, validators can bypass the `make` command and directly execute the test script using `./scripts/test-dssSpell-forge.sh`.\n10. Wait for completion. Allow 20 to 60 minutes for the tests to complete.\n11. Review and Save Results: Save the test results (pass or fail) for logging purposes.","contentHash":"9182560b0943b42ca05d2f1c0483ed19f320a97f3dc94096de3c8bbaee67fee4","addressRefs":[]},"a8bc220b-ed35-4c3a-95c3-88fb625b14ed":{"id":"a8bc220b-ed35-4c3a-95c3-88fb625b14ed","doc_no":"A.1.10.2.4.12.3.1.2","title":"Spell Validators Must Verify Spell On Etherscan","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":655,"content":"Validators must confirm that the Spell’s smart contract is verified on Etherscan.\n\nValidation can be performed by ensuring that the source code is visible under the \"Contract\" tab and under \"Contract Source Code\" on Etherscan. If only bytecode is displayed, the contract is not verified. Additionally, the source must match the correct version in Spells-mainnet on GitHub. A Spell is considered verified if these conditions are met.","contentHash":"a609acda83744b6e704510a264798cfb01cd931ab8b12ac7373e2a49be60320a","addressRefs":[]},"2407adac-7204-4dbe-acb8-abde6e0e57e9":{"id":"2407adac-7204-4dbe-acb8-abde6e0e57e9","doc_no":"A.1.10.2.4.12.3.1.3","title":"Spell Validators Must Validate DssExecLib Library","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":656,"content":"Validators must ensure that the address of the `DssExecLib` library is correct. The correct address corresponds to the latest release as specified in the `DssExecLib` GitHub repository. The deployed Spell must use and display the correct `DssExecLib` address on Etherscan to pass validation.\n\nThe validation can be performed by navigating to the \"Libraries Used\" section on the \"Contract tab\" on Etherscan. The library address displayed there must be compared against the official address specified in the README file ([https://github.com/sky-ecosystem/dss-exec-lib?tab=readme-ov-file#dss-exec-library](https://github.com/sky-ecosystem/dss-exec-lib?tab=readme-ov-file#dss-exec-library)) of the `DssExecLib` GitHub repository.","contentHash":"61b6683803b239bc3bf78494918a8cda045ba4b314127dd8ed351489655e770f","addressRefs":[]},"438343b7-8d2a-4698-8d0f-2ab01a570ff8":{"id":"438343b7-8d2a-4698-8d0f-2ab01a570ff8","doc_no":"A.1.10.2.4.12.3.1.4","title":"Spell Validators Must Check Deployed Spell Code","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":657,"content":"The Spell validator must ensure that the deployed Spell code matches the Spell code present in the GitHub Repository.\n\nIn order to pass validation, the deployed Spell must not contain any potentially malicious code or any notable functional changes within the `DssSpellAction`.\n\nThe validation for the Spell code can be done by using the `diff-deployed-Spell` script present in the Spell repository on GitHub to ensure that the deployed Spell’s code matches locally compiled code. Alternatively, an online tool like diff checker ([https://www.diffchecker.com/](https://www.diffchecker.com/)) can be used. The Spell code on Etherscan should be compared with the `DssSpell.sol` in the GitHub repository for the relevant Spell. If the Spell goes live before the code is merged to the main branch, it’s possible to find the branch by the Target Date name of the Spell (e.g., YYYY-MM-DD).\n\nWhen comparing, note that the following differences are acceptable and should not be flagged (based on validation guides):\n\n- Comments: Lines starting with `//` or inside `/* */`.\n- Imports and Solidity versions: Multiple declarations in the GitHub code.\n- Interfaces: Numerical suffixes like `_1` or `_2` added to interface names in the contract.\n- DssExecLib Interface: Extra code or warnings within the `DssExecLib` library.","contentHash":"100c47faa33a7f808977f97c1004e51c065577792df26a011de30e7143a6760b","addressRefs":[]},"354e4b28-61fd-4416-aa8b-085e40cdf920":{"id":"354e4b28-61fd-4416-aa8b-085e40cdf920","doc_no":"A.1.10.2.4.12.3.1.5","title":"Spell Validators Must Check Deployed Spell Is Not A DarkSpell","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":658,"content":"Validators must confirm that the deployed Spell does not execute an external `DssAction` contract. This validation ensures that the Spell is self-contained, does not rely on external contracts or pre-defined Ethereum addresses, and that the `DssExec` and `DssSpellAction` contracts are deployed together and not separately, as is done when using DarkSpells. Validators must perform the following two checks:\n\n1. Check that the DssAction contract’s `execute()` function only calls the `actions()` function and does not interact with any external contracts or explicitly defined Ethereum addresses.\n2. Check that the second argument used in the constructor when instantiating the `DssExec` is a newly created Spell action contract (e.g. `address(new DssSpellAction())`) and not an explicitly defined Ethereum address. This confirms that the Spell is linked to the correct action contract.\n\nIf either of these checks fails, the Spell cannot pass validation.\n\nThe validation checks can be performed by navigating to the \"Contract tab\" on Etherscan for the deployed Spell. In the source code, first locate the `DssAction` contract (or its equivalent, such as `DssSpellAction`). Review the `execute()` function and make sure that it only calls the `actions()` function. Then, locate the constructor and confirm that the `action` argument is instantiated as a new contract.","contentHash":"2236d72a82ebc198bcee2140b134da788bb6320b67037f215821d3295c57d8c3","addressRefs":[]},"0ad70737-d32f-4c50-a4ff-d3f505e171c2":{"id":"0ad70737-d32f-4c50-a4ff-d3f505e171c2","doc_no":"A.1.10.2.4.12.3.1.6","title":"Spell Validators Must Check Deployed Spell Was Not Deployed Using CREATE2","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":659,"content":"Validators must ensure that no contract, neither the Spell Executive contract (DssSpell / DssExec) nor the Spell Action contract (DssSpellAction / DssAction) - was deployed using the `CREATE2` opcode.\n\nTo perform this validation, the validator must:\n\n- Locate and copy the contract creation transaction on Etherscan. The contract creation transaction can be found under the \"internal transactions\" tab on Etherscan.\n- Use a transaction decoder, such as Tenderly or another blockchain analysis tool, to decode the transaction hash and identify the opcode used during deployment.\n- Ensure the opcode is `CREATE`. If `CREATE2` is used, the Spell fails validation.","contentHash":"b932f4dab5bf32e7a7a1c04c136b3e92457d19817e0b8b8391a22bbfed405336","addressRefs":[]},"7f3112c8-ed90-4dfc-b29a-eae1d3492a11":{"id":"7f3112c8-ed90-4dfc-b29a-eae1d3492a11","doc_no":"A.1.10.2.4.12.3.1.7","title":"Spell Validators Must Check Deployed Spell Optimization Settings","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":660,"content":"Validators must ensure that the code optimization settings used by the Spell contract are correct.\nValidators should ensure the following:\n\n- The `Optimization Enabled` field on Etherscan is set to `No with 200 runs` unless explicitly required due to contract size constraints during deployment.\n- If optimization is enabled, the value of the `Optimization Enabled` must be `Yes with 200 runs` unless the optimization settings have been specified in the Instruction Document as a specific number of runs, which must be a multiple of 100 other than 0.\n- If the optimization settings are incorrect (e.g., `No with 13767 runs` or `Yes with 0 runs`), the Spell fails validation.\n\nTo perform this validation, the validator must go to the contract tab on Etherscan and review the `Optimization Enabled` field under the contract’s metadata.","contentHash":"fc83981a505d72841ff37f65ea273553b5dd11f54f0113d5f659bd6263020ada","addressRefs":[]},"a1773da6-7656-47b7-a31a-a4bd366d0d85":{"id":"a1773da6-7656-47b7-a31a-a4bd366d0d85","doc_no":"A.1.10.2.4.12.3.1.8","title":"Spell Validators Must Check Deployed Spell EVM Version","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":661,"content":"Validators must ensure that the correct EVM version for the Spell contract is displayed on Etherscan. The EVM version is determined by the Solidity compiler version used during compilation. For the Spell to pass validation, the `Other Settings` field on Etherscan must display either \"Default\" or the correct default EVM version name for that compiler release (e.g., for Solidity 0.8.16, either \"Default\" or \"London\" is acceptable, as London is the default EVM for that compiler version).\n\nTo perform this validation, the validator must go to the \"Contract\" tab on Etherscan and review the `Other Settings` field under the contract’s metadata.","contentHash":"a39eec64f8e7a32e8efc53bbcbfdf5d8c1e6995c5b0dc5db7cfa53939cc0f5d6","addressRefs":[]},"46cbc700-20e4-4a57-9508-07a6baa26fca":{"id":"46cbc700-20e4-4a57-9508-07a6baa26fca","doc_no":"A.1.10.2.4.12.3.1.9","title":"Spell Validators Must Perform Basic Spell Code Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":662,"content":"The Spell validator must perform a brief review of the Spell code. This includes reviewing the `DssSpellAction` contract within the `DssSpell.sol` file.\n\nValidators should look for any unusual behavior, such as:\n\n- Low-level assembly operations (e.g., `assembly` blocks).\n- The use of Solidity opcodes, such as `delegatecall`, `callcode`, or `selfdestruct`.\n- Suspicious-looking payments or transfers.\n- Any other malicious or unauthorized code. This includes cross-checking the Solidity code in `actions()` against the Executive Sheet and the Executive Document. Each action must be authorized per the Atlas.\n\nSpell validators must report any code they find that appears to be malicious or which likely forms part of an attempted attack. A Spell must not pass validation if the Spell validator is convinced that malicious code is present in a Spell or that its execution can lead to an attack on the Sky Protocol.\n\nTo perform this validation, the validator must go to the \"Contract\" tab on Etherscan and review the source code.","contentHash":"e535ad520be66d5bff93e2dbe4cded57db76c6881548205b5b895a2e41d9c6f5","addressRefs":[]},"c6b18786-1c46-4960-8348-0675a8141246":{"id":"c6b18786-1c46-4960-8348-0675a8141246","doc_no":"A.1.10.2.4.12.3.2","title":"Recommended Spell Validation Checks","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":663,"content":"Validators are encouraged to perform the Spell validation checks outlined in the subdocuments to ensure adherence to best practices.","contentHash":"d0a51241aae0de4225f512231a62026fb2341c89f9cb13f300d759df5b64d52d","addressRefs":[]},"fb60b182-3ac9-4593-b9c7-8e1eaaeaa099":{"id":"fb60b182-3ac9-4593-b9c7-8e1eaaeaa099","doc_no":"A.1.10.2.4.12.3.2.1","title":"Spell Validators Must Check Deployed Spell License","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":664,"content":"The correct license for the Spell contract is GNU AGPLv3. Validators should confirm that this license is used, which can be verified in one of two ways under the \"Contract\" tab on Etherscan:\n\n1. In the `Other Settings` field under the contract’s metadata. The license should be displayed as `GNU AGPLv3`.\n2. In the Spell Code in the commented line of code in the `DssSpell` contract. The line should contain: `SPDX-License-Identifier: AGPL-3.0-or-later`.\n\nWhile the Spell should use the correct license to pass validation, this is not considered a strict requirement.","contentHash":"c2bc035b94ce362c0d91f5596e4c139c6107574134e566140662591e49fa8299","addressRefs":[]},"83f53a73-7e2f-4dc9-a371-e19238924bf3":{"id":"83f53a73-7e2f-4dc9-a371-e19238924bf3","doc_no":"A.1.10.2.4.12.3.2.2","title":"Spell Validators Must Check Compiler Version","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":665,"content":"Validators should ensure that the Solidity compiler version used in the deployed Spell matches the version specified in the `Spells-mainnet` repository on GitHub. Validators should verify this by:\n\n- Navigate to the \"Contract\" tab on Etherscan and check the `Compiler Version` field under the contract’s metadata. The version displayed must match the version specified in the `DssSpell.sol` contract (e.g., pragma solidity `0.8.16`;).\n- Only the first part of the version (e.g., `v0.8.16`) needs to match; any additional commit information can be ignored.\n\nWhile the Spell should use the correct version to pass validation, this is not considered a strict requirement.","contentHash":"d5efc6170deec9c5eaeb9e5db77f2ff0f007514bcba2bfd8e9d7431421ab7d11","addressRefs":[]},"56b1cc27-a9e3-4099-8f1f-648da7d1c56b":{"id":"56b1cc27-a9e3-4099-8f1f-648da7d1c56b","doc_no":"A.1.10.2.4.12.3.3","title":"Additional Community Developed Spell Validation Checks","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":666,"content":"The community has developed additional checks to enhance the Spell validation process. These checks are outlined in the subdocuments.","contentHash":"fc3996fcb0b9b2167410aaf724bcb0b93ffbbef109e7623fe00d67ba1e78df71","addressRefs":[]},"2662dc31-d68b-4b63-91d9-8ca420632eb2":{"id":"2662dc31-d68b-4b63-91d9-8ca420632eb2","doc_no":"A.1.10.2.4.12.3.3.1","title":"Spell Validators Should Validate Executive Document","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":667,"content":"The Spell validator should confirm that the smart contract developers referenced the correct governance copy when building the Spell and that the document voters see on the Voting Portal matches the Spell contents. This is done by verifying that the hash in the Spell corresponds to the version of the Executive Document stored in the GitHub repository.\n\nTo perform this validation, the validator must first locate the Executive Hash, which can be found on the voting platform under \"Spell Details\" for the Executive Vote. Validators should be aware that the hash refers to an earlier commit of the Executive Document markdown, prior to the inclusion of the contract address. After validating the hash against this earlier commit, validators must conduct a diff check between the commit associated with the Executive Hash and the final version of the document to confirm that the only difference is the replacement of the Spell address placeholder.\n\nThe check can be performed in two ways:\n\n1. Using an Online Tool:\n    - Copy and paste the body of the Executive Document from GitHub into the online Keccak-256 hash generator tool ([https://emn178.github.io/online-tools/keccak_256.html](https://emn178.github.io/online-tools/keccak_256.html)).\n    - Compare the generated hash with the hash included in the Spell.\n2. Using `cast`\n    - Generate the hash directly from the raw GitHub URL at the specific commit:\n        - Run the following command to generate the hash: `cast keccak -- \"$(wget $RAW_EXEC_URL -O -)\"`\n        - Use the raw file URL at the specific commit.\n    - Compare the generated hash with the hash included in the Spell.","contentHash":"125acd17d7ff5656cad3366a649ae616e7afaafcfeca7f5e458d62a9bac4b399","addressRefs":[]},"b28afb60-f8cc-4529-9775-1a3a0e22efed":{"id":"b28afb60-f8cc-4529-9775-1a3a0e22efed","doc_no":"A.1.10.2.4.12.3.3.2","title":"Spell Validators Should Review Spell Constructor","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":668,"content":"Validators should ensure that the Spell constructor is properly implemented. The constructor is a critical part of the Spell contract, as it defines key parameters such as the Spell's expiry time and the inclusion of the `DssSpellAction` code block, which specifies the actions the Spell will execute.\n\nValidators should follow these steps to review the constructor:\n\n- Navigate to the \"Contract\" tab on Etherscan and scroll to the bottom of the contract source code to locate the constructor declaration.\n    - Verify that the Spell inherits from the `DssExec` contract, which serves as the base contract for all Sky Spells.\n    - Verify that the constructor is properly implemented with the correct parameters. For example, the expiry time should be set to the correct duration (e.g., `30 days`).","contentHash":"319b67c88af745e61d47e4c432097eaed737a465a1108a3bca3b16e2fd1fbebc","addressRefs":[]},"97f4831e-1566-46e1-bbac-2a668e4b5ca7":{"id":"97f4831e-1566-46e1-bbac-2a668e4b5ca7","doc_no":"A.1.10.2.4.12.3.3.3","title":"Spell Validators Should Review Spell Actions","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":669,"content":"Validators should ensure that all values before and after the Spell actions are constants or immutable. If values are not constants, they could present malicious code in the form of memory mutations impacting the function of the pause proxy.\n\nTo perform this validation, the validator must go to the \"Contract\" tab on Etherscan and review the source code.","contentHash":"d5f164a21c32abe9d1383803519cfbbf62f097bd281fb11cfc93a18eff98ca5e","addressRefs":[]},"39f67b68-ad24-40b3-9cda-6aaa6006722f":{"id":"39f67b68-ad24-40b3-9cda-6aaa6006722f","doc_no":"A.1.10.2.4.12.3.3.4","title":"Spell Validators Should Review Office Hours Function","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":670,"content":"Validators should verify that the office hours function matches the Executive Document. If this function is missing from the Spell Action, the code will default to the true state (office hours on).\n\nTo perform this validation, the validator must go to the \"Contract\" tab on Etherscan and review the source code.","contentHash":"299b72dc7e6d45200694e480b143a889feb3885804faae0dddff8a77d859a2bb","addressRefs":[]},"4f7f2b2f-3514-4ba6-a1a2-6dd40fff5a92":{"id":"4f7f2b2f-3514-4ba6-a1a2-6dd40fff5a92","doc_no":"A.1.10.2.4.12.3.3.5","title":"Spell Validators Should Review Chainlog","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":671,"content":"Spell validators should ensure that all `DssExecLib` calls to the chainlog use the correct name descriptors.\n\n- Verify that all Chainlog references, such as name descriptors or keys, correspond to valid, existing entries in the Chainlog.\n- Confirm that the name descriptors match the expected values as recorded in the Chainlog.\n- The chainlog patch version is updated correctly (e.g., `x.y.z` → `x.y.z+1`).\n\nTo perform this validation the validators must go to the \"Contract\" tab on Etherscan and review the source code. Look for `DssExecLib` calls in the code. Compare the name descriptors in the code with the expected values in the Chainlog.","contentHash":"2ecf17bf4c298af05164f00034609ac5041efec2b613350d20a5056a5003a78f","addressRefs":[]},"9a7a0d5e-ac6a-481d-ae61-d6504969524e":{"id":"9a7a0d5e-ac6a-481d-ae61-d6504969524e","doc_no":"A.1.10.2.4.12.3.3.6","title":"Spell Validators Should Review Oracle Address","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":672,"content":"Spell validators should ensure that oracle addresses are correctly verified.\n\nTo perform this validation the validators should go to the Chainlog and locate the relevant oracle (e.g. `PIP_ETH`). Take the contract address listed in the Chainlog to Etherscan. Open the \"Read\" tab of the contract on Etherscan. Look for the `src` value. Verify that the `src` value matches the `MedianETHUSDcontract` address referenced in the Spell.","contentHash":"ead313d4d51a0037e63e97e9bd873f226b522672dc1bd2529634cc9ed6a17556","addressRefs":[]},"a6940e22-f25c-4f29-9307-328b7f590ce7":{"id":"a6940e22-f25c-4f29-9307-328b7f590ce7","doc_no":"A.1.10.2.4.12.3.3.7","title":"Spell Validators Should Review Constants","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":673,"content":"Validators should ensure that the rates are defined as per-second accumulation values, using the correct precision units common in the Sky Protocol (e.g., RAY for rates, RAD for debt/DAI amounts, WAD for general token amounts).\n\n**Precision Units Overview**:\n\n- **WAD (10^18)**: Used for token amounts and balances.\n- **RAD (10^45)**: Used for debt values, ceilings, or large accumulations.\n- **RAY (10^27)**: Used for rates and multipliers.\n\nThese units prevent floating-point issues in Solidity — always confirm they're applied correctly to avoid overflows or miscalculations. Group this with general constant validations (e.g., ensuring hardcoded values like fees or ceilings are computed accurately).\n\nRate values can be validated against the commented rate by using the `bc` command in a bash shell. Using the `NEW_FEE` variable in the example contract the following is visible: `bc -l <<< 'scale=27; e( l(1.095)/(60 * 60 * 24 * 365) )`. This produces 1.000000002877801985002875644. Removing the decimal place will allow you to see that this matches the definition of `NEW_FEE`.\n\nValidating all rate adjustments can be done the same way. For more information on the rates module, refer to the developer guide ([https://github.com/sky-ecosystem/developerguides/blob/master/mcd/intro-rate-mechanism/intro-rate-mechanism.md](https://github.com/sky-ecosystem/developerguides/blob/master/mcd/intro-rate-mechanism/intro-rate-mechanism.md)). For easy reference, common pre-computed rates can also be viewed at the following ipfs link ([https://ipfs.io/ipfs/QmefQMseb3AiTapiAKKexdKHig8wroKuZbmLtPLv4u2YwW](https://ipfs.io/ipfs/QmefQMseb3AiTapiAKKexdKHig8wroKuZbmLtPLv4u2YwW)).\n\nImmediately prior to making rate changes, `drip` must be called on the respective contracts.","contentHash":"dfbc6069c56ce21809d1fedc75e68929e82b68a47ef1ae9be21b7214804231c3","addressRefs":[]},"353d7fab-461c-4141-b0b5-24a91357ee4d":{"id":"353d7fab-461c-4141-b0b5-24a91357ee4d","doc_no":"A.1.10.2.4.12.3.3.8","title":"Spell Validators Should Review Timestamps","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":674,"content":"Validators should ensure that all timestamps in the Spell (e.g., ETAs, expirations, or delays like GSM Pause) are calculated correctly and use Unix timestamp format (seconds since epoch) to prevent execution issues, such as invalid timings or reverts. Use the `make time` command in Spells-mainnet to validate these.","contentHash":"0d316900ed995a490cca35eb08591ea045a73bfc080b0ff2ec4d0b21c5a4bfb1","addressRefs":[]},"2f10b68b-e398-45de-bb9a-62f832e22e7a":{"id":"2f10b68b-e398-45de-bb9a-62f832e22e7a","doc_no":"A.1.10.2.4.12.3.3.9","title":"Spell Validators Should Review Require Statements","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":675,"content":"Validators should confirm that all `require` statements in the Spell's code are used only as sanity checks and not under normal conditions or inputs (e.g., the Spell should not revert during expected execution)","contentHash":"56a9e627c667e44f5f96c477c226cd854d25fbdeafa964e14987c95b4d6fd338","addressRefs":[]},"de343461-5583-4157-b71a-a15e3e3b1ad1":{"id":"de343461-5583-4157-b71a-a15e3e3b1ad1","doc_no":"A.1.10.2.4.12.3.3.10","title":"Spell Validators Should Review Contract For Unusual Elements","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":676,"content":"Validators should assess whether any unusual or unexpected elements appear in the contract. It could be:\n\n- Hidden state changes: Look for retrieval functions (e.g., `get` or `view`) that include assignments (`=`), indicating state changes.\n- External Calls At The End: Check for external calls (e.g., `.call`, `.send`, `.transfer`) made after state changes, as this could indicate potential reentrancy attacks.\n- Force Ether, DAI or SKY Reception: Look for a `receive` function with no logic, which could forcibly receive assets.\n- Use of `tx.origin`: The tx.origin variable refers to the address that started the current transaction. If `tx.origin` is used instead of `msg.sender` in decision-making processes, it could lead to unintended authorization.\n- Function Naming Overlaps: A contract might have function names that are similar or overlap with common Solidity functions to mislead a reviewer. Check for misleading function names (e.g., `transfer`, `approve`, `mint`) with unexpected logic or assignments.\n\nTo perform this validation the validator must go to the \"Contract\" tab on Etherscan and review the source code.","contentHash":"9868f8bc13e3c8674b6a37e193e4a1231201daf82ff95f4fad881dccb13eea96","addressRefs":[]},"a564f010-a30f-40bb-bf36-12f91f30b8fe":{"id":"a564f010-a30f-40bb-bf36-12f91f30b8fe","doc_no":"A.1.10.2.4.12.3.3.11","title":"Spell Validators Should Do Spell Tests And Repository Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":677,"content":"Validators should check the following:\n\n- Ensure that all dependencies in the Spell repository (e.g., imported libraries like dss-exec-lib or git submodules) are current and up to date with the Spell. To perform this check the validator must browse or clone the GitHub repository (e.g., Spells-mainnet). Review Solidity files (e.g., in src/) for import statements, check the .gitmodules file for submodules, and run `git submodule status` to verify versions. Compare against source repositories for updates, then test with `make test` to confirm compatibility. The source repository can be identified in the Spell's source code, as the imported library or dependency is followed by \"from\", which points to the source path (e.g., `import {GemAbstract} from \"dss-interfaces/ERC/GemAbstract.sol\";` points to dss-interfaces.)\n- Verify that the test scripts themselves have not been tampered with or maliciously modified in the repository.\n- Confirm that the Spell repository branch matches the branch specified in the pull request or governance proposal.","contentHash":"314eb25bce5b1580bd1e1740638fcf851c62c99619bebed4311f3e0b9d98c5d3","addressRefs":[]},"fdcea934-c3fb-4735-acc3-3e320ad89b00":{"id":"fdcea934-c3fb-4735-acc3-3e320ad89b00","doc_no":"A.1.10.2.4.12.3.3.12","title":"Spell Validators Should Verify The Contract ABI","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":678,"content":"Validators should verify that the contract ABI (Application Binary Interface) is correctly generated and matches the deployed contract.\n\nTo perform this check, the validator must go to the \"Contract\" tab on Etherscan and the \"Contract ABI\" section. Copy the ABI JSON and compare it against the expected ABI from the official GitHub repository (e.g., Spells-mainnet repo). To obtain the expected ABI from the GitHub repository download the relevant Solidity file, paste it into a tool like Remix IDE, select the matching compiler version, and compile to extract the ABI JSON. Use a diff tool to check for exact matches in functions, parameters, and types.","contentHash":"fd0a2075d43b350231672854ab62db61ea7ba7a75a407f87cc98867b11ebe1c1","addressRefs":[]},"4674dbfa-77d8-4d99-980e-330342b0ffa9":{"id":"4674dbfa-77d8-4d99-980e-330342b0ffa9","doc_no":"A.1.10.2.4.12.3.3.13","title":"Spell Validators Should Check For Hidden Or Unverified Contracts","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":679,"content":"Validators should check for hidden or unverified contracts linked to the Spell (e.g., libraries or proxies).\n\nTo perform these checks, the validator must go to the \"Contract\" tab on Etherscan and review the source code. Scan the code for any referenced contracts or addresses: Look for imports, inherited contracts, hardcoded addresses, or function calls to external contracts. If it's an address, search it directly on Etherscan and confirm it's verified (e.g., green checkmark with available source code). Compare the referenced code to the official GitHub repository (e.g., Spells-mainnet repo) to ensure versions match and nothing has been altered.","contentHash":"ef6ffd0991996cb952d4a155528f007d1a36dcf55ad48de5ed05968384c4df1e","addressRefs":[]},"43d2fe19-727f-4722-b913-7d5f79e1a2a7":{"id":"43d2fe19-727f-4722-b913-7d5f79e1a2a7","doc_no":"A.1.10.2.4.12.4","title":"Validation Outcome Reporting","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":680,"content":"The Spell validator is responsible for reporting the outcome of the validation process. This includes determining whether the Spell passes or fails validation, documenting any issues discovered during the validation process, and ensuring that all issues are resolved before the Spell can be classified as passing validation. The process for reporting, including how to report and to whom issues should be reported, is detailed in the subdocuments herein.","contentHash":"f2bd0200ae9f2d59a58bd895f07a8d227d11ca7dd28b55b70f19aee671722231","addressRefs":[]},"6f0fce93-7274-4cb1-921e-d120989294b4":{"id":"6f0fce93-7274-4cb1-921e-d120989294b4","doc_no":"A.1.10.2.4.12.4.1","title":"Spell Passing Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":681,"content":"A Spell is classified as passing validation when:\n\n1. All validation checks are completed without identifying issues, or\n2. All reported issues have been resolved to the satisfaction of the Spell validator\n\nValidation of the Spell should ideally be public, though this is not mandatory.","contentHash":"3acb431bb5225e5df1192d6f1a921f4fdc4139c2ef98402f5777bd6b33d413b9","addressRefs":[]},"66a80a93-fcfa-48d5-819e-99489288fa83":{"id":"66a80a93-fcfa-48d5-819e-99489288fa83","doc_no":"A.1.10.2.4.12.4.2","title":"Spell Failing Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":682,"content":"A Spell is classified as failing validation when:\n\n1. One or more issues are identified during validation, or\n2. Reported issues remain unresolved to the satisfaction of the Spell validator.","contentHash":"124ee7cbdff2fced28782b116065ac25704209a7642c4a0313a0fd0802a5e99e","addressRefs":[]},"6ea115ff-4554-4c3c-b3d5-a0407972de6a":{"id":"6ea115ff-4554-4c3c-b3d5-a0407972de6a","doc_no":"A.1.10.2.4.12.4.3","title":"Reporting Issues Found During Validation","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":683,"content":"Issues discovered during validation must be reported as follows:\n\n1. Mandatory Reporting: If the validation check is required, the issue must be reported immediately.\n2. Recommended Reporting: If the validation check is recommended, validators are strongly encouraged to report issues unless they are certain the issue is not malicious, a bug, or an attack on the Sky Protocol.\n3. Out-of-Scope Issues: Any issues found outside the scope of validation checks should also be reported as soon as it is found.\n\nIn general, any issue that appears functional or potentially functional should be reported.","contentHash":"5d070801c4efdf633895857b77d9ea786eba73fb56355d6ae8c42810464eb37b","addressRefs":[]},"eca405af-edd5-42a9-8bec-4a9e49bcd090":{"id":"eca405af-edd5-42a9-8bec-4a9e49bcd090","doc_no":"A.1.10.2.4.12.4.4","title":"Resolving Issues","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":684,"content":"When an issue has been reported by a Spell validator, the Core Facilitator or the Spell Team who worked on the Spell is likely to respond to the issue. The Spell validator must assume that the parties providing the answer are acting maliciously and lying to prevent the discovery of their attack.\n\nThe validator may only consider the issue as resolved once they are comfortable that the issue does not constitute a bug or attack that poses a threat to the Sky Protocol. Only the validator who raised the issue is permitted to consider an issue as resolved, and any unresolved issue will prevent the Spell from passing validation.","contentHash":"0bab51045ba5be3e08e5689c0300eaf1376c54bcfc74131f14186222c453bd6c","addressRefs":[]},"8bd3523a-751f-4371-a20e-b267680410ad":{"id":"8bd3523a-751f-4371-a20e-b267680410ad","doc_no":"A.1.10.2.4.12.4.5","title":"Primary Reporting Counterparty","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":685,"content":"Issues found during the Spell validation should be reported to all Core Facilitators, not a single Facilitator, to mitigate the risk of compromised or malicious actors.","contentHash":"554fa85a93bf5dfc3c7bab950c5c475aaa438fce2d63ca610cb89e05d91fa7b3","addressRefs":[]},"813e403a-2ffb-463c-b9ac-1cc6653ba755":{"id":"813e403a-2ffb-463c-b9ac-1cc6653ba755","doc_no":"A.1.10.2.4.12.4.6","title":"Secondary Reporting Counterparty","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":686,"content":"If a validator suspects that Core Facilitators are malicious or colluding, they must notify Sky Governance by reporting the issues they found publicly. This permits Sky Governance community to independently investigate the issue and act together to mitigate an attack, even if all Core Facilitators are compromised or acting maliciously.","contentHash":"ea08190e3d78b56e6589adcd140704728008081fa773b509821375e2d6ffb0b9","addressRefs":[]},"55d6723f-c93d-4a81-ad4e-e55cfd8b096c":{"id":"55d6723f-c93d-4a81-ad4e-e55cfd8b096c","doc_no":"A.1.10.2.4.12.4.7","title":"Private Validation Status Reporting","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":687,"content":"Privately reporting issues found during Ecosystem Spell Validation is only recommended where the private communication involves a group of Core Facilitators, as a single Core Facilitator may be acting maliciously and provide false information. Private reporting of issues can be performed using platforms such as Discord or Signal.","contentHash":"228d830d1f7e81d8f4ad4b915b37a5d59dda5202a56b77f67a0687c07f5f0050","addressRefs":[]},"2a14eed2-f334-410c-a669-d055ed0a9e59":{"id":"2a14eed2-f334-410c-a669-d055ed0a9e59","doc_no":"A.1.10.2.4.12.4.8","title":"Public Validation Status Reporting","type":"Core","depth":6,"parentId":"84d31eb0-fbbc-4783-a7cf-ef7dddfa8271","order":688,"content":"Publicly reporting issues found during Spell validation is the recommended method of issue reporting. Issues reported publicly may be reported to the Core Facilitator using the \"#new-Spells\" channel in the Sky Builder Discord Group. If the Core Facilitator may be acting maliciously, issues should be reported to Aligned Delegates and wider Sky Governance using the \"#governance\" channel in the Sky Builder Discord Group. In cases where this is not possible, posts made to the Sky Forum may be used; however, these should be used as a last resort as they will likely cause a slower response time.","contentHash":"d46bc3f54bec545410aced6e835dbef8a58f6c2411c3bc82372acb9dfaf3ad1b","addressRefs":[]},"761cd866-17a9-47f5-8ae6-ab1788371be1":{"id":"761cd866-17a9-47f5-8ae6-ab1788371be1","doc_no":"A.1.10.2.4.13","title":"Spell Execution Process And Retro (Step 13)","type":"Core","depth":5,"parentId":"98298ab3-8d08-4c4f-b47b-81242a3e3903","order":689,"content":"The subdocuments herein provide a detailed breakdown of the technical steps involved in the execution of Spells and follow-ups after Spell execution.","contentHash":"e0a159be60eca72d0aa7a72823684b777c9011d8c1ed53eff8eb480ce2316af7","addressRefs":[]},"d87a286e-ebfa-477b-8d03-b69c6fead235":{"id":"d87a286e-ebfa-477b-8d03-b69c6fead235","doc_no":"A.1.10.2.4.13.1","title":"Outcome Of The Executive Proposal Vote","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":690,"content":"When an Executive Proposal is ready for a vote by Sky Governance, SKY holders cast their votes. The voting process determines whether the Executive Proposal gains enough support to move forward to the execution phase. If the executive does not accumulate sufficient SKY to \"move the hat\" (i.e., reach the required threshold for approval), it does not proceed to execution immediately; however, it can still gain support and be executed later within the expiration window. For official Spells, there is a 30-day expiration period after deployment. Once this period lapses, the Spell process ends, and no further actions can be taken for the associated Spell. If the executive gains enough support to be approved, the process moves forward to the execution phase.","contentHash":"0f5e5a5cf37869fbcfd27fb0b552d8cc5ee18314f8fa99735a39b7c8052b09f6","addressRefs":[]},"ee6fc86b-99da-4782-bc7f-7c01e5bbcd81":{"id":"ee6fc86b-99da-4782-bc7f-7c01e5bbcd81","doc_no":"A.1.10.2.4.13.2","title":"Lifting the Spell","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":691,"content":"Before a Spell can be scheduled for execution, it must be \"lifted\" to become the active \"hat\" in the DSChief contract. To lift a Spell, that Spell must have more approvals than the current hat. This action is permissionless, meaning any Ethereum address can trigger the execution without requiring special permissions.","contentHash":"a09fbbb5bce7689abe6d973a821ee900c3281c5f048c48932e109b0593f886eb","addressRefs":[]},"f31bd0d0-fc5b-4c86-9b84-30c4b010c986":{"id":"f31bd0d0-fc5b-4c86-9b84-30c4b010c986","doc_no":"A.1.10.2.4.13.2.1","title":"Chief-keeper","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":692,"content":"The chief-keeper monitors and interacts with DSChief and DSSSpells. When a Spell receives more approval than the current hat, the chief-keeper calls the `lift` function to make this Spell the new hat. After confirming hat status, the chief-keeper proceeds to schedule the Spell, ensuring that only the current hat is scheduled for execution.","contentHash":"72be68367e6fe81407ed24bd4b11ce575c5f97c031c92c2510d345fdbad4048f","addressRefs":[]},"e06f6a83-7c74-4abd-b4da-771cbfdf2fb9":{"id":"e06f6a83-7c74-4abd-b4da-771cbfdf2fb9","doc_no":"A.1.10.2.4.13.3","title":"Execution Setup For Approved Vote","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":693,"content":"If the executive is approved and has been lifted to become the current hat in the DSChief, a future action to execute the Spell's actions is prepared by calling `schedule()` on the Spell contract. This action is permissionless, meaning any Ethereum address can trigger the execution without requiring special permissions. This process involves calling `plot` on `ds-pause` with four parameters related to the Spell action contract:\n\n- The address of the Spell action contract.\n- The `extcodehash` value of the Spell action contract.\n- Any `calldata` information required for the future execution of the Spell contract's actions using `execute()`.\n- The `eta`, which is the earliest time the Spell's actions can be executed. This must be scheduled at least the duration of the pause delay into the future.\n\nOnce the Spell's actions are \"plotted\" in the Pause, the Spell is considered `scheduled`, and the countdown to the `eta` time begins. In the absence of Office Hours, this countdown is typically equal to the duration of the `GSM Pause Delay`. If Office Hours are set to \"Yes\" then the countdown will be equal to the `GSM Pause Delay` plus whatever time is needed to enter the Office Hours window.","contentHash":"b8839f6301dfb538c038618454035add4420307dd84672064c6ea7c426fb61a7","addressRefs":[]},"a900623d-15e0-4fc6-a393-bae5da03c139":{"id":"a900623d-15e0-4fc6-a393-bae5da03c139","doc_no":"A.1.10.2.4.13.4","title":"Casting And Execution Of Approved Spell","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":694,"content":"Once the current time exceeds the `eta` value set during scheduling, the Spell can be `cast` (see [A.1.10.2.4.13.3 - Execution Setup For Approved Vote](e06f6a83-7c74-4abd-b4da-771cbfdf2fb9)). Casting and the subsequent execution path occur atomically within the same transaction. This entire process is permissionless, meaning any Ethereum address can trigger the execution without requiring special permissions.","contentHash":"e935bcdea9bd1530b432fc1bdc3d02f4c6b462a71991bce5d878abbc68e8d4fc","addressRefs":[]},"cdd724f1-5cc7-48df-81f7-25c6a932a184":{"id":"cdd724f1-5cc7-48df-81f7-25c6a932a184","doc_no":"A.1.10.2.4.13.4.1","title":"Casting Of Spell","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":695,"content":"When the `cast` function in the DssSpell contract is called:\n\n- The Spell is marked as `cast`, preventing it from being executed again.\n- The `cast` function initiates the execution process by calling the `exec` function in the `ds-pause` contract.","contentHash":"ad9a6c6209f655bc59d1f711bfcae7612564d995f86cde970e3a441ae3f0baa9","addressRefs":[]},"8ee36ed9-cae6-462b-a6b4-9aa5479fee18":{"id":"8ee36ed9-cae6-462b-a6b4-9aa5479fee18","doc_no":"A.1.10.2.4.13.4.2","title":"Execution Of Spell","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":696,"content":"Within the same transaction initiated by `cast()`, ds-pause proceeds as follows:\n\n1. Validation and Removal: The `exec` function in `ds-pause` validates the execution request and removes it from the list of scheduled executions.\n2. Delegate Call to Spell Action Contract: The `ds-pause` contract calls `exec` on the Pause Proxy contract, which performs a `delegatecall` to the Spell action contract address specified during scheduling.\n3. Execution of Spell Actions:\n    - For regular Spells, the Pause Proxy calls the `execute()` function on the `DssSpellAction` contract.\n    - The `execute()` function calls the `actions()` function, where the Spell’s actions are carried out.\n4. Error Handling: If the transaction reverts at any point (e.g., due to an error in `actions()`), the Pause Proxy halts execution.\n5. Final Checks: If the transaction succeeds, the `exec` function in `ds-pause` performs a final ownership check to ensure the Pause Proxy is still owned by `ds-pause`.\n6. Completion: Once the final check passes, the execution of `cast()` is finalized, marking the end of the process.","contentHash":"d5501152f5832bc5add1e0138f116ecce9baeeafe12cff8176b866e2af754bb4","addressRefs":[]},"193f43fc-f26f-4fa0-b3cf-f50c68177906":{"id":"193f43fc-f26f-4fa0-b3cf-f50c68177906","doc_no":"A.1.10.2.4.13.5","title":"Facilitator Updates Atlas To Reflect Spell Outcome","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":697,"content":"Following the successful execution of a Spell, the Atlas must be updated to accurately reflect the resulting changes. The Core Facilitator is responsible for ensuring that all relevant Sky Core Atlas documents are modified to incorporate the outcome of the Spell. For modifications pertaining to Agent Artifacts, the Operational Facilitator for the affected Agent is responsible for carrying out the required follow-up changes.\n\nThe updates must be completed in a timely manner following Spell execution, and must not introduce changes beyond those necessitated by the Spell outcome.","contentHash":"dfe5e795693454d7c21ab74054a0c4dc4cf840a4c5a4a3a72a990fb6f8f8d867","addressRefs":[]},"300fc1fe-ffa7-4204-8e38-0b9069b75bb9":{"id":"300fc1fe-ffa7-4204-8e38-0b9069b75bb9","doc_no":"A.1.10.2.4.13.6","title":"Spell Crafter Initiates Retrospective And Conducts Any Needed Follow Ups","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":698,"content":"With the Pull Request merged, the Spell Crafter turns to initiating the retrospective and conducting any needed follow-up as specified herein.","contentHash":"8f9d4b4cf1d0cf9655302f4c40bf73a81168dee7c4e8eee070f05610374cd05b","addressRefs":[]},"a5959563-d525-4431-b2e3-b1ebcaf88b99":{"id":"a5959563-d525-4431-b2e3-b1ebcaf88b99","doc_no":"A.1.10.2.4.13.6.1","title":"Spell Crafter Initiates Retrospective","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":699,"content":"The Spell Crafter initiates a retrospective on the Spell in the existing Spell thread in the `#govops` Discord channel. The Spell Crafter prefaces the message with `initiating retro`. The Spell Crafter should include any problems identified during the Spell, including concrete improvement proposals. If there is nothing to discuss, the Spell Crafter should communicate that (e.g `Initiating retro: nothing to discuss from my side`).","contentHash":"4b91b3f1a6669d5a03446d38581cad4baab5214ac5b150ea800337e63c5844df","addressRefs":[]},"e3009714-a46c-43b9-8f90-d09bd2e816b6":{"id":"e3009714-a46c-43b9-8f90-d09bd2e816b6","doc_no":"A.1.10.2.4.13.6.2","title":"Spell Crafter Conducts Any Needed Follow Up Regarding Megapoker","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":700,"content":"If any changes related to Megapoker were made in the Spell (e.g., oracles replaced, collaterals onboarded or offboarded), the Spell Crafter should inform the Ecosystem Actor responsible for maintaining Megapoker and ensure the contract is updated.\n\nThe following steps are necessary to ensure the Megapoker contract is updated:\n\n- Coordinate with Ecosystem Actor responsible for maintaining Megapoker and TechOps\n- Previous code patterns are followed\n- Megapoker changes are reviewed and approved\n- CI and local tests pass\n- New Megapoker contract is deployed\n- New deployed Megapoker contract address is handed to TechOps\n- New deployed Megapoker contract address is updated in README","contentHash":"8f0bff838a41c74d1a605f905025392ba58baaa3984a609aae4f627748b056e7","addressRefs":[]},"2d902745-59ae-4ea1-88bb-c5146ebd1750":{"id":"2d902745-59ae-4ea1-88bb-c5146ebd1750","doc_no":"A.1.10.2.4.13.6.3","title":"Spell Crafter Conducts Any Needed Follow Up Regarding New Collateral","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":701,"content":"If new collateral is onboarded, the Spell Crafter works with TechOps to ensure that there is Keeper support for the newly onboarded collateral.","contentHash":"e58dbed1408372a61e5fa2282a1b63dfd93421106adc42da44f567194d381fa5","addressRefs":[]},"f1365a6d-3749-48ed-aed4-966c3aa0bd5b":{"id":"f1365a6d-3749-48ed-aed4-966c3aa0bd5b","doc_no":"A.1.10.2.4.13.6.4","title":"Spell Crafter Conducts Any Needed Follow-Up Regarding Linear Interpolation Module","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":702,"content":"If a Linear Interpolation Module was added, the Spell Crafter ensures keeper support to call the `tall` function on a daily basis.","contentHash":"09264680285670b45f4f73a137d12396b59e99de0c585cf37e94ddc73171516a","addressRefs":[]},"0ad20a0f-2e23-4c24-b68d-55af08c32657":{"id":"0ad20a0f-2e23-4c24-b68d-55af08c32657","doc_no":"A.1.10.2.4.13.6.5","title":"Spell Crafter Conducts Specific Checks As Needed For High-Stakes Spells","type":"Core","depth":6,"parentId":"761cd866-17a9-47f5-8ae6-ab1788371be1","order":703,"content":"For critical or high-stakes Spells, the Spell Crafter conducts specific checks as required in the particular context of the Spell.","contentHash":"c666a668056afca9b3a554d08699920f2ebd1d1691c005312d10468c9ea17335","addressRefs":[]},"3aa5bc98-91ce-4588-b345-a96af8ba2366":{"id":"3aa5bc98-91ce-4588-b345-a96af8ba2366","doc_no":"A.1.10.2.5","title":"Voting Process For Executive Votes","type":"Core","depth":4,"parentId":"03d32549-1da5-4a9c-902f-196641370eaf","order":704,"content":"The subdocuments herein provide a high-level summary of the voting process for Executive Votes within the Sky Protocol.","contentHash":"aa717ccf9b9e058c6b2e406cfe7c11f85cc05e51ff1b95268a4f23c17d707b2c","addressRefs":[]},"441d8bef-e71a-4621-bc03-353821865031":{"id":"441d8bef-e71a-4621-bc03-353821865031","doc_no":"A.1.10.2.5.1","title":"Voting Requirements","type":"Core","depth":5,"parentId":"3aa5bc98-91ce-4588-b345-a96af8ba2366","order":705,"content":"Participation in Executive Votes requires access to SKY for voting, the governance token of the Sky Protocol, whether through direct ownership or delegated authority. Voters can connect their Ethereum wallet to the official voting platform (accessible at [https://vote.sky.money](https://vote.sky.money/)) to allocate their SKY vote-weight in support of an active proposal, or directly via onchain transactions using other interfaces or smart contract interactions. Voting incurs a gas fee, as it is an onchain transaction. SKY tokens can be used directly by holders or delegated to representatives like Aligned Delegates or Shadow Delegates, who vote on behalf of token holders see [A.1.10.2.2.4 - SKY Holders](3e1d0486-4805-4bed-a246-f75198e111e6). There is no minimum SKY amount required to vote, and each SKY token carries equal voting rights, ensuring a democratic process where cumulative vote-weight determines a proposal’s chance of execution.","contentHash":"23ef45b99f6116f6c68786264b17fed257fc8903c2727f6c2e2e6599bdb30be4","addressRefs":[]},"c888b306-369e-4db4-98cc-75beddc3689a":{"id":"c888b306-369e-4db4-98cc-75beddc3689a","doc_no":"A.1.10.2.5.2","title":"Voting Validation","type":"Core","depth":5,"parentId":"3aa5bc98-91ce-4588-b345-a96af8ba2366","order":706,"content":"Once an Executive Vote is live on the Voting Portal, it enters the Ecosystem Spell Validation Window, a critical period for community review. For more details of the validation process see [A.1.10.2.4.12 - Ecosystem Validators Validates Spell During Validation Window (Step 12)](84d31eb0-fbbc-4783-a7cf-ef7dddfa8271).","contentHash":"365951ae353f50dc4c8182d8883dda29d5e6c041bfddee6c3ed9d3ba159b892d","addressRefs":[]},"9b43b664-fcfc-484e-9faa-5ca0ffabd10e":{"id":"9b43b664-fcfc-484e-9faa-5ca0ffabd10e","doc_no":"A.1.10.2.5.3","title":"Continuous Approval Voting","type":"Core","depth":5,"parentId":"3aa5bc98-91ce-4588-b345-a96af8ba2366","order":707,"content":"Executive Votes operate under a Continuous Approval Voting mechanism. Voters can support multiple proposals by allocating their SKY vote-weight to each, with the goal of helping a favored proposal surpass the current \"hat\"—the proposal with the most approval in the DSChief contract. Voters can apply their full SKY vote-weight to up to 5 different proposals simultaneously (as defined by the `max_yays` limit in the contract), rather than splitting their tokens between them. If SKY token holders disagree with a new proposal, they can redirect their SKY vote-weight to the inactive proposal with the highest vote-weight (often the last successfully passed proposal) to maintain the status quo or support an alternative. An active proposal can become the hat if it accumulates more votes than any other, including the current hat, at which point it is \"lifted\" to become the new hat. This lifting process marks the active proposal, and it may now be scheduled and later executed, provided it meets other conditions like the GSM Pause Delay. There are three key aspects to Continuous Approval Voting:\n\n- Victory threshold set by the hat: The vote-weight on the current hat proposal establishes the \"victory threshold\" that new proposals must exceed to become eligible for execution. This ensures only the most supported changes advance.\n- Dynamic vote-weight movement: Vote-weight can shift from the hat to a new proposal, simultaneously lowering the victory threshold for the hat while boosting the new proposal’s chances. This fluidity allows for real-time community consensus shifts.\n- Securing the hat: Vote-weight is encouraged to remain on the hat proposal even after it’s lifted, acting as a security measure against \"rogue\" or less-supported proposals that might attempt to overtake it with minimal backing.","contentHash":"03a1f7a680e109eacc0c1936a0c2051a09cf8ccee3ea416a98ae3b8e20b200b8","addressRefs":[]},"9c5cae66-1317-43e9-bd85-041a9d8b5623":{"id":"9c5cae66-1317-43e9-bd85-041a9d8b5623","doc_no":"A.1.10.2.5.4","title":"Voting Outcome","type":"Core","depth":5,"parentId":"3aa5bc98-91ce-4588-b345-a96af8ba2366","order":708,"content":"The voting outcome is determined by the amount of SKY vote-weight allocated to the Executive Vote. If a proposal does not receive more SKY vote-weight than the current hat, it will not be scheduled for execution and will eventually expire; SKY holders can continue supporting it or redirect their vote-weight to another proposal, often the previously approved one, to maintain the status quo. For details of the execution process see [A.1.10.2.4.13 - Spell Execution Process And Retro (Step 13)](761cd866-17a9-47f5-8ae6-ab1788371be1).","contentHash":"6c933aa19112731657ebc281eebed8ca6d4c02002284e3bbc8334abaffa5eeb3","addressRefs":[]},"c5f0e955-0441-42e0-a6fc-eab875bba568":{"id":"c5f0e955-0441-42e0-a6fc-eab875bba568","doc_no":"A.1.10.3","title":"Governance Security Delay Requirements","type":"Section","depth":3,"parentId":"de0cc370-de9c-48a4-b10e-91782df7abcd","order":709,"content":"This subdocuments herein define critical processes and requirements concerning the Governance Security Module (GSM) Pause Delay.","contentHash":"68f3ed6cc9a0871b7eb8cf6a15a44c8c47c5578a5e718773d545ca3b2dd801b4","addressRefs":[]},"3c9545d9-775f-4149-88bf-7d297b5302c6":{"id":"3c9545d9-775f-4149-88bf-7d297b5302c6","doc_no":"A.1.10.3.1","title":"Pause Delay","type":"Core","depth":4,"parentId":"c5f0e955-0441-42e0-a6fc-eab875bba568","order":710,"content":"The GSM (Governance Security Module) Pause Delay parameter sets the minimum amount of time after an Executive Vote has passed before changes will come into effect in the Sky Protocol.\n\nOnce an Executive Vote passes, the GSM Pause Delay must pass before the changes within that Executive Vote can affect the Sky Protocol. The Sky Protocol only has one GSM Pause Delay, and all parameter changes are subject to it. The GSM Pause Delay is usually expressed in terms of hours.\n\nIt is possible to move functionality outside of the GSM Pause Delay; however, this requires additional engineering work. A list of exceptional functionality can be found in [A.1.10.3.2 - Exceptions](6781594b-5dff-45ec-89a4-1c9684c4eed8).","contentHash":"5b475cf50536d30be6b7929f8f28df6279b9f8fe5f8841aeb7085ce4c68121da","addressRefs":[]},"bcf9f14d-9c9b-4b3f-b417-a7e52fca0399":{"id":"bcf9f14d-9c9b-4b3f-b417-a7e52fca0399","doc_no":"A.1.10.3.1.1","title":"Pause Delay Adjustment","type":"Core","depth":5,"parentId":"3c9545d9-775f-4149-88bf-7d297b5302c6","order":711,"content":"Adjusting the GSM Pause Delay parameter is a manual process that requires an Executive Vote. Changes to the GSM Pause Delay are subject to the pre-change GSM Pause Delay.\n\nAn increase to the GSM Pause Delay parameter should be considered if the risk of governance attack is considered especially high for whatever reason. In the past, the GSM Pause Delay has been increased due to the risk from flash loans combined with increased liquidity of the SKY token on the open market.\n\nA decrease should be considered if time-critical governance actions are projected to be needed in the near future. For example, if extreme market volatility is expected, it may be beneficial to reduce the GSM Pause Delay temporarily to allow Governance to better react to changing conditions.","contentHash":"d3436ec99cd9efbc9d2a621df34445971debfad8d8bfcf8d50ebe2fd7dcb58d5","addressRefs":[]},"db442d8a-8d98-47a2-b162-01c2adc22b67":{"id":"db442d8a-8d98-47a2-b162-01c2adc22b67","doc_no":"A.1.10.3.1.2","title":"Pause Delay Current Value","type":"Core","depth":5,"parentId":"3c9545d9-775f-4149-88bf-7d297b5302c6","order":712,"content":"The GSM Pause Delay is: 48 hours","contentHash":"184e68f6640d12da64021496a02353bdadaea843e86173075d1cf19a9335eb36","addressRefs":[]},"6781594b-5dff-45ec-89a4-1c9684c4eed8":{"id":"6781594b-5dff-45ec-89a4-1c9684c4eed8","doc_no":"A.1.10.3.2","title":"Exceptions","type":"Core","depth":4,"parentId":"c5f0e955-0441-42e0-a6fc-eab875bba568","order":713,"content":"The current exceptions to the GSM Pause Delay are specified in the subdocuments herein.","contentHash":"3e1eac83c634440eb5ada63819dbf712496bfc34e5b64b9c260a7cd4b0645a4d","addressRefs":[]},"3041b5f2-36f4-49c5-b1ca-f0c97d6e63b2":{"id":"3041b5f2-36f4-49c5-b1ca-f0c97d6e63b2","doc_no":"A.1.10.3.2.1","title":"Executive Drop Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":714,"content":"The MCD_PAUSE contract manages the general governance timelock of the GSM Pause Delay; however, it also contains an in-built exception to its own rule.\n\nThe executive drop functionality allows a successful governance proposal to cancel a previous governance proposal that has not yet passed the GSM Pause Delay period and been executed. As in any other situation, the new Executive proposal must be the hat proposal, meaning more SKY is voting for it than is voting for any other Executive proposal.\n\nThis functionality allows Sky Governance to prevent a malicious attack on the protocol if they are able to exceed the attacker’s SKY weight before the GSM Pause Delay expires.\n\nThe risk opened up by this exceptional functionality is that a malicious attacker may be able to delay or permanently block a legitimate governance proposal.","contentHash":"ca1b02c95e9ad0d5b3430f98110fe71b1f3dcf77e7cf211712fbc5101091c5eb","addressRefs":[]},"e604c477-e8e4-483f-a41e-c93dcff3acfd":{"id":"e604c477-e8e4-483f-a41e-c93dcff3acfd","doc_no":"A.1.10.3.2.2","title":"Oracle Freeze Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":715,"content":"The OSM_MOM contract manages the freezing of Sky’s oracles. The freeze functionality allows a successful governance proposal to immediately freeze the oracle price for any or all of the vault types in the Sky Protocol. Once frozen, the oracle price will remain at its current value.\n\nThe oracle cannot be unfrozen without waiting for the GSM Pause Delay as part of a regular governance proposal.\n\nThe risk opened up by this exceptional functionality is that the oracles may be frozen by an attacker in order to either:\n\n- Prevent an expensive liquidation.\n- Take advantage of a significant drop in collateral prices to mint unbacked USDS.","contentHash":"14737fac04cd1fcd1a585e5b75046b440fbfcfc950ef6498b82ecfa4e83802e6","addressRefs":[]},"cd57f7e4-6acd-431e-97fd-89c3453c8eba":{"id":"cd57f7e4-6acd-431e-97fd-89c3453c8eba","doc_no":"A.1.10.3.2.3","title":"Debt Ceiling Breaker Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":716,"content":"The LINE_MOM contract manages the breaker for the Debt Ceilings of a configurable subset of the vault types in the Sky Protocol. This Debt Ceiling Breaker allows a successful governance proposal to reduce the debt ceilings of a pre-configured whitelist of vault types to zero without waiting for the GSM Pause Delay to expire.\n\nThe Debt Ceiling Breaker affects both the Debt Ceiling and the Maximum Debt Ceiling of a given vault type when activated, disabling the Dynamic Debt Ceiling functionality for that vault type if enabled. To reverse the effect, parameters of affected vault types must be reconfigured with an Executive Vote which is subject to the GSM Pause Delay.\n\nThe whitelist may be configured via a successful governance proposal, but must wait for the GSM Pause Delay before changes come into effect. The whitelist is defined in [A.1.10.3.2.3.1 - Debt Ceiling Breaker Exception Whitelist](4937205a-5be0-4def-9b7f-00f9f3bff421) and can be changed via the Weekly Governance Cycle.","contentHash":"960a494f136c00286d37b7352022d143a7c99cb228a433bdd6e7a03305cb7f39","addressRefs":[]},"4937205a-5be0-4def-9b7f-00f9f3bff421":{"id":"4937205a-5be0-4def-9b7f-00f9f3bff421","doc_no":"A.1.10.3.2.3.1","title":"Debt Ceiling Breaker Exception Whitelist","type":"Core","depth":6,"parentId":"cd57f7e4-6acd-431e-97fd-89c3453c8eba","order":717,"content":"- PSM (USDC) - PSM-USDC-A\n- PSM (PAX) - PSM-PAX-A\n- PSM (GUSD) - PSM-GUSD-A\n- ETH-A\n- ETH-B\n- ETH-C\n- WSTETH-A\n- WSTETH-B\n- WBTC-A\n- WBTC-B\n- WBTC-C\n- ALLOCATOR-SPARK-A\n- ALLOCATOR-BLOOM-A\n- ALLOCATOR-NOVA-A\n- ALLOCATOR-OBEX-A\n- LSE-MKR-A\n- LSEV2-SKY-A","contentHash":"e5ea8458d7d56d56cb3be4dac0b193797775ab810191dabf077bf6703866bc4d","addressRefs":[]},"54b41b8f-8104-47b9-a115-14a4a9716cf7":{"id":"54b41b8f-8104-47b9-a115-14a4a9716cf7","doc_no":"A.1.10.3.2.4","title":"Liquidations Circuit Breaker Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":718,"content":"The CLIPPER_MOM contract manages the circuit breaker for vault types using Liquidations 2.0. The circuit breaker functionality allows a successful governance proposal to impose Sky Governance’s choice of limitations on liquidations for any or all of the vault types in the Sky Protocol.\n\n- Level 0 - Liquidations Enabled - The breaker is not tripped, new vaults can be liquidated and old liquidations can proceed.\n- Level 1 - New Liquidations Disabled - No new liquidations can take place.\n- Level 2 - New Liquidations and Resets Disabled - No new liquidations can take place. No existing auctions can be reset if they expire.\n- Level 3 - All Liquidations Disabled - No new liquidations, no resets, no bidding in active auctions.\n\nThis functionality is exceptional because liquidations at non-market prices have the potential to be irreversibly damaging to both users and the Sky Protocol. The circuit breaker allows Sky Governance to attempt to limit the damage in the event of an issue affecting liquidations without waiting for the GSM Pause Delay.\n\nAdditionally, the contract allows for permissionless activation of the circuit breaker, if the price decrease in a collateral exceeds a preset percentage value between oracle price updates. The permissionless activation triggers the circuit breaker at Level 2 because both new auctions and resets reference the current oracle price.\n\nWhen Level (0, 1, 2, 3) of liquidations circuit breaker is altered via Executive Vote, Sky Governance has the ability to set locked time, which is a specified duration which needs to pass before the liquidations circuit breaker can be triggered again via permissionless activation.\n\nThe risk opened up by this exceptional functionality is that liquidations may be halted by an attacker in order to either:\n\n- Prevent an expensive liquidation.\n- Take advantage of a significant drop in collateral prices to mint unbacked USDS.","contentHash":"94e2214ea6a1bd9edb6e714a293f3044258bbbc119ebac8b7a5165157225b1ac","addressRefs":[]},"a228410a-353b-45dc-8f26-aae54ad8bf44":{"id":"a228410a-353b-45dc-8f26-aae54ad8bf44","doc_no":"A.1.10.3.2.4.1","title":"Liquidations Circuit Breaker Exception Price Tolerance","type":"Core","depth":6,"parentId":"54b41b8f-8104-47b9-a115-14a4a9716cf7","order":719,"content":"Breaker Price Tolerance is a parameter which determines the condition for the permissionless activation of circuit breaker. Adjusting the Breaker Price Tolerance requires an Executive Vote, which is subject to GSM Pause Delay.\n\nThe Breaker Price Tolerance is expressed as a number between zero and one, and works with the following equation: `next_oracle_price < current_oracle_price * breaker_price_tolerance`.\n\nIn instances where the price oracle model does not support the price delay function, the permissionless activation of the liquidation circuit breaker ceases to function, since there is no next oracle price.","contentHash":"56dc74c473017f48954984983222096efda5607537243b326e37a153a4dab24d","addressRefs":[]},"cd377adf-aee4-42b2-9bbc-0e4a69570e0b":{"id":"cd377adf-aee4-42b2-9bbc-0e4a69570e0b","doc_no":"A.1.10.3.2.4.1.1","title":"Liquidations Circuit Breaker Exception Price Tolerance Current Value","type":"Core","depth":6,"parentId":"54b41b8f-8104-47b9-a115-14a4a9716cf7","order":720,"content":"The Breaker Price Tolerance is: 0.5","contentHash":"e9bbf02aa3d39c3fa2238d5257075eed0d1a16d4dca170aac49bd8195868fcb3","addressRefs":[]},"2a0f27c9-7468-465d-9e07-19481f5e8c89":{"id":"2a0f27c9-7468-465d-9e07-19481f5e8c89","doc_no":"A.1.10.3.2.5","title":"Direct Deposit Breaker Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":721,"content":"The DIRECT_MOM contract manages the breaker for Direct Deposit Modules (D3Ms). The breaker functionality allows a successful governance proposal to disable any or all of the active D3Ms. In practice, this will set the bar parameter to zero, which (contrary to intuition) disables the module by setting the allowed Debt Ceiling to zero. At this point, no further USDS can be minted through the Direct Deposit Module. To reverse the effect, parameters of affected Direct Deposit Modules must be reconfigured with an Executive Vote which is subject to GSM Pause Delay.\n\nThe risk opened up by this exceptional functionality is that a given line of USDS credit is unexpectedly shut down. This has the potential to disrupt the protocol in question, which may impact Sky indirectly.","contentHash":"d2c7e2b135eb86a0a7806ecc5320f1c5b60bd502058fdf3c5dc78480e42c1c79","addressRefs":[]},"d07e74b5-2faa-4d4d-9b4f-eb6ea72e8768":{"id":"d07e74b5-2faa-4d4d-9b4f-eb6ea72e8768","doc_no":"A.1.10.3.2.6","title":"Dynamic Debt Ceiling Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":722,"content":"The MCD_IAM_AUTO_LINE contract manages the debt ceiling parameters for many of Sky’s vault types according to preset rules. Keepers can use the contract to attempt to maintain a Target Available Debt in a given vault type. The contract modifies the debt ceiling up or down to maintain a level of available debt.\n\nThis functionality is exceptional so that the Sky protocol can react to changes in debt demand more quickly than waiting for the GSM Pause Delay.\n\nThe risk opened up by this exceptional functionality is a theoretical griefing attack on the IAM that prevents debt from being accessible in affected vault types.","contentHash":"1364cff7ee8f2e2b906aa4a857f3f8a429a8dec56eff5c30c7dff5c960085aac","addressRefs":[]},"645443f1-9004-48d3-868c-139b608bb1f9":{"id":"645443f1-9004-48d3-868c-139b608bb1f9","doc_no":"A.1.10.3.2.7","title":"SparkLend Freezer Mom Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":723,"content":"The SparkLend FREEZER_MOM contract allows Sky Governance to bypass the GSM Pause Delay to either freeze or pause any markets in SparkLend. The contract also allows the undoing of such actions for any market in SparkLend.\n\nThis functionality allows Sky Governance to react faster in an emergency. Freezing markets does not allow for new supplies or borrows, while pause restricts all market functionality, including deposits/withdrawals/borrows/repays and liquidations.","contentHash":"7d73fd7ddd05821bfcb4807f65a1e6625721300b75def2ceb0d956211d10431f","addressRefs":[]},"5247c795-7f9d-4d3f-a040-6bc9b070e2d4":{"id":"5247c795-7f9d-4d3f-a040-6bc9b070e2d4","doc_no":"A.1.10.3.2.8","title":"Smart Burn Engine Breaker Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":724,"content":"The SPLITTER_MOM contract allows for the disabling of the Smart Burn Engine without the GSM Pause Delay.\n\nThis functionality is available so that Sky Governance can react to emergencies regarding the Smart Burn Engine.\n\nSince the Splitter contract also allocates USDS from the Surplus Buffer to USDS Staking Rewards, the activation of SPLITTER_MOM also disables these rewards until the activation is reversed by Sky Governance.","contentHash":"cf72ff067d90d5284033283855e900a1efec5c09c3dfe457c66dcb573f8ac0d9","addressRefs":[]},"704fbaff-fa10-4c63-af5b-3ee5fd1ea6a8":{"id":"704fbaff-fa10-4c63-af5b-3ee5fd1ea6a8","doc_no":"A.1.10.3.2.9","title":"PSM Breaker Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":725,"content":"The LITE_PSM_MOM contract manages the breaker for swaps through the LitePSM. The PSM Breaker allows a successful governance proposal to halt swaps through the LitePSM.","contentHash":"34fed5235d42aca4f3a298835585a75f7614978e9aeb8c2b05890c0919f8ca36","addressRefs":[]},"5533c091-e638-4c3d-92e8-43e3e7026078":{"id":"5533c091-e638-4c3d-92e8-43e3e7026078","doc_no":"A.1.10.3.2.10","title":"Bounded External Access Modules","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":726,"content":"Bounded External Access Modules (BEAMs) are contracts that allow whitelisted operators to manage parameters in the Sky Ecosystem without needing to use the standard Executive Vote process. Thus, parameter changes enacted via these modules are not subject to the GSM Pause Delay.\n\nThe actions of BEAMs are limited by risk parameters, which are set by Sky Core Governance and require an Executive Vote to change.","contentHash":"6b9c83acfff48f820094b961be8bb2fe153d88944104fcca405f07dac48913d2","addressRefs":[]},"b2bffec7-2a62-43a1-bfed-1e38370ac086":{"id":"b2bffec7-2a62-43a1-bfed-1e38370ac086","doc_no":"A.1.10.3.2.10.1","title":"Bounded External Access Module Risk Disclosure","type":"Core","depth":6,"parentId":"5533c091-e638-4c3d-92e8-43e3e7026078","order":727,"content":"BEAMs allow whitelisted operators greater flexibility to respond to market movements when setting parameters in the Sky Ecosystem. This flexibility introduces additional risk since operators are able to bypass the Executive Vote process when changing the parameters relevant to the BEAM that they operate.\n\nThis risk can be mitigated by limiting the frequency and size of modifications that can be made by operators in parameters controlled by Sky Core. All BEAMs should also have a related MOM contract that can deactivate the relevant BEAM in the event of an operator acting in a misaligned manner.\n\nAny operator that fails to follow the defined procedures for a BEAM they are operating should be considered misaligned.","contentHash":"eb029f9453a0cc6284b7a675cc20fc80e196e5dd31d3fc5b591f1b8dad16519f","addressRefs":[]},"12bb55dc-8f44-4f7a-a7f8-bf197a278784":{"id":"12bb55dc-8f44-4f7a-a7f8-bf197a278784","doc_no":"A.1.10.3.2.10.2","title":"Stability Parameter Bounded External Access Module Exception","type":"Core","depth":6,"parentId":"5533c091-e638-4c3d-92e8-43e3e7026078","order":728,"content":"The Stability Parameter Bounded External Access Module (SP-BEAM) MCD_SPBEAM contract manages the rates applied to Sky Protocol’s native vaults as well as the savings rates. Whitelisted operators can use the SP-BEAM to modify rates without waiting for the GSM Pause Delay. The SP-BEAM modifies rates up or down within specified parameters. See [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n\nThis functionality allows the Sky Protocol to react to changes in market rates more quickly than waiting for an Executive Vote and the GSM Pause Delay.\n\nThe risk opened up by this functionality is malicious action by whitelisted operators setting rates to undesirable values. This risk can be mitigated through the SP-BEAM parameters and the SPBEAM_MOM.","contentHash":"c0ae81a0a3788d2e8e64766ae259e74e33fb8450d2058d3d5d26b5afc6442d55","addressRefs":[]},"5ce20b57-b8bb-4a67-b5b6-a28b707e2cb2":{"id":"5ce20b57-b8bb-4a67-b5b6-a28b707e2cb2","doc_no":"A.1.10.3.2.10.3","title":"stUSDS Bounded External Access Module Exception","type":"Core","depth":6,"parentId":"5533c091-e638-4c3d-92e8-43e3e7026078","order":729,"content":"The stUSDS Bounded External Access Module (stUSDS BEAM) manages the parameters of the stUSDS system. Whitelisted operators can use the stUSDS BEAM to modify certain stUSDS parameters without waiting for the GSM Pause Delay. The stUSDS BEAM modifies stUSDS parameters within specified ranges. See [A.4.4.1.3.8 - stUSDS Bounded External Access Module](37f8f82e-7239-4cfb-8f95-d2cc40515cd9).\n\nThis functionality allows the Sky Protocol to update stUSDS parameters more quickly than waiting for an Executive Vote and the GSM Pause Delay.\n\nThe risk opened up by this functionality is malicious action by whitelisted operators setting stUSDS parameters to undesirable values. This risk can be mitigated through the stUSDS BEAM parameters and the STUSDS_MOM.","contentHash":"eba9c5ead9c96680560f68990a26a886c02e0aa202e4bb1bbeabbf6f9b8b18a3","addressRefs":[]},"1fd7d164-e9f3-4d6c-ab5e-0122bb415f8d":{"id":"1fd7d164-e9f3-4d6c-ab5e-0122bb415f8d","doc_no":"A.1.10.3.2.11","title":"Stability Parameter Bounded External Access Module Breaker Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":730,"content":"The SPBEAM_MOM contract allows Sky Governance to bypass the GSM Pause Delay and disable the Stability Parameter Bounded External Access Module.\n\nThis functionality allows Sky Governance to react more quickly in an emergency, e.g., if an operator of the SP-BEAM is hacked or is a malicious actor. Once the SPBEAM_MOM is activated, the SP-BEAM will not be able to change any rates in the system. If the SPBEAM_MOM has been triggered, it will still be possible to modify rates through the usual Executive Vote process, subject to the GSM Pause Delay.","contentHash":"7c991f8cafd8e79bbf4167cdd335ccad5ef5b6726aade97b75f5a753e575cc18","addressRefs":[]},"b9f3824c-31a5-472c-8a53-8166f3eeb7ee":{"id":"b9f3824c-31a5-472c-8a53-8166f3eeb7ee","doc_no":"A.1.10.3.2.12","title":"stUSDS Bounded External Access Module Breaker Exception","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":731,"content":"The STUSDS_MOM contract allows Sky Governance to bypass the GSM Pause Delay and disable the stUSDS Bounded External Access Module or set the `cap` or `line` stUSDS parameters to zero.\n\nThis functionality allows Sky Governance to react more quickly in an emergency, e.g., if an operator of the stUSDS BEAM is hacked or is a malicious actor. Once the STUSDS_MOM is activated to disable the stUSDS BEAM, the stUSDS BEAM will not be able to change any stUSDS parameters in the system. If the STUSDS_MOM has been triggered, it will still be possible to modify stUSDS parameters through the usual Executive Vote process, subject to the GSM Pause Delay.","contentHash":"92bef71f9742fc655e35d83abbb6aa7be2cf8b404d779089fe1d2e6cadc9bacf","addressRefs":[]},"60767684-f67f-4e03-85db-7718af41b827":{"id":"60767684-f67f-4e03-85db-7718af41b827","doc_no":"A.1.10.3.2.13","title":"Linear Interpolation Module","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":732,"content":"The Linear Interpolation Module (`lerp`) is a smart contract tool that allows a governance parameter to be adjusted on a straight-line basis over time, without requiring additional Executive Votes. The Linear Interpolation Module refers to the smart contract logic that enables time-based parameter changes. To deploy individual `lerp` instances, each of which manages the adjustment of a specific parameter over time, the Linear Interpolation Module Factory contract is used. Once authorized through an Executive Vote, the `lerp` may enact parameter changes without being subject to the GSM Pause Delay. The subdocuments herein specify the features of the `lerp` and its authorized use.","contentHash":"29c0099a4cc0d4f64347e23da310fcf937f754d04746fe13728967b395e7e2a8","addressRefs":[]},"c21d4246-8294-4f30-b69d-3d6056247893":{"id":"c21d4246-8294-4f30-b69d-3d6056247893","doc_no":"A.1.10.3.2.13.1","title":"Linear Interpolation Module Features","type":"Core","depth":6,"parentId":"60767684-f67f-4e03-85db-7718af41b827","order":733,"content":"The `lerp` must be activated in an Executive Vote but can thereafter change the value of the designated parameter without additional Executive Votes. Each `lerp` instance is defined in terms of a `start` value, representing the desired starting value, an `end` value, representing the desired ending value, and a `duration` over which the parameter will be adjusted between the starting value and the ending value. Any user can then permissionlessly call `tick` to set the governance parameter to the appropriate value based on the time elapsed.","contentHash":"2def71ab08142e551ed61aa26c37f831ab7ca97d16b41277be3844dd38107645","addressRefs":[]},"ac2fb8ab-4137-4243-8f75-1817f8529a70":{"id":"ac2fb8ab-4137-4243-8f75-1817f8529a70","doc_no":"A.1.10.3.2.13.1.1","title":"Linear Interpolation Module Parameters","type":"Core","depth":6,"parentId":"60767684-f67f-4e03-85db-7718af41b827","order":734,"content":"Each `lerp` instance has the following parameters:\n\n- `target` - The target contract in which a parameter is being changed\n- `what` - The name of the parameter being changed\n- `startTime` - The starting time of this `lerp` instance\n- `start` - The starting value of that parameter\n- `end` - The ending value of that parameter\n- `duration` - How long this `lerp` instance will run for\n- `done` - Indicates whether this given `lerp` instance is completed or not","contentHash":"dc9e6445837c42db7a382cd392c2ea8382e1f97ad936dd442c084553ee6f083f","addressRefs":[]},"59fecdcf-6d2b-4a2d-96bf-af1729fc2bf9":{"id":"59fecdcf-6d2b-4a2d-96bf-af1729fc2bf9","doc_no":"A.1.10.3.2.13.1.2","title":"Linear Interpolation Module Factory","type":"Core","depth":6,"parentId":"60767684-f67f-4e03-85db-7718af41b827","order":735,"content":"`lerp` instances are created using a factory contract LERP_FAB that contains standard logic for creating those instances and maintains a registry of all active `lerp` instances. The contract may also be used to cancel an existing `lerp` instance through the `remove` function. The factory contract provides a `list` method that lists the addresses of all active `lerp` instances, as well as a `tall` (short for \"tick all\") method that calls `tick` on all active contracts.","contentHash":"97f9f00d8e4bbc010200801489180f31d6a26130ee6f26f01dbf3209635e7e38","addressRefs":[]},"2de4d031-e079-415e-b982-66a4efa78c05":{"id":"2de4d031-e079-415e-b982-66a4efa78c05","doc_no":"A.1.10.3.2.13.2","title":"Linear Interpolation Module Usage Process Definition","type":"Core","depth":6,"parentId":"60767684-f67f-4e03-85db-7718af41b827","order":736,"content":"The subdocuments herein define the governance process for using the Linear Interpolation Module.","contentHash":"094951ac18dc9d38fcf54de6aabc0fa0b7679acce49764dfa73addea5da36a9c","addressRefs":[]},"9652bd2c-f51c-42bb-9240-701e9723f574":{"id":"9652bd2c-f51c-42bb-9240-701e9723f574","doc_no":"A.1.10.3.2.13.2.1","title":"Linear Interpolation Module Authorization","type":"Core","depth":6,"parentId":"60767684-f67f-4e03-85db-7718af41b827","order":737,"content":"The Facilitators responsible for the Scope that governs the parameter to be adjusted by the Linear Interpolation Module, in consultation with the Core Council Risk Advisor, may recommend deploying the Linear Interpolation Module for parameter adjustments.","contentHash":"31bc886bd807c63d08f094d4941ac35ae44d589242fe502a3a6f70461b3d4ea4","addressRefs":[]},"dd631146-0227-4fe3-87dd-085d0c909879":{"id":"dd631146-0227-4fe3-87dd-085d0c909879","doc_no":"A.1.10.3.2.13.2.1.1","title":"Linear Interpolation Module Consideration","type":"Core","depth":6,"parentId":"60767684-f67f-4e03-85db-7718af41b827","order":738,"content":"The Facilitators must take into consideration the benefits and costs with using the Linear Interpolation Module. A longer `duration` has the benefit of adjusting the parameter more slowly, giving users more time to adjust. However, the drawback of a longer `duration` is that the parameter will not reach its desired `end` value for a longer period of time. When the cost of a parameter not being at its desired value is high, use of the Linear Interpolation Module is not appropriate, and the parameter should be adjusted to its desired value following the required process.","contentHash":"576901d6eec4836b678886a9c7e649358f799a0fe29345ea5222c4ad75434c8f","addressRefs":[]},"3a075a4b-4071-4993-8210-5a87d13203b2":{"id":"3a075a4b-4071-4993-8210-5a87d13203b2","doc_no":"A.1.10.3.2.13.2.1.2","title":"Governance Process For Linear Interpolation Module","type":"Core","depth":6,"parentId":"60767684-f67f-4e03-85db-7718af41b827","order":739,"content":"The process to utilize the Linear Interpolation Module to adjust a parameter must follow the same governance process required to modify the designated parameter. If the parameter can be updated directly through an Executive Vote, then utilizing the Linear Interpolation Module to adjust it may also be included directly in an Executive Vote. If modifying the parameter requires a prior Governance Poll, then utilizing the Linear Interpolation Module for that parameter must also be preceded by a Governance Poll.","contentHash":"4850bc4ee892c3c5c6e93ed1425efbf795fcd520d095dd8580eab7e91cd1bd8a","addressRefs":[]},"b7820ec3-dbe5-43bc-99b9-c7168c53c8fe":{"id":"b7820ec3-dbe5-43bc-99b9-c7168c53c8fe","doc_no":"A.1.10.3.2.14","title":"Ethereum SkyLink Freezer Multisig","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":740,"content":"The Ethereum SkyLink Freezer Multisig (see [A.1.10.4.1.1 - Ethereum SkyLink Freezer Multisig](21fa6749-6209-4280-9b5f-b2a73d400421)) can freeze SkyLink bridges deployed in the Sky Ecosystem without the need for inclusion in a Spell through the standard Executive Vote process.\n\nEach action executed by the multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum. Such actions include activating or disabling the freeze function.","contentHash":"f6053a46b5ce5ac904943826789b573541f066d51beee217751fdae5aa8693bb","addressRefs":[]},"82aaec1b-acac-4ed4-8e03-2d8f29ba5ccb":{"id":"82aaec1b-acac-4ed4-8e03-2d8f29ba5ccb","doc_no":"A.1.10.3.2.15","title":"Solana SkyLink Freezer Multisig","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":741,"content":"The Solana SkyLink Freezer Multisig (see [A.1.10.4.1.2.3.1.1 - Solana SkyLink Freezer Multisig](8e618196-257a-49d8-834d-665dba345fcd)) can freeze the Solana SkyLink Bridge without the need for inclusion in a Spell through the standard Executive Vote process.\n\nEach action executed by the multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum. Such actions include activating or disabling the freeze function.","contentHash":"9ecdcdb15771b48e10dbfb2bb123ee00dc66f91953152b49c3ced066b110c1ec","addressRefs":[]},"57f524b8-292c-496b-a879-2102ce4a81e5":{"id":"57f524b8-292c-496b-a879-2102ce4a81e5","doc_no":"A.1.10.3.2.16","title":"Avalanche SkyLink Freezer Multisig","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":742,"content":"The Avalanche SkyLink Freezer Multisig (see [A.1.10.4.1.3.3.1.1 - Avalanche SkyLink Freezer Multisig](0b1162f6-6a30-4a30-b693-68e077093e7c)) can freeze the Avalanche SkyLink Bridge without the need for inclusion in a Spell through the standard Executive Vote process.\n\nEach action executed by the multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum. Such actions include activating or disabling the freeze function.","contentHash":"c1166c8f63ae8fa4f39ac24e8adb89d0364562f71cc4471a0ebfee733f91594d","addressRefs":[]},"93089354-d2eb-4930-a1c7-0ca2f7b60e67":{"id":"93089354-d2eb-4930-a1c7-0ca2f7b60e67","doc_no":"A.1.10.3.2.17","title":"Plasma SkyLink Freezer Multisig","type":"Core","depth":5,"parentId":"6781594b-5dff-45ec-89a4-1c9684c4eed8","order":743,"content":"The Plasma SkyLink Freezer Multisig (see [A.1.10.4.1.4.3.1.1 - Plasma SkyLink Freezer Multisig](f833edaa-9f5f-4445-afcb-a9cfc3620b10)) can freeze the Plasma SkyLink Bridge without the need for inclusion in a Spell through the standard Executive Vote process.\n\nEach action executed by the multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum. Such actions include activating or disabling the freeze function.","contentHash":"fc1d3e9851ea0c2ba544c8eef053b802ea47560608fa12b63c540c463466612c","addressRefs":[]},"19222532-1ce1-4306-8129-ea95a982c247":{"id":"19222532-1ce1-4306-8129-ea95a982c247","doc_no":"A.1.10.4","title":"Governance Security Culture And Research","type":"Section","depth":3,"parentId":"de0cc370-de9c-48a4-b10e-91782df7abcd","order":744,"content":"This Section must define processes to cultivate and maintain a strong security culture within the Sky Ecosystem. This Section must implement continuous research and integration of best practices to ensure that the Ecosystem’s security remains effective and up-to-date.","contentHash":"2eb8ca8619636f43243ae7cf17c43409b3382296e931f697fd36817bb7d4c55f","addressRefs":[]},"bd68f60c-f2dc-4c0e-9209-ba5aa20b6f2f":{"id":"bd68f60c-f2dc-4c0e-9209-ba5aa20b6f2f","doc_no":"A.1.10.4.1","title":"SkyLink Bridges","type":"Core","depth":4,"parentId":"19222532-1ce1-4306-8129-ea95a982c247","order":745,"content":"The documents herein define the LayerZero-based SkyLink bridges deployed by the Sky Ecosystem, as well as shared security infrastructure across these bridges.","contentHash":"6268f56de70aa94aeee12f36b8d61a35f2180b38c2566eab84fb296b4d21987e","addressRefs":[]},"21fa6749-6209-4280-9b5f-b2a73d400421":{"id":"21fa6749-6209-4280-9b5f-b2a73d400421","doc_no":"A.1.10.4.1.1","title":"Ethereum SkyLink Freezer Multisig","type":"Core","depth":5,"parentId":"bd68f60c-f2dc-4c0e-9209-ba5aa20b6f2f","order":746,"content":"The Ethereum SkyLink Freezer Multisig has the ability to freeze SkyLink bridges deployed in the Sky Ecosystem from Ethereum Mainnet.","contentHash":"69146762aa2375e618ac9ecc1b7e4b672124003b761b7dd06a75553cf4ea370d","addressRefs":[]},"4192a2f6-a660-476d-bbb8-677a78b1c3a3":{"id":"4192a2f6-a660-476d-bbb8-677a78b1c3a3","doc_no":"A.1.10.4.1.1.1","title":"Ethereum SkyLink Freezer Multisig Address","type":"Core","depth":6,"parentId":"21fa6749-6209-4280-9b5f-b2a73d400421","order":747,"content":"The address of the Ethereum SkyLink Freezer Multisig on the Ethereum Mainnet is `0x38d1114b4cE3e079CC0f627df6aC2776B5887776`.","contentHash":"4b5aabeb0b56b3e798ad2e5aa718acc65ec690acd82b2f73cd7d276ab84aea1f","addressRefs":["0x38d1114b4ce3e079cc0f627df6ac2776b5887776"]},"861347b3-320f-48fb-ab9a-e9030cb9e44f":{"id":"861347b3-320f-48fb-ab9a-e9030cb9e44f","doc_no":"A.1.10.4.1.1.2","title":"Ethereum SkyLink Freezer Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"21fa6749-6209-4280-9b5f-b2a73d400421","order":748,"content":"The Ethereum SkyLink Freezer Multisig has a 2/4 signing requirement.","contentHash":"5ea944cf236cc2526ad3df851669a6fdc6c8555bfd98dcdfab9aa9a999336317","addressRefs":[]},"2a86809e-8b34-4692-92fe-bcb75b00ce6d":{"id":"2a86809e-8b34-4692-92fe-bcb75b00ce6d","doc_no":"A.1.10.4.1.1.3","title":"Ethereum SkyLink Freezer Multisig Signers","type":"Core","depth":6,"parentId":"21fa6749-6209-4280-9b5f-b2a73d400421","order":749,"content":"The signers of the Ethereum SkyLink Freezer Multisig are two (2) addresses controlled by the Core Facilitator and two (2) addresses controlled by Core GovOps.","contentHash":"14b76f340b7929b072d00aae723096e29498b54b7f89edbac1e40596a32d5bbd","addressRefs":[]},"c0337114-d46d-436f-892d-4f6feb192b29":{"id":"c0337114-d46d-436f-892d-4f6feb192b29","doc_no":"A.1.10.4.1.1.4","title":"Ethereum SkyLink Freezer Multisig Usage Standards","type":"Core","depth":6,"parentId":"21fa6749-6209-4280-9b5f-b2a73d400421","order":750,"content":"The Ethereum SkyLink Freezer Multisig can only be used in urgent or emergency situations (e.g., potential code exploits). Such situations are characterized by the fact that 1) they have the potential to harm the Sky Ecosystem or its users; and 2) the preparation time required for an Executive Vote would leave the ecosystem vulnerable to harm (e.g., an exploit).\n\nThe multisig should be used to prevent technical vulnerabilities; prevent unwanted functionality of the smart contracts or corresponding parts of the system (e.g., price oracles); or prevent unwanted usage of the smart contracts or corresponding parts of the system which deviates from intended behavior.\n\nThe Core Council must ensure that use of the multisig is generally aligned and specifically accords with these requirements.","contentHash":"0a377040fd94cdc14f7b02b20d08e742cc4f6b84405d52c76dfaf40e934a7487","addressRefs":[]},"af5b97be-bf52-431d-8fa9-9b1c6164e328":{"id":"af5b97be-bf52-431d-8fa9-9b1c6164e328","doc_no":"A.1.10.4.1.1.5","title":"Ethereum SkyLink Freezer Multisig Modification","type":"Core","depth":6,"parentId":"21fa6749-6209-4280-9b5f-b2a73d400421","order":751,"content":"The Core Facilitator and Core GovOps can change the signers of the Ethereum SkyLink Freezer Multisig so long as:\n\n- there are four (4) signers;\n- two (2) signers are required to execute transactions; and\n- an equal number of signers are controlled by the Core Facilitator and Core GovOps.","contentHash":"365ac406439ac32c93b7ba221635e6d972fb8261806988d8f61f798e5861a3fb","addressRefs":[]},"56593663-55e5-45d5-8682-5eede11aa14a":{"id":"56593663-55e5-45d5-8682-5eede11aa14a","doc_no":"A.1.10.4.1.2","title":"Solana SkyLink Bridge","type":"Core","depth":5,"parentId":"bd68f60c-f2dc-4c0e-9209-ba5aa20b6f2f","order":752,"content":"Sky uses a SkyLink bridge to securely move assets between Ethereum Mainnet and Solana, as well as to provide governance controls for Sky-issued tokens on Solana.","contentHash":"9ebb56d2abdf23ef2b153982b10ea67fca5e079c05b942266a409d3cfbeb05ee","addressRefs":[]},"1157a0cd-9acc-4149-9258-d7f8946df475":{"id":"1157a0cd-9acc-4149-9258-d7f8946df475","doc_no":"A.1.10.4.1.2.1","title":"Introduction","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":753,"content":"The Solana SkyLink Bridge consists of both a Token Bridge that allows bridging USDS between Ethereum Mainnet and Solana as well as a Governance Bridge that allows exercising governance control for Sky-issued tokens on Solana.","contentHash":"837ddc4342e35cfbe3f8a3c8d09a652c61f6a9c6429b64faa6279549eda8ab12","addressRefs":[]},"593095a6-aec4-4ca5-9c2e-87ce748ac198":{"id":"593095a6-aec4-4ca5-9c2e-87ce748ac198","doc_no":"A.1.10.4.1.2.2","title":"Deployment","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":754,"content":"The Solana SkyLink Bridge was deployed in two phases. The first phase occurred in the November 13, 2025 Executive Vote and the second phase occurred in the November 17, 2025 Out-Of-Schedule Executive Vote.","contentHash":"3ae3dc55cbcb33795f1b52fbd84df92fb2a4515e47033a8566ec351dfe48ddce","addressRefs":[]},"2cf3dc2e-2a2a-4f8a-a959-611e5654a29c":{"id":"2cf3dc2e-2a2a-4f8a-a959-611e5654a29c","doc_no":"A.1.10.4.1.2.3","title":"Security Parameters","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":755,"content":"The documents herein define the security parameters of the Solana SkyLink Bridge.","contentHash":"1f0a4ca6bf68a138b082110b0b30dc11198615e8e3f3dab81d9a69ae88126245","addressRefs":[]},"d70d5580-760f-4441-9f93-7494e0d05808":{"id":"d70d5580-760f-4441-9f93-7494e0d05808","doc_no":"A.1.10.4.1.2.3.1","title":"Freezer Multisigs","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":756,"content":"The Solana SkyLink Bridge can be frozen from Ethereum Mainnet by the Ethereum SkyLink Freezer Multisig as specified in [A.1.10.4.1.1 - Ethereum SkyLink Freezer Multisig](21fa6749-6209-4280-9b5f-b2a73d400421). The document herein defines the Solana-side freezer multisig.","contentHash":"a5a237b55fcbe07ba6ca73b34439589d90a72437f7c6189d2d0c3de7aa81fc8d","addressRefs":[]},"8e618196-257a-49d8-834d-665dba345fcd":{"id":"8e618196-257a-49d8-834d-665dba345fcd","doc_no":"A.1.10.4.1.2.3.1.1","title":"Solana SkyLink Freezer Multisig","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":757,"content":"The Solana SkyLink Freezer Multisig has the ability to freeze the Solana SkyLink Bridge from Solana.","contentHash":"a66736c97361a514640c093a7b842b40d406d906c05844069e9a8df0f16923e3","addressRefs":[]},"bb0b31dd-f68c-4ea1-b36e-ceda655bee7d":{"id":"bb0b31dd-f68c-4ea1-b36e-ceda655bee7d","doc_no":"A.1.10.4.1.2.3.1.1.1","title":"Solana SkyLink Freezer Multisig Address","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":758,"content":"The address of the Solana SkyLink Freezer Multisig on Solana is `5hARLsT1VA2AmuGL2AXUeSyyFG6o2Fcpb9S6aKXNsbeK`.","contentHash":"38ccf02fd99b385f7610278ef39adcb60b8586925dfd3ddfef17c5dee1b0bc3f","addressRefs":["5hARLsT1VA2AmuGL2AXUeSyyFG6o2Fcpb9S6aKXNsbeK"]},"f376a4da-0818-4d13-a496-25451577fe32":{"id":"f376a4da-0818-4d13-a496-25451577fe32","doc_no":"A.1.10.4.1.2.3.1.1.2","title":"Solana SkyLink Freezer Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":759,"content":"The Solana SkyLink Freezer Multisig has a 2/4 signing requirement.","contentHash":"60ad37dcd0b14936737e64158d53b0ff593bc12d6716335b910c5e6709ced9a9","addressRefs":[]},"a9f95fb4-690e-43c2-a231-b8705d62036d":{"id":"a9f95fb4-690e-43c2-a231-b8705d62036d","doc_no":"A.1.10.4.1.2.3.1.1.3","title":"Solana SkyLink Freezer Multisig Signers","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":760,"content":"The signers of the Solana SkyLink Freezer Multisig are two (2) addresses controlled by Operational GovOps Soter Labs and two (2) addresses controlled by Operational Facilitator Endgame Edge.","contentHash":"2f320e979a325e44b9ee5f20994355a422bf726da4a02d5b34aeea5afea1835e","addressRefs":[]},"9f845d09-4304-4aa7-8bd0-2dda747e52e6":{"id":"9f845d09-4304-4aa7-8bd0-2dda747e52e6","doc_no":"A.1.10.4.1.2.3.1.1.4","title":"Solana SkyLink Freezer Multisig Usage Standards","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":761,"content":"The Solana SkyLink Freezer Multisig can only be used in urgent or emergency situations (e.g., potential code exploits). Such situations are characterized by the fact that 1) they have the potential to harm the Sky Ecosystem or its users; and 2) the preparation time required for an Executive Vote would leave the ecosystem vulnerable to harm (e.g., an exploit).\n\nThe multisig should be used to prevent technical vulnerabilities; prevent unwanted functionality of the smart contracts or corresponding parts of the system (e.g., price oracles); or prevent unwanted usage of the smart contracts or corresponding parts of the system which deviates from intended behavior.\n\nThe Core Council must ensure that use of the multisig is generally aligned and specifically accords with these requirements.","contentHash":"ed7e3a4e5bb377d7a48f51705e598338f8f26805e0138d0c20215ae741bb53eb","addressRefs":[]},"b70ebff7-355c-46c2-bc36-f08561c5ded1":{"id":"b70ebff7-355c-46c2-bc36-f08561c5ded1","doc_no":"A.1.10.4.1.2.3.1.1.5","title":"Solana SkyLink Freezer Multisig Modification","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":762,"content":"Operational GovOps Soter Labs and Operational Facilitator Endgame Edge can change the signers of the Solana SkyLink Freezer Multisig so long as:\n\n- there are four (4) signers;\n- two (2) signers are required to execute transactions; and\n- an equal number of signers are controlled by Operational GovOps Soter Labs and Operational Facilitator Endgame Edge.","contentHash":"3fa07a76558d444c854fab826198d8b3be0decdbbcebb1ef064fdcda77007507","addressRefs":[]},"36626f77-52da-4bb6-9e32-851420133922":{"id":"36626f77-52da-4bb6-9e32-851420133922","doc_no":"A.1.10.4.1.2.3.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":763,"content":"The documents herein define the rate limits for the Solana SkyLink Bridge.","contentHash":"fd4e36c0526d567fa36ed4bf70f67387e74be9f06c4cf304e6e729326abe4a6b","addressRefs":[]},"7c0eeee4-ce0d-45fe-8eab-1be501e367c0":{"id":"7c0eeee4-ce0d-45fe-8eab-1be501e367c0","doc_no":"A.1.10.4.1.2.3.2.1","title":"Rate Limit Accounting","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":764,"content":"The Solana SkyLink Bridge uses net accounting.\n\nNet accounting means that the rate limit applies to the net amount of tokens transferred from one side of the bridge to the other. For example, if 25,000,000 USDS were transferred from Ethereum Mainnet to Solana and 15,000,000 USDS were transferred from Solana to Ethereum Mainnet, the net amount transferred would be 10,000,000 USDS.","contentHash":"62bdb52f51f81b58df1796a62d5c2b36d13940feb0bd5f16251c75175fb43a3b","addressRefs":[]},"8414b48b-932e-430e-a236-727807fd73ba":{"id":"8414b48b-932e-430e-a236-727807fd73ba","doc_no":"A.1.10.4.1.2.3.2.2","title":"Rate Limit","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":765,"content":"The Solana SkyLink Bridge currently has a rate limit of 5,000,000 USDS per day. This limit should be gradually increased over time as the bridge becomes more mature.\n\nThe rate limit for the Solana SkyLink Bridge may be modified by the Core Facilitator, in consultation with the Core Council Risk Advisor, through the Operational Weekly Cycle. Such modifications can be effected directly via an Executive Vote, without requiring a prior Governance Poll.","contentHash":"724756a6d13c0c97488e73cafa5d41cc224caf89844c3cb3e602fa55ad35eff9","addressRefs":[]},"6d04b42a-9e3c-4490-840a-dbe98388ee78":{"id":"6d04b42a-9e3c-4490-840a-dbe98388ee78","doc_no":"A.1.10.4.1.2.3.3","title":"Validators","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":766,"content":"The documents herein specify the selection and configuration of validators for the Solana SkyLink Bridge.","contentHash":"b788189e0b8c15256af2471d89a3408d172cf80fc43fe69b1b9658fc10572397","addressRefs":[]},"16b49e7d-7360-41bf-ae7a-3c7380972987":{"id":"16b49e7d-7360-41bf-ae7a-3c7380972987","doc_no":"A.1.10.4.1.2.3.3.1","title":"Token Bridge","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":767,"content":"The documents herein specify the selection and configuration of validators for the Token Bridge component of the Solana SkyLink Bridge.","contentHash":"329c730401a850e41e43aa35b68d370fb65ca8b2c8fd99ebd6a153ba974bf3e7","addressRefs":[]},"ffb71c51-44cc-4b9e-ae50-ee6975d7bc31":{"id":"ffb71c51-44cc-4b9e-ae50-ee6975d7bc31","doc_no":"A.1.10.4.1.2.3.3.1.1","title":"Validators","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":768,"content":"The validators for the Token Bridge are LayerZero and Nethermind.","contentHash":"317771453a28629cb0f0f59d9ef193f8fbffcf7c3260a9d568b2658de15dc762","addressRefs":[]},"30a6d20d-fd23-4fa1-96a6-494b044c023e":{"id":"30a6d20d-fd23-4fa1-96a6-494b044c023e","doc_no":"A.1.10.4.1.2.3.3.1.2","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":769,"content":"The quorum requirement for the Token Bridge is 2/2.","contentHash":"2653c5ef77e0d04cb33b3b5e398e7b81e14aa187c0ba5eaf5fce14ceea7940de","addressRefs":[]},"07d43b8c-1230-4de9-959b-8593d69e922a":{"id":"07d43b8c-1230-4de9-959b-8593d69e922a","doc_no":"A.1.10.4.1.2.3.3.2","title":"Governance Bridge","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":770,"content":"The documents herein specify the selection and configuration of validators for the Governance Bridge component of the Solana SkyLink Bridge.","contentHash":"b61e08da5ad215680e4b8d23598686ff70be31ef353e6017ded3bce2ffe05769","addressRefs":[]},"0939f4bf-93d2-4d32-859f-ae4cfdff33b4":{"id":"0939f4bf-93d2-4d32-859f-ae4cfdff33b4","doc_no":"A.1.10.4.1.2.3.3.2.1","title":"Validators","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":771,"content":"The validators for the Governance Bridge are LayerZero, Nethermind, Canary, Deutsche Telekom, P2P, Horizen, and Luganodes.","contentHash":"75434bdef95afd5a981e8e8271c4d0fa21f5a04dd111f336a901998730c1210d","addressRefs":[]},"c5850a58-948d-4c19-bf7f-ba2644cd5001":{"id":"c5850a58-948d-4c19-bf7f-ba2644cd5001","doc_no":"A.1.10.4.1.2.3.3.2.2","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"56593663-55e5-45d5-8682-5eede11aa14a","order":772,"content":"The quorum requirement for the Governance Bridge is 4/7.","contentHash":"8833eacdae9fbafa85aec20c50dcc83c7315d0fc79844948e0072bb103d99148","addressRefs":[]},"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b":{"id":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","doc_no":"A.1.10.4.1.3","title":"Avalanche SkyLink Bridge","type":"Core","depth":5,"parentId":"bd68f60c-f2dc-4c0e-9209-ba5aa20b6f2f","order":773,"content":"Sky uses a SkyLink bridge to securely move assets between Ethereum Mainnet and Avalanche C-Chain (\"Avalanche\"), as well as to provide governance controls for Sky-issued tokens on Avalanche.","contentHash":"566d63964fc81f59e220def393d0f99567950ba8ff73034da9dceb2385511675","addressRefs":[]},"b71e1dec-357c-4009-a11d-e236667e4086":{"id":"b71e1dec-357c-4009-a11d-e236667e4086","doc_no":"A.1.10.4.1.3.1","title":"Introduction","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":774,"content":"The Avalanche SkyLink Bridge consists of a Token Bridge that allows bridging USDS and sUSDS between Ethereum Mainnet and Avalanche, as well as a Governance Bridge that allows exercising governance control for Sky-issued tokens on Avalanche.","contentHash":"35be3baafc5ff401f0de643f5562a3ffef7042df86d9376a24d94240b8e505dd","addressRefs":[]},"1c0d2cf1-dc44-4b7f-b709-61fcc5c1612c":{"id":"1c0d2cf1-dc44-4b7f-b709-61fcc5c1612c","doc_no":"A.1.10.4.1.3.2","title":"Deployment","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":775,"content":"The Avalanche SkyLink Bridge will be deployed in the April 9, 2026 Executive Vote. The timing may be modified by the Core Facilitator in consultation with relevant Ecosystem Actors.","contentHash":"08b26d034dbfe1c039da0e2d77ab8e0152adae8e463452d9f1310218bbd207c0","addressRefs":[]},"413852e0-23b8-4630-a8a1-de0d9018c482":{"id":"413852e0-23b8-4630-a8a1-de0d9018c482","doc_no":"A.1.10.4.1.3.3","title":"Security Parameters","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":776,"content":"The documents herein define the security parameters of the Avalanche SkyLink Bridge.","contentHash":"ae6e7336357899582b5c19f79c3be895313493fa202706492c99486345a5c94f","addressRefs":[]},"199661f2-b3d9-4308-a5d9-9ed15880b00d":{"id":"199661f2-b3d9-4308-a5d9-9ed15880b00d","doc_no":"A.1.10.4.1.3.3.1","title":"Freezer Multisigs","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":777,"content":"The Avalanche SkyLink Bridge can be frozen from Ethereum Mainnet by the Ethereum SkyLink Freezer Multisig as specified in [A.1.10.4.1.1 - Ethereum SkyLink Freezer Multisig](21fa6749-6209-4280-9b5f-b2a73d400421). The document herein defines the Avalanche-side freezer multisig.","contentHash":"17c2942d6d33dbf76e44cdac9d322aebac64c5cf2648698dc2e4d3b9e04c5ca8","addressRefs":[]},"0b1162f6-6a30-4a30-b693-68e077093e7c":{"id":"0b1162f6-6a30-4a30-b693-68e077093e7c","doc_no":"A.1.10.4.1.3.3.1.1","title":"Avalanche SkyLink Freezer Multisig","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":778,"content":"The Avalanche SkyLink Freezer Multisig has the ability to freeze the Avalanche SkyLink Bridge from Avalanche.","contentHash":"5d8c2d9928b5ac6b7c959987903bdc3770c36866a2fcc304dffe3bd65718907b","addressRefs":[]},"3f9645b2-ae99-4c6a-a49a-dfe39ead218c":{"id":"3f9645b2-ae99-4c6a-a49a-dfe39ead218c","doc_no":"A.1.10.4.1.3.3.1.1.1","title":"Avalanche SkyLink Freezer Multisig Address","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":779,"content":"The address of the Avalanche SkyLink Freezer Multisig on Avalanche is `0x4deb1B5372dd3271691A9E80bCBfd98F5aa27f30`.","contentHash":"6130025e64b3b3a82fa0d3fe6918811b69f1eca3f49695f4581177e1e5fe7fac","addressRefs":["0x4deb1b5372dd3271691a9e80bcbfd98f5aa27f30"]},"542e7e15-da27-488b-a192-baaa4ec1a9b9":{"id":"542e7e15-da27-488b-a192-baaa4ec1a9b9","doc_no":"A.1.10.4.1.3.3.1.1.2","title":"Avalanche SkyLink Freezer Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":780,"content":"The Avalanche SkyLink Freezer Multisig has a 2/5 signing requirement.","contentHash":"4ca618ab2e20cb379bff45e780ccee236b7559bd79078c90212202b0d800a854","addressRefs":[]},"22d693e8-4dd9-4673-ba8a-a372069cee43":{"id":"22d693e8-4dd9-4673-ba8a-a372069cee43","doc_no":"A.1.10.4.1.3.3.1.1.3","title":"Avalanche SkyLink Freezer Multisig Signers","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":781,"content":"The signers of the Avalanche SkyLink Freezer Multisig are two (2) addresses controlled by Operational GovOps Soter Labs, two (2) addresses controlled by Operational Facilitator Endgame Edge, and one (1) address controlled by Prime Agent Grove.","contentHash":"e1c41fea188ac51af18c4f2cc9f3d4f334a239a31e611ab26f23655a12930c60","addressRefs":[]},"8596233b-db6e-4787-b601-32d4f5f0393f":{"id":"8596233b-db6e-4787-b601-32d4f5f0393f","doc_no":"A.1.10.4.1.3.3.1.1.4","title":"Avalanche SkyLink Freezer Multisig Usage Standards","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":782,"content":"The Avalanche SkyLink Freezer Multisig can only be used in urgent or emergency situations (e.g., potential code exploits). Such situations are characterized by the fact that 1) they have the potential to harm the Sky Ecosystem or its users; and 2) the preparation time required for an Executive Vote would leave the ecosystem vulnerable to harm (e.g., an exploit).\n\nThe multisig should be used to prevent technical vulnerabilities; prevent unwanted functionality of the smart contracts or corresponding parts of the system (e.g., price oracles); or prevent unwanted usage of the smart contracts or corresponding parts of the system which deviates from intended behavior.\n\nThe Core Council must ensure that use of the multisig is generally aligned and specifically accords with these requirements.","contentHash":"fad01bc8853bd303d0af22d3187f0037b050fcc56fd7f910c24cbdd06646854f","addressRefs":[]},"8514341b-bbce-4e6e-a9c4-e41519cac67c":{"id":"8514341b-bbce-4e6e-a9c4-e41519cac67c","doc_no":"A.1.10.4.1.3.3.1.1.5","title":"Avalanche SkyLink Freezer Multisig Modification","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":783,"content":"Operational GovOps Soter Labs, Operational Facilitator Endgame Edge, and Prime Agent Grove can change the signers of the Avalanche SkyLink Freezer Multisig so long as:\n\n- there are five (5) signers;\n- two (2) signers are required to execute transactions;\n- two (2) signers are controlled by Operational GovOps Soter Labs;\n- two (2) signers are controlled by Operational Facilitator Endgame Edge; and\n- one (1) signer is controlled by Prime Agent Grove.","contentHash":"f975e408477af3c9e061b6035151dc45aa897a35758ae329d2668e155dc3f811","addressRefs":[]},"2fb5eb69-2f10-4173-8d26-36890db8fe83":{"id":"2fb5eb69-2f10-4173-8d26-36890db8fe83","doc_no":"A.1.10.4.1.3.3.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":784,"content":"The documents herein define the rate limits for the Avalanche SkyLink Bridge.","contentHash":"9ce69df501a056b1b0ea7755cb2d8210edfaacf9d1887b39f8c4a99ae0309ce3","addressRefs":[]},"49041287-546d-48bb-b85d-8ec48960d2f8":{"id":"49041287-546d-48bb-b85d-8ec48960d2f8","doc_no":"A.1.10.4.1.3.3.2.1","title":"Rate Limit Accounting","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":785,"content":"The Avalanche SkyLink Bridge uses net accounting.\n\nNet accounting means that the rate limit applies to the net amount of tokens transferred from one side of the bridge to the other. For example, if 5,000,000 USDS were transferred from Ethereum Mainnet to Avalanche and 3,000,000 USDS were transferred from Avalanche to Ethereum Mainnet, the net amount transferred would be 2,000,000 USDS.","contentHash":"9fa45093af2b265c0f15af9760abb5fe18d22081b9380fc54df0c6bd6fca1542","addressRefs":[]},"6d550b28-1299-456f-879b-9f66dd8085a6":{"id":"6d550b28-1299-456f-879b-9f66dd8085a6","doc_no":"A.1.10.4.1.3.3.2.2","title":"USDS Rate Limit","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":786,"content":"The Avalanche SkyLink Bridge currently has a USDS rate limit of 0 USDS per day.\n\nThe rate limit for the Avalanche SkyLink Bridge may be modified by the Core Facilitator, in consultation with the Core Council Risk Advisor, through the Operational Weekly Cycle. Such modifications can be effected directly via an Executive Vote, without requiring a prior Governance Poll.","contentHash":"3f2793f848929ad84e60394a68fca2c8aac263d984db8a58c90890ea9a3378e2","addressRefs":[]},"186450c7-25a8-4a4e-a945-3366e9d65b13":{"id":"186450c7-25a8-4a4e-a945-3366e9d65b13","doc_no":"A.1.10.4.1.3.3.2.3","title":"sUSDS Rate Limit","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":787,"content":"The Avalanche SkyLink Bridge currently has no rate limit for sUSDS. A rate limit for sUSDS may be set or subsequently modified by the Core Facilitator, in consultation with the Core Council Risk Advisor, through the Operational Weekly Cycle. Such changes can be effected directly via an Executive Vote, without requiring a prior Governance Poll.","contentHash":"9f33de7c9281472d1c83f90bfe3ea15655aa2db5f3026842446ede132a28ad67","addressRefs":[]},"483d9616-cde4-490a-9291-766733b83de4":{"id":"483d9616-cde4-490a-9291-766733b83de4","doc_no":"A.1.10.4.1.3.3.3","title":"Validators","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":788,"content":"The documents herein specify the selection and configuration of validators for the Avalanche SkyLink Bridge.","contentHash":"403188c59d7440ab74db27968775ee61c05a375477d714dc6705147ffb4fb45a","addressRefs":[]},"3a3bcbb1-0989-4d62-80c3-7a71de0b022a":{"id":"3a3bcbb1-0989-4d62-80c3-7a71de0b022a","doc_no":"A.1.10.4.1.3.3.3.1","title":"Token Bridge","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":789,"content":"The documents herein specify the selection and configuration of validators for the Token Bridge component of the Avalanche SkyLink Bridge.","contentHash":"0eddd36d5da4fadd98c380138557091a7a25e992afcf6ecabdff30eb926afdea","addressRefs":[]},"a9f87e05-2b53-40e7-b477-ec55136ee95d":{"id":"a9f87e05-2b53-40e7-b477-ec55136ee95d","doc_no":"A.1.10.4.1.3.3.3.1.1","title":"Validators","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":790,"content":"The validators for the Token Bridge are LayerZero and Nethermind.","contentHash":"317771453a28629cb0f0f59d9ef193f8fbffcf7c3260a9d568b2658de15dc762","addressRefs":[]},"2c6b25de-b2ed-4874-9ab3-2a379cbaf601":{"id":"2c6b25de-b2ed-4874-9ab3-2a379cbaf601","doc_no":"A.1.10.4.1.3.3.3.1.2","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":791,"content":"The quorum requirement for the Token Bridge is 2/2.","contentHash":"2653c5ef77e0d04cb33b3b5e398e7b81e14aa187c0ba5eaf5fce14ceea7940de","addressRefs":[]},"6a24fd94-9915-468d-a2a4-14f222ff5980":{"id":"6a24fd94-9915-468d-a2a4-14f222ff5980","doc_no":"A.1.10.4.1.3.3.3.2","title":"Governance Bridge","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":792,"content":"The documents herein specify the selection and configuration of validators for the Governance Bridge component of the Avalanche SkyLink Bridge.","contentHash":"4e3aacf302835419b018f38d4558456d7a82ba103d58c6ff046fcd3c3a109c46","addressRefs":[]},"ae25a37a-9699-4811-93ab-88379227578e":{"id":"ae25a37a-9699-4811-93ab-88379227578e","doc_no":"A.1.10.4.1.3.3.3.2.1","title":"Validators","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":793,"content":"The validators for the Governance Bridge are Horizen, LayerZero, Nethermind, Deutsche Telekom, Canary, Luganodes, and P2P.","contentHash":"7bc0e5a0e4a067b57c9f4a7b39a2b2ce4195f0b8b8ae22c50acd62349ad18abb","addressRefs":[]},"d1a78b46-a227-4551-9bcd-2a5a6e5d3e56":{"id":"d1a78b46-a227-4551-9bcd-2a5a6e5d3e56","doc_no":"A.1.10.4.1.3.3.3.2.2","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"6b0eaa0d-d2d3-44b6-b2d4-9344efbf453b","order":794,"content":"The quorum requirement for the Governance Bridge is 4/7.","contentHash":"8833eacdae9fbafa85aec20c50dcc83c7315d0fc79844948e0072bb103d99148","addressRefs":[]},"aca54441-3738-4aee-b7a8-f2a4b9ef02fa":{"id":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","doc_no":"A.1.10.4.1.4","title":"Plasma SkyLink Bridge","type":"Core","depth":5,"parentId":"bd68f60c-f2dc-4c0e-9209-ba5aa20b6f2f","order":795,"content":"Sky uses a SkyLink bridge to securely move assets between Ethereum Mainnet and Plasma, as well as to provide governance controls for Sky-issued tokens on Plasma.","contentHash":"ba1fd325f19d7d3e38baf0484ab0671dc9d2e503a8200af774c50ebfff725ba7","addressRefs":[]},"b8241202-6305-4485-b938-e5e8fe6c2e50":{"id":"b8241202-6305-4485-b938-e5e8fe6c2e50","doc_no":"A.1.10.4.1.4.1","title":"Introduction","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":796,"content":"The Plasma SkyLink Bridge consists of a Token Bridge that allows bridging USDS and sUSDS between Ethereum Mainnet and Plasma, as well as a Governance Bridge that allows exercising governance control for Sky-issued tokens on Plasma.","contentHash":"afaf992f5719001f5194ec3bc333ffa17d1dad084559817d844db7079138cba2","addressRefs":[]},"44af823e-841b-4b2e-a4dd-363925a8bf7b":{"id":"44af823e-841b-4b2e-a4dd-363925a8bf7b","doc_no":"A.1.10.4.1.4.2","title":"Deployment","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":797,"content":"The Plasma SkyLink Bridge will be deployed in a future Executive Vote. The timing will be determined by the Core Facilitator in consultation with relevant Ecosystem Actors.","contentHash":"21dbea725a94a74126f3ca6310aeb8d8241770d997a7a7d421a066d018a2f281","addressRefs":[]},"0b2674c5-f9e2-4592-9358-c35e06ed5214":{"id":"0b2674c5-f9e2-4592-9358-c35e06ed5214","doc_no":"A.1.10.4.1.4.3","title":"Security Parameters","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":798,"content":"The documents herein define the security parameters of the Plasma SkyLink Bridge.","contentHash":"36822e22a94ba2d108a6336fc090abfa20a296d53091e817af3545caff364221","addressRefs":[]},"022129be-e83f-417f-a0b6-4a066fc66d62":{"id":"022129be-e83f-417f-a0b6-4a066fc66d62","doc_no":"A.1.10.4.1.4.3.1","title":"Freezer Multisigs","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":799,"content":"The Plasma SkyLink Bridge can be frozen from Ethereum Mainnet by the Ethereum SkyLink Freezer Multisig as specified in [A.1.10.4.1.1 - Ethereum SkyLink Freezer Multisig](21fa6749-6209-4280-9b5f-b2a73d400421). The document herein defines the Plasma-side freezer multisig.","contentHash":"f4d37d66ba51c9b74926929865fed8469714f406dded082d89090b86b148dce9","addressRefs":[]},"f833edaa-9f5f-4445-afcb-a9cfc3620b10":{"id":"f833edaa-9f5f-4445-afcb-a9cfc3620b10","doc_no":"A.1.10.4.1.4.3.1.1","title":"Plasma SkyLink Freezer Multisig","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":800,"content":"The Plasma SkyLink Freezer Multisig has the ability to freeze the Plasma SkyLink Bridge from Plasma.","contentHash":"fa254192bdc6b219fd8cf5ce7511374dc06c69be9ffb2b16facc1d131537f5c0","addressRefs":[]},"88cb9621-d10f-49b6-85e6-2c822bb5beda":{"id":"88cb9621-d10f-49b6-85e6-2c822bb5beda","doc_no":"A.1.10.4.1.4.3.1.1.1","title":"Plasma SkyLink Freezer Multisig Address","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":801,"content":"The address of the Plasma SkyLink Freezer Multisig on Plasma is `0xB3d26eF66F53C9546d1365F417a85B0Aa69049eE`.","contentHash":"2bf3b09c16b0b37ee844a999b5600c568cfac2df8f57e0f87970acaadc020285","addressRefs":["0xb3d26ef66f53c9546d1365f417a85b0aa69049ee"]},"cb8707d5-ff3f-4312-b8cc-97b3734fa81c":{"id":"cb8707d5-ff3f-4312-b8cc-97b3734fa81c","doc_no":"A.1.10.4.1.4.3.1.1.2","title":"Plasma SkyLink Freezer Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":802,"content":"The Plasma SkyLink Freezer Multisig has a 2/5 signing requirement.","contentHash":"ad9a55cf5e7b4fb91b32da7347ded1818defd32a4778791acc74bc208f64b3fd","addressRefs":[]},"f9cd34cb-802e-4322-9307-0e72bb4a4f66":{"id":"f9cd34cb-802e-4322-9307-0e72bb4a4f66","doc_no":"A.1.10.4.1.4.3.1.1.3","title":"Plasma SkyLink Freezer Multisig Signers","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":803,"content":"The signers of the Plasma SkyLink Freezer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs, one (1) address controlled by Operational Facilitator Redline Facilitation Group, and one (1) address controlled by Launch Agent 6.","contentHash":"fe7a53bc4de845f011bc11e09d12d8a0ee1ef7dc454153a001c291b6ff5d3b6f","addressRefs":[]},"5b79ed95-6a02-47dc-8ac1-9ba55b513e32":{"id":"5b79ed95-6a02-47dc-8ac1-9ba55b513e32","doc_no":"A.1.10.4.1.4.3.1.1.4","title":"Plasma SkyLink Freezer Multisig Usage Standards","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":804,"content":"The Plasma SkyLink Freezer Multisig can only be used in urgent or emergency situations (e.g., potential code exploits). Such situations are characterized by the fact that 1) they have the potential to harm the Sky Ecosystem or its users; and 2) the preparation time required for an Executive Vote would leave the ecosystem vulnerable to harm (e.g., an exploit).\n\nThe multisig should be used to prevent technical vulnerabilities; prevent unwanted functionality of the smart contracts or corresponding parts of the system (e.g., price oracles); or prevent unwanted usage of the smart contracts or corresponding parts of the system which deviates from intended behavior.\n\nThe Core Council must ensure that use of the multisig is generally aligned and specifically accords with these requirements.","contentHash":"b620dbdbd154e2cc27164eaa575338f0b3b9da2d1ed5fc50adbe18933bb607c8","addressRefs":[]},"a8be9d0a-629b-4a2c-a2f2-6b2b7f965b16":{"id":"a8be9d0a-629b-4a2c-a2f2-6b2b7f965b16","doc_no":"A.1.10.4.1.4.3.1.1.5","title":"Plasma SkyLink Freezer Multisig Modification","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":805,"content":"Operational GovOps Soter Labs, Operational Facilitator Redline Facilitation Group, and Launch Agent 6 can change the signers of the Plasma SkyLink Freezer Multisig so long as:\n\n- there are five (5) signers;\n- two (2) signers are required to execute transactions;\n- three (3) signers are controlled by Operational GovOps Soter Labs;\n- one (1) signer is controlled by Operational Facilitator Redline Facilitation Group; and\n- one (1) signer is controlled by Launch Agent 6.","contentHash":"356a227f9f5a4766b2f80ea413fe7774f5e7792ef2722d6b11b5da18e1c9bdc7","addressRefs":[]},"cc4b7dac-9754-473a-ae3a-bdb0de0a2d88":{"id":"cc4b7dac-9754-473a-ae3a-bdb0de0a2d88","doc_no":"A.1.10.4.1.4.3.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":806,"content":"The documents herein define the rate limits for the Plasma SkyLink Bridge.","contentHash":"9a5d57ba3df6823c13e9f810050e2d44f99213788ac10d16f8dd23a068776e7c","addressRefs":[]},"7b6ca79a-66f8-40c8-a76b-4497ddc6518f":{"id":"7b6ca79a-66f8-40c8-a76b-4497ddc6518f","doc_no":"A.1.10.4.1.4.3.2.1","title":"Rate Limit Accounting","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":807,"content":"The Plasma SkyLink Bridge uses net accounting.\n\nNet accounting means that the rate limit applies to the net amount of tokens transferred from one side of the bridge to the other. For example, if 5,000,000 USDS were transferred from Ethereum Mainnet to Plasma and 3,000,000 USDS were transferred from Plasma to Ethereum Mainnet, the net amount transferred would be 2,000,000 USDS.","contentHash":"f80ba7a7abed93470618e0c95d82ae880abc4ab2c1c1c6348080b312d2faefcf","addressRefs":[]},"527a2195-dcfd-4bd2-b20c-d47edf1797b9":{"id":"527a2195-dcfd-4bd2-b20c-d47edf1797b9","doc_no":"A.1.10.4.1.4.3.2.2","title":"USDS Rate Limit","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":808,"content":"The Plasma SkyLink Bridge currently has a USDS rate limit of 5,000,000 USDS per day.\n\nThe rate limit for the Plasma SkyLink Bridge may be modified by the Core Facilitator, in consultation with the Core Council Risk Advisor, through the Operational Weekly Cycle. Such modifications can be effected directly via an Executive Vote, without requiring a prior Governance Poll.","contentHash":"8db6a82c359a584f452ae5667da0773a1d43e4378c6481c34a0ccd1b46d7ca39","addressRefs":[]},"5c722eb6-22fd-4be4-bb19-4b40159ca007":{"id":"5c722eb6-22fd-4be4-bb19-4b40159ca007","doc_no":"A.1.10.4.1.4.3.2.3","title":"sUSDS Rate Limit","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":809,"content":"The Plasma SkyLink Bridge currently has no rate limit for sUSDS. A rate limit for sUSDS may be set or subsequently modified by the Core Facilitator, in consultation with the Core Council Risk Advisor, through the Operational Weekly Cycle. Such changes can be effected directly via an Executive Vote, without requiring a prior Governance Poll.","contentHash":"ab0b133344662edd6c6cf57542d331af71d644a445a89852f0839c751fdd5bf9","addressRefs":[]},"84e98241-3071-49d4-9a9d-9006acaef72e":{"id":"84e98241-3071-49d4-9a9d-9006acaef72e","doc_no":"A.1.10.4.1.4.3.3","title":"Validators","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":810,"content":"The documents herein specify the selection and configuration of validators for the Plasma SkyLink Bridge.","contentHash":"6a1c3a889eed7e0d08ea329883410083a7512e21fea04e28bc53078613d9d419","addressRefs":[]},"658d9408-ecdd-4279-8f88-d1ed9e6bcd45":{"id":"658d9408-ecdd-4279-8f88-d1ed9e6bcd45","doc_no":"A.1.10.4.1.4.3.3.1","title":"Token Bridge","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":811,"content":"The documents herein specify the selection and configuration of validators for the Token Bridge component of the Plasma SkyLink Bridge.","contentHash":"264a2c29bfe81f21d1930d743bd017af41a52cec35066cdf4e14fa5158ca8069","addressRefs":[]},"07c605cc-9023-457d-aa88-ae9950063f4b":{"id":"07c605cc-9023-457d-aa88-ae9950063f4b","doc_no":"A.1.10.4.1.4.3.3.1.1","title":"Validators","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":812,"content":"The validators for the Token Bridge are LayerZero and Nethermind.","contentHash":"317771453a28629cb0f0f59d9ef193f8fbffcf7c3260a9d568b2658de15dc762","addressRefs":[]},"ccdc870c-b61c-4c80-9958-a30f74d2f7af":{"id":"ccdc870c-b61c-4c80-9958-a30f74d2f7af","doc_no":"A.1.10.4.1.4.3.3.1.2","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":813,"content":"The quorum requirement for the Token Bridge is 2/2.","contentHash":"2653c5ef77e0d04cb33b3b5e398e7b81e14aa187c0ba5eaf5fce14ceea7940de","addressRefs":[]},"6aea3973-59ed-4f64-ad7f-4d1ad53e4357":{"id":"6aea3973-59ed-4f64-ad7f-4d1ad53e4357","doc_no":"A.1.10.4.1.4.3.3.2","title":"Governance Bridge","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":814,"content":"The documents herein specify the selection and configuration of validators for the Governance Bridge component of the Plasma SkyLink Bridge.","contentHash":"d5cef623abb7ef4766aac2fa02e9f7699822ab98df2e16b4566763f4cfd90151","addressRefs":[]},"b314c96f-45c9-4726-967e-66153c0a8a0c":{"id":"b314c96f-45c9-4726-967e-66153c0a8a0c","doc_no":"A.1.10.4.1.4.3.3.2.1","title":"Validators","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":815,"content":"The validators for the Governance Bridge are Canary, Deutsche Telekom, Horizen, LayerZero, Luganodes, Nethermind, and P2P.","contentHash":"0717b5a7d49376e79d552d9ca170995b7dae124931e736399fcc692115cce13d","addressRefs":[]},"8b278dd8-e0c5-4f08-97be-dc9cce9f0680":{"id":"8b278dd8-e0c5-4f08-97be-dc9cce9f0680","doc_no":"A.1.10.4.1.4.3.3.2.2","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"aca54441-3738-4aee-b7a8-f2a4b9ef02fa","order":816,"content":"The quorum requirement for the Governance Bridge is 4/7.","contentHash":"8833eacdae9fbafa85aec20c50dcc83c7315d0fc79844948e0072bb103d99148","addressRefs":[]},"fe525e67-1142-4312-bab7-bd9549747f77":{"id":"fe525e67-1142-4312-bab7-bd9549747f77","doc_no":"A.1.10.4.2","title":"Spark Agent","type":"Core","depth":4,"parentId":"19222532-1ce1-4306-8129-ea95a982c247","order":817,"content":"Spark is one of the initial Agents focused on developing crypto on-chain lending engines. Spark will be governed by Spark token holders pursuant to the conditions specified in the Atlas.\n\nSparkLend Protocol is the first such on-chain lending engine, structured as a Conduit in the upcoming Allocation System. SparkLend will be adopted by Spark once Agents are launched.\n\nThe subdocuments below outline the governance security procedures specifically in development for the SparkLend Protocol.","contentHash":"d19cb871c158d8839a68be53c864a71390a3370d7151492780ded8cd3146c2e4","addressRefs":[]},"df709091-a82b-4bd6-ab05-42c56a49d326":{"id":"df709091-a82b-4bd6-ab05-42c56a49d326","doc_no":"A.1.10.4.2.1","title":"Multisig Freeze Of SparkLend","type":"Core","depth":5,"parentId":"fe525e67-1142-4312-bab7-bd9549747f77","order":818,"content":"In addition to the SparkLend Freezer Mom contract defined in [A.1.10.3.2.7 - SparkLend Freezer Mom Exception](645443f1-9004-48d3-868c-139b608bb1f9), an external SparkLend Security Access Multisig has been established that allows for pausing and/or freezing SparkLend markets. The SparkLend Security Access Multisig can enable or disable the SparkLend Freezer Mom contract without the need for inclusion in a Spell through the standard Executive Vote process.\n\nEach action executed by the multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum. Such actions include activating or disabling the pause or freeze function.","contentHash":"55499866df63bde67b85b6b72c08c19dee0b03c0d42b1ac411d4c0d805c4adeb","addressRefs":[]},"95dd3a55-eff4-4d5c-971d-c9bb8a145d36":{"id":"95dd3a55-eff4-4d5c-971d-c9bb8a145d36","doc_no":"A.1.10.4.2.1.1","title":"SparkLend Multisig Usage Standards","type":"Core","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":819,"content":"The SparkLend Security Access Multisig can only be used in urgent or emergency situations (e.g., potential code exploits). Such situations are characterized by the fact that 1) they have the potential to harm the Sky Ecosystem or SparkLend users; and 2) the preparation time required for an Executive Vote would leave the ecosystem vulnerable to harm (e.g., an exploit).\n\nThe multisig should be used to prevent technical vulnerabilities; prevent unwanted functionality of the smart contracts or corresponding parts of the system (e.g., price oracles); or prevent unwanted usage of the smart contracts or corresponding parts of the system which deviates from intended behavior.\n\nThe Multisig can also be used in cases where a vulnerability or exploit is discovered in other protocols using the same codebase as SparkLend, and a timely action can prevent or mitigate the damage.\n\nThe Core Council must ensure that use of the multisig is generally aligned and specifically accords with the requirements defined herein.","contentHash":"7b6057847639c782f8f886271c1eeaa764cde3da3f7ab507f18fe1ad9c93df6c","addressRefs":[]},"d373ebcb-c746-4388-885c-d1bba4edbf05":{"id":"d373ebcb-c746-4388-885c-d1bba4edbf05","doc_no":"A.1.10.4.2.1.1.0.3.1","title":"Same Codebase - Element Annotation","type":"Annotation","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":820,"content":"The element \"same codebase\" refers to the fact that SparkLend is based on the Aave codebase. Vulnerabilities or exploits discovered within Aave, or any other protocol utilizing the Aave codebase, could potentially be replicated and affect SparkLend.","contentHash":"be2784910e39c39aab767c9bafcbdab45c565e30cf4b912650ea438913178b30","addressRefs":[]},"71898c9e-1bb5-43fb-95bb-e9aeec2bdd0c":{"id":"71898c9e-1bb5-43fb-95bb-e9aeec2bdd0c","doc_no":"A.1.10.4.2.1.1.0.4.1","title":"Facilitators Must Exercise Due Caution In Reviewing Use Of Multisig","type":"Action Tenet","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":821,"content":"The list of instances justifying use of the multisig in the Target Document is not intended to be exhaustive. However, the Core Council must exercise due caution in reviewing and validating use of the multisig in edge cases, i.e., use of the multisig that falls outside of the examples provided in the Target Document. In such \"edge cases,\" the Core Council must ensure that a postmortem is publicly published on the Sky Forum which justifies the use of the multisig. The Core Council should also consider proposing an edit to the Target Document so that the edge case is explicitly included in the examples provided in the Target Document.","contentHash":"b172cdbb2c45df66376b9b9121d0bdedc89f9b1803822b3d2f351bbe8e692af6","addressRefs":[]},"0c71e677-9acb-4f89-bb25-1726e8dac076":{"id":"0c71e677-9acb-4f89-bb25-1726e8dac076","doc_no":"A.1.10.4.2.1.2","title":"SparkLend Multisig Number Of Signers","type":"Core","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":822,"content":"The SparkLend Security Access Multisig currently has a 3/5 signing requirement.","contentHash":"bbd11370605d0b4d0c63a8bd947e2757d9179f4ac8ffc05c7548c0ead7fba161","addressRefs":[]},"526a954b-5939-47d0-aacf-fdc190f71d5e":{"id":"526a954b-5939-47d0-aacf-fdc190f71d5e","doc_no":"A.1.10.4.2.1.3","title":"SparkLend Multisig Current Signers","type":"Core","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":823,"content":"The SparkLend Security Access Multisig currently has the following signers:\n\n- VoteWizard\n- LDR\n- Hexonaut\n- MonetSupply\n- LucasManuel","contentHash":"a2afee352f8ec2e0aa7549c4d9080879754cd9db94c2da17d142f08edccf26a5","addressRefs":[]},"d8e0d76b-dd1f-4f3e-9a8b-7724ce4fc880":{"id":"d8e0d76b-dd1f-4f3e-9a8b-7724ce4fc880","doc_no":"A.1.10.4.2.1.4","title":"SparkLend Multisig Signer Modifications","type":"Core","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":824,"content":"Modification of the signers of the SparkLend Security Access Multisig must be approved through a Governance Poll; no Executive Vote is required.\n\nThe only exceptions to this are if: 1) a signer self-reports a loss of access to their private key due to any reason; or 2) a signer explicitly expresses their wish to be removed as a signer. In both cases, the signer is required to communicate the loss of access to their private key, or the wish to be removed as a signer, in the form of a public Sky Forum post. The specific signer should be replaced as soon as possible, which does not require a Governance Poll.\n\nAny changes to the multisig signers that do not fall within the two exceptions listed above, or that have not been ratified by Sky Governance, should be questioned immediately and treated as malicious. The Core Facilitator should consider preparing an expedited Executive Vote so that Sky Governance can vote on removing external security access from the multisig.","contentHash":"83f42adaf5c3952191638891283a816fbaed3d856897c97dd03161713de9ea2c","addressRefs":[]},"13ad3a13-d446-40db-9db6-18ab34fe049a":{"id":"13ad3a13-d446-40db-9db6-18ab34fe049a","doc_no":"A.1.10.4.2.1.5","title":"SparkLend Multisig Address","type":"Core","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":825,"content":"The current whitelisted SparkLend Security Access Multisig address is:\n\n`0x44efFc473e81632B12486866AA1678edbb7BEeC3`","contentHash":"b8259fe3bc616255573d26e38aecea4f403fb3db8228f52e881d512d24f294fb","addressRefs":["0x44effc473e81632b12486866aa1678edbb7beec3"]},"1844a8bf-ad90-413c-9278-129379dc17bb":{"id":"1844a8bf-ad90-413c-9278-129379dc17bb","doc_no":"A.1.10.4.2.1.0.3.1","title":"Multisig - Element Annotation","type":"Annotation","depth":6,"parentId":"df709091-a82b-4bd6-ab05-42c56a49d326","order":826,"content":"The element \"multisig\" refers to a blockchain wallet implemented as a smart contract and requiring multiple signers to approve transactions.\n\nA blockchain wallet has an address associated with it and can hold cryptocurrency assets as well as interact with smart contracts. The address of a blockchain wallet may be granted privileged access to interact with other smart contracts, allowing the owner of the wallet to perform functions not available to other users.\n\nA multisig allows the control of a wallet to be shared among the signers based on specified parameters, including the number of signers and how many signers are needed to approve each transaction. This allows a wallet to be more safely managed: for instance, a multisig prevents the possibility that a single signer could take malicious action and allows the signers to be updated if necessary.","contentHash":"eb5393cc61b113c17e852ef2f199bc0f311a220384230d7faca485cb678db90d","addressRefs":[]},"b8266c11-3a84-4bbe-abe2-de9474f74ffd":{"id":"b8266c11-3a84-4bbe-abe2-de9474f74ffd","doc_no":"A.1.10.5","title":"Emergency Spells","type":"Section","depth":3,"parentId":"de0cc370-de9c-48a4-b10e-91782df7abcd","order":827,"content":"The subdocuments herein govern the management of emergencies whose resolution requires an Executive Vote.","contentHash":"00b1bda7112001e85681b3f83536ec4625e429e03e35bce90bc004d786bc67d6","addressRefs":[]},"b28a2439-3d64-4e64-aaa1-d7a58090d3a0":{"id":"b28a2439-3d64-4e64-aaa1-d7a58090d3a0","doc_no":"A.1.10.5.1","title":"Emergency Spells Definition","type":"Core","depth":4,"parentId":"b8266c11-3a84-4bbe-abe2-de9474f74ffd","order":828,"content":"Emergency Spells are expedited ad hoc Spells that, while typically compliant with all customary quality-assurance processes, do not adhere to the normal Spell cadence. Emergency Spells solve the root issue of an emergency / urgent situation impacting the Protocol and are used when a rapid response time is needed. The Core Facilitator and Core GovOps are responsible for managing the use of Emergency Spells pursuant to [A.1.9.1.4 - Emergency Response Roles And Responsibilities](c9c32f24-cf6c-43d5-ac4c-bd2b4d02032b) and [A.1.9.1.5.4.1 - Known And Uncontentious Remedies](3f5f79fa-698c-42db-a941-ead5a5d0aa48).","contentHash":"77550c4603bbbc475514373c995aff9d0129ce1bf2923a0d031d813dc6c84540","addressRefs":[]},"5e40b575-4eda-4a6b-ae63-15a046cfb35d":{"id":"5e40b575-4eda-4a6b-ae63-15a046cfb35d","doc_no":"A.1.10.5.2","title":"Standby Spells","type":"Core","depth":4,"parentId":"b8266c11-3a84-4bbe-abe2-de9474f74ffd","order":829,"content":"A subset of Emergency Spells is Standby Spells.\n\nStandby Spells allow Sky Governance to bypass the GSM Pause Delay and directly perform crucial actions such as stopping an oracle, setting a debt ceiling to zero, disabling a D3M integration, or stopping liquidations for a collateral. Standby Spells or the factory contracts used to deploy them are reusable, meaning they can be executed several times if needed, or voted on again on a later date to be executed again.\n\nThe subdocuments herein specify the authorized use of Standby Spells.","contentHash":"a5609d857027ddc60588aa43a1fcf00cea14c4c23506da0142664d3bcbdf7292","addressRefs":[]},"022b27ab-220d-4411-bfc8-5d09681ecc48":{"id":"022b27ab-220d-4411-bfc8-5d09681ecc48","doc_no":"A.1.10.5.2.1","title":"Standby Spells Definition","type":"Core","depth":5,"parentId":"5e40b575-4eda-4a6b-ae63-15a046cfb35d","order":830,"content":"Sky Protocol uses circuit-breakers to mitigate undesired scenarios, which circuit-breakers are called MOM contracts. MOM contracts must first be triggered through a Spell, after which they bypass the GSM Pause Delay and can immediately act on the Protocol. See [A.1.10.3.2 - Exceptions](6781594b-5dff-45ec-89a4-1c9684c4eed8).\n\nIn emergency scenarios, time is a scarce resource. Therefore, Standby Spells are used in validated emergency scenarios to trigger a MOM contract. In an emergency situation, Spell teams can then focus on crafting an ad hoc Emergency Spell to solve the root cause of an issue, if appropriate. Due to Standby Spells, it is no longer necessary in an emergency for Spell teams to spend time crafting and reviewing a Spell whose sole purpose is to trigger a mitigation of the issue, i.e., the MOM contract.\n\nStandby Spells open new attack vectors that must be mitigated pursuant to [A.1.10.5.2.3.3 - ADs' Role In Standby Spells](53cea69b-45cc-4f9c-b863-9bf259e37deb).","contentHash":"3ad3b4ceb83072f26bbd9d57c5b0c4f8f7ef92f874721092e43915a65e7e49b6","addressRefs":[]},"646ed712-24c6-4b77-9d2d-2599be50f325":{"id":"646ed712-24c6-4b77-9d2d-2599be50f325","doc_no":"A.1.10.5.2.1.1","title":"Standby Spell Incorporation Into New MOM Contracts","type":"Core","depth":6,"parentId":"022b27ab-220d-4411-bfc8-5d09681ecc48","order":831,"content":"Each new MOM contract created must incorporate a Standby Spell or Standby Spell factory, which can be used to create new Standby Spells that can trigger the MOM contract. With a Standby Spell per every MOM contract, the generation of technical debt can be avoided.","contentHash":"29cbac4cb8e115fac8068490a82358616250d999f1b886d2e8377806f9c60ec8","addressRefs":[]},"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba":{"id":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","doc_no":"A.1.10.5.2.2","title":"Available Standby Spells","type":"Core","depth":5,"parentId":"5e40b575-4eda-4a6b-ae63-15a046cfb35d","order":832,"content":"The currently available Standby Spells are defined in the subdocuments herein. The following list of Standby Spells is not exhaustive: that is, the Core Facilitator, in collaboration with the Emergency Response Group and Spell teams, has the discretion to develop and use a Standby Spell that is not listed in the subdocuments below. When that occurs, however, the Core Facilitator must ensure that the new Standby Spell is subsequently added to the subdocuments below.","contentHash":"ac68ae4477c23bd5da6f1a2e704d4b9ac04131abfb19d54633dbeb11a3ff7f95","addressRefs":[]},"8b1f9d33-ed32-4fa9-88b9-19f39c4a4af6":{"id":"8b1f9d33-ed32-4fa9-88b9-19f39c4a4af6","doc_no":"A.1.10.5.2.2.1","title":"Single-Collateral Standby Spells","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":833,"content":"The subdocuments herein define currently available single-collateral Standby Spells. For each instance of use, single-collateral Standby Spell contracts require a transaction to deploy the Standby Spell from a factory.","contentHash":"16d774be5bca3225c09b21401f029a4e0178b794789705f67dff706a8a10a061","addressRefs":[]},"d84fd214-6fba-4a0d-a624-e054968ccacc":{"id":"d84fd214-6fba-4a0d-a624-e054968ccacc","doc_no":"A.1.10.5.2.2.1.1","title":"SingleOsmStopSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":834,"content":"This Standby Spell can be used in an emergency to freeze an OSM for a single collateral. If the oracle price provider fails for any reason, Governance can act before the OSM registers the next price; this allows for the problem to be fixed with no impact on the system.","contentHash":"cc0294ae089e74b99613f7b069ddb6ccd8039b51cb9deea0bc2fe339008b3bc5","addressRefs":[]},"dedab114-26eb-49d3-987c-2ca8e95eeeb4":{"id":"dedab114-26eb-49d3-987c-2ca8e95eeeb4","doc_no":"A.1.10.5.2.2.1.2","title":"SingleDdmDisableSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":835,"content":"This Standby Spell can be used in an emergency to disable a D3M integration. If a D3M partner is experiencing a problem such as a hack, this emergency Spell can be used to prevent abuse. While it cannot recover Dai already injected into the compromised protocol, the Emergency Spell can prevent additional exposure.","contentHash":"ae09a10030e37b3db107c1d7e6c3f9d847babd132b15879f4b6b1305c1a759e9","addressRefs":[]},"7c763597-d1df-48b3-8aed-625f77f517e4":{"id":"7c763597-d1df-48b3-8aed-625f77f517e4","doc_no":"A.1.10.5.2.2.1.3","title":"SingleLitePsmHaltFactory","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":836,"content":"This Standby Spell can be used in an emergency to halt a LitePSM completely.","contentHash":"6c3972064f8febb4414c919990c08d8f61f0cc99813da5e18106e88992435235","addressRefs":[]},"2f9fb16b-b71f-4423-85f5-b366e84e261e":{"id":"2f9fb16b-b71f-4423-85f5-b366e84e261e","doc_no":"A.1.10.5.2.2.2","title":"Grouped Standby Spells","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":837,"content":"The subdocuments herein define currently available grouped Standby Spells. For each instance of use, grouped Standby Spell contracts require a transaction to deploy the Standby Spell from a factory. Unlike single-collateral Standby Spells, a grouped Standby Spell is configured at the time of deployment with a specific list of collaterals it can operate on. This setup enables a single grouped Standby Spell to operate on multiple related collaterals.","contentHash":"2127202262bc2338261f827c261c82fd4a0ad9021bba5098679b179503d0a185","addressRefs":[]},"844d0f55-0f7a-40a8-b2e6-8e5ce72c73b3":{"id":"844d0f55-0f7a-40a8-b2e6-8e5ce72c73b3","doc_no":"A.1.10.5.2.2.2.1","title":"GroupedLineWipeSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":838,"content":"This Standby Spell will perform a Line MOM Wipe (set debt ceiling to zero) for the specified collaterals. It can be used if the specified collaterals fail - for example, if a stablecoin depegs or the protocol that provides the token is hacked. Users will still be able to exit their positions, but no new debt will be allowed to be created for the collaterals.","contentHash":"603a201cc9be628cc483bb9fc4725a6000c8c6d6e38301f9679c4ece622191f7","addressRefs":[]},"d51e41f6-c29d-4476-92c2-ceae38ddca9c":{"id":"d51e41f6-c29d-4476-92c2-ceae38ddca9c","doc_no":"A.1.10.5.2.2.2.2","title":"GroupedClipBreakerSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":839,"content":"This Standby Spell can be used in an emergency to stop liquidations for the specified collaterals.","contentHash":"921b8fb7e93769ebff6f98eb2732880a31710be8cf9695afcfe173865afd645f","addressRefs":[]},"a43090f2-f8a6-4703-ac02-47f3cad16529":{"id":"a43090f2-f8a6-4703-ac02-47f3cad16529","doc_no":"A.1.10.5.2.2.3","title":"Multi-Collateral Standby Spells","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":840,"content":"The subdocuments herein define currently available multi-collateral Standby Spells. Multi-collateral Standby Spell contracts are Spells in themselves and are thus reusable; beyond the initial deployment of the contract, no further deployment is needed.","contentHash":"e62fc724b1250a480c8553c36bc56280e34ed11c3593881e02065a0843f2807e","addressRefs":[]},"8b4f7c2e-817c-40f8-9b2c-d1a3f907fe3a":{"id":"8b4f7c2e-817c-40f8-9b2c-d1a3f907fe3a","doc_no":"A.1.10.5.2.2.3.1","title":"MultiLineWipeSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":841,"content":"This Standby Spell will wipe all lines, setting the debt ceilings for all collaterals (lines) to zero. Users will still be able to exit their positions, but no new debt will be allowed to be created for any collateral.","contentHash":"a86e3660e4362500088edf00ad28649db627767d585752153b6a4f3b689844a2","addressRefs":[]},"f5587483-d4cb-452d-b3ad-a5f565a36275":{"id":"f5587483-d4cb-452d-b3ad-a5f565a36275","doc_no":"A.1.10.5.2.2.3.2","title":"MultiClipBreakerSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":842,"content":"This Standby Spell will freeze liquidations for all collaterals.","contentHash":"fb32b23fad35aea1e5b400a5e532fa654704f3acc6e066491d2db744aa2e52cd","addressRefs":[]},"4cc57ff9-576e-4e35-a166-06e4e1e287a6":{"id":"4cc57ff9-576e-4e35-a166-06e4e1e287a6","doc_no":"A.1.10.5.2.2.3.3","title":"MultiOsmStopSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":843,"content":"This Standby Spell will freeze all OSMs. If the oracle price provider fails for any reason, Governance can act before the OSM registers the next price; this allows for the problem to be fixed with no impact on the system.","contentHash":"cc3181f1698002694e301b84ab2759f2d5781570af23350befc63c69f1fe7b5a","addressRefs":[]},"ea6670a4-58d9-4608-8240-32c098b3db11":{"id":"ea6670a4-58d9-4608-8240-32c098b3db11","doc_no":"A.1.10.5.2.2.4","title":"Global Standby Spells","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":844,"content":"The subdocuments herein define currently available global Standby Spells. Global Standby Spell contracts are Spells in themselves and are thus reusable; beyond the initial deployment of the contract, no further deployment is needed. Global Standby Spells differ from multi-collateral Standby Spells in that the former operates on the Protocol globally and not on some set of collaterals.","contentHash":"8dac50b2b697a6c1d3064220971ac7f8de94e61b682a4d16eaf408ee1fba08af","addressRefs":[]},"06f796a3-4f91-4ba8-b7e9-f08e90a52a8d":{"id":"06f796a3-4f91-4ba8-b7e9-f08e90a52a8d","doc_no":"A.1.10.5.2.2.4.1","title":"SplitterStopSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":845,"content":"This Standby Spell can be used in an emergency to disable the Smart Burn Engine.","contentHash":"ebcf62f6f66cf6cd1ae54a0a6d6c446f668226d61a64c9fb5aa5236107b5ba5c","addressRefs":[]},"7a151ea1-5fe7-4d2f-901f-071f141abbf9":{"id":"7a151ea1-5fe7-4d2f-901f-071f141abbf9","doc_no":"A.1.10.5.2.2.4.2","title":"SPBEAMHaltSpell","type":"Core","depth":6,"parentId":"bd8bf8d3-e98f-48ae-91c0-a5f671c21cba","order":846,"content":"This Standby Spell can be used in an emergency to disable the Stability Parameter Bounded External Access Module (SP-BEAM). See [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a). After this Standby Spell is invoked, the SP-BEAM will no longer be able to set rates in the system. Invoking the Standby Spell has no impact on rates, which remain at pre-invocation levels until adjusted by Sky Governance via an Executive Vote.","contentHash":"d8fe3658d4509df5122bd6e6de7bc7bbacdcd5261c84e9c872eb89769a9c1ae7","addressRefs":[]},"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb":{"id":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","doc_no":"A.1.10.5.2.3","title":"Emergency Spells - Standby Spell Process Definition","type":"Core","depth":5,"parentId":"5e40b575-4eda-4a6b-ae63-15a046cfb35d","order":847,"content":"The subdocuments herein define the process for using Standby Spells.","contentHash":"fcdfec9c248ea1dd41d1fabc3d445b49c49be11119cbce41dc196648f14709e9","addressRefs":[]},"50d68397-c09d-4f82-9e8b-44c2bcc30fd7":{"id":"50d68397-c09d-4f82-9e8b-44c2bcc30fd7","doc_no":"A.1.10.5.2.3.1","title":"The Core Facilitator Role In Standby Spells","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":848,"content":"The role of the Core Facilitator in the Standby Spell process is as follows:\n\n- Standby Spells can only be used in response to a properly validated and categorized emergency scenario, for which the Core Facilitator is responsible. See [A.1.9.1.5.1 - Incident Validation](97020aa2-9492-4fa4-8eee-d860d6f33618) and [A.1.9.1.5.2 - Incident Categorization](f3a647b2-8083-41f1-b67a-66bd322ccc16).\n\nThe decision to initiate the process to use a Standby Spell is reserved for the Core Facilitator; where possible, the Core Facilitator should consult with any relevant Scope Advisor(s). See [A.1.9.1.4 - Emergency Response Roles And Responsibilities](c9c32f24-cf6c-43d5-ac4c-bd2b4d02032b).\n\n- The Core Facilitator must explicitly communicate the decision to use a Standby Spell in the secure, private communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf) or on a \"war room\" video call.\n\n- After the decision to use a Standby Spell is first reached on a video call, the Core Facilitator is required thereafter to promptly document their decision in the secure, private communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).\n\n- After the Core Facilitator decides to use a Standby Spell, TechOps Services must promptly trigger an incident to the Emergency Response Group as specified in [A.1.9.1.5.3 - Emergency-Contact Mechanism Trigger](34a3d273-ce49-4147-adf3-6d52b4a2fad5).\n\n- The Core Facilitator is responsible for actioning the Standby Spell and liaising with the Ranked Delegates (and other Aligned Delegates as needed) to gather the necessary support for it.","contentHash":"04ca2e14c748a5a5504092bbd2a07ea6e80876f83217b57de5237556802d7eee","addressRefs":[]},"832b2591-8512-4e87-a355-b87ded894e07":{"id":"832b2591-8512-4e87-a355-b87ded894e07","doc_no":"A.1.10.5.2.3.2","title":"Core GovOps Role In Standby Spells","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":849,"content":"Core GovOps must promptly acknowledge receipt of the Core Facilitator's decision to use a Standby Spell. This acknowledgment must take place in the communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).","contentHash":"ff43fc10e73d99efc7b6b968a9374d8bdc65a95055eaaf73fd09aa4d44ca96bb","addressRefs":[]},"82393e1d-1021-4f48-ac4e-a98d2328f2e7":{"id":"82393e1d-1021-4f48-ac4e-a98d2328f2e7","doc_no":"A.1.10.5.2.3.2.1","title":"Requirement To Validate Authenticity Of Standby Spell","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":850,"content":"Two Authorized Representatives, as defined in the subdocument below, from Core GovOps must validate the authenticity of the Standby Spell.\n\nThis validation must be in the form of a written communication in the secure channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf). Only the entities specified in [A.1.10.5.2.3.2.1.1 - Current Entities Authorized To Validate Authenticity of Standby Spell](4cf98145-079f-44e0-9a2b-1d7b16037f4a) are authorized to provide the validation of authenticity.\n\nPursuant to [A.1.10.5.2.3.3 - ADs' Role In Standby Spells](53cea69b-45cc-4f9c-b863-9bf259e37deb), ADs are prohibited from voting for a Standby Spell without this validation of authenticity.","contentHash":"987ae9e84d1ee17377ab26a961b8a2925ed8e667ae7eca7c6d79b2ae1567d85e","addressRefs":[]},"4cf98145-079f-44e0-9a2b-1d7b16037f4a":{"id":"4cf98145-079f-44e0-9a2b-1d7b16037f4a","doc_no":"A.1.10.5.2.3.2.1.1","title":"Current Entities Authorized To Validate Authenticity of Standby Spell","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":851,"content":"This document defines the term \"Authorized Representative\" as used in [A.1.10.5.2.3.2.1 - Requirement To Validate Authenticity Of Standby Spell](82393e1d-1021-4f48-ac4e-a98d2328f2e7).\n\nThe entities listed below are authorized to validate the authenticity of a Standby Spell on behalf of Core GovOps:\n\n- Le Bateleur on behalf of Core GovOps team Atlas Axis\n- Adam Fraser on behalf of Core GovOps team Atlas Axis\n- Lex on behalf of Core GovOps team Atlas Axis\n\nThe Authorized Representatives listed are synonymous with the Sky Forum account holders with the following handles:\n\n- Le_Bateleur\n- adamfraser\n- Lex","contentHash":"fb00ee5ff64f4eacef31e2c4bbf162bf6378e0e7605d1f5862c5b8065c62ef52","addressRefs":[]},"387fa314-7c0a-469d-8996-5dc4c30b4f7e":{"id":"387fa314-7c0a-469d-8996-5dc4c30b4f7e","doc_no":"A.1.10.5.2.3.2.2","title":"Custom Spell Voting For Standby Spells","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":852,"content":"The Core Facilitator may use the Custom Spell Voting Page when it is beneficial to coordinate voting without using the standard Spell process. The Core Facilitator must not use this method unless domain expert Ecosystem Actors in the Emergency Response Group have recommended this approach; such a recommendation must be explicitly documented in the communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).","contentHash":"e847413cb10deed50d6d3f0a62bcc002a586c48db7c0d2f0c2f19a1a64d91147","addressRefs":[]},"53cea69b-45cc-4f9c-b863-9bf259e37deb":{"id":"53cea69b-45cc-4f9c-b863-9bf259e37deb","doc_no":"A.1.10.5.2.3.3","title":"ADs' Role In Standby Spells","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":853,"content":"ADs are strictly prohibited from voting to use a Standby Spell unless they have first confirmed all of the following requirements:\n\n- Receipt of the Core Facilitator's official notification of the emergency scenario in the Emergency Contact Mechanism specified in [A.1.9.1.5.3 - Emergency-Contact Mechanism Trigger](34a3d273-ce49-4147-adf3-6d52b4a2fad5).\n- Receipt of the Core Facilitator's announcement of the decision to use a Standby Spell in the communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf); and\n- Core GovOps has validated the authenticity of the Standby Spell. This validation must fulfill two requirements: (1) the validation must be in the form of a written communication in the secure channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf); and (2) the validation must be provided by the Authorized Representatives listed in [A.1.10.5.2.3.2.1.1 - Current Entities Authorized To Validate Authenticity of Standby Spell](4cf98145-079f-44e0-9a2b-1d7b16037f4a).\n\nAfter ADs have confirmed all requirements are met, they must either (1) promptly vote to approve the Standby Spell, or (2) communicate any concerns to the Core Facilitator and collaborate with the latter for a speedy resolution.","contentHash":"09f535931d3cf8977544e256833e95336d00eeaa7ed4827c9b468d5d7a8b84ac","addressRefs":[]},"0567fc4c-4a93-4f7e-803e-f587ddbd4f15":{"id":"0567fc4c-4a93-4f7e-803e-f587ddbd4f15","doc_no":"A.1.10.5.2.3.3.1","title":"AD Reliance On Core GovOps In Standby Spell Process Where Core GovOps Is Nonresponsive","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":854,"content":"There is an exception to the requirement that two Authorized Representatives from Core GovOps must validate the authenticity of a Standby Spell. In situations where the Authorized Representatives have failed to respond to the emergency situation, the Core Facilitator may temporarily grant an Operational Facilitator the sole authority to validate the authenticity of the Emergency Spell pursuant to [A.1.10.5.2.3.3 - ADs' Role In Standby Spells](53cea69b-45cc-4f9c-b863-9bf259e37deb). The Core Facilitator must communicate this in writing in the secure channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).","contentHash":"635a89ffe7aa4065fb135888aa91be6269744493c10cfc30ce4bf656b56fbf2f","addressRefs":[]},"75cdffe9-bec6-478c-aa6c-adcc3edb4fbe":{"id":"75cdffe9-bec6-478c-aa6c-adcc3edb4fbe","doc_no":"A.1.10.5.2.3.3.2","title":"Misalignment To Vote For Unvalidated Standby Spell","type":"Core","depth":6,"parentId":"eeaaa751-cc77-475c-a60f-13a3dcc5e3bb","order":855,"content":"It is severe misalignment for an Aligned Delegate to vote for a Standby Spell whose authenticity has not been validated pursuant to [A.1.10.5.2.3.3 - ADs' Role In Standby Spells](53cea69b-45cc-4f9c-b863-9bf259e37deb). Aligned Delegates in breach of this requirement must be immediately derecognized and their full AD Buffer should be confiscated.","contentHash":"bd2d82cd7acf581f0b40b28d6bb5a41d16158b6a535fab6de0108a1007d50afe","addressRefs":[]},"1ac0d0c7-5942-4f4d-9730-3a14244fcb38":{"id":"1ac0d0c7-5942-4f4d-9730-3a14244fcb38","doc_no":"A.1.10.5.2.4","title":"Accountability","type":"Core","depth":5,"parentId":"5e40b575-4eda-4a6b-ae63-15a046cfb35d","order":856,"content":"Breach of any requirement concerning Emergency Spells - including Standby Spells - constitutes misalignment and must be addressed pursuant to [A.1.9.1.6 - Accountability For Emergency Response Preparedness](8df982ee-754c-4cd9-a5f9-ce1c30e06cf8).","contentHash":"f956b3a72f1c901ca66116809de325472a273ef695106135893d3108fd471278","addressRefs":[]},"13cdbb75-527a-4b68-b02e-90641881dbe6":{"id":"13cdbb75-527a-4b68-b02e-90641881dbe6","doc_no":"A.1.10.5.3","title":"Protego","type":"Core","depth":4,"parentId":"b8266c11-3a84-4bbe-abe2-de9474f74ffd","order":857,"content":"Protego is a contract that allows Sky Governance to cancel the execution of planned governance actions that are awaiting the expiration of the Governance Security Module Pause Delay (GSM Pause Delay). See [A.1.10.3.1 - Pause Delay](3c9545d9-775f-4149-88bf-7d297b5302c6). The subdocuments herein specify the features of the Protego contract and its authorized use.","contentHash":"c8ceb40c502a10028df3e43eeb39c23ff4a8d73f7830449e9926eed32c96483e","addressRefs":[]},"152e5205-8fed-4240-aa0c-00fd433d3542":{"id":"152e5205-8fed-4240-aa0c-00fd433d3542","doc_no":"A.1.10.5.3.1","title":"Protego Features","type":"Core","depth":5,"parentId":"13cdbb75-527a-4b68-b02e-90641881dbe6","order":858,"content":"The Protego contract allows canceling the execution of planned governance actions within the Sky Protocol. Technical updates and other protocol changes are implemented as Spells within the Sky Protocol, approved by Sky Governance via Executive Votes. These planned governance actions have a time delay before taking effect. In this period between approval and execution, the Protego contract allows for planned governance actions to be canceled. The documents herein specify the core features of the Protego contract.","contentHash":"1433ac3f721f98f1a9d25d0583ce0b9ce009ab2955b258b23d6f13cf3c50f314","addressRefs":[]},"4f5e346e-5ed4-4e2e-a463-19cbcfb5021c":{"id":"4f5e346e-5ed4-4e2e-a463-19cbcfb5021c","doc_no":"A.1.10.5.3.1.1","title":"Emergency Drop Spells","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":859,"content":"The Protego contract can be used to deploy an Emergency Drop Spell. Once authorized by Sky Governance, the Emergency Drop Spell can cancel any planned governance action that is awaiting GSM Pause Delay expiration.","contentHash":"17b1f575c1051223d412c07aa8d970dcb4b0ea1e3f66eee9bee0c55ce5a1b805","addressRefs":[]},"583c1a98-b63a-42fa-b29e-ce0688dcdaf6":{"id":"583c1a98-b63a-42fa-b29e-ce0688dcdaf6","doc_no":"A.1.10.5.3.1.1.1","title":"Deployment Of Emergency Drop Spells","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":860,"content":"Any user can permissionlessly deploy an Emergency Drop Spell by invoking the `deploy` function on the Protego contract with parameters identifying the planned governance action to be canceled:\n\n`deploy(address _usr, bytes32 _tag, bytes memory _fax, uint256 _eta)(address)`\n\nThe parameters of the `deploy` function are defined in [A.1.10.5.3.1.3 - Protego Parameters](55195cdc-90c3-4133-a0e4-792444b60ed8).","contentHash":"958904c1812c4a871c8d8dfeeddfe9623b859220176e5e90689f834fec3cc645","addressRefs":[]},"44bb2b0d-ba95-47db-9195-6c80f97734b7":{"id":"44bb2b0d-ba95-47db-9195-6c80f97734b7","doc_no":"A.1.10.5.3.1.1.2","title":"Execution Of Emergency Drop Spells","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":861,"content":"Once an Emergency Drop Spell has been deployed, it can be used to cancel the execution of the planned governance action by invoking its `drop` function. This function can only be invoked if the Emergency Drop Spell has been granted authority by Sky Governance by giving the Emergency Drop Spell the `hat` in the Chief contract.","contentHash":"8af5cb956dad1be977764c225e90777b7194558d6768f77859a713f61a36bd29","addressRefs":[]},"540d277c-cc25-4e1b-b17e-3a13001483ba":{"id":"540d277c-cc25-4e1b-b17e-3a13001483ba","doc_no":"A.1.10.5.3.1.2","title":"Allowing Permissionless Cancellation Of Planned Governance Actions","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":862,"content":"The Protego contract can be granted authority by Sky Governance to allow any user to permissionlessly cancel any planned governance action. This is done by giving the Protego contract the `hat` in the Chief contract. Once the Protego contract has been granted authority, any user can cancel either a single planned governance action or a set of planned governance actions as specified herein.","contentHash":"488f29ab9378e4b0759c0c979e5be87c314419f0b5fb9c5b8adc719e8b99d8f6","addressRefs":[]},"e4e3c3d9-939d-43ef-9f7a-64f5d4cfe7d6":{"id":"e4e3c3d9-939d-43ef-9f7a-64f5d4cfe7d6","doc_no":"A.1.10.5.3.1.2.1","title":"Permissionless Cancellation Of Single Planned Governance Action","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":863,"content":"If the Protego contract has authority from Sky Governance, any user can permissionlessly invoke the `drop` function to cancel a specified Spell:\n\n```\n/// @notice Permissionlessly drop anything that has been planned on the pause.\ndrop(address _usr, bytes32 _tag, bytes memory _fax, uint256 _eta)\n```\n\nThe parameters of the `drop` function are defined in [A.1.10.5.3.1.3 - Protego Parameters](55195cdc-90c3-4133-a0e4-792444b60ed8).","contentHash":"bccb6eedd47694a0eac8cb63e924942b8ba7c9f637a44fa2c96c5ce0e39e1495","addressRefs":[]},"6022623f-e7cd-4a04-a8ab-e5b61c11a9da":{"id":"6022623f-e7cd-4a04-a8ab-e5b61c11a9da","doc_no":"A.1.10.5.3.1.2.2","title":"Permissionless Cancellation Of Multiple Planned Governance Actions","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":864,"content":"If the Protego contract has authority from Sky Governance, any user can permissionlessly invoke the `drop` function to cancel a specified set of Spells:\n\n```\n/// @notice Drop multiple plans in a single call.\ndrop(Plan[] calldata plans)\n```\n\nThe parameter of the `drop` function is defined in [A.1.10.5.3.1.3 - Protego Parameters](55195cdc-90c3-4133-a0e4-792444b60ed8).","contentHash":"25bc68101332db803839e0afbf92ef3912582f35752738e294f4fed7062942ed","addressRefs":[]},"55195cdc-90c3-4133-a0e4-792444b60ed8":{"id":"55195cdc-90c3-4133-a0e4-792444b60ed8","doc_no":"A.1.10.5.3.1.3","title":"Protego Parameters","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":865,"content":"The documents herein define parameters that are used in functions of the Protego contract and the process for determining them.","contentHash":"753e50b4dcb55a76745b993e69fb06b9376b843ce01a16600287f1995404aa6c","addressRefs":[]},"4ff6766c-53a7-4c77-8f72-b4e120728d92":{"id":"4ff6766c-53a7-4c77-8f72-b4e120728d92","doc_no":"A.1.10.5.3.1.3.1","title":"Protego Usr Parameter Definition","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":866,"content":"The `usr` parameter is the address of the scheduled Spell to be canceled.","contentHash":"8a32dd19072233303796f87c85852f991af5e23bcb19bf13a1e78bdd0d0f54c1","addressRefs":[]},"29e06433-4d5f-458e-9adb-2e93b44a29f0":{"id":"29e06433-4d5f-458e-9adb-2e93b44a29f0","doc_no":"A.1.10.5.3.1.3.2","title":"Protego Tag Parameter Definition","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":867,"content":"The `tag` parameter identifies the address of the scheduled Spell to be canceled.","contentHash":"49c64962e6efb2639938e37274d1ca2b08364b9c6216ec4610007eb2fc1ccb83","addressRefs":[]},"559f640c-bca7-4f8b-8fa2-8745566a2d03":{"id":"559f640c-bca7-4f8b-8fa2-8745566a2d03","doc_no":"A.1.10.5.3.1.3.3","title":"Protego Fax Parameter Definition","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":868,"content":"The `fax` parameter is the encoded call to be made in the scheduled Spell to be canceled.","contentHash":"6214717babea8b4078cca79abedbe19a1a8d35bdbffcff646979b4de7c9961fe","addressRefs":[]},"da310ed1-1d3c-425f-9369-c65782b8f092":{"id":"da310ed1-1d3c-425f-9369-c65782b8f092","doc_no":"A.1.10.5.3.1.3.4","title":"Protego Eta Parameter Definition","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":869,"content":"The `eta` parameter is the expiration time of the scheduled Spell to be canceled.","contentHash":"0837c653a4cd772d180fbdff94ebfae38f3f9f517db790f2e7eeb74e92a4300a","addressRefs":[]},"4a154956-88d7-4b90-a9b0-3a96871087a7":{"id":"4a154956-88d7-4b90-a9b0-3a96871087a7","doc_no":"A.1.10.5.3.1.3.5","title":"Plans Parameter Definition","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":870,"content":"The `plans` parameter is an array of scheduled Spells to be canceled. Each scheduled Spell to be canceled is represented as a `Plan` struct:\n\n```\n/**\n * @notice A struct representing a plan.\n * @param usr The address of the scheduled spell.\n * @param tag The tag identifying the address.\n * @param fax The encoded call to be made in \\`usr\\`.\n * @param eta The expiration time.\n */\nstruct Plan {\n    address usr;\n    bytes32 tag;\n    bytes fax;\n    uint256 eta;\n}\n```\n\nThe parameters of the `Plan` struct are defined in [A.1.10.5.3.1.3 - Protego Parameters](55195cdc-90c3-4133-a0e4-792444b60ed8).","contentHash":"09dd29dd6a8c13338106bfa401750e14f98793d412813309947050c2f9fab4af","addressRefs":[]},"49997c91-ec3c-47be-ad1a-abfd33dd259b":{"id":"49997c91-ec3c-47be-ad1a-abfd33dd259b","doc_no":"A.1.10.5.3.1.3.6","title":"Determining Protego Parameters","type":"Core","depth":6,"parentId":"152e5205-8fed-4240-aa0c-00fd433d3542","order":871,"content":"The parameters for the scheduled Spell to be canceled, as specified in [A.1.10.5.3.1.3 - Protego Parameters](55195cdc-90c3-4133-a0e4-792444b60ed8), should always be determined by inspecting the logs emitted from the `plot` function of the Pause contract. The parameters should never be determined by calling functions on the Spell to be canceled, because these functions may not return the correct values in the case of a malicious Spell.","contentHash":"4b3fdeccfa82a3de29dec00adbd3746b389008c655884c7fd15268b9649e663a","addressRefs":[]},"69da8af1-ecc0-4fd3-9268-33fff87d5253":{"id":"69da8af1-ecc0-4fd3-9268-33fff87d5253","doc_no":"A.1.10.5.3.2","title":"Protego Usage Process Definition","type":"Core","depth":5,"parentId":"13cdbb75-527a-4b68-b02e-90641881dbe6","order":872,"content":"The subdocuments herein define the governance process for using Protego.","contentHash":"24650faed5784a0c75951f8dcbde7a0d23eb7c6799d83c666d8b033cf279582f","addressRefs":[]},"afa90735-e752-462c-b06f-c3bd9076e06f":{"id":"afa90735-e752-462c-b06f-c3bd9076e06f","doc_no":"A.1.10.5.3.2.1","title":"The Core Facilitator Role In Protego Usage","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":873,"content":"The role of the Core Facilitator in the usage of Protego is as follows:\n\n- Protego can only be used in response to a properly validated and categorized emergency scenario, for which the Core Facilitator is responsible. See [A.1.9.1.5.1 - Incident Validation](97020aa2-9492-4fa4-8eee-d860d6f33618) and [A.1.9.1.5.2 - Incident Categorization](f3a647b2-8083-41f1-b67a-66bd322ccc16).\n- The decision to initiate the process to use Protego is reserved for the Core Facilitator; where possible, the Core Facilitator should consult with any relevant Scope Advisor(s). See [A.1.9.1.4 - Emergency Response Roles And Responsibilities](c9c32f24-cf6c-43d5-ac4c-bd2b4d02032b).\n- The Core Facilitator must explicitly communicate the decision to use Protego in the secure, private communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf) or on a \"war room\" video call.\n- If the decision to use Protego is first reached on a video call, the Core Facilitator is required thereafter to promptly document their decision in the secure, private communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).\n- After the Core Facilitator decides to use Protego, TechOps Services must promptly trigger an incident to the Emergency Response Group as specified in [A.1.9.1.5.3 - Emergency-Contact Mechanism Trigger](34a3d273-ce49-4147-adf3-6d52b4a2fad5).\n- The Core Facilitator is responsible for actioning the usage of Protego and liaising with the Ranked Delegates (and other Aligned Delegates as needed) to gather the necessary support for it.","contentHash":"089496b0904b9aa82d02c301bdf8287e3f01575aa6940cb73ce60105c2f51139","addressRefs":[]},"62d53156-9b53-447b-9655-cef35a74defd":{"id":"62d53156-9b53-447b-9655-cef35a74defd","doc_no":"A.1.10.5.3.2.2","title":"Core GovOps Role In Protego Usage","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":874,"content":"Core GovOps must promptly acknowledge receipt of the Core Facilitator's decision to use Protego. This acknowledgment must take place in the communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).","contentHash":"98b77e324a04438507131cac1be8a1218282c8ce702a831b1eeaef69e360fa1a","addressRefs":[]},"44b9503d-bc11-427e-8deb-47feed07eba2":{"id":"44b9503d-bc11-427e-8deb-47feed07eba2","doc_no":"A.1.10.5.3.2.2.1","title":"Requirement To Validate Authenticity Of Emergency Drop Spell","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":875,"content":"Two Authorized Representatives, as defined in the subdocument below, from Core GovOps must validate the authenticity of the Emergency Drop Spell, if applicable.\n\nThis validation must be in the form of a written communication in the secure channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf). Only the entities specified in [A.1.10.5.3.2.2.1.1 - Current Entities Authorized To Validate Authenticity of Emergency Drop Spell](a15e7cd9-ea93-48ac-b53a-afc476ca2d05) are authorized to provide the validation of authenticity.\n\nPursuant to [A.1.10.5.3.2.3 - ADs' Role In Protego Usage](0cec9b17-ef83-4d25-9b6e-dbba11587d52), ADs are prohibited from voting for an Emergency Drop Spell without this validation of authenticity.","contentHash":"af32dfcff6abda281f6623ee8e3974c6a0ca317986f11e71bced0236d40c12e8","addressRefs":[]},"a15e7cd9-ea93-48ac-b53a-afc476ca2d05":{"id":"a15e7cd9-ea93-48ac-b53a-afc476ca2d05","doc_no":"A.1.10.5.3.2.2.1.1","title":"Current Entities Authorized To Validate Authenticity of Emergency Drop Spell","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":876,"content":"This document defines the term \"Authorized Representative\" as used in [A.1.10.5.3.2.2.1 - Requirement To Validate Authenticity Of Emergency Drop Spell](44b9503d-bc11-427e-8deb-47feed07eba2).\n\nThe entities listed below are authorized to validate the authenticity of an Emergency Drop Spell on behalf of Core GovOps:\n\n- Le Bateleur on behalf of Core GovOps team Atlas Axis\n- Adam Fraser on behalf of Core GovOps team Atlas Axis\n- Lex on behalf of Core GovOps team Atlas Axis\n\nThe Authorized Representatives listed are synonymous with the Sky Forum account holders with the following handles:\n\n- Le_Bateleur\n- adamfraser\n- Lex","contentHash":"ca5ca7067a4e94f49b44c77c0ee363c789fce7e349d6128ce48f22ea88d629e0","addressRefs":[]},"5bf1e3b0-1e2a-4237-b87f-7db48def5960":{"id":"5bf1e3b0-1e2a-4237-b87f-7db48def5960","doc_no":"A.1.10.5.3.2.2.1.2","title":"Custom Spell Voting For Protego Usage","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":877,"content":"The Core Facilitator may use the Custom Spell Voting Page when it is beneficial to coordinate voting without using the standard Spell process. The Core Facilitator must not use this method unless domain expert Ecosystem Actors in the Emergency Response Group have recommended this approach; such a recommendation must be explicitly documented in the communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).","contentHash":"e847413cb10deed50d6d3f0a62bcc002a586c48db7c0d2f0c2f19a1a64d91147","addressRefs":[]},"0cec9b17-ef83-4d25-9b6e-dbba11587d52":{"id":"0cec9b17-ef83-4d25-9b6e-dbba11587d52","doc_no":"A.1.10.5.3.2.3","title":"ADs' Role In Protego Usage","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":878,"content":"ADs are strictly prohibited from voting to use an Emergency Drop Spell, or to give authority to the Protego contract, unless they have first confirmed all of the following requirements:\n\n- Receipt of the Core Facilitator's official notification of the emergency scenario in the Emergency Contact Mechanism specified in [A.1.9.1.5.3 - Emergency-Contact Mechanism Trigger](34a3d273-ce49-4147-adf3-6d52b4a2fad5);\n- Receipt of the Core Facilitator's announcement of the decision to use Protego or an Emergency Drop Spell in the communication channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf); and\n- Core GovOps has validated the authenticity of the Emergency Drop Spell, if applicable. This validation must fulfill two requirements: (1) the validation must be in the form of a written communication in the secure channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf); and (2) the validation must be provided by the Authorized Representatives listed in [A.1.10.5.3.2.2.1.1 - Current Entities Authorized To Validate Authenticity of Emergency Drop Spell](a15e7cd9-ea93-48ac-b53a-afc476ca2d05).\n\nAfter ADs have confirmed all requirements are met, they must either (1) promptly vote to approve the usage of Protego or the Emergency Drop Spell, or (2) communicate any concerns to the Core Facilitator and collaborate with the latter for a speedy resolution.","contentHash":"0055acfb29771345fc7859cfd7ea6a502a471162f0d090b482fc60e1bac2a85f","addressRefs":[]},"5bff38dc-5416-40e7-ab84-25adacb1e60a":{"id":"5bff38dc-5416-40e7-ab84-25adacb1e60a","doc_no":"A.1.10.5.3.2.3.1","title":"AD Reliance On Core GovOps In Emergency Drop Spell Process Where Core GovOps Is Nonresponsive","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":879,"content":"There is an exception to the requirement that two Authorized Representatives from Core GovOps must validate the authenticity of an Emergency Drop Spell. In situations where the Authorized Representatives have failed to respond to the emergency situation, the Core Facilitator may temporarily grant an Operational Facilitator the sole authority to validate the authenticity of the Emergency Drop Spell pursuant to [A.1.10.5.3.2.3 - ADs' Role In Protego Usage](0cec9b17-ef83-4d25-9b6e-dbba11587d52). The Core Facilitator must communicate this in writing in the secure channel specified in [A.1.9.1.3.1 - Emergency Response Signal Group](45a7ccff-09fa-4d95-b3d8-e3f34f7917cf).","contentHash":"92d379c10cb1d5f8c4617505a0e255e16bddbf688a205fab97671988d48aa548","addressRefs":[]},"fc62902d-f408-4f45-a284-193ed7688c19":{"id":"fc62902d-f408-4f45-a284-193ed7688c19","doc_no":"A.1.10.5.3.2.3.2","title":"Misalignment To Vote For Unvalidated Emergency Drop Spell","type":"Core","depth":6,"parentId":"69da8af1-ecc0-4fd3-9268-33fff87d5253","order":880,"content":"It is severe misalignment for an Aligned Delegate to vote for an Emergency Drop Spell whose authenticity has not been validated pursuant to [A.1.10.5.3.2.3 - ADs' Role In Protego Usage](0cec9b17-ef83-4d25-9b6e-dbba11587d52). Aligned Delegates in breach of this requirement must be immediately derecognized and their full AD Buffer should be confiscated.","contentHash":"23e63cd1c2603192256032f2a928a6ce7f32187d63df43c61c66f642851a1ed9","addressRefs":[]},"fd63dc4d-851a-4995-801d-843e68bfb68e":{"id":"fd63dc4d-851a-4995-801d-843e68bfb68e","doc_no":"A.1.10.5.3.3","title":"Protego Usage Accountability","type":"Core","depth":5,"parentId":"13cdbb75-527a-4b68-b02e-90641881dbe6","order":881,"content":"Breach of any requirement concerning Emergency Spells - including usage of Protego - constitutes misalignment and must be addressed pursuant to [A.1.9.1.6 - Accountability For Emergency Response Preparedness](8df982ee-754c-4cd9-a5f9-ce1c30e06cf8).","contentHash":"940e025fd57049b21488517f3d60c076fce6c93cf0835ab050bd8d4388917763","addressRefs":[]},"83edd4e1-692e-4566-a415-b8f272c33c5e":{"id":"83edd4e1-692e-4566-a415-b8f272c33c5e","doc_no":"A.1.11","title":"Weekly Governance Cycle","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":882,"content":"This Article regulates the Weekly Governance Cycle which comprises two distinct subsets, the Operational Weekly Cycle and the Atlas Edit Weekly Cycle.","contentHash":"5da32335b1ffad148f159640360225365c457ac3e79c28054fada243b3864aee","addressRefs":[]},"999e4aff-e61b-4097-87a8-153afae5098b":{"id":"999e4aff-e61b-4097-87a8-153afae5098b","doc_no":"A.1.11.1","title":"Operational Weekly Cycle","type":"Section","depth":3,"parentId":"83edd4e1-692e-4566-a415-b8f272c33c5e","order":883,"content":"This Section defines the Operational Weekly Cycle, a predictable weekly framework for recurring operational decisions. The Operational Weekly Cycle is implemented via Governance Polls and Executive Votes. The Cycle complements the Monthly Governance Cycle by enabling recurring weekly decisions to be made that require quicker action than is allowed by the Monthly Governance Cycle.","contentHash":"db57116a11f5cc04542fb72b5ebcd74d3a515b1a39a61272fc7d25934cfa97b1","addressRefs":[]},"6a1ef4ee-7f34-47ae-8018-dd4b059d495d":{"id":"6a1ef4ee-7f34-47ae-8018-dd4b059d495d","doc_no":"A.1.11.1.1","title":"Edits To The Atlas","type":"Core","depth":4,"parentId":"999e4aff-e61b-4097-87a8-153afae5098b","order":884,"content":"The Operational Weekly Cycle may be used to edit the Atlas only if the pertinent Atlas document specifies that it, or a related unit of governance logic which it expressly controls, is modifiable through the Operational Weekly Cycle.\n\nThe general rule is that an Operational Weekly Cycle proposal requires a Governance Poll followed by an Executive Vote. The general rule, by default, is assumed wherever the Atlas provides that a document, or a unit of governance logic controlled by said document, is modifiable through the Operational Weekly Cycle.\n\nAny exception to the general rule must be specifically stated in the pertinent Atlas document. The possible exceptions include documents that can be modified subject to a Governance Poll only; and documents that can be modified subject to an Executive Vote only, without requiring a previous Governance Poll.","contentHash":"db21c781a82dd1529f6422e3e5c9ce9b1b03ef281ea4694129bfa1918b59eba9","addressRefs":[]},"a7c4d100-e2ae-481a-aeca-de95a78cef73":{"id":"a7c4d100-e2ae-481a-aeca-de95a78cef73","doc_no":"A.1.11.1.2","title":"Definitions","type":"Core","depth":4,"parentId":"999e4aff-e61b-4097-87a8-153afae5098b","order":885,"content":"The subdocuments herein contain essential definitions pertinent to the Operational Weekly Cycle.","contentHash":"a5ec77cf9ab7e2071cde9d30a75a60b15eafca92d79830ad5a739c035cbf556c","addressRefs":[]},"cae731e3-0828-42ce-ae53-259c5c54cb79":{"id":"cae731e3-0828-42ce-ae53-259c5c54cb79","doc_no":"A.1.11.1.2.1","title":"Definition Of Weekly Poll","type":"Core","depth":5,"parentId":"a7c4d100-e2ae-481a-aeca-de95a78cef73","order":886,"content":"A Weekly Poll (\"Governance Poll\" or \"Poll\") is a non-binding poll that determines the bi-weekly Executive Vote contents. In this context, a non-binding weekly poll refers to the fact that a weekly poll cannot change the system parameters independently; it merely dictates what will be included in the next Executive Vote.\n\nGovernance Polls occur on-chain and are used to measure the sentiment of SKY voters. Polls often run concurrently, allowing voters to participate in any number of them at the same time. Polls may have different formats like Binary Voting, Instant Run-Off Voting, or Approval Voting depending on the topic. The voting period of a given Governance Poll varies; the most common are three (3) and fourteen (14) day periods. Concurrently-posted polls do not necessarily have the same voting periods.","contentHash":"3a3e5e5853d68f74c30cd5e6176a8e22683a71018842aa6bfbe75e714e56ef7d","addressRefs":[]},"8bde129a-49a5-4f68-a82f-9995b86a1aa3":{"id":"8bde129a-49a5-4f68-a82f-9995b86a1aa3","doc_no":"A.1.11.1.2.2","title":"Definition Of Executive Vote","type":"Core","depth":5,"parentId":"a7c4d100-e2ae-481a-aeca-de95a78cef73","order":887,"content":"An Executive Vote (also \"Executive\") is a formalized governance proposal that requires on-chain voting. Through the Executive Vote mechanism, SKY holders steward Sky Governance by voting on Executive proposals that pertain to operations maintaining the Protocol. Executive Votes execute technical changes to the Sky Protocol.\n\nThe Executive Vote occurs approximately every two weeks. Its contents are often determined by weekly Governance Polls that pre-approve the inclusion of proposals in the Executive Vote. However, the Atlas can explicitly authorize proposals to go directly to an Executive Vote.\n\nNote that the terms ‘Executive’ and ‘Spell’ are distinct concepts.\n\nThe term ‘Executive’ or ‘Executive Vote’ is used in all instances where the formal governance vote is being referenced. The term ‘Executive Process’ refers to the end-to-end process of the development of an Executive Vote, in which Facilitators, Spell teams (also referred to collectively as the \"Governance Security Engineering Team\") and other recognized Ecosystem Actors participate.\n\nThe term ‘Spell’ refers to the smart contract that executes the changes to the protocol approved by Sky Governance in an Executive Vote. Generally, when referring to Spell team operations and their technical outcome or product (including code base, code operations, code reviews and code quality), the term ‘Spell’ will be used.\n\nThe term ‘Spell process’ refers to the end-to-end process of developing a Spell, a process in which the Core Facilitator and the current Spell team participate. The term ‘Spell development process’ is a subset of the ‘Spell process’ and pertains solely to the technical development of the Spell by the current Spell team.","contentHash":"73a7e3c7213ec68be0a6ba79fa88973d0c1a67b7730f5eaea87efc81404c8d6f","addressRefs":[]},"22508894-e015-4f7c-9ee8-24ac13756d31":{"id":"22508894-e015-4f7c-9ee8-24ac13756d31","doc_no":"A.1.11.1.3","title":"Full Cycle Breakdown","type":"Core","depth":4,"parentId":"999e4aff-e61b-4097-87a8-153afae5098b","order":888,"content":"Every Monday, the Operational Weekly Cycle begins. It implements standard recurring operational decisions, proposed in the form of polls.\n\nOperational Weekly Cycle proposals (\"proposals\") can be proposed by Facilitators and recognized Ecosystem Actors. The proposals should be posted to the Sky Forum by Friday at 8:00 am UTC to ensure the Core Facilitator has sufficient time to prepare the needed polls for the following Monday.\n\nAfter confirming that the proposer has the authority to request a poll, the Facilitator must post an explicit approval of the poll request as a reply to the proposer’s Forum thread. The Core Facilitator must then prepare and publish the Governance Poll.\n\nThe Operational Weekly Cycle polls run for three days.\n\nThe outcome of the polls determines the contents of the upcoming Executive Vote.\n\nThe Core Facilitator confirm the Executive Vote contents and deliver the Executive Sheet to the Spell team. The Spell team prepares and reviews the Mainnet Spell. The Spell team deploys the Mainnet Spell; and then creates and reviews a Mainnet fork.\n\nThe Core Facilitator add the Executive Vote to the Voting Portal and communicate this to the Sky Ecosystem community. The Executive Vote has an expiration of thirty (30) days; if an Executive proposal does not pass within this timeframe, it expires and can no longer have any effect on the Sky Protocol.","contentHash":"34c0771f06a09e6691d8d8e0772ccff58835f73b9150a1eebdd27020d0c0cdbe","addressRefs":[]},"52aef6ac-9eda-4795-9dab-73ea85b8ca31":{"id":"52aef6ac-9eda-4795-9dab-73ea85b8ca31","doc_no":"A.1.11.1.3.0.3.1","title":"Executive Sheet - Element Annotation","type":"Annotation","depth":5,"parentId":"22508894-e015-4f7c-9ee8-24ac13756d31","order":889,"content":"The Executive Sheet refers to a Google Sheets document located at [https://docs.google.com/spreadsheets/d/1w_z5WpqxzwreCcaveB2Ye1PP5B8QAHDglzyxKHG3CHw/edit?gid=1593813984#gid=1593813984](https://docs.google.com/spreadsheets/d/1w_z5WpqxzwreCcaveB2Ye1PP5B8QAHDglzyxKHG3CHw/edit?gid=1593813984#gid=1593813984). The Executive Sheet contains a list of content which is planned to be included in a given Spell. The Executive Sheet is prepared by the Core Facilitator.","contentHash":"278c04a4cffbd64711ad3dc90e5cbd55eb5b1299e91ff05e24354e75fc259479","addressRefs":[]},"afe57048-78b8-4deb-9dde-971c49f2f442":{"id":"afe57048-78b8-4deb-9dde-971c49f2f442","doc_no":"A.1.11.1.3.0.3.2","title":"Operational Weekly Cycle - Element Annotation","type":"Annotation","depth":5,"parentId":"22508894-e015-4f7c-9ee8-24ac13756d31","order":890,"content":"Previously, the \"Operational Weekly Cycle\" was called simply the \"Weekly Governance Cycle.\" With the introduction of the Atlas Edit Weekly Cycle, it became necessary to divide the Weekly Governance Cycle into two (2) subtypes: the Atlas Edit Weekly Cycle and the Operational Weekly Cycle. These two subtypes differ in terms of the permissioned parties authorized to trigger a proposal and the governance mechanisms involved. For instance, the Atlas Edit Weekly Cycle implements edits to the Atlas via the mechanism of a Governance Poll only. The Operational Weekly Cycle can action changes to the Protocol that require Atlas edits, and generally requires both a Governance Poll and an Executive Vote.","contentHash":"7145ee8065a504d01d76ac7623806afe55482360e756f883a9f9027fdcd5f835","addressRefs":[]},"830b65d8-9a05-4960-a41f-7309d1b07bbb":{"id":"830b65d8-9a05-4960-a41f-7309d1b07bbb","doc_no":"A.1.11.1.3.0.3.3","title":"Upcoming Executive Vote - Element Annotation","type":"Annotation","depth":5,"parentId":"22508894-e015-4f7c-9ee8-24ac13756d31","order":891,"content":"Successfully polled changes to the Sky Protocol are included in an Executive Vote that is typically conducted within approximately 30 days of the poll passing. The exact timing is dependent on the decisions made by the Core Facilitator and the Spell teams.","contentHash":"24566fb15453becddc99114bfd700f3380e1000d4cf16edd7b85f920cabcab1b","addressRefs":[]},"ad4fc5d1-ea5e-4270-9f8b-0a8f534598b8":{"id":"ad4fc5d1-ea5e-4270-9f8b-0a8f534598b8","doc_no":"A.1.11.1.4","title":"Executive Vote Contingencies","type":"Core","depth":4,"parentId":"999e4aff-e61b-4097-87a8-153afae5098b","order":892,"content":"The subdocuments herein define contingencies related to Executive Votes.","contentHash":"f15511b86a06080b06c256422cba509ad8d5087578ac20c5e0afcdb39d0aa5f6","addressRefs":[]},"de178e9a-b4b6-4103-82fc-e353aea89f2c":{"id":"de178e9a-b4b6-4103-82fc-e353aea89f2c","doc_no":"A.1.11.1.4.1","title":"Executive Vote Cadence","type":"Core","depth":5,"parentId":"ad4fc5d1-ea5e-4270-9f8b-0a8f534598b8","order":893,"content":"The Executive Vote occurs approximately every two weeks, although this cadence can vary based on decisions made by the Core Facilitator and the current Spell team.","contentHash":"05914401272abeca7a23e97a578091ade25d64ec3fecf71cb0cbd2a24fe48d83","addressRefs":[]},"2946ed2d-b027-4aea-a37b-b7c58dd75f56":{"id":"2946ed2d-b027-4aea-a37b-b7c58dd75f56","doc_no":"A.1.11.1.4.1.0.3.1","title":"Current Spell Team - Element Annotation","type":"Annotation","depth":6,"parentId":"de178e9a-b4b6-4103-82fc-e353aea89f2c","order":894,"content":"The element \"current Spell team\" refers to the group of people who are presently working on a given Spell. Members of the Spell team may perform a crafter role or a reviewer role. The \"current Spell team\" does not include the \"Spell roster\", which latter is defined as the group of people from which Spell team members for a given Spell are selected.","contentHash":"95de95d5900183993394c440d7b50c8e050f6e8f752bbe2651f9aa8a02786f72","addressRefs":[]},"1b54a173-547e-4f6a-8e09-61b9ce73f506":{"id":"1b54a173-547e-4f6a-8e09-61b9ce73f506","doc_no":"A.1.11.1.4.2","title":"Postponement Of Executive Vote","type":"Core","depth":5,"parentId":"ad4fc5d1-ea5e-4270-9f8b-0a8f534598b8","order":895,"content":"A scheduled Executive Vote can be postponed if deemed necessary by the Core Facilitator and the current Spell team.","contentHash":"50c71a1b1daf99b2a4dc4c6bbf703447fdf46cb5fa7344ce3752b1e02cd1728d","addressRefs":[]},"5e035410-3bab-4434-aa57-975e746ed0e4":{"id":"5e035410-3bab-4434-aa57-975e746ed0e4","doc_no":"A.1.11.1.4.2.0.3.1","title":"Current Spell Team - Element Annotation","type":"Annotation","depth":6,"parentId":"1b54a173-547e-4f6a-8e09-61b9ce73f506","order":896,"content":"The element \"current Spell team\" refers to the group of people who are presently working on a given Spell. Members of the Spell team may perform a crafter role or a reviewer role. The \"current Spell team\" does not include the \"Spell roster\", which latter is defined as the group of people from which Spell team members for a given Spell are selected.","contentHash":"95de95d5900183993394c440d7b50c8e050f6e8f752bbe2651f9aa8a02786f72","addressRefs":[]},"1e89af32-19c5-423d-be30-a1b2f7a98c1f":{"id":"1e89af32-19c5-423d-be30-a1b2f7a98c1f","doc_no":"A.1.11.1.4.3","title":"Additional Executive Votes","type":"Core","depth":5,"parentId":"ad4fc5d1-ea5e-4270-9f8b-0a8f534598b8","order":897,"content":"Additional Executive Votes outside the regular schedule may be introduced if deemed necessary by the Core Facilitator and the current Spell team.","contentHash":"cba20b061a804850cd0564aee720cff4f31472255695b849a68e4e12401fe301","addressRefs":[]},"95b3197a-0e14-4a9f-82b7-d3af39c58e34":{"id":"95b3197a-0e14-4a9f-82b7-d3af39c58e34","doc_no":"A.1.11.1.4.3.0.3.1","title":"Current Spell Team - Element Annotation","type":"Annotation","depth":6,"parentId":"1e89af32-19c5-423d-be30-a1b2f7a98c1f","order":898,"content":"The element \"current Spell team\" refers to the group of people who are presently working on a given Spell. Members of the Spell team may perform a crafter role or a reviewer role. The \"current Spell team\" does not include the \"Spell roster\", which latter is defined as the group of people from which Spell team members for a given Spell are selected.","contentHash":"95de95d5900183993394c440d7b50c8e050f6e8f752bbe2651f9aa8a02786f72","addressRefs":[]},"b0b1243a-5a27-4e04-8a4e-2098047f1ccd":{"id":"b0b1243a-5a27-4e04-8a4e-2098047f1ccd","doc_no":"A.1.11.1.4.4","title":"Decision To Not Publish Executive Vote","type":"Core","depth":5,"parentId":"ad4fc5d1-ea5e-4270-9f8b-0a8f534598b8","order":899,"content":"If there are no substantive changes due to be made to the Sky Protocol, the Core Facilitator, in conjunction with the Spell teams, may opt not to publish an Executive Vote. This decision should be announced and justified on the Sky Forum.","contentHash":"ea88f35a29370178e176bff6ba50339654b2b1ae41f7154bdbb057d61f7567cc","addressRefs":[]},"ef10f4bb-fec7-4c43-b0c2-1c8429114db7":{"id":"ef10f4bb-fec7-4c43-b0c2-1c8429114db7","doc_no":"A.1.11.1.4.4.0.4.1","title":"Spell Teams - All Recognized Spell Teams Can Participate","type":"Action Tenet","depth":6,"parentId":"b0b1243a-5a27-4e04-8a4e-2098047f1ccd","order":900,"content":"The element \"Spell teams\" indicates that the entire Spell roster can participate in the decision described in the Target Document. The Spell roster is defined as all Spell team members authorized to perform Spell crafting and Spell reviewing services for Sky Core.","contentHash":"ad83ae0214502ba8aafc2ea52f0dac0068691cf2e2ed24fd1b9420a58301d3e4","addressRefs":[]},"2ef63f36-5550-420a-96ee-a99c09451afb":{"id":"2ef63f36-5550-420a-96ee-a99c09451afb","doc_no":"A.1.11.1.5","title":"Core Facilitator’s Authority To Create Proposals","type":"Core","depth":4,"parentId":"999e4aff-e61b-4097-87a8-153afae5098b","order":901,"content":"The Core Facilitator may create proposals using the Weekly Governance Cycle to enable them to fulfill their responsibilities.","contentHash":"2318210f969a9d76aedf692bb5bc529a1c9d4afebc9b25edbcde07b8dba4284e","addressRefs":[]},"0d0e2e1a-0502-4ee3-bc9d-8bd8ddde19ec":{"id":"0d0e2e1a-0502-4ee3-bc9d-8bd8ddde19ec","doc_no":"A.1.11.1.5.1","title":"Core Facilitator's Role In Adding Housekeeping Items In Executive Votes","type":"Core","depth":5,"parentId":"2ef63f36-5550-420a-96ee-a99c09451afb","order":902,"content":"The Core Facilitator is authorized to add housekeeping items in an Executive Vote pursuant to the procedure defined in [A.1.11.1.5.1.2 - Process for Adding Housekeeping Item In Executive Vote](2d165c27-5daf-4a84-af8c-7c36f5de03d2). The Core Facilitator can propose housekeeping items of their own accord; or, they can do so in consultation with the Spell teams.\n\nWhere housekeeping items are proposed by the Spell teams, the Core Facilitator must always conduct an independent assessment of the justification for, and security risks associated with, the housekeeping items. After the proposed housekeeping items have passed this independent assessment, the Core Facilitator may propose adding these items in an Executive Vote pursuant to the procedure defined in [A.1.11.1.5.1.2 - Process for Adding Housekeeping Item In Executive Vote](2d165c27-5daf-4a84-af8c-7c36f5de03d2).","contentHash":"1ed09bc7fae0e018f3568f2926b6d721ee0f18871d4f86c1e81cfbe4163e0dec","addressRefs":[]},"7648bf12-d600-4e0d-807b-5eb18e8d0f4f":{"id":"7648bf12-d600-4e0d-807b-5eb18e8d0f4f","doc_no":"A.1.11.1.5.1.1","title":"Definition Of Housekeeping Items","type":"Core","depth":6,"parentId":"0d0e2e1a-0502-4ee3-bc9d-8bd8ddde19ec","order":903,"content":"Housekeeping items are defined as maintenance and record-keeping actions necessary to the correct functionality of the Sky Protocol. Housekeeping items do not include actions that modify risk parameters or introduce new elements into the protocol.\n\nExamples of housekeeping items include, but are not limited to, (1) cleaning up technical debt, (2) updating the Chainlog, and (3) cancelling payment streams that are no longer used.","contentHash":"9a4ce51e01d635c9e0151f8e23aebcbcd5003f45b532fbbad9e00bdff9a2fec0","addressRefs":[]},"2d165c27-5daf-4a84-af8c-7c36f5de03d2":{"id":"2d165c27-5daf-4a84-af8c-7c36f5de03d2","doc_no":"A.1.11.1.5.1.2","title":"Process for Adding Housekeeping Item In Executive Vote","type":"Core","depth":6,"parentId":"0d0e2e1a-0502-4ee3-bc9d-8bd8ddde19ec","order":904,"content":"Housekeeping items can be directly included in Executive Votes without a Governance Poll through the following process. The Core Facilitator must first create a post on the Sky Forum detailing the housekeeping items and the rationale for their inclusion. The Core Facilitator must request a confirmation of the technical accuracy of the housekeeping items from the technical Ecosystem Actor (or Spell team) who is leading Spell development for the pertinent Executive Vote. The Technical Ecosystem Actor (Spell team) must reply to the Forum Post confirming the accuracy of the housekeeping item.","contentHash":"6cb266941396dee976d1b50dd0d636e02c81e10653e5262bc4b74e0b868ecb8d","addressRefs":[]},"fa682e4f-eb5a-4af2-920d-3c1da51987d8":{"id":"fa682e4f-eb5a-4af2-920d-3c1da51987d8","doc_no":"A.1.11.1.0.3.1","title":"Operational Weekly Cycle - Element Annotation","type":"Annotation","depth":4,"parentId":"999e4aff-e61b-4097-87a8-153afae5098b","order":905,"content":"Previously, the \"Operational Weekly Cycle\" was called simply the \"Weekly Governance Cycle.\" With the introduction of the Atlas Edit Weekly Cycle, it became necessary to divide the Weekly Governance Cycle into two (2) subtypes: the Atlas Edit Weekly Cycle and the Operational Weekly Cycle. These two subtypes differ in terms of the permissioned parties authorized to trigger a proposal and the governance mechanisms involved. For instance, the Atlas Edit Weekly Cycle implements edits to the Atlas via the mechanism of a Governance Poll only. The Operational Weekly Cycle can action changes to the Protocol that require Atlas edits, and generally requires both a Governance Poll and an Executive Vote.","contentHash":"7145ee8065a504d01d76ac7623806afe55482360e756f883a9f9027fdcd5f835","addressRefs":[]},"14e99d92-71fc-44d9-9dbf-933bce2e1b32":{"id":"14e99d92-71fc-44d9-9dbf-933bce2e1b32","doc_no":"A.1.11.2","title":"Atlas Edit Weekly Cycle","type":"Section","depth":3,"parentId":"83edd4e1-692e-4566-a415-b8f272c33c5e","order":906,"content":"This Section defines the Atlas Edit Weekly Cycle which provides a predictable framework for weekly edits to the Atlas. The Atlas Edit Weekly Cycle is implemented via Governance Polls.","contentHash":"8fa5f52c0c530459af2543f733bc8fbb09d2bffd5e7145c8ee4c3bf74e846c5e","addressRefs":[]},"3aa3aa8a-0097-46a4-a89a-2db46f7cb2af":{"id":"3aa3aa8a-0097-46a4-a89a-2db46f7cb2af","doc_no":"A.1.11.2.1","title":"Cycle Breakdown","type":"Core","depth":4,"parentId":"14e99d92-71fc-44d9-9dbf-933bce2e1b32","order":907,"content":"The subdocuments herein provide a breakdown of the Atlas Edit Weekly Cycle.","contentHash":"2d0b88f4202e77ad771ba9696536d5489676e144a16f8f2329c2335c6a05827f","addressRefs":[]},"6c52610b-b9f0-49a3-8014-d1f51543dcdf":{"id":"6c52610b-b9f0-49a3-8014-d1f51543dcdf","doc_no":"A.1.11.2.1.1","title":"Proposals In General","type":"Core","depth":5,"parentId":"3aa3aa8a-0097-46a4-a89a-2db46f7cb2af","order":908,"content":"In the transition to Endgame, the Atlas can be edited through the submission of an Atlas Edit Weekly Cycle Proposal (also \"Weekly Cycle Proposal\" or \"Proposal\"). Multiple amendments to multiple components of the Atlas are allowed to be submitted in a single Weekly Cycle Proposal. A single Weekly Cycle Proposal may seek to remove multiple components of the Atlas.\n\nAtlas Edits must always adhere to the Spirit of the Atlas and remain within the bounds of Universal Alignment.","contentHash":"e1b97b73e8592454d46da7ae9a1bf6f1cf6e623c454018318a7bab3c3ce50546","addressRefs":[]},"8139e05f-dbe9-4324-ba87-53248d7ca1b5":{"id":"8139e05f-dbe9-4324-ba87-53248d7ca1b5","doc_no":"A.1.11.2.1.1.0.4.1","title":"In The Transition To Endgame - Immutable Documents Can Be Amended","type":"Action Tenet","depth":6,"parentId":"6c52610b-b9f0-49a3-8014-d1f51543dcdf","order":909,"content":"Currently, in the transition to Endgame, the Immutable Documents (Articles and Sections) can be amended pursuant to [A.1.11 - Weekly Governance Cycle](83edd4e1-692e-4566-a415-b8f272c33c5e) and [A.1.12 - Monthly Governance Cycle](7f2ba62c-9b3b-4df6-aa16-189a749cffa3). Once the Sky Ecosystem enters the Endgame State, the Immutable Documents of the Atlas will be forever locked down and cannot be changed.","contentHash":"f5a52786b1a0c369582c8f774991bc2adf7a13e94028d90c4ef32b20b9bab6aa","addressRefs":[]},"2891a392-d5ca-45a5-80ca-ad2afaf5baa1":{"id":"2891a392-d5ca-45a5-80ca-ad2afaf5baa1","doc_no":"A.1.11.2.1.2","title":"Origination Via Forum Post","type":"Core","depth":5,"parentId":"3aa3aa8a-0097-46a4-a89a-2db46f7cb2af","order":910,"content":"The Author of an Atlas Edit Weekly Cycle Proposal (also \"Weekly Cycle Proposal\" or \"Proposal\") must post the Proposal in the Sky Forum in the appropriate category and signal their intent to submit the Proposal to the Weekly Cycle.","contentHash":"ae6c164b217e5055919c16160c1d2e2e98ea677e8472932c9d42682de49fc3a8","addressRefs":[]},"cef09d74-efc6-45cc-a75b-1132dae9e743":{"id":"cef09d74-efc6-45cc-a75b-1132dae9e743","doc_no":"A.1.11.2.1.3","title":"Triggering Requirement","type":"Core","depth":5,"parentId":"3aa3aa8a-0097-46a4-a89a-2db46f7cb2af","order":911,"content":"An Atlas Edit Weekly Cycle Proposal (also \"Weekly Cycle Proposal\" or \"AEW Proposal\") can proceed to a vote only if it is triggered by a Ranked Delegate whose AD Buffer contains at least the Triggering Threshold (see [A.1.6.4.4.2.1.1 - Triggering Threshold](2c2b201e-b95f-4852-8e76-6dfe4c3c6a4f)) at the time of triggering the Proposal. The Core Facilitator is responsible for confirming that these requirements are met.\n\nA Ranked Delegate may trigger a Proposal they authored, provided they meet the Triggering Threshold. To trigger a Proposal, the Ranked Delegate must post a reply to the Author's Weekly Cycle Proposal on the Forum. The Ranked Delegate’s post should signal their intent to trigger the Weekly Cycle Proposal.\n\nWhere more than one Ranked Delegate posts an intention to trigger a Weekly Cycle Proposal, the first Ranked Delegate to post a reply to the Author’s Forum post shall be treated as the triggering Ranked Delegate.\n\nIf the Weekly Cycle Proposal is subsequently voted down, the triggering Ranked Delegate loses an amount of USDS from their AD Buffer equal to the Triggering Threshold.","contentHash":"31714ff5bd30b3bf6a00a0bc692d2760793f988f743d155deb910e3e2e1f31bf","addressRefs":[]},"fa3e83ff-02ee-4e24-b88a-660585c6d8f4":{"id":"fa3e83ff-02ee-4e24-b88a-660585c6d8f4","doc_no":"A.1.11.2.1.3.0.4.1","title":"Ranked Delegate Loss Of Rank After Triggering Proposal Is Inconsequential","type":"Action Tenet","depth":6,"parentId":"cef09d74-efc6-45cc-a75b-1132dae9e743","order":912,"content":"A Weekly Cycle Proposal is considered correctly triggered when the triggering Aligned Delegate is a Ranked Delegate with at least the Triggering Threshold in their AD Buffer at the time of triggering the Proposal. It is inconsequential if, after triggering the Proposal, the Ranked Delegate loses their Ranked Delegate rank.","contentHash":"f164fe069cb385ce364922d5ef56fed1eff77707fcbfc7c8a7fc57489cd693a5","addressRefs":[]},"9079bf46-34b8-4ba5-a856-7f96f2093acb":{"id":"9079bf46-34b8-4ba5-a856-7f96f2093acb","doc_no":"A.1.11.2.1.3.0.4.1.1.1","title":"Ranked Delegate Triggers Proposal And Loses Ranked Delegate Rank Immediately Thereafter","type":"Scenario","depth":6,"parentId":"cef09d74-efc6-45cc-a75b-1132dae9e743","order":913,"content":"**Description**:\n\nEntity is a Ranked Delegate with at least the Triggering Threshold in their AD Buffer. Entity triggers a Weekly Cycle Proposal. Immediately thereafter, Entity loses their Ranked Delegate rank. The Core Facilitator continues to prepare a Governance Poll for the Proposal.\n\n**Finding**:\n\nAligned as to Entity. Aligned as to the Core Facilitator.\n\n**Additional Guidance**:\n\nThe fact that Entity lost their Ranked Delegate rank after triggering the Proposal is inconsequential. Entity satisfied the requirement of being a Ranked Delegate with at least the Triggering Threshold in their AD Buffer at the time of triggering the Proposal, and thus the Proposal was properly triggered. The Core Facilitator acted correctly to prepare a Governance Poll for the Proposal in accord with the process definition for the Atlas Edit Weekly Cycle.","contentHash":"f1711cbc42e52ffba65cea1c68bf84b6af48bd32963562c93d8f51a4fa16592d","addressRefs":[]},"bba7fb85-c652-4af2-b7ff-0257532be488":{"id":"bba7fb85-c652-4af2-b7ff-0257532be488","doc_no":"A.1.11.2.1.3.0.4.2","title":"Ranked Delegates Must Stake Their AD Buffer To Trigger Weekly Cycle Proposals","type":"Action Tenet","depth":6,"parentId":"cef09d74-efc6-45cc-a75b-1132dae9e743","order":914,"content":"To deter spurious or misaligned proposals, Ranked Delegates must \"stake\" a portion of their AD Buffer to trigger a Proposal. A Ranked Delegate can trigger a Weekly Cycle Proposal only if their AD Buffer contains at least the Triggering Threshold at the time of triggering the Proposal. This \"staking\" requirement of an amount of USDS equal to the Triggering Threshold remains in effect until the triggered Proposal is fully resolved - that is, until either (1) the Proposal is rejected by the Core Facilitator for misalignment, or (2) a Sky Governance vote on the Proposal concludes in an approval or rejection. If the Proposal is voted down or rejected for misalignment, the RD will lose an amount of USDS from their AD Buffer equal to the Triggering Threshold.","contentHash":"6c8f12ebe5090467e021d28ec6ba6819bd8a665b95e345f6d54c1c7387cca0f3","addressRefs":[]},"1ebcda5d-5a10-4e78-ba52-5772df38cc56":{"id":"1ebcda5d-5a10-4e78-ba52-5772df38cc56","doc_no":"A.1.11.2.1.3.0.4.2.1.1","title":"Delay In Payment To Ranked Delegate Triggering Proposal","type":"Scenario","depth":6,"parentId":"cef09d74-efc6-45cc-a75b-1132dae9e743","order":915,"content":"**Description**:\n\nEntity is a Ranked Delegate with at least the Triggering Threshold in their AD Buffer. Entity triggers a Weekly Cycle Proposal. Immediately thereafter, Entity loses their Ranked Delegate rank. Three days later, before the Proposal has been voted on, the Core Facilitator distributes compensation to other Aligned Delegates but does not distribute compensation to Entity.\n\n**Finding**:\n\nAligned\n\n**Additional Guidance**:\n\nPaying out the AD Buffer would have led to Entity's AD Buffer dropping below the required Triggering Threshold while the Proposal was still unresolved. In this Scenario, the triggering AD cannot receive payout from the AD Buffer until the triggered Proposal is voted on and approved by Sky Governance. Assuming that the Proposal is approved, the Core Facilitator is authorized to disburse the entire contents of the AD Buffer to the triggering AD in the next AD compensation cycle. However, if the Proposal is rejected by the Core Facilitator for misalignment or voted down by Sky Governance, the triggering AD loses an amount of USDS from their AD Buffer equal to the Triggering Threshold.","contentHash":"fec4d91242d8aeb0e9943e2317ab7aa1f030f5f2ac30edf95d2372805ce71c80","addressRefs":[]},"f7e857e0-9de6-47ee-8817-966cb46ac9d6":{"id":"f7e857e0-9de6-47ee-8817-966cb46ac9d6","doc_no":"A.1.11.2.2","title":"Preparation And Publication of Governance Poll","type":"Core","depth":4,"parentId":"14e99d92-71fc-44d9-9dbf-933bce2e1b32","order":916,"content":"An Atlas Edit Weekly Cycle Proposal should be posted to the Forum by Friday at 8:00 am UTC to ensure the Core Facilitator has sufficient time to prepare the needed polls for the following Monday.\n\nEvery Monday, the Atlas Edit Weekly Cycle is carried out via Governance Polls. The Core Facilitator must publish the set of Governance Polls to the community Github and the official Voting Portal.\n\nThe Polls run for three days. Successful polls trigger direct edits to the Atlas.","contentHash":"fc4901a504e373deee04c05f11864bcf013cbd5a006364affa1a1de766d39519","addressRefs":[]},"94856ced-5c37-42e0-a756-0fa2ccd73180":{"id":"94856ced-5c37-42e0-a756-0fa2ccd73180","doc_no":"A.1.11.2.3","title":"Rejecting A Proposal For Misalignment","type":"Core","depth":4,"parentId":"14e99d92-71fc-44d9-9dbf-933bce2e1b32","order":917,"content":"The Core Facilitator can reject an Atlas Edit Weekly Cycle Proposal if they deem it to be misaligned. If the Facilitator rejects an Atlas Edit Weekly Cycle Proposal for misalignment, the Ranked Delegate who triggered the poll loses their AD buffer.","contentHash":"7e0e3e8e005c0d19152d9d9848dcb0209bc5320d683add5376114cf57b96b621","addressRefs":[]},"824e78be-2c90-46e5-9fde-3ecd5d9d7665":{"id":"824e78be-2c90-46e5-9fde-3ecd5d9d7665","doc_no":"A.1.11.2.3.0.4.1","title":"Unanimity Is Not Required To Block Proposal For Misalignment","type":"Action Tenet","depth":5,"parentId":"94856ced-5c37-42e0-a756-0fa2ccd73180","order":918,"content":"Unanimity is not required among the Core Facilitators to block an Atlas Edit Weekly Cycle Proposal for misalignment.","contentHash":"3652e302066da4896cc706cd7616abac1a0efb4d7a3e9ed8ab13c191bbb3a683","addressRefs":[]},"863b3e56-76c5-4448-b2b0-3b5e2d26a3fa":{"id":"863b3e56-76c5-4448-b2b0-3b5e2d26a3fa","doc_no":"A.1.11.2.4","title":"Minimum Positive Participation","type":"Core","depth":4,"parentId":"14e99d92-71fc-44d9-9dbf-933bce2e1b32","order":919,"content":"Atlas Edit Weekly Cycle Proposals must have at least 480,000,000 SKY equivalents of Yes votes to be accepted.","contentHash":"fc5c38db40ad28be429e7585d5c19824767e9c2f250095c747cf3e5d092c01e8","addressRefs":[]},"9f8be4ba-170e-44c3-887e-c577c7b9394f":{"id":"9f8be4ba-170e-44c3-887e-c577c7b9394f","doc_no":"A.1.11.2.5","title":"Reconciliation Process","type":"Core","depth":4,"parentId":"14e99d92-71fc-44d9-9dbf-933bce2e1b32","order":920,"content":"If multiple Atlas Edit Weekly Cycle Proposals editing the same component of the Atlas are approved by voters in the same Governance Cycle, the Reconciliation Process documented herein must be followed.","contentHash":"d29492e7e9a674003a3c19858f3da93b3c214783c67453e2091cf0f6816e1ee2","addressRefs":[]},"aa76a7ea-daba-406b-af52-4fa8da2277d3":{"id":"aa76a7ea-daba-406b-af52-4fa8da2277d3","doc_no":"A.1.11.2.5.1","title":"Language Disallowing Simultaneous Edits Not Allowed","type":"Core","depth":5,"parentId":"9f8be4ba-170e-44c3-887e-c577c7b9394f","order":921,"content":"Atlas Edit Weekly Cycle Proposals cannot include language that aims to prevent other Atlas Edit Weekly Cycle Proposals from editing the same component of the Atlas within the same Governance Cycle.","contentHash":"93f933d78b8363a26cb031fc7544b1d2f1d859c45d13c64a56db402cdae19265","addressRefs":[]},"edb3b979-b7b6-4728-9c26-cf768d8827ea":{"id":"edb3b979-b7b6-4728-9c26-cf768d8827ea","doc_no":"A.1.11.2.5.2","title":"Simultaneous Edit Reconciliation Process Definition","type":"Core","depth":5,"parentId":"9f8be4ba-170e-44c3-887e-c577c7b9394f","order":922,"content":"Where voters approve multiple Atlas Edit Weekly Cycle Proposals that seek to edit the same component or components of the Atlas within the same Governance Cycle, the process described below must be followed.\n\nThis process only applies to the specific components that are being simultaneously edited. Other amended components that do not have edits in simultaneous proposals may be merged, unless they are dependent on the component that does have simultaneous edits.\n\nWhere simultaneous edits are non-conflicting / logically compatible: the Core Facilitator will consolidate them into a single edit either by stitching them together in the affected component or by stringing one after the other as a new component. Any action taken by the Core Facilitator in this regard will be documented publicly and should be available for examination prior to the end date of the relevant polls.\n\nWhere simultaneous edits are conflicting / logically incompatible and cannot be coherently reconciled: it falls to voters to decide which of the conflicting Atlas Edit Weekly Cycle Proposals they wish to accept. If there are two conflicting Atlas Edit Weekly Proposals, a subsequent binary vote actioned via a single Reconciliation Process Poll is appropriate.\n\nIn the event there are more than two conflicting Atlas Edit Weekly Cycle Proposals, the Core Facilitator may choose a suitable polling method that allows voters to choose between multiple options. The difference between the conflicting amendments must be clearly presented so that voters can make an informed choice on their preferred option.\n\nA Reconciliation Process Poll will take place during the Operational Weekly Cycle immediately following the closure of the originating polls. The Reconciliation Process Poll will last for three days.","contentHash":"e84dd91ecb6fbe84e970db6a63b94f261dbb75e0633d32f5046588dd64a02ecb","addressRefs":[]},"7f2ba62c-9b3b-4df6-aa16-189a749cffa3":{"id":"7f2ba62c-9b3b-4df6-aa16-189a749cffa3","doc_no":"A.1.12","title":"Monthly Governance Cycle","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":923,"content":"This Article regulates the Monthly Governance Cycle, which provides a predictable monthly framework by which Sky Governance decisions are made.","contentHash":"02f5ffa0cdb212b33d5065cdaee0d2effe534649d52a6324a9d7c0561b5f8bc5","addressRefs":[]},"6c0810e2-390d-4efb-8b31-f36a7f6e1a05":{"id":"6c0810e2-390d-4efb-8b31-f36a7f6e1a05","doc_no":"A.1.12.1","title":"Calendar Exceptions","type":"Section","depth":3,"parentId":"7f2ba62c-9b3b-4df6-aa16-189a749cffa3","order":924,"content":"Due to the multitude of cultural and religious holidays occurring in and around the month of December, there will be no Monthly Governance Cycle in the December of each year.","contentHash":"c207d86f8907b94b685d4abbbd510404c6caf2bf4e92cae638975b96d03171d9","addressRefs":[]},"d2cbddd2-58ef-4311-a71d-d2c340364cb5":{"id":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","doc_no":"A.1.12.2","title":"Atlas Edit Monthly Cycle","type":"Section","depth":3,"parentId":"7f2ba62c-9b3b-4df6-aa16-189a749cffa3","order":925,"content":"This Section defines the Atlas Edit Monthly Cycle, which provides a predictable framework for monthly edits to the Atlas. The Atlas Edit Monthly Cycle is implemented via the Atlas Edit Proposal (AEP) framework.\n\nIn the transition to Endgame, the Atlas can be edited through the submission of an AEP. Multiple amendments to multiple components of the Atlas are allowed to be submitted in a single AEP. A single AEP may seek to remove multiple components of the Atlas.\n\nAEPs must always adhere to the Spirit of the Atlas and remain within the bounds of Universal Alignment.","contentHash":"213c5d1f83e44195a905bd7bf038668937504835f9401dd32e4dd98a2d943b07","addressRefs":[]},"c3c4b7c8-0979-48f7-9ba8-9565d71334b6":{"id":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","doc_no":"A.1.12.2.1","title":"Cycle Breakdown","type":"Core","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":926,"content":"The subdocuments herein define infrastructure and processes for the Atlas Edit Monthly Cycle.","contentHash":"41b56588044fd5ce2cdc1b850b21c79f6e8380f06336c18cb5bc8e3bebefd9fd","addressRefs":[]},"e10e40b3-a942-411d-9646-129a5f3f984a":{"id":"e10e40b3-a942-411d-9646-129a5f3f984a","doc_no":"A.1.12.2.1.1","title":"Origination","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":927,"content":"The author of an Atlas Edit Monthly Cycle proposal (\"proposal\", \"Atlas Edit Proposal\", \"AEP\", \"Monthly Cycle Proposal\", or \"AEM Proposal\") must post the proposal in the Sky Forum under the appropriate category.","contentHash":"3e22040d611b48e4e9a55beaf3a9bedbc205ea39655d9aa51dc5fdf661af7f57","addressRefs":[]},"7bbfd3b1-99b5-4c60-9292-68d776e03886":{"id":"7bbfd3b1-99b5-4c60-9292-68d776e03886","doc_no":"A.1.12.2.1.2","title":"Triggering Requirement","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":928,"content":"An Atlas Edit Monthly Cycle Proposal can proceed to verification by the Core Facilitator only if it is triggered by a Ranked Delegate whose AD Buffer contains at least the Triggering Threshold (see [A.1.6.4.4.2.1.1 - Triggering Threshold](2c2b201e-b95f-4852-8e76-6dfe4c3c6a4f)) at the time of triggering the Proposal. The Core Facilitator is responsible for confirming that these requirements are met.\n\nA Ranked Delegate may trigger a Proposal they authored, provided they meet the Triggering Threshold. To trigger a Proposal, the Ranked Delegate must post a reply to the Author's Monthly Cycle Proposal on the Forum. The Ranked Delegate should indicate their intent to trigger the Monthly Cycle Proposal.\n\nWhere more than one Ranked Delegate posts an intention to trigger a Monthly Cycle Proposal, the first Ranked Delegate to post a reply to the Author’s Forum post shall be treated as the triggering Ranked Delegate.\n\nIf the Proposal is edited subsequent to being triggered, the Proposal must be triggered again before proceeding further in the Atlas Edit Monthly Cycle process.\n\nIf the Monthly Cycle Proposal is voted down, the triggering Ranked Delegate loses an amount of USDS from their AD Buffer equal to the Triggering Threshold.","contentHash":"a94a088d18d4d41f3ff49bc8eea42c6ae80775221ae032f208f11579b0903031","addressRefs":[]},"05cf14c1-621a-4e86-bab6-0fcbdca12666":{"id":"05cf14c1-621a-4e86-bab6-0fcbdca12666","doc_no":"A.1.12.2.1.3","title":"Core Facilitator’s Initial Verification","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":929,"content":"After the Atlas Edit Proposal is triggered, the Core Facilitator must verify that the Atlas Edit Proposal follows the template specified in [A.1.12.2.3 - Atlas Edit Proposal Template](3af371ae-cc75-47c8-bd51-9446d68afea7).\n\nThe Core Facilitator must also verify that the AEP has been submitted to the Atlas Github repository with a Pull Request by the AEP Author. Alternatively, the AEP author can request the Core Facilitator to create the Pull Request for them.\n\nIf the AEP is successfully verified, the Core Facilitator must\n\n- Approve the AEP and assign it a formal #\n- Update the Preamble to the AEP\n- Merge the Pull Request","contentHash":"e881878ca98080170d4df096411d4a14c11b25af7add3ec010d7bc020fa176cb","addressRefs":[]},"45ced7a3-f362-43c8-a053-d4360d94260a":{"id":"45ced7a3-f362-43c8-a053-d4360d94260a","doc_no":"A.1.12.2.1.4","title":"Request for Comments","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":930,"content":"After the Atlas Edit Proposal is verified, a period of reviewing by the community and attendant redrafting begins. The minimum duration of this period is determined by the Feedback Period and the Frozen Period.\n\nThe Feedback Period is the minimum amount of time within which the community can give feedback in response to an Atlas Edit Proposal before it can advance to Formal Submission.\n\nThe Frozen Period is the minimum amount of time during which an Atlas Edit Proposal must remain unchanged before it can advance to Formal Submission.\n\nThese periods can overlap.","contentHash":"d4370334a2b0a1afe93949253cb485573ee8069eeb7dfd975bb76e7ccd9579d2","addressRefs":[]},"8c1f48d7-2393-4749-9599-fb6e98cdc155":{"id":"8c1f48d7-2393-4749-9599-fb6e98cdc155","doc_no":"A.1.12.2.1.5","title":"Fulfilled Feedback Period Requirements","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":931,"content":"After the Atlas Edit Proposal has fulfilled the requirements for a community feedback period, it is ready for Formal Submission.","contentHash":"adff44e24917b1378063fc3f683f3ac87d21d2c6b2df0e27aa6451202e2f8870","addressRefs":[]},"ffd09668-6088-4331-b8ee-bf8557e767eb":{"id":"ffd09668-6088-4331-b8ee-bf8557e767eb","doc_no":"A.1.12.2.1.6","title":"Submitting To Formal Submission","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":932,"content":"When the Atlas Edit Proposal is ready for Formal Submission, the AEP Author submits their AEP to the Monthly Governance Cycle by posting a Forum comment that states \"Formal Submission\". This can only be done within the Formal Submission Window of a Monthly Governance Cycle. The Formal Submission Window is a two-day window that starts at 00:00 UTC on the first Monday of the Monthly Governance Cycle and lasts until 23:59 UTC on Tuesday the next day.","contentHash":"5c91a159355f321c9c0a213dc1b47ed24c4171d7c3b09bc2141c910e6b5cdd88","addressRefs":[]},"7ba721b9-73f4-4080-a076-f6d1ceb519b4":{"id":"7ba721b9-73f4-4080-a076-f6d1ceb519b4","doc_no":"A.1.12.2.1.7","title":"Core Facilitator’s Review","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":933,"content":"The Core Facilitator is required to review all Atlas Edit Proposals (AEPs) submitted for Formal Submission to determine whether they are misaligned.","contentHash":"1558a7abff087f4cb9ff95dbfc81e4887c4058f1b29639ceb8cba50cc527e4b8","addressRefs":[]},"51dc4c3b-94cf-4fbc-bff2-648250a1f1ce":{"id":"51dc4c3b-94cf-4fbc-bff2-648250a1f1ce","doc_no":"A.1.12.2.1.7.1","title":"Procedure For Blocking AEP For Misalignment","type":"Core","depth":6,"parentId":"7ba721b9-73f4-4080-a076-f6d1ceb519b4","order":934,"content":"An Atlas Edit Proposal can be blocked by the Core Facilitator for misalignment. Unanimity among the Core Facilitators is not required to block an AEP for misalignment.\n\nWhere an AEP has been blocked for misalignment, the Core Facilitator must update the AEP status as \"Rejected-Misaligned\".\n\nEach Core Facilitator should issue a written advisory opinion containing their findings/reasoning either supporting or rejecting the blocking of the AEP.","contentHash":"a529ae9bba763694f1161aed668901fc564bdc331b6819b3b9f928c73aac8426","addressRefs":[]},"90932951-629d-449f-ae15-fd459b454da6":{"id":"90932951-629d-449f-ae15-fd459b454da6","doc_no":"A.1.12.2.1.7.2","title":"Resubmitting A Blocked AEP To A Future Monthly Cycle","type":"Core","depth":6,"parentId":"7ba721b9-73f4-4080-a076-f6d1ceb519b4","order":935,"content":"An Atlas Edit Proposal that has been blocked for misalignment can be amended and re-submitted in a future Atlas Edit Monthly Governance Cycle.","contentHash":"80df200fe3be53c528c4d2965d0e64fe142a159245b2cb80e760ef14d3732e90","addressRefs":[]},"523bfc8f-2d8a-4364-8307-7f9a7a764fd6":{"id":"523bfc8f-2d8a-4364-8307-7f9a7a764fd6","doc_no":"A.1.12.2.1.7.2.0.4.1","title":"Amended - Blocked AEPs Cannot Be Re-Submitted In Original Form","type":"Action Tenet","depth":6,"parentId":"7ba721b9-73f4-4080-a076-f6d1ceb519b4","order":936,"content":"An AEP that was blocked for misalignment cannot be resubmitted in its original form; it must be edited before it can be formally submitted again to the Monthly Cycle.","contentHash":"f2ba571ad0bf1ad490beb9d5b15c91e7c9bd931b135d5fe3e40efc7c6e6513dc","addressRefs":[]},"9949588a-dad2-4649-a071-ef9c46992895":{"id":"9949588a-dad2-4649-a071-ef9c46992895","doc_no":"A.1.12.2.1.7.3","title":"Update Status","type":"Core","depth":6,"parentId":"7ba721b9-73f4-4080-a076-f6d1ceb519b4","order":937,"content":"If an AEP has passed the Core Facilitator’s review, the Core Facilitator must update the status of the AEP to \"Formal Submission.\"","contentHash":"ff258859e7b89b2c0c0d35c975c30b4245ecd290929b8c3de8b9411c5eee177e","addressRefs":[]},"e00795ef-f741-4946-83f6-a9b3d52e44bc":{"id":"e00795ef-f741-4946-83f6-a9b3d52e44bc","doc_no":"A.1.12.2.1.8","title":"Proposal Enters Monthly Cycle","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":938,"content":"Once an Atlas Edit Proposal has been formally submitted and has passed the Core Facilitator’s review, the AEP enters the Monthly Governance Cycle.","contentHash":"d34a55cee96e0d937990832a3a4ab0edf61e5538802e12fad9959958c79c62c6","addressRefs":[]},"6402ac15-75b4-421b-8541-8221f3a2c2e5":{"id":"6402ac15-75b4-421b-8541-8221f3a2c2e5","doc_no":"A.1.12.2.1.9","title":"Accepted / Rejected Status","type":"Core","depth":5,"parentId":"c3c4b7c8-0979-48f7-9ba8-9565d71334b6","order":939,"content":"The Atlas Edit Proposal is voted on. If it passes, it is officially accepted and given the \"Accepted\" status. If not, the AEP is rejected and given the \"Rejected\" status.","contentHash":"40164860425f4a194e4f00689c0f100e57b1e0f040dea694d348ad90b9650861","addressRefs":[]},"106bd569-4cea-4221-b8e7-a064a9b1c3a6":{"id":"106bd569-4cea-4221-b8e7-a064a9b1c3a6","doc_no":"A.1.12.2.2","title":"Atlas Edit Proposal Requirements","type":"Core","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":940,"content":"The requirements for an Atlas Edit Proposal are defined in the subdocuments herein.","contentHash":"ea3f01a488c840926c28354ba76c90d5519cd7d7e6d76bd71a70f0360feb78b0","addressRefs":[]},"16e06904-4596-4755-9d18-7c25d9e6177b":{"id":"16e06904-4596-4755-9d18-7c25d9e6177b","doc_no":"A.1.12.2.2.1","title":"Atlas Edit Proposal Parameters","type":"Core","depth":5,"parentId":"106bd569-4cea-4221-b8e7-a064a9b1c3a6","order":941,"content":"Atlas Edit Proposals have the following parameters:\n\n- Default Feedback Period: one (1) week\n- Frozen Period: one (1) week\n- Governance Cycle: Monthly","contentHash":"f7387307e151a02d60bc53b8147740b91034232fb53755c7fd1b8c17063ffafa","addressRefs":[]},"b9da67b6-4cc2-4bd9-b6ec-900cd855fa64":{"id":"b9da67b6-4cc2-4bd9-b6ec-900cd855fa64","doc_no":"A.1.12.2.2.2","title":"Frozen Period Requirement","type":"Core","depth":5,"parentId":"106bd569-4cea-4221-b8e7-a064a9b1c3a6","order":942,"content":"The final version of an Atlas Edit Proposal must be posted on Sky Forum seven (7) days before Formal Submission, and cannot move into Formal Submission if it was changed within the last seven (7) days.","contentHash":"2047c522653f00c02c080e85734f22fbd87ad70f885e2b74412c8f350c2e70bb","addressRefs":[]},"3af371ae-cc75-47c8-bd51-9446d68afea7":{"id":"3af371ae-cc75-47c8-bd51-9446d68afea7","doc_no":"A.1.12.2.3","title":"Atlas Edit Proposal Template","type":"Core","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":943,"content":"All Atlas Edit Proposals must use the following template:\n\nPreamble\n\nAEP#: #\nAuthor(s):\nContributors:\nStatus:\nDate Proposed: <yyyy-mm-dd>\nDate Ratified: <yyyy-mm-dd>\nForum URL:\n\nMotivation\n\n- Explain the motivation behind this AEP.\n\nEdited Atlas Documents\n\n- List the Atlas Documents that are being edited. Please include the Portal URL pointing to the specific Atlas Documents to facilitate identification.\n\nEdit Pull Request\n\n- Link to the Pull Request containing the proposed Atlas Edit. The Core Facilitator can create the Pull Request on request.","contentHash":"aab04d23d1e81673976c8ebd131f96914c8f9b5d2eda5bd785d5fb89c3a386d4","addressRefs":[]},"fbbd47b3-8985-42bb-98f4-3e5af582dea1":{"id":"fbbd47b3-8985-42bb-98f4-3e5af582dea1","doc_no":"A.1.12.2.4","title":"Atlas Edit Proposal Statuses","type":"Core","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":944,"content":"An Atlas Edit Proposal can be assigned several different statuses: RFC, Formal Submission, Rejected-Misaligned, Accepted, Rejected, and Obsolete.\n\nRFC (Request For Comments):\nAn AEP is in the Request For Comments Period.\n\nFormal Submission:\nAn AEP has been moved into Formal Submission to the Monthly Governance Cycle.\n\nRejected - Misaligned:\nAn AEP has been blocked by the Core Facilitator from entering the Monthly Cycle due to misalignment.\n\nAccepted:\nAn AEP has been voted on and is officially accepted.\n\nRejected:\nAn AEP has been voted on and is not officially accepted.\n\nObsolete:\nAn AEP is assigned the status Obsolete when:\n\n- an AEP has been superseded or deprecated\n- an AEP has been deferred for over six (6) months\n- an AEP Author has abandoned the proposal and no person has communicated willingness to take over the responsibility of a AEP Author.","contentHash":"985fa66596a0f1a98384efd193939350d6e4efb88cf172a2bd1cce215757a28f","addressRefs":[]},"8eea2827-4d10-4893-92d3-9083be7e9267":{"id":"8eea2827-4d10-4893-92d3-9083be7e9267","doc_no":"A.1.12.2.5","title":"Process Definition","type":"Core","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":945,"content":"The first Monday of each calendar month marks the beginning of the Monthly Governance Cycle.\n\nTime is inclusive and based on UTC (Coordinated Universal Time) and the Gregorian Calendar.\n\n**First Wednesday after the first Monday of the month:**\n\n- The Authors of Atlas Edit Proposals must formally submit their AEP before this Day.\n- The Formal Submission must be done through a message on the Author’s Forum thread that contains the AEP.\n\n**Week 1, Friday**\nAfter reviewing the AEPs, the Core Facilitator must decide whether each submitted AEP warrants moving forward to a Ratification Poll.\n\n**Week 2, Monday**\nThe Core Facilitator publish the set of Ratification Polls. The format of these is defined in [A.1.12.2.6 - Ratification Poll Requirements](13e6da57-ee8e-4593-90f2-698642b1c82f).\n\nRatification Polls are published to the community GitHub, submitted on-chain, and appear on the official Voting Portal.\n\n**Week 4, Monday**\nThe Ratification Polls conclude, and each proposal or set of proposals is marked as either Accepted or Rejected by the Core Facilitator.","contentHash":"57d553d3b9279b33e01e5948dea1f79dab63cd8a454316e5d96003a718b3ee7c","addressRefs":[]},"13e6da57-ee8e-4593-90f2-698642b1c82f":{"id":"13e6da57-ee8e-4593-90f2-698642b1c82f","doc_no":"A.1.12.2.6","title":"Ratification Poll Requirements","type":"Core","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":946,"content":"Ratification Polls under the Atlas Edit Monthly Governance Cycle must meet these requirements:\n\n- Duration: two (2) Weeks.\n- Minimum Positive Participation: 240,000,000 SKY.\n- Type: Binary Poll (yes/no/abstain).\n\nRatification Polls under the Atlas Edit Monthly Governance Cycle must contain:\n\n- Links to a specific version of a single Atlas Edit Proposal within the official Atlas GitHub.\n\nIn order for a Ratification Poll to conclude successfully and the contained proposal(s) moved to Accepted status, triggering an edit of the Atlas, each of the following conditions must be true:\n\n- Yes vote-weight must exceed No vote-weight when the poll closes.\n- Yes vote-weight must exceed the Minimum Positive Participation value of 240,000,000 SKY when the poll closes.","contentHash":"5dc25562c15d3aaf85f7b22badbfeb55357c99a2516780b89bdbe76c7d1dfaea","addressRefs":[]},"535570e7-8548-451f-87f0-edb699373978":{"id":"535570e7-8548-451f-87f0-edb699373978","doc_no":"A.1.12.2.6.1","title":"Revision of Minimum Positive Participation","type":"Core","depth":5,"parentId":"13e6da57-ee8e-4593-90f2-698642b1c82f","order":947,"content":"The Minimum Positive Participation value defined in [A.1.12.2.6 - Ratification Poll Requirements](13e6da57-ee8e-4593-90f2-698642b1c82f) may be modified via a successful Governance Poll under the Operational Weekly Governance Cycle.\n\nIf such a vote is successful, the new Minimum Positive Participation value will come into effect in the _following_ Monthly Governance Cycle. The Minimum Positive Participation value may not be changed for Ratification Polls that are in progress under any circumstances.","contentHash":"6d34ec77b3492f935e63fa91a43c0840b4f8be7ca85331a0b997da7c0b52b066","addressRefs":[]},"b1887e4a-c937-4597-9259-1109e106885d":{"id":"b1887e4a-c937-4597-9259-1109e106885d","doc_no":"A.1.12.2.6.1.0.4.1","title":"In Progress - Change To Minimum Positive Participation Value Cannot Affect Polls That Have Already Begun","type":"Action Tenet","depth":6,"parentId":"535570e7-8548-451f-87f0-edb699373978","order":948,"content":"\"In progress\" refers to the state of a Ratification Poll that has already started, where voting is currently taking place. The Target Document thus states that any changes to Minimum Positive Participation values cannot affect polls that have already begun.","contentHash":"b0917ef0ea14e53a7c795ff5a95883b643c7b7905d6843df1648c4a649926e7d","addressRefs":[]},"8fb17cf7-71bd-4248-9294-60c06ac5321f":{"id":"8fb17cf7-71bd-4248-9294-60c06ac5321f","doc_no":"A.1.12.2.7","title":"Reconciliation Process","type":"Core","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":949,"content":"If multiple Atlas Edit Proposals editing the same component of the Atlas are approved by voters in the same Monthly Governance Cycle, the Reconciliation Process documented herein must be followed.","contentHash":"53519a86b02e6a4269505d7969810267c50b54c7d14a786705623fac02850c97","addressRefs":[]},"530fe959-2d16-4475-84ba-09a8ba3f66bb":{"id":"530fe959-2d16-4475-84ba-09a8ba3f66bb","doc_no":"A.1.12.2.7.1","title":"Language Disallowing Simultaneous Edits Not Allowed","type":"Core","depth":5,"parentId":"8fb17cf7-71bd-4248-9294-60c06ac5321f","order":950,"content":"Atlas Edit Proposals cannot include language that aims to prevent other Atlas Edit Proposals from editing the same component of the Atlas within the same Governance Cycle.","contentHash":"1a6037e5c84f1f776ee7c606047db5b3389076d09ceb077d80d7607aa4c39a84","addressRefs":[]},"3a7e2781-c6c4-4b0d-86c4-1c94abf010fc":{"id":"3a7e2781-c6c4-4b0d-86c4-1c94abf010fc","doc_no":"A.1.12.2.7.2","title":"Simultaneous Edit Reconciliation Process","type":"Core","depth":5,"parentId":"8fb17cf7-71bd-4248-9294-60c06ac5321f","order":951,"content":"Where voters approve multiple Atlas Edit Proposals that seek to edit the same component or components of the Atlas within the same Governance Cycle, the process described below must be followed.\n\nThis process only applies to the specific components that are being simultaneously edited. Other amended components that do not have edits in simultaneous proposals may be merged, unless they are dependent on the component that does have simultaneous edits.\n\nWhere simultaneous edits are non-conflicting / logically compatible: the Core Facilitator will consolidate them into a single edit either by stitching them together in the affected component or by stringing one after the other as a new component. Any action taken by the Core Facilitator in this regard will be documented publicly and should be available for examination prior to the end date of the relevant ratification polls.\n\nWhere simultaneous edits are conflicting / logically incompatible and cannot be coherently reconciled: it falls to voters to decide which of the conflicting AEPs they wish to accept. If there are two conflicting AEPs, a subsequent binary vote is appropriate in the form of a Reconciliation Process Poll.\n\nIn the event there are more than two conflicting AEPs, the Core Facilitator may choose a suitable polling method that allows voters to choose between multiple options. The difference between the conflicting amendments must be clearly presented so that voters can make an informed choice on their preferred option.\n\nA Reconciliation Process poll will take place during the Operational Weekly Cycle immediately following the closure of the ratification polls. The Reconciliation Process poll will last for three days.","contentHash":"6cf6f6aa19b2d15e0933d13579acc661e58352441705853b5a2a99ac0ab737dc","addressRefs":[]},"b1ffdef7-4472-4cc9-8be1-4896e3373761":{"id":"b1ffdef7-4472-4cc9-8be1-4896e3373761","doc_no":"A.1.12.2.0.4.1","title":"In The Transition To Endgame - Immutable Documents Can Be Amended","type":"Action Tenet","depth":4,"parentId":"d2cbddd2-58ef-4311-a71d-d2c340364cb5","order":952,"content":"Currently, in the transition to Endgame, the Immutable Documents (Articles and Sections) can be amended pursuant to [A.1.11 - Weekly Governance Cycle](83edd4e1-692e-4566-a415-b8f272c33c5e) and [A.1.12 - Monthly Governance Cycle](7f2ba62c-9b3b-4df6-aa16-189a749cffa3). Once the Sky Ecosystem enters the Endgame State, the Immutable Documents of the Atlas will be forever locked down and cannot be changed.","contentHash":"f5a52786b1a0c369582c8f774991bc2adf7a13e94028d90c4ef32b20b9bab6aa","addressRefs":[]},"75e8fd51-a540-4c3a-aaa9-1a38502f89b2":{"id":"75e8fd51-a540-4c3a-aaa9-1a38502f89b2","doc_no":"A.1.13","title":"Updating Active Data","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":953,"content":"This Article regulates modifications to Active Data documents. Active Data documents can be directly modified by Facilitators or other recognized actors through processes that occur outside the standard Weekly Governance Cycle and Monthly Governance Cycle.","contentHash":"2e03eb1c722bf4a10efd61cbf8a997ae03f49f2351ae6b55f1d2a048d4de69a3","addressRefs":[]},"39cd11f3-70fc-4a05-9cc0-fcb5efccaa11":{"id":"39cd11f3-70fc-4a05-9cc0-fcb5efccaa11","doc_no":"A.1.13.1","title":"Updating Active Data","type":"Section","depth":3,"parentId":"75e8fd51-a540-4c3a-aaa9-1a38502f89b2","order":954,"content":"This Section defines the processes by which Active Data documents are updated.","contentHash":"fc2b6c6a43fcd0fdfe899173a58295ad1187fe7b7d4b8891b446bdcd0c5b1a55","addressRefs":[]},"918bfa13-3390-4524-bd9e-759089ea643e":{"id":"918bfa13-3390-4524-bd9e-759089ea643e","doc_no":"A.1.13.1.1","title":"Overview","type":"Core","depth":4,"parentId":"39cd11f3-70fc-4a05-9cc0-fcb5efccaa11","order":955,"content":"Active Data documents must be maintained and frequently updated as part of the Sky Ecosystem’s routine operational tasks. See [A.1.2.2.2.17 - The Active Data Type](925ce2e3-c3a9-4774-a96c-cf77e024d37c).\n\nTherefore, Active Data documents can be directly modified outside of the standard Weekly Governance Cycle and Monthly Governance Cycle.\n\nEach Active Data document has an Active Data Controller document associated with it, which latter defines two elements:\n\n1. the \"Responsible Party\", or the entity who is obligated to update the Active Data, and\n2. the \"Update Process\", or the authorized process by which the Active Data is updated.","contentHash":"e4fe08ddd1effd0a2e7da60ee917b9c2dfc630a4a8b2cb6affbf3072afaf2813","addressRefs":[]},"af17e4fd-3c1c-49b1-acc1-95811ddbe5ef":{"id":"af17e4fd-3c1c-49b1-acc1-95811ddbe5ef","doc_no":"A.1.13.1.2","title":"Responsible Party","type":"Core","depth":4,"parentId":"39cd11f3-70fc-4a05-9cc0-fcb5efccaa11","order":956,"content":"The Responsible Party is the entity responsible for updating the Active Data. The Responsible Party has the permissions and obligation to update the Active Data through the Update Process specified in the respective Active Data Controller Document.\n\nSince the Responsible Party element is defined in an Active Data Controller Document, modification of that Responsible Party element is subject to a SKY vote pursuant to standard governance processes.","contentHash":"6a1c2c280b94b647d8bfafbf8648c3c946e95813f7a815f3e2dc69e46e4d7d8f","addressRefs":[]},"d84b2bbf-adeb-4a1d-a220-0dcfbff91b1e":{"id":"d84b2bbf-adeb-4a1d-a220-0dcfbff91b1e","doc_no":"A.1.13.1.2.0.3.1","title":"Active Data Controller Document - Element Annotation","type":"Annotation","depth":5,"parentId":"af17e4fd-3c1c-49b1-acc1-95811ddbe5ef","order":957,"content":"Active Data Controller Documents are Primary Documents that have Active Data Documents attached to them as Supporting Documents. Edits to Active Data Controller Documents are subject to a SKY vote pursuant to the standard governance processes. These processes include:\n\n- Atlas Edit Weekly Cycle\n- Atlas Edit Monthly Cycle\n- Bootstrapping Governance Poll\n- Operational Weekly Cycle","contentHash":"3267987bac4d5961925b5e46aab0e0354fe9128b5f2056fd9550cb514153ccfb","addressRefs":[]},"9cc660e9-4ce5-4358-9195-5b4b82eb769d":{"id":"9cc660e9-4ce5-4358-9195-5b4b82eb769d","doc_no":"A.1.13.1.3","title":"Update Process","type":"Core","depth":4,"parentId":"39cd11f3-70fc-4a05-9cc0-fcb5efccaa11","order":958,"content":"The Active Data Update Process specified in any Active Data Controller document must conform to one of the processes defined in the subdocuments herein.\n\nSince the Update Process element is defined in an Active Data Controller Document, modification of that Update Process element is subject to a SKY vote pursuant to standard governance processes.","contentHash":"f7a9329c50070de4af6c2a30c9730d869d88f3be43e760b67d67ed6b172b106e","addressRefs":[]},"ecce1a73-dac3-4fe5-a9d6-8b445bbc591a":{"id":"ecce1a73-dac3-4fe5-a9d6-8b445bbc591a","doc_no":"A.1.13.1.3.1","title":"Direct Edit","type":"Core","depth":5,"parentId":"9cc660e9-4ce5-4358-9195-5b4b82eb769d","order":959,"content":"Active Data with the \"Direct Edit\" Update Process may be edited pursuant to the following process.\n\nThe Responsible Party must post on the Sky Forum their proposed changes to the Active Data, using the appropriate category. If the Active Data document is located in the Sky Core Atlas, then the Core Facilitator must confirm that the Responsible Party has the authority to request a Direct Edit, and then modify the Atlas to reflect the Responsible Party’s proposed change. If the Active Data document is located in an Agent Artifact, then it is the Operational Facilitator for that Agent that must confirm the Responsible Party’s authority to request a Direct Edit and then modify the Atlas to reflect the proposed changes.\n\nIt is permissible for an Active Data Controller to specify unique requirements in addition to the general \"Direct Edit\" Update Process described above. These additional requirements, if any, must be specified directly in the Active Data Controller Document; this can be done through a reference or citation to the pertinent Atlas document containing the additional requirements. The additional requirements may supplement, but cannot conflict with, any aspect of the \"Direct Edit\" Update Process defined herein.","contentHash":"cbe78c39e6d22e5ea92c47064e205163950f4f14ca7cd97397f4a55a0c10debb","addressRefs":[]},"1604506b-c56f-44a2-a429-d1d7a6aa5d1f":{"id":"1604506b-c56f-44a2-a429-d1d7a6aa5d1f","doc_no":"A.1.13.1.3.1.1","title":"Corrections By Core Facilitator","type":"Core","depth":6,"parentId":"ecce1a73-dac3-4fe5-a9d6-8b445bbc591a","order":960,"content":"To correct a clear error, the Core Facilitator may directly update an Active Data document at any time. Prior to taking such action, the Core Facilitator should notify the respective Responsible Party charged with maintaining the Active Data document.\n\nHowever, if the error or issue is not clearly evident, the Active Data document must be updated in accordance with the established procedure defined in [A.1.13.1.3.1 - Direct Edit](ecce1a73-dac3-4fe5-a9d6-8b445bbc591a).","contentHash":"bad7a2d504d28ee969b18ae0e2b46fbdaccdcabd0ddf46e142a0a11c36cf1460","addressRefs":[]},"a8be1e67-802b-45c0-bf87-ea96073a5e71":{"id":"a8be1e67-802b-45c0-bf87-ea96073a5e71","doc_no":"A.1.13.1.3.1.1.0.4.1","title":"Clear Error","type":"Action Tenet","depth":6,"parentId":"ecce1a73-dac3-4fe5-a9d6-8b445bbc591a","order":961,"content":"The Target Document grants Facilitators the authority to directly edit an Active Data document if it contains a mistake or inaccuracy that is obvious, unambiguous, and indisputable. The term \"clear error\" means that the mistake is apparent and does not require extensive debate or investigation to be recognized as such.","contentHash":"5c13616c7bde049b354668f469b98f265a60831a1122d80fded622ff3da1720e","addressRefs":[]},"cfbfb3a9-4e2f-4494-bac8-af298b608b06":{"id":"cfbfb3a9-4e2f-4494-bac8-af298b608b06","doc_no":"A.1.13.1.3.2","title":"Alignment Conserver Changes","type":"Core","depth":5,"parentId":"9cc660e9-4ce5-4358-9195-5b4b82eb769d","order":962,"content":"Active Data with the \"Alignment Conserver Changes\" Update Process pertains to the Core Facilitator’s maintenance of the Atlas’ official listing of some subset of Alignment Conservers.\n\nThe triggers of such updates can include, but are not limited to, recognizing a new Alignment Conserver; offboarding an Alignment Conserver at the request of that Alignment Conserver; adding an Alignment Conserver to the list of ACs who have received a formal warning; or derecognizing an Alignment Conserver for misalignment.\n\nThe Core Facilitator can modify the pertinent Active Data documents to reflect such changes immediately; they are not required to create a post on Sky Forum.","contentHash":"3481c43da089acc7e498e05237bf1dbbccbe7f6f42505d038e7daaee84f2edd3","addressRefs":[]},"0a8d0081-2063-4f50-a085-b9c9c91d0e19":{"id":"0a8d0081-2063-4f50-a085-b9c9c91d0e19","doc_no":"A.1.13.1.3.0.3.1","title":"Active Data Controller Document - Element Annotation","type":"Annotation","depth":5,"parentId":"9cc660e9-4ce5-4358-9195-5b4b82eb769d","order":963,"content":"Active Data Controller Documents are Primary Documents that have Active Data Documents attached to them as Supporting Documents. Edits to Active Data Controller Documents are subject to a SKY vote pursuant to the standard governance processes. These processes include:\n\n- Atlas Edit Weekly Cycle\n- Atlas Edit Monthly Cycle\n- Bootstrapping Governance Poll\n- Operational Weekly Cycle","contentHash":"3267987bac4d5961925b5e46aab0e0354fe9128b5f2056fd9550cb514153ccfb","addressRefs":[]},"d607a8e3-17e1-4aab-9e74-11af39767cc7":{"id":"d607a8e3-17e1-4aab-9e74-11af39767cc7","doc_no":"A.1.14","title":"Relationship Between Sky Core And Agents","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":964,"content":"This Article governs the relationship and balance of power between Sky Core (and the Sky Core Atlas) and all Agents (and their respective Agent Artifacts).","contentHash":"45cac4dec33a10fa0cd214629441f7f1968c254c79010d52119319bb0b084d94","addressRefs":[]},"3722c147-b5f6-45ed-b462-de9d1cf5cd50":{"id":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","doc_no":"A.1.14.1","title":"Agents And The Sky Atlas","type":"Section","depth":3,"parentId":"d607a8e3-17e1-4aab-9e74-11af39767cc7","order":965,"content":"The documents contained herein define the relationship between the Sky Atlas and Agents, including the pre-eminence of the Sky Core Atlas and how conflicts between the Sky Core Atlas and Agent Artifacts are identified, escalated, and resolved.","contentHash":"3c55fce7f82f91aa623571bb8e27b0ef15e2fd6d6239ba74779e3fccd5e03089","addressRefs":[]},"2d5b0c0b-66ab-4546-b622-cd3ae1e39752":{"id":"2d5b0c0b-66ab-4546-b622-cd3ae1e39752","doc_no":"A.1.14.1.1","title":"Sky Atlas Jurisdiction","type":"Core","depth":4,"parentId":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","order":966,"content":"The Sky Atlas is the overarching governance framework for the entire Sky ecosystem and comprises six (6) Scopes in total. The first five Scopes define ecosystem-wide rules and governance processes, while the final Scope contains all Agent Artifacts.","contentHash":"dd6994a17d241a1141770d94f197fc780b146f2bb04b569f1b72f37edcb3ce37","addressRefs":[]},"7cbb23c7-277d-4a43-9b37-2cf4a0561916":{"id":"7cbb23c7-277d-4a43-9b37-2cf4a0561916","doc_no":"A.1.14.1.2","title":"Sky Core Atlas","type":"Core","depth":4,"parentId":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","order":967,"content":"The Governance Scope, Support Scope, Stability Scope, Protocol Scope and Accessibility Scope, together with the Preamble, are collectively referred to as the \"Sky Core Atlas\". These contain the foundational and supreme governance rules, principles, and processes that govern Sky at the highest level.","contentHash":"5e15e202cf13ad57ff6d3b72eca59ff0c61c5a63780272dfc687e3f8b7a957e6","addressRefs":[]},"0f55f573-4c25-4b9d-87c6-01d2f7f43eb6":{"id":"0f55f573-4c25-4b9d-87c6-01d2f7f43eb6","doc_no":"A.1.14.1.3","title":"Pre-Eminence Of The Sky Core Atlas","type":"Core","depth":4,"parentId":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","order":968,"content":"The first five (5) Scopes of the Sky Atlas, together with the Preamble, serve as the foundational governance ruleset for the entire Sky ecosystem. All Agent Artifacts in the sixth Scope are derived from the Sky Core Atlas and must remain fully consistent with same. Where a provision in an Agent Artifact conflicts with a provision in the [A.1.14.1.2 - Sky Core Atlas](7cbb23c7-277d-4a43-9b37-2cf4a0561916), the latter takes precedence and shall supersede the former to the extent of that conflict.","contentHash":"ca570e74704df72df46cb65c9eb71db5daf7b55843ed5232f146b8c8aefe525a","addressRefs":[]},"178d80c7-832e-4b0c-b2f1-79b718f11e78":{"id":"178d80c7-832e-4b0c-b2f1-79b718f11e78","doc_no":"A.1.14.1.4","title":"Agent Artifacts and the Agent Scope","type":"Core","depth":4,"parentId":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","order":969,"content":"The Agent Scope consists of all Agent-specific governance and operational documents, referred to as Agent Artifacts. Although Agent Artifacts are part of the Sky Atlas, they remain subordinate to the Sky Core Atlas. Any Agent Artifact provision that conflicts with the Sky Core Atlas is invalid to the extent of that conflict.","contentHash":"32ff3808be20705280437b77327ab3023e25e0b68db760241bda884017af9909","addressRefs":[]},"ecb0b102-fe9a-41b0-9fab-ba229764fa2b":{"id":"ecb0b102-fe9a-41b0-9fab-ba229764fa2b","doc_no":"A.1.14.1.5","title":"Conflict Protocol Between Agent Artifacts And The Sky Core Atlas","type":"Core","depth":4,"parentId":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","order":970,"content":"A SKY holder who believes that an Agent Artifact conflicts with the Sky Core Atlas may escalate their concern to the Core Facilitator via posting a \"Notice of Potential Conflict\" on the Sky Forum. Upon receipt of such notice, the protocol specified in the documents herein must be initiated.","contentHash":"86dd3611c4be64f96dc9da73c6e6d57e6a1b0665f32404876872297ab4fea14b","addressRefs":[]},"81e59b78-a355-4497-bd4f-72188376c021":{"id":"81e59b78-a355-4497-bd4f-72188376c021","doc_no":"A.1.14.1.5.1","title":"Core Facilitator Review","type":"Core","depth":5,"parentId":"ecb0b102-fe9a-41b0-9fab-ba229764fa2b","order":971,"content":"Once a Notice of Potential Conflict is posted on the Sky Forum, the Core Facilitator must review the merits of the claim. The Core Facilitator has the discretion to conduct an investigation and collect more information as needed to assess the potential conflict.","contentHash":"72f6c01abb6aea192cce892560466fef3167b3fc55309719f5e3fa627a4c4c70","addressRefs":[]},"5ab97ecc-bf4f-4511-af73-da307b9ff951":{"id":"5ab97ecc-bf4f-4511-af73-da307b9ff951","doc_no":"A.1.14.1.5.2","title":"Core Facilitator Determination","type":"Core","depth":5,"parentId":"ecb0b102-fe9a-41b0-9fab-ba229764fa2b","order":972,"content":"Following their review of the Notice of Potential Conflict, the Core Facilitator must issue a formal determination about whether a conflict exists. If the Core Facilitator determines that a conflict exists, they must issue an \"Intent to Suspend\" notice relating to the particular part of the Agent Artifact they consider to be in conflict. If the Core Facilitator determines that no conflict exists, they must post this determination and their reasoning in response to the Notice of Potential Conflict on the Sky Forum.","contentHash":"ca91f0d047348aa2a8daeb7096a4a886b8da637d808ff68cade8b4f466c6cd3c","addressRefs":[]},"011846e4-8cab-4423-ae19-5a68ed83625c":{"id":"011846e4-8cab-4423-ae19-5a68ed83625c","doc_no":"A.1.14.1.5.3","title":"Intent to Suspend Notice Process","type":"Core","depth":5,"parentId":"ecb0b102-fe9a-41b0-9fab-ba229764fa2b","order":973,"content":"Once the Core Facilitator issues an Intent to Suspend notice relating to the relevant conflicting portion of an Agent Artifact, the relevant Prime Agent or Prime Agent token holders have fourteen (14) days to amend or clarify the Artifact provision in question in order to ameliorate the conflict. Once the fourteen days elapse, the Core Facilitator must determine whether the conflict continues to exist. If the Core Facilitator determines that the conflict is not resolved, the relevant portion of the Agent Artifact is formally invalidated.","contentHash":"dd65387be221ad8fcdcff9bc47487067bd3cd7dec303a320a8b863f275abfdbd","addressRefs":[]},"cd9b64bd-9a0c-41ed-b02c-5cc6bfb231d3":{"id":"cd9b64bd-9a0c-41ed-b02c-5cc6bfb231d3","doc_no":"A.1.14.1.5.4","title":"Emergency Process For Misaligned Agent Artifacts","type":"Core","depth":5,"parentId":"ecb0b102-fe9a-41b0-9fab-ba229764fa2b","order":974,"content":"In an emergency situation (see [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225)), Sky Core has the discretion to immediately suspend an Agent Artifact provision or function if it reasonably suspects that the Artifact is contributing towards a significant or system-level risk. Sky Core must act in good faith when exercising its discretion in emergency situations.","contentHash":"6384b5f8ea733712b9ba90abdd5aa82ca2d0186381a9e0150a2957714a0a035a","addressRefs":[]},"4037c7a7-908d-4cd1-8020-0dd3db899c10":{"id":"4037c7a7-908d-4cd1-8020-0dd3db899c10","doc_no":"A.1.14.1.5.4.1","title":"Emergency Suspension Resolution Process","type":"Core","depth":6,"parentId":"cd9b64bd-9a0c-41ed-b02c-5cc6bfb231d3","order":975,"content":"If Sky Core immediately suspends a particular provision or function in an Agent Artifact, that provision or function will remain inactive until either the emergency situation is resolved or a formal review by the Core Facilitator concludes that there is no issue with the Agent Artifact.","contentHash":"1686fc62946b8c08ed7122062cab6fd96e7e2f505ee2c512a661ef03194941ed","addressRefs":[]},"584801d6-f1ac-4158-8633-f4e566ce0c09":{"id":"584801d6-f1ac-4158-8633-f4e566ce0c09","doc_no":"A.1.14.1.5.4.2","title":"Emergency Suspension Review Process","type":"Core","depth":6,"parentId":"cd9b64bd-9a0c-41ed-b02c-5cc6bfb231d3","order":976,"content":"Any decision by Sky Core to use its emergency suspension discretion must be followed by a formal review process by the Core Facilitator as to the particular risks or issues with the Agent Artifact in question. The Core Facilitator must ensure that this review process is timely and clearly communicated to the affected Prime Agent.","contentHash":"aca4df72b03abec783314d4808c005f3c47f9edae88a3215db8f7780409da0e9","addressRefs":[]},"37c79482-b6b3-4055-82ce-169d1da98022":{"id":"37c79482-b6b3-4055-82ce-169d1da98022","doc_no":"A.1.14.1.6","title":"Root Control","type":"Core","depth":4,"parentId":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","order":977,"content":"Sky Core retains, at all times, ultimate \"root-level\" authority over Agents via Executive Vote and can exercise it as necessary. While Sky Core may delegate certain interpretive duties and other functions to specialized bodies such as Executor Agents, ultimate root-level authority always resides with Sky Core.","contentHash":"449099b9885338c40cfbe2486f777b939210e5744f376fd5365d15f08a3d662b","addressRefs":[]},"a9d8aa61-9046-4e34-beee-44a0310174bb":{"id":"a9d8aa61-9046-4e34-beee-44a0310174bb","doc_no":"A.1.14.1.6.1","title":"Sky Executive Vote Override","type":"Core","depth":5,"parentId":"37c79482-b6b3-4055-82ce-169d1da98022","order":978,"content":"A Sky Executive Vote will override any Agent Artifact or decision by an Executor Agent if there is a determination by Sky Core that the Prime Agent or Executor Agent is acting misaligned, or if the Sky ecosystem's safety or solvency is at risk.","contentHash":"40f1c5931639e9b50c3dc4c116763a6ddf89b1d81811e87216543688e36137a1","addressRefs":[]},"a6996fe3-6018-4241-aae9-bca7eb0fefb5":{"id":"a6996fe3-6018-4241-aae9-bca7eb0fefb5","doc_no":"A.1.14.1.6.2","title":"No Removal Of Sky Core Root Control","type":"Core","depth":5,"parentId":"37c79482-b6b3-4055-82ce-169d1da98022","order":979,"content":"Agents may not take any governance action or enact any Agent Artifact edit that would have the effect of undermining the root control of Sky Core. Any attempt to do so represents significant misalignment.","contentHash":"f349b83254e205cde0fccb5f6e84301378786c4eb511c0dd0f5e942462c63581","addressRefs":[]},"e5b96bad-0b8d-4cac-afda-d1bd41d6bcb0":{"id":"e5b96bad-0b8d-4cac-afda-d1bd41d6bcb0","doc_no":"A.1.14.1.6.3","title":"Root Control Alignment Requirement","type":"Core","depth":5,"parentId":"37c79482-b6b3-4055-82ce-169d1da98022","order":980,"content":"Sky Core can only exercise root control over a particular Agent in a manner that is consistent with the Spirit of the Atlas. Any use of root control must be proportionate and limited.","contentHash":"f57774c5f63e6436651d86f570d4d16837735010f86e2732fe77c3758b6441e2","addressRefs":[]},"26e6229d-4ee3-4dd1-a1b4-0fd45f1a45ff":{"id":"26e6229d-4ee3-4dd1-a1b4-0fd45f1a45ff","doc_no":"A.1.14.1.7","title":"Fundamental Alignment Requirement","type":"Core","depth":4,"parentId":"3722c147-b5f6-45ed-b462-de9d1cf5cd50","order":981,"content":"No Agent is permitted to take any action that is misaligned with the Spirit of the Atlas see [A.1.1 - Spirit of the Atlas](86a93dab-2f12-4c3f-9285-bcc4520c851b).","contentHash":"ab4b3eb23848bd9f6bd1318b3dfb082546cbf1c138d14800c5f783c706b0d6ea","addressRefs":[]},"84f1702d-1faf-42fb-a9f6-fbc197f40b9c":{"id":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","doc_no":"A.1.14.2","title":"Agent Artifacts","type":"Section","depth":3,"parentId":"d607a8e3-17e1-4aab-9e74-11af39767cc7","order":982,"content":"The documents contained herein detail the jurisdiction of Agent Artifacts, including the interaction between Artifacts, configuration requirements, and the specific functions and requirements of Executor Agent Artifacts.","contentHash":"840b0f778cbebfdf5b60ee4844eeb325830f222a815a0c5f69bde7ce966f6f48","addressRefs":[]},"e22a06b2-018b-4acb-a928-681f4c3e682a":{"id":"e22a06b2-018b-4acb-a928-681f4c3e682a","doc_no":"A.1.14.2.1","title":"Jurisdiction Of Agent Artifacts","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":983,"content":"Subject to any relevant provisions in the Sky Core Atlas, Agents are governed by the provisions of their respective Agent Artifacts. Agent Artifacts define the Agent’s strategic vision and day-to-day operational logic, including, in the case of Prime Agents, specific parameters or operational instructions relevant to the Agents’ business activities. These Artifacts play a pivotal role in delineating the operational processes that must be carried out by the Executor Agents with whom Prime Agents partner.","contentHash":"82a481bd434bf3b66f2b232d010bd04cbba9d5fc3fb97e26d670ef35ab805cc7","addressRefs":[]},"afab0e51-9546-4eaf-94cc-00a460aa5efe":{"id":"afab0e51-9546-4eaf-94cc-00a460aa5efe","doc_no":"A.1.14.2.2","title":"Interaction Of Agent Artifacts","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":984,"content":"Agent Artifacts must not limit or constrain the effect or operation of other Agent Artifacts. Agents can freely experiment or pursue divergent governance and operational logic within their respective Artifacts, subject to the fundamental requirement that all Artifacts remain aligned with the Sky Core Atlas.","contentHash":"dbf100494a79bfaf30ad5ff33211ebf72b7c96e6c91efe80e7fd87b1482f2378","addressRefs":[]},"32495169-340a-4969-bb4f-c72512a95e8b":{"id":"32495169-340a-4969-bb4f-c72512a95e8b","doc_no":"A.1.14.2.3","title":"Location Of Agent Artifacts","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":985,"content":"All Agent Artifacts, including new Agent Artifacts, must be recorded and publicly documented in the Agent Scope of the Sky Atlas: see [A.6 - The Agent Scope](4a08ca6c-e652-49e4-9b79-4831b20e600a).","contentHash":"780dd1e807f8b5c60a4f0981ae1b162538ead20da840e37af7f3c95b45357120","addressRefs":[]},"371a6946-24ab-4bc8-b8d7-7a8e9ad92013":{"id":"371a6946-24ab-4bc8-b8d7-7a8e9ad92013","doc_no":"A.1.14.2.3.1","title":"Canonical Version Of Agent Artifacts","type":"Core","depth":5,"parentId":"32495169-340a-4969-bb4f-c72512a95e8b","order":986,"content":"While the text of Agent Artifacts may be copied and made accessible in other locations, the version of a given Agent Artifact publicly documented within the Agent Scope of the Sky Atlas must be treated as canonical. In the event of any discrepancies between the Agent Artifact recorded in the Sky Atlas and elsewhere, the version formally documented in the Sky Atlas shall prevail.","contentHash":"d4ed8bd939b3ee22505ce0bda2480ec245f54e2742b3741947b9ff26e894a932","addressRefs":[]},"a132233a-8ec0-44d5-b93a-3cff6ca49ad6":{"id":"a132233a-8ec0-44d5-b93a-3cff6ca49ad6","doc_no":"A.1.14.2.4","title":"Agent Artifact Primitives","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":987,"content":"All Agent Artifacts contain a set of configured Primitive Instances, as set out in the Sky Primitives Article in the Support Scope see [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"da403f3f7a061085e87f32b8f357ae4109f8a7704d67182763a612537bffd8c4","addressRefs":[]},"3d7f42a5-8c7d-44ed-9a85-2ab8e7cca2f5":{"id":"3d7f42a5-8c7d-44ed-9a85-2ab8e7cca2f5","doc_no":"A.1.14.2.4.1","title":"Agent Artifact Instance Configuration Requirements","type":"Core","depth":5,"parentId":"a132233a-8ec0-44d5-b93a-3cff6ca49ad6","order":988,"content":"Agent Artifacts must have an Instance Configuration Document detailing the configuration of each Instance of a given Primitive. This Instance Configuration Document must define the Parameters of the particular Instance, the Operational Process for that Instance, and all relevant documents and data for that Instance.","contentHash":"21296c2e0ac376d902af0070e23a7d640924abc67825383ed5922bbb2ace5188","addressRefs":[]},"54baff0b-5b40-4dce-ae6c-8a69d27dc70b":{"id":"54baff0b-5b40-4dce-ae6c-8a69d27dc70b","doc_no":"A.1.14.2.4.1.1","title":"Support Scope Required Information","type":"Core","depth":6,"parentId":"3d7f42a5-8c7d-44ed-9a85-2ab8e7cca2f5","order":989,"content":"The Parameters of each Instance Configuration Document in an Agent Artifact must correspond to the required information specified in the Sky Primitives Article in the Support Scope see [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"477830471539846012f9739c694acfb69839eb43d3750c4936d7cf3853df1906","addressRefs":[]},"d2c31de7-75a9-4b69-9fd8-ca974aea5fee":{"id":"d2c31de7-75a9-4b69-9fd8-ca974aea5fee","doc_no":"A.1.14.2.5","title":"Agent Artifact Omni Documents","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":990,"content":"All Agent Artifacts contain Omni Documents. Omni Documents can be used to encode any operational or business logic that either spans multiple Sky Primitives, or relates to non-Sky Primitive infrastructure inherited from Sky Core or other activities unrelated to Sky Primitives.","contentHash":"bcfbe0c38e4f0544bde347ccda883b088f6bbc52446d0833fa29aeda99cae60e","addressRefs":[]},"b6e391fa-3265-4694-a835-3231049c2062":{"id":"b6e391fa-3265-4694-a835-3231049c2062","doc_no":"A.1.14.2.5.1","title":"Required Omni Documents","type":"Core","depth":5,"parentId":"d2c31de7-75a9-4b69-9fd8-ca974aea5fee","order":991,"content":"While in general Omni Documents may have whatever content an Agent desires, certain Omni Documents are required for all Agent Artifacts as specified herein.","contentHash":"cc5f16de7a8f517bd8b432bbd996c450294880a8a3c5e36d9eff6ea188cbb996","addressRefs":[]},"5875496e-f87d-4eea-b8f9-2b26be681389":{"id":"5875496e-f87d-4eea-b8f9-2b26be681389","doc_no":"A.1.14.2.5.1.1","title":"Root Omni Document","type":"Core","depth":6,"parentId":"b6e391fa-3265-4694-a835-3231049c2062","order":992,"content":"All Agent Artifacts must contain exactly one (1) Omni Document subtree. The head of this subtree is the Root Omni Document. All Omni Documents must be located in this subtree.","contentHash":"b414bb02b1afbbe25045ef027e96cea27fc0c686f5e6bb9d545704e66bc2454e","addressRefs":[]},"a689a844-5632-4d5e-b3dd-c345fde9dd27":{"id":"a689a844-5632-4d5e-b3dd-c345fde9dd27","doc_no":"A.1.14.2.5.1.2","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"b6e391fa-3265-4694-a835-3231049c2062","order":993,"content":"All Agent Artifacts must contain a `Governance Information Unrelated To Root Edit Primitive` document as a direct child of the Root Omni Document. This document and its subdocuments must define governance processes of the Agent unrelated to token holder voting, which latter is specified in the Root Edit Primitive.","contentHash":"1511ac34a7c0763b4eae5479302ec1dc90a7c79420d984749ef122d73c55eabd","addressRefs":[]},"f9f1a5a5-4c79-4b91-ada6-b473c22e154f":{"id":"f9f1a5a5-4c79-4b91-ada6-b473c22e154f","doc_no":"A.1.14.2.5.1.2.1","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"b6e391fa-3265-4694-a835-3231049c2062","order":994,"content":"All Agent Artifacts must contain a `Sky Ecosystem Emergency Response` document as a direct child of the `Governance Information Unrelated To Root Edit Primitive` document. This document and its subdocuments must specify the Agent’s emergency response protocol applicable in situations that impact the entire Sky Ecosystem.","contentHash":"c236393016b81f69bf9f43aeffd0e2a744e90d3117cee10d4892bceb9cce2eba","addressRefs":[]},"f04bd29a-a736-4663-9df8-e46e794d6a60":{"id":"f04bd29a-a736-4663-9df8-e46e794d6a60","doc_no":"A.1.14.2.5.1.2.2","title":"Agent Emergency Response","type":"Core","depth":6,"parentId":"b6e391fa-3265-4694-a835-3231049c2062","order":995,"content":"All Agent Artifacts must contain an `Agent-Specific Emergency Response` document as a direct child of the `Governance Information Unrelated To Root Edit Primitive` document. This document and its subdocuments must specify the Agent’s emergency response protocol applicable in situations solely impacting the Agent, versus the broader Sky Ecosystem.","contentHash":"d4ac2dfc3b94cfe76d446fe926e6998a88f91eafc00647d9b02ba8414571fa33","addressRefs":[]},"39dc8d4c-5ed3-4d77-8b37-848b7cb23009":{"id":"39dc8d4c-5ed3-4d77-8b37-848b7cb23009","doc_no":"A.1.14.2.6","title":"Prime Agent Artifacts","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":996,"content":"Each Prime Agent Artifact defines an Agent’s unique strategy, model, or method of operations, as well as specific parameters or operational instructions relevant to that Agent’s business activities. There are requirements and restrictions for Prime Agent Artifacts, particularly in terms of how they may be edited over time.","contentHash":"44d50e600111acf3da08e8d7c78170078133a83f2181fb2f013f499f96c2422f","addressRefs":[]},"fd5f6ac6-767e-4908-b64c-f88025ce5f18":{"id":"fd5f6ac6-767e-4908-b64c-f88025ce5f18","doc_no":"A.1.14.2.6.1","title":"Fundamental Artifact Edit Requirements","type":"Core","depth":5,"parentId":"39dc8d4c-5ed3-4d77-8b37-848b7cb23009","order":997,"content":"All governance actions taken by a Prime Agent must be enacted through edits to their Agent Artifact.","contentHash":"44c33dc03b8ed01bb5eb0bc1f7afde1b376cf2e17fddbc0d3afc5da18605d97a","addressRefs":[]},"2be8d2f0-bf02-4aa1-ad37-afb7a811a3b8":{"id":"2be8d2f0-bf02-4aa1-ad37-afb7a811a3b8","doc_no":"A.1.14.2.7","title":"Artifact Edit Processes","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":998,"content":"There are two mechanisms for Agents to edit their respective Agent Artifacts: Root Edits and Omni Documents.","contentHash":"02d333d02f79c7183ede9676810450fdf3c11af265eb3e10419c05c03e9fa979","addressRefs":[]},"dcdc71b3-0afc-471d-8e7c-cb0b81ba34d9":{"id":"dcdc71b3-0afc-471d-8e7c-cb0b81ba34d9","doc_no":"A.1.14.2.7.1","title":"Root Edit Process","type":"Core","depth":5,"parentId":"2be8d2f0-bf02-4aa1-ad37-afb7a811a3b8","order":999,"content":"The Root Edit process allows Prime Agents to update their Agent Artifact as prescribed in the Root Edit Primitive, see: [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d). The Root Edit Primitive enables Prime Agent token holders to hold a vote on a proposed Artifact update. If that vote is successful, the Prime Agent’s designated Executor Agent will modify the Prime Agent Artifact as directed.","contentHash":"f1e7605e4aea2deadfd0b54f92172213b338d09affa97d300c95a34d5f578939","addressRefs":[]},"26ec6b08-8187-44b4-abb3-aee3868161a4":{"id":"26ec6b08-8187-44b4-abb3-aee3868161a4","doc_no":"A.1.14.2.7.2","title":"Omni Document Process","type":"Core","depth":5,"parentId":"2be8d2f0-bf02-4aa1-ad37-afb7a811a3b8","order":1000,"content":"An Omni Document is a general-purpose Artifact Document that can be used by a Prime Agent to encode any operational or business logic, data, or processes spanning multiple Primitives or relating to non-Sky Primitive infrastructure inherited from Sky Core or other activities unrelated to Sky Primitives. Where appropriate, Omni Documents’ data schema can mirror that of Sky Primitives, or it can be customized for particular use cases.","contentHash":"d5cc35d4fa0941d68d6c2bea4ab49982db1e27d6d666af39e9c9825255d9676e","addressRefs":[]},"5db28264-320a-4293-8813-dccb0d19ce32":{"id":"5db28264-320a-4293-8813-dccb0d19ce32","doc_no":"A.1.14.2.7.2.1","title":"Omni Document Procedural Requirements","type":"Core","depth":6,"parentId":"26ec6b08-8187-44b4-abb3-aee3868161a4","order":1001,"content":"An Executor Agent must not implement Omni Document logic where it requires a subjective judgment call or use of discretion. Accordingly, Omni Documents must set out clear, specific and deterministic instructions for updating the relevant Agent Artifact. In addition, all updates by Executor Agents to Agent Artifacts must be aligned with the Sky Core Atlas and the relevant Agent Artifact.","contentHash":"b2c634b2b544ad4407cfeb53c84fb206d9e3adfdaa2f95d8666a4eb24047c39f","addressRefs":[]},"49f808e6-f82d-4ac4-882f-9878fdb998f0":{"id":"49f808e6-f82d-4ac4-882f-9878fdb998f0","doc_no":"A.1.14.2.7.2.1.1","title":"Determining Whether Artifact Logic Is Sufficiently Specific","type":"Core","depth":6,"parentId":"26ec6b08-8187-44b4-abb3-aee3868161a4","order":1002,"content":"An Executor Agent may not update a Prime Agent Artifact if the relevant logic requires a significant degree of discretion, such that reasonable people may differ on how to interpret and implement the action. If there is ambiguity as to whether an Agent Artifact authorizes an Executor Agent to directly update the Artifact, the Executor Agent must err on the side of not making any changes. In an ambiguous situation, the Agent must enact the change to the Artifact through a Root Edit process.","contentHash":"8f07562ed4aa3c4c620ad2637c8b22645263941dd363c69b7418d8aba976cdeb","addressRefs":[]},"7c750981-f9cd-492e-acb9-947eb9feb86a":{"id":"7c750981-f9cd-492e-acb9-947eb9feb86a","doc_no":"A.1.14.2.8","title":"Founder Access Artifact Edits","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":1003,"content":"At the early stage of a new Agent Artifact, before the Invocation and codification of the Prime Transformation or Executor Transformation Primitive, the Founder of a new Agent has greater discretion to create new Omni Documents and edit existing Omni Documents. Further details about \"Founder Access\" are located in the Support Scope see [A.2.2.1.1.3.2 - Founder Access](a4f65994-2526-4522-a986-cd444a5cb896).","contentHash":"7850a1f4b92426b68b9e3639ee3f6e6608ca05cdf3b60dfeb9acb3b28a5f581d","addressRefs":[]},"85afc135-eb0d-4f17-8f8f-88ff13b8b6da":{"id":"85afc135-eb0d-4f17-8f8f-88ff13b8b6da","doc_no":"A.1.14.2.8.1","title":"Founder Access Discretion","type":"Core","depth":5,"parentId":"7c750981-f9cd-492e-acb9-947eb9feb86a","order":1004,"content":"Prior to the Invocation and codification of the Prime Transformation or Executor Transformation Primitive within an Agent Artifact, the Agent’s Founder may unilaterally create new Omni Documents or edit existing Omni Documents.","contentHash":"58e09838b366ca4099c922c48ef33456e11ad32870e15f700ad4cb00227ff94a","addressRefs":[]},"00ee44e4-9a2e-4dd8-a30b-eb4f2401b72a":{"id":"00ee44e4-9a2e-4dd8-a30b-eb4f2401b72a","doc_no":"A.1.14.2.8.2","title":"Prime Transformation / Executor Transformation Ends Period Of Discretion","type":"Core","depth":5,"parentId":"7c750981-f9cd-492e-acb9-947eb9feb86a","order":1005,"content":"Following the Invocation and codification of the Prime Transformation or Executor Transformation Primitive, the Agent’s Founder no longer has the discretion to unilaterally create new Omni Documents or edit existing Omni Documents. Instead, the Agent Artifact can only be updated or changed through existing Omni Documents or the governance process defined in the Root Edit Primitive.","contentHash":"cc0f0ef97197b5e0ca752f33fa2405bdfd2b3670d4bdbd417e482ecab6746990","addressRefs":[]},"45b3a9e8-56fe-4f22-a21a-54526f38763f":{"id":"45b3a9e8-56fe-4f22-a21a-54526f38763f","doc_no":"A.1.14.2.9","title":"Executor Agent Artifacts","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":1006,"content":"Unlike Prime Agent Artifacts, Executor Agent Artifacts are standardized and come with specific limitations regarding Sky Primitives Activation.","contentHash":"7353d490f63f7e02f2953723ce285cf00fd1b2010f6326138a06b3c36df230d3","addressRefs":[]},"3be71f09-25a8-4a4b-9306-81d1007e9210":{"id":"3be71f09-25a8-4a4b-9306-81d1007e9210","doc_no":"A.1.14.2.9.1","title":"Standardized Executor Agent Sky Primitives","type":"Core","depth":5,"parentId":"45b3a9e8-56fe-4f22-a21a-54526f38763f","order":1007,"content":"The following Sky Primitives are available for Executor Agents to Activate: all Genesis Primitives (the Agent Creation Primitive, the Agent Token Primitive, the Prime Transformation Primitive and the Executor Transformation Primitive), Operational Primitives (the Executor Accord Primitive, the Root Edit Primitive and the Light Agent Primitive) and the Executor’s own version of the Upkeep Primitive.","contentHash":"a5fa9cb2049da939f023d60d22a105d688e2a569a3b44351da39fe328711a9de","addressRefs":[]},"1405d49c-8373-409e-a96b-e59f49e3aeb0":{"id":"1405d49c-8373-409e-a96b-e59f49e3aeb0","doc_no":"A.1.14.2.9.2","title":"Role Of Executor Agent Artifacts","type":"Core","depth":5,"parentId":"45b3a9e8-56fe-4f22-a21a-54526f38763f","order":1008,"content":"Executor Agent Artifacts define each Agent’s approach to operationalizing the strategy of different Prime Agents, including risk-management and fees","contentHash":"10e20f35c30043d9bef7585bfbcda673f7c847b6928269b0dde5cf1c8dce9436","addressRefs":[]},"d4bf73e7-2f9f-454c-8add-614dff784f78":{"id":"d4bf73e7-2f9f-454c-8add-614dff784f78","doc_no":"A.1.14.2.10","title":"Agent Artifact Review By Core GovOps","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":1009,"content":"Agents are responsible for maintaining their Artifacts in accordance with the Sky Core Atlas. Core GovOps may review Agent Artifacts to determine whether this requirement has been met and assess penalties if not, as specified in the documents herein.","contentHash":"761e77ab088bdc0b6a3777a24120626ed37caf0dc5ee39d0491c847b6f28a144","addressRefs":[]},"603b2914-30eb-4a32-bbdb-1416903428d4":{"id":"603b2914-30eb-4a32-bbdb-1416903428d4","doc_no":"A.1.14.2.10.1","title":"Responsibility To Maintain Agent Artifact","type":"Core","depth":5,"parentId":"d4bf73e7-2f9f-454c-8add-614dff784f78","order":1010,"content":"Each Agent is responsible for maintaining its Artifact such that the following requirements are met:\n\n- the Artifact provides clear authorization for all actions taken by the Agent;\n- the Artifact accurately reflects the current state of the Agent and its operations;\n- the Artifact conforms to all specifications in the Sky Core Atlas, including, without limitation, the specifications for each of the Sky Primitives (see [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907)); and\n- the Artifact is free of significant ambiguities or contradictions.\n\nIf the Agent has an Operational Executor Agent then this responsibility is shared by Operational GovOps and the Operational Facilitator.","contentHash":"af6c4bff39a3ca690508042eb77fcc890c2846e10ca1b7abefa10af051f7dd4a","addressRefs":[]},"e0dd40ef-1d3b-4a00-9601-181ce80d3eef":{"id":"e0dd40ef-1d3b-4a00-9601-181ce80d3eef","doc_no":"A.1.14.2.10.2","title":"Review By Core GovOps","type":"Core","depth":5,"parentId":"d4bf73e7-2f9f-454c-8add-614dff784f78","order":1011,"content":"The documents herein define the process for review of Agent Artifacts for their compliance with the requirements specified in [A.1.14.2.10.1 - Responsibility To Maintain Agent Artifact](603b2914-30eb-4a32-bbdb-1416903428d4).","contentHash":"8bd270957732a0f07efaf333a66f08370039e25de4cf2085dc47cce297240983","addressRefs":[]},"ec953006-98f0-436d-8324-7b75cd84688c":{"id":"ec953006-98f0-436d-8324-7b75cd84688c","doc_no":"A.1.14.2.10.2.1","title":"Core GovOps Initiatives Review Of Agent Artifact","type":"Core","depth":6,"parentId":"e0dd40ef-1d3b-4a00-9601-181ce80d3eef","order":1012,"content":"Core GovOps may review an Agent Artifact for its compliance with the requirements specified in [A.1.14.2.10.1 - Responsibility To Maintain Agent Artifact](603b2914-30eb-4a32-bbdb-1416903428d4) at any time. This review may either be initiated by Core GovOps in response to an issue that has arisen or be conducted as part of a regular review process established by Core GovOps.","contentHash":"f2b335e4096463ac09c4bb6242199e9c6d1577e0c93426ba9c7cfe6e736c2294","addressRefs":[]},"ed93f083-0e23-460e-a2fb-1f53233a237f":{"id":"ed93f083-0e23-460e-a2fb-1f53233a237f","doc_no":"A.1.14.2.10.2.2","title":"Core GovOps Shares Initial Findings With Agent","type":"Core","depth":6,"parentId":"e0dd40ef-1d3b-4a00-9601-181ce80d3eef","order":1013,"content":"If Core GovOps identifies deficiencies in an Agent Artifact relative to the requirements specified in [A.1.14.2.10.1 - Responsibility To Maintain Agent Artifact](603b2914-30eb-4a32-bbdb-1416903428d4), Core GovOps shares those findings with the Agent and its Operational Executor Agent, if applicable.","contentHash":"c5e401494fdbfd3bbde007f492fbc03d2793ebb179e1c89d597288f739fe59ff","addressRefs":[]},"5e737413-20a2-4fe3-8878-e7fb4706d238":{"id":"5e737413-20a2-4fe3-8878-e7fb4706d238","doc_no":"A.1.14.2.10.2.3","title":"Response By Agent","type":"Core","depth":6,"parentId":"e0dd40ef-1d3b-4a00-9601-181ce80d3eef","order":1014,"content":"Core GovOps gives the Agent, and its Operational Executor Agent, if applicable, a reasonable opportunity to respond to the deficiencies identified.","contentHash":"52167e493a0f4b40e02b059c6bc2e123f1bb8672a70469c5b9b494f461b71299","addressRefs":[]},"453f04da-9fcc-4a49-bd3e-374908d60319":{"id":"453f04da-9fcc-4a49-bd3e-374908d60319","doc_no":"A.1.14.2.10.2.4","title":"Publication Of Final Findings By Core GovOps","type":"Core","depth":6,"parentId":"e0dd40ef-1d3b-4a00-9601-181ce80d3eef","order":1015,"content":"Core GovOps considers the response of the Prime Agent and publishes a final set of findings to the Sky Forum under the category for the relevant Agent.","contentHash":"83e23929f3d9b4d78e7bc1ce07542a9f7b4df8995721ff97513896da3488410f","addressRefs":[]},"87a0f80d-bf02-403e-997f-0793701bcaa9":{"id":"87a0f80d-bf02-403e-997f-0793701bcaa9","doc_no":"A.1.14.2.10.2.5","title":"Remediation By Agent","type":"Core","depth":6,"parentId":"e0dd40ef-1d3b-4a00-9601-181ce80d3eef","order":1016,"content":"The Agent must submit a Root Edit Proposal to update its Artifact to address the deficiencies identified in the final set of findings (see [A.1.14.2.10.2.4 - Publication Of Final Findings By Core GovOps](453f04da-9fcc-4a49-bd3e-374908d60319)). If the Agent does not, Core GovOps may propose an Atlas Edit Proposal to directly modify the Agent Artifact to address the deficiencies.","contentHash":"52f890d0226b0b64fa0963367bb5745fa91c86a29eb539c811ae56672118494b","addressRefs":[]},"4fe3409f-468b-42d5-8ba1-cc03e4e1563d":{"id":"4fe3409f-468b-42d5-8ba1-cc03e4e1563d","doc_no":"A.1.14.2.10.2.6","title":"Appeals Process","type":"Core","depth":6,"parentId":"e0dd40ef-1d3b-4a00-9601-181ce80d3eef","order":1017,"content":"If the Agent disagrees with the final set of findings of Core GovOps, the Core Facilitator resolves the dispute.","contentHash":"1b9a4eeb29f8c96cbccca913de8822515e82fde11815671a785a6be5d011dfc1","addressRefs":[]},"d195ee61-1afc-4cec-81b3-7514193bceaf":{"id":"d195ee61-1afc-4cec-81b3-7514193bceaf","doc_no":"A.1.14.2.10.3","title":"Penalties","type":"Core","depth":5,"parentId":"d4bf73e7-2f9f-454c-8add-614dff784f78","order":1018,"content":"Penalties for an Agent failing to meet the requirements specified in [A.1.14.2.10.1 - Responsibility To Maintain Agent Artifact](603b2914-30eb-4a32-bbdb-1416903428d4) will be specified in a future iteration of the Atlas.","contentHash":"59514ff1fa9b7056c98afe13e1cf4e2af25a1ac252c329c5dd3a49201fcd7b23","addressRefs":[]},"3458d1c7-d55b-4028-9ab6-fc02dc99a795":{"id":"3458d1c7-d55b-4028-9ab6-fc02dc99a795","doc_no":"A.1.14.2.11","title":"Changes To Agent Artifact Specifications","type":"Core","depth":4,"parentId":"84f1702d-1faf-42fb-a9f6-fbc197f40b9c","order":1019,"content":"Updates to the Sky Core Atlas may change the specifications for Agent Artifacts. The documents herein define how these changes in specifications are carried through to Agent Artifacts.","contentHash":"36423a324ba002fee38a9bc71e3949f32ce7c2e44caaf8526bc95b9c1b682601","addressRefs":[]},"b1684804-9bd9-47a7-a080-d260609e023f":{"id":"b1684804-9bd9-47a7-a080-d260609e023f","doc_no":"A.1.14.2.11.1","title":"Process For Carrying Out Changes","type":"Core","depth":5,"parentId":"3458d1c7-d55b-4028-9ab6-fc02dc99a795","order":1020,"content":"Updates to Agent Artifacts to conform to changes in specifications may either be carried out by each Agent (see [A.1.14.2.11.1.1 - Changes By Agents](8dbacc54-8a35-41a5-9337-f608fcea8b56)) or carried out directly by Core GovOps (see [A.1.14.2.11.1.2 - Changes By Core GovOps](dd76b3fb-6d99-43cf-92e4-b386c9141e25)). If Core GovOps chooses to directly carry out the changes, it must communicate this directly to the affected Agents before submitting an Atlas Edit Proposal. Otherwise the process for changes carried out by Agents applies.","contentHash":"b60225318644cde7226db0e5fe80df5ae7b6ac0333b316bca34db25ec95d3361","addressRefs":[]},"8dbacc54-8a35-41a5-9337-f608fcea8b56":{"id":"8dbacc54-8a35-41a5-9337-f608fcea8b56","doc_no":"A.1.14.2.11.1.1","title":"Changes By Agents","type":"Core","depth":6,"parentId":"b1684804-9bd9-47a7-a080-d260609e023f","order":1021,"content":"When Agents carry out changes in specifications themselves, each Agent must update their Agent Artifact through the appropriate governance process to conform to the new specifications.\n\nAgents must carry out these changes within thirty (30) days of the change in specifications in the Atlas unless otherwise specified by Core GovOps.","contentHash":"03002c45e730d69e5e5e467fe9588a327a59eec3541ca3e6faafa6cfec55f0f7","addressRefs":[]},"dd76b3fb-6d99-43cf-92e4-b386c9141e25":{"id":"dd76b3fb-6d99-43cf-92e4-b386c9141e25","doc_no":"A.1.14.2.11.1.2","title":"Changes By Core GovOps","type":"Core","depth":6,"parentId":"b1684804-9bd9-47a7-a080-d260609e023f","order":1022,"content":"Alternatively, Core GovOps may submit an Atlas Edit Proposal to directly update each Agent Artifact to conform to the change in specifications. Such an edit may directly modify Agent Artifacts and is not subject to further approval by Agent token holders. Core GovOps should communicate the anticipated timing of this edit to all affected Agents as early as practicable.","contentHash":"15be960a0cc1828dae3faa28200954daba0fad26887a689ab741efb5224f5c7b","addressRefs":[]},"b9afc2bf-7697-4e21-820d-63dc8598f522":{"id":"b9afc2bf-7697-4e21-820d-63dc8598f522","doc_no":"A.1.14.3","title":"Prime Agents","type":"Section","depth":3,"parentId":"d607a8e3-17e1-4aab-9e74-11af39767cc7","order":1023,"content":"The documents contained herein detail the specific role, requirements and capabilities of Prime Agents, including the operational delineation between Prime Agents and Executor Agents.","contentHash":"a29543065889bc0a6dd6c287b4207e6c5d8c7cb79087cc572ed2634b636667e3","addressRefs":[]},"6a6c2870-3fa9-409d-a54c-952f61a30854":{"id":"6a6c2870-3fa9-409d-a54c-952f61a30854","doc_no":"A.1.14.3.1","title":"Prime Agent Strategic Autonomy","type":"Core","depth":4,"parentId":"b9afc2bf-7697-4e21-820d-63dc8598f522","order":1024,"content":"Subject to the fundamental requirement to adhere to the Sky Core Atlas, Prime Agents have the autonomy to pursue a unique strategy, model, or method of operations, as defined in their Agent Artifact. Each Prime Agent’s unique Agent Artifact should also include specific parameters or operational instructions relevant to the Agents’ business activities. These Artifacts play a pivotal role in delineating the operational processes that must be carried out by the Executor Agents with whom Prime Agents partner.","contentHash":"eda1c5740d7dac0f67513f0ddbe400652a174219e725c9ee5a676315ae7f50b3","addressRefs":[]},"cdf12e79-18f7-4b44-97ec-78290682005a":{"id":"cdf12e79-18f7-4b44-97ec-78290682005a","doc_no":"A.1.14.3.2","title":"Prime Agent Executor Agent Requirement","type":"Core","depth":4,"parentId":"b9afc2bf-7697-4e21-820d-63dc8598f522","order":1025,"content":"A fundamental requirement is that Prime Agents must partner with an Executor Agent. Prime Agents cannot be active without an active \"Executor Accord\" which codifies their relationship with an Executor Agent. Prime Agents may not amend their Artifact or make any other procedural change that would have the effect of removing the Executor Agent Requirement.","contentHash":"70bd0c5a476984bae70829ae3599728c18ab494a8b8042786309de6e649b16fb","addressRefs":[]},"946b8318-779c-4873-9413-6d44316f6d5e":{"id":"946b8318-779c-4873-9413-6d44316f6d5e","doc_no":"A.1.14.3.3","title":"Prime Agent Operational Autonomy","type":"Core","depth":4,"parentId":"b9afc2bf-7697-4e21-820d-63dc8598f522","order":1026,"content":"Prime Agents autonomously handle initiatives that do not directly interface with Sky Protocol-level resources, including, but not limited to, the Sky Primitives. These activities could include product strategy and innovation, business development, partnership negotiations, and other business activities.","contentHash":"772f3e75d9bd160f8ae0bfe7129e35a68909cfc03baf9398d26bd3c1892b4002","addressRefs":[]},"fdf32ca5-5e2e-481e-9047-4d1599547216":{"id":"fdf32ca5-5e2e-481e-9047-4d1599547216","doc_no":"A.1.14.3.4","title":"Agent Role Delineation","type":"Core","depth":4,"parentId":"b9afc2bf-7697-4e21-820d-63dc8598f522","order":1027,"content":"Whenever a Prime Agent’s strategy involves any on-chain or off-chain interaction with Sky Protocol resources or infrastructure, including the Sky Primitives, the operationalization of that strategy is generally restricted to Executor Agents. There is an exception for Prime Agents directly operationalizing Allocation System Primitive Instances using internal, proprietary strategies, see [A.2.2.9.1.1.3.1 - Operationalization Of Allocation Instances](989512c2-4fa1-46b8-947c-00e3c0b56024).","contentHash":"b832216ac4f0b0b9be43009d99fe5f9df962d99817043c86726a758996a16a98","addressRefs":[]},"bc07050a-4d28-4977-b46b-44bb52dea9ab":{"id":"bc07050a-4d28-4977-b46b-44bb52dea9ab","doc_no":"A.1.14.3.4.1","title":"Role Of Executor Agents","type":"Core","depth":5,"parentId":"fdf32ca5-5e2e-481e-9047-4d1599547216","order":1028,"content":"In situations requiring interaction with the Sky Protocol, Prime Agents themselves do not carry out the tasks needed to implement the relevant strategies. Instead, Prime Agents rely on Executor Agents to operationalize these processes, including bridging capital, verifying on-chain data and generating reports, and preparing off-chain votes for Prime Agent token holders to update their Artifact.","contentHash":"c87b436fee118ea1c7c3892f0622d23905aa1e18349010d08a3f4947464d1137","addressRefs":[]},"ca805edd-ec90-41c8-b9b0-7f76909c4a18":{"id":"ca805edd-ec90-41c8-b9b0-7f76909c4a18","doc_no":"A.1.14.3.4.2","title":"Specificity Requirement For Prime Agent Artifacts","type":"Core","depth":5,"parentId":"fdf32ca5-5e2e-481e-9047-4d1599547216","order":1029,"content":"To ensure clear direction for Executor Agents when executing Prime Agent strategies involving interaction with the Sky Protocol, Prime Agent Artifacts must include highly detailed and deterministic instructions. These instructions should allow Executor Agents to understand and implement the instructions without ambiguity or the use of discretion. More details about these processes and related logic can be found in the Agent Artifacts Section. More information about the role and function of Executor Agents can be found in the Executor Agents Section.","contentHash":"35f06c9e5153814e70f8fbeded8cedec7c8f331198e328637281a3ed64baf465","addressRefs":[]},"79a69869-3418-420a-8cba-032b808cb887":{"id":"79a69869-3418-420a-8cba-032b808cb887","doc_no":"A.1.14.4","title":"Executor Agents","type":"Section","depth":3,"parentId":"d607a8e3-17e1-4aab-9e74-11af39767cc7","order":1030,"content":"The documents contained herein define the specific role, requirements and capabilities of Executor Agents.","contentHash":"4e76776129d0acf11925c01e8d29e89499bdf940c0c8af45843e1c48c798d7af","addressRefs":[]},"1b10829a-7b5d-4307-a1f1-916468abdfca":{"id":"1b10829a-7b5d-4307-a1f1-916468abdfca","doc_no":"A.1.14.4.1","title":"The Role Of Executor Agents","type":"Core","depth":4,"parentId":"79a69869-3418-420a-8cba-032b808cb887","order":1031,"content":"Executor Agents play a critical role in implementing Prime Agent strategies, as defined by their Executor Agent Accord with a particular Agent. Executor Agents are tasked with operationalizing Prime Agent strategies, and are able to directly update Agent Artifacts where sufficiently specific logic exists to do so.","contentHash":"8951ed859ee3c880e91905a0919be2772e14089bf2dd766c2baaedd14a749678","addressRefs":[]},"5dca36a5-a9aa-4c8a-9c41-b2be94c0e12c":{"id":"5dca36a5-a9aa-4c8a-9c41-b2be94c0e12c","doc_no":"A.1.14.4.2","title":"Requirement For Executor Agent Accord","type":"Core","depth":4,"parentId":"79a69869-3418-420a-8cba-032b808cb887","order":1032,"content":"Executor Agents must partner with Prime Agents through a formal Executor Agent Accord. An Executor Agent may not carry out any executive functions for a particular Prime Agent without a formal Executor Agent Accord.","contentHash":"0f8f62cb963de4db6e93ec21193eb5c8426f87cbf706a8a30e7d3eaebbc2de85","addressRefs":[]},"8249a5d8-f7b1-4189-8901-ba4de330d031":{"id":"8249a5d8-f7b1-4189-8901-ba4de330d031","doc_no":"A.1.14.4.3","title":"Adherence To An Executor Agent Accord","type":"Core","depth":4,"parentId":"79a69869-3418-420a-8cba-032b808cb887","order":1033,"content":"Executor Agents must adhere to all specific rules and requirements set out in a relevant Executor Agent Accord they agree with a Prime Agent.","contentHash":"fae93e06e797dc4453d86ea5fc90880b182a3ea97edb8c3d228129d23a0abe9e","addressRefs":[]},"beb4109c-b425-42ef-afd6-9b52fe454268":{"id":"beb4109c-b425-42ef-afd6-9b52fe454268","doc_no":"A.1.14.4.4","title":"Ensuring Alignment With The Atlas","type":"Core","depth":4,"parentId":"79a69869-3418-420a-8cba-032b808cb887","order":1034,"content":"Executor Agents must always ensure that a Prime Agent’s actions or processes are fully aligned with the text and spirit of the Atlas.","contentHash":"62d646c536afd5b375dee5ce3ab748b4f467b4e45a2c9042b2d496ad46cc413d","addressRefs":[]},"b8cb6cf9-2904-49e8-b627-7907ba208adf":{"id":"b8cb6cf9-2904-49e8-b627-7907ba208adf","doc_no":"A.1.14.4.4.1","title":"Executor Agent Alignment Requirements","type":"Core","depth":5,"parentId":"beb4109c-b425-42ef-afd6-9b52fe454268","order":1035,"content":"The requirement for Executor Agents to check every Prime Agent action or process for alignment with the Atlas is fundamental. It cannot be amended or altered by either Prime Agents or Executor Agents.","contentHash":"d1ddf0ca87efa6589f6fe93e8b37538eb41e9bed05386d2433eee4be47e49986","addressRefs":[]},"d20d3a11-0b46-4fb7-93dd-db473aa63665":{"id":"d20d3a11-0b46-4fb7-93dd-db473aa63665","doc_no":"A.1.14.4.5","title":"Executor Agent Right Of Refusal","type":"Core","depth":4,"parentId":"79a69869-3418-420a-8cba-032b808cb887","order":1036,"content":"Executor Agents have the discretion to refuse to operationalize a Prime Agent’s update to their Agent Artifact, or any other action, if they consider that the action is either misaligned with the Atlas or presents significant risk beyond the Executor Agent’s insured capacity.","contentHash":"fa592514fb3af14f3266834c3b515349c3b5dda803559c110ed68801bc56bbd9","addressRefs":[]},"a878427f-64a8-430f-8576-70b6e34ef419":{"id":"a878427f-64a8-430f-8576-70b6e34ef419","doc_no":"A.1.14.4.6","title":"Executor Agent GovOps And Facilitator Actors","type":"Core","depth":4,"parentId":"79a69869-3418-420a-8cba-032b808cb887","order":1037,"content":"Through GovOps and Facilitator Actors, Executor Agents supervise other Agents and carry out operational activities on behalf of Prime Agents related to the Sky Primitives.","contentHash":"865a28084ee15573eb1767d7df01201c5cc344c41132625744290c3302e3ab13","addressRefs":[]},"6e4b1649-4d85-404e-a70d-ababba877d9e":{"id":"6e4b1649-4d85-404e-a70d-ababba877d9e","doc_no":"A.1.14.4.6.1","title":"Executor Agent GovOps And Facilitators","type":"Core","depth":5,"parentId":"a878427f-64a8-430f-8576-70b6e34ef419","order":1038,"content":"Executor Agents act exclusively through their associated GovOps and Facilitator actors.","contentHash":"e556a49c7df0e82a056e3c1ab76b9fc7e3d334bbbd7b495635b0eba7d99b4b75","addressRefs":[]},"76405733-3740-4c62-836f-c0683840a9a2":{"id":"76405733-3740-4c62-836f-c0683840a9a2","doc_no":"A.1.14.4.6.1.1","title":"Executor Agent GovOps","type":"Core","depth":6,"parentId":"6e4b1649-4d85-404e-a70d-ababba877d9e","order":1039,"content":"GovOps actors carry out operational activities on behalf of Executor Agents and, by extension, Prime Agents that Executor Agents have entered into Executor Accords with. With the exception of specific activities reserved for Executor Agent Facilitators, all activities of Executor Agents are carried out by GovOps.","contentHash":"f626f74f0da4d7273eba44b697096f535ed967adc9d4c67b97fe7148a409df65","addressRefs":[]},"1b199df8-2bc3-4884-a60f-e45c3269fad4":{"id":"1b199df8-2bc3-4884-a60f-e45c3269fad4","doc_no":"A.1.14.4.6.1.2","title":"Executor Agent Facilitators","type":"Core","depth":6,"parentId":"6e4b1649-4d85-404e-a70d-ababba877d9e","order":1040,"content":"Executor Agent Facilitators are Facilitators that carry out specific activities on behalf of Executor Agents. Whenever an Executor Agent must interpret an Artifact, that interpretation must be done by the Facilitator. Whenever an Executor Agent has privileged access to smart contracts of Sky or an Agent, that access must be held by the Facilitator. Facilitators use this access to carry out the Executor Agent’s operational responsibilities as directed by GovOps, unless the Facilitator believes that GovOps is misaligned.","contentHash":"0442d71778fcf65abb6a20c065e512a2d0405cfc20071078adfe3986ff087d49","addressRefs":[]},"4fce0fd5-cfba-48b6-9af5-bbb0b5e917a6":{"id":"4fce0fd5-cfba-48b6-9af5-bbb0b5e917a6","doc_no":"A.1.14.4.7","title":"Executor Agent Short-Term Transitionary Measures","type":"Core","depth":4,"parentId":"79a69869-3418-420a-8cba-032b808cb887","order":1041,"content":"The documents herein define short term transitionary measures during the launch of Executor Agents.","contentHash":"4823d056622611fc3d8a7cadcf9a47265f0408c32258415fa2f352828de9ced1","addressRefs":[]},"2dc20bcf-08d7-4314-a2f2-aee9b41940e1":{"id":"2dc20bcf-08d7-4314-a2f2-aee9b41940e1","doc_no":"A.1.14.4.7.1","title":"GovOps And Facilitators Acting As Executor Agents","type":"Core","depth":5,"parentId":"4fce0fd5-cfba-48b6-9af5-bbb0b5e917a6","order":1042,"content":"In the short term, before the launch of Executor Agents, all references to Executor Agents in the Atlas refer to a GovOps Actor and a Facilitator, collectively. Sky Governance designates these actors as an Executor Agent on a transitional basis, and they have all the powers of Executor Agents as defined in the Atlas. When an Executor Agent enters into an Executor Accord during this transitionary period, it requires the mutual agreement of both the GovOps actor and the Facilitator, in addition to the Prime Agent.","contentHash":"1437aee864a0aaa5ce759345814bfb8dad9620763f0ec48b17d7926c4c7bd74e","addressRefs":[]},"334c2821-23c2-46e9-b728-607608a8e933":{"id":"334c2821-23c2-46e9-b728-607608a8e933","doc_no":"A.1.14.4.7.2","title":"Transfer Of Budgets To Executor Agents","type":"Core","depth":5,"parentId":"4fce0fd5-cfba-48b6-9af5-bbb0b5e917a6","order":1043,"content":"Shortly after the launch of Prime Agents, limited versions of Executor Agents will be launched. Budgets will be transferred to these Executor Agents from Sky Core so that, along with budgets transferred to Prime Agents, all Sky Core budgets are transferred to Agents. During this period GovOps and Facilitators will continue to operate as Executor Agents, with GovOps controlling the budget of the Executor Agent subject to review for alignment by the Facilitator.","contentHash":"9d290119f0402e5b3289a3ff0e169d3842edf925928e46dd4f03149fa4e85407","addressRefs":[]},"fed006c3-75fb-47d9-a03a-a01ac0e57ccb":{"id":"fed006c3-75fb-47d9-a03a-a01ac0e57ccb","doc_no":"A.1.14.4.7.3","title":"Full Launch Of Executor Agents","type":"Core","depth":5,"parentId":"4fce0fd5-cfba-48b6-9af5-bbb0b5e917a6","order":1044,"content":"In the long term, Executor Agents will be fully launched with their own tokens and governance processes. At this point, GovOps actors and Facilitators will be contracted by Executor Agents through a vote of Executor Agent token holders.","contentHash":"8747bac0983b998ef06e19cd1ef8d2af38a77e3426a85ea83b60e9a652fc6799","addressRefs":[]},"fe833d0e-8451-45e0-84a5-229d6ec964a8":{"id":"fe833d0e-8451-45e0-84a5-229d6ec964a8","doc_no":"A.1.14.5","title":"Agent Termination Protocol","type":"Section","depth":3,"parentId":"d607a8e3-17e1-4aab-9e74-11af39767cc7","order":1045,"content":"The documents contained herein set out the procedure for Agents who elect to enter a formal termination process.","contentHash":"4f4b80a1d5b85f51b236f5e20a178127243f6943b029b1ae4d635e747419f908","addressRefs":[]},"023540ad-3b1b-429b-bfa7-9d740bf6ea77":{"id":"023540ad-3b1b-429b-bfa7-9d740bf6ea77","doc_no":"A.1.14.5.1","title":"Initiation Of Agent Termination Process","type":"Core","depth":4,"parentId":"fe833d0e-8451-45e0-84a5-229d6ec964a8","order":1046,"content":"Initiation of the Agent Termination Protocol requires the token holders of an Agent to follow the special voting requirements prescribed in the Root Edit Primitive for the Agent’s termination, as specified in [A.2.2.5.2.2.2.8.1 - Agent Termination Process](82f9f4b9-76db-4ad7-94af-200ffe7c3b75). These requirements include a minimum voting period, a minimum quorum, a supermajority approval threshold, and advance notice of the Agent’s proposed termination and the subsequent Agent vote issued in the Sky Forum by the Operational Facilitator.","contentHash":"374ee5424ad201ff34550790c1f770603153e015bfb7addf968fa73179ff03cb","addressRefs":[]},"28b90058-b29d-405d-a8e1-98fa133897cc":{"id":"28b90058-b29d-405d-a8e1-98fa133897cc","doc_no":"A.1.14.5.2","title":"Execution of Agent Termination Process","type":"Core","depth":4,"parentId":"fe833d0e-8451-45e0-84a5-229d6ec964a8","order":1047,"content":"If the Agent Termination Protocol is activated, the Agent’s designated Executor Agent is tasked with ensuring the smooth and seamless wind-down of all of the Agent’s activities and functions. The Executor Agent must ensure that the cessation of any functionality is clearly communicated and signaled to users or other stakeholders, with a wind-down period calibrated to enable a smooth transition. The Core Facilitator must oversee the Agent Termination Process and ensure that the Executor Agent is executing the wind-down of the Prime Agent’s business activities in a manner aligned with Sky Core and end users’ interests. The Executor Agent should also, to the extent practicable, ensure that the assets or holdings of the Prime Agent are proportionately disbursed to Prime Agent token holders.","contentHash":"13ff873e7b51a00997dee59105f8d6121dae858420c66378d126b7f7ccbe064d","addressRefs":[]},"d28f48be-ba54-48cb-86f9-fffeb71de5ae":{"id":"d28f48be-ba54-48cb-86f9-fffeb71de5ae","doc_no":"A.1.14.5.2.1","title":"Specific Termination Process Requirements For Executor Agents","type":"Core","depth":5,"parentId":"28b90058-b29d-405d-a8e1-98fa133897cc","order":1048,"content":"Where the Agent Termination Protocol is activated for Executor Agents, the smooth wind-down of the Executor Agent’s activities must ensure that any affected Prime Agents are able to continue their day-to-day operations without interruptions. Any suspension of Executor Agent activities and services must have a sufficiently elongated period of notice to allow Prime Agents and other stakeholders to obtain alternative support. An Executor Agent cannot conclude an Agent Termination Protocol until all supervision arrangements are transferred smoothly to other Executor Agents.","contentHash":"04ddd0ded9740dd02f20c426892987300de6f0fae73d0250b33b88069a459b9d","addressRefs":[]},"52fb64c4-6ab3-45e9-a492-1d42926d93fc":{"id":"52fb64c4-6ab3-45e9-a492-1d42926d93fc","doc_no":"A.1.14.5.3","title":"End Of Agent Termination Process","type":"Core","depth":4,"parentId":"fe833d0e-8451-45e0-84a5-229d6ec964a8","order":1049,"content":"Once the Executor Agent has ensured that all operational activities and functions of the Prime Agent have been wound down, the Operational Facilitator must issue a notice in the Sky Forum indicating the formal termination of the Agent. Any residual assets or holdings of the Prime Agents, that could not be disbursed to Prime Agent token holders, revert to ownership by Sky Core.","contentHash":"5513e956ef8ab91cabc878bf74cde23831df50cb18986ed7b4db2eb3a4cf6779","addressRefs":[]},"065c176d-4a7e-4944-babb-43b325e33cf4":{"id":"065c176d-4a7e-4944-babb-43b325e33cf4","doc_no":"A.1.14.5.4","title":"Agent Termination Process Dispute Resolution","type":"Core","depth":4,"parentId":"fe833d0e-8451-45e0-84a5-229d6ec964a8","order":1050,"content":"In the event of any dispute between the Agent or Agent token holders, and the designated Executor Agent carrying out the Agent Termination Process, the Core Facilitator must mediate. If there are operational disagreements between an Agent’s Founder or Agent token holders and the Executor Agent, the Core Facilitator has discretion to direct the Executor Agent to take a particular action as consistent with the Sky Core Atlas and the relevant Agent Artifact.","contentHash":"a42ba666085a2b978c11b3c2fd89ae783d0d47c7a97810f162870f6ff394fc7f","addressRefs":[]},"ba97b4dd-c4e0-4d12-8769-423f6ecdc6bf":{"id":"ba97b4dd-c4e0-4d12-8769-423f6ecdc6bf","doc_no":"A.1.15","title":"Scope Bootstrapping","type":"Article","depth":2,"parentId":"18ac7dd3-c646-4352-9b0d-d01a2932d7d1","order":1051,"content":"This Article defines rules and procedures for swiftly resolving issues that may arise in the Governance Scope during the transition to the Endgame State. This Article must work to minimize transition costs and friction impeding this transition.","contentHash":"892e99a70419c3d7d34e372b83aa07eff97e495ad4b27d349e1920f4fd1bcd2d","addressRefs":[]},"08dbb8ad-6481-41b4-b438-4b08425abefc":{"id":"08dbb8ad-6481-41b4-b438-4b08425abefc","doc_no":"A.1.15.1","title":"Scope Bootstrapping","type":"Section","depth":3,"parentId":"ba97b4dd-c4e0-4d12-8769-423f6ecdc6bf","order":1052,"content":"This Section defines bootstrapping measures that can override requirements and specifications in the Atlas. These bootstrapping measures are temporary.","contentHash":"7dab5dedd291dc9547686475c8e7ba56436c4148b165b309cc998de351e193c6","addressRefs":[]},"7c9fd35d-e6c2-4bcd-95bb-5b4d1b0de5f0":{"id":"7c9fd35d-e6c2-4bcd-95bb-5b4d1b0de5f0","doc_no":"A.1.15.1.1","title":"Multiple Conflicting Atlas Edit Proposals","type":"Core","depth":4,"parentId":"08dbb8ad-6481-41b4-b438-4b08425abefc","order":1053,"content":"When conflicting Atlas Edit Proposals are approved within a short period of each other, the Core Facilitator can decide to merge parts of the proposals together to ensure that the aggregate changes incorporate the best updates from each of the conflicting proposals.","contentHash":"60b8a7ffea46faf74ed3cba71884c4f39d4329069d599639a8691d1325ed3f4c","addressRefs":[]},"ab868a43-3f89-4e9e-b281-6078e655e065":{"id":"ab868a43-3f89-4e9e-b281-6078e655e065","doc_no":"NR-18","title":"Conflicting Atlas Edit Proposals","type":"Needed Research","depth":5,"parentId":"7c9fd35d-e6c2-4bcd-95bb-5b4d1b0de5f0","order":1054,"content":"**Content**:\n\nThis is an extensive Research Track. Some critical questions to be explored:\n\nWhat criteria should be used to determine when two or more Atlas Edit Proposals are in conflict? Are conflicts strictly based on overlapping content, or do broader thematic or operational conflicts also count?\n\nFor instance: if two AEPs amend different sections of the Atlas but have implications that could lead to contradictory outcomes, how should the Core Facilitator identify and address this indirect conflict?\n\nWhat if one AEP effects a significant overhaul of an Atlas document, while another effects minor tweaks to the same component? How do the Facilitators determine which elements of which AEP should take precedence?\n\nIf one AEP drew more support than the other, does this automatically mean the former is the best update? What if the former AEP was authored by an unknown author, while the second AEP was authored by a well-known community member with high reputation?\n\nIf merging proposals in this fashion becomes a common practice, what issues could arise? There is a risk of governance paralysis, where no significant progress can be made because of a loop of constant revisions and counter-revisions. Community fatigue could set in, where stakeholders become disengaged from the governance process due to the perception that decisions are never final. The continuous cycle of evaluating, merging, and discarding parts of conflicting AEPs is not only time-consuming but also increases the complexity of governance operations.\n\nIf the Core Facilitator merge parts of two approved, but conflicting AEPs, and the final merged product significantly deviates from the original intents of both, the representation of SKY voters' will becomes a compelling question.","contentHash":"c5e4bc32f853a311922e341635b01177f20bfc3472ad34ad36d2f2e75494675f","addressRefs":[]},"12286b6c-0231-40e3-ab3f-234bc0249216":{"id":"12286b6c-0231-40e3-ab3f-234bc0249216","doc_no":"A.1.15.1.2","title":"Governance Security & Ecosystem Actor Embedding","type":"Core","depth":4,"parentId":"08dbb8ad-6481-41b4-b438-4b08425abefc","order":1055,"content":"As a temporary bootstrapping measure, incubating Ecosystem Actor Atlas Axis will be embedded in Core Facilitator-permissioned communication channels where Executive Vote-coordination work is performed. Atlas Axis will have no decision-making authority in the Executive Vote workstreams. The objective is solely to facilitate Atlas Axis’ preparation of comprehensive, robust and resilient Atlas data for Governance Security by enabling it to directly observe patterns and issues as they arise.","contentHash":"bd4ca7f284d5ca65d85c0873b6a953e6744b61035d2b47bb4ff324e7ac6a28c3","addressRefs":[]},"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0":{"id":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","doc_no":"A.2","title":"The Support Scope","type":"Scope","depth":1,"parentId":null,"order":1056,"content":"The Support Scope governs all routine aspects of ecosystem support, including governance process infrastructure and management, Agent support and Ecosystem Actor support.","contentHash":"0281d7ffbe9edfe351ad84e9766fdddfc8efbae4a7512f256cfb6147656a30dd","addressRefs":[]},"f83a880f-6440-49ac-8e28-b16b4e2c9912":{"id":"f83a880f-6440-49ac-8e28-b16b4e2c9912","doc_no":"A.2.1","title":"Governance Process Support","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1057,"content":"The Support Scope regulates the routine governance processes needed to operationalize the Atlas. This Article defines key infrastructure and processes supporting this objective.","contentHash":"6888eb6989927c377b9411d7e76dc75e6abeaebd5ee5b499f111b923fa3f9eee","addressRefs":[]},"ef1ad0bf-069c-4199-8620-a508b34c2348":{"id":"ef1ad0bf-069c-4199-8620-a508b34c2348","doc_no":"A.2.1.1","title":"Governance Process Support","type":"Section","depth":3,"parentId":"f83a880f-6440-49ac-8e28-b16b4e2c9912","order":1058,"content":"The Support Scope must facilitate the routine governance processes of the Sky Ecosystem, pursuant to the principles and procedures defined herein.","contentHash":"c3cc8f7a0fe28087b1033eccf57065b8e7f950ec0e26bf6667b3fce76d20b3c3","addressRefs":[]},"4b76256c-c625-49ce-a91d-88d3fbd2452f":{"id":"4b76256c-c625-49ce-a91d-88d3fbd2452f","doc_no":"A.2.1.1.1","title":"In General","type":"Core","depth":4,"parentId":"ef1ad0bf-069c-4199-8620-a508b34c2348","order":1059,"content":"Sky Governance deploys various core processes to implement its decision-making, including Aligned Delegate processes, the Weekly Governance Cycle, the Monthly Governance Cycle and the modification of Active Data. The Support Scope regulates routine governance processes based in the explicit rules of the Atlas. In contrast, the Governance Scope governs situations in which a document is appealed or is otherwise contentious for reasons of ambiguity or conflict with other documents.","contentHash":"fe6c0cf9f39357faaf63ed1eea22d35374a7ae5a65071848c25a7568c5163719","addressRefs":[]},"62e031ef-de5a-4425-8561-439b6f72a548":{"id":"62e031ef-de5a-4425-8561-439b6f72a548","doc_no":"A.2.1.1.1.0.3.1","title":"Ambiguity - Element Annotation","type":"Annotation","depth":5,"parentId":"4b76256c-c625-49ce-a91d-88d3fbd2452f","order":1060,"content":"The element \"ambiguity\" refers to instances where the language of an Atlas document allows for multiple possible interpretations.","contentHash":"ba18426f39701d367636191410777819e7b8eed4a5e71083f67b7da3ab5a7e89","addressRefs":[]},"6691933f-0d3f-4a20-b609-57001a6a3491":{"id":"6691933f-0d3f-4a20-b609-57001a6a3491","doc_no":"A.2.1.1.1.0.3.2","title":"Contentious - Element Annotation","type":"Annotation","depth":5,"parentId":"4b76256c-c625-49ce-a91d-88d3fbd2452f","order":1061,"content":"The element \"contentious\" describes a situation where there is disagreement or dispute regarding the interpretation, application, or validity of a document.","contentHash":"a8d001d016692f16843595248f1b785eb9d9d02c2e18c58966a54d44c3430f45","addressRefs":[]},"b5be838e-23a8-4ed4-b713-d5a57fe1864d":{"id":"b5be838e-23a8-4ed4-b713-d5a57fe1864d","doc_no":"A.2.1.1.1.0.3.3","title":"Document Is Appealed - Element Annotation","type":"Annotation","depth":5,"parentId":"4b76256c-c625-49ce-a91d-88d3fbd2452f","order":1062,"content":"The element means that a formal request has been made to the Core Facilitator to review an Atlas document for potential conflicts with other documents or misalignment. See [A.1.2.3 - Conflict Resolution](e883ceb7-707d-4b1d-af3c-ed6f9aeac565).","contentHash":"84fa5d37cd6f881b16ccdbfdb9713b439ff81f800f004aa3f57d92a445acf4d7","addressRefs":[]},"53388cf1-7934-4048-a372-2aec5e5b8430":{"id":"53388cf1-7934-4048-a372-2aec5e5b8430","doc_no":"A.2.1.1.2","title":"Coordination Of Scope Framework Processes","type":"Core","depth":4,"parentId":"ef1ad0bf-069c-4199-8620-a508b34c2348","order":1063,"content":"The Scopes establish various specialized processes, including those for submitting governance proposals or modifying the Atlas. Core GovOps is responsible for monitoring and ensuring that these processes are executed in accordance with the established rules. An action carried out through a Scope-defined process is considered valid only if Core GovOps has been properly notified.","contentHash":"7f7ca2882f00a8bd5acb13efa25dc473b06f4206da79e38a3896d5d013c19a39","addressRefs":[]},"f51addb2-fba3-476f-b3e4-1c5b4b9013fc":{"id":"f51addb2-fba3-476f-b3e4-1c5b4b9013fc","doc_no":"A.2.1.1.2.0.3.1","title":"Monitoring And Ensuring - Element Annotation","type":"Annotation","depth":5,"parentId":"53388cf1-7934-4048-a372-2aec5e5b8430","order":1064,"content":"This element refers to the ongoing responsibility of Core GovOps to monitor the progress of routine governance processes, check for compliance with the rules, and confirm that all necessary documentation and approvals are in place.","contentHash":"ca8a1cc04f7fd7748f1192450c6dd70e154afb3b755547d350a01e20d25aba2a","addressRefs":[]},"df31f503-1238-4380-9a0e-25e2ef7c81d0":{"id":"df31f503-1238-4380-9a0e-25e2ef7c81d0","doc_no":"A.2.1.1.2.0.3.2","title":"Properly Notified - Element Annotation","type":"Annotation","depth":5,"parentId":"53388cf1-7934-4048-a372-2aec5e5b8430","order":1065,"content":"This element means that Core GovOps have been informed in accordance with the prescribed procedures, including the timing, method, and content of the notification, as required by the relevant Scope.","contentHash":"02a3c47bb4b80331ea762a36f6a348d9986df4f3f16d63b294edf6ba2bc8bff4","addressRefs":[]},"d537c3df-287c-45a5-aa69-2b4242b2259f":{"id":"d537c3df-287c-45a5-aa69-2b4242b2259f","doc_no":"A.2.1.1.3","title":"Designation Of Governance Process Support Ecosystem Actors","type":"Core","depth":4,"parentId":"ef1ad0bf-069c-4199-8620-a508b34c2348","order":1066,"content":"Core GovOps can designate Ecosystem Actors (including individuals, companies or Forum or Chat pseudonyms) as Governance Process Support Ecosystem Actors. This designation can include granting them moderation rights and other forms of administration rights on the relevant communication channels.\n\nGovernance Process Support Ecosystem Actors can assist with governance processes including verifying Atlas Edit Proposals (AEPs), preparing and merging Pull Requests, updating the status of AEPs, preparing Polls, editing the Atlas, etc.","contentHash":"9c606114ef5688b9c4f210bea559fc9abf40c884245758e375b15a2d563e66b3","addressRefs":[]},"048600dc-3e21-4e1b-9e69-a0b5aff92ff8":{"id":"048600dc-3e21-4e1b-9e69-a0b5aff92ff8","doc_no":"A.2.1.1.4","title":"Resources","type":"Core","depth":4,"parentId":"ef1ad0bf-069c-4199-8620-a508b34c2348","order":1067,"content":"Core GovOps is granted a budget to procure the necessary administrative support and services from Governance Process Support Ecosystem Actors. The budget can only be used to perform tasks described in [A.2.1.1 - Governance Process Support](ef1ad0bf-069c-4199-8620-a508b34c2348) and its subdocuments. Core GovOps can modify the budget using an Operational Weekly Governance Cycle poll.","contentHash":"473269c5c9df87ee7991108c6071e42d5e258a3570e63409987a21994217711d","addressRefs":[]},"5efada66-f3d2-4e3e-b26c-123467069437":{"id":"5efada66-f3d2-4e3e-b26c-123467069437","doc_no":"A.2.1.1.4.1","title":"Current Budget","type":"Core","depth":5,"parentId":"048600dc-3e21-4e1b-9e69-a0b5aff92ff8","order":1068,"content":"The budget available to fund Governance Process Support tasks is 0 USDS per quarter.","contentHash":"55aef60e720583e8cc7d55f83fe2e266fdd67362932dbd6999cb8000639e5415","addressRefs":[]},"fcde2604-a138-4c1b-9d9a-14895835c907":{"id":"fcde2604-a138-4c1b-9d9a-14895835c907","doc_no":"A.2.2","title":"Sky Primitives","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1069,"content":"This Article governs the Sky Primitives. A Sky Primitive is a standardized interface that allows Agents to connect to, and leverage, Sky Protocol’s permissioned infrastructure. This Article defines each of the Sky Primitives available for Prime Agents to use to expand the Sky Ecosystem. Each Prime Agent strategy is unique, so each may combine the Sky Primitives differently.","contentHash":"d23b301357f1922a5ddb215453827df6c7e590a9d48136cfccb0f39fa33dbd19","addressRefs":[]},"df611e97-f99d-4244-8573-e706fbd1dfbc":{"id":"df611e97-f99d-4244-8573-e706fbd1dfbc","doc_no":"A.2.2.1","title":"Primitives In General","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1070,"content":"The documents herein define general principles relating to Agent Artifact evolution, enumerate the currently available Sky Primitives, and prescribe the procedures by which Agents can activate, invoke and deploy the Primitives.","contentHash":"7a53ead04b2e8f89a6b9e4c79d1399d8f086ae19dd283337ca6d9ec84a9eb686","addressRefs":[]},"73eb0d53-2746-4db8-8b61-608f7439d560":{"id":"73eb0d53-2746-4db8-8b61-608f7439d560","doc_no":"A.2.2.1.1","title":"Initial Stages Of Artifact Evolution","type":"Core","depth":4,"parentId":"df611e97-f99d-4244-8573-e706fbd1dfbc","order":1071,"content":"The documents herein define the initial stages of the lifecycle of an Agent Artifact, beginning with the prerequisite of capital deployment and continuing until the Agent gains full operational status with an active Executor Accord and Root Edit Primitive. At that point, the Agent is interoperable with other Sky Agents and possesses a formal governance process by which token holders can guide its activities.","contentHash":"909a60c89a5bc2d5a4331c43240929897debe8edd55954415c5833c764b96861","addressRefs":[]},"96ecd286-9361-4cb0-8062-9dd930780f3e":{"id":"96ecd286-9361-4cb0-8062-9dd930780f3e","doc_no":"A.2.2.1.1.1","title":"Founder Deposits Capital And Pays Agent Creation Fee","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1072,"content":"The prospective Agent founder kicks off the lifecycle of an Agent by deploying an initial minimum amount of capital and paying an Agent Creation fee in an off-chain process as defined in [A.2.2.3.1.1 - Capital Injection](bed7471a-54aa-4167-88dd-22ebd63f8827).","contentHash":"1eaa9566d7c47b22c27bc7e44e699478d21f55de4a01f75750fac824471485bc","addressRefs":[]},"b485d31f-e7e2-45fd-aefb-2a55206390a2":{"id":"b485d31f-e7e2-45fd-aefb-2a55206390a2","doc_no":"A.2.2.1.1.2","title":"Core GovOps Creates Scaffold Agent Artifact","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1073,"content":"After receiving the initial capital and Agent Creation fee, Core GovOps proceeds to set up a Scaffold Agent Artifact (\"Scaffold Artifact\"), which serves as a base template containing all Sky Primitives. In the Scaffold Artifact, the Global Activation Status of all Sky Primitives is initially set to `Inactive`. The sole exception is the Upkeep Rebate Primitive, whose Global Activation Status in the newly generated Scaffold Artifact is `Active` by default. See [A.2.2.1.2 - Primitive Global Activation Status](dde8cf4c-4823-4fea-96b8-a9b9d6b24533).","contentHash":"3c3517c068ae88c2306f7dcbcafbf7b7a05ff7e5691818cd867fe12b80ead193","addressRefs":[]},"1b66ee09-3e81-4ae3-b3df-69787e0f662a":{"id":"1b66ee09-3e81-4ae3-b3df-69787e0f662a","doc_no":"A.2.2.1.1.3","title":"Founder Inputs","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1074,"content":"The documents herein specify the Agent Founder’s inputs following the creation of the Scaffold Artifact.","contentHash":"a34c7bee4a540d53850cdd3d27d0fd991769f2e7b57247573fee30acaf35402c","addressRefs":[]},"1a48e833-d960-4bdf-8f67-0f9d9307e00d":{"id":"1a48e833-d960-4bdf-8f67-0f9d9307e00d","doc_no":"A.2.2.1.1.3.1","title":"Founder Required Primitive Activation","type":"Core","depth":6,"parentId":"1b66ee09-3e81-4ae3-b3df-69787e0f662a","order":1075,"content":"The Founder is responsible for Globally Activating the Agent Creation, Prime Transformation / Executor Transformation, Agent Token, Executor Accord, Root Edit, and Ecosystem Upkeep Fee Primitives.\n\nThe Primitives named above must first be Globally Activated before the Founder can Invoke them to finalize Agent setup. The Founder may choose to Globally Activate these Primitives individually at different times or all at once; only the Primitive Invocation must be done in a specified order.","contentHash":"e36285948e80132aec42cab029facc9433da21e6bddf59212cfd33f9dd15917c","addressRefs":[]},"a4f65994-2526-4522-a986-cd444a5cb896":{"id":"a4f65994-2526-4522-a986-cd444a5cb896","doc_no":"A.2.2.1.1.3.2","title":"Founder Access","type":"Core","depth":6,"parentId":"1b66ee09-3e81-4ae3-b3df-69787e0f662a","order":1076,"content":"_\"_Founder Access\" gives the Founder of an Agent the ability to freely edit the Scaffold Artifact, including Activating any desired Primitives and adding custom Omni Documents. \"Founder Access\" is revoked at the moment the Founder Invokes either the Prime Transformation or Executor Transformation Primitive. From that point on, the Founder cannot add or edit Omni Documents, but can only Activate and Invoke specific Primitives so that the Agent can complete setup. See [A.2.2.1.2.4.1 - Agent Launch And Sequence of Primitive Global Activation](2f5ff5c8-bcd1-44a4-ba56-2075ac8e9c61).","contentHash":"2a32a4153ae49bb05e7bea09084f84a8507f673dc5e4a2eba68b90413e4b1ef7","addressRefs":[]},"5dd07957-8e5b-4694-a0ba-a8aa88863552":{"id":"5dd07957-8e5b-4694-a0ba-a8aa88863552","doc_no":"A.2.2.1.1.3.2.1","title":"Short Term Suspension of “Founder Access”","type":"Core","depth":6,"parentId":"1b66ee09-3e81-4ae3-b3df-69787e0f662a","order":1077,"content":"In the short term, \"Founder Access\" will not be operational. Instead, if a Prime Founder wishes to edit their Scaffold Artifact, they must use the customary Atlas Edit Proposal processes specified in the Sky Core Atlas at [A.1.11.2 - Atlas Edit Weekly Cycle](14e99d92-71fc-44d9-9dbf-933bce2e1b32) or [A.1.12.2 - Atlas Edit Monthly Cycle](d2cbddd2-58ef-4311-a71d-d2c340364cb5).","contentHash":"2a709d4ef38776a241bc8b72c306b1071cc0e3ab06292029478db6c776bd0499","addressRefs":[]},"d0b283e9-dac1-49c6-8dd7-b061c7a87335":{"id":"d0b283e9-dac1-49c6-8dd7-b061c7a87335","doc_no":"A.2.2.1.1.3.3","title":"Founder Invokes Agent Creation Primitive","type":"Core","depth":6,"parentId":"1b66ee09-3e81-4ae3-b3df-69787e0f662a","order":1078,"content":"To proceed to the next stage, the Founder must Invoke the Agent Creation Primitive. From the Agent’s perspective, invoking, or calling, a Primitive always involves submitting required inputs into the respective Primitive itself. Here, the Agent Founder must input the name of the Agent and an introduction providing a brief overview of the Agent’s vision or business model into the Agent Creation Primitive.","contentHash":"ef4a9ed8e2c0943f6f209b2a5a1d91a60f35e5e20dd9a083949082c157c03cad","addressRefs":[]},"93d6147b-8760-431e-b38c-4a7afcb27e5f":{"id":"93d6147b-8760-431e-b38c-4a7afcb27e5f","doc_no":"A.2.2.1.1.4","title":"Core GovOps Validates Agent Creation Primitive Inputs","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1079,"content":"Core GovOps validates the Founder’s inputs into the Agent Creation Primitive and the \"Founder Access\"-related edits to the Scaffold Artifact, ensuring that all information is well specified and that the Scaffold Artifact is aligned.","contentHash":"8bc554da6f8e900ad89c6f679501d6d5aac376ad48b04088a70040acd4431adb","addressRefs":[]},"16d9dede-7fbf-4215-8e60-c06a8e6c3218":{"id":"16d9dede-7fbf-4215-8e60-c06a8e6c3218","doc_no":"A.2.2.1.1.5","title":"Core GovOps Creates Genesis And SubProxy Accounts","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1080,"content":"After validating the Scaffold Artifact and Agent Creation Primitive inputs, Core GovOps creates a Genesis Account and SubProxy Account for the Agent. This data is automatically added to the Agent Creation Primitive.","contentHash":"69241279e3dddd962c3021cc57b724477aed04b6857cab2313cc8b7e4f5e9662","addressRefs":[]},"2592b3d0-531e-42a3-a098-cf4b82bdd567":{"id":"2592b3d0-531e-42a3-a098-cf4b82bdd567","doc_no":"A.2.2.1.1.6","title":"Founder Invokes Prime / Executor Transformation Primitive","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1081,"content":"When ready, the Founder Invokes the Prime Transformation or Executor Transformation Primitive to become either a Prime Agent or Executor Agent, respectively.","contentHash":"7293ac8955b44efbf513bfcbe395fc22f77559273f0f4bbf6105f7e74b49bb66","addressRefs":[]},"05e70418-5dbf-4d02-9d2a-9afea6619dd0":{"id":"05e70418-5dbf-4d02-9d2a-9afea6619dd0","doc_no":"A.2.2.1.1.7","title":"Core GovOps Validates Transformation Primitive Inputs","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1082,"content":"Upon successful validation by Core GovOps, the Transformation Primitive is deployed and the Agent Artifact is upgraded to reflect that the Agent is either a Prime Agent or an Executor Agent.","contentHash":"22dc54b6299be4c877bbd856ec4b9d08d1e2ea2a83858198c5fc33d5531f0ea0","addressRefs":[]},"20f4cfe0-1855-4942-ac0d-f5cb738e82fc":{"id":"20f4cfe0-1855-4942-ac0d-f5cb738e82fc","doc_no":"A.2.2.1.1.8","title":"Post-Transformation Primitive Artifact Freeze","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1083,"content":"After the Transformation Primitive is successfully Invoked, the Agent’s \"Founder Access\" is revoked. The Founder can no longer freely edit the Agent Artifact, but may only Invoke certain Primitives in a specified order until the Agent setup is complete.","contentHash":"7e515be01f1c76ddd086d8c817a0c62bfb3e1aae41bf0d6dd80a14c0d1dda1f7","addressRefs":[]},"f5132655-afdd-4a93-adbe-64526759720c":{"id":"f5132655-afdd-4a93-adbe-64526759720c","doc_no":"A.2.2.1.1.9","title":"Founder Invokes Agent Token Primitive","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1084,"content":"The Founder next Invokes the Agent Token Primitive to create a token for the Agent that can be used to raise capital, build a community, and conduct governance processes.","contentHash":"48022e11cf6fab711dac9c39b201fd10c951f18c4080f71c6c376eabefeee7d0","addressRefs":[]},"416dc0f2-fb0d-4ea2-975d-9bf2d9b0e1d4":{"id":"416dc0f2-fb0d-4ea2-975d-9bf2d9b0e1d4","doc_no":"A.2.2.1.1.10","title":"Core GovOps Validates Agent Token Primitive Inputs","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1085,"content":"Core GovOps reviews the inputs to the Agent Token Primitive to ensure that they are well specified and aligned.","contentHash":"cb6367a9bf20ae41465b066815f788ac4e986eb38750e9b5d81ad4fbf789422d","addressRefs":[]},"0e033de5-ce15-45df-ae85-9ed69bd40da0":{"id":"0e033de5-ce15-45df-ae85-9ed69bd40da0","doc_no":"A.2.2.1.1.11","title":"Core GovOps Mints Tokens","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1086,"content":"After validating the Agent Token Primitive inputs, Core GovOps proceeds to mint the Agent’s initial supply of tokens according to the instructions specified in the Primitive.","contentHash":"392771b2f9d6adc7855a7b440c925523b43be664fca619ddadb2c637da332930","addressRefs":[]},"9b074b3d-73db-4a3a-9491-571021e4e61b":{"id":"9b074b3d-73db-4a3a-9491-571021e4e61b","doc_no":"A.2.2.1.1.12","title":"Agent Invokes Executor Accord Primitive","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1087,"content":"The Agent must reach an understanding with an Operational Executor Agent that will operationalize the Agent’s strategy. After doing so, the Agent records this understanding by invoking the Executor Accord Primitive. Note that this step is only applicable to Prime Agents.","contentHash":"6aa878b27abae377df1688538a6a2bb86f5570c11b7cbd817699135ae447d215","addressRefs":[]},"c1ff42c9-1ffc-46f0-9dac-da54eb4eb042":{"id":"c1ff42c9-1ffc-46f0-9dac-da54eb4eb042","doc_no":"A.2.2.1.1.13","title":"Core GovOps Validates Executor Accord Primitive Inputs","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1088,"content":"CoreGovOps reviews the inputs to the Executor Accord Primitive to ensure that there is a valid Executor Accord with an Executor Agent and that the terms of the Executor Accord are reasonably specific. Upon successful validation, the Executor Accord Primitive is considered successfully Invoked and the Artifact is upgraded to include the Executor Accord. Now that the Agent has a documented relationship with an Executor Agent, Core GovOps will no longer perform validation of the Agent’s Primitive inputs. Instead, Operational GovOps associated with the Executor Agent specified in the Executor Accord will carry out certain operational tasks on behalf of the Prime Agent see [A.1.14.3.4 - Agent Role Delineation](fdf32ca5-5e2e-481e-9047-4d1599547216).","contentHash":"e561f11fd616877f36e4a653dd8afe66fce4f3e5542f4528ed73928c3123dcf4","addressRefs":[]},"63f85a1a-da2d-4828-ae32-da56f46d500d":{"id":"63f85a1a-da2d-4828-ae32-da56f46d500d","doc_no":"A.2.2.1.1.14","title":"Agent Invokes Root Edit Primitive","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1089,"content":"The Agent Invokes the Root Edit Primitive and sets up a governance process for voting to occur.","contentHash":"64c749b121336332566b4588c9f2234bb1e67f801c317c10c8e9e8af06d30802","addressRefs":[]},"d5ee3f2c-cd2f-4428-974b-341e4cce7295":{"id":"d5ee3f2c-cd2f-4428-974b-341e4cce7295","doc_no":"A.2.2.1.1.15","title":"Operational GovOps Validates Root Edit Primitive Inputs","type":"Core","depth":5,"parentId":"73eb0d53-2746-4db8-8b61-608f7439d560","order":1090,"content":"Operational GovOps reviews the inputs to the Root Edit Primitive to ensure it specifies a process that they can operationalize and does not conflict with any of the requirements regarding the voting process set forth in the Sky Core Atlas.\n\nUpon validation, the Root Edit Primitive is considered successfully Invoked, and the Artifact is upgraded with its functionality. At this point the Agent is fully operational. The Agent Artifact can only be edited through a token holder vote or, if applicable, by the Operational Executor Facilitator as authorized by Omni Documents. The Agent can Invoke and deploy any Primitives that it has previously Activated and can also Activate additional Primitives through a Root Edit.","contentHash":"19f0debdebbb1be6dd55c59ea12035be1d86392fee37f6a90e32107cd96f0597","addressRefs":[]},"dde8cf4c-4823-4fea-96b8-a9b9d6b24533":{"id":"dde8cf4c-4823-4fea-96b8-a9b9d6b24533","doc_no":"A.2.2.1.2","title":"Primitive Global Activation Status","type":"Core","depth":4,"parentId":"df611e97-f99d-4244-8573-e706fbd1dfbc","order":1091,"content":"The documents herein define Primitive Global Activation Status.","contentHash":"fbd0e21f3bbd646afeede6b94454d30bd439b0d1efff3dc016f75e65498533eb","addressRefs":[]},"dcd0bead-7ad1-4fe0-b485-b3565d670c78":{"id":"dcd0bead-7ad1-4fe0-b485-b3565d670c78","doc_no":"A.2.2.1.2.1","title":"Primitives Must First Be Activated To Be Invoked","type":"Core","depth":5,"parentId":"dde8cf4c-4823-4fea-96b8-a9b9d6b24533","order":1092,"content":"An Agent may only Invoke a Primitive that it has previously Globally Activated; the process of Invocation is defined below at [A.2.2.1.3.3 - Changing Primitive Instance Status](263f3b28-9cd4-4ba2-b8e5-152c2ce0c050). In this way, an Agent’s decision regarding which Primitives to Activate allows the Agent to express its strategy to token holders. For example, an Agent that was focused on asset gathering might Globally Activate the Distribution Reward and Integration Boost Primitives, but not the Allocation System Primitive.","contentHash":"3f10e63478e1276f7aa934a426f7930d7696a8dc36fee570be3f690f6f36b787","addressRefs":[]},"377150b3-d64b-4436-ab6d-758b05d82f26":{"id":"377150b3-d64b-4436-ab6d-758b05d82f26","doc_no":"A.2.2.1.2.2","title":"Initial Primitive Global Activation Status","type":"Core","depth":5,"parentId":"dde8cf4c-4823-4fea-96b8-a9b9d6b24533","order":1093,"content":"Scaffold Artifacts by default include all Sky Primitives. To begin with, all Sky Primitives have the Global Activation Status of `Inactive`; the exception is the Upkeep Rebate Primitive, which comes Globally Activated in all Scaffold Artifacts.","contentHash":"d7fc2ca25a912174d63572ebd1919dd66253e3febcef86a0d4d57bcd978ee779","addressRefs":[]},"1560f392-db95-43d0-968b-af8d1afa4e84":{"id":"1560f392-db95-43d0-968b-af8d1afa4e84","doc_no":"A.2.2.1.2.3","title":"Primitive Activation Does Not Require Invocation","type":"Core","depth":5,"parentId":"dde8cf4c-4823-4fea-96b8-a9b9d6b24533","order":1094,"content":"Activation gives the Agent the ability to Invoke a Primitive (thereby creating an instance of that Primitive), but does not require the Agent to do so.","contentHash":"e05398be9e38aac5f455a5d60f151bef13fa0ac4b6bd4a6113297fb2e7124c9c","addressRefs":[]},"51cfca28-c8de-457a-abc4-8ce1f64abb91":{"id":"51cfca28-c8de-457a-abc4-8ce1f64abb91","doc_no":"A.2.2.1.2.4","title":"Changing A Primitive’s Global Activation Status","type":"Core","depth":5,"parentId":"dde8cf4c-4823-4fea-96b8-a9b9d6b24533","order":1095,"content":"An Agent can change the Global Activation Status of a Primitive as defined herein.","contentHash":"0f99940490e492ffdf0593568824843669a1d719f01c92aa435fca63f670a458","addressRefs":[]},"2f5ff5c8-bcd1-44a4-ba56-2075ac8e9c61":{"id":"2f5ff5c8-bcd1-44a4-ba56-2075ac8e9c61","doc_no":"A.2.2.1.2.4.1","title":"Agent Launch And Sequence of Primitive Global Activation","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1096,"content":"Sky Primitives can be Globally Activated (and their instances later Invoked) by an Agent at different points in the Artifact’s lifecycle. The process is divided into three main stages, outlined in the documents herein.","contentHash":"27182197c94dd1709907017dad434cb7292e75f619250d60701964379199dc7f","addressRefs":[]},"b5cbcb47-ff44-4809-8071-2b5f7b30efbb":{"id":"b5cbcb47-ff44-4809-8071-2b5f7b30efbb","doc_no":"A.2.2.1.2.4.1.1","title":"“Pre Transformation Primitive” Stage","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1097,"content":"After the Scaffold Artifact has been established, but before invoking the Prime Transformation or Executor Transformation Primitive, the Agent Founder retains unilateral authority (\"Founder Access\") to Activate any desired Primitives while freely editing the Agent Artifact. The Founder must Globally Activate the Ecosystem Upkeep Fee Primitive during this stage. No Operational Executor Facilitator approval or token holder vote is required at this stage. See [A.2.2.1.1.3.2 - Founder Access](a4f65994-2526-4522-a986-cd444a5cb896).","contentHash":"42a19effce9f2dbd8ef3ac242639410ddf1525f3f14e3f022a94e085240c0011","addressRefs":[]},"7b25b220-92f9-4936-8296-31c0f3d8ddbc":{"id":"7b25b220-92f9-4936-8296-31c0f3d8ddbc","doc_no":"A.2.2.1.2.4.1.2","title":"“Pre Root Edit Primitive” Stage","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1098,"content":"After the Prime Transformation or Executor Transformation Primitive has been Invoked, but before the Root Edit Primitive is Invoked, the Agent Founder can no longer freely edit the Artifact. During this period, the Agent must Activate and Invoke (1) the Agent Token Primitive, then (2) the Executor Accord Primitive, and finally (3) the Root Edit Primitive, in that order, to complete its governance setup - assuming that these Primitives were not already Globally Activated during the \"Pre Transformation Primitive\" Stage. No other Primitives can be Globally Activated by the Agent during this period.","contentHash":"76f35adab9a90a972cefc47cb78622cea5615c29048568e2cf6693866f6db423","addressRefs":[]},"857b85e5-b57e-4043-82eb-6fbb68cf1d51":{"id":"857b85e5-b57e-4043-82eb-6fbb68cf1d51","doc_no":"A.2.2.1.2.4.1.3","title":"“Post Root Edit Primitive” Stage","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1099,"content":"After the Root Edit Primitive is Invoked, changing the Global Activation Status of a Primitive - whether activating or deactivating - requires a token holder vote and review by the Operational Executor Facilitator.","contentHash":"356eaa28fd6e7e8311ffac60cea4352e0ad9ced685cb2060d62ae4bce687dcba","addressRefs":[]},"d0fb8761-2fcb-4d81-b498-38cd44f47fb0":{"id":"d0fb8761-2fcb-4d81-b498-38cd44f47fb0","doc_no":"A.2.2.1.2.4.2","title":"Global Primitive Deactivation","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1100,"content":"Generally, a Prime Agent may freely deactivate a Primitive’s Global Status pursuant to the governance process defined in its Root Edit Primitive. However, there are exceptions to this rule given the special functionality of certain Primitives. See [A.2.2.1.2.4.2.1 - Prohibition On Deactivating Certain Primitives](3ce3a1ae-9300-4159-9676-261d0404360f).\n\nIf a Primitive’s Global Status is deactivated, _all_ existing instances of that Primitive immediately become `Suspended`. While the Primitive remains Globally Inactive, the Agent is barred from creating new instances or reactivating existing instances of that Primitive.","contentHash":"3c1f85542911d410df29d0e1608d240304f497ac927ff05f17aa68fee72bf01e","addressRefs":[]},"3ce3a1ae-9300-4159-9676-261d0404360f":{"id":"3ce3a1ae-9300-4159-9676-261d0404360f","doc_no":"A.2.2.1.2.4.2.1","title":"Prohibition On Deactivating Certain Primitives","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1101,"content":"The documents herein specify the Sky Primitives that, once Globally Activated, cannot be deactivated.","contentHash":"bc8432d3cb9457ca8d518c700fd5ef9b48e0ebeb1d5e05e615aff4d202dbe878","addressRefs":[]},"04bbf091-b2a8-47e4-ad03-f3fd66e70279":{"id":"04bbf091-b2a8-47e4-ad03-f3fd66e70279","doc_no":"A.2.2.1.2.4.2.1.1","title":"Prohibition On Deactivating Genesis Primitives","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1102,"content":"Once Activated, the Agent Creation, Prime / Executor Transformation, and Agent Token Primitives cannot be deactivated. These Primitives are deployed once, and thereafter their Global Status is `Completed` and cannot be altered.","contentHash":"efeb0603e30580913075135c6d8c2132ab5bce00b7bb250bc4ccadc0cdc1675e","addressRefs":[]},"a4797404-1015-4cd5-a2ea-bc1a2699b575":{"id":"a4797404-1015-4cd5-a2ea-bc1a2699b575","doc_no":"A.2.2.1.2.4.2.1.2","title":"Prohibition On Deactivating Executor Accord And Root Edit Primitives","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1103,"content":"To maintain recognized operational status within the ecosystem, Agents must have active Executor Accord and Root Edit Primitives at all times. Once Globally Activated, these Primitives cannot be deactivated, as doing so renders the Agent unable to operate or make further changes to its Artifact. Should an Agent seek to wind down, rather than deactivating these Primitives, it must follow the approved termination process defined in [A.1.14.5 - Agent Termination Protocol](fe833d0e-8451-45e0-84a5-229d6ec964a8).","contentHash":"0496e85bf0dafc0665eded58734214b058d33e231c3eeb2ba7d8c59f02cc1791","addressRefs":[]},"85121142-aa54-4957-b0e1-8f4294512c7e":{"id":"85121142-aa54-4957-b0e1-8f4294512c7e","doc_no":"A.2.2.1.2.4.2.1.3","title":"Prohibition On Deactivating Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1104,"content":"The Upkeep Rebate Primitive is by default Globally Activated in all Scaffold Agent Artifacts; it is not possible to deactivate it.","contentHash":"fe16fffa447ae79127baa036c19413912978468f360ee42b91c9e1d8a9d61b9e","addressRefs":[]},"984dcacc-d242-4203-90c2-d5cf61c92702":{"id":"984dcacc-d242-4203-90c2-d5cf61c92702","doc_no":"A.2.2.1.2.4.2.1.4","title":"Prohibition On Deactivating Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1105,"content":"An Agent must always have the Ecosystem Upkeep Fee Primitive Globally Activated; once Activated, it cannot be deactivated.","contentHash":"3bad4a864d48435f8c9108e643ad0d2b81becd530a76c2f6c5c4281a480dc681","addressRefs":[]},"cb452f09-007a-4000-a37f-46e8be48c066":{"id":"cb452f09-007a-4000-a37f-46e8be48c066","doc_no":"A.2.2.1.2.4.2.2","title":"Global Primitive Reactivation","type":"Core","depth":6,"parentId":"51cfca28-c8de-457a-abc4-8ce1f64abb91","order":1106,"content":"An Agent may reactivate a Globally Inactive Primitive according to the governance process defined in its Root Edit Primitive. Reactivating the Primitive restores the Agent’s ability to create new instances (via proper Invocation) but does _not_ automatically revive previously deactivated instances. Each existing instance remains inactive unless separately reactivated through the appropriate governance process.","contentHash":"321625a0cde92f28df3bf23634f234de613bc3525a82a7d0278fa603f3414620","addressRefs":[]},"4531962c-9847-40d6-b534-8a3a301703d0":{"id":"4531962c-9847-40d6-b534-8a3a301703d0","doc_no":"A.2.2.1.3","title":"Primitive Instance Status","type":"Core","depth":4,"parentId":"df611e97-f99d-4244-8573-e706fbd1dfbc","order":1107,"content":"The documents herein define Primitive Instance Status.","contentHash":"0a280195793647f4eb44a53a6d19cd7b258f224bfdab986f7dfd8f188cb29e23","addressRefs":[]},"f507250e-8558-4692-914d-7760ea266a50":{"id":"f507250e-8558-4692-914d-7760ea266a50","doc_no":"A.2.2.1.3.1","title":"Primitive Instance Status Definition","type":"Core","depth":5,"parentId":"4531962c-9847-40d6-b534-8a3a301703d0","order":1108,"content":"Each valid Invocation of a Primitive causes the Agent Artifact to be updated with a specific instance of a Primitive. For example, each Invocation of the Token SkyLink Primitive launches a SkyLink deployment to a specific blockchain. The Agent may manage each Primitive instance independently (e.g., Activate or suspend it as circumstances change). A Primitive instance thus has its own Status or life cycle that is independent of the Primitive’s Global Activation Status.","contentHash":"f452ea2dc9393139693c2476e4f84af8df0c21f938edd469663512414d27fd91","addressRefs":[]},"d3908a6c-a5b4-40d3-a982-89ad606a24d9":{"id":"d3908a6c-a5b4-40d3-a982-89ad606a24d9","doc_no":"A.2.2.1.3.2","title":"Instance Status Values","type":"Core","depth":5,"parentId":"4531962c-9847-40d6-b534-8a3a301703d0","order":1109,"content":"The documents herein specify the potential values of the Status of an instance of a Primitive. An instance of a Primitive must always have exactly one of these values.","contentHash":"dfea810e7f2a620b66d60caeaf0b005758a43d6535c1e559e61b3ca0ec04223d","addressRefs":[]},"dfd19e92-2660-4393-8dff-a3a7e4ad75ff":{"id":"dfd19e92-2660-4393-8dff-a3a7e4ad75ff","doc_no":"A.2.2.1.3.2.1","title":"Active Instance Status","type":"Core","depth":6,"parentId":"d3908a6c-a5b4-40d3-a982-89ad606a24d9","order":1110,"content":"The instance Status of `Active` indicates that an instance of a Primitive is fully operational and may be used for its intended purpose by the Agent and potentially other parties. For example, a Token SkyLink deployment is active and can be used to bridge tokens between blockchains.","contentHash":"52d9231fe4af89c6df5bceaee68818278b974f073674758ed90cc5931cd832e8","addressRefs":[]},"3e5de640-5bc2-4953-a233-913e3337b4bb":{"id":"3e5de640-5bc2-4953-a233-913e3337b4bb","doc_no":"A.2.2.1.3.2.2","title":"Suspended Instance Status","type":"Core","depth":6,"parentId":"d3908a6c-a5b4-40d3-a982-89ad606a24d9","order":1111,"content":"The instance Status of `Suspended` indicates that an instance of a Primitive was `Active` at one point in time and may be `Active` again, but is not currently operational. This may be due to the Primitive not meeting performance expectations (e.g. for an Allocation System instance), security issues, or due to failure of the Agent operating the Primitive to satisfy other requirements such as those specified in the Risk Capital or Asset Liability Management frameworks.","contentHash":"345905bff2032316ec20dcebdf932f8ae5ebf4805c61867f2dbd34cd784d8b96","addressRefs":[]},"82b88f94-b83a-432a-bb8e-4e726535156a":{"id":"82b88f94-b83a-432a-bb8e-4e726535156a","doc_no":"A.2.2.1.3.2.3","title":"Completed Instance Status","type":"Core","depth":6,"parentId":"d3908a6c-a5b4-40d3-a982-89ad606a24d9","order":1112,"content":"The instance Status of `Completed` indicates that an Instance of a Primitive has reached a terminal state and will not become `Active` again. This status applies in two cases: 1) a previously active Instance has permanently ceased operations; or 2) an Instance designed for a single Invocation has achieved its intended outcome and requires no further management (e.g., the one-time deployment of the Prime Transformation Primitive).","contentHash":"fce1b1b161dcc1d94be631f0bd9eed71466ea72973b9a80d015062df58528bc0","addressRefs":[]},"263f3b28-9cd4-4ba2-b8e5-152c2ce0c050":{"id":"263f3b28-9cd4-4ba2-b8e5-152c2ce0c050","doc_no":"A.2.2.1.3.3","title":"Changing Primitive Instance Status","type":"Core","depth":5,"parentId":"4531962c-9847-40d6-b534-8a3a301703d0","order":1113,"content":"A Prime Agent that has a Globally Active Primitive may freely create (assuming the Primitive was properly Invoked), suspend, archive, or update individual instances of that Primitive, subject to the rules defined in the Agent Artifact and the Sky Core Atlas. For example, the Agent may run multiple Integration Boost instances in parallel (each with its own markets and configurations), toggling them on or off as needed, without affecting the underlying Integration Boost Primitive’s Global Activation Status. Changing a Primitive’s Instance-Level Status can be effected through the governance process defined in the Root Edit Primitive, or through an appropriately configured Omni Document. See [A.1.14.2.7.2 - Omni Document Process](26ec6b08-8187-44b4-abb3-aee3868161a4).","contentHash":"efd7bc17b412f8d5aea13cf10cb129f37e6202c952de4a6353fea3c9337cfc76","addressRefs":[]},"da763556-c316-431d-b57e-cc4df5a52fb8":{"id":"da763556-c316-431d-b57e-cc4df5a52fb8","doc_no":"A.2.2.1.4","title":"Invocation of Primitive Instance","type":"Core","depth":4,"parentId":"df611e97-f99d-4244-8573-e706fbd1dfbc","order":1114,"content":"The documents herein define the process by which an Agent may Invoke instances of Sky Primitives. If the Invocation is valid, the Agent Artifact is upgraded and the Agent gains the Primitives’ specific functionality.","contentHash":"8f202c9ad6f2fb1a2bd69de7bd79a0dba81d4fe561bdaa68350acbb9e0e2a391","addressRefs":[]},"83ac15ef-30e5-4958-95f4-a7bc2de10e97":{"id":"83ac15ef-30e5-4958-95f4-a7bc2de10e97","doc_no":"A.2.2.1.4.1","title":"Invocation Status","type":"Core","depth":5,"parentId":"da763556-c316-431d-b57e-cc4df5a52fb8","order":1115,"content":"The documents herein define the Statuses assigned to an Invocation that is in progress.","contentHash":"a656f09053ebe179936561d7d5cde5c1fb9161c95c8f89739be2e27f3c5cb204","addressRefs":[]},"316daff4-3260-45da-afde-eea3d357b9eb":{"id":"316daff4-3260-45da-afde-eea3d357b9eb","doc_no":"A.2.2.1.4.2","title":"Required Inputs Into Sky Primitive","type":"Core","depth":5,"parentId":"da763556-c316-431d-b57e-cc4df5a52fb8","order":1116,"content":"To Invoke a Primitive, an Agent must supply all required inputs as defined in the Sky Core Atlas. Every Primitive instance abides by a standardized data model specified at the Sky Core level, ensuring that all Prime Agents, Executor Agents and other actors are able to submit and track the necessary data reliably.","contentHash":"515fea6603583dcc3b4f4d76d39c8fe58878dd0808abed21a1b902b634adb0cf","addressRefs":[]},"3a8fe63b-a95d-4c6d-b8ae-48f4fe62e4c3":{"id":"3a8fe63b-a95d-4c6d-b8ae-48f4fe62e4c3","doc_no":"A.2.2.1.4.2.1","title":"Required Inputs Submitted To Powerhouse","type":"Core","depth":6,"parentId":"316daff4-3260-45da-afde-eea3d357b9eb","order":1117,"content":"The actual submission and handling of these data inputs occurs exclusively through the Powerhouse interface, which serves as the Sky ecosystem’s shared data infrastructure. Powerhouse thus becomes the canonical gateway for exchanging information with the Primitive, enforcing consistency in both the format of the data and the steps taken to Invoke (and later update) the Primitive.","contentHash":"275a2ca240d07c1873691bf29b8599315944aa8934a59b57cf73512de566a9de","addressRefs":[]},"c1e8985f-a21d-4264-b0e3-7cebee40e062":{"id":"c1e8985f-a21d-4264-b0e3-7cebee40e062","doc_no":"A.2.2.1.4.3","title":"Validation of Primitive Inputs","type":"Core","depth":5,"parentId":"da763556-c316-431d-b57e-cc4df5a52fb8","order":1118,"content":"Once the Agent has provided all required inputs to the relevant Primitive(s), the proposed Artifact Update undergoes review / validation by designated actors such as Operational Executor Facilitators. The identity and responsibilities of these actors are detailed in subsequent documents of this Article.","contentHash":"130fd4ce12e3b30dfa11e192ce71d2966abb656bd756ced8f82a29d1538a077d","addressRefs":[]},"a06c8e7a-e20f-459a-99e3-a62a5c0c4fd1":{"id":"a06c8e7a-e20f-459a-99e3-a62a5c0c4fd1","doc_no":"A.2.2.1.4.4","title":"Token Holder Vote","type":"Core","depth":5,"parentId":"da763556-c316-431d-b57e-cc4df5a52fb8","order":1119,"content":"After the Primitive inputs have been validated, Agent token holders vote on whether to upgrade the Artifact with the Primitive(s).","contentHash":"a4c25cd2d8bbd02ca2dc53367ad1158730c4bbfc290dfdfc1790b8b743c52523","addressRefs":[]},"6948d758-ad79-47b8-8466-74c75ec9db9e":{"id":"6948d758-ad79-47b8-8466-74c75ec9db9e","doc_no":"A.2.2.1.4.5","title":"Formal Integration Of Primitives","type":"Core","depth":5,"parentId":"da763556-c316-431d-b57e-cc4df5a52fb8","order":1120,"content":"If the vote is successful, the Agent Artifact is officially upgraded with a Primitive Instance, which latter has its own independent Status that is distinct from the Primitive’s Global Activation Status. See [A.2.2.1.3 - Primitive Instance Status](4531962c-9847-40d6-b534-8a3a301703d0). This upgrade means that the respective Primitive(s) is formally integrated into the Agent’s Artifact and the Atlas as a whole; the Prime Agent can now operationalize the Primitive’s special functionality.","contentHash":"ef1731a736f3139790fda213af5a7677a55c33f094a048d608a650bb829d2b07","addressRefs":[]},"947a5b27-d2dc-41e4-b6fd-696e35e2929d":{"id":"947a5b27-d2dc-41e4-b6fd-696e35e2929d","doc_no":"A.2.2.1.5","title":"Primitives","type":"Core","depth":4,"parentId":"df611e97-f99d-4244-8573-e706fbd1dfbc","order":1121,"content":"The documents herein list the current Sky Primitives and set forth the process for amending them. Each Primitive is defined in more detail below.","contentHash":"e0dfc9c09024fe8972aa8803e01b94f0f4ef37a490cb32de91b0c9d0edf15781","addressRefs":[]},"203b8c79-c7cf-4fcc-94e3-5bf42f791619":{"id":"203b8c79-c7cf-4fcc-94e3-5bf42f791619","doc_no":"A.2.2.1.5.1","title":"Current Primitives","type":"Core","depth":5,"parentId":"947a5b27-d2dc-41e4-b6fd-696e35e2929d","order":1122,"content":"The current Sky Primitives are:\n\n- Genesis Primitives\n    - Agent Creation Primitive\n    - Prime Transformation Primitive\n    - Executor Transformation Primitive\n    - Agent Token Primitive\n- Operational Primitives\n    - Executor Accord Primitive\n    - Root Edit Primitive\n    - Light Agent Primitive\n- Ecosystem Upkeep Primitives\n    - Ecosystem Upkeep Fee Primitive\n    - Upkeep Rebate Primitive\n- SkyLink Primitives\n    - Token SkyLink Primitive\n- Demand Side Stablecoin Primitives\n    - Distribution Reward Primitive\n    - Integration Boost Primitive\n    - Pioneer Chain Primitive\n- Supply Side Stablecoin Primitives\n    - Allocation System Primitive\n    - Junior Risk Capital Rental Primitive\n    - Asset Liability Management Rental Primitive\n- Core Governance Primitives\n    - Core Governance Reward Primitive","contentHash":"7823250c198d6d84645d41b06f59f2f33d7f8b7b2e6a993635ac2ebf75b0f62c","addressRefs":[]},"1a46fd49-7b37-4a14-a311-eb1dbe947d85":{"id":"1a46fd49-7b37-4a14-a311-eb1dbe947d85","doc_no":"A.2.2.1.5.2","title":"Amendments To Primitives","type":"Core","depth":5,"parentId":"947a5b27-d2dc-41e4-b6fd-696e35e2929d","order":1123,"content":"The set of available Sky Primitives may be amended in accordance with the governance processes established in the Sky Core Atlas.","contentHash":"8c884b2581c0c5d37112674e8855aed464c46ed3da951929677ca05a66d3997c","addressRefs":[]},"bdbb8ac9-d87e-4052-9e69-8267f38a54cf":{"id":"bdbb8ac9-d87e-4052-9e69-8267f38a54cf","doc_no":"A.2.2.2","title":"Primitive Process Definition Schema","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1124,"content":"Process Definitions function as the first-class objects through which Sky Primitives transform high-level governance logic into actionable document-driven workflows. All Sky Primitive Process Definitions are structured according to a common data schema - a set of fields that describe when they can start, how they run step by step, and what they must input or produce upon completion.\n\nThe documents herein define this data schema for Sky Primitive Process Definitions, which are applied to the universal specifications for each Sky Primitive. This common data schema aligns the entire ecosystem, while each Agent Artifact automatically references and extends the universal rules to incorporate the Agent’s unique Instance-level strategies, parameters and document-driven process flows.\n\nAt present, only the Distribution Reward Primitive and the Integration Boost Primitive specifications are structured using this schema. In future iterations of the Atlas, the schema will be applied to all Primitive specifications in this Article.","contentHash":"56b61464acbf9bed448e0271704349846425b69cbf16f32057a81ee311b77236","addressRefs":[]},"5df2043c-000a-4627-9c3a-2fdc12b78c47":{"id":"5df2043c-000a-4627-9c3a-2fdc12b78c47","doc_no":"A.2.2.2.1","title":"Process Initiation Logic","type":"Core","depth":4,"parentId":"bdbb8ac9-d87e-4052-9e69-8267f38a54cf","order":1125,"content":"The documents herein define when a Process is triggered, and what conditions must be satisfied, if any, for the Process to properly initiate.","contentHash":"3749a9de64bea6071994baa98a43d6cde46858f113b9dded92e1f550bb723d9a","addressRefs":[]},"134d8e80-6ec7-49fe-b7bb-6846694be11c":{"id":"134d8e80-6ec7-49fe-b7bb-6846694be11c","doc_no":"A.2.2.2.1.1","title":"Triggers","type":"Core","depth":5,"parentId":"5df2043c-000a-4627-9c3a-2fdc12b78c47","order":1126,"content":"The presence of a Time-Based Trigger or Document Update Trigger for a given Process does not necessarily mean such Trigger is the sole means to initiate the Process. For example, an Atlas Document that is external to the Sky Primitives specifications may authorize a Facilitator to manually initiate a process.","contentHash":"e83b3eb5e3da4b94bb3305841178d70e21804ba8db0fb20e4713558d12cf1e2b","addressRefs":[]},"1040dd2b-e7f8-4f68-b6c6-4b910f394a5a":{"id":"1040dd2b-e7f8-4f68-b6c6-4b910f394a5a","doc_no":"A.2.2.2.1.1.1","title":"Time-Based Trigger","type":"Core","depth":6,"parentId":"134d8e80-6ec7-49fe-b7bb-6846694be11c","order":1127,"content":"This field defines the triggering date/time for recurring or scheduled Processes.","contentHash":"890cd557010ca9992de04f294e67ef7d7b67b0871c573ce3f5f5e0ed184d981b","addressRefs":[]},"16be342d-0584-4092-9943-97a8c4eeb672":{"id":"16be342d-0584-4092-9943-97a8c4eeb672","doc_no":"A.2.2.2.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"134d8e80-6ec7-49fe-b7bb-6846694be11c","order":1128,"content":"Document Update Triggers are a type of gating condition that automatically or deterministically compels initiation of a Process in response to a specific Core Atlas or Agent Artifact Document Update in a previous Process Definition.\n\nOnce the specified Atlas or Artifact Document Update occurs (and assuming any specified Dependencies are also met), the Process must be initiated.\n\nIf no such deterministic Document Update-based trigger exists for a Process to initiate, this field is set to \"None.\"","contentHash":"23795ebd8119b32d01efae79fbb23d9008f3f5bc5146e15abf4ac58ed15a2cd9","addressRefs":[]},"64bec5dc-e288-4c8e-b638-c7180a92aca9":{"id":"64bec5dc-e288-4c8e-b638-c7180a92aca9","doc_no":"A.2.2.2.1.2","title":"Dependencies","type":"Core","depth":5,"parentId":"5df2043c-000a-4627-9c3a-2fdc12b78c47","order":1129,"content":"Dependencies are gating conditions that must be satisfied for the Process to be able to proceed, regardless of a triggering event.\n\nExamples of Dependencies include actors possessing suitable permissions, or a key stakeholder consenting to move forward.\n\nIf a trigger has occurred, but Dependencies are unmet, the Process cannot proceed.","contentHash":"8cd07ce7735ed6488016dc4b9650ed26d2552f611461a89908677e2591542925","addressRefs":[]},"6964c2d4-2994-487b-b68a-f1df5fa916f7":{"id":"6964c2d4-2994-487b-b68a-f1df5fa916f7","doc_no":"A.2.2.2.2","title":"Process Flow","type":"Core","depth":4,"parentId":"bdbb8ac9-d87e-4052-9e69-8267f38a54cf","order":1130,"content":"This field describes the step-by-step operational procedure that occurs once a Process is properly initiated. A step can reference specific Core Atlas or Artifact Documents and broadly describe how their state is manipulated and decisions are made. More granular specifications regarding Document state changes are defined in the `Required Primitive Inputs` schema component [A.2.2.2.3 - Required Primitive Inputs](1474b30b-7e2b-4c9a-8624-3c2c5f53abc8). Process flow steps can both consume and produce relevant Document data.","contentHash":"97bcf369b18df9c7d7b747b5fff9a79781ae2bc18ead58982160212b847e3a9f","addressRefs":[]},"1474b30b-7e2b-4c9a-8624-3c2c5f53abc8":{"id":"1474b30b-7e2b-4c9a-8624-3c2c5f53abc8","doc_no":"A.2.2.2.3","title":"Required Primitive Inputs","type":"Core","depth":4,"parentId":"bdbb8ac9-d87e-4052-9e69-8267f38a54cf","order":1131,"content":"This field specifies the Agent Artifact Documents and their associated fields that must be manipulated using the Powerhouse interface as part of a Process. If any of the required Inputs is missing or incorrect, the Process cannot be completed.","contentHash":"0469be997e7202e9c455f4c168e3d6c79be4dd55a67da6d69216c49195d9b1f9","addressRefs":[]},"e9422783-6196-4117-9099-b5ec0c338c05":{"id":"e9422783-6196-4117-9099-b5ec0c338c05","doc_no":"A.2.2.2.3.1","title":"Sequential Stages","type":"Core","depth":5,"parentId":"1474b30b-7e2b-4c9a-8624-3c2c5f53abc8","order":1132,"content":"Some Processes require Primitive Inputs that are organized into multiple sequential stages (also called \"Input stages\"). Each Input stage must be completed before progressing to the next, ensuring that all dependencies and validations are met in order. Once an Input stage is completed, the subsequent Input stage is initiated automatically, continuing in this manner until all stages have been finished.\n\nUpon completing the final Primitive Input stage, the Process Definition transitions to the `Required Outputs` schema component; this component defines the necessary updates to Sky Core Atlas or Agent Artifact Documents.","contentHash":"00c725d3bc502cb7bc3129238b2709c528459728f3ccc634a347f4f90829433e","addressRefs":[]},"9c4f4cad-5124-44d8-b19e-bd931fae7963":{"id":"9c4f4cad-5124-44d8-b19e-bd931fae7963","doc_no":"A.2.2.2.3.1.1","title":"Required Output Trigger","type":"Core","depth":6,"parentId":"e9422783-6196-4117-9099-b5ec0c338c05","order":1133,"content":"Where a Process Definition has more than one set of `Required Outputs`, with each set corresponding to (or \"triggered by\") a particular Input stage, the `Required Primitive Inputs` schema component must explicitly correlate each Input stage with the `Required Outputs` it triggers. See [A.2.2.2.4.1 - Multiple Required Outputs And Their Respective Input Stage or Mutually Exclusive Pathway](10c53693-4784-40ad-a8c6-fd2551f14280).","contentHash":"d782a2ad23f20c6bf3c92113e3c50c03e26da2c4f7b520f3a9399e60df073d31","addressRefs":[]},"926cd44b-e26c-4ae9-9091-d97c362d7e29":{"id":"926cd44b-e26c-4ae9-9091-d97c362d7e29","doc_no":"A.2.2.2.3.2","title":"Mutually Exclusive Pathways","type":"Core","depth":5,"parentId":"1474b30b-7e2b-4c9a-8624-3c2c5f53abc8","order":1134,"content":"Some Processes require Primitive Inputs that are organized into two or more mutually exclusive pathways (also \"mutually exclusive Input pathways\"). Once a pathway is chosen—either manually or automatically via the application of a defined decision or condition—the Process follows that pathway through to completion, rendering the other pathways inapplicable.","contentHash":"9fa56ed54c726fa6cf7733c62f61f56fd2e5d0cf7b842476609327806a909767","addressRefs":[]},"a61d4797-9a1f-455c-8fe1-b62164e702b3":{"id":"a61d4797-9a1f-455c-8fe1-b62164e702b3","doc_no":"A.2.2.2.3.2.1","title":"Required Output Trigger","type":"Core","depth":6,"parentId":"926cd44b-e26c-4ae9-9091-d97c362d7e29","order":1135,"content":"When multiple \"sets\" of `Required Outputs` exist, with each set corresponding to (or \"triggered by\") a particular Mutually Exclusive Input Pathway, the `Required Primitive Inputs` schema component must explicitly correlate each Mutually Exclusive Input Pathway with the `Required Outputs` it triggers. Because the pathways are mutually exclusive, only the Required Output set associated with the selected Pathway will be executed. The other Output sets remain inactive.","contentHash":"d92e78149bb8c5aab889356298947ba43a7ff319077283032cc0dd836729a262","addressRefs":[]},"dee40c3b-2f89-44c6-8813-c48888df08a7":{"id":"dee40c3b-2f89-44c6-8813-c48888df08a7","doc_no":"A.2.2.2.4","title":"Required Outputs","type":"Core","depth":4,"parentId":"bdbb8ac9-d87e-4052-9e69-8267f38a54cf","order":1136,"content":"This field specifies the particular Sky Core Atlas and/or Agent Artifact Documents that must be updated as an end result of a Process.\n\nWhere applicable, a Document Update can serve as a \"trigger\" that deterministically compels another Process Definition to be initiated by a system or actor. The `Trigger - Process` field links to the respective Process Definition that is triggered by the Required Output.\n\nSome processes do not need formal \"Required Outputs\" because the only process flow step is a simple update of an Artifact Document. In these edge cases, the change specified in `Required Primitive Inputs` (e.g., toggling a field to Globally Activate a Primitive) fully completes the process, effectively completing it in a single step. Once the designated Document and field are updated as prescribed, the Process is considered finalized.","contentHash":"51a4a63c57f834c06541cfe41dcf36b713403820f29f5b9c119764d58a659ab9","addressRefs":[]},"10c53693-4784-40ad-a8c6-fd2551f14280":{"id":"10c53693-4784-40ad-a8c6-fd2551f14280","doc_no":"A.2.2.2.4.1","title":"Multiple Required Outputs And Their Respective Input Stage or Mutually Exclusive Pathway","type":"Core","depth":5,"parentId":"dee40c3b-2f89-44c6-8813-c48888df08a7","order":1137,"content":"Where a Process Definition has more than one set of Required Outputs, and each set corresponds to (or is \"triggered by\") either a specific Input stage or a specific Mutually Exclusive Input Pathway, the Process Definition’s `Required Primitive Input` field must define which `Required Output` set is Invoked upon completion of that stage or pathway.\n\n1. **For Sequential Stages**: When multiple sequential stages exist, each stage’s successful completion triggers its corresponding Required Output set. As subsequent stages are completed in turn, each triggers its own distinct Required Outputs, ensuring that all designated outputs eventually execute in sequence.\n2. **For Mutually Exclusive Pathways**: If the Required Primitive Input process instead (or additionally) involves mutually exclusive paths, once a pathway is chosen—either manually or automatically by a specified condition—only the Required Output set tied to that pathway is applied. Outputs associated with the unselected/unexecuted pathways remain inactive.","contentHash":"324eadc9a8a768f6ae1dd8d0d3ff9c2e8fcc688ff5e8b52da86e81bb88e999cd","addressRefs":[]},"3b3e537c-4989-4674-94bc-05928146ab42":{"id":"3b3e537c-4989-4674-94bc-05928146ab42","doc_no":"A.2.2.2.4.2","title":"Agent Artifact Document Specification","type":"Core","depth":5,"parentId":"dee40c3b-2f89-44c6-8813-c48888df08a7","order":1138,"content":"In the Sky Primitives Data Schema, references to an Agent Artifact Document are made in terms of the generic Document type. See [A.1.2.2.2 - List Of Document Types And Their Specifications](428b7f2e-30b0-4119-a10a-9c3496f19bd2). In practice, each Agent has its own Instance of that Document type in its Artifact. Thus, when a Primitive’s process flow indicates that an Agent Artifact Document must be updated, it is to be interpreted as referring to the _specific Instance_ of that Document type in the Prime Agent’s Artifact.","contentHash":"f8c91169ea4b2f84ac898ee0de4201f78091bbe31154d42e900c1cdbbbb7e094","addressRefs":[]},"9204bcaf-cfec-4f49-a115-31fad73ebd62":{"id":"9204bcaf-cfec-4f49-a115-31fad73ebd62","doc_no":"A.2.2.3","title":"Prerequisites For Activating Agent Creation Primitive","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1139,"content":"The Agent Creation Primitive is the first Sky Primitive that must be activated by prospective Agent founders. Because an Agent Artifact does not yet exist at this stage, the prerequisite requirements set forth herein must be met, including off-chain obligations and governance outputs. Only after satisfying these prerequisites does the Agent Creation Primitive become accessible to the prospective founder.","contentHash":"2bcb73f2b67f00592e2154c3692bf0e45b6e2aa70e60a22c20fd1e789d2c1f2a","addressRefs":[]},"df925d98-2e73-4b26-859b-33caa8865f0f":{"id":"df925d98-2e73-4b26-859b-33caa8865f0f","doc_no":"A.2.2.3.1","title":"Agent Inputs","type":"Core","depth":4,"parentId":"9204bcaf-cfec-4f49-a115-31fad73ebd62","order":1140,"content":"The prospective Agent founder must deploy the required startup capital and pay the Agent creation fee.","contentHash":"94dded68434594db93471f89dae966ecf37006f07b9ac7abbe6cebacbc358ee1","addressRefs":[]},"bed7471a-54aa-4167-88dd-22ebd63f8827":{"id":"bed7471a-54aa-4167-88dd-22ebd63f8827","doc_no":"A.2.2.3.1.1","title":"Capital Injection","type":"Core","depth":5,"parentId":"df925d98-2e73-4b26-859b-33caa8865f0f","order":1141,"content":"The required capital and the process for deploying it will be specified in a future iteration of the Atlas.","contentHash":"ccf3386acdd6e7e32acf2efc9bee243a6665ea845ba0c4b85038aea328c6d47f","addressRefs":[]},"708ad6b6-8e4a-46b3-9848-523d00a57420":{"id":"708ad6b6-8e4a-46b3-9848-523d00a57420","doc_no":"A.2.2.3.1.2","title":"Creation Fee","type":"Core","depth":5,"parentId":"df925d98-2e73-4b26-859b-33caa8865f0f","order":1142,"content":"The prospective founder must pay the required creation fee. The required fee and the process for paying it will be specified in a future iteration of the Atlas.","contentHash":"c99810c2a072f87250b592ba2183b81f549dbb9817ca2fbed6a14b4db914e9e3","addressRefs":[]},"e1cef578-801c-4905-a88b-e9703b048d2a":{"id":"e1cef578-801c-4905-a88b-e9703b048d2a","doc_no":"A.2.2.3.2","title":"Core GovOps Outputs","type":"Core","depth":4,"parentId":"9204bcaf-cfec-4f49-a115-31fad73ebd62","order":1143,"content":"After the prospective Agent founder deploys the required startup capital and pays the Agent creation fee, Core GovOps creates a Proto-Agent and sets up a Scaffold Agent Artifact.","contentHash":"0111807803612b31614fce2fd49ffb630989bfbb3c78cf29a8d8e83d583c1546","addressRefs":[]},"1f577977-2f4c-41a0-a3ba-f09fc77b8d09":{"id":"1f577977-2f4c-41a0-a3ba-f09fc77b8d09","doc_no":"A.2.2.3.2.1","title":"Proto-Agent Creation","type":"Core","depth":5,"parentId":"e1cef578-801c-4905-a88b-e9703b048d2a","order":1144,"content":"Core GovOps creates a Proto-Agent with no specific functionality in the ecosystem.","contentHash":"d56245de8671ef7ee6470aa553edea45c148fe4e5516eb8718547c794a016905","addressRefs":[]},"f55fdc70-dfe4-4c52-9be4-10bf3a6dc990":{"id":"f55fdc70-dfe4-4c52-9be4-10bf3a6dc990","doc_no":"A.2.2.3.2.2","title":"Scaffold Artifact Setup","type":"Core","depth":5,"parentId":"e1cef578-801c-4905-a88b-e9703b048d2a","order":1145,"content":"Core GovOps prepares a Scaffold Agent Artifact (\"Scaffold Artifact\") containing all Sky Primitives. In the Scaffold Artifact, the Upkeep Rebate Primitive is globally activated by default. See [A.2.2.1.2.2 - Initial Primitive Global Activation Status](377150b3-d64b-4436-ab6d-758b05d82f26). All other Primitives are initially set to `Inactive`. The Scaffold Artifact also includes an initial set of Omni Documents that provide general information about the Agent and organize the various Sky Primitive Instance Configuration Documents. Core GovOps must add the Scaffold Artifact to the Atlas’ Agent Artifact Scope.","contentHash":"97c2241b96dc51cd7d7ff2555cf5228e9fd59f365633820cc426a86e1dc18205","addressRefs":[]},"39d1cae8-a070-47a2-b69b-96e0f4f6a080":{"id":"39d1cae8-a070-47a2-b69b-96e0f4f6a080","doc_no":"A.2.2.3.2.3","title":"Address Deploying Capital","type":"Core","depth":5,"parentId":"e1cef578-801c-4905-a88b-e9703b048d2a","order":1146,"content":"The address deploying the start-up capital is assigned `Founder Access` to the Scaffold Agent Artifact. See [A.2.2.1.1.3.2 - Founder Access](a4f65994-2526-4522-a986-cd444a5cb896).","contentHash":"3777f63ed45100f76c68d1f5b0eeb6d99a04dc4cf3529cefc6b9501307d90a36","addressRefs":[]},"3d5e3668-8333-4908-adcc-5784cfe7f6b5":{"id":"3d5e3668-8333-4908-adcc-5784cfe7f6b5","doc_no":"A.2.2.4","title":"Genesis Primitives","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1147,"content":"Genesis Primitives are a category of Primitives addressing different aspects of initial Agent setup—such as Agent creation, token launch and configuration, and transformation pathways.","contentHash":"f5e5a7a2025a9792a8ccb7459336d06442a643d96b3a689d2142f2f58af49067","addressRefs":[]},"82b95f6d-4883-4f08-ac3a-9d8189013fbe":{"id":"82b95f6d-4883-4f08-ac3a-9d8189013fbe","doc_no":"A.2.2.4.1","title":"Agent Creation Primitive","type":"Core","depth":4,"parentId":"3d5e3668-8333-4908-adcc-5784cfe7f6b5","order":1148,"content":"This Primitive may only be Invoked after the prospective Agent founder meets the prerequisites defined in [A.2.2.3 - Prerequisites For Activating Agent Creation Primitive](9204bcaf-cfec-4f49-a115-31fad73ebd62), resulting in the creation of a Proto-Agent. Invoking the Agent Creation Primitive allows the Proto-Agent to establish its identity by declaring its name, as well as articulate its intended vision, business model or ecosystem goals.","contentHash":"0dda5c01e95758eef14837a148097a2b881652d63af21401bb0c09854dde6826","addressRefs":[]},"46e64020-f283-48a6-b327-75ea15927ee4":{"id":"46e64020-f283-48a6-b327-75ea15927ee4","doc_no":"A.2.2.4.1.1","title":"Agent Creation Primitive Process Definition","type":"Core","depth":5,"parentId":"82b95f6d-4883-4f08-ac3a-9d8189013fbe","order":1149,"content":"The documents herein define the Process Definition for initial setup and ongoing management of an Instance of the Agent Creation Primitive.","contentHash":"d2f6c24c08dc242061f2e8c8faf6c54eb57f9b3b5b9a693454d744f6939b72e8","addressRefs":[]},"754e1599-28d7-499a-b68f-e2155e87105a":{"id":"754e1599-28d7-499a-b68f-e2155e87105a","doc_no":"A.2.2.4.1.1.1","title":"Agent Creation Instance Setup Process","type":"Core","depth":6,"parentId":"46e64020-f283-48a6-b327-75ea15927ee4","order":1150,"content":"The documents herein define the process for setting up an Instance of the Agent Creation Primitive.","contentHash":"08f0f224c613afce5b30696a5fb2c4ef4a2abb9c246b7e0ff7c68845c4e3def7","addressRefs":[]},"cfde405d-e7e1-48eb-b044-3e9514c0aa96":{"id":"cfde405d-e7e1-48eb-b044-3e9514c0aa96","doc_no":"A.2.2.4.1.1.1.1","title":"Founder Inputs","type":"Core","depth":6,"parentId":"46e64020-f283-48a6-b327-75ea15927ee4","order":1151,"content":"The Founder uses the Powerhouse interface to input the Agent's name and an introduction outlining the Agent's vision.","contentHash":"2390d38f9040ec55f7ded7e92c98d882ff475493476874840e45a8b1c55b5f3b","addressRefs":[]},"d2b0f57b-1596-4355-9c63-aec6466cf316":{"id":"d2b0f57b-1596-4355-9c63-aec6466cf316","doc_no":"A.2.2.4.1.1.1.2","title":"Validation","type":"Core","depth":6,"parentId":"46e64020-f283-48a6-b327-75ea15927ee4","order":1152,"content":"Core GovOps validates the Founder’s inputs. This includes verifying that all of the documents created by the Founder using Founder Access are well-specified, that the documents are Aligned, and that all necessary Primitives to complete setup have been Activated. The necessary Primitives are the Agent Creation, Prime/Executor Transformation, Agent Token, Executor Accord, Root Edit, and Ecosystem Upkeep Fee Primitives. (See [A.2.2.1.1.3.1 - Founder Required Primitive Activation](1a48e833-d960-4bdf-8f67-0f9d9307e00d).) After confirming these conditions, Core GovOps creates a Genesis Account and a SubProxy Account for the Agent.","contentHash":"620da700034d9bb7df61e53fac0e2fc0d645cf9bafc47ad7e69c38b85a162b0d","addressRefs":[]},"c73a1815-b2dc-4cec-9ef4-ae6e6aabf633":{"id":"c73a1815-b2dc-4cec-9ef4-ae6e6aabf633","doc_no":"A.2.2.4.1.1.1.3","title":"Official Update Of Artifact","type":"Core","depth":6,"parentId":"46e64020-f283-48a6-b327-75ea15927ee4","order":1153,"content":"After successful validation, the Agent Creation Primitive is considered successfully Invoked, and the Agent Artifact is officially upgraded to reflect an Agent Creation Primitive Instance, with a Status of `Completed`.","contentHash":"5f502923236214841569c9f43f1ea7b7facfcb847c016562df2c613d870b00cd","addressRefs":[]},"b7238f7c-253d-4881-bbb8-10e3ca2d62ba":{"id":"b7238f7c-253d-4881-bbb8-10e3ca2d62ba","doc_no":"A.2.2.4.1.1.2","title":"Agent Creation Instance Ongoing Management","type":"Core","depth":6,"parentId":"46e64020-f283-48a6-b327-75ea15927ee4","order":1154,"content":"The documents herein define the process for the ongoing management of an Instance of the Agent Creation Primitive.","contentHash":"d3f14f116177fb1f581bdc934f2dffb2c925ff6ca9193581aaf5a52fa60e3b95","addressRefs":[]},"1ca2f5f3-1be7-4855-bbb7-49630e7e2ae6":{"id":"1ca2f5f3-1be7-4855-bbb7-49630e7e2ae6","doc_no":"A.2.2.4.1.1.2.1","title":"Agent Creation Primitive Results In One-Time Creation","type":"Core","depth":6,"parentId":"46e64020-f283-48a6-b327-75ea15927ee4","order":1155,"content":"Because the Agent Creation Primitive is deployed solely to effect the one-time creation of the Agent, no further management process is needed post-deployment.","contentHash":"e162578d64466083b35910b8b1554031efca7a417776c2044d757cab6ee88e3b","addressRefs":[]},"7a7a2631-e5e2-4b63-8f2b-45ecaec7af2e":{"id":"7a7a2631-e5e2-4b63-8f2b-45ecaec7af2e","doc_no":"A.2.2.4.1.2","title":"Agent Creation Primitive Input Requirements","type":"Core","depth":5,"parentId":"82b95f6d-4883-4f08-ac3a-9d8189013fbe","order":1156,"content":"The documents herein define the required inputs for a valid Invocation of the Agent Creation Primitive. If any input is noncompliant or omitted, the Primitive will be invalidated.","contentHash":"0dee20d1e784f93c6eac7f485a03a11742ef6f7274e39a290d5278d333f1ec40","addressRefs":[]},"f9de4749-2bf4-4871-a5a8-6fb6849af7ad":{"id":"f9de4749-2bf4-4871-a5a8-6fb6849af7ad","doc_no":"A.2.2.4.1.2.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"7a7a2631-e5e2-4b63-8f2b-45ecaec7af2e","order":1157,"content":"The Agent Creation Primitive must be Globally Activated.","contentHash":"90c5467e6262914096fa94558dcb03bcd47dc4ad891e4db2f12be979a3f309c7","addressRefs":[]},"c7e7507e-4d57-4842-932c-88cf232a53a8":{"id":"c7e7507e-4d57-4842-932c-88cf232a53a8","doc_no":"A.2.2.4.1.2.2","title":"Agent Name And Introduction","type":"Core","depth":6,"parentId":"7a7a2631-e5e2-4b63-8f2b-45ecaec7af2e","order":1158,"content":"The Agent Creation Primitive must specify the Agent’s Name and provide a brief overview of its vision or business model.","contentHash":"bf046e5fc5cd28f42065d7e18931acbb933014a617e4f3bc85a8353a788bfc5c","addressRefs":[]},"585dc747-65f1-4443-b61b-9779031f9258":{"id":"585dc747-65f1-4443-b61b-9779031f9258","doc_no":"A.2.2.4.1.2.3","title":"Agent SubProxy Account","type":"Core","depth":6,"parentId":"7a7a2631-e5e2-4b63-8f2b-45ecaec7af2e","order":1159,"content":"The Agent Creation Primitive must specify the SubProxy address of the Agent. This field is populated by Core GovOps. The SubProxy is an account that serves as the Agent’s treasury. The SubProxy Account is controlled by Sky Governance.","contentHash":"439136c23a5376a5a4c1ff0f035bf7b3f2d6e625519e37eb91f1e40cc7907ee5","addressRefs":[]},"761966db-e9db-41f8-a9fe-cf8b0c1a7d26":{"id":"761966db-e9db-41f8-a9fe-cf8b0c1a7d26","doc_no":"A.2.2.4.1.2.4","title":"Agent Genesis Account","type":"Core","depth":6,"parentId":"7a7a2631-e5e2-4b63-8f2b-45ecaec7af2e","order":1160,"content":"The Agent Creation Primitive must designate the Genesis Account. This field is populated by Core GovOps. The Genesis account initially controls 100% of the tokens of the Agent. The Genesis Account is initially controlled by the Agent Founder.","contentHash":"3607fd2a48c8e24e33564de24de24cc4805fc7405162cc7c3e9c75a8ba1a51ce","addressRefs":[]},"81411106-fd6d-4f9c-b3ae-7af7b5e62482":{"id":"81411106-fd6d-4f9c-b3ae-7af7b5e62482","doc_no":"A.2.2.4.2","title":"Prime Transformation Primitive","type":"Core","depth":4,"parentId":"3d5e3668-8333-4908-adcc-5784cfe7f6b5","order":1161,"content":"Prior to Activating this Primitive, a Proto-Agent has been created, meaning it has not yet adopted any specialized role. Since a Proto-Agent cannot perform actions in the Sky Ecosystem, it must first transform into either a Prime Agent or Executor Agent to gain functionality. The Prime Transformation Primitive defined herein allows an Agent to transform into a Prime Agent, subject to certain conditions.","contentHash":"0b03360c1404e6c2076e0c7671f5b02406f694e75b7696545d490fbdb5367602","addressRefs":[]},"ddfbb811-94f5-43bb-bf5e-a9bab2be046d":{"id":"ddfbb811-94f5-43bb-bf5e-a9bab2be046d","doc_no":"A.2.2.4.2.1","title":"Prime Transformation Primitive Process Definition","type":"Core","depth":5,"parentId":"81411106-fd6d-4f9c-b3ae-7af7b5e62482","order":1162,"content":"The documents herein define the Process Definition for initial setup and ongoing management of an Instance of the Prime Transformation Primitive.","contentHash":"0e61f302cddabfc930559ba997a219b52102b8cbda32befeeb5880dc6deb2c8c","addressRefs":[]},"3f1824b6-5325-43ac-b3d5-151fb0f55dec":{"id":"3f1824b6-5325-43ac-b3d5-151fb0f55dec","doc_no":"A.2.2.4.2.1.1","title":"Prime Transformation Primitive Setup Process","type":"Core","depth":6,"parentId":"ddfbb811-94f5-43bb-bf5e-a9bab2be046d","order":1163,"content":"The documents herein define the process for setting up the Prime Transformation Primitive.","contentHash":"34b19803e678e0e5b5218f826cb94023b3c532f403fcbda621c011daf2fada08","addressRefs":[]},"aef13d1b-08d6-4c89-8858-65f8acbe4adc":{"id":"aef13d1b-08d6-4c89-8858-65f8acbe4adc","doc_no":"A.2.2.4.2.1.1.1","title":"Agent Inputs","type":"Core","depth":6,"parentId":"ddfbb811-94f5-43bb-bf5e-a9bab2be046d","order":1164,"content":"The Proto-Agent must use the Powerhouse interface to input their desired Agent Type into the Primitive. For the Prime Transformation Primitive process, the Proto-Agent must specify ‘Prime Agent’ as their desired Agent Type.","contentHash":"72d8720118e1740dfdf3b85f65843c500dcf05cdd55cc45fd661851e308592c0","addressRefs":[]},"43598845-989e-44fc-8cb4-c60b67fd1f28":{"id":"43598845-989e-44fc-8cb4-c60b67fd1f28","doc_no":"A.2.2.4.2.1.1.2","title":"Validation","type":"Core","depth":6,"parentId":"ddfbb811-94f5-43bb-bf5e-a9bab2be046d","order":1165,"content":"Core GovOps validates the Proto-Agent’s inputs, namely, the Agent Type. Additionally, Core GovOps performs a further review to confirm that all the documents created by the Founder using Founder Access are well-specified, that the documents are Aligned, and that all necessary Primitives have been Activated. The necessary Primitives are the Agent Creation, Prime/Executor Transformation, Agent Token, Executor Accord, Root Edit, and Ecosystem Upkeep Fee Primitives. (See [A.2.2.1.1.3.1 - Founder Required Primitive Activation](1a48e833-d960-4bdf-8f67-0f9d9307e00d).)","contentHash":"84ddcbff7dabe00b78163dee23909653230a426895c1070afea711f68b9bca4d","addressRefs":[]},"2182141b-a2bc-46bc-b9a6-2cb62e55b302":{"id":"2182141b-a2bc-46bc-b9a6-2cb62e55b302","doc_no":"A.2.2.4.2.1.1.3","title":"Official Update Of Artifact","type":"Core","depth":6,"parentId":"ddfbb811-94f5-43bb-bf5e-a9bab2be046d","order":1166,"content":"After successful validation, the Prime Transformation Primitive is considered successfully Invoked, and the Agent Artifact is officially upgraded to reflect a Prime Transformation Primitive Instance, with a Status of `Completed`.","contentHash":"c79459d7f00e65fb36a778687821830e654646503cd9fc29027e8932749458a3","addressRefs":[]},"c1cae3bb-283e-44bf-9860-b721a1625bae":{"id":"c1cae3bb-283e-44bf-9860-b721a1625bae","doc_no":"A.2.2.4.2.1.2","title":"Prime Transformation Primitive Ongoing Management","type":"Core","depth":6,"parentId":"ddfbb811-94f5-43bb-bf5e-a9bab2be046d","order":1167,"content":"The documents herein define the process for the ongoing management of an Instance of the Prime Transformation Primitive.","contentHash":"97787c4e4eb589e26b5688e8d6a7c2aab960307c4a9830f81ae85c917a24df9f","addressRefs":[]},"248bfb90-8bd8-410a-86d3-527e355eca43":{"id":"248bfb90-8bd8-410a-86d3-527e355eca43","doc_no":"A.2.2.4.2.1.2.1","title":"Prime Transformation Primitive Results In One-Time Creation","type":"Core","depth":6,"parentId":"ddfbb811-94f5-43bb-bf5e-a9bab2be046d","order":1168,"content":"Because the Prime Transformation Primitive is deployed solely to effect the one-time transformation of the Proto-Agent, no further management process is needed post-deployment.","contentHash":"979a81e6fa1ced491bb876d8ff5303cebafe5de34e0c76e5b500413c05850043","addressRefs":[]},"062b9275-9778-4f24-b0e5-bccf9129c179":{"id":"062b9275-9778-4f24-b0e5-bccf9129c179","doc_no":"A.2.2.4.2.2","title":"Prime Transformation Primitive Input Requirements","type":"Core","depth":5,"parentId":"81411106-fd6d-4f9c-b3ae-7af7b5e62482","order":1169,"content":"The documents herein define the required inputs for a valid Invocation of the Prime Transformation Primitive. If any input is noncompliant or omitted, the Primitive will be invalidated.","contentHash":"e57992fd1f74223676a13dd9f93b1ca78ef460d3e4d7544032d8b5df3e25e667","addressRefs":[]},"cd67fe26-d82d-4859-be8d-36f1a9c42a65":{"id":"cd67fe26-d82d-4859-be8d-36f1a9c42a65","doc_no":"A.2.2.4.2.2.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"062b9275-9778-4f24-b0e5-bccf9129c179","order":1170,"content":"The Prime Transformation Primitive must be Globally Activated.","contentHash":"d31c7b76007b430b03dd545eded08d4ac343699116b3309dcdcc812e10de09d7","addressRefs":[]},"857468db-7ff3-4986-b808-a7cd9854000a":{"id":"857468db-7ff3-4986-b808-a7cd9854000a","doc_no":"A.2.2.4.2.2.2","title":"Prime Agent Type","type":"Core","depth":6,"parentId":"062b9275-9778-4f24-b0e5-bccf9129c179","order":1171,"content":"The Prime Transformation Primitive must specify the Prime Agent’s Type, e.g., that it is a Prime Agent.","contentHash":"30c43532eda76a41fdeed737d262262b074b2036f750ecee317ca05a2729b904","addressRefs":[]},"2f249be5-8edb-41e4-b429-734e1ba2cbc7":{"id":"2f249be5-8edb-41e4-b429-734e1ba2cbc7","doc_no":"A.2.2.4.3","title":"Executor Transformation Primitive","type":"Core","depth":4,"parentId":"3d5e3668-8333-4908-adcc-5784cfe7f6b5","order":1172,"content":"The Executor Transformation Primitive allows an Agent to transform into an Executor Agent, subject to certain conditions.","contentHash":"32509a4e06b59ac8272291b91068ef036617814563ce10c99a048bf6c7f0f888","addressRefs":[]},"2047c361-db28-4952-a70c-83d07b562064":{"id":"2047c361-db28-4952-a70c-83d07b562064","doc_no":"A.2.2.4.4","title":"Agent Token Primitive","type":"Core","depth":4,"parentId":"3d5e3668-8333-4908-adcc-5784cfe7f6b5","order":1173,"content":"The Agent Token Primitive enables Agents to define, mint, and distribute their governance tokens including foundation allocations, token rewards, and airdrops.","contentHash":"7cc2e716a1042ee648d4f07ea125dfe53f1e8c66c81636b74cef70cd78b1650c","addressRefs":[]},"f7a81be7-057c-4a05-97ab-78a37c674010":{"id":"f7a81be7-057c-4a05-97ab-78a37c674010","doc_no":"A.2.2.4.4.1","title":"Agent Token Primitive Process Definition","type":"Core","depth":5,"parentId":"2047c361-db28-4952-a70c-83d07b562064","order":1174,"content":"The documents herein define the Process Definition for initial setup and ongoing management of an Instance of the Agent Token Primitive.","contentHash":"6cb73fa1e81c8aed432b9ff02412eee28f27b734f652eff1e4effaff058c4dd5","addressRefs":[]},"3e49628d-1f82-4980-9855-75ad5e86aa54":{"id":"3e49628d-1f82-4980-9855-75ad5e86aa54","doc_no":"A.2.2.4.4.1.1","title":"Agent Token Primitive Setup Process","type":"Core","depth":6,"parentId":"f7a81be7-057c-4a05-97ab-78a37c674010","order":1175,"content":"The documents herein define the process for setting up the Agent Token Primitive.","contentHash":"1b1117c5966e9a6d6f420cb7b725e8a9826629ef09b7059a4724ab971f8772ab","addressRefs":[]},"f74588a5-cbde-4635-9e18-bca3d9c80612":{"id":"f74588a5-cbde-4635-9e18-bca3d9c80612","doc_no":"A.2.2.4.4.1.1.1","title":"Agent Inputs","type":"Core","depth":6,"parentId":"f7a81be7-057c-4a05-97ab-78a37c674010","order":1176,"content":"The Agent must use the Powerhouse interface to input key data into the Agent Token Primitive, including token name, ticker, symbol, genesis supply, total supply, distribution rules, emissions schedule, pending token address and token admin address. The token admin address should be the Agent SubProxy Account. The Agent must also specify whether token emissions beyond the current supply have been irreversibly disabled.","contentHash":"6433d1fd9c29f420dc9786bd81b4554fe738aabede5325a948e4a5e0bfba9865","addressRefs":[]},"6f63137d-5385-46e9-96ac-fc16a568f54a":{"id":"6f63137d-5385-46e9-96ac-fc16a568f54a","doc_no":"A.2.2.4.4.1.1.2","title":"Validation","type":"Core","depth":6,"parentId":"f7a81be7-057c-4a05-97ab-78a37c674010","order":1177,"content":"Core GovOps validates the Agent’s inputs.","contentHash":"590369ada6dd03d0c679c0d8effe8988680c0f6c6c19c493a9d52451d9b43bdf","addressRefs":[]},"309e17ed-c75a-48f5-859f-70a5cb29a1f8":{"id":"309e17ed-c75a-48f5-859f-70a5cb29a1f8","doc_no":"A.2.2.4.4.1.1.3","title":"Official Update Of Artifact","type":"Core","depth":6,"parentId":"f7a81be7-057c-4a05-97ab-78a37c674010","order":1178,"content":"After successful validation, the Agent Token Primitive is considered successfully Invoked. The Agent Artifact is officially upgraded to reflect an Agent Token Primitive Instance, with a Status of `Active`.","contentHash":"dad70bd2f6659ed8612ef939c6a9d39bdc3b3e380996a482be9e7a58c7dd76a8","addressRefs":[]},"d26166c3-b07f-4583-8303-051a90468ed3":{"id":"d26166c3-b07f-4583-8303-051a90468ed3","doc_no":"A.2.2.4.4.1.1.4","title":"Core GovOps Output","type":"Core","depth":6,"parentId":"f7a81be7-057c-4a05-97ab-78a37c674010","order":1179,"content":"Upon successful validation, the token contract can now be deployed on-chain by Core GovOps. The minted supply must be allocated as specified in the Agent Token Primitive Instance. The Primitive is automatically updated to replace the pending token address with the actual token address.","contentHash":"63718768b2d28d059d2174fcc960ef231784e8811a55195d36601ec86ee16d10","addressRefs":[]},"d8f6b024-f4f8-4897-99f2-d433137c8850":{"id":"d8f6b024-f4f8-4897-99f2-d433137c8850","doc_no":"A.2.2.4.4.1.2","title":"Agent Token Primitive Ongoing Management","type":"Core","depth":6,"parentId":"f7a81be7-057c-4a05-97ab-78a37c674010","order":1180,"content":"The documents herein define the process for the ongoing management of an Instance of the Agent Token Primitive.","contentHash":"5126c2413976c11bd5484ec2a664b9ebe58e3e3e18c95b6488dd5cc564f5c080","addressRefs":[]},"0489781a-243c-4704-86e5-efe422cdd41c":{"id":"0489781a-243c-4704-86e5-efe422cdd41c","doc_no":"A.2.2.4.4.1.2.1","title":"Agent Token Primitive Results In One-Time Creation","type":"Core","depth":6,"parentId":"f7a81be7-057c-4a05-97ab-78a37c674010","order":1181,"content":"Because the Agent Token Primitive is deployed solely to create a one-off Token for an Agent, no further management process is needed post-deployment.","contentHash":"281f698485ee9572524829c07f2e5c74de71a4407a7cdde825f89e6b6afc69a2","addressRefs":[]},"9d88d70e-7dfc-42f3-9d58-0d2a905861fd":{"id":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","doc_no":"A.2.2.4.4.2","title":"Agent Token Primitive Input Requirements","type":"Core","depth":5,"parentId":"2047c361-db28-4952-a70c-83d07b562064","order":1182,"content":"The documents herein define the required inputs for a valid Invocation of the Agent Token Primitive. If any input is noncompliant or omitted, the Primitive will be invalidated.","contentHash":"bb3a84d2662ae6e2a1c290e974606e72dfc2422f9e6dd924e64ff166b2d02e39","addressRefs":[]},"fb858d4e-5d42-4496-807b-979e1946f8f0":{"id":"fb858d4e-5d42-4496-807b-979e1946f8f0","doc_no":"A.2.2.4.4.2.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1183,"content":"The Agent Token Primitive must be Globally Activated.","contentHash":"93ab9dd2a13906a4a699a52a185a0a57abf170ead41da46352e36bdb59e87e53","addressRefs":[]},"98fa133d-878a-4337-9d47-ad01ef19b9bb":{"id":"98fa133d-878a-4337-9d47-ad01ef19b9bb","doc_no":"A.2.2.4.4.2.2","title":"Agent Token Name","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1184,"content":"The Agent Token Primitive must specify the name of the token.","contentHash":"5b6c0e293ba5e5d2af7e77b7f027ca0bb385f1ee9406028ece47dedf556cabcb","addressRefs":[]},"46bbc08e-dcfc-4ed5-9e2f-3e78fd8735f9":{"id":"46bbc08e-dcfc-4ed5-9e2f-3e78fd8735f9","doc_no":"A.2.2.4.4.2.3","title":"Agent Token Symbol","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1185,"content":"The Agent Token Primitive must specify the symbol of the token.","contentHash":"1d21f1204efb5c2eab9de3895e519521ec9a19f07f58ef57b627cd436715ecab","addressRefs":[]},"ed342c6e-15ae-4c95-ad4e-4702c27eba62":{"id":"ed342c6e-15ae-4c95-ad4e-4702c27eba62","doc_no":"A.2.2.4.4.2.4","title":"Agent Token Genesis Supply","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1186,"content":"The Agent Token Primitive must specify the genesis supply of the token.","contentHash":"26b7e18f7bfeedb55942dac1a237999dbec4706f6cfcef50940bcad43c9fb19d","addressRefs":[]},"745126ca-1d64-461e-b8b9-603216d7e74b":{"id":"745126ca-1d64-461e-b8b9-603216d7e74b","doc_no":"A.2.2.4.4.2.5","title":"Agent Token Address","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1187,"content":"The Agent Token Primitive must specify either the pending or permanent address of the token (depending on whether the Primitive has been successfully Invoked).","contentHash":"4248d67da8c0308b1a4627be8b09477df6adcae510f2f906bbb151c650120f87","addressRefs":[]},"70e08dd1-8a2d-441b-95c4-92bce3bd37e8":{"id":"70e08dd1-8a2d-441b-95c4-92bce3bd37e8","doc_no":"A.2.2.4.4.2.6","title":"Agent Token Admin","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1188,"content":"The Agent Token Primitive must specify the Admin of the token.","contentHash":"31d04c9d73d9132784b1561ff4acd773de8783abc65e2b2f503a936d98cd7049","addressRefs":[]},"0f71bdc3-f18d-4e6f-8041-d73026a91d27":{"id":"0f71bdc3-f18d-4e6f-8041-d73026a91d27","doc_no":"A.2.2.4.4.2.7","title":"Agent Token Emissions","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1189,"content":"The Agent Token Primitive must specify whether token emissions beyond the current supply have been irreversibly disabled. Once Disabled is set to `True`, the action cannot be undone by the Agent. Sky Governance retains the ability to revert the Disabled setting where the Agent is in violation of Risk Capital requirements and emissions are required by the Risk Framework.","contentHash":"8f3e5f4d9814c1dd8f47ac6e465bbdc6958a41722b7f164969f765e9db2ae74f","addressRefs":[]},"3d43ba11-ac87-41a5-a98d-c80071aaf1eb":{"id":"3d43ba11-ac87-41a5-a98d-c80071aaf1eb","doc_no":"A.2.2.4.4.2.8","title":"Agent Token Distribution Rules","type":"Core","depth":6,"parentId":"9d88d70e-7dfc-42f3-9d58-0d2a905861fd","order":1190,"content":"The Agent Token Primitive must specify the process for distributing the initial token supply.","contentHash":"ee379412bde46140fdcf8c758a9e7196ac663148576343091e5a899bf6de3db5","addressRefs":[]},"0192ec95-9207-480e-8c51-88d2a1da95ad":{"id":"0192ec95-9207-480e-8c51-88d2a1da95ad","doc_no":"A.2.2.5","title":"Operational Primitives","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1191,"content":"Operational Primitives are a category of Primitives enabling the Agents’ own operation and governance and AI features, as well as the ability to create derivative Light Agents.","contentHash":"5962cc41514d95b78d9e434e79d47db4efe0415e6e890620215955fcdaa1d7d5","addressRefs":[]},"88017877-3ec1-4c43-a035-6bebdf11d9bb":{"id":"88017877-3ec1-4c43-a035-6bebdf11d9bb","doc_no":"A.2.2.5.1","title":"Executor Accord Primitive","type":"Core","depth":4,"parentId":"0192ec95-9207-480e-8c51-88d2a1da95ad","order":1192,"content":"The Executor Accord Primitive is the foundational mechanism that allows Prime Agents to operate autonomously according to the strategy specified in their Agent Artifacts with automated operational insurance provided by separate Operational Executor Agents that delegate the work to GovOps actors.","contentHash":"15666ed022ad136f8426cfdeb6f809fc1b4c489d5b142c3d76a6768658da8589","addressRefs":[]},"b2b42304-f715-4cc2-8fbf-68c794876386":{"id":"b2b42304-f715-4cc2-8fbf-68c794876386","doc_no":"A.2.2.5.1.1","title":"Executor Accord Primitive Process Definition","type":"Core","depth":5,"parentId":"88017877-3ec1-4c43-a035-6bebdf11d9bb","order":1193,"content":"The documents herein define the Process Definition for initial setup and ongoing management of an Instance of the Executor Accord Primitive.","contentHash":"e410d4de350180875358e8d9b34fbbb3163ee5b8d39faae54eb3861fef8545e5","addressRefs":[]},"af7c2593-b397-4fff-9b81-3d640508a163":{"id":"af7c2593-b397-4fff-9b81-3d640508a163","doc_no":"A.2.2.5.1.1.1","title":"Executor Accord Primitive Setup Process","type":"Core","depth":6,"parentId":"b2b42304-f715-4cc2-8fbf-68c794876386","order":1194,"content":"The documents herein define the process for setting up an Instance of the Executor Accord Primitive.","contentHash":"c6481f3c08b1a44b30d3a76806acb7112e8646450f3ecc95e958165e0d5fc58d","addressRefs":[]},"d082d5de-a0b2-4441-8ba8-06d1e5fe2aed":{"id":"d082d5de-a0b2-4441-8ba8-06d1e5fe2aed","doc_no":"A.2.2.5.1.1.1.1","title":"Agent Inputs","type":"Core","depth":6,"parentId":"b2b42304-f715-4cc2-8fbf-68c794876386","order":1195,"content":"The Prime Agent and Operational Executor Agent must come to a consensus about the details of the Executor Accord. These details must be entered into the Powerhouse interface along with independent confirmation from each Agent that they agree to those terms.","contentHash":"5c44884a95c66081ffa9b1e5fac9cd2fa98a00335c6447dbfdb0f4802f63378c","addressRefs":[]},"dad19a7b-769c-43e3-a7b9-ce91d267c3b1":{"id":"dad19a7b-769c-43e3-a7b9-ce91d267c3b1","doc_no":"A.2.2.5.1.1.1.2","title":"Validation","type":"Core","depth":6,"parentId":"b2b42304-f715-4cc2-8fbf-68c794876386","order":1196,"content":"Core GovOps validates the Agent’s inputs, ensuring that the terms of the Executor Accord are reasonably specific.","contentHash":"8b706e89eeb35dfacac0ad753ac65a63fd9c43f6fb2f721873353b5cca2dc68a","addressRefs":[]},"458ec13a-5352-4720-a6eb-70f1bec6cb20":{"id":"458ec13a-5352-4720-a6eb-70f1bec6cb20","doc_no":"A.2.2.5.1.1.1.3","title":"Official Update Of Artifact","type":"Core","depth":6,"parentId":"b2b42304-f715-4cc2-8fbf-68c794876386","order":1197,"content":"After successful validation, the Executor Accord Primitive is considered successfully Invoked. The Agent Artifact is officially upgraded to reflect an Executor Accord Primitive Instance, with a Status of `Active`.","contentHash":"d6c9db46140478229b60046cbdbbb57050396ea73b8f72fe2b461a42a4c9b452","addressRefs":[]},"8179ca9b-2875-4f7c-9573-9ed6fc5f91cf":{"id":"8179ca9b-2875-4f7c-9573-9ed6fc5f91cf","doc_no":"A.2.2.5.1.1.1.4","title":"Operational GovOps Takes Over Operational Duties","type":"Core","depth":6,"parentId":"b2b42304-f715-4cc2-8fbf-68c794876386","order":1198,"content":"Upon successful validation, the Prime Agent has a documented relationship with an Executor Agent and so Core GovOps will no longer perform validation of the Agent’s Primitive inputs. Instead, the Operational GovOps associated with the Executor Agent specified in the Executor Accord will carry out operational tasks on behalf of the Prime Agent.","contentHash":"ae446239e60cd678a4a7c91eeab3a10dd0a701dbdbd5a4bcc5e829b2fc57c91b","addressRefs":[]},"8fe7d3f4-51bc-41bb-95b0-6dfe26fab562":{"id":"8fe7d3f4-51bc-41bb-95b0-6dfe26fab562","doc_no":"A.2.2.5.1.1.2","title":"Executor Accord Primitive Ongoing Management","type":"Core","depth":6,"parentId":"b2b42304-f715-4cc2-8fbf-68c794876386","order":1199,"content":"The documents herein define the process for the ongoing management of an Instance of the Executor Accord Primitive.","contentHash":"ed272924ae02b088a9016eab5465e859e36696054e3aa389e7363ad8fd5ff3ce","addressRefs":[]},"5785964a-75ca-4109-af39-5ae1e872b89d":{"id":"5785964a-75ca-4109-af39-5ae1e872b89d","doc_no":"A.2.2.5.1.2","title":"Executor Accord Primitive Required Inputs","type":"Core","depth":5,"parentId":"88017877-3ec1-4c43-a035-6bebdf11d9bb","order":1200,"content":"The documents herein define the required inputs for a valid Invocation of the Executor Accord Primitive. If any input is noncompliant or omitted, the Primitive will be invalidated and the Executor Accord will not be set up.","contentHash":"6c06717a96134fdd1f6f065d69d05f3807b18e1dc305a27f1de9b2200913e789","addressRefs":[]},"7dcc0b40-f577-4590-92d2-62697bfff33a":{"id":"7dcc0b40-f577-4590-92d2-62697bfff33a","doc_no":"A.2.2.5.1.2.1","title":"Executor Accord Primitive Activation Status","type":"Core","depth":6,"parentId":"5785964a-75ca-4109-af39-5ae1e872b89d","order":1201,"content":"The Executor Accord Primitive must be Globally Activated.","contentHash":"79054a6b7a3cc75ed64846e77ec034d66dededab4074fede8b733a9d4571067c","addressRefs":[]},"2ac80f9d-744d-4dde-9ecd-9497642716dc":{"id":"2ac80f9d-744d-4dde-9ecd-9497642716dc","doc_no":"A.2.2.5.1.2.2","title":"Executor Accord Terms","type":"Core","depth":6,"parentId":"5785964a-75ca-4109-af39-5ae1e872b89d","order":1202,"content":"The Executor Accord Primitive must include the terms of the Executor Accord between the Prime Agent and Operational Executor Agent.","contentHash":"419da6874baac5d416c1c664162a8aa83da1942494ee105d2d94921bc7305460","addressRefs":[]},"bf03d18d-e5f9-434c-9aff-f6f0679f5746":{"id":"bf03d18d-e5f9-434c-9aff-f6f0679f5746","doc_no":"A.2.2.5.1.2.3","title":"Agent Agreement","type":"Core","depth":6,"parentId":"5785964a-75ca-4109-af39-5ae1e872b89d","order":1203,"content":"The Executor Accord Primitive must include independent confirmation from each Agent that they agree to the terms of the Executor Accord.","contentHash":"44e198f99beec508a27abbb83f63b2a12b5083810e207383a4c68f8235b02e5a","addressRefs":[]},"78488c6b-d77f-4344-b954-476e415a2c7d":{"id":"78488c6b-d77f-4344-b954-476e415a2c7d","doc_no":"A.2.2.5.2","title":"Root Edit Primitive","type":"Core","depth":4,"parentId":"0192ec95-9207-480e-8c51-88d2a1da95ad","order":1204,"content":"The Root Edit Primitive allows Prime Agents, through a token holder vote, to direct the Operational Executor Agent specified in the Executor Accord Primitive to directly modify the Prime Agent Artifact.","contentHash":"eb2ae9a65bbf5af3708858c24e55de33381f2ac62d62200bcd53f15a8a215165","addressRefs":[]},"f543db65-dac7-494d-bd0d-a24bf600157d":{"id":"f543db65-dac7-494d-bd0d-a24bf600157d","doc_no":"A.2.2.5.2.1","title":"Root Edit Primitive Process Definition","type":"Core","depth":5,"parentId":"78488c6b-d77f-4344-b954-476e415a2c7d","order":1205,"content":"The documents herein define the Process Definition for initial setup and ongoing management of an Instance of the Root Edit Primitive.","contentHash":"26dcfa5ee1fd89c4ddb5eadfc063051c45edaff452948f1900eabca46a9f4fee","addressRefs":[]},"1fbca4e2-e89f-4819-afba-e58702ca2ed9":{"id":"1fbca4e2-e89f-4819-afba-e58702ca2ed9","doc_no":"A.2.2.5.2.1.1","title":"Root Edit Primitive Setup Process","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1206,"content":"The documents herein define the process for setting up an Instance of the Root Edit Primitive.","contentHash":"16fd11ee2b318dce8061e4ff50bf47fd1cccebbffa942dc060c00580e81089f0","addressRefs":[]},"131380cc-df22-4862-a275-49e6a7302cf8":{"id":"131380cc-df22-4862-a275-49e6a7302cf8","doc_no":"A.2.2.5.2.1.1.1","title":"Agent Inputs","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1207,"content":"The Agent must use the Powerhouse interface to specify the process by which Root Edits occur. See [A.1.14.2.7 - Artifact Edit Processes](2be8d2f0-bf02-4aa1-ad37-afb7a811a3b8).","contentHash":"d940dee8e677cddcfc1f3f467d9864effb7c74a843eebc1098024af66cc6e690","addressRefs":[]},"2a466974-af55-4d3f-84a5-7ac840ffb620":{"id":"2a466974-af55-4d3f-84a5-7ac840ffb620","doc_no":"A.2.2.5.2.1.1.2","title":"Validation","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1208,"content":"Core GovOps validates the Agent’s inputs.","contentHash":"590369ada6dd03d0c679c0d8effe8988680c0f6c6c19c493a9d52451d9b43bdf","addressRefs":[]},"3a95c852-efc0-43aa-b4fe-358332aaaf74":{"id":"3a95c852-efc0-43aa-b4fe-358332aaaf74","doc_no":"A.2.2.5.2.1.1.3","title":"Official Update Of Artifact","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1209,"content":"After successful validation, the Root Edit Primitive is considered successfully Invoked. The Agent Artifact is officially upgraded to reflect a Root Edit Primitive Instance, with a Status of `Active`.","contentHash":"cb0246fc41c6056b74385bad174e1540ee64e8a20daee34da39140344421ac61","addressRefs":[]},"023847b4-9987-449f-9f2c-6c719856295f":{"id":"023847b4-9987-449f-9f2c-6c719856295f","doc_no":"A.2.2.5.2.1.2","title":"Root Edit Primitive Ongoing Management","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1210,"content":"The documents herein define the process for the ongoing management of an Instance of the Root Edit Primitive.","contentHash":"0344065f2ac0c9cbca326d6883b1af721db048187eb4524e916657eb29c8e8d7","addressRefs":[]},"71ae684b-da79-4ece-ab38-91a498b3bdb1":{"id":"71ae684b-da79-4ece-ab38-91a498b3bdb1","doc_no":"A.2.2.5.2.1.2.1","title":"Root Edit Primitive Artifact Edit Proposal","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1211,"content":"The process for using the Root Edit Primitive begins with a party presenting a proposal for an Artifact Edit. The Root Edit Primitive specifies the requirements to submit a proposal, the required form of the proposal, and any other prerequisites that must be satisfied prior to the proposal being voted on.","contentHash":"21dc145b8c2152f54d48fd108db521f775e3c1bde826c7e5d856a5b4d39da10e","addressRefs":[]},"823cad54-4438-4ec3-9e13-d2624795fabd":{"id":"823cad54-4438-4ec3-9e13-d2624795fabd","doc_no":"A.2.2.5.2.1.2.2","title":"Root Edit Primitive Review By Operational Facilitator","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1212,"content":"The Operational Facilitator reviews the proposal. This review encompasses two aspects. First, the Operational Executor reviews the proposal for alignment with the Atlas. Second, the Facilitator reviews the proposal for compliance with any requirements set out in the Root Edit Primitive for the Agent, such as eligible actors to submit proposals, form of the proposal, or required time for review before submitting a proposal.","contentHash":"7a96b467414aa4c3ecb9e958678772a3a5569179679b3e2eaa49546aed07eacc","addressRefs":[]},"7e4574c0-a83c-4e3f-bfa6-1f66db2a0aed":{"id":"7e4574c0-a83c-4e3f-bfa6-1f66db2a0aed","doc_no":"A.2.2.5.2.1.2.3","title":"Root Edit Primitive Voting","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1213,"content":"If the Operational Facilitator concludes that the proposal is aligned with the Atlas and consistent with the process specified in the Root Edit Primitive, then the Operational Facilitator moves forward with conducting the vote. The Root Edit Primitive specifies how the vote should be conducted (e.g. on-chain or off-chain), the time period over which voting should occur, and other relevant parameters for the vote such as quorum and approval requirements.","contentHash":"10c01618a63fb54b3e0322c56aaaa559a421854bb244d8b0585b6f3589e1b13a","addressRefs":[]},"34d06691-afc4-4ade-9ada-ad180c2aef0f":{"id":"34d06691-afc4-4ade-9ada-ad180c2aef0f","doc_no":"A.2.2.5.2.1.2.4","title":"Root Edit Primitive Artifact Update","type":"Core","depth":6,"parentId":"f543db65-dac7-494d-bd0d-a24bf600157d","order":1214,"content":"After the voting period ends, the Operational Facilitator reviews the outcome of the vote. If the vote is successful, the Operational Facilitator actions the Artifact Edit in the Powerhouse system. In either case, the Operational Facilitator records the outcome of the vote, including all pertinent materials, in the Powerhouse system.","contentHash":"090cdbb634d2dbcee072f4d570aa7c2a5e7987dfa874473c1f12a888cdff9b5b","addressRefs":[]},"cec43505-2bf3-48ce-81d9-852f65edc468":{"id":"cec43505-2bf3-48ce-81d9-852f65edc468","doc_no":"A.2.2.5.2.2","title":"Root Edit Primitive Required Inputs","type":"Core","depth":5,"parentId":"78488c6b-d77f-4344-b954-476e415a2c7d","order":1215,"content":"The documents herein define the required inputs for a valid Invocation of the Root Edit Primitive. If any input is noncompliant or omitted, the Primitive will be invalidated and the Root Edit Primitive will not be set up.","contentHash":"a4fd75cdf8605da6afe1e8a7bad47cbcf752976425f4a481bac3953ec0ef39b9","addressRefs":[]},"416b0a3a-fa97-40ad-8b58-50650f4a956b":{"id":"416b0a3a-fa97-40ad-8b58-50650f4a956b","doc_no":"A.2.2.5.2.2.1","title":"Root Edit Primitive Activation Status","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1216,"content":"The Root Edit Primitive must be Globally Activated.","contentHash":"b1bce077b965263b58a82732e677c3058054ea3bd4420ffc99d4f0c8127c996f","addressRefs":[]},"dc7fd889-80dd-4ac0-b807-f01ab440ba8a":{"id":"dc7fd889-80dd-4ac0-b807-f01ab440ba8a","doc_no":"A.2.2.5.2.2.2","title":"Artifact Edit Process","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1217,"content":"The Root Edit Primitive must specify the process by which updates to the Agent Artifact may be made by Agent token holder vote. The details of this process may be specified by the Agent, subject to the following conditions: (1) Agent token holders must vote to approve Artifact Edit proposals, (2) the Operational Facilitator must review each proposal for alignment and conformance with the process specified in the Root Edit Primitive, (3) the vote must be conducted by the Operational Facilitator, and (4) the Operational Facilitator must action the Artifact Edit if the vote passes. The process definition must include the elements included in the documents herein.","contentHash":"f775cf308d5a5b8da5435e4359e7c3c48fcf0fc7b81532e1a03fce025257260c","addressRefs":[]},"7a473c50-f947-481b-8466-468b8d1708d9":{"id":"7a473c50-f947-481b-8466-468b8d1708d9","doc_no":"A.2.2.5.2.2.2.1","title":"Proposal Format","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1218,"content":"The Root Edit Primitive must specify the required format of proposals.","contentHash":"3e5c189bdb3a32738f30bc723596bddc0235ba260422f35fab86c7da8b5beeee","addressRefs":[]},"b5e21f94-5239-44c5-8eec-b5a5e6e05cf9":{"id":"b5e21f94-5239-44c5-8eec-b5a5e6e05cf9","doc_no":"A.2.2.5.2.2.2.2","title":"Actors Eligible To Submit Proposals","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1219,"content":"The Root Edit Primitive must specify the requirements for actors to be eligible to submit proposals.","contentHash":"d32b15279599a42454e28517474e5c7a7189add69c8f68cb605c5ded0d693209","addressRefs":[]},"0580f68b-06b4-41b0-b091-c88c8e6a0f81":{"id":"0580f68b-06b4-41b0-b091-c88c8e6a0f81","doc_no":"A.2.2.5.2.2.2.3","title":"Requirements For Proposals To Be Included In Vote","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1220,"content":"The Root Edit Primitive must specify the requirements for proposals to be included in a vote, such as any required review period or any reviews that must be conducted by other parties such as expert advisors.","contentHash":"17431d874e537e640f4388ed8326b1c30c8f4e3fc628254bbb57193a3d919887","addressRefs":[]},"0ca3f0ee-92ee-420e-915d-37aae1ab4848":{"id":"0ca3f0ee-92ee-420e-915d-37aae1ab4848","doc_no":"A.2.2.5.2.2.2.4","title":"Voting Period","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1221,"content":"The Root Edit Primitive must specify the period over which voting should occur.","contentHash":"f286b45b35661250bdab6469805def838909860d4e39a9eed8ee7e3ac0ea7e21","addressRefs":[]},"d4ad86a0-ec69-49b6-a794-6826cde3be0e":{"id":"d4ad86a0-ec69-49b6-a794-6826cde3be0e","doc_no":"A.2.2.5.2.2.2.5","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1222,"content":"The Root Edit Primitive must specify the percent of outstanding tokens that must participate in a vote for it to be considered valid.","contentHash":"0bcc8853e9e6e84aa2365278f13812a943e3e979a0d32893a37593d487473c63","addressRefs":[]},"0c36f76d-17de-4958-bace-d1b1d7473982":{"id":"0c36f76d-17de-4958-bace-d1b1d7473982","doc_no":"A.2.2.5.2.2.2.6","title":"Approval Threshold","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1223,"content":"The Root Edit Primitive must specify the percent of tokens participating in the vote that must vote in favor of the proposal for it to be approved.","contentHash":"d4000c0721fc6c7234d965ad7b4cb86f54fb57488170d721559fcf7c4cac0997","addressRefs":[]},"dda24bc9-d7e3-4593-9cdd-afe62355d198":{"id":"dda24bc9-d7e3-4593-9cdd-afe62355d198","doc_no":"A.2.2.5.2.2.2.7","title":"Handling Of Emergency Or Urgent Situations","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1224,"content":"The Root Edit Primitive must specify any procedures for expedited voting in emergency or urgent situations.","contentHash":"1b30359e76586f9c339139d2bf85195965689c7681662a253507c1a5503c056e","addressRefs":[]},"b6fa5678-0b62-4607-b0e9-b3d27f57f689":{"id":"b6fa5678-0b62-4607-b0e9-b3d27f57f689","doc_no":"A.2.2.5.2.2.2.8","title":"Special Voting Processes","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1225,"content":"The Root Edit Primitive must specify any exceptions to the general process, such as subject matter requiring supermajority approval.","contentHash":"ac8399d642ea0a64b7c88f8020942a9c0e43bf3400a635fd390ce6bcf4e63779","addressRefs":[]},"82f9f4b9-76db-4ad7-94af-200ffe7c3b75":{"id":"82f9f4b9-76db-4ad7-94af-200ffe7c3b75","doc_no":"A.2.2.5.2.2.2.8.1","title":"Agent Termination Process","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1226,"content":"The Agent Termination Process, as specified in [A.1.14.5 - Agent Termination Protocol](fe833d0e-8451-45e0-84a5-229d6ec964a8), deviates from the general Artifact Edit Process and follows the special voting process specified in the documents herein.","contentHash":"e7f064a7a69fed9ffa8a7235934a3cdbe98f27008dc88b6c27e6afb359feedce","addressRefs":[]},"02fb768f-d21e-4c00-baf4-3bc9ac999269":{"id":"02fb768f-d21e-4c00-baf4-3bc9ac999269","doc_no":"A.2.2.5.2.2.2.8.1.1","title":"Voting Period","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1227,"content":"The Root Edit Primitive must specify a voting period of at least 14 days.","contentHash":"24735ffa45718b4a7294934a5436905e29451349f1879f19b49012ea41b9d0c8","addressRefs":[]},"119efbc0-f67d-4719-8180-e41333a3edd4":{"id":"119efbc0-f67d-4719-8180-e41333a3edd4","doc_no":"A.2.2.5.2.2.2.8.1.2","title":"Quorum Requirement","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1228,"content":"The Root Edit Primitive must specify a minimum quorum of at least 20% of outstanding tokens.","contentHash":"c6a6df52749c9414485afb7be41923ee1799c5f5825430ce185ddf1a702f6a1f","addressRefs":[]},"f6dc0c8e-7c22-445b-a42a-c6ab1250a4d8":{"id":"f6dc0c8e-7c22-445b-a42a-c6ab1250a4d8","doc_no":"A.2.2.5.2.2.2.8.1.3","title":"Approval Threshold","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1229,"content":"The Root Edit Primitive must specify a supermajority approval threshold where at least two-thirds (2/3) of votes cast are in favor.","contentHash":"c5f7c1a2bec8f505c3a58edb01c03bb853f9bab70f59ab7f1b9a161a162ed37b","addressRefs":[]},"42cedad0-9458-4f45-a87b-2313df539311":{"id":"42cedad0-9458-4f45-a87b-2313df539311","doc_no":"A.2.2.5.2.2.2.8.1.4","title":"Required Notice","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1230,"content":"The Root Edit Primitive must require the Operational Facilitator to issue advance notice of the Agent's proposed termination and the subsequent Agent vote in the Sky Forum.","contentHash":"9c0c5029fa8825f3f414e7cdf90799020c1f0a395a4e9bab4224e6a093feecdd","addressRefs":[]},"56c255d4-a827-43a5-8eec-44b9d629023c":{"id":"56c255d4-a827-43a5-8eec-44b9d629023c","doc_no":"A.2.2.5.2.2.2.8.1.5","title":"Compliance Deadline For Existing Prime Agents","type":"Core","depth":6,"parentId":"cec43505-2bf3-48ce-81d9-852f65edc468","order":1231,"content":"Existing Prime Agents whose Root Edit Primitive does not already incorporate the requirements specified in [A.2.2.5.2.2.2.8.1 - Agent Termination Process](82f9f4b9-76db-4ad7-94af-200ffe7c3b75) must update their Agent Artifact to include them by September 1, 2026.","contentHash":"b5b2cee4ae6d09435377ccba89094047e5057860244f72f8a0a99720688d1ca3","addressRefs":[]},"459f257e-ef68-43b0-8d39-7836d98067ff":{"id":"459f257e-ef68-43b0-8d39-7836d98067ff","doc_no":"A.2.2.5.2.3","title":"Short-Term Limitations On Usage Of Root Edit Primitive","type":"Core","depth":5,"parentId":"78488c6b-d77f-4344-b954-476e415a2c7d","order":1232,"content":"In the short term, usage of the Root Edit Primitive by Prime Agents will be limited as specified in the documents herein.","contentHash":"0cf216873af76c7abb7f7355a2701a4c0cee8bcaa4faa5b014470e5075041102","addressRefs":[]},"8c15762a-ea7e-4c6d-9089-60d30c219c0f":{"id":"8c15762a-ea7e-4c6d-9089-60d30c219c0f","doc_no":"A.2.2.5.2.3.1","title":"Limitations On Usage Of Root Edit Primitive Prior To Tokens Being Publicly Held","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1233,"content":"Until the tokens of a Prime Agent are Publicly Held, as defined in [A.2.2.5.2.3.1.1 - Publicly Held Definition](d6265f88-d2d0-457b-8958-a3c22f9a5718), the Root Edit Primitive will not be operational. Instead, if a Prime Agent wishes to edit its Agent Artifact, it must use the customary Atlas Edit Proposal processes specified in the Sky Core Atlas at [A.1.11.2 - Atlas Edit Weekly Cycle](14e99d92-71fc-44d9-9dbf-933bce2e1b32) or [A.1.12.2 - Atlas Edit Monthly Cycle](d2cbddd2-58ef-4311-a71d-d2c340364cb5). The process for Prime Agents to use the Atlas Edit Proposal process is further specified in [A.2.2.5.2.3.2 - Atlas Edit Proposal Process For Prime Agents](364e52eb-4529-46a9-9852-edaaab88baeb).","contentHash":"3e6206bf99a242e7601dbfb7bcdcd25f92a694a7a9b5968c226e45ece56bcb1b","addressRefs":[]},"d6265f88-d2d0-457b-8958-a3c22f9a5718":{"id":"d6265f88-d2d0-457b-8958-a3c22f9a5718","doc_no":"A.2.2.5.2.3.1.1","title":"Publicly Held Definition","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1234,"content":"The tokens of a Prime Agent shall be deemed Publicly Held if they are held by at least 2,000 Public Holders who collectively own 10% or more of the Prime Agent’s portion of its genesis supply, as defined in [A.2.2.4.4.2.4 - Agent Token Genesis Supply](ed342c6e-15ae-4c95-ad4e-4702c27eba62).\n\nPublic Holders are unique wallet addresses, excluding any address reasonably believed to be controlled by the Prime Agent, its core contributors, or their affiliates. An entity is affiliated with another if it directly or indirectly controls, is controlled by, or is under common control with such other entity.\n\nTo qualify as a Public Holder, tokens owned by a wallet address must not be subject to any contractual, legal, or technical transfer restrictions, including:\n\n(a) time-based vesting or lock-up schedules;\n(b) contractual resale limitations (including any limitations imposed by token purchase agreements, SAFTs, or other similar instruments); or\n(c) smart contract restrictions that prevent transfer without further governance action.\n\nTokens held in liquidity pools or staking contracts shall be attributed to the beneficial owners of the deposited tokens, rather than to the pool or contract itself, for purposes of determining both the number of Public Holders and their collective ownership.\n\nThe Core Executor Agents are responsible for determining whether the tokens of a Prime Agent are Publicly Held. If the Core Executor Agents believe that a Prime Agent’s tokens are sufficiently decentralized despite failing to meet the technical criteria specified herein, they may conduct a Governance Poll to determine whether the Prime Agent’s tokens should be deemed Publicly Held.","contentHash":"5bf6afc1d08a81eeafd1f0b671f5d638118cf0b02a169c3a3897da5c8f777119","addressRefs":[]},"364e52eb-4529-46a9-9852-edaaab88baeb":{"id":"364e52eb-4529-46a9-9852-edaaab88baeb","doc_no":"A.2.2.5.2.3.2","title":"Atlas Edit Proposal Process For Prime Agents","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1235,"content":"Prime Agents that do not have an operational Root Edit Primitive must work with Core GovOps to use the Atlas Edit Weekly Cycle (see [A.1.11.2 - Atlas Edit Weekly Cycle](14e99d92-71fc-44d9-9dbf-933bce2e1b32)) process to update their Agent Artifacts, as specified in the documents herein.","contentHash":"25e330c0befe874886181ca9c8881ea178ab3f16cd007d1cd546f3ea4ce8d22e","addressRefs":[]},"461272f0-e9ae-43df-9571-4be49a2286c7":{"id":"461272f0-e9ae-43df-9571-4be49a2286c7","doc_no":"A.2.2.5.2.3.2.1","title":"Prime Agent Submits Draft Proposal To Core GovOps","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1236,"content":"The Prime Agent must submit a draft of the proposed edit to Core GovOps by 23:59 UTC on Monday in a given week. The draft need not be in the form of Atlas documents but should reflect a finished work product of the Prime Agent that is logically organized, contains all pertinent information, and is free of ambiguities to the best of the Prime’s ability.","contentHash":"9b172de97a3a29e1b8ccc0ce46733b181bb28c539925187645b9039b2667f148","addressRefs":[]},"07d1ed44-c457-49b9-a054-50e26aa70acc":{"id":"07d1ed44-c457-49b9-a054-50e26aa70acc","doc_no":"A.2.2.5.2.3.2.2","title":"Core GovOps Submits Atlas Edit Weekly Cycle Proposal","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1237,"content":"Upon receiving the draft from the Prime Agent, Core GovOps drafts a formal Atlas Edit Weekly Cycle proposal containing the relevant content, shares a draft with the Prime Agent for review, and then submits that proposal to be voted on Monday of the following week.","contentHash":"c8648cf5e327b158b22954c825030004dbd4f6241f719c74b4ca6bb36ae3ca31","addressRefs":[]},"4b37392d-9c0f-4572-8293-e7c6b3fc3743":{"id":"4b37392d-9c0f-4572-8293-e7c6b3fc3743","doc_no":"A.2.2.5.2.3.2.2.1","title":"Potential Delays In Submission","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1238,"content":"Core GovOps may in their discretion delay submitting a proposed edit based on factors including, but not limited to:\n\n- the size of the proposed edit;\n- any ambiguities in the proposed edit;\n- broader issues raised by the proposed edit requiring other changes or consultation with other stakeholders;\n- delays by the Prime Agent in responding to questions or requests to review drafts by Core GovOps; and\n- the overall workload of Core GovOps.","contentHash":"4b49009b57ea987d777e6754c1cc0e72138532684796aabc2f28e690ad428112","addressRefs":[]},"afeaa98f-b8f5-48d9-adb2-8ceed287667d":{"id":"afeaa98f-b8f5-48d9-adb2-8ceed287667d","doc_no":"A.2.2.5.2.3.2.3","title":"Atlas Edit Weekly Cycle Proposal Is Approved Or Rejected","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1239,"content":"The Atlas Edit Weekly Cycle proposal, if triggered by a Ranked Delegate and not rejected by the Core Facilitator for misalignment, is either approved or rejected by SKY holders by Thursday of the following week. A proposal that is not triggered or is rejected by the Core Facilitator for misalignment is treated as rejected.","contentHash":"dcaf17a1acb1c59b4a881e5217de799d1f1c5a7304b6a4cf7dc466d3426f6045","addressRefs":[]},"61414e64-815d-4bab-8b8b-f81d787453b6":{"id":"61414e64-815d-4bab-8b8b-f81d787453b6","doc_no":"A.2.2.5.2.3.2.4","title":"If Approved Then Prime Agent Begins Operationalizing Change","type":"Core","depth":6,"parentId":"459f257e-ef68-43b0-8d39-7836d98067ff","order":1240,"content":"If the Atlas Edit Weekly Cycle proposal is approved by SKY holders, then the Prime Agent may begin operationalizing that logic immediately thereafter.","contentHash":"a589d0b5dfdec58ce4a022ed12deb9eb064c86f06f75101bfe964fe888621dba","addressRefs":[]},"44028423-2cd1-40cb-89ac-3f762b602b90":{"id":"44028423-2cd1-40cb-89ac-3f762b602b90","doc_no":"A.2.2.5.3","title":"Light Agent Primitive","type":"Core","depth":4,"parentId":"0192ec95-9207-480e-8c51-88d2a1da95ad","order":1241,"content":"The Light Agent Primitive enables users to create Light Agents, which are sub-agents operating on top of the Agent’s Executor Accord, conferring the advantages of Sky GovOps at a lower cost, but without direct access to other Sky Primitives.","contentHash":"55ef8c0bdda956fa49c8ba11d3c42d013f16911ad10e7c75ff0d8f8de95aa7d9","addressRefs":[]},"25673fd2-76cb-4c4d-8ec6-8c489207bcfc":{"id":"25673fd2-76cb-4c4d-8ec6-8c489207bcfc","doc_no":"A.2.2.6","title":"Ecosystem Upkeep Primitives","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1242,"content":"Ecosystem Upkeep Primitives ensure that all Agents contribute to long-term ecosystem sustainability. The Ecosystem Upkeep Fee Primitive specifies a uniform upkeep fee payable by all Prime Agents, and the Upkeep Rebate Primitive specifies rebates that adjust those fees for Agents holding the tokens of other Prime Agents. The term \"Ecosystem Upkeep Fees\" refers to the upkeep obligation of a Prime Agent as specified in the Ecosystem Upkeep Fee Primitive.","contentHash":"25b7852e92385d7606f986233bb5bfeb7cd69bea90ab394706e9cf652b8bc406","addressRefs":[]},"a21616f4-1611-4e0b-87b2-efbdff9f6f28":{"id":"a21616f4-1611-4e0b-87b2-efbdff9f6f28","doc_no":"A.2.2.6.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":4,"parentId":"25673fd2-76cb-4c4d-8ec6-8c489207bcfc","order":1243,"content":"The Ecosystem Upkeep Fee Primitive requires Prime Agents to pay an annual fee equivalent to 50 basis points (bps) (0.50%) of their market capitalization to Sky, payable in USDS and accounted for monthly. The annual fee of 50 basis points (bps) (0.50%) of the market capitalization is divided into twelve (12) equal monthly payments. Payments must occur on the first day of each month, with the fee transferred to an address designated by Sky Core in [A.2.2.6.1.1 - Sky Core-Designated Address](2a5f0e38-e51a-4a68-a4b8-1a912b8bb12e).","contentHash":"5e046b92938e193c516be9ea66b3bc84f2dfc7ced82c37f1c5c70480dc943638","addressRefs":[]},"2a5f0e38-e51a-4a68-a4b8-1a912b8bb12e":{"id":"2a5f0e38-e51a-4a68-a4b8-1a912b8bb12e","doc_no":"A.2.2.6.1.1","title":"Sky Core-Designated Address","type":"Core","depth":5,"parentId":"a21616f4-1611-4e0b-87b2-efbdff9f6f28","order":1244,"content":"The address to which the fee must be transferred will be specified in a future iteration of the Atlas.","contentHash":"6deb00d384e7ccd5b290042b63a69bd7cbed04c395a06733484cd468564db0e4","addressRefs":[]},"4b856873-8c6a-449a-8ca6-487d8fed9029":{"id":"4b856873-8c6a-449a-8ca6-487d8fed9029","doc_no":"A.2.2.6.1.2","title":"Valuation","type":"Core","depth":5,"parentId":"a21616f4-1611-4e0b-87b2-efbdff9f6f28","order":1245,"content":"The market capitalization is determined as the total token supply multiplied by the TWAP of the token over the 24-hour period ending at 23:59 UTC on the last day of each month, immediately preceding the payment event. This value is applied in the rebate calculation under the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"4ba50b8fd7eb4a91865781370f2e54dd5c00fc1c84d3312abf25b9f0343010c2","addressRefs":[]},"569e1c2b-0e69-43e7-8491-06cc5f7d2988":{"id":"569e1c2b-0e69-43e7-8491-06cc5f7d2988","doc_no":"A.2.2.6.2","title":"Upkeep Rebate Primitive","type":"Core","depth":4,"parentId":"25673fd2-76cb-4c4d-8ec6-8c489207bcfc","order":1246,"content":"The Upkeep Rebate Primitive allows a Prime Agent (\"Holding Agent\") to claim a rebate on its Ecosystem Upkeep Fees when it holds any portion of the token supply of another Prime Agent (\"Issuing Agent\").\n\nEcosystem Upkeep Fees are accounted on a monthly basis. The Upkeep Rebate is calculated on the same cadence per Holding Agent as follows:\n\n1. The Holding Agent’s share of the Issuing Agent’s token supply at the time the Issuing Agent pays its Ecosystem Upkeep Fees, multiplied by\n2. The total monthly Ecosystem Upkeep Fees paid by the Issuing Agent, calculated as specified in [A.2.2.6.1.2 - Valuation](4b856873-8c6a-449a-8ca6-487d8fed9029).\n\nThis resulting rebate amount is applied against the Holding Agent’s Ecosystem Upkeep Fees due in the calendar month immediately following the Issuing Agent’s payment.","contentHash":"5974da9ba64976f9ada776cbe0eb45ca9ea03841f22cde1c1ce78ef80e3bf9ae","addressRefs":[]},"7b5d8965-a64c-4c44-b742-607f51f69d8f":{"id":"7b5d8965-a64c-4c44-b742-607f51f69d8f","doc_no":"A.2.2.7","title":"SkyLink Primitives","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1247,"content":"SkyLink Primitives are Sky Primitives that are technical infrastructure that extends the Sky Protocol. SkyLink Primitives are built autonomously by Prime Agents, but owned by Sky Core and shared among all Prime Agents. Prime Agents are reimbursed for the cost of setting up SkyLink Primitives and given additional first-mover incentives.","contentHash":"f1332a7b2a27496d397199ffe914b2440e085acba21b30767253903fe179ace5","addressRefs":[]},"4504d2d4-ee45-4a07-8c5b-9baf20b12e76":{"id":"4504d2d4-ee45-4a07-8c5b-9baf20b12e76","doc_no":"A.2.2.7.1","title":"Token SkyLink Primitive","type":"Core","depth":4,"parentId":"7b5d8965-a64c-4c44-b742-607f51f69d8f","order":1248,"content":"The Token SkyLink Primitive allows users to bridge USDS, sUSDS, SKY, or an Agent token to new blockchains and enables other multichain features.","contentHash":"0a396e3e787cd769264f2a70b57aff621af39051e8e39d86337096a3b3489465","addressRefs":[]},"18386a64-1f20-4495-99a0-2271c7d607b0":{"id":"18386a64-1f20-4495-99a0-2271c7d607b0","doc_no":"A.2.2.7.1.1","title":"Token SkyLink Process Definition","type":"Core","depth":5,"parentId":"4504d2d4-ee45-4a07-8c5b-9baf20b12e76","order":1249,"content":"The documents herein define the Process Definition for initial setup and ongoing management of the Token SkyLink Primitive.","contentHash":"507f7951c0536d06f7ce2319085a1e22da14126d16975bacb376fedb151bb2ea","addressRefs":[]},"408400c0-db9d-41d8-b657-de59ac18a288":{"id":"408400c0-db9d-41d8-b657-de59ac18a288","doc_no":"A.2.2.7.1.1.1","title":"Token SkyLink Setup Process Definition","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1250,"content":"The documents herein define the process for setting up an Instance of the Token SkyLink Primitive.","contentHash":"cc416ace1a05e9e23fc2440c3dd951baef953e65de282ac2e739c3ba84e9f140","addressRefs":[]},"f1836fc1-8691-4520-8159-e6d451a256b3":{"id":"f1836fc1-8691-4520-8159-e6d451a256b3","doc_no":"A.2.2.7.1.1.1.1","title":"Token SkyLink Setup Real World Agreements And Planning","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1251,"content":"The documents herein define the preliminary, off-chain human coordination stage of setting up an Instance of the Token SkyLink Primitive.","contentHash":"131f94fb10b1e5bb18e577e93a97e500b6a427db0e2a21849fc8e0a2ec877f6f","addressRefs":[]},"298ee5be-2f95-46b2-8dc7-8cf68f99c038":{"id":"298ee5be-2f95-46b2-8dc7-8cf68f99c038","doc_no":"A.2.2.7.1.1.1.1.1","title":"Token SkyLink Setup Target Chain Identification And Feasibility Analysis","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1252,"content":"The Prime Agent researches potential target blockchains for token bridging, including evaluation of user base, DeFi ecosystem, and bridging security requirements. The Prime Agent confirms that the target chain supports LayerZero or can be integrated easily with the LayerZero Omnichain Fungible Token standard. The Prime Agent also estimates potential use of the token on the target chain to justify the bridge deployment and audit costs. The output of this step is a preliminary decision to proceed with deploying a bridge to the target chain including a scope of work for the bridge deployment and estimated audit costs.","contentHash":"cf36abc8ff289c32b8e5f7a47077df0ebf937ac710180d252e9a77c9576f558c","addressRefs":[]},"eec4c93e-5012-4547-b1ad-ab6ba6d7042c":{"id":"eec4c93e-5012-4547-b1ad-ab6ba6d7042c","doc_no":"A.2.2.7.1.1.1.1.2","title":"Token SkyLink Setup Initial Alignment With Operational GovOps","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1253,"content":"The Prime Agent presents the bridging plan to Operational GovOps, including a technical summary, proposed timeline, and estimate of audit costs. The Prime Agent and Operational GovOps also discuss any guidelines in the Atlas or the Agent Artifact that may affect bridging. The Prime Agent receives early feedback on the plan and modifies it accordingly. The output of this step is an informal agreement to proceed with developing a bridge deployment along with any documented conditions or feedback from Operational GovOps.","contentHash":"64e511f3b364b8a469e2cfe117482a3bc0389d9efa6a01709ffc8073cdda3cf9","addressRefs":[]},"aa9f9672-2d80-404b-9c6e-fe69615fc125":{"id":"aa9f9672-2d80-404b-9c6e-fe69615fc125","doc_no":"A.2.2.7.1.1.1.1.3","title":"Token SkyLink Setup Audit Preparation And Proposal Of Costs","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1254,"content":"The Prime Agent contacts a reputable third-party security audit firm for reviewing the bridge implementation. The Prime Agent negotiates audit scope, timeline, and fees with the audit firm. The Prime Agent documents the projected cost for the bridge, including development, audit, and deployment costs, for future reimbursement. The outcome of this step is a formal agreement with the audit firm and a detailed cost breakdown for bridge deployment and auditing.","contentHash":"78fcc14bbf6a4d1ae3132e92fda33dc94b592c6264ea356376f846ce5bd742ef","addressRefs":[]},"18ce8e21-898d-4bf9-9bf8-ef1c1e7266ee":{"id":"18ce8e21-898d-4bf9-9bf8-ef1c1e7266ee","doc_no":"A.2.2.7.1.1.1.2","title":"Token SkyLink Setup Codification and Validation","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1255,"content":"The documents herein define how agreements to setup an Instance of the Token SkyLink Primitive are codified and validated in the Powerhouse system and how governance votes happen.","contentHash":"a16645feb82ca2745b2fe7974e3e1dfadf7a71f2eb6a192ac3a179ef70ab953f","addressRefs":[]},"5027bb60-ea5f-4f1a-9ce6-a9a0afae33e5":{"id":"5027bb60-ea5f-4f1a-9ce6-a9a0afae33e5","doc_no":"A.2.2.7.1.1.1.2.1","title":"Agent Inputs","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1256,"content":"The Prime Agent drafts an update to the Prime Agent Artifact adding the Token SkyLink to the list of active Token SkyLink deployments and including the information specified in [A.2.2.7.1.2.2 - List of Active Token SkyLink Deployments](bf3ede73-bba3-4048-b105-a49400611fcb). The Prime Agent submits the draft to the Powerhouse system. The output of this step is a draft Prime Agent Artifact update in the Powerhouse system.","contentHash":"3de22dbb051a20ca5e54384d39e9ae2b552355a201fce1f3f0e23dab05887e5f","addressRefs":[]},"cac40223-e628-4248-a44d-2aaa6f03ba00":{"id":"cac40223-e628-4248-a44d-2aaa6f03ba00","doc_no":"A.2.2.7.1.1.1.2.2","title":"Validation And Off-Chain Vote","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1257,"content":"The Operational Executor Facilitator reviews the proposal to ensure that it is complete and aligned with the Atlas. The Operational Executor Facilitator then initiates an off-chain snapshot vote, following the quorum and majority rules in the Prime Agent Artifact. When complete, the result of the vote is recorded in the Powerhouse system. The output of this step is the snapshot vote result recorded in the Powerhouse system.","contentHash":"86115322f768ad057136e3bdfce7754eeb5564bfb74a05f231acc272f13baa8a","addressRefs":[]},"79abf483-f256-4ef6-9aa7-558a8800e7a8":{"id":"79abf483-f256-4ef6-9aa7-558a8800e7a8","doc_no":"A.2.2.7.1.1.1.2.3","title":"Official Update of Artifact","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1258,"content":"If the Token SkyLink Invocation is successfully approved, the Operational Executor Facilitator finalizes and publishes the update to the Prime Agent Artifact, making it effective in the Atlas. The output of this step is an updated Prime Agent Artifact with the Token SkyLink Instance Activated.","contentHash":"e088e9cb868cf62ce4d0dbc348ab7ed8fec9215ceec114ea2ca988ea2870a3dc","addressRefs":[]},"21241867-d25e-47ee-b4c2-13224dcd0292":{"id":"21241867-d25e-47ee-b4c2-13224dcd0292","doc_no":"A.2.2.7.1.1.1.3","title":"Token SkyLink Setup Deployment","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1259,"content":"The documents herein define how the deployment of an Instance of the Token SkyLink Primitive is executed on-chain.","contentHash":"68c4218c78a5ba463ae3501cd6f10701a2d033c111b34e9022452bdc688e2e08","addressRefs":[]},"af88c454-2171-41ce-a8e8-1d6c40d4e209":{"id":"af88c454-2171-41ce-a8e8-1d6c40d4e209","doc_no":"A.2.2.7.1.1.1.3.1","title":"Token SkyLink Setup Bridge Deployment And Initial Audit","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1260,"content":"The Prime Agent, through Operational GovOps, deploys the Token SkyLink contract on the target chain. The Prime Agent shares the Token SkyLink contract’s final address with the audit firm for verification. Operational GovOps confirms that the bridge contract address and references match the updated Prime Agent Artifact. The audit firm completes and updates the bridging audit registry with the results of the audit. The output of this step is a deployed bridge contract with audit results uploaded to the bridging audit registry.","contentHash":"03472e4f6f12f367f2b03bdb6fa8c1173d6f3acef4634d56ba27d73a5ffa3cd0","addressRefs":[]},"c18d8c58-d347-4efd-9c33-4fd89cf40f90":{"id":"c18d8c58-d347-4efd-9c33-4fd89cf40f90","doc_no":"A.2.2.7.1.1.1.3.2","title":"Token SkyLink Setup Activation On New Chain","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1261,"content":"Core GovOps formalizes the audit results with a Sky Core Executive Vote to fully activate bridging functionality. Operational GovOps updates the Prime Agent Reimbursement Module to begin counting any bridged tokens toward the incremental reward. The output of this step is fully enabled bridging on the target chain with the Prime Agent Reimbursement Module updated to track bridging based rewards.","contentHash":"603588cdb902ff2fc9abaa98160773688bbe0bb66da7f8e0f9c086fc6ee20980","addressRefs":[]},"d7adf706-c9cc-4408-9668-cec0fdc90be8":{"id":"d7adf706-c9cc-4408-9668-cec0fdc90be8","doc_no":"A.2.2.7.1.1.2","title":"Token SkyLink Ongoing Management","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1262,"content":"The documents herein define the process for managing an Instance of the Token SkyLink Primitive.","contentHash":"c7aaba52151c5176ec1a62b2a7bb9b8fc552bbf1daef00b44f5f1a60d73d1874","addressRefs":[]},"97fb1954-b9f4-429e-bc29-e9eea9fe2e0e":{"id":"97fb1954-b9f4-429e-bc29-e9eea9fe2e0e","doc_no":"A.2.2.7.1.1.2.1","title":"Token SkyLink Management Settlement Cycle","type":"Core","depth":6,"parentId":"18386a64-1f20-4495-99a0-2271c7d607b0","order":1263,"content":"During each settlement cycle, the Prime Agent Reimbursement Module tallies the total token bridging volume on the new chain. The Prime Agent Reimbursement Module calculates the reimbursement due for bridge development costs as a percent of the token bridging volume, in addition to normal Distribution Rewards if applicable. Core GovOps executes a payment to the Prime Agent for the amount due for reimbursement of bridge development costs, to the extent that such costs have not already been fully reimbursed. Core GovOps updates the Powerhouse system to reflect the amount of bridge development costs that have been reimbursed.","contentHash":"244782b3a6e3a04355cdfc8a3dab9c1e3ef181d3b811fac621caf975dea38b91","addressRefs":[]},"7d9a8373-ed56-4b01-8ec7-ebf2ed4ef8b0":{"id":"7d9a8373-ed56-4b01-8ec7-ebf2ed4ef8b0","doc_no":"A.2.2.7.1.2","title":"Token SkyLink Input Requirements","type":"Core","depth":5,"parentId":"4504d2d4-ee45-4a07-8c5b-9baf20b12e76","order":1264,"content":"The documents herein define the required inputs for a valid Token SkyLink Primitive. If any input is noncompliant or omitted, the Primitive will be invalidated and the SkyLink deployment will not move forward.","contentHash":"07207e58e038897c28e05bfffbdaa1f76ba99d337410fcc3d49e408d84f772f4","addressRefs":[]},"94a0a22c-cbd6-4022-80e8-4681f60c7cec":{"id":"94a0a22c-cbd6-4022-80e8-4681f60c7cec","doc_no":"A.2.2.7.1.2.1","title":"Token SkyLink Activation Status","type":"Core","depth":6,"parentId":"7d9a8373-ed56-4b01-8ec7-ebf2ed4ef8b0","order":1265,"content":"The Token SkyLink Primitive must be Globally Activated.","contentHash":"4b8a97e283e0c9c915721a22dd9848453012a3871b251148814e9336866198bc","addressRefs":[]},"bf3ede73-bba3-4048-b105-a49400611fcb":{"id":"bf3ede73-bba3-4048-b105-a49400611fcb","doc_no":"A.2.2.7.1.2.2","title":"List of Active Token SkyLink Deployments","type":"Core","depth":6,"parentId":"7d9a8373-ed56-4b01-8ec7-ebf2ed4ef8b0","order":1266,"content":"The Token SkyLink Primitive must list each active Token SkyLink deployment. The listing must include the following information: (1), the token being bridged, (2) the target chain of the bridge, (3) the address of the bridge contract on the Ethereum Mainnet, (4) the address of the bridge contract on the target chain, (5) the audit of the bridge contract, (6) the bridge parameters, (7) the total bridge deployment and audit costs, and (8) the amount of bridge deployment and audit costs that have been reimbursed to date.","contentHash":"b9f424e5b7f0d232222b2e0d0f080064aa973be4a1e56ffee107d0977c2e4884","addressRefs":[]},"26415305-432d-423b-9553-3f325279712d":{"id":"26415305-432d-423b-9553-3f325279712d","doc_no":"A.2.2.8","title":"Demand Side Stablecoin Primitives","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1267,"content":"Demand Side Stablecoin Primitives are Sky Primitives that target demand generation for USDS. Prime Agents can create and control multiple instances of these Primitives which exist as technical infrastructure incentivizing the adoption or usage of USDS by end users or third parties.","contentHash":"28e53365d3c76892ffc7ad46e5b139bf541ff4621cdaee2b89d7a0192724d320","addressRefs":[]},"e632c38f-3e4e-4c7e-acfd-b6ec45a422e6":{"id":"e632c38f-3e4e-4c7e-acfd-b6ec45a422e6","doc_no":"A.2.2.8.1","title":"Distribution Reward Primitive","type":"Core","depth":4,"parentId":"26415305-432d-423b-9553-3f325279712d","order":1268,"content":"The documents herein govern the Distribution Reward Primitive.","contentHash":"05d71f8a8da7807387613ca160aab5ddc6de161cd43b0724fc2b6b6cb39a78ba","addressRefs":[]},"02189c79-a529-4388-98ad-a743d2a8980d":{"id":"02189c79-a529-4388-98ad-a743d2a8980d","doc_no":"A.2.2.8.1.1","title":"Introduction","type":"Core","depth":5,"parentId":"e632c38f-3e4e-4c7e-acfd-b6ec45a422e6","order":1269,"content":"The documents herein provide an introduction to the Distribution Reward Primitive.","contentHash":"2bb3ad66bfb113492879b41a378e4770630fd15e0f0fe7c6665122bc1a06d901","addressRefs":[]},"6f1bc619-b8a9-4917-a34b-f52016942c01":{"id":"6f1bc619-b8a9-4917-a34b-f52016942c01","doc_no":"A.2.2.8.1.1.1","title":"Purpose","type":"Core","depth":6,"parentId":"02189c79-a529-4388-98ad-a743d2a8980d","order":1270,"content":"The purpose of the Distribution Reward is to incentivize Prime Agents and third parties to drive USDS adoption by providing a financial reward to these actors for all USDS and sUSDS balances attributable to them.","contentHash":"05cae2e103d86554eb55dc40b9954ddc069583ef7eb4bf3f63974d38f53c80ec","addressRefs":[]},"45149960-fbf3-4079-be4e-fe2a71e5e43f":{"id":"45149960-fbf3-4079-be4e-fe2a71e5e43f","doc_no":"A.2.2.8.1.1.2","title":"Allowed Number Of Instances","type":"Core","depth":6,"parentId":"02189c79-a529-4388-98ad-a743d2a8980d","order":1271,"content":"Multiple instances of the Distribution Reward Primitive are allowed. Each instance corresponds to a Distribution Reward program with an associated Distribution Reward Code.","contentHash":"8e68180d1e76d8d7af08fe03b218887f637271b3d01634e7664c18fb7b38a73f","addressRefs":[]},"c788ebcf-98a4-4b97-ae3c-db578c75dc2e":{"id":"c788ebcf-98a4-4b97-ae3c-db578c75dc2e","doc_no":"A.2.2.8.1.1.3","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"02189c79-a529-4388-98ad-a743d2a8980d","order":1272,"content":"An Agent Artifact that has more than one active instance of the Distribution Reward Primitive is not required to have a `Multi-Instance Coordinator Document`, since each Instance can be managed independently.","contentHash":"327cc5ee568ee59accebf5bdc85a9f0a8c6f9e58d967e50dd8b5f63d3606c47b","addressRefs":[]},"7f0959dc-c6e2-4e64-9526-76563a2a6d29":{"id":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","doc_no":"A.2.2.8.1.2","title":"Global Specification","type":"Core","depth":5,"parentId":"e632c38f-3e4e-4c7e-acfd-b6ec45a422e6","order":1273,"content":"The requirements herein apply universally across all possible deployments of the Distribution Reward Primitive by Prime Agents. They include the steps that Agents must take to deploy the Primitive, including Global Activation of the Primitive, Instance Invocation, and ongoing management of the Primitive Instance(s).","contentHash":"8df8ec527e22613977efc9390e96abf511df1228481ec2af379876fafcdcb2c5","addressRefs":[]},"dc123bca-eac1-40e1-ad1f-f888a6ec8d1f":{"id":"dc123bca-eac1-40e1-ad1f-f888a6ec8d1f","doc_no":"A.2.2.8.1.2.1","title":"Base Elements","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1274,"content":"The documents herein define base elements of the Distribution Reward Primitive.","contentHash":"e93ab0193695e20c476af205776ab896fa921f044955ac0ec231f558afcce6d1","addressRefs":[]},"37c38f07-b5a0-40df-939c-a54330ea3c7b":{"id":"37c38f07-b5a0-40df-939c-a54330ea3c7b","doc_no":"A.2.2.8.1.2.1.1","title":"Integrator Program","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1275,"content":"Integrators are actors that offer access to the Sky Protocol via their frontends or infrastructure. The documents herein define the Integrator Program, which includes the Distribution Reward and Integration Boost. (Base elements specific to the Integration Boost Primitive are defined in [A.2.2.8.2.2.1 - Base Elements](c398b383-3752-4534-aec6-4cd8e7292119))","contentHash":"93745ed3960fb3712bf88977edf468e37e699d469e29be6d8ae7cbb3cf57126d","addressRefs":[]},"1c2b6983-1e03-41b9-a2bf-70f3eca19b98":{"id":"1c2b6983-1e03-41b9-a2bf-70f3eca19b98","doc_no":"A.2.2.8.1.2.1.1.1","title":"Integrator Requirements","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1276,"content":"The documents herein define the requirements for Integrators.","contentHash":"acda8dabbb92b770ca9e60ac5f6e93b9d4a7deb5b4f965359ef4058de771a2b2","addressRefs":[]},"98e98f68-e749-4d0a-8972-7e36ed166326":{"id":"98e98f68-e749-4d0a-8972-7e36ed166326","doc_no":"A.2.2.8.1.2.1.1.1.1","title":"Alignment","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1277,"content":"The Integrator must be aligned with Sky’s overall strategy regarding promoting adoption of USDS. This determination is made by Operational GovOps. Sky Core may choose whether to maintain an Integrator’s Reward Code in its sole and absolute discretion.","contentHash":"1feb78580d92ee3d96e3c6d3a814669e87b5ce3bc40b172b75f42f7774f9d019","addressRefs":[]},"f3b4b43d-b2e5-4f56-aeac-9627d3acc31e":{"id":"f3b4b43d-b2e5-4f56-aeac-9627d3acc31e","doc_no":"A.2.2.8.1.2.1.1.1.2","title":"Compliance With Local Laws And Regulations As A Condition Precedent To Integrators Receiving Distribution Rewards","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1278,"content":"This document and its subdocuments define the jurisdictional compliance rules applicable to Integrators that operate user-facing frontends that integrate with, and thus offer access to, the Sky Protocol and receive Distribution Rewards.\n\nIntegrators are solely responsible for complying with all relevant legal and regulatory requirements related to their participation in the Integrator Program. Integrators represent and warrant that their participation and activities under the Integrator Program are and will remain in full compliance with all applicable laws and regulations.\n\nIn connection with integrating with, and thereby providing access to, the Sky Protocol, Integrators must operate their frontends and infrastructure in compliance with all relevant legal and regulatory requirements in the jurisdictions applicable to their services. This requires compliance with all relevant legal and regulatory requirements in relation to frontend operations, marketing, and promotions in the jurisdictions where the Integrator provides access to the Sky Protocol through the integration.\n\nAn Integrator’s right to participate in the Integrator Program is contingent upon its ongoing compliance with all applicable laws and regulations.","contentHash":"d39bca39d7755a471de888d07076fc8c48fc0e7744ecf826b5d2823a9664243c","addressRefs":[]},"a01622fa-e81c-4bcb-8e31-7e66e36f2e57":{"id":"a01622fa-e81c-4bcb-8e31-7e66e36f2e57","doc_no":"A.2.2.8.1.2.1.1.1.2.1","title":"Consequence For Integrator Non-Compliance With Local Laws And Regulations","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1279,"content":"Sky Ecosystem Governance, in its absolute and unilateral discretion, retains the right to withhold, revoke, or demand immediate repayment of any and all Distribution Rewards from any Integrator that is determined, suspected, or alleged to be in violation of the Atlas or any legal, regulatory, or other obligations associated with its integration with, and provision of access to, the Sky Protocol.","contentHash":"7c97481b690f676a02be1cc0f71b8fd86a7327ba654ca4c6d648308e4727f487","addressRefs":[]},"0bdcef8a-b851-42ed-b2e2-77d85c14dad0":{"id":"0bdcef8a-b851-42ed-b2e2-77d85c14dad0","doc_no":"A.2.2.8.1.2.1.1.1.2.2","title":"Removal From Integrator Program","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1280,"content":"If Sky Governance removes an Integrator from the Integrator Program, Operational GovOps must remove the Integrator from the list of Current Integrators in [A.2.2.8.1.2.1.6.1.0.6.1 - List Of Current Integrators](efbe7903-a76e-40f0-a440-56e463283157) and deactivate the Instances of the Distribution Reward and Integration Boost Primitive associated with them.","contentHash":"13bdfdbcee726189b3111e6ebc268333ea9afd3b04d7b98945c3429e62ba7fc7","addressRefs":[]},"abc79583-78da-4578-9ae0-51dc322ed1cb":{"id":"abc79583-78da-4578-9ae0-51dc322ed1cb","doc_no":"A.2.2.8.1.2.1.1.2","title":"Integrator Applications","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1281,"content":"The documents herein define the process for applying to become an Integrator.","contentHash":"a587eb445aa702edf4f618038aa74a50b2ee155aa823db37b06377100612e1fa","addressRefs":[]},"7fe5dbb2-a07d-4ef9-94de-f54a2d568c57":{"id":"7fe5dbb2-a07d-4ef9-94de-f54a2d568c57","doc_no":"A.2.2.8.1.2.1.1.2.1","title":"Near Term Process","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1282,"content":"In the near term, applications are made directly to Operational GovOps. Operational GovOps must create and maintain a thread on the Sky Forum for Integrator Applications. Operational GovOps reviews applications and coordinates with Prime Agents interested in working with specific applicants. Operational GovOps issues Reward Codes to approved applicants.","contentHash":"619bcc83bccf1fe66258174bad9fd49ba45a019d5cd52b85c4ab5b9cc8aa813b","addressRefs":[]},"d251bbac-df0e-4aff-a26b-33d60e153e19":{"id":"d251bbac-df0e-4aff-a26b-33d60e153e19","doc_no":"A.2.2.8.1.2.1.1.2.1.1","title":"Integrator Program Applications","type":"Active Data Controller","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1283,"content":"The list of Integrator Program applicants is defined as Active Data in [A.2.2.8.1.2.1.1.2.1.1.0.6.1 - List Of Integrator Applications](30db9618-ddf2-4df7-ad81-3f8f3395ff62).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"377cacec28dbd2a324631f11a010dba289f3debad01c4de66ede7fc64089c259","addressRefs":[]},"30db9618-ddf2-4df7-ad81-3f8f3395ff62":{"id":"30db9618-ddf2-4df7-ad81-3f8f3395ff62","doc_no":"A.2.2.8.1.2.1.1.2.1.1.0.6.1","title":"List Of Integrator Applications","type":"Active Data","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1284,"content":"The current Integrator Applications are:","contentHash":"40460efdea173298b5f9aebb587cfe57bd9411d428476d9c30cf9f742a1396f8","addressRefs":[]},"6283379c-d871-40a9-a915-d716d7df5642":{"id":"6283379c-d871-40a9-a915-d716d7df5642","doc_no":"A.2.2.8.1.2.1.1.2.2","title":"Long Term Process","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1285,"content":"In the long term, Integrator applications come exclusively through Prime Agents. Prime Agents may establish whatever processes they deem appropriate to receive inbound requests for potential partnerships.","contentHash":"b854265e6f293adb32b165546d0e51e3464e3b378e0124e16c5942401108bfbd","addressRefs":[]},"361e2e68-b2ab-4b1e-93ce-030cf25e509e":{"id":"361e2e68-b2ab-4b1e-93ce-030cf25e509e","doc_no":"A.2.2.8.1.2.1.1.3","title":"Integrator Onboarding","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1286,"content":"The documents herein define the process for onboarding new Integrators.","contentHash":"484470cd8efb17324360a5cb92352da0a1ac477376938f3fac5f943902ff464d","addressRefs":[]},"fc46821f-9d3d-4807-b519-d54faf546702":{"id":"fc46821f-9d3d-4807-b519-d54faf546702","doc_no":"A.2.2.8.1.2.1.1.3.1","title":"Process","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1287,"content":"When a Prime Agent’s Invocation of the Distribution Reward Primitive involves an actor who is not yet an approved Integrator, that actor must submit an Integrator Application to Operational GovOps. Operational GovOps determines whether the Integrator Requirements are met, and if so issues a Reward Code to the applicant. After the Reward Code has been issued, the Invocation of the Primitive may proceed. Operational GovOps may contract with another actor to perform the work of reviewing applications and issuing Reward Codes.","contentHash":"6d050c67d74fec8fd5c46a17904bf2808eec81a05559685d715210089decf8e7","addressRefs":[]},"cda71b0c-37cc-4f6a-92a3-b6a14895bfe1":{"id":"cda71b0c-37cc-4f6a-92a3-b6a14895bfe1","doc_no":"A.2.2.8.1.2.1.2","title":"Reward Codes","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1288,"content":"The documents herein define base elements related to Reward Codes.","contentHash":"8309dfecc3541a4c3383244a16a23e918540d1c35aac672c8c016cbd8c414aaa","addressRefs":[]},"225454ec-ac16-470e-b780-114acbb2a453":{"id":"225454ec-ac16-470e-b780-114acbb2a453","doc_no":"A.2.2.8.1.2.1.2.1","title":"Assignment","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1289,"content":"The documents herein define the process for assigning Reward Codes.","contentHash":"c7d8a49c5ab2251fd91ac64022ba69ddc3b9b1d9e8b80047f272b1a826893e65","addressRefs":[]},"e00e28d1-dad1-4cff-8ea4-1290c27d3b07":{"id":"e00e28d1-dad1-4cff-8ea4-1290c27d3b07","doc_no":"A.2.2.8.1.2.1.2.1.1","title":"Process","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1290,"content":"Reward Codes are assigned by Operational GovOps. Operational GovOps may contract with another actor to perform this work for them, at their discretion.","contentHash":"4515bbc155d36241dc81c228274251914f071aa6c5b59652959cd7f865555ae9","addressRefs":[]},"ec2c6d8a-e10f-471a-8f85-67803159cc37":{"id":"ec2c6d8a-e10f-471a-8f85-67803159cc37","doc_no":"A.2.2.8.1.2.1.2.2","title":"Marking","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1291,"content":"To be eligible for the Distribution Reward, USDS balances must be \"marked\" with a Reward Code using the agreed-on Tracking Methodology.","contentHash":"163ac6076827ea89c1397b8d378cd8275c6dae1d1d32fbd1470a9b65dc039115","addressRefs":[]},"87fd6861-ba8a-4bde-945e-ee9ad37ae3e2":{"id":"87fd6861-ba8a-4bde-945e-ee9ad37ae3e2","doc_no":"A.2.2.8.1.2.1.2.2.1","title":"Ethereum Mainnet General Tracking Methodology","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1292,"content":"The general Tracking Methodology for Ethereum Mainnet is to specify the Reward Code as a parameter to depositing USDS into the Sky Savings Rate contract or Token Rewards contracts. This on-chain deposit data is then combined with withdrawal data, which is further processed by Operational GovOps to estimate net deposits associated with the Reward Code on a First In First Out (FIFO) basis.","contentHash":"761d5fcb0c23610afc96823810b12a0956485f562d366389aefcffa2525e4380","addressRefs":[]},"1b5cc0ee-0ee8-467e-ab49-33c06ad417dc":{"id":"1b5cc0ee-0ee8-467e-ab49-33c06ad417dc","doc_no":"A.2.2.8.1.2.1.2.2.2","title":"Ethereum Mainnet CoW Swap Tracking Methodology","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1293,"content":"The Tracking Methodology for CoW Swap on the Ethereum Mainnet is the same as the general process for the Ethereum Mainnet, with the exception that events on CoW Swap’s decentralized network of solvers are tracked instead.","contentHash":"19b340638ed60730564c9e7d756023e595d506daabe0a3b3eedb61dd20cdb2df","addressRefs":[]},"f710bddf-dc1d-483c-9503-483574cb6333":{"id":"f710bddf-dc1d-483c-9503-483574cb6333","doc_no":"A.2.2.8.1.2.1.2.2.3","title":"Base Tracking Methodology","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1294,"content":"The Tracking Methodology for Base is to specify the Reward Code as a parameter in calls to the Base PSM contract. Conversions from USDS or USDC to sUSDS are considered \"deposits\" and net deposits are calculated using an approach similar to that on Ethereum Mainnet.","contentHash":"88aed8a05f9250c1fd4f6736d232da069de1bfc940b71a3c182e85c8ce6a3b1b","addressRefs":[]},"5eba1c21-4e93-4a0a-aa10-e99bcfa65f16":{"id":"5eba1c21-4e93-4a0a-aa10-e99bcfa65f16","doc_no":"A.2.2.8.1.2.1.2.2.4","title":"Alternative Tracking Methodologies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1295,"content":"The Tracking Methodologies specified above are not exclusive. Prime Agents and Operational GovOps can develop additional Tracking Methodologies, so long as those methodologies reasonably estimate USDS balances that are attributable to the holder of the Reward Code and there is no possibility that the same USDS balances could be \"double counted\" for multiple Reward Code holders. Tracking methodologies must be based on either (1) on-chain data or (2) off-chain data that can be independently verified or attested to by a third party.","contentHash":"b8f7c30293a7656fba0ab4b532ed4442d29cd0d0951e47702485e8237a2de3ab","addressRefs":[]},"c0b77312-5e88-4311-bfe2-d95a1a2c5a7c":{"id":"c0b77312-5e88-4311-bfe2-d95a1a2c5a7c","doc_no":"A.2.2.8.1.2.1.2.2.5","title":"Lifetime","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1296,"content":"USDS balances are eligible for a Distribution Reward for a period of ten (10) years from the date of the event marking the USDS balance with the Reward Code. The date of the marking event is determined based on the Primitive Instance’s specified Tracking Methodology.","contentHash":"b65264cbd9ce18de628df06294b249b80300454984f0dc9ee8bf73a1b45c80ad","addressRefs":[]},"75ddec36-c39e-4333-9ec1-2d329128e848":{"id":"75ddec36-c39e-4333-9ec1-2d329128e848","doc_no":"A.2.2.8.1.2.1.2.3","title":"Management","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1297,"content":"Operational GovOps manages the list of Actor Reward Codes. All current Integrators and onboarding Integrators must be specified in [A.2.2.8.1.2.1.6 - Current And Onboarding Integrators](f3952cc5-cde2-46b9-b575-034dda83570b) so that Prime Agents, through their Operational Executor Agents, can onboard new partners themselves without having to go through a single party.","contentHash":"1abe54f7843f355f84fada8435e110571926bc5abbdc4b6e722edc58a7423e03","addressRefs":[]},"57384c49-e499-4c69-b22c-8e1f1dd34759":{"id":"57384c49-e499-4c69-b22c-8e1f1dd34759","doc_no":"A.2.2.8.1.2.1.3","title":"Distribution Reward Rate","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1298,"content":"The standard Distribution Reward rate is set at 0.2%. The Distribution Reward rate is annualized on all USDS and sUSDS balances associated with the relevant Reward Code.","contentHash":"0bb09f23502f3d7d1501a65600d5ad64d100b65c9c20cddcf258a3824a6c7a1a","addressRefs":[]},"1d9219cb-9359-40de-96a0-ac60a8174c63":{"id":"1d9219cb-9359-40de-96a0-ac60a8174c63","doc_no":"A.2.2.8.1.2.1.3.1","title":"Boosted Distribution Reward Rate","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1299,"content":"An additional 0.3% Boosted Distribution Reward rate will be available starting January 2026 as specified in the documents herein. This Boosted Distribution Reward may be discontinued in the future at the discretion of Sky Governance.","contentHash":"0ffefdd25be2a208450a67a1cc2f6de51280f5a18966e47ab38ae7c5eea3161c","addressRefs":[]},"3f3162cc-c83c-471d-9dfa-1e0ccada4261":{"id":"3f3162cc-c83c-471d-9dfa-1e0ccada4261","doc_no":"A.2.2.8.1.2.1.3.1.1","title":"Approval Process","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1300,"content":"A Prime Agent may request the Boosted Distribution Reward rate for a specific Instance by posting on the Sky Forum under the \"Sky Core\" category. The Core Council will review requests and approve them at its discretion. The Core Facilitator must respond to each request with an approval or rejection decision in the thread of the original post.","contentHash":"b4711d37ef6e41db23d5f131eae270f0fdc4b4fe9c38cffca212b8ccb60e7249","addressRefs":[]},"ce66fc65-014f-447d-b068-2487ec11032e":{"id":"ce66fc65-014f-447d-b068-2487ec11032e","doc_no":"A.2.2.8.1.2.1.3.1.2","title":"Specification In The Instance Configuration Document","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1301,"content":"Prime Agent Instances approved for the Boosted Distribution Reward rate must document this designation in their Instance Configuration Document under \"Custom Instance Parameters\".","contentHash":"6ab1f2b5ce8185fc4d9f9051b6c3a1b6d5b6eba172b95c61c67114a19f468ad0","addressRefs":[]},"f2b3688f-e9e0-4159-9af3-0502141babab":{"id":"f2b3688f-e9e0-4159-9af3-0502141babab","doc_no":"A.2.2.8.1.2.1.3.1.3","title":"Limitations","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1302,"content":"The Boosted Distribution Reward rate is not applicable to USDS and sUSDS balances held by the Prime Agent itself.","contentHash":"7fd13b1d146e2ef232d5835ac8b9b25065c814d344988ea3991c86e9fe160e63","addressRefs":[]},"862b6d83-f464-4125-8259-233b7de75ec4":{"id":"862b6d83-f464-4125-8259-233b7de75ec4","doc_no":"A.2.2.8.1.2.1.4","title":"Demand Side Buffer","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1303,"content":"The Demand Side Buffer is the account used for disbursement of Distribution Reward and Integration Boost payments. The Demand Side Buffer is controlled by a multisig as specified in the documents herein. The balance of this account may be topped up through an Executive Vote.","contentHash":"82796fb03fae5651f6dbe8f62f68ae5e7a20fb4a66e0923915ef2f59c2127465","addressRefs":[]},"dadf97b5-1d71-42b2-9954-cd9a18d4345f":{"id":"dadf97b5-1d71-42b2-9954-cd9a18d4345f","doc_no":"A.2.2.8.1.2.1.4.1","title":"Demand Side Buffer Multisig Address","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1304,"content":"The address of the Demand Side Buffer Multisig on the Ethereum Mainnet is `0x5e2fEc3a3C4E63A422e45C1BB83EdB3a5aD0543B`.","contentHash":"d760f28baff31af14ddc10999b5bd7016e69cfed05c2acdd8519d550a0fc8a22","addressRefs":["0x5e2fec3a3c4e63a422e45c1bb83edb3a5ad0543b"]},"8e341f8c-be33-49c2-8345-76ecc3e1179c":{"id":"8e341f8c-be33-49c2-8345-76ecc3e1179c","doc_no":"A.2.2.8.1.2.1.4.2","title":"Demand Side Buffer Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1305,"content":"The Demand Side Buffer Multisig has a 2/3 signing requirement.","contentHash":"67f41498f388bf590fae85fa711d8566e987e7873bf62f45d99fe50172b215e9","addressRefs":[]},"af4edd62-8e3c-42d2-bf70-41a31570ab0b":{"id":"af4edd62-8e3c-42d2-bf70-41a31570ab0b","doc_no":"A.2.2.8.1.2.1.4.3","title":"Demand Side Buffer Multisig Signers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1306,"content":"The signers of the Demand Side Buffer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs.","contentHash":"4cba08c71aa99c4675da2d30a0f4410333159e42059f773025e1066493c8cdb6","addressRefs":[]},"f489f6b8-67a9-49bd-ad98-a543757214b8":{"id":"f489f6b8-67a9-49bd-ad98-a543757214b8","doc_no":"A.2.2.8.1.2.1.4.4","title":"Demand Side Buffer Multisig Usage Standards","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1307,"content":"The signers of the Demand Side Buffer Multisig must use the Multisig to disburse Distribution Reward and Integration Boost payments in accordance with the Atlas.","contentHash":"7eee158646fc35d05d9eb34d5c58bd62801f11060a395db7d9c16fb19cc98ce6","addressRefs":[]},"379f5e3c-3ea4-4d82-a8bb-70e8d750e157":{"id":"379f5e3c-3ea4-4d82-a8bb-70e8d750e157","doc_no":"A.2.2.8.1.2.1.4.5","title":"Demand Side Buffer Multisig Modification","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1308,"content":"Operational GovOps Soter Labs can change the signers of the Demand Side Buffer Multisig at any time, so long as there are at least three (3) signers and at least two-thirds of signers are required to execute transactions.","contentHash":"38c615800118ffb5f3a74546a149b009e7c3dfa67c5c515df4a6100471125bcc","addressRefs":[]},"dfc22e9d-139b-498c-a3d0-408503632f77":{"id":"dfc22e9d-139b-498c-a3d0-408503632f77","doc_no":"A.2.2.8.1.2.1.4.6","title":"Demand Side Buffer Auxiliary Accounts","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1309,"content":"Operational GovOps Soter Labs may establish auxiliary accounts on other blockchains to facilitate efficient distribution of Distribution Reward and Integration Boost payments to Integrators operating on those blockchains. Operational GovOps Soter Labs may move funds from the Demand Side Buffer Multisig to auxiliary accounts as necessary to facilitate such payments. Each auxiliary account must conform to the same standards as the Demand Side Buffer Multisig, specifically:\n\n- a minimum of three (3) signers;\n- at least two-thirds of signers are required to execute transactions; and\n- all signers are controlled by Operational GovOps Soter Labs.","contentHash":"3ecba496c9c100c86bc0b24d8f027be3a9f2dc06955bc5b7a4ca5ffdf4c48e89","addressRefs":[]},"32e27a27-7d1e-4acc-9b67-805eaedb7b97":{"id":"32e27a27-7d1e-4acc-9b67-805eaedb7b97","doc_no":"A.2.2.8.1.2.1.4.6.1","title":"List Of Auxiliary Accounts","type":"Active Data Controller","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1310,"content":"The list of auxiliary accounts is defined as Active Data in [A.2.2.8.1.2.1.4.6.1.0.6.1 - Current Auxiliary Accounts](620715c0-6260-4501-9d3f-50ef4f5fc572).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps Soter Labs.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"7d7e411a259ec0cd40da4d0a9b424c5f6dccdf15c9d241cbc76f26e36c78fc86","addressRefs":[]},"620715c0-6260-4501-9d3f-50ef4f5fc572":{"id":"620715c0-6260-4501-9d3f-50ef4f5fc572","doc_no":"A.2.2.8.1.2.1.4.6.1.0.6.1","title":"Current Auxiliary Accounts","type":"Active Data","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1311,"content":"The following auxiliary accounts are currently in use:\n\n- Solana — `7Gf8AqAtmYkkVhQbbJr18RxVUuoGjA8ZEw3Af4NauyaY`","contentHash":"9d9cc103239c9e392eee84a33a0cbbab6ca488b9d7c8a44c9ac07e84425f4247","addressRefs":["7Gf8AqAtmYkkVhQbbJr18RxVUuoGjA8ZEw3Af4NauyaY"]},"8dfabd92-aabc-4605-9ca5-d10f413203dc":{"id":"8dfabd92-aabc-4605-9ca5-d10f413203dc","doc_no":"A.2.2.8.1.2.1.5","title":"Rewards Distribution","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1312,"content":"The documents herein define base elements of the Distribution Reward Primitive related to distribution of Distribution Rewards.","contentHash":"26b989f49290e3e3ac8d9d5cd32064ad2ec031591014b2a880e73a30fb880655","addressRefs":[]},"02d1e35f-0a24-43d9-9406-347eef58a9d1":{"id":"02d1e35f-0a24-43d9-9406-347eef58a9d1","doc_no":"A.2.2.8.1.2.1.5.1","title":"Reward Cadence","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1313,"content":"The Distribution Reward is calculated and distributed on a monthly basis.","contentHash":"059dbaecafe7c24c7938a5948cc2e13ed127d82cbdf645d202545d10b3df07b8","addressRefs":[]},"38cb0bfe-3733-4a11-8b3a-6728df00d08e":{"id":"38cb0bfe-3733-4a11-8b3a-6728df00d08e","doc_no":"A.2.2.8.1.2.1.5.2","title":"Reward Payment","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1314,"content":"The Distribution Reward payment for each month is equal to:\n\n1. the average balance over the month, times\n2. the annual Distribution Reward Fee specified in [A.2.2.8.1.2.1.3 - Distribution Reward Rate](57384c49-e499-4c69-b22c-8e1f1dd34759), divided by\n3. twelve (12).","contentHash":"a2c8e3d168b792e0171dc5e14f754789a6a33fa80a6a569de01c005d3a59ddc0","addressRefs":[]},"935b90bb-a854-4c06-b6ea-48a1cf8fd2f1":{"id":"935b90bb-a854-4c06-b6ea-48a1cf8fd2f1","doc_no":"A.2.2.8.1.2.1.5.3","title":"Treasury Management","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1315,"content":"The documents herein define the treasury management process.","contentHash":"ad659cd5dae218b2312c8d0a905b315b6fe2813c8238625eda210ea7c9864e69","addressRefs":[]},"05fb732b-de55-4886-81a7-7c5d4c13d2d2":{"id":"05fb732b-de55-4886-81a7-7c5d4c13d2d2","doc_no":"A.2.2.8.1.2.1.5.3.1","title":"Near-Term Process","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1316,"content":"In the near term, Operational GovOps calculates the Distribution Reward. The Distribution Reward is paid from the Demand Side Buffer (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)) within seven (7) days of the end of every month.","contentHash":"63b5e393c609b56043ce6aedbdf2c630de3324e11bceaf2db6f33d9243ea3324","addressRefs":[]},"07953e87-c201-4ad5-9c1e-b32efc5fba94":{"id":"07953e87-c201-4ad5-9c1e-b32efc5fba94","doc_no":"A.2.2.8.1.2.1.5.3.2","title":"Long Term Process","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1317,"content":"In the long term, Operational GovOps calculates the Distribution Reward for each month. Operational GovOps then pays the Distribution Reward recipient from its Buffer. Later Sky Core reimburses the Operational Agent Buffer for the amount paid as part of the Settlement Cycle. This minimizes the role of Sky Core in Distribution Reward payments and emphasizes the primary role of the Operational Executor Agent, acting through Operational GovOps, in implementing the Sky Primitives. The process is specified in further detail in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701).","contentHash":"7b6a76385ee09e5e7cac2e18593992e088782a2ea9bda72a673a26fcce5f15cc","addressRefs":[]},"1b5edf68-0825-449a-a404-34141a1892cc":{"id":"1b5edf68-0825-449a-a404-34141a1892cc","doc_no":"A.2.2.8.1.2.1.5.4","title":"Payment Errors","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1318,"content":"If it is discovered that previous Distribution Reward calculations were made erroneously, underpayments are resolved retroactively. In cases where an Integrator was overpaid, the Prime Agent associated with the Integrator must reimburse Sky the overpayment amount and can use future Distribution Rewards that the Integrator earns to reimburse itself.","contentHash":"f51d0071e34a47b4802bccca2a0b6c53aede5416a62904b3f47a2061b30039c1","addressRefs":[]},"f3952cc5-cde2-46b9-b575-034dda83570b":{"id":"f3952cc5-cde2-46b9-b575-034dda83570b","doc_no":"A.2.2.8.1.2.1.6","title":"Current And Onboarding Integrators","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1319,"content":"The documents herein specify current and onboarding Integrators.","contentHash":"043c2c08fe931bb512e9897404a5086c5b13fd6692c99beb12be713fc4c01708","addressRefs":[]},"883f1b52-a6d2-417b-bb24-12917de83b53":{"id":"883f1b52-a6d2-417b-bb24-12917de83b53","doc_no":"A.2.2.8.1.2.1.6.1","title":"Current Integrators","type":"Active Data Controller","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1320,"content":"Current Integrators are Integrators who have a Reward Code specified in an `Active` Instance of the Distribution Reward Primitive. The list of Current Integrators is defined as Active Data in [A.2.2.8.1.2.1.6.1.0.6.1 - List Of Current Integrators](efbe7903-a76e-40f0-a440-56e463283157).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"58ca7b4928b6c4f17b1491973c9efa96b076cea32f632fe60342c11dd6ae199d","addressRefs":[]},"efbe7903-a76e-40f0-a440-56e463283157":{"id":"efbe7903-a76e-40f0-a440-56e463283157","doc_no":"A.2.2.8.1.2.1.6.1.0.6.1","title":"List Of Current Integrators","type":"Active Data","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1321,"content":"The current Active Integrators are:","contentHash":"269bb03917c8902340d526d26d1e2df11dff7b66597507790a92049fe8b6883b","addressRefs":[]},"9a7f47ae-760f-44b5-9b5f-dd4fef86e1cc":{"id":"9a7f47ae-760f-44b5-9b5f-dd4fef86e1cc","doc_no":"A.2.2.8.1.2.1.6.2","title":"Onboarding Integrators","type":"Active Data Controller","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1322,"content":"Onboarding Integrators are actors whose application to the Integrator Program has been approved, but are specified in an Instance of the Distribution Reward Primitive or Integration Boost Primitive that is \"Pending\", or is not `Active` yet. The list of Onboarding Integrators is defined as Active Data in [A.2.2.8.1.2.1.6.2.0.6.1 - List Of Onboarding Integrators](eb644108-94fc-430f-ae5a-e3294b9dd9be).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"936228ab6d7ba285f89f91dc8fd625cc6bc95323ab11657bb53ff92112631bcf","addressRefs":[]},"eb644108-94fc-430f-ae5a-e3294b9dd9be":{"id":"eb644108-94fc-430f-ae5a-e3294b9dd9be","doc_no":"A.2.2.8.1.2.1.6.2.0.6.1","title":"List Of Onboarding Integrators","type":"Active Data","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1323,"content":"The current Onboarding Integrators are:","contentHash":"a171547de1f072bbe3b28fe552feb6a361779c97d36241d06606758dc3c7feed","addressRefs":[]},"fd551536-2177-4e78-87a1-c2528ff2fcaf":{"id":"fd551536-2177-4e78-87a1-c2528ff2fcaf","doc_no":"A.2.2.8.1.2.1.7","title":"Distribution Reward Reimbursement","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1324,"content":"The documents herein specify the Distribution Reward reimbursement.","contentHash":"532a7847f400a41b804f5098f32e41d2fe4bc431d460d1487c995f2d24423bb3","addressRefs":[]},"2c0eb02c-144e-4326-b5ec-85805653f0b7":{"id":"2c0eb02c-144e-4326-b5ec-85805653f0b7","doc_no":"A.2.2.8.1.2.1.7.1","title":"Sky Core Distribution Reward Reimbursement","type":"Active Data Controller","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1325,"content":"The Distribution Reward reimbursement payments are defined as Active Data in [A.2.2.8.1.2.1.7.1.0.6.1 - Sky Core Distribution Reward Reimbursement Amounts](169eb312-ed63-4a83-9f5d-43b621c0705e).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Core GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"9707049330562cffc6fa9c9d73a77070c289d8d1525e1d620bcc01f868f6b4e3","addressRefs":[]},"169eb312-ed63-4a83-9f5d-43b621c0705e":{"id":"169eb312-ed63-4a83-9f5d-43b621c0705e","doc_no":"A.2.2.8.1.2.1.7.1.0.6.1","title":"Sky Core Distribution Reward Reimbursement Amounts","type":"Active Data","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1326,"content":"The current Sky Core Distribution Reward Reimbursement Amounts are:","contentHash":"e2bea9a9d03c3f98fba52408512b138428f9d0c6fe73f1fef022e2d71c8b1977","addressRefs":[]},"49513ac9-43d6-4766-8a51-195e221de3f2":{"id":"49513ac9-43d6-4766-8a51-195e221de3f2","doc_no":"A.2.2.8.1.2.2","title":"Global Activation","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1327,"content":"An Agent who intends to deploy the Distribution Reward Primitive must first Globally Activate it.","contentHash":"03fe6c90e9aa461a55d825cb54e9145ffbd9bd4bbaa0ee21aa63daa8635a158e","addressRefs":[]},"776d926e-70d0-4771-bd60-d3fcef0a7ea3":{"id":"776d926e-70d0-4771-bd60-d3fcef0a7ea3","doc_no":"A.2.2.8.1.2.2.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1328,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"090b3f8e-78a8-4df1-8db9-b9a6a2e23a33":{"id":"090b3f8e-78a8-4df1-8db9-b9a6a2e23a33","doc_no":"A.2.2.8.1.2.2.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1329,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"b4271bcd-12f5-4a14-bf5a-c77c9afd3629":{"id":"b4271bcd-12f5-4a14-bf5a-c77c9afd3629","doc_no":"A.2.2.8.1.2.2.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1330,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"e2766ea3-ddf9-434d-a6ab-6e13ca23e164":{"id":"e2766ea3-ddf9-434d-a6ab-6e13ca23e164","doc_no":"A.2.2.8.1.2.2.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1331,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"4e4476d8-0b98-4a2a-a3af-e879af06e01c":{"id":"4e4476d8-0b98-4a2a-a3af-e879af06e01c","doc_no":"A.2.2.8.1.2.2.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1332,"content":"See [A.2.2.1.2.4.1 - Agent Launch And Sequence of Primitive Global Activation](2f5ff5c8-bcd1-44a4-ba56-2075ac8e9c61) for constraints on when an Agent can Globally Activate this Primitive.","contentHash":"38b8b8ee07622dbaeb74a66be3e21d009f1328c4e3268f56aae1d3d8be26e0e7","addressRefs":[]},"89d26f82-b662-41df-8935-44aa7e93be6d":{"id":"89d26f82-b662-41df-8935-44aa7e93be6d","doc_no":"A.2.2.8.1.2.2.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1333,"content":"The Prime Agent uses the Powerhouse interface to Globally Activate (toggle on) the Distribution Reward Primitive.","contentHash":"57065d2db5123cfdc67e116e812b0472674261e93e507c9fae6b7719d498af89","addressRefs":[]},"108c6d9c-8ecf-48bf-bc8b-365f8cf65c0c":{"id":"108c6d9c-8ecf-48bf-bc8b-365f8cf65c0c","doc_no":"A.2.2.8.1.2.2.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1334,"content":"The following inputs must be submitted into the Primitive using the Powerhouse interface:\n\n- **Create** `Primitive Hub Document`\n    - Updated Field: Global Activation Status\n        - New Value: set to `Activated`","contentHash":"028e65933fc762a38c3e88196df72574994cafe6b4116ea8f41c221022688f64","addressRefs":[]},"faf79404-fe20-406d-a0a2-f3ac9e8592ab":{"id":"faf79404-fe20-406d-a0a2-f3ac9e8592ab","doc_no":"A.2.2.8.1.2.2.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1335,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"74003afb-d603-4898-bd2a-bcf988e8c039":{"id":"74003afb-d603-4898-bd2a-bcf988e8c039","doc_no":"A.2.2.8.1.2.2.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1336,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"6af6cd24-9513-42a7-be91-3f16845ebadf":{"id":"6af6cd24-9513-42a7-be91-3f16845ebadf","doc_no":"A.2.2.8.1.2.2.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1337,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified in [A.2.2.8.1.2.2.3 - Required Primitive Inputs](108c6d9c-8ecf-48bf-bc8b-365f8cf65c0c) fully complete the Process.","contentHash":"a97098d5e4fa1af2daa7f5e1b771179c3e6f22fc4c44177ca607399af642786a","addressRefs":[]},"ad3a3f6b-7bc3-4e5f-b1c3-225b5b4cbe15":{"id":"ad3a3f6b-7bc3-4e5f-b1c3-225b5b4cbe15","doc_no":"A.2.2.8.1.2.3","title":"Instance Invocation Protocol","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1338,"content":"After fulfilling the requirements for Global Activation, an Agent can Invoke its first Instance of the Distribution Reward Primitive by following the sequential process specified herein. Subsequent Invocations of the Primitive must also adhere to the same requirements defined below.","contentHash":"ee71a37d5fd7da465b2caf80f966d9ad2d389d58127b8a48d6552dc74c45fb69","addressRefs":[]},"f07b1cca-5db2-4b1b-b760-ea738d2776f3":{"id":"f07b1cca-5db2-4b1b-b760-ea738d2776f3","doc_no":"A.2.2.8.1.2.3.1","title":"Process Definition For Initial Opportunity Identification And Planning","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1339,"content":"The documents herein specify the process definition for initial opportunity identification and planning.","contentHash":"2d1521b283454013e45a8c02b5572101ce9a14363ffa87c3a7abcbb124eca2fb","addressRefs":[]},"005beba7-131f-43f9-93fc-29463905ef69":{"id":"005beba7-131f-43f9-93fc-29463905ef69","doc_no":"A.2.2.8.1.2.3.1.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1340,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"222fc95e-eead-49ec-9d55-730b2b3cb0a0":{"id":"222fc95e-eead-49ec-9d55-730b2b3cb0a0","doc_no":"A.2.2.8.1.2.3.1.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1341,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"dec5be6c-3123-4808-93e9-0486fc8e9572":{"id":"dec5be6c-3123-4808-93e9-0486fc8e9572","doc_no":"A.2.2.8.1.2.3.1.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1342,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"34497a9f-b623-45b3-a2f2-dc74a06c6700":{"id":"34497a9f-b623-45b3-a2f2-dc74a06c6700","doc_no":"A.2.2.8.1.2.3.1.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1343,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"c89c3cd1-20c4-461f-a220-1754d97e2049":{"id":"c89c3cd1-20c4-461f-a220-1754d97e2049","doc_no":"A.2.2.8.1.2.3.1.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1344,"content":"This process is dependent on a Prime Agent Globally Activating the Distribution Reward Primitive pursuant to [A.2.2.8.1.2.2 - Global Activation](49513ac9-43d6-4766-8a51-195e221de3f2).","contentHash":"fa1689097834add8298c568bbf3dde8fc407767ee7863e33741d45043d81853e","addressRefs":[]},"75ff9b92-47e1-454f-864b-b74742df918e":{"id":"75ff9b92-47e1-454f-864b-b74742df918e","doc_no":"A.2.2.8.1.2.3.1.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1345,"content":"The process flow is defined herein.\n\n- The Prime Agent identifies an opportunity to drive USDS adoption through a Distribution Reward to either 1) reward an existing Integrator for driving USDS adoption or 2) incentivize a new actor to onboard as an Integrator to drive USDS adoption.\n- Existing Integrators\n    - The Prime Agent and the third party, if applicable, develop a plan to track USDS utilization attributable to the actor using either on-chain or off-chain data.\n- Prospective Integrators\n    - Near Term process:\n        - The Prospective Integrator must first apply to the Integrator program and be approved by Operational GovOps per [A.2.2.8.1.2.1.1.2.1 - Near Term Process](7fe5dbb2-a07d-4ef9-94de-f54a2d568c57). Post approval, Operational GovOps issues a Reward Code to the Integrator.\n        - The Prime Agent and the third party develop a plan to track USDS utilization attributable to the actor using either on-chain or off-chain data.\n    - Long Term process:\n        - The Prospective Integrator must first apply to the Integrator program and be approved by Operational GovOps pursuant to [A.2.2.8.1.2.1.1.2.2 - Long Term Process](6283379c-d871-40a9-a915-d716d7df5642). Post approval, Operational GovOps issues a Reward Code to the Integrator.\n        - The Prime Agent develops a plan to track USDS utilization attributable to it using either on-chain or off-chain data. Where applicable, the plan should include how the Prime Agent will support the prospective Integrator in including the Reward Code in their on-chain infrastructure.\n- The Prime Agent may also be (or choose to be) an Integrator itself and deploy a Reward Code on its frontend to earn the Distribution Reward.\n    - Near Term process:\n        - If the Prime Agent is not already an approved Integrator, it must apply to the Program and be approved by Operational GovOps. Post approval, Operational GovOps issues a Reward Code to the Prime Agent.\n        - The Prime Agent develops a plan to track USDS utilization attributable to it using either on-chain or off-chain data.\n    - Long Term process:\n        - The Prime Agent must first apply to the Integrator program and be approved by Operational GovOps pursuant to [A.2.2.8.1.2.1.1.2.2 - Long Term Process](6283379c-d871-40a9-a915-d716d7df5642). Post approval, Operational GovOps issues a Reward Code to the Prime Agent.\n        - The Prime Agent develops a plan to track USDS utilization attributable to it using either on-chain or off-chain data.","contentHash":"75c0aab2e3695b0f776623b893f0e5141020deb1f42c16e4b9ab8e0df8248964","addressRefs":[]},"4d5482ad-7944-4073-8fbe-b9dbcd1a27a3":{"id":"4d5482ad-7944-4073-8fbe-b9dbcd1a27a3","doc_no":"A.2.2.8.1.2.3.1.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1346,"content":"The required Primitive Inputs for this process are defined herein and organized in sequential stages.\n\n- Drafting of Initial Planning Document\n    - Create `Initial Planning Document`\n        - Updated fields\n            - `Status`\n                - New value: set to `Drafting`\n            - `Integrator`\n                - New Value: set to Integrator Name\n            - `Reward Code`\n                - New Value: set to Reward Code\n            - `Tracking Methodology`\n                - New value: populate with details for tracking utilization\n            - `Custom Instance Parameters`\n                - New Value: populate with details for any custom parameters\n        - Responsible Party: Prime Agent Team\n        - Trigger - Required Output: After Prime Agent's `Initial planning document` Status is set to `Drafting`\n- Initial Planning Document Triggered For GovOps review\n    - Edit `Initial Planning Document`\n        - Updated fields\n            - `Tracking Methodology`\n                - New value: updated content, as applicable\n            - `Status`\n                - New value: set to `Ready for GovOps Review`\n        - Responsible party: Prime Agent\n        - Trigger - Required Output: After Prime Agent's `Initial planning document` Status is set to `Ready for GovOps review`.","contentHash":"ba542c5bc107e59d59c243855865f8a151498835e623f0a72b8c59d6217383cc","addressRefs":[]},"1ad17e84-8bde-4669-9967-9f67d1d3c603":{"id":"1ad17e84-8bde-4669-9967-9f67d1d3c603","doc_no":"A.2.2.8.1.2.3.1.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1347,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"bab05cb6-532f-41e0-8fba-203b1b92294b":{"id":"bab05cb6-532f-41e0-8fba-203b1b92294b","doc_no":"A.2.2.8.1.2.3.1.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1348,"content":"The Sky Core Atlas is updated pursuant to the following requirements.","contentHash":"c58ab1ed78086e3be3121b7112775f54d8e4e704a988321b88a748c905e29ca9","addressRefs":[]},"6857396f-f0ce-4471-8e48-ed5f06b86830":{"id":"6857396f-f0ce-4471-8e48-ed5f06b86830","doc_no":"A.2.2.8.1.2.3.1.4.1.1","title":"Onboarding Integrators Active Data Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1349,"content":"[A.2.2.8.1.2.1.6.2.0.6.1 - List Of Onboarding Integrators](eb644108-94fc-430f-ae5a-e3294b9dd9be) is updated as follows:\n\n- Updated fields\n    - `Onboarding Integrators/Integrator Name`\n        - New value: set to the name of the Integrator\n    - `Integrator Name/Reward Code`\n        - New value: set to Reward Code\n- Responsible Party: Operational GovOps","contentHash":"0df8777dcf5cf27c9b1edc20fdbf5ff5c32c817c81f2820ded8c2374f259a692","addressRefs":[]},"11161730-6568-445f-a250-ba5c67857390":{"id":"11161730-6568-445f-a250-ba5c67857390","doc_no":"A.2.2.8.1.2.3.1.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1350,"content":"The Agent Artifact is updated pursuant to the following requirements. Each Output \"set\" is triggered following the completion of its respective Input stage, defined in [A.2.2.8.1.2.3.1.3 - Required Primitive Inputs](4d5482ad-7944-4073-8fbe-b9dbcd1a27a3).\n\n- After Prime Agent's `Initial planning document` Status is set to `Drafting`\n    - Create `Instance Configuration` Document for prospective Primitive Instance. The Instance Configuration Document contains a `Data Repository.`\n        - Instance Status: (automatically inherits from `Primitive Hub Document`)\n    - Edit `Primitive Hub Document/In Progress Invocations Directory/Instance Name`\n        - Updated fields:\n            - Invocation Status:\n                - New value: set to `Planning`\n            - Instance Configuration Document Location\n                - New value: link to `Instance Configuration Document` (created at Create `Instance Configuration` Document for prospective Primitive Instance. The Instance Configuration Document contains a `Data Repository.`)\n    - Responsible party: Operational GovOps [automated]\n- After Prime Agent's `Initial planning document` Status is set to `Ready for GovOps review`.\n    - Edit `Primitive Hub Document/In Progress Invocations/Instance Name`\n        - Updated fields:\n            - Invocation Status:\n                - New value: set to `Pending GovOps review`\n        - Responsible party: Operational GovOps [automated]\n        - Trigger - Process: [A.2.2.8.1.2.3.2 - Process Definition For Operational GovOps Review](5fd265ef-17f0-4400-b06c-a6ce9fa87636).","contentHash":"007531085973a2c145bd53523367d826da18f21e4de1539542a94137c9656aa1","addressRefs":[]},"5fd265ef-17f0-4400-b06c-a6ce9fa87636":{"id":"5fd265ef-17f0-4400-b06c-a6ce9fa87636","doc_no":"A.2.2.8.1.2.3.2","title":"Process Definition For Operational GovOps Review","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1351,"content":"The documents herein define the process for Operational GovOps Review for an Invocation of the Distribution Reward Primitive.","contentHash":"b88a716b8e8fea52e87a43ef77cd8ae5f45b19168a9e14a35112a48c329d0a97","addressRefs":[]},"da868510-121f-442a-982e-8ab2d2149a25":{"id":"da868510-121f-442a-982e-8ab2d2149a25","doc_no":"A.2.2.8.1.2.3.2.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1352,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"f89a41b2-973b-4eca-b463-e0e77bc719ef":{"id":"f89a41b2-973b-4eca-b463-e0e77bc719ef","doc_no":"A.2.2.8.1.2.3.2.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1353,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"d1d3de53-ad5a-40cb-9155-58db67a6340c":{"id":"d1d3de53-ad5a-40cb-9155-58db67a6340c","doc_no":"A.2.2.8.1.2.3.2.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1354,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"fd211726-1576-4b0a-8489-6e76e83ee92b":{"id":"fd211726-1576-4b0a-8489-6e76e83ee92b","doc_no":"A.2.2.8.1.2.3.2.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1355,"content":"This process is triggered by the Artifact Document Update specified at Edit `Primitive Hub Document/In Progress Invocations/Instance Name`.","contentHash":"1a4676e6a4f705688915fee1e3f4cf26ed2c56a2f956bc9cdb72d1592e7c1698","addressRefs":[]},"abb8f0ef-eae6-4af5-8a70-20630a33e7c9":{"id":"abb8f0ef-eae6-4af5-8a70-20630a33e7c9","doc_no":"A.2.2.8.1.2.3.2.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1356,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"ef743f33-32b0-4a51-af00-a9e35c2e1017":{"id":"ef743f33-32b0-4a51-af00-a9e35c2e1017","doc_no":"A.2.2.8.1.2.3.2.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1357,"content":"The process flow is defined herein:\n\n- Operational GovOps reviews the `Initial Planning Document` to ensure:\n    - Operational GovOps has the ability to operationalize the proposed tracking mechanism, and\n    - The proposed tracking mechanism accurately reflects USDS usage attributable to the actor and there is no possibility that rewards could be \"double counted\" (i.e. multiple actors being paid for the same USDS balance).\n- Operational GovOps submits its feedback into the `Operational GovOps Review Document` (created at Create `Operational GovOps Review Document`.) along with suggested changes, if any.\n- The Prime Agent incorporates feedback from Operational GovOps and edits its `Initial Planning Document` as needed.","contentHash":"cc9c9ac08247133d31693ffc09661d0b859a3158c94c298b12369cc018839b7e","addressRefs":[]},"9c4653fa-6afe-4567-9e85-54c0a84b9311":{"id":"9c4653fa-6afe-4567-9e85-54c0a84b9311","doc_no":"A.2.2.8.1.2.3.2.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1358,"content":"The following inputs must be submitted into the Primitive using the Powerhouse interface.\n\n- Create `Operational GovOps Review Document`.\n    - Updated fields\n        - `Initial Planning Document`\n            - New Value: automatically links to respective Document\n        - `Feedback Summary`\n            - New Value: GovOps populates with its review commentary and suggested changes that are agreed to by Agent and GovOps, if any.\n        - Responsible party: Operational GovOps.","contentHash":"fd7329e054b91a1e88b88d9621863a0596e2927120fce5e6e193543c61666549","addressRefs":[]},"a7a3e2d3-54bd-4c0f-a222-505b5e14a5e4":{"id":"a7a3e2d3-54bd-4c0f-a222-505b5e14a5e4","doc_no":"A.2.2.8.1.2.3.2.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1359,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"9a94a573-8a51-4b04-9704-d84dc0623bb8":{"id":"9a94a573-8a51-4b04-9704-d84dc0623bb8","doc_no":"A.2.2.8.1.2.3.2.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1360,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"ec050d61-1d48-453a-ac13-4cea23c68292":{"id":"ec050d61-1d48-453a-ac13-4cea23c68292","doc_no":"A.2.2.8.1.2.3.2.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1361,"content":"The Agent Artifact is updated pursuant to the following requirements.","contentHash":"e5b276f7f31f8804c17a356b8b4dfabce1aa09385e842e4e02f4ae9cee444044","addressRefs":[]},"66a07769-2de9-4b15-a439-4fc84b6a1575":{"id":"66a07769-2de9-4b15-a439-4fc84b6a1575","doc_no":"A.2.2.8.1.2.3.2.4.2.1","title":"Initial Planning Document Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1362,"content":"The Document is updated as follows.\n\n- Updated fields\n    - `Tracking Methodology`\n        - New Value: as applicable, update to reflect any changes agreed to between the Prime Agent and Operational GovOps\n    - Responsible Party: Operational GovOps","contentHash":"3c4be375c67ed9809c8c192f50b8a7eaf4c0b5bb1a34833fc19019201c54ea5f","addressRefs":[]},"6f457b50-a98c-4516-9b37-932603a59627":{"id":"6f457b50-a98c-4516-9b37-932603a59627","doc_no":"A.2.2.8.1.2.3.2.4.2.2","title":"Primitive Hub Document/In Progress Invocations Directory/Instance Name Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1363,"content":"The Document is updated as follows.\n\n- Updated fields\n    - Invocation Status\n        - New value: set to `Proposal drafting in progress`\n- Responsible Party: Operational GovOps [automated]\n- Triggers: [A.2.2.8.1.2.3.3 - Process Definition For Artifact Update Draft](240e0e2c-64b6-4290-aa23-ec19eb2f6e59)","contentHash":"151ac748318f12842915537b182a2622f97f94841280e49a9b8d195d3aeb3c93","addressRefs":[]},"240e0e2c-64b6-4290-aa23-ec19eb2f6e59":{"id":"240e0e2c-64b6-4290-aa23-ec19eb2f6e59","doc_no":"A.2.2.8.1.2.3.3","title":"Process Definition For Artifact Update Draft","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1364,"content":"The documents herein define the process for preparing the Artifact Update Draft for an Invocation of the Distribution Reward Primitive.","contentHash":"3555da0499950994c35c961702aebb83e99a80eee8acbe2de377eab30ce4b0fb","addressRefs":[]},"9add3334-5779-4d23-bf5f-6c25cf9fcf9a":{"id":"9add3334-5779-4d23-bf5f-6c25cf9fcf9a","doc_no":"A.2.2.8.1.2.3.3.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1365,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"bdc8d447-a140-4580-b439-b3ac8deb5aac":{"id":"bdc8d447-a140-4580-b439-b3ac8deb5aac","doc_no":"A.2.2.8.1.2.3.3.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1366,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"e379a9d8-c0d2-4aa6-ab62-41a6767dc490":{"id":"e379a9d8-c0d2-4aa6-ab62-41a6767dc490","doc_no":"A.2.2.8.1.2.3.3.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1367,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"94d06bae-9bc9-4e8f-a38d-4b879466873b":{"id":"94d06bae-9bc9-4e8f-a38d-4b879466873b","doc_no":"A.2.2.8.1.2.3.3.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1368,"content":"This process is triggered by the Document Update specified at [A.2.2.8.1.2.3.3.4.2.1 - Primitive Hub/In Progress Invocations Directory/Instance Name Update](b37c4266-2dd9-4cce-8b6b-cc35af2b94d9).","contentHash":"53603448f4d327856a2a53c7c2c161b885a49495a7a08d05fae0ff2b3568c0f4","addressRefs":[]},"a6f968d6-0e8c-4962-b982-43beffc602db":{"id":"a6f968d6-0e8c-4962-b982-43beffc602db","doc_no":"A.2.2.8.1.2.3.3.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1369,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"ccb71126-1333-453c-aaeb-4359a8013f32":{"id":"ccb71126-1333-453c-aaeb-4359a8013f32","doc_no":"A.2.2.8.1.2.3.3.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1370,"content":"The process flow is defined herein:\n\n- The Prime Agent creates the `Artifact Edit Draft` Document and works to finalize its draft of the Artifact Edit per discussions with Operational GovOps.\n- When draft is finalized, the Prime Agent triggers the creation of the `Artifact Edit Proposal`, which inherits content from the finalized `Artifact Edit Draft` Document.\n- The Prime Agent submits the `Artifact Edit Proposal` Document to the Powerhouse system.","contentHash":"73c12b2d232ee71cf4525448ef7b4d83ad9709bd922f8c8bc914fe022abdee38","addressRefs":[]},"6f4e7971-1813-4ff6-9e4f-5953c8cb54af":{"id":"6f4e7971-1813-4ff6-9e4f-5953c8cb54af","doc_no":"A.2.2.8.1.2.3.3.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1371,"content":"The required Primitive Inputs for this process are defined herein and implemented in sequential stages.\n\n- Agent creates `Artifact Edit Draft` document; drafting in progress:\n    - Edit `Artifact Edit Draft`\n        - Updated fields\n            - Status\n                - New value: set to `In Progress`\n            - Content\n                - New value: populate with drafted content\n- Agent finalizes `Artifact Edit Draft`\n    - Edit `Artifact Edit Draft`\n        - Updated fields\n            - Status\n                - New value: set to `Draft Finalized`\n- Powerhouse System Creates `Artifact Edit Proposal` Document\n    - Updated fields\n        - Content\n            - New value: Inherits data from Artifact Edit Draft content field.\n    - Responsible party: Operational GovOps [if not automated]\n- Agent submits `Artifact Edit Proposal` Document to Powerhouse system\n    - Updated fields\n        - Status:\n            - New value: set to `Pending Facilitator Review`\n    - Responsible party: Agent","contentHash":"b23db85d32796247ed3a1a54b3c175a315ad0a19f631da28d70a5e5e75576a69","addressRefs":[]},"c7ed27ce-d296-4a44-83c3-96bb1ed8976d":{"id":"c7ed27ce-d296-4a44-83c3-96bb1ed8976d","doc_no":"A.2.2.8.1.2.3.3.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1372,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"264273c8-7805-45ec-aa87-ebd08faf763d":{"id":"264273c8-7805-45ec-aa87-ebd08faf763d","doc_no":"A.2.2.8.1.2.3.3.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1373,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"a3294ae2-3fd7-446a-a628-dbddd487931e":{"id":"a3294ae2-3fd7-446a-a628-dbddd487931e","doc_no":"A.2.2.8.1.2.3.3.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1374,"content":"The Agent Artifact documents specified herein are updated as the output of this process.","contentHash":"089da35aa8b5594f8d611ad8991e3ce92e5b986a007dac62109b22911a5a5c15","addressRefs":[]},"b37c4266-2dd9-4cce-8b6b-cc35af2b94d9":{"id":"b37c4266-2dd9-4cce-8b6b-cc35af2b94d9","doc_no":"A.2.2.8.1.2.3.3.4.2.1","title":"Primitive Hub/In Progress Invocations Directory/Instance Name Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1375,"content":"The Document is updated as follows:\n\n- Updated fields\n    - Invocation Status\n        - New value: `Proposal Pending Facilitator Review`\n- Responsible Party: Operational GovOps\n- Triggers: [A.2.2.8.1.2.3.4 - Process Definition For Operational Facilitator Review](fd9aac63-00a0-4fc5-ad7c-8bb131322bd7).","contentHash":"bc0fcc64eb1452ef8cba1ca1c3653dcadc7dce03d0aa908383b5ba7c0616b085","addressRefs":[]},"fd9aac63-00a0-4fc5-ad7c-8bb131322bd7":{"id":"fd9aac63-00a0-4fc5-ad7c-8bb131322bd7","doc_no":"A.2.2.8.1.2.3.4","title":"Process Definition For Operational Facilitator Review","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1376,"content":"The documents herein define the process for Operational Facilitator Review for an Invocation of the Distribution Reward Primitive.","contentHash":"1c7294ba4c1e5c9ca8da6eea3117fc7ff4c5e7a862dd7b02f4ea0a5653b1501f","addressRefs":[]},"4e87663b-619e-46b6-a672-9bc81d11f4e7":{"id":"4e87663b-619e-46b6-a672-9bc81d11f4e7","doc_no":"A.2.2.8.1.2.3.4.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1377,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"48a12682-0218-4851-8a05-731ae7823b7b":{"id":"48a12682-0218-4851-8a05-731ae7823b7b","doc_no":"A.2.2.8.1.2.3.4.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1378,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"296a23ca-988b-4516-aa78-230ed17b0bbb":{"id":"296a23ca-988b-4516-aa78-230ed17b0bbb","doc_no":"A.2.2.8.1.2.3.4.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1379,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"bee5a2d9-1e98-4918-a77d-3e3607b51f0f":{"id":"bee5a2d9-1e98-4918-a77d-3e3607b51f0f","doc_no":"A.2.2.8.1.2.3.4.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1380,"content":"This process is triggered by the Document Update specified at [A.2.2.8.1.2.3.3.4.2.1 - Primitive Hub/In Progress Invocations Directory/Instance Name Update](b37c4266-2dd9-4cce-8b6b-cc35af2b94d9).","contentHash":"53603448f4d327856a2a53c7c2c161b885a49495a7a08d05fae0ff2b3568c0f4","addressRefs":[]},"967572c4-ba29-4a98-ae05-e3698457d440":{"id":"967572c4-ba29-4a98-ae05-e3698457d440","doc_no":"A.2.2.8.1.2.3.4.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1381,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"67dce065-9fed-4c23-abf5-881371792796":{"id":"67dce065-9fed-4c23-abf5-881371792796","doc_no":"A.2.2.8.1.2.3.4.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1382,"content":"The process flow is defined herein.\n\n- The Operational Facilitator reviews the `Artifact Edit Proposal` to ensure alignment with the Sky Core Atlas and the Agent Artifact.\n- Where the Proposal is determined to be aligned, the Operational Facilitator updates the `Artifact Edit Proposal` Document to reflect their approval and commentary, if applicable.\n- Where the Proposal is determined to be misaligned, the Operational Facilitator updates the `Artifact Edit Proposal` document to reflect their rejection and commentary. Commentary is required where the Operational Facilitator rejects the proposal for misalignment.","contentHash":"db3a209f68bbca7ff297658e5f1843869a2aae2583a92efa474090d6ba85cf90","addressRefs":[]},"967f54c6-9a51-4225-a8fd-e366f7a3d91e":{"id":"967f54c6-9a51-4225-a8fd-e366f7a3d91e","doc_no":"A.2.2.8.1.2.3.4.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1383,"content":"The required Primitive Inputs to this process are defined herein and organized as two mutually exclusive pathways. Once the Review outcome is determined by the Facilitator, the corresponding Pathway is followed to the exclusion of the other.\n\n- Operational Facilitator Approves Proposal\n    - Edit `Artifact Edit Proposal`\n        - Updated fields\n            - `Operational Facilitator Review/Review Decision`\n                - New value: set to `Approved`\n            - `Commentary`\n                - New value (optional): populate with reasoning for Approval\n            - `Status`\n                - New value: set to `Proposal Approved by Facilitator` [automated]\n        - Responsible party: Operational Facilitator\n        - Trigger-Process: [A.2.2.8.1.2.3.5 - Process Definition For Offchain Vote](3170b9a1-d074-4cbd-bb81-ae1661bc0ed8)\n- Operational Facilitator Rejects proposal\n    - Edit `Artifact Edit Proposal`\n        - Updated fields\n            - `Operational Facilitator Review/Review Decision`\n                - New value: set to `Rejected`\n            - `Commentary`\n                - New value (required): populate with reasoning for Rejection\n            - `Status`\n                - New value: set to `Proposal Rejected By Facilitator` [automated]\n        - Responsible party: Operational Facilitator","contentHash":"f778df6f9b2c1a1a7b4f0c3da9a04842231291728bf952e5403f058c5b87428e","addressRefs":[]},"b63e78d1-112d-4d48-a647-a1e3fc2f54a5":{"id":"b63e78d1-112d-4d48-a647-a1e3fc2f54a5","doc_no":"A.2.2.8.1.2.3.4.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1384,"content":"The documents herein specify the required outputs from this process, if any.","contentHash":"c62ae4f853fc59e2c7bb7f374d52024c16f05e870ca07fd3eb1e1f9f5521cd67","addressRefs":[]},"dfdf873a-c24a-4856-a3e9-717ea09dd9bb":{"id":"dfdf873a-c24a-4856-a3e9-717ea09dd9bb","doc_no":"A.2.2.8.1.2.3.4.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1385,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"9cb3ab72-37f5-4501-8661-a204d0747dd8":{"id":"9cb3ab72-37f5-4501-8661-a204d0747dd8","doc_no":"A.2.2.8.1.2.3.4.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1386,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified in [A.2.2.8.1.2.3.4.3 - Required Primitive Inputs](967f54c6-9a51-4225-a8fd-e366f7a3d91e) fully complete the Process.","contentHash":"56ae174dc92c1a6ce44d05e1740d917e8b85da0a8a7715087b48000d00d97f7a","addressRefs":[]},"3170b9a1-d074-4cbd-bb81-ae1661bc0ed8":{"id":"3170b9a1-d074-4cbd-bb81-ae1661bc0ed8","doc_no":"A.2.2.8.1.2.3.5","title":"Process Definition For Offchain Vote","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1387,"content":"The documents herein define the process for an Offchain Vote for an Invocation of the Distribution Reward Primitive.","contentHash":"ddcaa097d675a3fa069ed513e7ea7f5752cfaa79bf40cb2f8259f9c2778516b6","addressRefs":[]},"3b38ec56-64c1-4093-82f0-fd5a162d549c":{"id":"3b38ec56-64c1-4093-82f0-fd5a162d549c","doc_no":"A.2.2.8.1.2.3.5.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1388,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"c743c744-a699-4236-b6d9-80563f789421":{"id":"c743c744-a699-4236-b6d9-80563f789421","doc_no":"A.2.2.8.1.2.3.5.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1389,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"51f50be4-00f4-4023-8d43-dff42e8c7571":{"id":"51f50be4-00f4-4023-8d43-dff42e8c7571","doc_no":"A.2.2.8.1.2.3.5.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1390,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"b43edb36-1255-4e9d-92e2-9e4435c7bb2f":{"id":"b43edb36-1255-4e9d-92e2-9e4435c7bb2f","doc_no":"A.2.2.8.1.2.3.5.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1391,"content":"This process is triggered by the Artifact Update specified at Operational Facilitator Approves Proposal.","contentHash":"cb46a368638f4eec32a3028670bb48f9b1cb18fe594b870bb1ac055e9b523fbf","addressRefs":[]},"174e41b1-0e93-491c-8da1-50c0845947c3":{"id":"174e41b1-0e93-491c-8da1-50c0845947c3","doc_no":"A.2.2.8.1.2.3.5.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1392,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"d0ceb4ed-8f65-45c6-808e-fca702dc2a62":{"id":"d0ceb4ed-8f65-45c6-808e-fca702dc2a62","doc_no":"A.2.2.8.1.2.3.5.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1393,"content":"The process flow for this process is defined herein:\n\n- Using the finalized `Atlas Edit Proposal` content, the Operational Facilitator sets up an offchain Snapshot vote.\n- Prime Agent token holders vote on the proposal.\n- After the voting concludes, the Operational Facilitator records the result of the vote in the Powerhouse system.","contentHash":"14020011644b175ecc14bd367eb09bc8b5eaf621c998ed71b70cc35ff981f8a3","addressRefs":[]},"b593ff77-2c46-418d-a7b3-9730437ce804":{"id":"b593ff77-2c46-418d-a7b3-9730437ce804","doc_no":"A.2.2.8.1.2.3.5.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1394,"content":"The required Primitive Inputs to this process are defined herein.\n\n- After Facilitator prepares Snapshot vote:\n    - Edit `Artifact Edit Proposal` Document\n        - Updated fields\n            - Status\n                - New value: set to `Pending Poll`\n            - Off-chain Snapshot\n                - New value: Populate with link to the official Snapshot page\n        - Responsible party: Operational Facilitator\n- Mutually Exclusive Input Pathways: The two Primitive Inputs below are mutually exclusive pathways. Once the vote concludes, the corresponding Pathway is followed to the exclusion of the other.\n    - Proposal Passes\n        - Edit `Artifact Edit Proposal` Document\n            - Update fields\n                - Status\n                    - New value: set to `Poll Approved`\n            - Responsible party: Operational Facilitator.\n            - Trigger - Required Output: Proposal Passes\n    - Proposal Fails\n        - Updated fields\n            - Edit `Artifact Edit Proposal` Document\n                - Status\n                    - New value: set to `Poll Rejected`\n        - Responsible party: Operational Facilitator.\n        - Trigger - Required Output: Proposal Fails","contentHash":"e300b147c631dae38be04e19aad84a3d890fb63699c65a5d81df4ef1f749042f","addressRefs":[]},"1e95dff0-2a7f-461f-86f9-70433b888650":{"id":"1e95dff0-2a7f-461f-86f9-70433b888650","doc_no":"A.2.2.8.1.2.3.5.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1395,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"cc530c80-0c89-4c4a-b108-46a623f4f4c6":{"id":"cc530c80-0c89-4c4a-b108-46a623f4f4c6","doc_no":"A.2.2.8.1.2.3.5.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1396,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"1efa0fc5-5377-428f-a203-8c3c10dcc153":{"id":"1efa0fc5-5377-428f-a203-8c3c10dcc153","doc_no":"A.2.2.8.1.2.3.5.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1397,"content":"The Agent Artifact documents specified herein are updated as the output of this process. The Output \"sets\" are mutually exclusive.\n\n- Proposal Passes\n    - Required Primitive Input Trigger: Proposal Passes see [A.2.2.8.1.2.3.5.3 - Required Primitive Inputs](b593ff77-2c46-418d-a7b3-9730437ce804)\n    - Edit `Primitive Hub Document/In Progress Invocations Directory/Instance Name`\n        - Updated fields\n            - Invocation Status\n                - New value: set to `Proposal Approved`\n        - Responsible Party: Operational GovOps\n        - Trigger - Process: [A.2.2.8.1.2.3.6 - Process Definition For Artifact Update](b3ed1e74-7ec2-4537-8e1d-2098dc17d984)\n- Proposal Fails\n    - Required Primitive Input Trigger: Proposal Fails see [A.2.2.8.1.2.3.5.3 - Required Primitive Inputs](b593ff77-2c46-418d-a7b3-9730437ce804)\n    - Edit `Primitive Hub Document/In Progress Invocations Directory/Instance Name`\n        - Updated fields\n            - Invocation Status\n                - New value: set to `Proposal Rejected`\n        - Other Document Operations:\n            - `Instance Configuration Document` is `Archived` in Primitive Hub Document/Hub Data Repository\n        - Responsible Party: Operational GovOps","contentHash":"947d5e26fea8f87e9dc0fce1e8b70306645d6976da5f4116a2795abdbd1f5bb0","addressRefs":[]},"b3ed1e74-7ec2-4537-8e1d-2098dc17d984":{"id":"b3ed1e74-7ec2-4537-8e1d-2098dc17d984","doc_no":"A.2.2.8.1.2.3.6","title":"Process Definition For Artifact Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1398,"content":"The documents herein define the Artifact Update process for an Invocation of the Distribution Reward Primitive.","contentHash":"7618ed79274e238e5727acef221315c7b3f3f6aef6e67e2b134f1e5e48d5839f","addressRefs":[]},"005830a0-5845-4460-961a-9d5f15a722ab":{"id":"005830a0-5845-4460-961a-9d5f15a722ab","doc_no":"A.2.2.8.1.2.3.6.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1399,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"9e5fb847-18f1-4b86-989f-95ec770236b7":{"id":"9e5fb847-18f1-4b86-989f-95ec770236b7","doc_no":"A.2.2.8.1.2.3.6.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1400,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"03ec388b-5e00-42da-a708-e2fd6a7d8775":{"id":"03ec388b-5e00-42da-a708-e2fd6a7d8775","doc_no":"A.2.2.8.1.2.3.6.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1401,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"309ac677-8841-4821-aba5-6cf637b8e7a7":{"id":"309ac677-8841-4821-aba5-6cf637b8e7a7","doc_no":"A.2.2.8.1.2.3.6.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1402,"content":"This process is triggered by the Artifact update specified in Proposal passes.","contentHash":"227941b29f47fe9a51c947b4ece1b2f152e5083fe2a4fd92b455dc81eceb17b3","addressRefs":[]},"d7ec33fc-6c67-4632-80b2-1fab854699bc":{"id":"d7ec33fc-6c67-4632-80b2-1fab854699bc","doc_no":"A.2.2.8.1.2.3.6.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1403,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"3a23ed21-d9ac-4575-9c53-806fddb10f5c":{"id":"3a23ed21-d9ac-4575-9c53-806fddb10f5c","doc_no":"A.2.2.8.1.2.3.6.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1404,"content":"The process flow is defined herein.\n\n- Using the Powerhouse interface, the Operational Facilitator updates the Agent Artifact with the approved Proposal content.","contentHash":"7435f49fbe1e9ddbb8ba2e86559ff4bb964b60c1dfe9f2012f96b56953880e52","addressRefs":[]},"6eb0901b-d324-4124-b27e-5f5416264f37":{"id":"6eb0901b-d324-4124-b27e-5f5416264f37","doc_no":"A.2.2.8.1.2.3.6.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1405,"content":"The following inputs must be submitted into the Primitive using the Powerhouse interface.\n\n- Edit `Instance Configuration Document` to reflect ratified Primitive Instance.\n    - Updated fields\n        - Parameters/Status - automatically inherits from `Primitive Hub Document`\n        - Parameters/Reward Code\n            - New Value: set to `Reward Code` value from approved Proposal\n        - Parameters/Tracking Methodology\n            - New Value: set to `Tracking Methodology` value from the approved Proposal\n        - Parameters/Custom Instance Parameters\n            - New Value: set to `Custom Instance Parameters` value from approved Proposal\n        - Responsible Party: Operational GovOps [if not automated]","contentHash":"aeeda983a55740510ad49c1c5e38005f82cc6d356de7699c36c7682226680830","addressRefs":[]},"231e3527-5534-42d4-b83e-0f99cb40bf76":{"id":"231e3527-5534-42d4-b83e-0f99cb40bf76","doc_no":"A.2.2.8.1.2.3.6.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1406,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"108174f5-b53d-4bc0-8576-172b27021121":{"id":"108174f5-b53d-4bc0-8576-172b27021121","doc_no":"A.2.2.8.1.2.3.6.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1407,"content":"The Sky Core Documents specified herein are updated as the output of this process.","contentHash":"7db1b992bf8d7b69c53ab16bcb1e8983b2db4919127e4f1e2dd51c6d5b10a889","addressRefs":[]},"4287ecd9-5ba6-4646-b949-306b494a108c":{"id":"4287ecd9-5ba6-4646-b949-306b494a108c","doc_no":"A.2.2.8.1.2.3.6.4.1.1","title":"Onboarding Integrators Active Data Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1408,"content":"[A.2.2.8.1.2.1.6.2.0.6.1 - List Of Onboarding Integrators](eb644108-94fc-430f-ae5a-e3294b9dd9be) is updated as follows:\n\n- Updated fields\n    - `Onboarding Integrators`\n        - New value: Delete the Integrator.\n- Responsible Party: Operational GovOps\n- Triggers: None","contentHash":"d95f8fd65290c9ad26bd6ecbe1be4b34fb0c5f938366fd97fbfe0bb719a8cc6c","addressRefs":[]},"1c0708d0-6388-4264-90f2-7a0d0b877012":{"id":"1c0708d0-6388-4264-90f2-7a0d0b877012","doc_no":"A.2.2.8.1.2.3.6.4.1.2","title":"Current Integrators Active Data Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1409,"content":"[A.2.2.8.1.2.1.6.1.0.6.1 - List Of Current Integrators](efbe7903-a76e-40f0-a440-56e463283157) is updated as follows:\n\n- Updated fields\n    - `Current Integrators`\n        - New value: set to the name of the Integrator from the approved Proposal\n    - `Reward Code`\n        - New value: set to the Reward Code from the approved Proposal\n    - `Tracking Methodology`\n        - New value: set to the tracking methodology from the approved Proposal\n- Responsible Party: Operational GovOps\n- Triggers: None","contentHash":"79ef551f929722341405012e9e54b25ace190a5fe34e1319fb09da96c176c63e","addressRefs":[]},"8336c1ad-e182-4c91-b4f9-b5f743500457":{"id":"8336c1ad-e182-4c91-b4f9-b5f743500457","doc_no":"A.2.2.8.1.2.3.6.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1410,"content":"The Agent Artifact documents specified herein are updated as the output of this process.","contentHash":"089da35aa8b5594f8d611ad8991e3ce92e5b986a007dac62109b22911a5a5c15","addressRefs":[]},"3401c95d-3a9f-4af4-bc70-fb1be8f0f676":{"id":"3401c95d-3a9f-4af4-bc70-fb1be8f0f676","doc_no":"A.2.2.8.1.2.3.6.4.2.1","title":"Instance Configuration Document Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1411,"content":"The Document is updated as follows:\n\n- Document Operations:\n    - Document is moved from `In Progress Invocations` to `Active Instances`\n- Responsible Party: Operational Facilitator","contentHash":"8915067979e5bf2d4ae54464f4b2775bd04451a7f9c52ed4f50cf6228c42bd10","addressRefs":[]},"f5b8f596-5999-4ed8-a998-9c920bb86c14":{"id":"f5b8f596-5999-4ed8-a998-9c920bb86c14","doc_no":"A.2.2.8.1.2.3.6.4.2.2","title":"Primitive Hub Document/In Progress Invocations Directory/Instance Name Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1412,"content":"The Document is updated as follows:\n\n- Document Operations:\n    - Document is converted into `Active Instances Directory` schema and moved into that subtree\n- Updated fields\n    - Instance Configuration Document location: link to `Instance Configuration Document` in `Active Instances` subtree\n- Responsible Party: Operational Facilitator\n- Trigger-Process: None.","contentHash":"771f7071598d03105fb493992df45647e2ba2fc05924071c576e9a1cee6167eb","addressRefs":[]},"3af0e156-b5c0-493b-bd6f-80185072b7b1":{"id":"3af0e156-b5c0-493b-bd6f-80185072b7b1","doc_no":"A.2.2.8.1.2.4","title":"Instance Ongoing Management Protocol","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1413,"content":"The documents herein define the process for the ongoing management of an Instance of the Distribution Reward Primitive.","contentHash":"024c881e2599a943111b49b95197c425c58c9f47c5e753089fe9477b1410139d","addressRefs":[]},"c2abdd22-fe0f-489e-b281-450e066db701":{"id":"c2abdd22-fe0f-489e-b281-450e066db701","doc_no":"A.2.2.8.1.2.4.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1414,"content":"The documents herein define the protocol for routine ongoing management of an Instance of the Distribution Reward Primitive.","contentHash":"fef24ee227515bd6bae2f7c6058819e7376f1f49f33cf54f4f1fa81dfffe07db","addressRefs":[]},"27229032-ddb6-41a5-a5d5-6168ccc3142f":{"id":"27229032-ddb6-41a5-a5d5-6168ccc3142f","doc_no":"A.2.2.8.1.2.4.1.1","title":"Process Definition For Reward Calculation By Operational Govops","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1415,"content":"The documents herein define the process for Distribution Reward Calculation by Operational GovOps. The Distribution Reward Calculation includes the calculation of the Fees for Unrewarded USDS Balances, the Fees for Rewarded USDS Balances, and the Prime Agent Management Fee.","contentHash":"eaaa073fc92e0d8eab6a14f4b18436014bc92be2c5f0fa1b5e732170c2f626a6","addressRefs":[]},"a0a60c30-1c73-4bb1-b4c3-92a5541ff4b2":{"id":"a0a60c30-1c73-4bb1-b4c3-92a5541ff4b2","doc_no":"A.2.2.8.1.2.4.1.1.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1416,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"7a9450db-0d90-4578-ad14-6a8308b2b4b8":{"id":"7a9450db-0d90-4578-ad14-6a8308b2b4b8","doc_no":"A.2.2.8.1.2.4.1.1.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1417,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"3e14118d-b60b-49c4-a730-90eb3ad606a9":{"id":"3e14118d-b60b-49c4-a730-90eb3ad606a9","doc_no":"A.2.2.8.1.2.4.1.1.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1418,"content":"This process is triggered on the 1st of every month for each Instance of the Distribution Reward Primitive with an Instance Status of `Active`.","contentHash":"2cc44fd06b418d2347977da4a6144ff146d147411741486c33f0e6364d1df246","addressRefs":[]},"351bd87e-1795-4b00-ad05-2b9869394854":{"id":"351bd87e-1795-4b00-ad05-2b9869394854","doc_no":"A.2.2.8.1.2.4.1.1.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1419,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"dfd59dc4-365c-4718-833a-b859f00dff9b":{"id":"dfd59dc4-365c-4718-833a-b859f00dff9b","doc_no":"A.2.2.8.1.2.4.1.1.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1420,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"70360ef3-14b5-4eaf-abc1-8c3ceb1596a1":{"id":"70360ef3-14b5-4eaf-abc1-8c3ceb1596a1","doc_no":"A.2.2.8.1.2.4.1.1.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1421,"content":"The process flow is defined herein:\n\n- Operational GovOps calculates the eligible USDS and sUSDS balances using the Tracking Methodology specified in the Primitive Instance.\n- Operational GovOps calculates the Distribution Reward due based on the USDS and sUSDS balances and the Distribution Reward formula for each.\n- Operational GovOps updates the Powerhouse system with both the underlying data and their calculations.","contentHash":"7887c828f92b310b8a1b38f67030f2cce9440a6c42977ccaea04f9c6bf07f5ad","addressRefs":[]},"57921647-2a63-4d01-907b-131a50510d76":{"id":"57921647-2a63-4d01-907b-131a50510d76","doc_no":"A.2.2.8.1.2.4.1.1.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1422,"content":"The required Primitive Inputs to this process are specified herein.\n\n- Edit `Distribution Reward Payments` Document (Active Data)\n    - Updated fields\n        - Status\n            - New value: set to `In Progress`\n        - Underlying data\n            - New value: populate with underlying data used to calculate the eligible USDS and sUSDS balances\n        - Eligible USDS balance\n            - New value: populate with calculated value\n        - Eligible sUSDS balance\n            - New value: populate with calculated value\n        - Distribution Reward Due\n            - New value: populate with calculated value.\n    - Responsible party: Operational GovOps.\n    - Trigger-Process: [A.2.2.8.1.2.4.1.2 - Process Definition For Reward Issuance From Operational Executor Agent Buffer](ddd65b02-3a2b-4478-a435-989324c2f1b8).","contentHash":"78c30fa11dac8af9ee57cd17cbe20fc75c71aa5cc5137f386611e427076f95bd","addressRefs":[]},"082e5d05-9394-4b4a-8ef2-0e6d8110c2cc":{"id":"082e5d05-9394-4b4a-8ef2-0e6d8110c2cc","doc_no":"A.2.2.8.1.2.4.1.1.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1423,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"34264a04-6a76-4bf0-9b32-283992d9364a":{"id":"34264a04-6a76-4bf0-9b32-283992d9364a","doc_no":"A.2.2.8.1.2.4.1.1.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1424,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"f3ba519f-0d2f-4565-80be-3c095fc49b75":{"id":"f3ba519f-0d2f-4565-80be-3c095fc49b75","doc_no":"A.2.2.8.1.2.4.1.1.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1425,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified [A.2.2.8.1.2.4.1.1.3 - Required Primitive Inputs](57921647-2a63-4d01-907b-131a50510d76) fully complete the Process.","contentHash":"edad2016b0555d9fc7da75dfaaa2c5933e0feb04ec58521385deff008660b418","addressRefs":[]},"ddd65b02-3a2b-4478-a435-989324c2f1b8":{"id":"ddd65b02-3a2b-4478-a435-989324c2f1b8","doc_no":"A.2.2.8.1.2.4.1.2","title":"Process Definition For Reward Issuance From Operational Executor Agent Buffer","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1426,"content":"The documents herein define the process for Distribution Reward issuance from the Operational Executor Agent Buffer as part of ongoing management of an Instance of the Distribution Reward Primitive.","contentHash":"6d07f5d300a8d5f9f7fbda25fd11643a2b6927792572f1579ed6ecc476cdc6db","addressRefs":[]},"a24bf9e6-3805-4a12-a277-ade2e24e0d77":{"id":"a24bf9e6-3805-4a12-a277-ade2e24e0d77","doc_no":"A.2.2.8.1.2.4.1.2.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1427,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"18123d66-7a54-40dd-a4a7-389f83658247":{"id":"18123d66-7a54-40dd-a4a7-389f83658247","doc_no":"A.2.2.8.1.2.4.1.2.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1428,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"aa6d4d8e-1b6a-41d6-b5f8-29dde7d5a55a":{"id":"aa6d4d8e-1b6a-41d6-b5f8-29dde7d5a55a","doc_no":"A.2.2.8.1.2.4.1.2.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1429,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"a66e1d9d-f113-4e83-8a17-77ce1724c2c9":{"id":"a66e1d9d-f113-4e83-8a17-77ce1724c2c9","doc_no":"A.2.2.8.1.2.4.1.2.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1430,"content":"This process is triggered by the Required Primitive Inputs specified in Edit Distribution Reward Payments Document (Active Data).","contentHash":"1d9c0c2a261f7cbfa254e748d21e43171b32bd61fff2aa4568e500347f49571d","addressRefs":[]},"3741afa3-1593-4ca5-b90c-186f499b111b":{"id":"3741afa3-1593-4ca5-b90c-186f499b111b","doc_no":"A.2.2.8.1.2.4.1.2.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1431,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"3373c13d-907d-420b-9ad8-3cf6b4645359":{"id":"3373c13d-907d-420b-9ad8-3cf6b4645359","doc_no":"A.2.2.8.1.2.4.1.2.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1432,"content":"The process flow is defined herein.\n\n- Operational GovOps makes the payment to the reward address specified in the Primitive Instance from the Operational Executor Agent Buffer.\n- Operational GovOps updates the Powerhouse system with the transaction details.","contentHash":"69b5473438f2e1e95d2dea42fe02c29d91ba1b6e2509026cb60ec7ad0fb4eff9","addressRefs":[]},"63ba8de2-55ed-4df5-9e11-016a006cf828":{"id":"63ba8de2-55ed-4df5-9e11-016a006cf828","doc_no":"A.2.2.8.1.2.4.1.2.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1433,"content":"The required Primitive Inputs to this process are specified herein.\n\n- Edit `Distribution Reward Payments` Document (Active Data)\n    - Updated fields\n        - Status\n            - New value: set to `Paid`\n        - Transaction Details/Amount Paid\n            - New value: populate with amount paid\n        - Transaction Details/Tx hash\n            - New value: populate with transaction hash\n    - Responsible Party: Operational GovOps\n    - Trigger - Process: [A.2.2.8.1.2.4.1.3 - Process Definition For Settlement Cycle And Core GovOps Review](dfd65786-e4be-4dad-9e34-cd6235a30a4f).","contentHash":"53929b3f6c2311cb07619ee7049669314cd08b238853167188fbe15baf940880","addressRefs":[]},"f33e0dee-b8e8-4d93-b56e-624dec274739":{"id":"f33e0dee-b8e8-4d93-b56e-624dec274739","doc_no":"A.2.2.8.1.2.4.1.2.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1434,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"810220a0-0694-4174-b438-6fb0a4b98299":{"id":"810220a0-0694-4174-b438-6fb0a4b98299","doc_no":"A.2.2.8.1.2.4.1.2.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1435,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"ede7410d-a632-4209-ae79-7e3ba730cef1":{"id":"ede7410d-a632-4209-ae79-7e3ba730cef1","doc_no":"A.2.2.8.1.2.4.1.2.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1436,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified in [A.2.2.8.1.2.4.1.2.3 - Required Primitive Inputs](63ba8de2-55ed-4df5-9e11-016a006cf828) fully complete the process.","contentHash":"a275657493a67d48eb6cf7856833bb09483551f042456631ee990c284110829a","addressRefs":[]},"dfd65786-e4be-4dad-9e34-cd6235a30a4f":{"id":"dfd65786-e4be-4dad-9e34-cd6235a30a4f","doc_no":"A.2.2.8.1.2.4.1.3","title":"Process Definition For Settlement Cycle And Core GovOps Review","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1437,"content":"The documents herein define the process for the Distribution Reward Settlement Cycle and Core GovOps review as part of ongoing management of an Instance of the Distribution Reward Primitive.","contentHash":"191bdcc1b1b20359cb89c911065c6708abb9dd66f65b17faa5d769e341e482af","addressRefs":[]},"e0495e9f-5dbd-4191-b52d-b87c6067d19a":{"id":"e0495e9f-5dbd-4191-b52d-b87c6067d19a","doc_no":"A.2.2.8.1.2.4.1.3.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1438,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"82b72cd2-b012-4865-9266-bcc35d644ec2":{"id":"82b72cd2-b012-4865-9266-bcc35d644ec2","doc_no":"A.2.2.8.1.2.4.1.3.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1439,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"97fba609-d197-43dc-a6e1-72c6b2c48519":{"id":"97fba609-d197-43dc-a6e1-72c6b2c48519","doc_no":"A.2.2.8.1.2.4.1.3.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1440,"content":"This process is triggered at the beginning of every calendar quarter.","contentHash":"a51098740bae49f00f5af381d4297577b9e72a9ffc5538c677c3faea9030ed53","addressRefs":[]},"c96dd69d-2be3-451e-8551-a17de1c81579":{"id":"c96dd69d-2be3-451e-8551-a17de1c81579","doc_no":"A.2.2.8.1.2.4.1.3.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1441,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"db7ad152-ee64-4185-b224-ad9ad7ec1093":{"id":"db7ad152-ee64-4185-b224-ad9ad7ec1093","doc_no":"A.2.2.8.1.2.4.1.3.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1442,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"8b8308fd-e1ac-431c-8fe1-8e824ba7e978":{"id":"8b8308fd-e1ac-431c-8fe1-8e824ba7e978","doc_no":"A.2.2.8.1.2.4.1.3.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1443,"content":"The process flow is defined herein.\n\n- Core GovOps reviews Distribution Rewards calculations, including underlying data and calculation of balances and rewards due.\n- Once Core GovOps has completed review, they update Powerhouse system to indicate that they confirm the accuracy of the Distribution Reward amounts.","contentHash":"fadc61e3c9eb69dc0c407bceff2a7ac4381f336535d352d1d823b709226e0cb8","addressRefs":[]},"b55afaef-db92-4bbf-8d80-258d5849ef1c":{"id":"b55afaef-db92-4bbf-8d80-258d5849ef1c","doc_no":"A.2.2.8.1.2.4.1.3.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1444,"content":"The required Primitive Inputs to this process are specified herein and are mutually exclusive pathways.\n\n- Core GovOps Confirms Accuracy of Payment\n    - Edit `Distribution Reward Payments` Active Data Document\n        - Updated fields\n            - Core GovOps Review/Confirmation\n                - New value: populate with Yes\n            - Core GovOps Review/Commentary\n                - New value (optional): populate with reasoning\n        - Responsible party: Core GovOps\n        - Trigger - Process: [A.2.2.8.1.2.4.1.3.4.1 - Sky Core Atlas Updates](cca17fe9-3dc9-48ce-be26-39a1625b3690)\n- Core GovOps Finds Inaccurate Payment\n    - Edit `Distribution Reward Payments` Active Data Document\n        - Updated fields\n            - Core GovOps Review/Confirmation\n                - New value: populate with No\n            - Core GovOps Review/Commentary\n                - New value (required): populate with reasoning\n        - Responsible party: Core GovOps\n        - Trigger - Process: Payment Inaccuracy Previously Found By Core GovOps","contentHash":"bec3cc0a2fc2113b99169ebe8d415235e4fbdd5796a6db41b28c323fa57ad693","addressRefs":[]},"7cb3c11b-7356-4967-b232-6667b66b6f51":{"id":"7cb3c11b-7356-4967-b232-6667b66b6f51","doc_no":"A.2.2.8.1.2.4.1.3.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1445,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"cca17fe9-3dc9-48ce-be26-39a1625b3690":{"id":"cca17fe9-3dc9-48ce-be26-39a1625b3690","doc_no":"A.2.2.8.1.2.4.1.3.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1446,"content":"The Sky Core Atlas documents specified herein are updated as the output of this process.\n\n- Payment Accuracy Previously Confirmed By Core GovOps\n    - The document [A.2.2.8.1.2.1.7.1.0.6.1 - Sky Core Distribution Reward Reimbursement Amounts](169eb312-ed63-4a83-9f5d-43b621c0705e) in the Sky Core Atlas is updated as follows:\n        - Updated Fields\n            - Status\n                - New value: populate with `Pending Payment`\n            - Confirmed Reimbursement Due\n                - New value: populate with total Reimbursement amount\n            - Reward Period\n                - New Value: populate with reward period\n            - Operational Executor Agent\n                - New value: Populate with name of Operational Executor Agent\n            - Prime Agent\n                - New value: Populate with name of Prime Agent.\n        - Responsible Party: Core GovOps\n        - Triggers: [A.2.2.8.1.2.4.1.4 - Process Definition For Executive Vote Reimbursement](59259360-a288-4412-a39a-da3991c60f8f)\n- Payment Inaccuracy Previously Found By Core GovOps\n    - TBD","contentHash":"dc19c130c3081c196e4244dd8640ac0a828ee24fa76460c5fcd3b36f3adca2c2","addressRefs":[]},"300fca05-66b1-4f31-966a-d26168ded7c3":{"id":"300fca05-66b1-4f31-966a-d26168ded7c3","doc_no":"A.2.2.8.1.2.4.1.3.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1447,"content":"No Agent Artifact documents are updated as the output of this process.","contentHash":"454c32a6d9945855f1957b9da47e18d80fe986f357e256d293d6e7d557905208","addressRefs":[]},"59259360-a288-4412-a39a-da3991c60f8f":{"id":"59259360-a288-4412-a39a-da3991c60f8f","doc_no":"A.2.2.8.1.2.4.1.4","title":"Process Definition For Executive Vote Reimbursement","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1448,"content":"The documents herein define the process for Distribution Reward Executive Vote reimbursement as part of ongoing management of an Instance of the Distribution Reward Primitive.","contentHash":"58b4f92b71b1287385e29f4cc04c9c8bc936b57f89360f36487f036d4dd8a6af","addressRefs":[]},"f7bc89b8-424f-4f6a-8f1b-e173ca22f2ce":{"id":"f7bc89b8-424f-4f6a-8f1b-e173ca22f2ce","doc_no":"A.2.2.8.1.2.4.1.4.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1449,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"14d233e1-0e8e-4dd5-915a-89f2b94f6e18":{"id":"14d233e1-0e8e-4dd5-915a-89f2b94f6e18","doc_no":"A.2.2.8.1.2.4.1.4.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1450,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"b61d8b1d-5a03-41ba-9bc7-49e1e876b855":{"id":"b61d8b1d-5a03-41ba-9bc7-49e1e876b855","doc_no":"A.2.2.8.1.2.4.1.4.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1451,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"c298f200-2ac8-4fc3-9d02-e05f4cf2f42f":{"id":"c298f200-2ac8-4fc3-9d02-e05f4cf2f42f","doc_no":"A.2.2.8.1.2.4.1.4.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1452,"content":"This process is triggered by the Document Update specified in **`Sky Core Distribution Reward Reimbursement`** **Active Data Document Update**.","contentHash":"080c6402caaf9b41204ce0701b45592591d66d0254e1d922de05090fc5162f35","addressRefs":[]},"ae1c6021-2790-43ce-9d9b-fe8a17a64b60":{"id":"ae1c6021-2790-43ce-9d9b-fe8a17a64b60","doc_no":"A.2.2.8.1.2.4.1.4.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1453,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"ffa519f8-71f9-4285-892f-49e79f8ed0de":{"id":"ffa519f8-71f9-4285-892f-49e79f8ed0de","doc_no":"A.2.2.8.1.2.4.1.4.2","title":"Process Flow","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1454,"content":"The process flow is defined herein:\n\n- Core GovOps includes the Distribution Reward reimbursement in the next standard Executive Vote.\n- After the Executive Vote passes, Core GovOps updates the Powerhouse system with the transaction details.","contentHash":"558f2c73a62e61f646bd2d076a8ea61972978f8635227c32347650efa8855487","addressRefs":[]},"6b90e3a1-48ce-4ac2-852e-00a8e4edf152":{"id":"6b90e3a1-48ce-4ac2-852e-00a8e4edf152","doc_no":"A.2.2.8.1.2.4.1.4.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1455,"content":"The required Primitive Inputs to this process are specified herein and organized as sequential stages.\n\n- Core GovOps adds reimbursement to Executive Vote\n    - Edit `Sky Core Distribution Reward Reimbursement Amounts`\n        - Updated fields\n            - Executive Vote Settlement/Executive Vote\n                - New value: links to proposal\n            - Status\n                - New value: set to `Added to Executive Vote`\n- After Executive Vote passes, Core GovOps updates Powerhouse system\n    - Edit `Sky Core Distribution Reward Reimbursement Amounts`\n        - Updated fields\n            - Executive Vote Settlement / Transaction Details/ Amount Paid\n                - New value: populate with amount paid to reimburse Operational Executor Agent Buffer\n            - Executive Vote Settlement / Transaction Details / Tx Hash\n                - New value: Populate with transaction hash\n            - Status\n                - New value: set to `Completed`","contentHash":"a15fda091f1eec50d63a692313e6d2ef80a22e18709cabab2443ed8748f1bf3a","addressRefs":[]},"d14fff67-fd16-443b-9d32-763b052dce8b":{"id":"d14fff67-fd16-443b-9d32-763b052dce8b","doc_no":"A.2.2.8.1.2.4.1.4.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1456,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"7daf5881-434b-403e-b443-7bbfa0ce0534":{"id":"7daf5881-434b-403e-b443-7bbfa0ce0534","doc_no":"A.2.2.8.1.2.4.1.4.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1457,"content":"The Sky Core Atlas documents specified herein are updated as the output of this process.","contentHash":"3325881a954b9bc0611bdbf656aa00be7816e4a7d3333829a7ad413fd5f62bff","addressRefs":[]},"0c619a26-b9a6-495a-b7e6-a4a5c79c2da6":{"id":"0c619a26-b9a6-495a-b7e6-a4a5c79c2da6","doc_no":"A.2.2.8.1.2.4.1.4.4.1.1","title":"Sky Core Distribution Reward Reimbursement Active Data Update","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1458,"content":"The Document in the Sky Core Atlas is updated as follows:\n\n- Updated fields\n    - Status\n        - New value: set to `Paid`\n    - Responsible Party: Core GovOps\n    - Trigger-Process: None","contentHash":"9a6ccea37087066b69215a54a5e0e3aa7fe7c0ee887f3de2e531941a9bec9f63","addressRefs":[]},"594d3b57-107d-44bc-a1bf-3f1291b8cccb":{"id":"594d3b57-107d-44bc-a1bf-3f1291b8cccb","doc_no":"A.2.2.8.1.2.4.1.4.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1459,"content":"No Agent Artifact documents are updated as the output of this process.","contentHash":"454c32a6d9945855f1957b9da47e18d80fe986f357e256d293d6e7d557905208","addressRefs":[]},"e852bd1a-b257-4de9-b25b-63a5492ab720":{"id":"e852bd1a-b257-4de9-b25b-63a5492ab720","doc_no":"A.2.2.8.1.2.4.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1460,"content":"The documents herein define the protocol for non-routine ongoing management of an Instance of the Distribution Reward Primitive.","contentHash":"ec3325ca5fdd729a29f2cc2be612f28229489ad5c4bb7e7ffcd14d78efb0a66f","addressRefs":[]},"81b89dda-558c-438e-8ba4-b75a977b8fd3":{"id":"81b89dda-558c-438e-8ba4-b75a977b8fd3","doc_no":"A.2.2.8.1.2.4.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"7f0959dc-c6e2-4e64-9526-76563a2a6d29","order":1461,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of an Instance of the Distribution Reward Primitive.","contentHash":"7b7b83062240e57d320cb4e84051be1ff85d72b7b0efcb47693590695ee1081c","addressRefs":[]},"73577399-62e4-4a83-ae11-64ef7e7b7f20":{"id":"73577399-62e4-4a83-ae11-64ef7e7b7f20","doc_no":"A.2.2.8.2","title":"Integration Boost Primitive","type":"Core","depth":4,"parentId":"26415305-432d-423b-9553-3f325279712d","order":1462,"content":"The documents herein govern the Integration Boost Primitive.","contentHash":"6e94eaa20f67f5cc9419da2c20915749d490773dd7f38d3a4110fe45173c62dd","addressRefs":[]},"84b4b5c7-7125-4f8e-815d-72b3be20a8e9":{"id":"84b4b5c7-7125-4f8e-815d-72b3be20a8e9","doc_no":"A.2.2.8.2.1","title":"Introduction","type":"Core","depth":5,"parentId":"73577399-62e4-4a83-ae11-64ef7e7b7f20","order":1463,"content":"The documents herein provide an introduction to the Integration Boost Primitive.","contentHash":"91514a8f27bd4a2dc5d40e931b94c36f10a98cb639c2ba6ffcb15d6ae0a3337b","addressRefs":[]},"a9751ac4-b292-4c43-a5e5-168df9f0e41e":{"id":"a9751ac4-b292-4c43-a5e5-168df9f0e41e","doc_no":"A.2.2.8.2.1.1","title":"Purpose","type":"Core","depth":6,"parentId":"84b4b5c7-7125-4f8e-815d-72b3be20a8e9","order":1464,"content":"The Integration Boost Primitive provides a low complexity version of the Sky Savings Rate to integration partners that hold USDS or lending markets that integrate USDS.","contentHash":"8aea0fc8c7589068ef1189ffeb3a232677a7ce6804b1b6e7c8f5b22af327322d","addressRefs":[]},"7853b196-73d9-4662-a4aa-f057aa64280c":{"id":"7853b196-73d9-4662-a4aa-f057aa64280c","doc_no":"A.2.2.8.2.1.2","title":"Allowed Number Of Instances","type":"Core","depth":6,"parentId":"84b4b5c7-7125-4f8e-815d-72b3be20a8e9","order":1465,"content":"Multiple instances of the Integration Boost Primitive are allowed. Each instance corresponds to an Integration Boost program.","contentHash":"3e23f9e7a768c21c0f896152a0288e808306ef3e9c139f3515544018e2364d2f","addressRefs":[]},"71c3bf8e-9c5c-447d-afb8-d6ca66acf45f":{"id":"71c3bf8e-9c5c-447d-afb8-d6ca66acf45f","doc_no":"A.2.2.8.2.1.3","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"84b4b5c7-7125-4f8e-815d-72b3be20a8e9","order":1466,"content":"An Agent Artifact that has more than one active instance of the Integration Boost Primitive is not required to have a `Multi-Instance Coordinator Document`, since each Instance can be managed independently.","contentHash":"be47dda35aaf51d489dd8bf67219d26d3f5a7b242527c0d7b809ea064668c7bb","addressRefs":[]},"eecfa6ad-3419-411e-b25a-1ccde2d6484b":{"id":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","doc_no":"A.2.2.8.2.2","title":"Global Specification","type":"Core","depth":5,"parentId":"73577399-62e4-4a83-ae11-64ef7e7b7f20","order":1467,"content":"The requirements herein apply universally across all possible deployments of the Integration Boost Primitive by Prime Agents. They include the steps that Agents must take to deploy the Primitive, including Global Activation of the Primitive, Instance Invocation, and ongoing management of the Primitive Instance(s).","contentHash":"9469085010409a48982004b0f97d374b5a7513de22bb2234cc1108ec457b9d5a","addressRefs":[]},"c398b383-3752-4534-aec6-4cd8e7292119":{"id":"c398b383-3752-4534-aec6-4cd8e7292119","doc_no":"A.2.2.8.2.2.1","title":"Base Elements","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1468,"content":"The documents herein define the base elements of the Integration Boost Primitive.","contentHash":"72df7e499aedb5208157d8c29fd44abc6ca51c7157c3009cb0a9f9b4aacfca48","addressRefs":[]},"31cb3b86-0125-4a04-996f-634b75b6cea2":{"id":"31cb3b86-0125-4a04-996f-634b75b6cea2","doc_no":"A.2.2.8.2.2.1.1","title":"Integration Boost Partners","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1469,"content":"The Integration Boost is provided to DeFi protocol partners that allow users to deposit USDS balances. Sky makes payments to Integration Boost partners equal to the Sky Savings Rate times the Unrewarded USDS balances in their protocol. The expectation is that the Integration Boost Partner will pass these Integration Boost Payments along to their users, thus providing USDS users with the equivalent of the Sky Savings Rate.\n\nIntegration Boost partners are part of the Integrator Program as defined in [A.2.2.8.1.2.1.1 - Integrator Program](37c38f07-b5a0-40df-939c-a54330ea3c7b).\n\nCurrent and onboarding Integrators are recorded in [A.2.2.8.1.2.1.6 - Current And Onboarding Integrators](f3952cc5-cde2-46b9-b575-034dda83570b).","contentHash":"5306240e928b88236fe3cc9939ca1b0ed10a410fa10659e7d4106dbe95191d5f","addressRefs":[]},"dc0bc012-2313-4eea-b898-2ebd97c2a59a":{"id":"dc0bc012-2313-4eea-b898-2ebd97c2a59a","doc_no":"A.2.2.8.2.2.1.1.1","title":"No Obligation To Pass Through Integration Boost Payments","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1470,"content":"Integration Boost partners are under no obligation to pass through any portion of Integration Boost payments to their users. Nevertheless, the expectation is that most partners will pass through Integration Boost payments to remain competitive with other protocols.","contentHash":"f93cc0df04554ddf885b320ae6c51690d135be4e6978f11f1fb7a34b89319d75","addressRefs":[]},"756b466e-2bc0-43af-957f-d827593f5fe2":{"id":"756b466e-2bc0-43af-957f-d827593f5fe2","doc_no":"A.2.2.8.2.2.1.2","title":"Data Submission","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1471,"content":"The documents herein specify data submission requirements related to the Integrator Program.","contentHash":"d80f21887b0d0176eb8ed55e6ecf90d14ac0042434b1a20dee043f20467ec7c5","addressRefs":[]},"6a2ec8d3-0403-46a9-8c96-3a9c86a59792":{"id":"6a2ec8d3-0403-46a9-8c96-3a9c86a59792","doc_no":"A.2.2.8.2.2.1.2.1","title":"Data Verifiability Requirement","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1472,"content":"Integration Boost Partners must submit net deposit data in such a form that the data can be verified by Sky using on-chain data. In the short term, the Core Council Risk Advisor calculates the net deposit data based on on-chain events and makes it available to Operational GovOps through an API endpoint. The API endpoint is [https://info-sky.blockanalitica.com/api/v1/incentivized-pools/](https://info-sky.blockanalitica.com/api/v1/incentivized-pools/) for Integration Boost Partners on Ethereum and [https://info-sky.blockanalitica.com/api/v1/solana-incentives/](https://info-sky.blockanalitica.com/api/v1/solana-incentives/) on Solana. In the long term, Operational GovOps assumes responsibility for ensuring that the data submission meets the on-chain verifiability requirement; this is done as part of their review of Invocations of the Integration Boost Primitive.","contentHash":"ad0dd8d5c463d8afffc2101a0a15f35946d4e86f48269e4fb04617732bd25dda","addressRefs":[]},"079abfa8-583a-4a95-a2d6-7fe50a1dd2dd":{"id":"079abfa8-583a-4a95-a2d6-7fe50a1dd2dd","doc_no":"A.2.2.8.2.2.1.2.2","title":"Data Submission Responsible Party","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1473,"content":"Integration Boost Partners must also identify a responsible party that will submit the net deposit data. In the near term, this is the Core Council Risk Advisor. In the long term, this may be the Integration Boost Partner, a third party contractor, or the Prime Agent or Operational GovOps themselves if they agree to do so.","contentHash":"45febb2d74b67ad9bdaee9e8395ccedacd390ab366f354440b3d15cc532aac2f","addressRefs":[]},"a26ea73f-ab67-4e02-93cd-b43d22a6e63c":{"id":"a26ea73f-ab67-4e02-93cd-b43d22a6e63c","doc_no":"A.2.2.8.2.2.1.2.3","title":"Data Submission Frequency","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1474,"content":"Data is calculated on a weekly basis from Monday to Sunday for payment the following Monday. Failure to submit data on time will result in a delay of payment of the Integration Boost until the following week.","contentHash":"ae44be3e89bc304702febf0029faae7ca28c2593c119f82728eb3234151d9d1d","addressRefs":[]},"3b3914d0-eb7b-4a49-bbca-5f6237a4a8ac":{"id":"3b3914d0-eb7b-4a49-bbca-5f6237a4a8ac","doc_no":"A.2.2.8.2.2.1.3","title":"Distribution","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1475,"content":"The documents herein define base elements of the Integration Boost Primitive related to the distribution of the Integration Boost.","contentHash":"87c83d010047a3b172021e0bf062ca1f21fedbd86537e5c0938e75e8d669dd72","addressRefs":[]},"181954b6-d22c-4605-bffa-b5d964fbb10d":{"id":"181954b6-d22c-4605-bffa-b5d964fbb10d","doc_no":"A.2.2.8.2.2.1.3.1","title":"Cadence","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1476,"content":"The Cadence is the frequency at which the Integration Boost is calculated and distributed. There are only three options available for the Reward Cadence: (1) weekly, (2) biweekly, or (3) monthly.","contentHash":"0da640844ddfd69c826cdf35c2ff0e492329a477c9e7ca2729c5d48b724d0b1b","addressRefs":[]},"e27f2332-1072-4b61-84ab-efe6f2ca056e":{"id":"e27f2332-1072-4b61-84ab-efe6f2ca056e","doc_no":"A.2.2.8.2.2.1.3.2","title":"Treasury Management","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1477,"content":"The documents herein define the treasury management process.","contentHash":"ad659cd5dae218b2312c8d0a905b315b6fe2813c8238625eda210ea7c9864e69","addressRefs":[]},"4ab621b4-ef8e-4b01-a6aa-9296601033c5":{"id":"4ab621b4-ef8e-4b01-a6aa-9296601033c5","doc_no":"A.2.2.8.2.2.1.3.2.1","title":"Near Term Process","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1478,"content":"In the short term, Integration Boost payments are made from the Demand Side Buffer (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)).","contentHash":"a512b798a060cee953f0b84218188bd40fc798eac93338c1a699bff7de8ed643","addressRefs":[]},"787276c9-728b-491f-84d6-c1303fe72986":{"id":"787276c9-728b-491f-84d6-c1303fe72986","doc_no":"A.2.2.8.2.2.1.3.2.2","title":"Long Term Process","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1479,"content":"In the long term, Operational GovOps calculates the Integration Boost for each occurrence of the specified Cadence. Operational GovOps then pays the Integration Boost recipient from its Buffer. Later, Sky Core reimburses the Operational Agent Buffer for the amount paid as part of the Settlement Cycle. This minimizes the role of Sky Core in Integration Boost payments and emphasizes the primary role of the Operational Executor Agent, acting through Operational GovOps, in implementing the Sky Primitives. The process is specified in further detail in [A.2.2.8.2.2.4.1 - Routine Protocol](04864587-25ef-4179-b237-4dd0a23485a4).","contentHash":"7f3937aefa6ecf6a705d8733f54da49d6fa94ce0dd2c6cbcd05d35d989b7cee7","addressRefs":[]},"8d19b08f-d10e-4db2-9e21-03e5021bdaec":{"id":"8d19b08f-d10e-4db2-9e21-03e5021bdaec","doc_no":"A.2.2.8.2.2.1.3.3","title":"Payment Errors","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1480,"content":"If it is discovered that previous Integration Boost calculations were made erroneously, underpayments are resolved retroactively. In cases where an Integrator was overpaid, the Prime Agent associated with the Integrator must reimburse Sky the overpayment amount and can use future Integration Boost payments that the Integrator earns to reimburse itself.","contentHash":"8aaebeb679e439310180cd0d7c9e916fb46fbc9d2ea3963c6e32ffda5981055c","addressRefs":[]},"d71a7b9c-3d0e-4383-9671-098bead326c1":{"id":"d71a7b9c-3d0e-4383-9671-098bead326c1","doc_no":"A.2.2.8.2.2.1.4","title":"Distribution Rewards","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1481,"content":"Net USDS balances in a DeFi protocol that is receiving an Integration Boost are also eligible for the Distribution Reward.","contentHash":"46878f2737f6addaba6764cdbedcad74dbfa3d26670bd06f1a288b2725c689ea","addressRefs":[]},"a4ca2e70-d013-4c54-8e17-1d6f352ddbc0":{"id":"a4ca2e70-d013-4c54-8e17-1d6f352ddbc0","doc_no":"A.2.2.8.2.2.1.4.1","title":"Reporting Of Net USDS Balances Is Valid Tracking Methodology","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1482,"content":"The methodology used to report net USDS balances in the protocol for the Integration Boost is itself an acceptable Tracking Methodology for purposes of the Distribution Reward.","contentHash":"34652e6265e559cbf27da5406a1a509e9e9e4dfae189c58a1e7ad7b9840a1986","addressRefs":[]},"5828a3a0-243d-48a5-b537-297015a0c5f5":{"id":"5828a3a0-243d-48a5-b537-297015a0c5f5","doc_no":"A.2.2.8.2.2.1.4.2","title":"No Double Payments","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1483,"content":"Distribution Reward may only be paid on net USDS balances of an Integration Boost partner to the extent that a Distribution Reward is not already being paid on those balances.","contentHash":"ee992effe898566b2d71ba184b0b63fe2230dbc1e8d80d5f8ed8d1ab180a25bb","addressRefs":[]},"c27d41eb-61f4-4daa-a9c3-b463fa840f60":{"id":"c27d41eb-61f4-4daa-a9c3-b463fa840f60","doc_no":"A.2.2.8.2.2.1.4.3","title":"Prime Agent May Choose Whether To Share Distribution Reward With Integration Boost Partner","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1484,"content":"Prime Agents may choose whether to share Distribution Reward payments with Integration Boost Partners.","contentHash":"c9a00a67aea55e8c50e2cd659b79bdf1a7d231deea8b42792d1fa0e0bfeb5c27","addressRefs":[]},"63ff5ae5-4a50-4d44-b7e4-526608c44598":{"id":"63ff5ae5-4a50-4d44-b7e4-526608c44598","doc_no":"A.2.2.8.2.2.1.5","title":"Integration Boost Reimbursement","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1485,"content":"The documents herein specify the Integration Boost reimbursement.","contentHash":"8b9af6d5e13a10079b87b0013828d0b6ef846fb12bf3a58576b93f0217e22abf","addressRefs":[]},"7ed013c9-f7ac-4459-8675-8bbd398d5133":{"id":"7ed013c9-f7ac-4459-8675-8bbd398d5133","doc_no":"A.2.2.8.2.2.1.5.1","title":"Sky Core Integration Boost Reimbursement","type":"Active Data Controller","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1486,"content":"The Integration Boost reimbursement payments are defined as Active Data in [A.2.2.8.2.2.1.5.1.0.6.1 - Sky Core Integration Boost Reimbursement Amounts](8cbff90b-5633-427e-91da-0fb775812535).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Core GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"4c244992c10d5047423bb5b23010df73f90c6826215a1c4d3b65103701e96cd8","addressRefs":[]},"8cbff90b-5633-427e-91da-0fb775812535":{"id":"8cbff90b-5633-427e-91da-0fb775812535","doc_no":"A.2.2.8.2.2.1.5.1.0.6.1","title":"Sky Core Integration Boost Reimbursement Amounts","type":"Active Data","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1487,"content":"The current Sky Core Integration Boost Reimbursement Amounts are:","contentHash":"ad0de68c184b65d372ab80b98bf343a1d830c5317f02205b0904a9f2d385bede","addressRefs":[]},"4ad2a180-10bd-443d-ba5b-3e46f2b5cf52":{"id":"4ad2a180-10bd-443d-ba5b-3e46f2b5cf52","doc_no":"A.2.2.8.2.2.2","title":"Global Activation","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1488,"content":"An Agent who intends to deploy the Integration Boost Primitive must first Globally Activate it.","contentHash":"0439be2a0e4bb4c5138d0a5944eb16aa678afe60d488c0388b0f337ba076aba7","addressRefs":[]},"b68f9009-e002-4d92-bcb6-c0aeca9239a5":{"id":"b68f9009-e002-4d92-bcb6-c0aeca9239a5","doc_no":"A.2.2.8.2.2.2.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1489,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"ea3fd0be-411c-44e4-9539-2c88000110b5":{"id":"ea3fd0be-411c-44e4-9539-2c88000110b5","doc_no":"A.2.2.8.2.2.2.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1490,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"7457b041-e037-43fa-aee9-107bacdb3acb":{"id":"7457b041-e037-43fa-aee9-107bacdb3acb","doc_no":"A.2.2.8.2.2.2.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1491,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"a007505e-aa58-40f5-bf83-1ded2aa87588":{"id":"a007505e-aa58-40f5-bf83-1ded2aa87588","doc_no":"A.2.2.8.2.2.2.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1492,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"befbf1d8-aa4e-4326-9536-6620754cc96b":{"id":"befbf1d8-aa4e-4326-9536-6620754cc96b","doc_no":"A.2.2.8.2.2.2.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1493,"content":"See [A.2.2.1.2.4 - Changing A Primitive’s Global Activation Status](51cfca28-c8de-457a-abc4-8ce1f64abb91) for constraints on when an Agent can Globally Activate this Primitive.","contentHash":"44856c6ef2bbb0dd8e733f415586bb828ee3e9ea768165dff9e34ede838fbf67","addressRefs":[]},"163b998a-50fe-4bbe-872c-748f526f7604":{"id":"163b998a-50fe-4bbe-872c-748f526f7604","doc_no":"A.2.2.8.2.2.2.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1494,"content":"The Prime Agent uses the Powerhouse interface to Globally Activate (toggle on) the Integration Boost Primitive.","contentHash":"afd961510758fbb3c24bd7f65b0417d7c66202043b2af3b5d9063a563ff94d1d","addressRefs":[]},"5e673229-0130-4b2c-94ce-f8597babd9c1":{"id":"5e673229-0130-4b2c-94ce-f8597babd9c1","doc_no":"A.2.2.8.2.2.2.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1495,"content":"The following inputs must be submitted into the Primitive using the Powerhouse interface:\n\n- **Create** `Primitive Hub Document`\n    - Updated Field: Global Activation Status\n        - New Value: set to `Activated`","contentHash":"028e65933fc762a38c3e88196df72574994cafe6b4116ea8f41c221022688f64","addressRefs":[]},"9a9b56f4-eef8-4d31-af06-3b6d5ba4cb60":{"id":"9a9b56f4-eef8-4d31-af06-3b6d5ba4cb60","doc_no":"A.2.2.8.2.2.2.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1496,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"74f88b57-beef-4cae-a2a6-fafd74812e5c":{"id":"74f88b57-beef-4cae-a2a6-fafd74812e5c","doc_no":"A.2.2.8.2.2.2.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1497,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"35c38264-03ec-4485-9de6-2ff368981066":{"id":"35c38264-03ec-4485-9de6-2ff368981066","doc_no":"A.2.2.8.2.2.2.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1498,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified in [A.2.2.8.2.2.2.3 - Required Primitive Inputs](5e673229-0130-4b2c-94ce-f8597babd9c1) fully complete the Process.","contentHash":"a24996c8cd1f6863bad5d69657598ee7efd9d57ddec166679c40d604f985d089","addressRefs":[]},"a1dc075e-6c36-4375-89ff-fe9bb2c7a2fa":{"id":"a1dc075e-6c36-4375-89ff-fe9bb2c7a2fa","doc_no":"A.2.2.8.2.2.3","title":"Instance Invocation Protocol","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1499,"content":"After fulfilling the requirements for Global Activation, an Agent can Invoke its first Instance of the Integration Boost Primitive by following the sequential process specified herein. Subsequent Invocations of the Primitive must adhere to the same requirements defined below.","contentHash":"11f99e30e5b41766b9cda41798141e77c33b19e2d9158494c20588c81b258ccd","addressRefs":[]},"a14cea92-f114-4cc8-abfe-77b202e3c1f7":{"id":"a14cea92-f114-4cc8-abfe-77b202e3c1f7","doc_no":"A.2.2.8.2.2.3.1","title":"Process Definition For Initial Opportunity Identification And Planning","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1500,"content":"The documents herein specify the process definition for initial opportunity identification and planning.","contentHash":"2d1521b283454013e45a8c02b5572101ce9a14363ffa87c3a7abcbb124eca2fb","addressRefs":[]},"2645e2f0-2624-4fd0-bdc7-2eb09fe28498":{"id":"2645e2f0-2624-4fd0-bdc7-2eb09fe28498","doc_no":"A.2.2.8.2.2.3.1.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1501,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"32cc16f9-2d59-4722-b56a-7f9eae661b57":{"id":"32cc16f9-2d59-4722-b56a-7f9eae661b57","doc_no":"A.2.2.8.2.2.3.1.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1502,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"e06ee9c9-72a5-47ac-8a20-400b3615994a":{"id":"e06ee9c9-72a5-47ac-8a20-400b3615994a","doc_no":"A.2.2.8.2.2.3.1.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1503,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"def2ad89-c78b-4662-a2c3-5a889dbbd722":{"id":"def2ad89-c78b-4662-a2c3-5a889dbbd722","doc_no":"A.2.2.8.2.2.3.1.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1504,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"85a0d037-6b82-4435-aa6d-2d8b481c8f60":{"id":"85a0d037-6b82-4435-aa6d-2d8b481c8f60","doc_no":"A.2.2.8.2.2.3.1.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1505,"content":"This process is dependent on a Prime Agent Globally Activating the Integration Boost Primitive pursuant to [A.2.2.8.2.2.2 - Global Activation](4ad2a180-10bd-443d-ba5b-3e46f2b5cf52).","contentHash":"b8a600b075ee10257a7f3f746ab1647a02ed05f201121085a25a0955250f8be1","addressRefs":[]},"179cb7a5-60ee-4fa0-bc22-d70d4a15c575":{"id":"179cb7a5-60ee-4fa0-bc22-d70d4a15c575","doc_no":"A.2.2.8.2.2.3.1.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1506,"content":"The process flow is defined herein.\n\n- The Prime Agent identifies a DeFi protocol or market where an Integration Boost would drive adoption. The Prime Agent estimates the potential earnings from the Distribution Reward associated with the incremental USDS usage versus the operational cost of funding the Sky Savings Rate payouts.\n- The Prime Agent and the prospective Integration Boost partner discuss (1) the proposed Integration Boost cadence and (2) whether and how the protocol operator also receives a portion of the Distribution Reward.","contentHash":"43c19433044257cf666c73a8a98e1d8d5f955844caa40a91a1d2a3400c1a0f95","addressRefs":[]},"b91d0eb6-fa86-486c-8350-4564bdb5af09":{"id":"b91d0eb6-fa86-486c-8350-4564bdb5af09","doc_no":"A.2.2.8.2.2.3.1.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1507,"content":"The required Primitive Inputs for this process are defined herein and organized in sequential stages.\n\n- Drafting of Initial Planning Document\n    - Create `Initial Planning Document`\n        - Updated fields\n            - `Status`\n                - New value: set to `Drafting`\n            - `Integration Partner Name`\n                - New Value: set to Integration Partner name\n            - `Integration Partner Reward Address`\n                - New Value: set to Integration Partner reward address\n            - `Integration Partner Chain`\n                - New Value: set to Integration Partner chain\n            - `Integration Boost Cadence`\n                - New Value: set to Integration Boost cadence\n            - `Integration Boost Data Submission Format`\n                - New Value: populate with details for format of data submission\n            - `Integration Boost Data Submission Responsible Actor`\n                - New Value: set to Actor responsible for data submission\n            - `Integration Boost Savings Rate Adjustment Strategy`\n                - New Value: populate with details for handling adjustments to Sky Savings Rate\n            - `Custom Instance Parameters`\n                - New Value: populate with details for any custom parameters\n        - Responsible Party: Prime Agent Team\n        - Trigger - Required Output: After Prime Agent's `Initial planning document` Status is set to `Drafting`\n- Initial Planning Document triggered for GovOps review\n    - Edit `Initial Planning Document`\n        - Updated fields\n            - `Integration Boost Savings Rate Adjustment Strategy`\n                - New value: updated content, as applicable\n            - `Status`\n                - New value: set to `Ready for GovOps Review`\n        - Responsible party: Prime Agent\n        - Trigger - Required Output: After Prime Agent's `Initial planning document` Status is set to `Ready for GovOps review`.","contentHash":"0239b9ed8366c44cba1646b2d4149d1b6a85b25236b49e1436a6398a3a6f23b6","addressRefs":[]},"c0e07df6-d6b9-4268-95a6-f0f42877a639":{"id":"c0e07df6-d6b9-4268-95a6-f0f42877a639","doc_no":"A.2.2.8.2.2.3.1.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1508,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"991aaf4f-3d85-41c3-b0c3-d1cf3a84ec0d":{"id":"991aaf4f-3d85-41c3-b0c3-d1cf3a84ec0d","doc_no":"A.2.2.8.2.2.3.1.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1509,"content":"The Sky Core Atlas is updated pursuant to the following requirements.","contentHash":"c58ab1ed78086e3be3121b7112775f54d8e4e704a988321b88a748c905e29ca9","addressRefs":[]},"a227491c-903f-4571-aad0-b76422a5ea7f":{"id":"a227491c-903f-4571-aad0-b76422a5ea7f","doc_no":"A.2.2.8.2.2.3.1.4.1.1","title":"Onboarding Integrators Active Data Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1510,"content":"[A.2.2.8.1.2.1.6.2.0.6.1 - List Of Onboarding Integrators](eb644108-94fc-430f-ae5a-e3294b9dd9be) is updated as follows:\n\n- Updated fields\n    - `Onboarding Integrators/Integrator Name`\n        - New value: set to the name of the Integrator\n- Responsible Party: Operational GovOps","contentHash":"e630e725ec954c88666f52e7c6f0f3318312bd30cb8873d076648c3814819d62","addressRefs":[]},"d86e5f9f-7b1c-4605-9253-4281a6bdbc13":{"id":"d86e5f9f-7b1c-4605-9253-4281a6bdbc13","doc_no":"A.2.2.8.2.2.3.1.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1511,"content":"The Agent Artifact is updated pursuant to the following requirements. Each Output \"set\" is triggered following the completion of its respective Input stage, which latter is defined in [A.2.2.8.2.2.3.1.3 - Required Primitive Inputs](b91d0eb6-fa86-486c-8350-4564bdb5af09).\n\n- After Prime Agent's `Initial planning document` Status is set to `Drafting`\n    - Create `Instance Configuration` Document for prospective Primitive Instance. The Instance Configuration Document contains a `Data Repository`.\n        - Instance Status: (automatically inherits from `Primitive Hub Document`)\n    - Edit `Primitive Hub Document/In Progress Invocations Directory/Instance Name`\n        - Updated fields:\n            - Invocation Status:\n                - New value: set to `Planning`\n            - Instance Configuration Document Location\n                - New value: link to `Instance Configuration Document` (created at Create `Instance Configuration` Document for prospective Primitive Instance. The Instance Configuration Document contains a `Data Repository`.)\n    - Responsible party: Operational GovOps [automated]\n- After Prime Agent's `Initial planning document` Status is set to `Ready for GovOps review`.\n    - Edit `Primitive Hub Document/In Progress Invocations/Instance Name`\n        - Updated fields:\n            - Invocation Status:\n                - New value: set to `Pending GovOps review`\n        - Responsible party: Operational GovOps [ automated]\n        - Trigger - Process: [A.2.2.8.2.2.3.2 - Process Definition for Operational GovOps Review](38c54d2b-715b-433d-a9ff-af5cbecc89a2).","contentHash":"55419d3be72144429669473513e4e44d9296c762532400e0b176e3dfad006ff0","addressRefs":[]},"38c54d2b-715b-433d-a9ff-af5cbecc89a2":{"id":"38c54d2b-715b-433d-a9ff-af5cbecc89a2","doc_no":"A.2.2.8.2.2.3.2","title":"Process Definition for Operational GovOps Review","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1512,"content":"The documents herein define the process for Operational GovOps Review for an Invocation of the Integration Boost Primitive.","contentHash":"215e9bc032c7bfa83d079b7453c8b9a0075a7bc2a08801b012365f32dfeca77f","addressRefs":[]},"ef37ff82-5639-4b5a-88b3-04cc4a4539cb":{"id":"ef37ff82-5639-4b5a-88b3-04cc4a4539cb","doc_no":"A.2.2.8.2.2.3.2.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1513,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"cb905fcc-6834-42a4-a0e8-534e600fad7e":{"id":"cb905fcc-6834-42a4-a0e8-534e600fad7e","doc_no":"A.2.2.8.2.2.3.2.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1514,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"ff9674e1-174c-4365-ba27-4af0aa10539e":{"id":"ff9674e1-174c-4365-ba27-4af0aa10539e","doc_no":"A.2.2.8.2.2.3.2.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1515,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"4290c4b4-5c4d-4de5-bcbe-7d4d6db8b755":{"id":"4290c4b4-5c4d-4de5-bcbe-7d4d6db8b755","doc_no":"A.2.2.8.2.2.3.2.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1516,"content":"This process is triggered by the Artifact Update specified at Edit `Primitive Hub Document/In Progress Invocations/Instance Name`.","contentHash":"d2dabadfae1d4a87d3827e440c921f133b8b21ae0bd6a21cbb2fd2ad01594379","addressRefs":[]},"921d945d-5e36-4ffd-8c30-447aeca18045":{"id":"921d945d-5e36-4ffd-8c30-447aeca18045","doc_no":"A.2.2.8.2.2.3.2.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1517,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"0eba9704-14c9-4be3-ab41-62129ff9f162":{"id":"0eba9704-14c9-4be3-ab41-62129ff9f162","doc_no":"A.2.2.8.2.2.3.2.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1518,"content":"The process flow is defined herein:\n\n- Operational GovOps reviews the `Initial Planning Document` to ensure:\n    - The submitted data can be verified using on-chain data;\n    - the Savings Rate Adjustment Strategy ensures that the payment on USDS balances equals the Sky Savings Rate, and\n    - the submitted data accurately reflects USDS deposits in the Integration Partner protocol and there is no possibility that rewards could be \"double counted\" (i.e. multiple actors being paid for the same USDS balance).\n- Operational GovOps submits its feedback into the `Operational GovOps Review Document` (created at Create `Operational GovOps Review Document`) along with suggested changes, if any.\n- The Prime Agent incorporates feedback from Operational GovOps and edits its `Initial Planning Document` as needed.","contentHash":"dbb0aebe28ba68e4acbccbfe6db345bfa477f29f751551d7650490c6d7fae341","addressRefs":[]},"1eafc42a-1fd2-4f96-988c-8dc37c1ab317":{"id":"1eafc42a-1fd2-4f96-988c-8dc37c1ab317","doc_no":"A.2.2.8.2.2.3.2.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1519,"content":"The following inputs must be submitted into the Primitive using the Powerhouse interface.\n\n- Create `Operational GovOps Review Document`\n    - Updated fields\n        - `Initial Planning Document`\n            - New Value: automatically links to respective Document\n        - `Feedback Summary`\n            - New Value: GovOps populates with its review commentary and suggested changes that are agreed to by Agent and GovOps, if any.\n        - Responsible party: Operational GovOps.","contentHash":"12f8c7f88bd85d09af0af6e8fed4f3ff10540fa9f5180c60b04057d60cdc3be8","addressRefs":[]},"0bce1c09-ba85-418f-8cf7-0f51c8fa0584":{"id":"0bce1c09-ba85-418f-8cf7-0f51c8fa0584","doc_no":"A.2.2.8.2.2.3.2.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1520,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"689a6ce6-0091-4e6a-b634-27ade6064e6b":{"id":"689a6ce6-0091-4e6a-b634-27ade6064e6b","doc_no":"A.2.2.8.2.2.3.2.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1521,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"22166d2b-40bc-4094-a3d8-fce46699a905":{"id":"22166d2b-40bc-4094-a3d8-fce46699a905","doc_no":"A.2.2.8.2.2.3.2.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1522,"content":"The Agent Artifact is updated pursuant to the following requirements.","contentHash":"e5b276f7f31f8804c17a356b8b4dfabce1aa09385e842e4e02f4ae9cee444044","addressRefs":[]},"ddcfe438-e322-425b-82c6-3bba3ce33823":{"id":"ddcfe438-e322-425b-82c6-3bba3ce33823","doc_no":"A.2.2.8.2.2.3.2.4.2.1","title":"Initial Planning Document Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1523,"content":"The Document is updated as follows.\n\n- Updated fields\n    - `Integration Boost Savings Rate Adjustment Strategy`\n        - New Value: as applicable, update to reflect any changes agreed to between the Prime Agent and Operational GovOps\n    - `Integration Boost Data Submission Format`\n        - New Value: as applicable, update to reflect any changes agreed to between the Prime Agent and Operational GovOps\n    - Responsible Party: Operational GovOps","contentHash":"59bf17bc58c131b2862977973af5f50945f635d714eddebe6b023e0a282b81ad","addressRefs":[]},"09ddd2c5-3768-4538-b979-629e1b369299":{"id":"09ddd2c5-3768-4538-b979-629e1b369299","doc_no":"A.2.2.8.2.2.3.2.4.2.2","title":"Primitive Hub Document Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1524,"content":"The Document is updated as follows.\n\n- Updated fields\n    - Active instances/Instance name/Instance status -\n        - New value: set to `Proposal drafting in progress`\n- Responsible Party: Operational GovOps [automated]\n- Triggers: [A.2.2.8.2.2.3.3 - Process Definition for Artifact Update Draft](6a8b5e8b-cca6-48be-b543-6db468f83ebb).","contentHash":"e3433d849b3e10d5177f660872f3c595ac16d76313105ee69165e45b4996a5a2","addressRefs":[]},"6a8b5e8b-cca6-48be-b543-6db468f83ebb":{"id":"6a8b5e8b-cca6-48be-b543-6db468f83ebb","doc_no":"A.2.2.8.2.2.3.3","title":"Process Definition for Artifact Update Draft","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1525,"content":"The documents herein define the process for preparing the Artifact Update Draft for an Invocation of the Integration Boost Primitive.","contentHash":"c4ae0d89c6b2ea7a1b455370e80762056d75071741e339d038b36131dc9ec5f7","addressRefs":[]},"cc3d967c-ec99-4c9c-a874-c42b8412791d":{"id":"cc3d967c-ec99-4c9c-a874-c42b8412791d","doc_no":"A.2.2.8.2.2.3.3.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1526,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"428d6e85-5c6d-4469-9bc8-e1a127427ac0":{"id":"428d6e85-5c6d-4469-9bc8-e1a127427ac0","doc_no":"A.2.2.8.2.2.3.3.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1527,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"42848ad7-ad2e-402f-8ec5-cf6ee991c46c":{"id":"42848ad7-ad2e-402f-8ec5-cf6ee991c46c","doc_no":"A.2.2.8.2.2.3.3.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1528,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"98b5465e-add9-4ae0-a02e-1c5be6006410":{"id":"98b5465e-add9-4ae0-a02e-1c5be6006410","doc_no":"A.2.2.8.2.2.3.3.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1529,"content":"This process is triggered by the Document Update specified at [A.2.2.8.2.2.3.2.4.2.2 - Primitive Hub Document Update](09ddd2c5-3768-4538-b979-629e1b369299).","contentHash":"b92b2415f7f2c21612448caa8309497bdad3fbd309b1b4908521800b01a5ad71","addressRefs":[]},"a616c3f6-b252-4d85-996a-019dea9f01e7":{"id":"a616c3f6-b252-4d85-996a-019dea9f01e7","doc_no":"A.2.2.8.2.2.3.3.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1530,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"c860168e-b88e-4d2a-ad0b-388288d1e0cb":{"id":"c860168e-b88e-4d2a-ad0b-388288d1e0cb","doc_no":"A.2.2.8.2.2.3.3.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1531,"content":"The process flow is defined herein:\n\n- The Prime Agent creates the `Artifact Edit Draft` Document and works to finalize its draft of the Artifact Edit per discussions with Operational GovOps.\n- When draft is finalized, the Prime Agent triggers the creation of the `Artifact Edit Proposal`, which inherits content from the finalized `Artifact Edit Draft` Document.\n- The Prime Agent submits the `Artifact Edit Proposal` Document to the Powerhouse system.","contentHash":"73c12b2d232ee71cf4525448ef7b4d83ad9709bd922f8c8bc914fe022abdee38","addressRefs":[]},"01214a59-5119-4c77-ad41-c9d3dd72a517":{"id":"01214a59-5119-4c77-ad41-c9d3dd72a517","doc_no":"A.2.2.8.2.2.3.3.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1532,"content":"The required Primitive Inputs for this process are defined herein and implemented in sequential stages.\n\n- Agent creates `Artifact Edit Draft` document; drafting in progress\n    - Edit `Artifact Edit Draft`\n        - Updated fields\n            - Status\n                - New value: set to `In Progress`\n            - Content\n                - New value: populate with drafted content\n- Agent finalizes `Artifact Edit Draft`\n    - Edit `Artifact Edit Draft`\n        - Updated fields\n            - Status\n                - New value: set to `Draft Finalized`\n- Powerhouse System Creates `Artifact Edit Proposal` Document\n    - Updated fields\n        - Content\n            - New value: Inherits data from `Artifact Edit Draft` Document’s Content field.\n    - Responsible party: Operational GovOps [if not automated]\n- Agent submits `Artifact Edit Proposal` Document to Powerhouse system\n    - Updated fields\n        - Status:\n            - New value: set to `Pending Facilitator Review`\n    - Responsible Party: Agent","contentHash":"6175d169cda160291f64e8e5a04d32a23c2c7a1d44ef0464967074f3b75e70c7","addressRefs":[]},"bea2c790-2359-4bb7-8744-3f43deb05d26":{"id":"bea2c790-2359-4bb7-8744-3f43deb05d26","doc_no":"A.2.2.8.2.2.3.3.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1533,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"7e4e6528-b8a7-4aff-8d98-3cc3279c4f28":{"id":"7e4e6528-b8a7-4aff-8d98-3cc3279c4f28","doc_no":"A.2.2.8.2.2.3.3.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1534,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"f654be61-baa0-4d5e-8d66-a9d8b3d5b277":{"id":"f654be61-baa0-4d5e-8d66-a9d8b3d5b277","doc_no":"A.2.2.8.2.2.3.3.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1535,"content":"The Agent Artifact documents specified herein are updated as the output of this process.","contentHash":"089da35aa8b5594f8d611ad8991e3ce92e5b986a007dac62109b22911a5a5c15","addressRefs":[]},"e7fc7c2e-b6fc-4e0f-ae10-debb54124e8e":{"id":"e7fc7c2e-b6fc-4e0f-ae10-debb54124e8e","doc_no":"A.2.2.8.2.2.3.3.4.2.1","title":"Primitive Hub Document Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1536,"content":"The Document in the Agent Artifact is updated as follows:\n\n- Updated fields\n    - Active Instances/Instance Name/Instance Status\n        - New value: `Proposal Pending Facilitator Review`\n- Responsible Party: Operational GovOps\n- Triggers: [A.2.2.8.2.2.3.4 - Process Definition for Operational Facilitator Review](2d1d83ea-2a90-4c34-93ea-5bea390f3f62).","contentHash":"e83c84e4ea73bcaeeecfa54ec52bb93937add7e10f6a6186f6238025cd4aef1e","addressRefs":[]},"2d1d83ea-2a90-4c34-93ea-5bea390f3f62":{"id":"2d1d83ea-2a90-4c34-93ea-5bea390f3f62","doc_no":"A.2.2.8.2.2.3.4","title":"Process Definition for Operational Facilitator Review","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1537,"content":"The documents herein define the process for Operational Facilitator Review for an Invocation of the Integration Boost Primitive.","contentHash":"eef7d35cb4489be149e1d58a033964e24172a2603fc619d9ee2a8a2de16494a2","addressRefs":[]},"53016a06-1989-49af-8629-8cac254ef771":{"id":"53016a06-1989-49af-8629-8cac254ef771","doc_no":"A.2.2.8.2.2.3.4.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1538,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"9fa7d744-2f7d-4fb5-81e2-0b348eb01bb6":{"id":"9fa7d744-2f7d-4fb5-81e2-0b348eb01bb6","doc_no":"A.2.2.8.2.2.3.4.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1539,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"c3b16255-ecdc-4d42-9345-945ede629203":{"id":"c3b16255-ecdc-4d42-9345-945ede629203","doc_no":"A.2.2.8.2.2.3.4.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1540,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"555a08a4-e028-44bd-9ba2-91e4bbf61644":{"id":"555a08a4-e028-44bd-9ba2-91e4bbf61644","doc_no":"A.2.2.8.2.2.3.4.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1541,"content":"This process is triggered by the Document Update specified at [A.2.2.8.2.2.3.2.4.2.2 - Primitive Hub Document Update](09ddd2c5-3768-4538-b979-629e1b369299).","contentHash":"b92b2415f7f2c21612448caa8309497bdad3fbd309b1b4908521800b01a5ad71","addressRefs":[]},"f19c7277-65b4-4755-8756-fb0a242ba6a2":{"id":"f19c7277-65b4-4755-8756-fb0a242ba6a2","doc_no":"A.2.2.8.2.2.3.4.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1542,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"1b0c0956-1890-405f-b27b-22399b04526c":{"id":"1b0c0956-1890-405f-b27b-22399b04526c","doc_no":"A.2.2.8.2.2.3.4.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1543,"content":"The process flow is defined herein.\n\n- The Operational Facilitator reviews the `Artifact Edit Proposal` to ensure alignment with the Sky Core Atlas and the Agent Artifact.\n- Where the Proposal is determined to be aligned, the Operational Facilitator updates the `Artifact Edit Proposal` Document to reflect their approval and commentary, if any.\n- Where the Proposal is determined to be misaligned, the Operational Facilitator updates the `Artifact Edit Proposal` document to reflect their rejection and commentary. Commentary is required where the Operational Facilitator rejects the proposal for misalignment.","contentHash":"b32635084ffc5d17295a1a37af21c28c1f805fbf21341e2feac7e46fff8101c6","addressRefs":[]},"7f991abf-3395-4f92-82e1-88e991ebd97a":{"id":"7f991abf-3395-4f92-82e1-88e991ebd97a","doc_no":"A.2.2.8.2.2.3.4.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1544,"content":"The required Primitive Inputs to this process are defined herein and organized as two mutually exclusive pathways. Once the Review outcome is determined by the Facilitator, the corresponding Pathway is followed to the exclusion of the other.\n\n- Operational Facilitator Approves Proposal\n    - Edit `Artifact Edit Proposal`\n        - Updated fields\n            - `Operational Facilitator Review/Review Decision`\n                - New value: set to `Approved`\n            - `Commentary`\n                - New value (optional): populate with reasoning for Approval\n            - `Status`\n                - New value: set to `Proposal Approved by Facilitator` [automated]\n        - Responsible party: Operational Facilitator\n        - Trigger-Process: [A.2.2.8.2.2.3.5 - Process Definition for Offchain Vote](24fa76f6-4728-4f1d-97ff-fd7e72dac2ac).\n- Operational Facilitator Rejects Proposal\n    - Edit `Artifact Edit Proposal`\n        - Updated fields\n            - `Operational Facilitator Review/Review Decision`\n                - New value: set to `Rejected`\n            - `Commentary`\n                - New value (required): populate with reasoning for Rejection\n            - `Status`\n                - New value: set to `Proposal Rejected By Facilitator` [automated]\n        - Responsible party: Operational Facilitator","contentHash":"31ccd6d162dee92eb59dd0a0c5cd05acad52d9312922c8839f0dc8d0880ab9aa","addressRefs":[]},"c7436489-4aac-47cb-be2d-31774bd7ee99":{"id":"c7436489-4aac-47cb-be2d-31774bd7ee99","doc_no":"A.2.2.8.2.2.3.4.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1545,"content":"The documents herein specify the required outputs from this process, if any.","contentHash":"c62ae4f853fc59e2c7bb7f374d52024c16f05e870ca07fd3eb1e1f9f5521cd67","addressRefs":[]},"d7e64cf2-9f1a-4057-8395-fc1eca5c3059":{"id":"d7e64cf2-9f1a-4057-8395-fc1eca5c3059","doc_no":"A.2.2.8.2.2.3.4.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1546,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"d5cce836-259e-48df-ba77-89d58d1476cc":{"id":"d5cce836-259e-48df-ba77-89d58d1476cc","doc_no":"A.2.2.8.2.2.3.4.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1547,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified in [A.2.2.8.2.2.3.4.3 - Required Primitive Inputs](7f991abf-3395-4f92-82e1-88e991ebd97a) fully complete the Process.","contentHash":"3b90ab433159ebd28b9a73dc5f81d2497b30ba15ab33dd39f6d8b4f4ba8ee257","addressRefs":[]},"24fa76f6-4728-4f1d-97ff-fd7e72dac2ac":{"id":"24fa76f6-4728-4f1d-97ff-fd7e72dac2ac","doc_no":"A.2.2.8.2.2.3.5","title":"Process Definition for Offchain Vote","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1548,"content":"The documents herein define the process for an Offchain Vote for an Invocation of the Integration Boost Primitive.","contentHash":"2347beb5da7d4e3317027844ad94f675d3477fd16da601d2a3609e1641298571","addressRefs":[]},"e5c0a813-e8d6-4687-a1ac-c9abbd7bb29f":{"id":"e5c0a813-e8d6-4687-a1ac-c9abbd7bb29f","doc_no":"A.2.2.8.2.2.3.5.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1549,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"c5db0c30-6a19-492c-9389-926ffcbbca06":{"id":"c5db0c30-6a19-492c-9389-926ffcbbca06","doc_no":"A.2.2.8.2.2.3.5.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1550,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"c6ad2b62-8f38-41cd-987f-f771f1a53e38":{"id":"c6ad2b62-8f38-41cd-987f-f771f1a53e38","doc_no":"A.2.2.8.2.2.3.5.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1551,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"bac65a98-2e36-471a-8d3b-68d207ede4e2":{"id":"bac65a98-2e36-471a-8d3b-68d207ede4e2","doc_no":"A.2.2.8.2.2.3.5.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1552,"content":"This process is triggered by the Artifact Update specified at Operational Facilitator Approves Proposal.","contentHash":"cb46a368638f4eec32a3028670bb48f9b1cb18fe594b870bb1ac055e9b523fbf","addressRefs":[]},"bfdafaa4-e8bb-499b-99e6-f748d86cc569":{"id":"bfdafaa4-e8bb-499b-99e6-f748d86cc569","doc_no":"A.2.2.8.2.2.3.5.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1553,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"185d7f3b-9612-42ef-bde7-c9a64ad3ceab":{"id":"185d7f3b-9612-42ef-bde7-c9a64ad3ceab","doc_no":"A.2.2.8.2.2.3.5.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1554,"content":"The process flow for this process is defined herein:\n\n- Using the finalized `Atlas Edit Proposal` content, the Operational Facilitator sets up an offchain Snapshot vote.\n- Prime Agent token holders vote on the proposal.\n- After the voting concludes, the Operational Facilitator records the result of the vote in the Powerhouse system.","contentHash":"14020011644b175ecc14bd367eb09bc8b5eaf621c998ed71b70cc35ff981f8a3","addressRefs":[]},"d247fec5-a19d-4307-94de-a2cbcc368d64":{"id":"d247fec5-a19d-4307-94de-a2cbcc368d64","doc_no":"A.2.2.8.2.2.3.5.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1555,"content":"The required Primitive Inputs to this process are defined herein.\n\n- After Facilitator prepares Snapshot vote:\n    - Edit `Artifact Edit Proposal` Document\n        - Updated fields\n            - Status\n                - New value: set to `Pending Poll`\n            - Off-chain Snapshot\n                - New value: Populate with link to the official Snapshot page\n        - Responsible party: Operational Facilitator\n- Mutually Exclusive Input Pathways: The two Primitive Inputs below are mutually exclusive pathways. Once the vote concludes, the corresponding Pathway is followed to the exclusion of the other.\n    - Proposal Passes\n        - Edit `Artifact Edit Proposal` Document\n            - Update fields\n                - Status\n                    - New value: set to `Poll Approved`\n            - Responsible party: Operational Facilitator.\n            - Trigger - Required Output: Proposal passes\n    - Proposal Fails\n        - Updated fields\n            - Edit `Artifact Edit Proposal` Document\n                - Status\n                    - New value: set to `Poll Rejected`\n            - Responsible party: Operational Facilitator.\n            - Trigger - Required Output: Proposal fails","contentHash":"048f4153ea967dcc40ab75160bda96a50c49396c63e9d3896aefef43fd74548c","addressRefs":[]},"bae40b55-4f53-4992-a872-228fd3d87671":{"id":"bae40b55-4f53-4992-a872-228fd3d87671","doc_no":"A.2.2.8.2.2.3.5.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1556,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"43a3722c-97d0-4389-9d3b-4ac24901d365":{"id":"43a3722c-97d0-4389-9d3b-4ac24901d365","doc_no":"A.2.2.8.2.2.3.5.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1557,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"adfb66a3-4f73-4fcc-bfa2-f5126503187c":{"id":"adfb66a3-4f73-4fcc-bfa2-f5126503187c","doc_no":"A.2.2.8.2.2.3.5.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1558,"content":"The Agent Artifact documents specified herein are updated as the output of this process. The Output \"sets\" are mutually exclusive.\nThe Agent Artifact documents specified herein are updated as the output of this process. The Output \"sets\" are mutually exclusive.\n\n- Proposal passes\n    - Required Primitive Input Trigger: Proposal Passes\n    - **Edit** `Primitive Hub Document`\n        - Fields Updated\n            - Active instances/instance name/instance status - set to `Approved`\n        - Responsible Party: Operational GovOps\n        - Trigger - Process: [A.2.2.8.2.2.3.6 - Process Definition for Artifact Update](182ca3dc-108f-4941-ae2e-eb01c345125b).\n- Proposal fails\n    - Required Primitive Input Trigger: Proposal Fails\n    - **Edit** `Primitive Hub Document`\n        - Fields Updated\n            - Active instances/instance name/instance status - set to `Rejected`\n        - Other Document Operations:\n            - `Instance Configuration Document` is `Archived` in Primitive Hub Document/Data Repository\n        - Responsible Party: Operational GovOps","contentHash":"fa87cbaf910c85c2aeca8197b9b62613fa93ec514b518e52ad488003f8202b6a","addressRefs":[]},"182ca3dc-108f-4941-ae2e-eb01c345125b":{"id":"182ca3dc-108f-4941-ae2e-eb01c345125b","doc_no":"A.2.2.8.2.2.3.6","title":"Process Definition for Artifact Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1559,"content":"The documents herein define the Artifact Update process for an Invocation of the Integration Boost Primitive.","contentHash":"af5a9ae24855f239f6b8ab19a9917260bb64352c5e947ac4a23e463d78ea5009","addressRefs":[]},"59306024-9642-4f4c-891e-dc515e1eff8e":{"id":"59306024-9642-4f4c-891e-dc515e1eff8e","doc_no":"A.2.2.8.2.2.3.6.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1560,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"7ff087ca-2b81-45e2-98e9-08fd184722bc":{"id":"7ff087ca-2b81-45e2-98e9-08fd184722bc","doc_no":"A.2.2.8.2.2.3.6.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1561,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"95379a19-4115-4a94-a525-67ea27ccab85":{"id":"95379a19-4115-4a94-a525-67ea27ccab85","doc_no":"A.2.2.8.2.2.3.6.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1562,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"97e2c2b5-f17b-46a4-9e01-9b782429bd39":{"id":"97e2c2b5-f17b-46a4-9e01-9b782429bd39","doc_no":"A.2.2.8.2.2.3.6.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1563,"content":"This process is triggered by the Artifact update specified in Proposal passes.","contentHash":"227941b29f47fe9a51c947b4ece1b2f152e5083fe2a4fd92b455dc81eceb17b3","addressRefs":[]},"1c0ce5c0-df9a-417e-a3d4-2b09e96787f6":{"id":"1c0ce5c0-df9a-417e-a3d4-2b09e96787f6","doc_no":"A.2.2.8.2.2.3.6.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1564,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"48863e96-796e-4953-b811-cbbfdd294098":{"id":"48863e96-796e-4953-b811-cbbfdd294098","doc_no":"A.2.2.8.2.2.3.6.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1565,"content":"The process flow is defined herein.\n\n- Using the Powerhouse interface, the Operational Facilitator updates the Agent Artifact with the approved Proposal content.","contentHash":"7435f49fbe1e9ddbb8ba2e86559ff4bb964b60c1dfe9f2012f96b56953880e52","addressRefs":[]},"51ca2399-8c7f-4c2a-843a-c85f6c670d13":{"id":"51ca2399-8c7f-4c2a-843a-c85f6c670d13","doc_no":"A.2.2.8.2.2.3.6.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1566,"content":"The following inputs must be submitted into the Primitive using the Powerhouse interface.\n\n- Edit `Instance Configuration Document` to reflect ratified Primitive Instance.\n    - Updated fields\n        - Parameters/Status - automatically inherits from `Primitive Hub Document`\n        - Parameters/Integration Partner Name\n            - New Value: set to `Integration Partner Name` value from approved Proposal\n        - Parameters/Integration Partner Reward Address\n            - New Value: set to `Integration Partner Reward Address` value from approved Proposal\n        - Parameters/Integration Partner Chain\n            - New Value: set to `Integration Partner Chain` value from approved Proposal\n        - Parameters/Integration Boost Cadence\n            - New Value: set to `Integration Boost Cadence` value from approved Proposal\n        - Parameters/Integration Boost Data Submission Format\n            - New Value: set to `Integration Boost Data Submission Format` value from approved Proposal\n        - Parameters/Integration Boost Data Submission Responsible Actor\n            - New Value: set to `Integration Boost Data Submission Responsible Actor` value from approved Proposal\n        - Parameters/Integration Boost Savings Rate Adjustment Strategy\n            - New Value: set to `Integration Boost Savings Rate Adjustment Strategy` value from approved Proposal\n        - Parameters/Custom Instance Parameters\n            - New Value: set to `Custom Instance Parameters` value from approved Proposal\n        - Responsible party: Operational GovOps [if not automated]","contentHash":"5aa534131d0855a30a012af3fe836fd65e0659287797bab93fda707307cda103","addressRefs":[]},"bd74388f-69d8-48fc-bab8-522f1b3b5806":{"id":"bd74388f-69d8-48fc-bab8-522f1b3b5806","doc_no":"A.2.2.8.2.2.3.6.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1567,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"221cde4c-acb8-46c9-866b-7878fc6e5646":{"id":"221cde4c-acb8-46c9-866b-7878fc6e5646","doc_no":"A.2.2.8.2.2.3.6.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1568,"content":"The Sky Core Documents specified herein are updated as the output of this process.","contentHash":"7db1b992bf8d7b69c53ab16bcb1e8983b2db4919127e4f1e2dd51c6d5b10a889","addressRefs":[]},"847092ba-eb97-47ee-a121-6c8e505bc480":{"id":"847092ba-eb97-47ee-a121-6c8e505bc480","doc_no":"A.2.2.8.2.2.3.6.4.1.1","title":"Onboarding Integrators Active Data Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1569,"content":"[A.2.2.8.1.2.1.6.2.0.6.1 - List Of Onboarding Integrators](eb644108-94fc-430f-ae5a-e3294b9dd9be) is updated as follows:\n\n- Updated fields\n    - `Onboarding Integrators`\n        - New value: Delete the Integrator.\n- Responsible Party: Operational GovOps\n- Triggers: None","contentHash":"d95f8fd65290c9ad26bd6ecbe1be4b34fb0c5f938366fd97fbfe0bb719a8cc6c","addressRefs":[]},"1b03bc85-a7f4-4cc5-be41-d13a16b8c379":{"id":"1b03bc85-a7f4-4cc5-be41-d13a16b8c379","doc_no":"A.2.2.8.2.2.3.6.4.1.2","title":"Current Integrators Active Data Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1570,"content":"[A.2.2.8.1.2.1.6.1.0.6.1 - List Of Current Integrators](efbe7903-a76e-40f0-a440-56e463283157) is updated as follows:\n\n- Updated fields\n    - `Current Integrators`\n        - New value: set to the name of the Integrator from the approved Proposal\n    - `Reward Code`\n        - New value: set to the Reward Code from the approved Proposal\n    - `Tracking Methodology`\n        - New value: set to the tracking methodology from the approved Proposal\n- Responsible Party: Operational GovOps\n- Triggers: None","contentHash":"79ef551f929722341405012e9e54b25ace190a5fe34e1319fb09da96c176c63e","addressRefs":[]},"1ba7ea74-00a7-4e45-9fd4-d5222e40746b":{"id":"1ba7ea74-00a7-4e45-9fd4-d5222e40746b","doc_no":"A.2.2.8.2.2.3.6.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1571,"content":"The Agent Artifact documents specified herein are updated as the output of this process.","contentHash":"089da35aa8b5594f8d611ad8991e3ce92e5b986a007dac62109b22911a5a5c15","addressRefs":[]},"f4323202-b7ef-437b-9667-226dea4f9dce":{"id":"f4323202-b7ef-437b-9667-226dea4f9dce","doc_no":"A.2.2.8.2.2.3.6.4.2.1","title":"Primitive Hub Document Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1572,"content":"The Document in the Agent Artifact is updated as follows:\n\n- Required Primitive Input Trigger: Proposal passes\n- Updated fields\n    - Active Instances/Instance Name/Instance Status\n        - New value: `Active`\n    - Instance Location: [links to `Instance Configuration Document` subtree]\n- Responsible Party: Operational Facilitator\n- Trigger-Process: None.","contentHash":"8a01446124a08be0b6147f6ba142c295199883d292264d00fbe92118158fbc68","addressRefs":[]},"805381e5-89e7-4fb9-bda7-a97e84b531ba":{"id":"805381e5-89e7-4fb9-bda7-a97e84b531ba","doc_no":"A.2.2.8.2.2.4","title":"Instance Ongoing Management Protocol","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1573,"content":"The documents herein define the process for the ongoing management of an Instance of the Integration Boost Primitive.","contentHash":"8e9dcabeb470b8289e70abac1e503e0afa2ff10d42f6529df4c8377d5ac86702","addressRefs":[]},"04864587-25ef-4179-b237-4dd0a23485a4":{"id":"04864587-25ef-4179-b237-4dd0a23485a4","doc_no":"A.2.2.8.2.2.4.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1574,"content":"The documents herein define the routine process for ongoing management of an Instance of the Integration Boost Primitive.","contentHash":"6c40875284d056f1ceeb63db321c795b3813c1ea58210b6a309acc84990fc90b","addressRefs":[]},"780719e8-ea6d-4ae1-b519-34d03be483df":{"id":"780719e8-ea6d-4ae1-b519-34d03be483df","doc_no":"A.2.2.8.2.2.4.1.1","title":"Process Definition For Integration Boost Calculation By Operational GovOps","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1575,"content":"The documents herein define the process for Integration Boost Calculation by Operational GovOps.","contentHash":"1e7985e5ed2c3be66f3812505ef506fa829f9937cd249fdf2b67cdd8125c8529","addressRefs":[]},"0930f2b1-38ae-415e-85e6-bf96c7bcb0cb":{"id":"0930f2b1-38ae-415e-85e6-bf96c7bcb0cb","doc_no":"A.2.2.8.2.2.4.1.1.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1576,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"52fc6ecc-d3c2-4c6e-babe-2a3bb0e10f22":{"id":"52fc6ecc-d3c2-4c6e-babe-2a3bb0e10f22","doc_no":"A.2.2.8.2.2.4.1.1.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1577,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"56e6b01b-5f00-4385-9876-951f3160cb70":{"id":"56e6b01b-5f00-4385-9876-951f3160cb70","doc_no":"A.2.2.8.2.2.4.1.1.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1578,"content":"This process is triggered at the end of each occurrence of the Cadence for each Instance of the Integration Boost Primitive with an Instance Status of `Active`.","contentHash":"07dbde98aed877b0a1d5eac70cbb9c67a370acb693659a8fe9e296d415ce31d6","addressRefs":[]},"fa1e98b5-18f4-4e9a-b008-50fb2906e35a":{"id":"fa1e98b5-18f4-4e9a-b008-50fb2906e35a","doc_no":"A.2.2.8.2.2.4.1.1.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1579,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"f8991663-df3f-49ea-9c96-d7c0f09d8ee8":{"id":"f8991663-df3f-49ea-9c96-d7c0f09d8ee8","doc_no":"A.2.2.8.2.2.4.1.1.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1580,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"fa744d67-6609-4b94-9126-dade273d3d4d":{"id":"fa744d67-6609-4b94-9126-dade273d3d4d","doc_no":"A.2.2.8.2.2.4.1.1.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1581,"content":"The process flow is defined herein:\n\n- At the end of each Integration Boost period, the data provider submits the net USDS deposit data to Powerhouse.\n- Operational GovOps verifies this data by checking on-chain balances and confirms that there are no discrepancies.\n- Operational GovOps then calculates the payout based on the net USDS deposit data and the Sky Savings Rate.","contentHash":"d187226157e4e97b0e5165e66906828727123346cac0e7d0d45a9f97be75419d","addressRefs":[]},"4c84f0a6-0d4d-4718-a7c4-04fa29fadfcc":{"id":"4c84f0a6-0d4d-4718-a7c4-04fa29fadfcc","doc_no":"A.2.2.8.2.2.4.1.1.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1582,"content":"The required Primitive Inputs to this process are specified herein.\n\n- Edit `Integration Boost Payments` Document (Active Data)\n    - Updated fields\n        - Status\n            - New value: set to `In Progress`\n        - Underlying data\n            - New value: populate with underlying data used to calculate the net deposits\n        - Net deposits\n            - New value: populate with calculated value\n        - Integration Boost payment due\n            - New value: populate with calculated value.\n    - Responsible party: Operational GovOps.\n    - Trigger-Process: [A.2.2.8.2.2.4.1.2 - Process Definition For Integration Boost Payment Issuance From Operational Executor Agent Buffer](16474cb5-8af4-4f11-b0c1-2c00f292cc2b).","contentHash":"d511e527e8817f3b6e4e8e29b49b1371431219c468a00c4ef8b80a4d410ed7df","addressRefs":[]},"08dd7788-9265-46f3-bc91-3215218bc69f":{"id":"08dd7788-9265-46f3-bc91-3215218bc69f","doc_no":"A.2.2.8.2.2.4.1.1.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1583,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"273db3f1-9da3-4ef9-a5a0-31d537a62bbd":{"id":"273db3f1-9da3-4ef9-a5a0-31d537a62bbd","doc_no":"A.2.2.8.2.2.4.1.1.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1584,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"b785cb0c-1ebb-438d-a5c4-c385e7446977":{"id":"b785cb0c-1ebb-438d-a5c4-c385e7446977","doc_no":"A.2.2.8.2.2.4.1.1.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1585,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified [A.2.2.8.2.2.4.1.1.3 - Required Primitive Inputs](4c84f0a6-0d4d-4718-a7c4-04fa29fadfcc) fully complete the Process.","contentHash":"576ff8676c9294a48d61ca3547191f8c884b7479118e24af1f0fbbc320c74789","addressRefs":[]},"16474cb5-8af4-4f11-b0c1-2c00f292cc2b":{"id":"16474cb5-8af4-4f11-b0c1-2c00f292cc2b","doc_no":"A.2.2.8.2.2.4.1.2","title":"Process Definition For Integration Boost Payment Issuance From Operational Executor Agent Buffer","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1586,"content":"The documents herein define the process for Integration Boost payment from the Operational Executor Agent Buffer.","contentHash":"24b7d1e168a3ba540fd5c2fdd5fa1d296ced300612d25dd5a872c4ef9d419db7","addressRefs":[]},"c12533a4-9e4c-4618-a02b-cd33178db95b":{"id":"c12533a4-9e4c-4618-a02b-cd33178db95b","doc_no":"A.2.2.8.2.2.4.1.2.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1587,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"fd914a13-4bc6-4bfe-a809-a440d1acd1fa":{"id":"fd914a13-4bc6-4bfe-a809-a440d1acd1fa","doc_no":"A.2.2.8.2.2.4.1.2.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1588,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"9c5455f3-5f3b-484d-a253-62e417d7779c":{"id":"9c5455f3-5f3b-484d-a253-62e417d7779c","doc_no":"A.2.2.8.2.2.4.1.2.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1589,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"358d4696-47d3-41a2-a34c-33e47487d3bb":{"id":"358d4696-47d3-41a2-a34c-33e47487d3bb","doc_no":"A.2.2.8.2.2.4.1.2.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1590,"content":"This process is triggered by the Required Primitive Inputs specified in Edit Integration Boost Payments Document (Active Data).","contentHash":"4a2d8c48a061f915d9437c44cbf04610d496ccbd47ef3c1fa779cfad8ef0d628","addressRefs":[]},"5cae5183-8c36-4d19-8db6-d6145b282fe6":{"id":"5cae5183-8c36-4d19-8db6-d6145b282fe6","doc_no":"A.2.2.8.2.2.4.1.2.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1591,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"f894a7d2-8ef7-4130-8955-5a939f6eb535":{"id":"f894a7d2-8ef7-4130-8955-5a939f6eb535","doc_no":"A.2.2.8.2.2.4.1.2.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1592,"content":"The process flow is defined herein.\n\n- Operational GovOps makes the payment to the reward address specified in the Primitive Instance from the Operational Executor Agent Buffer.\n- Operational GovOps updates the Powerhouse system with the transaction details.","contentHash":"69b5473438f2e1e95d2dea42fe02c29d91ba1b6e2509026cb60ec7ad0fb4eff9","addressRefs":[]},"862aff47-67fc-4b7f-bc16-b45b7edd9e83":{"id":"862aff47-67fc-4b7f-bc16-b45b7edd9e83","doc_no":"A.2.2.8.2.2.4.1.2.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1593,"content":"The required Primitive Inputs to this process are specified herein.\n\n- Edit `Integration Boost Payments` Document (Active Data)\n    - Updated fields\n        - Status\n            - New value: set to `Paid`\n        - Transaction Details/Amount Paid\n            - New value: populate with amount paid\n        - Transaction Details/Tx hash\n            - New value: populate with transaction hash\n    - Responsible Party: Operational GovOps\n    - Trigger - Process: [A.2.2.8.2.2.4.1.3 - Process Definition For Settlement Cycle And Core GovOps Review](d9c13a1a-aa81-483a-bc72-453d27980717).","contentHash":"668e81069397438080b6297f8ed85aa83306b0384ea1c06f5c882ae38ee21431","addressRefs":[]},"baa296a6-7b9c-4134-b6a2-648d8a24a9bc":{"id":"baa296a6-7b9c-4134-b6a2-648d8a24a9bc","doc_no":"A.2.2.8.2.2.4.1.2.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1594,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"7e7e516a-64d4-48fa-b138-11924474b48d":{"id":"7e7e516a-64d4-48fa-b138-11924474b48d","doc_no":"A.2.2.8.2.2.4.1.2.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1595,"content":"No Sky Core Atlas documents are updated as the output of this process.","contentHash":"c74753540934e4e9e7d0daf6dbf17e1250d25ae9fc052f93cf1f0c1400ec1035","addressRefs":[]},"f1e0fb16-7f7d-4b91-8a21-e87e21a92979":{"id":"f1e0fb16-7f7d-4b91-8a21-e87e21a92979","doc_no":"A.2.2.8.2.2.4.1.2.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1596,"content":"No Agent Artifact documents are updated as the output of this process. The requirements specified in [A.2.2.8.2.2.4.1.2.3 - Required Primitive Inputs](862aff47-67fc-4b7f-bc16-b45b7edd9e83) fully complete the process.","contentHash":"4e1cf0822eeca07b87125b5ad217f69ca38240878cbd34ef56280d3b1e886f1b","addressRefs":[]},"d9c13a1a-aa81-483a-bc72-453d27980717":{"id":"d9c13a1a-aa81-483a-bc72-453d27980717","doc_no":"A.2.2.8.2.2.4.1.3","title":"Process Definition For Settlement Cycle And Core GovOps Review","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1597,"content":"The documents herein define the process for the Integration Boost Settlement Cycle and Core GovOps review as part of ongoing management of an Instance of the Integration Boost Primitive.","contentHash":"23d24468deec7797c66b60e06995430bf2bb86ce1769083046afc2d5c9f7f164","addressRefs":[]},"0f8e3d69-eeb9-4ab7-9976-ad7fd93b9fb0":{"id":"0f8e3d69-eeb9-4ab7-9976-ad7fd93b9fb0","doc_no":"A.2.2.8.2.2.4.1.3.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1598,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"7ba12eff-207b-4060-9a3e-8db1908cf982":{"id":"7ba12eff-207b-4060-9a3e-8db1908cf982","doc_no":"A.2.2.8.2.2.4.1.3.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1599,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"44fb9520-c7e6-4a6a-8362-6c3a7b9fa765":{"id":"44fb9520-c7e6-4a6a-8362-6c3a7b9fa765","doc_no":"A.2.2.8.2.2.4.1.3.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1600,"content":"This process is triggered at the beginning of every calendar quarter.","contentHash":"a51098740bae49f00f5af381d4297577b9e72a9ffc5538c677c3faea9030ed53","addressRefs":[]},"30152570-8af2-4e2a-bab2-9dbb871a00f4":{"id":"30152570-8af2-4e2a-bab2-9dbb871a00f4","doc_no":"A.2.2.8.2.2.4.1.3.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1601,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"8f3b3d8b-57cb-4ecf-a264-7818cd01d9b2":{"id":"8f3b3d8b-57cb-4ecf-a264-7818cd01d9b2","doc_no":"A.2.2.8.2.2.4.1.3.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1602,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"841497f9-b592-4365-8221-3bdbb82b8d4a":{"id":"841497f9-b592-4365-8221-3bdbb82b8d4a","doc_no":"A.2.2.8.2.2.4.1.3.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1603,"content":"The process flow is defined herein.\n\n- Core GovOps reviews Integration Boost calculations, including underlying data and calculation of balances and rewards due.\n- Once Core GovOps has completed review, they update Powerhouse system to indicate that they confirm the accuracy of the Integration Boost amounts.","contentHash":"6653a3d8deed841a5434b20099262a5e6efd0bcc327c05c051426ce9751c3802","addressRefs":[]},"ebbfa305-4d56-45f4-8d06-180dc02cbb2f":{"id":"ebbfa305-4d56-45f4-8d06-180dc02cbb2f","doc_no":"A.2.2.8.2.2.4.1.3.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1604,"content":"The required Primitive Inputs to this process are specified herein.\n\n- Edit `Integration Boost Payments` Active Data Document\n    - Updated field\n        - Core GovOps Review/Confirmation\n            - New value: populate with yes or no.\n        - Core GovOps Review/Commentary\n            - New value: populate with reasoning (required if confirmation value is `No`)\n    - Responsible party: Core GovOps","contentHash":"9678826226081ab1e27660da646855a6f75a4736caf1778ac9ac84774a891ecb","addressRefs":[]},"5a0f038c-c710-4889-882a-a0cb040577a3":{"id":"5a0f038c-c710-4889-882a-a0cb040577a3","doc_no":"A.2.2.8.2.2.4.1.3.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1605,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"1f50ce0e-76f8-4436-820f-363bcf8fc017":{"id":"1f50ce0e-76f8-4436-820f-363bcf8fc017","doc_no":"A.2.2.8.2.2.4.1.3.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1606,"content":"The Sky Core Atlas documents specified herein are updated as the output of this process.","contentHash":"3325881a954b9bc0611bdbf656aa00be7816e4a7d3333829a7ad413fd5f62bff","addressRefs":[]},"0f50e796-9486-42cd-a98d-b284f8340307":{"id":"0f50e796-9486-42cd-a98d-b284f8340307","doc_no":"A.2.2.8.2.2.4.1.3.4.1.1","title":"Sky Core Integration Boost Reimbursement Active Data Document Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1607,"content":"The document in the Sky Core Atlas is updated as follows:\n\n- Updated Fields\n    - Status\n        - New value: populate with `Pending Payment`\n    - Confirmed Reimbursement Due\n        - New value: populate with total Reimbursement amount\n    - Reward Period\n        - New Value: populate with reward period\n    - Operational Executor Agent\n        - New value: Populate with name of Operational Executor Agent\n    - Prime Agent\n        - New value: Populate with name of Prime Agent.\n- Responsible Party: Core GovOps\n- Triggers: [A.2.2.8.2.2.4.1.4 - Process Definition For Executive Vote Reimbursement](c40a0708-12e4-46da-89d7-0e5a3a839455).","contentHash":"871569c7e36e8d3dcb95d82beba76bfcba18931856423f0c423cca843005f76e","addressRefs":[]},"43aedc35-e90a-48ca-a0fc-346ced2bea0b":{"id":"43aedc35-e90a-48ca-a0fc-346ced2bea0b","doc_no":"A.2.2.8.2.2.4.1.3.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1608,"content":"No Agent Artifact documents are updated as the output of this process.","contentHash":"454c32a6d9945855f1957b9da47e18d80fe986f357e256d293d6e7d557905208","addressRefs":[]},"c40a0708-12e4-46da-89d7-0e5a3a839455":{"id":"c40a0708-12e4-46da-89d7-0e5a3a839455","doc_no":"A.2.2.8.2.2.4.1.4","title":"Process Definition For Executive Vote Reimbursement","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1609,"content":"The documents herein define the process for Integration Boost Executive Vote reimbursement as part of ongoing management of an Instance of the Integration Boost Primitive.","contentHash":"7019ac7fbf9742ffcd8089426ba3981ddf9efbc66c2fa9b5f10d90c03f182b7b","addressRefs":[]},"6dac32e6-593c-44db-908b-9075c8dd68ca":{"id":"6dac32e6-593c-44db-908b-9075c8dd68ca","doc_no":"A.2.2.8.2.2.4.1.4.1","title":"Process Initiation Logic","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1610,"content":"The process initiation logic is specified herein.","contentHash":"77f27a70df330bd61e2198a486cfc861daa10bf893203adc4a883761a4dec140","addressRefs":[]},"dea4f41d-b36b-421f-be80-3f495532ab7a":{"id":"dea4f41d-b36b-421f-be80-3f495532ab7a","doc_no":"A.2.2.8.2.2.4.1.4.1.1","title":"Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1611,"content":"Triggers are specified herein.","contentHash":"e761de23eed5b0bb94a253544d5343c883f276ded0bbcd66cc572f46f929b7db","addressRefs":[]},"fa1aab6f-61a8-493f-b282-6a0e3f64ce29":{"id":"fa1aab6f-61a8-493f-b282-6a0e3f64ce29","doc_no":"A.2.2.8.2.2.4.1.4.1.1.1","title":"Time-Based Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1612,"content":"None.","contentHash":"f91ad97d2c154b84b63397045975e4cda84b3460b7e325463b232c5ab5d38914","addressRefs":[]},"ee6adeb0-b3e5-4d0f-8d1a-b9fdc1510074":{"id":"ee6adeb0-b3e5-4d0f-8d1a-b9fdc1510074","doc_no":"A.2.2.8.2.2.4.1.4.1.1.2","title":"Document Update Triggers","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1613,"content":"This process is triggered by the Document Update specified in [A.2.2.8.2.2.4.1.3.4.1.1 - Sky Core Integration Boost Reimbursement Active Data Document Update](0f50e796-9486-42cd-a98d-b284f8340307).","contentHash":"e639896e77d5015ffe0b6621e49ca57e73abd7ab54724ad8615c8b22ff3b042f","addressRefs":[]},"10cb9c97-e21b-4ad2-af48-eb2fa577aded":{"id":"10cb9c97-e21b-4ad2-af48-eb2fa577aded","doc_no":"A.2.2.8.2.2.4.1.4.1.2","title":"Dependencies","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1614,"content":"This process has no dependencies.","contentHash":"6691fd925283c27879519edd8ca16270f92f6049cde3c79125731aecdc0113c0","addressRefs":[]},"9cb825c8-871f-47b7-9918-e48fe2a34d26":{"id":"9cb825c8-871f-47b7-9918-e48fe2a34d26","doc_no":"A.2.2.8.2.2.4.1.4.2","title":"Process Flow","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1615,"content":"The process flow is defined herein:\n\n- Core GovOps includes the Integration Boost reimbursement in the next standard Executive Vote.\n- After the Executive Vote passes, Core GovOps updates the Powerhouse system with the transaction details.","contentHash":"6446f21524951818d70444013b2272a734e6f94db33ffd21b26d0352cd3d4dfe","addressRefs":[]},"f54de74a-4208-4878-8049-3184ab3f9a0d":{"id":"f54de74a-4208-4878-8049-3184ab3f9a0d","doc_no":"A.2.2.8.2.2.4.1.4.3","title":"Required Primitive Inputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1616,"content":"The required Primitive Inputs to this process are specified herein and organized as sequential stages.\n\n- Core GovOps adds reimbursement to Executive Vote\n    - Edit `Sky Core Integration Boost Reimbursement Amounts`\n        - Updated fields\n            - Executive Vote Settlement/Executive Vote\n                - New value: links to proposal\n            - Status\n                - New value: set to `Added to Executive Vote`\n- After Executive Vote passes, Core GovOps updates Powerhouse system\n    - Edit `Sky Core Integration Boost Reimbursement Amounts`\n        - Updated fields\n            - Executive Vote Settlement / Transaction Details/ Amount Paid\n                - New value: populate with amount paid to reimburse Operational Executor Agent Buffer.\n            - Executive Vote Settlement / Transaction Details / Tx Hash\n                - New value: Populate with transaction hash\n            - Status\n                - New value: set to `Completed`","contentHash":"982a36971eb676fcc85d17c32f1f4c41df5b4b64f72c5d134910140c47181fbc","addressRefs":[]},"8d00d8df-f970-4b2e-8da9-3b9fe2af9e2b":{"id":"8d00d8df-f970-4b2e-8da9-3b9fe2af9e2b","doc_no":"A.2.2.8.2.2.4.1.4.4","title":"Required Outputs","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1617,"content":"The documents herein specify the required outputs from this process.","contentHash":"51bc6ebb26844d15e2817dfcc58bf81accd0c4fe513f2b6698481b79a12972f2","addressRefs":[]},"9478c3d6-ce1d-4c73-a479-9127b5c245e1":{"id":"9478c3d6-ce1d-4c73-a479-9127b5c245e1","doc_no":"A.2.2.8.2.2.4.1.4.4.1","title":"Sky Core Atlas Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1618,"content":"The Sky Core Atlas documents specified herein are updated as the output of this process.","contentHash":"3325881a954b9bc0611bdbf656aa00be7816e4a7d3333829a7ad413fd5f62bff","addressRefs":[]},"0ab76a83-ca8d-4ebf-83c1-b7e7dced0970":{"id":"0ab76a83-ca8d-4ebf-83c1-b7e7dced0970","doc_no":"A.2.2.8.2.2.4.1.4.4.1.1","title":"Sky Core Integration Boost Reimbursement Active Data Document Update","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1619,"content":"The Document in the Sky Core Atlas is updated as follows:\n\n- Updated fields\n    - Status\n        - New value: set to `Paid`\n    - Responsible Party: Core GovOps\n    - Trigger-Process: None","contentHash":"9a6ccea37087066b69215a54a5e0e3aa7fe7c0ee887f3de2e531941a9bec9f63","addressRefs":[]},"39aba7ed-95ff-4247-acb7-61032649b218":{"id":"39aba7ed-95ff-4247-acb7-61032649b218","doc_no":"A.2.2.8.2.2.4.1.4.4.2","title":"Agent Artifact Updates","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1620,"content":"No Agent Artifact documents are updated as the output of this process.","contentHash":"454c32a6d9945855f1957b9da47e18d80fe986f357e256d293d6e7d557905208","addressRefs":[]},"9cdac621-4677-4c79-8372-68e0a778c27d":{"id":"9cdac621-4677-4c79-8372-68e0a778c27d","doc_no":"A.2.2.8.2.2.4.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1621,"content":"The documents herein define processes for handling non-routine situations in the ongoing management of an Instance of the Integration Boost Primitive.","contentHash":"2ce9dc565f60c1b512eb8758fa1bcfb0ec65de279fa74a937117494bb26b10fd","addressRefs":[]},"0bbeab5f-ca17-463a-a9a4-9ab588347a0c":{"id":"0bbeab5f-ca17-463a-a9a4-9ab588347a0c","doc_no":"A.2.2.8.2.2.4.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"eecfa6ad-3419-411e-b25a-1ccde2d6484b","order":1622,"content":"The documents herein define processes for handling emergency situations in the ongoing management of an Instance of the Integration Boost Primitive.","contentHash":"28e6b5fea893d264ed4fd857d4977b84b92d4aadd93298d786bcd75317f4fe51","addressRefs":[]},"4c7be4c6-44b5-407a-94ae-3d7ca7e8039c":{"id":"4c7be4c6-44b5-407a-94ae-3d7ca7e8039c","doc_no":"A.2.2.8.3","title":"Pioneer Chain Primitive","type":"Core","depth":4,"parentId":"26415305-432d-423b-9553-3f325279712d","order":1623,"content":"The documents herein govern the Pioneer Chain Primitive.","contentHash":"fb265cdbfcab86464d9741d128974435011c8c94facc462c7d2adc30adab5768","addressRefs":[]},"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa":{"id":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","doc_no":"A.2.2.8.3.1","title":"Introduction","type":"Core","depth":5,"parentId":"4c7be4c6-44b5-407a-94ae-3d7ca7e8039c","order":1624,"content":"The documents herein provide an introduction to the Pioneer Chain Primitive.","contentHash":"3eea91ce5c5c1817300bffef76fb7e8f353a4af7a42b63bfed1593ceaeb281fd","addressRefs":[]},"219459b3-8333-4e9a-9b79-55e0c20d6dbb":{"id":"219459b3-8333-4e9a-9b79-55e0c20d6dbb","doc_no":"A.2.2.8.3.1.1","title":"Pioneer Prime Requirements","type":"Core","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1625,"content":"Pioneer Primes must be designated by the official team or foundation of the Pioneer Chain. It is only possible for a Pioneer Chain to have a Pioneer Prime once, and for a Pioneer Prime to have the Pioneer Prime status with a single blockchain, once.","contentHash":"2fed8e5e3eb75d5f7e0045c4f1070fe7a5332e51cadb2793b119bf82d1fee37f","addressRefs":[]},"d6d16076-da22-43f1-a303-627af41b486c":{"id":"d6d16076-da22-43f1-a303-627af41b486c","doc_no":"A.2.2.8.3.1.2","title":"Pioneer Prime Designation Process","type":"Core","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1626,"content":"In order to be confirmed as a Pioneer Prime, a Prime Agent must provide written proof to Operational GovOps that it has been provisionally designated as such by the official team or foundation of the relevant Pioneer Chain. Following a check by Operational GovOps to ensure that the Prime Agent has not been a Pioneer Prime previously and that the Pioneer Chain has not had a Pioneer Prime before, Operational GovOps will add the new Pioneer Prime to the list of Active Pioneer Primes. See [A.2.2.8.3.1.2.1.0.6.1 - List of Active Pioneer Primes](f2ecf6a4-4d5f-4443-b25c-3bd10b1af82e).","contentHash":"06b5c56ba4fa6f5fcf7ceaf6872807c49248e0319ec952bb42969d79fe920f50","addressRefs":[]},"65fc0b79-8827-403d-80ee-9f74a6be1069":{"id":"65fc0b79-8827-403d-80ee-9f74a6be1069","doc_no":"A.2.2.8.3.1.2.1","title":"Active Pioneer Primes","type":"Active Data Controller","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1627,"content":"Active Pioneer Primes are Prime Agents who have been designated by the official team or foundation of the Pioneer Chain and confirmed as Pioneer Primes by Operational GovOps. The list of Current Pioneer Primes is defined as Active Data in [A.2.2.8.3.1.2.1.0.6.1 - List of Active Pioneer Primes](f2ecf6a4-4d5f-4443-b25c-3bd10b1af82e).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"e77f36c246d6f74d7fba6eb128200767be9e24f65d5fa30f7b2296840cfe2dd5","addressRefs":[]},"f2ecf6a4-4d5f-4443-b25c-3bd10b1af82e":{"id":"f2ecf6a4-4d5f-4443-b25c-3bd10b1af82e","doc_no":"A.2.2.8.3.1.2.1.0.6.1","title":"List of Active Pioneer Primes","type":"Active Data","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1628,"content":"The current Active Pioneer Primes are:\n\n- Keel\n- Grove\n- Launch Agent 6","contentHash":"829a01f25fcca6d5149ba22cdbca5e11a8ed057bcec2447ac43a10e13a541b1d","addressRefs":[]},"f0d5ab5e-bf35-4a9d-a73f-d82baac6e604":{"id":"f0d5ab5e-bf35-4a9d-a73f-d82baac6e604","doc_no":"A.2.2.8.3.1.3","title":"Pioneer Prime Benefits","type":"Core","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1629,"content":"Pioneer Primes gain benefits and responsibilities related to the general adoption of USDS on the Pioneer Chain, and this benefit comes in two forms.\n\nFirst, during the Pioneer Phase, the Pioneer Prime counts as having tagged, for the purposes of calculating the Distribution Reward, all USDS and sUSDS accounts and balances on the Pioneer Chain that have not been tagged by another Prime. At the end of the Pioneer Phase, all untagged USDS accounts and balances are one-time tagged by the Pioneer Prime, and this tag will remain normally for the following ten (10) years unless tagged by a different Prime, or retagged.\n\nSecond, during the Pioneer Phase, all Unrewarded USDS bridged to the Pioneer Chain counts towards Pioneer Incentive payments, see [A.2.2.8.3.1.4 - Pioneer Incentive Pool](04edac33-19d5-4a87-a8ab-945a0cd57771).","contentHash":"d579d22f3c70b3f68928b8788f92064bfabf031ec3a6a302be4d763706779233","addressRefs":[]},"0c7b0644-68d4-441d-8221-88382a6515e4":{"id":"0c7b0644-68d4-441d-8221-88382a6515e4","doc_no":"A.2.2.8.3.1.3.1","title":"Pioneer Phase","type":"Core","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1630,"content":"For purposes of [A.2.2.8.3.1.3 - Pioneer Prime Benefits](f0d5ab5e-bf35-4a9d-a73f-d82baac6e604), the Pioneer Phase is a period beginning on the date that a Prime Agent satisfies the Pioneer Prime Requirements specified in [A.2.2.8.3.1.1 - Pioneer Prime Requirements](219459b3-8333-4e9a-9b79-55e0c20d6dbb) and ending three (3) years thereafter.","contentHash":"2dcb783c7b17b1f0995b6028f07dcbbfecc6ebb8c999184b5dc39e71aa00dd26","addressRefs":[]},"04edac33-19d5-4a87-a8ab-945a0cd57771":{"id":"04edac33-19d5-4a87-a8ab-945a0cd57771","doc_no":"A.2.2.8.3.1.4","title":"Pioneer Incentive Pool","type":"Core","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1631,"content":"All Pioneer Incentive payments are paid through the Monthly Settlement Cycle. Each Monthly Settlement Cycle, an amount of funds equivalent to the Sky Savings Rate multiplied by the balance of Unrewarded USDS is paid into a separate account controlled by the Pioneer Prime (the \"Pioneer Incentive Pool\"). The Pioneer Prime retains one hundred percent (100%) of the funds in the Pioneer Incentive Pool.","contentHash":"6306f40a37393884941726a9220f9cd279c9dc6593bef1260f5b85af70172398","addressRefs":[]},"15e14f25-8d56-4699-ac37-0cef4f0503c5":{"id":"15e14f25-8d56-4699-ac37-0cef4f0503c5","doc_no":"A.2.2.8.3.1.4.1","title":"Pre-Pioneer Incentive Pool","type":"Core","depth":6,"parentId":"4aab68fd-0e8c-4781-b6f6-f94a89cb22fa","order":1632,"content":"A Pre-Pioneer Incentive Pool is a temporary, chain-specific incentive mechanism designed to bootstrap USDS adoption on a new blockchain before a formal Pioneer Prime is established for that chain. It allows a designated Agent to direct incentive payments to ecosystem partners on that specific chain. The Pre-Pioneer Incentive Pool may operate under distinct rules that differ from the standard Pioneer Incentive Pool, which rules will be specified in an Ecosystem Accord between the respective Agent and Sky Core. A Pre-Pioneer Incentive Pool serves as a transitional phase until the conditions for a formal Pioneer Incentive Pool are met. See [A.2.2.8.3.1.4 - Pioneer Incentive Pool](04edac33-19d5-4a87-a8ab-945a0cd57771).","contentHash":"2f15aa45181392158156c036b6a0f74bc8dc4f3fa4ebceb6b8f2390ef0fde08d","addressRefs":[]},"d1142876-33c2-4e21-9339-d8711525d46f":{"id":"d1142876-33c2-4e21-9339-d8711525d46f","doc_no":"A.2.2.9","title":"Supply Side Stablecoin Primitives","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1633,"content":"Supply Side Stablecoin Primitives are Sky Primitives focused on capital allocation and risk management.","contentHash":"1dbe2ee6bee96bbe1cdf718d6139b49af4c9bcfa290e35aed7526719deb916fe","addressRefs":[]},"9db14ab7-bb4b-4751-8084-843bd4359f2a":{"id":"9db14ab7-bb4b-4751-8084-843bd4359f2a","doc_no":"A.2.2.9.1","title":"Allocation System Primitive","type":"Core","depth":4,"parentId":"d1142876-33c2-4e21-9339-d8711525d46f","order":1634,"content":"The Allocation System Primitive is the base mechanism that enables Prime Agents to put up Risk Capital to deploy USDS collateral into different opportunities that provide risk-adjusted return, by borrowing at the Base Rate from Sky, and following Asset Liability Management restrictions on the liquidity of deployed assets.","contentHash":"80f895e5ceac23dcd409d8afc750a1a6f16a29e6c5eaad5ec9461e8851df0968","addressRefs":[]},"823a12c3-45d2-438a-b061-46ecd09cdca8":{"id":"823a12c3-45d2-438a-b061-46ecd09cdca8","doc_no":"A.2.2.9.1.1","title":"Allocation System Process Definition","type":"Core","depth":5,"parentId":"9db14ab7-bb4b-4751-8084-843bd4359f2a","order":1635,"content":"The documents herein define the process for initial setup and ongoing management of an Allocation Instance (alternatively referred to as \"conduits\") as part of the Allocation System Primitive.","contentHash":"67ebe1e0db3f580089e6db3506fa72bc9bdf46063fe9b1e85be6bc1fe7a0086e","addressRefs":[]},"39f3ceee-2e0b-41b2-ad62-85cac3895cb0":{"id":"39f3ceee-2e0b-41b2-ad62-85cac3895cb0","doc_no":"A.2.2.9.1.1.1","title":"Base Elements","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1636,"content":"The documents herein define base elements of the Allocation System Primitive.","contentHash":"96a7383bd730a2b23c53c27a7881087225ce2c8b8d24a7d3ad67acbf11880394","addressRefs":[]},"b3fb8653-8503-4a9e-81b2-5e9f49ad6703":{"id":"b3fb8653-8503-4a9e-81b2-5e9f49ad6703","doc_no":"A.2.2.9.1.1.1.1","title":"Sky Direct Exposures","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1637,"content":"Sky Direct Exposures are exposures that are held directly by Sky but implemented through the Allocation System of a Prime Agent. The documents herein define the rules for Sky Direct Exposures.","contentHash":"1546264aac47a862d734eb2bf29c5d1a74e30573846dc4d62d1a6fa44628da1a","addressRefs":[]},"3161489a-11bd-4dea-b676-09d0cce45ae9":{"id":"3161489a-11bd-4dea-b676-09d0cce45ae9","doc_no":"A.2.2.9.1.1.1.1.1","title":"Designation Process","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1638,"content":"Sky Direct Exposures are designated by the Core Facilitator in consultation with the Core Council Risk Advisor via posts to the Sky Forum under the \"Sky Core\" category. Sky Direct Exposures are recorded in [A.2.2.9.1.1.1.1.2.0.6.1 - List Of Current Sky Direct Exposures](5f368e33-7a82-4244-a9ba-f285193ec043) and must specify the asset that is being designated as a Sky Direct Exposure and the Prime Agent responsible for implementing the exposure.","contentHash":"71e5dfbe3c30d95389535ac8268e39d3edba51634412b86c2fc092a9a79c355b","addressRefs":[]},"1c0410e4-fe36-4a01-8b82-8ea74f67fbec":{"id":"1c0410e4-fe36-4a01-8b82-8ea74f67fbec","doc_no":"A.2.2.9.1.1.1.1.2","title":"Current Sky Direct Exposures","type":"Active Data Controller","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1639,"content":"The list of current Sky Direct Exposures is defined as Active Data in [A.2.2.9.1.1.1.1.2.0.6.1 - List Of Current Sky Direct Exposures](5f368e33-7a82-4244-a9ba-f285193ec043).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Facilitator.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"a5aa59b42a13589a47f48a5006900f2bdf8466ac80e94366f2d9a26ae623fea6","addressRefs":[]},"5f368e33-7a82-4244-a9ba-f285193ec043":{"id":"5f368e33-7a82-4244-a9ba-f285193ec043","doc_no":"A.2.2.9.1.1.1.1.2.0.6.1","title":"List Of Current Sky Direct Exposures","type":"Active Data","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1640,"content":"The current Sky Direct Exposures are:\n\n- Treasury Bills - Investments by Grove in BUIDL, JTRSY, and USTB on Ethereum Mainnet\n- Peg Stability Modules - Investments by Spark or Grove in USDC in Peg Stability Modules on blockchains other than Ethereum Mainnet\n- Curve Pools - Investments by Spark in USDT in sUSDS/USDT Curve pools","contentHash":"8ab8065288ca73abc086af2f569486bc384a042a7a8a7d7f259259e7bce1ff18","addressRefs":[]},"cbd64e6c-547b-4b8d-a0cb-b605f780aef1":{"id":"cbd64e6c-547b-4b8d-a0cb-b605f780aef1","doc_no":"A.2.2.9.1.1.1.1.3","title":"Parameters For Sky Direct Exposures","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1641,"content":"The Core Facilitator sets the following parameters for Sky Direct Exposures in consultation with the Core Council Risk Advisor:\n\n- Rate limits; and\n- Aggregate exposure limits.\n\nThe Core Facilitator must post the initial values for these parameters and any updates to them to the Sky Forum under the \"Sky Core\" category. The values for the parameters for Sky Direct Exposures are set by the Core Facilitator and supersede any values for these parameters specified in the Risk Framework.","contentHash":"280f2654e5ebbcc5ef1c59406071260a799650ff72d156544cd79b8b4d6c29b3","addressRefs":[]},"8bd63c6b-b9ad-46e3-beb0-77c4a47bcd6d":{"id":"8bd63c6b-b9ad-46e3-beb0-77c4a47bcd6d","doc_no":"A.2.2.9.1.1.1.1.3.1","title":"Treatment Of Exposures In Excess Of Aggregate Exposure Limit","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1642,"content":"Any investments in assets that would otherwise qualify as Sky Direct Exposures by a Prime Agent in excess of the aggregate exposure limit are not Sky Direct Exposures and are subject to the customary requirements pursuant to [A.2.4 - Sky Core Monthly Settlement Cycle](6f8d5065-d6ff-4add-9a28-eadeffa7ed1a) and [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"3343444aac16a441aa820d8059233466c094fc0d332921b3fd4e71785c30027d","addressRefs":[]},"07e0f716-ce23-4394-a5f4-bee537713f48":{"id":"07e0f716-ce23-4394-a5f4-bee537713f48","doc_no":"A.2.2.9.1.1.1.1.4","title":"Revenue Sharing For Sky Direct Exposures","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1643,"content":"Because Sky Direct Exposures are held by Sky rather than the Prime Agent implementing the exposure through its Allocation System, Prime Agents are not required to pay the Agent Credit Line Borrow Rate with respect to funds borrowed to finance Sky Direct Exposures. All yield on Sky Direct Exposures is also due exclusively to Sky and is not retained by the Prime Agent. This is implemented as an adjustment to the Monthly Settlement Cycle.","contentHash":"dea766bd2c89267963c5de3844fb9d2f884272b7e71991b52aa54ace56806c1c","addressRefs":[]},"b683953e-d9b0-4e15-a405-978ef1854870":{"id":"b683953e-d9b0-4e15-a405-978ef1854870","doc_no":"A.2.2.9.1.1.1.1.5","title":"No Risk Capital Requirements With Respect To Sky Direct Exposures","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1644,"content":"Because Sky Direct Exposures are held by Sky rather than the Prime Agent implementing the exposure through its Allocation System, Prime Agents are not required to hold any Risk Capital with respect to Sky Direct Exposures.","contentHash":"948042e40f361262ca7ced9b00bb9044f70a9df591116925f7005fd6fb8b1231","addressRefs":[]},"bfb8013f-9226-4426-84bf-4b0e03b44107":{"id":"bfb8013f-9226-4426-84bf-4b0e03b44107","doc_no":"A.2.2.9.1.1.1.1.6","title":"No Actively Stabilizing Collateral Requirements With Respect To Sky Direct Exposures","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1645,"content":"Because Sky Direct Exposures are held by Sky rather than the Prime Agent implementing the exposure through its Allocation System, Prime Agents are not required to hold any Actively Stabilizing Collateral with respect to Sky Direct Exposures. Sky Direct Exposures also do not count towards satisfying a Prime Agent’s Actively Stabilizing Collateral requirements.","contentHash":"b4488e781569d3f2be8e9e2c744156d46cc91368b7b1b9af7b87704edb06bafa","addressRefs":[]},"a8a3e54d-980e-435d-9e08-0e5775af9aa3":{"id":"a8a3e54d-980e-435d-9e08-0e5775af9aa3","doc_no":"A.2.2.9.1.1.1.2","title":"Liquidity Layer Parameter Definitions","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1646,"content":"The documents herein define common parameters of implementations of the Allocation System based on the Spark Liquidity Layer, including the Grove Liquidity Layer.","contentHash":"119c68c7791cde740c2c0c4ccb479972c9f0c10ca39935421a97e2f26ebe90b5","addressRefs":[]},"a578830d-18f0-451c-8ff0-4a66094650ae":{"id":"a578830d-18f0-451c-8ff0-4a66094650ae","doc_no":"A.2.2.9.1.1.1.2.1","title":"Rate Limiter","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1647,"content":"Rate Limiter refers to the overall mechanism or system that limits the volume of token movements over time, implemented via the `RateLimits` contracts. The Rate Limiter manages multiple rate limits and enforces constraints on controller operations to prevent rapid asset drainage and mitigate risks from compromised relayers or other attacks. This ensures that the maximum amount of tokens processed within a specific time period stays within safe bounds. The `RateLimits` contracts and their addresses for each chain can be found in the Allocation System Primitive for a Prime, under ALM Contracts.","contentHash":"6725d5ea766504be2ef622077becd07ceb7e12f0ca2070be5a800cf68a45d826","addressRefs":[]},"8efb0a11-b798-48eb-af19-f65b38f039b5":{"id":"8efb0a11-b798-48eb-af19-f65b38f039b5","doc_no":"A.2.2.9.1.1.1.2.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1648,"content":"Rate limits set the maximum allowable amount of tokens that can be processed for specific operations within a given time period. Each rate limit contains the rate limit data: `maxAmount`, `slope`, `lastAmount` and `lastUpdated`. The current rate limit is calculated using the formula:\n\n`currentRateLimit = min(slope * (block.timestamp - lastUpdated) + lastAmount, maxAmount)`.\n\nThe rate limit data `maxAmount` and `slope` are configurable parameters that are set and modified by Governance. The rate limit data `lastAmount` and `lastUpdated` are internal state data dynamically tracked by the Rate Limiter to perform its calculations.\n\nRate limits set caps on the rate of allocation to a given Instance, they do not act as a limit on the total amount that may be allocated to that Instance.","contentHash":"a79331e6bf54cd895b7107541f4132cd2699f2bec044f7e9a28b8c33c4eab5a6","addressRefs":[]},"8b5f1ffd-9dfd-4aa0-8fc2-638a79d9fadb":{"id":"8b5f1ffd-9dfd-4aa0-8fc2-638a79d9fadb","doc_no":"A.2.2.9.1.1.1.2.2.1","title":"MaxAmount","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1649,"content":"`maxAmount` sets a hard cap on the level of allocation to an Instance at any given time. It sets the absolute rate limit regardless of how much time has passed since the last allocation. For example, if `maxAmount` is set to 1,000,000 tokens, the rate limit will increase over time at the rate determined by the `slope` until it reaches 1,000,000 tokens. At this point the rate limit will stop increasing, but it will resume increasing once an allocation to the Instance has been made.","contentHash":"335672f23ce598002f4df0e4df458015c9aed51d039a25787ce4da602342e12c","addressRefs":[]},"ae8674bc-44ac-4b95-b5df-c6322a1d6e9a":{"id":"ae8674bc-44ac-4b95-b5df-c6322a1d6e9a","doc_no":"A.2.2.9.1.1.1.2.2.2","title":"Slope","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1650,"content":"`slope` is the linear refill rate of a rate limiter’s allowance over time. It defines how quickly the capacity to perform additional inflow or outflow accrues after prior consumption. For example, if the slope is set to 1,000,000 tokens per day (converted to per second for on-chain execution), the rate limit will recover at that rate until it reaches the maxAmount.","contentHash":"edf1a2ac6920ea5d803599e0925fc38d583905bcf51383942be6b763600cc1d1","addressRefs":[]},"8d0419a4-50c5-4a7b-b68e-84d8c9243694":{"id":"8d0419a4-50c5-4a7b-b68e-84d8c9243694","doc_no":"A.2.2.9.1.1.1.2.2.3","title":"LastUpdated","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1651,"content":"`lastUpdated` is the timestamp when the rate limit was last updated, serving as the reference point for calculating time-elapsed refills in the formula.","contentHash":"6458c70ba2d924a70a12d2c002850775a40d2a16ad034e417e250ff72b962953","addressRefs":[]},"02918cfc-5d10-41bc-bb8a-0be9df76cbac":{"id":"02918cfc-5d10-41bc-bb8a-0be9df76cbac","doc_no":"A.2.2.9.1.1.1.2.2.4","title":"LastAmount","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1652,"content":"`lastAmount` is the remaining allowance available at the last update, used to compute the current rate limit by adding accrued capacity.","contentHash":"368e1a2ec855fe597c64ac765f1a1de7dd3dafa6d068b6c001b57560000259fc","addressRefs":[]},"d59a233c-11b9-4140-b15f-51df37475fd8":{"id":"d59a233c-11b9-4140-b15f-51df37475fd8","doc_no":"A.2.2.9.1.1.1.2.3","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1653,"content":"Inflow rate limits constrain the rate at which allocated liquidity can increase into a scope. \"Inflow\" means movements that raise exposure or capital allocated to an Instance or market, such as depositing, minting, or rebalancing into a position.","contentHash":"7185200c270e2205e386750d584ff342d50eb8dea5f25e7d2930cf5f4c51b9e4","addressRefs":[]},"e50fd86a-ffa4-4387-b212-420730a8d171":{"id":"e50fd86a-ffa4-4387-b212-420730a8d171","doc_no":"A.2.2.9.1.1.1.2.4","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1654,"content":"Outflow Rate Limits constrain the rate at which allocated liquidity can be withdrawn or exposure reduced from a scope. \"Outflow\" means movements that lower exposure or capital allocated to an Instance or market, such as withdrawals, redemptions, or unwind operations.\n\nOutflow limits are often configured more permissively to prioritize safety and fast exits. When outflow limits are \"unlimited,\" the rate limits contract simply does not apply a cap in that direction.","contentHash":"aedaf841f3c908d852ce3f31051cd31b8fba4f3aab4296fd1c2173bc79052d3d","addressRefs":[]},"b95b3bd8-d316-43d5-af56-df38d557aea3":{"id":"b95b3bd8-d316-43d5-af56-df38d557aea3","doc_no":"A.2.2.9.1.1.1.2.5","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1655,"content":"A `Rate Limit ID` is a bytes32 key that uniquely identifies a rate limit. Rate Limit IDs allow the system to maintain independent allowance state for each relevant transaction.","contentHash":"7bdc6cf9cf057f3babaf17bb85472f8d237290c17b4b5e5b9e6fa80f59f7342a","addressRefs":[]},"7c6da187-7d17-42ae-8c64-8d828ee83ea7":{"id":"7c6da187-7d17-42ae-8c64-8d828ee83ea7","doc_no":"A.2.2.9.1.1.1.2.6","title":"MaxSlippage","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1656,"content":"`maxSlippage` is a configurable parameter that sets the maximum allowed price impact or deviation from expected output when executing trades or liquidity operations in a pool. `maxslippage` is expressed as a decimal and must be a non-zero value. This protects against excessive price impact during volatile market conditions.","contentHash":"ca2676c7bb217c24c80567c9d0a1f3aa76a454f65129dad90c3cf10719d7c2e6","addressRefs":[]},"f47513f6-34e4-40a4-b7ff-8d68d75070be":{"id":"f47513f6-34e4-40a4-b7ff-8d68d75070be","doc_no":"A.2.2.9.1.1.2","title":"Allocation Instance Setup Process Definition","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1657,"content":"The documents herein define the process for setting up an Allocation Instance as part of the Allocation System Primitive.","contentHash":"17952666ff3f21ef2de7caa9662a9907d2693f0f0563c51a0a513f1ca948f858","addressRefs":[]},"eeeeb5ff-3f11-4857-a3da-ad354569f833":{"id":"eeeeb5ff-3f11-4857-a3da-ad354569f833","doc_no":"A.2.2.9.1.1.2.1","title":"Real World Agreements And Planning","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1658,"content":"The documents herein define the preliminary, off-chain human coordination stage of setting up an Allocation Instance.","contentHash":"9204bed73bf389cad51cf6d78d2a3168e435558b72052914ec58efd431666872","addressRefs":[]},"b60b170f-9e8c-4577-a046-313039ff25ba":{"id":"b60b170f-9e8c-4577-a046-313039ff25ba","doc_no":"A.2.2.9.1.1.2.1.1","title":"Initial Concept And Feasibility Discussions","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1659,"content":"The Prime Agent identifies a yield opportunity on a target chain that can exceed the Base Rate. The Prime Agent estimates Required Risk Capital (RRC) and Asset Liability Management requirements associated with the opportunity and evaluates options for fulfilling them. The Prime Agent also considers exchange and bridging costs, if applicable. Based on this, the Prime Agent develops a net yield target for the opportunity factoring in all of these costs. The output of this step is an internal meeting note summarizing the idea as well as estimates of Required Risk Capital, Asset Liability Management, and exchange / bridging costs.","contentHash":"540997a10431250e6036b418408f4fd87d9afd3b4b5ef64ca2d348c9d8ede960","addressRefs":[]},"8d3b553c-440d-4c67-b661-37ab1edc1c58":{"id":"8d3b553c-440d-4c67-b661-37ab1edc1c58","doc_no":"A.2.2.9.1.1.2.1.2","title":"Preliminary Required Risk Capital and Asset Liability Management Arrangement","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1660,"content":"If necessary, the Prime Agent reaches out to other Prime Agents that could provide Junior Risk Capital (JRC) / Senior Risk Capital (SRC) or assume Asset Liability Management obligations. The Prime Agent negotiates with these other Prime Agents and documents these potential deals. The output of this step is an informal confirmation of JRC/SRC and Asset Liability Management transfer details.","contentHash":"e673e7e6756f98adfe7876197f257c0c7514ad2f7b91cade6986c4c6520f021e","addressRefs":[]},"4aa05a21-86d6-451e-a1b1-2afd1107edba":{"id":"4aa05a21-86d6-451e-a1b1-2afd1107edba","doc_no":"A.2.2.9.1.1.2.1.3","title":"Prime Agent Preparation Of Capital And Operational Plan","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1661,"content":"The Capital and Operational Plan (\"C&O Plan\") articulates the Prime Agent’s strategy for a proposed new Allocation Instance or a modification to an existing Instance. In addition to articulating the Instance’s strategic objectives and operational parameters, the C&O Plan includes a pro-forma Required Risk Capital (RRC) estimate and a strategy for ensuring sufficient Total Risk Capital (TRC) coverage.\n\nThe C&O Plan is the major input into the Artifact Edit Proposal that codifies the new or modified Instance. Following the approval of such a proposal by Prime governance, the details and commitments outlined in the C&O Plan are formally integrated into the respective Instance Configuration Document of the Prime Agent’s Artifact.","contentHash":"fb448594dc1db5d559b2c9c03a86352d3557dbf50c88cf4a0a78986eaf00c26f","addressRefs":[]},"c3b53ee8-328a-4a79-8afe-ac0de99d8706":{"id":"c3b53ee8-328a-4a79-8afe-ac0de99d8706","doc_no":"A.2.2.9.1.1.2.1.3.1","title":"Pro-Forma Instance RRC Estimate","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1662,"content":"As a critical component of the Capital & Operational Plan, the Prime Agent must prepare an initial pro-forma Instance Required Risk Capital (RRC) estimate. This estimate serves as the basis for the Prime’s capital planning prior to the availability of official RRC figures from Sky Core. The estimate must strictly adhere to the implementation of RRC-models defined in [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"6b72bb3792c9e3481b2ebd9aa064178e4660f3da0bde772b29c1bdb1f1726517","addressRefs":[]},"a30447be-5214-4398-82aa-7306eeabd6f5":{"id":"a30447be-5214-4398-82aa-7306eeabd6f5","doc_no":"A.2.2.9.1.1.2.1.3.2","title":"Notional Total Risk Capital (TRC) Coverage Strategy","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1663,"content":"As a critical component of the Capital & Operational Plan, the Prime Agent must articulate its strategy for ensuring its Total Risk Capital (TRC) adequately covers the pro-forma Instance RRC of a new or modified Instance and the resulting impact on its Aggregate RRC.\n\nThe Prime’s notional TRC coverage strategy must outline how this new Instance’s RRC will be notionally accounted for or supported by the Prime’s overall TRC pool. If the Prime’s current TRC is not sufficient to cover its estimated increased Aggregate RRC, the strategy should outline the Prime Agent’s intended steps for acquiring additional JRC/SRC.\n\nFor instance, this risk-capital acquisition strategy could involve:\n\n1. Renting Junior Risk Capital (JRC)\n    - Sourcing Prime-External Junior Risk Capital (SEJRC) by renting it from other Primes through Ecosystem Accords.\n    - Sourcing Tokenized External Junior Risk Capital (TEJRC) from external capital providers.\n2. Sourcing Senior Risk Capital (SRC):\n    - Originating SRC through the Sky monthly auction.\n    - Renting OSRC from other Primes through Ecosystem Accords.\n3. Increasing Internal Junior Risk Capital (IJRC): A Prime might have plans to bolster its own IJRC through retained earnings or other internal means.\n4. Decreasing exposure in an existing Instance(s) to lower Aggregate RRC.\n\nThe Prime’s capital-acquisition strategy should indicate how the Prime will remain in compliance with all relevant Atlas rules, such as sourcing ratios that constrain how much Senior Risk Capital can be \"enabled\" or counted toward a Prime’s Aggregate RRC. See [A.3.2.1.2.3 - Total Risk Capital Sourcing Ratios](9e99b084-f15a-4f60-b831-d6c0bd9aec04).","contentHash":"ae6a5d4d5fb81edeeddd1b7dacdb35eb767f7577a85c4bebf6197fafafe4a5e0","addressRefs":[]},"a156b120-8b27-4a31-95fe-4154205ca102":{"id":"a156b120-8b27-4a31-95fe-4154205ca102","doc_no":"A.2.2.9.1.1.2.1.3.3","title":"Additional Elements Of Capital And Operational Plan","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1664,"content":"The Capital & Operational Plan includes the following additional elements:\n\n- Operational Parameters: defines the Instance’s target chain(s), protocols, initial capital, maximum deposit sizes, and any other parameters that underpin the pro-forma RRC calculation.\n- Data Submission Protocol: defines how yields, Required Risk Capital usage, ALM costs, exchange data, etc. will be reported and audited.\n- Emergency Procedures: defines mechanisms to be triggered if security or risk capital thresholds are breached, such as a kill switch or partial freeze.\n- Asset Liability Management (ALM) Strategy: details if the Prime will meet its ALM requirements through its own direct asset management or by transferring its obligations to another Prime Agent via the ASC Rental Primitive. If the latter, the C&O Plan must reference the governing Ecosystem Accord and its key terms.\n- Performance-based Adjustments: define the conditions or KPIs that allow adjustments to Instance deposit caps or yield expansions without requiring a formal Artifact edit.","contentHash":"00ae825612f164931ae8bd58594c999b641b817eb7ff0e7867256bd0f44c258a","addressRefs":[]},"e7d3d696-e2d0-4d4b-b4d6-c7a0c47b7cc6":{"id":"e7d3d696-e2d0-4d4b-b4d6-c7a0c47b7cc6","doc_no":"A.2.2.9.1.1.2.1.4","title":"Preliminary Informal Check With Operational GovOps","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1665,"content":"The Prime Agent presents the Capital and Operational Plan for the Allocation Instance to Operational GovOps, including any associated JRC/SRC and Asset Liability Management arrangements. Operational GovOps reviews and either provides an informal greenlight or requests modifications to the Plan. The output of this step is Operational GovOps approval to proceed with a request to revise the C&O Plan, as applicable.","contentHash":"2b5b9eadc794051ea686fd1b42e689210dd713dfffcb6ef767d02c7ef352dfcf","addressRefs":[]},"410c84be-ab41-4444-a7cb-1c19a0448948":{"id":"410c84be-ab41-4444-a7cb-1c19a0448948","doc_no":"A.2.2.9.1.1.2.2","title":"Instance Codification and Validation","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1666,"content":"The documents herein define how agreements to set up an Allocation Instance are codified and validated in the Powerhouse system and how governance votes happen.","contentHash":"5d062efa629d5b0de111295309974044dd3233b7710b595e0206cee1d5bf1e73","addressRefs":[]},"7a36f228-0438-43da-ae5f-a43af70c0121":{"id":"7a36f228-0438-43da-ae5f-a43af70c0121","doc_no":"A.2.2.9.1.1.2.2.1","title":"Agent Inputs","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1667,"content":"The Prime Agent drafts an update to the Prime Agent Artifact adding the Allocation Instance to the list of active Allocation Instances and including the information specified in [A.2.2.9.1.2.6 - List Of Allocation Instances](e4975062-6d19-438b-a5d5-cfc1a7fd8cb9). The Prime Agent submits the draft to the Powerhouse system. The output of this step is a draft Prime Agent Artifact update in the Powerhouse system.","contentHash":"e95d3c0d50a767be1ca6d13cdf7a1202ece6c0adef57199a5acb0edfafb3bc8a","addressRefs":[]},"dbae3918-75f7-469d-b623-8faa5ea7aa70":{"id":"dbae3918-75f7-469d-b623-8faa5ea7aa70","doc_no":"A.2.2.9.1.1.2.2.2","title":"Validation And Off-Chain Vote","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1668,"content":"The Operational Executor Facilitator reviews the proposal to ensure that it is complete and aligned with the Atlas. The Operational Executor Facilitator then initiates an off-chain snapshot vote, following the quorum and majority rules in the Prime Agent Artifact. When complete, the result of the vote is recorded in the Powerhouse system. The output of this step is the snapshot vote result recorded in the Powerhouse system.","contentHash":"86115322f768ad057136e3bdfce7754eeb5564bfb74a05f231acc272f13baa8a","addressRefs":[]},"2b1612b8-480c-49b3-a304-6a6f593340de":{"id":"2b1612b8-480c-49b3-a304-6a6f593340de","doc_no":"A.2.2.9.1.1.2.2.3","title":"Official Update of Artifact","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1669,"content":"If the Allocation Instance is successfully approved, the Operational Executor Facilitator finalizes and publishes the update to the Prime Agent Artifact, making it effective in the Atlas. The output of this step is an updated Prime Agent Artifact with the new Allocation Instance.\n\nOnce a new Instance is deployed, its data is integrated into risk-capital monitoring systems and its RRC will be officially determined and tracked via the Sky Core RRC Dashboard. See [A.2.2.9.1.1.3.2.1.1 - Sky Core Required Risk Capital (RRC) Dashboard](4eac2c9e-2718-4881-a3f1-ed10fb3f4d13). This official RRC figure supersedes the Prime-prepared pro-forma RRC.","contentHash":"22913b02c6ba48cb3668fedb335c7595c83ecd6117fd8e676e782e89453a4b63","addressRefs":[]},"3766cb8c-ab6c-41af-9465-b8dea76d0532":{"id":"3766cb8c-ab6c-41af-9465-b8dea76d0532","doc_no":"A.2.2.9.1.1.2.3","title":"Instance Setup Deployments","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1670,"content":"The documents herein define how the deployment of an Allocation Instance is executed on-chain. In the short-term, an Allocation Instance may also be deployed using the process for Interim Deployments specified in [A.1.10.2.3.2.2.2 - Interim Deployments](9b3edbbf-89d1-42da-a9c3-18f858f8471f).\n\nThe Prime Agent must subsequently prepare a pro-forma Required Risk Capital estimate, which must be approved by the Core Council Risk Advisor, before the parameters of the Instance can be updated for normal operation.","contentHash":"fc12712e82b125f2b3a48c6d9fb8257966b952f021d9cf634c9fcb0051ed2dcb","addressRefs":[]},"6899a722-3d1a-4bd1-80f2-f36be91bbab0":{"id":"6899a722-3d1a-4bd1-80f2-f36be91bbab0","doc_no":"A.2.2.9.1.1.2.3.1","title":"Conduit Development And Testing","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1671,"content":"Once formally validated, the Prime Agent implements the new Allocation Instance based on the specifications in the Prime Agent Artifact. Operational GovOps must test the Allocation Instance with minimal funds from the Prime Agent’s Central Allocation Buffer, verifying deposit / withdrawal logic, slippage constraints, and oracle checks. If this testing is successful Operational GovOps confirms that the Allocation Instance satisfies all risk constraints specified in the Prime Agent Artifact. The output of this step is validated contracts for the Allocation Instance and a green light to proceed with a scaled deployment.","contentHash":"6d788866ca44b7b3ebbce9cdedc7b43f303ea047efef7fb8a07d10f8c320292d","addressRefs":[]},"648bcae7-9723-4282-81fe-fcc77fd6f90e":{"id":"648bcae7-9723-4282-81fe-fcc77fd6f90e","doc_no":"A.2.2.9.1.1.2.3.2","title":"Initial Deployment and Required Risk Capital / Asset Liability Management Execution","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1672,"content":"The Prime Agent finalizes JRC/SRC and Asset Liability Management Arrangements. Operational GovOps records these arrangements in the Powerhouse interface. If Operational GovOps is charged with operationalizing an Instance, it deploys funds from the Prime Agent’s Operational Buffer into the Allocation Instance, performing any necessary DEX exchanges. See [A.2.2.9.1.1.3.1 - Operationalization Of Allocation Instances](989512c2-4fa1-46b8-947c-00e3c0b56024). In doing so, Operational GovOps follows instructions in the Agent Artifact regarding the amount of capital to deploy and slippage tolerances. The output of this step is a fully deployed Allocation Instance conforming to Risk Capital and Asset Liability Management requirements.","contentHash":"b23bf46b1b5fdd86d062a0860006e629d5a45c6c9b9847386219ab66113d4c7a","addressRefs":[]},"2db14aa7-ccfa-42f7-82a8-118048574d4c":{"id":"2db14aa7-ccfa-42f7-82a8-118048574d4c","doc_no":"A.2.2.9.1.1.3","title":"Allocation Instance Ongoing Management","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1673,"content":"The documents herein define the process for managing an Allocation Instance as part of the Allocation System Primitive.","contentHash":"6512e20c38624dbdae1402893ced765e00c93c6993a5a389e8415ecffae9435a","addressRefs":[]},"989512c2-4fa1-46b8-947c-00e3c0b56024":{"id":"989512c2-4fa1-46b8-947c-00e3c0b56024","doc_no":"A.2.2.9.1.1.3.1","title":"Operationalization Of Allocation Instances","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1674,"content":"Prime Agent teams may choose to directly operationalize their Allocation System Primitive Instances (\"Instances\") using internal, proprietary strategies that are not defined in their Artifacts. Alternatively, Prime Agents may elect to have the Instances operationalized by their Operational Executor Agent. This constitutes an exception to the general rule that Operational Executor Agents operationalize all Sky Primitives on behalf of Prime Agents. See [A.1.14.3.4 - Agent Role Delineation](fdf32ca5-5e2e-481e-9047-4d1599547216).\n\nFor Prime Agent teams that operationalize their Instances, they will be required to formulate KPIs for their proprietary strategies; should an Instance under-perform these KPIs, Operational GovOps is authorized to step in and operationalize the Instance(s) via a back-up strategy that is defined in the Agent Artifact. Additional logic on this point will be defined in a future iteration of the Atlas.","contentHash":"f6d74ebcbea9f8ae3e987d2368960b5c8093fa6b424618c7b83f864460f6d8bc","addressRefs":[]},"13eb2346-07e5-48b6-9740-ce60a20146ab":{"id":"13eb2346-07e5-48b6-9740-ce60a20146ab","doc_no":"A.2.2.9.1.1.3.2","title":"Requirements And Infrastructure For Risk Capital And Asset Liability Management","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1675,"content":"The documents herein define Risk Capital and Asset Liability Management requirements and infrastructure.","contentHash":"ffbf8958dcdd963c3242cdad6e8f046746a96c83643ea3bb46add6c2c5c06b42","addressRefs":[]},"1c5fb5bb-ec03-478c-89b7-4017d935276e":{"id":"1c5fb5bb-ec03-478c-89b7-4017d935276e","doc_no":"A.2.2.9.1.1.3.2.1","title":"Risk Capital Management","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1676,"content":"The documents herein detail the obligations, processes, standards and infrastructure related to risk-capital management.","contentHash":"3bccb337359cf61760bfd720d9d0c1a644e9d06dfa7de248bf669aac7400bdcb","addressRefs":[]},"4eac2c9e-2718-4881-a3f1-ed10fb3f4d13":{"id":"4eac2c9e-2718-4881-a3f1-ed10fb3f4d13","doc_no":"A.2.2.9.1.1.3.2.1.1","title":"Sky Core Required Risk Capital (RRC) Dashboard","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1677,"content":"The Sky Core Required Risk Capital (RRC) Dashboard serves as the official system for determining and disseminating RRC figures for Prime Agents and their Allocation System Primitive Instances.\n\nPrior to the full operational deployment of the Powerhouse system, Prime Agents must utilize the Sky Core RRC Dashboard as the authoritative source for their official Instance Total RRCs and Aggregate RRC. Data from this source is to be used for all internal TRC management, required reporting and compliance assessments.\n\nThe Sky Core RRC Dashboard is located at [https://info.sky.money/required-risk-capital](https://info.sky.money/required-risk-capital).","contentHash":"563822fd308e40afa820a71ce18880c33c9250c10f070276b979cb685232d860","addressRefs":[]},"f7da0f56-00f5-4bcf-bd31-b77c284c7992":{"id":"f7da0f56-00f5-4bcf-bd31-b77c284c7992","doc_no":"A.2.2.9.1.1.3.2.1.1.1","title":"Role and Functionality of the RRC Dashboard","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1678,"content":"The RRC Dashboard provides a user interface for Prime Agents to view their official RRC figures. The Dashboard provides the following key information:\n\n- Instance Total RRC: For each specific Allocation System Primitive Instance, the system displays its Instance Total RRC. This figure is the sum of all applicable risk-specific RRC calculations for that Instance, including:\n    - Instance Financial RRC ([A.3.2.1.1.4 - Instance Financial RRC](ba1d5c0e-399f-47a6-b5d4-b3f5477d5787))\n    - Instance Smart Contract RRC ([A.3.2.1.1.5 - Instance Smart Contract RRC](4b4ea578-28b4-481c-9abd-d34c5a4f383c))\n    - Instance Administrative RRC ([A.3.2.1.1.6 - Instance Administrative RRC](c2b60f0d-6555-463c-9ad3-2a9746be77c5))\n\nThe models for certain risk-factors are still currently under development. See [A.2.2.9.1.1.3.2.1.1.2 - Interim Notice Regarding RRC Dashboard Coverage](18243e7a-5b62-459d-83fb-e50b9df05f9d).\n\n- Aggregate RRC: For each Prime Agent, the system displays its Aggregate RRC, which is the sum of all its Instance Total RRCs. This is the figure against which a Prime Agent’s Total Risk Capital (TRC) adequacy is assessed.","contentHash":"91570c93c821b2d9dc059d48b541ba9da7f65e709d219524c66f1dc8b6254528","addressRefs":[]},"18243e7a-5b62-459d-83fb-e50b9df05f9d":{"id":"18243e7a-5b62-459d-83fb-e50b9df05f9d","doc_no":"A.2.2.9.1.1.3.2.1.1.2","title":"Interim Notice Regarding RRC Dashboard Coverage","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1679,"content":"Some Allocation System Instances displayed on the RRC Dashboard concern asset types whose risk models have not yet been fully developed. See [A.3.2.1.1.4.3 - Financial Risk Models](2af9fa64-ab25-4017-920c-f1c07dff4c06). An active Instance’s respective Instance Configuration Document will specify its `RRC Framework Full Implementation` status as either `Covered` or `Pending`.","contentHash":"9c69138ed812cc24c86c2738d0dee0e44a40fa47cb48aac2e1399cc35c557339","addressRefs":[]},"3af8a3a2-25e5-44b3-87a4-7df1f2712685":{"id":"3af8a3a2-25e5-44b3-87a4-7df1f2712685","doc_no":"A.2.2.9.1.1.3.2.1.2","title":"Primes' Total Risk Capital (TRC) Management","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1680,"content":"Prime Agent teams are responsible for managing their Total Risk Capital (TRC) to continuously meet their Aggregate Required Risk Capital (RRC). The accounting of TRC considers all on-chain holdings and any off-chain agreements, encumbrances, or conditions that may affect the immediate availability or eligibility of capital for RRC coverage. For a definition of Total Risk Capital, see [A.3.2.1.2.1 - Total Risk Capital Definition](6f6b25d6-f73c-4733-ba37-12a0a411433c).\n\nThe documents herein define requirements and standards for a Prime Agent’s internal TRC management systems.","contentHash":"00e1aaea81980366ebc25dc83cc1278672be9ee48093c758ccbd1ab00e1ad991","addressRefs":[]},"9a8120c4-0a5b-426f-97a5-283c708413f5":{"id":"9a8120c4-0a5b-426f-97a5-283c708413f5","doc_no":"A.2.2.9.1.1.3.2.1.2.1","title":"Objective of Prime TRC Management","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1681,"content":"To comply with Atlas risk capital requirements, Prime Agent teams must establish, maintain, and operate an internal system for TRC management. A Prime Agent’s internal TRC management system should enable proactive operational risk management. This entails ongoing capital adequacy assessment and strategic capital allocation planning for current and future Allocation System Primitive Instances, including the ability to perform scenario analyses for potential deployments or market stresses.\n\nPrime Agents’ internal TRC management systems should enable them to maintain continuous sufficiency of the Prime Agent’s held TRC against its official Aggregate RRC. This requires real-time or near real-time comparison and internal alerting mechanisms to prevent and address potential shortfalls.\nPrimes must ensure that their internal TRC management systems maintain comprehensive, verifiable internal records of all TRC components, related transactions, and compliance activities to support internal governance and external verification processes, such as the submission of TRC Reports to Core GovOps. See [A.2.2.9.1.1.3.2.1.2.3 - Primes’ TRC Report](41ca2085-d71b-47e5-8b1a-b183b6e2b6fc).","contentHash":"72e9076d6948cde9cc89d430e9db7041210cde231ca72b54016910b0a743856a","addressRefs":[]},"d034533f-9b6f-411c-8b60-3bccb374765f":{"id":"d034533f-9b6f-411c-8b60-3bccb374765f","doc_no":"A.2.2.9.1.1.3.2.1.2.2","title":"Minimum Capabilities of Prime TRC Management Systems","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1682,"content":"A Prime Agent’s internal TRC management system should possess the following capabilities to meet the objectives outlined in [A.2.2.9.1.1.3.2.1.2.1 - Objective of Prime TRC Management](9a8120c4-0a5b-426f-97a5-283c708413f5).\n\n1. Prime Agents’ internal TRC management systems should enable compliant sourcing and tracking of all TRC components, including Internal Junior Risk Capital (IJRC), Prime-External Junior Risk Capital (SEJRC), Tokenized External Junior Risk Capital (TEJRC), and Originated Senior Risk Capital (OSRC). Compliance in this context includes strict adherence to eligibility criteria and capital-sourcing ratios (e.g., External Per Internal, Senior Per Junior) as defined in the Atlas. See [A.3.2.1.2.3 - Total Risk Capital Sourcing Ratios](9e99b084-f15a-4f60-b831-d6c0bd9aec04).\nThe system must provide real-time or near real-time tracking of all held Total Risk Capital (TRC) components. This includes, for each TRC component:\n    - Accurate valuation of the assets comprising each component.\n    - Clear identification of the source of each component (e.g., Prime’s own SubProxy for IJRC, specific Ecosystem Accord references for rented SEJRC or OSRC, TEJRC encumbrance details, OSRC origination details).\n    - Verification of each TRC component’s eligibility status according to Atlas rules. This includes tracking whether capital is “enabled” or “active” for RRC coverage purposes (e.g., based on Ecosystem Accord status, compliance with sourcing ratios, etc.).\n    - Distinction between capital directly held by the Prime Agent and capital that is encumbered (e.g., SEJRC where the lending Prime retains custody but the capital is contractually committed).\n2. Prime Agents' internal TRC management systems should enable dynamic-state accounting. The system must account for TRC components that are in dynamic, pending, or off-chain states, as these can impact the true risk capital available to a Prime Agent. This includes:\n    - Pending transactions such as SEJRC or OSRC rental Ecosystem Accords that have been committed to by the parties, but not yet codified in the Atlas.\n    - Capital in transit, e.g., assets that are committed to be IJRC, but currently moving between chains via bridges or locked in Cross-Chain Transfer Protocol (CCTP) messages awaiting finality.\n    - Operational expenditures funded by TRC components (typically IJRC), such as blockchain transaction fees, oracle service fees, audit costs, and other operational overhead that reduces available risk capital. The system should track these expenditures in real-time or near real-time.\n    - Any off-chain factors that could impair the immediate deployability or availability of TRC components.\n3. Prime Agents' internal TRC management systems should enable continuous capital adequacy monitoring. The system must enable the near real-time comparison of the Prime Agent's internally tracked and calculated TRC against its official Aggregate RRC, as obtained from the Sky Core RRC Dashboard. See [A.2.2.9.1.1.3.2.1.1 - Sky Core Required Risk Capital (RRC) Dashboard](4eac2c9e-2718-4881-a3f1-ed10fb3f4d13). This core functionality is essential for the Prime Agent to proactively monitor its capital adequacy, identify potential or actual TRC shortfalls, and make timely operational and capital management decisions to maintain compliance.\n4. Prime Agents' internal TRC management systems should define a RRC-incident (e.g., TRC shortfall) response protocol. The system should enable internal alerting mechanisms that detect when a Prime Agent’s TRC approaches predefined internal buffer thresholds relative to its Aggregate RRC. See [A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9). The system should also detect an actual shortfall where the Prime Agent’s held TRC falls below its Aggregate RRC. Furthermore, Prime Agent teams should establish and document internal processes for responding to such alerts. Such internal processes should include: 1) internal escalation and assessment of the shortfall’s cause and magnitude; 2) formulation of potential responses or corrective actions, which may include sourcing additional TRC, reducing risk-weighted exposures, or other measures; 3) internal decision-making framework for the evaluation of potential responses and selection of the most appropriate one; and 4) notifying any pertinent parties (Operational GovOps) as needed for the purpose of planning or implementing follow-up action.\n\nPrime Agent teams' internal decision-making framework may consider the economic trade-offs of various actions, including the strategic acceptance of penalties for a TRC shortfall where such an approach is determined to be economically advantageous compared to immediate rebalancing (e.g., avoiding excessive transaction costs or market impact).","contentHash":"dafe14223ec81e28331f3d0c0626e435efb842b828c0dc5416035c7b70271e65","addressRefs":[]},"41ca2085-d71b-47e5-8b1a-b183b6e2b6fc":{"id":"41ca2085-d71b-47e5-8b1a-b183b6e2b6fc","doc_no":"A.2.2.9.1.1.3.2.1.2.3","title":"Primes’ TRC Report","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1683,"content":"Prime Agents are required to submit periodic Total Risk Capital (TRC) Reports to provide an accurate and verifiable attestation of their TRC composition and adherence to capital requirements.","contentHash":"2b791d95b10534b050ec7504609e4e5c0c478f7491c54eeafce741cec120d7d8","addressRefs":[]},"7e95efa7-e409-48dc-9b5a-96edce54bf31":{"id":"7e95efa7-e409-48dc-9b5a-96edce54bf31","doc_no":"A.2.2.9.1.1.3.2.1.2.3.1","title":"Mandate and Rationale","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1684,"content":"Prime Agents are required to periodically submit TRC Reports to Core GovOps. This report serves a dual purpose. It provides a verifiable snapshot of the Prime Agent's TRC composition and key capital ratios as of the end of the reporting period; and second, it provides a formal attestation regarding the Prime Agent's maintenance of TRC at or above its dynamically changing Aggregate Required Risk Capital (RRC) throughout the entire reporting period. See [A.3.2.1.1.2 - Aggregate RRC](6aed5cc1-9671-4b73-88a9-fdd86ac93ece).\n\nThis comprehensive reporting, encompassing both an end-of-period statement and disclosures of any intra-period events affecting TRC, is essential. On-chain data alone (such as that captured by the planned OVRC system) cannot definitively prove the full eligibility and unimpaired availability of a Prime Agent's capital position for continuous RRC coverage, nor can it capture all off-chain factors. These factors include, but are not limited to, whether assets are subject to Prime-initiated off-chain contractual pledges, if the economic value or redeemability of its bridged assets is compromised by issues with their originating bridge, or if its assets are encumbered by derivative structures or other off-chain commitments that would impair their immediate use at any point during the period.\n\nThe TRC Report serves as an important basis for Core GovOps’ verification procedures. This entails: 1) reconciling reported end-of-period TRC components against the Sky Atlas, on-chain data, and other relevant sources to validate the period-end capital position and adherence to Atlas-defined capital requirements; and 2) reviewing Prime Agents’ attestations and disclosures regarding its TRC management and any material events throughout the reporting period to assess continuous compliance with its dynamically changing Aggregate RRC. The outcome of this validation is a critical input for the monthly settlement cycles, which latter includes the determination and retroactive application of penalties for any identified discrepancies or violations of capital requirements during the period.\n\nThe long-term vision is for the Powerhouse system to enable the automation of TRC data aggregation and verification. The Powerhouse system will have capabilities such as directly querying Prime Agent SubProxy accounts for IJRC assets, programmatically accessing and interpreting Ecosystem Accords recorded in the Atlas, interfacing with TEJRC and OSRC smart contract systems, and automatically applying Atlas-defined eligibility rules. See [A.2.2.9.1.1.3.2.1.3.1 - Continuous Monitoring Of On-chain Verifiable Risk Capital (OVRC)](8048bdf0-84b7-4546-8f1a-98b62d073c84). Even in this advanced state, the TRC Report, or a similar form of periodic attestation, may remain necessary to cover elements of TRC verification that are not fully able to be automated or require explicit Prime Agent declaration.","contentHash":"e0433ee00bd1a30407870e26146209233fc23bcf901f1ebe86f4a17c94c38819","addressRefs":[]},"4887e971-be6c-4f98-9137-7cdec3ed0fa0":{"id":"4887e971-be6c-4f98-9137-7cdec3ed0fa0","doc_no":"A.2.2.9.1.1.3.2.1.2.3.2","title":"TRC Report Contents","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1685,"content":"The Total Risk Capital (TRC) Report submitted by a Prime Agent must provide an accurate and verifiable breakdown of all TRC components held by the Prime Agent as of the end of the specified reporting period. The TRC Report should include the following essential information:\n\n- Aggregate TRC Value As of End of Period: The total declared value in USD of all eligible TRC components held by the Prime Agent as of the end of the reporting period.\n- Detailed Breakdown of TRC Components As of End of Period: For each category of TRC held, the report must detail the following values as of the end of the reporting period:\n    - Internal Junior Risk Capital (IJRC): The total amount of IJRC, a breakdown of its constituent asset types, and their respective values in USD.\n    - Prime-External Junior Risk Capital (SEJRC): The total amount of SEJRC. For each portion of SEJRC sourced from another Prime Agent, the report must include the amount in USD, the identifier of the counterparty Prime Agent, the expiry date of the arrangement, and a direct reference to the Ecosystem Accord that governs the SEJRC arrangement.\n    - Tokenized External Junior Risk Capital (TEJRC): The total amount of TEJRC. For each TEJRC source, the report must include the amount in USD, the identifier of the TEJRC smart contract or facility and any relevant encumbrance identifier.\n    - Originated Senior Risk Capital (OSRC): The total amount of OSRC. The report must specify the amount originated directly by the Prime Agent from the Total Senior Risk Capital (TSRC) pool and any amount of OSRC rented from other Prime Agents. For any rented OSRC, the report must include the amount in USD, the identifier of the counterparty Prime Agent, the expiry date, and a direct reference to the pertinent Ecosystem Accord.\n    - Key Ratio Inputs and Computed Totals (Prime Internal Calculation) As Of End Of Period: Based on the component values reported above (as of the end of the reporting period), the report must include key figures used in and resulting from the Prime Agent's internal capital adequacy calculations. These figures reflect the capital structure and ratios as of the end of the reporting period and include:\n        - Internal Junior Risk Capital (IJRC)\n        - External Junior Risk Capital (EJRC) generated via External Per Internal Ratio (Prime External Junior Risk Capital + Tokenized External Junior Risk Capital sourced via the EPI ratio still carries Senior Per Junior or SPJ capacity)\n        - EJRC-via-SPJ (sourced by spending SPJ capacity; zero-SPJ-capacity thereafter)\n        - Enabled Senior Risk Capital (SRC)\n        - Total Senior Per Junior capacity\n            - Allocation of SPJ capacity to 1) enable SRC; or to 2) source EJRC\n        - Prime-computed eligible Total Risk Capital (IJRC + EJRC-via-EPI + EJRC-via-SPJ + enabled SRC)\n        - Official Aggregate RRC\n        - Capital buffer = TRC – Aggregate RRC\n        - Effective ratios\n            - EPI = EJRC-via-EPI ÷ IJRC\n            - SPJ utilisation:\n                - enabled SRC ÷ total SPJ capacity\n                - EJRC-via-SPJ ÷ total SPJ capacity\n- Dynamic Period Attestation and Disclosures: In addition to the end-of-period snapshot figures, the TRC Report must include an Attestation from the Prime Agent confirming it maintained TRC at or above its Aggregate RRC at all times throughout the entire reporting period. In addition, the TRC Report must include disclosure of any events, Prime-initiated off-chain contractual obligations, impairments to the value or redeemability of held assets (such as RWA backing or bridged asset viability), encumbrances, or other conditions that occurred at any point during the reporting period which materially affected its TRC, even if such conditions were temporary or not continuously visible to on-chain monitoring systems. This disclosure must include the nature of the event/condition, its precise timing and duration, and its quantified impact on the Prime Agent's TRC.","contentHash":"55ef99691d00e3ece7bdcd40fdd07ba39b7d3297ff84ad0c78e377aefea760d2","addressRefs":[]},"18d692ce-7a5d-47a7-ada9-dc73abd87987":{"id":"18d692ce-7a5d-47a7-ada9-dc73abd87987","doc_no":"A.2.2.9.1.1.3.2.1.3","title":"Sky Core TRC Monitoring And Verification Infrastructure","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1686,"content":"The documents herein define infrastructure for TRC monitoring and verification.","contentHash":"67ed01e3e1a6454ea6512609327b2d00aec72fa124ed488d141fa300c460c09e","addressRefs":[]},"8048bdf0-84b7-4546-8f1a-98b62d073c84":{"id":"8048bdf0-84b7-4546-8f1a-98b62d073c84","doc_no":"A.2.2.9.1.1.3.2.1.3.1","title":"Continuous Monitoring Of On-chain Verifiable Risk Capital (OVRC)","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1687,"content":"An autonomous monitoring system must be designed and implemented to enable continuous tracking of Prime Agents’ on-chain verifiable risk-capital components in near real-time. The on-chain, verifiable risk-capital components that can be tracked by such a monitoring system in real time are termed \"On-chain Verifiable Risk Capital\" (OVRC).\n\nOVRC is not necessarily equivalent to Total Risk Capital (TRC). A Prime Agent’s actual TRC cannot be determined definitively without accounting for off-chain agreements, encumbrances or other relevant conditions affecting capital eligibility or availability, which conditions must be disclosed in the TRC Reports submitted by Prime Agents. See [A.2.2.9.1.1.3.2.1.2.3 - Primes’ TRC Report](41ca2085-d71b-47e5-8b1a-b183b6e2b6fc).\n\nWhere the OVRC of a Prime Agent is less than its Aggregate RRC, the shortfall will be logged and penalty accrual will commence on a pro-rata, per-second basis for the duration and magnitude of the observed shortfall, according to the penalty schedule defined in the Atlas. Thus, this on-chain monitoring system serves as an interim penalty ledger.","contentHash":"563093a773fab8e54ec82f12633cd0b2881e52af1936582cfd438282732902a9","addressRefs":[]},"482fc286-9969-40cc-b3c9-6233ecbb659c":{"id":"482fc286-9969-40cc-b3c9-6233ecbb659c","doc_no":"A.2.2.9.1.1.3.2.1.3.2","title":"Validation of TRC Report In General","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1688,"content":"Prime Agents are required to submit periodic Total Risk Capital (TRC) Reports to Core GovOps. See [A.2.2.9.1.1.3.2.1.2.3 - Primes’ TRC Report](41ca2085-d71b-47e5-8b1a-b183b6e2b6fc). The protocol for validation of Primes’ TRC reports is defined in the documents herein.","contentHash":"092bd28cde82ab721cb6c9f63d9219421003ddafd759f8c0c27af495ce6b23f7","addressRefs":[]},"1ac3e606-f1c7-4a20-a9b6-a425920e98d3":{"id":"1ac3e606-f1c7-4a20-a9b6-a425920e98d3","doc_no":"A.2.2.9.1.1.3.2.1.3.2.1","title":"Core GovOps TRC Report Validation Process","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1689,"content":"Core GovOps receives TRC Reports from Primes on a regular basis and must perform the following validation process.\n\nCore GovOps verifies against the Atlas any Ecosystem Accord referenced in the TRC Report for sourced Prime-External Junior Risk Capital (SEJRC) or rented Originated Senior Risk Capital (OSRC). This includes confirming the existence, current validity, and terms of such Accords as formally recorded within the Atlas.\n\nCore GovOps validates the Prime Agent's reported IJRC by reconciling the reported IJRC amount and its constituent asset composition against the actual on-chain state of the Prime Agent’s designated SubProxy account. This involves direct on-chain verification of asset balances. Core GovOps verifies that all assets reported as IJRC and held within the SubProxy account meet the definition of \"eligible assets\" for IJRC as defined by the Atlas. See [A.3.2.1.2.2.1.1.1 - Internal Junior Risk Capital (IJRC)](8728abee-0dc5-449b-b4c2-78698da16f10).\n\nFor reported Tokenized External Junior Risk Capital (TEJRC) and Originated Senior Risk Capital directly originated by the Prime, Core GovOps validates the reported amounts and statuses by cross-referencing data from the relevant smart contract systems. This may involve querying TEJRC pool contracts, OSRC auction records, and other on-chain infrastructure to confirm the existence, ownership, and eligibility of these capital components.\n\nCore GovOps reviews all attestations and disclosures made by the Prime Agent in the TRC Report. This review focuses on understanding the Prime Agent's TRC compliance with Aggregate RRC throughout the entire reporting period. This assessment is critical for identifying intra-period shortfalls that might not be visible to on-chain monitoring systems or reflected in the end-of-period snapshot alone. The assessment process may include requiring the Prime Agent to provide supplementary documentation, verifiable evidence, or independent third-party confirmations for material off-chain claims or attestations concerning intra-period events; and/or cross-referencing disclosed off-chain information with relevant on-chain indicators or transactions that might corroborate or contradict the attestations.\n\nFinally, Core GovOps independently calculates and verifies the Prime Agent's compliance with all Atlas-defined capital sourcing ratios (e.g., External Per Internal (EPI), Senior Per Junior (SPJ)).","contentHash":"fbde797d3dfe7958c2f006a4571e453ac2f81e5a2f45ac1ebea546fc1cf0ecf7","addressRefs":[]},"36f3e675-d372-4d25-a50f-f0ba84a36273":{"id":"36f3e675-d372-4d25-a50f-f0ba84a36273","doc_no":"A.2.2.9.1.1.3.2.1.3.3","title":"Finalized Determination Of TRC Position And Penalties","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1690,"content":"After reaching a definitive accounting of Prime Agents’ capital position and TRC adequacy, penalties are finalized by Core GovOps. This involves reconciling the interim penalty ledger (derived from the OVRC system) with the definitive TRC history, which incorporates all validated information from the TRC Report including any intra-period shortfalls.\n\n1. If the validated TRC Report indicates that the Prime Agent's TRC was below its Aggregate RRC during the reporting period, and this actual shortfall was more severe than, or not detected by, the OVRC monitoring system, then penalties will be finalized as follows: if the OVRC system had already accrued penalties, these will be adjusted upwards to match the actual shortfall; if the OVRC system had not detected a shortfall, penalties will be assessed and applied retroactively based on the full duration and magnitude of the actual shortfall.\n2. If the validated TRC Report confirms that TRC shortfalls were identical in duration and magnitude to those logged by the OVRC monitoring system throughout the reporting period: the penalties accrued in the interim penalty ledger will be confirmed and finalized.\n3. If the validated TRC Report confirms that TRC was higher than a misleading OVRC reading during a specific portion of the reporting period which led to an erroneously logged penalty: Core GovOps will adjust or void the penalty accordingly.","contentHash":"6c893a2959d5948ec786c31b773bb5425622f6ac576050f5f0b5ac3b28e85fe0","addressRefs":[]},"12b7d480-68a0-4493-9534-d6915f86c112":{"id":"12b7d480-68a0-4493-9534-d6915f86c112","doc_no":"A.2.2.9.1.1.3.2.1.4","title":"Risk-Capital Incident Response","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1691,"content":"Where a Prime Agent’s Allocation System Instances are operationalized by its Operational Executor Agent, the management of and response to Required Risk Capital (RRC)-related incidents requires a defined framework within each Prime Agent's Artifact (the Multi-Instance Coordinator Document for the Allocation System Primitive) and its associated Executor Accord.\n\nWhile the Prime Agent's strategic team (\"Prime Team\") determines the specific rectification strategy for an RRC incident—considering its holistic portfolio, prevailing market conditions, and the potential for strategic acceptance of penalties—this discretion is exercised subject to the authority of Sky Core to impose penalties and take corrective measures, up to and including the conservatorship of a Prime Agent, to protect the ecosystem and make any losses whole.\n\nThis document will be developed further in a future iteration of the Atlas.","contentHash":"5f8d9dd4cf56d5e06e8e7488068cde4d28e9ab80dbb6dca957f1a63996f6aa9b","addressRefs":[]},"1ec5f16f-194d-4163-b1ba-5c196ffa554b":{"id":"1ec5f16f-194d-4163-b1ba-5c196ffa554b","doc_no":"A.2.2.9.1.1.3.2.1.5","title":"Instance Operational Conformance","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1692,"content":"Operational deviation from Artifact specifications can render an Instance’s RRC, and thus the Prime’s Aggregate RRC, invalid. Prime Agents must therefore ensure that each Allocation System Instance adheres to its respective Instance Configuration Document. Whether a Prime self-operationalizes its Allocation System or contracts with an Operational Executor Agent, its Agent Artifact must define processes for monitoring for, and addressing deviations of, Instance operational conformance. This document will be developed further in a future iteration of the Atlas.","contentHash":"7c3d10c81713b6d037e369e3983cd7d31b7af698e51766cfa6aafe9919c392d3","addressRefs":[]},"ed10830e-6b17-4117-8ab4-5ea388b518bb":{"id":"ed10830e-6b17-4117-8ab4-5ea388b518bb","doc_no":"A.2.2.9.1.1.3.2.2","title":"Asset Liability Management","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1693,"content":"Requirements and infrastructure related to Asset Liability Management shall be defined in a future iteration of the Atlas.","contentHash":"08e52a0f6f17c6de2adf8f915bf1be6f26b4a771830061a74e92a1f6a2f348b8","addressRefs":[]},"93bfb0f9-d662-467d-b8bc-ef585e5b081e":{"id":"93bfb0f9-d662-467d-b8bc-ef585e5b081e","doc_no":"A.2.2.9.1.1.3.3","title":"Allocation Instance Adjustments, Scaling, And Settlement","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1694,"content":"On an ongoing basis, the Prime Agent team or Operational GovOps operates the Allocation Instance, scaling exposure up and down. Any change to the Allocation Instance outside of the limits specified in the Prime Agent Artifact or requiring judgment on the part of Operational GovOps (where the Allocation System Instance is operationalized by the Operational Executor Agent) requires a new vote of Prime Agent token holders. See [A.2.2.9.1.1.3.3.1 - Modification Of Existing Instances](c1b5708c-e88f-45e0-92e1-b76e68b34f13). As part of monthly and quarterly settlement cycles, Core GovOps reviews yields and obligations, applying penalties retroactively for any previously undisclosed violations. In the event of any such violations, Operational GovOps may be required to take escalatory steps based on the fallback strategy in the Prime Agent Artifact.","contentHash":"99674db8aa32f27cfda1caadeec43a8ea620079cacc901d9336d256abc714c8b","addressRefs":[]},"c1b5708c-e88f-45e0-92e1-b76e68b34f13":{"id":"c1b5708c-e88f-45e0-92e1-b76e68b34f13","doc_no":"A.2.2.9.1.1.3.3.1","title":"Modification Of Existing Instances","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1695,"content":"When a Prime Agent wishes to modify an existing Allocation System Primitive Instance in a manner that cannot be accommodated by the existing operational parameters defined in its Agent Artifact, the Prime Agent must initiate an Artifact Edit Proposal process as detailed herein.","contentHash":"7e41304747aeb96d8b814e5bdde32367467f7a210f464c3a7291411352dfe969","addressRefs":[]},"3db4c73f-f480-4da4-9af3-8ecedd89e166":{"id":"3db4c73f-f480-4da4-9af3-8ecedd89e166","doc_no":"A.2.2.9.1.1.3.3.1.1","title":"Conditions Requiring Artifact Edit Proposal","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1696,"content":"An Artifact Edit Proposal is mandatory for an Instance modification under the following conditions:\n\n1. a desired modification to the Instance's operational parameters falls outside the pre-defined operational ranges codified in the respective Instance Configuration Document or other applicable Artifact Documents; or\n2. a desired modification, even if notionally within defined ranges in the Artifact, is determined by Operational GovOps to materially alter the Instance's risk profile in a way that could invalidate the underlying Capital and Operational Plan and, consequently, the premises driving the current Required Risk Capital (RRC) for that Instance. Operational GovOps retains the discretion to require an Artifact Edit Proposal if a proposed change, regardless of its fit within existing operational ranges, is determined to pose a material change to the assessed risk.","contentHash":"df324112ddae38a99b7ba061875ffdda65dcb82ab3c163b2ba9f372fd3b2168e","addressRefs":[]},"235a7317-ef29-48ed-a37f-5892108f8dc8":{"id":"235a7317-ef29-48ed-a37f-5892108f8dc8","doc_no":"A.2.2.9.1.1.3.3.1.2","title":"Revision of Capital and Operational Plan for Instance Modification","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1697,"content":"Prior to submitting an Artifact Edit Proposal for an Instance modification, the Prime Agent must revise the Capital and Operational Plan (C&O Plan) associated with that Instance to reflect the desired new state.\n\nThe revised Capital and Operational Plan for an Instance modification must include the following information:\n\n1. Updates to the Instance's strategy and operational parameters;\n2. A new pro-forma Required Risk Capital (RRC) estimate specifically calculated to reflect the Instance's proposed modified state; and\n3. A revised notional Total Risk Capital (TRC) coverage strategy, detailing how the Prime Agent will manage any changes to the Instance RRC and the consequential impact on its Aggregate RRC, including plans for acquiring additional JRC or SRC if necessary.","contentHash":"fcc635f27d02af26caec06e52ec0107bdaea0fffbde485073c0469f91d4e7253","addressRefs":[]},"aee1d848-eee8-4590-a596-1884efcb474a":{"id":"aee1d848-eee8-4590-a596-1884efcb474a","doc_no":"A.2.2.9.1.1.3.3.1.3","title":"Governance Process for Instance Modification","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1698,"content":"The Prime Agent's revised Capital and Operational Plan forms the core of the Artifact Edit Proposal for the Instance modification. This proposal must be submitted to the Operational Executor Facilitator for review. The Facilitator assesses the proposal for completeness and general alignment. Following this review, the proposal is subjected to the Prime Agent's governance process for approval to edit the Agent Artifact, typically involving a token holder vote as defined in the Prime Agent's Root Edit Primitive.","contentHash":"d2577205ce19d516b2073324203aa04dd235328f6e34982cd5bca18f37a34259","addressRefs":[]},"e3a00c33-9da7-4fa9-80ff-55d3a70100fa":{"id":"e3a00c33-9da7-4fa9-80ff-55d3a70100fa","doc_no":"A.2.2.9.1.1.3.3.1.4","title":"Post-Approval Integration and RRC Update","type":"Core","depth":6,"parentId":"823a12c3-45d2-438a-b061-46ecd09cdca8","order":1699,"content":"If the Artifact Edit Proposal for the Instance modification is approved through the Prime Agent’s governance process, the relevant content from the revised Capital and Operational Plan is formally integrated into the respective Instance Configuration Document within the Prime Agent's Artifact.\n\nOnce the modified Instance is operational under its new, approved parameters and its data is integrated into the ecosystem’s monitoring systems, its adjusted Required Risk Capital (RRC) will be officially determined and tracked via the Sky Core RRC Dashboard. This official RRC figure then supersedes the Prime-prepared pro-forma RRC that was part of the modification proposal.","contentHash":"1ed3249828d41f8112519382bbe3ff396195f4df7a955102c88c2c28d8af0686","addressRefs":[]},"b6ccdee2-a5e4-4d63-9af5-60b8163673af":{"id":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","doc_no":"A.2.2.9.1.2","title":"Allocation System Input Requirements","type":"Core","depth":5,"parentId":"9db14ab7-bb4b-4751-8084-843bd4359f2a","order":1700,"content":"The documents herein define the required inputs for a valid Invocation of the Allocation System Primitive. If any input is noncompliant or omitted, the Primitive will be invalidated and the Allocation Instance deployment will not move forward.","contentHash":"4fffabae89862cba77dc342937d884a1510ac840223759ad65e13f3cb908edfe","addressRefs":[]},"5a9cf81d-19dd-4f75-9ddc-be35c6b5cfb5":{"id":"5a9cf81d-19dd-4f75-9ddc-be35c6b5cfb5","doc_no":"A.2.2.9.1.2.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1701,"content":"The Allocation System Primitive must be Globally Activated.","contentHash":"4af15e00fb89566e2c177187b10bf9d83d4783e6790e5a2b0175fd3c66f1eb67","addressRefs":[]},"4655b643-b03f-49b7-a474-493c3e059b62":{"id":"4655b643-b03f-49b7-a474-493c3e059b62","doc_no":"A.2.2.9.1.2.2","title":"Core Allocation Vault Address","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1702,"content":"The Prime Agent Artifact must specify the address of the Prime Agent’s Core Allocation Vault.","contentHash":"55c8b1455ad059103a72937dde709eeaaee7cfb3ee8c4bcd8b02da5b28f22d42","addressRefs":[]},"2cdb447e-ebf5-4e57-a722-181178fbe80f":{"id":"2cdb447e-ebf5-4e57-a722-181178fbe80f","doc_no":"A.2.2.9.1.2.3","title":"Core Allocation Buffer Address","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1703,"content":"The Prime Agent Artifact must specify the address of the Prime Agent’s Core Allocation Buffer.","contentHash":"f086af8b21dd8100c36ced11a9db8d393bf4fee48f33bd68712e059af495b477","addressRefs":[]},"9c5e2e23-7756-4856-951b-0bcbecaa867d":{"id":"9c5e2e23-7756-4856-951b-0bcbecaa867d","doc_no":"A.2.2.9.1.2.4","title":"Allocation System Core Security Parameters","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1704,"content":"The Prime Agent Artifact must specify the rate limiters for the Allocation Vault and Core Allocation Buffer, including the address and parameters for each.","contentHash":"168f97338ee88af5a2a4e3e68747753d38de4f5ff081e993a754bc5177502464","addressRefs":[]},"4b8cf927-d5e3-4e5b-8626-62523fb286be":{"id":"4b8cf927-d5e3-4e5b-8626-62523fb286be","doc_no":"A.2.2.9.1.2.5","title":"Capital Faucet","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1705,"content":"The Prime Agent Artifact must specify the address of the Prime Agent’s Capital Faucet and its rate limits.","contentHash":"71d8d18230b6efe2055ed791b1b50f243c43e074944f04c8e5d22244eea006e3","addressRefs":[]},"e4975062-6d19-438b-a5d5-cfc1a7fd8cb9":{"id":"e4975062-6d19-438b-a5d5-cfc1a7fd8cb9","doc_no":"A.2.2.9.1.2.6","title":"List Of Allocation Instances","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1706,"content":"If the Allocation System Primitive is Activated, then the Prime Agent Artifact must list each active Allocation Instance, grouped by blockchain. For each blockchain, the Prime Agent Artifact must specify: (1) the name of the blockchain, (2) the bridging mechanism for the blockchain, if any, (3) the allocation buffer on the blockchain, and (4) the Allocation Instances on the blockchain. For each Allocation Instance, the Prime Agent Artifact must contain the information specified herein.","contentHash":"a1078fde6ec8d1afe9f9eda1f46b6171fa3e5bcb6dc8cfeee119d0b5366a5aac","addressRefs":[]},"6ad0fdb4-bd11-4d5a-a436-0d106873e0ec":{"id":"6ad0fdb4-bd11-4d5a-a436-0d106873e0ec","doc_no":"A.2.2.9.1.2.6.1","title":"Required Allocation Instance Parameters","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1707,"content":"For each Allocation Instance, the Prime Agent Artifact must specify: (1) the name of the Allocation Instance, (2) the address of the Allocation Instance, (3) the rate limit of the conduit for inflows and outflows, (4) any other technical parameters of the Allocation Instance (e.g. maximum slippage, oracles used), (5) data submission protocols, and (6) specification of emergency measures that can be used by Operational GovOps if Required Risk Capital or Asset Liability Management obligations are breached.","contentHash":"fe754cac79f6394dc8a87a791320ce2a575a220db952434bdc379496522e0fa7","addressRefs":[]},"0e4a5264-1365-4e5c-9be4-dac85ed6b46b":{"id":"0e4a5264-1365-4e5c-9be4-dac85ed6b46b","doc_no":"A.2.2.9.1.2.6.2","title":"Required Allocation Instance Allocation Strategy","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1708,"content":"For each Allocation Instance, the Prime Agent Artifact must specify the strategy documents contained herein. These strategy documents must describe in detail how the Allocation Instance should be operated so that the Operational Executor Agent that the Prime Agent has contracted with can operate the Allocation Instance without further input from the Prime Agent or having to make \"judgment calls\". To the extent that the Prime Agent’s strategy cuts across different Allocation Instances, the Prime Agent may include a single set of strategy documents covering all Allocation Instances.","contentHash":"70b8da0949525522aa75bbfa0aa028702f368b708804f258fe65953cb2d03c6e","addressRefs":[]},"3f48dff7-3bf1-44d2-a92f-531ce42be318":{"id":"3f48dff7-3bf1-44d2-a92f-531ce42be318","doc_no":"A.2.2.9.1.2.6.2.1","title":"Required Allocation Instance Asset Liability Management Strategy","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1709,"content":"The allocation strategy for each Allocation Instance should specify how Operational GovOps should adjust the amount of funds allocated to the Conduit based on performance, market conditions, or other factors. It should also specify limits to the amount by which the allocation can be adjusted before a vote of Prime Agent token holders is required.","contentHash":"642be852dab803b82ce21d2c8ca0478915af5f8d56cb7b5073bd7b8a33c1115f","addressRefs":[]},"2cdd38d7-7f85-411b-854e-5768d564c275":{"id":"2cdd38d7-7f85-411b-854e-5768d564c275","doc_no":"A.2.2.9.1.2.6.2.2","title":"Required Allocation Conduit Asset Liability Management Strategy","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1710,"content":"The asset liability management strategy for each Allocation Instance must specify what steps Operational GovOps should take to ensure that the Prime Agent continues to satisfy its Asset Liability Management obligations as the amount of funds allocated to the Conduit changes.","contentHash":"e91b1f5022af9f9fc61f3b70fbda114beb8beb4e86d25b959951c626456734c1","addressRefs":[]},"4363d9c4-afb3-44d1-a72a-9edbd40d415e":{"id":"4363d9c4-afb3-44d1-a72a-9edbd40d415e","doc_no":"A.2.2.9.1.2.6.2.3","title":"Required Allocation Instance Fallback Strategy","type":"Core","depth":6,"parentId":"b6ccdee2-a5e4-4d63-9af5-60b8163673af","order":1711,"content":"The fallback strategy for each Allocation Instance must specify how Operational GovOps should determine when an emergency situation is occurring regarding the Allocation Instance and what actions it should take to protect the Prime Agent from losses associated with the Allocation Instance. The fallback strategy must include emergency measures for Operational GovOps to reduce exposure to, drain, and ultimately shut down the Allocation Instance if Required Risk Capital or Asset Liability Management obligations are breached.","contentHash":"fd917a0c637aadee2b062a0f41f18b9f396a61c23b9ead71186465650aa8f6bf","addressRefs":[]},"d8086dc0-7e77-4c6b-98c7-5fc41337a1ce":{"id":"d8086dc0-7e77-4c6b-98c7-5fc41337a1ce","doc_no":"A.2.2.9.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":4,"parentId":"d1142876-33c2-4e21-9339-d8711525d46f","order":1712,"content":"The Junior Risk Capital Rental Primitive is a mechanism enabling Prime Agents to rapidly rent Junior Risk Capital from each other, ensuring that capital gets deployed to where the best opportunities are.","contentHash":"5a69648c917222ffabcba96f868189b8818ba69349cbf3d6d37dbaedd3c810d2","addressRefs":[]},"bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c":{"id":"bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c","doc_no":"A.2.2.9.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":4,"parentId":"d1142876-33c2-4e21-9339-d8711525d46f","order":1713,"content":"The Asset Liability Management Rental Primitive is a mechanism enabling Prime Agents to trade Asset Liability Management obligations between each other, providing more flexibility in how capital is deployed through the Allocation System and reducing duplicate work.","contentHash":"dbb9911e33eacd05884b96fea951456df14a4f68a3ecd81669b2f9a9936b00bf","addressRefs":[]},"6fa54611-c744-4b9d-897d-b2a20e9cae5d":{"id":"6fa54611-c744-4b9d-897d-b2a20e9cae5d","doc_no":"A.2.2.10","title":"Core Governance Primitives","type":"Section","depth":3,"parentId":"fcde2604-a138-4c1b-9d9a-14895835c907","order":1714,"content":"Core Governance Primitives allow Prime Agents to earn incentives for maintaining and securing Sky Governance frontends as well as borrow from the Smart Burn Engine.","contentHash":"d483b495cea64ed049cfc7ff30b09ef695e3d314ea5794dfb3a2f1da090c632b","addressRefs":[]},"b22d1c08-042a-4466-94fe-9d28951e4d4a":{"id":"b22d1c08-042a-4466-94fe-9d28951e4d4a","doc_no":"A.2.2.10.1","title":"Core Governance Reward Primitive","type":"Core","depth":4,"parentId":"6fa54611-c744-4b9d-897d-b2a20e9cae5d","order":1715,"content":"The Core Governance Reward Primitive is a reward that Sky pays to Prime Agents that provide SKY holders with secure access to the core Sky Governance features, ensuring that the Governance Security of Sky is maintained over time.","contentHash":"54091968f7e059f88837ab25dc3b8010978544bf39a5bb678d3ca9ca3a3f7559","addressRefs":[]},"111bedd1-35aa-4c72-91e1-963550d909bf":{"id":"111bedd1-35aa-4c72-91e1-963550d909bf","doc_no":"A.2.2.10.1.1","title":"Reward Pool","type":"Core","depth":5,"parentId":"b22d1c08-042a-4466-94fe-9d28951e4d4a","order":1716,"content":"The total reward pool for the Core Governance Reward Primitive is 1% of the Net Revenue of Sky, funded out of the Core Council Allocation (see [A.2.3.1.2.2.2 - Core Council Allocation](91b281c2-0687-45a3-939d-0480c7c33f9f)). Of this, 0.5% is paid to Integrators that maintain frontends that facilitate accessible governance, with the other 0.5% paid to the Prime Agents that manage the relationship with those Integrators.","contentHash":"06d4a3f63df9390f567af51fdaadfaf4c5003dd0fcdcf2f6a33b9916ece7b48d","addressRefs":[]},"a59cee2a-864e-4dbb-9364-bdf121573cb2":{"id":"a59cee2a-864e-4dbb-9364-bdf121573cb2","doc_no":"A.2.2.10.1.2","title":"Eligible Recipients","type":"Core","depth":5,"parentId":"b22d1c08-042a-4466-94fe-9d28951e4d4a","order":1717,"content":"In order for an Integrator and the Prime Agent that manages the relationship with such Integrator to be eligible for the Core Governance Reward, the frontend maintained by the Integrator must satisfy compliance requirements as specified in [A.2.2.10.1.3 - Compliance Requirements](068c37b5-2cda-4bcc-90af-7b70c746dbc3).\n\nA single entity may serve as both the Integrator operating a frontend and the Prime Agent managing the relationship with that Integrator, in which case such entity is eligible to receive both the Integrator and Prime Agent rewards for that frontend.\n\nThe current eligible recipients for the Core Governance Reward Primitive are specified in the documents herein.","contentHash":"4a41787b4f45be61a6303cf9b6975b7b0d612d80e884ec4864d1352cb450d76a","addressRefs":[]},"e8272862-e80d-470c-a0da-f964b6df110d":{"id":"e8272862-e80d-470c-a0da-f964b6df110d","doc_no":"A.2.2.10.1.2.1","title":"Current Eligible Recipients","type":"Core","depth":6,"parentId":"a59cee2a-864e-4dbb-9364-bdf121573cb2","order":1718,"content":"The current eligible recipients for the Core Governance Reward Primitive are:\n\n- **Skybase** - Skybase is eligible to receive the Core Governance Reward with respect to the [https://sky.money/](https://sky.money/) frontend as both the Integrator that operates the frontend and the Prime Agent that manages the relationship, and therefore receives both the Integrator reward and the Prime Agent reward for this frontend.","contentHash":"5b1efca316861fb4bb32199215b14ee7266d990b5e6fd4168e3b28d58474e54b","addressRefs":[]},"068c37b5-2cda-4bcc-90af-7b70c746dbc3":{"id":"068c37b5-2cda-4bcc-90af-7b70c746dbc3","doc_no":"A.2.2.10.1.3","title":"Compliance Requirements","type":"Core","depth":5,"parentId":"b22d1c08-042a-4466-94fe-9d28951e4d4a","order":1719,"content":"Security and information standards for compliant frontends are specified in the documents herein.","contentHash":"f57091a6ba8af95236339b8a4af6ac1915ea839ff7597ac74f67c007fe3c3070","addressRefs":[]},"a6ab8a87-bd53-4227-9ede-1dd65094989c":{"id":"a6ab8a87-bd53-4227-9ede-1dd65094989c","doc_no":"A.2.2.10.1.3.1","title":"Security Standards","type":"Core","depth":6,"parentId":"068c37b5-2cda-4bcc-90af-7b70c746dbc3","order":1720,"content":"Specific security standards for compliant frontends will be specified in a future iteration of the Atlas.","contentHash":"031b5607f5f63654bf2b8cebe2a355c70a581bad64c8433ca6b0f34dd624d55a","addressRefs":[]},"6c53d0a0-f5ce-4005-a887-6f94b08e4a28":{"id":"6c53d0a0-f5ce-4005-a887-6f94b08e4a28","doc_no":"A.2.2.10.1.3.2","title":"Information Standards","type":"Core","depth":6,"parentId":"068c37b5-2cda-4bcc-90af-7b70c746dbc3","order":1721,"content":"Specific information and disclosure standards for compliant frontends will be specified in a future iteration of the Atlas.","contentHash":"d2722098ae2115e550b7601ebbca4858211162d81e53f273e80b6f0da8ec67a7","addressRefs":[]},"72ce2c27-6d72-4b64-8a3c-083be9fe7659":{"id":"72ce2c27-6d72-4b64-8a3c-083be9fe7659","doc_no":"A.2.2.10.1.4","title":"Distribution Mechanism","type":"Core","depth":5,"parentId":"b22d1c08-042a-4466-94fe-9d28951e4d4a","order":1722,"content":"The documents herein define how the total reward pool is distributed to individual recipients.","contentHash":"180abccbcb1d9628d7d754ce8d46434887a39132ca49ea77cd2d72fa3d395c13","addressRefs":[]},"dc825d62-60cf-4701-ac8f-b48257b4f9a6":{"id":"dc825d62-60cf-4701-ac8f-b48257b4f9a6","doc_no":"A.2.2.10.1.4.1","title":"Integration With Treasury Management Function","type":"Core","depth":6,"parentId":"72ce2c27-6d72-4b64-8a3c-083be9fe7659","order":1723,"content":"Distributions of Core Governance Rewards are made on a monthly basis as part of the Treasury Management Function.","contentHash":"18fbbe11296dc87d18d3930504cb542128e902309c43c476a1c7861e7c04f385","addressRefs":[]},"f8d35814-d8bb-423f-97ce-35629bcc7a5e":{"id":"f8d35814-d8bb-423f-97ce-35629bcc7a5e","doc_no":"A.2.2.10.1.4.2","title":"Allocation Based On Staked SKY","type":"Core","depth":6,"parentId":"72ce2c27-6d72-4b64-8a3c-083be9fe7659","order":1724,"content":"Each distribution to Integrators is allocated pro rata between Integrators based on the percentage of SKY staked through eligible frontends maintained by each Integrator. Each distribution to Prime Agents is allocated pro rata between Prime Agents based on the percentage of SKY staked through eligible frontends maintained by Integrators managed by each Prime Agent.","contentHash":"9b8a36bca3f34e9a2263bddfdaacdde9ced79948dc06fa31ee681ebf36411efb","addressRefs":[]},"b16cb8a3-aea3-4fda-b904-eb782ea7a8e1":{"id":"b16cb8a3-aea3-4fda-b904-eb782ea7a8e1","doc_no":"A.2.2.10.1.4.2.1","title":"Tracking Via Reward Codes","type":"Core","depth":6,"parentId":"72ce2c27-6d72-4b64-8a3c-083be9fe7659","order":1725,"content":"The amount of SKY staked through each eligible frontend is tracked using Reward Codes. Eligible frontends pass a Reward Code identifying the Integrator and associated Prime Agent when users stake SKY. Each eligible Integrator is assigned a unique Reward Code by Operational GovOps for the Prime Agent managing the relationship with the Integrator. Reward Codes for each Integrator are recorded in the associated Instance of the Core Governance Reward Primitive in the Agent Artifact of the Prime Agent managing the relationship with the Integrator.","contentHash":"1222f0e1712e7fd99feb68e3ff331db3b79b886544c54c540c35c3d205a423e6","addressRefs":[]},"9a723ca1-8daa-4948-a808-4a2b9e801da6":{"id":"9a723ca1-8daa-4948-a808-4a2b9e801da6","doc_no":"A.2.2.10.1.4.3","title":"Distribution Through Prime Agents","type":"Core","depth":6,"parentId":"72ce2c27-6d72-4b64-8a3c-083be9fe7659","order":1726,"content":"All distributions to a Prime Agent and Integrators managed by it are paid to the Prime Agent. The Prime Agent is then responsible for paying the portion due to each Integrator it manages.","contentHash":"3b6a25e211869747347883a861d180b727258884680c5a85573ba0a909f847c2","addressRefs":[]},"b3f97303-4d41-497c-b931-9337c518bd7e":{"id":"b3f97303-4d41-497c-b931-9337c518bd7e","doc_no":"A.2.2.10.1.5","title":"Retroactive Effectiveness","type":"Core","depth":5,"parentId":"b22d1c08-042a-4466-94fe-9d28951e4d4a","order":1727,"content":"The allocations to the Core Governance Reward Primitive are effective retroactive to May 19, 2025. Amounts accrued and not yet disbursed are funded out of the Core Council Buffer (see [A.2.3.1.2.2.2.1 - Core Council Buffer](8b6781d7-f35c-4ffe-b8ed-299fa98e3da7)).","contentHash":"cf6a89a4c5808a3cb4ee2782d7bf550b188680c82c181e03569f51a64957e8f3","addressRefs":[]},"6c0af059-5d33-4e2b-90f1-1606957b8f85":{"id":"6c0af059-5d33-4e2b-90f1-1606957b8f85","doc_no":"A.2.3","title":"Treasury Management","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1728,"content":"The Sky Treasury Management Function defines how all Net Revenue of the Sky Protocol is distributed among various downstream functions or buffers. This ensures that all necessary functions are adequately funded, allowing all actors to focus on growing the ecosystem in a positive sum way.","contentHash":"98f6fb63bf688a835fc663a8b81d45bf119a4304fb03c67fd2bf53d199d9c2d9","addressRefs":[]},"9bd2f02c-8111-4431-9b3a-46d3695af1e1":{"id":"9bd2f02c-8111-4431-9b3a-46d3695af1e1","doc_no":"A.2.3.1","title":"Treasury Management","type":"Section","depth":3,"parentId":"6c0af059-5d33-4e2b-90f1-1606957b8f85","order":1729,"content":"The documents herein define the Sky Treasury Management Function.","contentHash":"ed646bb90f98f2c922a5e6d42b73ed5727517bd048e18d4c723750df2500d685","addressRefs":[]},"6e187fc0-6e5a-4384-b0b6-cdfd87a7d400":{"id":"6e187fc0-6e5a-4384-b0b6-cdfd87a7d400","doc_no":"A.2.3.1.1","title":"Integration With Monthly Settlement Cycle","type":"Core","depth":4,"parentId":"9bd2f02c-8111-4431-9b3a-46d3695af1e1","order":1730,"content":"The Sky Treasury Management Function is synchronized with the Monthly Settlement Cycle. See [A.2.4 - Sky Core Monthly Settlement Cycle](6f8d5065-d6ff-4add-9a28-eadeffa7ed1a). At the conclusion of each MSC, the Net Revenue of the Sky Protocol for the preceding month is calculated and allocated according to the waterfall process defined in [A.2.3.1.2 - Allocation Steps](7932c8f3-ce44-49ea-adc4-f6391c621c6e).","contentHash":"acbc6f36f6e0513c8ff96bfa4e9ee67f3a2548bea9822de3927c5e04b7125bfa","addressRefs":[]},"7932c8f3-ce44-49ea-adc4-f6391c621c6e":{"id":"7932c8f3-ce44-49ea-adc4-f6391c621c6e","doc_no":"A.2.3.1.2","title":"Allocation Steps","type":"Core","depth":4,"parentId":"9bd2f02c-8111-4431-9b3a-46d3695af1e1","order":1731,"content":"The documents herein define the allocation steps of the Sky Treasury Management Function. The process is divided into steps beginning with Net Revenue. These steps form a \"waterfall\" with each previous step needing to be fully funded before any funds can be allocated to later steps.","contentHash":"e1f8ce0e9a89f89049c2240bf142d52b98f25a4737a07c2e56d4bda4ef76de39","addressRefs":[]},"c09435ff-d876-442a-899c-ad494175500b":{"id":"c09435ff-d876-442a-899c-ad494175500b","doc_no":"A.2.3.1.2.1","title":"Step 0: Net Revenue","type":"Core","depth":5,"parentId":"7932c8f3-ce44-49ea-adc4-f6391c621c6e","order":1732,"content":"The sole function of Step 0 is to establish the Net Revenue of the Sky Protocol. It performs no allocations to downstream functions or buffers, unlike subsequent steps for which this Net Revenue serves as the input.\n\nAll items of Income and Expense are recognized on a \"cash basis\" based on when USDS/DAI enter or leave the Sky Surplus Buffer. Transfers out of accounts other than the Sky Surplus Buffer are not recognized as Expenses, except as provided in [A.2.3.1.2.2.2.1.6.4 - Expense Recognition For Legacy Account Consolidation](1760b35f-da5a-4504-a014-dd7a611b4c0e).","contentHash":"f3ac0124e80dd9b8c0a79df60b7e381f768c4af27759dc0b47a75ea7ed440f16","addressRefs":[]},"bddce7bf-c568-444b-b196-e15a99016696":{"id":"bddce7bf-c568-444b-b196-e15a99016696","doc_no":"A.2.3.1.2.1.1","title":"Net Revenue","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1733,"content":"Net Revenue is equal to Income minus Expenses. Income is defined in [A.2.3.1.2.1.2 - Income](a0fab275-399d-41ad-a9b0-411d3e5ea5c9). Expenses are defined in [A.2.3.1.2.1.3 - Expenses](88e3c367-fe30-4d59-8ba1-eddc0d88a0ea). Income and Expenses are defined such that Net Revenue must always be positive","contentHash":"7f12e364029040e55e28bb4a0368a876f2f071cad01ae7b011832c694eba877a","addressRefs":[]},"a0fab275-399d-41ad-a9b0-411d3e5ea5c9":{"id":"a0fab275-399d-41ad-a9b0-411d3e5ea5c9","doc_no":"A.2.3.1.2.1.2","title":"Income","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1734,"content":"The documents herein define each of the components of the Income of the Sky Protocol. These components are added together to arrive at total Income.","contentHash":"7a388c2bd144a619f48a9f2f7e5f6a18973bb2b3f4522af424ee30d3add55eed","addressRefs":[]},"13d342a7-e9cf-4fb2-afc1-a1dd36c47054":{"id":"13d342a7-e9cf-4fb2-afc1-a1dd36c47054","doc_no":"A.2.3.1.2.1.2.1","title":"Stability Fees From Base Rate","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1735,"content":"Stability Fees are the fees that Sky Core charges Prime Agents to borrow from Sky. See [A.3.1.2.1 - Base Rate](228f9955-6bba-4252-a101-5529e7a300b9). Sky Core’s legacy ALM infrastructure is currently being transferred to Prime Agents; during this transition period and until this transfer is fully complete, income generated from the Sky Core Collateral Portfolio contributes to net revenue. See [A.3.3.1.4 - Application To Sky Core](6e050b66-0bc8-43f1-b32d-2220c9df466b).","contentHash":"4d2e461632f975e3e598f743d26f6f136600cc2d5aa87060490c4d51a0038c3a","addressRefs":[]},"02b5422a-093d-4e21-86ff-5cfcd5af8ed5":{"id":"02b5422a-093d-4e21-86ff-5cfcd5af8ed5","doc_no":"A.2.3.1.2.1.2.2","title":"Internal Senior Risk Capital Income","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1736,"content":"Internal Senior Risk Capital income is the revenue attributed to Sky from the total payments made by Primes for Originated Senior Risk Capital (OSRC). ISRC itself is sourced from Aggregate Backstop Capital, as specified in [A.2.3.1.3 - Sourcing Of Internal Senior Risk Capital](ac7a6636-acbc-40c9-abc1-4543c0beb300). While Primes pay a single clearing price for their OSRC based on the monthly Origination Process, the total revenue received by Sky is subsequently allocated proportionally, with the portion corresponding to ISRC's share of the Total Senior Risk Capital (TSRC) pool designated as ISRC Income.","contentHash":"908474a201c9532c5bf9ca2bf9ecbedd338066a7a2063e81ede92d951e12aa5a","addressRefs":[]},"f01ce2f4-6bbe-4d70-8b22-edb80d8fb624":{"id":"f01ce2f4-6bbe-4d70-8b22-edb80d8fb624","doc_no":"A.2.3.1.2.1.2.3","title":"External Senior Risk Capital Fees","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1737,"content":"External Senior Risk Capital Fees are levied by Sky and calculated as 5% of the net interest earnings generated by the External Senior Risk Capital (ESRC) pool each Monthly Settlement Cycle. These earnings represent the portion of the total revenue from Primes' Originated Senior Risk Capital (OSRC) payments that is attributed proportionally to ESRC, based on its contribution to the Total Senior Risk Capital (TSRC) pool for that cycle. This 5% fee is deducted before the remaining ESRC earnings contribute to the srUSDS conversion rate. See [A.3.2.2.4.2.3.3.2 - ESRC Earnings Fee](559f6fb6-daf6-41b2-9882-53a91aaf132f).","contentHash":"ed68ae736c5a5bcf75da6d5dcf084dc0dab842c7faed1ab537ecf2713b7869b2","addressRefs":[]},"c650b38c-aa7c-42b4-94ed-6320238b0264":{"id":"c650b38c-aa7c-42b4-94ed-6320238b0264","doc_no":"A.2.3.1.2.1.2.4","title":"Agent Upkeep Fees","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1738,"content":"Agent Upkeep Fees are fees paid by Agents to contribute to the long-term sustainability of the Sky Ecosystem. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"de2756d345a03c0dc41861a5f64a1d3a28a836c537f1eaf86e5f59952d4ae649","addressRefs":[]},"1b1c9cc0-e410-4bb3-aa37-c639ca392dd7":{"id":"1b1c9cc0-e410-4bb3-aa37-c639ca392dd7","doc_no":"A.2.3.1.2.1.2.5","title":"Agent Creation Fees","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1739,"content":"Agent Creation Fees are one-time payments collected from founding teams when establishing new Prime Agents. See [A.2.2.3.1.2 - Creation Fee](708ad6b6-8e4a-46b3-9848-523d00a57420).","contentHash":"6e8062c0656f9cab6bcc00328c1e1bee29cca6a4aaf966a83a9944d3d0058448","addressRefs":[]},"aebc1c92-6538-4a1c-a90c-4928d9924eeb":{"id":"aebc1c92-6538-4a1c-a90c-4928d9924eeb","doc_no":"A.2.3.1.2.1.2.6","title":"Other Income","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1740,"content":"Other Income includes all sources of income of the Sky Protocol not identified in the other subdocuments of [A.2.3.1.2.1.2 - Income](a0fab275-399d-41ad-a9b0-411d3e5ea5c9), including, without limitation, the sources of income specified in the documents herein.","contentHash":"a099215a208d2fb493de32fd578e0b12f11d3ac897f9883c43b37aec182b0363","addressRefs":[]},"4a3e1d4d-a1d7-4207-9af8-fa0fd195a929":{"id":"4a3e1d4d-a1d7-4207-9af8-fa0fd195a929","doc_no":"A.2.3.1.2.1.2.6.1","title":"Sky Core Vault Income","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1741,"content":"Sky Core Vault Income is all income from Sky Core Vaults, including, without limitation, liquidation penalties. Sky Core Vaults include, without limitation, (1) all Sky Core Vaults specified in [A.3.7.1.1.1 - Vault Types](64971463-0650-4462-b9c4-1eecb704fa1a) and (2) the Sky Core Vault associated with SKY-Backed Borrowing (see [A.4.4.1.3 - SKY-Backed Borrowing](264b1787-cd75-4d28-9c14-c7d5a724eba7)).","contentHash":"07e5b57e5a1339b0ec9c31df7eca32f5d36d205f399b3035dadc808319ecd8d6","addressRefs":[]},"edb32ca7-329f-437b-bf02-2bf0e78e7ea7":{"id":"edb32ca7-329f-437b-bf02-2bf0e78e7ea7","doc_no":"A.2.3.1.2.1.2.6.2","title":"LitePSM Income","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1742,"content":"LitePSM Income is all income from the LitePSM.","contentHash":"a6408637fd917614db7f4c4ea71773895bcc3d5c1df9588e5fb0758454289576","addressRefs":[]},"88e3c367-fe30-4d59-8ba1-eddc0d88a0ea":{"id":"88e3c367-fe30-4d59-8ba1-eddc0d88a0ea","doc_no":"A.2.3.1.2.1.3","title":"Expenses","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1743,"content":"The documents herein define each of the components of Expenses. These components are added together to arrive at total Expenses.","contentHash":"48d84386005663651bf96e95a3e87185c8e62251538820ac495dcc5025d26dcf","addressRefs":[]},"e6b86b0e-163d-4be4-928d-a81dd6700d57":{"id":"e6b86b0e-163d-4be4-928d-a81dd6700d57","doc_no":"A.2.3.1.2.1.3.1","title":"Sky Savings Rate Paid To sUSDS Holders","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1744,"content":"The Sky Savings Rate is the interest expense paid to sUSDS holders on their balances. It also includes all other savings-related expenses (other than those paid through the Integration Boost), such as the Dai Savings Rate expense and interest on stUSDS.","contentHash":"9c6a1ec30bf36421ee541dcd3abb1fd5031f186e5ca16e4f3b97241489a1c8e2","addressRefs":[]},"feb95aa7-e1b1-4ba8-a9a5-f99b5a21477e":{"id":"feb95aa7-e1b1-4ba8-a9a5-f99b5a21477e","doc_no":"A.2.3.1.2.1.3.2","title":"Sky Savings Rate Paid Through Integration Boost","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1745,"content":"The Integration Boost provides the equivalent of the Sky Savings Rate to users of decentralized finance protocols who hold USDS balances. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"36e0e28cd0496840bfd0aca6ae42696f49e1d815a8544447e88f1f471bb3e691","addressRefs":[]},"2177f303-a0a7-4807-b815-d17aa76a264e":{"id":"2177f303-a0a7-4807-b815-d17aa76a264e","doc_no":"A.2.3.1.2.1.3.3","title":"Distribution Rewards","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1746,"content":"The Distribution Reward is paid to Prime Agents and third-party partners that drive adoption of USDS. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"82de904bb022ff49d18b9bb38bee8cd8fab1bf4e687f16d2f4f26e7e4d872cca","addressRefs":[]},"3aa5b01e-6661-4b01-b32c-ea7b02fbedcb":{"id":"3aa5b01e-6661-4b01-b32c-ea7b02fbedcb","doc_no":"A.2.3.1.2.1.3.4","title":"Reimbursement Rewards","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1747,"content":"Reimbursement Rewards are paid to Prime Agents to reimburse them for the costs of building common infrastructure used by the entire Sky Ecosystem, such as Token SkyLink deployments.","contentHash":"1d1d3d21130615b45329245e72a793f8f652992656a74d2a94ac5182271d50b7","addressRefs":[]},"33c56bad-c422-48f4-bcca-dc8794c6a0da":{"id":"33c56bad-c422-48f4-bcca-dc8794c6a0da","doc_no":"A.2.3.1.2.1.3.5","title":"Pioneer Rewards","type":"Core","depth":6,"parentId":"c09435ff-d876-442a-899c-ad494175500b","order":1748,"content":"Pioneer Rewards are paid to Pioneer Primes as specified in [A.2.2.8.3.1.4 - Pioneer Incentive Pool](04edac33-19d5-4a87-a8ab-945a0cd57771).","contentHash":"8e56e2daffdd04e8ba9e4203ec6fcd83d2d037b986d50a2609588ed5cdfd8cc6","addressRefs":[]},"324e9d22-70fe-4e44-82ab-118815f5c42e":{"id":"324e9d22-70fe-4e44-82ab-118815f5c42e","doc_no":"A.2.3.1.2.2","title":"Step 1: Security And Maintenance","type":"Core","depth":5,"parentId":"7932c8f3-ce44-49ea-adc4-f6391c621c6e","order":1749,"content":"All of the Net Revenue from Step 0 (see [A.2.3.1.2.1.1 - Net Revenue](bddce7bf-c568-444b-b196-e15a99016696)) becomes Step 1 Capital. Twenty percent (20%) of Step 1 Capital is allocated for security and maintenance of the Sky Ecosystem as specified in the documents herein. The remaining eighty percent (80%) of Step 1 Capital becomes Step 2 Capital and is allocated as specified in [A.2.3.1.2.3 - Step 2: Aggregate Backstop Capital](2b28d464-e683-48ba-9a66-2fee05ea0a88).","contentHash":"67a30ff51f208d2d548569f21287049ca26a6f371bae4fd1e9265f512eceb48d","addressRefs":[]},"728ea3d3-606a-4080-bc56-4a9e2c7fecb3":{"id":"728ea3d3-606a-4080-bc56-4a9e2c7fecb3","doc_no":"A.2.3.1.2.2.1","title":"Fortification Foundation Allocation","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1750,"content":"Ten percent (10%) of Step 1 Capital is allocated to the Fortification Foundation, covering legal defense, resilience, unquantifiable risk management, and protocol development and growth. See [A.2.13.1.2 - Fortification Foundation Grants](ec2ebbba-6944-44cb-a04d-4572c6bea1e7). Until the Fortification Foundation is fully operational, this allocation may be directed to the Sky Frontier Foundation on an interim basis.","contentHash":"0e048a4ade33af7ffbd1838b05bfc8473545781b174daf9b10d0af954a8b53a0","addressRefs":[]},"91b281c2-0687-45a3-939d-0480c7c33f9f":{"id":"91b281c2-0687-45a3-939d-0480c7c33f9f","doc_no":"A.2.3.1.2.2.2","title":"Core Council Allocation","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1751,"content":"Ten percent (10%) of Step 1 Capital is allocated to the Core Council, which directs these funds across governance operations and development work. This allocation funds, without limitation, active Core Executor Agents, Core Executor Agents whose terms have ended in the last four (4) years, Aligned Delegates, the Core Governance Reward Primitive (see [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a)), and grants to the Sky Frontier Foundation (see [A.2.13.1.1 - Sky Frontier Foundation Grants](1f5d9b2d-d94d-4945-bcf5-74b9152de90c)). At the discretion of the Core Council, funds may be allocated to pay these recipients directly or to fund the Core Council Buffer (see [A.2.3.1.2.2.2.1 - Core Council Buffer](8b6781d7-f35c-4ffe-b8ed-299fa98e3da7)) and Aligned Delegates Buffer (see [A.2.3.1.2.2.2.2 - Aligned Delegates Buffer](05fa5c41-26ca-4c25-94dd-834ef72c318a)) for subsequent disbursement.\n\nThe Core Council is authorized to direct grants from this allocation to the Sky Frontier Foundation without a separate governance decision for each grant.\n\nThe specific allocation among the components of the Core Council Allocation, including the mechanism by which Core Executor Agents are elected to Core Executor Slots, will be specified in a future iteration of the Atlas.","contentHash":"c3b1ce9e778c92f8d02fe6f93110e64c29333888de098189bcb3326289f91358","addressRefs":[]},"8b6781d7-f35c-4ffe-b8ed-299fa98e3da7":{"id":"8b6781d7-f35c-4ffe-b8ed-299fa98e3da7","doc_no":"A.2.3.1.2.2.2.1","title":"Core Council Buffer","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1752,"content":"The Core Council Buffer is a multisig used to transfer funds on behalf of the Core Council.","contentHash":"77e2f049ce267c40cc38410c021753e4ee9612f706d4b8b66e1eb945ea763bf8","addressRefs":[]},"af082bd0-fdcd-4ec1-980a-7fce50e77ed1":{"id":"af082bd0-fdcd-4ec1-980a-7fce50e77ed1","doc_no":"A.2.3.1.2.2.2.1.1","title":"Core Council Buffer Multisig Address","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1753,"content":"The address of the Core Council Buffer Multisig on the Ethereum Mainnet is `0x210CFcF53d1f9648C1c4dcaEE677f0Cb06914364`.","contentHash":"52c24ec8b91e9a13bbb1b4ae05b89863df5ee4630d3375488ec3f9edda490dfa","addressRefs":["0x210cfcf53d1f9648c1c4dcaee677f0cb06914364"]},"7f9cc28d-75af-4fe0-b090-8c85cda9656a":{"id":"7f9cc28d-75af-4fe0-b090-8c85cda9656a","doc_no":"A.2.3.1.2.2.2.1.2","title":"Core Council Buffer Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1754,"content":"The Core Council Buffer Multisig has a 5/6 signing requirement.","contentHash":"66b4699b2ce5b30387b1a9f0b8ce930be0dc0beae24e0e8ee9d6303a57cb9926","addressRefs":[]},"5aeba17d-3869-447d-adcd-8c55f41afc01":{"id":"5aeba17d-3869-447d-adcd-8c55f41afc01","doc_no":"A.2.3.1.2.2.2.1.3","title":"Core Council Buffer Multisig Signers","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1755,"content":"The signers of the Core Council Buffer Multisig are two (2) addresses controlled by the Core Facilitator, three (3) addresses controlled by Core GovOps, and one (1) address controlled by Operational GovOps Soter Labs.","contentHash":"9771ac9916dd6fc2db7fe703968ab1ee0659bb311c2de0c3978623fe4d907b69","addressRefs":[]},"dc6474f6-d285-4e1e-9902-406def4b72be":{"id":"dc6474f6-d285-4e1e-9902-406def4b72be","doc_no":"A.2.3.1.2.2.2.1.4","title":"Core Council Buffer Multisig Usage Standards","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1756,"content":"The signers must use the Core Council Buffer Multisig to disburse funds on behalf of the Core Council.","contentHash":"d59409c118aadb89101fc71eaaf8d29a3fe3b781ad3dc88407795c4151a26ce3","addressRefs":[]},"a56fe3ee-c11a-4df0-9cc3-677688c5563d":{"id":"a56fe3ee-c11a-4df0-9cc3-677688c5563d","doc_no":"A.2.3.1.2.2.2.1.5","title":"Core Council Buffer Multisig Modification","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1757,"content":"The signers can change the signers of the Core Council Buffer Multisig so long as:\n\n- there are exactly six (6) signers;\n- exactly five (5) signers are required to execute transactions; and\n- two (2) signers are controlled by the Core Facilitator, three (3) signers are controlled by Core GovOps, and one (1) signer is controlled by Operational GovOps Soter Labs.","contentHash":"2bfddf73b3bd8b93d2a73b6c196db6241e0f9db47cf2e1c03ef0d7704dd37e15","addressRefs":[]},"8c8778c4-ff4c-4add-ae03-5f32a052f433":{"id":"8c8778c4-ff4c-4add-ae03-5f32a052f433","doc_no":"A.2.3.1.2.2.2.1.6","title":"Consolidation Of Funds From Legacy Accounts","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1758,"content":"All funds in Legacy Accounts (see [A.2.3.1.2.2.2.1.6.1 - Legacy Accounts](6f7153e1-c535-4a35-a7cf-7a66180a1c0e)) must be consolidated into the Core Council Buffer or the Demand Side Buffer (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)) as specified in the documents herein.","contentHash":"79b3adf04697fad682dc1f42680094e9e0a73675a54a4cf2c795f85f1b52cc0f","addressRefs":[]},"6f7153e1-c535-4a35-a7cf-7a66180a1c0e":{"id":"6f7153e1-c535-4a35-a7cf-7a66180a1c0e","doc_no":"A.2.3.1.2.2.2.1.6.1","title":"Legacy Accounts","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1759,"content":"Legacy Accounts are all accounts controlled by Sky Core, with the exception of the Core Council Buffer, the Aligned Delegates Buffer (see [A.2.3.1.2.2.2.2 - Aligned Delegates Buffer](05fa5c41-26ca-4c25-94dd-834ef72c318a)), and the Demand Side Buffer and its auxiliary accounts (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)). This includes, without limitation:\n\n- the former Distribution Reward Controller Wallet;\n- the former Integration Boost Wallets; and\n- the Sky Ecosystem Liquidity Bootstrapping Budget.","contentHash":"ad1dd1bfe8d1517040630aae40c53aa12153434155c2287a3b92a79cec46356c","addressRefs":[]},"294154f2-8d36-4104-a660-89a7b52eeac7":{"id":"294154f2-8d36-4104-a660-89a7b52eeac7","doc_no":"A.2.3.1.2.2.2.1.6.2","title":"Ecosystem Actors Must Consolidate All Funds From Legacy Accounts","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1760,"content":"Relevant Ecosystem Actors must take all necessary actions to transfer all funds from Legacy Accounts into the Core Council Buffer or the Demand Side Buffer (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)).","contentHash":"efca1426b7b59abe6b3a53a8652a13602b63bd09e547004e0a73079c2553483d","addressRefs":[]},"fae8cff1-5ecc-4f4f-a4e1-622df4112eeb":{"id":"fae8cff1-5ecc-4f4f-a4e1-622df4112eeb","doc_no":"A.2.3.1.2.2.2.1.6.3","title":"Legacy Accounts Are Replaced","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1761,"content":"All funds that would otherwise be transferred into or out of Legacy Accounts must instead be transferred into or out of the Core Council Buffer or the Demand Side Buffer (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)).","contentHash":"b559fd645e4e329747cae61c1f8a46ca2f0b1629cbb6390891b9a2c4a3d336c4","addressRefs":[]},"1760b35f-da5a-4504-a014-dd7a611b4c0e":{"id":"1760b35f-da5a-4504-a014-dd7a611b4c0e","doc_no":"A.2.3.1.2.2.2.1.6.4","title":"Expense Recognition For Legacy Account Consolidation","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1762,"content":"The consolidation of funds from Legacy Accounts into the Core Council Buffer or the Demand Side Buffer (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)) is recognized as a one-time expense for purposes of [A.2.3.1.2.1 - Step 0: Net Revenue](c09435ff-d876-442a-899c-ad494175500b). This achieves the same result as if the funds in Legacy Accounts had been returned to the Sky Surplus Buffer and subsequently transferred to the relevant downstream account.","contentHash":"f43a7204fee6e7f318f5b40878f41ccc7d13c0ca4eec140533dc5aee3b1d7998","addressRefs":[]},"05fa5c41-26ca-4c25-94dd-834ef72c318a":{"id":"05fa5c41-26ca-4c25-94dd-834ef72c318a","doc_no":"A.2.3.1.2.2.2.2","title":"Aligned Delegates Buffer","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1763,"content":"The Aligned Delegates Buffer is a multisig controlled by the Core Facilitator and Core GovOps to transfer funds to Aligned Delegates.","contentHash":"211bc0cb5e4b011b4da87eac5e284f226fe1bc388a097f2120bdafb9c395aada","addressRefs":[]},"744ffdce-188e-403a-a0f4-532a27879cf5":{"id":"744ffdce-188e-403a-a0f4-532a27879cf5","doc_no":"A.2.3.1.2.2.2.2.1","title":"Aligned Delegates Buffer Multisig Address","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1764,"content":"The address of the Aligned Delegates Buffer Multisig on the Ethereum Mainnet is `0x37FC5d447c8c54326C62b697f674c93eaD2A93A3`.","contentHash":"2e80b434db67480792d72e1357ccc479a021ec873886948c87186f62d450b2e4","addressRefs":["0x37fc5d447c8c54326c62b697f674c93ead2a93a3"]},"b3672c98-07ca-488f-8a26-461bf8d14aae":{"id":"b3672c98-07ca-488f-8a26-461bf8d14aae","doc_no":"A.2.3.1.2.2.2.2.2","title":"Aligned Delegates Buffer Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1765,"content":"The Aligned Delegates Buffer Multisig has a 3/4 signing requirement.","contentHash":"39d2de4044c9d906c5fa6ded65e0f33e9af699dad28eb279517061d0d0ebfbb8","addressRefs":[]},"f0652394-ec87-4b08-abed-e15fd0799ab1":{"id":"f0652394-ec87-4b08-abed-e15fd0799ab1","doc_no":"A.2.3.1.2.2.2.2.3","title":"Aligned Delegates Buffer Multisig Signers","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1766,"content":"The signers of the Aligned Delegates Buffer Multisig are two (2) addresses controlled by the Core Facilitator and two (2) addresses controlled by Core GovOps.","contentHash":"104df06ed03c240bc0641f93b8862aad86e473f07ce7040954b7832589d0da1b","addressRefs":[]},"3ce8a599-f70b-4dad-9d71-a69d812c4ea8":{"id":"3ce8a599-f70b-4dad-9d71-a69d812c4ea8","doc_no":"A.2.3.1.2.2.2.2.4","title":"Aligned Delegates Buffer Multisig Usage Standards","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1767,"content":"The Core Facilitator and Core GovOps must use the Aligned Delegates Buffer Multisig to disburse funds to Aligned Delegates.","contentHash":"c62996b22e24813624b90cf471d5c10ad65a481b1a98a2ed4bf14768f0dd8df3","addressRefs":[]},"b8b38333-2763-47e1-9e34-0b37c750201a":{"id":"b8b38333-2763-47e1-9e34-0b37c750201a","doc_no":"A.2.3.1.2.2.2.2.5","title":"Aligned Delegates Buffer Multisig Modification","type":"Core","depth":6,"parentId":"324e9d22-70fe-4e44-82ab-118815f5c42e","order":1768,"content":"The Core Facilitator and Core GovOps can change the signers of the Aligned Delegates Buffer Multisig so long as:\n\n- there are at least four (4) signers;\n- a majority of signers are required to execute transactions; and\n- an equal number of signers are controlled by the Core Facilitator and Core GovOps.","contentHash":"7aa866eac8430e23db63d8869dac9063388031b094fc07bfe441bb65cc560e62","addressRefs":[]},"2b28d464-e683-48ba-9a66-2fee05ea0a88":{"id":"2b28d464-e683-48ba-9a66-2fee05ea0a88","doc_no":"A.2.3.1.2.3","title":"Step 2: Aggregate Backstop Capital","type":"Core","depth":5,"parentId":"7932c8f3-ce44-49ea-adc4-f6391c621c6e","order":1769,"content":"Step 1 Capital that remains after the Step 1 allocation becomes Step 2 Capital.\n\nThe allocation of Step 2 Capital depends on the level of Aggregate Backstop Capital (see [A.3.5.3.1.2 - Aggregate Backstop Capital](6dbead44-5ac4-4c5b-be3c-64eddd004e5c)) relative to the Turbo-Fill Floor (see [A.3.5.3.2.2 - Turbo-Fill Floor](db2aaf07-4ebb-4e5d-ae5e-575717d8fbcd)) and the Target Aggregate Backstop Capital (see [A.3.5.3.2.1 - Target Aggregate Backstop Capital](f73dda95-0b1c-4bdc-b957-469253d27281)).\n\nWhen Aggregate Backstop Capital is below the Turbo-Fill Floor, fifty percent (50%) of Step 2 Capital is retained to grow Aggregate Backstop Capital. The remainder of Step 2 Capital becomes Step 3 Capital and is allocated as specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121).\n\nWhen Aggregate Backstop Capital is at or above the Turbo-Fill Floor and below the Target Aggregate Backstop Capital, the portion of Step 2 Capital retained to grow Aggregate Backstop Capital is calculated as fifty percent (50%) multiplied by the fill factor, where the fill factor is one (1) minus the ratio of current Aggregate Backstop Capital to the Target Aggregate Backstop Capital. The remainder of Step 2 Capital becomes Step 3 Capital and is allocated as specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121).\n\nWhen Aggregate Backstop Capital is at or above the Turbo-Fill Floor and at or above the Target Aggregate Backstop Capital, none of Step 2 Capital is retained; all of Step 2 Capital becomes Step 3 Capital and is allocated as specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121).","contentHash":"84502f282b573c1b5573c1dc6eddb50afaa0c3a9e384fa5f496b2535d3881a82","addressRefs":[]},"5ce73730-4d5d-479c-b01e-40e87f072121":{"id":"5ce73730-4d5d-479c-b01e-40e87f072121","doc_no":"A.2.3.1.2.4","title":"Step 3: Smart Burn Engine","type":"Core","depth":5,"parentId":"7932c8f3-ce44-49ea-adc4-f6391c621c6e","order":1770,"content":"Step 3 Capital is allocated as follows:\n\n- Forty-five percent (45%) of Step 3 Capital is used by the Smart Burn Engine to buy back SKY, and the SKY tokens acquired through these buybacks are distributed to SKY stakers as SKY Staking Rewards as specified in [A.2.3.1.2.5 - Step 4: Staking Rewards](bb163691-630e-4fda-88f1-96381a649fa0).\n- Forty-five percent (45%) of Step 3 Capital is distributed to SKY stakers as USDS Staking Rewards as specified in [A.2.3.1.2.5 - Step 4: Staking Rewards](bb163691-630e-4fda-88f1-96381a649fa0).\n- Ten percent (10%) of Step 3 Capital is used by the Smart Burn Engine to buy back SKY, and the SKY tokens acquired through these buybacks are burned.\n\nThe specific parameters governing the execution of Smart Burn Engine buybacks are specified in [A.3.5.2 - Smart Burn Engine Parameters](ddb90fee-2851-4bf0-b924-f1d73e30ce7a).","contentHash":"c5f3832ebe2376de245dfe690a031609e2c043311605b83e1e21ecefefde789f","addressRefs":[]},"bb163691-630e-4fda-88f1-96381a649fa0":{"id":"bb163691-630e-4fda-88f1-96381a649fa0","doc_no":"A.2.3.1.2.5","title":"Step 4: Staking Rewards","type":"Core","depth":5,"parentId":"7932c8f3-ce44-49ea-adc4-f6391c621c6e","order":1771,"content":"Step 4 Capital is distributed to SKY stakers as Staking Rewards. Step 4 Capital comprises (1) USDS allocated from Step 3, distributed as USDS Staking Rewards, and (2) SKY tokens acquired by the Smart Burn Engine through buybacks specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121), distributed as SKY Staking Rewards.","contentHash":"107529805616d02cce18a08afdc1beedf982568dfcd0971cbad9a36e322ca682","addressRefs":[]},"ac7a6636-acbc-40c9-abc1-4543c0beb300":{"id":"ac7a6636-acbc-40c9-abc1-4543c0beb300","doc_no":"A.2.3.1.3","title":"Sourcing Of Internal Senior Risk Capital","type":"Core","depth":4,"parentId":"9bd2f02c-8111-4431-9b3a-46d3695af1e1","order":1772,"content":"Internal Senior Risk Capital (ISRC) consists of a portion of the excess capital of the Sky Protocol that is reinvested in providing Senior Risk Capital to Prime Agents. ISRC is sourced from Aggregate Backstop Capital (see [A.3.5.3.1.2 - Aggregate Backstop Capital](6dbead44-5ac4-4c5b-be3c-64eddd004e5c)) in two components: one hundred percent (100%) of any Aggregate Backstop Capital in excess of the Target Aggregate Backstop Capital (see [A.3.5.3.2.1 - Target Aggregate Backstop Capital](f73dda95-0b1c-4bdc-b957-469253d27281)), plus one third (1/3) of Aggregate Backstop Capital up to the Target Aggregate Backstop Capital.","contentHash":"588ec6899ce7c11209e4d6121eaf8b5e18befcc7150319d90e4bab74cd552f43","addressRefs":[]},"f67a5780-11d5-4014-8254-795080c77133":{"id":"f67a5780-11d5-4014-8254-795080c77133","doc_no":"A.2.3.1.4","title":"Implementation","type":"Core","depth":4,"parentId":"9bd2f02c-8111-4431-9b3a-46d3695af1e1","order":1773,"content":"The Sky Treasury Management Function is implemented through Executive Votes that update the corresponding on-chain parameters. Changes to the documents herein define the intended operation of the Sky Treasury Management Function; operational effect on the Sky Protocol requires a subsequent Executive Vote. Until such an Executive Vote is executed, prior on-chain parameters remain in force.\n\nPending activation of the USDS Staking Rewards specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121), the Smart Burn Engine continues to operate under existing on-chain parameters specified in [A.3.5.2 - Smart Burn Engine Parameters](ddb90fee-2851-4bf0-b924-f1d73e30ce7a), and SKY staking rewards continue to be funded from the Protocol Treasury via the Vesting Stream Contract specified in [A.4.4.1.4.2.1.3 - Vesting Stream Contract](21a8978d-10a5-4151-b99a-ca8115fe0a6d). The USDS Staking Rewards become operational when the SKY tokens funding the Vesting Stream Contract approach depletion. The Core Facilitator, in consultation with the Core Council Risk Advisor, determines when this activation occurs and effects the corresponding on-chain parameter changes through an Executive Vote.","contentHash":"d52fd62eb3e3d975b29b80bcc483704cf484f3448701246fc450f8534d1b29d4","addressRefs":[]},"de233df4-34cc-4e88-a065-9a9dde9add3c":{"id":"de233df4-34cc-4e88-a065-9a9dde9add3c","doc_no":"A.2.3.1.4.1","title":"Short Term SKY Staking Rewards Rate","type":"Core","depth":5,"parentId":"f67a5780-11d5-4014-8254-795080c77133","order":1774,"content":"Pending activation of the USDS Staking Rewards specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121), no Step 4 Capital is allocated to SKY Staking Rewards. Instead, SKY Staking Rewards are funded from SKY token reserves held by the Protocol Treasury via the Vesting Stream Contract specified in [A.4.4.1.4.2.1.3 - Vesting Stream Contract](21a8978d-10a5-4151-b99a-ca8115fe0a6d), distributed at a rate equivalent to fifty percent (50%) of Step 2 Capital from the prior Monthly Settlement Cycle. The rate is determined by the Core Facilitator in consultation with the Core Council Risk Advisor following each Monthly Settlement Cycle, using the prior Monthly Settlement Cycle's Step 2 Capital and the price of SKY, and is implemented through an Executive Vote.","contentHash":"2696d7c62e86710917c28e47fc32af99d27101c9333b43dde3041ec66668d7e3","addressRefs":[]},"6f8d5065-d6ff-4add-9a28-eadeffa7ed1a":{"id":"6f8d5065-d6ff-4add-9a28-eadeffa7ed1a","doc_no":"A.2.4","title":"Sky Core Monthly Settlement Cycle","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1775,"content":"This Article governs the Sky Core Monthly Settlement Cycle (MSC), a recurring process that synchronizes core financial operations, governance functions, and risk management activities across the ecosystem.","contentHash":"c01226b1ae57aea3a2f355817ce0fd6e7ff557252794acd80fdd16a4ab896f79","addressRefs":[]},"e0d89c66-5bab-402e-82a2-6270f1bcac07":{"id":"e0d89c66-5bab-402e-82a2-6270f1bcac07","doc_no":"A.2.4.1","title":"Monthly Settlement Cycle Overview","type":"Section","depth":3,"parentId":"6f8d5065-d6ff-4add-9a28-eadeffa7ed1a","order":1776,"content":"The documents herein define the Monthly Settlement Cycle (MSC), a standardized, system-wide process executed at the end of each calendar month.","contentHash":"befd0fe2ebc237519392e36c43ee00ff05581bb0874cea77206cc1099aa7d206","addressRefs":[]},"7f43aea7-9b81-48ef-b3ce-fdfae7e8a551":{"id":"7f43aea7-9b81-48ef-b3ce-fdfae7e8a551","doc_no":"A.2.4.1.1","title":"Operational Processes","type":"Core","depth":4,"parentId":"e0d89c66-5bab-402e-82a2-6270f1bcac07","order":1777,"content":"The Monthly Settlement Cycle (MSC) synchronizes several key operational processes across the ecosystem, including:\n\n1. Sky Protocol’s net revenue from the previous month is calculated and allocated through the steps of the Treasury Management Function. See [A.2.3 - Treasury Management](6c0af059-5d33-4e2b-90f1-1606957b8f85).\n2. The monthly Senior Risk Capital (SRC) origination process is settled: the clearing price is established, costs are deducted from winning Prime Agents’ accounts, and their accounts are credited with Originated SRC (OSRC) for the upcoming month. See [A.3.2.2.4.3.5 - Settlement Of Origination](fff0112a-58dd-4041-97f9-7baf113b4e70).\n3. Queued conversions between USDS and srUSDS within the SRC system are processed. See [A.3.2.2.4.2.2 - Deposit And Redemption Queues](38a99586-4a13-4ce3-8b2f-cee025e0c390).\n4. Pioneer Incentive Pools are funded with an amount equivalent to the Sky Savings Rate multiplied by the balance of Unrewarded USDS. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).\n5. Smart Burn Engine parameters are updated at each Monthly Settlement Cycle based on the prior month's state. See [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121) and [A.3.5.2 - Smart Burn Engine Parameters](ddb90fee-2851-4bf0-b924-f1d73e30ce7a).\n6. Critical Core GovOps functions related to the operationalization of Sky Primitives are executed, including payment/reimbursement processing, compliance monitoring, and the calculation and application of retroactive penalties.","contentHash":"e9a41e6870ab6d6da89a49f9c892a34e1b74e8a8579871a975552d516cde0486","addressRefs":[]},"75473c4b-69ba-4e6b-bbf6-2c926732364c":{"id":"75473c4b-69ba-4e6b-bbf6-2c926732364c","doc_no":"A.2.4.1.2","title":"Implementation","type":"Core","depth":4,"parentId":"e0d89c66-5bab-402e-82a2-6270f1bcac07","order":1778,"content":"The documents herein define the initial implementation of the Monthly Settlement Cycle. This initial implementation of the Monthly Settlement Cycle does not include the Senior Risk Capital System, which is still being developed.","contentHash":"0df2c4309600f8dbb4bac95be7adb329eb894d4bcb148a4cec68ad251e5c97bc","addressRefs":[]},"dd25aba4-7b77-469e-beb2-feaaedbbf143":{"id":"dd25aba4-7b77-469e-beb2-feaaedbbf143","doc_no":"A.2.4.1.2.1","title":"Process Definition","type":"Core","depth":5,"parentId":"75473c4b-69ba-4e6b-bbf6-2c926732364c","order":1779,"content":"The documents herein define the initial process for performing the Monthly Settlement Cycle. The calculations to be performed as part of the Monthly Settlement Cycle are defined in [A.2.4.1.2.2 - Implementation Stages](cf1d76c1-fc9f-499d-866f-265276e421f0). This process definition specifies who performs the calculations and how funds are ultimately paid out.","contentHash":"fb13f71c1afa16f7890d97cf44111d49e9c4c8f66e0ba119b1bd5692d57a9f14","addressRefs":[]},"5122086f-a067-4898-bcd2-bfba4ca3d795":{"id":"5122086f-a067-4898-bcd2-bfba4ca3d795","doc_no":"A.2.4.1.2.1.1","title":"Forum Post By Core GovOps","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1780,"content":"By the end of each month, Core GovOps creates a post on the Sky Forum to organize all communications regarding the Monthly Settlement Cycle for that month (the \"Monthly Settlement Cycle Post\"). The post must be made under the \"Sky Core\" category using the `monthly-settlement-cycle` tag.","contentHash":"f812134e33d519026a81e1e0078b86473f0fe6f87dc5a4d4e2e28fab29bcd541","addressRefs":[]},"e9f6226e-656c-4290-a329-d745f45323ba":{"id":"e9f6226e-656c-4290-a329-d745f45323ba","doc_no":"A.2.4.1.2.1.2","title":"Calculations By Operational Executor Agents And Core Council Risk Advisor","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1781,"content":"Within seven (7) calendar days of the end of each month, each Operational Executor Agent and the Core Council Risk Advisor replies to the Monthly Settlement Cycle Post with their calculation of the net amounts due to or from Prime Agents as specified in the documents herein.","contentHash":"6174e944196076674da962b768d71a05095c8bff6ebed82feb10946265134413","addressRefs":[]},"7f209f46-72c6-42f7-a7ad-898190ff4e6f":{"id":"7f209f46-72c6-42f7-a7ad-898190ff4e6f","doc_no":"A.2.4.1.2.1.2.1","title":"Initial Calculation By Operational Executor Agent","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1782,"content":"Within seven (7) calendar days of the end of each month, each Operational Executor Agent replies to the Monthly Settlement Cycle Post with a calculation of the net amounts due to or from the Prime Agents that it has an Executor Accord with (the \"Initial Calculation\"). The Initial Calculation must contain reasonable supporting detail. The required contents of the Initial Calculation will be further specified in a future iteration of the Atlas.","contentHash":"f648aaf7953b5c3a5c1e7ca547e2bd0867fa15e1b823e07c8fd076a25c52d74f","addressRefs":[]},"f62602a6-1c1a-44d4-9c9f-a903ce433330":{"id":"f62602a6-1c1a-44d4-9c9f-a903ce433330","doc_no":"A.2.4.1.2.1.2.1.1","title":"Demand Side Stablecoin Primitive Recipients","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1783,"content":"For each Prime Agent, the Initial Calculation must specify whether payments with respect to Demand Side Stablecoin Primitives (see [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d)) have already been made by the Operational Executor Agent, and thus should be reimbursed to the Operational Executor Agent instead of being paid to the Prime Agent.","contentHash":"a562e40a18fca12b706f0e7a5737623431921ad33461db1b9431306970a5afab","addressRefs":[]},"8be8ae66-2453-4d7d-8880-ffaba36bdb7e":{"id":"8be8ae66-2453-4d7d-8880-ffaba36bdb7e","doc_no":"A.2.4.1.2.1.2.2","title":"Independent Calculation By Core Council Risk Advisor On Behalf Of Core Council","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1784,"content":"Within seven (7) calendar days of the end of each month, the Core Council Risk Advisor replies to the Monthly Settlement Cycle Post with their own independent calculation of the net amounts due to or from each Prime Agent (the \"Independent Calculation\"). The Independent Calculation should also include calculation of the amounts to be transferred to the Core Council and Aligned Delegates Buffers (see [A.2.3.1.2.2 - Step 1: Security And Maintenance](324e9d22-70fe-4e44-82ab-118815f5c42e)). The Independent Calculation must contain reasonable supporting detail. The required contents of the Independent Calculation will be further specified in a future iteration of the Atlas.","contentHash":"3614dc6a01272ee1ea3ff0deaf3fd2df42d81e3a1a211ae4a063f17877c2e8c3","addressRefs":[]},"9de89bf3-9051-44f1-9ec0-d362ee4d4b38":{"id":"9de89bf3-9051-44f1-9ec0-d362ee4d4b38","doc_no":"A.2.4.1.2.1.3","title":"Final Calculation By Core GovOps","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1785,"content":"Within twelve (12) calendar days of the end of each month, Core GovOps replies to the Monthly Settlement Cycle Post with the final calculation of the net amounts due to or from each Prime Agent (the \"Final Calculation\"). The Final Calculation should also include the final amounts to be transferred to the Core Council and Aligned Delegates Buffers (see [A.2.3.1.2.2 - Step 1: Security And Maintenance](324e9d22-70fe-4e44-82ab-118815f5c42e)). If there are any Disputed Amounts (see [A.2.4.1.2.1.3.2 - Disputed Amount](4ddda7cd-9942-4f60-9555-6b3f16770334)), then Core GovOps must resolve them. Core GovOps must work with the relevant Operational Executor Agent, relevant Prime Agents, and the Core Council Risk Advisor to reach a mutually acceptable resolution and may consult other parties to the extent it deems advisable.\n\nCore GovOps makes the final decision in resolving differences between the Initial Calculation and the Independent Calculation. The Final Calculation must specify the Final Amount and contain reasonable supporting detail. The required contents of the Final Calculation will be further specified in a future iteration of the Atlas.","contentHash":"302bcbbab33665cc2a39b819dcdcf933fa22aa251f6bd0d2e305c8b9f01b416d","addressRefs":[]},"8669ef42-d55b-4be8-839e-646b4ff17e4c":{"id":"8669ef42-d55b-4be8-839e-646b4ff17e4c","doc_no":"A.2.4.1.2.1.3.1","title":"Agreed Amount","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1786,"content":"The net amount due to or from a Prime Agent in an Initial Calculation is an Agreed Amount if the percentage deviation between the Initial Calculation and the Independent Calculation is less than or equal to the Allowed Deviation (see [A.2.4.1.2.1.3.3 - Allowed Deviation](2e471685-fec5-4306-8747-a50dbbdd5c70)). The percentage deviation is calculated as the absolute value of the difference between the net amount in the Initial Calculation and the net amount in the Independent Calculation, divided by the average of the two amounts, multiplied by 100%. The net amount due to or from a Prime Agent in an Independent Calculation is also an Agreed Amount if there is no Initial Calculation.","contentHash":"fb57d968464822c23a613de5bedf3e9a6fd03ed9e4bfc451f91f31255a4afcde","addressRefs":[]},"4ddda7cd-9942-4f60-9555-6b3f16770334":{"id":"4ddda7cd-9942-4f60-9555-6b3f16770334","doc_no":"A.2.4.1.2.1.3.2","title":"Disputed Amount","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1787,"content":"The net amount due to or from a Prime Agent in an Initial Calculation is a Disputed Amount if it is not an Agreed Amount.","contentHash":"66b0ab4510ffcdfdc8859620471c1a5532be9a38d50e96db0cd3916a7a4240d4","addressRefs":[]},"2e471685-fec5-4306-8747-a50dbbdd5c70":{"id":"2e471685-fec5-4306-8747-a50dbbdd5c70","doc_no":"A.2.4.1.2.1.3.3","title":"Allowed Deviation","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1788,"content":"The Allowed Deviation is the maximum allowed deviation, on a percentage basis, between the net amount due to or from a Prime Agent in the Initial Calculation and Independent Calculation before resolution of these differences is required. It recognizes that if the Initial Calculation and Independent Calculation are truly developed independently then differences in methodology are likely to result in small deviations.","contentHash":"37d0464a620f61f0b87f070b950c4bb77ed127a1b83f51060a661ca54b8bcc00","addressRefs":[]},"0d2f4cb2-815a-4b0c-9bca-3a0d2635effc":{"id":"0d2f4cb2-815a-4b0c-9bca-3a0d2635effc","doc_no":"A.2.4.1.2.1.3.3.1","title":"Allowed Deviation Current Value","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1789,"content":"The current value of the Allowed Deviation is 1%.","contentHash":"ce2bb6970f494d6713afa9a0a86cc63f5f41282a164c05e8f5bd4bb61e3e5b2c","addressRefs":[]},"c20c38fe-c952-4e75-86fe-d6b561f7f436":{"id":"c20c38fe-c952-4e75-86fe-d6b561f7f436","doc_no":"A.2.4.1.2.1.3.4","title":"Final Amount","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1790,"content":"The net amount due to or from a Prime Agent in a Final Calculation is a Final Amount.","contentHash":"7d47e14e2d6f112a6892e739acd4259163b92904de61073f2a669772e7d30fb8","addressRefs":[]},"c204b363-7cc0-4e40-a7dc-68de57358cf9":{"id":"c204b363-7cc0-4e40-a7dc-68de57358cf9","doc_no":"A.2.4.1.2.1.3.5","title":"Disputes By Prime Agents","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1791,"content":"A Prime Agent may dispute the calculation of the net amount due to or from it (a \"Dispute Notice\"). The Dispute Notice must be posted as a reply to the Monthly Settlement Cycle Post within five (5) calendar days of the posting of the Initial Calculation or Independent Calculation being disputed. The Dispute Notice must specify the errors in the Initial Calculation or Independent Calculation and the Prime’s own calculation of the net amount due to or from it. The required contents of the Dispute Notice will be further specified in a future iteration of the Atlas.\n\nCore GovOps may at its discretion resolve the differences between the calculations using the process specified in [A.2.4.1.2.1.3 - Final Calculation By Core GovOps](9de89bf3-9051-44f1-9ec0-d362ee4d4b38). Alternatively, Core GovOps may elect to determine the correct amount and true up any differences in the next Monthly Settlement Cycle as specified in [A.2.4.1.2.1.5 - True Up In Subsequent Monthly Settlement Cycle](de1592f5-dbce-46de-913f-6ec9589d36e8). In either case Core GovOps must post its decision as a reply to the Dispute Notice.","contentHash":"db4664d2530c6798ff2af7ff04d6064eedd4ce9bd272f53fe487a148490ec5b0","addressRefs":[]},"0d561ea6-8689-459c-85eb-7c861553e116":{"id":"0d561ea6-8689-459c-85eb-7c861553e116","doc_no":"A.2.4.1.2.1.4","title":"Settlement Through Sky Core Executive Vote","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1792,"content":"When Core GovOps has posted the Final Calculation then the Core Facilitator must include payments of these amounts in the next Sky Core Executive Vote as specified herein.","contentHash":"51818fb31f85c5f5c8972529e60fa4d04d6817e0f4950de9b20138748a6d6e7a","addressRefs":[]},"1816e5eb-3cf1-427f-b831-8eeb9408887c":{"id":"1816e5eb-3cf1-427f-b831-8eeb9408887c","doc_no":"A.2.4.1.2.1.4.1","title":"Payment Of Amounts Due To Prime Agents","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1793,"content":"Amounts due to Prime Agents, excluding reimbursements made to Operational Executor Agents (see [A.2.4.1.2.1.4.3 - Reimbursement Of Payments Made By Operational Executor Agents](07c5cfd2-d68a-40d6-873d-b82cea9a92be)), are transferred from the Sky Surplus Buffer to the Prime SubProxy Account through an Executive Vote.","contentHash":"5177bb2320ef1aa70fcf12af37128492c2ceab0c05f11eaca4d92b92bac0ad04","addressRefs":[]},"6e3d5198-fdb5-47dd-b632-4c71a313a1a6":{"id":"6e3d5198-fdb5-47dd-b632-4c71a313a1a6","doc_no":"A.2.4.1.2.1.4.2","title":"Collection Of Amounts Due From Prime Agents","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1794,"content":"Amounts due from Prime Agents, excluding reimbursements made to Operational Executor Agents (see [A.2.4.1.2.1.4.3 - Reimbursement Of Payments Made By Operational Executor Agents](07c5cfd2-d68a-40d6-873d-b82cea9a92be)) are settled in a way that is equivalent to a transfer from the Prime to the Sky Surplus Buffer through actions included in an Executive Vote.","contentHash":"a5f630f59bffabe67b182f689e4b1e7cad0011f15a1ea9bef42ecd1b7af1078c","addressRefs":[]},"07c5cfd2-d68a-40d6-873d-b82cea9a92be":{"id":"07c5cfd2-d68a-40d6-873d-b82cea9a92be","doc_no":"A.2.4.1.2.1.4.3","title":"Reimbursement Of Payments Made By Operational Executor Agents","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1795,"content":"Reimbursements of payments already made by the Operational Executor Agent with respect to Demand Side Stablecoin Primitives (see [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d)) are transferred to the Operational Executor Agent’s Buffer through an Executive Vote.","contentHash":"d6549fa8743449881c90729ec55f874883c4e934253b740e211acd0b09b8b17c","addressRefs":[]},"de1592f5-dbce-46de-913f-6ec9589d36e8":{"id":"de1592f5-dbce-46de-913f-6ec9589d36e8","doc_no":"A.2.4.1.2.1.5","title":"True Up In Subsequent Monthly Settlement Cycle","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1796,"content":"If the amounts of any payments included in the Sky Core Executive Vote (see [A.2.4.1.2.1.4 - Settlement Through Sky Core Executive Vote](0d561ea6-8689-459c-85eb-7c861553e116)) are subsequently determined to be incorrect, adjustments are included in the next Monthly Settlement Cycle to ensure that each party pays the amount it owes or receives the amount to which it is entitled.\n\nCore GovOps must prepare a statement specifying the errors, the correct amounts, and the adjustments needed (the \"Correction Calculation\"). The Correction Calculation must be posted to the Sky Forum under the \"Sky Core\" category with the `monthly-settlement-cycle` tag. The required contents of the Correction Calculation will be further specified in a future iteration of the Atlas.","contentHash":"1f2d08e488e487a25e2660c20ec21c0a9bf05a7d7fd3ebc87b6679fa1f3583ab","addressRefs":[]},"f2401c5e-0fea-4a50-ab0b-3e03fc413dbb":{"id":"f2401c5e-0fea-4a50-ab0b-3e03fc413dbb","doc_no":"A.2.4.1.2.1.6","title":"Interim Measures","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1797,"content":"The documents herein define interim exceptions to the process definition for the Monthly Settlement Cycle.","contentHash":"605ed62e10aed35cffeedcf8e6ded5574381fc4fd5d29160a02839830685d75f","addressRefs":[]},"bfc3548d-5ad1-4327-a54a-ddd4549c5fdc":{"id":"bfc3548d-5ad1-4327-a54a-ddd4549c5fdc","doc_no":"A.2.4.1.2.1.6.1","title":"Scope Of July / August 2025 Monthly Settlement Cycle","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1798,"content":"The initial Monthly Settlement Cycle conducted in September 2025 will be for the two month period from July 1, 2025 to August 31, 2025.","contentHash":"22a009770b77efb6a3bf847c575afa46c168f6efbd3f23551d76faab8be497cd","addressRefs":[]},"146d3d9c-7f8a-4dc4-b6b3-349bab4279bb":{"id":"146d3d9c-7f8a-4dc4-b6b3-349bab4279bb","doc_no":"A.2.4.1.2.1.6.2","title":"Process For July / August 2025 Monthly Settlement Cycle","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1799,"content":"For the initial Monthly Settlement Cycle conducted in September 2025, the Initial Calculation prepared by Operational Executor Agent Amatsu will only include calculations related to Demand Side Stablecoin Primitives (see [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d)). The Independent Calculation prepared by the Core Council Risk Advisor on behalf of the Core Council will be prepared normally. The calculations related to Demand Side Stablecoin Primitives will be subject to the normal resolution process defined in [A.2.4.1.2.1.3 - Final Calculation By Core GovOps](9de89bf3-9051-44f1-9ec0-d362ee4d4b38). For all other calculations, the amounts in the Independent Calculation will be treated as Agreed Amounts. The Initial Calculation and the Independent Calculation will be posted to the Sky Forum by September 10, 2025.","contentHash":"f4b72c27a5c7fdcf5afe77d8f64e318e0358a2db7003ca8ac6b811ea966cfeab","addressRefs":[]},"8e8ff62f-c6c5-4094-afd1-2cedcf482df6":{"id":"8e8ff62f-c6c5-4094-afd1-2cedcf482df6","doc_no":"A.2.4.1.2.1.6.3","title":"Process For September 2025 Monthly Settlement Cycle","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1800,"content":"For the Monthly Settlement Cycle conducted in October 2025, the Initial Calculation prepared by Operational Executor Agent Amatsu will only include calculations related to Spark. The Independent Calculation prepared by the Core Council Risk Advisor on behalf of the Core Council will be prepared normally. The calculations related to Spark will be subject to the normal resolution process defined in [A.2.4.1.2.1.3 - Final Calculation By Core GovOps](9de89bf3-9051-44f1-9ec0-d362ee4d4b38). For all other calculations, the amounts in the Independent Calculation will be treated as Agreed Amounts.","contentHash":"8707ee572ff286b43f348d789703b3e440c76b17cbc69be191f4f7fa9e880556","addressRefs":[]},"5aa66a15-d59c-4f66-9d80-96583698f24d":{"id":"5aa66a15-d59c-4f66-9d80-96583698f24d","doc_no":"A.2.4.1.2.1.6.4","title":"Process For November / December 2025 Monthly Settlement Cycle","type":"Core","depth":6,"parentId":"dd25aba4-7b77-469e-beb2-feaaedbbf143","order":1801,"content":"There will be no Monthly Settlement Cycle conducted in December 2025. Instead, the Monthly Settlement Cycle conducted in January 2026 will be for the two-month period from November 1, 2025 to December 31, 2025.\n\nFor the Monthly Settlement Cycle conducted in January 2026, the Independent Calculation prepared by the Core Council Risk Advisor on behalf of the Core Council will only include calculations related to Spark. The Initial Calculation prepared by Operational Executor Agent Amatsu will be prepared normally. The calculations related to Spark will be subject to the normal resolution process defined in [A.2.4.1.2.1.3 - Final Calculation By Core GovOps](9de89bf3-9051-44f1-9ec0-d362ee4d4b38). For all other calculations, the amounts in the Initial Calculation will be treated as Agreed Amounts.","contentHash":"eae1277f5338f5535cca2afebe74489965a9b6948f6edf4ab31c35a3487f12d7","addressRefs":[]},"cf1d76c1-fc9f-499d-866f-265276e421f0":{"id":"cf1d76c1-fc9f-499d-866f-265276e421f0","doc_no":"A.2.4.1.2.2","title":"Implementation Stages","type":"Core","depth":5,"parentId":"75473c4b-69ba-4e6b-bbf6-2c926732364c","order":1802,"content":"The initial implementation of the Monthly Settlement Cycle will occur in three stages as specified in the documents herein.","contentHash":"f43a25a6df726e73e6a1512dc73d83d35fb0b1ca99f8374bdc3bdbfdcc687cf0","addressRefs":[]},"efb30fa0-99b1-43bd-bdfd-219cf897c44f":{"id":"efb30fa0-99b1-43bd-bdfd-219cf897c44f","doc_no":"A.2.4.1.2.2.1","title":"Stage 1","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1803,"content":"The documents herein define Stage 1 of the implementation of the Monthly Settlement Cycle.","contentHash":"f9f3c84c1b6134ea1fc36a581f373fb443ce3104569abd91d213cb954646d25e","addressRefs":[]},"65bd404f-0fd4-4ae9-9860-2c6e37731fef":{"id":"65bd404f-0fd4-4ae9-9860-2c6e37731fef","doc_no":"A.2.4.1.2.2.1.1","title":"Stage 1 Simplified Profit And Loss Calculation","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1804,"content":"In Stage 1 of the implementation of the Monthly Settlement Cycle, the net amount due from each Prime to Sky will be calculated using a Simplified Profit And Loss Calculation as specified in the documents herein.","contentHash":"2f605cc52917c62695e6b814ae1a10dfafb4231123175173e3d91a641b089c4a","addressRefs":[]},"33d1b516-d347-4d44-9af6-95f25e8a8d8c":{"id":"33d1b516-d347-4d44-9af6-95f25e8a8d8c","doc_no":"A.2.4.1.2.2.1.1.1","title":"Amount Due From Sky To Primes With Respect To Demand Side Primitives And Agent Rate","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1805,"content":"The amount due from Sky to each Prime with respect to Demand Side Primitives and the Agent Rate is calculated as specified in the documents herein.","contentHash":"13142cfe3b48dad2ecf06ceb0313cba29f040fa381af03429629101290e6e274","addressRefs":[]},"0b2165cb-c10d-474b-ad55-544821ac29c3":{"id":"0b2165cb-c10d-474b-ad55-544821ac29c3","doc_no":"A.2.4.1.2.2.1.1.1.1","title":"Amount Due From Sky To Primes With Respect To Distribution Reward","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1806,"content":"The amount due from Sky to a Prime in a month with respect to the Distribution Reward is the amount earned by the Prime with respect to all USDS and sUSDS balances marked with the Prime’s reward codes. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6). This includes any Bonus Distribution Reward. See [A.2.8.2.2.2.3.2 - 2025 Bonus](7ca440d3-03fb-4fba-81a8-d2118dc47aa6).","contentHash":"11bca8b606ec4b2f49615964f1a31c4171267ad8fb5fe1641ec2cacb3f7cfc4e","addressRefs":[]},"aeb1d633-d6e2-46ef-9f55-bcb0a16a2e63":{"id":"aeb1d633-d6e2-46ef-9f55-bcb0a16a2e63","doc_no":"A.2.4.1.2.2.1.1.1.2","title":"Amount Due From Sky To Primes With Respect To Agent Rate","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1807,"content":"The amount due from Sky to a Prime in a month with respect to the Agent Rate is calculated as specified in [A.3.1.2.3 - Agent Rate](012c953b-c522-4ea3-939b-3282af4e1d7e).","contentHash":"74b2b3112805e7a33d45f2311049a45946e7e3874af60e72b12e66f17a5b8f78","addressRefs":[]},"cef16014-05db-4b21-a5a2-20e62aaca027":{"id":"cef16014-05db-4b21-a5a2-20e62aaca027","doc_no":"A.2.4.1.2.2.1.1.1.3","title":"Amount Due From Sky To Primes With Respect To Distribution Reward And Agent Rate","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1808,"content":"The amount due from Sky to a Prime in a month with respect to the Distribution Reward and the Agent Rate is the sum of the amounts specified in [A.2.4.1.2.2.1.1.1.1 - Amount Due From Sky To Primes With Respect To Distribution Reward](0b2165cb-c10d-474b-ad55-544821ac29c3) and [A.2.4.1.2.2.1.1.1.2 - Amount Due From Sky To Primes With Respect To Agent Rate](aeb1d633-d6e2-46ef-9f55-bcb0a16a2e63).","contentHash":"4c5ea87bb56278aa964f000e8aed6b9f5db6b66e31fa12844766056c020f3139","addressRefs":[]},"e98ddd17-a8c3-4523-8464-cc41247c66e8":{"id":"e98ddd17-a8c3-4523-8464-cc41247c66e8","doc_no":"A.2.4.1.2.2.1.1.2","title":"Amount Due From Prime To Sky With Respect To Supply Side Primitives","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1809,"content":"The amount due from each Prime to Sky with respect to Supply Side Primitives is calculated as specified in the documents herein.","contentHash":"1b35e227072452651adf97f3430f92c18f40f6e3c5f8ab4433b3bad73b65cf0e","addressRefs":[]},"fd3ea856-dbef-4fe0-a662-82a58d33d9c0":{"id":"fd3ea856-dbef-4fe0-a662-82a58d33d9c0","doc_no":"A.2.4.1.2.2.1.1.2.1","title":"Step 1: Calculate Total Allocation System Revenue","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1810,"content":"First, Total Allocation System Revenue is calculated for each Prime for the month. Total Allocation System Revenue for a Prime in a month is the sum of Instance Revenue for each Active Instance of the Allocation System Primitive that the Prime has deployed.","contentHash":"16c3c1af6669d31d3ae8c2821f383c784d80741cda0dd41d5d89fcd18d3ef34d","addressRefs":[]},"90acccd5-d7b4-4c03-9ce2-471dc3e82c98":{"id":"90acccd5-d7b4-4c03-9ce2-471dc3e82c98","doc_no":"A.2.4.1.2.2.1.1.2.1.1","title":"Instance Revenue","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1811,"content":"Instance Revenue for an Allocation System Instance for a month is all earnings from that Instance.","contentHash":"c1e75b15ef06515d1fe36b0bd1e395cc518dab23542b48b96ab64337f0c62863","addressRefs":[]},"1eaa2350-e354-4000-baa6-be250853bddc":{"id":"1eaa2350-e354-4000-baa6-be250853bddc","doc_no":"A.2.4.1.2.2.1.1.2.2","title":"Step 2: Calculate Total Allocation System Profit","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1812,"content":"Second, Total Allocation System Profit is calculated for each Prime for the month. Total Allocation System Profit for a Prime in a month is the sum of Instance Profit for each Active Instance of the Allocation System Primitive that the Prime has deployed.","contentHash":"67323771342076469be6d1497b0e58920a60211792e71bd8f8596710b49296ad","addressRefs":[]},"9974c452-216b-45c0-8a1d-621816b8da2a":{"id":"9974c452-216b-45c0-8a1d-621816b8da2a","doc_no":"A.2.4.1.2.2.1.1.2.2.1","title":"Instance Profit","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1813,"content":"Instance Profit for an Allocation System Instance is equal to the greater of (1) Instance Revenue (see [A.2.4.1.2.2.1.1.2.1.1 - Instance Revenue](90acccd5-d7b4-4c03-9ce2-471dc3e82c98)) minus Instance Expenses (see [A.2.4.1.2.2.1.1.2.2.1.1 - Instance Expense](6cbe7181-419f-4a7b-a659-85972d5100a3)) and (2) zero.","contentHash":"059b2c0ff58c087c208af17eb99124e25f4e9fb85242b1701f33a03dccb3eb20","addressRefs":[]},"6cbe7181-419f-4a7b-a659-85972d5100a3":{"id":"6cbe7181-419f-4a7b-a659-85972d5100a3","doc_no":"A.2.4.1.2.2.1.1.2.2.1.1","title":"Instance Expense","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1814,"content":"Instance Expense for an Allocation System Instance for a month is the interest expense on the funds from Sky’s Collateral Portfolio invested in the Instance. It is calculated on a per block basis based on the amount invested from Sky’s Collateral Portfolio and the Agent Credit Line Borrow Rate.","contentHash":"a67cd7954e8ec75c3b9335fdcf1bcedaad5dece19fb8fbb3d4795556308c2938","addressRefs":[]},"a9427e1a-77ae-473b-aafd-b4216fcd615c":{"id":"a9427e1a-77ae-473b-aafd-b4216fcd615c","doc_no":"A.2.4.1.2.2.1.1.2.3","title":"Step 3: Calculate Adjusted Allocation System Profit","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1815,"content":"Third, Adjusted Allocation System Profit is calculated for each Prime for the month. Adjusted Allocation System Profit for a Prime in a month is Total Allocation System Profit minus the Distortion Penalty (see [A.2.4.1.2.2.1.1.2.3.1 - Distortion Penalty](2a021208-c964-440f-b491-3c9e034f2d22)) and the Low Yield Actively Stabilizing Collateral Penalty (see [A.2.4.1.2.2.1.1.2.3.2 - Low Yield Actively Stabilizing Collateral Penalty](631e7c75-375f-4298-9d85-b17cb2eb019f)).","contentHash":"5788b3afced9abd1d2e1477f52c2b70961a2441f8cb28806a3e13b4df40942a1","addressRefs":[]},"2a021208-c964-440f-b491-3c9e034f2d22":{"id":"2a021208-c964-440f-b491-3c9e034f2d22","doc_no":"A.2.4.1.2.2.1.1.2.3.1","title":"Distortion Penalty","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1816,"content":"The Distortion Penalty is a discretionary penalty designed to mitigate the potential misalignment caused by the asymmetric nature of the Simplified Profit And Loss Calculation, where Primes earn profits on Allocation System Instances that earn more than the Agent Credit Line Borrow Rate but do not suffer losses when Instances earn less than the Agent Credit Line Borrow Rate.\n\nThe Core Executor Agents, in consultation with the Core Council Risk Advisor, may assess a penalty of up to 100% of Total Allocation System Profit (see [A.2.4.1.2.2.1.1.2.2 - Step 2: Calculate Total Allocation System Profit](1eaa2350-e354-4000-baa6-be250853bddc)) if it determines that a Prime’s decisions were distorted by this incentive structure.","contentHash":"82fa68edaee7fd54ae64a059c5c727e67104b0ebcd2a6edfd836dc20c161f5b1","addressRefs":[]},"631e7c75-375f-4298-9d85-b17cb2eb019f":{"id":"631e7c75-375f-4298-9d85-b17cb2eb019f","doc_no":"A.2.4.1.2.2.1.1.2.3.2","title":"Low Yield Actively Stabilizing Collateral Penalty","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1817,"content":"The Low Yield Actively Stabilizing Collateral Penalty is a formulaic penalty designed to prevent Primes from holding excessive amounts of low yield Actively Stabilizing Collateral.\n\nThe penalty, as a percentage of the Total Allocation System Profit, is the lesser of (1) ten times the Excess Low Yield Actively Stabilizing Collateral Percentage and (2) 100%.","contentHash":"d45c1edbf3aae3182606d97a9161f0ddbcd86059e37765223d291304b5b6a4c5","addressRefs":[]},"5e78fb21-1208-442f-b215-3babcd69fd69":{"id":"5e78fb21-1208-442f-b215-3babcd69fd69","doc_no":"A.2.4.1.2.2.1.1.2.3.2.1","title":"Excess Low Yield Actively Stabilizing Collateral Percentage","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1818,"content":"The Excess Low Yield Actively Stabilizing Collateral Percentage for a Prime is equal to the excess of (1) its Low Yield Actively Stabilizing Collateral (see [A.2.4.1.2.2.1.1.2.3.2 - Low Yield Actively Stabilizing Collateral Penalty](631e7c75-375f-4298-9d85-b17cb2eb019f)) as a percentage of its Collateral Portfolio above (2) its Minimum Actively Stabilizing Collateral (see [A.3.3.2.2 - Minimum Actively Stabilizing Collateral](475fe222-9e4a-4e9d-9be6-a7a424ce02f8)) as a percentage of its Collateral Portfolio.","contentHash":"b37e82e81f8be09108a27ecdca92f7b8b1d7266cbcdd9ee65d4672c45950eb36","addressRefs":[]},"858b2ee0-89b8-4505-8324-f3cd315de40c":{"id":"858b2ee0-89b8-4505-8324-f3cd315de40c","doc_no":"A.2.4.1.2.2.1.1.2.3.2.1.1","title":"Low Yield Actively Stabilizing Collateral","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1819,"content":"Low Yield Actively Stabilizing Collateral is Actively Stabilizing Collateral (see [A.3.3.2.2.1.1 - Resting Actively Stabilizing Collateral](0e17b35a-c830-4695-b63c-5ef58b249d3f)) that earns less than the Agent Credit Line Borrow Rate.","contentHash":"9addce0d080ac881d093b599b132e32f7c81a208e6645c693133d282a6ee2b5d","addressRefs":[]},"2617edae-6c22-4d7c-8e14-353bfced35f2":{"id":"2617edae-6c22-4d7c-8e14-353bfced35f2","doc_no":"A.2.4.1.2.2.1.1.2.4","title":"Step 4: Calculate Amount Due To Sky With Respect To Supply Side Primitives","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1820,"content":"Fourth, the amount due to Sky with respect to Supply Side Primitives is calculated for each Prime for the month. The amount due to Sky with respect to Supply Side Primitives is Total Allocation System Revenue (see [A.2.4.1.2.2.1.1.2.1 - Step 1: Calculate Total Allocation System Revenue](fd3ea856-dbef-4fe0-a662-82a58d33d9c0)) minus Adjusted Allocation System Profit (see [A.2.4.1.2.2.1.1.2.3 - Step 3: Calculate Adjusted Allocation System Profit](a9427e1a-77ae-473b-aafd-b4216fcd615c)).","contentHash":"c71c54aa83e1c6e2793f740805ab137ec496b4b51d8f195daf5f4f707a86d0ce","addressRefs":[]},"6dcd7515-3398-443a-9377-99e0c3cd0174":{"id":"6dcd7515-3398-443a-9377-99e0c3cd0174","doc_no":"A.2.4.1.2.2.1.1.3","title":"Settlement","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1821,"content":"The amounts due from Sky to each Prime with respect to Demand Side Primitives and the Agent Rate (see [A.2.4.1.2.2.1.1.1 - Amount Due From Sky To Primes With Respect To Demand Side Primitives And Agent Rate](33d1b516-d347-4d44-9af6-95f25e8a8d8c)) and the amounts due from each Prime to Sky with respect to Supply Side Primitives (see [A.2.4.1.2.2.1.1.2 - Amount Due From Prime To Sky With Respect To Supply Side Primitives](e98ddd17-a8c3-4523-8464-cc41247c66e8)) are settled as specified in [A.2.4.1.2.1.4 - Settlement Through Sky Core Executive Vote](0d561ea6-8689-459c-85eb-7c861553e116).","contentHash":"c124dd1152eae88559edc1fd1864cca41ae936fd1eaa5efb8c9bda82ae911eff","addressRefs":[]},"db06608a-303d-4b35-864a-f7aad38fcb06":{"id":"db06608a-303d-4b35-864a-f7aad38fcb06","doc_no":"A.2.4.1.2.2.1.1.4","title":"Exceptions","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1822,"content":"The documents herein define exceptions to the Simplified Profit And Loss Calculation for specific assets held by certain Prime Agents.","contentHash":"339652bf6c382ab7486532cd39a1e400c79bc89a8f3cff15e8a19e46c5888923","addressRefs":[]},"34893b77-2cce-4753-9ce4-2b8ab1f951bb":{"id":"34893b77-2cce-4753-9ce4-2b8ab1f951bb","doc_no":"A.2.4.1.2.2.1.1.4.1","title":"USDT Held By Spark","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1823,"content":"Spark pays the Agent Credit Line Borrow Rate with respect to funds borrowed by Spark to invest in USDT and held in SparkLend. Spark thus realizes the full profit and loss associated with these investments.","contentHash":"0276549348b756de8734fc7aa00c0720f5ebefa54cbdcf12d6d264c501dadb8e","addressRefs":[]},"8619f00f-84e2-4951-86c4-08876d8a6f6a":{"id":"8619f00f-84e2-4951-86c4-08876d8a6f6a","doc_no":"A.2.4.1.2.2.1.1.4.2","title":"pyUSD Held By Spark","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1824,"content":"Spark pays the Agent Credit Line Borrow Rate with respect to funds borrowed by Spark to invest in pyUSD and held in SparkLend or Spark’s ALM Proxy. Spark thus realizes the full profit and loss associated with these investments.","contentHash":"8854b5acfcdf93d003107e8af8e6021c54aeab59ee99bbf90ba711a00603e0af","addressRefs":[]},"ff3aa296-34eb-4783-904f-4510fa0c6c37":{"id":"ff3aa296-34eb-4783-904f-4510fa0c6c37","doc_no":"A.2.4.1.2.2.1.2","title":"Stage 1 Timing","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1825,"content":"Stage 1 is currently expected to be implemented in the August 21, 2025 Executive Vote for the period from July 1, 2025 to July 31, 2025.","contentHash":"d78f9f27e6d62f715d36b96ccdf8d9b9cd2f9af56846b4f8f8cfd0fd7790935b","addressRefs":[]},"f87c520a-3324-46a7-ac4e-9c7de2a2af0a":{"id":"f87c520a-3324-46a7-ac4e-9c7de2a2af0a","doc_no":"A.2.4.1.2.2.1.3","title":"Stage 1 Actions","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1826,"content":"The actions specified herein must be completed to achieve Stage 1 implementation of the Monthly Settlement Cycle.","contentHash":"2f1a729ccc68850a9a55ba2a1a7bb1d5595dcdb719bfb8758502e0bdd0249f15","addressRefs":[]},"48ec2b03-0885-45d9-b5f6-22267414f587":{"id":"48ec2b03-0885-45d9-b5f6-22267414f587","doc_no":"A.2.4.1.2.2.1.3.1","title":"Reduction Of Prime Allocator Vault Stability Fees","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1827,"content":"The Stability Fees for each Prime Allocator Vault must be reduced to zero so that value is transferred from Primes to Sky Core exclusively through Executive Votes. The Core Executor Agents, in consultation with the Core Council Risk Advisor, is directed to use the Stability Parameter Bounded External Access Module to reduce the Stability Fee for each Prime Allocator Vault to zero. See [A.3.7.1.3.3 - Allocator Vault Parameters](6ab6bd12-93d3-419f-96e2-a7f79bfe1afa).","contentHash":"cd24b45816343f11434bd2bc1c1be31ca06f2db121407b9007c209377b1af786","addressRefs":[]},"1782eeb8-8c6f-4b34-beea-7ab140057324":{"id":"1782eeb8-8c6f-4b34-beea-7ab140057324","doc_no":"A.2.4.1.2.2.1.3.2","title":"Automation Of Simplified Profit And Loss Calculation","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1828,"content":"The Core Council Risk Advisor must develop tooling to allow the net amount due from each Prime to Sky each month under the Simplified Profit And Loss Calculation to be computed automatically.","contentHash":"5357148fa79478eceedff3b0c46b9f2776c70c9941c5c397c98b7058a6b110e6","addressRefs":[]},"74bdfafe-e3c7-4670-a8bd-c337f1ad1e49":{"id":"74bdfafe-e3c7-4670-a8bd-c337f1ad1e49","doc_no":"A.2.4.1.2.2.2","title":"Stage 2","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1829,"content":"The documents herein define Stage 2 of the implementation of the Monthly Settlement Cycle.","contentHash":"db3d6f7cc5d7c289afe9985580e40230c0dc1690bbd2186a5ce428327db57435","addressRefs":[]},"c1fc89f4-b30f-4da1-93c6-822839fed783":{"id":"c1fc89f4-b30f-4da1-93c6-822839fed783","doc_no":"A.2.4.1.2.2.2.1","title":"Stage 2 Virtual Base Rate","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1830,"content":"In Stage 2 of the implementation of the Monthly Settlement Cycle, the net amount due from each Prime to Sky is calculated as specified in the Atlas without the use of the Simplified Profit And Loss Calculation. However, interest under the Base Rate does not accrue in real time onchain and is instead calculated offchain and paid through Executive Votes as part of the Monthly Settlement Cycle. This is known as the Virtual Base Rate as these calculations occur offchain.","contentHash":"d57b0edb755257b6aad72f7e3229649941f26eda2c7e5166e08ab8404b6f8275","addressRefs":[]},"ceb3c433-d73f-4c58-bac9-e79b44e66fcf":{"id":"ceb3c433-d73f-4c58-bac9-e79b44e66fcf","doc_no":"A.2.4.1.2.2.2.2","title":"Stage 2 Timing","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1831,"content":"Stage 2 will be implemented in the December 2025 Monthly Settlement Cycle for the period from November 1, 2025 to November 30, 2025. If there is no December 2025 Monthly Settlement Cycle, then Stage 2 will be implemented in the January 2026 Monthly Settlement Cycle for the period from November 1, 2025 to December 31, 2025.","contentHash":"6ba91f69672270422ce764ca213fe6218ad844d83c013dd77674b1a879a0018b","addressRefs":[]},"b8c86fb3-2ba4-4c53-a509-81d022dffd20":{"id":"b8c86fb3-2ba4-4c53-a509-81d022dffd20","doc_no":"A.2.4.1.2.2.2.3","title":"Stage 2 Actions","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1832,"content":"The actions specified herein must be completed to achieve Stage 2 implementation of the Monthly Settlement Cycle.","contentHash":"477c7059ebd16054d0e5a0d98d602b191bf57c8039fc51d1781d265921609b7b","addressRefs":[]},"d98d3753-4230-4ad8-a1e7-7b1fd7e3b679":{"id":"d98d3753-4230-4ad8-a1e7-7b1fd7e3b679","doc_no":"A.2.4.1.2.2.2.3.1","title":"Automation Of Monthly Settlement Cycle Calculation Including Virtual Base Rate","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1833,"content":"The Core Council Risk Advisor must develop automated tooling for calculating the net amount due from each Prime to Sky each month, incorporating the Virtual Base Rate.","contentHash":"f340775b01f3e59595120f569d0a240ebb5572788e5bfa8f3f0f6200a542497b","addressRefs":[]},"1f9811fa-a759-4cd9-b7e1-aa0cc51174ed":{"id":"1f9811fa-a759-4cd9-b7e1-aa0cc51174ed","doc_no":"A.2.4.1.2.2.3","title":"Stage 3","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1834,"content":"The documents herein define Stage 3 of the implementation of the Monthly Settlement Cycle.","contentHash":"8e54577b858ef94ab050b6f5162e85f120e2faf23a54bc1a36a65863c1037e02","addressRefs":[]},"eebbcd6d-2cbe-47cb-89c5-f119cf4eda08":{"id":"eebbcd6d-2cbe-47cb-89c5-f119cf4eda08","doc_no":"A.2.4.1.2.2.3.1","title":"Stage 3 Onchain Base Rate","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1835,"content":"In Stage 3 of the implementation of the Monthly Settlement Cycle, the net amount due from each Prime to Sky is calculated as specified in the Atlas without the use of the Simplified Profit And Loss Calculation. In Stage 3, interest from the Base Rate accrues onchain to the Allocator Vault of each Prime. Thus, in Stage 3 Executive Votes are only required to pay down accrued interest on Allocator Vaults, as necessary, and settle other amounts due to and from Primes.","contentHash":"ffee58f7d38a1f17d8816f5bbc1da4393f7ae7f8431e0e2df18d3834f3ee34a7","addressRefs":[]},"cf7ed710-0302-4169-af70-34194269e184":{"id":"cf7ed710-0302-4169-af70-34194269e184","doc_no":"A.2.4.1.2.2.3.2","title":"Stage 3 Timing","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1836,"content":"The timing for Stage 3 implementation of the Monthly Settlement Cycle will be specified in a future iteration of the Atlas.","contentHash":"123b2a3d9080e7ff69cd95864ae84ad65d8022334a291ed28aa961419a577edc","addressRefs":[]},"42dc70f1-1353-40f8-90c3-cbbac317b26f":{"id":"42dc70f1-1353-40f8-90c3-cbbac317b26f","doc_no":"A.2.4.1.2.2.3.3","title":"Stage 3 Actions","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1837,"content":"The actions specified herein must be completed to achieve Stage 3 implementation of the Monthly Settlement Cycle.","contentHash":"5a65d34ac979731dbb558b76b60798a0ba74630054c4d2d02450cef4e72a8ee8","addressRefs":[]},"2eb1b10f-e959-42ad-87db-2556e7fc7581":{"id":"2eb1b10f-e959-42ad-87db-2556e7fc7581","doc_no":"A.2.4.1.2.2.3.3.1","title":"Integration Of Base Rate Into Allocator Vaults","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1838,"content":"Allocator Vaults must be updated to accrue interest in real time based on the Base Rate.","contentHash":"afeb6574759d46cbf720ea7136752933846400bddd45192460773e13e7c8af9b","addressRefs":[]},"50b52e7e-2f79-4a7a-b887-cda85bc77cd7":{"id":"50b52e7e-2f79-4a7a-b887-cda85bc77cd7","doc_no":"A.2.4.1.2.2.3.3.2","title":"Automation Of Monthly Settlement Cycle Based On Base Rate","type":"Core","depth":6,"parentId":"cf1d76c1-fc9f-499d-866f-265276e421f0","order":1839,"content":"The Core Council Risk Advisor must update the tooling specified in [A.2.4.1.2.2.2.3.1 - Automation Of Monthly Settlement Cycle Calculation Including Virtual Base Rate](d98d3753-4230-4ad8-a1e7-7b1fd7e3b679) to reflect the onchain accrual of the Base Rate.","contentHash":"a75a4d0fb16dc8b011b4bdcef40ebfc515cd68c76e49c5ca0f872bdeb53e431e","addressRefs":[]},"bb0c23c6-5123-4c35-ac84-fcb018a72cda":{"id":"bb0c23c6-5123-4c35-ac84-fcb018a72cda","doc_no":"A.2.5","title":"Agent Incubation","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1840,"content":"This Article governs the incubation of Agents. It defines the necessary infrastructure and processes to ensure Agents are maximally supported to generate as much value as possible for the Sky Ecosystem.","contentHash":"eb7b823a8b99bc9dcb144a104668b09ad039cfdabf808b508ff2b32fa12e2329","addressRefs":[]},"a28b1bca-adac-493d-a052-40e36c97e670":{"id":"a28b1bca-adac-493d-a052-40e36c97e670","doc_no":"A.2.5.1","title":"Support For Agents","type":"Section","depth":3,"parentId":"bb0c23c6-5123-4c35-ac84-fcb018a72cda","order":1841,"content":"This Section defines elements and infrastructure to support Agents.","contentHash":"638ce781a04191780a55e27180f9f6b0dfe96752e197acd716a9d3ca56f2b3ce","addressRefs":[]},"b09e86b1-0e95-4111-b141-7a980eeaef08":{"id":"b09e86b1-0e95-4111-b141-7a980eeaef08","doc_no":"A.2.6","title":"Ecosystem Actor Incubation","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1842,"content":"This Article governs the incubation of new Ecosystem Actors to support the Sky Ecosystem.","contentHash":"07d66836c0624efe58addf179e9d305f969f44c2d5937d14d60f33696336e006","addressRefs":[]},"0016dcac-6cf0-4e66-ae6f-112f40eb9767":{"id":"0016dcac-6cf0-4e66-ae6f-112f40eb9767","doc_no":"A.2.6.1","title":"Ecosystem Actor Incubation","type":"Section","depth":3,"parentId":"b09e86b1-0e95-4111-b141-7a980eeaef08","order":1843,"content":"The Support Scope is responsible for incubating Ecosystem Actors. This Section defines the elements to support this objective.","contentHash":"0ffae440fec294474e5513aed037c9a494596ae588f29cf957ecbabd1efd92e3","addressRefs":[]},"0239db13-482e-4a91-b173-ee31569dbb4c":{"id":"0239db13-482e-4a91-b173-ee31569dbb4c","doc_no":"A.2.6.1.1","title":"Incubating Ecosystem Actors","type":"Core","depth":4,"parentId":"0016dcac-6cf0-4e66-ae6f-112f40eb9767","order":1844,"content":"Incubating Ecosystem Actors are Ecosystem Actors that are being developed to support the Sky Protocol or its current and future Agents. Sky Governance can assign these actors projects that benefit the Sky Protocol or incubating Agents, such as solutions for branding, marketing, user acquisition; referral marketing and revenue share systems; smart contract development; and protocol development.","contentHash":"0f5b11af8cfc60d3f77fe229e4967c5032efeec78667cbfdd16c1f8970570135","addressRefs":[]},"3af47ea8-d85b-4bd8-9339-ab053ed7a21a":{"id":"3af47ea8-d85b-4bd8-9339-ab053ed7a21a","doc_no":"A.2.6.1.2","title":"Currently Incubating Ecosystem Actors Template","type":"Core","depth":4,"parentId":"0016dcac-6cf0-4e66-ae6f-112f40eb9767","order":1845,"content":"The list of Incubating Ecosystem Actors must follow this template for each recorded Incubating Ecosystem Actor:\n\n- **.x:** [Incubating Ecosystem Actor name and short description]\n- **.1:** [Budget information]\n- **.2:** [Deliverables and focus areas]\n- **.3:** [Team information, including headcount grouped by skill sets]","contentHash":"6144353f5567636e4410b773070fa03c73d086e427d931d16a73a36d72dc2e62","addressRefs":[]},"a520fea9-c2b7-4fda-a2b0-254b76504bc0":{"id":"a520fea9-c2b7-4fda-a2b0-254b76504bc0","doc_no":"A.2.7","title":"Ecosystem Communication Channels","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1846,"content":"This Article regulates the unified communication infrastructure for governance ecosystem communication. This infrastructure must include channels for inter-Agent and Ecosystem Actor interaction.","contentHash":"a5658fe777ec54b3f152d9c5fa9a6fff78c57a8cfeeb7adc96668bb9955ab7c5","addressRefs":[]},"7574b64b-ccf8-427f-9c32-fa7a1b222f73":{"id":"7574b64b-ccf8-427f-9c32-fa7a1b222f73","doc_no":"A.2.7.1","title":"Ecosystem Communication Channels","type":"Section","depth":3,"parentId":"a520fea9-c2b7-4fda-a2b0-254b76504bc0","order":1847,"content":"The Support Scope maintains the overall unified communication infrastructure used for governance ecosystem communication. This Section defines key elements and infrastructure supporting this objective.","contentHash":"ab8e838192086dc970c204fc0a36ed5e149ec5cb6a171de74045e68ee3ad7c62","addressRefs":[]},"14e381be-b1bb-4b87-a533-212bd135cf27":{"id":"14e381be-b1bb-4b87-a533-212bd135cf27","doc_no":"A.2.7.1.1","title":"Communications Infrastructure","type":"Core","depth":4,"parentId":"7574b64b-ccf8-427f-9c32-fa7a1b222f73","order":1848,"content":"The Core Facilitator is tasked with maintaining an ecosystem-wide communications infrastructure to enable Agent participants and Ecosystem Actors to interact with each other and discuss the Sky Ecosystem.","contentHash":"c1af1dfaf5bf96dcffeb96c9668f09dc82f86f14495573ae0aeb459f59d7f289","addressRefs":[]},"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6":{"id":"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6","doc_no":"A.2.7.1.1.1","title":"Forum","type":"Core","depth":5,"parentId":"14e381be-b1bb-4b87-a533-212bd135cf27","order":1849,"content":"The communications infrastructure must include an ecosystem Forum devoted to discussions on Agent-related business proposals, partnerships and interactions, as well as casual conversation for the broader Sky Ecosystem.","contentHash":"51e2e44e084dc1d4b916bc7cf41283b75c595887a5c3814a9fcd55283554cc00","addressRefs":[]},"a76f81b5-49bb-4697-a30b-bf009ab24286":{"id":"a76f81b5-49bb-4697-a30b-bf009ab24286","doc_no":"A.2.7.1.1.1.1","title":"Authorized Forum Accounts Requirements","type":"Core","depth":6,"parentId":"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6","order":1850,"content":"The documents herein define the requirements for forum account registration, disclosure, and enforcement applicable to entities participating in Sky governance.","contentHash":"7c5d2c3d705998f854524fa5b2117e64cc5b4d7d07620ac56c7d8510ec3f83fc","addressRefs":[]},"3f2ba4e7-cc85-406b-94ce-83da549babc5":{"id":"3f2ba4e7-cc85-406b-94ce-83da549babc5","doc_no":"A.2.7.1.1.1.1.1","title":"Registration Requirement","type":"Core","depth":6,"parentId":"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6","order":1851,"content":"All forum accounts used to post on the Sky Forum in a governance capacity must be registered in [A.2.7.1.1.1.1.4.0.6.1 - Current Authorized Forum Accounts](b71564fd-22e0-4c69-99d1-5b23fc1fa329). Each registration must include:\n\n- The entity handle, which is the official forum account representing the entity. If an entity does not maintain its own forum handle, it may indicate this in the registry and rely solely on Authorized Representatives.\n- All Authorized Representatives, which are forum accounts held by team members, individuals, or other entities that are authorized to post on behalf of the entity.\n\nEach entity is responsible for ensuring that its registration reflects its current handles and Authorized Representatives, and that any changes are promptly updated. A single forum handle may appear as an Authorized Representative of more than one (1) entity.","contentHash":"59977426015bb9aefdd670b22cf9abec3af5c1d0917bc45f7933edeccb9bf4c9","addressRefs":[]},"87a69cf4-cf81-4acc-bb90-7caf644eaa86":{"id":"87a69cf4-cf81-4acc-bb90-7caf644eaa86","doc_no":"A.2.7.1.1.1.1.2","title":"Disclosure Requirement","type":"Core","depth":6,"parentId":"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6","order":1852,"content":"When posting on behalf of another entity, the Authorized Representative must clearly indicate in the post that they are acting on behalf of that entity.","contentHash":"19503af0ed7f3f2f12dc81691ecec67b2237d02a25a92ecb048ac91c605ce8f6","addressRefs":[]},"0fa7211a-81a5-40bd-a364-0a85ebf6577e":{"id":"0fa7211a-81a5-40bd-a364-0a85ebf6577e","doc_no":"A.2.7.1.1.1.1.3","title":"Enforcement","type":"Core","depth":6,"parentId":"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6","order":1853,"content":"Posts on governance matters from unregistered forum accounts may be disregarded for governance purposes. Accounts that repeatedly post in a governance capacity without registration are subject to moderation as specified in [A.2.7.1.2 - Moderation](be3da4c5-6882-4694-9ccd-3fa7c5f6e09a).","contentHash":"6ce4ec3ec5803926ab759c67811987d52eb961d419a402ec55219da1af925d53","addressRefs":[]},"248a4fd8-f863-493a-9a38-2a97d9d7203e":{"id":"248a4fd8-f863-493a-9a38-2a97d9d7203e","doc_no":"A.2.7.1.1.1.1.4","title":"List Of Authorized Forum Accounts","type":"Active Data Controller","depth":6,"parentId":"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6","order":1854,"content":"The list of authorized forum accounts is defined as Active Data in [A.2.7.1.1.1.1.4.0.6.1 - Current Authorized Forum Accounts](b71564fd-22e0-4c69-99d1-5b23fc1fa329).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the entity to which the registration pertains.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"4f2a79eea15769e2ca2bb7834b2c9ba20f8106dc1b8a401b9f3b11bd6ff2275f","addressRefs":[]},"b71564fd-22e0-4c69-99d1-5b23fc1fa329":{"id":"b71564fd-22e0-4c69-99d1-5b23fc1fa329","doc_no":"A.2.7.1.1.1.1.4.0.6.1","title":"Current Authorized Forum Accounts","type":"Active Data","depth":6,"parentId":"ec33a431-9aa0-443e-9f0c-d0ab0aacfae6","order":1855,"content":"| Entity Name | Role | Entity Handle | Handles of Authorized Representatives |\n|---|---|---|---|\n| Pattern | Prime Agent | PatternDevCo | N/A |\n| Redline | Operational Facilitator | N/A | redlexic |\n| BA Labs | Core Council Risk Advisor | BALabs | DeFlamiingo, Sean, 0xmmj, commanderkeen, Primoz, Twigmaester, rema, definikola |\n| Spark | Prime Agent | PhoenixLabs | N/A |\n| Obex | Prime Agent | Rubicon | N/A |\n| Grove | Prime Agent | GroveLabs | steakhouse |\n| Soter Labs | Operational GovOps | SoterLabs | N/A |\n| Amatsu | Operational Executor Agent | Amatsu | SoterLabs, Endgame-Edge (and their authorized representatives) |\n| Dewiz | Ecosystem Actor | Dewiz | N/A |\n| Atlas Axis | Core GovOps | atlas-axis | Le_Bateleur, adamfraser, Lex |\n| Ozone | Operational Executor Agent | N/A | SoterLabs, Redline (and their authorized representatives) |\n| Endgame Edge | Operational Facilitator | Endgame-Edge | votewizard, CivicSage, boet, blimpa |\n| Keel | Prime Agent | Elodin | N/A |\n| Sidestream | Ecosystem Actor | Sidestream | N/A |\n| JanSky | Core Facilitator | JanSky-Team | JanSky, ldr |\n| Rune | N/A | rune | N/A |","contentHash":"4430f81a9f53b1f76757c02853dc9541e2444fea6669784456a0cbcc5074f638","addressRefs":[]},"a596136b-a805-420b-be77-bf249e41ada4":{"id":"a596136b-a805-420b-be77-bf249e41ada4","doc_no":"A.2.7.1.1.2","title":"Chatroom","type":"Core","depth":5,"parentId":"14e381be-b1bb-4b87-a533-212bd135cf27","order":1856,"content":"The communications infrastructure must include a chatroom for broad discussion related to Agents, Ecosystem Actors and Sky. As an initial bootstrapping measure, the Core Facilitator can use Discord.","contentHash":"48a65b86e1374eea7a8dda2d40c58776dc11d9234c1d5c985219fb97efd8afd0","addressRefs":[]},"be3da4c5-6882-4694-9ccd-3fa7c5f6e09a":{"id":"be3da4c5-6882-4694-9ccd-3fa7c5f6e09a","doc_no":"A.2.7.1.2","title":"Moderation","type":"Core","depth":4,"parentId":"7574b64b-ccf8-427f-9c32-fa7a1b222f73","order":1857,"content":"The documents herein define the moderation policies and responsible moderators for Sky's communication channels.","contentHash":"b59acfe26cfb42aa29d87e3948c15bba1b533d57cc395872c7d7c2465f5e68f5","addressRefs":[]},"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4":{"id":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","doc_no":"A.2.7.1.2.1","title":"Moderation Policies","type":"Core","depth":5,"parentId":"be3da4c5-6882-4694-9ccd-3fa7c5f6e09a","order":1858,"content":"The documents herein define the moderation policies applicable to Ecosystem Communication Channels.","contentHash":"7630567edb55a3e6de3cec7b517f1600e31c942a98a7335ea13fb60d8fe02e83","addressRefs":[]},"63701dcb-d885-4f81-a67b-71f5bf67bde8":{"id":"63701dcb-d885-4f81-a67b-71f5bf67bde8","doc_no":"A.2.7.1.2.1.1","title":"General Requirements","type":"Core","depth":6,"parentId":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","order":1859,"content":"This document defines the requirements generally applicable to all Ecosystem Communication Channels.\n\nResponsible moderators are granted the prerogative to ban users from the communication channels for which they are responsible when they deem users to be acting in a misaligned fashion. Misalignment can include maliciously exploiting the communication channel or disrupting its efficient functioning through improper use or antisocial behavior.\n\nHowever, unless egregiously misaligned or disrupting behavior takes place, responsible moderators should err on the side of charity and issue a public warning for users who engage in bad behavior before resorting to banning them. Egregiously misaligned or disrupting behavior includes spamming, flooding, threatening, or using inappropriate or abusive language.\n\nOnly the Core Facilitator may ban a user from the Sky Forum when doing so would operationally block an ongoing governance process (e.g. the user has submitted an otherwise eligible governance proposal).","contentHash":"c85e9fc5d42b51b88d5ee12fae39a8d1b631a5145e78691f84877bc4a8756353","addressRefs":[]},"d18821e4-cee6-41d0-91fb-b5bb963b2594":{"id":"d18821e4-cee6-41d0-91fb-b5bb963b2594","doc_no":"A.2.7.1.2.1.1.1","title":"Public Communication Of Bans","type":"Core","depth":6,"parentId":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","order":1860,"content":"The documents herein define the requirements regarding public communication of bans. The Sky Forum is subject to special requirements that are defined in [A.2.7.1.2.1.1.1.1 - Sky Forum-Specific Requirements](a3e4d767-56d1-4b1f-8ade-b733bca4244f). Requirements applicable to all other Ecosystem Communication Channels are defined in [A.2.7.1.2.1.1.1.2 - Requirements Applicable To All Other Channels](d64ffda4-097c-47f8-b497-f20e7456b7fa).","contentHash":"b7af51f172c7f14a84c4e4193b8fb9acf3358320236b2a2a90f4e46c7b8aa6f7","addressRefs":[]},"a3e4d767-56d1-4b1f-8ade-b733bca4244f":{"id":"a3e4d767-56d1-4b1f-8ade-b733bca4244f","doc_no":"A.2.7.1.2.1.1.1.1","title":"Sky Forum-Specific Requirements","type":"Core","depth":6,"parentId":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","order":1861,"content":"For the Sky Forum, the Core Facilitator must publicly communicate the ban and the reasons for banning a user if the ban interrupts the users' exercise of a governance process.\n\nIn all other cases involving the Sky Forum, responsible moderators may exercise their best judgment in determining whether to publicly communicate a ban and the reasons for a ban. In doing so, the responsible moderators should consider the importance of transparency and community awareness as well as whether the banned user has engaged in egregiously misaligned and disrupting behavior. In every case, the moderators must still use the built-in forum functionality to register the ban reason for every banned user so that all forum users can see it when visiting the forum profile of the banned user.\n\nIf it is assessed that a public communication is necessary, the Core Facilitator is responsible for writing and publishing it.","contentHash":"24c43e9274568bc063bb1faefd324e4bb2ddcbc5fae9b67473dc7bea7fd5e5e7","addressRefs":[]},"d64ffda4-097c-47f8-b497-f20e7456b7fa":{"id":"d64ffda4-097c-47f8-b497-f20e7456b7fa","doc_no":"A.2.7.1.2.1.1.1.2","title":"Requirements Applicable To All Other Channels","type":"Core","depth":6,"parentId":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","order":1862,"content":"For all Ecosystem Communication Channels other than the Sky Forum, the responsible moderators may exercise their discretion in determining whether to publicly communicate a ban and the reasons for the ban.","contentHash":"9ffe596a3a2e2bddb65ed76b4a497487145c05b4261821b9a320a9d8503ba15a","addressRefs":[]},"76247105-be57-4eac-9eb4-793947a43d67":{"id":"76247105-be57-4eac-9eb4-793947a43d67","doc_no":"A.2.7.1.2.1.1.2","title":"Use Of Automated Tools","type":"Core","depth":6,"parentId":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","order":1863,"content":"Responsible moderators may use automated tools, including AI and bots, to help fulfill their moderation responsibilities. The responsible moderators retain responsibility for ensuring that these tools conform to moderation policies and must establish a process through which automated decisions can be reviewed by the responsible moderators.","contentHash":"f646236898391050ab26d0484a076d33bf1f84a236acf84d8a0939e1df8143d5","addressRefs":[]},"4d4a1d9a-c8c7-4c2b-aaec-33e382790d52":{"id":"4d4a1d9a-c8c7-4c2b-aaec-33e382790d52","doc_no":"A.2.7.1.2.1.1.3","title":"Unbanning","type":"Core","depth":6,"parentId":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","order":1864,"content":"Bannings are by default permanent. However, Ranked Delegates can propose the unbanning of users by publishing a forum post that states the handle(s) of the user(s) whose unbanning they request and the rationale for their unbanning. The forum post must tag the Core Facilitator, who will in turn prepare a binary Weekly Cycle Governance Poll to be published on the Voting Portal as soon as reasonably possible. The outcome of the Governance Poll is binding.\n\nWhere identity can be proven, the ban on unbanned users will be lifted across all communication channels.","contentHash":"d9b931f3efb9f8f13b248ddfe71901785bbf9c80708d0476be7c0774b66eaf40","addressRefs":[]},"9e2d25b0-227c-4f08-a466-c99dc7243d92":{"id":"9e2d25b0-227c-4f08-a466-c99dc7243d92","doc_no":"A.2.7.1.2.1.1.4","title":"Intrinsic Limitations","type":"Core","depth":6,"parentId":"236ecf52-bd7f-4170-9cc5-f5b25f5ba3d4","order":1865,"content":"Given the digital nature of these communication channels and the consequent practical unenforceability of permanent bannings, responsible moderators are expected to have to deal with recurring banned users under new aliases. Responsible moderators must exercise best judgement when suspecting a user to be a banned user under a different guise and when assessing whether they pose a risk of recidivism.","contentHash":"55462192cc491eeef76497f56c3e2a5209084fd7bceb66e7096949577b10e1b0","addressRefs":[]},"1f76a652-0958-4165-8183-51c9eaccdbaa":{"id":"1f76a652-0958-4165-8183-51c9eaccdbaa","doc_no":"A.2.7.1.2.2","title":"List of Responsible Moderators","type":"Core","depth":5,"parentId":"be3da4c5-6882-4694-9ccd-3fa7c5f6e09a","order":1866,"content":"The responsible moderators for each communication channel are:\n\n- Sky Forum - The Core Facilitator\n- Sky and Sky Builder Discord - The Core Facilitator and Ecosystem Actor TechOps Services\n- Sky X / Twitter Account - Ecosystem Actor Maker Growth\n- MakerDAO Subreddit - Ecosystem Actor Maker Growth","contentHash":"b869b7fc0b00c0689e7d868b547b1c4421a4177b0ef2506b2cc3af985b6d2e91","addressRefs":[]},"72d16b65-95cf-4cff-a2f4-71ce92019f84":{"id":"72d16b65-95cf-4cff-a2f4-71ce92019f84","doc_no":"A.2.7.1.3","title":"Communications Infrastructure Budget","type":"Core","depth":4,"parentId":"7574b64b-ccf8-427f-9c32-fa7a1b222f73","order":1867,"content":"The ecosystem communication infrastructure budget is 0 USDS per quarter.","contentHash":"7c636c64223fa534189d623e2d46253d89758d786dd64a8eeb8640ad78051ce1","addressRefs":[]},"104c3543-ce94-4a2f-9968-57f1ee858085":{"id":"104c3543-ce94-4a2f-9968-57f1ee858085","doc_no":"A.2.8","title":"Ecosystem Accords","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":1868,"content":"This Article governs Ecosystem Accords, agreements between actors in the Sky Ecosystem that are enforceable by Sky Governance.","contentHash":"65684edaf809c424286300d4c1d4f057db2cdf142102a50dbdda340bbc84da88","addressRefs":[]},"f4d827e9-bf60-4180-a1d0-446af1245365":{"id":"f4d827e9-bf60-4180-a1d0-446af1245365","doc_no":"A.2.8.1","title":"Dispute Resolution","type":"Section","depth":3,"parentId":"104c3543-ce94-4a2f-9968-57f1ee858085","order":1869,"content":"This Section defines the process for resolving disputes regarding Ecosystem Accords.","contentHash":"bdc8a96e1d96c5255e0a3468cd0e212a6295c968216087ac96bfe1ccb51c6bbb","addressRefs":[]},"82a04a56-8cc9-4adf-9714-da246d541371":{"id":"82a04a56-8cc9-4adf-9714-da246d541371","doc_no":"A.2.8.1.1","title":"Dispute Resolution By Core Council","type":"Core","depth":4,"parentId":"f4d827e9-bf60-4180-a1d0-446af1245365","order":1870,"content":"Disputes regarding Ecosystem Accords are resolved by the Core Council as specified in the documents herein.","contentHash":"738bfa2f68e8c5d7b2410bffb8ec9209cc337442d13ce61a83462c9c2928cbc2","addressRefs":[]},"4973a9b8-66f1-4486-829e-6c9464b9407c":{"id":"4973a9b8-66f1-4486-829e-6c9464b9407c","doc_no":"A.2.8.1.1.1","title":"Roles","type":"Core","depth":5,"parentId":"82a04a56-8cc9-4adf-9714-da246d541371","order":1871,"content":"The documents herein define the respective roles of Core GovOps and the Core Facilitator in resolving disputes.","contentHash":"2fadf3fcc730117e747ddacc00d9122dcbcfbd0f5900e54f9fdfa168c79a5497","addressRefs":[]},"59ca12d1-a25c-4974-90d9-ccf7dae184f3":{"id":"59ca12d1-a25c-4974-90d9-ccf7dae184f3","doc_no":"A.2.8.1.1.1.1","title":"Role Of Core GovOps","type":"Core","depth":6,"parentId":"4973a9b8-66f1-4486-829e-6c9464b9407c","order":1872,"content":"Core GovOps manages the overall dispute resolution process, including establishing communication channels for dispute resolution, communicating with the parties, and gathering and analyzing information relating to the dispute.","contentHash":"337f5355805c75b86c9f0cf8aedd16e4b03122dc2dc95434824e0771d47eb436","addressRefs":[]},"cf7e0654-f9a6-45e4-9984-14387067cb17":{"id":"cf7e0654-f9a6-45e4-9984-14387067cb17","doc_no":"A.2.8.1.1.1.2","title":"Role Of Core Facilitator","type":"Core","depth":6,"parentId":"4973a9b8-66f1-4486-829e-6c9464b9407c","order":1873,"content":"The Core Facilitator decides how the dispute is ultimately resolved. The Core Facilitator is isolated from the parties to maintain impartiality. The Core Facilitator exclusively reviews the information prepared by Core GovOps and delivers a decision to Core GovOps, which communicates it to the parties.","contentHash":"29cf43a8b66bafa52b67ca6509504717726a2884ed7b8b78b5f87ed0fbd87b2b","addressRefs":[]},"6151ee33-ff22-4bda-955b-f3731ab9b522":{"id":"6151ee33-ff22-4bda-955b-f3731ab9b522","doc_no":"A.2.8.1.1.2","title":"Process Definition","type":"Core","depth":5,"parentId":"82a04a56-8cc9-4adf-9714-da246d541371","order":1874,"content":"The documents herein define the process for resolving disputes.","contentHash":"0851a4240453bfa5be984f0b5e5fa119cf805e725d3738b73f0ef484712974b2","addressRefs":[]},"8bf58bdf-4a6f-4e8b-9829-7e375719ad4a":{"id":"8bf58bdf-4a6f-4e8b-9829-7e375719ad4a","doc_no":"A.2.8.1.1.2.1","title":"Dispute Intake","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1875,"content":"The documents herein define the process for dispute intake for dispute resolution.","contentHash":"c9a19648b4de587a021c10c8b245e4a02d920a4c5242b820f4af869836a2b478","addressRefs":[]},"3f43d965-56e4-4153-a59a-00329e3b00e5":{"id":"3f43d965-56e4-4153-a59a-00329e3b00e5","doc_no":"A.2.8.1.1.2.1.1","title":"Formal Request For Dispute Resolution","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1876,"content":"The dispute resolution process begins with an actor in the Sky Ecosystem requesting formal dispute resolution from Core GovOps.","contentHash":"6523512de3be5dd6461741a547aea92215d39e9d901431f66dbc780194ed1eff","addressRefs":[]},"c2f9e098-b0f5-44ae-b44d-a9481707b787":{"id":"c2f9e098-b0f5-44ae-b44d-a9481707b787","doc_no":"A.2.8.1.1.2.1.2","title":"Preliminary Determination Of Reasonableness By Core GovOps","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1877,"content":"After receiving the request for dispute resolution, Core GovOps makes a brief preliminary determination regarding whether the request is reasonable (i.e. not vexatious or frivolous), within three (3) working days.","contentHash":"b625038efc2166e0fa6c189b220f5394c8c128749cd2582ea47b75d313db26c0","addressRefs":[]},"7765da19-eae7-4b76-b9e0-155b251be3c7":{"id":"7765da19-eae7-4b76-b9e0-155b251be3c7","doc_no":"A.2.8.1.1.2.1.3","title":"Handling Of Unreasonable Requests","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1878,"content":"If Core GovOps determines that the request for dispute resolution is not reasonable, it will inform the actor who submitted the request accordingly, providing their reasons. In this case, there is no further action.","contentHash":"6bf3b238804ac2fe3f3451a01812eb75535a8dfd2d0fefa7427af7aec4292695","addressRefs":[]},"f26cc457-75eb-4b42-9ac0-55fe3d6fcb43":{"id":"f26cc457-75eb-4b42-9ac0-55fe3d6fcb43","doc_no":"A.2.8.1.1.2.1.4","title":"Handling Of Reasonable Requests","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1879,"content":"If Core GovOps makes a determination that the request is reasonable, then Core GovOps formally begins the dispute resolution process by notifying all relevant parties that the process is about to begin. The notifications to each party will outline the process to be followed, including relevant steps and timeframes that the party should be aware of.","contentHash":"d10b17adfa5c25f5bad4276a296b58ead5e01376d4704e1cb8cca3a518de7648","addressRefs":[]},"f08ccecb-88cc-4d28-8a62-8be9f3b8d19b":{"id":"f08ccecb-88cc-4d28-8a62-8be9f3b8d19b","doc_no":"A.2.8.1.1.2.2","title":"Presentation Of Arguments","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1880,"content":"The documents herein define the process for the presentation of arguments for dispute resolution.","contentHash":"ad60346333342ee4f7b652de266bf4de99963c539038d414a7cb0439acb04566","addressRefs":[]},"550f5cfb-0f3d-4b05-8e86-80315d4f135a":{"id":"550f5cfb-0f3d-4b05-8e86-80315d4f135a","doc_no":"A.2.8.1.1.2.2.1","title":"Statement Of Problem","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1881,"content":"The party that initiated the dispute resolution process has five (5) working days from the formal initiation of the process to submit a Statement of Problem, laying out the facts they consider relevant to the dispute and the issues related to the Atlas as they see them.","contentHash":"5425935085fef89903e9c02086353efd2b0781416ac35fb32e4c3cdaa680dbb5","addressRefs":[]},"a1e21e2a-be88-4041-9204-0c2936e693d7":{"id":"a1e21e2a-be88-4041-9204-0c2936e693d7","doc_no":"A.2.8.1.1.2.2.2","title":"Statement Of Response","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1882,"content":"Core GovOps provides the Statement of Problem to the other party/parties. They have five (5) working days to submit a Statement of Response, which sets out their perspective on the relevant facts and issues in the dispute.","contentHash":"16e22cb0fb0cbf16654030c1e816f3d306f53beea9f8c2bb29e4d9d2f1eb8c48","addressRefs":[]},"cedc6a69-da33-421a-a090-2cae2f0e7185":{"id":"cedc6a69-da33-421a-a090-2cae2f0e7185","doc_no":"A.2.8.1.1.2.2.3","title":"Statement Of Rebuttal","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1883,"content":"Core GovOps provides the Statement of Response to the party that initiated the dispute resolution process. They have three (3) working days to submit a Statement of Rebuttal.","contentHash":"6d4770b546f8c16575b4e79d7f7d84b6197dc414c7cda21ea0a7738b1af8f4c0","addressRefs":[]},"262a79a0-c5be-4721-ab27-ba7ba45776c5":{"id":"262a79a0-c5be-4721-ab27-ba7ba45776c5","doc_no":"A.2.8.1.1.2.3","title":"Decision","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1884,"content":"The documents herein define the decision process for dispute resolution.","contentHash":"abaf4ae7c7f112e5f4142396488fa7e9e623d576c08a74f62e8269971ec1deaf","addressRefs":[]},"5594d477-159c-4baf-86dd-3d5f0c1d857b":{"id":"5594d477-159c-4baf-86dd-3d5f0c1d857b","doc_no":"A.2.8.1.1.2.3.1","title":"Analysis By Core GovOps","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1885,"content":"Core GovOps prepares a confidential analysis of the dispute for the Core Facilitator. This analysis must include a summary of all relevant facts as far as it is possible to ascertain, clear identification of any areas of factual ambiguity or disagreement between the parties, a structured presentation of the arguments in favor of each party, and a recommendation if Core GovOps believes one conclusion is clearly supported by the facts.","contentHash":"bed0896f673d681d75734c677f116a7ad22ecbcc85da67a79a4bc8127665d7fe","addressRefs":[]},"056774ab-b584-4f37-90f4-9c17b79ddfb3":{"id":"056774ab-b584-4f37-90f4-9c17b79ddfb3","doc_no":"A.2.8.1.1.2.3.2","title":"Adjudication By Core Facilitator","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1886,"content":"The Core Facilitator reviews the analysis prepared by Core GovOps along with the arguments presented by the parties and reaches a decision within three (3) working days.\n\nThe Core Facilitator must draft a decision setting out relevant facts and the core reasoning of their decision. In doing so, the Core Facilitator is free to adopt arguments presented by the parties, by Core GovOps, or to advance their own analysis.","contentHash":"d957ae4672effa51268486a81d1f4cff6c32380ec1ecc82e0c4516aee2fed698","addressRefs":[]},"c172684d-9564-40f9-8d47-82d736a3d876":{"id":"c172684d-9564-40f9-8d47-82d736a3d876","doc_no":"A.2.8.1.1.2.3.3","title":"Release Of Decision","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1887,"content":"The Core Facilitator communicates their decision to Core GovOps. Core GovOps communicates the decision to all related parties.","contentHash":"ef327e5ddfffba4f751f5cd054c50f03e692bebd9d9763a34d2440176edf6e97","addressRefs":[]},"5e4b0330-1469-4fb0-9622-6bf32b8c6afa":{"id":"5e4b0330-1469-4fb0-9622-6bf32b8c6afa","doc_no":"A.2.8.1.1.2.3.4","title":"Publication Of Decision","type":"Core","depth":6,"parentId":"6151ee33-ff22-4bda-955b-f3731ab9b522","order":1888,"content":"The Core Facilitator publishes the decision on the Sky Forum and updates the [A.2.8.1.2.0.6.1 - Dispute Resolutions](c48614bb-6f51-4de7-97bd-ef1fed968d72) Active Data document in the Atlas, redacting any confidential information as needed.","contentHash":"ea282918a2c7b0a5833bd2a4d382a569dc83969891da96ecd096a9d3921adb70","addressRefs":[]},"e6384df7-246b-4240-93e8-01bf903e072d":{"id":"e6384df7-246b-4240-93e8-01bf903e072d","doc_no":"A.2.8.1.2","title":"Dispute Resolution Recording","type":"Active Data Controller","depth":4,"parentId":"f4d827e9-bf60-4180-a1d0-446af1245365","order":1889,"content":"Resolutions of disputes involving Ecosystem Accords are defined as Active Data in [A.2.8.1.2.0.6.1 - Dispute Resolutions](c48614bb-6f51-4de7-97bd-ef1fed968d72).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Facilitator.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"4e945572cb4cb98758e7c049c7075901595bb44984804a64851d83a137efd6f8","addressRefs":[]},"c48614bb-6f51-4de7-97bd-ef1fed968d72":{"id":"c48614bb-6f51-4de7-97bd-ef1fed968d72","doc_no":"A.2.8.1.2.0.6.1","title":"Dispute Resolutions","type":"Active Data","depth":5,"parentId":"e6384df7-246b-4240-93e8-01bf903e072d","order":1890,"content":"The resolutions of disputes regarding Ecosystem Accords are:\n\n- **Dispute Between Spark And Grove Regarding Effective Date Of Their Ecosystem Accord** (September 2, 2025) - [Facilitator Decision on Grove/Spark Dispute](https://forum.skyeco.com/t/facilitator-decision-on-grove-spark-dispute/27141)","contentHash":"22782b26148299a59b92f34f12c1188f8ba9f8463ea6947bb1ea060ec074b95d","addressRefs":[]},"be46648d-a154-480a-b202-81fd1ac735d2":{"id":"be46648d-a154-480a-b202-81fd1ac735d2","doc_no":"A.2.8.2","title":"Active Ecosystem Accords","type":"Section","depth":3,"parentId":"104c3543-ce94-4a2f-9968-57f1ee858085","order":1891,"content":"The subdocuments herein record currently active Ecosystem Accords.","contentHash":"fc2c055838ccda31c824cc03e4f30bbcc7c014f69ab06c4cd56aab4728d3b943","addressRefs":[]},"9ca40096-937e-431e-af50-9ecd50c0d0a8":{"id":"9ca40096-937e-431e-af50-9ecd50c0d0a8","doc_no":"A.2.8.2.1","title":"Ecosystem Accord 1: Grove And Spark Agents","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":1892,"content":"The subdocuments herein record the terms of agreement between Grove and Spark as agreed in Ecosystem Accord 1.","contentHash":"5a3332f630117039cdd08b48cacb78956014401c8ca0ccc290d4d12f762f36ae","addressRefs":[]},"4512c23a-2b01-4a38-ad02-9a016e1d0c54":{"id":"4512c23a-2b01-4a38-ad02-9a016e1d0c54","doc_no":"A.2.8.2.1.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"9ca40096-937e-431e-af50-9ecd50c0d0a8","order":1893,"content":"The subdocuments herein set out the key details of Ecosystem Accord 1, such as parties to the agreement and the duration of the Accord.","contentHash":"780747c7ac661d6117e5b6e25ff6419ac20fe85324e832294c333ee5c4de0004","addressRefs":[]},"817d9d87-9659-43b5-80ce-8f68b592a625":{"id":"817d9d87-9659-43b5-80ce-8f68b592a625","doc_no":"A.2.8.2.1.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"4512c23a-2b01-4a38-ad02-9a016e1d0c54","order":1894,"content":"The Grove and Spark Agents are the parties to Ecosystem Accord 1. These parties are also referred to as Grove and Spark, respectively, in the terms of this Accord.","contentHash":"0d642b806f726c5ec2277b08500668ceb905fa1ec066520c4ffe32d1da23a072","addressRefs":[]},"c2fe6ab2-bec3-48d3-b4b1-9f93cd97f693":{"id":"c2fe6ab2-bec3-48d3-b4b1-9f93cd97f693","doc_no":"A.2.8.2.1.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"4512c23a-2b01-4a38-ad02-9a016e1d0c54","order":1895,"content":"The duration of Ecosystem Accord 1 is six (6) months, commencing from May 29, 2025.","contentHash":"f493b09dbd35194cc3242a3356140bd8322715c359e2a325bd3a9dc6ca0b6e05","addressRefs":[]},"a20cefff-cd64-4c01-93e0-052915759938":{"id":"a20cefff-cd64-4c01-93e0-052915759938","doc_no":"A.2.8.2.1.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"9ca40096-937e-431e-af50-9ecd50c0d0a8","order":1896,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 1.","contentHash":"57d63b7d408c8c41fe65438155882e314290e8cc5bd6775c80dde2ac38aabf85","addressRefs":[]},"25743b88-dead-47fe-bd81-b709e69f5949":{"id":"25743b88-dead-47fe-bd81-b709e69f5949","doc_no":"A.2.8.2.1.2.1","title":"Revenue Share","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1897,"content":"Grove and Spark agree to a bilateral revenue share, up to 40% maximum with JRC rental, see [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"34e33e7557e3bbf4ff1a9c48ca7bd33e68bafb76273065eee9e84b7420cc9a4c","addressRefs":[]},"66089224-1a28-475f-9276-ed2bd956e48e":{"id":"66089224-1a28-475f-9276-ed2bd956e48e","doc_no":"A.2.8.2.1.2.1.1","title":"Revenue Share Definition","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1898,"content":"Each Agent retains the right to force the other Prime Agent to do revenue sharing up to 40% by providing that Prime with rented JRC. Sharing is done on the net revenue after deducting the cost to Sky. This is only considered on the spread earned on USDS debt, including any subsidy amounts.","contentHash":"00bc92919d6ded2e54195c01ff59312e49420aa16d450dbbeafbd6f6b920386a","addressRefs":[]},"76d646ca-be88-47e5-b9c6-943155fe2fb1":{"id":"76d646ca-be88-47e5-b9c6-943155fe2fb1","doc_no":"A.2.8.2.1.2.2","title":"Grove Agent Exclusivity","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1899,"content":"Grove exclusivity includes Real World Assets (RWAs), which exclusivity does not extend to Treasuries used for ASC purposes or stablecoin liquidity provisioning.","contentHash":"874277ede7a91b9a118a52953110c6a1530c805ea6baa72c545a51256cb2fb28","addressRefs":[]},"e979e76f-e970-45de-bddb-38c86ac3c007":{"id":"e979e76f-e970-45de-bddb-38c86ac3c007","doc_no":"A.2.8.2.1.2.3","title":"Spark Agent Exclusivity","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1900,"content":"Spark Agent exclusivity includes Maple, cryptocurrency OTC lending, and Established DeFi Lending Protocols, as defined in [A.2.8.2.1.2.3.1 - Established DeFi Lending Protocol Definition](0d74de1b-bb46-4286-bcbf-d260d1204465).","contentHash":"f3b7b9acfdf7da33cd8906590e3ce0651439f01884ab9de252f6fefc79d48d5d","addressRefs":[]},"0d74de1b-bb46-4286-bcbf-d260d1204465":{"id":"0d74de1b-bb46-4286-bcbf-d260d1204465","doc_no":"A.2.8.2.1.2.3.1","title":"Established DeFi Lending Protocol Definition","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1901,"content":"Established DeFi Lending Protocols are defined as DeFi lending protocols deployed six months ago or earlier.","contentHash":"27bfba6820a961fe681353ed0b585e35dce4622eaa9c1ed4f62214e52229f3a5","addressRefs":[]},"8d64aa84-ae79-4bde-ae94-5dd7c18d3019":{"id":"8d64aa84-ae79-4bde-ae94-5dd7c18d3019","doc_no":"A.2.8.2.1.2.4","title":"Right Of First Refusal","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1902,"content":"Grove provides the Spark Agent with a right of first refusal for DeFi opportunities on unclaimed chains and new protocols, including bootstrapping incentive programs.","contentHash":"7c89cc390b11f21f2ab1134bdb4e738d93ffd98ae997cabd2e92798e18cd4685","addressRefs":[]},"0db1525d-bcce-469a-b414-65b41669432d":{"id":"0db1525d-bcce-469a-b414-65b41669432d","doc_no":"A.2.8.2.1.2.4.1","title":"DeFi Opportunities Right of First Refusal Duration","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1903,"content":"Grove provides the Spark Agent a right of first refusal for pursuing cross-chain bootstrapping opportunities, which lasts four weeks after notification by Grove. If Spark does not wish to deploy SparkLend or provide capital to the protocol in question, Grove retains the right to pursue the opportunity pending security and risk assessments of the target protocol. Upon written notification from Grove of a new DeFi opportunity via a communications channel mutually agreed by the parties, Spark has four weeks to decide whether it wants to deploy SparkLend or lend to the target chain and protocol. If Spark opts not to do so by the end of the four-week period, Grove is permitted to pursue the opportunity.\n\n_Example:__ A lending protocol (i.e. Aave, Euler, Morpho, etc) plans on deploying on blockchain X. Grove provides written notification to Spark about the potential new deployment. Spark evaluates the opportunity and decides there are better opportunities to pursue. The opportunity reverts to Grove after Spark’s refusal; or, if Spark does not issue a formal refusal, the opportunity reverts to Grove after four weeks._","contentHash":"2ec200cab95a3ce3004f15aa3c6ccb73d887386aa0da906ab9ba07c235e0f672","addressRefs":[]},"41ad5689-6679-4129-a24d-aa50334e1f26":{"id":"41ad5689-6679-4129-a24d-aa50334e1f26","doc_no":"A.2.8.2.1.2.4.2","title":"DeFi Opportunities Complementary Deployments","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1904,"content":"Grove and Spark may combine efforts if there is a large enough cross-chain opportunity. For example, Grove may deploy stablecoin liquidity on a target chain and Spark may deploy a SparkLend instance. In this case, complementary efforts are made to mutually benefit the cross-chain deployment, with significant economic benefits received by both parties. This chain would also serve as a new distribution channel for Spark, Grove, and Sky products.","contentHash":"fdb258f910f5874dc63f11f07f560eea826bc034ce0994de678f23382daf2346","addressRefs":[]},"72bad98d-007c-4247-98ba-daeb1c8130b4":{"id":"72bad98d-007c-4247-98ba-daeb1c8130b4","doc_no":"A.2.8.2.1.2.5","title":"ASC Provision","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1905,"content":"Grove retains the right to deploy into repo lending protocols to meet ASC requirements. Deposits must be capped at the lower of either 10% of protocol USDC deposits or the Minimum Actively Stabilizing Collateral, as defined in [A.3.3.2.2 - Minimum Actively Stabilizing Collateral](475fe222-9e4a-4e9d-9be6-a7a424ce02f8). The Spark Agent retains the right to use the PSM for ASC, provided it covers the cost to Grove.","contentHash":"bad9a897d3e7a9079df68ac20784c00e0499e4f92d679d574ef2fbee6ba97f8e","addressRefs":[]},"11ad7c74-6163-452c-acf0-a70af3396d03":{"id":"11ad7c74-6163-452c-acf0-a70af3396d03","doc_no":"A.2.8.2.1.2.6","title":"Treasuries Provision","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1906,"content":"The Spark Agent retains the right to deploy into tokenized US Treasury Bills to meet ASC requirements.","contentHash":"9ffc397c4fbcbc71473e0636105acdfd330cf75a12eb69917ec0abc252bb3614","addressRefs":[]},"d1a4398c-aa95-462b-a212-d2afc047477b":{"id":"d1a4398c-aa95-462b-a212-d2afc047477b","doc_no":"A.2.8.2.1.2.7","title":"Basis Trade Products","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1907,"content":"Basis trade products are available to both Grove and Spark.","contentHash":"9070626152f2bfa4ab56c964dc7771d624cb17e65bc21fe940e5a362509f9952","addressRefs":[]},"784feda7-d69e-4ed3-97c3-95b70314b44e":{"id":"784feda7-d69e-4ed3-97c3-95b70314b44e","doc_no":"A.2.8.2.1.2.8","title":"Grand Prix Airdrops","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1908,"content":"Grove receives any airdrops from the Grand Prix.","contentHash":"909ce0d66713c3cb63b21afa75b0d065f4d54f87db3514b57c1c5a3cfed00943","addressRefs":[]},"56589ad5-4e8e-4af9-926a-fadca7bfa0e3":{"id":"56589ad5-4e8e-4af9-926a-fadca7bfa0e3","doc_no":"A.2.8.2.1.2.9","title":"USDe and sUSDe Revenue Share","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1909,"content":"Spark and Grove agree to share revenue from USDe and sUSDe as specified in the subdocuments herein.","contentHash":"ae21a0499f5f717865c3e66057793e05f72348399bd021c86fffd53c6031ee03","addressRefs":[]},"7d16afc8-0eb4-40db-81aa-915a7f052859":{"id":"7d16afc8-0eb4-40db-81aa-915a7f052859","doc_no":"A.2.8.2.1.2.9.1","title":"Revenue Share","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1910,"content":"Spark and Grove will share 50% of all revenue and expenses associated with Spark’s Allocation System investments in USDe and sUSDe. Revenue includes (1) protocol yield on the amount deployed into these assets, (2) any OTC or negotiated arrangements, payments, or incentives, and (3) manual payments or rebates related to withdrawal activity. Expenses include all costs associated with Spark’s investment in USDe and sUSDe, including mint / burn fees, swap fees, and costs of borrowing funds from Sky.","contentHash":"6a6dc1eb49bed2b260e24be2728e25b2d2581fe5059cf55dfd247cd4383acf7b","addressRefs":[]},"ac648f96-3b0d-46c6-9501-a3a88da26961":{"id":"ac648f96-3b0d-46c6-9501-a3a88da26961","doc_no":"A.2.8.2.1.2.9.2","title":"Risk Capital Share","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1911,"content":"Grove agrees to rent to Spark 50% of the Required Risk Capital associated with Spark’s investments in USDe and sUSDe as a Junior Risk Capital Rental. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"a4980ddf1490234f1b7f60ab32b7f71e36cf68b62f631c357d2dfc14064e168c","addressRefs":[]},"2bb81311-e501-4d0d-b403-f4c619463538":{"id":"2bb81311-e501-4d0d-b403-f4c619463538","doc_no":"A.2.8.2.1.2.9.2.1","title":"Implementation","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1912,"content":"Spark and Grove expressly intend that Grove shares in 50% of the risks of Spark’s investment in USDe and sUSDe and not in the risk of any other investments by Spark.\n\nTo the extent that USDe or sUSDe investments experience losses and Spark is allocated a greater than 50% share of those losses relative to Grove under the TIP JRC mechanism (see [A.3.2.1.2.2.1.2.1 - Initial Loss Absorption By \"Tip JRC\"](6c33bcf5-c29d-48ca-9ee5-e37dcdeb0630)), Grove will transfer funds to Spark so that Grove and Spark each bear 50% of the losses that occur.\n\nTo the extent that Spark experiences losses on investments other than USDe or sUSDe and a portion of those losses is allocated to the Junior Risk Capital rented from Grove, Spark shall reimburse Grove for those losses.","contentHash":"6fd281b7867aef144c8388eb5527c3e826485047659d7e7eb9d164573d6813d5","addressRefs":[]},"a768dda1-1075-4762-a904-c523687cbe6c":{"id":"a768dda1-1075-4762-a904-c523687cbe6c","doc_no":"A.2.8.2.1.2.9.3","title":"Term","type":"Core","depth":6,"parentId":"a20cefff-cd64-4c01-93e0-052915759938","order":1913,"content":"This revenue share shall be effective retroactively, dated back to the launch of Spark’s allocation into USDe and sUSDe beginning the week of July 14, 2025.\nIt shall remain in effect until one of the following conditions is met, whichever occurs first:\n\n1. Grove begins to allocate capital to USDe or sUSDe directly; or\n2. Spark or Grove terminates the revenue share, with reasonable advance notice to the other party.\n\nAny changes to the structure or scope of this arrangement will be discussed transparently and approved by both Spark and Grove.","contentHash":"e48b128b9a079d3e0feadedbe7f37c79f0bfb7540158cf5eddd914ca6cb6bf23","addressRefs":[]},"aa3b8e65-0ded-48c2-9c40-812debf99f32":{"id":"aa3b8e65-0ded-48c2-9c40-812debf99f32","doc_no":"A.2.8.2.2","title":"Prime Program","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":1914,"content":"The subdocuments herein record the terms of agreement between Sky, Grove, and Spark as agreed in Ecosystem Accord 2.","contentHash":"327623938955da7706fcba504d708581a14b5eed758ec38275e59fa5e424cbb6","addressRefs":[]},"a9f4941d-9d07-4191-a8c6-f1cb25a067cc":{"id":"a9f4941d-9d07-4191-a8c6-f1cb25a067cc","doc_no":"A.2.8.2.2.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"aa3b8e65-0ded-48c2-9c40-812debf99f32","order":1915,"content":"The subdocuments herein set out the key details of Ecosystem Accord 2, such as parties to the agreement and the duration of the Accord.","contentHash":"8b2e104f3e9519012a578ec38fb13f8ade866c58263aec1261214e269156934c","addressRefs":[]},"fea17abc-79b6-4b49-81c0-258b303eafe9":{"id":"fea17abc-79b6-4b49-81c0-258b303eafe9","doc_no":"A.2.8.2.2.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"a9f4941d-9d07-4191-a8c6-f1cb25a067cc","order":1916,"content":"The parties to Ecosystem Accord 2 are Sky, Spark, Grove, and Moonbow, as defined in the subdocuments herein.","contentHash":"e14f7c1604ab1fb79892b94f5f64cec0275f2e7b125b37aac0b8d3e685ea547d","addressRefs":[]},"2916297b-e460-409b-85e1-6e1b6d431b98":{"id":"2916297b-e460-409b-85e1-6e1b6d431b98","doc_no":"A.2.8.2.2.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"a9f4941d-9d07-4191-a8c6-f1cb25a067cc","order":1917,"content":"The party ‘Sky’ comprises Sky Core.","contentHash":"9f309ae1b63e0b216b92c7f27c1fdc7edfeb60d0d845610b068d6654fb81ba87","addressRefs":[]},"d40acd19-773c-479f-837a-0291c8b9fcde":{"id":"d40acd19-773c-479f-837a-0291c8b9fcde","doc_no":"A.2.8.2.2.1.1.2","title":"Spark Details","type":"Core","depth":6,"parentId":"a9f4941d-9d07-4191-a8c6-f1cb25a067cc","order":1918,"content":"The party ‘Spark’ comprises the Spark Prime Agent, Spark Foundation, and Phoenix Labs.","contentHash":"5e85ab744093e982d0801eea02fbe9cd4baca3da40edb50380660f296246c566","addressRefs":[]},"ccc2c16a-68a6-4182-a1a4-4f666a8bce2f":{"id":"ccc2c16a-68a6-4182-a1a4-4f666a8bce2f","doc_no":"A.2.8.2.2.1.1.3","title":"Grove Details","type":"Core","depth":6,"parentId":"a9f4941d-9d07-4191-a8c6-f1cb25a067cc","order":1919,"content":"The party ‘Grove’ comprises the Grove Prime Agent, and Grove Foundation.","contentHash":"1832b35742193a0ada33800abdc6f213d978b21c0dfc39328856052344fc707c","addressRefs":[]},"eb3b0811-8b84-4216-ae3e-ac2181935204":{"id":"eb3b0811-8b84-4216-ae3e-ac2181935204","doc_no":"A.2.8.2.2.1.1.4","title":"Moonbow Details","type":"Core","depth":6,"parentId":"a9f4941d-9d07-4191-a8c6-f1cb25a067cc","order":1920,"content":"The party ‘Moonbow’ is the entity owning relevant intellectual property.","contentHash":"82862b48b55fd712693d0532116a7a3969ca5cf3c0747274a5d7704d67f5e634","addressRefs":[]},"f68cf0ec-47bb-45d7-80a8-3b28f9e8dd1c":{"id":"f68cf0ec-47bb-45d7-80a8-3b28f9e8dd1c","doc_no":"A.2.8.2.2.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"a9f4941d-9d07-4191-a8c6-f1cb25a067cc","order":1921,"content":"The duration of Ecosystem Accord 2 is indefinite, commencing from May 29, 2025.","contentHash":"a954c5f5bc647d035f8c2f5922c9212b175188dfd26fe1c1dd5ad6fcd30f144f","addressRefs":[]},"ffb7dab9-a276-4968-ab49-f5783250120a":{"id":"ffb7dab9-a276-4968-ab49-f5783250120a","doc_no":"A.2.8.2.2.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"aa3b8e65-0ded-48c2-9c40-812debf99f32","order":1922,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 2.","contentHash":"408e7ab9d980e07a5ddd7928e0a0edd4f45481cdf62ac908fc574eb17e7653a7","addressRefs":[]},"ed0308bf-4a87-4c7c-b05e-3a4d46b68a13":{"id":"ed0308bf-4a87-4c7c-b05e-3a4d46b68a13","doc_no":"A.2.8.2.2.2.1","title":"Tokenomics","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1923,"content":"The subdocuments herein set out agreed terms with respect to tokenomics.","contentHash":"dcb147e8fc0ba02258422d7729ccb83e8bd2d14af13f185943ced65aa375b596","addressRefs":[]},"63684d7c-09f4-48ab-9daa-f3bb0aac6f28":{"id":"63684d7c-09f4-48ab-9daa-f3bb0aac6f28","doc_no":"A.2.8.2.2.2.1.1","title":"Total Token Supply","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1924,"content":"The total token supply of each of the SPK and GROVE tokens shall be 10,000,000,000 (ten billion).","contentHash":"280328413b165f0a790366537dd49e93613b88bf345611331b724c24b95a775a","addressRefs":[]},"cfac7e47-d20e-4b52-8d25-9ec418bd2c96":{"id":"cfac7e47-d20e-4b52-8d25-9ec418bd2c96","doc_no":"A.2.8.2.2.2.1.2","title":"Token Allocations","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1925,"content":"Specific token allocations are defined in the subdocuments herein.","contentHash":"b0d847a6d2e286865158a8f49dab0d048aef20c143d7df291601b4a2e3861aba","addressRefs":[]},"9d7a2d3f-3079-4d3b-be89-e06966aec07c":{"id":"9d7a2d3f-3079-4d3b-be89-e06966aec07c","doc_no":"A.2.8.2.2.2.1.2.1","title":"Grove Prime Treasury","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1926,"content":"3,000,000,000 GROVE tokens are allocated to the Grove Foundation, with an option to further increase this allocation by 5% (500,000,000 tokens). The additional 5% will be distributed to relevant stakeholders / users from Sky’s allocation of GROVE tokens, but that distribution will happen from the Grove Foundation. This distribution plan must be approved by Sky before the transfer.","contentHash":"aaf5e419f828adf3a02f66abeb3132d24e480621fd0d90e11fda7ce3f08a9c91","addressRefs":[]},"fb447af6-1581-4711-b73c-dc2e8d65e843":{"id":"fb447af6-1581-4711-b73c-dc2e8d65e843","doc_no":"A.2.8.2.2.2.1.2.2","title":"Sky Retained Tokens And Reward Pools","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1927,"content":"Sky retains 7,000,000,000 GROVE tokens and 6,500,000,000 SPK tokens. These tokens are distributed as token rewards over time as determined by Sky Governance.","contentHash":"458bb22a529ee160803fca3c1829308010dfc7168ee3619f6b6ff87797334382","addressRefs":[]},"5b43f4d8-9728-411c-92c7-a7ebaf368ca0":{"id":"5b43f4d8-9728-411c-92c7-a7ebaf368ca0","doc_no":"A.2.8.2.2.2.1.2.2.1","title":"Grove Token Reward Distribution Schedule","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1928,"content":"The distribution of GROVE tokens will be specified in a future iteration of the Atlas.","contentHash":"08fb77ac7d36d61451f7fa01434a6981443f21b719862b25f0c712958b2a20f1","addressRefs":[]},"1f412288-af14-4aab-84e9-79f2e0c39100":{"id":"1f412288-af14-4aab-84e9-79f2e0c39100","doc_no":"A.2.8.2.2.2.1.2.2.2","title":"Spark Token Reward Distribution Schedule","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1929,"content":"A portion of the SPK tokens held by Sky are distributed to USDS users as specified in the table below. All other SPK tokens held by Sky are reserved for future token rewards as determined by Sky Governance.\n\n| Year | Tokens for USDS Users  |\n|------|------------------------|\n| 1    | 1,137,500,000          |\n| 2    | 1,137,500,000          |\n| 3    | 568,750,000            |\n| 4    | 568,750,000            |\n| 5    | 284,375,000            |\n| 6    | 284,375,000            |\n| 7    | 142,187,500            |\n| 8    | 142,187,500            |\n| 9    | 142,187,500            |\n| 10   | 142,187,500            |\n| Total| 4,550,000,000          |","contentHash":"fcc9c961066c73271108e05e833c0c7c0bcf7e6651256da06446663e7651ad8e","addressRefs":[]},"da03bcb0-734a-4d36-ab0e-e42a43e23d8a":{"id":"da03bcb0-734a-4d36-ab0e-e42a43e23d8a","doc_no":"A.2.8.2.2.2.1.3","title":"Transfer Limit","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1930,"content":"Transfer limits for Spark and Grove are specified in the subdocuments herein.","contentHash":"d9c434be8eca5f5c8df252f0b88eaded2c5b3bfff61b2de35ab53ec26f97cbab","addressRefs":[]},"ce04d270-d9e1-46e2-9cfc-a122b03e923c":{"id":"ce04d270-d9e1-46e2-9cfc-a122b03e923c","doc_no":"A.2.8.2.2.2.1.3.1","title":"Spark Transfer Limit","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1931,"content":"A maximum of 1,000,000,000 tokens can be transferred by Spark to the Spark Foundation in the first year for the purpose of rewarding contributors, and 500,000,000 tokens per year thereafter for the purpose of rewarding contributors.","contentHash":"3e706d8d12f588303225463b41edf06ae273ad7d4db9adf3a141c32c3d9673bc","addressRefs":[]},"2a1c77ee-de95-415e-b93b-3505d3bd32d5":{"id":"2a1c77ee-de95-415e-b93b-3505d3bd32d5","doc_no":"A.2.8.2.2.2.1.3.2","title":"Grove Transfer Limit","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1932,"content":"Grove may transfer its contributor allocation, in whole or in part, to its operating entities, foundations, or affiliated entities in advance of contributor distribution. Tokens allocated for contributor compensation may be granted to contributors upfront, subject to vesting, forfeiture, and clawback arrangements that are consistent with the vesting schedules and distribution parameters set forth in this Atlas.\n\nA maximum of 1,000,000,000 tokens for Grove may vest or otherwise be released into circulation for contributor compensation purposes in the first year, and a maximum of 500,000,000 tokens per year for Grove may vest or otherwise be released into circulation thereafter. Tokens that are unvested or subject to forfeiture shall not be considered distributed, released, or in circulation.","contentHash":"525d32ad0176a347f4b04b0a5cc9e927f4a1c8967caeedaa7af41f80aca7fef8","addressRefs":[]},"c00b9dad-06d6-4e91-bfb2-7f5afa0bc47e":{"id":"c00b9dad-06d6-4e91-bfb2-7f5afa0bc47e","doc_no":"A.2.8.2.2.2.1.4","title":"Prime Token Generation Event","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1933,"content":"The respective Prime Foundations for Spark and Grove, or one of their subsidiaries or affiliate companies, will conduct the token generation event. In the token generation event, the Agent tokens will be split and sent to the Prime SubProxy and Sky Proxy. In this process, Sky will receive a universal override over the Prime Agent Token in question.","contentHash":"b7e02446d9af4bb1927a4ed181c8d8bb212e1170d4652716318fe70fe9d746c3","addressRefs":[]},"3918317d-50e8-4095-a0c6-22536291a6b5":{"id":"3918317d-50e8-4095-a0c6-22536291a6b5","doc_no":"A.2.8.2.2.2.1.5","title":"Minimum Float","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1934,"content":"For each of Spark and Grove, a minimum of 10% of the total token supply must be in circulation (float) within a year, and maintain that float afterward. If the float goes below the 10% threshold, the Prime Agent might have 1 natural year to get the float back to 10% or above. If the float falls below 10%, Sky will mint additional Prime Agent tokens until the 10% threshold is reached. Newly minted tokens would be farmed and the revenue from farming would be returned to the Prime Agent, net of a penalty for needing to trigger the minimum float.","contentHash":"f57b4b7e263c3aef5cb1f621146ec4d943c8570a9b8c2b5e494323b537006692","addressRefs":[]},"2c6034e7-d716-4d36-8063-d893c23fc34a":{"id":"2c6034e7-d716-4d36-8063-d893c23fc34a","doc_no":"A.2.8.2.2.2.2","title":"Borrowing Capacity And Mechanism","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1935,"content":"The subdocuments herein set out agreed terms with respect to borrowing capacity and the borrow rate mechanism.","contentHash":"733613b5eda5a2989359d0b6d34abf59b4d0900c00658ed38b1418330dceda78","addressRefs":[]},"552e7b01-c2d0-4658-ac49-2c74e230aeac":{"id":"552e7b01-c2d0-4658-ac49-2c74e230aeac","doc_no":"A.2.8.2.2.2.2.1","title":"Subsidized Borrowing","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1936,"content":"Both Spark and Grove are entitled to borrow up to 1,000,000,000 USDS from Sky at a subsidized rate for an initial period of 2 years, beginning January 1, 2026. This subsidized rate is set out in [A.2.8.2.2.2.2.2 - Borrow Rate Mechanism](f97cc4c7-d0d5-47fc-9f86-c00824ae6d7f).","contentHash":"9ceecfac9d48f76deb913c7c37c1f6ae9cdd687c7f790057e219e5a60d5e80c7","addressRefs":[]},"f97cc4c7-d0d5-47fc-9f86-c00824ae6d7f":{"id":"f97cc4c7-d0d5-47fc-9f86-c00824ae6d7f","doc_no":"A.2.8.2.2.2.2.2","title":"Borrow Rate Mechanism","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1937,"content":"The borrow rate subsidy for Spark and Grove will be calculated according to the formula: `t-bill_rate + ((base_rate - t-bill_rate) * T/24)`, where T represents elapsed months and is a counter that increases monthly over the 2-year period.","contentHash":"e0c0013dec54410e097f68e4a7f45a2f49b93468742e1e3d76d042a81d6574cc","addressRefs":[]},"fd39df25-6093-49ae-be12-36df34754612":{"id":"fd39df25-6093-49ae-be12-36df34754612","doc_no":"A.2.8.2.2.2.2.3","title":"Base Rate","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1938,"content":"The Base Rate will be dynamic and aligned with the SSR (Sky Savings Rate).","contentHash":"e22cab48466c07c433ce1d8cc4635da30c3b50fb5d4f5ee87a2210ce7893febc","addressRefs":[]},"23b21d6f-ad66-42ff-9e9f-c5bd5da6e8d4":{"id":"23b21d6f-ad66-42ff-9e9f-c5bd5da6e8d4","doc_no":"A.2.8.2.2.2.2.4","title":"Minimum Borrowing Threshold for Grant Eligibility","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1939,"content":"Primes, including Spark and Grove, must each maintain a minimum borrowing of 1,000,000,000 USDS from Sky at all times to remain eligible for the full monthly reimbursement grant. If the amount borrowed falls below this threshold, the reimbursement grant will be proportionately slashed. This grant will cover the difference between the borrowing Base Rate and the T-bill rate. Spark and Grove can borrow amounts exceeding the 1,000,000,000 USDS limit at the prevailing Base Rate.","contentHash":"61d06fc5b01a65cbd1d66b176383616ee2e263c71b14d7471414c018bfdcac4a","addressRefs":[]},"c04dcedd-5e17-412f-8a71-55a76c29b80d":{"id":"c04dcedd-5e17-412f-8a71-55a76c29b80d","doc_no":"A.2.8.2.2.2.2.5","title":"Borrowing Above Subsidized Limit","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1940,"content":"Spark and Grove can borrow amounts exceeding the 1,000,000,000 USDS limit at the prevailing Base Rate.","contentHash":"85484bf1013730ae152d8a7d97fec12aa7e2743b150aeebe17ba358651c3ca79","addressRefs":[]},"daf0ea35-23cb-4550-88f9-7da59027d262":{"id":"daf0ea35-23cb-4550-88f9-7da59027d262","doc_no":"A.2.8.2.2.2.2.6","title":"Recourse","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1941,"content":"Sky’s recourse for bad debt consists of (1) minting Prime Agent tokens; (2) terminating a Prime’s right to further borrowing; and (3) activation of the Resolution Mechanism which includes, without limitation, the authority to suspend all protocol operations, seize or reallocate all of the Prime assets, override or disable smart contract functions, initiate managed restructuring, or execute full and permanent liquidation of the affected sub-protocol and all of its assets, in order to contain risk and preserve the stability and solvency of the broader ecosystem.","contentHash":"a5930630a0f3007167f74f88d0c3ada1fee7846d909e76bdab899ef1168ec450","addressRefs":[]},"85b8e871-2d42-4a85-a887-c33d860bed64":{"id":"85b8e871-2d42-4a85-a887-c33d860bed64","doc_no":"A.2.8.2.2.2.3","title":"Distribution Reward","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1942,"content":"The subdocuments herein set out agreed terms with respect to the Distribution Reward.","contentHash":"431e54a9d406a86269ff6566fdaeb2b4fb7a2e8235f1919e9a98880ea8085ccd","addressRefs":[]},"8e3cde6b-3b8b-4e9a-b9a0-8c24d84881f6":{"id":"8e3cde6b-3b8b-4e9a-b9a0-8c24d84881f6","doc_no":"A.2.8.2.2.2.3.1","title":"Distribution Reward Rate","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1943,"content":"The standard Distribution Reward rate is set at 0.2%.","contentHash":"eb475b4b342ccc243105799a95c771079f00744a06d1859acb81e154ed730409","addressRefs":[]},"7ca440d3-03fb-4fba-81a8-d2118dc47aa6":{"id":"7ca440d3-03fb-4fba-81a8-d2118dc47aa6","doc_no":"A.2.8.2.2.2.3.2","title":"2025 Bonus","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1944,"content":"An additional 0.4% Distribution Reward bonus will apply during the calendar year 2025 (ending December 31, 2025). This bonus is strictly limited to the Prime and does not extend to the Prime Foundation. The bonus is subject to the limitation specified in [A.2.8.2.2.2.3.2.1 - Bonus Limitation](6996e6c9-b936-4680-855f-b9717572082d).","contentHash":"324f1dedce6d86dfbb852325b0cf31892399cbf5c553e2fb5391bb64cde8d033","addressRefs":[]},"6996e6c9-b936-4680-855f-b9717572082d":{"id":"6996e6c9-b936-4680-855f-b9717572082d","doc_no":"A.2.8.2.2.2.3.2.1","title":"Bonus Limitation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1945,"content":"USDS and sUSDS balances held by the Prime itself are not eligible for the Distribution Reward bonus specified in [A.2.8.2.2.2.3.2 - 2025 Bonus](7ca440d3-03fb-4fba-81a8-d2118dc47aa6).","contentHash":"f1c57b00a78cfbf5d5ac352fb21e3d6b5f51f9f7e0f5de6a6b79b08555bab588","addressRefs":[]},"5e3e9338-221a-461a-96f9-01e0665ab6a4":{"id":"5e3e9338-221a-461a-96f9-01e0665ab6a4","doc_no":"A.2.8.2.2.2.3.3","title":"Sky Spread","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1946,"content":"A fixed margin of 0.1% (Sky Spread) forms part of the overall differential between the Savings Rate and the Base Rate, representing the premium earned by Sky for facilitating the ecosystem’s financing. The total spread between the Savings Rate and the Base Rate is therefore 0.3%.","contentHash":"532c4748a4e822b586e75beebc37c07a826a681ed29f9abadba5e9abc7304522","addressRefs":[]},"23149a25-19a1-4d8f-b4ce-ea4b2adc2e21":{"id":"23149a25-19a1-4d8f-b4ce-ea4b2adc2e21","doc_no":"A.2.8.2.2.2.4","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1947,"content":"The subdocuments herein set out agreed terms with respect to genesis capital allocations.","contentHash":"0aa1fe2634c456da9296215ddf7ffc0ae608a27823c4d251ad0874691d64e60c","addressRefs":[]},"a339b1d7-34a9-40bd-b452-a86e149f07f7":{"id":"a339b1d7-34a9-40bd-b452-a86e149f07f7","doc_no":"A.2.8.2.2.2.4.1","title":"Spark Initial Allocation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1948,"content":"The Initial Allocation for Spark is 25,000,000 USDS.","contentHash":"fc051525983b6d62fc95ae1f7aaa38c77f4718469714eb0da9e125bc1a8fcbd5","addressRefs":[]},"062fdb39-464e-4a5b-a44f-3462d2d38be5":{"id":"062fdb39-464e-4a5b-a44f-3462d2d38be5","doc_no":"A.2.8.2.2.2.4.2","title":"Grove Initial Allocation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1949,"content":"The Initial Allocation for Grove is 25,000,000 USDS.","contentHash":"05c81153ab5d642a11228c29c429612560b3b044afd7dd4aa8d8b3adbc09345a","addressRefs":[]},"6b8fc0e6-ee0b-4a48-a096-2ccb06f64e3f":{"id":"6b8fc0e6-ee0b-4a48-a096-2ccb06f64e3f","doc_no":"A.2.8.2.2.2.4.3","title":"Initial Allocation Distribution","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1950,"content":"The Initial Allocation is distributed in USDS to each Prime SubProxy (i.e. the Spark SubProxy and Grove SubProxy). Both Grove and Spark elected to distribute 5% of the total token supply over a period of 20 years, lasting from year 10 to year 30, and will receive USDS 25,000,000 each.","contentHash":"3d8c77a0662a4dbcfe05827beb76d127611c8867f0c836082c130c9825b7b2c6","addressRefs":[]},"eedd0309-b11b-459e-a966-13b16e961ccc":{"id":"eedd0309-b11b-459e-a966-13b16e961ccc","doc_no":"A.2.8.2.2.2.4.4","title":"Initial Allocation Mechanism","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1951,"content":"Shortly after the Agent Token launch, an Atlas Edit Proposal submitted to Sky Governance will allow the respective founding teams of Spark and Grove to propose an initial cash grant to their respective Prime Foundation. Sky Governance must consent to this initial cash grant via approving the Sky Atlas modification.","contentHash":"41a161d4d5fdcd4d9e5de60d0d9541f6bd956c96f76fb27faeafee9eb768c83c","addressRefs":[]},"9daea2fa-0fef-48a7-8633-fa33081236da":{"id":"9daea2fa-0fef-48a7-8633-fa33081236da","doc_no":"A.2.8.2.2.2.4.4.1","title":"Initial Cash Grant To Spark Foundation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1952,"content":"The founding team of Spark has proposed a cash grant of 800,000 USDS per month to the Spark Foundation from Spark’s Genesis Capital Allocation for a three (3) month period, beginning at the time of the Genesis Capital Allocation. The purpose of the grant is to enable Spark Foundation to fulfill its purpose of promoting the growth and development of Spark. This funding will support essential activities such as engineering efforts, community engagement, research, infrastructure, and administrative operations.\n\nSky Governance hereby consents to this cash grant. The first month’s transfer must be made to the Spark Foundation immediately after the transfer of the Genesis Capital Allocation. See [A.2.8.2.2.2.7.2.1 - Transfer Of Genesis Capital Allocation To Spark SubProxy](e3ec99ec-54c9-4fe7-8104-aee20c57ec57). Transfers for subsequent months will be made proportionally in Spark Spells included in Sky Executive Votes unless otherwise agreed by Sky and Spark.","contentHash":"43f1c124e51fcb3a11d612550922c8656c435969caaaab07c27c27923eb84f5c","addressRefs":[]},"aea8a2d8-2203-4123-8c09-17b2bb8427c1":{"id":"aea8a2d8-2203-4123-8c09-17b2bb8427c1","doc_no":"A.2.8.2.2.2.4.5","title":"Subsequent Allocation Mechanism","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1953,"content":"After the initial cash grant (see [A.2.8.2.2.2.4.4 - Initial Allocation Mechanism](eedd0309-b11b-459e-a966-13b16e961ccc)), Spark and Grove may request additional grants to their respective Prime Foundations to fund operations and growth.\n\nThe authorization of grant requests is subject to the governance requirements and limitations specified in [A.2.2.5.2.3.1 - Limitations On Usage Of Root Edit Primitive Prior To Tokens Being Publicly Held](8c15762a-ea7e-4c6d-9089-60d30c219c0f).\n\nIn all instances, Sky Governance must consent to the transfer of funds via an Atlas Edit.","contentHash":"1e27b551318d20f5d678c5360400ad1ade8892aeda03e402c784b0dfe593d634","addressRefs":[]},"6a9a3a7a-8670-41fc-98aa-d2d9b518bdfc":{"id":"6a9a3a7a-8670-41fc-98aa-d2d9b518bdfc","doc_no":"A.2.8.2.2.2.4.5.1","title":"Spark Foundation Grant Authorizations","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1954,"content":"The documents herein record Sky Governance authorizations for grants to the Spark Foundation.","contentHash":"c5b9b4dfdb46845de60acc935fb91a5276b2024c5f1ade630e0062fa1a709609","addressRefs":[]},"12425328-8344-4fbd-9afb-3ea6316972dd":{"id":"12425328-8344-4fbd-9afb-3ea6316972dd","doc_no":"A.2.8.2.2.2.4.5.1.1","title":"Spark Foundation Grant Authorization: October 2025","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1955,"content":"The founding team of Spark has proposed a cash grant of 1,100,000 USDS per month to the Spark Foundation from Spark’s Prime Treasury for a three (3) month period, beginning on October 1, 2025. The purpose of this grant is to enable the Spark Foundation to fulfill its purpose of promoting the growth and development of Spark. This funding will support essential activities such as engineering and product development, community engagement and growth initiatives, research and governance contributions, infrastructure and operational maintenance, and administrative operations.\n\nSky Governance hereby consents to this cash grant. The transfer for October must be made to the Spark Foundation in a Spark Spell included in the October 2, 2025 Executive Vote. Transfers for subsequent months will be made proportionally in Spark Spells included in Sky Executive Votes unless otherwise agreed by Sky and Spark.","contentHash":"cb2980a0e8adfa554057d6e9182e44bcc9e232ff5978a22e418ae3d6cf400f25","addressRefs":[]},"bd9673db-225e-42f4-8f26-6e993dc72bd0":{"id":"bd9673db-225e-42f4-8f26-6e993dc72bd0","doc_no":"A.2.8.2.2.2.4.5.1.2","title":"Spark Foundation Grant Authorization: December 2025","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1956,"content":"The founding team of Spark has proposed a cash grant of 1,100,000 USDS per month to the Spark Foundation from Spark's Prime Treasury for a three (3) month period to cover Q1 2026 Foundation expenses. Additionally, a one-time grant of 150,000 USDS has been proposed to cover expenses for Spark Asset Foundation for Q1 2026 (see [https://forum.skyeco.com/t/december-11-2025-proposed-changes-to-spark-for-upcoming-spell/27481](https://forum.skyeco.com/t/december-11-2025-proposed-changes-to-spark-for-upcoming-spell/27481)).\n\nSky Governance hereby consents to these grants and authorizes the execution of the associated funding payloads as specified in the referenced proposal.","contentHash":"9e8d63620a43b72e521a6ae69355255bd23253516ace3fe55e4839d7a3e45d5d","addressRefs":[]},"b69158da-476a-4d4b-b7ef-2f8b96b73d23":{"id":"b69158da-476a-4d4b-b7ef-2f8b96b73d23","doc_no":"A.2.8.2.2.2.4.5.1.3","title":"Spark Foundation Grant Authorization: Q2 2026","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1957,"content":"The founding team of Spark has proposed a cash grant of 1,100,000 USDS per month to the Spark Foundation from Spark's Prime Treasury for a three (3) month period to cover Q2 2026 Spark Foundation expenses. Additionally, a grant of 100,000 USDS per month to the Spark Asset Foundation from Spark's Prime Treasury for a three (3) month period to cover Q2 2026 Spark Asset Foundation expenses (see [https://forum.skyeco.com/t/march-26-2026-proposed-changes-to-spark-for-upcoming-spell/27770](https://forum.skyeco.com/t/march-26-2026-proposed-changes-to-spark-for-upcoming-spell/27770)).\n\nSky Governance hereby consents to these grants and authorizes the execution of the associated funding payloads as specified in the referenced proposal.","contentHash":"7ad1eab3ee41762cbb9c00ce9966807d696b209aea73f293a410717e2b28a7d3","addressRefs":[]},"db86fa15-45c6-4a44-9c2a-652fd3d227b0":{"id":"db86fa15-45c6-4a44-9c2a-652fd3d227b0","doc_no":"A.2.8.2.2.2.4.5.2","title":"Grove Foundation Grant Authorizations","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1958,"content":"The documents herein record Sky Governance authorizations for grants to the Grove Foundation.","contentHash":"78dedbe5a4ca544477f98e94322373093162b10c1ace265f1ed56e778437f70e","addressRefs":[]},"85f7d545-d56c-40b9-b1b4-05663cd7772a":{"id":"85f7d545-d56c-40b9-b1b4-05663cd7772a","doc_no":"A.2.8.2.2.2.4.5.2.1","title":"Grove Foundation Grant Authorization: Q2 2026","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1959,"content":"The founding team of Grove has proposed a cash grant of 800,000 USDS per month to the Grove Foundation from Grove's Prime Treasury for a three (3) month period, beginning on April 1, 2026. The purpose of this grant is to enable the Grove Foundation to fulfill its purpose of promoting the growth and development of Grove. This funding will support essential activities such as engineering and product development, community engagement and growth initiatives, research and governance contributions, infrastructure and operational maintenance, and administrative operations.\n\nSky Governance hereby consents to this grant and authorizes the execution of the associated funding payloads. Transfers must be made to the Grove Foundation at `0xE3EC4CC359E68c9dCE15Bf667b1aD37Df54a5a42` in Grove Spells included in Sky Executive Votes unless otherwise agreed by Sky and Grove.","contentHash":"58e027e83cb90bff6a662da17172e6a301f7d89baea15f80d2bfc4bf6b90a0eb","addressRefs":["0xe3ec4cc359e68c9dce15bf667b1ad37df54a5a42"]},"20e8467f-561c-4020-bd26-e6c1601fb64d":{"id":"20e8467f-561c-4020-bd26-e6c1601fb64d","doc_no":"A.2.8.2.2.2.4.6","title":"Genesis Capital Backstop","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1960,"content":"Each genesis capital allocation is subject to the Genesis Capital Backstop (see [A.3.7.1.6 - Genesis Capital Backstop](a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98)).","contentHash":"37dcc9da7e4e5a6eb57265f91e055e910a5e3a3263f6cd3cbdaa3ff73d053864","addressRefs":[]},"d276499a-2447-4dfb-a62b-4212c3d4b071":{"id":"d276499a-2447-4dfb-a62b-4212c3d4b071","doc_no":"A.2.8.2.2.2.5","title":"Intellectual Property","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1961,"content":"The subdocuments herein set out agreed terms with respect to intellectual property.","contentHash":"705b84142b49ac826b70efd1779716a373effb6c212c71367d1944bbb43124e4","addressRefs":[]},"bfd79c66-ba55-46d2-a844-eaf8ef44d6d7":{"id":"bfd79c66-ba55-46d2-a844-eaf8ef44d6d7","doc_no":"A.2.8.2.2.2.5.1","title":"License Agreements","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1962,"content":"Each Prime Foundation (i.e. the Spark Foundation and Grove Foundation) must sign a license agreement with Moonbow for all relevant intellectual property. This license agreement must contain the following terms:\n\n- Worldwide, commercial, exclusive license, revocable for material breach (immediate revocation in severe cases, 30-day notice for non-severe cases).\n- Royalty-free.\n- Perpetual term, subject to termination provisions.\n- Sublicensing allowed in specified cases without approval; any other sublicenses allowed only with Moonbow's explicit approval (not to be unreasonably withheld).\n- Licensee responsible for IP protection and enforcement; license agreement to define specific requirements.\n- Quarterly/annual reporting requirements on fraud cases and brand protection actions.\n- Moonbow's right to audit (at Moonbow's cost).\n- All improvements/developments belong to Moonbow.\n- Monetary penalties for IP violations shall be explicitly defined in the full licensing agreement, with specific thresholds for triggering penalties to be mutually agreed and stipulated therein.\n- Customary mutual indemnification and limitation of liability provisions.\n- Mandatory arbitration except in case of injunctive relief.\n- Other customary terms, conditions, representations and warranties.","contentHash":"9882d9bbefa29d8f4bc02037a04ff8dd5c659b7586de6140bfe8f82f3558d53b","addressRefs":[]},"fa90cec7-7b65-4798-a376-00cd8454bc0c":{"id":"fa90cec7-7b65-4798-a376-00cd8454bc0c","doc_no":"A.2.8.2.2.2.5.2","title":"Open Source Protocol Code","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1963,"content":"All components of code that form part of the Prime Protocols (i.e. Spark and Grove) will be open source.","contentHash":"f24fc1396bf5227ae8de3160f08b0decc1f9eca0f8172942e761da54ff526197","addressRefs":[]},"eb550b0a-3ffc-4a86-b8fe-9cc1f60f2a7e":{"id":"eb550b0a-3ffc-4a86-b8fe-9cc1f60f2a7e","doc_no":"A.2.8.2.2.2.5.3","title":"Financial Strategies","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1964,"content":"The financial strategies implemented by the Prime Foundations (i.e. the Spark Foundation and Grove Foundation) will be closed source. Operational specifics are further defined in the subdocuments herein.","contentHash":"e49be29533c4aa77d7bfb4584c66a6128ec8ee7573a254d0fc8117aa148d530e","addressRefs":[]},"ec0b206a-bf87-4ca8-aa7f-aa4ca1bc80f8":{"id":"ec0b206a-bf87-4ca8-aa7f-aa4ca1bc80f8","doc_no":"A.2.8.2.2.2.5.3.1","title":"Role Of Prime Foundation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1965,"content":"The Prime Foundation (i.e. the Spark Foundation and Grove Foundation) will retain ownership of the code and strategies that determine how capital is allocated for its Prime. They will contract with the Development Company for the development and execution of the strategies.","contentHash":"e0cb7df7905627c46420ea74b9645ef8f83a693cb75cbc20d7f9a799f392c83b","addressRefs":[]},"d88e4c91-cce4-4f95-a989-ea876ccdf99b":{"id":"d88e4c91-cce4-4f95-a989-ea876ccdf99b","doc_no":"A.2.8.2.2.2.5.3.2","title":"Role Of Development Company","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1966,"content":"The Development Company for each Prime Agent will execute the strategy and relay the results to the Operational Executor Agent.","contentHash":"acdd86818c165dccb2e94d76bc3b6136a8f066a0ad35322baa039a86667ea943","addressRefs":[]},"b0fc4a02-f41c-4556-b3f5-84d262ca00f2":{"id":"b0fc4a02-f41c-4556-b3f5-84d262ca00f2","doc_no":"A.2.8.2.2.2.5.3.3","title":"Role Of Operational Executor Agent","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1967,"content":"The relevant Operational Executor Agent, which is already engaged to the Prime in question, will conduct a principled compatibility analysis to ensure the strategy aligns with the Sky Atlas and the relevant Prime Artifact. Once validated, the Operational Executor Agent executes the capital allocation in question.","contentHash":"bca912048bb034f1c4349475610da0929fa8ad5ce21f86d5656ebb5a563b9911","addressRefs":[]},"63717bcd-4696-4104-a368-eac839a7ba2b":{"id":"63717bcd-4696-4104-a368-eac839a7ba2b","doc_no":"A.2.8.2.2.2.5.3.4","title":"Prime Tokenholder Governance Rights","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1968,"content":"To ensure accountability, Prime token holders will retain governance rights, including the ability to revoke the Operational Executor Agent’s Executor Accord through a vote if necessary.","contentHash":"2f92b99d7f57d1d86eff661d37a9ef6c1e02448a3a9ef99d56e0c3eef5281a85","addressRefs":[]},"63922aed-a1e4-43f2-a4a7-437b80ea6711":{"id":"63922aed-a1e4-43f2-a4a7-437b80ea6711","doc_no":"A.2.8.2.2.2.6","title":"Peg Stability Module Management And Ownership","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1969,"content":"The subdocuments herein set out agreed terms with respect to the Peg Stability Module (PSM).","contentHash":"b8cf8491176824dc987e831a7674bde0580e582a07b5dab6bb97bbcce062bbcb","addressRefs":[]},"b66f99ce-af91-4b32-a37a-fb26d16b57c4":{"id":"b66f99ce-af91-4b32-a37a-fb26d16b57c4","doc_no":"A.2.8.2.2.2.6.1","title":"Current and Future Control","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1970,"content":"The subdocuments herein set out details about the current control and oversight of the PSM, including the transition to ownership by Grove.","contentHash":"da0230c98121a052ae8aaafccef85807cedd0d8494a48aaf1140f905f427ff44","addressRefs":[]},"815fc554-c019-49b1-8b97-9eb62082cb5b":{"id":"815fc554-c019-49b1-8b97-9eb62082cb5b","doc_no":"A.2.8.2.2.2.6.1.1","title":"Current Control (Until 2026)","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1971,"content":"The Peg Stability Module (PSM) remains directly managed and controlled by Sky until the full deployment and operationalization of the Actively Stabilizing Collateral (ASC) system. Sky retains responsibility for setting debt ceilings, determining liquidity levels, and overseeing asset management activities within the PSM during this period.","contentHash":"9c0b2d08626c24e1f2332c393f8d8f38ea64e26cdcdc8cbbac4c873d01a23fc3","addressRefs":[]},"08896aa0-140a-4289-9027-1772a0109a35":{"id":"08896aa0-140a-4289-9027-1772a0109a35","doc_no":"A.2.8.2.2.2.6.1.2","title":"Transition to Grove (2025)","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1972,"content":"Beginning in 2025, Grove shall assume operational and accounting ownership of the PSM, incorporating the PSM’s assets into its total value locked (TVL). Sky maintains active oversight and retains final control over strategic and operational decision-making within the PSM until full ASC implementation occurs.","contentHash":"2dd1a7983ade3d7b96bfa2bb81fb2f0028f603a46db5fa3558b3031bd37ec403","addressRefs":[]},"704ccd85-e80e-478f-ab73-23d775968ca7":{"id":"704ccd85-e80e-478f-ab73-23d775968ca7","doc_no":"A.2.8.2.2.2.6.2","title":"Operational Responsibilities","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1973,"content":"The subdocuments herein set out details about operational responsibilities relating to the PSM.","contentHash":"bc0748652c04f5fdd207d940cdac59c58ca8a4ef0de44e35f3b1e0f9258a5d09","addressRefs":[]},"ff46baec-15da-4bf7-be18-e145f1809cf6":{"id":"ff46baec-15da-4bf7-be18-e145f1809cf6","doc_no":"A.2.8.2.2.2.6.2.1","title":"Base Rate Obligation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1974,"content":"Grove will be required to pay the Base Rate on all assets within the PSM. The Base Rate is dynamic and will align with the SSR (Sky Savings Rate), expected to fluctuate between the Aave and Ethena rates. See [A.2.8.2.2.2.2.3 - Base Rate](fd39df25-6093-49ae-be12-36df34754612).","contentHash":"866264dec7ed730fc57273ed3a48bf7bbda21d286b8209a0877180d4d7a1f3f1","addressRefs":[]},"223a695c-addd-443a-bfed-b136eeb2eddc":{"id":"223a695c-addd-443a-bfed-b136eeb2eddc","doc_no":"A.2.8.2.2.2.6.2.2","title":"Yield on USDC","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1975,"content":"Grove shall earn yield through Coinbase Custody on USDC holdings within the PSM, enabling potential positive carry depending upon the spread between custody yield and the Base Rate.","contentHash":"e3b559a39363144829c672d8e6f55fdf8f5394e2d6088ccfd4f9324986ad9f78","addressRefs":[]},"b1831dee-c95f-4872-98e0-2e49f3591bf9":{"id":"b1831dee-c95f-4872-98e0-2e49f3591bf9","doc_no":"A.2.8.2.2.2.6.2.3","title":"Economic Rationale","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1976,"content":"Grove will pay the Base Rate on the PSM for the purpose of meeting ASC requirements, if there are no better alternatives available. Unlike other alternatives, USDC in the PSM will have no capital requirement. If other, better options for ASC are available, Grove should empty the PSM and allocate the assets to those options. It is anticipated that other protocols will also be willing to rent ASC \"points\", potentially allowing for the management of ASC needs across several Prime Agents for a profit.","contentHash":"85e0f7b7ce340407674643b29427daf01947c5ae21ddd26bdf4bd08d266491a7","addressRefs":[]},"1a26a561-1f03-4d83-81df-3dedc9688597":{"id":"1a26a561-1f03-4d83-81df-3dedc9688597","doc_no":"A.2.8.2.2.2.6.3","title":"Future Transition and Long-Term Vision","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1977,"content":"The subdocuments herein set out agreed terms with respect to the future transition and long-term vision for the PSM.","contentHash":"adf6f40a53a3015ac3b413e23056fbea55ccaa70ed7fa1997213ed1cdf8a14a8","addressRefs":[]},"54bd8ca5-d078-4b1e-9f0a-e843fe13e5c0":{"id":"54bd8ca5-d078-4b1e-9f0a-e843fe13e5c0","doc_no":"A.2.8.2.2.2.6.3.1","title":"Short Term (2025-2026)","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1978,"content":"The PSM will remain a central liquidity hub for stablecoin deployment. Grove will manage the PSM, paying the Base Rate while earning USDC yield, under Sky oversight until full ASC implementation. PSM assets will count toward Grove's TVL, enhancing its economic standing and collateral efficiency.","contentHash":"734b6ba203f5aa949db5fa7268b3b6ea8467f271a8c0ded7634aab89fcabd655","addressRefs":[]},"4478d3b2-f8bc-400f-b6da-3bb43684e94d":{"id":"4478d3b2-f8bc-400f-b6da-3bb43684e94d","doc_no":"A.2.8.2.2.2.6.3.2","title":"Long Term (Post-2026)","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1979,"content":"The PSM's role will diminish as the ASC system becomes the primary liquidity management tool. Grove can wind down the PSM entirely if ASC requirements are fulfilled through other mechanisms (e.g., Uniswap positions, Curve pools). If ASC obligations rise significantly, PSM usage will increase, but as the system matures, its relevance will gradually decline.","contentHash":"64df328af5c39654cda1607f69999426d46585220d489671b46a548f30cd9bf2","addressRefs":[]},"3215686b-a770-484d-9602-6ee9d84c0e44":{"id":"3215686b-a770-484d-9602-6ee9d84c0e44","doc_no":"A.2.8.2.2.2.6.4","title":"Implications for Grove","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1980,"content":"The subdocuments herein set out implications of the PSM terms with respect to Grove.","contentHash":"560c89f33ce976053fa2f4db2230d92312a9087659c9a3846424957fc583be6f","addressRefs":[]},"9ed13fe5-7b07-4222-93ff-640880a976e2":{"id":"9ed13fe5-7b07-4222-93ff-640880a976e2","doc_no":"A.2.8.2.2.2.6.4.1","title":"Positive Carry And Liquidity Balancing","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1981,"content":"Grove can generate positive carry if the USDC yield exceeds the Base Rate. If the Base Rate rises significantly, the PSM may become costly, requiring liquidity balancing.","contentHash":"908bf80a0a8a92aed4a51b4aae87e2fba5decf53a98c0f4dd10b39a050453d21","addressRefs":[]},"207d4658-b6f4-4937-853c-b5d23cff3c89":{"id":"207d4658-b6f4-4937-853c-b5d23cff3c89","doc_no":"A.2.8.2.2.2.6.4.2","title":"Capital Efficiency","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1982,"content":"Grove can deploy USDC in high-yield strategies while retaining enough ASC to meet requirements. Aave USDC (aUSDC) and Curve LP positions are likely alternatives to direct PSM usage, albeit potentially with higher JRC requirements.","contentHash":"d4bba07a6869f10f2c1cac1c6ee6e00d21bc097beb0e9858c06dbd3e230efdd0","addressRefs":[]},"00aa264d-4fe6-41a1-91ea-014a2a520001":{"id":"00aa264d-4fe6-41a1-91ea-014a2a520001","doc_no":"A.2.8.2.2.2.6.4.3","title":"Risk Management","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1983,"content":"The PSM serves as a capital buffer, enabling Grove to scale liquidity massively without additional credit enhancement. As ASC obligations fluctuate, the PSM will act as a dynamic backstop, ensuring resilience during periods of high demand.","contentHash":"318f258f81cf312194599e49e57987299f15043fd471317dd2f4d65d90991d0b","addressRefs":[]},"2df67c30-1644-4455-a3e4-f3047c4c49ae":{"id":"2df67c30-1644-4455-a3e4-f3047c4c49ae","doc_no":"A.2.8.2.2.2.7","title":"Token Launch Penalty, Capital Transfer, And Income Generation","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1984,"content":"The subdocuments herein set out agreed terms with respect to a token launch penalty, capital transfer, and income generation.","contentHash":"ca1a57ef9bb670988c1cd1a8230e57c5cc28bbcc5d6b5cd4bcb621fb81cb9eb3","addressRefs":[]},"5a62cc3f-4337-4770-a4d1-8a9b3d158b3f":{"id":"5a62cc3f-4337-4770-a4d1-8a9b3d158b3f","doc_no":"A.2.8.2.2.2.7.1","title":"Token Launch Penalty","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1985,"content":"If either Spark or Grove (each, a \"Prime\") does not complete its Prime Token Generation Event (see [A.2.8.2.2.2.7.1.1 - Prime Token Generation Event](fb80d94d-dd93-40ae-bb4c-8300c1c53d73)) by July 1, 2025, a penalty of thirty percent (30%) will apply. This penalty will be calculated on the income (as defined in [A.2.8.2.2.2.7.6 - Income Definition](fa48f7be-3c7d-4390-8b39-4fdfe9aa06ae)) the Prime is receiving or is meant to receive (including revenue that has accrued but has not been transferred) until the TGE occurs.\n\nThe penalty shall be paid as specified in [A.2.8.2.2.2.7.1.2 - Token Launch Penalty Settlement](c680762a-a3f9-46bf-b740-9029b8a97e2b).","contentHash":"757249dd61e7dab82943942d82949a5a0a83b877828c569826503343bb418f0c","addressRefs":[]},"fb80d94d-dd93-40ae-bb4c-8300c1c53d73":{"id":"fb80d94d-dd93-40ae-bb4c-8300c1c53d73","doc_no":"A.2.8.2.2.2.7.1.1","title":"Prime Token Generation Event","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1986,"content":"The documents herein define a Prime Token Generation Event (\"TGE\") for Spark and Grove.","contentHash":"790aa944d62476e014f7629197a63840b1377721fdc18d52cc583bcae337886f","addressRefs":[]},"d703336e-b86f-4e50-99f0-f4a8dff1d0f7":{"id":"d703336e-b86f-4e50-99f0-f4a8dff1d0f7","doc_no":"A.2.8.2.2.2.7.1.1.1","title":"Spark Token Generation Event","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1987,"content":"The Spark Token Generation Event occurred on June 17, 2025.","contentHash":"b2dfcfdc8c60beb5d0d72a76a24bdd4ae9549445980c9e2d53ae962d35a1ab52","addressRefs":[]},"a69d2ed5-90ea-4d6b-ba6e-287a104017d2":{"id":"a69d2ed5-90ea-4d6b-ba6e-287a104017d2","doc_no":"A.2.8.2.2.2.7.1.1.2","title":"Grove Token Generation Event","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1988,"content":"The Grove Token Generation Event will occur on the first date that SKY Staking users are able to earn GROVE Token Rewards. See [A.4.4.1 - SKY Staking](626bd71c-b413-41b7-a5fe-39fd0d43dbf5).","contentHash":"9c676c36d259d23bf23794e8b076cf4b0b4964d159a09960a3303b44f22f15e2","addressRefs":[]},"c680762a-a3f9-46bf-b740-9029b8a97e2b":{"id":"c680762a-a3f9-46bf-b740-9029b8a97e2b","doc_no":"A.2.8.2.2.2.7.1.2","title":"Token Launch Penalty Settlement","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1989,"content":"The Token Launch Penalty will be paid by each Prime at the time of the last Capital Transfer to a Genesis Agent (the \"Token Launch Penalty Settlement Date\") as specified in the documents herein.","contentHash":"72d9997287f8233e4ef068365ab8161b9e8291f2059ed8aa76f2afcea4e007fa","addressRefs":[]},"66269cb6-0828-4977-b9d4-16840c6bc97d":{"id":"66269cb6-0828-4977-b9d4-16840c6bc97d","doc_no":"A.2.8.2.2.2.7.1.2.1","title":"Token Launch Penalty Settlement Date","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1990,"content":"When the Core Council determines the date of the last Capital Transfer to a Genesis Agent, it must submit an Atlas Edit Proposal to record the date in this document.","contentHash":"df275b0997bea4eee2d1d454b7eda5844bdfbf909f025deef6b01f2d3661577f","addressRefs":[]},"4c8a37f9-717d-437c-9f38-d17cbb3b3639":{"id":"4c8a37f9-717d-437c-9f38-d17cbb3b3639","doc_no":"A.2.8.2.2.2.7.1.2.2","title":"Token Launch Penalty Settlement Mechanism","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1991,"content":"The settlement mechanism for the Token Launch Penalty, including the calculation of the penalty for each Prime and how the calculated balance is paid to Sky, will be included in a future iteration of the Atlas.","contentHash":"929d217cff8bea85efc9db7025dfdbbc501002ab9563bc5af72490525ecd7db0","addressRefs":[]},"760c4258-50f7-4334-af21-888759194e64":{"id":"760c4258-50f7-4334-af21-888759194e64","doc_no":"A.2.8.2.2.2.7.2","title":"Transfer Of Capital Funds","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1992,"content":"The transfer of the Genesis Capital Allocation to each Prime SubProxy (i.e. the Spark SubProxy and Grove SubProxy) shall occur once funding from the Surplus Buffer is approved. This condition ensures that capital deployment is aligned with the successful launch of the Prime's token and the commencement of its independent operations.","contentHash":"43f6447c6b54148ce92962aedb2ecc18511db785dd6a30e55e1732713dc09560","addressRefs":[]},"e3ec99ec-54c9-4fe7-8104-aee20c57ec57":{"id":"e3ec99ec-54c9-4fe7-8104-aee20c57ec57","doc_no":"A.2.8.2.2.2.7.2.1","title":"Transfer Of Genesis Capital Allocation To Spark SubProxy","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1993,"content":"The transfer of 20.6 million USDS from the Surplus Buffer to the Spark SubProxy for the Genesis Capital Allocation must be included in the June 26, 2025 Executive Vote. This action is authorized to proceed directly to an Executive Vote without a prior Governance Poll.\n\nThis amount reflects that 4.4 million USDS of pre-TGE expenses were paid by Sky as specified in [A.2.8.2.2.2.7.4 - Treatment of Expenses Paid By Sky Pre-TGE](f3672ca1-b305-4e16-86f0-3dc3267073bb). This includes 2 million USDS transferred from the Sky Ecosystem Liquidity Bootstrapping Budget to Spark to provide liquidity to market makers and 2.4 million USDS transferred from the Ecosystem Liquidity Bootstrapping Budget to Spark to provide liquidity to exchanges. See [A.2.8.2.2.2.7.4.1 - Transfer From Liquidity Bootstrapping Budget To Spark For Market Makers](66abd123-f5cd-4d1a-bf75-2e5f468eae16) and [A.2.8.2.2.2.7.4.2 - Transfer From Liquidity Bootstrapping Budget To Spark For Exchanges](1d7924cd-8105-458f-a959-92f302b971d4).\n\nNo penalties were applied under [A.2.8.2.2.2.7.1 - Token Launch Penalty](5a62cc3f-4337-4770-a4d1-8a9b3d158b3f).","contentHash":"5c5b92ea4b56d36b76cec3aafa122cacbc6c1c8b04c3b5f814715ba875ea4466","addressRefs":[]},"91c1a218-ea12-4b75-ad71-efc4d1060e58":{"id":"91c1a218-ea12-4b75-ad71-efc4d1060e58","doc_no":"A.2.8.2.2.2.7.3","title":"Cessation Of MKR and SKY Token Flow","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1994,"content":"Upon the commencement of Income Generation (as defined in [A.2.8.2.2.2.7.6 - Income Definition](fa48f7be-3c7d-4390-8b39-4fdfe9aa06ae)) by a Prime, any existing or previously agreed-upon allocation or distribution of MKR or SKY tokens from Sky to that Prime shall immediately cease. The intent is for the Primes to transition to financial self-sufficiency upon the initiation of their respective income-generating activities. Furthermore, any token vesting to the Prime Foundation will be reduced by 50% until the TGE occurs. Prior to the TGE, Primes agree to share with Sky the Prime Agent Token vesting schedules and lock-ups for their teams to ensure they align with the principles of long-term commitment to the Prime.","contentHash":"b8754de1ea6c2e076715c5163718c70b7f2d1c0a78be0135a44712fc741dcafd","addressRefs":[]},"f3672ca1-b305-4e16-86f0-3dc3267073bb":{"id":"f3672ca1-b305-4e16-86f0-3dc3267073bb","doc_no":"A.2.8.2.2.2.7.4","title":"Treatment of Expenses Paid By Sky Pre-TGE","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1995,"content":"Any operational or other expenses incurred by a Prime and paid directly by Sky after July 1, 2025 shall be treated as an advance against the Prime’s Genesis Capital Allocation. The total amount of such expenses shall be documented and shall be deducted from the Prime’s allocated capital funds at the time of the Capital Transfer (as outlined in [A.2.8.2.2.2.7.2 - Transfer Of Capital Funds](760c4258-50f7-4334-af21-888759194e64)).","contentHash":"6851c501822f69110965be94c7920f99fbf547a8e8a1d73781f9edea71098427","addressRefs":[]},"66abd123-f5cd-4d1a-bf75-2e5f468eae16":{"id":"66abd123-f5cd-4d1a-bf75-2e5f468eae16","doc_no":"A.2.8.2.2.2.7.4.1","title":"Transfer From Liquidity Bootstrapping Budget To Spark For Market Makers","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1996,"content":"Sky has transferred 2 million USDS from the Sky Ecosystem Liquidity Bootstrapping Budget to Spark to provide liquidity to market makers. This amount shall be treated as an advance against Spark’s Genesis Capital Allocation and deducted from Spark’s allocated capital funds at the time of the Capital Transfer.","contentHash":"7fe46d3fe83258cd2205cce2a9ba07306e9e614b1cf832e1449d5f479a42651a","addressRefs":[]},"1d7924cd-8105-458f-a959-92f302b971d4":{"id":"1d7924cd-8105-458f-a959-92f302b971d4","doc_no":"A.2.8.2.2.2.7.4.2","title":"Transfer From Liquidity Bootstrapping Budget To Spark For Exchanges","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1997,"content":"Sky has transferred 2.4 million USDS from the Sky Ecosystem Liquidity Bootstrapping Budget to Spark to provide liquidity to exchanges. This amount shall be treated as an advance against Spark’s Genesis Capital Allocation and deducted from Spark’s allocated capital funds at the time of the Capital Transfer.","contentHash":"b5db56a1051ce952351e1d2fa715f72f2995f87026bb3f1ddd7b87d34a5e74dc","addressRefs":[]},"3ae9fa89-97e6-46ac-9b8b-ecb77a10574f":{"id":"3ae9fa89-97e6-46ac-9b8b-ecb77a10574f","doc_no":"A.2.8.2.2.2.7.5","title":"Income Generation And Pre-TGE Credit","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1998,"content":"\"Income Generation\" shall be deemed to commence on July 1, 2025. From that date until the Prime’s TGE, seventy percent (70%) of any income generated by the Prime’s activities shall be credited to its capital account (net of any expenses paid by Sky as per [A.2.8.2.2.2.7.4 - Treatment of Expenses Paid By Sky Pre-TGE](f3672ca1-b305-4e16-86f0-3dc3267073bb)), subject to any penalties.","contentHash":"b2f00d1b32bba937912cd7653fe91b127d69f6c1ee05fa2e6394ad22e22ec115","addressRefs":[]},"fa48f7be-3c7d-4390-8b39-4fdfe9aa06ae":{"id":"fa48f7be-3c7d-4390-8b39-4fdfe9aa06ae","doc_no":"A.2.8.2.2.2.7.6","title":"Income Definition","type":"Core","depth":6,"parentId":"ffb7dab9-a276-4968-ab49-f5783250120a","order":1999,"content":"\"Income\" means all revenues or fees received or accrued by the applicable Prime after July 1, 2025, including: (i) Distribution Rewards (see [A.2.8.2.2.2.3.1 - Distribution Reward Rate](8e3cde6b-3b8b-4e9a-b9a0-8c24d84881f6)), (ii) Distribution Reward Bonus for 2025 (see [A.2.8.2.2.2.3.2 - 2025 Bonus](7ca440d3-03fb-4fba-81a8-d2118dc47aa6)), (iii) any Platform Fees charged to users, and (iv) Real World Asset fees charged to users, including any origination, servicing, or related charges, and (v) the blended cost of allocation spread between Junior and Senior Risk Capital.","contentHash":"cf6aa6b922e1561c5b68c8e70d4d2ae2551f4a7605ae9f58184f10dca9ea9461","addressRefs":[]},"63a88b08-e6cd-48bf-9cec-64ce7e42ae0e":{"id":"63a88b08-e6cd-48bf-9cec-64ce7e42ae0e","doc_no":"A.2.8.2.3","title":"Ecosystem Accord 3: Sky And Keel","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2000,"content":"The subdocuments herein record the terms of agreement between Sky and Keel as agreed in Ecosystem Accord 3.","contentHash":"a9b05bc3b168120e798fa9c198497085608bd0470c083f2cbf2831e14a760f97","addressRefs":[]},"40a876f3-e0bb-4bdf-a980-ffa38d9f46d7":{"id":"40a876f3-e0bb-4bdf-a980-ffa38d9f46d7","doc_no":"A.2.8.2.3.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"63a88b08-e6cd-48bf-9cec-64ce7e42ae0e","order":2001,"content":"The subdocuments herein set out the key details of Ecosystem Accord 3, such as parties to the agreement and the duration of the Accord.","contentHash":"858fdd5290f1edf9494c94a0855bfda44b5ef4f9669bb3a6b02858d552e905ed","addressRefs":[]},"0577460f-3f87-44ea-b39b-a614e7507338":{"id":"0577460f-3f87-44ea-b39b-a614e7507338","doc_no":"A.2.8.2.3.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"40a876f3-e0bb-4bdf-a980-ffa38d9f46d7","order":2002,"content":"The parties to Ecosystem Accord 3 are Sky and Keel, as defined in the subdocuments herein.","contentHash":"242fbb991069db681298464d61778d4e5be2914c08a7e84fd427083a745a99cd","addressRefs":[]},"7042cc09-20d7-4a83-a0f0-c718cdc489f2":{"id":"7042cc09-20d7-4a83-a0f0-c718cdc489f2","doc_no":"A.2.8.2.3.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"40a876f3-e0bb-4bdf-a980-ffa38d9f46d7","order":2003,"content":"The party ‘Sky’ comprises Sky Core.","contentHash":"9f309ae1b63e0b216b92c7f27c1fdc7edfeb60d0d845610b068d6654fb81ba87","addressRefs":[]},"2e888dad-7700-450a-be85-49d7405e3541":{"id":"2e888dad-7700-450a-be85-49d7405e3541","doc_no":"A.2.8.2.3.1.1.2","title":"Keel Details","type":"Core","depth":6,"parentId":"40a876f3-e0bb-4bdf-a980-ffa38d9f46d7","order":2004,"content":"The party ‘Keel’ comprises the Keel Prime Agent, Keel Foundation, and Elodin.","contentHash":"fdef9a58861533f9e06dae33bc3ece527514c922d292a954dcf47d02a3683ce3","addressRefs":[]},"d936e118-89d8-4be7-9fcd-dd4d4334b26d":{"id":"d936e118-89d8-4be7-9fcd-dd4d4334b26d","doc_no":"A.2.8.2.3.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"40a876f3-e0bb-4bdf-a980-ffa38d9f46d7","order":2005,"content":"The duration of Ecosystem Accord 3 is indefinite, commencing from June 23, 2025.","contentHash":"9f1eb4a9bd9e2028fa443ab14a4a7f85e239c67fcb7e10d9dd9eb151a429f30d","addressRefs":[]},"ff6f7572-716f-4959-b312-a5ebf1547134":{"id":"ff6f7572-716f-4959-b312-a5ebf1547134","doc_no":"A.2.8.2.3.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"63a88b08-e6cd-48bf-9cec-64ce7e42ae0e","order":2006,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 3.","contentHash":"e4552a1b0c4f6aa7d043d8b80b30d773441907fba25c09ca29008d000b8c3c23","addressRefs":[]},"c929aef7-1b81-4693-8fd8-3d75e62882af":{"id":"c929aef7-1b81-4693-8fd8-3d75e62882af","doc_no":"A.2.8.2.3.2.1","title":"Pioneer Incentive Pool","type":"Core","depth":6,"parentId":"ff6f7572-716f-4959-b312-a5ebf1547134","order":2007,"content":"Keel is eligible for a Pioneer Incentive Pool as specified in [A.2.2.8.3.1.4 - Pioneer Incentive Pool](04edac33-19d5-4a87-a8ab-945a0cd57771).\n\nThe Pioneer Incentive Pool is calculated on a monthly basis as the Sky Savings Rate multiplied by all Unrewarded USDS on Solana. Payments are made on a monthly basis from the Demand Side Buffer (see [A.2.2.8.1.2.1.4 - Demand Side Buffer](862b6d83-f464-4125-8259-233b7de75ec4)) to a Pioneer Incentive Pool wallet controlled by the Pioneer Prime. The address of the Pioneer Incentive Pool wallet on Solana is `8JmDPG5BFQ6gpUPJV9xBixYJLqTKCSNotkXksTmNsQfj`.","contentHash":"eba7ebbe13cf37c5e0285994b4ef58b64d7b14cbe96a49364152f208f2f3731d","addressRefs":["8JmDPG5BFQ6gpUPJV9xBixYJLqTKCSNotkXksTmNsQfj"]},"b0de2330-3678-4852-8c24-ce85445201a7":{"id":"b0de2330-3678-4852-8c24-ce85445201a7","doc_no":"A.2.8.2.3.2.2","title":"Tokenomics","type":"Core","depth":6,"parentId":"ff6f7572-716f-4959-b312-a5ebf1547134","order":2008,"content":"The tokenomics for Keel will be specified in a future iteration of the Atlas.","contentHash":"70a8900e8acafa1854b0406609b5facbd0796d12120b3fc457d834437cf7bd15","addressRefs":[]},"7df88d38-679b-42a2-a8a8-f798ac6a736b":{"id":"7df88d38-679b-42a2-a8a8-f798ac6a736b","doc_no":"A.2.8.2.3.2.3","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"ff6f7572-716f-4959-b312-a5ebf1547134","order":2009,"content":"The Genesis Capital Allocation for Keel is 10,000,000 USDS. The transfer of the Genesis Capital Allocation to Keel will be included in the March 26, 2026 Executive Vote. This action is authorized to proceed directly to an Executive Vote without a prior Governance Poll. The address of Keel's SubProxy account is specified in [A.6.1.1.3.2.1.1.3.1.1.2 - SubProxy Account](2d5f052a-e32a-472c-884f-4fd8746e0459).","contentHash":"0a54f38763ea024136cda11d46e78fd9a3e62f1abb018316e58b635704e1b49b","addressRefs":[]},"6bddc5aa-ac80-43d8-b8c8-8cde14e896df":{"id":"6bddc5aa-ac80-43d8-b8c8-8cde14e896df","doc_no":"A.2.8.2.4","title":"Ecosystem Accord 4: Sky And Obex","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2010,"content":"The subdocuments herein record the terms of agreement between Sky and Obex as agreed in Ecosystem Accord 4.","contentHash":"8ff0ab54bbc5ca9a6cf402ae273f767105e2c2f895ded11dd7cdd3e06ebb3482","addressRefs":[]},"b82be738-892e-4d55-a42f-84fc1fdf3064":{"id":"b82be738-892e-4d55-a42f-84fc1fdf3064","doc_no":"A.2.8.2.4.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"6bddc5aa-ac80-43d8-b8c8-8cde14e896df","order":2011,"content":"The subdocuments herein set out the key details of Ecosystem Accord 4, such as parties to the agreement and the duration of the Accord.","contentHash":"d0ecbe61e794f091afa0ad93bc72f1eb56fed095566362caa6fbac0fcb6f9c8d","addressRefs":[]},"2cd5a1de-89d0-47d0-b671-87d8fec45766":{"id":"2cd5a1de-89d0-47d0-b671-87d8fec45766","doc_no":"A.2.8.2.4.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"b82be738-892e-4d55-a42f-84fc1fdf3064","order":2012,"content":"The parties to Ecosystem Accord 4 are Sky and Obex, as defined in the subdocuments herein.","contentHash":"a5cf360f1bfede5d6d69b0b5c4cf9ac53d6795c55d58a659c43b5fdf8bc54f45","addressRefs":[]},"acb3e4c8-5edb-4ff0-bf47-e0a770cc08e7":{"id":"acb3e4c8-5edb-4ff0-bf47-e0a770cc08e7","doc_no":"A.2.8.2.4.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"b82be738-892e-4d55-a42f-84fc1fdf3064","order":2013,"content":"The party 'Sky' comprises Sky Core.","contentHash":"885934be2394184a80ccc02c3012f1b11d782ab2fc6459a0b542d5ca5032b445","addressRefs":[]},"665a712a-d211-4a7a-b4c9-a8bad61b3f9c":{"id":"665a712a-d211-4a7a-b4c9-a8bad61b3f9c","doc_no":"A.2.8.2.4.1.1.2","title":"Obex Details","type":"Core","depth":6,"parentId":"b82be738-892e-4d55-a42f-84fc1fdf3064","order":2014,"content":"The party 'Obex' comprises the Obex Prime Agent, Rubicon, and Treadstone.","contentHash":"35cf6ce63e77674c36f3e3978f894a720e41495f7f9cf2f8074a194375168c17","addressRefs":[]},"90e40d2a-3baa-411f-9512-b7cf61762a75":{"id":"90e40d2a-3baa-411f-9512-b7cf61762a75","doc_no":"A.2.8.2.4.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"b82be738-892e-4d55-a42f-84fc1fdf3064","order":2015,"content":"The duration of Ecosystem Accord 4 is indefinite, commencing from November 13, 2025.","contentHash":"920db7522420cb88ee378cd305401396c9412e5a063eb2f3dc43fc315c542ffe","addressRefs":[]},"ec71c718-4a93-4cd7-8324-11d00110bbd3":{"id":"ec71c718-4a93-4cd7-8324-11d00110bbd3","doc_no":"A.2.8.2.4.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"6bddc5aa-ac80-43d8-b8c8-8cde14e896df","order":2016,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 4. Additional detail regarding the substantive terms of Ecosystem Accord 4 will be specified in a future iteration of the Atlas, as agreed by the Parties to the Accord.","contentHash":"679ca954d1d5695c8ce313d0e846608f7fe5e87c985292b9080dea860119e279","addressRefs":[]},"b9e591ad-fd43-42fa-9262-aa9589c79ea3":{"id":"b9e591ad-fd43-42fa-9262-aa9589c79ea3","doc_no":"A.2.8.2.4.2.1","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"ec71c718-4a93-4cd7-8324-11d00110bbd3","order":2017,"content":"The subdocuments herein set out agreed terms with respect to Genesis Capital Allocation.","contentHash":"7913ee5f2553936b7a65cba65b559a319d7b7e801325f82cb0a29278263c00b9","addressRefs":[]},"a15698be-8723-4bab-9b25-f393deec41e2":{"id":"a15698be-8723-4bab-9b25-f393deec41e2","doc_no":"A.2.8.2.4.2.1.1","title":"Obex Initial Allocation","type":"Core","depth":6,"parentId":"ec71c718-4a93-4cd7-8324-11d00110bbd3","order":2018,"content":"The Initial Allocation for Obex is 21,000,000 USDS.","contentHash":"db2dbccf9b5f15446a5a045484f67fd9ac693ec5fc89fc6e2ebfef86509da51e","addressRefs":[]},"2ace92dc-2a09-4d9e-9bae-9ea4da1b2f38":{"id":"2ace92dc-2a09-4d9e-9bae-9ea4da1b2f38","doc_no":"A.2.8.2.4.2.1.2","title":"Initial Allocation Distribution","type":"Core","depth":6,"parentId":"ec71c718-4a93-4cd7-8324-11d00110bbd3","order":2019,"content":"The Initial Allocation is distributed in USDS to the Obex SubProxy.","contentHash":"7fb1525a33cab64582422daa8b30ea0c30942787bd486ce5c423a9ace2dfb08d","addressRefs":[]},"c39702fb-bb6a-43c7-b208-18ddd279b1d3":{"id":"c39702fb-bb6a-43c7-b208-18ddd279b1d3","doc_no":"A.2.8.2.4.2.1.2.1","title":"Transfer Of Genesis Capital Allocation To Obex SubProxy","type":"Core","depth":6,"parentId":"ec71c718-4a93-4cd7-8324-11d00110bbd3","order":2020,"content":"The transfer of 21,000,000 USDS from the Surplus Buffer to the Obex SubProxy for the Genesis Capital Allocation must be included in the November 13, 2025 Executive Vote. This action is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"a02429a7ff4992f1aaf2db737892c5f725fef0cdf639c12d61b6e3e6e1b51159","addressRefs":[]},"3aa58bdc-1c86-4a4e-8ca5-5a836cd2e465":{"id":"3aa58bdc-1c86-4a4e-8ca5-5a836cd2e465","doc_no":"A.2.8.2.5","title":"Ecosystem Accord 5: Sky And Core Council Executor Agent 1","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2021,"content":"The subdocuments herein record the terms of agreement between Sky and Core Council Executor Agent 1 as agreed in Ecosystem Accord 5.","contentHash":"51f91135f95c5fa9829621e445ba3b93cbcdc8e3af26928f296556b992ded6a9","addressRefs":[]},"b95a2b5e-f0e7-4ae4-ba47-56588d35e559":{"id":"b95a2b5e-f0e7-4ae4-ba47-56588d35e559","doc_no":"A.2.8.2.5.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"3aa58bdc-1c86-4a4e-8ca5-5a836cd2e465","order":2022,"content":"The subdocuments herein set out the key details of Ecosystem Accord 5, such as parties to the agreement and the duration of the Accord.","contentHash":"6d8d1e92201de7c7b8b1329dd07ffe9d7f6e5fdc37eb1c7c7bb6b70c6272a58c","addressRefs":[]},"711e1403-022d-4617-a835-bc98ab4dc521":{"id":"711e1403-022d-4617-a835-bc98ab4dc521","doc_no":"A.2.8.2.5.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"b95a2b5e-f0e7-4ae4-ba47-56588d35e559","order":2023,"content":"The parties to Ecosystem Accord 5 are Sky and Core Council Executor Agent 1, as defined in the subdocuments herein.","contentHash":"e9ebd3a5ec8f8226011bf0573f07a5bd54b7651e3d850d6b0b70560c8d3979d9","addressRefs":[]},"5999930f-429a-411a-9103-203357fd5e99":{"id":"5999930f-429a-411a-9103-203357fd5e99","doc_no":"A.2.8.2.5.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"b95a2b5e-f0e7-4ae4-ba47-56588d35e559","order":2024,"content":"The party 'Sky' comprises Sky Core.","contentHash":"885934be2394184a80ccc02c3012f1b11d782ab2fc6459a0b542d5ca5032b445","addressRefs":[]},"3e5e6630-0c08-4e89-ae09-a3c45dd654f2":{"id":"3e5e6630-0c08-4e89-ae09-a3c45dd654f2","doc_no":"A.2.8.2.5.1.1.2","title":"Core Council Executor Agent 1 Details","type":"Core","depth":6,"parentId":"b95a2b5e-f0e7-4ae4-ba47-56588d35e559","order":2025,"content":"The party 'Core Council Executor Agent 1' comprises the Core Council Executor Agent 1 Executor Agent, Core Council Executor Agent 1 Foundation, and Core Council Executor Agent 1 Development Company.","contentHash":"74a4eb2051ca648e8a776ab737cf1a242eb4cc35f68f74c12318bbed5bc49262","addressRefs":[]},"c24d90d8-de2a-4d07-841b-f72ab8bf2b1b":{"id":"c24d90d8-de2a-4d07-841b-f72ab8bf2b1b","doc_no":"A.2.8.2.5.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"b95a2b5e-f0e7-4ae4-ba47-56588d35e559","order":2026,"content":"The duration of Ecosystem Accord 5 is indefinite, commencing from December 11, 2025.","contentHash":"c2f2251398a25be8b45ea546df20361f97114fbbcfcd4bf675005c53cc81a48c","addressRefs":[]},"265e5d17-6a43-43e0-ac52-ad3bc4f2e8ea":{"id":"265e5d17-6a43-43e0-ac52-ad3bc4f2e8ea","doc_no":"A.2.8.2.5.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"3aa58bdc-1c86-4a4e-8ca5-5a836cd2e465","order":2027,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 5. Additional detail regarding the substantive terms of Ecosystem Accord 5 will be specified in a future iteration of the Atlas, as agreed by the Parties to the Accord.","contentHash":"b2019d66b352195b231b9cf1ba91fb1a150b7c6dbe551d70635115b4b9ceebe1","addressRefs":[]},"fbf36985-ee32-4426-b809-b26f36c6e8a7":{"id":"fbf36985-ee32-4426-b809-b26f36c6e8a7","doc_no":"A.2.8.2.5.2.1","title":"Role As Core Executor Agent","type":"Core","depth":6,"parentId":"265e5d17-6a43-43e0-ac52-ad3bc4f2e8ea","order":2028,"content":"Core Council Executor Agent 1 will serve as the first Core Executor Agent and must carry out the responsibilities of the Core Council. See [A.0.1.1.46 - Core Council](5a03a0c4-a47a-409c-9b23-52ac93e63d45).","contentHash":"8c30eb69e57710c9a568248a5406f51a9046d3979745f6db158a8a963ed46360","addressRefs":[]},"6dc349a3-183e-4074-8f6e-cff39867363e":{"id":"6dc349a3-183e-4074-8f6e-cff39867363e","doc_no":"A.2.8.2.5.2.2","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"265e5d17-6a43-43e0-ac52-ad3bc4f2e8ea","order":2029,"content":"To effect the Genesis Capitalization of Core Council Executor Agent 1, Sky Core shall directly transfer (1) 20,000,000 USDS to the Core Council Executor Agent 1 SubProxy and (2) 5,000,000 USDS to the Core Council Buffer (see [A.2.3.1.2.2.2.1 - Core Council Buffer](8b6781d7-f35c-4ffe-b8ed-299fa98e3da7)). The 5,000,000 USDS transfer constitutes part of Core Council Executor Agent 1's Genesis Capital Allocation, deposited directly to its operational payment account.","contentHash":"c3e79db17c51b0640281142f0484d30990baf97490fbc8d1c9eef29f45f45e41","addressRefs":[]},"89c19c75-cd5d-4c21-887d-0f4bfe3e42a7":{"id":"89c19c75-cd5d-4c21-887d-0f4bfe3e42a7","doc_no":"A.2.8.2.5.2.2.1","title":"Core Council Executor Agent 1 SubProxy Address","type":"Core","depth":6,"parentId":"265e5d17-6a43-43e0-ac52-ad3bc4f2e8ea","order":2030,"content":"The address of Core Council Executor Agent 1's SubProxy Account will be specified in the Technical Scope Forum Post for the deployment of the SubProxy Account.","contentHash":"6436670f8e5dcc6ad637df9e9574a27083e35db10cae1129c62e89bb16a5655b","addressRefs":[]},"7935cb9f-2ca1-475a-8b43-bf21b3fa2370":{"id":"7935cb9f-2ca1-475a-8b43-bf21b3fa2370","doc_no":"A.2.8.2.5.2.2.2","title":"Use Of Genesis Capital","type":"Core","depth":6,"parentId":"265e5d17-6a43-43e0-ac52-ad3bc4f2e8ea","order":2031,"content":"The Genesis Capital Allocation will be used to fund the Core Council Executor Agent 1; the incubating Operational Executor Agents; and broader Core operational expenses, including technical infrastructure, Spell crafting, risk work, and Spell audits.","contentHash":"4cc2875f44bb7b75bca2e4061ba43fafa7e2094278245f67f39d0539af7beaf0","addressRefs":[]},"3dd54817-d655-4fc5-b6f3-287623c1ba93":{"id":"3dd54817-d655-4fc5-b6f3-287623c1ba93","doc_no":"A.2.8.2.5.2.3","title":"Funding Of Core Council Buffer","type":"Core","depth":6,"parentId":"265e5d17-6a43-43e0-ac52-ad3bc4f2e8ea","order":2032,"content":"The Core Council Executor Agents holding seats on the Core Council maintain operational authority over the Core Council Buffer, consistent with their mandate to operationalize Sky Core.\n\nCore Council Executor Agent 1 may capitalize the Core Council Buffer from its Genesis Capital allocation to ensure adequate liquidity for operational payments prior to its establishment of dedicated payment infrastructure.\n\nExpenses paid through the Core Council Buffer shall be recorded as operational expenses of Core Council Executor Agent 1, whether funded by the Genesis Capital Allocation deposited directly to the Core Council Buffer or by subsequent transfers from the Core Council Executor Agent 1 SubProxy prior to the establishment of independent payment infrastructure.","contentHash":"d406e1e36fd7037fa68dfdda787f5c6a276b82ff0c1dfcc28ecb5fb8c932418f","addressRefs":[]},"45125ff8-5435-4cbf-9b20-9f55a1dbc883":{"id":"45125ff8-5435-4cbf-9b20-9f55a1dbc883","doc_no":"A.2.8.2.6","title":"Ecosystem Accord 6: Sky And Launch Agent 6","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2033,"content":"The subdocuments herein record the terms of agreement between Sky and Launch Agent 6 as agreed in Ecosystem Accord 6.","contentHash":"5fa1d8fe47d28b84e20efed64bec9076ce4a4db67b786c76756fb670f4f34cf5","addressRefs":[]},"262776d7-3f8e-4884-b858-b1942334ebab":{"id":"262776d7-3f8e-4884-b858-b1942334ebab","doc_no":"A.2.8.2.6.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"45125ff8-5435-4cbf-9b20-9f55a1dbc883","order":2034,"content":"The subdocuments herein set out the key details of Ecosystem Accord 6, such as parties to the agreement and the duration of the Accord.","contentHash":"d64e006ecfb60c2e2f22d74bd14d094c8d390ef0193dc4fcf82269eed4f413db","addressRefs":[]},"0f44e3b9-5fd3-4f1c-8917-97000969d334":{"id":"0f44e3b9-5fd3-4f1c-8917-97000969d334","doc_no":"A.2.8.2.6.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"262776d7-3f8e-4884-b858-b1942334ebab","order":2035,"content":"The parties to Ecosystem Accord 6 are Sky and Launch Agent 6, as defined in the subdocuments herein.","contentHash":"90e584fa890ca526496508503e862d2988f884bfe7237dc26fbb6f6227510168","addressRefs":[]},"dd7f7030-6020-490b-a8a2-196537ed66cd":{"id":"dd7f7030-6020-490b-a8a2-196537ed66cd","doc_no":"A.2.8.2.6.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"262776d7-3f8e-4884-b858-b1942334ebab","order":2036,"content":"The party 'Sky' comprises Sky Core.","contentHash":"885934be2394184a80ccc02c3012f1b11d782ab2fc6459a0b542d5ca5032b445","addressRefs":[]},"d9b2da30-bdae-47a6-96ff-966f92ce2b7e":{"id":"d9b2da30-bdae-47a6-96ff-966f92ce2b7e","doc_no":"A.2.8.2.6.1.1.2","title":"Launch Agent 6 Details","type":"Core","depth":6,"parentId":"262776d7-3f8e-4884-b858-b1942334ebab","order":2037,"content":"The party 'Launch Agent 6' comprises the Launch Agent 6 Prime Agent, Launch Agent 6 Foundation, and Stablewatch.","contentHash":"0f40d1f0a68eefa71f0bf7503629433493bc04f6bdb746e5c417e4256e441746","addressRefs":[]},"0b2fcb50-7b46-431a-8ab8-9c95c6ce8fb0":{"id":"0b2fcb50-7b46-431a-8ab8-9c95c6ce8fb0","doc_no":"A.2.8.2.6.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"262776d7-3f8e-4884-b858-b1942334ebab","order":2038,"content":"The duration of Ecosystem Accord 6 is indefinite, commencing from December 18, 2025.","contentHash":"dfa3616d121d3d99f437e49090306c2dedf934416605aa33dd8ff24ca67c889e","addressRefs":[]},"8a42e953-8932-41c4-acdc-4bc5b9274e3d":{"id":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","doc_no":"A.2.8.2.6.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"45125ff8-5435-4cbf-9b20-9f55a1dbc883","order":2039,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 6. Additional detail regarding the substantive terms of Ecosystem Accord 6 will be specified in a future iteration of the Atlas, as agreed by the Parties to the Accord.","contentHash":"a7ac5096fa889f17ff826565ebdb317f43c1dc023dcdbfc97bfd54f119f1e18f","addressRefs":[]},"66a45926-a68c-41ff-9773-940c627aa03a":{"id":"66a45926-a68c-41ff-9773-940c627aa03a","doc_no":"A.2.8.2.6.2.1","title":"Tokenomics","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2040,"content":"The subdocuments herein set out agreed terms with respect to tokenomics.","contentHash":"dcb147e8fc0ba02258422d7729ccb83e8bd2d14af13f185943ced65aa375b596","addressRefs":[]},"b25e4af5-e97a-4457-83be-c253c7f4d039":{"id":"b25e4af5-e97a-4457-83be-c253c7f4d039","doc_no":"A.2.8.2.6.2.1.1","title":"Total Token Supply","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2041,"content":"The total token supply of AGENT6 shall be 1,000,000,000.","contentHash":"ae768317bcbc92039a3fa9ca551fa031b7ebe2ae6dbe485a88c6c69261f17d64","addressRefs":[]},"45a052e0-954d-49d9-a691-7adff194a839":{"id":"45a052e0-954d-49d9-a691-7adff194a839","doc_no":"A.2.8.2.6.2.1.2","title":"Token Allocations","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2042,"content":"Specific token allocations are defined in the subdocuments herein.","contentHash":"b0d847a6d2e286865158a8f49dab0d048aef20c143d7df291601b4a2e3861aba","addressRefs":[]},"1ae8c439-cc0d-400f-90cd-4f5ef10356d6":{"id":"1ae8c439-cc0d-400f-90cd-4f5ef10356d6","doc_no":"A.2.8.2.6.2.1.2.1","title":"Launch Agent 6 Prime Treasury","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2043,"content":"677,777,778 AGENT6 tokens are allocated to the Launch Agent 6 Prime Treasury (Launch Agent 6’s SubProxy).\n\nLaunch Agent 6 will use 150,000,000 AGENT6 tokens for incentives.","contentHash":"faa01896ccb3b442eeb8b2265ee754e8a40cb9e87cdfc2cb3a9887b6af31c912","addressRefs":[]},"efb7339d-fb3d-4f5d-bdea-16ac8c291510":{"id":"efb7339d-fb3d-4f5d-bdea-16ac8c291510","doc_no":"A.2.8.2.6.2.1.2.2","title":"Sky Retained Tokens And Reward Pools","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2044,"content":"Sky retains 322,222,222 AGENT6 tokens, distributing these as specified in a future iteration of the Atlas.","contentHash":"5289a0839449b78528c1b5188a3e6a9c69623ff838122ad1af50b59d66f03640","addressRefs":[]},"f6ab77a4-8ba4-4f67-8c9f-8cc6a921ae53":{"id":"f6ab77a4-8ba4-4f67-8c9f-8cc6a921ae53","doc_no":"A.2.8.2.6.2.2","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2045,"content":"The subdocuments herein set out agreed terms with respect to Genesis Capital Allocation.","contentHash":"7913ee5f2553936b7a65cba65b559a319d7b7e801325f82cb0a29278263c00b9","addressRefs":[]},"94b2eef8-f5fd-4df1-8638-e1b81d032c47":{"id":"94b2eef8-f5fd-4df1-8638-e1b81d032c47","doc_no":"A.2.8.2.6.2.2.1","title":"Launch Agent 6 Initial Allocation","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2046,"content":"The Initial Allocation for Launch Agent 6 is 10,500,000 USDS.","contentHash":"84d72fd5cd250b924a6abdc4faae7fb6f64ebbeb9d1a50fb95e0ce3c372aca62","addressRefs":[]},"20eeeaf4-38bc-4440-be1c-a1ee67ee3491":{"id":"20eeeaf4-38bc-4440-be1c-a1ee67ee3491","doc_no":"A.2.8.2.6.2.2.2","title":"Initial Allocation Distribution","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2047,"content":"The Initial Allocation is distributed in USDS to the Launch Agent 6 SubProxy.","contentHash":"38916307349c62132dcbe76401b00c6b4b83014e2ece05b32d72c8a9000f566a","addressRefs":[]},"4fd99f26-90a3-4385-a3ea-7949f5d56b3f":{"id":"4fd99f26-90a3-4385-a3ea-7949f5d56b3f","doc_no":"A.2.8.2.6.2.2.2.1","title":"Transfer Of Genesis Capital Allocation To Launch Agent 6 Foundation","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2048,"content":"Sky has transferred 500,000 USDS from the Core Council Buffer to the Launch Agent 6 Foundation.\n\nThe address of the Launch Agent 6 Foundation on the Ethereum Mainnet is `0xfDD055D3CCEE0D955031CF1FD76c8Db9317cCC58`.","contentHash":"e0de7f5fa18356e701ea0d9f223d651e1199791a7f6fb89c5ec3fe80cc1c8dda","addressRefs":["0xfdd055d3ccee0d955031cf1fd76c8db9317ccc58"]},"65638659-eb0d-4e5c-87e8-50705e3595b8":{"id":"65638659-eb0d-4e5c-87e8-50705e3595b8","doc_no":"A.2.8.2.6.2.2.2.2","title":"Transfer Of Genesis Capital Allocation To Launch Agent 6 SubProxy","type":"Core","depth":6,"parentId":"8a42e953-8932-41c4-acdc-4bc5b9274e3d","order":2049,"content":"The transfer of 10,000,000 USDS from the Surplus Buffer to the Launch Agent 6 SubProxy for the Genesis Capital Allocation will be included in the March 26, 2026 Executive Vote. This action is authorized to proceed directly to an Executive Vote without a prior Governance Poll. The address of Launch Agent 6's SubProxy account is `0x24fdcd3bFA5C2553e05B2f9AD0365EBC296278D3`.","contentHash":"3a49e1c69fc2192efe7bc0bf90ff8967630389a0c9cc2de83cb9b01bc675204f","addressRefs":["0x24fdcd3bfa5c2553e05b2f9ad0365ebc296278d3"]},"8a74919c-d9c1-4d9a-9499-302201f96f9c":{"id":"8a74919c-d9c1-4d9a-9499-302201f96f9c","doc_no":"A.2.8.2.7","title":"Ecosystem Accord 7: Sky and Skybase","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2050,"content":"The subdocuments herein record the terms of agreement between Sky and Skybase as agreed in Ecosystem Accord 7.","contentHash":"ac9f6488e06955f28be999a6e7edbbfcc7f0a76d8ca79a6fbe988cb1dd4ebb0b","addressRefs":[]},"a6b51805-7420-46a5-b5d0-d769eb90e48d":{"id":"a6b51805-7420-46a5-b5d0-d769eb90e48d","doc_no":"A.2.8.2.7.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"8a74919c-d9c1-4d9a-9499-302201f96f9c","order":2051,"content":"The subdocuments herein set out the key details of Ecosystem Accord 7, such as parties to the agreement and the duration of the Accord.","contentHash":"91f323396e04463bea21b46337fc982fc890d9448d504c1664e8db44db4bf5dd","addressRefs":[]},"e5a76dd6-2e8a-425e-b961-664b24097f6e":{"id":"e5a76dd6-2e8a-425e-b961-664b24097f6e","doc_no":"A.2.8.2.7.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"a6b51805-7420-46a5-b5d0-d769eb90e48d","order":2052,"content":"The parties to Ecosystem Accord 7 are Sky and Skybase, as defined in the subdocuments herein.","contentHash":"a2b006c3fa27a2777d25b2ca7d476e6a663b94484b34aabe0c2ceb6aa788e8f6","addressRefs":[]},"83844293-5cca-45b3-9eb9-fd1d228aa3b5":{"id":"83844293-5cca-45b3-9eb9-fd1d228aa3b5","doc_no":"A.2.8.2.7.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"a6b51805-7420-46a5-b5d0-d769eb90e48d","order":2053,"content":"The party 'Sky' comprises Sky Core.","contentHash":"885934be2394184a80ccc02c3012f1b11d782ab2fc6459a0b542d5ca5032b445","addressRefs":[]},"287bbf07-b29b-46b1-a8a1-d237825424cd":{"id":"287bbf07-b29b-46b1-a8a1-d237825424cd","doc_no":"A.2.8.2.7.1.1.2","title":"Skybase Prime Details","type":"Core","depth":6,"parentId":"a6b51805-7420-46a5-b5d0-d769eb90e48d","order":2054,"content":"The party 'Skybase' comprises the Skybase Prime Agent, Skybase Foundation, and Development Company.","contentHash":"cd972da0dd021478d3077fd88f82d72794b25877b88501d9f39430a1cc99c0a6","addressRefs":[]},"9d207eb3-955e-4b4d-af1b-056519d0235b":{"id":"9d207eb3-955e-4b4d-af1b-056519d0235b","doc_no":"A.2.8.2.7.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"a6b51805-7420-46a5-b5d0-d769eb90e48d","order":2055,"content":"The duration of Ecosystem Accord 7 is indefinite, commencing from September 1, 2024.","contentHash":"c2f7159623abdfa8f475b21f75d025c54040267bc8e4bf2c594e267d5dffcc08","addressRefs":[]},"e51d5901-0b0b-42f0-b484-8114516c8e8a":{"id":"e51d5901-0b0b-42f0-b484-8114516c8e8a","doc_no":"A.2.8.2.7.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"8a74919c-d9c1-4d9a-9499-302201f96f9c","order":2056,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 7. Additional detail regarding the substantive terms of Ecosystem Accord 7 will be specified in a future iteration of the Atlas, as agreed by the Parties to the Accord.","contentHash":"a5edde2e600948df6cd206fcf5ed15a3dcb312c396a5fa57c2c39cf53291c34a","addressRefs":[]},"28790b12-35f5-4754-9bc2-d5dc527a6e37":{"id":"28790b12-35f5-4754-9bc2-d5dc527a6e37","doc_no":"A.2.8.2.7.2.1","title":"Tokenomics","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2057,"content":"The subdocuments herein set out agreed terms with respect to tokenomics.","contentHash":"dcb147e8fc0ba02258422d7729ccb83e8bd2d14af13f185943ced65aa375b596","addressRefs":[]},"709e8307-20ba-48c9-b9b5-71d58d05abb2":{"id":"709e8307-20ba-48c9-b9b5-71d58d05abb2","doc_no":"A.2.8.2.7.2.1.1","title":"Total Token Supply","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2058,"content":"The total token supply of SKYBASE will be specified in a future iteration of the Atlas.","contentHash":"e2969ab83e8ec60f01bcbf2e6b6612dbaba5f0c9f69ca9a65b0927387414c38f","addressRefs":[]},"6b69c767-ee38-42b3-9e45-3abaa17677f1":{"id":"6b69c767-ee38-42b3-9e45-3abaa17677f1","doc_no":"A.2.8.2.7.2.1.2","title":"Token Allocations","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2059,"content":"Specific token allocations are defined in the subdocuments herein.","contentHash":"b0d847a6d2e286865158a8f49dab0d048aef20c143d7df291601b4a2e3861aba","addressRefs":[]},"088264de-3158-4200-a5ce-e1eb730d38a6":{"id":"088264de-3158-4200-a5ce-e1eb730d38a6","doc_no":"A.2.8.2.7.2.1.2.1","title":"Skybase Prime Treasury","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2060,"content":"The amount of SKYBASE tokens allocated to the Skybase Prime Treasury (Skybase's SubProxy) will be specified in a future iteration of the Atlas.","contentHash":"7f9bb3c8179f6248cff44d52df5afc0fa7bd8068e9107f2885458f024707b07b","addressRefs":[]},"576ff155-7fc3-4d9d-8359-f9e9cc5da874":{"id":"576ff155-7fc3-4d9d-8359-f9e9cc5da874","doc_no":"A.2.8.2.7.2.1.2.2","title":"Sky Retained Tokens And Reward Pools","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2061,"content":"The amount of SKYBASE tokens retained by Sky and their distribution will be specified in a future iteration of the Atlas.","contentHash":"c3e7b14d93370ba148c0a06802ddb4c2f44ef1dec67bcd7e6d090f9872898c2f","addressRefs":[]},"d5168fa2-5a7f-4dd7-9a00-d3d1732c3bc3":{"id":"d5168fa2-5a7f-4dd7-9a00-d3d1732c3bc3","doc_no":"A.2.8.2.7.2.2","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2062,"content":"The subdocuments herein set out agreed terms with respect to Genesis Capital Allocation.","contentHash":"7913ee5f2553936b7a65cba65b559a319d7b7e801325f82cb0a29278263c00b9","addressRefs":[]},"0ad56e68-ac7a-4660-8bdc-4d11d69511ce":{"id":"0ad56e68-ac7a-4660-8bdc-4d11d69511ce","doc_no":"A.2.8.2.7.2.2.1","title":"Skybase Initial Allocation","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2063,"content":"The Initial Allocation for Skybase is 15,000,000 USDS.","contentHash":"310475014baadfffa565196375f8f38780edcab0446a4f26013376a00fb0c743","addressRefs":[]},"2f2c4f2b-ff7a-4cd1-b1bc-8f3f81fe129f":{"id":"2f2c4f2b-ff7a-4cd1-b1bc-8f3f81fe129f","doc_no":"A.2.8.2.7.2.2.2","title":"Initial Allocation Distribution","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2064,"content":"10,000,000 USDS of the Initial Allocation is distributed to the Skybase SubProxy.\n\n5,000,000 USDS of the Initial Allocation is distributed to the USDS Demand Subsidies Multisig.","contentHash":"fe81a94fd5d861848a32d21b796c9b4ccd8e23bb05f8b6506b09899721c5160d","addressRefs":[]},"36556509-d2b6-4932-8781-9bf4ecc90987":{"id":"36556509-d2b6-4932-8781-9bf4ecc90987","doc_no":"A.2.8.2.7.2.2.2.1","title":"Transfer Of Genesis Capital Allocation To Skybase SubProxy","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2065,"content":"The transfer of 10,000,000 USDS from the Surplus Buffer to the Skybase SubProxy for the Genesis Capital Allocation will be included in the January 29, 2026 Executive Vote.\n\nThis action is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"8ed99c3277b6e31844212c033c658c653aeb3575d511b916373293e4fc7283e5","addressRefs":[]},"be600bf6-c0f2-42c5-ad5c-fd0cb429b628":{"id":"be600bf6-c0f2-42c5-ad5c-fd0cb429b628","doc_no":"A.2.8.2.7.2.2.2.2","title":"Transfer Of Genesis Capital Allocation To USDS Demand Multisig","type":"Core","depth":6,"parentId":"e51d5901-0b0b-42f0-b484-8114516c8e8a","order":2066,"content":"The transfer of 5,000,000 USDS from the Surplus Buffer to the USDS Demand Subsidies Multisig (see [A.6.1.1.4.3.4.2 - USDS Demand Subsidies Multisig](20ee784c-115a-40bb-ae74-d4b3726b0c1b)) for the Genesis Capital Allocation will be included in the January 29, 2026 Executive Vote.\n\nThis action is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"03ea7b7626606f2df4ee04f01e07f0c3a2b2d50642dd079063713e59c59540ef","addressRefs":[]},"9d187ae2-1106-4b43-a6a6-ff54c329d0da":{"id":"9d187ae2-1106-4b43-a6a6-ff54c329d0da","doc_no":"A.2.8.2.8","title":"Ecosystem Accord 8: Sky And Amatsu","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2067,"content":"The subdocuments herein record the terms of agreement between Sky and Amatsu as agreed in Ecosystem Accord 8.","contentHash":"ca4334f75e5b32f568a74257e7c894716ec2cfa75d6786ea184996952c32ea3f","addressRefs":[]},"7b53595c-b29f-40b4-8098-21949ed4f6e4":{"id":"7b53595c-b29f-40b4-8098-21949ed4f6e4","doc_no":"A.2.8.2.8.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"9d187ae2-1106-4b43-a6a6-ff54c329d0da","order":2068,"content":"The subdocuments herein set out the key details of Ecosystem Accord 8, such as parties to the agreement and the duration of the Accord.","contentHash":"ed766ddfe1e035df9b42ae6ee7f062b0b255587043e553a45aa513adf4ed4afe","addressRefs":[]},"511d2f27-51f4-48bb-b147-cfbb81a05096":{"id":"511d2f27-51f4-48bb-b147-cfbb81a05096","doc_no":"A.2.8.2.8.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"7b53595c-b29f-40b4-8098-21949ed4f6e4","order":2069,"content":"The parties to Ecosystem Accord 8 are Sky and Amatsu, as defined in the subdocuments herein.","contentHash":"80c62e3dcf0920dcc6227fa7a3cf6c817f985b04fee1342ce37e83c9b93b2f54","addressRefs":[]},"fa3bcebb-38a6-4541-8349-e07166fb4d81":{"id":"fa3bcebb-38a6-4541-8349-e07166fb4d81","doc_no":"A.2.8.2.8.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"7b53595c-b29f-40b4-8098-21949ed4f6e4","order":2070,"content":"The party 'Sky' comprises Sky Core.","contentHash":"885934be2394184a80ccc02c3012f1b11d782ab2fc6459a0b542d5ca5032b445","addressRefs":[]},"cef53b14-d230-4f10-a482-0fbacdf3d3bc":{"id":"cef53b14-d230-4f10-a482-0fbacdf3d3bc","doc_no":"A.2.8.2.8.1.1.2","title":"Amatsu Details","type":"Core","depth":6,"parentId":"7b53595c-b29f-40b4-8098-21949ed4f6e4","order":2071,"content":"The party 'Amatsu' comprises the Amatsu Executor Agent.","contentHash":"7c062e3dcbe31110c63fb88490d3236f229235c0f27f7474497a7e0d631a2d16","addressRefs":[]},"918ce6f7-dd4b-419d-8a5c-92fb595b0ec1":{"id":"918ce6f7-dd4b-419d-8a5c-92fb595b0ec1","doc_no":"A.2.8.2.8.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"7b53595c-b29f-40b4-8098-21949ed4f6e4","order":2072,"content":"The duration of Ecosystem Accord 8 is indefinite, commencing from March 19, 2026.","contentHash":"bba480e0b39d102402b04a595dd8b7f1cad136b65594d87c4556967e2a4443c4","addressRefs":[]},"d6624ff1-e50e-4a56-b1c4-2f24af3cb34e":{"id":"d6624ff1-e50e-4a56-b1c4-2f24af3cb34e","doc_no":"A.2.8.2.8.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"9d187ae2-1106-4b43-a6a6-ff54c329d0da","order":2073,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 8. Additional detail regarding the substantive terms of Ecosystem Accord 8 will be specified in a future iteration of the Atlas, as agreed by the Parties to the Accord.","contentHash":"d19c72a83d99da67ba3faf27ea0f02354c8ef1f455dd7ac2558047a65784b495","addressRefs":[]},"ff5c1b0c-8027-4711-9cc3-a18772c0ba5b":{"id":"ff5c1b0c-8027-4711-9cc3-a18772c0ba5b","doc_no":"A.2.8.2.8.2.1","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"d6624ff1-e50e-4a56-b1c4-2f24af3cb34e","order":2074,"content":"The Genesis Capital Allocation for Amatsu is 25,000,000 USDS. The transfer of the Genesis Capital Allocation to Amatsu will be included in the March 26, 2026 Executive Vote. This action is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"44d7f569c281d92d93608b979d2a9b63efe66a3c5bbaa9c9c228275f5fbc19bf","addressRefs":[]},"fa9d102c-39ad-49ea-a30e-5101c3400313":{"id":"fa9d102c-39ad-49ea-a30e-5101c3400313","doc_no":"A.2.8.2.8.2.1.1","title":"Amatsu SubProxy Address","type":"Core","depth":6,"parentId":"d6624ff1-e50e-4a56-b1c4-2f24af3cb34e","order":2075,"content":"The address of Amatsu's SubProxy Account will be specified in the Technical Scope Forum Post for the deployment of the SubProxy Account.","contentHash":"7a9fc8dcd009d0de872b6ca4a93a18e714c429c98d3a786594ec0f0171d56a5c","addressRefs":[]},"64bb69a7-6525-44ad-af92-cb7dd400fcc8":{"id":"64bb69a7-6525-44ad-af92-cb7dd400fcc8","doc_no":"A.2.8.2.8.2.1.2","title":"Use Of Genesis Capital","type":"Core","depth":6,"parentId":"d6624ff1-e50e-4a56-b1c4-2f24af3cb34e","order":2076,"content":"The Genesis Capital Allocation will be used to support Amatsu's work in delivering services in the role of Operational Executor Agent for the Sky Ecosystem.","contentHash":"5369b95d20b521476dd72c11777bbe1a27fd2e2a99df3045caf069245780f9bf","addressRefs":[]},"cb3c159b-46fd-4e85-a6d5-e2ab17977ac8":{"id":"cb3c159b-46fd-4e85-a6d5-e2ab17977ac8","doc_no":"A.2.8.2.9","title":"Ecosystem Accord 9: Sky And Ozone","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2077,"content":"The subdocuments herein record the terms of agreement between Sky and Ozone as agreed in Ecosystem Accord 9.","contentHash":"df231a1da6a76594aa49f93309d620aca9d073145fec6d9957297744ff1cbffa","addressRefs":[]},"dbbd6557-ff1e-49e2-951b-1457d290b55f":{"id":"dbbd6557-ff1e-49e2-951b-1457d290b55f","doc_no":"A.2.8.2.9.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"cb3c159b-46fd-4e85-a6d5-e2ab17977ac8","order":2078,"content":"The subdocuments herein set out the key details of Ecosystem Accord 9, such as parties to the agreement and the duration of the Accord.","contentHash":"1122f162cda8e3c531648288ab575c2ff70cfd971bb5bcd24ec256184f4a350a","addressRefs":[]},"81a42abc-2494-493e-9698-68a0c712684e":{"id":"81a42abc-2494-493e-9698-68a0c712684e","doc_no":"A.2.8.2.9.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"dbbd6557-ff1e-49e2-951b-1457d290b55f","order":2079,"content":"The parties to Ecosystem Accord 9 are Sky and Ozone, as defined in the subdocuments herein.","contentHash":"05c085c90c1745572af4826246e8e237b66327a3953b345849cd9f5f99e5b971","addressRefs":[]},"12d48429-0536-4efd-aaa2-2ca433498e81":{"id":"12d48429-0536-4efd-aaa2-2ca433498e81","doc_no":"A.2.8.2.9.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"dbbd6557-ff1e-49e2-951b-1457d290b55f","order":2080,"content":"The party 'Sky' comprises Sky Core.","contentHash":"885934be2394184a80ccc02c3012f1b11d782ab2fc6459a0b542d5ca5032b445","addressRefs":[]},"483798e7-9aac-4a93-9e89-52d108be3c55":{"id":"483798e7-9aac-4a93-9e89-52d108be3c55","doc_no":"A.2.8.2.9.1.1.2","title":"Ozone Details","type":"Core","depth":6,"parentId":"dbbd6557-ff1e-49e2-951b-1457d290b55f","order":2081,"content":"The party 'Ozone' comprises the Ozone Executor Agent.","contentHash":"f78df4528ffdb7637b1aeb92da8fd3c93b820cef3063ace41903f4087e29836b","addressRefs":[]},"28433341-af4a-435d-8839-0225f515af64":{"id":"28433341-af4a-435d-8839-0225f515af64","doc_no":"A.2.8.2.9.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"dbbd6557-ff1e-49e2-951b-1457d290b55f","order":2082,"content":"The duration of Ecosystem Accord 9 is indefinite, commencing from March 19, 2026.","contentHash":"880af81e9ae24fa047cb928117f4cac4e551f8be256d7cad7f79867680b0cf7f","addressRefs":[]},"91fabe18-fd56-448e-9485-46427647a675":{"id":"91fabe18-fd56-448e-9485-46427647a675","doc_no":"A.2.8.2.9.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"cb3c159b-46fd-4e85-a6d5-e2ab17977ac8","order":2083,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 9. Additional detail regarding the substantive terms of Ecosystem Accord 9 will be specified in a future iteration of the Atlas, as agreed by the Parties to the Accord.","contentHash":"3b1778724c8e22c2d4c316490f703884b91b133569189eee20d91b1ce20ac992","addressRefs":[]},"ee64a5b7-da29-4b14-aaa7-e2f370a37301":{"id":"ee64a5b7-da29-4b14-aaa7-e2f370a37301","doc_no":"A.2.8.2.9.2.1","title":"Genesis Capital Allocation","type":"Core","depth":6,"parentId":"91fabe18-fd56-448e-9485-46427647a675","order":2084,"content":"The Genesis Capital Allocation for Ozone is 25,000,000 USDS. The transfer of the Genesis Capital Allocation to Ozone will be included in the March 26, 2026 Executive Vote. This action is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"96c38408f50ae8147b458a57838c7d0d5543417a74c3655261342291ec82cead","addressRefs":[]},"6337ca25-2d6f-4483-9b89-c087138ebabf":{"id":"6337ca25-2d6f-4483-9b89-c087138ebabf","doc_no":"A.2.8.2.9.2.1.1","title":"Ozone SubProxy Address","type":"Core","depth":6,"parentId":"91fabe18-fd56-448e-9485-46427647a675","order":2085,"content":"The address of Ozone's SubProxy Account will be specified in the Technical Scope Forum Post for the deployment of the SubProxy Account.","contentHash":"ee738f4c153e14a658b5b3353173a751b7262cf37da2947955f46a986eec6220","addressRefs":[]},"9e7acf02-b30c-47fd-aa6f-bef61dc1210d":{"id":"9e7acf02-b30c-47fd-aa6f-bef61dc1210d","doc_no":"A.2.8.2.9.2.1.2","title":"Use Of Genesis Capital","type":"Core","depth":6,"parentId":"91fabe18-fd56-448e-9485-46427647a675","order":2086,"content":"The Genesis Capital Allocation will be used to fund Ozone's work in supporting the Agents that it serves as the Operational Executor Agent for.","contentHash":"7278e922326fa298c371650be181e171c8fd01c6c3bdc26d87fb5c58ad0ddfb8","addressRefs":[]},"0cb00b28-12a8-4790-974a-a3d98fd4dc97":{"id":"0cb00b28-12a8-4790-974a-a3d98fd4dc97","doc_no":"A.2.8.2.10","title":"Ecosystem Accord 10: Sky And Grove","type":"Core","depth":4,"parentId":"be46648d-a154-480a-b202-81fd1ac735d2","order":2087,"content":"The subdocuments herein record the terms of agreement between Sky and Grove as agreed in Ecosystem Accord 10.","contentHash":"15bedc6c2b3fb612a6e19f52179c09a75acffcec7cfebfb3d3ca81f2e8b2bf46","addressRefs":[]},"7b9e976e-f55a-45a4-b0ae-db5142164d98":{"id":"7b9e976e-f55a-45a4-b0ae-db5142164d98","doc_no":"A.2.8.2.10.1","title":"Accord Key Details","type":"Core","depth":5,"parentId":"0cb00b28-12a8-4790-974a-a3d98fd4dc97","order":2088,"content":"The subdocuments herein set out the key details of Ecosystem Accord 10, such as parties to the agreement and the duration of the Accord.","contentHash":"a5a13909301288be80688266631f4b402284bb71f2ed22d71d0571d309e7195d","addressRefs":[]},"6b454041-6333-4da3-94e5-d9a29b1c01d6":{"id":"6b454041-6333-4da3-94e5-d9a29b1c01d6","doc_no":"A.2.8.2.10.1.1","title":"Parties To The Accord","type":"Core","depth":6,"parentId":"7b9e976e-f55a-45a4-b0ae-db5142164d98","order":2089,"content":"The parties to Ecosystem Accord 10 are Sky and Grove, as defined in the subdocuments herein.","contentHash":"1497a3d92bcb58a59d1b57f9ef6ea9a356a5872b99c0c39ce32de610530dab3e","addressRefs":[]},"e785ccea-cf2a-44f3-a49b-632edfd4bb5a":{"id":"e785ccea-cf2a-44f3-a49b-632edfd4bb5a","doc_no":"A.2.8.2.10.1.1.1","title":"Sky Details","type":"Core","depth":6,"parentId":"7b9e976e-f55a-45a4-b0ae-db5142164d98","order":2090,"content":"The party 'Sky' comprises Sky Core.","contentHash":"885934be2394184a80ccc02c3012f1b11d782ab2fc6459a0b542d5ca5032b445","addressRefs":[]},"71eda1d2-5ea4-4999-89a9-168df36e0c60":{"id":"71eda1d2-5ea4-4999-89a9-168df36e0c60","doc_no":"A.2.8.2.10.1.1.2","title":"Grove Details","type":"Core","depth":6,"parentId":"7b9e976e-f55a-45a4-b0ae-db5142164d98","order":2091,"content":"The party 'Grove' comprises the Grove Prime Agent and Grove Foundation.","contentHash":"1421bba7a8872fefe4cf8c6ece8058d8d43a831d3f54559cd987f874c02fa47c","addressRefs":[]},"c7d102c8-3d5d-47c2-80a0-66a4c4ee7430":{"id":"c7d102c8-3d5d-47c2-80a0-66a4c4ee7430","doc_no":"A.2.8.2.10.1.2","title":"Duration Of The Accord","type":"Core","depth":6,"parentId":"7b9e976e-f55a-45a4-b0ae-db5142164d98","order":2092,"content":"The duration of Ecosystem Accord 10 is indefinite, commencing retroactively from July 24, 2025. The Accord remains in effect unless terminated or modified via an Atlas Edit.","contentHash":"85613f231c6d620691f3bb7993bc783f1c6a7aac84946b7c13d8f4ee480a0d05","addressRefs":[]},"c44e816f-dd67-4e35-aa4c-7098f159a05d":{"id":"c44e816f-dd67-4e35-aa4c-7098f159a05d","doc_no":"A.2.8.2.10.2","title":"Accord Substantive Terms","type":"Core","depth":5,"parentId":"0cb00b28-12a8-4790-974a-a3d98fd4dc97","order":2093,"content":"The subdocuments herein set out the substantive terms of Ecosystem Accord 10.","contentHash":"6a3a9041ab63ab3639a2e55e4683f35d76ee10ea6323bfd2a185e0c9834c39e1","addressRefs":[]},"a7ccb2d1-970e-4b91-a430-4173ade00396":{"id":"a7ccb2d1-970e-4b91-a430-4173ade00396","doc_no":"A.2.8.2.10.2.1","title":"Chronicle Point Reward Instance Definition","type":"Core","depth":6,"parentId":"c44e816f-dd67-4e35-aa4c-7098f159a05d","order":2094,"content":"The \"Chronicle Point Reward Instance\" refers to the Ethereum mainnet reward mechanism through which USDS is deposited in Sky's Rewards contract to accrue Chronicle Points. Onchain, this instance is the verified `StakingRewards` contract at the address corresponding to the `REWARDS_USDS_01` key in the Chainlog.","contentHash":"0480cbd71ed6df78e8f92a151a7c0dd96f0f53c9ee225f00a3f42c61fc678901","addressRefs":[]},"d4a5ce00-b041-4e9d-9bed-23253aba1b01":{"id":"d4a5ce00-b041-4e9d-9bed-23253aba1b01","doc_no":"A.2.8.2.10.2.2","title":"Compensation Formula","type":"Core","depth":6,"parentId":"c44e816f-dd67-4e35-aa4c-7098f159a05d","order":2095,"content":"Sky will pay Grove ongoing compensation in USDS, calculated as follows:\n\n$\n\\text{Chronicle\\_Point\\_Reward\\_Instance\\_USDS\\_Deposited} \\times 20\\% \\times \\text{Base\\_Rate}\n$\n\nwhere:\n\n- $\\text{Chronicle\\_Point\\_Reward\\_Instance\\_USDS\\_Deposited}$ is the total amount of USDS deposited in the Chronicle Point Reward Instance at the time of calculation;\n- $20\\%$ is the fixed compensation percentage; and\n- $Base\\_Rate$ is the Base Rate as defined in [A.3.1.2.1 - Base Rate](228f9955-6bba-4252-a101-5529e7a300b9).\n\nThis compensation recognizes Grove's role in promoting and supporting Chronicle across integrations within the Sky Ecosystem.","contentHash":"9c80d7ae600b4eead9fafa8c127a3ce4667931fe5162fc1d6ea1cb9832d9cd4d","addressRefs":[]},"4bed0292-a720-4306-b528-5d583fd4ead5":{"id":"4bed0292-a720-4306-b528-5d583fd4ead5","doc_no":"A.2.8.2.10.2.3","title":"Accrual Method","type":"Core","depth":6,"parentId":"c44e816f-dd67-4e35-aa4c-7098f159a05d","order":2096,"content":"Compensation under this Accord accrues continuously on the basis of the USDS deposited in the Chronicle Point Reward Instance and the Base Rate at each point in time. Where the Base Rate or the amount of USDS deposited changes during an accrual period, the compensation is calculated proportionally for each sub-period in which the relevant parameters remain constant.","contentHash":"a5b166835cc2c24c3921b184523a3c9257b92f85681aa828a96b62c275fd7785","addressRefs":[]},"31e070cf-2474-4815-a7da-350feaa97cc7":{"id":"31e070cf-2474-4815-a7da-350feaa97cc7","doc_no":"A.2.8.2.10.2.4","title":"Payment Frequency And Mechanism","type":"Core","depth":6,"parentId":"c44e816f-dd67-4e35-aa4c-7098f159a05d","order":2097,"content":"Compensation under this Accord is settled monthly via the Monthly Settlement Cycle (MSC). Each monthly settlement is calculated as:\n\n$$ \n\\text{Monthly Settlement} = \\sum \\left[ \\frac{\\text{USDS\\_Deposited (sub-period)} \\times 0.20 \\times \\text{Base\\_Rate (sub-period)}}{365} \\times \\text{Sub-Period\\_Days} \\right] \n$$\n\nwhere sub-periods are defined by any change to the USDS deposited in the Chronicle Point Reward Instance or the Base Rate during the settlement month, per the accrual method in [A.2.8.2.10.2.3 - Accrual Method](4bed0292-a720-4306-b528-5d583fd4ead5).","contentHash":"c53d2492fd97421e3777e38299e08db62cac613d98a82e131d0be213d3fb6b4e","addressRefs":[]},"e19ba00b-8509-4cf1-b9af-20f16e9683f8":{"id":"e19ba00b-8509-4cf1-b9af-20f16e9683f8","doc_no":"A.2.8.2.10.2.5","title":"Retroactive Compensation","type":"Core","depth":6,"parentId":"c44e816f-dd67-4e35-aa4c-7098f159a05d","order":2098,"content":"Grove is entitled to retroactive compensation for the period from July 24, 2025 to March 31, 2026, to be settled in the April 2026 Monthly Settlement Cycle.","contentHash":"266651f6d5b676bf8385a7512c32932430552128a32504fced1938cdd6f24d44","addressRefs":[]},"31df7e2b-184f-428c-9c4f-23fd8054c5d3":{"id":"31df7e2b-184f-428c-9c4f-23fd8054c5d3","doc_no":"A.2.8.0.3.1","title":"Business Activities - Element Annotation","type":"Annotation","depth":3,"parentId":"104c3543-ce94-4a2f-9968-57f1ee858085","order":2099,"content":"The element \"business activities\" refers to the commercial activities, transactions, and interactions that Ecosystem Actors perform within the ecosystem. These may include, but are not limited to, service delivery, product development, collaboration, and information exchange.","contentHash":"625b0b52a18547d9d31339ab0b83b567980aff8ddafb72f721dfa2db166a8448","addressRefs":[]},"ed6d46b7-01bc-4b3f-a951-e75c3f40351a":{"id":"ed6d46b7-01bc-4b3f-a951-e75c3f40351a","doc_no":"A.2.8.0.3.2","title":"Ecosystem - Element Annotation","type":"Annotation","depth":3,"parentId":"104c3543-ce94-4a2f-9968-57f1ee858085","order":2100,"content":"The element \"Ecosystem\" in the phrase \"Ecosystem Accords\" should be understood as the collaborative network in which multiple stakeholders (referred to as \"Ecosystem Actors\") interact to conduct business operations benefiting Sky.","contentHash":"2eb50e918b0ce44816119e11263a951081f02eab294b3271992e308eb42c581f","addressRefs":[]},"ac707ae4-65da-4cf9-8a34-8b9304cd9a95":{"id":"ac707ae4-65da-4cf9-8a34-8b9304cd9a95","doc_no":"A.2.9","title":"Legal Resilience","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":2101,"content":"This Article governs the Resilience Fund and defines infrastructure and processes to support legal risk management and legal governance.","contentHash":"403545a2747d81e33f5a3c6a2904a6c0f9cb4c99bedabcb58c1d27c5700e2c32","addressRefs":[]},"2abdcb34-3863-40d9-8dd1-52516cb1fa96":{"id":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","doc_no":"A.2.9.1","title":"Legal Resilience","type":"Section","depth":3,"parentId":"ac707ae4-65da-4cf9-8a34-8b9304cd9a95","order":2102,"content":"This Section manages the Resilience Fund (also \"RF\") and other infrastructure for legal risk management and legal governance.","contentHash":"3a742b8e3a10424ecb3e5d5052b194ac42ad270c4d5ad25e23207342e3412713","addressRefs":[]},"8f2eb896-4736-4649-a054-1c76dae64dc6":{"id":"8f2eb896-4736-4649-a054-1c76dae64dc6","doc_no":"A.2.9.1.1","title":"Legal Defense Resources","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2103,"content":"This document defines the resources available for legal defense. Over time, it can include both Sky Governance-controlled assets and external third-party resources and may be used to cover additional risks.","contentHash":"465eefcdf9787784ed007def72ebb1508689fa0a9b282828153d21024da4ca7a","addressRefs":[]},"ccd36a29-af79-4994-93b4-b07d150b0366":{"id":"ccd36a29-af79-4994-93b4-b07d150b0366","doc_no":"A.2.9.1.1.1","title":"Resilience Fund","type":"Core","depth":5,"parentId":"8f2eb896-4736-4649-a054-1c76dae64dc6","order":2104,"content":"The Resilience Fund (RF) is a self-insurance instrument fully controlled by Sky Governance, which will cover legal defense expenses in case of legal or regulatory action against Sky or active participants in the Sky Ecosystem. The RF will be the primary source for direct legal defense funding. The conditions of use are defined in [A.2.9.1.1.1.4.2 - Resilience Fund Claim Management Process](9ab8fdf3-939c-4096-a0b9-9d9486d5a339).","contentHash":"495d9a7f17cf2f7661c573c33761f76ce82f8ef7f22ce7e5f0a19246d14a7ef1","addressRefs":[]},"43c65f87-9de3-42ce-ab1c-e9bf420b6920":{"id":"43c65f87-9de3-42ce-ab1c-e9bf420b6920","doc_no":"A.2.9.1.1.1.1","title":"Resilience Fund Budget","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2105,"content":"The budget of the Resilience Fund is defined in [A.2.9.1.1.1.1.1 - Resilience Fund Current Budget](aa1e93e5-8fc0-4e12-ad9d-8bb9f6cd8956). The Support Facilitator can propose to pay out the budget manually through a Weekly Governance Cycle, according to the rules related to claims described in this Section. The Support Facilitator can propose modifications to the document cited above through the Weekly Governance Cycle.","contentHash":"59b3c2246d5df5ad04156bd8156a7c364713c094a263142ecebb3f7a5be1403d","addressRefs":[]},"aa1e93e5-8fc0-4e12-ad9d-8bb9f6cd8956":{"id":"aa1e93e5-8fc0-4e12-ad9d-8bb9f6cd8956","doc_no":"A.2.9.1.1.1.1.1","title":"Resilience Fund Current Budget","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2106,"content":"The current active budget for the Resilience Fund is: 5,000,000 USDS per year, with the full amount available at the start of each calendar year.","contentHash":"b4890f8abcad16bfb604802afe8b77c1de2a323a4479ea1cb2e006eebaa726a9","addressRefs":[]},"cbcfc2ff-d26a-4e2d-896d-273ed2eb8a94":{"id":"cbcfc2ff-d26a-4e2d-896d-273ed2eb8a94","doc_no":"A.2.9.1.1.1.1.2","title":"Resilience Fund Transition Funding","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2107,"content":"Legal defense expenses directly related to Sky may be temporarily financed using the resources of the Resilience Fund. However, a separate Claim Protocol and Standard Operational Protocol must be developed to govern cases where Sky is the target of a legal or regulatory action.","contentHash":"ccfb3ba8b88f6b236aaeebbc626b351044fde30f7e08055678f899fa933f4132","addressRefs":[]},"b1cbe4dd-1df7-461f-b6dd-315d899f922c":{"id":"b1cbe4dd-1df7-461f-b6dd-315d899f922c","doc_no":"A.2.9.1.1.1.1.2.0.3.1","title":"Separate Claim Protocol And Standard Operational Protocol - Element Annotation","type":"Annotation","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2108,"content":"The element refers to a separate set of procedures to be applied where Sky is the target of a legal or regulatory action. These separate procedures have not yet been defined. Once defined and ratified, they will be detailed in [A.2.9.1.1.4 - Legal Defense Standard Operational Protocols](bd82af2f-6617-4d4e-8acb-e23c7d2c904b). The Resilience Technical Committee must assist in elaborating this ruleset.","contentHash":"d66157bf79e6f9b0c3b33707e7476a1e1ccdb0baa153679dfdb2461e7a83f648","addressRefs":[]},"469a7e0b-0ded-45cf-9911-06723bf0cfd4":{"id":"469a7e0b-0ded-45cf-9911-06723bf0cfd4","doc_no":"A.2.9.1.1.1.2","title":"Resilience Fund Technical Committee","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2109,"content":"The Resilience Technical Committee is a group of Ecosystem Actors authorized by Sky to provide operational support such as onboarding new beneficiaries to the RF, approving quotes, and assessing claims to be supported by the RF. Additional operational support includes providing general advice on the further development of the fund, amendments to the claim procedure, resilience measures and other risk-management topics.","contentHash":"75e3ea64f642203943d6b9b65bbbdc3dc6b39b9bd2fbbcb09dfc25a6ccfdc089","addressRefs":[]},"71352327-3ea8-4a47-ae7e-5ccff35d5763":{"id":"71352327-3ea8-4a47-ae7e-5ccff35d5763","doc_no":"A.2.9.1.1.1.2.1","title":"Resilience Fund Technical Committee Selection And Compensation","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2110,"content":"The Support Facilitator selects the members of the Resilience Technical Committee and manages payments for their services on a project basis. The associated budget is defined in [A.2.9.1.1.1.1.1 - Resilience Fund Current Budget](aa1e93e5-8fc0-4e12-ad9d-8bb9f6cd8956).","contentHash":"f5cac5830b11c22044db0ee7c4ad9df71418f1e98990438baf1e82ca692a19af","addressRefs":[]},"ad242c8e-81e3-4590-b034-722b3767b9d2":{"id":"ad242c8e-81e3-4590-b034-722b3767b9d2","doc_no":"A.2.9.1.1.1.2.2","title":"Resilience Fund Technical Committee Member Requirements","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2111,"content":"The individual members of the Resilience Technical Committee who are directly involved in providing operational services on behalf of Sky must fulfill the requirements defined in the subdocuments herein.","contentHash":"22429bcd913cf4b2e2f8959b50450eb5406fc2b6a4508c07db0bc4836721ca0b","addressRefs":[]},"524ad7de-c3ee-4c5f-8c92-a5fdbb4aa29b":{"id":"524ad7de-c3ee-4c5f-8c92-a5fdbb4aa29b","doc_no":"A.2.9.1.1.1.2.2.1","title":"Resilience Fund Technical Committee Member Skill Set Requirement","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2112,"content":"Members of the Resilience Technical Committee must have relevant experience or current employment in the legal industry, or with a world-leading insurance broker, insurance company, or risk management firm.","contentHash":"18f5613a97973a8dd62835380c1829eccb5018de6565059fdb903b7d673d799c","addressRefs":[]},"d931273b-cdcb-40d3-97a5-d4bafcd38981":{"id":"d931273b-cdcb-40d3-97a5-d4bafcd38981","doc_no":"A.2.9.1.1.1.2.2.2","title":"Resilience Fund Technical Committee Member Experience Requirement","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2113,"content":"Members of the Resilience Technical Committee must have at least three (3) years of experience managing self-insurance instruments or experience in legal or regulatory risk analysis.","contentHash":"0a26e1243bfe7a47f2f1e0656b1a003bd1dadaacfb87cec764f774fd6adf35bc","addressRefs":[]},"19e4c5ce-1a9c-4df4-b8e7-5e22d27450b6":{"id":"19e4c5ce-1a9c-4df4-b8e7-5e22d27450b6","doc_no":"A.2.9.1.1.1.2.2.3","title":"Resilience Fund Technical Committee Member Professional Degree Requirement","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2114,"content":"Members of the Resilience Technical Committee must have a law, management, risk, or insurance professional degree.","contentHash":"9fad2ed41cbd0a37b819d490f3bfc0e4100477f5827312843b54a248612c8437","addressRefs":[]},"a7d9166a-6ac6-4592-a67c-19f1a59f9355":{"id":"a7d9166a-6ac6-4592-a67c-19f1a59f9355","doc_no":"A.2.9.1.1.1.2.2.4","title":"Resilience Fund Technical Committee Member No Conflicts Requirement","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2115,"content":"Members of the Resilience Technical Committee must not be involved in any business activity outside Sky or in any role within Sky that could result in a conflict of interest, either directly or indirectly.","contentHash":"07931fd85ab2fbdf5b47c73ba13dfdaa3b4f3b02da50c6cb24dbb59ff564999c","addressRefs":[]},"9f1b0abd-9000-4df7-8aa4-82a7234608ac":{"id":"9f1b0abd-9000-4df7-8aa4-82a7234608ac","doc_no":"A.2.9.1.1.1.2.2.5","title":"Resilience Fund Technical Committee Member Technology Experience Requirement","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2116,"content":"Members of the Resilience Technical Committee must have at least three (3) years of experience in the cryptocurrency, DeFi, Web3, or emerging technology sectors.","contentHash":"62714dc8d5af227a60f2bf89237c5decbd7b1a593db2feddedbc8b543059fd68","addressRefs":[]},"ab894e9e-b423-404b-8488-3d0578bbde28":{"id":"ab894e9e-b423-404b-8488-3d0578bbde28","doc_no":"A.2.9.1.1.1.2.3","title":"Resilience Fund Technical Committee Current Membership","type":"Active Data Controller","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2117,"content":"Approved Resilience Technical Committee members are defined as Active Data in [A.2.9.1.1.1.2.3.0.6.1 - Resilience Fund Technical Committee List Of Current Members](10b0e0aa-0338-40d7-b1e6-a29442c206e6).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Support Facilitators.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"adf0cedf8f062426bd98ab76e47a433468f12cb4801a77c569f09be1c5c464f5","addressRefs":[]},"10b0e0aa-0338-40d7-b1e6-a29442c206e6":{"id":"10b0e0aa-0338-40d7-b1e6-a29442c206e6","doc_no":"A.2.9.1.1.1.2.3.0.6.1","title":"Resilience Fund Technical Committee List Of Current Members","type":"Active Data","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2118,"content":"List of active Resilience Technical Committee Members:\n\n- Gallagher","contentHash":"01acf5ee65506dd36f191eaddace9a2a75482dc547254c0b3c66e248af98249c","addressRefs":[]},"bf8f69ef-6e55-47be-9203-02036a7f8c0d":{"id":"bf8f69ef-6e55-47be-9203-02036a7f8c0d","doc_no":"A.2.9.1.1.1.3","title":"Resilience Fund Policy","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2119,"content":"This provision and its subdocuments will govern the conditions and terms of use of the Resilience Fund.","contentHash":"a3b0fcdea35479f6a317ce8cdfe5386119e614774ecdffbc99a580e8faee6737","addressRefs":[]},"9cb0c1c3-269b-433b-ac03-de4b0bec43fb":{"id":"9cb0c1c3-269b-433b-ac03-de4b0bec43fb","doc_no":"A.2.9.1.1.1.3.1","title":"Resilience Fund Policy Loss Events","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2120,"content":"The Resilience Process covers legal defense or legal representation expenses incurred by a participant of the Sky Ecosystem when they are the defendant or respondent in a legal or regulatory action (\"The Loss Event\"). There must be a direct relationship between the legal or regulatory action and the Beneficiary’s activity at Sky.\n\nA (non-exhaustive) list of legal or regulatory actions that may qualify is:\n\n- Official requirements, or communications, from a regulatory body, governmental authority, or a court\n- Subpoenas\n- Lawsuit\n- Writs","contentHash":"c044f81e5a589ea06e2588d02ac74788ad462cdaf1946becfdbb5a3da595d577","addressRefs":[]},"b6f8e9a3-8e56-41fd-b760-a81834d4e214":{"id":"b6f8e9a3-8e56-41fd-b760-a81834d4e214","doc_no":"A.2.9.1.1.1.3.2","title":"Resilience Fund Policy Exclusions","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2121,"content":"The cases specified in the following subelements will generally be excluded from coverage by the legal defense process:\n\n- Prior or pending claims\n- Claims between persons involved in the Sky Ecosystem\n- Loss covered by other insurance\n- Willful criminal offenses, fraud, or dishonesty\n- Conflict of interest","contentHash":"acb1d054ef37070848e32705492481ac7727a2f3ec68dd7e4daffaaf3d667f70","addressRefs":[]},"8b3a5bf0-ac9a-4142-8fc6-dfcab8c385e9":{"id":"8b3a5bf0-ac9a-4142-8fc6-dfcab8c385e9","doc_no":"A.2.9.1.1.1.3.3","title":"Resilience Fund Policy Beneficiaries","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2122,"content":"Eligible beneficiaries of the Resilience Fund are persons who fulfill the following requirements:\n\na) act on their own behalf OR b) act on behalf of a legal entity OR c) act on behalf of a collective AND have one of the following roles:\n\nPrevious Structure:\n\n- Recognized Delegates\n- Core Unit Facilitators\n- Core Unit Contributors\n- Dai Foundation Board Members\n\nCurrent Structure:\n\n- Active SKY or Agent token holders that participate regularly in governance (e.g., voting, writing proposals)\n- Alignment Conservers\n- Aligned Delegates (ADs)\n- Facilitators\n- The Guardian ([A.2.9.1.1.3 - The Guardian](0f808bde-fc68-4bda-bc6d-049c6aaaab1b)) or actors that fulfill an equivalent role.","contentHash":"cc3f41a29c368c36c5353c5b39d7c94d8e807994901e738ee0cc9e5e3c95c35e","addressRefs":[]},"5b88e18f-dadc-47b2-af7c-e9ff8039d39e":{"id":"5b88e18f-dadc-47b2-af7c-e9ff8039d39e","doc_no":"A.2.9.1.1.1.3.3.1","title":"No Acquired Right Or Claim For Resilience Fund Policy Beneficiaries","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2123,"content":"Persons qualified as beneficiaries do not have any acquired right or claim. The claim decision process is described in [A.2.9.1.1.1.4 - Resilience Fund Processes And Principles](06aed112-2636-4478-b2c8-037808adc475), and the payout of a claim is subject to the approval of the Resilience Technical Committee (at their sole and absolute discretion) and further contingent on a SKY vote endorsing payment of the claim.","contentHash":"5ae2724a1f2f449a04efeae77978a318479952a0e83168a2a01674a0bf9e5260","addressRefs":[]},"3b1f2fc4-3d6c-445b-806b-1dbae77d8ad1":{"id":"3b1f2fc4-3d6c-445b-806b-1dbae77d8ad1","doc_no":"A.2.9.1.1.1.3.4","title":"Resilience Fund Policy Geographic Coverage","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2124,"content":"Geographical coverage is worldwide.","contentHash":"5a9928e4f9d3ce368cb3a35b33e39e89656b52775e02d72b907bae42c6adeb60","addressRefs":[]},"9de7d51b-32f3-4746-b97d-9eb75a189cb6":{"id":"9de7d51b-32f3-4746-b97d-9eb75a189cb6","doc_no":"A.2.9.1.1.1.3.5","title":"Resilience Fund Policy Effective Date","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2125,"content":"A Beneficiary’s eligibility for coverage under this Artifact will start after ratification of MIP106: 2023-03-27. (\"Effective Date\") and expire twenty-four (24) months after cessation of their role as a Beneficiary.","contentHash":"03440e3d4974418ed5c81d5a9593a477e9f91b84683a008eaa849e8d1ff84a0a","addressRefs":[]},"9204cca6-3e91-4a34-b8be-fa6135d41f24":{"id":"9204cca6-3e91-4a34-b8be-fa6135d41f24","doc_no":"A.2.9.1.1.1.3.6","title":"Resilience Fund Policy Base Of Coverage","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2126,"content":"Coverage is \"Claims made\". This means the Loss Event ([A.2.9.1.1.1.3.1 - Resilience Fund Policy Loss Events](9cb0c1c3-269b-433b-ac03-de4b0bec43fb)) must occur after the Effective Date ([A.2.9.1.1.1.3.5 - Resilience Fund Policy Effective Date](9de7d51b-32f3-4746-b97d-9eb75a189cb6)).\n\nThe facts and circumstances that originated the Loss Event may have occurred in the past for a maximum period of up to twenty-four (24) months before the date representing the later of (a) the Effective Date and (b) the date the Beneficiary is first eligible for coverage under this Artifact (the \"Retroactivity Period\").","contentHash":"e92c64e37bf37490921a10bf705f641425a66397aab463fe933b35a2c411a683","addressRefs":[]},"06aed112-2636-4478-b2c8-037808adc475":{"id":"06aed112-2636-4478-b2c8-037808adc475","doc_no":"A.2.9.1.1.1.4","title":"Resilience Fund Processes And Principles","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2127,"content":"Overview of the related processes and principles:\n\n- Application process\n- Claim management process\n- Caps and Exclusions\n- Refund of amounts to the Resilience Fund","contentHash":"5f8f64e35e534a6dfe14635a8a638f764e26ae49fd3867706548a7933e2d4cee","addressRefs":[]},"7ee909ce-ae6d-4886-a0ea-c3017eb00bcd":{"id":"7ee909ce-ae6d-4886-a0ea-c3017eb00bcd","doc_no":"A.2.9.1.1.1.4.1","title":"Resilience Fund Application Process","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2128,"content":"The Resilience Fund application process is defined in the subdocuments of this document.","contentHash":"b0cee0d6ed09beae8faeea73f6ce0ac4ba048500e31ba3244e89f1ba1bc77258","addressRefs":[]},"c14521ea-e2fa-4853-a5af-64f4c96a526a":{"id":"c14521ea-e2fa-4853-a5af-64f4c96a526a","doc_no":"A.2.9.1.1.1.4.1.1","title":"Resilience Fund Proof Of Eligibility","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2129,"content":"To become recognized as a Beneficiary, an Applicant must first select an Ethereum address that is linked to their activity at Sky (\"Proof of Eligibility\" or \"POE\"). Each Beneficiary type will have specific Proofs of Eligibility that are suitable for their role.\n\nValid PoE:\n\n- Address set as owner and used to sign transactions from Sky multisigs, such as Core Unit operational wallets, auditor wallets or SPFs (old structure), or a Facilitator multisig (Endgame Structure)\n    - PoE valid for former Core Unit Contributors, Core Unit Facilitators, and Scope Facilitators.\n- Address that voted directly or through delegation in at least ten Governance Polls or Executive Votes.\n    - PoE valid for active MKR or SKY holders, former Recognized Delegates (old structure), and Aligned Delegates (new structure)\n- Address that received compensation from Sky, with the following conditions:\n    - at least six (6) payouts spread over at least six (6) months in Dai or USDS OR\n    - Dai or USDS DssVest stream spanning at least six (6) months OR\n    - 3 MKR or SKY payouts spread over at least three (3) months OR\n    - MKR or SKY DssVest stream spanning at least three (3) months\n    - PoE valid for former Core Unit Contributors and Facilitators\n- Address that holds >1 MKR or >24,000 SKY\n- Attestation\n    - If no PoE is available, a verified Beneficiary must attest eligibility on behalf of the applicant.\n    - This PoE will be used exceptionally if no other Proof is available and will be assessed individually by the Resilience Fund Technical Committee.","contentHash":"09d92ca19eafd3667747ad512f41b794dab24eaade74586724bbb3b1e4f405dd","addressRefs":[]},"a457da07-943a-4d98-8153-db7b0eb55fe2":{"id":"a457da07-943a-4d98-8153-db7b0eb55fe2","doc_no":"A.2.9.1.1.1.4.1.2","title":"Resilience Fund Proof Of Eligibility Template","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2130,"content":"Applications for the Resilience Fund must follow this template:\n\n- .x: [Application RF]\n- .x.1: [PoE]\n- .x.2: [Active Period]\n- .x.3: [Relevant Executive Proposal: Governance decision ratified by a governance vote]\n- .x4: [Signature hash]","contentHash":"84ac9fd847dab142808866db3a7c85421e281c2419f5f3e2e564ebd24619d615","addressRefs":[]},"c83e0e76-f5b2-43f1-9bef-14c6571e72e2":{"id":"c83e0e76-f5b2-43f1-9bef-14c6571e72e2","doc_no":"A.2.9.1.1.1.4.1.3","title":"Resilience Fund Proof Of Eligibility Digital Signature","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2131,"content":"The Applicant for the Resilience Fund must additionally sign an application message from the Ethereum Address (Digital Signature) used as PoE [A.2.9.1.1.1.4.1.1 - Resilience Fund Proof Of Eligibility](c14521ea-e2fa-4853-a5af-64f4c96a526a).","contentHash":"92dc163c364d074abf490b40605efdf1cba33c96af3a422db21b58b21f3e35c9","addressRefs":[]},"0e430890-6911-4d22-98e7-f46eecb1ac24":{"id":"0e430890-6911-4d22-98e7-f46eecb1ac24","doc_no":"A.2.9.1.1.1.4.1.4","title":"Application Resilience Fund Application Terms And Conditions","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2132,"content":"By signing this message, the Applicant accepts and agrees:\n\n- To comply with the terms and rules of [A.2.9 - Legal Resilience](ac707ae4-65da-4cf9-8a34-8b9304cd9a95) (the \"Legal Resilience Fund Terms\").\n- That participation in the program is opt-in and voluntary and can be waived anytime by the Beneficiary.\n- The Legal Resilience Fund Terms can be amended at any time through the established governance processes.\n- That being registered as Beneficiary does not give rise to any right, benefit, entitlement, or claim, nor creates an obligation on any party to pay the Beneficiary.\n\nAdditionally, the Beneficiary declares that:\n\n- No situation currently involves or appears to involve a conflict of interest, and any emerging potential conflict of interest shall be disclosed as soon as it happens.\n- Any role change in Sky or termination of active engagement will be immediately communicated to the Resilience Technical Committee.\n\nThe Resilience Technical Committee will elaborate a user-friendly onboarding manual for the RF.","contentHash":"9e8f307e649a1a66be4357f4cb1ea3afd8361c39197a4224bebf30613258ee61","addressRefs":[]},"12bfa6fd-df07-4222-858c-11ae6b75509d":{"id":"12bfa6fd-df07-4222-858c-11ae6b75509d","doc_no":"A.2.9.1.1.1.4.1.5","title":"Resilience Fund Application Confirmation","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2133,"content":"The Applicant for the Resilience Fund will additionally send an encrypted message to the Resilience Technical Committee Member in charge of the onboarding process to confirm the application.","contentHash":"c2cf3a92dbebf9605439f7d9d9fa347382ad8f75188de01f975c950f2b94ef18","addressRefs":[]},"980b1bb1-3282-48ec-aff7-54107a580bf5":{"id":"980b1bb1-3282-48ec-aff7-54107a580bf5","doc_no":"A.2.9.1.1.1.4.1.6","title":"Resilience Fund Approval Process And Verifiability","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2134,"content":"PoEs rely on a governance decision that was ratified by an Executive Vote.\n\nThe Resilience Technical Committee Member must identify this governance decision by verifying the Spell that enacted the Executive Vote ratifying the respective governance decision. This Spell contains the hash of the respective Executive Vote. Exceptional circumstances where no direct governance decision is available or difficult to assert will be handled case by case.\n\nThe Resilience Technical Committee Member will confirm the onboarding decision via an encrypted message to the Applicant.","contentHash":"c129395e4d4fa12506c706229f3b435fc54f45d2d76df2ab55671910cebdd5a3","addressRefs":[]},"9ab8fdf3-939c-4096-a0b9-9d9486d5a339":{"id":"9ab8fdf3-939c-4096-a0b9-9d9486d5a339","doc_no":"A.2.9.1.1.1.4.2","title":"Resilience Fund Claim Management Process","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2135,"content":"Overview of the claim management processes:\n\n- Legal Counsel Pre-approval\n- Claim approval / Advance Payment\n- Reimbursement","contentHash":"544cfb2af6ef389271b301a8e263dd7bebf33e772cc407f947671e05487acd96","addressRefs":[]},"49ecea76-a16d-4135-88db-ccd554866715":{"id":"49ecea76-a16d-4135-88db-ccd554866715","doc_no":"A.2.9.1.1.1.4.2.1","title":"Resilience Fund Legal Counsel And Quote Pre-Approval","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2136,"content":"The first step in the claim management process is to approve the Legal Counsel to undertake legal defense or representation and the quote presented to commence legal work. The Beneficiary must present the quote from the law firm they selected for their legal defense/representation. The request must indicate at least the following:\n\n- Name of Legal Counsel\n- Name of Law Firm\n- If not in the Lawyer Registry, Proof of Eligibility\n- Quote\n\nThe quote must include:\n\n1. The initial payment required by Counsel to commence work immediately. This is the initial amount to be claimed against the Resilience Fund.\n2. A global estimated fee based on an hourly rate OR fixed fee OR monthly retainer fee.","contentHash":"caab1872e106ec1aaa54285dd09d895520207d1ba6da286a1cf878dcbd43c6be","addressRefs":[]},"bdb4beda-794e-42e6-a9d0-06632235c478":{"id":"bdb4beda-794e-42e6-a9d0-06632235c478","doc_no":"A.2.9.1.1.1.4.2.1.1","title":"Resilience Fund Qualified Counsel","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2137,"content":"If the Legal Counsel is RF-qualified in the Lawyer Registry ([A.2.9.1.1.2 - Lawyer Registry](4c327b04-48f7-4941-b996-1c629eb42bf7)), the claim is automatically submitted to the Claim Approval process ([A.2.9.1.1.1.4.2.2 - Resilience Fund Claim Approval](d9cd69ff-88ed-4869-9ca7-ff87ce8f1ff6)).","contentHash":"1b865d81916524baed0ec36d6d148bbd80d5c21b03d37328f0a90231b4baa12c","addressRefs":[]},"9f423880-3184-4172-9ac5-6e8a371f5bb0":{"id":"9f423880-3184-4172-9ac5-6e8a371f5bb0","doc_no":"A.2.9.1.1.1.4.2.1.2","title":"Not Resilience Fund Qualified Counsel","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2138,"content":"If Legal Counsel is NOT RF-qualified in the Lawyer Registry ([A.2.9.1.1.2 - Lawyer Registry](4c327b04-48f7-4941-b996-1c629eb42bf7)), then the Support Facilitators, or alternatively the Resilience Fund Technical Committee Member, will verify if the Legal Counsel complies with requisites in Lawyer Registry Acceptance Criteria and LR Resilience Fund Acceptance Criteria. See: [A.2.9.1.1.2.2 - Lawyer Registry Acceptance Criteria](2b66ce16-d104-4238-b7d5-e4c6fe8d961b) and [A.2.9.1.1.2.3 - Resilience Fund Representation Requirements](b39f4808-18ae-456b-86fc-d449a69ea99a).\n\nIf the Legal Counsel of the quote is determined by the Resilience Technical Committee to comply with the requirements of this Artifact, the quote is pre-approved and the legal counsel is added to the LR.\n\nIf the Legal Counsel doesn’t comply with the LR requirements, the claim is rejected and the Beneficiary must propose a different Legal Counsel.","contentHash":"ef06a63059fc7c019214ca91cdcc581a3657e90b9a5fefd6276bfd025245e3b3","addressRefs":[]},"d9cd69ff-88ed-4869-9ca7-ff87ce8f1ff6":{"id":"d9cd69ff-88ed-4869-9ca7-ff87ce8f1ff6","doc_no":"A.2.9.1.1.1.4.2.2","title":"Resilience Fund Claim Approval","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2139,"content":"If a Beneficiary incurs a Loss Event, they can submit a Reimbursement Payout Claim against the LD RF according to the process specified in the subdocuments herein.","contentHash":"b7a3d92663f7da9f901a0e2ae8aaae3ccc0998992c39c13d7972767e782e14a3","addressRefs":[]},"d47f9aa8-96d1-4be7-910c-505693b1784a":{"id":"d47f9aa8-96d1-4be7-910c-505693b1784a","doc_no":"A.2.9.1.1.1.4.2.2.1","title":"Resilience Fund Claim Approval Payout Claim","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2140,"content":"The Support Facilitator must review the Reimbursement Claim and decide whether to trigger a Governance Poll to perform a claims payout, by developing an internal model with input from experts and professionals.\n\nThe Payout Reimbursement Claim must contain the following elements:\n\n- Description of Loss Event with relevant commentaries and context\n- Advance Payment or Reimbursement\n- Type of process\n- Date of writ/subpoena/lawsuit\n- Supportive Documentation\n    - Law firm’s proposal and invoice OR quote\n    - Copy of the Lawsuit/writ/ communication OR official requirement issued by a Court or Governmental Agency Supportive documentation is highly sensible. It is required to use encryption tools.","contentHash":"d30222190d8ae1f74664e9bb0c06f9c37b808df1663c2c1252f329e20e5935ff","addressRefs":[]},"fe131e29-a159-453e-a3e0-7577af4e147b":{"id":"fe131e29-a159-453e-a3e0-7577af4e147b","doc_no":"A.2.9.1.1.1.4.2.2.2","title":"Resilience Fund Claim Approval Coverage Framework","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2141,"content":"In consultation with the Resilience Technical Committee, the Support Facilitators must develop a framework for establishing limits and coverage amounts per case, and apply these limits to individual claims.","contentHash":"d5f6ff2cb605f3e7a9e62fbb3d90a6ab30e5bf6296e2c81c48a2b58e74704d79","addressRefs":[]},"26044d1d-f92c-4945-9a1c-4907c56d4038":{"id":"26044d1d-f92c-4945-9a1c-4907c56d4038","doc_no":"A.2.9.1.1.1.4.2.2.3","title":"Resilience Fund Claim Approval Support Facilitators Review","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2142,"content":"The Support Facilitators will review the Payout Claim and if it contains all required elements and supportive documentation, will immediately transmit it to the Resilience Fund Technical Committee.","contentHash":"3ca01f64f690b3f232c8cc1c26a4b4cad4396a2d12555dcc6f048b6e57bbaa68","addressRefs":[]},"07cd5714-47aa-46ef-a162-ab96875631d6":{"id":"07cd5714-47aa-46ef-a162-ab96875631d6","doc_no":"A.2.9.1.1.1.4.2.2.4","title":"Resilience Fund Claim Approval Technical Commitee Review","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2143,"content":"The Resilience Fund Technical Committee will verify the merits of the claim according to the following substantial criteria (non-exhaustive list):\n\n- Absence of Exclusions\n- Identity and Role of Beneficiary\n- Time scope\n- Authenticity of writ/lawsuit\n- Reasonability of lawyer fees, which must take into account market rates in the respective jurisdiction","contentHash":"7baffb0f7e60a5f4531466f3dbc499f57ce44600668760ce6eb0e0605320dd46","addressRefs":[]},"313d72e5-62db-4dd4-b125-97467508f44c":{"id":"313d72e5-62db-4dd4-b125-97467508f44c","doc_no":"A.2.9.1.1.1.4.2.2.5","title":"Resilience Fund Claim Approval Technical Committee Review Process","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2144,"content":"From the moment the Payout Claim is filed, the Resilience Technical Committee will have five (5) working days to provide a payout recommendation. The recommendations of the Technical Committee are made in their sole and absolute discretion, are definitive, and are not subject to appeal.","contentHash":"b3025e1be68c0aa919d1191c4bbf4a8122eda2ece40c1bb9472cbadde9954b25","addressRefs":[]},"10662753-b167-4043-b952-225cc9dd9e49":{"id":"10662753-b167-4043-b952-225cc9dd9e49","doc_no":"A.2.9.1.1.1.4.2.2.6","title":"Resilience Fund Claim Approval Quorum And Decision Majorities","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2145,"content":"Decisions related to claim payouts require a quorum of three (3) experts from the Resilience Technical Committee with a simple majority (>50%).","contentHash":"007e6898b5bc2def84f15ac6fcec7f6e475d3f335269ab8040fe97c0796b6af7","addressRefs":[]},"99079da7-e8e9-4660-96a6-269625d821cc":{"id":"99079da7-e8e9-4660-96a6-269625d821cc","doc_no":"A.2.9.1.1.1.4.2.2.7","title":"Resilience Fund Claim Approval Decision Protections","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2146,"content":"The recommendations of the Resilience Technical Committee are non-binding and will not give rise to any right or claim to the beneficiaries nor give rise to any obligation or responsibility.","contentHash":"92f315bc506570152b17154e47cd2ce5cb76d99c0f57c533abc8ee0c1d1bc30d","addressRefs":[]},"bf63fc62-3555-4b9b-a561-053fb35721b5":{"id":"bf63fc62-3555-4b9b-a561-053fb35721b5","doc_no":"A.2.9.1.1.1.4.2.2.8","title":"Resilience Fund Claim Approval Support Facilitators Decision","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2147,"content":"Based on the recommendation of the Resilience Technical Committee, the Support Facilitators will decide whether to trigger a Governance Poll through the Weekly Governance Cycle to perform a claim payout.","contentHash":"6b7546ab0d84537a2e3397cac79a57af1ce7f3d5bbe1eab2847d5029bd71c3d3","addressRefs":[]},"9edd8feb-790b-42de-bf42-ba5d6550df1c":{"id":"9edd8feb-790b-42de-bf42-ba5d6550df1c","doc_no":"A.2.9.1.1.1.4.2.3","title":"Resilience Fund Payout / Reimbursement","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2148,"content":"If the Governance Poll for paying out a claim is successful, an Executive Vote must be created and approved through Sky Governance processes to draw the funds from the Surplus Buffer and send them to the Beneficiary’s registered wallet. The spend must be accounted for in the budget in [A.2.9.1.1.1.1.1 - Resilience Fund Current Budget](aa1e93e5-8fc0-4e12-ad9d-8bb9f6cd8956).","contentHash":"901074343972d994c31b64675999be7309d34ee2835466d3ccee74eefe7372ff","addressRefs":[]},"e99c4433-e55b-49b1-b73a-8bc1ae3a56b6":{"id":"e99c4433-e55b-49b1-b73a-8bc1ae3a56b6","doc_no":"A.2.9.1.1.1.4.3","title":"Resilience Fund Caps And Exclusions","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2149,"content":"Unless otherwise approved by a governance vote of Sky, claim funds approved under this Section are subject to the caps and exclusions specified in the subdocuments of this document.","contentHash":"9ddde800f8562a7beeb17abe55e9903a41a67403335fdccf17d30cdd79cb6c62","addressRefs":[]},"327407b2-9c87-4d7a-b772-1a61ac9d2da3":{"id":"327407b2-9c87-4d7a-b772-1a61ac9d2da3","doc_no":"A.2.9.1.1.1.4.3.1","title":"Resilience Fund Aggregate Cap","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2150,"content":"Claims will be subject to an aggregate cap for all claims in relation to a Claim Event determined by the risk models elaborated by the Resilience Technical Committee.","contentHash":"1136abe74dc33cb658655e40348c15cbe56c956319ba91cb2e864f290532956a","addressRefs":[]},"c103cdb7-0213-492f-b900-96175ac89e5b":{"id":"c103cdb7-0213-492f-b900-96175ac89e5b","doc_no":"A.2.9.1.1.1.4.3.2","title":"Resilience Fund Direct Costs And Legal Expenses Cap","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2151,"content":"Claims can only be used to reimburse Beneficiaries for their losses and disbursements directly arising from a Claim Event, and reasonable legal expenses. \"Reasonable legal expense\" is a variable amount that will be determined taking into account the average market rates of the respective jurisdiction.","contentHash":"74aafc9a3b034dc5b168e4d8c858ed47896828f0cd95b21b81acd9a0b1d7cf39","addressRefs":[]},"f44b8c82-f420-4d14-ad89-8b885408e10e":{"id":"f44b8c82-f420-4d14-ad89-8b885408e10e","doc_no":"A.2.9.1.1.1.4.3.3","title":"Resilience Fund Caps Government Or Regulatory Fines Or Damages Exclusion","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2152,"content":"Must not be used to reimburse the payment of government or regulatory fines or damages awarded by the court.","contentHash":"f12cc4d57db5f3a389c097474588ad9b732c465388b000fe027ee40a28acc9b4","addressRefs":[]},"608f5fd0-f441-47b2-8775-4f8b019e8c41":{"id":"608f5fd0-f441-47b2-8775-4f8b019e8c41","doc_no":"A.2.9.1.1.1.4.4","title":"Refund Of Amounts To Resilience Fund","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2153,"content":"Where Beneficiaries receive financial benefit or reimbursement of any type as a result of orders of a court, governmental or investigative body or regulatory agency that results in a windfall to the Beneficiary, these windfall amounts will be returned by the Beneficiary to the Resilience Fund within 14 days of receipt.","contentHash":"d0d28bcd15cf8513e9889d37e242da20a8e780d7f958f9689cfd5a5c17b1bcc1","addressRefs":[]},"6855b494-f493-4dad-a7be-a43a17959016":{"id":"6855b494-f493-4dad-a7be-a43a17959016","doc_no":"A.2.9.1.1.1.4.4.1","title":"Refund Of Amounts To Resilience Fund Examples","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2154,"content":"By way of example only and without limiting the generality of the principle described in [A.2.9.1.1.1.4.4 - Refund Of Amounts To Resilience Fund](608f5fd0-f441-47b2-8775-4f8b019e8c41), such amounts include, without limitation:\n\n- Amounts awarded by a court towards the Beneficiary’s legal fees or disbursements;\n- An award of damages to a Beneficiary in relation to a Claim Event;\n- Monies or digital assets located by police or other investigative bodies that were identified as the property of Sky; and\n- Interest payable to a Beneficiary in relation to a Claim Event.","contentHash":"4715e3087aac0539ab23d78033e39bffbc40c65a44a42e405814483e1e3c0950","addressRefs":[]},"cb5e73d2-0b65-4465-94db-eb70fb8c814c":{"id":"cb5e73d2-0b65-4465-94db-eb70fb8c814c","doc_no":"A.2.9.1.1.1.4.5","title":"Resilience Fund Litigation / Defense Management","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2155,"content":"Beneficiaries and their legal teams must, in the conduct of the litigation and as a condition of receiving reimbursement from the Resilience Fund, satisfy all of the conditions listed in the subdocuments of this document.","contentHash":"026c338b0efcf95107daa881cc125e201d228c866e4f0c583df9dfc5453173d0","addressRefs":[]},"4ca172c5-b48c-4e62-8b23-055573cb2376":{"id":"4ca172c5-b48c-4e62-8b23-055573cb2376","doc_no":"A.2.9.1.1.1.4.5.1","title":"Good Faith In Resilience Fund Litigation / Defense Management","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2156,"content":"Beneficiaries and their legal teams must act honestly, consistently, and fairly in handling claims and litigation.","contentHash":"dccaddf5c04d5af2628e58ac27925587b25cedb52096ee5ee4224c27426c9bfd","addressRefs":[]},"2981a7cf-cdc2-4967-816b-dcbbc21f3ee8":{"id":"2981a7cf-cdc2-4967-816b-dcbbc21f3ee8","doc_no":"A.2.9.1.1.1.4.5.2","title":"Promptness In Resilience Fund Litigation / Defense Management","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2157,"content":"Beneficiaries and their legal teams must make an early assessment of the prospects of success and deal with claims promptly.","contentHash":"54156e8731922dfdd01b18805666ec967c017312bdc8d03537b34d57e6d22330","addressRefs":[]},"455bd317-a36c-48ba-9c34-0034b824b3e4":{"id":"455bd317-a36c-48ba-9c34-0034b824b3e4","doc_no":"A.2.9.1.1.1.4.5.3","title":"Cost Control In Resilience Fund Litigation / Defense Management","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2158,"content":"Beneficiaries and their legal teams must keep costs to a minimum and avoid reliance on technical defenses which have low probability of success.","contentHash":"55cfaed34ddec76b7944fed171eb5b03ba4c9ba63b42b054ec6c3ea34b5d949c","addressRefs":[]},"c7222199-c81b-4d67-b7c1-044391c288d5":{"id":"c7222199-c81b-4d67-b7c1-044391c288d5","doc_no":"A.2.9.1.1.1.4.5.4","title":"Alternative Dispute Resolution In Resilience Fund Litigation / Defense Management","type":"Core","depth":6,"parentId":"ccd36a29-af79-4994-93b4-b07d150b0366","order":2159,"content":"Beneficiaries and their legal teams must consider alternative dispute resolution (ADR) options at all times.","contentHash":"c26c65b64527beb407cbe1ba60097081c1c2bf8446a7eb81f1cd7122c1f6431a","addressRefs":[]},"4c327b04-48f7-4941-b996-1c629eb42bf7":{"id":"4c327b04-48f7-4941-b996-1c629eb42bf7","doc_no":"A.2.9.1.1.2","title":"Lawyer Registry","type":"Core","depth":5,"parentId":"8f2eb896-4736-4649-a054-1c76dae64dc6","order":2160,"content":"The Lawyer Registry (also \"LR\") is a registry of specialized Ecosystem Actors who are qualified to perform legal work for Sky Ecosystem or participants in the Sky Ecosystem, including, but not limited to, legal representation or legal defense.\n\nLawyers will be onboarded in the Lawyer Registry covering at least the areas specified in [A.2.9.1.1.2.1 - Lawyer Registry Covered Areas](a176f67f-009f-44a0-a19b-169c2eb376a4).","contentHash":"05f87357efa4b60aff726e604f1eb31abf389fc64f3622a16b68b20b9fe6b3f7","addressRefs":[]},"a176f67f-009f-44a0-a19b-169c2eb376a4":{"id":"a176f67f-009f-44a0-a19b-169c2eb376a4","doc_no":"A.2.9.1.1.2.1","title":"Lawyer Registry Covered Areas","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2161,"content":"```\n| Category                         | Areas of Law                                         | Examples                                                                                                          |\n|----------------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|\n| Disputes/Investigations          | Regulatory Enforcement – Securities/Finance Law      | SEC/FinCEN/CFTC/Central Bank matters, Tax authority actions, OFAC orders, Sanctions                               |\n|                                  | Securities Law Disputes (private party claims, class actions, etc.) | Sky investor claims, Lawsuits against Sky CORE actors                                                            |\n|                                  | Intellectual Property                                | Patent Claims/Trolls, Trademark Claims/Trolls                                                                     |\n|                                  | General Litigation – Any other Party-Party Disputes  | Disputes between Sky and 3rd party suppliers, Breach of contract disputes, Employment law disputes, Disputes between Sky and Ecosystem actors |\n| Commercial Matters (non-litigious) | Commercial and Contracts                            | Commercial transactions (Audits, listing agreements, inter-Agent agreements affecting Sky Core etc.), Contracts and Procurement (includes contract management), Competition/Anti-Trust Law, Data protection and Privacy, Insurance Law |\n|                                  | Intellectual Property, Information Technology        | IT procurement, licenses, and contracts, Convergent technologies, Intellectual property rights, Data protection and privacy, Trademark/Patent applications |\n|                                  | Corporate Structuring, Entity Formation/Reporting, Corporate Financing and Tax | Entity formation assistance provided to Sky Core, Annual Reporting/Filings, Company Law, Corporate Finance, Tax Law |\n```","contentHash":"9c7e4a156d4797739d720666be7315b609c48002780d010fd5b22d94c8a53401","addressRefs":[]},"2b66ce16-d104-4238-b7d5-e4c6fe8d961b":{"id":"2b66ce16-d104-4238-b7d5-e4c6fe8d961b","doc_no":"A.2.9.1.1.2.2","title":"Lawyer Registry Acceptance Criteria","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2162,"content":"To be included in the Lawyer Registry, lawyers must satisfy all requirements described in the following subelements.","contentHash":"0f28c650fda9b9dc79183d3f25a2c93baaf1ba6a3d86dffd9cda66c05c025e0c","addressRefs":[]},"fd8dec1d-6872-439d-b30a-eb4d39e2310b":{"id":"fd8dec1d-6872-439d-b30a-eb4d39e2310b","doc_no":"A.2.9.1.1.2.2.1","title":"Lawyer Registry Licensing Criterion","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2163,"content":"Licensed legal professionals in their respective jurisdiction.","contentHash":"d413e0a5d622c9e8429d32160b36f66b5b9ebde3b918f6251e9fa64f08e01d68","addressRefs":[]},"bbe5b615-0bfd-4dd4-b6a8-bae4af500261":{"id":"bbe5b615-0bfd-4dd4-b6a8-bae4af500261","doc_no":"A.2.9.1.1.2.2.2","title":"Lawyer Registry Technology Experience Criterion","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2164,"content":"Proven experience with Sky Ecosystem crypto, or emerging technologies.","contentHash":"8ab3a45a9192d6d273fc71a83b83e89074ef202ac3946917127e7896d677694a","addressRefs":[]},"e74ab7b2-273e-4593-aee5-38af6c45dba6":{"id":"e74ab7b2-273e-4593-aee5-38af6c45dba6","doc_no":"A.2.9.1.1.2.2.3","title":"Lawyer Registry No Conflicts Criterion","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2165,"content":"No Conflict of Interest in the matter over which they have carriage.","contentHash":"6870840eb29245fcc2713bf5b752553313bb81ba4b5ca1fdd31e58b99f2f2637","addressRefs":[]},"e9fd410d-7bf4-483c-b6bf-2206dbb8c513":{"id":"e9fd410d-7bf4-483c-b6bf-2206dbb8c513","doc_no":"A.2.9.1.1.2.2.4","title":"Lawyer Registry Conflict Checks Criterion","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2166,"content":"Lawyers must have internal processes to conduct conflict checks prior to any engagement under this Section.","contentHash":"5570393f4f9518e9aa7248474867153c94405521260fcf4870e3f12b49ebbc07","addressRefs":[]},"d2581c75-828d-46dc-aac2-e2ae6ffd4e57":{"id":"d2581c75-828d-46dc-aac2-e2ae6ffd4e57","doc_no":"A.2.9.1.1.2.2.5","title":"Lawyer Registry Conflict Handling Criterion","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2167,"content":"Where conflicts arise within the lawyer’s firm, the firm must:\n\n1. In the case where a Beneficiary is handling the claim, cease all further work and immediately notify the Resilience Technical Committee in writing and cooperate with the Resilience Technical Committee to avoid a continuing conflict or, where this is not practicable, transfer the matter to another LR registered Lawyer, and\n2. In the case where the Guardian is handling the claim, cease all further work and immediately notify the Guardian in writing and cooperate with the Guardian to avoid a continuing conflict or, where this is not practicable, transfer the matter to another LR registered Lawyer.","contentHash":"0d1af4e740030577cbab3bbb0b85e45c4dfdadf4bc94a16c879005986546fa4f","addressRefs":[]},"b39f4808-18ae-456b-86fc-d449a69ea99a":{"id":"b39f4808-18ae-456b-86fc-d449a69ea99a","doc_no":"A.2.9.1.1.2.3","title":"Resilience Fund Representation Requirements","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2168,"content":"Legal counsel providing services funded through the RF must fulfill additional requirements specified in the subdocuments herein. Legal counsel qualified for RF will be listed as such in the Lawyer Registry.","contentHash":"f295957e881e98dbcc6f69d436a3fe2e239a6e4c641adcdb200586d8db587508","addressRefs":[]},"04852c06-a9c0-4775-a891-1fd8946083a7":{"id":"04852c06-a9c0-4775-a891-1fd8946083a7","doc_no":"A.2.9.1.1.2.3.1","title":"Resilience Fund Representation Experience Requirement","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2169,"content":"Lead Counsel, Lead Barristers, and Lead Trial Attorneys (as applicable) must each have a minimum of ten (10) years of relevant legal experience and demonstrable expertise in the specific areas of law, legal processes, and jurisdictions listed on the Lawyer Registry.","contentHash":"c6610cf784093c5f2e40308f2019e0449c2ce64ce359c17048e7f4f9386249b3","addressRefs":[]},"23612175-bf87-4c2a-b295-a46900a36bbd":{"id":"23612175-bf87-4c2a-b295-a46900a36bbd","doc_no":"A.2.9.1.1.2.3.2","title":"Resilience Fund Representation Expertise Requirement","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2170,"content":"Lawyers included on the Lawyer Registry for litigious categories, must have been Lead Counsel in at least 15 cases in the relevant area of law, type of process, and jurisdiction for which they are listed. Lawyers included on the Lawyer Registry for non-litigious matters must have demonstrable experience in the relevant area of law, type of process and jurisdiction indicated in the table set out under [A.2.9.1.1.2.1 - Lawyer Registry Covered Areas](a176f67f-009f-44a0-a19b-169c2eb376a4).","contentHash":"42a39cb7bb9e3329864c5129d0d834ff3dcba67966a58b5c971e482d6ac07d5e","addressRefs":[]},"d4bc5f95-a5a8-4f55-8db8-eb9f30cc0abf":{"id":"d4bc5f95-a5a8-4f55-8db8-eb9f30cc0abf","doc_no":"A.2.9.1.1.2.4","title":"Lawyer Registry Template","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2171,"content":"Entries in the LR must follow this template:\n\n- .x: [Advisor name and short description]\n- .x.1: [Name of Firm]\n- .x.2: [Specialization Area]\n- .x.3: [Jurisdiction]\n- .x.4: [RF qualified (y/n)]","contentHash":"9336cda27ce1cbaab4fcac742a3ec13206cfb54066e10dbea213d7c568394714","addressRefs":[]},"ba0f1c77-3fe8-45b5-bb5b-1bc84a3a5f8f":{"id":"ba0f1c77-3fe8-45b5-bb5b-1bc84a3a5f8f","doc_no":"A.2.9.1.1.2.5","title":"Requirements For Resilience Technical Committee","type":"Core","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2172,"content":"The Resilience Technical Committee will verify the eligibility criteria of new candidates in the Lawyer Registry and submit a list of approved candidates to the Support Facilitators.","contentHash":"09c5059792e73f404518864375426a5f8983ceb0972aaece005be8071511c776","addressRefs":[]},"2e3f851c-6ee2-472a-aa4f-cf637ff1cd8a":{"id":"2e3f851c-6ee2-472a-aa4f-cf637ff1cd8a","doc_no":"A.2.9.1.1.2.6","title":"Lawyer Registry Update Process","type":"Active Data Controller","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2173,"content":"The current approved lawyers in the Lawyer Registry are defined as Active Data in [A.2.9.1.1.2.6.0.6.1 - Lawyer Registry Current Approved Legal Counsels](e1f72c98-e3f7-43b5-857c-82294abbbe09).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Support Facilitators.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"368da5b71e58885baa7943720a9ce0a920090877be209ff3baac141f562c1e69","addressRefs":[]},"e1f72c98-e3f7-43b5-857c-82294abbbe09":{"id":"e1f72c98-e3f7-43b5-857c-82294abbbe09","doc_no":"A.2.9.1.1.2.6.0.6.1","title":"Lawyer Registry Current Approved Legal Counsels","type":"Active Data","depth":6,"parentId":"4c327b04-48f7-4941-b996-1c629eb42bf7","order":2174,"content":"There are no active legal counsels in the Lawyer Registry.","contentHash":"ea8acd86f99a82b5810db2ffbd8db55cc7aec54ec3bb5e65e17c85f85f9cafa5","addressRefs":[]},"0f808bde-fc68-4bda-bc6d-049c6aaaab1b":{"id":"0f808bde-fc68-4bda-bc6d-049c6aaaab1b","doc_no":"A.2.9.1.1.3","title":"The Guardian","type":"Core","depth":5,"parentId":"8f2eb896-4736-4649-a054-1c76dae64dc6","order":2175,"content":"The Guardian is a specialized Ecosystem Actor that will be exclusively mandated to retain and instruct counsel to assist with the legal defense of actors in the Sky Ecosystem that, due to their organizational structure or circumstances, may be unable to obtain legal representation when pursuing or defending claims against adversarial parties.","contentHash":"17ccf4ac9ec98c5730b22f03409f04bd1f47cf1a4f74d383315cc36642a8a4a1","addressRefs":[]},"bd82af2f-6617-4d4e-8acb-e23c7d2c904b":{"id":"bd82af2f-6617-4d4e-8acb-e23c7d2c904b","doc_no":"A.2.9.1.1.4","title":"Legal Defense Standard Operational Protocols","type":"Core","depth":5,"parentId":"8f2eb896-4736-4649-a054-1c76dae64dc6","order":2176,"content":"This document must define the Standard Operational Protocols (SOPs) for reacting against legal or regulatory actions against a participant of the Sky Ecosystem.","contentHash":"1f4467124dccd76fd0a4b8e7e573bf440ec7aa1badb6ad4996a6b09401810ade","addressRefs":[]},"f50b0f4d-05c3-48ef-9073-997c9f678feb":{"id":"f50b0f4d-05c3-48ef-9073-997c9f678feb","doc_no":"A.2.9.1.2","title":"Legal Risk Management","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2177,"content":"This document defines the framework for managing, retaining, transferring, and structuring legal risk through instruments such as self-insurance and insurance.","contentHash":"cd928bfc82cf7d5c53707bae2640e3a350a366f7a3a93e721345fdf6092bd3bf","addressRefs":[]},"fbc37039-df17-4146-9cbc-69dbc13c1d85":{"id":"fbc37039-df17-4146-9cbc-69dbc13c1d85","doc_no":"A.2.9.1.2.1","title":"The Policyholder","type":"Core","depth":5,"parentId":"f50b0f4d-05c3-48ef-9073-997c9f678feb","order":2178,"content":"The Policyholder is a specialized Ecosystem Actor in charge of executing agreements with external entities with the exclusive purpose of structuring and transferring risk to third parties through instruments such as insurances, reinsurances, mutuals, or other types of arrangements. These instruments will provide extended risk coverage for participants of the Sky Ecosystem and Agents.\n\nThe object of the Policyholder is to\n\n- Act as a legal counterparty with insurance brokers, insurance, reinsurance, underwriters, or risk management companies.\n- Act as a policyholder of insurance contracts, which will have as beneficiaries participants of the Sky Ecosystem.\n- Hire suppliers and contractors necessary for the operation of self-insurance or insurance instruments, such as\n    - The Resilience Technical Committee for claim management\n    - Managers, Directors, and other executive staff of the legal vehicle. The power of directors will be limited to administrative and operative roles.\n\nSky Governance will have all necessary control mechanisms over the Policyholder:\n\n- Sky Governance can designate and remove Directors, Supervisor, and Committees\n- Sky Governance can instruct the entity to act and ratify decisions\n- Power of directors is limited to administrative/operative roles\n- The Policyholder will not manage Sky's assets nor will be legally affiliated with Sky.\n\nThe setup and operational budget of the legal vehicle will be sourced initially from the [A.2.9.1.1.1.1.1 - Resilience Fund Current Budget](aa1e93e5-8fc0-4e12-ad9d-8bb9f6cd8956). This is intended to move later to a separate budget.","contentHash":"91a7ddf48739829375278789411bf72dcc33e913b9ba4fcaa3597d4a15d627cf","addressRefs":[]},"b376e933-f145-42a6-ac8b-462b6dbce497":{"id":"b376e933-f145-42a6-ac8b-462b6dbce497","doc_no":"A.2.9.1.2.2","title":"Policyholder Management","type":"Core","depth":5,"parentId":"f50b0f4d-05c3-48ef-9073-997c9f678feb","order":2179,"content":"This document governs the adding and removing of Policyholders. SKY holders must first approve the structure and associated costs of the Policyholder, based on a Governance Poll initiated by Facilitators if they deem it necessary.\n\nThe list of currently approved Policyholders is maintained in [A.2.9.1.2.3 - Current Active Policyholders](6db0f9ee-9011-44da-8b75-521218f91aba).","contentHash":"3340792463044bd56722e496d52e1ed797588fab4789c2091426caf0e2c88c75","addressRefs":[]},"6db0f9ee-9011-44da-8b75-521218f91aba":{"id":"6db0f9ee-9011-44da-8b75-521218f91aba","doc_no":"A.2.9.1.2.3","title":"Current Active Policyholders","type":"Core","depth":5,"parentId":"f50b0f4d-05c3-48ef-9073-997c9f678feb","order":2180,"content":"There are currently no active Policyholders.","contentHash":"1358f7ef1477cd6ff82608b6c5cfc2e68e1435873d2341fea1e9c4f744dd85e0","addressRefs":[]},"42c525ca-c541-4bf5-ac6a-7bd19960d583":{"id":"42c525ca-c541-4bf5-ac6a-7bd19960d583","doc_no":"A.2.9.1.3","title":"Privacy and Operational Security","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2181,"content":"This document must define policies pertaining to operational security, privacy, and pseudonymity for participants in the Sky Ecosystem. The general purpose of this framework is to maximize security and safety for contributors and users and minimize potential attack vectors for the Ecosystem.","contentHash":"8ceda9b8675d4b68ef43d2d33bd9779adf7ed67758b2895669bb15a4cb438ab5","addressRefs":[]},"336b0e21-d62a-49d3-9179-14f467b7609c":{"id":"336b0e21-d62a-49d3-9179-14f467b7609c","doc_no":"A.2.9.1.4","title":"Advocacy And Public Policy","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2182,"content":"This document defines the framework and processes for public policy, advocacy, and governmental relations. The general purpose of this framework is to develop innovative regulatory frameworks and standards that protect open source resources and position the Public Good Purpose of the Sky Ecosystem.","contentHash":"118b330d79a16aa57e805e5275681ef98744c4a7a0337b9593e1ff0c066ff918","addressRefs":[]},"035ec13b-5676-45f0-a3b3-8b8e24a4adcf":{"id":"035ec13b-5676-45f0-a3b3-8b8e24a4adcf","doc_no":"A.2.9.1.5","title":"Legal And Regulatory Risk Monitoring","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2183,"content":"This document defines the general framework and standard processes for monitoring and assessing risk and implementing responses. Risk assessment will include external/jurisdictional risk monitoring and internal risk monitoring.\n\nResponses will be structured as Standard Operational Protocols (SOPs). The categories of Legal and Regulatory Risk Monitoring responses are:\n\n- Preventive responses that reduce the likelihood of occurrence of a risk event\n- Reactive responses that reduce the severity of consequences if the risk event materializes.\n- Emergency Responses and Contingency Plans.","contentHash":"a74d81646fa9a951de2cfba2a0167b04a54323bed4de11678f159823391a2ac3","addressRefs":[]},"d5ffcc76-3cde-475d-8336-fcb5ce499988":{"id":"d5ffcc76-3cde-475d-8336-fcb5ce499988","doc_no":"A.2.9.1.6","title":"Public Procurement Framework","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2184,"content":"This document defines a Public Procurement Framework for contributors and actors involved in the Sky Ecosystem. The purpose is to develop a standard framework that governs the entire lifecycle of service providers, which includes the following processes:\n\n- Application process\n- Selection process (scoring / evaluating proposals or applications)\n- Hiring and payment process\n- Performance evaluation and reporting\n- Terminating involvement and resolving disputes","contentHash":"b7bd54e9d6920168c06925cf85cecaa4103f7898c37ffa4d63bc4af42cc856ae","addressRefs":[]},"92dcb95c-5a3d-45a4-a1e6-865686909c64":{"id":"92dcb95c-5a3d-45a4-a1e6-865686909c64","doc_no":"A.2.9.1.7","title":"Audit Procedure for Atlas Amendments","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2185,"content":"This document must define the procedure for performing ex-post legal and technical audits of amended Atlas documents. The general purpose of this procedure is to ensure internal consistency and alignment of the Atlas as a whole.","contentHash":"66143e9b76bf122320e6f3a4504286710a1d1013acd0d9f7a3491028221e464b","addressRefs":[]},"7c4e41ab-c8b4-4938-be92-994c58cf3e2e":{"id":"7c4e41ab-c8b4-4938-be92-994c58cf3e2e","doc_no":"A.2.9.1.8","title":"Technical And Legal Standards","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2186,"content":"This document defines the required technical-legal standards and tools such as, but not limited to, legal agreements ([A.2.8 - Ecosystem Accords](104c3543-ce94-4a2f-9968-57f1ee858085)), templates, and legal structures required to perform specific functions or roles in the Sky Ecosystem. The general purpose of this framework is to minimize trust assumptions and dependencies on specific actors, minimize personal exposure, and increase the accountability and predictability in their behavior.","contentHash":"1fe491efe3ec1c3682c50ff89a89581806c62423122b1ee70b84b693498dca27","addressRefs":[]},"1d5042e4-d7b9-4a2b-b935-aae25220308a":{"id":"1d5042e4-d7b9-4a2b-b935-aae25220308a","doc_no":"A.2.9.1.9","title":"Code And Asset Licenses","type":"Core","depth":4,"parentId":"2abdcb34-3863-40d9-8dd1-52516cb1fa96","order":2187,"content":"Ecosystem Actors should generally release code and assets under the Apache 2.0 license, unless there are specific and clear reasons to use a different license, as determined by the Support Facilitators.\n\nThe Support Facilitators must ensure that a Foundation and other appropriate legal entities exists to properly protect intellectual property and trademarks related to the Sky Ecosystem.\n\nSuch Foundations or other entities must over time be set up to follow instructions from Sky Governance.\n\nAll Ecosystem Actors must take steps to protect the brands and trademarks relevant to the Sky Ecosystem, and in doing so must follow guidelines and best practice defined by the Foundations related to Trademarks, Code and Asset licenses.","contentHash":"69168eb3138af3c2d03e72157d04bbd94b37e7eb879c37dc450a7de07580b1f4","addressRefs":[]},"29b21344-c651-4ea8-9d25-c1b0948c9dca":{"id":"29b21344-c651-4ea8-9d25-c1b0948c9dca","doc_no":"A.2.10","title":"Resilience Research and Preparedness","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":2188,"content":"This Article defines infrastructure and processes to support resilience research and legal preparedness.","contentHash":"d333bddd5c9acdc190842470175050768fd46e4e4e57d1a4af2129540bc2c436","addressRefs":[]},"9bb5e917-2a88-4e9c-bb5c-2d803b0ddcf0":{"id":"9bb5e917-2a88-4e9c-bb5c-2d803b0ddcf0","doc_no":"A.2.10.1","title":"Resilience Research And Preparedness","type":"Section","depth":3,"parentId":"29b21344-c651-4ea8-9d25-c1b0948c9dca","order":2189,"content":"The Support Scope is responsible for conducting ongoing resilience and preparedness research.","contentHash":"4f63cfaead61ab52e4249e2f0060c55d0be05f0c32e47e6ded343874e1533461","addressRefs":[]},"aeb75fe3-f52b-4cdf-a206-1e54ef648d88":{"id":"aeb75fe3-f52b-4cdf-a206-1e54ef648d88","doc_no":"A.2.10.1.1","title":"Role Of Support Facilitators","type":"Core","depth":4,"parentId":"9bb5e917-2a88-4e9c-bb5c-2d803b0ddcf0","order":2190,"content":"The Support Facilitators must ensure that resilience research and preparedness efforts are continuously maintained to ensure the ecosystem is well-positioned to handle any legal uncertainty or risk that should arise. These projects must generally be broadly diversified across all jurisdictions where the Sky Ecosystem could be directly or indirectly exposed, but efforts and resources must be prioritized towards jurisdictions where risks are more likely to emerge.","contentHash":"5da17373492c6dc9fa274b30bc31a603182b7a4505bc3ff003cf9a25436ff9f5","addressRefs":[]},"dff5ff4c-acb4-47cd-93a1-b435dd6db87e":{"id":"dff5ff4c-acb4-47cd-93a1-b435dd6db87e","doc_no":"A.2.10.1.1.0.3.1","title":"Resilience Research And Preparedness - Element Annotation","type":"Annotation","depth":5,"parentId":"aeb75fe3-f52b-4cdf-a206-1e54ef648d88","order":2191,"content":"This element refers to activities and studies aimed at strengthening Sky Ecosystem’s ability to respond effectively to legal uncertainties or risks, including monitoring and analysis of legal trends and regulatory changes; scenario planning and risk modeling; and the development of strategies to mitigate potential threats.","contentHash":"7946bbe69f369c1a16dfd9d2cf3a7029e096cfbacdee7cd4f896af91078d8c60","addressRefs":[]},"236dc6f0-afe4-4d9f-86ba-7bc975df3f7b":{"id":"236dc6f0-afe4-4d9f-86ba-7bc975df3f7b","doc_no":"A.2.10.1.2","title":"Budget","type":"Core","depth":4,"parentId":"9bb5e917-2a88-4e9c-bb5c-2d803b0ddcf0","order":2192,"content":"The Resilience Research and Preparedness budget is specified in [A.2.10.1.2.1 - Current Budget](afb4b3c3-96ad-422d-9033-bd4e5feca90c). The Support Facilitators can trigger a payout from the budget to a relevant recipient address through a Governance Poll.","contentHash":"1d5b7781da23fe77fc6793116504ce1a8671bd83335060d70f12d72b32ea00d3","addressRefs":[]},"afb4b3c3-96ad-422d-9033-bd4e5feca90c":{"id":"afb4b3c3-96ad-422d-9033-bd4e5feca90c","doc_no":"A.2.10.1.2.1","title":"Current Budget","type":"Core","depth":5,"parentId":"236dc6f0-afe4-4d9f-86ba-7bc975df3f7b","order":2193,"content":"The Resilience Research and Preparedness budget is\n\n- Up to 2,000,000 USDS available per year.\n\nThe full amount is immediately available at the start of the calendar year.","contentHash":"4b7103a3c29ec47123ca143baf1d27d2b862fe990e5bcbce2630adf97fab242b","addressRefs":[]},"47c4b698-5cd0-4917-9bf2-96cf385a5098":{"id":"47c4b698-5cd0-4917-9bf2-96cf385a5098","doc_no":"A.2.10.1.3","title":"Research Objectives","type":"Core","depth":4,"parentId":"9bb5e917-2a88-4e9c-bb5c-2d803b0ddcf0","order":2194,"content":"Resilience Research and Preparedness (also \"Resilience Research\") projects must fulfill at least one of the following objectives:\n\n- Bootstrap necessary infrastructure to develop one of the high-order legal resilience objectives as defined in this Article:\n    - Legal Defense\n    - Legal Risk Management\n    - Privacy and Operational Security\n    - Advocacy and Public Policy\n    - Legal and Regulatory Risk Monitoring\n    - Public Procurement Framework\n    - Atlas Amendment and Audit\n    - Technical and Legal Standards\n- Design and implement processes that contribute directly to one of the high-order legal resilience objectives defined in this Article.\n- Implement specific preventive or reactive legal risk mitigation tools.\n- Execute specific activities or tasks necessary to fulfill one of the high-order legal resilience objectives defined in this Article.","contentHash":"813e79a175d99a9ecf68c9751d29ba5605601dd4f705e50662c6fb0ef562877b","addressRefs":[]},"f6af14d7-e62d-44c5-aa65-35c9ec979f4c":{"id":"f6af14d7-e62d-44c5-aa65-35c9ec979f4c","doc_no":"A.2.10.1.4","title":"Application Process","type":"Core","depth":4,"parentId":"9bb5e917-2a88-4e9c-bb5c-2d803b0ddcf0","order":2195,"content":"Ecosystem Actors can apply for a Resilience Research Project by submitting a proposal to be processed by the Support Scope. To submit a Resilience Research Proposal, the Ecosystem Actor must make a post on the Sky Forum following the template provided in [A.2.10.1.4.5 - Application Template](6cecf165-923a-4720-91f6-11c434afa641) and comply with all requirements described in the subdocuments herein.","contentHash":"2ea10d9ea6d9eb6833ceecc39c8bf41bc0e5503f97f6906b050b45f22fc9a106","addressRefs":[]},"e0eedeec-b982-413d-8381-2ceecf5f2e6b":{"id":"e0eedeec-b982-413d-8381-2ceecf5f2e6b","doc_no":"A.2.10.1.4.1","title":"Costs And Benefits","type":"Core","depth":5,"parentId":"f6af14d7-e62d-44c5-aa65-35c9ec979f4c","order":2196,"content":"Resilience Research Proposals must provide a clear and detailed account of both direct and indirect costs, as well as the anticipated results and benefits in relation to the Resilience Research Objectives.","contentHash":"eb0d9c529f2fe9165253801a26dc29a82ca9382d7faa4190769a6aab584fbdb8","addressRefs":[]},"e59dcf34-88f7-4ded-9101-b6ea71797cfe":{"id":"e59dcf34-88f7-4ded-9101-b6ea71797cfe","doc_no":"A.2.10.1.4.2","title":"Team","type":"Core","depth":5,"parentId":"f6af14d7-e62d-44c5-aa65-35c9ec979f4c","order":2197,"content":"Resilience Research Proposals must detail their headcount, team skillset composition, and reliance on third parties.","contentHash":"04f532bab9a5f4f061eb8d567a42fbce2a1e2df7419f7c8e859143dacda186aa","addressRefs":[]},"6f62cb26-d7cc-4a97-8837-79b80bd15d1b":{"id":"6f62cb26-d7cc-4a97-8837-79b80bd15d1b","doc_no":"A.2.10.1.4.3","title":"Timeline And Milestones","type":"Core","depth":5,"parentId":"f6af14d7-e62d-44c5-aa65-35c9ec979f4c","order":2198,"content":"Resilience Research Proposals must provide a clear timeline with detailed, granular milestones and the KPIs to review at each milestone.","contentHash":"a8f59392e78c2fc753375785ba70d075603b6169b92f0c13c7919a383244aa06","addressRefs":[]},"eb9be99b-81d4-46a6-95ff-e81ac56bd33c":{"id":"eb9be99b-81d4-46a6-95ff-e81ac56bd33c","doc_no":"A.2.10.1.4.4","title":"Risk Mitigation Impact","type":"Core","depth":5,"parentId":"f6af14d7-e62d-44c5-aa65-35c9ec979f4c","order":2199,"content":"Resilience Research Proposals must justify how the project will mitigate a specific risk or help bootstrap resources necessary to improve legal resilience.","contentHash":"234f1f2c3d31f205e4ab93ba37f65b19878eada28854a96e983aff2a31d2a6b0","addressRefs":[]},"6cecf165-923a-4720-91f6-11c434afa641":{"id":"6cecf165-923a-4720-91f6-11c434afa641","doc_no":"A.2.10.1.4.5","title":"Application Template","type":"Core","depth":5,"parentId":"f6af14d7-e62d-44c5-aa65-35c9ec979f4c","order":2200,"content":"Applications for Resilience Research projects must follow this template:\n\n- .x: [Project Name]\n- .x.1: [Project Abstract: In 3-5 sentences, what problem are you trying to solve?]\n- .x.2: [Objectives: What are you hoping to accomplish? How do you define and measure success for this project?]\n- .x.3: [Outcomes: How does this project benefit the Sky Ecosystem? How does this project help fulfill one of the Legal Resilience Objectives in [A.2.9 - Legal Resilience](ac707ae4-65da-4cf9-8a34-8b9304cd9a95)]\n- .x.4: [Scope: What will you research/build /design/implement? What is the expected output?]\n- .x.5: [Project Team: How many people are working on this project? Please list their names and roles for the project and how many hours per month each person will work on this project?]\n- .x.6: [Background: Relevant links, reference to other projects or research papers]\n- .x.7: [Methodology: How do you plan to achieve your objectives?]\n- .x.8: [Timeline: Please include a brief explanation of the milestones/roadmap, along with expected deliverables and KPIs.]\n- .x.9: [Budget: Requested grant amount and how this will be used. Please provide the requested amount and outline how the funds will be used.]","contentHash":"1d05ca6c71a1fb4d5dd75f5f004a84ec452ccf1afe5d38c1cdb02450037eb40e","addressRefs":[]},"35aec115-f27c-42f2-9812-644a2df8f38f":{"id":"35aec115-f27c-42f2-9812-644a2df8f38f","doc_no":"A.2.10.1.5","title":"Review Process","type":"Core","depth":4,"parentId":"9bb5e917-2a88-4e9c-bb5c-2d803b0ddcf0","order":2201,"content":"The Support Facilitators must ensure that all Research Proposals are reviewed. The Support Facilitators should document their reviews of all Research Proposals they deem high quality, and publish them in the Sky Forum.","contentHash":"5a4061b85a79cfe6192d3689f6a143da2ad7533106b5eb34c1f2f3a4abcece3f","addressRefs":[]},"9fd21b41-d5ca-4c19-ba21-c2120365b051":{"id":"9fd21b41-d5ca-4c19-ba21-c2120365b051","doc_no":"A.2.10.1.5.1","title":"Budget Availability","type":"Core","depth":5,"parentId":"35aec115-f27c-42f2-9812-644a2df8f38f","order":2202,"content":"Proposals should only be reviewed if there are available funds in the Resilience Research and Preparedness budget.","contentHash":"b4bfcdd899604424ac7352039ca7aefa37820b1ec4e1456b430104531eab453e","addressRefs":[]},"d80f4451-c773-4ddf-b448-c42aaf0b64ec":{"id":"d80f4451-c773-4ddf-b448-c42aaf0b64ec","doc_no":"A.2.10.1.5.2","title":"Factors To Consider","type":"Core","depth":5,"parentId":"35aec115-f27c-42f2-9812-644a2df8f38f","order":2203,"content":"Multiple factors should be considered when reviewing Research Proposals, including the amount of remaining budget, the potential impact on the Resilience Research Objectives, and whether the Research Proposal helps improve legal resilience as described in [A.2.9 - Legal Resilience](ac707ae4-65da-4cf9-8a34-8b9304cd9a95).","contentHash":"e253fcbbf2641512e479061b60294907545008d30746bf0af46439a9bf15ef5f","addressRefs":[]},"cbf70252-fde5-4df7-8552-c778ecc3506a":{"id":"cbf70252-fde5-4df7-8552-c778ecc3506a","doc_no":"A.2.10.1.5.3","title":"Approval Process","type":"Core","depth":5,"parentId":"35aec115-f27c-42f2-9812-644a2df8f38f","order":2204,"content":"Resilience Research Projects require different approval processes depending on the total cost of the project. Projects with a total cost under 15,000 USDS can be directly approved by the Support Facilitator and included in an Executive Vote without a prior Governance Poll. Projects with a total cost of 15,000 USDS or above require a Governance Poll followed by inclusion in an Executive Vote.\n\nThe Support Facilitator must formally approve the inclusion of funding in a Governance Poll or directly in an Executive Vote, as applicable, by replying to the Forum Post containing their evaluation (see [A.2.10.1.5 - Review Process](35aec115-f27c-42f2-9812-644a2df8f38f)).","contentHash":"c80aab1f1214d3ef7e37a6ce93357cbd99a4c287c988c9a545870c3b61c53618","addressRefs":[]},"e7f4ca65-be7d-4c05-b657-5c6243308e71":{"id":"e7f4ca65-be7d-4c05-b657-5c6243308e71","doc_no":"A.2.10.1.5.3.0.3.1","title":"Included In An Executive Vote","type":"Annotation","depth":6,"parentId":"cbf70252-fde5-4df7-8552-c778ecc3506a","order":2205,"content":"The element \"Included In An Executive Vote\" refers to the Support Facilitators’ act of adding a Resilience Research and Preparedness grant payment to an Executive Vote. The Support Facilitators are also responsible for providing provenance for such requests by confirming payment requests on the Executive Sheet. See [A.1.11.1.3.0.3.1 - Executive Sheet - Element Annotation](52aef6ac-9eda-4795-9dab-73ea85b8ca31).","contentHash":"9d5bf896c73e70612898873b25837151d5633b4f7e099e93bd88ffef015d96db","addressRefs":[]},"dd379ac9-5e10-48ac-9b64-a1cb63d6ff51":{"id":"dd379ac9-5e10-48ac-9b64-a1cb63d6ff51","doc_no":"A.2.10.1.5.4","title":"Active Projects","type":"Core","depth":5,"parentId":"35aec115-f27c-42f2-9812-644a2df8f38f","order":2206,"content":"There are currently no active resilience research projects.","contentHash":"164f94fa3e3d92856ae9465857159332a7565653553308fa5f6a198acedc6f52","addressRefs":[]},"2427d573-5e69-4429-a267-97fa6e84ac43":{"id":"2427d573-5e69-4429-a267-97fa6e84ac43","doc_no":"A.2.11","title":"Ecosystem Security Infrastructure","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":2207,"content":"This Article defines ecosystem security infrastructure and processes to protect the Sky Protocol and its users.","contentHash":"03ee79a153713d9c7677ca38b6559c9d58db56e30a44262e60bd7a78930c41c1","addressRefs":[]},"49398799-ca02-4770-a42f-16292260076d":{"id":"49398799-ca02-4770-a42f-16292260076d","doc_no":"A.2.11.1","title":"Ecosystem Security Infrastructure","type":"Section","depth":3,"parentId":"2427d573-5e69-4429-a267-97fa6e84ac43","order":2208,"content":"This Section manages Sky Ecosystem security infrastructure and initiatives.","contentHash":"ebf5d7893976fb2c7186a22060b642d2886efddccf6d0b4e98ae81095be3d587","addressRefs":[]},"e48aa6f8-7806-40c5-a53d-d577249cc6e4":{"id":"e48aa6f8-7806-40c5-a53d-d577249cc6e4","doc_no":"A.2.11.1.1","title":"Bug Bounty Program For Critical Infrastructure","type":"Core","depth":4,"parentId":"49398799-ca02-4770-a42f-16292260076d","order":2209,"content":"As one of the most important DeFi protocols with a high TVL, the Sky Protocol is a honeypot for hackers and other nefarious actors. The Sky Protocol must always be protected by an active Bug Bounty Program. This document regulates the budget and processes of the Bug Bounty Program, which serves to protect the Sky Protocol and its users from hacks and exploits. The Bug Bounty Program is conducted on the Immunefi platform.","contentHash":"f0a9e07b5ec49f3ffc7a745951d6f60ebc04ada2e7082c55bb47485409fe5903","addressRefs":[]},"54134f24-84a2-4130-80a5-a519f291c918":{"id":"54134f24-84a2-4130-80a5-a519f291c918","doc_no":"A.2.11.1.1.1","title":"Introduction","type":"Core","depth":5,"parentId":"e48aa6f8-7806-40c5-a53d-d577249cc6e4","order":2210,"content":"The Bug Bounty Program aims to create incentives for hackers to contribute to the resilience of the Sky Protocol as opposed to exploiting vulnerabilities for personal gain. Immunefi is the party responsible for conducting the Bug Bounty Program; its setup and operations are based on standards set by Immunefi.\n\nThe Sky Ecosystem must continue to maintain a Bug Bounty Program for SparkLend until the launch of the Spark Agent.","contentHash":"5a3b3379170a21f0aad78956ed9bced3b7dc7a8fb2670520c3dfbe786d88f2b2","addressRefs":[]},"b9ed6d24-10e6-48dc-9348-9e2098d8dd31":{"id":"b9ed6d24-10e6-48dc-9348-9e2098d8dd31","doc_no":"A.2.11.1.1.2","title":"Scope","type":"Core","depth":5,"parentId":"e48aa6f8-7806-40c5-a53d-d577249cc6e4","order":2211,"content":"The subdocuments herein describe the scope of the Sky Bug Bounty Program, which currently includes both Sky Protocol and Spark Protocol.","contentHash":"db08b2c8ac629947324abfac8cb9fe6d6af28c1536991ac1c49dce411bf11687","addressRefs":[]},"bc8630bb-ee26-47d6-9e9a-90c87bfcb7a1":{"id":"bc8630bb-ee26-47d6-9e9a-90c87bfcb7a1","doc_no":"A.2.11.1.1.2.1","title":"Assets In Scope","type":"Core","depth":6,"parentId":"b9ed6d24-10e6-48dc-9348-9e2098d8dd31","order":2212,"content":"The Assets In Scope of the Sky Core Bug Bounty Program will be those identified as critical infrastructure for the Sky Ecosystem.\n\nFor Sky Core, the Assets In Scope accepted for this Bug Bounty Program are specified on Sky’s listing on the Immunefi platform, which can be found at ([https://immunefi.com/bounty/makerdao/](https://immunefi.com/bounty/makerdao/)). Assets in Scope include smart contracts, frontend applications, data infrastructure and oracles.\n\nFor SparkLend, the Assets In Scope for the Bug Bounty Program is specified on SparkLend’s listing on the Immunefi platform, which can be found at ([https://immunefi.com/bounty/sparklend/](https://immunefi.com/bounty/sparklend/)). For SparkLend, the Assets In Scope only include smart contracts.\n\nThe Support Facilitator is responsible for maintaining these lists of Assets In Scope, in consultation with the relevant stakeholders.","contentHash":"d5738ce1cec2dd7a454e411e701e78f9b2cdbaee8df551e4f67b8af496777071","addressRefs":[]},"223f562e-3542-4f08-9071-838cb41ad681":{"id":"223f562e-3542-4f08-9071-838cb41ad681","doc_no":"A.2.11.1.1.2.2","title":"Severity Classification","type":"Core","depth":6,"parentId":"b9ed6d24-10e6-48dc-9348-9e2098d8dd31","order":2213,"content":"The Immunefi Vulnerability Severity Classification System ([https://immunefi.com/severity-updated/](https://immunefi.com/severity-updated/)) is applicable to both Sky Core and SparkLend. The Support Facilitator is authorized to adopt a new severity system for the Bug Bounty Programs in consultation with relevant technical stakeholders.","contentHash":"a04a6f9f0801af6919c20118dc388b7c145c0f501a49be89d1f479823bf6089a","addressRefs":[]},"9a38cad6-c0e0-4ca2-931e-b9999710c6d5":{"id":"9a38cad6-c0e0-4ca2-931e-b9999710c6d5","doc_no":"A.2.11.1.1.2.3","title":"Impacts In Scope","type":"Core","depth":6,"parentId":"b9ed6d24-10e6-48dc-9348-9e2098d8dd31","order":2214,"content":"For Sky Core, the Impacts In Scope accepted for the Bug Bounty Program is specified on Sky’s listing on the Immunefi platform, which can be found at ([https://immunefi.com/bounty/makerdao/](https://immunefi.com/bounty/makerdao/)). The impacts are categorized into ‘smart contract’ and ‘websites and applications.’\n\nFor SparkLend, the Impacts In Scope for the Bug Bounty Program is specified on SparkLend’s listing on the Immunefi platform, which can be found at ([https://immunefi.com/bounty/sparklend/](https://immunefi.com/bounty/sparklend/)).","contentHash":"e20de8acc6c6be552c7a7066c2f15acc57b8aedf62a5ab818dc30186c6f1b2c0","addressRefs":[]},"bfcb512b-787c-4509-b130-7bf1abd84c36":{"id":"bfcb512b-787c-4509-b130-7bf1abd84c36","doc_no":"A.2.11.1.1.2.4","title":"Out Of Scope Vulnerabilities And Other Limitations","type":"Core","depth":6,"parentId":"b9ed6d24-10e6-48dc-9348-9e2098d8dd31","order":2215,"content":"A selection of vulnerabilities is deemed out of scope for the Bug Bounty Program. An overview of these out of scope vulnerabilities can be found on Sky’s listing on the Immunefi platform ([https://immunefi.com/bounty/makerdao/](https://immunefi.com/bounty/makerdao/)). Feasibility limitations also apply, which can be found in the aforementioned listing on the Immunefi website.\n\nSpecific rules applying to the Bug Bounty Program can be found at the website above, listed under the following categories:\n\n- Repeatable attack limitations\n- Restrictions on security researcher eligibility\n- Public disclosure of known issues\n- Proof of Concept (PoC) requirements\n- Other terms and information\n- Prohibited activities\n\nFor SparkLend, the rules, terms, and exceptions can be found on SparkLend’s listing on the Immunefi platform ([https://immunefi.com/bounty/sparklend/](https://immunefi.com/bounty/sparklend/)).","contentHash":"5c7240a78818e1ef5ebb617fd75a6b47654cf8360a18918ecbe67dc18011b01d","addressRefs":[]},"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd":{"id":"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd","doc_no":"A.2.11.1.1.3","title":"Rewards Terms And Conditions","type":"Core","depth":5,"parentId":"e48aa6f8-7806-40c5-a53d-d577249cc6e4","order":2216,"content":"The subelements herein describe the Bug Bounty Program’s terms and conditions for rewards.","contentHash":"9dc7a12e0b75d7afc90c655bc9d1b4e34dc9131f90fa8182cd8486cc229a7429","addressRefs":[]},"3dea6103-8e97-4602-866c-371054b71a01":{"id":"3dea6103-8e97-4602-866c-371054b71a01","doc_no":"A.2.11.1.1.3.1","title":"Rewards For Smart Contract Vulnerabilities","type":"Core","depth":6,"parentId":"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd","order":2217,"content":"The Rewards per Threat Level for Smart Contract Vulnerabilities, including related terms, conditions and exceptions, are specified in Sky’s listing on the Immunefi platform ([https://immunefi.com/bounty/makerdao/](https://immunefi.com/bounty/makerdao/)).\n\nFor SparkLend, the Rewards per Threat Level for Smart Contract Vulnerabilities, including related terms, conditions and exceptions, are specified on SparkLend’s listing on the Immunefi platform ([https://immunefi.com/bounty/sparklend/](https://immunefi.com/bounty/sparklend/)).","contentHash":"7f2c3163d60c13e5288b529224b43dc22c6763e63398be9e56318a8590ccc97e","addressRefs":[]},"9c4f269d-b365-4e44-89bc-e99d71737f40":{"id":"9c4f269d-b365-4e44-89bc-e99d71737f40","doc_no":"A.2.11.1.1.3.2","title":"Rewards For Website And Application Vulnerabilities","type":"Core","depth":6,"parentId":"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd","order":2218,"content":"The Rewards per Threat Level for Website and Application Vulnerabilities, including related terms, conditions and exceptions, are specified in Sky’s listing on the Immunefi platform ([https://immunefi.com/bounty/makerdao/](https://immunefi.com/bounty/makerdao/)).","contentHash":"f123b2ef38e118b062739e063fca842a73734ae2457fb272917b749f4a7d7484","addressRefs":[]},"cf4e6968-18a3-48d8-b38e-15ae8009d03d":{"id":"cf4e6968-18a3-48d8-b38e-15ae8009d03d","doc_no":"A.2.11.1.1.3.3","title":"Rewards Payment Terms","type":"Core","depth":6,"parentId":"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd","order":2219,"content":"The subelements herein describe the payment terms for the Bug Bounty Program for Sky Critical Infrastructure.","contentHash":"4fa4d98d258fef4f86f6a72704d35d180e7c9660e90a2c2abfdc5ce91742a148","addressRefs":[]},"f06632c1-5c19-4851-ac68-b6d21466f1c4":{"id":"f06632c1-5c19-4851-ac68-b6d21466f1c4","doc_no":"A.2.11.1.1.3.3.1","title":"Rewards Denomination","type":"Core","depth":6,"parentId":"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd","order":2220,"content":"Payments are denominated in USD. However, payouts are done in USDS assuming a full 1:1 ratio with the USD. However, if the price of USDS deviates from the USD value by more than 1%, the amount of USDS will be adjusted.","contentHash":"914761161d609de429c6601f56527b9403d092df1cc00b84ae5b0d0e756b845e","addressRefs":[]},"07f4faa6-f900-46e6-87d4-137fe2e5cb99":{"id":"07f4faa6-f900-46e6-87d4-137fe2e5cb99","doc_no":"A.2.11.1.1.3.3.2","title":"Rewards Payout Process","type":"Core","depth":6,"parentId":"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd","order":2221,"content":"All bounty payouts are handled by Sky Governance. Upon confirmation, bug bounty payouts should be included in the next possible Executive Vote. This would involve sending USDS directly from the protocol’s buffer to the whitehat hacker.\n\nImmunefi will publicly contact the Core Facilitator with the request, including a specification of the respective vulnerability report, the requested amount and the Ethereum mainnet addresses of the beneficiaries. This should also include the payment details of the Immunefi fee, if it applies. Immunefi and the Core Facilitator should make sure the payout is made within one full calendar month after the report was approved.\n\nFor Bug Bounty rewards over USD 1,000,000: after the first million is paid out, the remaining amount is paid out over time with up to USD 1,000,000 per consecutive month until the determined amount for payout is reached.","contentHash":"8a20a9e2dcdbdf6603e3f356f496f927626eb2e4ceb4a18c4f52fbce2a337459","addressRefs":[]},"97359514-045c-4699-8b1e-e68fe13f8840":{"id":"97359514-045c-4699-8b1e-e68fe13f8840","doc_no":"A.2.11.1.1.3.3.3","title":"Rewards Budget","type":"Core","depth":6,"parentId":"f934a75a-20f1-46d1-ae5e-56fa7da7b4cd","order":2222,"content":"The Bug Bounty Programs incur fixed and variable costs.\n\n- Variable costs: Bug bounty payouts including related fees to Immunefi are considered variable costs and are covered by the process described in [A.2.11.1.1.3.3 - Rewards Payment Terms](cf4e6968-18a3-48d8-b38e-15ae8009d03d).\n- Fixed costs: Fixed costs comprise service fees for the Immunefi Premium Triaging Service, and compensation of a part-time Bug Bounty program steward. These costs will be funded by Sky.","contentHash":"06658925b29fdefa6a43081c8466e914f9f47523cda94e93105e04107adc1a58","addressRefs":[]},"bb494bc1-f3cb-4b7f-826f-437c62d534c8":{"id":"bb494bc1-f3cb-4b7f-826f-437c62d534c8","doc_no":"A.2.11.1.2","title":"Safe Harbor","type":"Core","depth":4,"parentId":"49398799-ca02-4770-a42f-16292260076d","order":2223,"content":"Sky Ecosystem is adopting the Security Alliance Safe Harbor Agreement (\"Safe Harbor\") by executing the procedures specified in [A.2.11.1.2.2 - Execution](25015208-5234-4818-8479-c46f927c272c). Safe Harbor is a public agreement that protocols may adopt to waive the right to pursue legal claims against a whitehat hacker, provided that the hacker acts competently, lawfully, and in good faith. Under Safe Harbor, any whitehat hacker who identifies a time-critical active exploit that could result in the loss of funds is authorized to act immediately to rescue those funds. Immediate intervention prevents delays that might otherwise cause irrevocable financial harm. Once the funds have been secured, the whitehat hacker returns them within 72 hours to an Asset Recovery Address (see [A.2.11.1.2.2.3.3.2 - Asset Recovery Addresses](3f125522-dff7-48a3-948f-e99c71fc3929)) designated by the protocol that has adopted the Safe Harbor Agreement.","contentHash":"5ee66231d0cbeb134c9ea007814db78a0bb29283e8c46877d8d4b89659b665ab","addressRefs":[]},"c3705a82-9cda-4626-89bb-2ec21774b371":{"id":"c3705a82-9cda-4626-89bb-2ec21774b371","doc_no":"A.2.11.1.2.1","title":"Agreement","type":"Core","depth":5,"parentId":"bb494bc1-f3cb-4b7f-826f-437c62d534c8","order":2224,"content":"Safe Harbor is an onchain agreement. The agreement is specified in [https://etherscan.io/address/0xf17bb418b4ec251f300aa3517cb37349f17697a1#readContract#F2](https://etherscan.io/address/0xf17bb418b4ec251f300aa3517cb37349f17697a1#readContract#F2). The agreement located at the IPFS address shown in the smart contract above is the definitive version of the agreement.","contentHash":"7f0cc4dd68a62ad26738fef9000cf42a6929956a7c4abaf792864b47296fd5f5","addressRefs":["0xf17bb418b4ec251f300aa3517cb37349f17697a1"]},"25015208-5234-4818-8479-c46f927c272c":{"id":"25015208-5234-4818-8479-c46f927c272c","doc_no":"A.2.11.1.2.2","title":"Execution","type":"Core","depth":5,"parentId":"bb494bc1-f3cb-4b7f-826f-437c62d534c8","order":2225,"content":"The agreement is executed by calling the `adoptSafeHarbor` function on the Safe Harbor registry contract. The Core Facilitator is directed to include the adoption of Safe Harbor in an upcoming Executive Spell.","contentHash":"5bec9334f8b0664fa3cee204b0a32894c029981746a8f210e9533629aa2c2bc9","addressRefs":[]},"2b097341-3735-43d4-9a18-8a43626a4f4e":{"id":"2b097341-3735-43d4-9a18-8a43626a4f4e","doc_no":"A.2.11.1.2.2.1","title":"Safe Harbor Registry Contract","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2226,"content":"The address of the Safe Harbor registry contract on the Ethereum Mainnet is `0x326733493E143b8904716E7A64A9f4fb6A185a2c`.","contentHash":"fef1c07dcfdb1cf5d109a19cd243f813feaec83e83367e578d71c6f432b04dee","addressRefs":["0x326733493e143b8904716e7a64a9f4fb6a185a2c"]},"0f541963-584d-4bcd-8c00-adbbcb85edf8":{"id":"0f541963-584d-4bcd-8c00-adbbcb85edf8","doc_no":"A.2.11.1.2.2.2","title":"Agreement Address","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2227,"content":"The address of the Safe Harbor agreement is `0xf17bB418B4EC251f300Aa3517Cb37349f17697A1`.","contentHash":"22445a7589729f1814e947438637d47479e9441c111c5ad518b6b4109c19b270","addressRefs":["0xf17bb418b4ec251f300aa3517cb37349f17697a1"]},"b061e1d9-76c3-444a-9a91-641c5d00315d":{"id":"b061e1d9-76c3-444a-9a91-641c5d00315d","doc_no":"A.2.11.1.2.2.3","title":"Execution Parameters","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2228,"content":"The `adoptSafeHarbor` function on the Safe Harbor registry contract should be called with the parameters specified herein.","contentHash":"c327308ac9c21dd452628bd2244994a93010b2162d1e32bb3d5017ce1a8e9f12","addressRefs":[]},"0064ee74-b8bb-4c83-b7a1-cafee3c6e55f":{"id":"0064ee74-b8bb-4c83-b7a1-cafee3c6e55f","doc_no":"A.2.11.1.2.2.3.1","title":"Agreement URI Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2229,"content":"The `agreementURI` parameter is the IPFS address of the agreement. The value of the `agreementURI` parameter is [https://bafkreiernns2f4nv2uzvwtzjc2jboyivsu2mixz33y3xo7cvtllsuao6jy.ipfs.w3s.link/](https://bafkreiernns2f4nv2uzvwtzjc2jboyivsu2mixz33y3xo7cvtllsuao6jy.ipfs.w3s.link/).","contentHash":"eb7b24f3ee4dd7b1fa904051b10ef9908943a12454ee73f21e2ebb2862284496","addressRefs":[]},"206c02ae-b87e-4ed4-95c1-0312b8c73e40":{"id":"206c02ae-b87e-4ed4-95c1-0312b8c73e40","doc_no":"A.2.11.1.2.2.3.2","title":"Bounty Terms Parameters","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2230,"content":"The elements of the `bountyTerms` parameter are specified in the documents herein.","contentHash":"c2d1b7671d631bcc77190791540ddf09dcae85f5d3fe93b36e5e19c55eb8c3c3","addressRefs":[]},"062e64d7-647b-4025-b6ea-d0659737b56b":{"id":"062e64d7-647b-4025-b6ea-d0659737b56b","doc_no":"A.2.11.1.2.2.3.2.1","title":"Bounty Cap USD Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2231,"content":"The `bountyCapUSD` parameter is the maximum amount in USD of the bounty. The value of the `bountyCapUSD` parameter is `10000000`.","contentHash":"456f3593e08ab0be8a53e82b977a821bc099af29a6368cc1f4446d087302d6c3","addressRefs":[]},"226543b7-8cb0-4d26-9569-e5b760f986f5":{"id":"226543b7-8cb0-4d26-9569-e5b760f986f5","doc_no":"A.2.11.1.2.2.3.2.2","title":"Bounty Percentage Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2232,"content":"The `bountyPercentage` parameter is the value to which the whitehat hacker is entitled, expressed as a percentage of the funds recovered. The value of the `bountyPercentage` parameter is `10`.","contentHash":"b005950c1dfb6f4b1ed5c2e5d7eb5e8d37d9e62dc002ba960bbcc1ecc754e18c","addressRefs":[]},"3b5d10d1-16b0-49d8-88e6-9d1185e5de4f":{"id":"3b5d10d1-16b0-49d8-88e6-9d1185e5de4f","doc_no":"A.2.11.1.2.2.3.2.3","title":"Diligence Requirements Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2233,"content":"The `diligenceRequirements` parameter includes KYC, assessing compliance with sanctions (for instance, ensuring that individuals or entities from sanctioned jurisdictions are excluded), diligence, or other verification that the protocol requires the whitehat hacker to satisfy in order to claim the bounty. The value of the `diligenceRequirements` parameter is:\n\n`\"KYC and Sanctions Screening. Sky and Stars require all eligible whitehats to undergo Know Your Customer (KYC) verification and be screened against global sanctions lists, including OFAC, UK, and EU regulations. This ensures that bounty recipients meet legal and regulatory standards before qualifying for payment. The verification process shall be conducted by a trusted third-party provider at Sky and Stars discretion, and all data is deleted, if successful, within 30 days post-verification.\"`","contentHash":"91cbf4603819e371a5406cd1ac36ec1a06a5d6b16b829f614023c0655e55b2f3","addressRefs":[]},"46f3510c-0dbd-40aa-b9fa-abcb59a7ff75":{"id":"46f3510c-0dbd-40aa-b9fa-abcb59a7ff75","doc_no":"A.2.11.1.2.2.3.2.4","title":"Identity Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2234,"content":"The `identity` parameter specifies the identity requirements for the whitehat hacker and may either be `0` for `Anonymous` (the whitehat hacker may be anonymous), `1` for `Pseudonymous` (the whitehat hacker must provide at least a pseudonym), or `2` for `Named` (the whitehat hacker must provide their legal name). The value of the `identity` parameter is `2`.","contentHash":"b554d9cca7f1fd3fb22ca9601a5dd60ac927fef783e5709f40b19a963c0c9f5d","addressRefs":[]},"6ca0bed7-e4b2-4b48-9d03-5ec410ce9fc4":{"id":"6ca0bed7-e4b2-4b48-9d03-5ec410ce9fc4","doc_no":"A.2.11.1.2.2.3.2.5","title":"Retainable Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2235,"content":"The `retainable` parameter specifies whether the whitehat hacker may retain the bounty out of the funds recovered or must first return the entire recovered amount to the Asset Recovery Address before receiving payment from the protocol. The value of the `retainable` parameter is `false`.","contentHash":"bd98390596c0669f8a25b9bdcb6e37377f10ce6c3a89745a9b4389ecf033259d","addressRefs":[]},"80c4c6f0-aade-4908-adaa-847de153d75e":{"id":"80c4c6f0-aade-4908-adaa-847de153d75e","doc_no":"A.2.11.1.2.2.3.3","title":"Chains Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2236,"content":"The `chains` parameter specifies each blockchain on which a funds rescue is authorized. For each chain, the following information must be specified: (1) the `chainId` of the chain, (2) the `assetRecoveryAddress` to which recovered funds should be sent, and (3) the `scope`of contracts on the chain that are covered by Safe Harbor. The chains are specified in the subdocuments herein.","contentHash":"06fc84ec1d9ca0de4f6479700835808cee1b587e2904520bceb053bb0ddd5726","addressRefs":[]},"b5190639-a193-4b8b-8c3a-4d90b369ad07":{"id":"b5190639-a193-4b8b-8c3a-4d90b369ad07","doc_no":"A.2.11.1.2.2.3.3.1","title":"Chain IDs","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2237,"content":"The value of the `chainId` parameter for each chain is:\n\n- Ethereum Mainnet - `1`\n- Arbitrum - `42161`\n- Optimism - `10`\n- Base - `8453`\n- Unichain - `130`\n- Solana - `5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`\n- Avalanche - `43114`\n- Plasma - `9745`","contentHash":"d406f378f8dc8dc4d421996c0b2ec90165ff89e5213559586ff98dcb104e502c","addressRefs":[]},"3f125522-dff7-48a3-948f-e99c71fc3929":{"id":"3f125522-dff7-48a3-948f-e99c71fc3929","doc_no":"A.2.11.1.2.2.3.3.2","title":"Asset Recovery Addresses","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2238,"content":"The Asset Recovery Address is the Pause Proxy on Ethereum Mainnet and the Governance Relay on each other chain. The value of the `assetRecoveryAddress` parameter for each chain is:\n\n- Ethereum Mainnet - `0xbe8e3e3618f7474f8cb1d074a26affef007e98fb`\n- Arbitrum - `0x10E6593CDda8c58a1d0f14C5164B376352a55f2F`\n- Optimism - `0x10E6593CDda8c58a1d0f14C5164B376352a55f2F`\n- Base - `0xdD0BCc201C9E47c6F6eE68E4dB05b652Bb6aC255`\n- Unichain - `0x3510a7F16F549EcD0Ef018DE0B3c2ad7c742990f`\n- Solana - `AYPtjx4Hc8us1ikULUedkmZ3wtiD6tmL7gK3qe4V3oHt`\n- Avalanche - `0xe928885BCe799Ed933651715608155F01abA23cA`\n- Plasma - `0x5CE28f2dD353945db9AB3273A2a1dD1AB632e24b`","contentHash":"3eeeec0f3d6d13d8781e8432fb40b10aaf7e53c0f60bc241734ab0c032efe893","addressRefs":["0x10e6593cdda8c58a1d0f14c5164b376352a55f2f","0x3510a7f16f549ecd0ef018de0b3c2ad7c742990f","0x5ce28f2dd353945db9ab3273a2a1dd1ab632e24b","0xbe8e3e3618f7474f8cb1d074a26affef007e98fb","0xdd0bcc201c9e47c6f6ee68e4db05b652bb6ac255","0xe928885bce799ed933651715608155f01aba23ca","AYPtjx4Hc8us1ikULUedkmZ3wtiD6tmL7gK3qe4V3oHt"]},"c6591c5c-c767-4769-b2d6-80564d96fa48":{"id":"c6591c5c-c767-4769-b2d6-80564d96fa48","doc_no":"A.2.11.1.2.2.3.3.3","title":"Accounts","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2239,"content":"The `accounts` parameter for each chain is a list of contracts to be included in Safe Harbor. Each contract listed must include the sub-elements of (1) the `accountAddress` of the contract and (2) the `childContractScope`, which specifies whether child contracts of the specified contract are covered. The possible values for the `childContractScope` parameter are: (1) `None` (no child contracts are in scope), (2) `ExistingOnly` (only child contracts created prior to calling `adoptSafeHarbor` are in scope), or (3) `All` (all child contracts are in scope).\n\nThe value of the `scope` parameter is all contracts specified in the Bug Bounty Program.\n\nThe `childContractScope` parameter for each contract is specified in the Bug Bounty Program.","contentHash":"f2c4771116a7b5ca8c8086a301ec74d32b6765c6dc37d7c17727cd8849a32803","addressRefs":[]},"611baee4-7c68-47ba-a683-25e795f55101":{"id":"611baee4-7c68-47ba-a683-25e795f55101","doc_no":"A.2.11.1.2.2.3.4","title":"Contact Details","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2240,"content":"The representatives of the protocol should be contacted as specified in the Safe Harbor registry.","contentHash":"e3d1f7d645ec46322a831a4f32755132d0a05d42fea53f20ad1e5e94f855794b","addressRefs":[]},"3ecab562-7477-4606-bce3-74da81dc78e6":{"id":"3ecab562-7477-4606-bce3-74da81dc78e6","doc_no":"A.2.11.1.2.2.3.5","title":"Protocol Name Parameter","type":"Core","depth":6,"parentId":"25015208-5234-4818-8479-c46f927c272c","order":2241,"content":"The `protocolName` parameter specifies a human-readable name for the protocol. The value of the `protocolName` parameter is “Sky”.","contentHash":"bfa507f44256884577e89cde4e4180b001ea8147cb812dc53bafd20271864dad","addressRefs":[]},"fcd868db-4a91-4ee0-baf5-1ebd40fc651e":{"id":"fcd868db-4a91-4ee0-baf5-1ebd40fc651e","doc_no":"A.2.11.1.2.3","title":"Maintenance","type":"Core","depth":5,"parentId":"bb494bc1-f3cb-4b7f-826f-437c62d534c8","order":2242,"content":"The list of contracts covered by the Safe Harbor agreement for Sky must be updated when new contracts are added. Whenever a contract is added to the Bug Bounty Program, it should also be added to Safe Harbor. The Spell Teams are primarily responsible for updating the Safe Harbor registry each time a contract is added to the Bug Bounty Program. The Core Facilitator is responsible for reviewing the work of the Spell Teams to ensure that this requirement is met.","contentHash":"114984d1ff7c336e0cb9f3f0e4d12227b3eaff0e247347c664c49fade8772dc3","addressRefs":[]},"45ab54e8-309a-4149-91cc-fcdbeb5d1d37":{"id":"45ab54e8-309a-4149-91cc-fcdbeb5d1d37","doc_no":"A.2.11.1.2.4","title":"Frontends","type":"Core","depth":5,"parentId":"bb494bc1-f3cb-4b7f-826f-437c62d534c8","order":2243,"content":"The terms and conditions of frontends operated by Sky must be updated to include consent to the potential rescue of funds. Core GovOps must work with relevant Ecosystem Actors to ensure that the contents contained in Exhibit D of the Safe Harbor agreement are incorporated into the terms of conditions governing the frontends operated by Sky and/or Prime Agents.","contentHash":"d1554e9c560e8ee7f1753c7055aa2f23add30ec6f1dce729daa010ac08953760","addressRefs":[]},"48d7232f-59c5-459c-b868-498d0ce00457":{"id":"48d7232f-59c5-459c-b868-498d0ce00457","doc_no":"A.2.11.1.2.5","title":"Prime Responsibilities","type":"Core","depth":5,"parentId":"bb494bc1-f3cb-4b7f-826f-437c62d534c8","order":2244,"content":"Primes must develop processes to register contracts they deploy with Safe Harbor. Primes must include the terms and conditions specified in Exhibit D of the Safe Harbor agreement in all frontends that they operate.","contentHash":"361601367aafb69cd8828d0fc4111dfe2ec36173d988479e65ae310899341f70","addressRefs":[]},"258e85f5-df03-45c5-874e-c2c7fa0fbe87":{"id":"258e85f5-df03-45c5-874e-c2c7fa0fbe87","doc_no":"A.2.11.1.2.6","title":"Agreement Fact Page","type":"Core","depth":5,"parentId":"bb494bc1-f3cb-4b7f-826f-437c62d534c8","order":2245,"content":"[A.2.11.1.2 - Safe Harbor](bb494bc1-f3cb-4b7f-826f-437c62d534c8) constitutes the \"Agreement Fact Page\" as specified in the Safe Harbor Agreement.","contentHash":"60fb11d1999151d598fd5ce46517e652b105a69e5cbd779345752f999453b13a","addressRefs":[]},"142ed420-18a6-4ab9-9889-cbd9c376d48d":{"id":"142ed420-18a6-4ab9-9889-cbd9c376d48d","doc_no":"A.2.11.1.3","title":"Multisig Security Enforcement","type":"Core","depth":4,"parentId":"49398799-ca02-4770-a42f-16292260076d","order":2246,"content":"The documents herein establish the security policies, oversight mechanisms, processes, security requirements, and operational procedures governing the use and administration of Multisigs within the Sky Ecosystem.","contentHash":"33c85a94ecb2e9a98809a526260b133e2aa650c6ad475b005fa1ed96ad9dfcf0","addressRefs":[]},"c2facaa0-f700-49aa-bcbe-ffc0649eb02b":{"id":"c2facaa0-f700-49aa-bcbe-ffc0649eb02b","doc_no":"A.2.11.1.3.1","title":"Purpose","type":"Core","depth":5,"parentId":"142ed420-18a6-4ab9-9889-cbd9c376d48d","order":2247,"content":"The Multisig Security Enforcement Framework establishes binding policies and operational requirements for the use of Multisig wallets across the Sky Ecosystem. Its objective is to ensure that Multisigs used to control smart contracts, allocate capital, and operate under emergency conditions across Sky Core and Prime Agent infrastructure comply with established security and operational requirements, providing clear grounds for oversight, auditing, and enforcement in cases of noncompliance.","contentHash":"315c0038827d1ad89eeb2a98a63ed4000de37e91e6ea5185493927cf29dd0887","addressRefs":[]},"aa2c4af5-5530-4872-9750-20813f3cd258":{"id":"aa2c4af5-5530-4872-9750-20813f3cd258","doc_no":"A.2.11.1.3.1.1","title":"Multisig Administrator","type":"Core","depth":6,"parentId":"c2facaa0-f700-49aa-bcbe-ffc0649eb02b","order":2248,"content":"A Multisig Administrator is the entity or individual responsible for the setup, configuration, ongoing management, and compliance of a Multisig. Each Multisig must have a designated Multisig Administrator, communicated to the Protocol Security Workstream Lead and Core GovOps prior to the Multisig's activation or operational use.","contentHash":"2f1f9bc7ee8b8f3a1be59d4181e8d677721e3fe1905b25c94bc253176b5b37f3","addressRefs":[]},"6033699f-1d55-45ba-8eb1-bd8982571cc0":{"id":"6033699f-1d55-45ba-8eb1-bd8982571cc0","doc_no":"A.2.11.1.3.2","title":"Multisig Security Guidelines","type":"Core","depth":5,"parentId":"142ed420-18a6-4ab9-9889-cbd9c376d48d","order":2249,"content":"The documents herein specify the requirements governing Multisig planning, operation, and administration. All requirements in the documents herein shall take effect on May 20, 2026.","contentHash":"a9de04d290c5710156ff1ba89abe3a21623197ce87c0f09a3fb98830dd960689","addressRefs":[]},"2b44acd9-b589-4a4d-b367-e26a387b2358":{"id":"2b44acd9-b589-4a4d-b367-e26a387b2358","doc_no":"A.2.11.1.3.2.1","title":"Multisig Setup","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2250,"content":"The documents herein specify requirements and relevant operational processes that must be satisfied prior to Multisig activation or operational use.","contentHash":"de258df9ff33da3a5b3f26fa836c1e00b8a2f62e8d501540b7fab4b0208b275b","addressRefs":[]},"e5751fe2-fc2b-4bc8-b9c1-828fef7fc38f":{"id":"e5751fe2-fc2b-4bc8-b9c1-828fef7fc38f","doc_no":"A.2.11.1.3.2.1.1","title":"Multisig Administrator Responsibilities - Setup","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2251,"content":"The documents herein define the responsibilities and requirements applicable to Multisig Administrators prior to Multisig activation or operational use. Multisig Administrators may consult the operational guides specified in [A.2.11.1.3.2.3 - Operational Guides](37f6864d-5f6a-43fd-adbe-f3b2e82c9e01) for guidance on fulfilling these requirements.","contentHash":"14ea945b6c188b6ad26dd4b1aafd3adcbff5f18b8ffac3f26628ad601942c078","addressRefs":[]},"c2344b39-faa2-45af-ab97-99ff521d0826":{"id":"c2344b39-faa2-45af-ab97-99ff521d0826","doc_no":"A.2.11.1.3.2.1.1.1","title":"Multisig Classification","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2252,"content":"The documents herein define relevant processes by which the Multisig Administrator classifies a Multisig in order to determine the appropriate security measures prior to its activation and operational use.","contentHash":"dd1375fbecda30855bea2b089f62b4db8cc71549fdacb7ad9c3168cf2c2d07bf","addressRefs":[]},"3c0847fe-e117-40f8-86a3-9de56c9a3bba":{"id":"3c0847fe-e117-40f8-86a3-9de56c9a3bba","doc_no":"A.2.11.1.3.2.1.1.1.1","title":"Impact Assessment","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2253,"content":"Impact Assessment defines the assessment process in which the potential impact of a Multisig compromise or failure is evaluated. The result of this evaluation is the assignment of an Impact Classification level as defined below. The Multisig Administrator is responsible for determining this classification and must provide it to Core GovOps as part of the Multisig registration process in accordance with [A.2.11.1.3.2.1.1.8 - Multisig Registration](110614e9-6375-464a-90b3-3b350d3cf79c).\n\n| **Impact Classification Level** | **Financial Exposure** | **Decision Context** | **Reputational Impact** |\n|---|---|---|---|\n| Low | <$100k direct exposure | Minimal disruption, alternative paths exist | Limited scope impact |\n| Medium | $100k – $1M exposure | Significant operational delays, workarounds available | Moderate reputational concern |\n| High | $1M – $10M exposure | Major protocol disruption, difficult recovery | Serious reputational damage |\n| Critical | >$10M exposure | Protocol-wide failure, catastrophic impact | Severe reputational damage |\n\nWhen a Multisig falls between two classification levels, the higher security classification must be selected.","contentHash":"8b299915618c0a711f25ad28ce500c3e2518285f3fa557a8ec482e089c9595ce","addressRefs":[]},"35224359-76a6-41fe-adc2-6f70a29f3f4a":{"id":"35224359-76a6-41fe-adc2-6f70a29f3f4a","doc_no":"A.2.11.1.3.2.1.1.1.2","title":"Operational Assessment","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2254,"content":"Operational Assessment defines the assessment process in which the operational response requirements of a Multisig are evaluated. The result of this evaluation is the assignment of an Operational Classification type as defined below. The Multisig Administrator is responsible for determining this classification and must provide it to Core GovOps as part of the Multisig registration process in accordance with [A.2.11.1.3.2.1.1.8 - Multisig Registration](110614e9-6375-464a-90b3-3b350d3cf79c).\n\n| **Operational Classification Type** | **Response Time** | **Decision Context** | **Verification Process** |\n|---|---|---|---|\n| Routine | 24 - 48 hours | Standard procedures, predictable operations | Full verification protocols |\n| Time-Sensitive | 2 - 12 hours | Market conditions, protocol needs | Streamlined but thorough |\n| Emergency | <2 hours | Crisis response, preventing immediate damage | Minimal delays, risk-appropriate |\n\nWhen a Multisig falls between two classification levels, the higher security classification must be selected.","contentHash":"05369b75ee0d66724aaf1ee67743649caf05e5c6eca26cbde29f488e21c1bc6e","addressRefs":[]},"e410573b-a92a-4686-9b4b-71b97d73e99c":{"id":"e410573b-a92a-4686-9b4b-71b97d73e99c","doc_no":"A.2.11.1.3.2.1.1.2","title":"Thresholds And Configuration","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2255,"content":"The documents herein define all requirements relating to Multisig thresholds and configuration.","contentHash":"2188a0f196f3879342dafb139adf86017d7ab1b5342bb240b7aef1291c6631a8","addressRefs":[]},"89b7bcf9-8268-4e46-bdfb-dae3a5985a98":{"id":"89b7bcf9-8268-4e46-bdfb-dae3a5985a98","doc_no":"A.2.11.1.3.2.1.1.2.1","title":"Threshold Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2256,"content":"The baseline minimum threshold standards applicable to all Multisigs are:\n\n- Multisigs must have a minimum of three (3) signers.\n- Multisigs must maintain a signing threshold of at least fifty percent (50%) of total signers.\n\nThese requirements apply unless explicitly exempted in [A.2.11.1.3.2.1.1.2.2 - Threshold Exceptions](130a44af-0715-4aa6-b248-f4a267ebe1a4).\n\nAdditional threshold requirements or considerations may apply depending on the specific operational use case of the Multisig. Such requirements are defined in [A.2.11.1.3.2.1.1.2.3 - Additional Use-Case Specific Threshold Requirements And Considerations](5af1115e-5155-449a-829d-6e641af49b0f).","contentHash":"173b03782b0f6ac5aab4f7244196f4297730ced0b877c94a3ca9c6961521bea0","addressRefs":[]},"130a44af-0715-4aa6-b248-f4a267ebe1a4":{"id":"130a44af-0715-4aa6-b248-f4a267ebe1a4","doc_no":"A.2.11.1.3.2.1.1.2.2","title":"Threshold Exceptions","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2257,"content":"Threshold Exceptions define the limited circumstances under which Multisigs may operate below the baseline threshold requirements defined in [A.2.11.1.3.2.1.1.2.1 - Threshold Requirements](89b7bcf9-8268-4e46-bdfb-dae3a5985a98).\n\nExceptions may be permitted by Core GovOps, in consultation with the Protocol Security Workstream Lead. Examples include rate-setting or parameter adjustment operations where parameters are tightly bounded and set by governance, and where a defined recovery or replacement mechanism exists in the event of Multisig failure or compromise.","contentHash":"1c9a075297777ae71df709be056b57ddd6d62153c19e212297dcdeb9fa03ec52","addressRefs":[]},"5af1115e-5155-449a-829d-6e641af49b0f":{"id":"5af1115e-5155-449a-829d-6e641af49b0f","doc_no":"A.2.11.1.3.2.1.1.2.3","title":"Additional Use-Case Specific Threshold Requirements And Considerations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2258,"content":"Additional threshold requirements and considerations may apply depending on the specific operational use case of the Multisig. These requirements supplement the baseline threshold requirements defined in [A.2.11.1.3.2.1.1.2.1 - Threshold Requirements](89b7bcf9-8268-4e46-bdfb-dae3a5985a98).","contentHash":"537a851b8eec60fdb1cea7228a749a6fc1cd7b0639b0fdb76f3105a9a3cfe0f3","addressRefs":[]},"2a4762e5-b369-45c1-98d6-4dfb34b4ac17":{"id":"2a4762e5-b369-45c1-98d6-4dfb34b4ac17","doc_no":"A.2.11.1.3.2.1.1.2.3.1","title":"Smart Contract Control Multisig Threshold Consideration","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2259,"content":"Higher signing thresholds should be used for operations involving contract upgrades or significant protocol changes. As a general guideline, thresholds equivalent to at least seven of nine (7/9) signers, or an equivalent supermajority, should be used where feasible. Lower thresholds may be acceptable for highly constrained operations where execution scope is limited by on-chain parameter bounds.","contentHash":"89c98ecf455debc641b29a9a43f4a2e685bb437aadef4142c0753778e059db7d","addressRefs":[]},"ca29bdf9-0d6f-42ee-aae5-cb361799cf92":{"id":"ca29bdf9-0d6f-42ee-aae5-cb361799cf92","doc_no":"A.2.11.1.3.2.1.1.2.3.2","title":"High-Value Asset Multisig Threshold Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2260,"content":"Multisigs managing assets with a value equal to or greater than one million USD ($1,000,000) equivalent must have no fewer than seven (7) signers. This requirement applies to custodial control of assets, not emergency freeze functions.","contentHash":"16c11c3706b6ab3c27264efcfbd21dc74b3179ce8667e2b1430226c24055062c","addressRefs":[]},"1f7afd0e-b5b4-47a1-83a0-b15de7a112f8":{"id":"1f7afd0e-b5b4-47a1-83a0-b15de7a112f8","doc_no":"A.2.11.1.3.2.1.1.3","title":"Multisig Configuration Restrictions","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2261,"content":"The documents herein define all requirements relating to Multisig configurations.","contentHash":"aa65dc8a49bcf0174ca83eced68f7ec56c24f188d3a101bcb1f029f883c1fa3f","addressRefs":[]},"492d766d-908c-4dbc-bbcf-e8b9ad720d73":{"id":"492d766d-908c-4dbc-bbcf-e8b9ad720d73","doc_no":"A.2.11.1.3.2.1.1.3.1","title":"Module Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2262,"content":"Multisigs must not utilize any modules or guards, except those explicitly permitted for the applicable use case in [A.2.11.1.3.2.1.1.3.2 - Use-Case Specific Configuration Requirements And Considerations](f8d0e4df-acca-4f20-a030-584efb4a8695).","contentHash":"c65a5217b6a7bfda4ab3aa6edab1da73bdbd8f9c41d253fb9bbc3e6f08cb3028","addressRefs":[]},"f8d0e4df-acca-4f20-a030-584efb4a8695":{"id":"f8d0e4df-acca-4f20-a030-584efb4a8695","doc_no":"A.2.11.1.3.2.1.1.3.2","title":"Use-Case Specific Configuration Requirements And Considerations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2263,"content":"Additional configuration requirements, exceptions or considerations may apply depending on the specific operational use case of the Multisig, and these requirements are specified in the subdocuments herein.","contentHash":"68859ebd1bbd6aae12417555439198c2f3e17078e345951be55b2f21f10fccb1","addressRefs":[]},"f5ed192d-8c49-4095-9b98-840a1a31d47a":{"id":"f5ed192d-8c49-4095-9b98-840a1a31d47a","doc_no":"A.2.11.1.3.2.1.1.3.2.1","title":"Treasury Multisig Configuration Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2264,"content":"Treasury Multisigs must use an allowance module that grants the Sky Pause Proxy allowance equal to the maximum amount of each token held by the Multisig.","contentHash":"ad9346fe40c7980d27d7fa8918d23a4773f32bc9bcd1f48054b22b2b381c0b24","addressRefs":[]},"925a2690-e538-4406-9f6c-491da4f6c58e":{"id":"925a2690-e538-4406-9f6c-491da4f6c58e","doc_no":"A.2.11.1.3.2.1.1.3.2.2","title":"Capital Allocation Multisig Configuration Requirements And Considerations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2265,"content":"Capital Allocation Multisigs should implement on-chain constraints wherever feasible, including, but not limited to, smart contract limits or parameter bounds.","contentHash":"440818bd94014871c7d882146777c7db1bdaf4555441582d0fd8ea03c3504cdf","addressRefs":[]},"0f76bf08-c7a2-4088-b5f7-8b5ac25e748e":{"id":"0f76bf08-c7a2-4088-b5f7-8b5ac25e748e","doc_no":"A.2.11.1.3.2.1.1.3.2.3","title":"Smart Contract Control Multisig Configuration Requirements And Considerations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2266,"content":"For Multisigs responsible for smart contract control, the following requirements apply:\n\n- Major contract changes, including, but not limited to, upgrades or significant parameter changes, must be subject to timelock contracts or equivalent delay mechanisms where feasible.\n- Protocol parameters controlled by Multisigs must be bounded through smart contract enforcement where feasible.","contentHash":"71bd2372bdb856c882089f1973f68d0ccd786175ceb29155ff8c8d07f5043f2e","addressRefs":[]},"022c6cf1-9fba-4c3d-8f15-aa2c616d27c6":{"id":"022c6cf1-9fba-4c3d-8f15-aa2c616d27c6","doc_no":"A.2.11.1.3.2.1.1.4","title":"Standard Threshold Recommendations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2267,"content":"Standard Thresholds refer to recommended Multisig threshold configurations based on use case, Impact Classification level (as defined in [A.2.11.1.3.2.1.1.1.1 - Impact Assessment](3c0847fe-e117-40f8-86a3-9de56c9a3bba)), and Operational Classification type (as defined in [A.2.11.1.3.2.1.1.1.2 - Operational Assessment](35224359-76a6-41fe-adc2-6f70a29f3f4a)). These standards serve as guidance to the Multisig Administrator during Multisig setup.\n\n| **Use Case** | **Impact Classification Level** | **Operational Classification Type** | **Standard Threshold** |\n|---|---|---|---|\n| Treasury - Large | High | Routine | 4/7 |\n| Treasury - Small | Medium | Routine | 3/5 |\n| Emergency Freeze | Critical | Emergency | 2/4 |\n| Capital Allocation | High | Time-Sensitive | 3/5 |\n| Protocol Parameters | High | Routine | 4/7 |\n| Constrained DeFi | Medium | Time-Sensitive | 2/3 |","contentHash":"42a47aaf7d6134fcfb40d8081d333d9e55ecd00c656dc3175e6461895ab95ad3","addressRefs":[]},"42a339d4-5caa-4ea1-bfeb-a0c49d898591":{"id":"42a339d4-5caa-4ea1-bfeb-a0c49d898591","doc_no":"A.2.11.1.3.2.1.1.5","title":"Backup Infrastructure Recommendations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2268,"content":"The documents herein outline recommended practices for establishing and maintaining backup infrastructure to help ensure that Multisig signers can continue to monitor, verify, and execute transactions if primary user interfaces, RPC providers, or block explorers become unavailable.","contentHash":"9c2aacad2bed675c35cb73aff0350e49f31e42502a4af51f7b1a27f090989b2c","addressRefs":[]},"864fe73b-3fd4-4f95-9f26-ece6ef53d925":{"id":"864fe73b-3fd4-4f95-9f26-ece6ef53d925","doc_no":"A.2.11.1.3.2.1.1.5.1","title":"Backup Interface Setup Recommendations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2269,"content":"The Multisig Administrator should ensure that alternative Multisig user interfaces are available to signers in the event that the primary interface becomes unavailable. These interfaces should ideally be accessible through independent infrastructure and may include self-hosted or locally runnable alternatives where available.","contentHash":"e92b5566f83a556b26e8f981cb9d27ed131161c747eed66ae1360b973b62488f","addressRefs":[]},"b5abaa31-031c-4488-a900-05fe5c1afff4":{"id":"b5abaa31-031c-4488-a900-05fe5c1afff4","doc_no":"A.2.11.1.3.2.1.1.5.2","title":"RPC Redundancy Recommendations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2270,"content":"The Multisig Administrator should maintain access to multiple RPC providers for each supported network to help preserve operational continuity if a primary provider becomes unavailable. Where possible, RPC providers should be selected to minimize shared infrastructure dependencies.","contentHash":"ddbc994e8df1b1c0f1103855d12224d972a25f8930792bc0acf61798fa72fbdd","addressRefs":[]},"f7950657-3cf5-4dec-939b-17e13f2f7e9d":{"id":"f7950657-3cf5-4dec-939b-17e13f2f7e9d","doc_no":"A.2.11.1.3.2.1.1.6","title":"Communication Setup","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2271,"content":"The Multisig Administrator is responsible for establishing and maintaining communication channels and communication readiness in accordance with the requirements defined in the subdocuments herein.","contentHash":"753d7e3537628deeb12086e9c0e3266de9719c581d09b4baf9d154979b9cdd45","addressRefs":[]},"ebe71281-44d5-46b8-a64f-eda51d5184b5":{"id":"ebe71281-44d5-46b8-a64f-eda51d5184b5","doc_no":"A.2.11.1.3.2.1.1.6.1","title":"Primary Communication Channel Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2272,"content":"A dedicated communication channel must be established for Multisig operations. The Multisig Administrator is responsible for ensuring that the channel is restricted to Multisig signers and authorized participants and supports reliable and timely operational communication and coordination between participants.","contentHash":"36a2f76de5b853903a1c890516019e1e279c0935ee911ee60a10bb65dcd282e7","addressRefs":[]},"fa17d9fc-b505-411b-995b-5bde1ae8ebc3":{"id":"fa17d9fc-b505-411b-995b-5bde1ae8ebc3","doc_no":"A.2.11.1.3.2.1.1.6.2","title":"Backup Communication Channel Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2273,"content":"A backup communication channel, established on a different platform from the primary communication channel, must be established to maintain communication continuity in the event the primary channel becomes unavailable. The Multisig Administrator is responsible for ensuring that the backup channel follows the same access and participation constraints as the primary channel.","contentHash":"267494d417df15e82e9b624bb4f60716b39154d076d50ea2d1f948a5a571c3e3","addressRefs":[]},"8976fa02-7f24-4d42-8f13-8acfb8757d1b":{"id":"8976fa02-7f24-4d42-8f13-8acfb8757d1b","doc_no":"A.2.11.1.3.2.1.1.6.3","title":"Emergency Communication Readiness Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2274,"content":"Multisig Administrators are responsible for ensuring that Multisigs classified with an Emergency or Time-Sensitive Operational Classification level, as defined in [A.2.11.1.3.2.1.1.1.2 - Operational Assessment](35224359-76a6-41fe-adc2-6f70a29f3f4a), maintain communication and alerting mechanisms capable of reliably and rapidly reaching signers, enabling timely execution of required actions in accordance with the operational response expectations of the Multisig. Multisig Administrators must also include Signers in the approved Emergency Response contact mechanisms as specified in [A.1.9.1.3.2.2 - Approved Emergency Contact Mechanisms](57006d4e-cd91-4565-97b5-5fab73fa94d5).","contentHash":"c765bf7830a79ecdaff26200244e5c9e97d11d4a80e3f074d04a8a64ca2b6869","addressRefs":[]},"317732f8-d609-42a5-9367-c892451cac81":{"id":"317732f8-d609-42a5-9367-c892451cac81","doc_no":"A.2.11.1.3.2.1.1.6.4","title":"Communication Access Removal Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2275,"content":"Any signer removed from a Multisig must be promptly removed from all Multisig communication channels and communication systems associated with that Multisig, including primary and backup communication channels. The Multisig Administrator is responsible for ensuring that access is limited to current authorized participants.","contentHash":"76e2c3f895b53474d3aa11ef272d61cc7ad47676fe96a54c925f35306429b752","addressRefs":[]},"e60b83f2-04a5-4c4a-9666-b2f4f2f55330":{"id":"e60b83f2-04a5-4c4a-9666-b2f4f2f55330","doc_no":"A.2.11.1.3.2.1.1.7","title":"Signer Security Check","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2276,"content":"The Multisig Administrator must ensure that all Multisig signers comply with the applicable signer security requirements as outlined in [A.2.11.1.3.2.1.2.2 - Signer Security Requirements](3f441562-4c03-429c-8934-f0f87fa0eee7), prior to operational use of the Multisig.","contentHash":"0d44acbc19dad51071ad55f7791e71e527014e8ce0d6424bef20a531c8475ad4","addressRefs":[]},"110614e9-6375-464a-90b3-3b350d3cf79c":{"id":"110614e9-6375-464a-90b3-3b350d3cf79c","doc_no":"A.2.11.1.3.2.1.1.8","title":"Multisig Registration","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2277,"content":"All Multisigs currently in use or intended for use within Treasury Management, Emergency Operations (including Freezer or equivalent emergency control Multisigs), Capital Allocation, or Smart Contract Control (including protocol parameter management and constrained DeFi operations) must be registered prior to their inclusion in any Spell or governance execution process.\n\nThe Multisig Administrator is responsible for communicating all necessary details about the Multisig to Core GovOps for registration in accordance with the information requirements outlined in [A.2.11.1.3.4 - Multisig Registry](4d80cae1-b28a-4907-8d59-2ebcbba6003d). Core GovOps must coordinate with the Protocol Security Workstream Lead to obtain approval prior to completing the registration.","contentHash":"07ead60d32c63573b4e84a14332d7416e8a60023863f006958c3aacde81e67c9","addressRefs":[]},"3331e101-36f1-45e5-be2e-e22757b3083b":{"id":"3331e101-36f1-45e5-be2e-e22757b3083b","doc_no":"A.2.11.1.3.2.1.2","title":"Signer Responsibilities - Setup","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2278,"content":"The documents herein define the responsibilities and requirements applicable to Multisig signers during the setup phase of a Multisig. Signers may consult with their Multisig Administrator for guidance on fulfilling these requirements.","contentHash":"2b55284736295d85bbe437eaff6a7cb70332b382847fd63757a7085e81132124","addressRefs":[]},"002821ab-c67c-4eb1-987c-69e759ab7b3c":{"id":"002821ab-c67c-4eb1-987c-69e759ab7b3c","doc_no":"A.2.11.1.3.2.1.2.1","title":"Signer Verification Process","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2279,"content":"Multisig signers must verify their addresses prior to being added to a Multisig. The documents herein define the processes and requirements related to the Signer Verification Process.","contentHash":"36ddaa82511b43264a6cd05df796e84c34eab03a34f66f6898863d81ebde3938","addressRefs":[]},"d1b44379-1e60-480f-b6f8-574e4d2bbb1e":{"id":"d1b44379-1e60-480f-b6f8-574e4d2bbb1e","doc_no":"A.2.11.1.3.2.1.2.1.1","title":"Verification Signature","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2280,"content":"The signer must produce a cryptographically signed message demonstrating control of the signer address intended for Multisig participation. The signed message must include the following:\n\n- A statement indicating that the signer intends to join the specified Multisig;\n- The Multisig address;\n- The signer address intended for participation;\n- The signer's handle, entity name, or other identifying affiliation sufficient to establish accountability.","contentHash":"b72c9dd5bbc9f7b3ecf23a2a62712fc5907475619bef71c58722dda28e94e91f","addressRefs":[]},"84a4c85e-0396-499b-955b-7eb64275b21d":{"id":"84a4c85e-0396-499b-955b-7eb64275b21d","doc_no":"A.2.11.1.3.2.1.2.1.2","title":"Verification Submission","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2281,"content":"The verification signature must be shared with the Multisig Administrator.","contentHash":"5ff82004df8d31a0936c05379e8b7697eac4ee15847544759fbaa9b96f5eee89","addressRefs":[]},"3f441562-4c03-429c-8934-f0f87fa0eee7":{"id":"3f441562-4c03-429c-8934-f0f87fa0eee7","doc_no":"A.2.11.1.3.2.1.2.2","title":"Signer Security Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2282,"content":"Multisig signers must comply with the following security requirements:\n\n- All Multisig signers must use hardware wallets for signing operations. The associated seed phrase must be securely backed up using physical, offline storage methods only. Seed phrases must never be stored digitally, including in photographs, files, password managers, cloud storage, email, or messaging applications. Seed phrase backups must be stored on durable offline media and kept in secure physical locations with appropriate access controls to prevent unauthorized access or single-point compromise.\n- Signers must use a unique signing address per Multisig and must not reuse the same signing address across Multisigs.\n- Signers participating in Multisigs responsible for critical protocol configuration or security-sensitive operations should not use their signing addresses for personal transactions or other unrelated activities and should instead use a dedicated address created specifically for Multisig participation.","contentHash":"0d257032bfff312612b5def69bf8d57423c26a18c445dc3269446faf616dcd68","addressRefs":[]},"c010de5a-57a5-4cdf-9852-d6570b7791ca":{"id":"c010de5a-57a5-4cdf-9852-d6570b7791ca","doc_no":"A.2.11.1.3.2.2","title":"Multisig Ongoing Management","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2283,"content":"The documents herein define the responsibilities and requirements relating to the ongoing management of Multisigs during operational use.","contentHash":"6f93c3ebe075c06f22529d88eb31d217fa4eb8c644c5501167026f24ec0453f9","addressRefs":[]},"7ff66181-3c64-46e8-b17c-f0a90793b388":{"id":"7ff66181-3c64-46e8-b17c-f0a90793b388","doc_no":"A.2.11.1.3.2.2.1","title":"Multisig Administrator Responsibilities - Ongoing Management","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2284,"content":"The documents herein define the responsibilities and requirements of Multisig Administrators relating to the ongoing management and maintenance of Multisigs during operational use. Multisig Administrators may consult the operational guides specified in [A.2.11.1.3.2.3 - Operational Guides](37f6864d-5f6a-43fd-adbe-f3b2e82c9e01) for guidance on fulfilling these requirements.","contentHash":"a915382375f9cc20c5700cb07120fa5fa58b439c144dd3fb039a2007e812cec6","addressRefs":[]},"d81db018-bce7-44b9-a354-667f128a4db3":{"id":"d81db018-bce7-44b9-a354-667f128a4db3","doc_no":"A.2.11.1.3.2.2.1.1","title":"Signer Composition And Rotation","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2285,"content":"The documents herein define requirements governing changes to Multisig signer composition, including the rotation, replacement, and updating of Multisig signers and signer addresses.","contentHash":"d536b3ff3918c7076267e784b43d2c37a49f26cf6e9727431f47389749883fb4","addressRefs":[]},"cb4d28ac-6d54-4d57-99b2-ed80cea73139":{"id":"cb4d28ac-6d54-4d57-99b2-ed80cea73139","doc_no":"A.2.11.1.3.2.2.1.1.1","title":"Signer Rotation Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2286,"content":"Multisig signers may be rotated as operational or security requirements evolve. All signer rotations must be communicated to the Protocol Security Workstream Lead by the Multisig Administrator, accompanied by clear documentation describing the reason for the change, the outgoing signer, and the incoming signer.","contentHash":"2cf2acee53182991b4412f25ee3540f07046af6d0da9cbf17d1e45630dea3673","addressRefs":[]},"2d434d95-a892-404f-9e59-216dce97ce89":{"id":"2d434d95-a892-404f-9e59-216dce97ce89","doc_no":"A.2.11.1.3.2.2.1.1.2","title":"Signer Composition Documentation Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2287,"content":"Any change to Multisig signer composition must be promptly communicated to the Protocol Security Workstream Lead by the Multisig Administrator, including all updated signer addresses.","contentHash":"e47392412a9612fc8765931a0fd8d2c0fb5581d9ff24fc825b32efde70ad6a35","addressRefs":[]},"6dc7cb2e-0c20-4698-b183-28b49f76f88c":{"id":"6dc7cb2e-0c20-4698-b183-28b49f76f88c","doc_no":"A.2.11.1.3.2.2.1.1.3","title":"Threshold Preservation Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2288,"content":"Signer rotations must not reduce the total number of signers or decrease the signing threshold unless the Multisig Administrator provides a clear operational or security justification that is submitted to and approved by the Protocol Security Workstream Lead.","contentHash":"9b93654005ae280b5c8d3910e0bdb5f04d98b96675bc0b5a3c117a1b4e74d1ea","addressRefs":[]},"6bf116c0-657d-454f-8181-cc2677844513":{"id":"6bf116c0-657d-454f-8181-cc2677844513","doc_no":"A.2.11.1.3.2.2.1.1.4","title":"Signer Offboarding Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2289,"content":"The Multisig Administrator must ensure that signers are offboarded in accordance with the procedures outlined in the documents herein.","contentHash":"b31d476c6dd2d697a747d5a430daa69bf46aa18f5fb3356eb785ea5cdb2b4ec4","addressRefs":[]},"5c4850a6-cfd9-4b5e-b8fb-a0500c043bfd":{"id":"5c4850a6-cfd9-4b5e-b8fb-a0500c043bfd","doc_no":"A.2.11.1.3.2.2.1.1.4.1","title":"Signer Removal","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2290,"content":"The Multisig Administrator must coordinate with the remaining signers to execute a signer removal transaction in accordance with the Multisig's standard signer rotation procedures. After execution, the Multisig Administrator must verify that the departing signer's address has been removed from the Multisig and that the change is appropriately communicated and documented as outlined in [A.2.11.1.3.2.2.1.1.2 - Signer Composition Documentation Requirement](2d434d95-a892-404f-9e59-216dce97ce89).","contentHash":"b80fc832321848a460237efd70c248d757b56ae90efea375d54f786078e2cbf0","addressRefs":[]},"6a420118-a76a-4e8f-bd70-e30fca5cf703":{"id":"6a420118-a76a-4e8f-bd70-e30fca5cf703","doc_no":"A.2.11.1.3.2.2.1.1.4.2","title":"Access Revocation And Handover","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2291,"content":"The Multisig Administrator must ensure that the departing signer relinquishes access to all Multisig-related communication channels, shared resources, and sensitive operational systems. Any locally stored sensitive Multisig information must be securely deleted. Departing signers should provide relevant operational context, including any pending actions or responsibilities, to the remaining signers to support a smooth transition.","contentHash":"550a422191993778f298181b7178a364476d6340d3410cca1f5254898f776647","addressRefs":[]},"f1c6bc31-d2f4-454d-8200-8a2ddc78c695":{"id":"f1c6bc31-d2f4-454d-8200-8a2ddc78c695","doc_no":"A.2.11.1.3.2.2.1.1.5","title":"Use-Case Specific Signer Requirements And Considerations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2292,"content":"Additional signer requirements or considerations may apply depending on the specific operational use case of the Multisig. Such requirements are specified in the subdocuments herein.","contentHash":"dfda940c807fe4e0de2a0454e3a6300b053127bfdefbbe56f88c2daa7abb45de","addressRefs":[]},"fdeaaece-d90e-4f47-a8f9-0ea23cf8d49f":{"id":"fdeaaece-d90e-4f47-a8f9-0ea23cf8d49f","doc_no":"A.2.11.1.3.2.2.1.1.5.1","title":"Emergency Response Multisig Signer Composition Requirements And Considerations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2293,"content":"The signer requirements and considerations applicable to Multisigs classified with a Time-Sensitive or Emergency Operational Classification level, as defined in [A.2.11.1.3.2.1.1.1.2 - Operational Assessment](35224359-76a6-41fe-adc2-6f70a29f3f4a), are as follows:\n\n- Emergency Response Multisigs must maintain 24/7 availability of a number of signers equal to or greater than the Multisig signing threshold.\n- Geographic distribution of signers is encouraged for Emergency Response Multisigs where appropriate to support 24/7 operational coverage.","contentHash":"c9cab9c1ee2130db6fa2d9c054e578def0b0403eb9efaa4ffdb0ae24074ea41c","addressRefs":[]},"8d4d4683-03fc-4e4d-a255-9e7e0c40e059":{"id":"8d4d4683-03fc-4e4d-a255-9e7e0c40e059","doc_no":"A.2.11.1.3.2.2.1.1.5.2","title":"Capital Allocation Multisig Signer Composition Requirements And Considerations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2294,"content":"The Multisig Administrator must ensure that all signers participating in Capital Allocation Multisigs (Multisigs responsible for allocating or reallocating capital) possess sufficient protocol expertise.","contentHash":"9660410543945eab34abb4216555d01ce146c93184a08aa4cf49cb66a3606d00","addressRefs":[]},"8ff4a715-3ca6-4196-8fae-80ea556c2266":{"id":"8ff4a715-3ca6-4196-8fae-80ea556c2266","doc_no":"A.2.11.1.3.2.2.1.2","title":"Incident Reporting","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2295,"content":"Incident Reporting defines the procedures governing the reporting of security incidents, operational issues, and security-relevant events relating to Multisig operations.","contentHash":"dfe3ee0d21bdd8f480b632f8ed9ecff0202e76cba548daaabd0e23b0c36baa43","addressRefs":[]},"f604c9b7-a728-4b53-acbc-cc8677dd23d6":{"id":"f604c9b7-a728-4b53-acbc-cc8677dd23d6","doc_no":"A.2.11.1.3.2.2.1.2.1","title":"Reportable Incidents Classification","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2296,"content":"All incidents must be reported and classified to ensure appropriate response timelines and escalation. The documents herein define the classification categories, reporting timelines, and applicable reporting processes for Multisig-related incidents.","contentHash":"99a28b35731303f2d270ee839003158151b888657a9abb8ab166d953364baa0c","addressRefs":[]},"bae73b4f-aa60-4c42-a56c-3d29af2bef36":{"id":"bae73b4f-aa60-4c42-a56c-3d29af2bef36","doc_no":"A.2.11.1.3.2.2.1.2.1.1","title":"Security Incidents","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2297,"content":"Security incidents must be reported immediately upon discovery, in accordance with the process outlined in [A.2.11.1.3.2.2.1.2.2 - Emergency Incident Reporting Process](56e44cdc-1ba5-4254-9308-c4cfe189394a). Security incidents include, but are not limited to:\n\n- Signing key compromise or suspected compromise\n- Account takeover of email or communication platforms used for Multisig operations\n- Device theft or loss involving signing or operational access\n- Suspicious or unauthorized activity on Multisig accounts\n- Phishing attempts targeting Multisig operations\n- Compromise or suspected infiltration of communication channels used for Multisig coordination","contentHash":"e7e1ee7f48f6f11453801035aaa969a0c6110eedb8a7496576a7949066b578dc","addressRefs":[]},"8f2bc680-c6f7-40dc-b003-118b71f1de20":{"id":"8f2bc680-c6f7-40dc-b003-118b71f1de20","doc_no":"A.2.11.1.3.2.2.1.2.1.2","title":"Operational Issues","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2298,"content":"Operational issues must be reported within 24 hours of discovery, in accordance with the process outlined in [A.2.11.1.3.2.2.1.2.3 - Standard Incident Reporting Process](ec4cd423-74ba-4e74-82d9-46ba5f6cf526). Operational issues include, but are not limited to:\n\n- Loss of access to signing keys or signing devices\n- Hardware wallet or backup device failure\n- Communication channel failures affecting Multisig coordination\n- Verification tool malfunctions\n- Operational difficulties preventing adherence to security procedures","contentHash":"e5961e5b47e19b19a69b0a9c1ffa0289905fa4f775699b414bbfd8619696bb61","addressRefs":[]},"32420ad5-4fd2-4088-8564-452d4adf9589":{"id":"32420ad5-4fd2-4088-8564-452d4adf9589","doc_no":"A.2.11.1.3.2.2.1.2.1.3","title":"Near Misses","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2299,"content":"Near misses should be reported in accordance with the process outlined in [A.2.11.1.3.2.2.1.2.3 - Standard Incident Reporting Process](ec4cd423-74ba-4e74-82d9-46ba5f6cf526) when practical. Near misses include events that did not result in compromise but may indicate risk, including, but not limited to:\n\n- Social engineering attempts\n- Suspicious emails or messages\n- Security procedure confusion or errors\n- Training gaps or unclear documentation","contentHash":"ae367d65db290a1783ca1d92d9ae1598684e87c924415bb0fb1e3dfc18e7d569","addressRefs":[]},"56e44cdc-1ba5-4254-9308-c4cfe189394a":{"id":"56e44cdc-1ba5-4254-9308-c4cfe189394a","doc_no":"A.2.11.1.3.2.2.1.2.2","title":"Emergency Incident Reporting Process","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2300,"content":"When an emergency incident occurs, the following steps must be completed:\n\n- The reporting signer must take immediate actions to secure the situation and prevent further risk, including isolating affected devices or systems where appropriate.\n- The reporting signer must notify the Multisig Administrator and other participants through the primary communication channel.\n- The Multisig Administrator must ensure that the reporting signer immediately reports the incident to the Protocol Security Workstream Lead, following the documentation requirements outlined in [A.2.11.1.3.2.2.1.2.2.1 - Emergency Incident Documentation Requirements](6d6e7b53-8fcb-4ecb-8428-e07f682d13d4).\n- The Multisig Administrator must ensure that the reporting signer follows up with the Protocol Security Workstream Lead if no acknowledgement is received within 24 hours.","contentHash":"3f9350ec085bb6bce55a7b90f5256f854ae9992e1e6330fec27b7b1314dc1529","addressRefs":[]},"6d6e7b53-8fcb-4ecb-8428-e07f682d13d4":{"id":"6d6e7b53-8fcb-4ecb-8428-e07f682d13d4","doc_no":"A.2.11.1.3.2.2.1.2.2.1","title":"Emergency Incident Documentation Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2301,"content":"All emergency incident reports must include sufficient documentation to allow review, follow-up, and operational learning. At minimum, security incident documentation must include:\n\n- Multisig details and classification\n- Incident type\n- Time of incident occurrence and discovery\n- Reporting signer\n- Description of the incident\n- Immediate actions taken\n- Next steps required\n- Current Multisig status\n- Impact","contentHash":"29aa5281382fb31cf47b1a6de0174f32fc52566908331a2a1e9061f4e5fa79f4","addressRefs":[]},"ec4cd423-74ba-4e74-82d9-46ba5f6cf526":{"id":"ec4cd423-74ba-4e74-82d9-46ba5f6cf526","doc_no":"A.2.11.1.3.2.2.1.2.3","title":"Standard Incident Reporting Process","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2302,"content":"When a standard incident occurs, the following steps must be completed:\n\n- The Multisig Administrator must ensure that the reporting signer immediately reports the incident to the Protocol Security Workstream Lead, following the documentation requirements outlined in [A.2.11.1.3.2.2.1.2.3.1 - Standard Incident Documentation Requirements](0aec011a-18d2-4945-90b5-8089fa01cefb).\n- Follow-up with the Protocol Security Workstream Lead if no acknowledgement is received within 48 hours.","contentHash":"997eca276929b46ce5ee7181dbe8d8f05110f868ca385452bee7261672a5e0ff","addressRefs":[]},"0aec011a-18d2-4945-90b5-8089fa01cefb":{"id":"0aec011a-18d2-4945-90b5-8089fa01cefb","doc_no":"A.2.11.1.3.2.2.1.2.3.1","title":"Standard Incident Documentation Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2303,"content":"All standard incident reports must include, at minimum, the following information:\n\n- Multisig details and classification\n- Incident type\n- Time of incident occurrence and discovery\n- Reporting signer\n- Description of the incident\n- Immediate actions taken\n- Current Multisig status\n- Impact","contentHash":"d798f4c7f8272fb93df45436264b7b2d19d519a72c231d5c5dbea4070aded555","addressRefs":[]},"a0a34154-2789-4ffd-844b-36f27e9900db":{"id":"a0a34154-2789-4ffd-844b-36f27e9900db","doc_no":"A.2.11.1.3.2.2.1.3","title":"Training And Operational Readiness","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2304,"content":"Multisig Administrators must ensure that signers maintain sufficient operational expertise through ongoing training and familiarity with the Multisig's procedures. This includes, but is not limited to, training and periodic review of transaction verification practices, operational procedures, and incident response processes applicable to the Multisig's function.","contentHash":"e3853545e3f2d1cc56e9a90b672b891e373095b19a457b901b047b0d2d452b34","addressRefs":[]},"f9e5507b-1433-47fc-ae41-28c23831c0fc":{"id":"f9e5507b-1433-47fc-ae41-28c23831c0fc","doc_no":"A.2.11.1.3.2.2.1.3.1","title":"Backup Infrastructure Readiness Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2305,"content":"The Multisig Administrator must ensure that signers are prepared to operate using backup infrastructure. This includes providing signers with access to offline or alternative Multisig interfaces, verifying that signers have practiced using backup interfaces, testing backup RPC providers during non-emergency periods, and maintaining documented procedures describing how to switch to backup infrastructure when required.","contentHash":"c4bceda2ca6d3a1c8f40e8c44d4b707ef8213082e2f3aabab636a2872bf73fa6","addressRefs":[]},"3d5068af-cb19-4a10-b712-de8e8be7a4f6":{"id":"3d5068af-cb19-4a10-b712-de8e8be7a4f6","doc_no":"A.2.11.1.3.2.2.1.3.2","title":"Emergency Operations Training And Readiness Requirement","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2306,"content":"Multisig Administrators are responsible for ensuring that Multisigs classified with a Time-Sensitive or Emergency Operational Classification level, as defined in [A.2.11.1.3.2.1.1.1.2 - Operational Assessment](35224359-76a6-41fe-adc2-6f70a29f3f4a), maintain operational readiness appropriate to their function.\n\nTo satisfy this requirement, Multisig Administrators must ensure that the following activities are conducted:\n\n- Periodic operational drills\n- Quarterly testing of emergency communication and alerting systems to ensure continued reliability\n- Semi-annual paging system tests to verify alert functionality\n- An annual full emergency simulation involving all signers\n\nThe Multisig Administrator must document the completion and outcome of all required readiness activities and provide testing reports and confirmation of completion to Core GovOps.","contentHash":"ebc4113ea2e240a02529bced137c0cca865d10a0849e45039fbb9dc2a967e4c2","addressRefs":[]},"51431dc2-d731-4570-8e54-de390e565bb1":{"id":"51431dc2-d731-4570-8e54-de390e565bb1","doc_no":"A.2.11.1.3.2.2.2","title":"Signer Responsibilities - Ongoing Management","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2307,"content":"The documents herein define the responsibilities and requirements of Multisig signers relating to the ongoing management of Multisigs during operational use. Signers may consult with their Multisig Administrator for guidance on fulfilling these requirements.","contentHash":"1dcb9f86f001a799bf90bc9204c3116b10ed0b4cb547ac0dcbc6b4d40d9ace12","addressRefs":[]},"79b5daf4-5c02-4aa8-89a7-879a6d594758":{"id":"79b5daf4-5c02-4aa8-89a7-879a6d594758","doc_no":"A.2.11.1.3.2.2.2.1","title":"Signer Address Update Process","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2308,"content":"Any update to a Multisig signer address must be performed in accordance with the process defined in the subdocuments herein.","contentHash":"7e4b1ccc5970092e2d4cdf98410c49efa8179e87c467d109d1f67388bfac3ccf","addressRefs":[]},"c6bcbd5f-7450-4c6e-9aa6-82c49a678bd3":{"id":"c6bcbd5f-7450-4c6e-9aa6-82c49a678bd3","doc_no":"A.2.11.1.3.2.2.2.1.1","title":"Signer Address Update Process If Original Key Is Accessible","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2309,"content":"If the original key of the signer address that needs to be changed remains accessible, the following steps must be completed by the signer:\n\n- The signer authorizes the address change by signing a message with the existing signer address. The signed message must clearly state the intent to replace the existing signer address with the new address.\n- The signer must follow the steps defined in [A.2.11.1.3.2.1.2.1 - Signer Verification Process](002821ab-c67c-4eb1-987c-69e759ab7b3c) prior to the new address being added to the Multisig.","contentHash":"727c2b5d096b2aa22ffff4ef11f363842c1d1fb25ba7a12bbe4d6672ff6021da","addressRefs":[]},"a2f65561-ba6d-4ef0-b1c0-31da659306f3":{"id":"a2f65561-ba6d-4ef0-b1c0-31da659306f3","doc_no":"A.2.11.1.3.2.2.2.1.2","title":"Signer Address Update Process If Original Key Is Lost Or Inaccessible","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2310,"content":"If the original key of the signer address that needs to be changed is inaccessible, the signer must verify their identity to the remaining signers through alternative verification methods such as:\n\n- Authentication through a verified social media or publicly associated account\n- Live verification via video call with existing signers\n- Other comparable verification methods\n\nUpon successful identity verification, the signer must follow the steps defined in [A.2.11.1.3.2.1.2.1 - Signer Verification Process](002821ab-c67c-4eb1-987c-69e759ab7b3c) and notify the Multisig Administrator once completed.","contentHash":"ab06db6b25fefe61f67e72d29aa1862a92674bc85be00dd2fba07ffce3f214cc","addressRefs":[]},"aa6f2aeb-5c90-4b23-bfc4-e6de0a588915":{"id":"aa6f2aeb-5c90-4b23-bfc4-e6de0a588915","doc_no":"A.2.11.1.3.2.2.2.2","title":"Transaction Verification And Signing Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2311,"content":"Multisig signers must verify all transaction data prior to signing in order to reduce the risk of malicious or unintended transactions being executed. The procedures defined in the documents herein establish the relevant transaction verification processes for supported execution environments.","contentHash":"a05e64216ecaf81c23143ded416dee4f96ed81f0bd07fc3535d97deecc849257","addressRefs":[]},"98eeb3a8-8199-417f-a0a7-ab4625aa39aa":{"id":"98eeb3a8-8199-417f-a0a7-ab4625aa39aa","doc_no":"A.2.11.1.3.2.2.2.2.1","title":"Explorer Redundancy Recommendations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2312,"content":"Signers are encouraged to maintain access to multiple blockchain explorers for each supported network to support transaction monitoring, verification, and investigation if a primary explorer becomes unavailable.","contentHash":"c8bc86b3527a1e5431d274ce8feeee16e3f7dc2a6a2e4403c1f3adea50aeb77d","addressRefs":[]},"1d4492e8-f2eb-4ff5-9bf8-471a9aef26c5":{"id":"1d4492e8-f2eb-4ff5-9bf8-471a9aef26c5","doc_no":"A.2.11.1.3.2.2.2.2.2","title":"EVM Transaction Verification Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2313,"content":"Multisig signers must verify EVM-based Multisig transactions prior to signing to ensure that the transaction being signed matches the intended operation.","contentHash":"379e3cbd028b0e9170b00b7a108774b224d4d71be59fe36fdc57ccbf6631e917","addressRefs":[]},"eb5de4dd-2921-439e-bbce-a26f66410c48":{"id":"eb5de4dd-2921-439e-bbce-a26f66410c48","doc_no":"A.2.11.1.3.2.2.2.2.2.1","title":"Transaction Hash Verification","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2314,"content":"Signers must verify that the transaction hash displayed on the signing device matches the expected transaction hash derived from the transaction parameters. When signing transactions involving nested Multisigs, the hash displayed on the signing device may correspond to an approval hash rather than the underlying transaction. In such cases, signers must verify both the nested transaction and the parent Multisig approval.","contentHash":"627d03e01121bacb20a19b1353efe452b4c72c6baa251d8b13480b4b873040e6","addressRefs":[]},"35229761-1568-4b00-84c2-878aa64562e1":{"id":"35229761-1568-4b00-84c2-878aa64562e1","doc_no":"A.2.11.1.3.2.2.2.2.2.2","title":"Transaction Simulation Review","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2315,"content":"Where available, signers must review a transaction simulation to confirm that the expected events, asset transfers, and state changes match the intended transaction.","contentHash":"176fde4c1bd1bd4484346f9ad8619cd172d0f03c0ad90a106782c9b5ef04aaaf","addressRefs":[]},"023b1251-96d0-4784-a11b-1d470444eba2":{"id":"023b1251-96d0-4784-a11b-1d470444eba2","doc_no":"A.2.11.1.3.2.2.2.2.2.3","title":"Transaction Calldata Review","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2316,"content":"Signers must review decoded transaction calldata prior to signing to confirm that the function calls, recipient addresses, and transferred amounts match the intended action.","contentHash":"5e33e4e8ae8c816cc630add64295aa78fd0ef962017f521ee7299d923776fd92","addressRefs":[]},"e329c539-16e2-4316-bb2c-6879bb45d391":{"id":"e329c539-16e2-4316-bb2c-6879bb45d391","doc_no":"A.2.11.1.3.2.2.2.2.2.4","title":"Verification Tool Diversity","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2317,"content":"Signers are encouraged to verify transaction hashes and decoded calldata using independent verification tools where available and should avoid relying on a single verification interface.","contentHash":"a73747c1340235dede85258aebea76700595cb6bd8e9d357a47216af8fc1d977","addressRefs":[]},"d6ab5e65-bc6b-4959-9c11-e5612cc07ee0":{"id":"d6ab5e65-bc6b-4959-9c11-e5612cc07ee0","doc_no":"A.2.11.1.3.2.2.2.2.3","title":"SVM Transaction Verification Requirements","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2318,"content":"Multisig signers must verify Solana Virtual Machine (SVM) Multisig transactions prior to signing to ensure that the proposal contains the intended instructions and parameters.","contentHash":"fc97fe8503cd46e8de1807c827ddea6bef5a07b7746e157dd5058e4092a44942","addressRefs":[]},"dd520781-597e-4a0f-9120-47d18c0fc7c0":{"id":"dd520781-597e-4a0f-9120-47d18c0fc7c0","doc_no":"A.2.11.1.3.2.2.2.2.3.1","title":"Proposal Verification","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2319,"content":"Signers must verify that the transaction proposal reflects the intended operation, including the sender, recipient addresses, asset type, transfer amounts, configuration changes, and associated instructions. Signers must confirm that all instructions correspond to the intended action and that no unauthorized interactions are included.","contentHash":"04023d57749155ab533681c82c97d240c05964907eb5a8c8d2f38e82d94e0876","addressRefs":[]},"37d9a254-08e2-43f3-b2a6-4226b6a8429a":{"id":"37d9a254-08e2-43f3-b2a6-4226b6a8429a","doc_no":"A.2.11.1.3.2.2.2.2.3.2","title":"Simulation Review","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2320,"content":"Where available, signers must review a transaction simulation to confirm that expected token transfers, SOL transfers, or configuration changes match the intended transaction.","contentHash":"05ca034600db416c15315353ed541f9b445fb832c2b10917a2a2ed6ab9da9dfa","addressRefs":[]},"979afea2-e159-46e3-be25-8ce22dac7dd0":{"id":"979afea2-e159-46e3-be25-8ce22dac7dd0","doc_no":"A.2.11.1.3.2.2.2.2.3.3","title":"Explorer Verification","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2321,"content":"Signers are encouraged to inspect the transaction or proposal account using a public blockchain explorer to review the decoded transaction instructions and parameters.","contentHash":"d8bdbaaa84983fca5498b49e9feb38ee3f4c7403ad7191ec808957015c1c8dad","addressRefs":[]},"388f1cc7-f10c-4410-bc49-e0e3e358a90e":{"id":"388f1cc7-f10c-4410-bc49-e0e3e358a90e","doc_no":"A.2.11.1.3.2.2.2.2.3.4","title":"Tooling Limitations","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2322,"content":"Verification tooling for SVM Multisig transactions is currently more limited than for EVM environments. Signers should exercise additional caution and may cross-verify transactions with other signers prior to execution.","contentHash":"fdc750c4bf58723d5bfec2012fe5f19f785e67303794f2075cf93e0aab40061e","addressRefs":[]},"37f6864d-5f6a-43fd-adbe-f3b2e82c9e01":{"id":"37f6864d-5f6a-43fd-adbe-f3b2e82c9e01","doc_no":"A.2.11.1.3.2.3","title":"Operational Guides","type":"Core","depth":6,"parentId":"6033699f-1d55-45ba-8eb1-bd8982571cc0","order":2323,"content":"The Protocol Security Workstream Lead must maintain and make available operational guides to support Multisig Administrators in complying with the requirements specified in [A.2.11.1.3.2 - Multisig Security Guidelines](6033699f-1d55-45ba-8eb1-bd8982571cc0). These guides must cover, at minimum, Multisig registration, signer rotation and replacement, signer onboarding and offboarding, incident reporting, and any other processes where standardized documentation is required. The Protocol Security Workstream Lead is responsible for keeping these guides current and accessible to all Multisig Administrators.","contentHash":"4a5d50f32ded2facd426487596be3fbe5e3bd5e1c863e8bf071345936df9ff8f","addressRefs":[]},"e5a3658b-0218-42a7-b053-ddd276a0a512":{"id":"e5a3658b-0218-42a7-b053-ddd276a0a512","doc_no":"A.2.11.1.3.3","title":"Multisig Monitoring And Review","type":"Core","depth":5,"parentId":"142ed420-18a6-4ab9-9889-cbd9c376d48d","order":2324,"content":"The documents herein define the periodic monitoring and review responsibilities performed by Core GovOps to ensure that Multisigs remain compliant with the Multisig Security Enforcement Framework and that Multisig documentation and classification remain accurate. These provisions apply only after the effective date specified in [A.2.11.1.3.2 - Multisig Security Guidelines](6033699f-1d55-45ba-8eb1-bd8982571cc0).","contentHash":"779f54ac2429a3c39ccdba41b1811f730ad6488218149bf95f18141429be6eed","addressRefs":[]},"94d70a1d-885b-4f46-ade4-0702f65cfc89":{"id":"94d70a1d-885b-4f46-ade4-0702f65cfc89","doc_no":"A.2.11.1.3.3.1","title":"Periodic Review Requirement","type":"Core","depth":6,"parentId":"e5a3658b-0218-42a7-b053-ddd276a0a512","order":2325,"content":"Core GovOps must engage the Protocol Security Workstream Lead and third party providers to conduct periodic reviews of registered Multisigs to verify that Multisig documentation, configuration, and operational classification remain accurate and aligned with current usage. At minimum:\n\n- Multisig documentation and classification must be reviewed on a quarterly basis.\n- Reviews must be conducted following major operational, financial, or structural changes affecting the Multisig.\n- Reviews must be conducted when significant protocol changes materially affect the Multisig's role, authority, or risk exposure.","contentHash":"a7d3516d00ea087aae63d4df99900b645107693b241751df3a2b4c0d7dfb045d","addressRefs":[]},"4090334c-d240-49d4-89c1-7901ffbfa299":{"id":"4090334c-d240-49d4-89c1-7901ffbfa299","doc_no":"A.2.11.1.3.3.1.1","title":"Review Scope","type":"Core","depth":6,"parentId":"e5a3658b-0218-42a7-b053-ddd276a0a512","order":2326,"content":"Periodic reviews may include, but are not limited to:\n\n- Verification that Multisig documentation in the Multisig Registry remains accurate and up to date.\n- Reassessment of Multisig operational purpose where operational patterns change.\n- Reassessment of financial exposure or protocol impact where asset exposure or operational scope changes.\n- Verification that Multisig configuration and operational practices remain consistent with the Multisig Security Enforcement Framework.","contentHash":"726e51d6207d4c6154a88e564961ac0ab958310ec3154a1657ad6aec8c65f3c6","addressRefs":[]},"69646ecd-268a-4487-9077-c6efa11f1026":{"id":"69646ecd-268a-4487-9077-c6efa11f1026","doc_no":"A.2.11.1.3.3.2","title":"Monitoring Outcome","type":"Core","depth":6,"parentId":"e5a3658b-0218-42a7-b053-ddd276a0a512","order":2327,"content":"Where monitoring or review activities identify inconsistencies, outdated documentation, or potential noncompliance, Core GovOps must proceed in accordance with [A.2.11.1.3.5 - Determination And Enforcement Of Multisig Security Noncompliance](2a36aafa-cfe3-4ba5-b549-f341fbb4c666).","contentHash":"b425a982342ad699ba4034789ad8f703696fb1c742c8e54b884d92a9aee5ebea","addressRefs":[]},"4d80cae1-b28a-4907-8d59-2ebcbba6003d":{"id":"4d80cae1-b28a-4907-8d59-2ebcbba6003d","doc_no":"A.2.11.1.3.4","title":"Multisig Registry","type":"Core","depth":5,"parentId":"142ed420-18a6-4ab9-9889-cbd9c376d48d","order":2328,"content":"All Multisigs must be recorded in the Multisig Registry at [A.2.11.1.3.4.2.0.6.1 - Registered Multisigs](7d966e5e-ecb3-4a5b-9111-a70927cfa79a).","contentHash":"d54fe1f70a7558eeafaa19f499d9ac3d43e20253c9734d10739fcb083b4b4c61","addressRefs":[]},"e525c938-7fd2-4e6e-9c01-86cf0783d728":{"id":"e525c938-7fd2-4e6e-9c01-86cf0783d728","doc_no":"A.2.11.1.3.4.1","title":"Multisig Registry Entry Requirements","type":"Core","depth":6,"parentId":"4d80cae1-b28a-4907-8d59-2ebcbba6003d","order":2329,"content":"Each Multisig entry in the Multisig Registry must contain the following information:\n\n- Multisig Name\n- Administrator Entity\n- Multisig Address","contentHash":"3a4e9625cec20c16f935449ae6a67312c35cec97175b7a1736fe572f2b06ceab","addressRefs":[]},"e063a7c5-eb41-489e-8334-b095b785af62":{"id":"e063a7c5-eb41-489e-8334-b095b785af62","doc_no":"A.2.11.1.3.4.2","title":"List Of Registered Multisigs","type":"Active Data Controller","depth":6,"parentId":"4d80cae1-b28a-4907-8d59-2ebcbba6003d","order":2330,"content":"The list of registered Multisigs is defined as Active Data in [A.2.11.1.3.4.2.0.6.1 - Registered Multisigs](7d966e5e-ecb3-4a5b-9111-a70927cfa79a).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Core GovOps.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"1f92fafd643e405c89e5f0e7a69ed02d048360180d3824f9c88f153036f2f527","addressRefs":[]},"7d966e5e-ecb3-4a5b-9111-a70927cfa79a":{"id":"7d966e5e-ecb3-4a5b-9111-a70927cfa79a","doc_no":"A.2.11.1.3.4.2.0.6.1","title":"Registered Multisigs","type":"Active Data","depth":6,"parentId":"4d80cae1-b28a-4907-8d59-2ebcbba6003d","order":2331,"content":"The Multisigs that are registered are:\n\n| **Multisig Name** | **Administrator Entity** | **Multisig Address** |\n|---|---|---|\n| | | |","contentHash":"d420cc76c1b03e2637b89fc3e74b66573d0a013de69b2d708322cafb205b52da","addressRefs":[]},"2a36aafa-cfe3-4ba5-b549-f341fbb4c666":{"id":"2a36aafa-cfe3-4ba5-b549-f341fbb4c666","doc_no":"A.2.11.1.3.5","title":"Determination And Enforcement Of Multisig Security Noncompliance","type":"Core","depth":5,"parentId":"142ed420-18a6-4ab9-9889-cbd9c376d48d","order":2332,"content":"When a Multisig is determined to be noncompliant with the Multisig Security Enforcement Framework, a grace period of forty-eight (48) hours is provided to resolve the issue. If the noncompliance is not resolved within this period, Multisig operations must be immediately stopped, unless an exception is granted by the Protocol Security Workstream Lead. Core GovOps may then determine whether further actions are required to enforce the halt of operations in relation to such Multisig. These provisions apply only after the effective date specified in [A.2.11.1.3.2 - Multisig Security Guidelines](6033699f-1d55-45ba-8eb1-bd8982571cc0).","contentHash":"76c8850867bc8070f10347db00ed336a7691ffa8072c87e06cb7a306c6900f52","addressRefs":[]},"b888a6f2-df29-4254-bc74-8dff265f2697":{"id":"b888a6f2-df29-4254-bc74-8dff265f2697","doc_no":"A.2.12","title":"Purpose System","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":2333,"content":"This Article governs the Purpose System, which aims to fund open-source AI and software projects that benefit the Sky Ecosystem and public good.","contentHash":"843f703038cc34788480b96a508c434ebb5dc1f44397576c61cdc3ac01a71540","addressRefs":[]},"d6d4b091-8143-4a43-a3cf-b5dfa18a8d35":{"id":"d6d4b091-8143-4a43-a3cf-b5dfa18a8d35","doc_no":"A.2.12.1","title":"Funding","type":"Section","depth":3,"parentId":"b888a6f2-df29-4254-bc74-8dff265f2697","order":2334,"content":"This Section must define the elements and infrastructure necessary to implement the Purpose System effectively. This includes establishing a process for allocating purpose funds to individual Agents.","contentHash":"84db828e72ee77d278d4861255b4e5777b791cb06d92c5f617e17861e00db4cc","addressRefs":[]},"a2de9679-22b6-432b-861f-f315d422e51e":{"id":"a2de9679-22b6-432b-861f-f315d422e51e","doc_no":"A.2.12.2","title":"Direct And Specific Impact Solutions","type":"Section","depth":3,"parentId":"b888a6f2-df29-4254-bc74-8dff265f2697","order":2335,"content":"At all times, at least 10% of the Purpose System funds must be used for more direct and specific impact solutions.","contentHash":"6ad5640c00516e72d513cb22c712759e9166139dca9a672807a7b581014082bb","addressRefs":[]},"7be35f96-8230-41d6-aab4-0a76bd705a25":{"id":"7be35f96-8230-41d6-aab4-0a76bd705a25","doc_no":"A.2.13","title":"Ecosystem Entity Grants","type":"Article","depth":2,"parentId":"1ce14bd8-c7b3-4f74-a152-292a8d8ebed0","order":2336,"content":"This Article defines the Ecosystem Entity Grants, which aim to fund the Sky Frontier Foundation and the Fortification Foundation.","contentHash":"5f0d604435a3bb1fd421b9628434ebaf764a03b3e104bc6243c456cab9980d11","addressRefs":[]},"5d5759e4-8077-4af5-9a1a-eaeab5088dd7":{"id":"5d5759e4-8077-4af5-9a1a-eaeab5088dd7","doc_no":"A.2.13.1","title":"Ecosystem Entity Grants","type":"Section","depth":3,"parentId":"7be35f96-8230-41d6-aab4-0a76bd705a25","order":2337,"content":"Information regarding ecosystem entities grants to the Sky Frontier Foundation and the Fortification Foundation is detailed in the documents herein.","contentHash":"da8fe0403a4899716cc312acfc7265c7f64e782ec155dc1ab05eb4eed5cd824e","addressRefs":[]},"1f5d9b2d-d94d-4945-bcf5-74b9152de90c":{"id":"1f5d9b2d-d94d-4945-bcf5-74b9152de90c","doc_no":"A.2.13.1.1","title":"Sky Frontier Foundation Grants","type":"Core","depth":4,"parentId":"5d5759e4-8077-4af5-9a1a-eaeab5088dd7","order":2338,"content":"Information regarding ecosystem entity grants to the Sky Frontier Foundation is detailed in the documents herein.","contentHash":"407aaf62e116e00f6fe1ef4197e741f5e5d20700ab31c7d0f221d6164ada1797","addressRefs":[]},"ecc26bbd-ee6c-4ede-a3da-176cb8857d87":{"id":"ecc26bbd-ee6c-4ede-a3da-176cb8857d87","doc_no":"A.2.13.1.1.1","title":"August 2025 Grant","type":"Core","depth":5,"parentId":"1f5d9b2d-d94d-4945-bcf5-74b9152de90c","order":2339,"content":"The approved and disbursed August 2025 grant to the Sky Frontier Foundation is as follows:\n\n- Recipient: Sky Frontier Foundation\n- Recipient Address: `0xca5183FB9997046fbd9bA8113139bf5a5Af122A0`\n- Transaction Hash: `0x9dff3cf283969f0d6b54347829463aabbcad43e79ebb7ad20c5154e951586e3f`\n- USDS amount: 50,000,000\n- SKY amount: 1,977,443,914.00\n- USDS/SKY LP (UNI-V2) amount: 28,829,858.44\n- DAI amount: 35.41\n- ENS amount: 46,362.27\n- stkAAVE amount: 1,467.08\n- COMP amount: 643.73\n- AAVE amount: 60\n- WETH amount: 0.0296\n\nThe amounts above are rounded down; refer to onchain data for exact figures.","contentHash":"931ec98b521fbe98e996ae5e0899100e1346bd52814a0e304f4d4d0f30fba150","addressRefs":["0xca5183fb9997046fbd9ba8113139bf5a5af122a0"]},"ec2ebbba-6944-44cb-a04d-4572c6bea1e7":{"id":"ec2ebbba-6944-44cb-a04d-4572c6bea1e7","doc_no":"A.2.13.1.2","title":"Fortification Foundation Grants","type":"Core","depth":4,"parentId":"5d5759e4-8077-4af5-9a1a-eaeab5088dd7","order":2340,"content":"Information regarding ecosystem entity grants to the Fortification Foundation is detailed in the documents herein.","contentHash":"cafa6e94e31709d9b58f8fb941520bcc616b3512eb536c9f864fd75193d9e863","addressRefs":[]},"fc6b41c6-f9e3-4690-a75a-6d3d68e8d942":{"id":"fc6b41c6-f9e3-4690-a75a-6d3d68e8d942","doc_no":"A.2.13.1.2.1","title":"August 2025 Grant","type":"Core","depth":5,"parentId":"ec2ebbba-6944-44cb-a04d-4572c6bea1e7","order":2341,"content":"The approved and disbursed August 2025 grant to the Fortification Foundation is as follows:\n\n- Recipient: Fortification Foundation\n- Recipient Address: `0x483413ccCD796Deddee88E4d3e202425d5E891C6`\n- Transaction Hash: `0x9dff3cf283969f0d6b54347829463aabbcad43e79ebb7ad20c5154e951586e3f`\n- USDS amount: 10,000,000\n- SKY amount: 200,000,000","contentHash":"54f748f7415241f7f377b8ba9ebc8c6fd0e823777d100bb9386aef9ccbda60c6","addressRefs":["0x483413cccd796deddee88e4d3e202425d5e891c6"]},"d56538fc-2220-491a-a4d2-7ad6e461d707":{"id":"d56538fc-2220-491a-a4d2-7ad6e461d707","doc_no":"A.3","title":"The Stability Scope","type":"Scope","depth":1,"parentId":null,"order":2342,"content":"The Stability Scope governs the management of the USDS Stablecoin. The USDS Stablecoin must be a permissionless and useful currency available to anyone. Its stability and risk must be managed to generate as much value for Sky and public good as possible.","contentHash":"ba9d3637ffb4574c657132adfbc35bd0307e1dce6cefc600457de48a2aee3d93","addressRefs":[]},"80f168a3-4a01-40dd-bb57-851f48d58912":{"id":"80f168a3-4a01-40dd-bb57-851f48d58912","doc_no":"A.3.1","title":"Core Stability Parameters","type":"Article","depth":2,"parentId":"d56538fc-2220-491a-a4d2-7ad6e461d707","order":2343,"content":"This Article defines methodologies and processes for optimizing and aligning the Core Stability Parameters, which are designed to stabilize the USDS Stablecoin.","contentHash":"7f54a0f91bbaf0d658764408b8bcf5a54449c7ab99f7a2fbf3833968a9c3377d","addressRefs":[]},"4162b64d-fff8-4200-9b6c-86284ff06d08":{"id":"4162b64d-fff8-4200-9b6c-86284ff06d08","doc_no":"A.3.1.1","title":"Role Of Core Executor Agents","type":"Section","depth":3,"parentId":"80f168a3-4a01-40dd-bb57-851f48d58912","order":2344,"content":"This Section defines the role of the Core Executor Agents in managing the Core Stability Parameters.","contentHash":"c53b260d976a503a1bbddafcd57243d5e2c1a06c0f2e54a138668b96d60a419c","addressRefs":[]},"9ced57db-dfcd-4ca3-ba29-b4803c91bb7c":{"id":"9ced57db-dfcd-4ca3-ba29-b4803c91bb7c","doc_no":"A.3.1.1.1","title":"Setting Base Rate","type":"Core","depth":4,"parentId":"4162b64d-fff8-4200-9b6c-86284ff06d08","order":2345,"content":"The Core Executor Agents, in consultation with the Core Council Risk Advisor, must set the Base Rate to ensure (1) a sufficient level of Cash Stablecoins and (2) price stability of USDS and other Stablecoins produced by the Sky Ecosystem. The subdocuments herein define the process that the Core Executor Agents should follow in setting the Base Rate.","contentHash":"bf1fac2528c2708ee920331e09c00dd61c05fefc2b480b2c63e5c423334f7fa2","addressRefs":[]},"e152c03d-5891-4962-867d-a0c42fa7539f":{"id":"e152c03d-5891-4962-867d-a0c42fa7539f","doc_no":"A.3.1.1.1.1","title":"Adjustment Process","type":"Core","depth":5,"parentId":"9ced57db-dfcd-4ca3-ba29-b4803c91bb7c","order":2346,"content":"The Core Executor Agents should modify the Base Rate on a daily basis, as necessary, in consultation with the Core Council Risk Advisor. In doing so, the Core Executor Agents should consider the factors specified in the documents herein.","contentHash":"778aff409215c73f95bcb62fda79d0e4a2b5a9688efaeb73f5e786fa918dcfaa","addressRefs":[]},"839bfb33-5ac5-4e10-9521-65e43dd04464":{"id":"839bfb33-5ac5-4e10-9521-65e43dd04464","doc_no":"A.3.1.1.1.1.1","title":"Level Of Actively Stabilizing Collateral In Lite PSM","type":"Core","depth":6,"parentId":"e152c03d-5891-4962-867d-a0c42fa7539f","order":2347,"content":"PSM ASC is defined as the level of Actively Stabilizing Collateral (see [A.3.3.2.2.1 - Actively Stabilizing Collateral](62495dee-8d2a-45d4-87c4-01150e3db3c8)) in the Lite PSM (see [A.3.3.2.7.1.1 - Lite Peg Stability Module](39473e1a-63f8-433b-a850-08f53b2dcf02)) as a percentage of the Sky Collateral Portfolio (see [A.3.3.1.1 - Minimum Actively Stabilizing Collateral](de00cd5a-91ab-4c04-8ce1-8aa3b7f3c82b)). The Core Executor Agents should consider the level of PSM ASC using the following non-binding guidelines:\n\n- If PSM ASC is above 30%, consider decreasing the Base Rate by approximately 2%;\n- If PSM ASC is between 28% and 30%, consider decreasing the Base Rate by approximately 1%;\n- If PSM ASC is between 26% and 28%, consider decreasing the Base Rate by approximately 0.3%;\n- If PSM ASC is between 24% and 26%, consider maintaining the Base Rate at approximately its current level;\n- If PSM ASC is between 22% and 24%, consider increasing the Base Rate by approximately 0.3%;\n- If PSM ASC is between 20% and 22%, consider increasing the Base Rate by approximately 1%; and\n- If PSM ASC is below 20%, consider increasing the Base Rate by approximately 2%.","contentHash":"75610bb35525bacdee6ed8c6d135f6567161c89a7b1eb997dffa4201d848155a","addressRefs":[]},"0a4f2260-5f9a-4f78-a944-20500b153fec":{"id":"0a4f2260-5f9a-4f78-a944-20500b153fec","doc_no":"A.3.1.1.1.1.2","title":"External Rate Environment","type":"Core","depth":6,"parentId":"e152c03d-5891-4962-867d-a0c42fa7539f","order":2348,"content":"The Core Executor Agents should consider the external interest-rate environment, including the interest rates offered by competitors and funding rates in decentralized finance and traditional finance markets.","contentHash":"183548dec9faf5c83cdac033617d707594193e38f010bf091a28edca67acade0","addressRefs":[]},"4feb630b-d694-42d9-9b69-a6da09affa2c":{"id":"4feb630b-d694-42d9-9b69-a6da09affa2c","doc_no":"A.3.1.1.1.1.2.1","title":"Tools Development","type":"Core","depth":6,"parentId":"e152c03d-5891-4962-867d-a0c42fa7539f","order":2349,"content":"The Core Executor Agents must develop automated tools to monitor the external interest-rate environment to improve the rate-setting process.","contentHash":"c0720c2a5acedfc5917de551970660224f6ebfbc193fea85f330ce19a7bf8061","addressRefs":[]},"a985bebe-4fe6-44e9-8025-78c4f099ef57":{"id":"a985bebe-4fe6-44e9-8025-78c4f099ef57","doc_no":"A.3.1.1.1.1.3","title":"Other Factors","type":"Core","depth":6,"parentId":"e152c03d-5891-4962-867d-a0c42fa7539f","order":2350,"content":"The Core Executor Agents should consider other factors such as supporting long-term market stability, user stability, system sustainability, and growth. In addition, the Core Executor Agents should consider constraints on Primes, including their cost of capital and reaction time, to avoid creating unnecessary volatility in rates.","contentHash":"ec3f8f455cf51107807618e7bb0418be42cda48197ae358e0c448e6dbd3eb392","addressRefs":[]},"7c65e6aa-3218-4636-bfee-545988aca7df":{"id":"7c65e6aa-3218-4636-bfee-545988aca7df","doc_no":"A.3.1.1.2","title":"Setting Other Core Stability Parameters","type":"Core","depth":4,"parentId":"4162b64d-fff8-4200-9b6c-86284ff06d08","order":2351,"content":"When setting the Base Rate, the Core Executor Agents must also set all other Core Stability Parameters so that they maintain their specified relationship to the Base Rate. See [A.3.1.2 - Parameters](86c75c9c-3803-48c1-a897-88d2be7aeb0e). The only exception is the Dai Savings Rate, which must be gradually reduced to 0% as specified in [A.3.1.2.4.1 - Dai Savings Rate Modification](238d8932-633d-44df-a7ed-0ec5a423cc53).","contentHash":"aa9719edae367e59b249c444966b213808ea639aa479b335032f0d9502b961dc","addressRefs":[]},"21a34a01-87a8-4753-be83-ea452b5d388d":{"id":"21a34a01-87a8-4753-be83-ea452b5d388d","doc_no":"A.3.1.1.3","title":"Implementation Of Rate Changes","type":"Core","depth":4,"parentId":"4162b64d-fff8-4200-9b6c-86284ff06d08","order":2352,"content":"The smart contracts that implement all of the Core Stability Parameters must be configured to allow the Core Executor Agents to modify the Core Stability Parameters using the Stability Parameter Bounded External Access Module. See [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).","contentHash":"c769b0774adf5c8a051e422d469a7e62d23b599f47cb5790ec18841f2ce6ac62","addressRefs":[]},"86c75c9c-3803-48c1-a897-88d2be7aeb0e":{"id":"86c75c9c-3803-48c1-a897-88d2be7aeb0e","doc_no":"A.3.1.2","title":"Parameters","type":"Section","depth":3,"parentId":"80f168a3-4a01-40dd-bb57-851f48d58912","order":2353,"content":"This Section defines the Core Stability Parameters.","contentHash":"a6ced75571f51aa4bf8239bfec5a16e5acec16e502154afab3bf223fbe9201cc","addressRefs":[]},"228f9955-6bba-4252-a101-5529e7a300b9":{"id":"228f9955-6bba-4252-a101-5529e7a300b9","doc_no":"A.3.1.2.1","title":"Base Rate","type":"Core","depth":4,"parentId":"86c75c9c-3803-48c1-a897-88d2be7aeb0e","order":2354,"content":"The Base Rate is the key interest rate in the system. It defines all other rates by various spreads. It is expressed as an annual percentage rate.","contentHash":"683a303e871edc5bd2da5856c8de7e89e71ecac009820d81c168b5d4761fa329","addressRefs":[]},"e7be875c-fa61-42af-8986-ec22aceab0e8":{"id":"e7be875c-fa61-42af-8986-ec22aceab0e8","doc_no":"A.3.1.2.1.0.3.1","title":"Spreads - Element Annotation","type":"Annotation","depth":5,"parentId":"228f9955-6bba-4252-a101-5529e7a300b9","order":2355,"content":"The element refers to the differences added or subtracted from the Base Rate to determine other specific rates.","contentHash":"238d6a69fcea2503d6cc49afda4f0dfc3f9aafdaba3b8d6c2143be5ddc2dd6a4","addressRefs":[]},"2674cccb-d779-4868-b83f-8cb86648c88a":{"id":"2674cccb-d779-4868-b83f-8cb86648c88a","doc_no":"A.3.1.2.2","title":"Sky Savings Rate","type":"Core","depth":4,"parentId":"86c75c9c-3803-48c1-a897-88d2be7aeb0e","order":2356,"content":"The Sky Savings Rate (\"SSR\") is the rate USDS holders can earn on their USDS in the Sky Savings Rate smart contracts.","contentHash":"42de7506c2c790331a62709f3cd1e4c4227cf8f615056990956af07a4c0d3fa1","addressRefs":[]},"d16483ff-b83e-490f-a620-1b58cc679c7f":{"id":"d16483ff-b83e-490f-a620-1b58cc679c7f","doc_no":"A.3.1.2.2.1","title":"Relationship To Base Rate","type":"Core","depth":5,"parentId":"2674cccb-d779-4868-b83f-8cb86648c88a","order":2357,"content":"The Sky Savings Rate is 0.3% below the Base Rate. This difference is equal to the sum of (1) the 0.2% Distribution Reward Fee (see [A.2.2.8.1.2.1.3 - Distribution Reward Rate](57384c49-e499-4c69-b22c-8e1f1dd34759)) and (2) the 0.1% Sky Spread (see [A.3.2.2.4.2.3.3.1 - Sky Spread](c160f99c-c3d8-41e9-a3d1-cde514b7a2da)).","contentHash":"a2dd610fdb7ade28c88a698bdb010b199718236d3ac1bf264e203073f525ee90","addressRefs":[]},"1c8bb297-52a6-4774-a76d-e457ae5f5862":{"id":"1c8bb297-52a6-4774-a76d-e457ae5f5862","doc_no":"A.3.1.2.2.2","title":"Sky Savings Rate Modification","type":"Core","depth":5,"parentId":"2674cccb-d779-4868-b83f-8cb86648c88a","order":2358,"content":"The Sky Savings Rate can be modified through either Executive Votes or the Stability Parameter Bounded External Access Module. See [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).","contentHash":"77b6dd6572519f7bded6b237c50ceaf32e8cdc0d3fc283259b6f0a9d69570c15","addressRefs":[]},"e3a7ca35-0569-4867-bc64-e732622bda21":{"id":"e3a7ca35-0569-4867-bc64-e732622bda21","doc_no":"A.3.1.2.2.2.1","title":"Sky Savings Rate Stability Parameter Bounded External Access Module Parameters","type":"Core","depth":6,"parentId":"1c8bb297-52a6-4774-a76d-e457ae5f5862","order":2359,"content":"The Stability Parameter Bounded External Access Module parameters for the Sky Savings Rate are:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"4cdefbc7ef9eb8352973e52c190dd2e1aea9ba74ea319ab307627cb65d8c372d","addressRefs":[]},"aff1868f-66aa-4252-851f-9343567a52eb":{"id":"aff1868f-66aa-4252-851f-9343567a52eb","doc_no":"A.3.1.2.2.3","title":"Sky Savings Rate Current Value","type":"Core","depth":5,"parentId":"2674cccb-d779-4868-b83f-8cb86648c88a","order":2360,"content":"The current value of the Sky Savings Rate can be obtained by calling the `ssr()` function on the sUSDS contract located on the Ethereum Mainnet at `0xa3931d71877C0E7a3148CB7Eb4463524FEc27fbD`.\n\nThe `ssr()` function returns a per-second compounding rate in RAY precision (10^27). The equivalent annualized rate, compounded over a 365-day year (31,536,000 seconds), is given by the formula:\n\n`annualized rate = (ssr() / 1E27)^31536000 - 1`\n\nThe result is a decimal rate (e.g., 0.0365 represents 3.65% per year).","contentHash":"62997554cfd70e5553fda0f2c978897603a234b68acfc9f610082dacdf06c904","addressRefs":["0xa3931d71877c0e7a3148cb7eb4463524fec27fbd"]},"012c953b-c522-4ea3-939b-3282af4e1d7e":{"id":"012c953b-c522-4ea3-939b-3282af4e1d7e","doc_no":"A.3.1.2.3","title":"Agent Rate","type":"Core","depth":4,"parentId":"86c75c9c-3803-48c1-a897-88d2be7aeb0e","order":2361,"content":"The Agent Rate is the rate that Prime Agents earn on Unrewarded USDS, Dai, and sUSDS balances that they hold.","contentHash":"9910e2228ce646376c43577eac0dc9a70ee155821626f9211d51192d7a760e56","addressRefs":[]},"4e49c66c-3361-48bb-9a18-a0217278488e":{"id":"4e49c66c-3361-48bb-9a18-a0217278488e","doc_no":"A.3.1.2.3.1","title":"Relationship To Base Rate","type":"Core","depth":5,"parentId":"012c953b-c522-4ea3-939b-3282af4e1d7e","order":2362,"content":"The Agent Rate is 0.1% below the Base Rate. This is equal to the Sky Savings Rate plus the 0.2% Distribution Reward Fee (see [A.2.2.8.1.2.1.3 - Distribution Reward Rate](57384c49-e499-4c69-b22c-8e1f1dd34759)).","contentHash":"1e757b819f981bde5d4eeed6fd172b9b62e787c59fe3c1d78449cba0134125b8","addressRefs":[]},"3fbca67b-f75d-48f8-9459-3cba592f835b":{"id":"3fbca67b-f75d-48f8-9459-3cba592f835b","doc_no":"A.3.1.2.3.2","title":"Treatment Of USDS and Dai Balances","type":"Core","depth":5,"parentId":"012c953b-c522-4ea3-939b-3282af4e1d7e","order":2363,"content":"Prime Agents receive the full Agent Rate on Unrewarded USDS and Dai balances through the Monthly Settlement Cycle, as specified in [A.3.1.2.3.6 - Settlement](eed3d922-7bb8-4cee-97a4-47e902a1c937).","contentHash":"917acd2609329fb4a6b75f03d34f6ed85c6a01469ba7239f8b120771d959c3a4","addressRefs":[]},"b1cc2cb1-aff6-4b7a-bb32-bdf56fc7fd2f":{"id":"b1cc2cb1-aff6-4b7a-bb32-bdf56fc7fd2f","doc_no":"A.3.1.2.3.3","title":"Treatment Of sUSDS Balances","type":"Core","depth":5,"parentId":"012c953b-c522-4ea3-939b-3282af4e1d7e","order":2364,"content":"Prime Agents receive the Agent Rate on sUSDS balances in a modified form. sUSDS balances already earn the Sky Savings Rate. In addition to this, sUSDS balances earn additional compensation of 0.20% (see [A.2.2.8.1.2.1.3 - Distribution Reward Rate](57384c49-e499-4c69-b22c-8e1f1dd34759)) to account for the Distribution Reward Rate that is paid through the Monthly Settlement Cycle, as specified in [A.3.1.2.3.6 - Settlement](eed3d922-7bb8-4cee-97a4-47e902a1c937).","contentHash":"a480c46ebf31d808502a204c4d339cf64817c6c2d45196aa32b4fd82f9969eec","addressRefs":[]},"e15caed7-276c-4489-95dc-9ba628566bf4":{"id":"e15caed7-276c-4489-95dc-9ba628566bf4","doc_no":"A.3.1.2.3.4","title":"Spark","type":"Core","depth":5,"parentId":"012c953b-c522-4ea3-939b-3282af4e1d7e","order":2365,"content":"Spark is entitled to a higher Agent Rate equal to the Base Rate on USDS and sUSDS balances held in Peg Stability Modules. See [A.3.3.2.1.1 - Peg Stability Module](0082c12d-f1a7-46ff-a4aa-5fe42ece1a4d). The Agent Rate earned by Spark is still subject to the limitations set forth in [A.3.1.2.3.5 - Limitations For Prime Agents Receiving Subsidized Rate](7f6c1ab6-7674-41b0-9522-7e7e5a1cab3d).","contentHash":"f272c07bb805e633e9e7ec7af1ab36449a506941db8137199f15ec998eae4be2","addressRefs":[]},"7f6c1ab6-7674-41b0-9522-7e7e5a1cab3d":{"id":"7f6c1ab6-7674-41b0-9522-7e7e5a1cab3d","doc_no":"A.3.1.2.3.5","title":"Limitations For Prime Agents Receiving Subsidized Rate","type":"Core","depth":5,"parentId":"012c953b-c522-4ea3-939b-3282af4e1d7e","order":2366,"content":"If a Prime Agent is borrowing funds from Sky at a Subsidized Rate, as defined in [A.3.1.2.5.2 - Subsidized Rate](ceceb90b-57d1-43db-9e52-133532c373fd), then the Agent Rate earned by that Prime Agent shall be limited. Specifically, if the standard Agent Rate would exceed the Prime Agent’s Subsidized Rate, the Prime Agent will earn the Subsidized Rate on those balances. The difference between what would have been the standard Agent Rate earnings and the earnings at the Subsidized Rate is effectively retained by Sky. This adjustment is processed as part of the Monthly Settlement Cycle, as specified in [A.3.1.2.3.6 - Settlement](eed3d922-7bb8-4cee-97a4-47e902a1c937). If the standard Agent Rate is less than or equal to the Subsidized Rate, the standard Agent Rate applies.","contentHash":"949726be23e7a8cf235482a9d9c9d6edef5b9f0d5332e2471488a6e37df94b56","addressRefs":[]},"eed3d922-7bb8-4cee-97a4-47e902a1c937":{"id":"eed3d922-7bb8-4cee-97a4-47e902a1c937","doc_no":"A.3.1.2.3.6","title":"Settlement","type":"Core","depth":5,"parentId":"012c953b-c522-4ea3-939b-3282af4e1d7e","order":2367,"content":"Any compensation due to or from Prime Agents so that they earn the Agent Rate on USDS, Dai, and sUSDS balances is paid as part of the Monthly Settlement Cycle. See [A.2.4 - Sky Core Monthly Settlement Cycle](6f8d5065-d6ff-4add-9a28-eadeffa7ed1a).","contentHash":"bbb475ba276763994ce23ec206ad7592e2654f372a11fdd14b1cdf617e0b3777","addressRefs":[]},"d220731b-35db-4803-8a74-1c470a5ad693":{"id":"d220731b-35db-4803-8a74-1c470a5ad693","doc_no":"A.3.1.2.4","title":"Dai Savings Rate","type":"Core","depth":4,"parentId":"86c75c9c-3803-48c1-a897-88d2be7aeb0e","order":2368,"content":"The Dai Savings Rate (\"DSR\") is the rate Dai holders can earn on their Dai in the Dai Savings Rate smart contracts.","contentHash":"9b3578615970cf993cd5e0c955d4512193aa2e30bb39dcaa74039d12b20da774","addressRefs":[]},"238d8932-633d-44df-a7ed-0ec5a423cc53":{"id":"238d8932-633d-44df-a7ed-0ec5a423cc53","doc_no":"A.3.1.2.4.1","title":"Dai Savings Rate Modification","type":"Core","depth":5,"parentId":"d220731b-35db-4803-8a74-1c470a5ad693","order":2369,"content":"The Dai Savings Rate can be modified through either Executive Votes or the Stability Parameter Bounded External Access Module. See [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n\nThe Dai Savings Rate must gradually be reduced to 0% over time.","contentHash":"d87039289ee6dcb45d029c1e2f84f1233d15be5a33c30df3a0be0421f4103892","addressRefs":[]},"335dd92b-cbd8-4d98-8d23-1dd57d98487d":{"id":"335dd92b-cbd8-4d98-8d23-1dd57d98487d","doc_no":"A.3.1.2.4.1.1","title":"Dai Savings Rate Stability Parameter Bounded External Access Module Parameters","type":"Core","depth":6,"parentId":"238d8932-633d-44df-a7ed-0ec5a423cc53","order":2370,"content":"The Stability Parameter Bounded External Access Module parameters for the Dai Savings Rate are:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"89ad53cdf775aeca5afae44396e35b6d2df535a85d6b590df791514f1e03d787","addressRefs":[]},"6b2b7302-e63b-457e-afeb-daab5ca7a7de":{"id":"6b2b7302-e63b-457e-afeb-daab5ca7a7de","doc_no":"A.3.1.2.5","title":"Agent Credit Line Borrow Rate","type":"Core","depth":4,"parentId":"86c75c9c-3803-48c1-a897-88d2be7aeb0e","order":2371,"content":"The Agent Credit Line Borrow Rate is the annual percentage rate that Agents must pay to Sky Core to receive USDS liquidity into their respective vaults.","contentHash":"d62f4ff3e7511a6521b7da7cf9f909634bf6fe513dc2e4c737f0f8997d973f3a","addressRefs":[]},"4659cbf0-78c2-469b-8432-883e5c931dd1":{"id":"4659cbf0-78c2-469b-8432-883e5c931dd1","doc_no":"A.3.1.2.5.1","title":"Relationship To Base Rate","type":"Core","depth":5,"parentId":"6b2b7302-e63b-457e-afeb-daab5ca7a7de","order":2372,"content":"The Agent Credit Line Borrow Rate is equal to the Base Rate unless variable pricing has been activated pursuant to [A.1.10.2.3.2.2.1.4.2.1 - Use Of Prime Spell Security Registry In Prime Agent Credit Rating System](4c165fcc-59e5-45c8-866d-c5c68192e591). Upon activation, the Agent Credit Line Borrow Rate will vary by Prime Agent according to its Credit Rating.","contentHash":"d0b12c861a85a56931617fcd9d3bf5fb01c297c575440b7c14c717d1d868c803","addressRefs":[]},"ceceb90b-57d1-43db-9e52-133532c373fd":{"id":"ceceb90b-57d1-43db-9e52-133532c373fd","doc_no":"A.3.1.2.5.2","title":"Subsidized Rate","type":"Core","depth":5,"parentId":"6b2b7302-e63b-457e-afeb-daab5ca7a7de","order":2373,"content":"Prime Agents may temporarily be able to borrow specified amounts from Sky Core at a Subsidized Rate below the Base Rate under the terms of an Ecosystem Accord entered into between Sky and the Prime Agent.","contentHash":"00e68117f805ad235db1be37f4b68d0ea73d8eaa3e6cb5d8e7f5cf493e8f2bae","addressRefs":[]},"b914352c-f270-46e8-991a-468a4b01dc49":{"id":"b914352c-f270-46e8-991a-468a4b01dc49","doc_no":"A.3.1.2.5.3","title":"Use Of Funds","type":"Core","depth":5,"parentId":"6b2b7302-e63b-457e-afeb-daab5ca7a7de","order":2374,"content":"Funds borrowed by Agents from Sky at the Agent Credit Line Borrow Rate must be deposited into the Agent’s Allocation Vault and used to invest in Allocation System Instances. See [A.2.2.9.1 - Allocation System Primitive](9db14ab7-bb4b-4751-8084-843bd4359f2a). These funds may not be transferred to the Agent’s SubProxy account or otherwise outside of the Agent’s designated accounts for its Allocation System Primitive.","contentHash":"fd4d4826577ffcf98832c1fd03d29538f6859815d91f710b8a1b2f3f9c1ccbf5","addressRefs":[]},"9835ebab-59cc-4a2b-b030-3b07b4e9203d":{"id":"9835ebab-59cc-4a2b-b030-3b07b4e9203d","doc_no":"A.3.1.2.5.4","title":"Accrued Interest","type":"Core","depth":5,"parentId":"6b2b7302-e63b-457e-afeb-daab5ca7a7de","order":2375,"content":"Interest accrues on borrowed funds and is reflected in the Allocation Vault balance. Prime Agents must regularly transfer interest payments to the Allocation Vault to pay down accrued interest, ensuring the Allocation Vault balance returns to the principal amount only. Any accrued but unpaid interest reduces the Prime Agent's available Total Risk Capital. See [A.3.2.1.2.1 - Total Risk Capital Definition](6f6b25d6-f73c-4733-ba37-12a0a411433c).","contentHash":"c4eab9eaf380aa340bd9da4e6002302cdf2eabac14820f2b0e856d3400e4e7dc","addressRefs":[]},"926fb13d-efdd-4a83-a3dc-db1448a106f5":{"id":"926fb13d-efdd-4a83-a3dc-db1448a106f5","doc_no":"A.3.1.2.5.5","title":"Prime Agent Credit Rating System","type":"Core","depth":5,"parentId":"6b2b7302-e63b-457e-afeb-daab5ca7a7de","order":2376,"content":"After the development of a Prime Agent Credit Rating System, the Agent Credit Line Borrow Rate will vary based on the Credit Rating of each Prime Agent. The Credit Rating for a Prime Agent will take into account factors including the Encumbrance Ratio and the Prime Spell Security Incident Registry.","contentHash":"2d068f40408e011f2fc3e652511a934de88f2d92ab88f86e02bc59778ab7ed3b","addressRefs":[]},"2f658a82-a8d2-4bd1-be5c-906e4733400d":{"id":"2f658a82-a8d2-4bd1-be5c-906e4733400d","doc_no":"A.3.1.0.3.1","title":"Methodologies - Element Annotation","type":"Annotation","depth":3,"parentId":"80f168a3-4a01-40dd-bb57-851f48d58912","order":2377,"content":"The element \"methodologies\" refers to the systematic approaches or frameworks used to achieve the specific objective of optimizing and aligning the Core Stability Parameters.","contentHash":"47e8420bb82d14efcb95af5de00a90d4f512a6a7744891ebfc2ce268e7e0d287","addressRefs":[]},"fa290d52-16ee-49c7-b05c-0b53f3781d39":{"id":"fa290d52-16ee-49c7-b05c-0b53f3781d39","doc_no":"A.3.1.0.3.2","title":"Optimizing And Aligning - Element Annotation","type":"Annotation","depth":3,"parentId":"80f168a3-4a01-40dd-bb57-851f48d58912","order":2378,"content":"The element \"optimizing\" refers to the process of making the Core Stability Parameters as effective as possible in achieving their goal of stabilizing the USDS Stablecoin. The element \"aligning\" refers to ensuring that these parameters are consistent and work in harmony with the objectives of Sky and with each other to prevent conflicts or discrepancies that could undermine stability.","contentHash":"b61080eaade75c0e32bf8e26f7b1a20692ff195cfa609e489f0336224345c93a","addressRefs":[]},"a740b3eb-9500-4134-b216-6dd97d4363b8":{"id":"a740b3eb-9500-4134-b216-6dd97d4363b8","doc_no":"A.3.1.0.3.3","title":"Processes - Element Annotation","type":"Annotation","depth":3,"parentId":"80f168a3-4a01-40dd-bb57-851f48d58912","order":2379,"content":"The element \"processes\" refers to the step-by-step procedures or sequences of actions carried out to implement the methodologies referenced in the Target Document.","contentHash":"f69b97049c5e8f01f4fc2818094073a4575366cbe0a62a42b6cb873e7bbc049d","addressRefs":[]},"f90156d0-6dd2-4a0d-9981-b3079368fbc0":{"id":"f90156d0-6dd2-4a0d-9981-b3079368fbc0","doc_no":"A.3.1.0.3.4","title":"Stabilize - Element Annotation","type":"Annotation","depth":3,"parentId":"80f168a3-4a01-40dd-bb57-851f48d58912","order":2380,"content":"The element \"stabilize\" refers to the objective of maintaining USDS’s value within a narrow range, preventing significant fluctuations that could lead to volatility. USDS should be worth $1 USD to fulfill its promise of being a Stablecoin.","contentHash":"9cf6ee01596ad4c082f60906064f3f1fcb28bb8ec7b9a70810663b762fd1c814","addressRefs":[]},"55999acf-75fe-4adf-8584-9746ef50d3e4":{"id":"55999acf-75fe-4adf-8584-9746ef50d3e4","doc_no":"A.3.2","title":"Risk Capital","type":"Article","depth":2,"parentId":"d56538fc-2220-491a-a4d2-7ad6e461d707","order":2381,"content":"Prime Agents who invest capital from Sky’s Collateral Portfolio using the Allocation System Primitive must hold Risk Capital to protect Sky from potential losses on these investments. This Article sets forth the framework governing Risk Capital.","contentHash":"344ee31c3bf17c9b7ef75dd3c0228b9b4756275c39fbf630b6c51066cb56b95c","addressRefs":[]},"ee3a912d-c340-41ee-b33e-45e72f215d49":{"id":"ee3a912d-c340-41ee-b33e-45e72f215d49","doc_no":"A.3.2.1","title":"Conceptual Framework","type":"Section","depth":3,"parentId":"55999acf-75fe-4adf-8584-9746ef50d3e4","order":2382,"content":"This Section defines the conceptual framework for Risk Capital.","contentHash":"3e520aa6f7e0169b9f26d0810e524d8414e0b528d0df2c5ec2e43d4e94d0e09b","addressRefs":[]},"b6597fb4-d347-44f4-8780-b9a4116c1a36":{"id":"b6597fb4-d347-44f4-8780-b9a4116c1a36","doc_no":"A.3.2.1.1","title":"Required Risk Capital","type":"Core","depth":4,"parentId":"ee3a912d-c340-41ee-b33e-45e72f215d49","order":2383,"content":"The documents herein define the conceptual framework for determining the Aggregate Required Risk Capital (RRC) that Prime Agents are required to hold to protect Sky from risks on their investments.","contentHash":"ad76d7d51436087ba3c13b5e0abc5157e125f9ce16bed056bc49b6ee30bdc3f5","addressRefs":[]},"3828778e-0197-4ce9-a836-6770d04f2ea9":{"id":"3828778e-0197-4ce9-a836-6770d04f2ea9","doc_no":"A.3.2.1.1.1","title":"Capital Requirement Ratio","type":"Core","depth":5,"parentId":"b6597fb4-d347-44f4-8780-b9a4116c1a36","order":2384,"content":"The Capital Requirement Ratio (CRR) with respect to one or more Instances is the Required Risk Capital with respect to such Instances divided by the amount of capital from Sky’s Collateral Portfolio invested in such Instances.\n\nRisk Capital requirements in the Risk Framework may be specified either as an amount of RRC or as a CRR. If a CRR is specified, then the RRC is equal to the amount of capital from Sky’s Collateral Portfolio invested in the relevant Instances times the CRR.\n\nFor example, if a certain Instance has a CRR of 5% and 100,000,000 USDS is invested in the Instance, then the RRC is 5,000,000 USDS.\n\nCRR may be specified in aggregate (Aggregate CRR), for a particular Instance (Instance CRR), or for a particular type of risk with respect to an Instance (Instance Financial CRR, Instance Smart Contract CRR, or Instance Administrative CRR).","contentHash":"e2a67cad1d5966bb62a1b2b5a6072ffeba67929d259c8f8d977a49a5070d5477","addressRefs":[]},"6aed5cc1-9671-4b73-88a9-fdd86ac93ece":{"id":"6aed5cc1-9671-4b73-88a9-fdd86ac93ece","doc_no":"A.3.2.1.1.2","title":"Aggregate RRC","type":"Core","depth":5,"parentId":"b6597fb4-d347-44f4-8780-b9a4116c1a36","order":2385,"content":"The Aggregate RRC that a Prime Agent must maintain is equal to the sum of the Instance Total RRC for each Active Instance of the Allocation System Primitive that the Prime Agent has deployed.","contentHash":"9da001b079287d3338fdae8c5b7f0a69fd035a5596c4ffc9b6c88e64a84eb9f8","addressRefs":[]},"5fe6b54c-cc68-4f8a-8d1e-5044af941afe":{"id":"5fe6b54c-cc68-4f8a-8d1e-5044af941afe","doc_no":"A.3.2.1.1.3","title":"Instance Total RRC","type":"Core","depth":5,"parentId":"b6597fb4-d347-44f4-8780-b9a4116c1a36","order":2386,"content":"The Instance Total RRC for an Instance is equal to the sum of the Instance Financial RRC, Instance Smart Contract RRC, and Instance Administrative RRC for that Instance. See [A.3.2.1.1.4 - Instance Financial RRC](ba1d5c0e-399f-47a6-b5d4-b3f5477d5787), [A.3.2.1.1.5 - Instance Smart Contract RRC](4b4ea578-28b4-481c-9abd-d34c5a4f383c), and [A.3.2.1.1.6 - Instance Administrative RRC](c2b60f0d-6555-463c-9ad3-2a9746be77c5).","contentHash":"42069f67bcc777baf45ec70966360736d3da4a2e212700b7851f7b791a4e512f","addressRefs":[]},"4ce93e4b-e842-475b-bf85-d814e7e9d19c":{"id":"4ce93e4b-e842-475b-bf85-d814e7e9d19c","doc_no":"A.3.2.1.1.3.1","title":"Incorporation Of Additional Types Of RRC","type":"Core","depth":6,"parentId":"5fe6b54c-cc68-4f8a-8d1e-5044af941afe","order":2387,"content":"Additional types of RRC reflecting other risk factors, including legal risk and oracle risk, will be incorporated in future iterations of the Risk Framework.","contentHash":"2b8c8b5bc200d3328e9bd19ab4cac7c19c094c75cbc5013b040c3a51ae096bbc","addressRefs":[]},"268af0e9-be3d-458e-9ccd-5a560abc7540":{"id":"268af0e9-be3d-458e-9ccd-5a560abc7540","doc_no":"A.3.2.1.1.3.2","title":"Inability To Calculate Types Of RRC","type":"Core","depth":6,"parentId":"5fe6b54c-cc68-4f8a-8d1e-5044af941afe","order":2388,"content":"If Instance Financial RRC, Instance Smart Contract RRC, or Instance Administrative RRC for an Instance cannot be calculated then the Instance Total RRC is 100%.","contentHash":"946ac3eefb69c5e9e9b7168ea3f3cf4b05537e065bef6b958c15f21263be6293","addressRefs":[]},"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787":{"id":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","doc_no":"A.3.2.1.1.4","title":"Instance Financial RRC","type":"Core","depth":5,"parentId":"b6597fb4-d347-44f4-8780-b9a4116c1a36","order":2389,"content":"The documents herein define the conceptual framework for determining the Instance Financial RRC required to protect Sky from financial risk arising from an Instance of the Allocation System Primitive.","contentHash":"ef831d8fcff74a5663cedd2ee10d8c884b1e869f12571927600d9473128ec55f","addressRefs":[]},"622580fb-1153-4ef7-8196-4e643f2178b7":{"id":"622580fb-1153-4ef7-8196-4e643f2178b7","doc_no":"A.3.2.1.1.4.1","title":"Introduction","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2390,"content":"The conceptual framework for financial risk is designed to ensure that Prime Agents hold sufficient capital to cover potential losses on their investments in case of an extreme market event. The Financial Risk Framework is based on the Basel Accords developed by the Committee on Bank Supervision, including Basel II, Basel III, and Basel IV. These frameworks are then adapted to reflect the differences between traditional finance and decentralized finance.","contentHash":"c0ca5aed0d17088f84fe934e96ebe985487488381c5305b95214dfd80bf1e6fd","addressRefs":[]},"3d1f35bf-4342-45cd-b151-090b241c7ba1":{"id":"3d1f35bf-4342-45cd-b151-090b241c7ba1","doc_no":"A.3.2.1.1.4.2","title":"Financial Risk Categories","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2391,"content":"Financial risk can be divided into three categories, as specified in the documents herein. These categories of risk are interrelated, so Instance Financial RRC is not directly associated with these risk categories. Instead, risk models are developed for different asset classes, as specified in [A.3.2.1.1.4.3 - Financial Risk Models](2af9fa64-ab25-4017-920c-f1c07dff4c06). The development of each of these risk models is informed by considerations regarding how each of the financial risk categories impacts the specific asset.","contentHash":"7a2893a071278f290b954252c73fd72d7bceb16fc5761bc1d26c01f04d2424cc","addressRefs":[]},"ca07880e-7bc4-4f18-a59a-2b5a8cd4374e":{"id":"ca07880e-7bc4-4f18-a59a-2b5a8cd4374e","doc_no":"A.3.2.1.1.4.2.1","title":"Credit Risk","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2392,"content":"Credit risk is the risk that a loan or other debt instrument will not be repaid according to agreed terms.","contentHash":"3218b4acf8d73829e206629a8bbaff8c6e3cd804cc3556d53d977413b36bfb66","addressRefs":[]},"e0dc140f-8172-497d-8576-ce24a7464e89":{"id":"e0dc140f-8172-497d-8576-ce24a7464e89","doc_no":"A.3.2.1.1.4.2.2","title":"Market Risk","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2393,"content":"Market risk is the risk that a financial asset will decline in value due to market conditions or changes in investor perceptions of the asset.","contentHash":"087dae1bf2337c8b66616db6d642b69eabf41d393ec48e5f4b60492f5fadd840","addressRefs":[]},"547571b1-83ae-4977-8f39-b136e6d52b9c":{"id":"547571b1-83ae-4977-8f39-b136e6d52b9c","doc_no":"A.3.2.1.1.4.2.3","title":"Liquidity Risk","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2394,"content":"Liquidity risk is the risk that an asset cannot be sold quickly enough, or in sufficient quantity, at its fair market value without causing a significant price impact.","contentHash":"93284453798b4e5c89fdbc947b26708699f92679830d30fd8d39c6024d38a5ec","addressRefs":[]},"2af9fa64-ab25-4017-920c-f1c07dff4c06":{"id":"2af9fa64-ab25-4017-920c-f1c07dff4c06","doc_no":"A.3.2.1.1.4.3","title":"Financial Risk Models","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2395,"content":"The conceptual framework for financial risk is implemented through asset class specific risk models. The documents herein define the asset classes that risk models exist or are being developed for, including the high level approach and examples of relevant assets.","contentHash":"7e132776e5a323e73784edaa6a6a6ab3aa84a0f63d9592c6f63e4c134785e3d6","addressRefs":[]},"419a1d00-fbae-4d26-bd47-8f57677d8001":{"id":"419a1d00-fbae-4d26-bd47-8f57677d8001","doc_no":"A.3.2.1.1.4.3.1","title":"Fully Implemented Risk Models","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2396,"content":"The documents herein define fully implemented asset-class-specific risk models.","contentHash":"2abc4bfec4f7abcfea5935e751de99ac9e1833b426d9850ed25b37ac96cb99de","addressRefs":[]},"b2c5ee5d-81f6-4066-94b5-e9d1b781cbc9":{"id":"b2c5ee5d-81f6-4066-94b5-e9d1b781cbc9","doc_no":"A.3.2.1.1.4.3.1.1","title":"Lending Markets","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2397,"content":"The model for lending markets focuses on Credit Risk by incorporating asset volatility and liquidity factors. This model can be applied to lending markets such as SparkLend, Aave, Morpho, Fluid, and Maple. The implementation of the model for lending markets is specified in [A.3.2.2.1.1.1.1 - Lending Markets](d4e9c9e0-eeab-4399-99a0-5f72ff0d0e43).","contentHash":"e47248f6af730bc475ee1bcb042c131795973a91ccfba65e38fb7a2acb3d1f59","addressRefs":[]},"72076b08-d4f4-4cbf-af6d-379363cade39":{"id":"72076b08-d4f4-4cbf-af6d-379363cade39","doc_no":"A.3.2.1.1.4.3.1.2","title":"Real World Assets","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2398,"content":"The model for Real World Assets is based on the direct application of existing frameworks to evaluate the risk of tokenized Real World Assets. The implementation of the model for Real World Assets is specified in [A.3.2.2.1.1.1.5 - Real World Assets](79c20bfd-f724-482e-8aae-52c962b8268a).","contentHash":"910da14fce2d4b6873999c8f713e839ece6f7559c10fd5acb15a823356d8e917","addressRefs":[]},"81ca88bf-3f6a-4d10-a3e2-d47cf6636d7d":{"id":"81ca88bf-3f6a-4d10-a3e2-d47cf6636d7d","doc_no":"A.3.2.1.1.4.3.2","title":"Pending Risk Models","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2399,"content":"The documents herein define pending asset-class-specific risk models.","contentHash":"9f717b9bcf95082a5ea04f02dda1cb4ffee52d23a924c3fa39eac540358f0daa","addressRefs":[]},"8e518098-6a0b-4a31-b726-0739000a51ed":{"id":"8e518098-6a0b-4a31-b726-0739000a51ed","doc_no":"A.3.2.1.1.4.3.2.1","title":"Perpetual Positions","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2400,"content":"The model for perpetual positions uses a modified Credit Risk model to evaluate the risk of tokenized delta-neutral positions, such as Ethena and Resolv. The implementation of the model for perpetual positions is specified in [A.3.2.2.1.1.1.2 - Perpetual Positions](69fac7fa-6168-4b74-99cc-28b557826556).","contentHash":"bbc21d07edc30fe71b90733013aba8057b58e7255174f30221db7a5817810c59","addressRefs":[]},"38580dc9-dc5b-4842-88a2-7ab6eb3fcb14":{"id":"38580dc9-dc5b-4842-88a2-7ab6eb3fcb14","doc_no":"A.3.2.1.1.4.3.2.2","title":"Direct Exposures","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2401,"content":"The model for direct exposures combines Market Risk and Liquidity Risk to evaluate the risk of direct asset holdings of volatile cryptoassets, such as ETH, stETH, and WBTC. The implementation of the model for direct exposures is specified in [A.3.2.2.1.1.1.3 - Direct Exposures](69d0776b-786c-408b-b76a-860ea60b6b9a).","contentHash":"0e5bdba6ad17fb60706ec24d37c79e38eba47491ad287404bac88d976cef94a4","addressRefs":[]},"1d4cd705-2892-4b59-82e8-609c4649652d":{"id":"1d4cd705-2892-4b59-82e8-609c4649652d","doc_no":"A.3.2.1.1.4.3.2.3","title":"Bond-Like Instruments","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2402,"content":"The model for bond-like instruments uses a modified Credit Risk model to evaluate the risk of cryptoassets with duration risk, such as Pendle’s PT-tokens. The implementation of the model for bond-like instruments is specified in [A.3.2.2.1.1.1.4 - Bond-Like Instruments](da1a154c-6db8-4012-91a7-31ea4e73e95d).","contentHash":"66a4fac887f7c5da221fd68bcd24c41a9afd9df7a35d11c6120ef965d5899328","addressRefs":[]},"0658e6cd-d785-498a-94c4-71cfbc319c24":{"id":"0658e6cd-d785-498a-94c4-71cfbc319c24","doc_no":"A.3.2.1.1.4.3.2.4","title":"Cash Stablecoins","type":"Core","depth":6,"parentId":"ba1d5c0e-399f-47a6-b5d4-b3f5477d5787","order":2403,"content":"The model for Cash Stablecoins is based on identifying stablecoins, such as USDC and USDT, that do not present significant Market Risk, Credit Risk, or Liquidity Risk. The implementation of the model for Cash Stablecoins is specified in [A.3.2.2.1.1.1.6 - Cash Stablecoins](3c0a9e8b-4a0b-4059-87a4-155deaee0486).","contentHash":"eb9f0a8d15cc784f0eb0ae0391ea8c5c0d89712cdece00fb4ce5cf1765341006","addressRefs":[]},"4b4ea578-28b4-481c-9abd-d34c5a4f383c":{"id":"4b4ea578-28b4-481c-9abd-d34c5a4f383c","doc_no":"A.3.2.1.1.5","title":"Instance Smart Contract RRC","type":"Core","depth":5,"parentId":"b6597fb4-d347-44f4-8780-b9a4116c1a36","order":2404,"content":"The documents herein define the conceptual framework for determining the Instance Smart Contract RRC required to protect Sky from smart contract risk arising from an Instance of the Allocation System Primitive.","contentHash":"3d1dc4f46f33d8810e8b40255543814afaa7b4ee38f0d95a94081037a8699b1a","addressRefs":[]},"8536fbd1-674d-4982-bd50-0bacf0986ce2":{"id":"8536fbd1-674d-4982-bd50-0bacf0986ce2","doc_no":"A.3.2.1.1.5.1","title":"Definition","type":"Core","depth":6,"parentId":"4b4ea578-28b4-481c-9abd-d34c5a4f383c","order":2405,"content":"Smart Contract Risk refers to the risk that an investment through the Allocation System will experience a loss of funds due to a bug or technical exploit. This risk may arise from the protocol invested in or other aspects of the investment such as bridging requirements.","contentHash":"fdd38def37e03cee7a38031a136bda0f7e157ea3d15f83b80102a6a1279702dd","addressRefs":[]},"3cdbe77b-5df8-4ebb-9604-65db818abe69":{"id":"3cdbe77b-5df8-4ebb-9604-65db818abe69","doc_no":"A.3.2.1.1.5.2","title":"Risk Rating","type":"Core","depth":6,"parentId":"4b4ea578-28b4-481c-9abd-d34c5a4f383c","order":2406,"content":"The determination of Smart Contract Risk should initially be based on an evaluation of the risk that the investment could experience losses due to a bug or technical exploit. This determination should take into account factors such as (1) the technical complexity of the code base (e.g. cyclomatic complexity, decision points, number of external calls, lines of code), (2) the number, quality, and recency of audits, and (3) the \"Lindiness\" of the relevant smart contracts.","contentHash":"ae7ae1676fbd5bb3c288a095667b4e45d7011d0c65d3b406ebd52ae0661cf2d5","addressRefs":[]},"eee90ace-5ee9-4efe-be26-6d3597d8b4a1":{"id":"eee90ace-5ee9-4efe-be26-6d3597d8b4a1","doc_no":"A.3.2.1.1.5.3","title":"Required Risk Capital","type":"Core","depth":6,"parentId":"4b4ea578-28b4-481c-9abd-d34c5a4f383c","order":2407,"content":"The risk of a technical exploit in one protocol is unlikely to be correlated with the risk of a technical exploit in an unrelated protocol. Therefore, the risks from small exposures to even relatively risky protocols are likely to be diversified away. In contrast, very large exposures to even relatively safe protocols can create a risk to a Prime Agent and potentially to Sky itself if there is a technical exploit, especially if multiple Prime Agents have the same exposure. To account for this, the calculation of Instance Smart Contract RRC should take into account the risk rating, the level of exposure of the Prime, and the level of exposure of the Sky Ecosystem.","contentHash":"f6478b1364b551ee4999305ef19a6e2b6cfe3b6320c8b986e6936a9d76411ed5","addressRefs":[]},"3df9da84-f435-4d8d-a432-daa92d12a12c":{"id":"3df9da84-f435-4d8d-a432-daa92d12a12c","doc_no":"A.3.2.1.1.5.4","title":"Implementation","type":"Core","depth":6,"parentId":"4b4ea578-28b4-481c-9abd-d34c5a4f383c","order":2408,"content":"The implementation of the calculation of Instance Smart Contract RRC is specified in [A.3.2.2.1.2 - Instance Smart Contract RRC Implementation](e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080).","contentHash":"bc7ef2ca537b3de7d615ab2f560578875bb2bd66b5119e70725accfff467fec5","addressRefs":[]},"c2b60f0d-6555-463c-9ad3-2a9746be77c5":{"id":"c2b60f0d-6555-463c-9ad3-2a9746be77c5","doc_no":"A.3.2.1.1.6","title":"Instance Administrative RRC","type":"Core","depth":5,"parentId":"b6597fb4-d347-44f4-8780-b9a4116c1a36","order":2409,"content":"The documents herein define the conceptual framework for determining the Instance Administrative RRC required to protect Sky from administrative risk arising from an Instance of the Allocation System Primitive.","contentHash":"efbc2188f78c5a2e795b13c7580ce474ecf68f8c8dc38a606ab48bd884628668","addressRefs":[]},"0482b0c5-d78b-4e4a-b6c6-c858368d0b2c":{"id":"0482b0c5-d78b-4e4a-b6c6-c858368d0b2c","doc_no":"A.3.2.1.1.6.1","title":"Definition","type":"Core","depth":6,"parentId":"c2b60f0d-6555-463c-9ad3-2a9746be77c5","order":2410,"content":"Administrative Risk refers to the risk that an investment through the Allocation System will experience a loss of funds due to abuse of privileged access to a protocol. This risk may arise from a multisig or another actor that has the ability to modify the protocol or access funds without going through a governance process.","contentHash":"bccd1d67cd54913467be36ec693016f6db93b7204a3f2ebeaf9b04992bd2de3f","addressRefs":[]},"3fe89645-48a9-430d-9ff1-925c361bb56f":{"id":"3fe89645-48a9-430d-9ff1-925c361bb56f","doc_no":"A.3.2.1.1.6.2","title":"Risk Rating","type":"Core","depth":6,"parentId":"c2b60f0d-6555-463c-9ad3-2a9746be77c5","order":2411,"content":"The determination of Administrative Risk should initially be based on an evaluation of the risk that an investment could experience losses due to an abuse of privileged access. This determination should take into account factors such as (1) the level of privileged access that exists, (2) the security delay that such access is subject to, and (3) the \"Lindiness\" of the system.","contentHash":"ca21ec983cd47475742aaaa2aa7e374d5f1354a8740571963870c46ba2796c4a","addressRefs":[]},"bcb97e92-b578-4195-9ea5-a9e6bf2e201b":{"id":"bcb97e92-b578-4195-9ea5-a9e6bf2e201b","doc_no":"A.3.2.1.1.6.3","title":"Required Risk Capital","type":"Core","depth":6,"parentId":"c2b60f0d-6555-463c-9ad3-2a9746be77c5","order":2412,"content":"The risk of an abuse of privileged access in one protocol is unlikely to be correlated with the risk of an abuse of privileged access in an unrelated protocol. Therefore, the risks from small exposures to even relatively risky protocols are likely to be diversified away. In contrast, very large exposures to even relatively safe protocols can create a risk to a Prime Agent and potentially to Sky itself if there is an abuse of privileged access, especially if multiple Prime Agents have the same exposure. To account for this, the calculation of Instance Administrative RRC should take into account the risk rating, the level of exposure of the Prime, and the level of exposure of the Sky Ecosystem.","contentHash":"81e1f73f4331eb13c3886531c0cb262dca7f3fcda9d63f53bb0c751418f43150","addressRefs":[]},"ee71508b-9c89-4765-83a5-6e50832549bb":{"id":"ee71508b-9c89-4765-83a5-6e50832549bb","doc_no":"A.3.2.1.1.6.4","title":"Implementation","type":"Core","depth":6,"parentId":"c2b60f0d-6555-463c-9ad3-2a9746be77c5","order":2413,"content":"The implementation of the calculation of Instance Administrative RRC is specified in [A.3.2.2.1.3 - Instance Administrative RRC Calculation](277d6712-25ff-4566-a42b-38d7e860ae76).","contentHash":"5a405bdfb9920e7b7c01decd0c948924791060603e3c30f2f5197d03a1004348","addressRefs":[]},"be7589f5-32c0-42d2-8d10-38bceb1de28b":{"id":"be7589f5-32c0-42d2-8d10-38bceb1de28b","doc_no":"A.3.2.1.2","title":"Total Risk Capital","type":"Core","depth":4,"parentId":"ee3a912d-c340-41ee-b33e-45e72f215d49","order":2414,"content":"The documents herein define the conceptual framework for types of capital that contribute to a Prime Agent’s Total Risk Capital (TRC). Prime Agents must maintain at all times a level of TRC that exceeds their Aggregate RRC or be subject to penalties.","contentHash":"d0471ebad287e71f4a43e8a34e8d15ad3b67d93fa799361c139a774b5e0c858b","addressRefs":[]},"6f6b25d6-f73c-4733-ba37-12a0a411433c":{"id":"6f6b25d6-f73c-4733-ba37-12a0a411433c","doc_no":"A.3.2.1.2.1","title":"Total Risk Capital Definition","type":"Core","depth":5,"parentId":"be7589f5-32c0-42d2-8d10-38bceb1de28b","order":2415,"content":"Total Risk Capital is capital that is currently eligible, available, and verifiably under the Prime’s control. For capital to be included in a Prime Agent's TRC, it must be currently deployable towards covering its Required Risk Capital obligations. Consequently, in-flight capital (e.g., assets being bridged) does not contribute towards a Prime’s TRC. Similarly, commitments for future capital, such as Ecosystem Accords for renting Prime-External Junior Risk Capital (SEJRC) or Tokenized External Junior Risk Capital (TEJRC) that have been agreed upon by counterparties but are not yet formally codified within the Atlas, cannot contribute towards a Prime’s TRC until such formalization is complete.","contentHash":"80d9b4595f8914e92a559ee755cc784364c072d85270261bd5afcb15e268a3ef","addressRefs":[]},"24db6047-c829-4d31-ac0e-f81f908186ad":{"id":"24db6047-c829-4d31-ac0e-f81f908186ad","doc_no":"A.3.2.1.2.2","title":"Types Of Risk Capital","type":"Core","depth":5,"parentId":"be7589f5-32c0-42d2-8d10-38bceb1de28b","order":2416,"content":"TRC comprises two categories based on loss absorption seniority: Junior Risk Capital (JRC) and Senior Risk Capital (SRC), further divided by source.","contentHash":"33ef0cf30630c5cc3f7b067429bcab4fe0a6aeeb15cbb07a37bbfd5e9bae19bb","addressRefs":[]},"92e51a94-ef70-4a86-9946-36077ebad1e9":{"id":"92e51a94-ef70-4a86-9946-36077ebad1e9","doc_no":"A.3.2.1.2.2.1","title":"Junior Risk Capital","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2417,"content":"Junior Risk Capital (JRC) is the first capital to absorb losses on investments under the Allocation System. Junior Risk Capital must experience 100% losses before any losses are absorbed by Senior Risk Capital.","contentHash":"a4a54bc23542e5c8a8ef0c53b14d3de77fda156381585d7edbafaf710c2209d2","addressRefs":[]},"57b0b226-ae2c-4d47-871d-57e6d3bb1a9f":{"id":"57b0b226-ae2c-4d47-871d-57e6d3bb1a9f","doc_no":"A.3.2.1.2.2.1.1","title":"Junior Risk Capital Types","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2418,"content":"The documents herein define the types of Junior Risk Capital.","contentHash":"59b32ba5c638728b2af6974fee216a48f4b15427838f46d1dc1296566194e98b","addressRefs":[]},"8728abee-0dc5-449b-b4c2-78698da16f10":{"id":"8728abee-0dc5-449b-b4c2-78698da16f10","doc_no":"A.3.2.1.2.2.1.1.1","title":"Internal Junior Risk Capital (IJRC)","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2419,"content":"Internal Junior Risk Capital is capital owned by the Prime Agent itself. It serves as the foundation for the Prime’s risk capacity: the amount of IJRC directly dictates the maximum External JRC the Prime can source (governed by the External Per Internal ratio) and provides the primary capacity for enabling Senior Risk Capital (via the Senior Per Junior ratio), while also bearing the initial impact of any losses (the Tip JRC mechanism). IJRC must be eligible assets held in the Prime Agent’s designated treasury account (e.g., SubProxy), controlled by the Prime’s root governance.\n\nSee [A.3.2.1.2.3.1.1 - External Per Internal Ratio](ff374833-920c-40f6-ae6c-a71d33d99b82), [A.3.2.1.2.3.1.2 - Senior Per Junior Ratio](fbc9a273-d217-4d52-8b3e-b496580f27a2), and [A.3.2.1.2.2.1.2 - JRC Loss Allocation Rules](c201122a-75d2-44fa-b221-4e7c09bf42f2).","contentHash":"a9bf6d8f948cfa6feef76ed2dc60969ef7921eeceeb877905c8574ec7926f46b","addressRefs":[]},"a2df2b73-c1c5-40d6-b87e-43ba24f54870":{"id":"a2df2b73-c1c5-40d6-b87e-43ba24f54870","doc_no":"A.3.2.1.2.2.1.1.1.1","title":"Types Of Eligible Assets For IJRC","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2420,"content":"The documents herein define the types of assets that qualify as Internal Junior Risk Capital.\n\nThese types will be specified in a future iteration of the Risk Framework.","contentHash":"df3d312296891deff7da4ebeca8074ab3fc8611800b3fb8cf9ff79ed9d18c482","addressRefs":[]},"00f61aa6-7bb4-4c7f-9492-2e2b2b4e78b2":{"id":"00f61aa6-7bb4-4c7f-9492-2e2b2b4e78b2","doc_no":"A.3.2.1.2.2.1.1.2","title":"Prime-External Junior Risk Capital (SEJRC)","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2421,"content":"SEJRC is JRC rented from another Prime Agent via the [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce). The capital remains in the lender's treasury but counts towards the borrower's JRC amount. SEJRC is represented by a registered Ecosystem Accord signifying that a specified amount of the lending Agent's JRC (held within the lender's treasury) is designated to count towards the borrowing Agent's JRC requirement for the duration and terms specified in the Accord.","contentHash":"0d32837664c5de9054fd59df5d1bdede4518f543cb5a4aaea7a583088cb3a212","addressRefs":[]},"6dd3c9c2-414b-4f06-bbc7-944f67e1cd89":{"id":"6dd3c9c2-414b-4f06-bbc7-944f67e1cd89","doc_no":"A.3.2.1.2.2.1.1.3","title":"Tokenized External Junior Risk Capital (TEJRC)","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2422,"content":"Tokenized External Junior Risk Capital is capital provided by external capital providers depositing sUSDS into the Tokenized External Junior Risk Capital smart contract, from which Primes can encumber funds. The details of this contract will be specified in a future iteration of the Atlas.","contentHash":"f372260509a162d27436c74564b8a755e242681ce2a196f9283f1cda190a98c5","addressRefs":[]},"c201122a-75d2-44fa-b221-4e7c09bf42f2":{"id":"c201122a-75d2-44fa-b221-4e7c09bf42f2","doc_no":"A.3.2.1.2.2.1.2","title":"JRC Loss Allocation Rules","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2423,"content":"This document defines the conceptual framework for distributing losses within the JRC layer.","contentHash":"74df3c74756ca68caf10a578a28df708a719a7f4678729c9452054a5a26b0831","addressRefs":[]},"6c33bcf5-c29d-48ca-9ee5-e37dcdeb0630":{"id":"6c33bcf5-c29d-48ca-9ee5-e37dcdeb0630","doc_no":"A.3.2.1.2.2.1.2.1","title":"Initial Loss Absorption By “Tip JRC”","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2424,"content":"The Tip JRC mechanism dictates that losses from a distinct risk event are first absorbed entirely by the Prime Agent's Internal Junior Risk Capital (IJRC), up to a specific threshold amount. This threshold amount is calculated as a percentage of Total JRC and is specified in [A.3.2.2.2.1 - JRC Loss Allocation Parameters](b718459e-57e0-414f-9c99-fbc82685cc0f).\n\nOnly losses exceeding this threshold amount trigger absorption by other Junior Risk Capital components - specifically, the remaining IJRC and External Junior Risk Capital. This initial absorption solely by IJRC ensures that Prime Agents are highly incentivized to prevent losses and avoids the need to resolve disputes regarding the allocation of small losses to EJRC providers.","contentHash":"487716c7ecea1a79d0ed50a73f0643c895a015e95e8810cd13c3e47013246e94","addressRefs":[]},"64cc7061-1bdf-4f1d-8300-fafb3743578b":{"id":"64cc7061-1bdf-4f1d-8300-fafb3743578b","doc_no":"A.3.2.1.2.2.1.2.2","title":"Post-Tip JRC Loss Allocation","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2425,"content":"If a loss event exceeds the Tip JRC amount, the remaining loss is allocated pro-rata across the rest of the JRC capital. This includes the remaining Internal Junior Risk Capital (Total IJRC minus the Tip amount) and all External Junior Risk Capital (Prime External Junior Risk Capital plus Tokenized External Junior Risk Capital).","contentHash":"a9fed21d11ff838288e2b7ca44c0347f11fe5059069cb635df496db76065059a","addressRefs":[]},"ca685840-ab9a-4fa8-8f08-794536b94490":{"id":"ca685840-ab9a-4fa8-8f08-794536b94490","doc_no":"A.3.2.1.2.2.1.2.3","title":"Per-Event Basis","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2426,"content":"The JRC loss allocation rules are applied independently based on the total losses attributed to each distinct risk event. The concept of \"per-event basis\" is crucial; the classification of a distinct risk event (classifying losses as one large event versus multiple smaller ones) can dictate whether the Tip JRC threshold is breached.\n\nBreaching the threshold activates the pro-rata sharing mechanism for any losses exceeding the Tip JRC amount, distributing such excess losses between both the remaining Internal JRC (IJRC) and all External JRC (EJRC). Conversely, if the threshold is not breached for an event, the loss is contained entirely within the Tip layer and absorbed solely by IJRC.\n\nThe operational process for the determination of distinct risk events will be defined in a future iteration of the Atlas.","contentHash":"e764507ec47c818e0c48d0ee6d3f5e2b62c315ca1a67b5f6236ece2d36b77eb4","addressRefs":[]},"6bba2076-5d5b-43fd-82c6-df6a35f67355":{"id":"6bba2076-5d5b-43fd-82c6-df6a35f67355","doc_no":"A.3.2.1.2.2.2","title":"Senior Risk Capital","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2427,"content":"Senior Risk Capital (SRC) is protected from losses relative to Junior Risk Capital. Senior Risk Capital only begins to absorb losses after Junior Risk Capital has experienced 100% losses and absorbs 100% of losses thereafter.\n\nSenior Risk Capital can be originated from Sky Core on a monthly basis as part of the Monthly Settlement Cycle; Prime Agents can also rent Senior Risk Capital from each other.","contentHash":"f13efbfb0441590ab506db9d627ec2db39196e7cd5844206d705515345f440eb","addressRefs":[]},"d2e9a92e-dd5d-4a26-8fc6-c5b47a2c06c2":{"id":"d2e9a92e-dd5d-4a26-8fc6-c5b47a2c06c2","doc_no":"A.3.2.1.2.2.2.1","title":"Senior Risk Capital Types","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2428,"content":"The documents herein define the types of Senior Risk Capital.","contentHash":"6df84ac424861249ba9493a5c42ad3b6329b53e857ea67ed41c03b88a3b0c81c","addressRefs":[]},"09c20045-4b53-4370-98b8-a1199ccf7007":{"id":"09c20045-4b53-4370-98b8-a1199ccf7007","doc_no":"A.3.2.1.2.2.2.1.1","title":"Internal Senior Risk Capital","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2429,"content":"Internal Senior Risk Capital (ISRC) is capital sourced from Aggregate Backstop Capital, as specified in [A.2.3.1.3 - Sourcing Of Internal Senior Risk Capital](ac7a6636-acbc-40c9-abc1-4543c0beb300).","contentHash":"d614d57b85d032769b6c4ffd789b8c63aeddb7d36c6adedd001b7152de162f03","addressRefs":[]},"2adf8738-09b2-43e2-884c-c4ce6ff601ba":{"id":"2adf8738-09b2-43e2-884c-c4ce6ff601ba","doc_no":"A.3.2.1.2.2.2.1.2","title":"External Senior Risk Capital","type":"Core","depth":6,"parentId":"24db6047-c829-4d31-ac0e-f81f908186ad","order":2430,"content":"External Senior Risk Capital (ESRC) is capital provided from the srUSDS smart contract, which allow users to provide USDS to Sky Core to serve as senior risk capital in exchange for higher returns. The mechanics of this are specified in [A.3.2.2.4.2 - External Senior Risk Capital And srUSDS System](9fac0f6b-cb2d-4dc2-97d5-72c705303675).","contentHash":"94c2415d35aeac311a05035919066aeb4ecd494806f6cba223c76285c4beafe1","addressRefs":[]},"9e99b084-f15a-4f60-b831-d6c0bd9aec04":{"id":"9e99b084-f15a-4f60-b831-d6c0bd9aec04","doc_no":"A.3.2.1.2.3","title":"Total Risk Capital Sourcing Ratios","type":"Core","depth":5,"parentId":"be7589f5-32c0-42d2-8d10-38bceb1de28b","order":2431,"content":"The documents herein define the required relationship and constraints between the different types of Total Risk Capital. These ensure that the Prime Agent maintains the appropriate level of Internal Junior Risk Capital relative to its External and Senior capital exposures, ensuring sufficient \"skin in the game\" with respect to its investments.","contentHash":"9f2fe9ecf6a337cef42e160391ce44534dc6929dd0675db1689074b0af16d126","addressRefs":[]},"e600afc0-6f8e-42a7-9413-9ef2f5cf0ebb":{"id":"e600afc0-6f8e-42a7-9413-9ef2f5cf0ebb","doc_no":"A.3.2.1.2.3.1","title":"Definition Of Ratios","type":"Core","depth":6,"parentId":"9e99b084-f15a-4f60-b831-d6c0bd9aec04","order":2432,"content":"The documents herein define the Total Risk Capital sourcing ratios.","contentHash":"100f50673bc8886c852682c19b3ae4fdf42c1d870191902470288147a5ec0db9","addressRefs":[]},"ff374833-920c-40f6-ae6c-a71d33d99b82":{"id":"ff374833-920c-40f6-ae6c-a71d33d99b82","doc_no":"A.3.2.1.2.3.1.1","title":"External Per Internal Ratio","type":"Core","depth":6,"parentId":"9e99b084-f15a-4f60-b831-d6c0bd9aec04","order":2433,"content":"The External Per Internal (EPI) ratio determines the maximum amount of External Junior Risk Capital (SEJRC and TEJRC combined) that a Prime Agent can source directly based on its held Internal Junior Risk Capital (IJRC). This acts as the primary constraint ensuring a baseline level of the Prime’s own capital backs its external JRC sourcing. The required External Per Internal ratio is specified in [A.3.2.2.2.2.1 - External Per Internal (EPI) Ratio Value](3ed32706-c072-42b5-b1e5-187bddf8dc37).","contentHash":"41182786875cd79966d0e480ce6909452cb6e3578e3ef28764a737e4b0496b1b","addressRefs":[]},"fbc9a273-d217-4d52-8b3e-b496580f27a2":{"id":"fbc9a273-d217-4d52-8b3e-b496580f27a2","doc_no":"A.3.2.1.2.3.1.2","title":"Senior Per Junior Ratio","type":"Core","depth":6,"parentId":"9e99b084-f15a-4f60-b831-d6c0bd9aec04","order":2434,"content":"The Senior Per Junior (SPJ) ratio defines the effectiveness of each type of Junior Risk Capital (IJRC, SEJRC, TEJRC) in supporting Senior Risk Capital (SRC). Specifically, it quantifies how many units of SRC (whether Originated or Rented) can be activated or \"enabled\" per unit of a given JRC type.\n\nA Prime Agent's overall \"SPJ capacity\" is calculated by summing the potential enablement contributed by each type of JRC it holds (IJRC, SEJRC or TEJRC), where each contribution equals the amount of that JRC type multiplied by its specific SPJ ratio.\n\nSince SRC only absorbs losses after JRC is depleted, the SPJ enablement mechanism validates that sufficient JRC backing exists, allowing enabled SRC to be counted as part of the Prime Agent's total eligible Risk Capital. Therefore, a Prime Agent might hold a certain amount of OSRC or rented SRC, but only the portion that is successfully \"enabled\" by its JRC according to the SPJ ratios is accounted by the system as eligible capital contributing towards the Prime’s satisfaction of its Required Risk Capital. The required ratio of Senior Per Junior is specified in [A.3.2.2.2.2.2 - Senior Per Junior (SPJ) Ratio Values](8578e240-3fe8-41c0-8b2c-15ec9a7181ab).","contentHash":"789ceac4f3ef48537cb617edc5707cfd0b4f872ef18fc86ccb0732f8a0d3e9c7","addressRefs":[]},"03029174-91b4-4974-af1e-52438556a70b":{"id":"03029174-91b4-4974-af1e-52438556a70b","doc_no":"A.3.2.1.2.3.1.2.1","title":"Alternative Use Of SPJ Capacity To Source External Junior Risk Capital","type":"Core","depth":6,"parentId":"9e99b084-f15a-4f60-b831-d6c0bd9aec04","order":2435,"content":"A Prime Agent may optionally choose to deploy all or some portion of its calculated SPJ capacity not to enable Senior Risk Capital, but instead to source additional External Junior Risk Capital. This provides a secondary mechanism to increase the total JRC potentially beyond the amount initially constrained by the EPI ratio applied solely to IJRC.\n\nCrucially, the EJRC tranche acquired through utilizing SPJ capacity is permanently accounted for as having an SPJ ratio of zero (0). It contributes to the JRC buffer but provides no capacity itself for enabling SRC in any subsequent calculations. This contrasts with EJRC sourced normally via the EPI ratio, which retains its standard SPJ capacity.","contentHash":"4903ac35cd662f533f422b13483a052ccb2e37c76d734592bef7d167fd58c434","addressRefs":[]},"e19dc42d-10d4-46d1-81e7-081f2f3e79f9":{"id":"e19dc42d-10d4-46d1-81e7-081f2f3e79f9","doc_no":"A.3.2.1.2.3.2","title":"Interaction Between Ratios And SPJ Capacity","type":"Core","depth":6,"parentId":"9e99b084-f15a-4f60-b831-d6c0bd9aec04","order":2436,"content":"The sourcing of External Junior Risk Capital and enablement of Senior Risk Capital involves a sequential application of the Risk Capital sourcing ratios in conjunction with the Prime Agent’s deployment of its SPJ capacity.\n\nFirst, the EPI ratio sets the initial limit for sourcing standard, SPJ-bearing EJRC based solely on the Prime Agent’s IJRC.\nSecond, the total SPJ capacity is calculated from the Prime Agent’s resulting JRC pool (IJRC + any EPI-sourced EJRC).\n\nFinally, this total calculated SPJ capacity can be allocated by the Prime Agent to enable SRC (standard use), and/or to source additional, non-SPJ-bearing EJRC using the mechanism described under [A.3.2.1.2.3.1.2.1 - Alternative Use Of SPJ Capacity To Source External Junior Risk Capital](03029174-91b4-4974-af1e-52438556a70b). Any specific portion of the total SPJ capacity allocated towards sourcing EJRC cannot simultaneously be allocated towards enabling SRC.","contentHash":"3bf9c44dd71fbe31304c82ad963dbac2e1384b7073b456f9cf7a901a7b28ea8d","addressRefs":[]},"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a":{"id":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","doc_no":"A.3.2.2","title":"Implementation","type":"Section","depth":3,"parentId":"55999acf-75fe-4adf-8584-9746ef50d3e4","order":2437,"content":"This Section defines the current implementation of the Risk Capital framework.","contentHash":"27c4dc5b4238a91c964230802d14c4558b4ff492c660bc9371de40e34008862d","addressRefs":[]},"d10b1c92-b839-45f1-995d-a23381fd6068":{"id":"d10b1c92-b839-45f1-995d-a23381fd6068","doc_no":"A.3.2.2.1","title":"Required Risk Capital Calculation Implementation","type":"Core","depth":4,"parentId":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","order":2438,"content":"The documents herein define the implementation of the Risk Framework for calculating required Total Instance RRC.","contentHash":"b01dc65933c3d7b7775e7cc7ee6908d0dee6df564907dbd8f184775fcce66d88","addressRefs":[]},"aada206c-84bd-41e7-880d-1304889f4896":{"id":"aada206c-84bd-41e7-880d-1304889f4896","doc_no":"A.3.2.2.1.1","title":"Instance Financial RRC Implementation","type":"Core","depth":5,"parentId":"d10b1c92-b839-45f1-995d-a23381fd6068","order":2439,"content":"The documents herein define the implementation of the Risk Framework for calculating Instance Financial RRC.","contentHash":"fb117a7e3a64741033b374d07e588d1549ae7c5724f9a95ffae864848cd1597a","addressRefs":[]},"8b6a6ecd-da74-4be5-bcb8-96215f473c08":{"id":"8b6a6ecd-da74-4be5-bcb8-96215f473c08","doc_no":"A.3.2.2.1.1.1","title":"Asset Class Specific Implementation","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2440,"content":"The documents herein define the calculation of Instance Financial RRC for specific asset classes.","contentHash":"56af33bb5395ebc7d3540319b455f1be224246d05714ed0c706c4fe27f8864a1","addressRefs":[]},"d4e9c9e0-eeab-4399-99a0-5f72ff0d0e43":{"id":"d4e9c9e0-eeab-4399-99a0-5f72ff0d0e43","doc_no":"A.3.2.2.1.1.1.1","title":"Lending Markets","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2441,"content":"The documents herein define the calculation of Instance Financial RRC for lending markets.","contentHash":"ae0c1b016f7b8fc3f4e7cfeed3eaec31c82719a3eb226f0ffd8f53f54d0d2ca0","addressRefs":[]},"0442fb55-5abb-4fa8-8f50-9a6f0bf6b86f":{"id":"0442fb55-5abb-4fa8-8f50-9a6f0bf6b86f","doc_no":"A.3.2.2.1.1.1.1.1","title":"Process For Calculating Instance Financial RRC","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2442,"content":"The documents herein define the process for calculating Instance Financial RRC for lending markets.","contentHash":"076cbbda10188cb2adbf6131cd32b98a8d3c30d9e80211f832c418ca1a765d91","addressRefs":[]},"6766c25f-3e67-41e0-8b66-5af444c40572":{"id":"6766c25f-3e67-41e0-8b66-5af444c40572","doc_no":"A.3.2.2.1.1.1.1.1.1","title":"Calculate Probability Of Default","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2443,"content":"The first step is calculating the Probability Of Default $PD$. $PD$ is calculated using the following formula:\n\n$$\n\\text{PD} = N(-d_1) + N(-d_2) \\left( \\frac{\\sum_{i=1}^n \\text{LT}_i V_0^i}{\\sum_{j=1}^m D_0^j} \\right)^{-2a}\n$$\n\nHere $N$ is the normal cumulative probability distribution function.\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"c98aba4cc5d4f6b08b8bc60e6c8c17cf4138c327d9a53afd8ee08cd9e32c9ee9","addressRefs":[]},"0fcaf411-74e1-4b99-be50-40eb36bd6566":{"id":"0fcaf411-74e1-4b99-be50-40eb36bd6566","doc_no":"A.3.2.2.1.1.1.1.1.1.1","title":"Leverage Adjusted Drift To Risk Ratio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2444,"content":"The Leverage Adjusted Drift To Risk Ratio $a$ is calculated as follows:\n\n$$\na = \\frac{\\sum_{i=1}^n w_U^i (r_c^i + r_s^i) - \\sum_{j=1}^m w_D^j (r_d^j + r_s^j) + \\rho_{UD} \\sigma_U \\sigma_D - \\sigma_U^2}{\\sigma_U^2 + \\sigma_D^2 - 2 \\rho_{UD} \\sigma_U \\sigma_D}\n$$","contentHash":"c0a3d2973b90ee02ab11b6e4906b12958c92980c4d3a005498a12793a81572b9","addressRefs":[]},"b449741c-0144-406e-9d18-eabb050bcba0":{"id":"b449741c-0144-406e-9d18-eabb050bcba0","doc_no":"A.3.2.2.1.1.1.1.1.1.2","title":"Distance To Default","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2445,"content":"The Distance To Default $d_1$ is calculated using the following formula:\n\n$$\nd_1 = \\frac{\\ln\\left( \\frac{\\sum_{i=1}^n \\text{LT}_i V_0^i}{\\sum_{j=1}^m D_0^j} \\right) + \\left( \\sum_{i=1}^n w_U^i (r_c^i + r_s^i) - \\sum_{j=1}^m w_D^j (r_d^j + r_s^j) + \\rho_{UD} \\sigma_U \\sigma_D - \\sigma_U^2 \\right) T}{\\sqrt{\\sigma_U^2 + \\sigma_D^2 - 2 \\rho_{UD} \\sigma_U \\sigma_D} \\sqrt{T}}\n$$","contentHash":"ff6d94a6217849c59fb9a783c164008e7faad7923b2e72f4974882b20aca5397","addressRefs":[]},"6eedb98a-0238-421a-9f8d-613859ddfcef":{"id":"6eedb98a-0238-421a-9f8d-613859ddfcef","doc_no":"A.3.2.2.1.1.1.1.1.1.3","title":"Downward Adjusted Distance To Default","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2446,"content":"The Downward Adjusted Distance To Default $d_2$ is calculated using the following formula:\n\n$$\nd_2 = \\frac{\\ln\\left( \\frac{\\sum_{i=1}^n \\text{LT}_i V_0^i}{\\sum_{j=1}^m D_0^j} \\right) - \\left( \\sum_{i=1}^n w_U^i (r_c^i + r_s^i) - \\sum_{j=1}^m w_D^j (r_d^j + r_s^j)+ \\rho_{UD} \\sigma_U \\sigma_D - \\sigma_U^2 \\right) T}{\\sqrt{\\sigma_U^2 + \\sigma_D^2 - 2 \\rho_{UD} \\sigma_U \\sigma_D} \\sqrt{T}}\n$$","contentHash":"a1c4515978795516d0ed02951e967cfa4bf0a8e45fb5d72edf2cd061907e1101","addressRefs":[]},"d7f84a30-53f6-425c-afba-3ffc59e03e0f":{"id":"d7f84a30-53f6-425c-afba-3ffc59e03e0f","doc_no":"A.3.2.2.1.1.1.1.1.1.4","title":"Total Variance Of Underlying Asset Portfolio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2447,"content":"The Total Variance Of Underlying Asset Portfolio $\\sigma_U^2$ is calculated using the following formula:\n\n$$\n\\sigma_U^2 = \\sum_{i,k=1}^n w_U^i w_U^k \\sigma_V^i \\sigma_V^k \\rho_{V,ik}\n$$","contentHash":"0044944b85952c58f9b5d5dcfda87a19801bd7f90a19f68d3103d42e097df377","addressRefs":[]},"1db43b96-d2eb-4563-87ad-d5046c21b66c":{"id":"1db43b96-d2eb-4563-87ad-d5046c21b66c","doc_no":"A.3.2.2.1.1.1.1.1.1.5","title":"Total Variance Of Debt Portfolio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2448,"content":"The Total Variance Of Debt Portfolio $\\sigma_D^2$ is calculated using the following formula:\n\n$$\n\\sigma_D^2 = \\sum_{j,l=1}^m w_D^j w_D^l \\sigma_D^j \\sigma_D^l \\rho_{D,jl}\n$$","contentHash":"34158da87d50c38e3dcd0fb1a357b4ec7a4738704cf7546552cf456570cbc99c","addressRefs":[]},"ae1dbcb9-828d-40c0-8ad8-96b3072dad4e":{"id":"ae1dbcb9-828d-40c0-8ad8-96b3072dad4e","doc_no":"A.3.2.2.1.1.1.1.1.1.6","title":"Correlation Between Asset Portfolio And Debt Portfolio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2449,"content":"The Correlation Between Asset Portfolio And Debt Portfolio $\\rho_{UD}$ is calculated using the following formula:\n\n$$\n\\rho_{UD} = \\frac{\\sum_{i=1}^n \\sum_{j=1}^m w_U^i w_D^j \\sigma_V^i \\sigma_D^j \\rho_{VD,ij}}{\\sqrt{\\sigma_U^2 \\sigma_D^2}}\n$$","contentHash":"5c37701bc34ce3c725cdd062fed36d47870917d3d50559d922e56ec82be5a024","addressRefs":[]},"c614e705-59c8-40bd-aa15-c8d61c0ead4f":{"id":"c614e705-59c8-40bd-aa15-c8d61c0ead4f","doc_no":"A.3.2.2.1.1.1.1.1.1.7","title":"Weight Of Asset In Underlying Asset Portfolio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2450,"content":"The weight of asset $i$ in the underlying asset portfolio $w_U^i$ is calculated using the following formula:\n\n$$\nw_U^i = \\frac{\\text{LT}_i V_0^i}{\\sum_{k=1}^n \\text{LT}_k V_0^k}\n$$","contentHash":"6aff8e74ec71f14db7850eaafd42e40b3505926c07695110669bdee91d86bf89","addressRefs":[]},"c5605290-8c64-4ed0-8fab-f2824488c4c9":{"id":"c5605290-8c64-4ed0-8fab-f2824488c4c9","doc_no":"A.3.2.2.1.1.1.1.1.1.8","title":"Weight Of Debt Instrument In Debt Portfolio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2451,"content":"The weight of debt instrument $j$ in the debt portfolio $w_D^j$ is calculated using the following formula:\n\n$$\nw_D^j = \\frac{D_0^j}{\\sum_{l=1}^m D_0^l}\n$$","contentHash":"657cf943de632f81cc83a62b768e1d8e67dda3b09621d93138145e7ba64e84d2","addressRefs":[]},"9f322c61-92d7-4ff5-aa9b-523e124c8748":{"id":"9f322c61-92d7-4ff5-aa9b-523e124c8748","doc_no":"A.3.2.2.1.1.1.1.1.1.9","title":"Return On Asset","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2452,"content":"The Return On Asset $r_c^i$ of an asset $i$ is the yield earned for supplying the asset in the lending market.","contentHash":"b9cebf03c5f3d2bbb411eff3c0bea531fd03f693d9d9ff83f95258316fd76f69","addressRefs":[]},"e0fea8fd-3925-463b-ab0d-3ff9fee1298d":{"id":"e0fea8fd-3925-463b-ab0d-3ff9fee1298d","doc_no":"A.3.2.2.1.1.1.1.1.1.10","title":"Asset Yield","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2453,"content":"The Asset Yield $r_s^i$ of an asset $i$ is the income yield of the asset and would include any dividends or interest paid by the asset and/or asset issuer, including staking rewards for yield-bearing assets.","contentHash":"6af641f10a90098f62b272db1bd874d3dd7facfd628558714cb9d6d12e0e8222","addressRefs":[]},"5051029f-8e9c-4234-9951-c6a95fc0cddb":{"id":"5051029f-8e9c-4234-9951-c6a95fc0cddb","doc_no":"A.3.2.2.1.1.1.1.1.1.11","title":"Cost Of Debt","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2454,"content":"The Cost Of Debt $r_d^j$ of a debt instrument $j$ is the interest rate on the debt.","contentHash":"11dcb2abbfcd5bfd4f2fdce234005af28898b8fa0fcd9dc9cd3d2f2186e10817","addressRefs":[]},"022a0b3b-18db-4440-9868-be62ad2f6d47":{"id":"022a0b3b-18db-4440-9868-be62ad2f6d47","doc_no":"A.3.2.2.1.1.1.1.1.1.12","title":"Debt Yield","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2455,"content":"The Debt Yield $r_s^j$ of a debt instrument $j$ is the income yield on the debt asset. It includes any dividends or interest paid by the debt asset and/or debt asset issuer, including staking rewards for yield-bearing debt assets.","contentHash":"83cae83781c0589cc8cf7be77aee52e9f2b14af89827651f06741b390a4ecdb8","addressRefs":[]},"0663022c-c7bf-49db-800c-c186e9819455":{"id":"0663022c-c7bf-49db-800c-c186e9819455","doc_no":"A.3.2.2.1.1.1.1.1.1.13","title":"Correlation Coefficient","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2456,"content":"The correlation coefficient $\\rho$ between two instruments is the correlation of block-weighted log returns of those assets over the last 365 days. In the documents herein, the correlation coefficient is followed by subscripts indicating the relevant instruments. For example, $\\rho_{UD}$ is the correlation between the underlying asset portfolio $U$ and the debt portfolio $D$ as specified in [A.3.2.2.1.1.1.1.1.1.6 - Correlation Between Asset Portfolio And Debt Portfolio](ae1dbcb9-828d-40c0-8ad8-96b3072dad4e). The subscript may begin with $V$ or $D$ to indicate whether the relevant instruments are part of the asset portfolio or debt portfolio. For example, $\\rho_{VD,ij}$ is the correlation coefficient between the asset $i$ and the debt instrument $j$.","contentHash":"3ce49cc0a5bbb438a907a427c38f71acbc1e56232871ceffbd4ab2148b78a50b","addressRefs":[]},"ce774017-be30-4482-8df7-361875cb771d":{"id":"ce774017-be30-4482-8df7-361875cb771d","doc_no":"A.3.2.2.1.1.1.1.1.1.14","title":"Liquidation Threshold","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2457,"content":"The Liquidation Threshold $LT_i$ is the value of the debt as a percentage of the collateral value at which the lender may liquidate the collateral to satisfy the debt.","contentHash":"b8289acf25fd310ba196be71897b913bc88013232d14d3bdba083f0013d09c6b","addressRefs":[]},"63b212be-2bde-43b3-ba61-7ebf9c442137":{"id":"63b212be-2bde-43b3-ba61-7ebf9c442137","doc_no":"A.3.2.2.1.1.1.1.1.1.15","title":"Asset Value","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2458,"content":"The Asset Value $V_0^i$ of an asset $i$ is the market value of that asset.","contentHash":"251b340521b8ca7d8b958542d9b07aa58a57f62230781a09789e3bf7c462f7eb","addressRefs":[]},"65032e2b-5da8-4fed-b893-20b18e13383b":{"id":"65032e2b-5da8-4fed-b893-20b18e13383b","doc_no":"A.3.2.2.1.1.1.1.1.1.16","title":"Debt Value","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2459,"content":"The Debt Value $D_0^i$ of a debt instrument is the notional value of the debt.","contentHash":"0579263cb8220a2f2aef812fc355b29c65b740168946cd380e10ed215cf626a9","addressRefs":[]},"9dc1abf3-365b-4ed5-b4aa-fdbb9024e0e2":{"id":"9dc1abf3-365b-4ed5-b4aa-fdbb9024e0e2","doc_no":"A.3.2.2.1.1.1.1.1.1.17","title":"Time Horizon","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2460,"content":"The Time Horizon $T$ is the time horizon in years over which the Probability Of Default is being estimated. The value of the $T$ parameter is `1`.","contentHash":"276d2c96b9f0098c7930847502ad2df9775f4541d2493f2cbd697923fea4b3a9","addressRefs":[]},"c9bd4928-d054-4e89-9a98-720c439b0db3":{"id":"c9bd4928-d054-4e89-9a98-720c439b0db3","doc_no":"A.3.2.2.1.1.1.1.1.2","title":"Calculate Loss Given Default","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2461,"content":"The second step is calculating the Loss Given Default $LGD$. $LGD$ is calculated using the following formula:\n\n$$\nLGD = min(1 - \\frac{(1 - LP) * (1 - S)}{LT}, 0)\n$$\n\nHere $min$ is the mathematical minimum function that returns the lower of the two specified parameters.\n\nThe parameters of this formula are specified in the subdocuments herein. All of these parameters should be specified as decimal numbers. For example, 3% should be specified as `0.03`.","contentHash":"e2953fcd878ec4a351601e0965bbfec5274499444d8044b1a127a2f84acd4a73","addressRefs":[]},"bce9331b-04ca-4c50-9783-098739fc72c8":{"id":"bce9331b-04ca-4c50-9783-098739fc72c8","doc_no":"A.3.2.2.1.1.1.1.1.2.1","title":"Liquidation Penalty","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2462,"content":"The Liquidation Penalty $LP$ is the contractually agreed upon liquidation penalty if the asset is liquidated to satisfy the debt.","contentHash":"79373515c87428abcadba78d78abd0c5340b85dad12d855093634d50bc31add9","addressRefs":[]},"f2612a0d-6bf8-470b-b5b6-884567e1317b":{"id":"f2612a0d-6bf8-470b-b5b6-884567e1317b","doc_no":"A.3.2.2.1.1.1.1.1.2.2","title":"Slippage","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2463,"content":"The Slippage $S$ is the estimated slippage for liquidating the entire position in one block. The estimated slippage should not exceed 25%.","contentHash":"95d395dda17c8d84bed407278538fc97bade38d0fa18b1cc9a7356e59934b8ba","addressRefs":[]},"f1d3990a-f398-454f-82ed-272052d1ad08":{"id":"f1d3990a-f398-454f-82ed-272052d1ad08","doc_no":"A.3.2.2.1.1.1.1.1.2.3","title":"Liquidation Threshold","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2464,"content":"The Liquidation Threshold $LT$ is the value of the debt as a percentage of the collateral value at which the lender may liquidate the collateral to satisfy the debt.","contentHash":"a9869e27fbdb3f9bb63e56557e919edfba1e42377da73b827cd495c91697ddc7","addressRefs":[]},"bbf43294-09c2-413a-b0a4-745cb72d1cd8":{"id":"bbf43294-09c2-413a-b0a4-745cb72d1cd8","doc_no":"A.3.2.2.1.1.1.1.1.3","title":"Calculate Asset Correlation Coefficient","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2465,"content":"The third step is to calculate the Asset Correlation Coefficient $R$. $R$ is calculated as follows:\n\n$$\nR = a \\times \\left(1 - e^{-K \\times PD}\\right) + b \\times \\left(1 - \\left(1 - e^{-K \\times PD}\\right)\\right)\n$$\n\nHere $e$ is the base of the natural logarithm.\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"9b78377fab6a994f64fc81ec94994e359e23336bab30d58e776539065f01ae97","addressRefs":[]},"68c5da4f-9c4e-4206-a582-99be9833481f":{"id":"68c5da4f-9c4e-4206-a582-99be9833481f","doc_no":"A.3.2.2.1.1.1.1.1.3.1","title":"Lower Bound","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2466,"content":"The Lower Bound $a$ is an estimate of the correlation between assets during \"calm\" periods. It is set of `0.13`.","contentHash":"8ea6603013ad1fba729d4aaf7f7e3f30dc02dddb46167523474f695bd88ea5d5","addressRefs":[]},"71136e6a-d0f5-443b-b834-40d39234e707":{"id":"71136e6a-d0f5-443b-b834-40d39234e707","doc_no":"A.3.2.2.1.1.1.1.1.3.2","title":"Upper Bound","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2467,"content":"The Upper Bound $b$ is an estimate of the correlation between assets during \"stressful\" market environments. It is set to `0.33`.","contentHash":"8152473435d9206319bbb76044939830d50897a0a93371ab439918d0be3b4c48","addressRefs":[]},"3b7924b2-1236-43cb-b0f0-ebe06f573b78":{"id":"3b7924b2-1236-43cb-b0f0-ebe06f573b78","doc_no":"A.3.2.2.1.1.1.1.1.3.3","title":"Sensitivity Coefficient","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2468,"content":"The Sensitivity Factor `K` is a tuning parameter indicating how quickly the correlations transition between $a$ and $b$. It is set to `10`.","contentHash":"80545c22e1e9a886a84efe929b5c34b8340f4bb5f8232b2b71aba0c4801c65ff","addressRefs":[]},"152bc5d8-7642-424c-b5fc-9242479f705e":{"id":"152bc5d8-7642-424c-b5fc-9242479f705e","doc_no":"A.3.2.2.1.1.1.1.1.4","title":"Calculate Capital Requirement Without Buffers","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2469,"content":"The fourth step is to calculate the Capital Requirement Without Buffers $K$. $K$ is calculated as follows:\n\n$$\nK = \\left[ LGD \\times N\\left( \\frac{N^{-1}(PD) + \\sqrt{R} \\cdot N^{-1}(0.999)}{\\sqrt{1-R}} \\right) - PD \\times LGD \\right]\n$$\n\nHere $N$ is the cumulative normal probability distribution function and $N^{-1}$ is the inverse cumulative normal probability distribution function.","contentHash":"07bb7a413e176dafff099ba6b0c088df78760289692e1a7500c8ee81b1d29e3c","addressRefs":[]},"fc471b5a-6741-4f50-aa69-302a34479526":{"id":"fc471b5a-6741-4f50-aa69-302a34479526","doc_no":"A.3.2.2.1.1.1.1.1.5","title":"Calculate Required Risk Capital","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2470,"content":"The final step is to calculate the Instance Financial RRC $RRC$. $RRC$ is calculated as follows:\n\n$$\n\\text{RRC} = K \\times \\frac{1}{CR} \\times \\text{EAD} \\times \\text{ECR}\n$$\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"65099de4e07733ce87c26a42719c36f2405c0cfd6763a04df2ae8ff4cbae88d6","addressRefs":[]},"4a1d377d-eb0e-481a-a447-9ff3630b8787":{"id":"4a1d377d-eb0e-481a-a447-9ff3630b8787","doc_no":"A.3.2.2.1.1.1.1.1.5.1","title":"Capital Ratio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2471,"content":"The Capital Ratio $CR$ is the capital ratio without additional buffers. It is set to `8.75%`.","contentHash":"f24811ef750122c0e90d2b928ea34f563bc8a0ce54eec0f997be102002838caa","addressRefs":[]},"49ed449e-6caf-4b70-9b9f-eef294f80c0e":{"id":"49ed449e-6caf-4b70-9b9f-eef294f80c0e","doc_no":"A.3.2.2.1.1.1.1.1.5.2","title":"Exposure At Default","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2472,"content":"The Exposure At Default $EAD$ is the total amount of funds from the Allocation System that have been deployed into the decentralized lending protocol.","contentHash":"c0d72c6e23600d94394757ed6fd970ff83810e58dc1ca57efa24e17e15126c30","addressRefs":[]},"3b4c7006-0bb1-4885-9c57-e97abf3d59e9":{"id":"3b4c7006-0bb1-4885-9c57-e97abf3d59e9","doc_no":"A.3.2.2.1.1.1.1.1.5.3","title":"Effective Capital Ratio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2473,"content":"The Effective Capital Ratio $ECR$ is the capital ratio included additional capital buffers established by Sky Governance as part of the Risk Framework. There are currently no additional capital buffers so the $ECR$ is equal to the $CR$, which is `8.75%`.","contentHash":"283d192f1e3faf04643d6e305525d89560b6f5127a1d0774a7af0ec0adbfa13c","addressRefs":[]},"881a9eee-1d05-4394-b0eb-cad2f9c1b181":{"id":"881a9eee-1d05-4394-b0eb-cad2f9c1b181","doc_no":"A.3.2.2.1.1.1.1.2","title":"Covered Protocols","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2474,"content":"The calculation of Instance Financial RRC for lending markets is applicable to the following protocols:\n\n- Aave v2\n- Aave v3\n- SparkLend\n- Morpho\n- Maple\n\nThe application by a Prime Agent of the Risk Framework for lending markets to any protocols not listed above must be approved by the Core Executor Agents. The Core Executor Agents shall consult with the Core Council Risk Advisor in making this determination. Any such approval must be posted to the Sky Forum under the category for the Prime Agent.","contentHash":"69f168d99d224d31aed63a76eb8c226ac1e0e6387d4006b7331ed6ee7b402983","addressRefs":[]},"21cd7356-14c9-42f1-adc0-883655ad4795":{"id":"21cd7356-14c9-42f1-adc0-883655ad4795","doc_no":"A.3.2.2.1.1.1.1.3","title":"Exceptions","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2475,"content":"The documents herein define exceptions to the calculation of Instance Financial RRC for specific lending protocols.","contentHash":"2ec8446d7570f05a469a6aff6b0b9069d57ef3c988e15a12895bb2f9d85c83d5","addressRefs":[]},"d3000c93-d5d5-4a9e-b8c7-484aa3d16633":{"id":"d3000c93-d5d5-4a9e-b8c7-484aa3d16633","doc_no":"A.3.2.2.1.1.1.1.3.1","title":"Maple","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2476,"content":"The Instance Financial CRR for Maple SyrupUSDC is 3%.\n\nThe maximum exposure a Prime Agent may have to Maple SyrupUSDC will be specified in a future iteration of the Atlas.","contentHash":"873f8ba60a15fbd7b959313e35658a1e3dcc71cb6eb6bda0e42cebe74b6fecd3","addressRefs":[]},"ef7403c9-8663-4759-b5aa-9496eca1f475":{"id":"ef7403c9-8663-4759-b5aa-9496eca1f475","doc_no":"A.3.2.2.1.1.1.1.3.2","title":"Fluid","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2477,"content":"The Instance Financial CRR for Fluid is 3% of the amount of funds supplied to Fluid that are borrowed.","contentHash":"1fc0a615e73d0476eec84e3bb97265588f331276624f40340a41e931d8809398","addressRefs":[]},"e831249e-f81a-496a-b9b9-17229c2683dd":{"id":"e831249e-f81a-496a-b9b9-17229c2683dd","doc_no":"A.3.2.2.1.1.1.1.3.3","title":"Ethena-Related Assets","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2478,"content":"The portion of exposure to lending markets that is backed by Ethena-related assets is not subject to the standard Instance Financial RRC calculation. Instead, an alternative calculation method applies: the Instance Financial CRR for indirect Ethena exposure through lending markets should be applied for this portion. See [A.3.2.2.1.1.1.2.1 - Near-Term Treatment](92727d50-1ca0-48a9-93a0-0e504e845654). This portion of exposure is calculated based on the proportional debt amount backed by Ethena-related assets, weighted by the collateral amount times liquidation threshold.","contentHash":"7493f0207960c01b3e5532e3512b67e8ce5aef483f40396bd40446300e55094d","addressRefs":[]},"5ac25db9-6567-4b83-88a2-59e295db6ed8":{"id":"5ac25db9-6567-4b83-88a2-59e295db6ed8","doc_no":"A.3.2.2.1.1.1.1.3.4","title":"Aave And SparkLend","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2479,"content":"Because Aave and SparkLend liquidate a maximum of 50% of a user’s position, the Slippage parameter for Aave and SparkLend should be the estimated slippage for liquidating half of the position in one block. See [A.3.2.2.1.1.1.1.1.2.2 - Slippage](f2612a0d-6bf8-470b-b5b6-884567e1317b).","contentHash":"33b7742dcd40d06a96150696386982f1ae639f9953eb5a66028996ba9211d303","addressRefs":[]},"836668a9-235b-458d-80fa-91a9d08c84b4":{"id":"836668a9-235b-458d-80fa-91a9d08c84b4","doc_no":"A.3.2.2.1.1.1.1.3.5","title":"Kamino","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2480,"content":"The CRR for Kamino is:\n\n- 4.98% for USDG on JLP market\n- 4.94% for USDC on JLP market\n- 4.91% for USDT on JLP market\n- 4.87% for PYUSD on JLP market\n- 1.60% for USDG on Main market\n- 1.58% for USDC on Main market\n- 1.48% for EURC on Main market\n- 0.91% for PYUSD on Main market\n- 0.78% for USDT on Main market\n- 0.77% for USDS on Main market\n- 2.12% for USDC on Maple market\n- 0.75% for USDS on Maple market\n\nThe maximum exposure a Prime Agent may have to Kamino may not exceed 25,000,000 USDS.","contentHash":"acc41a2b0934ed9e42d96f0557ac9bd182f4fdf7698a31110ced14dd70b9f1b1","addressRefs":[]},"05036471-be13-42e6-b278-7ae128de708b":{"id":"05036471-be13-42e6-b278-7ae128de708b","doc_no":"A.3.2.2.1.1.1.1.3.6","title":"Drift","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2481,"content":"The CRR for Drift is:\n\n- 3.51% for USDe on Main market\n- 3.49% for USDC on Main market\n- 2.67% for EURC on Main market\n- 2.26% for sUSDe on Main market\n- 2.24% for USDY on Main market\n- 1.90% for USDT on Main market\n- 1.84% for AUSD on Main market\n- 1.82% for syrupUSDC on Main market\n- 1.59% for PYUSD on Main market\n- 1.55% for USDS on Main market\n- 1.52% for USDC on JLP market\n\nThe maximum exposure a Prime Agent may have to Drift may not exceed 25,000,000 USDS.","contentHash":"d0bc4b9bc76dc4d6b00524a5c08881f23ee4c94a05887d1d4b9ced4acc7c51e3","addressRefs":[]},"3f49b256-b18d-4a2a-b5a9-f55318455a3c":{"id":"3f49b256-b18d-4a2a-b5a9-f55318455a3c","doc_no":"A.3.2.2.1.1.1.1.3.7","title":"Anchorage","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2482,"content":"Offchain lending through Anchorage Digital has a CRR of 3%. The maximum exposure is 500,000,000 USD. The terms of this offchain lending must conform to the following specifications:\n\n- Collateral Asset: Native BTC\n- Initial LTV: 80% (125% collateralization ratio)\n- Margin Call LTV: 85% (117.6% collateralization ratio)\n- Margin Call Period: 24 hours\n- Liquidation LTV: 90% (111.1% collateralization ratio)\n- Maturity Date: Approximately 6-month duration","contentHash":"e606d197c4faf64ee0034cdc0754a6d0e0dea8b23cc663d272f2c7445165725b","addressRefs":[]},"6cef23c7-aaae-493d-bd76-a2909c25970a":{"id":"6cef23c7-aaae-493d-bd76-a2909c25970a","doc_no":"A.3.2.2.1.1.1.1.3.8","title":"Morpho Vaults","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2483,"content":"The documents herein define the Instance Financial CRR applied to specific Morpho vault allocations.","contentHash":"68161053ba28e9032ee56f7e8dcd1fcc6a072df17d36a5c2fe143af10b8b1153","addressRefs":[]},"f3df0565-407c-43bb-9b3e-52bbc5223a26":{"id":"f3df0565-407c-43bb-9b3e-52bbc5223a26","doc_no":"A.3.2.2.1.1.1.1.3.8.1","title":"Morpho Grove x Steakhouse High Yield USDC Vault","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2484,"content":"The CRRs for the following market allocations in the vault are:\n\n- PT-USDe / USDC – LLTV: 91.5%\n    - CRR = 4%\n- PT-sUSDe / USDC – LLTV: 91.5%\n    - CRR = 4%\n- PT-cUSD0 / USDC – LLTV: 91.5%\n    - CRR = 1%\n- mF-One / USDC – LLTV: 91.5%\n    - CRR = 100%","contentHash":"cd2822e7048f972007f309bf3100656832a3c4f75435a0d5b29469d8cccd48d5","addressRefs":[]},"b9a27ec8-26fd-469b-8963-1e03e9a73ff6":{"id":"b9a27ec8-26fd-469b-8963-1e03e9a73ff6","doc_no":"A.3.2.2.1.1.1.1.3.8.2","title":"Morpho Grove x Steakhouse High Yield AUSD Vault","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2485,"content":"Allocation to the Agora AUSD Morpho Vault on Monad via FalconX has an Instance Financial CRR of 5%. Total combined FalconX allocations must not exceed 100,000,000 USDS.","contentHash":"1b11f747cc3d428b3f8da135cab350833642fd3159731cd694a586dbc1b4372f","addressRefs":[]},"200cd606-26e9-427e-b965-976e7140a976":{"id":"200cd606-26e9-427e-b965-976e7140a976","doc_no":"A.3.2.2.1.1.1.1.3.9","title":"Uniswap V3","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2486,"content":"Allocation to the AUSD / USDC Uniswap v3 pool via FalconX on Monad has a CRR of 3%. Total combined FalconX allocations must not exceed 100,000,000 USDS.","contentHash":"cf7b613093b37ff47f07478c19ae8118a4cc72dc3166690f255fb821883a9c5a","addressRefs":[]},"e96da090-34ff-4445-a1d3-22cc69be2e51":{"id":"e96da090-34ff-4445-a1d3-22cc69be2e51","doc_no":"A.3.2.2.1.1.1.1.4","title":"Reference Implementation","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2487,"content":"A reference implementation of the calculation of Instance Financial RRC for lending markets is included herein.\n\n```\nimport math\nfrom collections import defaultdict\nimport numpy as np\nfrom scipy.stats import norm\n\n# Constants\nRISK_FREE_RATE = 0.04  # SOFR\nTIME_HORIZON = 1       # 1 year\n\nclass FinancialRRCModel:\n    def __init__(self):\n        # For demo purposes, we hardcode a dummy correlation map\n        self.token_correlation_map = {\n            'TOKENA': {'TOKENB': 0.5},\n            'TOKENB': {'TOKENA': 0.5},\n        }\n\n    def _calculate_effective_volatility(self, list_1, list_2):\n        \"\"\"\n        Calculate the effective variance between two sets of positions.\n        \"\"\"\n        effective_variance = 0.0\n        for sym1, pos1 in list_1.items():\n            for sym2, pos2 in list_2.items():\n                if sym1 == sym2:\n                    corr = 1.0\n                else:\n                    corr = self.token_correlation_map.get(sym1, {}).get(sym2,\n                           self.token_correlation_map.get(sym2, {}).get(sym1, 0.0))\n                effective_variance += (\n                    pos1[\"share\"]\n                    * pos2[\"share\"]\n                    * pos1[\"volatility_30d\"]\n                    * pos2[\"volatility_30d\"]\n                    * corr\n                )\n        return effective_variance\n\n    def _estimate_rrc_for_position(self, wallet_data):\n        \"\"\"\n        Estimate the required-risk capital (RRC) for a given wallet_data dict.\n        \"\"\"\n        # 1) compute effective volatilities\n        var_coll = self._calculate_effective_volatility(\n            wallet_data[\"collateral_positions\"],\n            wallet_data[\"collateral_positions\"],\n        )\n        var_debt = self._calculate_effective_volatility(\n            wallet_data[\"debt_positions\"],\n            wallet_data[\"debt_positions\"],\n        )\n        vol_coll = math.sqrt(var_coll)\n        vol_debt = math.sqrt(var_debt)\n\n        # 2) correlation collateral↔debt\n        cov_cd = self._calculate_effective_volatility(\n            wallet_data[\"collateral_positions\"],\n            wallet_data[\"debt_positions\"],\n        )\n        corr_cd = cov_cd / (vol_coll * vol_debt) if vol_coll * vol_debt > 0 else 0.0\n\n        # 3) drift terms\n        eff_coll_rate = sum(p[\"share\"] * p[\"supply_apy_30d\"]\n                            for p in wallet_data[\"collateral_positions\"].values())\n        eff_borrow_rate = sum(p[\"share\"] * p[\"borrow_apy_30d\"]\n                              for p in wallet_data[\"debt_positions\"].values())\n        eff_stake_rate = sum(p[\"share\"] * p[\"staking_apy_30d\"]\n                             for p in wallet_data[\"collateral_positions\"].values())\n\n        drift_cd = (\n            eff_coll_rate + eff_stake_rate - eff_borrow_rate\n            + (var_debt - var_coll) / 2\n        )\n\n        vol_cd = math.sqrt(\n            max(var_coll + var_debt - 2 * corr_cd * vol_coll * vol_debt, 0)\n        )\n\n        # 4) Black-Cox inputs\n        a = (drift_cd - vol_cd**2 / 2) / (vol_cd**2) if vol_cd > 0 else 0.0\n        L = wallet_data[\"collateral_usd_lt\"]\n        D = wallet_data[\"debt_usd\"]\n        log_term = math.log(L / D) if L > 0 and D > 0 else float(\"-inf\")\n        denom = vol_cd * math.sqrt(TIME_HORIZON) if vol_cd > 0 else 1e-10\n\n        d1 = (log_term + (drift_cd - vol_cd**2/2) * TIME_HORIZON) / denom\n        d2 = (log_term - (drift_cd - vol_cd**2/2) * TIME_HORIZON) / denom\n\n        # 5) Probability of Default\n        try:\n            pd = (\n                norm.cdf(-d1)\n                + norm.cdf(-d2) * (L / D) ** (-2 * a)\n            )\n        except OverflowError:\n            pd = 1.0\n        pd = max(0.0, min(pd, 1.0))\n\n        # 6) Loss Given Default\n        recovery = sum(\n            p[\"share\"] * (1 - p[\"liquidation_penalty\"]) * (1 - p[\"slippage\"])\n            / p[\"liquidation_threshold\"]\n            for p in wallet_data[\"collateral_positions\"].values()\n        )\n        lgd = max(0.0, min(1 - recovery, 1.0))\n\n        # 7) Exposure at Default\n        ead = sum(\n            debt[\"debt_usd\"] * math.exp((RISK_FREE_RATE + debt[\"borrow_apy_30d\"]) * TIME_HORIZON)\n            for debt in wallet_data[\"debt_positions\"].values()\n        )\n\n        # 8) Asset Correlation Coefficient\n        a_acc, b_acc, c_acc = 0.13, 10, 0.33\n        exp_term = math.exp(-b_acc * pd)\n        acc = a_acc * (1 - exp_term)/(1-math.exp(-b_acc)) + c_acc*(1 - (1-exp_term)/(1-math.exp(-b_acc)))\n\n        # 9) Credit risk weight\n        default_threshold = (\n            norm.ppf(max(pd, 1e-10)) + math.sqrt(acc) * norm.ppf(0.999)\n        ) / math.sqrt(1 - acc)\n        credit_risk = max(lgd * norm.cdf(default_threshold) - lgd * pd, 0)\n\n        # 10) RRC\n        rrc = credit_risk * ead\n        return rrc\n\n# -------- DEMO USAGE --------\n\nif __name__ == \"__main__\":\n    # 1) Build a dummy wallet_data structure\n    wallet_data = {\n        \"collateral_positions\": {\n            \"TOKENA\": {\n                \"share\": 0.6,\n                \"volatility_30d\": 0.2,\n                \"supply_apy_30d\": 0.05,\n                \"staking_apy_30d\": 0.02,\n                \"liquidation_penalty\": 0.1,\n                \"liquidation_threshold\": 0.8,\n                \"slippage\": 0.01,\n            },\n            \"TOKENB\": {\n                \"share\": 0.4,\n                \"volatility_30d\": 0.25,\n                \"supply_apy_30d\": 0.04,\n                \"staking_apy_30d\": 0.015,\n                \"liquidation_penalty\": 0.12,\n                \"liquidation_threshold\": 0.85,\n                \"slippage\": 0.015,\n            },\n        },\n        \"debt_positions\": {\n            \"TOKENA\": {\n                \"share\": 0.7,\n                \"volatility_30d\": 0.2,\n                \"borrow_apy_30d\": 0.06,\n                \"debt_usd\":  100_000,\n            },\n            \"TOKENB\": {\n                \"share\": 0.3,\n                \"volatility_30d\": 0.25,\n                \"borrow_apy_30d\": 0.07,\n                \"debt_usd\":  50_000,\n            },\n        },\n        \"collateral_usd_lt\": 200_000,\n        \"debt_usd\": 150_000,\n    }\n\n    # 2) Instantiate and run\n    model = FinancialRRCModel()\n    rrc = model._estimate_rrc_for_position(wallet_data)\n    print(f\"Estimated Required Risk Capital (RRC): ${rrc:,.2f}\")\n```","contentHash":"0269d2668f41f39b06b962abb5142ba35eaa9295d2b80d0b672a52d2af727862","addressRefs":[]},"69fac7fa-6168-4b74-99cc-28b557826556":{"id":"69fac7fa-6168-4b74-99cc-28b557826556","doc_no":"A.3.2.2.1.1.1.2","title":"Perpetual Positions","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2488,"content":"The implementation of the model for perpetual positions will be specified in a future iteration of the Atlas. The near-term treatment of these assets are specified in the subdocuments herein.","contentHash":"3065e193ac8f266473e80d82de28ba540930b3663f4b4e379a37907f40cc0ea3","addressRefs":[]},"92727d50-1ca0-48a9-93a0-0e504e845654":{"id":"92727d50-1ca0-48a9-93a0-0e504e845654","doc_no":"A.3.2.2.1.1.1.2.1","title":"Near-Term Treatment","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2489,"content":"In the near term pending development of the implementation of the model for perpetual positions, the Instance Financial CRRs specified in the documents herein will apply.","contentHash":"7ad12a511e57cccf1b9aa15f3e170e1cf0645e79f155d59c072054b0148ba3c0","addressRefs":[]},"f999239e-8676-4772-b201-2e00920b2bfb":{"id":"f999239e-8676-4772-b201-2e00920b2bfb","doc_no":"A.3.2.2.1.1.1.2.1.1","title":"Ethena","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2490,"content":"The near-term treatment for Ethena is specified in the documents herein.","contentHash":"35eab44c604b0e87c475f6b90f8cfe98317505caba5c5fe5f2aa738b2680ab7c","addressRefs":[]},"7ce05a43-e3ec-4c54-a11e-30e56526cfdd":{"id":"7ce05a43-e3ec-4c54-a11e-30e56526cfdd","doc_no":"A.3.2.2.1.1.1.2.1.1.1","title":"Ethena Capital Requirement Ratio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2491,"content":"Ethena Exposures consist of Direct Ethena Exposures (see [A.3.2.2.1.1.1.2.1.1.1.1 - Direct Ethena Exposures](e0fa035c-e8f3-4cd2-8ca1-a6afbd1825eb)), Indirect Ethena Exposures (see [A.3.2.2.1.1.1.2.1.1.1.2 - Indirect Ethena Exposures](d549b42d-a62e-4a5c-98a8-0ddc72aa6a67)), and Pendle Ethena Exposures (see [A.3.2.2.1.1.1.2.1.1.1.3 - Pendle Ethena Exposures](4094c159-9132-454a-81be-361a461b5098)). The Instance Financial CRR for Ethena Exposures is specified in the documents herein.","contentHash":"c4cd4a4f1afe3952fc35d6db90909612f0f3b86dabe17a61e0b353cdd71fdc93","addressRefs":[]},"e0fa035c-e8f3-4cd2-8ca1-a6afbd1825eb":{"id":"e0fa035c-e8f3-4cd2-8ca1-a6afbd1825eb","doc_no":"A.3.2.2.1.1.1.2.1.1.1.1","title":"Direct Ethena Exposures","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2492,"content":"Direct Ethena Exposures are exposures from directly holding USDe and sUSDe. Direct Ethena Exposures have a 3% Instance Financial CRR.","contentHash":"6cf15a6df62388345d59ddc6c270007fa595548f6f58b33a7839f7603c5d5c84","addressRefs":[]},"d549b42d-a62e-4a5c-98a8-0ddc72aa6a67":{"id":"d549b42d-a62e-4a5c-98a8-0ddc72aa6a67","doc_no":"A.3.2.2.1.1.1.2.1.1.1.2","title":"Indirect Ethena Exposures","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2493,"content":"Indirect Ethena Exposures are exposures from lending against Ethena related assets through lending markets. Indirect Ethena Exposures have Instance Financial CRR as specified in the documents herein.\n\nFor Indirect Ethena Exposure through lending markets, only the portion of the exposure to the lending market that is backed by Ethena related assets is subject to the Instance Financial CRR specified in the documents herein. The Instance Financial CRR for the remaining portion of the exposure is calculated based on the nature of the assets backing the exposure.","contentHash":"44d1c82daa57e8cd717fd4ae17a3e6e2678421a2d6fba496631f32ed9997f6ec","addressRefs":[]},"cfa615fb-9927-4059-873a-7c824a517835":{"id":"cfa615fb-9927-4059-873a-7c824a517835","doc_no":"A.3.2.2.1.1.1.2.1.1.1.2.1","title":"Lending Ethena Related Assets Against Ethena Related Collateral","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2494,"content":"For Ethena related assets lent against Ethena related collateral (e.g. lending USDe or sUSDe against PT-USDe or PT-sUSDe), the Instance Financial CRR is 3%.","contentHash":"d5ddaed4178da8b04b7de46a6d697b12921d17983e1402f6070731bbf5a10956","addressRefs":[]},"dadc95a6-c8ef-4abb-b9a5-d51bf2c0bf29":{"id":"dadc95a6-c8ef-4abb-b9a5-d51bf2c0bf29","doc_no":"A.3.2.2.1.1.1.2.1.1.1.2.2","title":"Lending Non-Ethena Related Assets Against Ethena Related Collateral","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2495,"content":"For non-Ethena related assets lent against Ethena related collateral (e.g. lending USDC against PT-USDe or PT-sUSDe), the Instance Financial CRR is 4%.","contentHash":"3eb1fd5564fa5fb6af0330f22b0f7d75eef0b4db0bef17470601f48c42b54240","addressRefs":[]},"4094c159-9132-454a-81be-361a461b5098":{"id":"4094c159-9132-454a-81be-361a461b5098","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3","title":"Pendle Ethena Exposures","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2496,"content":"Pendle Ethena Exposures are exposures from directly holding PT-USDe or PT-sUSDe. The Instance Financial CRR for Pendle Ethena Exposures is specified in the documents herein.","contentHash":"1293e963680644d69280ab7223e962aa2e228129375b6b978a1f7dcec8b9e564","addressRefs":[]},"ee9246d9-7500-4cd6-a934-0d2312d9e2a6":{"id":"ee9246d9-7500-4cd6-a934-0d2312d9e2a6","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.1","title":"Maturity Greater Than Six Months","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2497,"content":"Pendle Ethena Exposures with more than six (6) months to maturity require 100% Instance Total CRR.","contentHash":"64cf09a012be2c8da3bbb49027c397cf604231bf1f6087ea73557b7fd38a5f2b","addressRefs":[]},"6ed19cc0-5447-4df9-a9c1-45c8730f5f44":{"id":"6ed19cc0-5447-4df9-a9c1-45c8730f5f44","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2","title":"Maturity Less Than Or Equal To Six Months","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2498,"content":"Pendle Ethena Exposures with less than or equal to six (6) months to maturity have Instance Financial CRR calculated as follows:\n\n`Instance Financial CRR = initialValue - ((currentTime - startTime) * decayRatePerSecond)`\n\nThe parameters of this formula are defined in the documents herein.","contentHash":"3b6d29041699f8c9594ba7fb11670fc0e73474a1607dc908a77e1fcca047d7e4","addressRefs":[]},"5d2d2430-2fd5-4418-a688-e8f091eb44b9":{"id":"5d2d2430-2fd5-4418-a688-e8f091eb44b9","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.1","title":"Initial Value","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2499,"content":"The Initial Value `initialValue` is the Instance Financial CRR when the PT has exactly six (6) months to maturity. The `initialValue` is 10%.","contentHash":"d29ee985c61d28e1f926caa220afa51f5b46b0161506781bb7794ef7736782bc","addressRefs":[]},"340be283-72fe-4b51-9d75-d7f3c28fdab2":{"id":"340be283-72fe-4b51-9d75-d7f3c28fdab2","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.2","title":"Current Time","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2500,"content":"The Current Time `currentTime` is the timestamp of the current Ethereum block.","contentHash":"75af0b543dc13b16800783c2e3ec88791b6779270e063d108c4522d1ceb8ef5f","addressRefs":[]},"461eef24-5b4d-44b2-8281-a8c86bc4bc40":{"id":"461eef24-5b4d-44b2-8281-a8c86bc4bc40","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.3","title":"Start Time","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2501,"content":"The Start Time `startTime` is the timestamp of the block exactly six (6) months before the expiration timestamp of the PT.","contentHash":"6f16a4d9fcc1407b21baa447606ef9021b130ce27cfde56876c1938206f3e36c","addressRefs":[]},"cda560ff-5b25-44e1-bad4-e6ccfefdf7eb":{"id":"cda560ff-5b25-44e1-bad4-e6ccfefdf7eb","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.4","title":"Decay Rate Per Second","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2502,"content":"The Decay Rate Per Second `decayRatePerSecond` is calculated as follows:\n\n`decayRatePerSecond = totalDecay / totalDuration`\n\nThe parameters of this formula are defined in the documents herein.","contentHash":"379588bd6644855b917c50e318830f2068774b4852e06f6033b35448090e821c","addressRefs":[]},"c5530d25-b8ef-4ebe-9b38-7b2a29014ff3":{"id":"c5530d25-b8ef-4ebe-9b38-7b2a29014ff3","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.4.1","title":"Total Decay","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2503,"content":"The Total Decay `totalDecay` is equal to the Initial Value minus the Final Value.","contentHash":"32798bf42a16c9e1f36ccc5948d4b997b8aafef712f8d6a3d71ade6f51fbe101","addressRefs":[]},"900ecd08-64b7-4f37-8539-f4e822f11d98":{"id":"900ecd08-64b7-4f37-8539-f4e822f11d98","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.4.1.1","title":"Final Value","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2504,"content":"The Final Value is the Instance Financial CRR when the PT is at maturity. Since the PT is convertible into the underlying asset at this point it is equal to the Instance Financial CRR for Direct Ethena Exposures specified in [A.3.2.2.1.1.1.2.1.1.1.1 - Direct Ethena Exposures](e0fa035c-e8f3-4cd2-8ca1-a6afbd1825eb).","contentHash":"97b443060d3573d88e6c30dbf5c0e54b374ed9f7ae91e98e97d6ab6ce05adb30","addressRefs":[]},"0e21a4c4-cd66-4ace-9dcd-6015fc9e4966":{"id":"0e21a4c4-cd66-4ace-9dcd-6015fc9e4966","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.4.2","title":"Total Duration","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2505,"content":"The Total Duration `totalDuration` is equal to the Expiration Time minus the Start Time.","contentHash":"769b36cbc69ba2f5af68f74ca2056c78a5e92685149032eadbd701eabb5a0e49","addressRefs":[]},"537db44c-1b07-49bd-8b26-0174e3a2f34a":{"id":"537db44c-1b07-49bd-8b26-0174e3a2f34a","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.2.4.2.1","title":"Expiration Time","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2506,"content":"The Expiration Time is the expiration timestamp of the PT.","contentHash":"1af003499689e28c4c08c4278f84e460a3d0be0153902157ddf52087b7230e8a","addressRefs":[]},"6f850537-5e8a-4e57-95c8-f57a099ed8f3":{"id":"6f850537-5e8a-4e57-95c8-f57a099ed8f3","doc_no":"A.3.2.2.1.1.1.2.1.1.1.3.3","title":"Concentration Limit","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2507,"content":"Any investments made by Prime Agents in Pendle Ethena Exposures in excess of 20% of their total Allocation System Investments require 100% Instance Total CRR.","contentHash":"3df24fc632a8cd99651907034cb41231cef912a129a984245569de3bc08adb89","addressRefs":[]},"31757562-7f99-4d4e-b4e6-a7b0028e5d4d":{"id":"31757562-7f99-4d4e-b4e6-a7b0028e5d4d","doc_no":"A.3.2.2.1.1.1.2.1.1.2","title":"Ethena Aggregate Exposure Limits","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2508,"content":"The documents herein define aggregate exposure limits applicable to Ethena.","contentHash":"30fb5c3023a87d5f449dea56862c6ddf5ecdc504668691fd151ca096efb788bd","addressRefs":[]},"642b6bee-9702-4339-bda3-3a35d025bbcc":{"id":"642b6bee-9702-4339-bda3-3a35d025bbcc","doc_no":"A.3.2.2.1.1.1.2.1.1.2.1","title":"Ethena Aggregate Exposure","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2509,"content":"Ethena Aggregate Exposure is the sum of Ethena Exposures (see [A.3.2.2.1.1.1.2.1.1.1 - Ethena Capital Requirement Ratio](7ce05a43-e3ec-4c54-a11e-30e56526cfdd)) across all Prime Agents in the Sky Ecosystem.","contentHash":"ede2d1bbef5cc9d4de1eb596e66524cc6d90161a704850093e9ae1cb4bf46982","addressRefs":[]},"176c8562-848c-4868-8490-8e64da24adcd":{"id":"176c8562-848c-4868-8490-8e64da24adcd","doc_no":"A.3.2.2.1.1.1.2.1.1.2.2","title":"Ethena Aggregate Exposure Limit","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2510,"content":"The Ethena Aggregate Exposure Limit is 1,300,000,000 USDS.","contentHash":"91a3b7757b3190e3f6624a474667056aee23fc45b5ba3e0362d29610e508bea4","addressRefs":[]},"8e120edf-c87b-4d99-8f2a-65fb49bcc3b7":{"id":"8e120edf-c87b-4d99-8f2a-65fb49bcc3b7","doc_no":"A.3.2.2.1.1.1.2.1.1.2.3","title":"Ethena Exposure Limit","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2511,"content":"The Ethena Exposure Limit for each Agent is:\n\n- Spark - One half of the Ethena Aggregate Exposure Limit\n- Grove - One half of the Ethena Aggregate Exposure Limit\n- All other Prime Agents - Zero","contentHash":"84c620117c311deb4133a1082c413d7419dc44d9b1adc4623235645bf884f3f8","addressRefs":[]},"50854ba8-c788-4df5-9c70-b6f070a28bfd":{"id":"50854ba8-c788-4df5-9c70-b6f070a28bfd","doc_no":"A.3.2.2.1.1.1.2.1.1.2.4","title":"Prohibition On Investments That Would Cause Ethena Exposure Limit To Be Exceeded","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2512,"content":"No Prime Agent may make an investment in Ethena Exposures that would cause its Ethena Exposures to exceed its Ethena Exposure Limit.","contentHash":"8d59623fe7cbadc499fe91560c6eed0958e65a0b9bda3631c6a7e8959be8c11e","addressRefs":[]},"81e64445-f74c-4d61-8322-b2d30d3582f1":{"id":"81e64445-f74c-4d61-8322-b2d30d3582f1","doc_no":"A.3.2.2.1.1.1.2.1.1.2.5","title":"Sale Of Investments When Ethena Exposure Limit Is Exceeded","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2513,"content":"If a Prime Agent’s Ethena Exposures exceed its Ethena Exposure Limit, then the Core Council may direct the Agent to sell Ethena Exposures to reduce its Ethena Exposures below its Ethena Exposure Limit.","contentHash":"045626e85a83592e74ec0ce2ca0c5930167b4c35b12ebdeeb54cfab99cdb20be","addressRefs":[]},"465472b5-acc2-4a8e-9a42-543e16854e71":{"id":"465472b5-acc2-4a8e-9a42-543e16854e71","doc_no":"A.3.2.2.1.1.1.2.1.2","title":"Superstate","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2514,"content":"The near-term treatment for Superstate is specified in the documents herein.","contentHash":"2a2e55c30b0989a6b2886cc4e8f327aaf6435cf00e1e87e5ffae0267f51e83da","addressRefs":[]},"ffca1065-7f92-4815-8a65-52bdbc82c558":{"id":"ffca1065-7f92-4815-8a65-52bdbc82c558","doc_no":"A.3.2.2.1.1.1.2.1.2.1","title":"Superstate Capital Requirement Ratio","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2515,"content":"Superstate Exposures are exposures from holding USCC. Superstate Exposures have a 4.5% Instance Financial CRR.","contentHash":"168c278506da6717742e6a5d649c999035463b309fb0e52eeae2de89488f7a20","addressRefs":[]},"f5348df6-6161-454d-a8d4-bd02d2acc354":{"id":"f5348df6-6161-454d-a8d4-bd02d2acc354","doc_no":"A.3.2.2.1.1.1.2.1.2.2","title":"Superstate Aggregate Exposure Limits","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2516,"content":"The documents herein define aggregate exposure limits applicable to Superstate Exposures.","contentHash":"35ed37e73aa7b343e788878fc2e4904e0b1a688e88ded215d6d55a8d1fed8e23","addressRefs":[]},"6cf2221f-214c-4bc2-8de1-b0d6adb2a327":{"id":"6cf2221f-214c-4bc2-8de1-b0d6adb2a327","doc_no":"A.3.2.2.1.1.1.2.1.2.2.1","title":"Superstate Aggregate Exposure","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2517,"content":"Superstate Aggregate Exposure is the sum of Superstate Exposures (see [A.3.2.2.1.1.1.2.1.2.1 - Superstate Capital Requirement Ratio](ffca1065-7f92-4815-8a65-52bdbc82c558)) across all Prime Agents in the Sky Ecosystem.","contentHash":"8205003729694cfe386453934c9b5344e11e182fd429188104c0906d9bb7db87","addressRefs":[]},"ea606bf7-6dbf-41d2-a993-79b66c56b7c2":{"id":"ea606bf7-6dbf-41d2-a993-79b66c56b7c2","doc_no":"A.3.2.2.1.1.1.2.1.2.2.2","title":"Superstate Aggregate Exposure Limit","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2518,"content":"The Superstate Aggregate Exposure Limit is 500,000,000 USDS.","contentHash":"1fce222a645727256a2666f65e9631ba9e897f8e8cda4cd4cf02d0e18fc26097","addressRefs":[]},"a75e7eea-7567-4f5c-aba4-6d41fb6732dd":{"id":"a75e7eea-7567-4f5c-aba4-6d41fb6732dd","doc_no":"A.3.2.2.1.1.1.2.1.2.2.3","title":"Prohibition On Investments That Would Cause Superstate Aggregate Exposure Limit To Be Exceeded","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2519,"content":"No Prime Agent may make an investment in Superstate Exposures that would cause the Superstate Aggregate Exposure to exceed the Superstate Aggregate Exposure Limit.","contentHash":"68f401dc0f95c7352fda958d8db3750e72e231b1c9eba0f5db31d01ee4471a22","addressRefs":[]},"ee3016e5-521a-4f86-a684-aa66bd102c8f":{"id":"ee3016e5-521a-4f86-a684-aa66bd102c8f","doc_no":"A.3.2.2.1.1.1.2.1.2.2.4","title":"Sale Of Investments When Superstate Aggregate Exposure Limit Is Exceeded","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2520,"content":"If the Superstate Aggregate Exposure exceeds the Superstate Aggregate Exposure Limit, then the Core Council may direct Prime Agents to sell Superstate Exposures to reduce the Superstate Aggregate Exposure below the Superstate Aggregate Exposure Limit.","contentHash":"54c2d095dfdd4a282a2873fd2219672737be40ffb084c63367c5691e124ac8cc","addressRefs":[]},"d0b3b345-23c1-4cb0-9d16-aa7b44ff7294":{"id":"d0b3b345-23c1-4cb0-9d16-aa7b44ff7294","doc_no":"A.3.2.2.1.1.1.2.1.2.3","title":"Superstate Deployment Limits","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2521,"content":"The documents herein define the deployment limits applicable to Superstate Exposures.","contentHash":"5cf502be8d46d027a116b4d132d33872d6cb13e6eec606d960ea45d370812b22","addressRefs":[]},"3fd57a2e-3e2a-41c1-a9f7-cfbe58799837":{"id":"3fd57a2e-3e2a-41c1-a9f7-cfbe58799837","doc_no":"A.3.2.2.1.1.1.2.1.2.3.1","title":"Superstate Initial Deployment Limit","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2522,"content":"The Initial Deployment is the first deployment of capital by a Prime Agent into Superstate Exposures. The Initial Deployment may not exceed 20,000,000 USDS.","contentHash":"e41a0dceb66b645f729d769106048aa8c3a5ed07369848c40f58729efe6426b4","addressRefs":[]},"e36d7537-95f8-4156-955f-bc74d37935d8":{"id":"e36d7537-95f8-4156-955f-bc74d37935d8","doc_no":"A.3.2.2.1.1.1.2.1.2.3.2","title":"Superstate Subsequent Deployment Limits","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2523,"content":"Subsequent Deployments are deployments of capital by a Prime Agent into Superstate Exposures after its Initial Deployment (see [A.3.2.2.1.1.1.2.1.2.3.1 - Superstate Initial Deployment Limit](3fd57a2e-3e2a-41c1-a9f7-cfbe58799837)). Each Subsequent Deployment may not exceed 50,000,000 USDS and requires approval from the Core Council Risk Advisor on behalf of the Core Council.","contentHash":"1077cebe799cd214ddeac60039a0d91b2b37e95559e160afa5dee4d28a095558","addressRefs":[]},"69d0776b-786c-408b-b76a-860ea60b6b9a":{"id":"69d0776b-786c-408b-b76a-860ea60b6b9a","doc_no":"A.3.2.2.1.1.1.3","title":"Direct Exposures","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2524,"content":"The implementation of the model for direct exposures will be specified in a future iteration of the Atlas. The near-term treatment of these assets are specified in the subdocuments herein.","contentHash":"5d56d37a7487f8157536868acae47435386c5ea2baedd993ba7270426888b7ce","addressRefs":[]},"f4d20c04-8a62-43b1-b806-7559e8182bfb":{"id":"f4d20c04-8a62-43b1-b806-7559e8182bfb","doc_no":"A.3.2.2.1.1.1.3.1","title":"Near-Term Treatment","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2525,"content":"In the near term pending development of the implementation of the model for direct exposures, a 25% Instance Financial CRR will be applied to all direct exposures. In the near term, direct exposures will be considered to be any assets held idle in a wallet controlled by a Prime Agent.","contentHash":"425e97661512d66065f20c3388bdf471efeb8fa306781cdd66f80e684be22c51","addressRefs":[]},"da1a154c-6db8-4012-91a7-31ea4e73e95d":{"id":"da1a154c-6db8-4012-91a7-31ea4e73e95d","doc_no":"A.3.2.2.1.1.1.4","title":"Bond-Like Instruments","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2526,"content":"The implementation of the model for bond-like instruments will be specified in a future iteration of the Atlas. The near-term treatment of these assets are specified in the subdocuments herein.","contentHash":"d0da5c924d98f61691c04f096a8731c9afc0f7bbc45d035dbc949014ae854b8d","addressRefs":[]},"a479643e-fbd3-4c9b-aba0-40f4657a8011":{"id":"a479643e-fbd3-4c9b-aba0-40f4657a8011","doc_no":"A.3.2.2.1.1.1.4.1","title":"Near-Term Treatment","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2527,"content":"In the near term pending development of the implementation of the model for bond-like exposures, the following Instance Financial CRRs will apply:\n\n- PT-USDS - 0% Instance Financial CRR\n- All other bond-like exposures - 4% Instance Financial CRR\n\nIn the near term, only Pendle PT tokens will be eligible for investment under this provision.","contentHash":"81081dfb16bec698db7bd96541fa769b795f5c528d20a78ffbd3f84f1ba23de9","addressRefs":[]},"79c20bfd-f724-482e-8aae-52c962b8268a":{"id":"79c20bfd-f724-482e-8aae-52c962b8268a","doc_no":"A.3.2.2.1.1.1.5","title":"Real World Assets","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2528,"content":"The documents herein define the calculation of Instance Financial RRC for Real World Assets.","contentHash":"131ab36f9744cbdf4c58c577c23999ae24220e21a3ebcd567c522055073f5c7b","addressRefs":[]},"b95825a2-9293-434d-bc06-459fee6aecde":{"id":"b95825a2-9293-434d-bc06-459fee6aecde","doc_no":"A.3.2.2.1.1.1.5.1","title":"Methodology","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2529,"content":"The documents herein define common methodologies that are applicable to the entirety of the process for calculating Instance Financial RRC for Real World Assets.","contentHash":"6d903d31c13a77fde95139237daad555d4613bc88719c204716a1b167ba37e9d","addressRefs":[]},"95695429-cc27-403d-ad12-4ecf89203637":{"id":"95695429-cc27-403d-ad12-4ecf89203637","doc_no":"A.3.2.2.1.1.1.5.1.1","title":"Basis In Basel Framework","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2530,"content":"The process for calculating Instance Financial RRC for Real World Assets is based on the Basel Framework developed by the Basel Committee on Bank Supervision. See [https://www.bis.org/basel_framework/index.htm](https://www.bis.org/basel_framework/index.htm).","contentHash":"9bdd7f95f634597639d8dd98f0e0f2b500bfaa7e81c0d93a7808eeecb59d8180","addressRefs":[]},"0c97534b-d4f4-4a42-854c-b39993c95f02":{"id":"0c97534b-d4f4-4a42-854c-b39993c95f02","doc_no":"A.3.2.2.1.1.1.5.1.2","title":"Citations To Basel Framework","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2531,"content":"Citations are made throughout the process for calculating Instance Financial RRC for Real World Assets to relevant provisions from the Basel Framework.\n\nThese citations follow the standard format of `[Prefix][Chapter Number].[Paragraph Number]`, where `Prefix` is a three letter prefix indicating the regulatory standard area or chapter family. For example, a citation to `CRE20.1` refers to Credit Risk Standards, Chapter 20 regarding \"Standardised Approach: Individual Exposures\", paragraph 1.\n\nWhen reference is made to a range of documents, a hyphen may be used. For example, `CRE20.1-93` refers to Credit Risk Standards, Chapter 20 regarding \"Standardised Approach: Individual Exposures\", paragraphs 1 through 93.\n\nSimilarly, discrete sets of documents may be referenced using a comma. For example, `CRE40-41, 45` refers to Credit Risk Standards, Chapters 40 to 41 and 45.","contentHash":"13085cc99be7b2ab09c49f872b8cbac15611475f9e53f6497f6ad15fe4a8fe89","addressRefs":[]},"96a9c07c-6a3e-4a03-87a9-d6c72ffac340":{"id":"96a9c07c-6a3e-4a03-87a9-d6c72ffac340","doc_no":"A.3.2.2.1.1.1.5.1.3","title":"Banking Book","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2532,"content":"In the process for calculating Instance Financial RRC for Real World Assets, all exposures are treated as if they were part of the banking book.","contentHash":"2ef5493d0733ca999a5c59d385d0d0c0c32a0c378cd8d6945745802e36d721ce","addressRefs":[]},"58cc9f0b-0d88-4027-bae4-a33cb839e748":{"id":"58cc9f0b-0d88-4027-bae4-a33cb839e748","doc_no":"A.3.2.2.1.1.1.5.2","title":"Process For Calculating Instance Financial RRC","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2533,"content":"The documents herein define the process for calculating Instance Financial RRC for Real World Assets.","contentHash":"6ffa3e382901a10092f237cb2d8154a79ca217c8b9f8dcfec96a9792f4f2b33a","addressRefs":[]},"dbc4c20e-faa4-429d-8289-f38318d443f1":{"id":"dbc4c20e-faa4-429d-8289-f38318d443f1","doc_no":"A.3.2.2.1.1.1.5.2.1","title":"Identify Exposure Types","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2534,"content":"The first step is identifying the Exposure Type that an exposure fits under. The Exposure Types are:\n\n- On-Balance Sheet Items (see `CRE20.1-93`)\n- Off-Balance Sheet Items (see `CRE20.94-101`)\n- Securitization Tranches (see `CRE40-41, 45`)\n- Derivatives or Securities Financing Transactions (see `CRE50-52`)\n- Funds / Collective Investment Undertakings / Exchange Traded Funds (see `CRE60`)\n- Commodities (see `MAR21.13`)\n- Foreign Exchange (see `MAR21.14`)","contentHash":"01362bc55b3df3a70138da0eff22b14cca0f070e5c30b439484fb55997e16b67","addressRefs":[]},"db4ae988-b240-4506-b040-4712afc76fb2":{"id":"db4ae988-b240-4506-b040-4712afc76fb2","doc_no":"A.3.2.2.1.1.1.5.2.2","title":"Calculate Exposure At Default Including Credit Risk Mitigation","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2535,"content":"The second step is calculating the Exposure at Default including Credit Risk Mitigation as specified in the documents herein.","contentHash":"2c572787cba8cf384e74b4aad0e8957944e898f57f12d2d984a0a1a8d8f1dd9f","addressRefs":[]},"ec8879e3-71b8-450d-985f-b1edf14f8b4d":{"id":"ec8879e3-71b8-450d-985f-b1edf14f8b4d","doc_no":"A.3.2.2.1.1.1.5.2.2.1","title":"Calculation Of Exposure At Default","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2536,"content":"Exposure At Default is calculated as specified in the documents herein.","contentHash":"5cb7671d149714e700d69ae139930715a427f2c6113fd523b1c5b25a4e751bbf","addressRefs":[]},"9e047432-7a9f-4dc0-8172-4085c603d9ba":{"id":"9e047432-7a9f-4dc0-8172-4085c603d9ba","doc_no":"A.3.2.2.1.1.1.5.2.2.1.1","title":"Exposure At Default Equal To Book Value","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2537,"content":"For the following Exposure Types, Exposure At Default is equal to book value:\n\n- On-Balance Sheet Items\n- Securitization Tranches\n- Derivatives or Securities Financing Transactions\n- Funds / Collective Investment Undertakings / Exchange Traded Funds\n- Commodities\n- Foreign Exchange","contentHash":"0a03ea2a7b82fdb79553f3058fc7c67e5ca3fa8961fa870bb10128577465e495","addressRefs":[]},"9868d6c9-17ec-44da-8898-b59a1ae579e0":{"id":"9868d6c9-17ec-44da-8898-b59a1ae579e0","doc_no":"A.3.2.2.1.1.1.5.2.2.1.2","title":"Exposure At Default Equal To Book Value Multiplied By Credit Conversion Factor","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2538,"content":"For the following Exposure Types, Exposure At Default is equal to book value multiplied by the Credit Conversion Factor (see `CRE51`):\n\n- Off-Balance Sheet Items","contentHash":"8b9a000da26b1d056b1c668697112da3ae1d3ba30fdf395a694abec91b918f92","addressRefs":[]},"da454ffd-494a-4806-acb5-93653b1b8b11":{"id":"da454ffd-494a-4806-acb5-93653b1b8b11","doc_no":"A.3.2.2.1.1.1.5.2.2.2","title":"Adjustment For Credit Risk Mitigation","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2539,"content":"The Exposure At Default calculated in [A.3.2.2.1.1.1.5.2.2.1 - Calculation Of Exposure At Default](ec8879e3-71b8-450d-985f-b1edf14f8b4d) is then adjusted for Credit Risk Mitigation (see `CRE22`) to arrive at an adjusted Exposure At Default used for the remainder of the calculations.","contentHash":"dd273630f5e762ccf65c0c16311027d8aceab22c9f94d44f0fe30a39d46e229f","addressRefs":[]},"a1ff2a3d-7131-425c-80c5-a887a4259f12":{"id":"a1ff2a3d-7131-425c-80c5-a887a4259f12","doc_no":"A.3.2.2.1.1.1.5.2.3","title":"Determine Risk Weights","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2540,"content":"The third step is calculating the Risk Weights as specified in the documents herein.","contentHash":"69e6f08ac4243cf7c4c10322384a57eb004843127354e31ab8a80415df10dfaf","addressRefs":[]},"0144ae72-c945-4f62-998c-e533a5f32858":{"id":"0144ae72-c945-4f62-998c-e533a5f32858","doc_no":"A.3.2.2.1.1.1.5.2.3.1","title":"On-Balance Sheet Or Off-Balance Sheet Items","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2541,"content":"Credit Risk for On-Balance Sheet or Off-Balance Sheet Items is calculated based on the relevant provisions in the Basel Framework as follows:\n\n| Exposure Type | Reference |\n| --- | --- |\n| Sovereigns | `CRE20.7-10` |\n| Non-central government Public Sector Entities (PSEs) | `CRE20.11-12` |\n| Multilateral Development Banks | `CRE20.13-15` |\n| Banks | `CRE20.16-32` |\n| Covered Bonds | `CRE20.33-39` |\n| Securities, firms, and other financial institutions | `CRE20.40` |\n| Corporates | `CRE20.41-52` |\n| Subordinated debt, equity, and other capital instruments | `CRE20.53-62` |\n| Retail exposure class | `CRE20.63-68` |\n| Real Estate exposure class | `CRE20.69-91` |\n| Direct credit substitutes | `CRE20.95` |\n| Sale and repurchase agreements where the credit risk remains with the bank | `CRE20.95` |\n| Lending of banks' securities or the posting of securities as collateral by banks | `CRE20.95` |\n| Forward assets purchases | `CRE20.95` |\n| Forward forward deposits | `CRE20.95` |\n| Partly paid shares and securities | `CRE20.95` |\n| Credit substitutes not included in any other category | `CRE20.95` |\n| Note issuance facilities | `CRE20.96` |\n| Revolving underwriting facilities | `CRE20.96` |\n| Certain transactions-related contingent items (e.g. performance bonds, bid bonds, warranties, standby letters of credit) | `CRE20.97` |\n| Commitments regardless of the maturity of the underlying facility | `CRE20.98` |\n| Both issuing and confirming banks of short-term self-liquidating trade letters of credit arising from the movement of goods | `CRE20.99` |\n| Commitments that are unconditionally cancellable at any time by the bank without prior notice | `CRE20.100` |","contentHash":"0fa56eb78088446120133f8698d91c875400c7894a575c3db8ca6ef28d3d5dc7","addressRefs":[]},"5f70b7dd-4a76-4204-9bd6-9e6ce2864f82":{"id":"5f70b7dd-4a76-4204-9bd6-9e6ce2864f82","doc_no":"A.3.2.2.1.1.1.5.2.3.2","title":"Securitization Tranches","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2542,"content":"Risk Weights for Securitization Tranches (see `CRE40-41, 45`) are calculated as follows:\n\n- If the Securitization Tranche is rated, then the Securitisation - External Ratings Based Approach should be applied (see `CRE42`).\n- If the Securitization Tranche is not rated, then the Securitisation - Standard Approach should be applied (see `CRE41`).","contentHash":"8cf2deeb770df27c04fe1a0280e6a028c62de1841f7efcd77a434930c31dce9e","addressRefs":[]},"3622ac1e-4ed9-41ba-ba91-0396e1b30b67":{"id":"3622ac1e-4ed9-41ba-ba91-0396e1b30b67","doc_no":"A.3.2.2.1.1.1.5.2.3.3","title":"Derivatives Or Securities Financing Transactions","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2543,"content":"Counterparty Credit Risk for Derivatives or Securities Financing Transactions is calculated based on the relevant provisions in the Basel Framework (see `CRE50-52`). In addition, if the instrument is an Over The Counter derivative, Credit Valuation Adjustment capital is applied as well (see `MAR50`).","contentHash":"7bc23368f60fffd9d0ace1b6b20278e64761ad129ed8e284eca96139100e5316","addressRefs":[]},"56ef98fa-582e-4c60-87f2-34400bad72fe":{"id":"56ef98fa-582e-4c60-87f2-34400bad72fe","doc_no":"A.3.2.2.1.1.1.5.2.3.4","title":"Funds / Collective Investment Undertakings / Exchange Traded Funds","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2544,"content":"Risk Weights for Funds / Collective Investment Undertakings / Exchange Traded Funds (see `CRE60`) are calculated as follows:\n\n- If look-through is feasible, apply the Look Through Approach (see `CRE60.2-5`)\n- If look-through is not feasible but the mandate information is available, apply the Mandate Based Approach (see `CRE60.6-7`)\n- If look-through is not feasible and the mandate information is not available, apply the fallback conservative approach (see `CRE60.8`)","contentHash":"c3f7fdf6ef102026e530e421906b38ec693e6c822502fd18bf1edfd9f8fbf1fc","addressRefs":[]},"75db9d5b-c245-4574-8705-2cd5d4dde0b1":{"id":"75db9d5b-c245-4574-8705-2cd5d4dde0b1","doc_no":"A.3.2.2.1.1.1.5.2.3.5","title":"Commodities","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2545,"content":"Market Risk for Commodities is calculated based on the relevant provisions in the Basel Framework (see `MAR21.13`).","contentHash":"9255f9dbc22bacd4fbf11559344e9015bf7a6186651f2ffb9c0b27b8a4d6e541","addressRefs":[]},"11b18384-63d6-478c-bc14-9f1ec495c1cb":{"id":"11b18384-63d6-478c-bc14-9f1ec495c1cb","doc_no":"A.3.2.2.1.1.1.5.2.3.6","title":"Foreign Exchange","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2546,"content":"Market Risk for Foreign Exchange is calculated based on the relevant provisions in the Basel Framework (see `MAR21.14`).","contentHash":"554aef639d9d160760c3f4a83f01052e71454fc111ee82b6c39d79d6da2dbce4","addressRefs":[]},"cb6e24c8-5e69-41ae-b600-4d9a7261f172":{"id":"cb6e24c8-5e69-41ae-b600-4d9a7261f172","doc_no":"A.3.2.2.1.1.1.5.2.4","title":"Aggregate Risk Weighted Assets","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2547,"content":"The fourth step is calculating Aggregate Risk Weighted Assets (\"RWA\").","contentHash":"26d39d881849dbb4015e1578fdb5e069d9cc88e1850509b99ffbd00b070ca9bd","addressRefs":[]},"34a37582-aa59-4c04-92d6-3cc758e9e92e":{"id":"34a37582-aa59-4c04-92d6-3cc758e9e92e","doc_no":"A.3.2.2.1.1.1.5.2.4.1","title":"Calculate Risk Weighted Assets","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2548,"content":"Credit RWA, Market RWA, Counterparty Credit Risk RWA, and Credit Valuation Adjustment RWA are calculated by multiplying the Exposure At Default (see [A.3.2.2.1.1.1.5.2.2 - Calculate Exposure At Default Including Credit Risk Mitigation](db4ae988-b240-4506-b040-4712afc76fb2)) by the applicable Risk Weights (see [A.3.2.2.1.1.1.5.2.3 - Determine Risk Weights](a1ff2a3d-7131-425c-80c5-a887a4259f12)).","contentHash":"11082872cace19413b0d83fbbd76281ac1e9ac190df118819a1f430184562a1e","addressRefs":[]},"fabb3382-d2eb-4cba-9e54-3fd5b83ea47c":{"id":"fabb3382-d2eb-4cba-9e54-3fd5b83ea47c","doc_no":"A.3.2.2.1.1.1.5.2.4.2","title":"Calculate Aggregate Risk Weighted Assets","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2549,"content":"Aggregate RWA is calculated as the sum of (1) Credit RWA, (2) Market RWA, (3) Counterparty Credit RWA, and (4) Credit Valuation Adjustment RWA.","contentHash":"aa15eae5d8d18088084b6f694b6489ca4c7d6925a1299a41af9f7cfb8d9346d9","addressRefs":[]},"6047795b-9a0e-4410-b794-76083388281e":{"id":"6047795b-9a0e-4410-b794-76083388281e","doc_no":"A.3.2.2.1.1.1.5.2.5","title":"Apply Leverage Adjustment","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2550,"content":"The fifth step is to adjust the Aggregate RWA specified in [A.3.2.2.1.1.1.5.2.4 - Aggregate Risk Weighted Assets](cb6e24c8-5e69-41ae-b600-4d9a7261f172) for leverage (see `CRE99.128-133`)","contentHash":"034ce3ea13e1b489f244d384b8f821b4e5e607c589ef9ed1fd181878d5a832bf","addressRefs":[]},"70013695-3823-407a-9603-b38795ba9899":{"id":"70013695-3823-407a-9603-b38795ba9899","doc_no":"A.3.2.2.1.1.1.5.2.6","title":"Determine Required Risk Capital","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2551,"content":"The final step is to multiply the adjusted Aggregate RWA specified in [A.3.2.2.1.1.1.5.2.5 - Apply Leverage Adjustment](6047795b-9a0e-4410-b794-76083388281e) by an 8% capital ratio to arrive at Instance Financial RRC.","contentHash":"93572c95c3afb4bea305ef8d8093be9f1ee403fae2c7db13c9baed4981544ba4","addressRefs":[]},"748f6364-f63b-4601-8f43-345ae3398224":{"id":"748f6364-f63b-4601-8f43-345ae3398224","doc_no":"A.3.2.2.1.1.1.5.3","title":"Exceptions","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2552,"content":"The documents herein define exceptions to the calculation of Instance Financial RRC for specific Real World Assets. These exceptions will be removed in a future iteration of the Atlas.","contentHash":"12fbdf0029270752fd1a50e64cfecc67d3243aa20588e05b548dc4db2f4ca85d","addressRefs":[]},"672d377f-067e-4742-a987-b2c6258f9c99":{"id":"672d377f-067e-4742-a987-b2c6258f9c99","doc_no":"A.3.2.2.1.1.1.5.3.1","title":"Instance Financial CRRs For Specific Assets","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2553,"content":"The following Instance Financial CRRs apply to specific assets listed:\n\n- BUIDL, JTRSY on Ethereum Mainnet, and USTB - 0% Instance Financial CRR\n- JTRSY on Avalanche - 0.5% Instance Financial CRR\n- JAAA on Ethereum Mainnet - 1.6% Instance Financial CRR\n- JAAA on Avalanche - 2.1% Instance Financial CRR\n- STAC on Ethereum Mainnet - 1.6% Instance Financial CRR\n- GACLO-1 on Ethereum Mainnet - 0.85% Instance Financial CRR\n- ACRDX on Plume - 9.99% Instance Financial CRR\n- ACRDX on Ethereum Mainnet - 9.99% Instance Financial CRR","contentHash":"a3e4b805e1698b943db22075b08523bc4d5cb22b62adf4a7c1abedec82d4dbf8","addressRefs":[]},"66506235-0e6c-4fa9-8e22-5eb4f19cb330":{"id":"66506235-0e6c-4fa9-8e22-5eb4f19cb330","doc_no":"A.3.2.2.1.1.1.5.3.1.1","title":"Additional Restrictions On Investments In JTRSY And JAAA On Avalanche","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2554,"content":"Investments in JTRSY and JAAA on Avalanche are subject to the following additional restrictions:\n\n- The initial deployment of capital into JTRSY and JAAA on Avalanche may not exceed 20 million USDS in total;\n- Each additional deployment of capital into JTRSY or JAAA must be approved by the Core Council Risk Advisor;\n- Until audits of Centrifuge v3 are approved by the Protocol Security Workstream Lead, the Prime must be below a 90% Encumbrance Ratio on a pro forma basis assuming that each additional deployment of capital into JTRSY and JAAA requires 100% Instance Total CRR; and\n- Total investments in JTRSY and JAAA on Avalanche may not exceed 250 million USDS.","contentHash":"261fb687bce95d6693421d8e33dac071511533e4ab836a80f3dd188605259fe7","addressRefs":[]},"8cbfb295-019d-4ac6-af19-1a1fead233b0":{"id":"8cbfb295-019d-4ac6-af19-1a1fead233b0","doc_no":"A.3.2.2.1.1.1.5.3.1.2","title":"Additional Restrictions On Investments In ACRDX On Plume And Ethereum Mainnet","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2555,"content":"Total ACRDX exposure may not increase beyond 50.97 million USDS and should be reduced to zero over time.","contentHash":"a807037da1dfdb0ce79f440416ad15665d4aa1ec238391de5710440f6e421cd5","addressRefs":[]},"c5d70220-4797-4df9-8977-4998d4a57888":{"id":"c5d70220-4797-4df9-8977-4998d4a57888","doc_no":"A.3.2.2.1.1.1.5.3.2","title":"Restrictions On Investments On Plume","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2556,"content":"Investments on Plume are subject to the following restrictions:\n\n- Assets other than RWAs on Plume or being bridged to Plume require 100% Instance Total CRR; and\n- Total investments on Plume may not exceed 125 million USDS.","contentHash":"17da471c6658972c2486c36ce168378e8eebf3322e1932d03a52fd355dfe738a","addressRefs":[]},"3c0a9e8b-4a0b-4059-87a4-155deaee0486":{"id":"3c0a9e8b-4a0b-4059-87a4-155deaee0486","doc_no":"A.3.2.2.1.1.1.6","title":"Cash Stablecoins","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2557,"content":"The implementation of the model for Cash Stablecoins will be specified in a future iteration of the Atlas. The near-term treatment of these assets are specified in the subdocuments herein.","contentHash":"a2ebf1d417d60d9e1fcffacf7e493abafe835e5bb54c1d05091ab193d9c35c3a","addressRefs":[]},"8aee612b-fe36-4c6b-adee-2e0762579a40":{"id":"8aee612b-fe36-4c6b-adee-2e0762579a40","doc_no":"A.3.2.2.1.1.1.6.1","title":"Near-Term Treatment","type":"Core","depth":6,"parentId":"aada206c-84bd-41e7-880d-1304889f4896","order":2558,"content":"In the near term pending development of the implementation of the model for Cash Stablecoins, a 0% Instance Financial CRR will be applied to Cash Stablecoins. In the near term, only USDS, sUSDS, Dai, sDai, USDC, USDT, and pyUSD (either held directly or through decentralized exchanges such as Curve) will be eligible for investment under this provision.","contentHash":"528354b914157189c5247a583a56c4787c97e13a84ded405769b706777794e58","addressRefs":[]},"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080":{"id":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","doc_no":"A.3.2.2.1.2","title":"Instance Smart Contract RRC Implementation","type":"Core","depth":5,"parentId":"d10b1c92-b839-45f1-995d-a23381fd6068","order":2559,"content":"The documents herein define the implementation of the Risk Framework for calculating Instance Smart Contract RRC.","contentHash":"f71f7d4224e907afe011e27b94df7257c512bf0268098dab41c1a687bd79b4a9","addressRefs":[]},"162cfc93-77bd-4878-a8be-370d8862d792":{"id":"162cfc93-77bd-4878-a8be-370d8862d792","doc_no":"A.3.2.2.1.2.1","title":"Defining Relevant Smart Contracts","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2560,"content":"The first step in calculating Instance Smart Contract RRC with respect to an Allocation System opportunity is to identify the set of relevant smart contracts for the opportunity.","contentHash":"62db6040d2c7df20a5c446b402da558bc8d09b792c41f56ee287b1b4f6e1a0e7","addressRefs":[]},"87a91c14-92b1-4d14-a90a-a02086a05066":{"id":"87a91c14-92b1-4d14-a90a-a02086a05066","doc_no":"A.3.2.2.1.2.1.1","title":"Identifying Exposure Contracts","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2561,"content":"First, all relevant smart contracts must be identified. Relevant smart contracts are those that are critical for the project being invested in, including core business logic, vaults, token contracts, and proxy implementations.","contentHash":"13c200ae9dd745539c86f2e29c9938b8114b99743cb974370fa88636cdd53710","addressRefs":[]},"fa41a412-b81d-4eba-93a9-95fec2a842c5":{"id":"fa41a412-b81d-4eba-93a9-95fec2a842c5","doc_no":"A.3.2.2.1.2.1.1.1","title":"Reliance On External Sources","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2562,"content":"External sources such as third party data providers, security consultants, and project documentation may be used to help identify relevant smart contracts. However, the Prime Agent deploying funds from the Collateral Portfolio into the opportunity retains overall responsibility for the reasonableness of identifying the relevant smart contracts.","contentHash":"71b3fd1488809f258a1d69b67b4ca0fc6d92632bd6f1b4d7afc78ebfd5b3bad4","addressRefs":[]},"b4e430a3-e848-4ef1-9b3a-6da724060674":{"id":"b4e430a3-e848-4ef1-9b3a-6da724060674","doc_no":"A.3.2.2.1.2.1.2","title":"Locating Verified Code","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2563,"content":"Second, the source code for each relevant contract must be obtained. The source code should be obtained for the deployed version of the contract using an appropriate block explorer (e.g. Etherscan for Ethereum Mainnet or L2s). The source code should include any dependencies or inherited library contracts that are part of the live system.","contentHash":"a6b0eb983a4623862a43de6c7fe2bb7b490b7d06b42e08464db6a7b5b57f577c","addressRefs":[]},"00fd9362-f606-49bc-a425-9c96008be238":{"id":"00fd9362-f606-49bc-a425-9c96008be238","doc_no":"A.3.2.2.1.2.2","title":"Smart Contract Risk Rating Calculation","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2564,"content":"The second step in calculating the Instance Smart Contract RRC with respect to an Allocation System opportunity is to calculate the Smart Contract Risk Rating $SCRR$ for the covered smart contracts identified in [A.3.2.2.1.2.1 - Defining Relevant Smart Contracts](162cfc93-77bd-4878-a8be-370d8862d792). The $SCRR$ is calculated as follows:\n\n$$\n\\text{SCRR} = min[\\text{CAP}, (\\text{SR} + \\text{CCR}) \\times \\text{LAF} \\times {AF}]\n$$\n\nHere $min$ is the mathematical minimum function that returns the lesser of the specified parameters.\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"bb9e5f6de27b1a12bbc4b8a0e0d317f4004c1d4d2b959ad9c5ba816f7a1db52c","addressRefs":[]},"b824c6ec-940b-4921-89f0-aca89b54e86a":{"id":"b824c6ec-940b-4921-89f0-aca89b54e86a","doc_no":"A.3.2.2.1.2.2.1","title":"Smart Contract Risk Rating Cap","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2565,"content":"The Smart Contract Risk Rating Cap $\\text{CAP}$ is a temporary cap on the Smart Contract Risk Rating. The value of the $CAP$ is `30`.","contentHash":"282491b3a28567ae1f60b9e36bdbbbea2357855b8013efb9f8dce4c696c7a107","addressRefs":[]},"51fc7445-8602-451d-87af-64f35abd7833":{"id":"51fc7445-8602-451d-87af-64f35abd7833","doc_no":"A.3.2.2.1.2.2.2","title":"Starting Rate","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2566,"content":"The Starting Rate $SR$ is an arbitrary starting risk rating for protocols. The value of the $SR$ is `25`.","contentHash":"d61ade702abe78d0dd43f574bcb3a0189831989e7793c1e44900407630031922","addressRefs":[]},"295e4d3b-8c8a-4f74-879f-88060bb07803":{"id":"295e4d3b-8c8a-4f74-879f-88060bb07803","doc_no":"A.3.2.2.1.2.2.3","title":"Code Complexity Rating","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2567,"content":"The Code Complexity Rate $CCR$ is a measure of the complexity of the code of the smart contracts used by the protocol. The $CCR$ is calculated as follows:\n\n$$\nCCR = \\text{CCRMax} \\times min(1, \\frac{\\text{RawCCR} + 1}{\\text{CCRUpperBound} + 1})\n$$\n\nHere the $min$ function is the mathematical minimum function that returns the lesser of the specified parameters.\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"0d0c2996f384fb7ec79243a9796bc1de0b5b3e331b66d4a4e13e35a3bb14719f","addressRefs":[]},"d41b80e2-97fc-4227-bcda-51f4d5fac7a6":{"id":"d41b80e2-97fc-4227-bcda-51f4d5fac7a6","doc_no":"A.3.2.2.1.2.2.3.1","title":"Code Complexity Rating Maximum","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2568,"content":"The Code Complexity Rating Maximum $\\text{CCRMax}$ is the maximum Code Complexity Rating for a protocol. The $\\text{CCRMax}$ is set to `75`.","contentHash":"f7a7e818894d88d3f2d38a66c6b0d05d30b9d78dd54f64c15917821465ded2cf","addressRefs":[]},"1632947d-b197-4478-9122-0c0e1acc8c7a":{"id":"1632947d-b197-4478-9122-0c0e1acc8c7a","doc_no":"A.3.2.2.1.2.2.3.2","title":"Code Complexity Rating Upper Bound","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2569,"content":"The Code Complexity Rating Upper Bound $\\text{CCRUpperBound}$ is an arbitrary factor to normalize the Raw Code Complexity Rating. The $\\text{CCRUpperBound}$ is set to `8,500`.","contentHash":"d28559427f0e1f11735dd0db9787934da3e8dfb2ea56669aa721812ddf41b8fb","addressRefs":[]},"ce3f2e96-b643-4de7-bfb9-cb0aee678635":{"id":"ce3f2e96-b643-4de7-bfb9-cb0aee678635","doc_no":"A.3.2.2.1.2.2.3.3","title":"Raw Code Complexity Rating","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2570,"content":"The Raw Code Complexity Rating $\\text{RawCCR}$ is an unnormalized measure of the complexity of the code of the smart contracts that implement the protocol. The $\\text{RawCCR}$ is calculated as follows:\n\n$$\n\\text{RawCCR}=(\\text{TCC} \\times \\text{CCweight}) + (\\text{TDP} \\times \\text{DPweight}) + (\\text{TEC} \\times \\text{ECweight}) + (\\text{ID} \\times \\text{IDweight}) + (\\frac{\\text{CS}}{\\text{CSfactor}} \\times \\text{CSweight})\n$$\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"63b31bb7746b5fe5accbc20ce856f4837a18a29f879208c33caeab4b94d1c60f","addressRefs":[]},"935d13f6-c66c-4020-85e3-831525776629":{"id":"935d13f6-c66c-4020-85e3-831525776629","doc_no":"A.3.2.2.1.2.2.3.3.1","title":"Total Cyclomatic Complexity","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2571,"content":"Cyclomatic complexity measures the number of independent execution paths through a unit of code. The total cyclomatic complexity score is the sum of the cyclomatic complexity of each of the covered smart contracts.","contentHash":"5a5dcb9c9d3769380e17604c092b2177436e49e4b462541bb8452da03b319ffc","addressRefs":[]},"9bd7b778-eeb2-4704-81cf-1135240924a0":{"id":"9bd7b778-eeb2-4704-81cf-1135240924a0","doc_no":"A.3.2.2.1.2.2.3.3.2","title":"Cyclomatic Complexity Weight","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2572,"content":"The Cyclomatic Complexity Weight $\\text{CCweight}$ is a weighting factor indicating the relative importance of the Total Cyclomatic Complexity versus other factors. It is set to `1`.","contentHash":"cf7cbd5c2e9e1e7bd4f610812964852ef6356f05c7562b3ac8513e193de684b2","addressRefs":[]},"e62098b2-f2ef-4604-9041-c7e0c8356ed3":{"id":"e62098b2-f2ef-4604-9041-c7e0c8356ed3","doc_no":"A.3.2.2.1.2.2.3.3.3","title":"Total Decision Points","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2573,"content":"Decision points measure the number of branching points where conditional logic is applied. The Total Decision Points are the total number of Decision Points in all functions in the covered smart contracts.","contentHash":"6f5c5d0e81729c4ef3734960018cfb4e02ca054f0ad349148eec8d87d9dc1dad","addressRefs":[]},"3c4d6fc5-2c37-4094-9a06-681fded786bc":{"id":"3c4d6fc5-2c37-4094-9a06-681fded786bc","doc_no":"A.3.2.2.1.2.2.3.3.4","title":"Decision Points Weight","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2574,"content":"The Decision Points Weight $\\text{DPweight}$ is a weighting factor indicating the relative importance of the Total Decision Points versus other factors. It is set to `0.5`.","contentHash":"73d2409b6c9af71387e10282546f077e5d5f10589d0b9ccb30f02533bd400a4f","addressRefs":[]},"028431ff-5b02-4f42-9224-6b53ff8756c8":{"id":"028431ff-5b02-4f42-9224-6b53ff8756c8","doc_no":"A.3.2.2.1.2.2.3.3.5","title":"Total External Calls","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2575,"content":"Total External Calls is the count of all external calls (e.g. `call`, `delegatecall`) made in the covered smart contracts.","contentHash":"4360bd66d39db4ba68407b0b640526e0fcabdbafba6f805cf42e14037341db4e","addressRefs":[]},"3088abe3-4206-431a-9408-9672cc45d61a":{"id":"3088abe3-4206-431a-9408-9672cc45d61a","doc_no":"A.3.2.2.1.2.2.3.3.6","title":"External Calls Weight","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2576,"content":"The External Calls Weight $\\text{ECweight}$ is a weighting factor indicating the relative importance of the Total External Calls versus other factors. It is set to `1.5`.","contentHash":"ac194be7ab692279fdd7ee849174418cef62bc3ce1f660e0e23fb157f8f3b828","addressRefs":[]},"bc711432-efd9-4724-8244-d9469fcd193e":{"id":"bc711432-efd9-4724-8244-d9469fcd193e","doc_no":"A.3.2.2.1.2.2.3.3.7","title":"Inheritance Depth","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2577,"content":"Inheritance Depth is the maximum number of inheritance levels in any contract in the covered contracts.","contentHash":"6c75b3253d8a34d9a34a173a8c4bbc3f037eeee5944c3355ddc53c168cf19659","addressRefs":[]},"b519469f-3f2b-40dc-96b5-69f5e81d9fe6":{"id":"b519469f-3f2b-40dc-96b5-69f5e81d9fe6","doc_no":"A.3.2.2.1.2.2.3.3.8","title":"Inheritance Depth Weight","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2578,"content":"The Inheritance Depth Weight $\\text{IDweight}$ is a weighting factor indicating the relative importance of the Inheritance Depth versus other factors. It is set to `5`.","contentHash":"912061f2b225644fd866ce7fadd11636dca15b4d741febd2dae0165325a8b654","addressRefs":[]},"32c32e11-baf0-4bce-a865-5de19a3e5d09":{"id":"32c32e11-baf0-4bce-a865-5de19a3e5d09","doc_no":"A.3.2.2.1.2.2.3.3.9","title":"Code Size","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2579,"content":"Code Size is the total number of lines of code in the covered contracts, excluding tests and documentation.","contentHash":"6f0cb0602d066daaeb02e678404789941b822d2356ce05af016e38f41389da2b","addressRefs":[]},"a30c8bc7-2686-46ac-952e-9c1f71c96aa0":{"id":"a30c8bc7-2686-46ac-952e-9c1f71c96aa0","doc_no":"A.3.2.2.1.2.2.3.3.10","title":"Code Size Factor","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2580,"content":"The Code Size Factory is an arbitrary factor to normalize the Code Size relative to other parameters. It is set to `1,000`.","contentHash":"d058c3e05b85030130ee3aaf0b01588d5a2c7395687ff711dfa339f044359009","addressRefs":[]},"21656714-b6f6-4ba5-b99a-ea3ac6f2ff89":{"id":"21656714-b6f6-4ba5-b99a-ea3ac6f2ff89","doc_no":"A.3.2.2.1.2.2.3.3.11","title":"Code Size Weight","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2581,"content":"The Code Size Weight $\\text{CSweight}$ is a weighting factor indicating the relative importance of the Code Size versus other factors. It is set to `1`.","contentHash":"e08dfcdbc488a02fd20f25dd6233f307286ba7e6f1893f592b1e1e789fee39be","addressRefs":[]},"227eff62-f2aa-4e49-91ad-1321261ed299":{"id":"227eff62-f2aa-4e49-91ad-1321261ed299","doc_no":"A.3.2.2.1.2.2.4","title":"Lindy Adjustment Factor","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2582,"content":"The Lindy Adjustment Factor $\\text{LAF}$ is a measure of the \"Lindiness\" of the smart contracts and is based on the idea that vulnerable smart contracts with large TVL for a significant period of time would have already been hacked. Therefore, protocols with a greater time integrated TVL are safer, all other things equal, than protocols with a lower time integrated TVL. The $\\text{LAF}$ is calculated as follows:\n\n$$\n\\text{LAF} = max(0, 1 - \\frac{ln(1 + \\lambda \\times \\text{AGEeff})}{ln(1 + \\lambda \\times \\text{max})})\n$$\n\nHere $max$ is the mathematical maximum function that returns the greater of the specified parameters and $ln$ is the natural logarithm.\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"90d3cd65ea03f25c461859e79ac47e9039a71706adfd72c5f197e3199d77bb07","addressRefs":[]},"7f109cc0-ee8d-48b6-8fbf-6e363004edfb":{"id":"7f109cc0-ee8d-48b6-8fbf-6e363004edfb","doc_no":"A.3.2.2.1.2.2.4.1","title":"Decay Factor","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2583,"content":"The Decay Factor $lambda$ is a tuning parameter that represents an estimate of how quickly the risk of a set of smart contracts decreases as its effective age increases. The value of $lambda$ is set to `0.1`.","contentHash":"eb2fba3f760fc8efe6b6c73549424bb66b217f8168637d310c832f9e50972a3a","addressRefs":[]},"891eab12-0c47-4b87-b867-3cba6ca7db4e":{"id":"891eab12-0c47-4b87-b867-3cba6ca7db4e","doc_no":"A.3.2.2.1.2.2.4.2","title":"Maximum Age","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2584,"content":"The Maximum Age $\\text{max}$ is the effective age, in months, at which the risk of a set of smart contracts has decayed to zero. The value of $\\text{max}$ is set to `60`.","contentHash":"64a4f12d9a8607fcc4b2a70ed337de769ff04bd357e581f84a8bab97065ab6e0","addressRefs":[]},"a8db99b2-f072-4132-9ee2-c8ebcc2b3609":{"id":"a8db99b2-f072-4132-9ee2-c8ebcc2b3609","doc_no":"A.3.2.2.1.2.2.4.3","title":"Effective Age","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2585,"content":"The Effective Age $\\text{AGEeff}$ is the age of the contracts adjusted for the TVL of the contracts. The $\\text{AGEeff}$ is calculated as follows:\n\n$$\n\\text{AGEeff}=\\text{CA} \\times ln(1 + \\frac{\\text{gmTVL}}{\\text{TVLthreshold}})\n$$\n\nHere $ln$ is the natural logarithm.\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"6c9c71dcfe3a1d55539c18e089e9f3cb6425763177b048a24606798bec29a33a","addressRefs":[]},"8ee9538a-0655-4600-8436-1cc610bcdb1b":{"id":"8ee9538a-0655-4600-8436-1cc610bcdb1b","doc_no":"A.3.2.2.1.2.2.4.3.1","title":"Contract Age","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2586,"content":"The contract age $\\text{CA}$ is the average age, in months, of each of the relevant contracts. The age of each relevant contract should be measured based on the time elapsed between the date the contract was deployed and the date of calculation.","contentHash":"a7d529d9e6b1de42295cc8555753378fc444592f5c2528876de8683187e33b72","addressRefs":[]},"bec61312-6a70-4881-8a52-4a7fa75dbf07":{"id":"bec61312-6a70-4881-8a52-4a7fa75dbf07","doc_no":"A.3.2.2.1.2.2.4.3.2","title":"Geometric Mean Total Value Locked","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2587,"content":"The Geometric Mean Total Value Locked $\\text{gmTVL}$ is the geometric mean of the daily TVL over the contract age.","contentHash":"8d43d65f7a3d385166d9de8de6db462e306f6019aa31b9826cfc35b8f3b16e6e","addressRefs":[]},"c7939b23-39e1-4299-9beb-700857b8f90e":{"id":"c7939b23-39e1-4299-9beb-700857b8f90e","doc_no":"A.3.2.2.1.2.2.4.3.3","title":"Total Value Locked Threshold","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2588,"content":"The Total Value Locked Threshold $\\text{TVLthreshold}$ is a factor used to normalize the Geometric mean Total Value Locked. The $\\text{TVLthreshold}$ is set to `100,000,000`.","contentHash":"9d10920db64e0acff9e6e2a33abf80106fc96814508dbced8fbad0c47eebbfd5","addressRefs":[]},"0016d78c-66e7-447f-9691-eaff8ea68d6d":{"id":"0016d78c-66e7-447f-9691-eaff8ea68d6d","doc_no":"A.3.2.2.1.2.2.5","title":"Audit Factor","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2589,"content":"The Audit Factor $AF$ is a measure of the extent to which the Base Risk is reduced by audits. The $AF$ is calculated as:\n\n$$\nAF = \\Pi{[1 - \\text{effAuditValue} \\times \\text{decayFactor}]}\n$$\n\nThe audit from each audit firm with the highest product of Effective Audit Value and Delay factor should be included in this calculation.\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"67e7b96f6271eb99d3092fec0592f039698335cc4fb609e014c3e0f37f4b2b0c","addressRefs":[]},"ade75eba-ac08-465c-a8a1-4ccaf5b99109":{"id":"ade75eba-ac08-465c-a8a1-4ccaf5b99109","doc_no":"A.3.2.2.1.2.2.5.1","title":"Effective Audit Value","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2590,"content":"The Effective Audit Value $\\text{effAuditValue}$ measures the effectiveness of a single audit in reducing the risk of a set of smart contracts and is a function of the percent of the code covered by the audit and the reputation of the audit firm. The $\\text{effAuditValue}$ is calculated as:\n\n$$\n\\text{effAuditValue} = \\text{effectivenessCoefficient} \\times \\text{coverage}\n$$\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"28db52060313fb097b66ed67b2e15c6b76ed3cafba819dab3e08da68d912f8dc","addressRefs":[]},"096c574f-7194-4b4d-aa5b-e5da7c6c87f2":{"id":"096c574f-7194-4b4d-aa5b-e5da7c6c87f2","doc_no":"A.3.2.2.1.2.2.5.1.1","title":"Coverage","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2591,"content":"The Coverage $\\text{coverage}$ is a measure of the percent of a set of smart contracts that were covered in the scope of an audit. The $\\text{coverage}$ is calculated as:\n\n$$\n\\text{coverage} = \\frac{\\text{LinesOfCodeCovered}}{\\text{TotalLinesOfCode}}\n$$\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"70955c4b96a87582f16a3367d89c345ee2cb64135cdfb30b8eb41a59d12c82b4","addressRefs":[]},"428022f5-039e-418b-831d-7f816afb2cf3":{"id":"428022f5-039e-418b-831d-7f816afb2cf3","doc_no":"A.3.2.2.1.2.2.5.1.1.1","title":"Lines Of Code Covered","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2592,"content":"The Lines Of Code Covered $\\text{LinesOfCodeCovered}$ is the number of lines of code of the relevant contracts that were within the scope of the audit, excluding documentation and tests.","contentHash":"275814c0e62be9a5f79c18583900f878386674a8f271cf1ad68e9e68420c0d3f","addressRefs":[]},"baaf78d3-7182-459e-83a0-6494eb43f048":{"id":"baaf78d3-7182-459e-83a0-6494eb43f048","doc_no":"A.3.2.2.1.2.2.5.1.1.2","title":"Total Lines Of Code","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2593,"content":"The Total Lines Of Code $\\text{TotalLinesOfCode}$ is the total number of lines of code of the relevant contracts, excluding documentation and tests.","contentHash":"8a62f82c369e964b931a2fad2cfa3c8145b8acf7ba0f91866b150d14612c7485","addressRefs":[]},"d281c572-ff98-43ba-a01d-e54657b50ab9":{"id":"d281c572-ff98-43ba-a01d-e54657b50ab9","doc_no":"A.3.2.2.1.2.2.5.1.2","title":"Effectiveness Coefficient","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2594,"content":"The Effectiveness Coefficient $\\text{effectivenessCoefficient}$ is a measure of the effectiveness of the particular audit firm and is estimated based on the tier of the audit firm.","contentHash":"1b0eff643066a36eac563f5f97d60c31bd9eb249008ce6f92ff63ea8e4db8fb2","addressRefs":[]},"97eee131-b5d6-4246-8631-fb077616b671":{"id":"97eee131-b5d6-4246-8631-fb077616b671","doc_no":"A.3.2.2.1.2.2.5.1.2.1","title":"Audit Firm Tiers","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2595,"content":"Audit firms are divided into two tiers: top-tier and mid-tier.","contentHash":"09adaf1f1075209e7fc269c62c337a40dd2ce4534abfb8e4465b2c14616861e1","addressRefs":[]},"b4a13cfc-1fef-47da-a350-6e81346203f4":{"id":"b4a13cfc-1fef-47da-a350-6e81346203f4","doc_no":"A.3.2.2.1.2.2.5.1.2.1.1","title":"Top-Tier Effectiveness Coefficient","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2596,"content":"The Effectiveness Coefficient of a top-tier audit firm is set to `0.8`.","contentHash":"17d742c83f34192f1e6c93f067e8870a3c11a5dde8e13a2d8f8c9638d0d233ce","addressRefs":[]},"18e07645-44c3-4175-8941-d7010233288a":{"id":"18e07645-44c3-4175-8941-d7010233288a","doc_no":"A.3.2.2.1.2.2.5.1.2.1.2","title":"Mid-Tier Effectiveness Coefficient","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2597,"content":"The Effectiveness Coefficient of a mid-tier audit firm is set to `0.5`.","contentHash":"fe94ce55f4764d2e227ae61f7f5e3169c7e58ef4fc158a6cdef097dd81a0842c","addressRefs":[]},"5b542b65-2ef1-49e9-8995-122373f1b312":{"id":"5b542b65-2ef1-49e9-8995-122373f1b312","doc_no":"A.3.2.2.1.2.2.5.1.2.2","title":"Audit Firms By Tier","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2598,"content":"The subdocuments herein categorize specific audit firms into the top-tier and mid-tier categories. Audits from firms other than the ones specified herein may not be included in the calculation of the Audit Adjustment Factor.\n\nThe Protocol Security Workstream Lead must review this categorization on a regular basis and update it as necessary.","contentHash":"c1ce0c96b4ca46f4cef5be677683a5ded76f2f8f41d16d1e5ef74ad08d86991f","addressRefs":[]},"6ada67c6-0cf1-4456-b280-57e8ae7edc13":{"id":"6ada67c6-0cf1-4456-b280-57e8ae7edc13","doc_no":"A.3.2.2.1.2.2.5.1.2.2.1","title":"List Of Top-Tier Audit Firms","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2599,"content":"The top-tier audit firms are:\n\n- ChainSecurity\n- OpenZeppelin\n- ConsenSys Diligence\n- Trail Of Bits","contentHash":"48fd024c011899afab6bbed0562f85981cfb591b17fd0174e29dfd639ccc47c5","addressRefs":[]},"dea3a182-4b89-4fda-9eed-232562e5f057":{"id":"dea3a182-4b89-4fda-9eed-232562e5f057","doc_no":"A.3.2.2.1.2.2.5.1.2.2.2","title":"List Of Mid-Tier Audit Firms","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2600,"content":"The mid-tier audit firms are:\n\n- Quantstamp\n- SlowMist\n- PeckShield\n- Halborn\n- Certora\n- Hunter Security\n- Omniscia\n- Spearbit\n- Electisec\n- MixBytes\n- Cyfrin\n- SECBIT Labs\n- Bramah Systems\n- Zokyo\n- Guardian Audits\n- Zellic\n- Code4rena\n- Pashov\n- ABDK\n- Decurity\n- OtterSec\n- WatchPug\n- Sigma Prime\n- Cantina\n- Oxorio\n- Enigma Dark\n- Runtime Verification\n- Pessimistic\n- Solidified\n- StErMi\n- Sherlock\n- 0xMacro","contentHash":"6dca658031242e422bae9f9cf326512fcb9d9512e14e18409946a53dba8736d2","addressRefs":[]},"7ccfae3d-59ae-433e-adba-7822ae335755":{"id":"7ccfae3d-59ae-433e-adba-7822ae335755","doc_no":"A.3.2.2.1.2.2.5.2","title":"Decay Factor","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2601,"content":"The Decay Factor $decayFactor$ is a parameter indicating how rapidly the effectiveness of audits in reducing risk decreases over time. The $decayFactor$ is calculated as follows:\n\n$$\ndecayFactor =\\begin{cases}1 & \\text{if } auditAge \\leq 2 \\\\\\frac{10 - auditAge}{8} & \\text{if } 2 < auditAge < 10 \\\\0 & \\text{if } auditAge \\geq 10\\end{cases}\n$$\n\nThe parameter of this formula is specified in the subdocument herein.","contentHash":"6be2337f5d4a13d8a5759b15cb883bcc055b52de32f0332bdb74b9913e5c5436","addressRefs":[]},"792084a1-d844-4774-b909-0cf0bc40df7c":{"id":"792084a1-d844-4774-b909-0cf0bc40df7c","doc_no":"A.3.2.2.1.2.2.5.2.1","title":"Audit Age","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2602,"content":"The Audit Age $auditAge$ is the age, in years, of the audit. The age of the audit should be measured based on the time elapsed between the date the audit report was issued and the date of calculation.","contentHash":"d77c214a634a194a0a66ac5aa807c7e6f4538aa6fac2b025c859003fdd6775ae","addressRefs":[]},"b2c8867b-0da0-4765-a927-9a530a0ccf24":{"id":"b2c8867b-0da0-4765-a927-9a530a0ccf24","doc_no":"A.3.2.2.1.2.3","title":"Smart Contract Risk Required Risk Capital Calculation","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2603,"content":"The third step in calculating the Instance Smart Contract RRC with respect to an Allocation System opportunity is to calculate the Instance Smart Contract RRC as a function of the Smart Contract Risk Rating.","contentHash":"d08639d0f2f282240924a60115f9bf5a89ad848e77268f75829b0b95d26d923b","addressRefs":[]},"01f9d3be-2e3e-4bd0-9f34-1000165405c5":{"id":"01f9d3be-2e3e-4bd0-9f34-1000165405c5","doc_no":"A.3.2.2.1.2.3.1","title":"Calculation Of Instance Smart Contract CRR Based on Risk Category","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2604,"content":"The methodology used to calculate the Instance Smart Contract CRR as a percentage of the exposure depends on the Risk Rating $r$ of the protocol as specified in the documents herein.","contentHash":"740df773aeac7e5f95a45f8aeb0259de0a7508299c9425f1b24438bb90b9c34e","addressRefs":[]},"80701bc2-5b75-4205-841e-7799c2be2c33":{"id":"80701bc2-5b75-4205-841e-7799c2be2c33","doc_no":"A.3.2.2.1.2.3.1.1","title":"Low Risk Protocols","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2605,"content":"Low risk protocols are ones with a Risk Rating between less than or equal to `25`. The methodology for low risk protocols is specified in the documents herein.","contentHash":"ee085d3be7c61f377d43216daf3cecef3fde395a455199cc7b1e5715ec693da1","addressRefs":[]},"4f841792-cffb-4817-939a-454ce4f262f0":{"id":"4f841792-cffb-4817-939a-454ce4f262f0","doc_no":"A.3.2.2.1.2.3.1.1.1","title":"Calculate F1 Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2606,"content":"For low risk protocols, the F1 parameter $f_{1}$ should first be calculated using the methodology specified in [A.3.2.2.1.2.3.3.2.2 - F1 Function](443bcf99-b015-44d3-99c9-42fd611710fe).","contentHash":"22dcc5c1b122911a220cc6fc5605b7ec0a3c710eba7dab04cc4e8994104729ab","addressRefs":[]},"e7be59bb-a72c-4ca8-afeb-da78f1afd44e":{"id":"e7be59bb-a72c-4ca8-afeb-da78f1afd44e","doc_no":"A.3.2.2.1.2.3.1.1.2","title":"Calculate Capital Requirement Ratio Using Piecewise Function With F1 Thresholds","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2607,"content":"The Capital Requirement Ratio should then be calculated by inputting the F1 parameter calculated in [A.3.2.2.1.2.3.1.1.1 - Calculate F1 Parameter](4f841792-cffb-4817-939a-454ce4f262f0) into the Piecewise Function specified in [A.3.2.2.1.2.3.3.1 - Piecewise Function](7441253c-0030-4b8e-ac91-65046761aab6) using the F1 thresholds specified in [A.3.2.2.1.2.3.3.1.5.3 - Kink Threshold](c28b47a8-951b-4ca4-8501-bbd6d2279b74).","contentHash":"83a9036d76136f7347db7d89b4aa99a98d780eeda9216530ee63f924d9b4e8bb","addressRefs":[]},"8500fc58-7cd8-4573-b64d-bf7bd445745e":{"id":"8500fc58-7cd8-4573-b64d-bf7bd445745e","doc_no":"A.3.2.2.1.2.3.1.2","title":"Medium Risk Protocols","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2608,"content":"Medium risk protocols are ones with a Risk Rating greater than `25` but less than or equal to `50`. The methodology for medium risk protocols is specified in the documents herein.","contentHash":"c29d6f62e16bb7a070f48ec955cb3fe9bc975dbf77de35c46bb18de254e0b115","addressRefs":[]},"fb47383f-e7f9-412b-893d-86e4c7b83def":{"id":"fb47383f-e7f9-412b-893d-86e4c7b83def","doc_no":"A.3.2.2.1.2.3.1.2.1","title":"Calculate F1 Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2609,"content":"For medium risk protocols, the F1 parameter $f_{1}$ should first be calculated using the methodology specified in [A.3.2.2.1.2.3.3.2.2 - F1 Function](443bcf99-b015-44d3-99c9-42fd611710fe).","contentHash":"c20fd1418d646c8d0fc12b74f4b9e14d41ff5caf69d79e1d08344c232a12aaeb","addressRefs":[]},"3f2622e3-dce6-44ef-9bc5-2853413abbe8":{"id":"3f2622e3-dce6-44ef-9bc5-2853413abbe8","doc_no":"A.3.2.2.1.2.3.1.2.2","title":"Calculate F2 Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2610,"content":"The F2 parameter $f_{2}$ should then be calculated using the methodology specified in [A.3.2.2.1.2.3.3.2.3 - F2 Function](3286915a-7d81-4eb4-a238-bc7ded8e2634).","contentHash":"4cb77084c983a578f3d5b2e206050a51b4b0b41c16d987cff212ecd3c991e2c3","addressRefs":[]},"15290d29-ea87-4d07-a25e-84a6c34c6c87":{"id":"15290d29-ea87-4d07-a25e-84a6c34c6c87","doc_no":"A.3.2.2.1.2.3.1.2.3","title":"Calculate Capital Requirement Ratio Using F1 Piecewise Function","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2611,"content":"The Capital Requirement Ratio using the F1 Piecewise Function should then be calculated by inputting the F1 parameter calculated in [A.3.2.2.1.2.3.1.2.1 - Calculate F1 Parameter](fb47383f-e7f9-412b-893d-86e4c7b83def) into the Piecewise Function specified in [A.3.2.2.1.2.3.3.1 - Piecewise Function](7441253c-0030-4b8e-ac91-65046761aab6) using the F1 thresholds specified in [A.3.2.2.1.2.3.3.1.5.3 - Kink Threshold](c28b47a8-951b-4ca4-8501-bbd6d2279b74).","contentHash":"37a047872b41a23b75fd2a678be0eaddcd8ab876f62986e97aba8a2c1ae72095","addressRefs":[]},"ac7e97eb-a780-4986-8f4d-0f9c5a0831a4":{"id":"ac7e97eb-a780-4986-8f4d-0f9c5a0831a4","doc_no":"A.3.2.2.1.2.3.1.2.4","title":"Calculate Capital Requirement Ratio Using F2 Piecewise Function","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2612,"content":"The Capital Requirement Ratio using the F2 Piecewise Function should then be calculated by inputting the F2 parameter calculated in [A.3.2.2.1.2.3.1.2.2 - Calculate F2 Parameter](3f2622e3-dce6-44ef-9bc5-2853413abbe8) into the Piecewise Function specified in [A.3.2.2.1.2.3.3.1 - Piecewise Function](7441253c-0030-4b8e-ac91-65046761aab6) using the F2 thresholds specified in [A.3.2.2.1.2.3.3.1.5.2 - Maximum Threshold](df77d6b1-b08a-45c9-8fc2-74268918b0b0).","contentHash":"655a933fc80720258ab95186096c5d88c7a0aa894d3a7843c2377cf1cdba26e6","addressRefs":[]},"95ee7840-66b0-4db9-80f7-c1f641bf0f17":{"id":"95ee7840-66b0-4db9-80f7-c1f641bf0f17","doc_no":"A.3.2.2.1.2.3.1.2.5","title":"Calculate Blended Average Required Capital Percentage","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2613,"content":"The final Required Capital Percentage $x$ should be calculated as a weighted average of the F1 Required Capital Percentage and the F2 Required Capital Percentage as follows:\n\n$$\nx = b \\times \\alpha \\times f_2 + (1 - \\alpha) \\times f_1\n$$\n\nThe parameters of this formula are defined in the subdocuments herein.","contentHash":"a4fe5207dea5591bd076f6a3d59ac73dd05e554651fd1677f5b21b35a37b590b","addressRefs":[]},"303c0d7f-42a7-4b9e-8afd-26e4d54e2f56":{"id":"303c0d7f-42a7-4b9e-8afd-26e4d54e2f56","doc_no":"A.3.2.2.1.2.3.1.2.5.1","title":"Constant Factor","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2614,"content":"The constant factor $b$ is set to `0.15`.","contentHash":"417e97f6852eb1453ae5a1cadac8f157aee63127486a9d27a63868a92dc64728","addressRefs":[]},"b753da3d-ce30-4a66-8da6-16f563cee120":{"id":"b753da3d-ce30-4a66-8da6-16f563cee120","doc_no":"A.3.2.2.1.2.3.1.2.5.2","title":"Alpha","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2615,"content":"Alpha $\\alpha$ is a weighting factor indicating how close the Risk Rating is to the threshold for a High Risk Protocol versus the threshold for a Low Risk Protocol. It is calculated as:\n\n$$\n\\alpha = \\dfrac{r - 25}{50 - 25}\n$$\n\nHere $r$ is the Risk Rating of the protocol.","contentHash":"89fab626034ae35951620c87acd0f7382117af7de33a0d4b34dba5811bcbb355","addressRefs":[]},"04abc79f-ad0f-49d9-91d4-1a94271e1979":{"id":"04abc79f-ad0f-49d9-91d4-1a94271e1979","doc_no":"A.3.2.2.1.2.3.1.2.5.3","title":"F1 Capital Requirement Ratio","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2616,"content":"The F1 Capital Requirement Ratio $f_1$ is the figure calculated as the output of [A.3.2.2.1.2.3.1.2.3 - Calculate Capital Requirement Ratio Using F1 Piecewise Function](15290d29-ea87-4d07-a25e-84a6c34c6c87).","contentHash":"3be4457faf09ade285db09600572759e335062e815c2ef667f1c2f6454990c74","addressRefs":[]},"44f6339f-988c-494b-9f0f-37460d11ac56":{"id":"44f6339f-988c-494b-9f0f-37460d11ac56","doc_no":"A.3.2.2.1.2.3.1.2.5.4","title":"F2 Capital Requirement Ratio","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2617,"content":"The F2 Capital Requirement Ratio $f_2$ is the figure calculated as the output of [A.3.2.2.1.2.3.1.2.4 - Calculate Capital Requirement Ratio Using F2 Piecewise Function](ac7e97eb-a780-4986-8f4d-0f9c5a0831a4).","contentHash":"5008329f83c1796c8bac1b569fe8d871720dc46343b57a033155352a7b7acdc7","addressRefs":[]},"5dc03a3c-aac9-4a32-bcf6-16077d21e4fd":{"id":"5dc03a3c-aac9-4a32-bcf6-16077d21e4fd","doc_no":"A.3.2.2.1.2.3.1.3","title":"High Risk Protocols","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2618,"content":"High risk protocols are ones with a Risk Rating greater than `50` but less than or equal to `75`. The methodology for high risk protocols is specified in the documents herein.","contentHash":"ad3b59b1f53dac182187d791749e2ffb587a8852371f13927fe549ee36411e2b","addressRefs":[]},"234dea0c-e4db-49ea-8dff-30bd7652f6c2":{"id":"234dea0c-e4db-49ea-8dff-30bd7652f6c2","doc_no":"A.3.2.2.1.2.3.1.3.1","title":"Calculate F2 Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2619,"content":"For high risk protocols, the F2 parameter $f_{2}$ should first be calculated using the methodology specified in [A.3.2.2.1.2.3.3.2.3 - F2 Function](3286915a-7d81-4eb4-a238-bc7ded8e2634).","contentHash":"63b8c56ef7bbb95f751d8fda691695c2045e2979e06b7f42a56ed036a0f2586e","addressRefs":[]},"456c0a8f-348a-477b-8550-eea23e9fd4a5":{"id":"456c0a8f-348a-477b-8550-eea23e9fd4a5","doc_no":"A.3.2.2.1.2.3.1.3.2","title":"Calculate Capital Requirement Ratio Using Piecewise Function With F2 Thresholds","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2620,"content":"The Capital Requirement Ratio should then be calculated by inputting the F2 parameter calculated in [A.3.2.2.1.2.3.1.3.1 - Calculate F2 Parameter](234dea0c-e4db-49ea-8dff-30bd7652f6c2) into the Piecewise Function specified in [A.3.2.2.1.2.3.3.1 - Piecewise Function](7441253c-0030-4b8e-ac91-65046761aab6) using the F2 thresholds specified in [A.3.2.2.1.2.3.3.1.5.2 - Maximum Threshold](df77d6b1-b08a-45c9-8fc2-74268918b0b0).","contentHash":"897d8be81227ea6fdb7f3b4ad51d8610544e9df0531fc558a1bca8c0f0d5d5b3","addressRefs":[]},"8c73b3c0-04e2-491d-bd52-367c3590e992":{"id":"8c73b3c0-04e2-491d-bd52-367c3590e992","doc_no":"A.3.2.2.1.2.3.1.4","title":"Extreme Risk Protocols","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2621,"content":"Extreme risk protocols are ones with a Risk Rating greater than `75`. The methodology for extreme risk protocols is specified in the documents herein.","contentHash":"ca341e04d1d2e8c596d755998949ea5c4d337c27b38dad9ca79dc6f8cc4d8f07","addressRefs":[]},"a5a0fab2-d380-41eb-b7d0-ba534cefa0ae":{"id":"a5a0fab2-d380-41eb-b7d0-ba534cefa0ae","doc_no":"A.3.2.2.1.2.3.1.4.1","title":"Maximum Capital Requirement Ratio","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2622,"content":"For extreme risk protocols, the Capital Requirement Ratio is automatically set to 100%.","contentHash":"4ef950744e7058e39e5634a53947532ee465cf077687cdcb832fd879d1e7e15b","addressRefs":[]},"6905f51d-374e-4bf7-b43c-059073d2d68c":{"id":"6905f51d-374e-4bf7-b43c-059073d2d68c","doc_no":"A.3.2.2.1.2.3.2","title":"Calculation Of Instance Smart Contract CRR Value","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2623,"content":"The Instance Smart Contract CRR is equal to the product of (1) the Instance Smart Contract CRR calculated from [A.3.2.2.1.2.3.1 - Calculation Of Instance Smart Contract CRR Based on Risk Category](01f9d3be-2e3e-4bd0-9f34-1000165405c5) and (2) the exposure to the Allocation System opportunity.","contentHash":"e24d17eeb1f2c63265f7112266d50481156d75fd55869461afcc3ad83f2a8004","addressRefs":[]},"b634443b-ee03-4b53-a924-049fa971bfef":{"id":"b634443b-ee03-4b53-a924-049fa971bfef","doc_no":"A.3.2.2.1.2.3.3","title":"Inputs To Instance Smart Contract CRR Calculations","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2624,"content":"The documents herein define functions and parameters that are used in multiple parts of the methodology for calculating the Instance Smart Contract CRR based on the Smart Contract Risk Rating specified in [A.3.2.2.1.2.3.1 - Calculation Of Instance Smart Contract CRR Based on Risk Category](01f9d3be-2e3e-4bd0-9f34-1000165405c5).","contentHash":"d50196fe97784790af7d7f52c95dc28345103405ba90bb7d3f8d82b7d56ba5c5","addressRefs":[]},"7441253c-0030-4b8e-ac91-65046761aab6":{"id":"7441253c-0030-4b8e-ac91-65046761aab6","doc_no":"A.3.2.2.1.2.3.3.1","title":"Piecewise Function","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2625,"content":"The Piecewise Function $CRR(x)$ calculates a percentage risk capital requirement based on an input $x$ and is defined as follows:\n\n$$\n\\text{CRR}(x) =\\begin{cases}a & \\text{if } x \\le x_{\\text{start}}, \\\\[8pt]b \\times \\dfrac{x - x_{\\text{start}}}{x_{\\text{kink}} - x_{\\text{start}}} & \\text{if } x_{\\text{start}} < x \\le x_{\\text{kink}}, \\\\[8pt]b \\;+\\; c \\;\\dfrac{x - x_{\\text{kink}}}{x_{\\text{max}} - x_{\\text{kink}}}& \\text{if } x_{\\text{kink}} < x < x_{\\text{max}}, \\\\[8pt]d& \\text{if } x \\ge x_{\\text{max}}.\\end{cases}\n$$","contentHash":"07bb0ff49ad08476d88e8c4d92efea2b6e81bb2eac7810c71bcc30e2a72b17dc","addressRefs":[]},"d6fda10f-7eff-4703-a2b4-29bbcd2241e1":{"id":"d6fda10f-7eff-4703-a2b4-29bbcd2241e1","doc_no":"A.3.2.2.1.2.3.3.1.1","title":"Low Risk Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2626,"content":"The low risk parameter $a$ is the output of the piecewise function when the input is at or below the starting threshold. The $a$ parameter is set to `0`.","contentHash":"4f64d1cefbd3c4ff5f472652151484d75b774b4e490d149e415ff16423340b45","addressRefs":[]},"5efe5b7e-cd77-43ea-9499-549e0f46a5d1":{"id":"5efe5b7e-cd77-43ea-9499-549e0f46a5d1","doc_no":"A.3.2.2.1.2.3.3.1.2","title":"Medium Risk Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2627,"content":"The medium risk parameter $b$ is the output of the piecewise function when the input is equal to the kink threshold. The $b$ parameter is set to `0.25`.","contentHash":"e1aa1b06e80b12bf13b7da2121bfec4a5647b004d5c6b750fa9eb26c6a00fa3f","addressRefs":[]},"2262dbd9-d59b-490f-9ff6-b28057bbb6ce":{"id":"2262dbd9-d59b-490f-9ff6-b28057bbb6ce","doc_no":"A.3.2.2.1.2.3.3.1.3","title":"High Risk Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2628,"content":"The high risk parameter $c$ is the incremental value above the $b$ parameter that the piecewise function will output when the input is equal to the maximum threshold. The $c$ parameter is set to `0.75`.","contentHash":"0c1c52b0373373e868690d0feda87856dadade83b16e4dad991ea81f53d190a5","addressRefs":[]},"a2ed34be-4bb3-44ae-b92c-4bf4384abc8b":{"id":"a2ed34be-4bb3-44ae-b92c-4bf4384abc8b","doc_no":"A.3.2.2.1.2.3.3.1.4","title":"Extreme Risk Parameter","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2629,"content":"The extreme risk parameter $d$ is the output of the piecewise function when the input is equal to or greater than the maximum threshold. The $d$ parameter is set to `1`.","contentHash":"e80e094f5c2b82cddf277123367747c81d1ef7a79bacebf4c50f57d08b0ae2f0","addressRefs":[]},"0fc529dd-d4f7-43d3-a618-d41fd8a8c42f":{"id":"0fc529dd-d4f7-43d3-a618-d41fd8a8c42f","doc_no":"A.3.2.2.1.2.3.3.1.5","title":"Thresholds","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2630,"content":"The documents herein define the thresholds for the piecewise function.","contentHash":"c49cc1298d8e23b97410471a6ea4e0b6a1a68561942597b1f95671e7ca0f37ea","addressRefs":[]},"bbda61eb-828d-486a-8bba-df1f517ad0b5":{"id":"bbda61eb-828d-486a-8bba-df1f517ad0b5","doc_no":"A.3.2.2.1.2.3.3.1.5.1","title":"Starting Threshold","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2631,"content":"The Starting Threshold $x_{\\text{start}}$ is calculated as follows:\n\n$$\nx_{\\text{start}}(r) = i \\times (r_i - r)\n$$\n\nHere $r$ is the Risk Rating.\n\nThe parameters of this formula are defined in [A.3.2.2.1.2.3.3.1.5.4 - Threshold Parameters](654528b9-d7c8-4cee-9261-d5a745ea231e).","contentHash":"9297105b58730864b7d688ea17f6c5b69232744cbac0f5a0520c0990d4d387f5","addressRefs":[]},"df77d6b1-b08a-45c9-8fc2-74268918b0b0":{"id":"df77d6b1-b08a-45c9-8fc2-74268918b0b0","doc_no":"A.3.2.2.1.2.3.3.1.5.2","title":"Maximum Threshold","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2632,"content":"The Maximum Threshold $x_{\\text{max}}$ is calculated as follows:\n\n$$\nx_{\\text{max}}(r) = x_{\\text{start}}(r) + i_{max}\n$$\n\nHere $r$ is the Risk Rating.\n\nThe parameters of this formula are defined in [A.3.2.2.1.2.3.3.1.5.4 - Threshold Parameters](654528b9-d7c8-4cee-9261-d5a745ea231e).","contentHash":"e5322acbf22492a22cc082511713b92a20ba06ad173cb6aa113b9ee53f8a1eff","addressRefs":[]},"c28b47a8-951b-4ca4-8501-bbd6d2279b74":{"id":"c28b47a8-951b-4ca4-8501-bbd6d2279b74","doc_no":"A.3.2.2.1.2.3.3.1.5.3","title":"Kink Threshold","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2633,"content":"The Kink Threshold $x_{\\text{kink}}$ is calculated as follows:\n\n$$\nx_{\\text{kink}}(r) = x_{\\text{start}}(r) \\;+\\; i_{kink} \\times\\bigl[\\;x_{\\text{max}}(r)\\;-\\;x_{\\text{start}}(r)\\bigr]\n$$\n\nHere $r$ is the Risk Rating.\n\nThe parameters of this formula are defined in [A.3.2.2.1.2.3.3.1.5.4 - Threshold Parameters](654528b9-d7c8-4cee-9261-d5a745ea231e).","contentHash":"d98e90f73d4014e144db24eba29cbeced6bcb26b202bdbf47a7abdb3b4b7b459","addressRefs":[]},"654528b9-d7c8-4cee-9261-d5a745ea231e":{"id":"654528b9-d7c8-4cee-9261-d5a745ea231e","doc_no":"A.3.2.2.1.2.3.3.1.5.4","title":"Threshold Parameters","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2634,"content":"The documents herein define inputs that are used to calculate the Starting Threshold, Maximum Threshold, and Kink Threshold. These parameters differ depending on whether the piecewise function is invoked with F1 threshold parameters or F2 threshold parameters.","contentHash":"d939b951cbb87d11c27a9fbd870c540c8137ab996368098f37245a688e4d7f91","addressRefs":[]},"f022c0b5-e19d-4fff-aa14-c34c686a7629":{"id":"f022c0b5-e19d-4fff-aa14-c34c686a7629","doc_no":"A.3.2.2.1.2.3.3.1.5.4.1","title":"F1 Threshold Parameters","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2635,"content":"The documents herein define the F1 threshold parameters.","contentHash":"e876c3079cabbf1f93d03f83a0f723ba930371a960a3af76cf14cdcebf9d04cd","addressRefs":[]},"c2c18ff3-1186-4dd9-84b4-ace189d6cda4":{"id":"c2c18ff3-1186-4dd9-84b4-ace189d6cda4","doc_no":"A.3.2.2.1.2.3.3.1.5.4.1.1","title":"Rating Point Scaling Coefficient","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2636,"content":"The value of the Rating Point Scaling Coefficient $i$ is `0.01`.","contentHash":"77e7e0182f0f7a06532df11c7223a1564d719f3a33406fe54b98ae5a008874aa","addressRefs":[]},"26fc2a85-86c4-4b75-b561-357d1fcc6115":{"id":"26fc2a85-86c4-4b75-b561-357d1fcc6115","doc_no":"A.3.2.2.1.2.3.3.1.5.4.1.2","title":"Reference Inflection Risk Rating","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2637,"content":"The value of the Reference Inflection Risk Rating $r_i$ is `50`.","contentHash":"c38374b55e095846c77cf10800aa3fd5b3c46dfe5b85dff790bccbf9009c8d00","addressRefs":[]},"4f28bafe-6366-40ce-a3df-b796421af66c":{"id":"4f28bafe-6366-40ce-a3df-b796421af66c","doc_no":"A.3.2.2.1.2.3.3.1.5.4.1.3","title":"Maximum Interval Width","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2638,"content":"The value of the Maximum Interval Width $i_{max}$ is `0.50`.","contentHash":"accc8a95f670adbaff7127cf01b695eb0de368b14fff8c5af523596bf14e47e3","addressRefs":[]},"648567a4-b457-46a0-b9da-7a1586c0735e":{"id":"648567a4-b457-46a0-b9da-7a1586c0735e","doc_no":"A.3.2.2.1.2.3.3.1.5.4.1.4","title":"Kink Location Fraction","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2639,"content":"The value of the Kink Location Fraction $i_{kink}$ is `0.75`.","contentHash":"7e770c9d9f9e5b79bf77d737fce8355d25ccecb1c502906f41e3698eea76220b","addressRefs":[]},"a7250cdc-5bf8-48c0-a79f-beb774de8196":{"id":"a7250cdc-5bf8-48c0-a79f-beb774de8196","doc_no":"A.3.2.2.1.2.3.3.1.5.4.2","title":"F2 Threshold Parameters","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2640,"content":"The documents herein define the F2 threshold parameters.","contentHash":"5f036fd0857098ca1aea8f3e9d3d1a73a4d1167da7b1a5f30b25ee89b98e0f70","addressRefs":[]},"c7650bb7-11b0-4ab1-a163-09f948b740a1":{"id":"c7650bb7-11b0-4ab1-a163-09f948b740a1","doc_no":"A.3.2.2.1.2.3.3.1.5.4.2.1","title":"Rating Point Scaling Coefficient","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2641,"content":"The value of the Rating Point Scaling Coefficient $i$ is `0.02`.","contentHash":"55382aa0cfaa695689a3c3627838aba27ab9d16f1cf914157e800231c73bc3dd","addressRefs":[]},"9cee8e99-7d32-4eaa-a559-c364c428f7e1":{"id":"9cee8e99-7d32-4eaa-a559-c364c428f7e1","doc_no":"A.3.2.2.1.2.3.3.1.5.4.2.2","title":"Reference Inflection Risk Rating","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2642,"content":"The value of the Reference Inflection Risk Rating $r_i$ is `75`.","contentHash":"52b596eac72bb4f740e768a17d6f8ecadfad2d55c7d1b3a3277994ddce90d0bf","addressRefs":[]},"e746474b-16ae-4472-b382-f431060a72ec":{"id":"e746474b-16ae-4472-b382-f431060a72ec","doc_no":"A.3.2.2.1.2.3.3.1.5.4.2.3","title":"Maximum Interval Width","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2643,"content":"The value of the Maximum Interval Width $i_{max}$ is `0.50`.","contentHash":"accc8a95f670adbaff7127cf01b695eb0de368b14fff8c5af523596bf14e47e3","addressRefs":[]},"0e04acfb-336b-499a-bbec-e332a82685fd":{"id":"0e04acfb-336b-499a-bbec-e332a82685fd","doc_no":"A.3.2.2.1.2.3.3.1.5.4.2.4","title":"Kink Location Fraction","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2644,"content":"The value of the Kink Location Fraction $i_{kink}$ is `0.75`.","contentHash":"7e770c9d9f9e5b79bf77d737fce8355d25ccecb1c502906f41e3698eea76220b","addressRefs":[]},"3f150022-5449-42cf-b673-fd6ca037f624":{"id":"3f150022-5449-42cf-b673-fd6ca037f624","doc_no":"A.3.2.2.1.2.3.3.2","title":"F1 And F2 Functions","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2645,"content":"The documents herein define the F1 and F2 functions.","contentHash":"26e189e4b58b193f96470a58b6dc90dcf29359965098e1a478772b0dcb0a3717","addressRefs":[]},"7f919121-af12-4adb-904a-8ee88a70e98a":{"id":"7f919121-af12-4adb-904a-8ee88a70e98a","doc_no":"A.3.2.2.1.2.3.3.2.1","title":"Variable Definitions","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2646,"content":"The documents herein define variables used in the F1 and F2 functions.","contentHash":"8af4da76466500b7b18726f7b85dd5f90ba0b6ad1b36e4623fd2052506b390fc","addressRefs":[]},"23cebf79-75ee-49d5-8244-a3e67add3b89":{"id":"23cebf79-75ee-49d5-8244-a3e67add3b89","doc_no":"A.3.2.2.1.2.3.3.2.1.1","title":"Internal Exposure","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2647,"content":"The Internal Exposure $e_{\\text{int}}$ is the Agent’s allocation to the protocol.","contentHash":"90fd5b816019f4d7b653b956de778c84e0829f90c4c13db6fcfa689c204dc31f","addressRefs":[]},"ca513c78-e517-4d95-9d5e-d9485cbaee7a":{"id":"ca513c78-e517-4d95-9d5e-d9485cbaee7a","doc_no":"A.3.2.2.1.2.3.3.2.1.2","title":"Total Exposure","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2648,"content":"The Total Exposure $e_{\\text{tot}}$ is the Sky Ecosystem’s aggregate allocation to the protocol.","contentHash":"2cfa222aab3ae958c50433a7b33b14ac88b6980b593e148cdc2465b829d3acf9","addressRefs":[]},"291fabbc-2121-4439-8129-f9eb9d9ec863":{"id":"291fabbc-2121-4439-8129-f9eb9d9ec863","doc_no":"A.3.2.2.1.2.3.3.2.1.3","title":"Internal Liquid Surplus","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2649,"content":"The Internal Liquid Surplus $s_{\\text{liq}}$ is equal to the Total Risk Capital of the Agent.","contentHash":"b39761b397d9238c0298852943a37b546d9db85b68817492c3900dc7d5a036dc","addressRefs":[]},"6e3f511e-c4bc-479b-b34a-56c42863da2e":{"id":"6e3f511e-c4bc-479b-b34a-56c42863da2e","doc_no":"A.3.2.2.1.2.3.3.2.1.4","title":"Exposure Beyond Surplus","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2650,"content":"The Exposure Beyond Surplus $E_{\\text{beyond}}$ is the difference between the Sky Ecosystem’s aggregate allocation to the protocol and aggregate internal liquid surplus of all Agents.","contentHash":"176ebac3fce4682ad7f8efddbd16d283538d068eef7d570a1d5eb7ec53b72471","addressRefs":[]},"567dd86e-9df5-4dd5-94a9-dcb2d3d4a1e9":{"id":"567dd86e-9df5-4dd5-94a9-dcb2d3d4a1e9","doc_no":"A.3.2.2.1.2.3.3.2.1.5","title":"Total Collateral","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2651,"content":"The Total Collateral $C_{\\text{tot}}$ is the total USDS and Dai debt in the system.","contentHash":"cb1e7cce2d26492d02d6c52d28f6e722877e0d1c280975e4879da4d7ba2f6ac7","addressRefs":[]},"443bcf99-b015-44d3-99c9-42fd611710fe":{"id":"443bcf99-b015-44d3-99c9-42fd611710fe","doc_no":"A.3.2.2.1.2.3.3.2.2","title":"F1 Function","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2652,"content":"The F1 parameter $f_{1}$ is calculated as follows:\n\n$$\nf_{1} = \\dfrac{E_{\\text{beyond}}}{C_{\\text{tot}}}\n$$\n\nThe parameters of this function are defined in [A.3.2.2.1.2.3.3.2.1 - Variable Definitions](7f919121-af12-4adb-904a-8ee88a70e98a).","contentHash":"dd593c96cd58bf7fb58eec58ac0c06d5c6d69a85668511c546ced104d81ed18c","addressRefs":[]},"3286915a-7d81-4eb4-a238-bc7ded8e2634":{"id":"3286915a-7d81-4eb4-a238-bc7ded8e2634","doc_no":"A.3.2.2.1.2.3.3.2.3","title":"F2 Function","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2653,"content":"The F2 parameter $f_2$ is calculated as follows:\n\n$$\nf_{2} = \\dfrac{e_{\\text{int}} + a \\,\\bigl(e_{\\text{tot}} - e_{\\text{int}}\\bigr)}{s_{\\text{liq}}}\n$$\n\nHere $\\alpha$ is equal to `0.1`.\n\nThe parameters of this function are defined in [A.3.2.2.1.2.3.3.2.1 - Variable Definitions](7f919121-af12-4adb-904a-8ee88a70e98a).","contentHash":"32d5e8b067176a28e49d6764c4264bba38380c77a0a979b2f11b657a172eccd8","addressRefs":[]},"35ec7382-0613-4e74-b5ba-d86c647b1d73":{"id":"35ec7382-0613-4e74-b5ba-d86c647b1d73","doc_no":"A.3.2.2.1.2.3.4","title":"Reference Implementation","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2654,"content":"The document herein contains a reference implementation of the calculation of Instance Smart Contract RRC based on the Smart Contract Risk Rating.\n\n```\nimport numpy as np\nimport matplotlib.pyplot as plt\n\n# ------------------------------------------------------------------\n# Function Definition\n# ------------------------------------------------------------------\n\ndef piecewise_coverage(x, x_start, x_kink, x_max):\n    \"\"\"\n    Returns a coverage fraction in [0.0 ... 1.0] given x\n    and piecewise linear thresholds:\n      - 0% coverage if x < x_start\n      - linear 0%→25% from x_start to x_kink\n      - linear 25%→100% from x_kink to x_max\n      - 100% if x > x_max\n    \"\"\"\n    # Safely handle edge cases\n    if x <= x_start:\n        return 0.0\n    if x >= x_max:\n        return 1.0\n\n    # If between x_start and x_kink -> map linearly from 0% to 25%\n    if x_start < x <= x_kink:\n        span = x_kink - x_start\n        # fraction of the way through that segment\n        frac = (x - x_start) / span\n        # coverage goes 0 -> 0.25 (25%)\n        return 0.25 * frac\n\n    # If between x_kink and x_max -> map linearly from 25% to 100%\n    else:  # x_kink < x < x_max\n        span = x_max - x_kink\n        frac = (x - x_kink) / span\n        # coverage goes 0.25 -> 1.0\n        return 0.25 + (0.75 * frac)\n\n# ------------------------------------------------------------------\n# Thresholds\n# ------------------------------------------------------------------\n\ndef f1_thresholds_low_risk(rating):\n    \"\"\"\n    Return (x_start, x_kink, x_max)\n    in % terms, e.g. 5%, 23.75%, 30%, etc.\n    \"\"\"\n    x_start = (50 - rating) * 0.01  # e.g. rating=0 -> 0.5 (50%)\n    x_max   = x_start + 0.50       # always a 50% gap to max\n    # kink is 75% of the way from start to max\n    x_kink  = x_start + 0.75 * (x_max - x_start)\n    return (x_start, x_kink, x_max)\n\ndef f2_thresholds_high_risk(rating):\n    \"\"\"\n    Return (x_start, x_kink, x_max)\n    in fraction form (0.50, 0.875, 1.00, etc).\n    \"\"\"\n    # starting threshold = (75 - rating) * 2%:\n    x_start = (75 - rating) * 0.02\n    x_max = x_start + 0.50\n    x_kink = x_start + 0.75 * (x_max - x_start)  # 75% of the way\n    return (x_start, x_kink, x_max)\n\n# ------------------------------------------------------------------\n# RRC Calculation\n# ------------------------------------------------------------------\n\ndef calculate_rrc_coverage(\n    rating,\n    exposure_internal,\n    exposure_total,\n    liquid_surplus_internal,\n    total_exposure_beyond_surplus,\n    total_collateral\n):\n    \"\"\"\n    Returns the coverage fraction (0 - 1) for a given rating & scenario.\n    For the absolute coverage amount, multiply coverage_fraction\n    by \\`exposure_internal\\`.\n    \"\"\"\n\n    # 1) Compute the two driver ratios\n    f1 = max(0.0, total_exposure_beyond_surplus / total_collateral) # Ensuring it is non-negative when surplus > exposure\n    f2 = (exposure_internal + 0.1 * (exposure_total - exposure_internal)) / liquid_surplus_internal\n\n    # 2) Determine which category the rating is in\n    if rating <= 25:\n        # TRR Category 1 (Low Risk)  => use only f1 piecewise\n        x_start, x_kink, x_max = f1_thresholds_low_risk(rating)\n        coverage_fraction = piecewise_coverage(f1, x_start, x_kink, x_max)\n\n    elif rating <= 50:\n        # TRR Category 2 (Medium Risk) => blend coverage from f1-curve and f2-curve\n        # First get coverage from the \"f1 low-risk\"\n        x_start_1, x_kink_1, x_max_1 = f1_thresholds_low_risk(25)\n        cov_f1 = piecewise_coverage(f1, x_start_1, x_kink_1, x_max_1)\n\n        # Then get coverage from the \"f2 high-risk\"\n        x_start_2, x_kink_2, x_max_2 = f2_thresholds_high_risk(50)\n        cov_f2 = piecewise_coverage(f2, x_start_2, x_kink_2, x_max_2)\n\n        # Blend factor alpha\n        alpha = (rating - 25) / (50 - 25)\n        coverage_fraction = (1 - alpha) * cov_f1 + 0.15 * alpha * cov_f2\n\n    elif rating <= 75:\n        # TRR Category 3 (High Risk) => use only f2\n        x_start, x_kink, x_max = f2_thresholds_high_risk(rating)\n        coverage_fraction = piecewise_coverage(f2, x_start, x_kink, x_max)\n\n    else:\n        # TRR Category 4 (Extreme Risk) => special piecewise lumps.\n        if rating > 75:\n            return 1.0\n\n    return coverage_fraction\n```","contentHash":"4e89a2faf4f2d9658fec9cd0fb492bbbbdb7ea776798abed5751525215fac5b4","addressRefs":[]},"3de7a183-3871-49e0-89b0-1363db621dc0":{"id":"3de7a183-3871-49e0-89b0-1363db621dc0","doc_no":"A.3.2.2.1.2.4","title":"Exceptions","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2655,"content":"The documents herein define exceptions to the calculation of Instance Smart Contract CRR for specific asset classes or protocols.","contentHash":"220ab956bca3fceca9ac231ed69227c6e462b08a354a398951bd217cfc75761a","addressRefs":[]},"52c23a24-aedf-4a1e-abf3-23b819ec9fc5":{"id":"52c23a24-aedf-4a1e-abf3-23b819ec9fc5","doc_no":"A.3.2.2.1.2.4.1","title":"BUIDL, JTRSY, USTB, And JAAA","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2656,"content":"In the short term, investments in BUIDL, JTRSY, USTB, and JAAA have Instance Smart Contract CRR and Instance Administrative CRR of zero.","contentHash":"635e2bc927c83e785f651afa833047237d334ce4776e64b072222903f6bd1070","addressRefs":[]},"717b33c3-708e-4acf-acb4-7be5d5039a2f":{"id":"717b33c3-708e-4acf-acb4-7be5d5039a2f","doc_no":"A.3.2.2.1.2.4.2","title":"Legal Recourse Assets","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2657,"content":"The exposure for investments in Legal Recourse Assets is calculated as specified in the documents herein.","contentHash":"36d83363f52c102a3aba9779a22a90ac04f44b1925f09f114338b57bd422d5ad","addressRefs":[]},"48216554-13d2-460d-b7c5-539167946528":{"id":"48216554-13d2-460d-b7c5-539167946528","doc_no":"A.3.2.2.1.2.4.2.1","title":"Definition","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2658,"content":"Legal Recourse Assets (\"LRAs\") are Real World Assets where legal recourse can be used to recover the assets even if the smart contract is technically hacked or exploited.","contentHash":"6826c6affdab31d6369da1e86b9f7e2dd53b816e0a3ea7c056186c1e87c83fa5","addressRefs":[]},"522e7dc2-9f9d-40f8-a24f-21a688099f15":{"id":"522e7dc2-9f9d-40f8-a24f-21a688099f15","doc_no":"A.3.2.2.1.2.4.2.2","title":"Exposure Calculation","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2659,"content":"The exposure for investments in Legal Recourse Assets is calculated according to the following formula:\n\n`Exposure = Equivalent Loss * Effective Age + Raw Exposure * (1 - Effective Age)`\n\nThe parameters of this formula are defined in the documents herein.","contentHash":"9753502244f026ca0263a4561094a7a2743dfbaf1003a0287182f3a266dadfd7","addressRefs":[]},"dbe94efe-061f-4821-9494-aea27a8c80bf":{"id":"dbe94efe-061f-4821-9494-aea27a8c80bf","doc_no":"A.3.2.2.1.2.4.2.2.1","title":"Equivalent Loss","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2660,"content":"Equivalent Loss is an estimate of the loss that the holder of a Legal Recourse Asset would experience if they had to use legal recourse to recover the assets, based on a combination of expected time to recovery and litigation financing costs. It is calculated according to the following formula:\n\n`Equivalent Loss = Raw Exposure * Expected Frozen Duration * Litigation Financing Costs`\n\nThe parameters of this formula are defined in the documents herein.","contentHash":"c62df7c6b7d9105482247f63cc72776d669ab9c26231c0330675b7427a4888ed","addressRefs":[]},"60833a59-f7f8-45db-92c0-a3bc71ea5375":{"id":"60833a59-f7f8-45db-92c0-a3bc71ea5375","doc_no":"A.3.2.2.1.2.4.2.2.1.1","title":"Raw Exposure","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2661,"content":"Raw Exposure is specified in [A.3.2.2.1.2.4.2.2.3 - Raw Exposure](87fe863b-801d-4415-a3d2-8b4fb977b6c2).","contentHash":"2dbfca530beeaff94f071e218ad42996882626b57374d2abee78347c9f59cd8f","addressRefs":[]},"1e07154c-2a3f-40ff-b96b-476558bc0002":{"id":"1e07154c-2a3f-40ff-b96b-476558bc0002","doc_no":"A.3.2.2.1.2.4.2.2.1.2","title":"Expected Frozen Duration","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2662,"content":"Expected Frozen Duration is the estimated time, in years or fractions thereof, that the Legal Recourse Asset would remain frozen after a hack or technical exploit before the holder would be able to recover the underlying assets through legal recourse. The value of the Expected Frozen Duration is 0.5.","contentHash":"913c48aa36be1f280d142e1e897d48c2e7a3c4a4b2e1b61c9207ab1c2cca4492","addressRefs":[]},"061ee579-9c4f-4f59-b5cf-401ff4c11f72":{"id":"061ee579-9c4f-4f59-b5cf-401ff4c11f72","doc_no":"A.3.2.2.1.2.4.2.2.1.3","title":"Litigation Financing Costs","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2663,"content":"Litigation Financing Costs are the annual costs of borrowing against the right to receive the future recovery of the assets underlying the Legal Recourse Asset through legal recourse. The value of the Litigation Financing Costs is 20%.","contentHash":"84ba2609428c69de2d71cdce85ed3144bbac9f8c0881a3c874e17502478e9030","addressRefs":[]},"c06bbc44-09c0-43f9-b443-39c2802a4a78":{"id":"c06bbc44-09c0-43f9-b443-39c2802a4a78","doc_no":"A.3.2.2.1.2.4.2.2.2","title":"Effective Age","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2664,"content":"The Effective Age is calculated as specified in [A.3.2.2.1.2.2.4.3 - Effective Age](a8db99b2-f072-4132-9ee2-c8ebcc2b3609) except that the Effective Age cannot exceed one (1) year.","contentHash":"2239a6130e7ae02ba69c36c997f03c2f6cd845e052e62d0629982688cb0e89b4","addressRefs":[]},"87fe863b-801d-4415-a3d2-8b4fb977b6c2":{"id":"87fe863b-801d-4415-a3d2-8b4fb977b6c2","doc_no":"A.3.2.2.1.2.4.2.2.3","title":"Raw Exposure","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2665,"content":"The Raw Exposure is the total exposure to the particular Allocation System opportunity.","contentHash":"a06503e30e415477894a36c8f07e819359581d1b78db8eb52fbef86d7735e23d","addressRefs":[]},"4d4f4c60-4941-41c8-8164-c1f35c4574c8":{"id":"4d4f4c60-4941-41c8-8164-c1f35c4574c8","doc_no":"A.3.2.2.1.2.4.3","title":"Ethena","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2666,"content":"In the short term, Direct Ethena Exposures (see [A.3.2.2.1.1.1.2.1.1.1.1 - Direct Ethena Exposures](e0fa035c-e8f3-4cd2-8ca1-a6afbd1825eb)) automatically have Instance Smart Contract CRR and Instance Administrative CRR of zero. In the long term, given the similarity of these assets to Real World Assets, adapted frameworks for Smart Contract Risk and Administrative Risk for these exposures must be developed. See [A.3.2.2.1.2.4.2 - Legal Recourse Assets](717b33c3-708e-4acf-acb4-7be5d5039a2f).","contentHash":"e80f14f233f68e1679302428281cd896ca822f4118792d70dbfa21a82df4e9cf","addressRefs":[]},"d129279e-73a5-4f55-9cc8-3950a05c3fc1":{"id":"d129279e-73a5-4f55-9cc8-3950a05c3fc1","doc_no":"A.3.2.2.1.2.4.4","title":"Superstate","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2667,"content":"In the short term, Superstate Exposures (see [A.3.2.2.1.1.1.2.1.2.1 - Superstate Capital Requirement Ratio](ffca1065-7f92-4815-8a65-52bdbc82c558)) automatically have Instance Smart Contract CRR and Instance Administrative CRR of zero. In the long term, given the similarity of these assets to Real World Assets, adapted frameworks for Smart Contract Risk and Administrative Risk for these exposures must be developed. See [A.3.2.2.1.2.4.2 - Legal Recourse Assets](717b33c3-708e-4acf-acb4-7be5d5039a2f).","contentHash":"66e49a13775e44bebd774b73d082169a3457619d2252eb72c29890ead56c8289","addressRefs":[]},"442c47ef-0fef-4d10-9b5c-12b163795cdd":{"id":"442c47ef-0fef-4d10-9b5c-12b163795cdd","doc_no":"A.3.2.2.1.2.4.5","title":"Fluid","type":"Core","depth":6,"parentId":"e6cfa64f-68c0-4dac-8cec-a5f9bfcb9080","order":2668,"content":"The Smart Contract Risk Rating for Fluid is `25`.","contentHash":"44f248e657b62425ac0f298b022747ddd66c495c0aea6c456f33e3feed20d367","addressRefs":[]},"277d6712-25ff-4566-a42b-38d7e860ae76":{"id":"277d6712-25ff-4566-a42b-38d7e860ae76","doc_no":"A.3.2.2.1.3","title":"Instance Administrative RRC Calculation","type":"Core","depth":5,"parentId":"d10b1c92-b839-45f1-995d-a23381fd6068","order":2669,"content":"The documents herein define the implementation of the Risk Framework for calculating Instance Administrative RRC.","contentHash":"abce2032a79d06d360754df8a585bb73dbf1905ca0bd63c47a10dda41f147716","addressRefs":[]},"a9dfd122-2862-4759-aba7-482f86428ca7":{"id":"a9dfd122-2862-4759-aba7-482f86428ca7","doc_no":"A.3.2.2.1.3.1","title":"Administrative Risk Rating Calculation","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2670,"content":"The first step in calculating the Instance Administrative RRC with respect to an Allocation System opportunity is to calculate the Administrative Risk Rating $\\text{ARR}$ for the protocol being invested in. The $\\text{ARR}$ is calculated as follows:\n\n$$\n\\text{ARR} = min[\\text{CAP}, \\text{SR} \\times \\text{DF} \\times \\text{LAF}]\n$$\n\nHere $min$ is the mathematical minimum function that returns the lesser of the specified parameters.\n\nThe parameters of this formula are specified in the subdocuments herein.","contentHash":"c5f4cf7f78a0e5cd2544c22d2c94d5ac4cbe12a9dfb6ce61d452e01d298b3cbf","addressRefs":[]},"7e359ea6-e846-4977-b3db-87fc1db64c0f":{"id":"7e359ea6-e846-4977-b3db-87fc1db64c0f","doc_no":"A.3.2.2.1.3.1.1","title":"Administrative Risk Rating Cap","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2671,"content":"The Administrative Risk Rating Cap $\\text{CAP}$ is a temporary cap on the Administrative Risk Rating. The value of the $\\text{CAP}$ is `30`.","contentHash":"e4e2ee9dff33b3d188416465063a530b6de6c38d45e6c92cd67eb01957557ee1","addressRefs":[]},"368786cb-da80-4d48-a2e8-52d14fb6320c":{"id":"368786cb-da80-4d48-a2e8-52d14fb6320c","doc_no":"A.3.2.2.1.3.1.2","title":"Starting Rating","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2672,"content":"The Starting Rate $\\text{SR}$ is an initial risk rating for Administrative Risk before taking into account the Delay Factor and Lindy Adjustment Factor. It is a function of the type of backdoor access that exists to the protocol, as specified in the documents herein.","contentHash":"b0480bfbdfbaa3b62d4b5f72d2fd42ad90203f92106539a66e07b059ac68dec1","addressRefs":[]},"0d40ea83-8eef-4bea-b1ca-5700fb4536bc":{"id":"0d40ea83-8eef-4bea-b1ca-5700fb4536bc","doc_no":"A.3.2.2.1.3.1.2.1","title":"No Backdoor","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2673,"content":"A protocol with no backdoor access allows no privileged access to the relevant smart contracts by a whitelisted set of users. The Starting Rate for a protocol with no backdoor access is `0`.","contentHash":"965ea032f151c05badbc64d3a4bf4451337acc374d92469f04d3478084e277c7","addressRefs":[]},"ef31a379-c7ea-43c6-9a68-0f6083fcfeaf":{"id":"ef31a379-c7ea-43c6-9a68-0f6083fcfeaf","doc_no":"A.3.2.2.1.3.1.2.2","title":"Limited Backdoor","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2674,"content":"A protocol with limited backdoor access allows a set of privileged users to materially modify the terms of the smart contracts (e.g. freezing the transfer of funds) but does not allow root backdoor access as specified in [A.3.2.2.1.3.1.2.3 - Root Backdoor](7d203683-a16c-479c-8425-2fed3b4c2375). The Starting Rate for a protocol with limited backdoor access is `50`.","contentHash":"eee2f9809f2d1bfc9b3fea03673df4ec05e64998459e26094b7b18258c8dec5f","addressRefs":[]},"7d203683-a16c-479c-8425-2fed3b4c2375":{"id":"7d203683-a16c-479c-8425-2fed3b4c2375","doc_no":"A.3.2.2.1.3.1.2.3","title":"Root Backdoor","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2675,"content":"A protocol with root backdoor access allows a set of privileged users to make arbitrary changes to the terms of the smart contracts, including transferring user funds. The Starting Rate for a protocol with root backdoor access is `100`.","contentHash":"78cd2f4423a2c7a2114f623dc1ba33a20f68bf37e2324d96f665ccf693fd0438","addressRefs":[]},"52511026-55f4-4848-95a2-53db048d906c":{"id":"52511026-55f4-4848-95a2-53db048d906c","doc_no":"A.3.2.2.1.3.1.3","title":"Delay Factor","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2676,"content":"The Delay Adjustment Factor $\\text{DF}$ is a factor indicating the extent to which the risk associated with backdoor access is mitigated by a security delay between the time that a change using backdoor access is approved and the time that such a change becomes effective. This delay gives users time to raise issues or withdraw funds in the event of malicious or undesirable use of backdoor access.\n\nThe Delay Factor is `1` if there is no security delay and `0` if the security delay is 48 hours or greater. For security delays between 0 hours and 48 hours, the Delay Factor is linearly reduced for each hour of security delay. So a security delay of 24 hours would result in a Delay Factor of `0.5`.","contentHash":"0cf89227fed35b5095d249ce679ba4de77cd1d3045ea2e405b356a2b031cb90f","addressRefs":[]},"1d676660-675c-40a4-8319-23671c55491b":{"id":"1d676660-675c-40a4-8319-23671c55491b","doc_no":"A.3.2.2.1.3.1.4","title":"Lindy Adjustment Factor","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2677,"content":"The Lindy Adjustment Factor $\\text{LAF}$ is calculated using the same methodology specified in [A.3.2.2.1.2.2.4 - Lindy Adjustment Factor](227eff62-f2aa-4e49-91ad-1321261ed299).","contentHash":"b0a558ad9263ed2a05387a00d37a69806dbd3362076e10cc1b69d17917d033dd","addressRefs":[]},"d5546d38-3aba-4161-a991-1e74ef637fbc":{"id":"d5546d38-3aba-4161-a991-1e74ef637fbc","doc_no":"A.3.2.2.1.3.2","title":"Instance Administrative RRC Calculation","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2678,"content":"The second step in calculating the Instance Administrative RRC with respect to an Allocation System opportunity is to calculate the Instance Administrative RRC as a function of the Administrative Risk Rating. This is done using the same methodology as specified in [A.3.2.2.1.2.3 - Smart Contract Risk Required Risk Capital Calculation](b2c8867b-0da0-4765-a927-9a530a0ccf24).","contentHash":"85853e8cc61c94d7fb356c857084a99ee4da95feb4f069d91ca0a9256e9d19cc","addressRefs":[]},"5ecb7c62-29bb-4135-a5c6-dbfb0999c996":{"id":"5ecb7c62-29bb-4135-a5c6-dbfb0999c996","doc_no":"A.3.2.2.1.3.3","title":"Exceptions","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2679,"content":"The documents herein define exceptions to the calculation of Instance Administrative CRR for specific asset classes or protocols.","contentHash":"e4a27a9027f2d0ad564fdfc11c79349ca1f0c5e1d267214ebc769b1c922377bf","addressRefs":[]},"095464ba-2301-4bb6-b342-e840bdd3c018":{"id":"095464ba-2301-4bb6-b342-e840bdd3c018","doc_no":"A.3.2.2.1.3.3.1","title":"BUIDL, JTRSY, USTB, And JAAA","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2680,"content":"The Administrative CRR for BUIDL, JTRSY, USTB, and JAAA is calculated as specified in [A.3.2.2.1.2.4.1 - BUIDL, JTRSY, USTB, And JAAA](52c23a24-aedf-4a1e-abf3-23b819ec9fc5).","contentHash":"3a085034fbac7a21fc9026228e680b97f8a4be064de2fcf56f15a82eefd81681","addressRefs":[]},"e5cf1f62-b8e7-405d-9e3e-46e2e4cbcfd1":{"id":"e5cf1f62-b8e7-405d-9e3e-46e2e4cbcfd1","doc_no":"A.3.2.2.1.3.3.2","title":"Legal Recourse Assets","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2681,"content":"The exposure for investments in Legal Recourse Assets is calculated as specified in [A.3.2.2.1.2.4.2 - Legal Recourse Assets](717b33c3-708e-4acf-acb4-7be5d5039a2f).","contentHash":"a1956e15c4608231975cbaad8a5a5c802513cedc9584419d2e4caa5bc94aa205","addressRefs":[]},"2397551e-9704-435e-b815-0384429be224":{"id":"2397551e-9704-435e-b815-0384429be224","doc_no":"A.3.2.2.1.3.3.3","title":"Ethena","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2682,"content":"The Administrative CRR for Ethena is calculated as specified in [A.3.2.2.1.2.4.3 - Ethena](4d4f4c60-4941-41c8-8164-c1f35c4574c8).","contentHash":"db27e6a1795c6d8c58b1c19e9c2394bb2f46c0871dd34b48ba593fd9c06c02ef","addressRefs":[]},"92c06f19-21a3-4aea-9503-db685b3fd7f9":{"id":"92c06f19-21a3-4aea-9503-db685b3fd7f9","doc_no":"A.3.2.2.1.3.3.4","title":"Superstate","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2683,"content":"The Administrative CRR for Superstate is calculated as specified in [A.3.2.2.1.2.4.4 - Superstate](d129279e-73a5-4f55-9cc8-3950a05c3fc1).","contentHash":"173ad41b963bfb0bfcb8081db1079d26e92e994895f89612292178515f91cab4","addressRefs":[]},"6bbbfa59-7988-4d34-bd75-05402d8ac6f8":{"id":"6bbbfa59-7988-4d34-bd75-05402d8ac6f8","doc_no":"A.3.2.2.1.3.3.5","title":"Fluid","type":"Core","depth":6,"parentId":"277d6712-25ff-4566-a42b-38d7e860ae76","order":2684,"content":"The Administrative Risk Rating for Fluid is `25`.","contentHash":"60a9228e61ba81f404250bd589b637ed571fd4626ba2c93946ff7b9c8a8804f5","addressRefs":[]},"15276567-bf61-4c27-8aa2-2f27da831a48":{"id":"15276567-bf61-4c27-8aa2-2f27da831a48","doc_no":"A.3.2.2.2","title":"Core Risk Capital Parameters","type":"Core","depth":4,"parentId":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","order":2685,"content":"The documents herein define the core risk capital parameters.","contentHash":"e81c3aa1155fb33780c08129d2dded61ac0c2fbd20ad22ba939ba66b71ab01e8","addressRefs":[]},"b718459e-57e0-414f-9c99-fbc82685cc0f":{"id":"b718459e-57e0-414f-9c99-fbc82685cc0f","doc_no":"A.3.2.2.2.1","title":"JRC Loss Allocation Parameters","type":"Core","depth":5,"parentId":"15276567-bf61-4c27-8aa2-2f27da831a48","order":2686,"content":"This document specifies the JRC loss allocation parameters.","contentHash":"c49da331797ab14afde60d9b8ff3ca2675035228b9e6ec987eae2e52342ad15e","addressRefs":[]},"73f2410b-3579-4c68-ae36-e4a4713a6e4b":{"id":"73f2410b-3579-4c68-ae36-e4a4713a6e4b","doc_no":"A.3.2.2.2.1.1","title":"Tip Junior Risk Capital Percentage","type":"Core","depth":6,"parentId":"b718459e-57e0-414f-9c99-fbc82685cc0f","order":2687,"content":"The Tip JRC amount is **10%** of the Prime Agent's Total Junior Risk Capital (IJRC + SEJRC + TEJRC).\n\nFor example, if a Prime Agent has $20 million of Internal Junior Risk Capital and $20 million of Prime External Junior Risk Capital, the Tip Junior Risk Capital would be $4 million.","contentHash":"a167113a77230f2606388e17d09cd33c905330a0c19d8b3018635ea8736281b3","addressRefs":[]},"c8b80b82-abe9-43d0-96bb-bfc82c83feb4":{"id":"c8b80b82-abe9-43d0-96bb-bfc82c83feb4","doc_no":"A.3.2.2.2.2","title":"Risk Capital Composition Structural Ratios","type":"Core","depth":5,"parentId":"15276567-bf61-4c27-8aa2-2f27da831a48","order":2688,"content":"This document specifies the values of the Risk Capital sourcing ratios defined in [A.3.2.1.2.3 - Total Risk Capital Sourcing Ratios](9e99b084-f15a-4f60-b831-d6c0bd9aec04).","contentHash":"79a7a531abdc0bee21c9ba00cfd5d128b736d91825a2889630c86a0ed68031ef","addressRefs":[]},"3ed32706-c072-42b5-b1e5-187bddf8dc37":{"id":"3ed32706-c072-42b5-b1e5-187bddf8dc37","doc_no":"A.3.2.2.2.2.1","title":"External Per Internal (EPI) Ratio Value","type":"Core","depth":6,"parentId":"c8b80b82-abe9-43d0-96bb-bfc82c83feb4","order":2689,"content":"The External Per Internal (EPI) ratio is **1.00**. For example, if a Prime Agent has $20 million of Internal Junior Risk Capital, the EPI ratio enables it to source $20 million of External Junior Risk Capital.\n\nThis EPI ratio governs the initial mechanism for sourcing EJRC (SEJRC + TEJRC) and is based purely on the Prime’s IJRC; Primes can source EJRC via this initial mechanism up to a maximum amount equal to their IJRC holdings. However, additional EJRC may potentially be acquired via the alternative use of SPJ capacity, as described in [A.3.2.1.2.3.1.2.1 - Alternative Use Of SPJ Capacity To Source External Junior Risk Capital](03029174-91b4-4974-af1e-52438556a70b).","contentHash":"ce9e2ce02dd047951c09b5205580c5f88b2b20e201b4c490f72b972f3bc05a60","addressRefs":[]},"8578e240-3fe8-41c0-8b2c-15ec9a7181ab":{"id":"8578e240-3fe8-41c0-8b2c-15ec9a7181ab","doc_no":"A.3.2.2.2.2.2","title":"Senior Per Junior (SPJ) Ratio Values","type":"Core","depth":6,"parentId":"c8b80b82-abe9-43d0-96bb-bfc82c83feb4","order":2690,"content":"The SPJ ratio varies by the JRC type used for enablement:\n\n- Internal Junior Risk Capital SPJ: **1.00**,\n- EPI-acquired Prime External Junior Risk Capital SPJ: **0.75**,\n- EPI-acquired Tokenized External Junior Risk Capital SPJ: **0.50**,\n- SPJ-acquired External Junior Risk Capital (SEJRC or TEJRC): **zero (0)**.\n\nFor example, if a Prime Agent has $20 million of Internal Junior Risk Capital, $10 million of Prime External Junior Risk Capital, and $10 million of Tokenized External Junior Risk Capital, then it would be able to count or \"enable\" $32.5 million of Senior Capital towards its required Risk Capital.","contentHash":"6f0fa7d9fc558c70e698f8555004fa9f7df7aefd0f8e65a8e5acc5c97ce9b345","addressRefs":[]},"2c7c0297-28d5-4954-be87-ffc24d70cef5":{"id":"2c7c0297-28d5-4954-be87-ffc24d70cef5","doc_no":"A.3.2.2.3","title":"Junior Risk Capital System Implementation","type":"Core","depth":4,"parentId":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","order":2691,"content":"The documents herein define operational requirements and protocols for the implementation of the Junior Risk Capital system in the Risk Framework.","contentHash":"372f84a30083c2fcda50873b5fabf63a18c6c6ecd0f02d8d729f58e40c839845","addressRefs":[]},"d47ffd80-c463-49b3-b4a9-60bb6d2b114e":{"id":"d47ffd80-c463-49b3-b4a9-60bb6d2b114e","doc_no":"A.3.2.2.3.1","title":"Prime External JRC Rental System Implementation","type":"Core","depth":5,"parentId":"2c7c0297-28d5-4954-be87-ffc24d70cef5","order":2692,"content":"The implementation of the SEJRC rental system is defined as a Sky Primitive, specifically, the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"bebb75bc8b813bf3da7699bceb3595e41cd66819c2b860d3459bd7c655ac648f","addressRefs":[]},"025c8a59-3c2e-4b33-a635-bb84b6ac6496":{"id":"025c8a59-3c2e-4b33-a635-bb84b6ac6496","doc_no":"A.3.2.2.3.2","title":"Tokenized External JRC System Implementation","type":"Core","depth":5,"parentId":"2c7c0297-28d5-4954-be87-ffc24d70cef5","order":2693,"content":"This document will be further developed in a future iteration of the Atlas.","contentHash":"8f90718ef524bc8ef563e6c84a617488d607cd8e7cb1412ace98a6ad2b6e2200","addressRefs":[]},"6d2be0c6-37fe-42ba-a4a8-a18dd17b0bc1":{"id":"6d2be0c6-37fe-42ba-a4a8-a18dd17b0bc1","doc_no":"A.3.2.2.4","title":"Senior Risk Capital System Implementation","type":"Core","depth":4,"parentId":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","order":2694,"content":"The documents herein define operational requirements and protocols for the implementation of the Senior Risk Capital system in the Risk Framework.","contentHash":"80cff983109d7d211e22963f49b1ea812bb02858055439eff77037ac0af5ac96","addressRefs":[]},"70888f64-f53f-488a-b138-b3b2ab2300b0":{"id":"70888f64-f53f-488a-b138-b3b2ab2300b0","doc_no":"A.3.2.2.4.1","title":"Sourcing Of Internal Senior Risk Capital","type":"Core","depth":5,"parentId":"6d2be0c6-37fe-42ba-a4a8-a18dd17b0bc1","order":2695,"content":"ISRC is sourced from Aggregate Backstop Capital, as specified in [A.2.3.1.3 - Sourcing Of Internal Senior Risk Capital](ac7a6636-acbc-40c9-abc1-4543c0beb300).","contentHash":"3d4ed29a075bc362f9eb89e263359926256f9d1c975479ea45ace92213569882","addressRefs":[]},"9fac0f6b-cb2d-4dc2-97d5-72c705303675":{"id":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","doc_no":"A.3.2.2.4.2","title":"External Senior Risk Capital And srUSDS System","type":"Core","depth":5,"parentId":"6d2be0c6-37fe-42ba-a4a8-a18dd17b0bc1","order":2696,"content":"The documents herein define rules and infrastructure pertaining to the sourcing of External Senior Risk Capital (ESRC). ESRC is capital provided by external investors to be invested as Senior Risk Capital of Prime Agents.","contentHash":"4404d949098e91822109ac5208d2d0e704cdcac4f8d550159e03803d3c19b440","addressRefs":[]},"30e9de3a-d67f-4b89-a777-a9781aab9b1a":{"id":"30e9de3a-d67f-4b89-a777-a9781aab9b1a","doc_no":"A.3.2.2.4.2.1","title":"srUSDS Contract","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2697,"content":"srUSDS is the tokenized form of External Senior Risk Capital. Users can deposit USDS into the srUSDS contract to provide External Senior Risk Capital to the SRC system, making it available for origination by Prime Agents. See [A.3.2.2.4.3 - Senior Risk Capital (SRC) Origination Process](b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f). srUSDS holders can potentially earn higher yields in exchange for the risk that the External Senior Risk Capital will suffer losses.","contentHash":"e11841ee2de75a9f7db86305b1c42707e664bf53748274a9104553f66d49ddee","addressRefs":[]},"38a99586-4a13-4ce3-8b2f-cee025e0c390":{"id":"38a99586-4a13-4ce3-8b2f-cee025e0c390","doc_no":"A.3.2.2.4.2.2","title":"Deposit And Redemption Queues","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2698,"content":"The srUSDS contract utilizes distinct queues for managing conversions. Users can add USDS to the deposit queue for conversion into srUSDS; or add srUSDS to the redemption queue for conversion back into USDS at any point during the month.\n\nAssets placed in either queue can be withdrawn by the user at any time before the Monthly Settlement Cycle begins.\n\nAt the Monthly Settlement Cycle, all assets remaining in the queues are processed: queued USDS is converted into srUSDS, and queued srUSDS is converted into USDS based on the prevailing Conversion Rate. See [A.3.2.2.4.2.3 - Conversion Rate](2220b1b5-f2f6-4325-9bb5-43cca84e184c).","contentHash":"acf44a92d3036bd1f4c7d1a4bffef421285d03d17fa9743a77449e574fda3c32","addressRefs":[]},"2220b1b5-f2f6-4325-9bb5-43cca84e184c":{"id":"2220b1b5-f2f6-4325-9bb5-43cca84e184c","doc_no":"A.3.2.2.4.2.3","title":"Conversion Rate","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2699,"content":"The conversion rate represents the amount of USDS redeemable per unit of srUSDS. This rate increases or decreases over time, reflecting the net return earned by the ESRC pool. The rate is updated at the conclusion of each Monthly Settlement Cycle based on the performance of the ESRC pool during the preceding month, according to the following standard compounding formula:\n\n`New srUSDS Conversion Rate = Previous Conversion Rate * (1 + Monthly srUSDS Yield)`\n\nThe parameters of this formula are defined in the documents herein.","contentHash":"b35ca84378a303e038f77fe50b52eb495d101523d23dc43688f9864cfca6c516","addressRefs":[]},"7074ce0f-5a30-40cf-804f-7621233ac9db":{"id":"7074ce0f-5a30-40cf-804f-7621233ac9db","doc_no":"A.3.2.2.4.2.3.1","title":"Previous Conversion Rate","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2700,"content":"`Previous Conversion Rate` is the conversion rate (USDS per srUSDS) that was in effect at the beginning of the concluded monthly cycle. The initial conversion rate between srUSDS and USDS is 1:1.","contentHash":"6f0a16e18b09e0e2ed4ea5cb579fa92cbd5a3decc9fe818da10da8aeeafda2f2","addressRefs":[]},"cb9bb5b1-50a7-49d8-8ff6-27269061f87e":{"id":"cb9bb5b1-50a7-49d8-8ff6-27269061f87e","doc_no":"A.3.2.2.4.2.3.2","title":"Monthly srUSDS Yield","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2701,"content":"`Monthly srUSDS Yield` represents the net percentage return earned solely by the ESRC pool during the concluded monthly cycle, distributable to srUSDS holders via the conversion rate adjustment. It directly reflects the risk-adjusted performance of the capital deployed and is calculated as:\n\n`[(Total Interest Paid by Stars on ESRC Portion - Losses Allocated to ESRC) / ESRC Principal at start of month - Sky Spread] * (1 - ESRC Earnings Fee)`\n\nThe Sky Spread and ESRC Earnings Fee are defined in [A.3.2.2.4.2.3.3.1 - Sky Spread](c160f99c-c3d8-41e9-a3d1-cde514b7a2da) and [A.3.2.2.4.2.3.3.2 - ESRC Earnings Fee](559f6fb6-daf6-41b2-9882-53a91aaf132f), respectively.","contentHash":"9e6a02c104f9b38fd5cc9d6d2b731b9938149b843d3710c2c613d6e030d0990f","addressRefs":[]},"2e3dcac8-d641-49b7-94e9-6947f0a413ca":{"id":"2e3dcac8-d641-49b7-94e9-6947f0a413ca","doc_no":"A.3.2.2.4.2.3.3","title":"Sources Of Revenue To Sky","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2702,"content":"Sky earns revenue from facilitating ESRC from two sources. These sources are included in the formula and defined in the subdocuments below.","contentHash":"50d4673a6b99dea6d37d4622578f650d4c114c3672a94fd8977d210a697e2210","addressRefs":[]},"c160f99c-c3d8-41e9-a3d1-cde514b7a2da":{"id":"c160f99c-c3d8-41e9-a3d1-cde514b7a2da","doc_no":"A.3.2.2.4.2.3.3.1","title":"Sky Spread","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2703,"content":"Sky takes a spread equal to the Sky Spread on all ESRC balances. The Sky Spread is the difference between (1) the rate at which Prime Agents borrow from Sky and (2) the Sky Savings Rate plus the Distribution Reward Fee.","contentHash":"9dd98b1bc17053624c3476cde086f4fd4db6aedad27d4d3a075bd25367cb8fa4","addressRefs":[]},"559f6fb6-daf6-41b2-9882-53a91aaf132f":{"id":"559f6fb6-daf6-41b2-9882-53a91aaf132f","doc_no":"A.3.2.2.4.2.3.3.2","title":"ESRC Earnings Fee","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2704,"content":"Sky takes a 5% fee on the net interest earnings generated from the ESRC portion of originated SRC before these earnings are distributed to srUSDS holders via the conversion rate adjustment.","contentHash":"7bae364bbd90db92e3ed3ad98231475ae39a8f0a826031d45c818303cf175dd3","addressRefs":[]},"626f0f67-1df9-41e8-a4a6-230aa1ccc824":{"id":"626f0f67-1df9-41e8-a4a6-230aa1ccc824","doc_no":"A.3.2.2.4.2.4","title":"srUSDS Distribution Reward","type":"Core","depth":6,"parentId":"9fac0f6b-cb2d-4dc2-97d5-72c705303675","order":2705,"content":"Prime Agents and third-party partners that drive srUSDS usage are entitled to a srUSDS Distribution Reward similar to the Distribution Reward paid on USDS balances. The srUSDS Distribution Reward Fee is the same as the Distribution Reward Fee on USDS. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"c2f52e0c5882c88cfee6a168b334bf7719782e59592d266c923cf008e9344212","addressRefs":[]},"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f":{"id":"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f","doc_no":"A.3.2.2.4.3","title":"Senior Risk Capital (SRC) Origination Process","type":"Core","depth":5,"parentId":"6d2be0c6-37fe-42ba-a4a8-a18dd17b0bc1","order":2706,"content":"This document defines the operational details of the recurring monthly process allowing Prime Agents to originate Senior Risk Capital (Originated Senior Risk Capital or OSRC) from the Total Senior Risk Capital (TSRC) pool. The process involves determining the available TSRC supply, a bidding phase, an allocation auction, and settlement aligned with the Monthly Settlement Cycle.","contentHash":"47132f089cc1568498ed99f588564aba64d4de100ffcee42ac2435711c02ad88","addressRefs":[]},"d06b1c1a-7613-4361-a155-f62f68ec30a1":{"id":"d06b1c1a-7613-4361-a155-f62f68ec30a1","doc_no":"A.3.2.2.4.3.1","title":"Process Timing and Schedule","type":"Core","depth":6,"parentId":"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f","order":2707,"content":"The SRC origination process operates monthly, synchronized with the Monthly Settlement Cycle. The bidding window occurs during the current month for SRC that is usable in the next month; the bidding window closes before settlement processing begins. Additional operational details, including timelines, will be specified in a future iteration of the Atlas.","contentHash":"4899c81aab94f1820ddb8303b0b329c94b80b76c4da52446c754cea006ac772a","addressRefs":[]},"48a3a23c-2e2f-48b8-bcca-6c99d1c2b6ca":{"id":"48a3a23c-2e2f-48b8-bcca-6c99d1c2b6ca","doc_no":"A.3.2.2.4.3.2","title":"Available Total Senior Risk Capital Pool Determination","type":"Core","depth":6,"parentId":"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f","order":2708,"content":"Total Senior Risk Capital (TSRC) is the amount of Senior Risk Capital that is available each Monthly Settlement Cycle for Primes to originate and thus turn into Originated Senior Risk Capital (OSRC) through the monthly origination process. TSRC is the sum of designated Internal Senior Risk Capital (ISRC) (see [A.2.3.1.3 - Sourcing Of Internal Senior Risk Capital](ac7a6636-acbc-40c9-abc1-4543c0beb300)) and available External Senior Risk Capital (ESRC) from the srUSDS contract. Prior to each monthly bidding window, the TSRC is calculated and publicly announced. Additional operational details will be defined in a future iteration of the Atlas.","contentHash":"32894ef30aed30e5f55a5df8fbba98343872f9e0867b79d7c18c4099c9332b07","addressRefs":[]},"33ef06d4-6ee3-4302-943d-1b932d8c88b4":{"id":"33ef06d4-6ee3-4302-943d-1b932d8c88b4","doc_no":"A.3.2.2.4.3.3","title":"Bidding Process","type":"Core","depth":6,"parentId":"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f","order":2709,"content":"Participating Prime Agents submit bids via the Powerhouse interface during the defined bidding window. Each bid must specify: (1) The quantity of SRC the Prime seeks to originate, and (2) The maximum price the Prime is willing to pay (expressed in basis points above the Base Rate) for using the OSRC during the upcoming monthly period. Additional operational details will be specified in a future iteration of the Atlas.","contentHash":"e77d5e10391e3acefadd7828fea3039a63ad2f6162ba30bc8704c3f7962c3408","addressRefs":[]},"0234bb0c-4686-40bc-94e5-13cd8bcd0db7":{"id":"0234bb0c-4686-40bc-94e5-13cd8bcd0db7","doc_no":"A.3.2.2.4.3.4","title":"Allocation & Clearing Price Determination","type":"Core","depth":6,"parentId":"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f","order":2710,"content":"Bids are ranked descending by price. TSRC is allocated sequentially to the highest bids until the pool is exhausted or all bids are filled. The price of the lowest successful bid that receives an allocation (even partial) sets the uniform clearing price for the month. All winning bidders pay this clearing price per unit of OSRC allocated, regardless of their original bid price. Additional operational details will be specified in a future iteration of the Atlas.","contentHash":"f8f8b9405f4935fb5d9a558922459be152ffa774a0b18cc52a04f3a4d3dac22f","addressRefs":[]},"fff0112a-58dd-4041-97f9-7baf113b4e70":{"id":"fff0112a-58dd-4041-97f9-7baf113b4e70","doc_no":"A.3.2.2.4.3.5","title":"Settlement Of Origination","type":"Core","depth":6,"parentId":"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f","order":2711,"content":"During the Monthly Settlement Cycle following allocation, the cost (Allocated OSRC Quantity * Clearing Price) is deducted from each winning Prime Agent’s operational account. Concurrently, the allocated OSRC amount is credited to the Prime Agent’s Risk Capital account as OSRC for the upcoming monthly period.","contentHash":"dfd3c53452d95aafa2abbe0204ccf7e3ac5e0789d11dd9d9b90b019708d6d300","addressRefs":[]},"b63d43f9-cea7-42ee-bfea-5098e55fa68f":{"id":"b63d43f9-cea7-42ee-bfea-5098e55fa68f","doc_no":"A.3.2.2.4.3.6","title":"OSRC Duration and Renewal","type":"Core","depth":6,"parentId":"b74e61f5-3793-406d-a0e5-f8f0e4d3ac2f","order":2712,"content":"OSRC is valid only for the single monthly period following the settlement cycle in which it was originated. Renewal requires successful participation in the next monthly origination process; there is no automatic rollover.","contentHash":"41e85a1ca5883a2de6a16276d5d64c72010105145251009d5101a0717dfbf638","addressRefs":[]},"268b4b1f-9a19-42f8-b7c6-d8dc01e32517":{"id":"268b4b1f-9a19-42f8-b7c6-d8dc01e32517","doc_no":"A.3.2.2.4.4","title":"Originated Senior Risk Capital (OSRC) Rental Implementation","type":"Core","depth":5,"parentId":"6d2be0c6-37fe-42ba-a4a8-a18dd17b0bc1","order":2713,"content":"The operational process for inter-Prime Agent OSRC risk-capital rentals is defined herein. SEJRC rentals are facilitated through the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"6b9d689565d919566021dd1630ed3dbed79b4d3f9cf2b9b8c8151f7b77486cfa","addressRefs":[]},"0664a5cc-22c9-4d9e-adcf-55ce8c1afc20":{"id":"0664a5cc-22c9-4d9e-adcf-55ce8c1afc20","doc_no":"A.3.2.2.4.4.1","title":"Ecosystem Accord Requirements","type":"Core","depth":6,"parentId":"268b4b1f-9a19-42f8-b7c6-d8dc01e32517","order":2714,"content":"Rental of Originated Senior Risk Capital (OSRC) requires a registered Ecosystem Accord specifying: Amount, Duration, and Price/Terms. As the system permits sub-renting (allowing a Prime to rent out OSRC it has previously rented), the Accord must explicitly state if the borrower is granted this permission. In regards to Duration, the Ecosystem Accord must specify the rental period, which cannot extend beyond the end of the current Monthly Settlement Cycle. Primes may agree on any Duration within this limit.\n\nStandardized Ecosystem Accord templates will be provided in a future iteration of the Atlas.","contentHash":"a6aab0f127ff88e238d69de2f217366b01b0daa633161dfee0a3826962c44b65","addressRefs":[]},"dab711a4-e932-4e2e-bed5-3f459f89cde6":{"id":"dab711a4-e932-4e2e-bed5-3f459f89cde6","doc_no":"A.3.2.2.4.4.2","title":"SRC Accounting & Enablement","type":"Core","depth":6,"parentId":"268b4b1f-9a19-42f8-b7c6-d8dc01e32517","order":2715,"content":"A registered OSRC-rental Ecosystem Accord effectively transfers the claim on the specified amount of the lender’s OSRC to the borrower for the duration of the agreement. The borrowing Prime Agent must possess sufficient Junior Risk Capital (IJRC, SEJRC, TEJRC) and corresponding Senior Per Junior (SPJ) capacity to enable the rented OSRC, such that it counts towards their own Risk Capital requirements. Rented OSRC that is not successfully enabled by the borrower pursuant to the SPJ ratio does not contribute to their Risk Capital calculation.","contentHash":"a7aa88908f05e0cd0921edc83f0c180e396f5ea67fc76c4b35a0319de5ff049a","addressRefs":[]},"d33ac81e-bab1-4969-b46d-e605da2afae3":{"id":"d33ac81e-bab1-4969-b46d-e605da2afae3","doc_no":"A.3.2.2.4.5","title":"Short Term Transitionary Measures","type":"Core","depth":5,"parentId":"6d2be0c6-37fe-42ba-a4a8-a18dd17b0bc1","order":2716,"content":"As an interim measure, prior to the implementation of the Senior Risk Capital System, Sky Core may provide Senior Risk Capital to Prime Agents under Ecosystem Accords between Sky Core and the respective Prime Agents. The terms of such Ecosystem Accords shall be documented under [A.2.8 - Ecosystem Accords](104c3543-ce94-4a2f-9968-57f1ee858085).","contentHash":"ad2f0a0c8ae2543729a8146168d10ad9a8937e35aeb851e093588f925a7cdf5c","addressRefs":[]},"d92f0d3b-e6d5-47d4-b6f1-203ef9326ea6":{"id":"d92f0d3b-e6d5-47d4-b6f1-203ef9326ea6","doc_no":"A.3.2.2.5","title":"Risk Capital Update Process","type":"Core","depth":4,"parentId":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","order":2717,"content":"The documents herein define the process for updating Risk Capital requirements.","contentHash":"e41123bbf3f144be059635f02953e38d7054b6c46fa3dddf856b83792b4a5cd0","addressRefs":[]},"f969dee1-774b-4201-97ae-c9fb91960a18":{"id":"f969dee1-774b-4201-97ae-c9fb91960a18","doc_no":"A.3.2.2.5.1","title":"Schedule For Updating Parameters","type":"Core","depth":5,"parentId":"d92f0d3b-e6d5-47d4-b6f1-203ef9326ea6","order":2718,"content":"The documents herein define the requirements for updating inputs to the calculation of Risk Capital requirements.","contentHash":"4de0ea9288fa6e4c861339d11874f18959e5402495c3ee8e01028dcfb71c24cd","addressRefs":[]},"23083399-43b0-4bc2-adf8-4e97a9ae494d":{"id":"23083399-43b0-4bc2-adf8-4e97a9ae494d","doc_no":"A.3.2.2.5.1.1","title":"Real Time Updates","type":"Core","depth":6,"parentId":"f969dee1-774b-4201-97ae-c9fb91960a18","order":2719,"content":"Inputs into Risk Capital calculations that are based on market or other external variables should be updated in real time or immediately after the underlying data is updated, if the underlying data is only updated periodically.","contentHash":"41796305d671fc4f461aade5b029255729d7d2d9c5cff408d08cb85d710b1254","addressRefs":[]},"4c76f9d0-f354-4fba-bf99-2be97b77d234":{"id":"4c76f9d0-f354-4fba-bf99-2be97b77d234","doc_no":"A.3.2.2.5.1.1.1","title":"Responsibility For Cost Of Real Time Updates","type":"Core","depth":6,"parentId":"f969dee1-774b-4201-97ae-c9fb91960a18","order":2720,"content":"Each Prime Agent is responsible, at its own expense, for providing the required data and developing and maintaining the data feeds that update the Atlas with its data. A Prime Agent may retain another party, including its Operational Executor Agent, to assist it in fulfilling these responsibilities on mutually agreed terms. However, the ultimate responsibility always remains with the Prime Agent.","contentHash":"7d10658cbe1cb9d38202b5206813926d5e192c509a4f3a5416fb6467e5109a47","addressRefs":[]},"31095e6f-6f05-4d0f-83f6-49ef92e1b6ec":{"id":"31095e6f-6f05-4d0f-83f6-49ef92e1b6ec","doc_no":"A.3.2.2.5.1.1.1.1","title":"Near Term Real Time Updates By Core Council Risk Advisor","type":"Core","depth":6,"parentId":"f969dee1-774b-4201-97ae-c9fb91960a18","order":2721,"content":"In the near term, the Core Council Risk Advisor will provide real time data regarding major lending markets. The Core Council Risk Advisor will be compensated for this work as part of its existing relationship with Sky Core and Spark.","contentHash":"cf24e5b369983cf9d11cfa7fd0e1ceaf0cb756cd9e5a25e72d007f0b11861ebd","addressRefs":[]},"7cdc17d9-6199-42bb-8ff9-f7ffce126d3a":{"id":"7cdc17d9-6199-42bb-8ff9-f7ffce126d3a","doc_no":"A.3.2.2.5.1.2","title":"Non-Real Time Updates","type":"Core","depth":6,"parentId":"f969dee1-774b-4201-97ae-c9fb91960a18","order":2722,"content":"In the near term, Prime Agents may update calculations that are based on market or other external variables less frequently than real time. If they do so, Operational GovOps must apply a buffer to each variable that is not updated in real time to account for the fact that the variable may change in a way that increases Required Risk Capital between update frequencies.","contentHash":"6b7865f2255f410cae7277f013cc06e20bc2ecac77310091e5b4430858fe10ef","addressRefs":[]},"d105b84d-c1f6-4460-892c-0971942f8905":{"id":"d105b84d-c1f6-4460-892c-0971942f8905","doc_no":"A.3.2.2.5.2","title":"Data Maintenance And Integrity","type":"Core","depth":5,"parentId":"d92f0d3b-e6d5-47d4-b6f1-203ef9326ea6","order":2723,"content":"The documents herein define processes to maintain and ensure the integrity of data that is used as an input to Risk Capital calculations.","contentHash":"19c818b067595a059a9dc78b3a2d6e0217b89e1a0a896f622b64a72f5114fef5","addressRefs":[]},"ecd07bcd-8a9f-4a3d-b7b0-393f6b5143f7":{"id":"ecd07bcd-8a9f-4a3d-b7b0-393f6b5143f7","doc_no":"A.3.2.2.5.2.1","title":"Responsibility For Data Updates","type":"Core","depth":6,"parentId":"d105b84d-c1f6-4460-892c-0971942f8905","order":2724,"content":"Each Prime Agent is responsible for providing and updating the required data inputs to the Risk Capital calculations. A Prime Agent may retain another party, including its Operational Executor Agent, to assist it in fulfilling these responsibilities on mutually agreed terms. However, the ultimate responsibility always remains with the Prime Agent.","contentHash":"295bf7dab2d59e01efe8186beab3fcc8dfbb3d724cf877a7314157270e3f7184","addressRefs":[]},"b80bdd00-c88b-4186-84de-b6c770b915e0":{"id":"b80bdd00-c88b-4186-84de-b6c770b915e0","doc_no":"A.3.2.2.5.2.2","title":"Verification Of Data Updates","type":"Core","depth":6,"parentId":"d105b84d-c1f6-4460-892c-0971942f8905","order":2725,"content":"If Operational GovOps does not perform the data updates, it must verify their accuracy.","contentHash":"e42866aaa492ec4db242d38cfeba7122d4ccf8508e319f9348def00a0c9f2906","addressRefs":[]},"b6dd98ee-5156-496c-95f3-a6ad0f2eff3b":{"id":"b6dd98ee-5156-496c-95f3-a6ad0f2eff3b","doc_no":"A.3.2.2.5.2.3","title":"Penalties For Late Data Updates","type":"Core","depth":6,"parentId":"d105b84d-c1f6-4460-892c-0971942f8905","order":2726,"content":"In the near term, Operational GovOps must reduce exposure to any Asset Allocation Conduit if the Prime Agent responsible for that Conduit fails to provide the timely information necessary to calculate the required Risk Capital. In the future, a system of monetary penalties must be developed to compensate Sky for the risk posed by late data submission.","contentHash":"eae4d49c29441627c873a3521d3de1490a8df877c63bb9c5259eaf8ea9620a64","addressRefs":[]},"b24ee088-0096-47b0-9e27-4c9e9aeb2d9b":{"id":"b24ee088-0096-47b0-9e27-4c9e9aeb2d9b","doc_no":"A.3.2.2.6","title":"Process For Adjusting Risk Capital","type":"Core","depth":4,"parentId":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","order":2727,"content":"The documents herein define how changes to the calculation of Required Risk Capital or Total Risk Capital should be handled.","contentHash":"553d6a1fd017e1bcae0ffe15427bd26454ad8edbdfd92271363952b7d953fc1d","addressRefs":[]},"86134cd1-f754-4637-8796-f239ec00e434":{"id":"86134cd1-f754-4637-8796-f239ec00e434","doc_no":"A.3.2.2.6.1","title":"Updates Due To Changed Market Parameters","type":"Core","depth":5,"parentId":"b24ee088-0096-47b0-9e27-4c9e9aeb2d9b","order":2728,"content":"The documents herein define the process for handling changes to Required Risk Capital requirements due to changes in market or other external variables.","contentHash":"bf6fbda9044620e520944970f56e29eb0dd0ed05d8410779648a9af1cba117c8","addressRefs":[]},"0932bccb-4d3e-4be8-afbf-649227a60435":{"id":"0932bccb-4d3e-4be8-afbf-649227a60435","doc_no":"A.3.2.2.6.1.1","title":"Immediate Update To Required Risk Capital For Changes In Market Or External Variables","type":"Core","depth":6,"parentId":"86134cd1-f754-4637-8796-f239ec00e434","order":2729,"content":"To the extent that a market or external variable changes in a way that increases the Aggregate Required Risk Capital, the Prime Agent is immediately responsible for supplying additional Total Risk Capital, as necessary, and is subject to penalties for any period in which this Total Risk Capital is not provided. It is the responsibility of the Prime Agent to maintain sufficient capital so that they remain well capitalized in the face of changes to market conditions.","contentHash":"238b8142723ccac43f640a42007026a90d8273cf021a07a3071d81f002daa47b","addressRefs":[]},"088cba75-a83b-4f85-8923-d98c36ff8714":{"id":"088cba75-a83b-4f85-8923-d98c36ff8714","doc_no":"A.3.2.2.6.2","title":"Updates Due To Changed Methodology Or Governance Parameters","type":"Core","depth":5,"parentId":"b24ee088-0096-47b0-9e27-4c9e9aeb2d9b","order":2730,"content":"The documents herein define the process for adjusting the calculation of Required Risk Capital or Total Risk Capital whenever Sky Governance modifies the underlying methodology/parameters governing Risk Capital calculations.","contentHash":"4b8509868a430eb987b62a34938b2ab89b4827c5ee9a85450cc3d2d763211eae","addressRefs":[]},"0f4b2490-bb15-480d-b719-be2bfec69c85":{"id":"0f4b2490-bb15-480d-b719-be2bfec69c85","doc_no":"A.3.2.2.6.2.1","title":"Phased Update To Risk Capital For Changes In Methodology Or Governance Parameters","type":"Core","depth":6,"parentId":"088cba75-a83b-4f85-8923-d98c36ff8714","order":2731,"content":"To the extent that a change to the implementation of the Risk Capital framework or a parameter set by Sky Governance changes the Required Risk Capital or Total Risk Capital, the change will phase in over time. The Prime Agent must provide 50% of the additional Total Risk Capital necessary to comply with the change within seven (7) calendar days of the change, and the remaining 50% on a pro rata basis over the following twenty one (21) calendar days.","contentHash":"3773c035699db25e3cec452258d38bd4c3b6ec1959469ad8f3074622e96977a0","addressRefs":[]},"e083b732-237d-461b-92a4-fe91ea636e3f":{"id":"e083b732-237d-461b-92a4-fe91ea636e3f","doc_no":"A.3.2.2.6.2.2","title":"No Penalties For Changes In Methodology Or Governance Parameters In Near Term","type":"Core","depth":6,"parentId":"088cba75-a83b-4f85-8923-d98c36ff8714","order":2732,"content":"In the near term as the Risk Capital implementation continues to be developed, Prime Agents will not be subject to penalties for failing to supply the incremental capital required by changes to the Risk Capital implementation. However, Operational GovOps must reduce the exposure to Allocation Conduits managed by the Prime Agent to bring it back into compliance with capital requirements if the Prime Agent does not work in good faith to provide the additional capital on the timeline specified above.","contentHash":"8bf61bb7113ba4917c783d8ced5b5f093215682d45b2923ac3c72a8bb4f49247","addressRefs":[]},"50035dc9-4cab-4141-a5d8-a8a4e6870a56":{"id":"50035dc9-4cab-4141-a5d8-a8a4e6870a56","doc_no":"A.3.2.2.7","title":"Monitoring And Penalty Mechanisms","type":"Core","depth":4,"parentId":"e8ca3c08-3daf-4b36-bd5e-02b3eea0935a","order":2733,"content":"The documents herein define monitoring and penalty mechanisms.","contentHash":"9f8b9c03919b28c362fead8b263d0a49788c9210e6169c414bc2a17f46b6a12c","addressRefs":[]},"3fa1e746-ea64-49f0-92e3-f914e8b92b16":{"id":"3fa1e746-ea64-49f0-92e3-f914e8b92b16","doc_no":"A.3.2.2.7.1","title":"Monitoring As Part Of Settlement Cycle","type":"Core","depth":5,"parentId":"50035dc9-4cab-4141-a5d8-a8a4e6870a56","order":2734,"content":"Core GovOps reviews the calculation of Risk Capital by each Prime Agent as part of the Settlement Cycle. In the event that it detects that Risk Capital requirements were violated, it applies the penalty mechanisms specified in [A.3.2.2.7.2 - Penalty Mechanisms](b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0).","contentHash":"ce95b941cf7365e8e8cf7698cd811e4847aea7a1a0e2f326aef825d6ea8e8520","addressRefs":[]},"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0":{"id":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","doc_no":"A.3.2.2.7.2","title":"Penalty Mechanisms","type":"Core","depth":5,"parentId":"50035dc9-4cab-4141-a5d8-a8a4e6870a56","order":2735,"content":"The documents herein specify the penalty mechanisms that exist to incentivize Prime Agents and Operational Agents to ensure that sufficient capital is always held against investments by Prime Agents and to protect Sky from risks due to insufficient capital.","contentHash":"a7ee328d1758468e28d3668896ba6678a2dfdc56a472071697bf8ebefb181023","addressRefs":[]},"58d81b6e-148e-464f-b6ff-1cbbdb173fde":{"id":"58d81b6e-148e-464f-b6ff-1cbbdb173fde","doc_no":"A.3.2.2.7.2.1","title":"Penalty Mechanisms For Prime Agents","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2736,"content":"The documents herein specify the penalty mechanisms for Prime Agents for breaches of the Risk Capital requirements.","contentHash":"cf4b6363a2ccfc275110d2b8ae2cdc4095df04796457a67209d862632b62a925","addressRefs":[]},"3327c009-1d96-46c2-8094-9ca2149427e0":{"id":"3327c009-1d96-46c2-8094-9ca2149427e0","doc_no":"A.3.2.2.7.2.1.1","title":"Financial Penalties For Breach Of Capital Requirements","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2737,"content":"The documents herein define the financial penalties for breaches of Risk Capital requirements.","contentHash":"3b81d97a3f37458e9e667013bb5460c9f9e0fcd487cf09d3358bbfc5e0b7571b","addressRefs":[]},"5435f680-aaaa-461a-bcae-4056bb8964d9":{"id":"5435f680-aaaa-461a-bcae-4056bb8964d9","doc_no":"A.3.2.2.7.2.1.1.1","title":"Encumbrance Ratio","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2738,"content":"The Encumbrance Ratio for a Prime Agent is the ratio of its Aggregate Required Risk Capital to its Total Risk Capital.","contentHash":"78230dbced7f43f7f997e4ad9189570c12c64fb9f759f4faa29ac38f0a837f59","addressRefs":[]},"cf1bcb59-c72a-4b17-ae4b-e80beb881f57":{"id":"cf1bcb59-c72a-4b17-ae4b-e80beb881f57","doc_no":"A.3.2.2.7.2.1.1.2","title":"Severity Of Breaches","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2739,"content":"The financial penalties for breaches of Risk Capital requirements depend on whether the breaches are Low Severity or High Severity. The documents herein define Low Severity and High Severity Breaches. The financial penalties associated with High Severity Breaches and Low Severity Breaches are defined in [A.3.2.2.7.2.1.1.4 - Financial Penalties For Low Severity Breaches](f4bef3da-45a1-4575-9e38-78f2a1f95a3d) and [A.3.2.2.7.2.1.1.5 - Financial Penalties For High Severity Breaches](970c1ce7-dc45-4c02-bad4-80c9f2e32eab), respectively.","contentHash":"ac0f7b2e8b2bc97b1899f94379c88b59b515475dc749d16d6531ececdda51a10","addressRefs":[]},"1981fd65-a9a5-4e5a-a9f8-aa8e85342d7c":{"id":"1981fd65-a9a5-4e5a-a9f8-aa8e85342d7c","doc_no":"A.3.2.2.7.2.1.1.2.1","title":"Low Severity Breach Definition","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2740,"content":"A Low Severity Breach is one in which the Encumbrance Ratio is greater than or equal to 100% but less than 103%.","contentHash":"f313945be1dbdcbb4413d2851b921ad84a86785a8209f46db0d1feede2118b5c","addressRefs":[]},"363e2bb5-47e2-4eb8-950d-eafd0f1392c7":{"id":"363e2bb5-47e2-4eb8-950d-eafd0f1392c7","doc_no":"A.3.2.2.7.2.1.1.2.2","title":"High Severity Breach Definition","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2741,"content":"A High Severity Breach is one in which the Encumbrance Ratio is greater than 103%.","contentHash":"e2f39cd20ed796ee67cf5849726b782dc1ceba631db5a1fa1f1ccb0a5cd38094","addressRefs":[]},"9e689143-99a7-4cae-a6fc-1b1c31da4ff6":{"id":"9e689143-99a7-4cae-a6fc-1b1c31da4ff6","doc_no":"A.3.2.2.7.2.1.1.3","title":"Length Of Breaches","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2742,"content":"The length of a breach refers to the duration measured between its defined start and end points, which depend on the specific aspect of the breach being considered.\n\nIf a breach is initially a Low Severity Breach and subsequently becomes a High Severity Breach, then (1) the length of the Low Severity Breach is the duration from when it became a Low Severity Breach until it became a High Severity Breach; and (2) the length of the High Severity Breach is the duration from when it became a High Severity Breach until that high-severity period concludes (e.g., upon final resolution of the breach or a transition to a different severity level).\n\nLikewise, if a breach is initially a High Severity Breach and subsequently becomes a Low Severity Breach, then (1) the length of the High Severity Breach is the duration from when it became a High Severity Breach until it became a Low Severity Breach; and (2) the length of the Low Severity Breach is the duration from when it became a Low Severity Breach until that low-severity period concludes (e.g., upon final resolution of the breach or a transition to a different severity level).","contentHash":"6499ed388d9518a007c9e4e0b8ec25c9e8749ad62828dda9403356eae428e68c","addressRefs":[]},"f4bef3da-45a1-4575-9e38-78f2a1f95a3d":{"id":"f4bef3da-45a1-4575-9e38-78f2a1f95a3d","doc_no":"A.3.2.2.7.2.1.1.4","title":"Financial Penalties For Low Severity Breaches","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2743,"content":"The documents herein define the financial penalties for Low Severity Breaches.","contentHash":"b90d4bc4aa8a3efdac77c800caf9c2b25265c3e4895c7d63f944a172289e7eed","addressRefs":[]},"32750a35-acf3-4248-a5f0-6787a7fc0cd7":{"id":"32750a35-acf3-4248-a5f0-6787a7fc0cd7","doc_no":"A.3.2.2.7.2.1.1.4.1","title":"Financial Penalties For First 30 Minutes","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2744,"content":"For the first 30 minutes of a Low Severity Breach, the financial penalty is equal to a 500% annual percentage yield on the difference between Aggregate Required Risk Capital and Total Risk Capital.","contentHash":"e904f4228cd02f0972b0ba3e14e150d396af0c8973faa0d70a7d640bc1535701","addressRefs":[]},"4f7e6e09-b0ca-477f-af42-a42d08ae04b7":{"id":"4f7e6e09-b0ca-477f-af42-a42d08ae04b7","doc_no":"A.3.2.2.7.2.1.1.4.2","title":"Financial Penalties For Subsequent 30 Minutes","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2745,"content":"For the next 30 minutes of a Low Severity Breach after the expiration of the duration specified in [A.3.2.2.7.2.1.1.4.1 - Financial Penalties For First 30 Minutes](32750a35-acf3-4248-a5f0-6787a7fc0cd7), the financial penalty is equal to a 1,000% annual percentage yield on the difference between Aggregate Required Risk Capital and Total Risk Capital.","contentHash":"082169a06fd4bd73bbbf244b67551ed4cf05565a4a48fb75d7d870f69fdac01c","addressRefs":[]},"9da86bfb-9df0-4ea7-8e39-56dfc5ef04d9":{"id":"9da86bfb-9df0-4ea7-8e39-56dfc5ef04d9","doc_no":"A.3.2.2.7.2.1.1.4.3","title":"Financial Penalties After 60 Minutes","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2746,"content":"After the first 60 minutes of a Low Severity Breach, the financial penalty is equal to a 1,500% annual percentage yield on the difference between Aggregate Required Risk Capital and Total Risk Capital.","contentHash":"e385619848ff606592a89b75ce51896abe155706b1be27c041bb36667fba9ac1","addressRefs":[]},"970c1ce7-dc45-4c02-bad4-80c9f2e32eab":{"id":"970c1ce7-dc45-4c02-bad4-80c9f2e32eab","doc_no":"A.3.2.2.7.2.1.1.5","title":"Financial Penalties For High Severity Breaches","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2747,"content":"The documents herein define the financial penalties for High Severity Breaches.","contentHash":"42bb52a759ef6b02182c8cdb92223ecca1ecf98a44f441538ff7a0acb51a0a87","addressRefs":[]},"b9bfd816-925e-4403-a4c2-fda647a2c59a":{"id":"b9bfd816-925e-4403-a4c2-fda647a2c59a","doc_no":"A.3.2.2.7.2.1.1.5.1","title":"Financial Penalties For First 15 Minutes","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2748,"content":"For the first 15 minutes of a High Severity Breach, the financial penalty is equal to a 1,500% annual percentage yield on the difference between Aggregate Required Risk Capital and Total Risk Capital.","contentHash":"e318a426fa0ff2d9915e77783fd49ce1ec31ec6b4f1c80024628977057715077","addressRefs":[]},"7d3dc8ba-d12c-4583-91eb-9a6d29dffd8d":{"id":"7d3dc8ba-d12c-4583-91eb-9a6d29dffd8d","doc_no":"A.3.2.2.7.2.1.1.5.2","title":"Financial Penalties For Subsequent 15 Minutes","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2749,"content":"For the next 15 minutes of a High Severity Breach after the expiration of the duration specified in [A.3.2.2.7.2.1.1.5.1 - Financial Penalties For First 15 Minutes](b9bfd816-925e-4403-a4c2-fda647a2c59a), the financial penalty is equal to a 2,000% annual percentage yield on the difference between Aggregate Required Risk Capital and Total Risk Capital.","contentHash":"9b7ca60f465f47e13708573e7d050496adece93ea5845a0211e3b5f05a42d4cf","addressRefs":[]},"8151947c-c6e7-4551-8cb9-1cfb6e82f6d0":{"id":"8151947c-c6e7-4551-8cb9-1cfb6e82f6d0","doc_no":"A.3.2.2.7.2.1.1.5.3","title":"Financial Penalties For Subsequent 30 Minutes","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2750,"content":"For the next 30 minutes of a High Severity Breach after the expiration of the duration specified in [A.3.2.2.7.2.1.1.5.2 - Financial Penalties For Subsequent 15 Minutes](7d3dc8ba-d12c-4583-91eb-9a6d29dffd8d), the financial penalty is equal to a 2,500% annual percentage yield on the difference between Aggregate Required Risk Capital and Total Risk Capital.","contentHash":"ec615147f943c4e29bb6853e848caa610a122ba43b24d77af89bf5cd6460207f","addressRefs":[]},"7f70143b-ddc4-4ad1-b5e1-410fa5ba96e5":{"id":"7f70143b-ddc4-4ad1-b5e1-410fa5ba96e5","doc_no":"A.3.2.2.7.2.1.1.5.4","title":"Financial Penalties After 60 Minutes","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2751,"content":"After the first 60 minutes of a High Severity Breach, the financial penalty is equal to a 3,000% annual percentage yield on the difference between Aggregate Required Risk Capital and Total Risk Capital.","contentHash":"8ded2307bb0cc36b3bfb2aa57b4ac1c06525c1835a9c0a7991b162d7c5a286be","addressRefs":[]},"92bc8eae-deaa-45f2-85f4-1c010d2b5daa":{"id":"92bc8eae-deaa-45f2-85f4-1c010d2b5daa","doc_no":"A.3.2.2.7.2.1.1.6","title":"Collection Of Penalties","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2752,"content":"Penalties are calculated by the Core Executor Agents as part of the Monthly Settlement Cycle. See [A.2.4 - Sky Core Monthly Settlement Cycle](6f8d5065-d6ff-4add-9a28-eadeffa7ed1a). Once calculated, penalties are transferred from the Prime Agent’s SubProxy Account to Sky by Sky Governance.","contentHash":"67e89f8ed2dc6379cd033a112dfd0b0c9df1388a8402d1b87133b3dd82bcbffc","addressRefs":[]},"8067694d-e7a2-46ed-8e35-50f0ecde79c7":{"id":"8067694d-e7a2-46ed-8e35-50f0ecde79c7","doc_no":"A.3.2.2.7.2.1.1.6.1","title":"Alternative Enforcement Mechanisms","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2753,"content":"In the event that the Prime Agent’s Total Risk Capital is less than its Required Risk Capital at the time of the Monthly Settlement Cycle, or the collection of the penalty would cause the Prime Agent’s Total Risk Capital to fall below its Required Risk Capital, then Sky may exercise the alternative enforcement mechanism described below.\n\nIn this instance Sky, at its discretion, may issue additional tokens of the Prime Agent and sell them on the open market until it has collected proceeds equal to the calculated penalty. Any proceeds above the calculated penalty shall be refunded to the Prime Agent SubProxy account.\n\nAlternatively, Sky may convert the penalty into a debt owed by the Prime Agent to Sky Core at terms mutually agreed between Sky Core and the Prime Agent.","contentHash":"53a6dfefd1f0f83f968314004810a46c960203e08d22a1ed01f5509a71c1da2b","addressRefs":[]},"829e886b-0d00-488a-bb27-27f12dae9b3b":{"id":"829e886b-0d00-488a-bb27-27f12dae9b3b","doc_no":"A.3.2.2.7.2.1.1.7","title":"Short-Term Exemption","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2754,"content":"While the Risk Framework undergoes refinement, penalties for any Prime Agent breaches of Required Risk Capital will be calculated by Core GovOps once the infrastructure is in place to do so. This calculation serves the purposes of system monitoring, data gathering, and framework calibration. However, throughout this interim phase, such calculated penalties will not be formally assessed against Prime Agents, and consequently, Prime Agents will not be required to make payment for these penalties. Notwithstanding this temporary exemption from penalty payment, Prime Agents are expected to maintain a Encumbrance Ratio of less than or equal to 90%. See [A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9).","contentHash":"860dd8e0ec350ff5899848b9fb1f582d454aedbe857fd06cbf227ecfdf8e2d6c","addressRefs":[]},"2e1a8489-5849-4030-9ed8-8b9a0b09d483":{"id":"2e1a8489-5849-4030-9ed8-8b9a0b09d483","doc_no":"A.3.2.2.7.2.1.2","title":"Additional Token Issuance For Breach Of Capital Requirements","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2755,"content":"In the event that financial penalties are not sufficient to address the shortfall because payment of the penalties would exacerbate an existing capital shortfall, Core GovOps may require the Prime Agent to issue additional tokens and sell them to the extent it deems necessary. Operational GovOps will assist Core GovOps in executing any such transaction. Future iterations of the Risk Capital framework will specify a more detailed methodology for required token issuance.","contentHash":"faafddd67bf48a2dcc64f95945eb6ef64597ae87a7210153399be5c27fae11d4","addressRefs":[]},"291f2548-a473-42f2-b5be-8fad854d8df3":{"id":"291f2548-a473-42f2-b5be-8fad854d8df3","doc_no":"A.3.2.2.7.2.1.3","title":"Restrictions On Investments For Breach Of Capital Requirement","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2756,"content":"Core GovOps may impose whatever restrictions it deems necessary on the usage of the Allocation System Primitive by the Prime Agent, including limiting the Prime Agent’s exposure to certain Instances (conduits) or prohibiting the Prime Agent from using certain Instances. These restrictions may extend for a period of time that Core GovOps deems fit.","contentHash":"856be589b74112f40dfdbdc691a81eaf525e1fad28daf61b5e4ded8b5fe94e06","addressRefs":[]},"5c3dd35a-0c67-44c2-b51b-d40bc865af85":{"id":"5c3dd35a-0c67-44c2-b51b-d40bc865af85","doc_no":"A.3.2.2.7.2.1.4","title":"Conservatorship For Breach Of Capital Requirements","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2757,"content":"In the event that less extreme measures are not adequate to address the capital shortfall, Core GovOps may seek to put the Prime Agent into conservatorship, in which case the Sky Core Facilitator takes direct control of the Prime Agent to maximize value for Sky and other Prime Agent stakeholders. Seeking to put a Prime Agent into conservatorship requires immediate escalation to Sky Core Governance and requires an expedited Executive Vote as specified in [A.1.9.1.5.4.1 - Known And Uncontentious Remedies](3f5f79fa-698c-42db-a941-ead5a5d0aa48).","contentHash":"20b46d1afe8ab918de686e3f2f87b3f19e9a3ff8596593b07587e7f0d71f09cc","addressRefs":[]},"a56f0e2a-2e3e-45a5-8aac-c7708ff4e20d":{"id":"a56f0e2a-2e3e-45a5-8aac-c7708ff4e20d","doc_no":"A.3.2.2.7.2.2","title":"Penalty Mechanisms For Operational Executor Agents","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2758,"content":"The documents herein specify the penalty mechanisms for Operational Executor Agents for breaches of Risk Capital requirements.","contentHash":"6c7e5beec2f2cd384a2778ac425c3c9c0863d3b46c9306a700c94caccbf82139","addressRefs":[]},"134f7d3e-fee1-4d9d-aef8-1e5a9b390d21":{"id":"134f7d3e-fee1-4d9d-aef8-1e5a9b390d21","doc_no":"A.3.2.2.7.2.2.1","title":"Financial Penalties For Operational Executor Agents","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2759,"content":"In the near term there are no penalties for Operational Executor Agents for failure of the Prime Agents they supervise to maintain appropriate levels of capital. In future iterations of the Risk Framework, Operational Executor Agents will be required to put up collateral and act as \"insurers\" of all activities by the Prime Agents they supervise with regard to the Sky Primitives. At that point Core GovOps will be able to seize this collateral in the event of failure to obtain compensation for breaches of the Risk Capital requirement by the Prime Agent.","contentHash":"51a2676d864c688e2dfc5960bafa70ec684efd96876b039748f12285a57b5279","addressRefs":[]},"782d49c6-e4db-4d4a-be29-3f005cd654c1":{"id":"782d49c6-e4db-4d4a-be29-3f005cd654c1","doc_no":"A.3.2.2.7.2.2.2","title":"Termination Of Executor Accord","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2760,"content":"In the event that Core GovOps determines that the Operational Executor Agent is not appropriately supervising the activities of the Prime Agent, Core GovOps may terminate the respective Executor Accord. This requires an immediate escalation to Sky Governance and requires an expedited Executive Vote as specified in [A.1.9.1.5.4.1 - Known And Uncontentious Remedies](3f5f79fa-698c-42db-a941-ead5a5d0aa48). Core GovOps must arrange for another Operational Executor Agent to stand in until the Prime Agent can Invoke the Executor Accord Primitive to enter into a new Executor Accord. The Prime Agent must suspend all operations until a new Executor Accord is voted on and formally integrated into the Agent’s Artifact.","contentHash":"539d238909e57d860104fda2ba46b3efc7636a3246c680f983cfc2c021e18248","addressRefs":[]},"7ff23236-91c4-4c5c-b462-d4427b03bfd4":{"id":"7ff23236-91c4-4c5c-b462-d4427b03bfd4","doc_no":"A.3.2.2.7.2.3","title":"Escalation To Sky Governance","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2761,"content":"The documents herein specify measures for escalating situations directly to Sky Governance in the event that they cannot be resolved by Core GovOps.","contentHash":"efe695661fb43b1652f8c7aae673d6c5f5d63463532c11a71a9acb476118f1dc","addressRefs":[]},"36978109-324d-40da-be44-f05809c1544a":{"id":"36978109-324d-40da-be44-f05809c1544a","doc_no":"A.3.2.2.7.2.3.1","title":"Triggers For Escalation","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2762,"content":"In the event of a disagreement regarding the penalties for a violation of Risk Capital requirements, either party may escalate the matter to Sky Governance. In addition, the extraordinary remedies of Prime Agent Conservatorship and Executor Accord Termination must always be escalated to a Sky Governance Executive Vote.","contentHash":"0ee33885bb418d6807e35346f88087a377b18386096501441f666ef2a3f95ee3","addressRefs":[]},"1ccb4063-facc-42d6-a71e-21fe29e84519":{"id":"1ccb4063-facc-42d6-a71e-21fe29e84519","doc_no":"A.3.2.2.7.2.3.2","title":"Sky Governance Process","type":"Core","depth":6,"parentId":"b8ee2d12-c94b-4d22-b55e-d2b6e6d94ad0","order":2763,"content":"Once a matter has been escalated to Sky Governance, the Sky Core Facilitator may request any information they deem necessary from Core GovOps, Operational GovOps, and the Prime Agent. Sky Governance then acts through a Governance Poll to determine its resolution of the matter.","contentHash":"09a8a680eb4739c15531cd3af5a27466ec4f3f3c874b44a77038e268a81124a5","addressRefs":[]},"6478afd5-7c3f-4bed-a2b7-9f8ee402bb64":{"id":"6478afd5-7c3f-4bed-a2b7-9f8ee402bb64","doc_no":"A.3.3","title":"Asset Liability Management","type":"Article","depth":2,"parentId":"d56538fc-2220-491a-a4d2-7ad6e461d707","order":2764,"content":"The Asset Liability Management framework establishes universal rules for Prime Agents deploying Sky’s Collateral Portfolio to maintain the stability of the USDS peg through highly liquid assets. The Asset Liability Management framework governs collateral allocation across all Agents, via the Allocation System Primitive, and replaces Sky Core’s historical Asset Liability Management mechanisms which will be offboarded entirely or transitioned to Prime Agents.","contentHash":"9e44fbb63eef88454426ceaa125d63ce7430a411a701ec3d1b9d6824842b47ac","addressRefs":[]},"dbdb3a38-4438-44a0-af77-9518ada97301":{"id":"dbdb3a38-4438-44a0-af77-9518ada97301","doc_no":"A.3.3.1","title":"Conceptual Framework","type":"Section","depth":3,"parentId":"6478afd5-7c3f-4bed-a2b7-9f8ee402bb64","order":2765,"content":"This section defines the conceptual framework for Asset Liability Management.","contentHash":"8f23ce46ee691222ecb11e66a9fcf71ad28a10d5eadf8c82ee8060183a5f7e06","addressRefs":[]},"de00cd5a-91ab-4c04-8ce1-8aa3b7f3c82b":{"id":"de00cd5a-91ab-4c04-8ce1-8aa3b7f3c82b","doc_no":"A.3.3.1.1","title":"Minimum Actively Stabilizing Collateral","type":"Core","depth":4,"parentId":"dbdb3a38-4438-44a0-af77-9518ada97301","order":2766,"content":"The \"Sky Collateral Portfolio\" consists of all assets backing USDS, whether deployed by Prime Agents or Sky Core. The Asset Liability Management framework is based on ensuring that a certain percentage of Sky Collateral Portfolio is invested in Actively Stabilizing Collateral, highly liquid market making non-USDS assets that trade for close to 1 USD per USDS. In this way, if there is ever downward pressure on the price of USDS these assets can be used to buy USDS to maintain the peg.","contentHash":"255132dab1f1f0dcf5cc945a2a134fb5a3dfe8e0425afcc17c5dfa5e80f54291","addressRefs":[]},"00592be0-8d84-4d3f-8c36-1454b18c27ec":{"id":"00592be0-8d84-4d3f-8c36-1454b18c27ec","doc_no":"A.3.3.1.2","title":"Minimum Demand Absorption Buffer","type":"Core","depth":4,"parentId":"dbdb3a38-4438-44a0-af77-9518ada97301","order":2767,"content":"The Asset Liability Management also ensures that a certain percentage of the Sky Collateral Portfolio is invested in a Demand Absorption Buffer, highly liquid market making USDS assets that trade for close to 1 USD per USDS. In this way, if there is ever upward pressure on the price of USDS these assets can be used to sell USDS to maintain the peg.","contentHash":"402a0aebc78c6d41da52de09bd07d2794e884e8f55b257bfb0dc2765bcf1c3fc","addressRefs":[]},"810270db-2436-411b-94e4-afbc66492531":{"id":"810270db-2436-411b-94e4-afbc66492531","doc_no":"A.3.3.1.3","title":"Application To Prime Agents","type":"Core","depth":4,"parentId":"dbdb3a38-4438-44a0-af77-9518ada97301","order":2768,"content":"Each Prime Agent investing a portion of the Sky Collateral Portfolio must maintain, with respect to its portion of same, the percentage of Actively Stabilizing Collateral and Demand Absorption Buffer specified in [A.3.3.2.2 - Minimum Actively Stabilizing Collateral](475fe222-9e4a-4e9d-9be6-a7a424ce02f8). By ensuring that every Prime Agent maintains these levels, Sky as a whole remains compliant with the required thresholds of Actively Stabilizing Collateral and Demand Absorption Buffer.","contentHash":"05c3bdda5a752891eac9c75f56a7adff1922ddc8fafb366059f10f57d6857362","addressRefs":[]},"64e1390f-68a1-43ec-87a8-8ae7b990f7ec":{"id":"64e1390f-68a1-43ec-87a8-8ae7b990f7ec","doc_no":"A.3.3.1.3.1","title":"Agent Collateral Portfolio","type":"Core","depth":5,"parentId":"810270db-2436-411b-94e4-afbc66492531","order":2769,"content":"An Agent Collateral Portfolio is defined as the total amount of capital that the Prime Agent has deployed from Sky through the Allocation System Primitive, excluding any portion of that capital held in USDS. See [A.2.2.9.1 - Allocation System Primitive](9db14ab7-bb4b-4751-8084-843bd4359f2a).","contentHash":"6b7339911e47238c3468063a0e7e682e2d82f6b0ed83fdd613843edfbfe3825c","addressRefs":[]},"c825a54b-8696-452c-b963-cbe999f61bad":{"id":"c825a54b-8696-452c-b963-cbe999f61bad","doc_no":"A.3.3.1.3.2","title":"Actively Stabilizing Collateral","type":"Core","depth":5,"parentId":"810270db-2436-411b-94e4-afbc66492531","order":2770,"content":"Actively Stabilizing Collateral is collateral that actively supports the peg of USDS by market-making and providing buy support at a price close to 1 USD per USDS. The implementation of the Asset Liability Management framework specifies the downside spread that is allowed for collateral to qualify as Actively Stabilizing Collateral. See [A.3.3.2 - Implementation](bf1a1991-1c2b-457c-b1ca-6147049e93c5).","contentHash":"c308d6a3cb60833ac2f31e77fca89f1e5a38aa85befb84d5001bbdcdb803181f","addressRefs":[]},"1a4a64fc-240b-4671-a333-3b35dc1e1e2f":{"id":"1a4a64fc-240b-4671-a333-3b35dc1e1e2f","doc_no":"A.3.3.1.3.3","title":"Demand Absorption Buffer","type":"Core","depth":5,"parentId":"810270db-2436-411b-94e4-afbc66492531","order":2771,"content":"The Demand Absorption Buffer is USDS that actively supports the peg of USDS by market-making and providing sell support at a price close to 1 USD per USDS. The implementation of the Asset Liability Management framework specifies the upside spread that is allowed for USDS to qualify toward the Demand Absorption Buffer. See [A.3.3.2 - Implementation](bf1a1991-1c2b-457c-b1ca-6147049e93c5).","contentHash":"e5200dc1bff3451c6bf8e081bc04ab27acb2c729b967da16e40ce3b9b6d6be68","addressRefs":[]},"6e050b66-0bc8-43f1-b32d-2220c9df466b":{"id":"6e050b66-0bc8-43f1-b32d-2220c9df466b","doc_no":"A.3.3.1.4","title":"Application To Sky Core","type":"Core","depth":4,"parentId":"dbdb3a38-4438-44a0-af77-9518ada97301","order":2772,"content":"While its legacy ALM infrastructure is being transferred to Prime Agents, Sky Core manages the portion of the Sky Collateral Portfolio not deployed by Prime Agents (\"Sky Core Collateral Portfolio\"). During this transitional period, Sky Core allocates the Sky Core Collateral Portfolio to Actively Stabilizing Collateral as specified in [A.3.3.2.6 - Sky Core Asset Liability Management Rules](8135523a-dd5f-482d-b522-ec4227746eaf).","contentHash":"300dc08f8914439a4cb951eb9d62bfef72ff73bfce44dfadaca6c95938b49a17","addressRefs":[]},"60d8fa49-f7cc-4b2e-b54a-cdd19b1e0a09":{"id":"60d8fa49-f7cc-4b2e-b54a-cdd19b1e0a09","doc_no":"A.3.3.1.5","title":"Peg Defense Event","type":"Core","depth":4,"parentId":"dbdb3a38-4438-44a0-af77-9518ada97301","order":2773,"content":"In addition to the requirement for Prime Agents to hold a certain percentage of their Collateral Portfolio in Actively Stabilizing Collateral and the Demand Absorption Buffer, Prime Agents have special responsibilities in extraordinary situations where the stability of the peg is threatened. The definition of these events and the obligations for Prime Agents are specified in the implementation of the framework. See [A.3.3.2 - Implementation](bf1a1991-1c2b-457c-b1ca-6147049e93c5).","contentHash":"1b42f8f3c9744d450a599a694e3dc792f8d6aee0243b043f239dd0ccfd53b7d2","addressRefs":[]},"1a7f0b6c-4ec2-4a5f-bb43-deab9305aab6":{"id":"1a7f0b6c-4ec2-4a5f-bb43-deab9305aab6","doc_no":"A.3.3.1.6","title":"Asset Liability Management Rental","type":"Core","depth":4,"parentId":"dbdb3a38-4438-44a0-af77-9518ada97301","order":2774,"content":"To allow the Asset Liability Management obligation of Prime Agents to be satisfied in the most efficient way possible, Prime Agents may enter into Asset Liability Management Rentals between each other, as specified in the Asset Liability Management Rental Primitive. This allows one Prime Agent to hold a greater amount of Actively Stabilizing Collateral to offset another Prime Agent holding a lesser amount. Thus, the overall level of Actively Stabilizing Collateral is unaffected but the Actively Stabilizing Collateral can be held by a Prime Agent that is able to more efficiently hold it.","contentHash":"f255846d3f3f0e47b57f2a00488db801e4aac20d025ea1c47eaf0c75070ceca4","addressRefs":[]},"d2895e10-71cf-416e-8c9c-3f3a9ff80d10":{"id":"d2895e10-71cf-416e-8c9c-3f3a9ff80d10","doc_no":"A.3.3.1.6.1","title":"All Asset Liability Management Obligations Are Rented Together","type":"Core","depth":5,"parentId":"1a7f0b6c-4ec2-4a5f-bb43-deab9305aab6","order":2775,"content":"When Asset Liability Management obligations are rented, the associated obligations with regard to Actively Stabilizing Collateral, Demand Absorption Buffer, and Peg Defense Events are all transferred together.","contentHash":"02b95a2943c5a040292d809f994d3851d0b5b6ff0e5449ace5a1f818be813c0b","addressRefs":[]},"bf1a1991-1c2b-457c-b1ca-6147049e93c5":{"id":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","doc_no":"A.3.3.2","title":"Implementation","type":"Section","depth":3,"parentId":"6478afd5-7c3f-4bed-a2b7-9f8ee402bb64","order":2776,"content":"This Section defines the current implementation of the Asset Liability Management framework.","contentHash":"2590aeea011fa55c009d952eb6ded03018b966d4a1ab344d4049573656a34bc6","addressRefs":[]},"d6c1d594-eb4a-4a81-b643-977c5c995d7a":{"id":"d6c1d594-eb4a-4a81-b643-977c5c995d7a","doc_no":"A.3.3.2.1","title":"Definitions","type":"Core","depth":4,"parentId":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","order":2777,"content":"The documents herein define terms used through the implementation of the Asset Liability Management framework.","contentHash":"367424a0c0fce8f556f87ab38ed87b037023fa2459e609f52fcd8646e355319d","addressRefs":[]},"0082c12d-f1a7-46ff-a4aa-5fe42ece1a4d":{"id":"0082c12d-f1a7-46ff-a4aa-5fe42ece1a4d","doc_no":"A.3.3.2.1.1","title":"Peg Stability Module","type":"Core","depth":5,"parentId":"d6c1d594-eb4a-4a81-b643-977c5c995d7a","order":2778,"content":"A Peg Stability Module (\"PSM\") allows users to swap a given collateral type directly for Dai or USDS at a fixed rate, rather than borrowing Dai or USDS. The PSM contract was designed with Stablecoin collateral in mind, allowing users to swap other Stablecoins for Dai or USDS at a fixed rate to aid with keeping Dai or USDS pegged to one (1) USD.\n\nA PSM operates similarly to a regular vault type with a zero Stability Fee and a liquidation ratio of 100% that can only be accessed through a user-facing smart contract containing the relevant swap functions. Unlike regular vaults, users of the PSM do not retain ownership of the asset and borrow Dai or USDS. Instead, PSM users swap the asset directly for Dai or USDS.","contentHash":"2957f941edd6d39fa517ff39859cc805122cef0af3a2751da08f1ec4475741d9","addressRefs":[]},"590c645c-8045-4053-9ab1-ea718b62f770":{"id":"590c645c-8045-4053-9ab1-ea718b62f770","doc_no":"A.3.3.2.1.2","title":"Low Risk Real World Assets","type":"Core","depth":5,"parentId":"d6c1d594-eb4a-4a81-b643-977c5c995d7a","order":2779,"content":"Low Risk RWAs (\"LRR\") are safe, short-term treasury strategies of less than one (1) year duration.","contentHash":"e89eb7af8d23ae78831c91b86b555faefea99c2fa373040f4242480a2a0c0e96","addressRefs":[]},"066a4d9f-13ed-4ac3-a55a-df7bf3429649":{"id":"066a4d9f-13ed-4ac3-a55a-df7bf3429649","doc_no":"A.3.3.2.1.3","title":"Cash Stablecoins","type":"Core","depth":5,"parentId":"d6c1d594-eb4a-4a81-b643-977c5c995d7a","order":2780,"content":"Cash Stablecoins are defined as USDC, USDT, and pyUSD.","contentHash":"ae656b7dbe0144505b53a4e9ea6d34c36dd265b1a31bcf612562fba01f8e48bf","addressRefs":[]},"475fe222-9e4a-4e9d-9be6-a7a424ce02f8":{"id":"475fe222-9e4a-4e9d-9be6-a7a424ce02f8","doc_no":"A.3.3.2.2","title":"Minimum Actively Stabilizing Collateral","type":"Core","depth":4,"parentId":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","order":2781,"content":"Prime Agents must maintain at least 5% of their Collateral Portfolio in Actively Stabilizing Collateral.","contentHash":"f5cf8d7e445330dc9d84b7f1a5ed6158970082b5f80764a34bda933ebd1e9a81","addressRefs":[]},"62495dee-8d2a-45d4-87c4-01150e3db3c8":{"id":"62495dee-8d2a-45d4-87c4-01150e3db3c8","doc_no":"A.3.3.2.2.1","title":"Actively Stabilizing Collateral","type":"Core","depth":5,"parentId":"475fe222-9e4a-4e9d-9be6-a7a424ce02f8","order":2782,"content":"Actively Stabilizing Collateral is the sum of (1) Resting Actively Stabilizing Collateral and (2) Latent Actively Stabilizing Collateral.","contentHash":"57eb2b009b6de3555c6516c37485eb5510a41f7bb18a9f3860c3bc45116e5f70","addressRefs":[]},"0e17b35a-c830-4695-b63c-5ef58b249d3f":{"id":"0e17b35a-c830-4695-b63c-5ef58b249d3f","doc_no":"A.3.3.2.2.1.1","title":"Resting Actively Stabilizing Collateral","type":"Core","depth":6,"parentId":"62495dee-8d2a-45d4-87c4-01150e3db3c8","order":2783,"content":"Resting Actively Stabilizing Collateral must provide buy support at a price of at least 0.999 USD per USDS (10bps downside spread). Resting Actively Stabilizing Collateral includes Cash Stablecoins in PSMs or decentralized exchanges (e.g., Curve), other stablecoins, crypto assets, or off-chain Real World Asset (RWA) loans to market makers, provided they meet the specified redemption price and transparency requirements.","contentHash":"9b8d5e845670405db5ee63943baa34f18173e3c040bc8cb1421b74b637244bfe","addressRefs":[]},"4e8cd2d1-4c74-49fd-b3fe-f8b6ccc1a79f":{"id":"4e8cd2d1-4c74-49fd-b3fe-f8b6ccc1a79f","doc_no":"A.3.3.2.2.1.1.1","title":"Resting Actively Stabilizing Collateral Calculations","type":"Core","depth":6,"parentId":"62495dee-8d2a-45d4-87c4-01150e3db3c8","order":2784,"content":"Resting Actively Stabilizing Collateral is currently calculated as the sum of:\n\n1. USDC in the LitePSM;\n2. USDC in the PSM3 on Base, Arbitrum, Unichain, Optimism;\n3. Cash Stablecoins in Curve (paired with USDS);\n4. USDC in GUNI 0.01%;\n5. USDC in GUNI 0.05%; and\n6. Cash Stablecoins in Uniswap (paired with USDS).","contentHash":"7efe056cf405d7c0f22613e51c6b66824bc58180bce685f72df3360405767d2b","addressRefs":[]},"300d45c5-96b4-47ad-9471-8122534d9bc4":{"id":"300d45c5-96b4-47ad-9471-8122534d9bc4","doc_no":"A.3.3.2.2.1.2","title":"Latent Actively Stabilizing Collateral","type":"Core","depth":6,"parentId":"62495dee-8d2a-45d4-87c4-01150e3db3c8","order":2785,"content":"Latent Actively Stabilizing Collateral consists of Cash Stablecoins that do not qualify as Resting Actively Stabilizing Collateral but can be converted to Resting Actively Stabilizing Collateral. Latent Actively Stabilizing Collateral may include Cash Stablecoins deposited into lending protocols, Cash Stablecoins used to provide liquidity to decentralized exchanges, or liquid staking derivatives of cash stablecoins.\n\nAssets must satisfy the following requirements to qualify as Latent Actively Stabilizing Collateral:\n\n1. The assets must be verifiable onchain or through reputable APIs or oracles;\n2. The assets must be able to be converted into Resting Actively Stabilizing Collateral within 15 minutes under normal market conditions; and\n3. The process to convert the assets into Resting Actively Stabilizing Collateral must be fully automated and triggered automatically when ASC falls below specified levels.","contentHash":"beabc53dcae85d1a1012b960b52303385ec869bc36c9f184a6fc069a9a850903","addressRefs":[]},"35ce6b38-9fc1-456e-93da-10ab1468a8bf":{"id":"35ce6b38-9fc1-456e-93da-10ab1468a8bf","doc_no":"A.3.3.2.2.1.2.1","title":"Latent Actively Stabilizing Collateral Calculations","type":"Core","depth":6,"parentId":"62495dee-8d2a-45d4-87c4-01150e3db3c8","order":2786,"content":"Latent Actively Stabilizing Collateral is currently calculated as the sum of:\n\n1. Cash Stablecoins in Curve (not paired with USDS);\n2. Cash Stablecoins in Uniswap (not paired with USDS);\n3. Cash Stablecoins in SparkLend;\n4. Cash Stablecoins in Aave;\n5. Cash Stablecoins in Morpho; and\n6. Cash Stablecoins in a Prime ALM Proxy.\n\nThe Core Executor Agents, in consultation with the Core Council Risk Advisor, may impose limitations on the size of exposures to these protocols or to specific pools within these protocols that qualify as Latent Actively Stabilizing Collateral in order to prevent excessive risk to Sky.","contentHash":"73be76c31946fed75e0cfe65a29c39268961b77d984d3c2c92f979ebb3ca7bb9","addressRefs":[]},"5e300cdb-b221-4b6f-9c4a-11502133a1f9":{"id":"5e300cdb-b221-4b6f-9c4a-11502133a1f9","doc_no":"A.3.3.2.2.1.2.2","title":"Maximum Latent Actively Stabilizing Collateral","type":"Core","depth":6,"parentId":"62495dee-8d2a-45d4-87c4-01150e3db3c8","order":2787,"content":"Latent Actively Stabilizing Collateral may not exceed 25% of Actively Stabilizing Collateral.","contentHash":"bf5fb062d8c469e79328c23edb785f08539ff0f072f0fc3a92d6cf5a514e49bf","addressRefs":[]},"51de8003-cdf3-4f86-93a1-1cc3424f299e":{"id":"51de8003-cdf3-4f86-93a1-1cc3424f299e","doc_no":"A.3.3.2.2.2","title":"Penalties For Failing To Satisfy Actively Stabilizing Collateral Requirement","type":"Core","depth":5,"parentId":"475fe222-9e4a-4e9d-9be6-a7a424ce02f8","order":2788,"content":"In the near term there will be no penalties for Prime Agents for failing to maintain the Minimum Actively Stabilizing Collateral. Instead, failures to maintain the Minimum Actively Stabilizing Collateral will be detected and reported as specified in [A.3.3.2.2.2.1 - Reporting Of Failures To Satisfy Actively Stabilizing Collateral Requirement](b74ba49a-de9e-4c4c-866c-b04d9dd208f7).","contentHash":"3f95a9261c1cc0775c55d80470944e0a3b5cea796129fb8c88efbb4f9e999180","addressRefs":[]},"b74ba49a-de9e-4c4c-866c-b04d9dd208f7":{"id":"b74ba49a-de9e-4c4c-866c-b04d9dd208f7","doc_no":"A.3.3.2.2.2.1","title":"Reporting Of Failures To Satisfy Actively Stabilizing Collateral Requirement","type":"Core","depth":6,"parentId":"51de8003-cdf3-4f86-93a1-1cc3424f299e","order":2789,"content":"In the near term, the Core Council Risk Advisor must develop a tool to automatically detect and report failures by Prime Agents to maintain the Minimum Actively Stabilizing Collateral. Each violation by a Prime Agent must be reported within 24 hours to the following parties:\n\n- the Core Facilitator;\n- Core GovOps;\n- the Operational Facilitator for the Prime Agent;\n- Operational GovOps for the Prime Agent; and\n- the Prime Agent.\n\nIn addition, the Core Council Risk Advisor must include a summary of all such violations in the Independent Calculation it prepares as part of each Monthly Settlement Cycle. See [A.2.4.1.2.1.2.2 - Independent Calculation By Core Council Risk Advisor On Behalf Of Core Council](8be8ae66-2453-4d7d-8880-ffaba36bdb7e).","contentHash":"dda16ee307d3982cedb718a8b3c9e3754586b7c096dc8f8ad352774e21ff60b7","addressRefs":[]},"864611dd-38cd-493e-b594-a85610a9c63e":{"id":"864611dd-38cd-493e-b594-a85610a9c63e","doc_no":"A.3.3.2.2.3","title":"Near Term Exemption For Keel","type":"Core","depth":5,"parentId":"475fe222-9e4a-4e9d-9be6-a7a424ce02f8","order":2790,"content":"In the near term, due to limitations in the infrastructure on Solana, Keel is exempt from the requirement to maintain the Minimum Actively Stabilizing Collateral. This exemption will be removed in a future iteration of the Asset Liability Management Framework.","contentHash":"a7bf208bcd4265d82a52716dcb2c5085bef2b555c9b2169a9f4cf3e1a8b693c0","addressRefs":[]},"e5d2d3c1-701c-4420-91a3-d02bc4aa50eb":{"id":"e5d2d3c1-701c-4420-91a3-d02bc4aa50eb","doc_no":"A.3.3.2.2.4","title":"Near Term Actively Stabilizing Collateral Incentive","type":"Core","depth":5,"parentId":"475fe222-9e4a-4e9d-9be6-a7a424ce02f8","order":2791,"content":"In the near term, Prime Agents are eligible for an Actively Stabilizing Collateral Incentive for fulfilling Actively Stabilizing Collateral requirements.","contentHash":"851a6ed9401ae87aa52706431ffa3b5772884ebd927c0e3c16bbbb324475d0e2","addressRefs":[]},"693330d6-9072-4054-bd61-d788537e34e8":{"id":"693330d6-9072-4054-bd61-d788537e34e8","doc_no":"A.3.3.2.2.4.1","title":"Calculation","type":"Core","depth":6,"parentId":"e5d2d3c1-701c-4420-91a3-d02bc4aa50eb","order":2792,"content":"The Actively Stabilizing Collateral Incentive is calculated on a per block basis as follows:\n\n`Actively Stabilizing Collateral Incentive = Eligible Actively Stabilizing Collateral * (Base Rate - Treasury Bill Rate)`\n\nThe parameters of this formula are defined in [A.3.3.2.2.4.1.1 - Eligible Actively Stabilizing Collateral](e0b95f42-2021-44ab-a979-491a113ccbc1).","contentHash":"0aa89c7abd9b1a72ed2e751268bbc56ddb27834d39cf9959f73f9b03b1309f92","addressRefs":[]},"e0b95f42-2021-44ab-a979-491a113ccbc1":{"id":"e0b95f42-2021-44ab-a979-491a113ccbc1","doc_no":"A.3.3.2.2.4.1.1","title":"Eligible Actively Stabilizing Collateral","type":"Core","depth":6,"parentId":"e5d2d3c1-701c-4420-91a3-d02bc4aa50eb","order":2793,"content":"The Eligible Actively Stabilizing Collateral is the lesser of (1) the Prime Agent’s Actively Stabilizing Collateral and (2) the Prime Agent’s Minimum Actively Stabilizing Collateral specified in [A.3.3.2.2 - Minimum Actively Stabilizing Collateral](475fe222-9e4a-4e9d-9be6-a7a424ce02f8).","contentHash":"23ce8902b228c4b8f4ef84cf2ffb6923273032c8283f1078e657961458bab8e5","addressRefs":[]},"0569aabe-179a-42ed-bb9e-24dd0a74408c":{"id":"0569aabe-179a-42ed-bb9e-24dd0a74408c","doc_no":"A.3.3.2.2.4.1.2","title":"Base Rate","type":"Core","depth":6,"parentId":"e5d2d3c1-701c-4420-91a3-d02bc4aa50eb","order":2794,"content":"The Base Rate is specified in [A.3.1.2.1 - Base Rate](228f9955-6bba-4252-a101-5529e7a300b9).","contentHash":"0c82003906d67fca0ee08acf5728f5723874c0021f322bc6771956d19d44b151","addressRefs":[]},"2edd1333-6ca6-4c10-9d71-80b85d4a4265":{"id":"2edd1333-6ca6-4c10-9d71-80b85d4a4265","doc_no":"A.3.3.2.2.4.1.3","title":"Treasury Bill Rate","type":"Core","depth":6,"parentId":"e5d2d3c1-701c-4420-91a3-d02bc4aa50eb","order":2795,"content":"The Treasury Bill Rate is, as of any date of determination, the yield (expressed as an annual rate) on United States Treasury Bills having a maturity of ninety-one (91) days (or, if no such maturity is available, such other maturity as the United States Department of the Treasury shall designate as comparable), as published by the United States Department of the Treasury in its Daily Treasury Yield Curve Rates (or any successor publication or source designated by the United States Department of the Treasury or, if unavailable, by the Federal Reserve). If such rate is not published on the relevant date, the Treasury Bill Rate shall be the most recently published rate prior to that date.","contentHash":"f82547d20cf9ed72f7e0cf8252afd30c550e3b762c7e05c13ddc85789ac65e1c","addressRefs":[]},"4ae6189e-231c-4a7f-b3cb-843fe495c2a8":{"id":"4ae6189e-231c-4a7f-b3cb-843fe495c2a8","doc_no":"A.3.3.2.2.4.2","title":"Payment","type":"Core","depth":6,"parentId":"e5d2d3c1-701c-4420-91a3-d02bc4aa50eb","order":2796,"content":"The Actively Stabilizing Collateral Incentive is paid on a monthly basis as part of the Monthly Settlement Cycle.","contentHash":"f1bb23ce7d71ed39d38c92e62fc54dcd4076dbad4d5364d15112a0c937dea630","addressRefs":[]},"1e129119-a2ce-4978-b235-c50f2a1c5e2e":{"id":"1e129119-a2ce-4978-b235-c50f2a1c5e2e","doc_no":"A.3.3.2.3","title":"Minimum Demand Absorption Buffer","type":"Core","depth":4,"parentId":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","order":2797,"content":"Every Prime Agent must maintain a Demand Absorption Buffer equal to 25% of their required Actively Stabilizing Collateral.","contentHash":"903b41c53bda8d1d94c5218ea90e87589c4b438d4af252897c991a84d4527041","addressRefs":[]},"104c90df-9236-41bc-a6ee-a6db3e8ef097":{"id":"104c90df-9236-41bc-a6ee-a6db3e8ef097","doc_no":"A.3.3.2.3.1","title":"Demand Absorption Buffer","type":"Core","depth":5,"parentId":"1e129119-a2ce-4978-b235-c50f2a1c5e2e","order":2798,"content":"To further stabilize USDS during periods of excess supply, Prime Agents must maintain a Demand Absorption Buffer (DAB), a subset of ASC consisting of USDS that is for sale for at most 1.001 USD per USDS. The Demand Absorption Buffer includes USDS or DAI in PSMs. The Demand Absorption Buffer can also be fulfilled by autonomous systems that generate USDS dynamically through the allocation as needed.","contentHash":"5705f07c827429cdd0043ad78517dfb799ddad0f2adc728d78d92ce74182a70f","addressRefs":[]},"eabe411c-6325-4732-8615-8fb9f2037945":{"id":"eabe411c-6325-4732-8615-8fb9f2037945","doc_no":"A.3.3.2.3.2","title":"Penalties For Failing To Satisfy Demand Absorption Buffer Requirement","type":"Core","depth":5,"parentId":"1e129119-a2ce-4978-b235-c50f2a1c5e2e","order":2799,"content":"Penalties for failing to maintain the Minimum Demand Absorption Buffer will be specified in a future iteration of the Asset Liability Management framework.","contentHash":"da7a6e5450a36e00981155eaa209ec9441e65d179ac735bde98ad16ae963f596","addressRefs":[]},"a61c1baa-db78-4106-b61a-62c6920a1a12":{"id":"a61c1baa-db78-4106-b61a-62c6920a1a12","doc_no":"A.3.3.2.4","title":"Peg Defense Event","type":"Core","depth":4,"parentId":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","order":2800,"content":"The documents herein specify the obligations of Prime Agents during a Peg Defense Event.","contentHash":"b688fc6658a47b6767b109b7e48d976f9ae86a502e6d39f8116f1b3ee0d8cc79","addressRefs":[]},"cc9b27bc-7c4e-46fd-a57c-d857875079dd":{"id":"cc9b27bc-7c4e-46fd-a57c-d857875079dd","doc_no":"A.3.3.2.4.1","title":"Peg Defense Event Definition","type":"Core","depth":5,"parentId":"a61c1baa-db78-4106-b61a-62c6920a1a12","order":2801,"content":"A Peg Defense Event is a situation where the average price of USDS on DEXes that are connected via LayerZero falls below 0.999 USD per USDS.","contentHash":"5e9f1fb333feb29d17faa629819847447dacb20c64d24ddb828983c7772ce38a","addressRefs":[]},"f2c381b3-96db-4f04-9817-6b69cdca8622":{"id":"f2c381b3-96db-4f04-9817-6b69cdca8622","doc_no":"A.3.3.2.4.1.1","title":"Peg Defense Event Alert Tool","type":"Core","depth":6,"parentId":"cc9b27bc-7c4e-46fd-a57c-d857875079dd","order":2802,"content":"The Core Council Risk Advisor, in consultation with Core GovOps, will develop a tool that calculates the average price of USDS on DEXes that are connected via LayerZero in real time. This tool must be made available to all Prime Agents and functionality must be developed that notifies Sky and Prime Agents in real time when a Peg Defense Event has been triggered.","contentHash":"a261b79dd133f9ec750d1afeddc61d2981ebb813d8709ab47c9807c970387803","addressRefs":[]},"816e01d2-76a7-45ea-a770-22e4d3bc1247":{"id":"816e01d2-76a7-45ea-a770-22e4d3bc1247","doc_no":"A.3.3.2.4.2","title":"Peg Defense Obligations","type":"Core","depth":5,"parentId":"a61c1baa-db78-4106-b61a-62c6920a1a12","order":2803,"content":"In a Peg Defense Event, all Prime Agents must immediately begin to buy USDS at a rate of at least 6.25% of their Actively Stabilizing Collateral requirement every 6 hours.","contentHash":"9043d17ff5a2bb6995919b1d05413e6f1a664e0e8bf3564242d13ebbf4bc4825","addressRefs":[]},"58c006ae-d7a7-4e23-929a-18b2bdfe62a5":{"id":"58c006ae-d7a7-4e23-929a-18b2bdfe62a5","doc_no":"A.3.3.2.4.2.1","title":"Alternatives For Satisfying Peg Defense Obligations","type":"Core","depth":6,"parentId":"816e01d2-76a7-45ea-a770-22e4d3bc1247","order":2804,"content":"Peg Defense can be performed through a combination of (1) selling other types of collateral for USDS, or (2) by using USDS, or generating new USDS via the Allocation System, that is then used as collateral to borrow other types of assets (e.g. USDC or USDT on Aave) and buy USDS with it.","contentHash":"a20e988916c74fb4012f2d80edcb0c0e5fd83da2bd0e08cafb4bacb27694275d","addressRefs":[]},"438697e3-7c67-4fc4-b174-df4d2fee176f":{"id":"438697e3-7c67-4fc4-b174-df4d2fee176f","doc_no":"A.3.3.2.4.3","title":"Penalties For Failure To Satisfy Peg Defense Obligations","type":"Core","depth":5,"parentId":"a61c1baa-db78-4106-b61a-62c6920a1a12","order":2805,"content":"Penalties for failing to fulfill the Peg Defense Obligations will be specified in a future iteration of the Asset Liability Management framework.","contentHash":"23098b0375548b3453dcbfce8c5e66df4f4c532d0d92cb57e5f42ed5bc659313","addressRefs":[]},"debeb71c-2689-4033-b3ab-51cd4018fed3":{"id":"debeb71c-2689-4033-b3ab-51cd4018fed3","doc_no":"A.3.3.2.5","title":"Asset Liability Management Rental","type":"Core","depth":4,"parentId":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","order":2806,"content":"The implementation of Asset Liability Management Rentals is specified in [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"83395102b6ee3d59543c603f14ee9382f9244113071ca59698fba4bcff4b3edd","addressRefs":[]},"8135523a-dd5f-482d-b522-ec4227746eaf":{"id":"8135523a-dd5f-482d-b522-ec4227746eaf","doc_no":"A.3.3.2.6","title":"Sky Core Asset Liability Management Rules","type":"Core","depth":4,"parentId":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","order":2807,"content":"Pursuant to [A.3.3.1.4 - Application To Sky Core](6e050b66-0bc8-43f1-b32d-2220c9df466b), Sky Core manages the Sky Core Collateral Portfolio by allocating capital to the Lite PSM (see [A.3.3.2.7.1.1 - Lite Peg Stability Module](39473e1a-63f8-433b-a850-08f53b2dcf02)).","contentHash":"259ced4121ff16a191a940ab56478f7f0c994eb9ad4f2c3ef5b845425d985e56","addressRefs":[]},"da716553-ad32-4292-b11d-74b66f0683b8":{"id":"da716553-ad32-4292-b11d-74b66f0683b8","doc_no":"A.3.3.2.7","title":"Legacy Mechanisms","type":"Core","depth":4,"parentId":"bf1a1991-1c2b-457c-b1ca-6147049e93c5","order":2808,"content":"The documents herein outline Sky Core’s legacy ALM mechanisms. Given the launch of Prime Agents, these legacy mechanisms will be either offboarded entirely or transitioned to Prime Agents.","contentHash":"de918b7f003fd2fc2ca50524f15fd5fca17b109a19df865487dd37f764c417aa","addressRefs":[]},"29de21b4-0603-435e-8149-170f0ae2866a":{"id":"29de21b4-0603-435e-8149-170f0ae2866a","doc_no":"A.3.3.2.7.1","title":"Peg Stability Module","type":"Core","depth":5,"parentId":"da716553-ad32-4292-b11d-74b66f0683b8","order":2809,"content":"The documents herein outline the legacy Peg Stability Module which supported Dai and USDS peg stability under Sky Core management. Going forward, the PSM will be transitioned to Grove.","contentHash":"6cd2b34b560821dae4b2ee87a6b8f82b469c36aab7ba631679a9d27859d3290c","addressRefs":[]},"39473e1a-63f8-433b-a850-08f53b2dcf02":{"id":"39473e1a-63f8-433b-a850-08f53b2dcf02","doc_no":"A.3.3.2.7.1.1","title":"Lite Peg Stability Module","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2810,"content":"Control of the Lite PSM is being transitioned to Grove. Until this transition is complete, the Lite PSM continues to be controlled by Sky Core, subject to the requirements specified in [A.3.3.2.6 - Sky Core Asset Liability Management Rules](8135523a-dd5f-482d-b522-ec4227746eaf). Post-transition, Grove will manage the Lite PSM as an ASC asset pursuant to the rules defined in this Article.","contentHash":"02438c36c487497def26b7d261ff81ba759dc7214bf5f6aa15d0c5669423e996","addressRefs":[]},"9196786a-18b6-4dea-b4e2-852090371dd7":{"id":"9196786a-18b6-4dea-b4e2-852090371dd7","doc_no":"A.3.3.2.7.1.1.1","title":"Lite Peg Stability Module Parameter Definitions","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2811,"content":"The subdocuments herein define the parameters of the Lite Peg Stability Module.","contentHash":"acf0c0bf3544fed227e5cb74d47913f20a6ed4877981a7802193bf07e7bee4db","addressRefs":[]},"12714156-5543-4443-b733-d213db62cecb":{"id":"12714156-5543-4443-b733-d213db62cecb","doc_no":"A.3.3.2.7.1.1.1.1","title":"Lite Peg Stability Module Toll / Fee In Definition","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2812,"content":"`tin` is a percentage fee applied when trading the collateral asset into the PSM in exchange for Dai**.**","contentHash":"b398de5f41504254b4c4cd4fe3f40e97c50178f157839264a829787b3007e204","addressRefs":[]},"a39b4df8-c022-4bfb-9339-e4d3f38715ec":{"id":"a39b4df8-c022-4bfb-9339-e4d3f38715ec","doc_no":"A.3.3.2.7.1.1.1.2","title":"Lite Peg Stability Module Toll / Fee Out Definition","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2813,"content":"`tout` is the percentage fee applied when trading Dai into the PSM in exchange for the collateral asset.","contentHash":"52d3d9e1ce1c7e0eed1c0667e6b35b9e10e2b694a9cdbe87b805560bf4016366","addressRefs":[]},"c1805ee8-626e-4aec-9a88-21377579aa3d":{"id":"c1805ee8-626e-4aec-9a88-21377579aa3d","doc_no":"A.3.3.2.7.1.1.1.3","title":"Lite Peg Stability Module Maximum Debt Ceiling Definition","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2814,"content":"DC-IAM `line` is the maximum amount of debt the LitePSM can accrue.","contentHash":"3859e2dcc90f38b990f795a1a05e43cb6b16037ae64a6085f6b75e2b5ab9e484","addressRefs":[]},"3b015982-458b-4412-8469-cbcdb4a0b481":{"id":"3b015982-458b-4412-8469-cbcdb4a0b481","doc_no":"A.3.3.2.7.1.1.1.3.0.3.1","title":"Debt Ceiling - Element Annotation","type":"Annotation","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2815,"content":"The element \"Debt Ceiling\" refers to the maximum amount that can be borrowed against assets in a vault. Although a PSM has a zero Stability Fee and a liquidation ratio of 100%, it is still a vault and swaps of a collateral asset for Dai represent issuance of Dai that is backed by that collateral asset. The Debt Ceiling serves to limit the exposure the PSM can incur to that collateral asset.","contentHash":"e25d4301134d35bffa058e1629ecb76a1229c70fc668bfb9d20b598d70af5a94","addressRefs":[]},"7d56c67d-d358-4641-aa27-ada5066c0579":{"id":"7d56c67d-d358-4641-aa27-ada5066c0579","doc_no":"A.3.3.2.7.1.1.1.4","title":"Lite Peg Stability Module Target Available Debt Definition","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2816,"content":"DC-IAM `gap` is the target gap between the debt usage and the Debt Ceiling.","contentHash":"e36c4f9a2900d2d7f771f1f6131b01aa7d7b1c262c297c2f3f4433ae8725a585","addressRefs":[]},"51e64b05-ddb8-4ce3-9307-1f2f8dc51a5f":{"id":"51e64b05-ddb8-4ce3-9307-1f2f8dc51a5f","doc_no":"A.3.3.2.7.1.1.1.5","title":"Lite Peg Stability Module Ceiling Increase Cooldown Definition","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2817,"content":"DC-IAM `ttl` is the minimum time requirement before it is possible to increase the debt ceiling, expressed in seconds.","contentHash":"21934c00c709e4e04f8cda9319f614ff95a6a75b1894aa08cf3049b14278db31","addressRefs":[]},"f1a64ee3-d89c-4c5e-9559-10bbf4977297":{"id":"f1a64ee3-d89c-4c5e-9559-10bbf4977297","doc_no":"A.3.3.2.7.1.1.1.5.0.3.1","title":"Debt Ceiling - Element Annotation","type":"Annotation","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2818,"content":"The element \"Debt Ceiling\" refers to the maximum amount that can be borrowed against assets in a vault. Although a PSM has a zero Stability Fee and a liquidation ratio of 100%, it is still a vault and swaps of a collateral asset for Dai represent issuance of Dai that is backed by that collateral asset. The Debt Ceiling serves to limit the exposure the PSM can incur to that collateral asset.","contentHash":"e25d4301134d35bffa058e1629ecb76a1229c70fc668bfb9d20b598d70af5a94","addressRefs":[]},"71776219-5425-4eaf-89fe-7dea283d5a7d":{"id":"71776219-5425-4eaf-89fe-7dea283d5a7d","doc_no":"A.3.3.2.7.1.1.1.6","title":"Lite Peg Stability Module Buffer Definition","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2819,"content":"`buf` is a fixed-sized amount of pre-minted Dai which LitePSM is designed to maintain in most situations. Note, however, that when a user calls `buyGem`, the amount of Dai available can be temporarily larger than `buf`.","contentHash":"bc644852b6a9c7f213bea86e6ea28e27f95cf562b865ca0c77c0e08aeaae3dc4","addressRefs":[]},"41d9ae0a-c3a6-4a24-ae6a-b2ee841fb03d":{"id":"41d9ae0a-c3a6-4a24-ae6a-b2ee841fb03d","doc_no":"A.3.3.2.7.1.1.1.6.0.3.1","title":"BuyGem - Element Annotation","type":"Annotation","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2820,"content":"`buyGem` is a function that can be called on the LitePSM smart contract to buy a collateral asset in exchange for Dai. \"Gem\" here is Daiwanese for the collateral token.\n\nThe Lite Peg Stability Module maintains a pool of pre-minted Dai and Stablecoins to minimize transaction costs in swapping. The `buf` parameter is the amount of pre-minted Dai the LitePSM is designed to maintain in most instances. However, when a user calls `buyGem` and buys the collateral asset in exchange for Dai, the amount of Dai can temporarily exceed the `buf` parameter.","contentHash":"aa823028e5ec37a471008343ee6d0c10c17b4a9043a1e33beb8125647445d8bf","addressRefs":[]},"12d3a162-9615-4bc0-ae09-57e0cd3af222":{"id":"12d3a162-9615-4bc0-ae09-57e0cd3af222","doc_no":"A.3.3.2.7.1.1.1.7","title":"Lite Peg Stability Module Authorized Parties Definition","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2821,"content":"Authorized Parties are actors who are authorized by Sky Governance to use the Lite Peg Stability Module without paying swap fees.","contentHash":"86f5bcfac05f93015d7e7644e64acd80a9a1ef17ecd25ee58f7139aef3492b9b","addressRefs":[]},"8694e11a-6acd-43f1-90fd-67eb7e7d98d6":{"id":"8694e11a-6acd-43f1-90fd-67eb7e7d98d6","doc_no":"A.3.3.2.7.1.1.2","title":"Lite Peg Stability Module Parameter Values","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2822,"content":"The current values of the Lite Peg Stability Module parameters are:\n\n- `tin`: 0%\n- `tout`: 0%\n- DC-IAM `line`: 10,000,000,000\n- DC-IAM `gap`: 400,000,000\n- DC-IAM `ttl`: 43,200 seconds\n- `buf`: 400,000,000\n- Authorized Parties: None","contentHash":"1d2a03c0745f6866f43757e024afb23837c105096304a8c6513645c2c1acd1dc","addressRefs":[]},"bf561ea8-ab09-4ff5-a84d-2e92bcff997b":{"id":"bf561ea8-ab09-4ff5-a84d-2e92bcff997b","doc_no":"A.3.3.2.7.1.1.3","title":"Lite Peg Stability Module Parameter Modification","type":"Core","depth":6,"parentId":"29de21b4-0603-435e-8149-170f0ae2866a","order":2823,"content":"The Sky Core Stability Facilitators, in consultation with the Core Council Risk Advisor, may recommend changes to any of the parameters specified in the subdocuments of [A.3.3.2.7.1.1.1 - Lite Peg Stability Module Parameter Definitions](9196786a-18b6-4dea-b4e2-852090371dd7). These changes will be subject to an Executive Vote through the Operational Weekly Governance Cycle.","contentHash":"d49e8dad5c629e56cc70ab1d291f6fbdeae08520e5b474a4c8d9b5d023052e65","addressRefs":[]},"bea66a32-4cf2-4de9-9a7e-3c94c293fc3c":{"id":"bea66a32-4cf2-4de9-9a7e-3c94c293fc3c","doc_no":"A.3.3.2.7.2","title":"Real World Assets","type":"Core","depth":5,"parentId":"da716553-ad32-4292-b11d-74b66f0683b8","order":2824,"content":"The documents herein define legacy mechanisms related to Real World Assets.","contentHash":"142663f06ecad9f24bf2bccb21d66f8db925a42e878ca382f9bc49b0aa139034","addressRefs":[]},"1b153f9f-7c70-4ae1-b76c-ef12f87532c6":{"id":"1b153f9f-7c70-4ae1-b76c-ef12f87532c6","doc_no":"A.3.3.2.7.2.1","title":"Andromeda","type":"Core","depth":6,"parentId":"bea66a32-4cf2-4de9-9a7e-3c94c293fc3c","order":2825,"content":"Historically, Andromeda balanced Sky Core’s Cash Stablecoin liquidity by allocating excess into low-risk treasury strategies and replenishing shortages. Control of the Andromeda RWA Arranged Structure is currently being transitioned to Grove. Until the transition to Grove is complete, Andromeda continues to be controlled by Sky Core, subject to the requirements defined in [A.3.3.2.6 - Sky Core Asset Liability Management Rules](8135523a-dd5f-482d-b522-ec4227746eaf). Post-transition, Grove will manage Andromeda as a non-ASC asset within its Collateral Portfolio, subject to JRC requirements. Andromeda is not currently operational and its debt ceiling has been reduced to zero.","contentHash":"eca09457a499a3d57fdac85f2574319c33a56b901be6652b1139d20d4fa60bc7","addressRefs":[]},"ca876157-5518-4bf3-9e87-7c4a07a13d36":{"id":"ca876157-5518-4bf3-9e87-7c4a07a13d36","doc_no":"A.3.3.2.7.2.2","title":"Other RWA Offboarding","type":"Core","depth":6,"parentId":"bea66a32-4cf2-4de9-9a7e-3c94c293fc3c","order":2826,"content":"Other than Andromeda, all old RWA exposure that was added before Endgame must stay for as long as necessary, and optimized for yield if possible. When it is possible, the Stability Facilitators should take action to wind down and offboard all such Legacy RWA. Governance actions related to optimizations, wind down and offboardings can be done directly in Executive Votes with no prior Governance Poll needed.","contentHash":"03d4f16b1bdf8f37b1224ee633b0d608ff9dce6a5dcc72b832b4074c9a9d309b","addressRefs":[]},"edd96df7-4058-4a74-a6e5-827df31e5fdd":{"id":"edd96df7-4058-4a74-a6e5-827df31e5fdd","doc_no":"A.3.4","title":"Real World Assets","type":"Article","depth":2,"parentId":"d56538fc-2220-491a-a4d2-7ad6e461d707","order":2827,"content":"This Article governs the secure management of Real World Assets (RWA), which serve as collateral for the USDS Stablecoin. RWAs are enforced through legal recourse by Arranged Structures and present unique risks that this Article must address.","contentHash":"9119dc6bbce117d91d996d5b96bd239301de4143ef1d9cb2a7a24c5254389e68","addressRefs":[]},"1df6a6c4-4f2e-451b-af0d-5c9eccc8762d":{"id":"1df6a6c4-4f2e-451b-af0d-5c9eccc8762d","doc_no":"A.3.4.1","title":"Arranged Structures","type":"Section","depth":3,"parentId":"edd96df7-4058-4a74-a6e5-827df31e5fdd","order":2828,"content":"Arranged Structures are special legal structures set up by Ecosystem Actors to secure Real World Assets to help stabilize the Sky Ecosystem. Each Arranged Structure has a Conduit system which is owned by an Agent and automatically connected to all Agents; the Conduit allows them to send and receive USDS or other assets.","contentHash":"d4882e69c86185573d64b79dbe2d169814d3c510ecdaec03a85929224020a496","addressRefs":[]},"2f1ab584-bb48-4588-a4ff-a4ff0e728c89":{"id":"2f1ab584-bb48-4588-a4ff-a4ff0e728c89","doc_no":"A.3.4.2","title":"Agent Owner For Arranged Structures","type":"Section","depth":3,"parentId":"edd96df7-4058-4a74-a6e5-827df31e5fdd","order":2829,"content":"Arranged Structures must have an Agent owner. The Agent owner assigns instructions to the Arranged Structure on behalf of Sky, and determines if and how other Agents can access the Conduit of the Arranged Structure.","contentHash":"e5464d6e5290dbbee4fda000feb3cc5f865d058eda07cdc28efd5106e6b0d777","addressRefs":[]},"12c9e05d-b47f-456f-aff9-ddece22cec62":{"id":"12c9e05d-b47f-456f-aff9-ddece22cec62","doc_no":"A.3.4.3","title":"Arrangers","type":"Section","depth":3,"parentId":"edd96df7-4058-4a74-a6e5-827df31e5fdd","order":2830,"content":"This Section defines procedures related to Arrangers, Ecosystem Actors that assist in the design and operation of Arranged Structures. Every Arranged Structure must have a designated Arranger responsible for conducting ongoing reporting. All aspects of this relationship, including the Arranger's duties, must be defined in this Section.","contentHash":"25a442cad69a10706223b626988d0ba8df625ef7b74bac96c27f4603ffbb9a73","addressRefs":[]},"4b110433-bf28-4c9a-b709-e2deaac9212e":{"id":"4b110433-bf28-4c9a-b709-e2deaac9212e","doc_no":"A.3.4.3.1","title":"Introduction","type":"Core","depth":4,"parentId":"12c9e05d-b47f-456f-aff9-ddece22cec62","order":2831,"content":"Arrangers are Ecosystem Actors who specialize in sourcing, negotiating, structuring, and reporting on Real World Assets, as well as maintaining and monitoring the underlying Arranged Structures used by the Sky Protocol. The Arrangers manage a restricted function on the Arranged Structure Conduit that allows them to send assets onwards to the predetermined blockchain account of the Arranged Structure.\n\nArrangers are generally prohibited from occupying any position where they could cause damage or loss to the Sky Ecoystem, notwithstanding delays or inconveniences.\n\nAfter the Arranged Structures are established and assets are allocated, Arrangers must not have the capability to operate or influence the legal and operational structure’s asset operations in any manner that could cause significant harm or losses to the stability of USDS.\n\nArrangers are directly approved by SKY voters, and all LRA collateral exposure must be structured by an approved Arranger.","contentHash":"bf74346ea665a70953ae16c9562633b5997ba23c26f75d47d4c2fda82c233af3","addressRefs":[]},"769c492c-2282-4466-8d24-0a530f724a0c":{"id":"769c492c-2282-4466-8d24-0a530f724a0c","doc_no":"A.3.4.3.2","title":"Onboarding And Offboarding of Arrangers","type":"Core","depth":4,"parentId":"12c9e05d-b47f-456f-aff9-ddece22cec62","order":2832,"content":"When they deem it necessary, the Stability Facilitators may initiate a Governance Poll to onboard or offboard Arrangers. The list of current active Arrangers is maintained in [A.3.4.3.2.1 - List Of Active Arrangers](b8791aaa-84b7-4012-8a4f-053595ec232a).","contentHash":"5c261b00d4b3481f1b1184bab3bb276c850c1b00ef54fab9e6d17028580a06a4","addressRefs":[]},"b8791aaa-84b7-4012-8a4f-053595ec232a":{"id":"b8791aaa-84b7-4012-8a4f-053595ec232a","doc_no":"A.3.4.3.2.1","title":"List Of Active Arrangers","type":"Core","depth":5,"parentId":"769c492c-2282-4466-8d24-0a530f724a0c","order":2833,"content":"List of current active Arrangers:\n\n- No current active Arrangers.","contentHash":"a3287679308f437b69c62423953fa961209d91533cdd5979f953c643672d4f17","addressRefs":[]},"a904881f-b235-4236-8439-deea105f06d0":{"id":"a904881f-b235-4236-8439-deea105f06d0","doc_no":"A.3.4.3.3","title":"Reporting And Stress Test Requirements","type":"Core","depth":4,"parentId":"12c9e05d-b47f-456f-aff9-ddece22cec62","order":2834,"content":"Arrangers must publish monthly reporting on each Arranged Structure they have arranged.\n\nEvery six (6) months, Arrangers are also required to publish a stress test analysis that demonstrates how the structures would perform under historical financial crisis scenarios and other hypothetical scenarios.\n\nThe Stability Facilitators must periodically fund independent Ecosystem Actors to review and verify the quality and the results of the stress tests. Should an independent review produce an unfavorable result, the Stability Facilitators must propose a Governance Poll for warning, temporarily deactivating, or permanently offboarding the Arranger and/or the Asset Managers connected to the discovered issue.\n\nTo be considered compliant, Arrangers’ monthly reports must satisfy the requirements of one of the following documents:\n\n- [A.3.4.3.3.1 - Monthly Arranger Report Requirements](7b902bb1-68b4-477d-a575-29aaa02e9e7b)\n- [A.3.4.3.3.2 - Access To Accounts](47eedd39-5bb9-492f-a4aa-9405bb5d196f)","contentHash":"86726f62ed2dfa8735362ea6f0f1db6c44e19bf0412f09f8a0feaa5096607596","addressRefs":[]},"7b902bb1-68b4-477d-a575-29aaa02e9e7b":{"id":"7b902bb1-68b4-477d-a575-29aaa02e9e7b","doc_no":"A.3.4.3.3.1","title":"Monthly Arranger Report Requirements","type":"Core","depth":5,"parentId":"a904881f-b235-4236-8439-deea105f06d0","order":2835,"content":"The following information must be included in the monthly Arranger report. Each item must be reported for at least the start and end date of the reporting period. If these dates fall on days when markets are closed, the first business day after the start date and the last business day before the end date may be used instead.\n\n- Cash balance.\n- Cash income over the reporting period. Any income over $20,000 in value should be broken out as its own line item, and an explanation provided for any non-recurring or non-ordinary expenses.\n- Cash expenses over the reporting period. Any expense over $20,000 in value should be broken out as its own line item, and an explanation provided for any non-recurring or non-ordinary expenses.\n- Market value of publicly traded equities, ETFs, and mutual funds.\n- Market value (the closing price) of publicly traded debt securities. Debt securities that are investment grade and less than 12 months from maturity may alternatively be reported at cost basis + linearly recognizing scheduled interest income.\n- A valuation for illiquid or privately traded assets. This should utilize a valuation from a reputable third party with relevant expertise or follow a well-defined methodology that is explained in detail in the report.\n- CUSIPs, date of purchase, date of maturity, coupon, cost basis, and face value of all publicly traded debt securities in the portfolio for the last day of the reporting period.\n- USDS inflows from the Sky Protocol during the reporting period.\n- Total repayments on-chain to the Sky Protocol either to a vault or for surplus. If repayments are derived from multiple sources, they should be broken out into line items for each source.\n- Vault debt to the Sky Protocol.\n- Copies of original statements for all bank, brokerage, exchange, custodial, or other accounts. The Arranger may redact the names for non-Arranger service providers if and only if that is a requirement of confidentiality agreements with the non-Arranger service providers.\n\nThe Stability Facilitator must publicly confirm on the Sky Forum that they have reviewed the original account documentation and verified that it supports the Arranger’s summary.","contentHash":"1f96b7137d9be8f14fcbf31cb4e691ac6cfba8240675e6ca401a214a83654d0b","addressRefs":[]},"47eedd39-5bb9-492f-a4aa-9405bb5d196f":{"id":"47eedd39-5bb9-492f-a4aa-9405bb5d196f","doc_no":"A.3.4.3.3.2","title":"Access To Accounts","type":"Core","depth":5,"parentId":"a904881f-b235-4236-8439-deea105f06d0","order":2836,"content":"As an alternative to the requirements set out in [A.3.4.3.3.1 - Monthly Arranger Report Requirements](7b902bb1-68b4-477d-a575-29aaa02e9e7b), the Arranger can provide the following information through public read-only access to all accounts:\n\n- All asset balances\n- All transaction amounts (non-Arranger service provider names may be redacted)\n- Hold-to-maturity yields (for assets with maturity) or current yield (for assets with no maturity)\n\nIn addition, Makerburn.com ([https://makerburn.com/#/](https://makerburn.com/#/)), Daistats.com ([https://daistats.com/#/](https://daistats.com/#/)), or another dashboard must be publicly available to summarize USDS inflows and outflows from the Sky vault.","contentHash":"66af8fe20a423b3588b24fa106ca2566049ee7b47879e1b5ffeb58eac3cc3c68","addressRefs":[]},"cb2098b0-9970-4a5b-b835-eaa4f0e2ea6f":{"id":"cb2098b0-9970-4a5b-b835-eaa4f0e2ea6f","doc_no":"A.3.4.4","title":"Agent Owner Can Change Arrangers","type":"Section","depth":3,"parentId":"edd96df7-4058-4a74-a6e5-827df31e5fdd","order":2837,"content":"The Agent owner of the Arranged Structure can change the blockchain account of the Arranged Structure and change the Arranger.","contentHash":"088ced2c81fdf324f07384b400042954ae63e7712560f8786946936e4dd22431","addressRefs":[]},"87ec737c-7c0d-4d94-a760-a1ad9935179b":{"id":"87ec737c-7c0d-4d94-a760-a1ad9935179b","doc_no":"A.3.4.5","title":"Perpetual Yield Strategies","type":"Section","depth":3,"parentId":"edd96df7-4058-4a74-a6e5-827df31e5fdd","order":2838,"content":"The subdocuments herein define perpetual yield strategies and exposure targets that can be implemented by the Stability Facilitators.","contentHash":"bf9c38b45d4fb3d4e100427467db800fe02924fd9bc54c67bd9ee1b867db10b3","addressRefs":[]},"a337def8-2baf-491b-9635-4beaa628b77f":{"id":"a337def8-2baf-491b-9635-4beaa628b77f","doc_no":"A.3.4.5.1","title":"Implemented By Stability Facilitator","type":"Core","depth":4,"parentId":"87ec737c-7c0d-4d94-a760-a1ad9935179b","order":2839,"content":"The Stability Facilitators can implement various perpetual yield strategies, including on-chain and off-chain mechanisms, that enable the Sky Protocol to take advantage of high risk-adjusted return on perpetual yield strategies in the crypto markets.\n\nExposure targets specified in this document override requirements defined by other Articles of the Stability Scope.","contentHash":"5768b491895fa344b64a796cd1d381fb4267f56410b226441a62398d870bf7bb","addressRefs":[]},"64841755-24d5-4464-850f-6b504b1c6022":{"id":"64841755-24d5-4464-850f-6b504b1c6022","doc_no":"A.3.4.5.2","title":"Perpetual Exposure","type":"Core","depth":4,"parentId":"87ec737c-7c0d-4d94-a760-a1ad9935179b","order":2840,"content":"The subdocuments herein define Perpetual Exposure parameters and the associated governance processes.","contentHash":"85c3479ce50118938e8f4d9508a485a64882d3684a0590b113b31ca24f43b7cb","addressRefs":[]},"6b70f984-1b30-40e8-9644-c49151b36caa":{"id":"6b70f984-1b30-40e8-9644-c49151b36caa","doc_no":"A.3.4.5.2.1","title":"Perpetual Exposure Direct Accumulation","type":"Core","depth":5,"parentId":"64841755-24d5-4464-850f-6b504b1c6022","order":2841,"content":"The Stability Facilitators can trigger Executive Votes that instruct Arranged Structures to set up mechanisms that allow them to take direct exposure to Ethena sUSDe, or use legal rails to get direct exposure through custodians.","contentHash":"5b25f4fc90f8d738a5788979172b9b42418e7a3723fe5e4e41efe38b993cfb09","addressRefs":[]},"3eb6f099-2736-4f62-9cb8-096a8fcca757":{"id":"3eb6f099-2736-4f62-9cb8-096a8fcca757","doc_no":"A.3.5","title":"Surplus Buffer and Smart Burn Engine","type":"Article","depth":2,"parentId":"d56538fc-2220-491a-a4d2-7ad6e461d707","order":2842,"content":"This Article defines key economic parameters relating to Sky Protocol Surplus, including the Surplus Buffer and Smart Burn Engine.","contentHash":"fec2a3683bebbc4248918a921772679bda804551a0641469b79e76cf0bd6be84","addressRefs":[]},"9782cdc5-c274-45c2-bf4a-690f22c6a294":{"id":"9782cdc5-c274-45c2-bf4a-690f22c6a294","doc_no":"A.3.5.1","title":"Surplus Buffer","type":"Section","depth":3,"parentId":"3eb6f099-2736-4f62-9cb8-096a8fcca757","order":2843,"content":"The Surplus Buffer is the difference between Sky’s assets and liabilities. Protocol revenue increases the Surplus Buffer and expenses decrease the Surplus Buffer.","contentHash":"770c1967c9e5a56588ce69ddb170a936a9620a3603d5ce006deb264454e88312","addressRefs":[]},"b747f341-927a-4673-817d-5e895acc9eb8":{"id":"b747f341-927a-4673-817d-5e895acc9eb8","doc_no":"A.3.5.1.1","title":"Current Implementation","type":"Core","depth":4,"parentId":"9782cdc5-c274-45c2-bf4a-690f22c6a294","order":2844,"content":"The current implementation of the Surplus Buffer is the Vow contract deployed on the Ethereum Mainnet at `0xA950524441892A31ebddF91d3cEEFa04Bf454466`.","contentHash":"bc0c3c650e63d6a0ef2fa44b1d5b29373edf43e4cd6000d900e08741b35fb806","addressRefs":["0xa950524441892a31ebddf91d3ceefa04bf454466"]},"52fa11b0-7167-47c3-9678-e879dc981127":{"id":"52fa11b0-7167-47c3-9678-e879dc981127","doc_no":"A.3.5.1.1.1","title":"Current Value","type":"Core","depth":5,"parentId":"b747f341-927a-4673-817d-5e895acc9eb8","order":2845,"content":"The current value of the Surplus Buffer can be calculated using the Vat contract, Sky’s central accounting contract, located on the Ethereum Mainnet at `0x35D1b3F3D7966A1DFe207aa4514C12a259A0492B`. The current value of the Surplus Buffer is the difference between:\n\n1. The assets of the Vow contract obtained by calling the `dai` function on the Vat contract with the address of the Vow contract, and\n2. The liabilities of the Vow contract obtained by calling the `sin` function on the Vat contract with the address of the Vow contract.","contentHash":"e940e87e91ce4ce1689b7de288c1f0be7b45c86c68475bed1f0338090291bca0","addressRefs":["0x35d1b3f3d7966a1dfe207aa4514c12a259a0492b"]},"ddb90fee-2851-4bf0-b924-f1d73e30ce7a":{"id":"ddb90fee-2851-4bf0-b924-f1d73e30ce7a","doc_no":"A.3.5.2","title":"Smart Burn Engine Parameters","type":"Section","depth":3,"parentId":"3eb6f099-2736-4f62-9cb8-096a8fcca757","order":2846,"content":"The current Smart Burn Engine parameters are:\n\n- kicker.khump: -200 million USDS (Threshold of Surplus Buffer for Splitter to activate)\n- kicker.kbump: 6,000 USDS\n- splitter.hop: 13,787 seconds\n- 100% of Splitter allocation is set to accumulate SKY\n- 0% of Splitter allocation is set to reward SKY stakers\n- burn (the percentage of the kicker.kbump to be moved to the underlying flapper): 100% (WAD * 1)\n- LSEV2-SKY-A USDS rewardsDuration: 13,787 seconds\n\nThe rewardsDuration for the LSEV2-SKY-A USDS rewards contract must be set such that it is equal to the splitter.hop parameter.","contentHash":"651461cc72388503eec0d3598109100a040da4a5e9ff7e10e581e83c31888116","addressRefs":[]},"0103ec2d-56d5-4981-be23-73cc37aa57eb":{"id":"0103ec2d-56d5-4981-be23-73cc37aa57eb","doc_no":"A.3.5.2.1","title":"Splitter Module","type":"Core","depth":4,"parentId":"ddb90fee-2851-4bf0-b924-f1d73e30ce7a","order":2847,"content":"The Splitter Module splits funds transferred to it from the Surplus Buffer between accumulating SKY and paying USDS rewards to SKY stakers.","contentHash":"c00888e37f99da9dec0172661b425ddfc3a5a46fc48227504a20211cb5747eb7","addressRefs":[]},"d1f57081-28e7-4646-be12-2a4d43ff6752":{"id":"d1f57081-28e7-4646-be12-2a4d43ff6752","doc_no":"A.3.5.2.1.1","title":"Splitter Module Parameters","type":"Core","depth":5,"parentId":"0103ec2d-56d5-4981-be23-73cc37aa57eb","order":2848,"content":"The parameters of the Splitter Module are defined in the documents herein.","contentHash":"9059b209c5965f1fe4d0b45370ff6f3b33c08ccdb296a5446e224c44f2f627fa","addressRefs":[]},"39a67e65-33f0-4f2c-917d-efff544cf5ab":{"id":"39a67e65-33f0-4f2c-917d-efff544cf5ab","doc_no":"A.3.5.2.1.1.1","title":"Splitter Interval Parameter","type":"Core","depth":6,"parentId":"d1f57081-28e7-4646-be12-2a4d43ff6752","order":2849,"content":"The `hop` parameter is the time interval between `kicker.kbump` funds being transferred from the Surplus Buffer to the Splitter. Together with the `kicker.kbump` parameter, it controls the rate at which funds are transferred from the Surplus Buffer to the Splitter.","contentHash":"66f2ca4fcfcd3737a9f5932304a3ef1c166f5336580d7235c678e926a0c21399","addressRefs":[]},"ab46f478-56a8-4ef0-86a3-d0010c60b6b1":{"id":"ab46f478-56a8-4ef0-86a3-d0010c60b6b1","doc_no":"A.3.5.2.1.1.1.1","title":"Splitter Interval Current Value","type":"Core","depth":6,"parentId":"d1f57081-28e7-4646-be12-2a4d43ff6752","order":2850,"content":"The current value of the `hop` parameter is specified in [A.3.5.2 - Smart Burn Engine Parameters](ddb90fee-2851-4bf0-b924-f1d73e30ce7a).","contentHash":"cce9581c54a3df7f04286b6e0b1504371650c520ae38f6b17eddde85983c80f2","addressRefs":[]},"e16d6215-c2f1-4140-affd-30e52a17fd43":{"id":"e16d6215-c2f1-4140-affd-30e52a17fd43","doc_no":"A.3.5.2.1.1.2","title":"SKY Accumulation Percentage Parameter","type":"Core","depth":6,"parentId":"d1f57081-28e7-4646-be12-2a4d43ff6752","order":2851,"content":"The `burn` parameter is the percentage of each transfer from the Surplus Buffer to the Splitter that is sent to the Flapper contract, which accumulates SKY. The remainder of each transfer is sent to the contract for USDS rewards for SKY stakers.","contentHash":"90f45031b6eca31bacafad04ada4b6bc487faa5d21764a03f842cce42ac75f1a","addressRefs":[]},"f6b14aab-a1af-40e2-9069-2f707cbe60f0":{"id":"f6b14aab-a1af-40e2-9069-2f707cbe60f0","doc_no":"A.3.5.2.1.1.2.1","title":"SKY Accumulation Percentage Current Value","type":"Core","depth":6,"parentId":"d1f57081-28e7-4646-be12-2a4d43ff6752","order":2852,"content":"The current value of the `burn` parameter is specified in [A.3.5.2 - Smart Burn Engine Parameters](ddb90fee-2851-4bf0-b924-f1d73e30ce7a).","contentHash":"9590b5fcf1f0f1359d7a29b33f5905f369614c73bcc0cb5147b1fb49d8c9f0fc","addressRefs":[]},"92e9ad85-2bbd-4c19-bfd2-87bd8bb740c6":{"id":"92e9ad85-2bbd-4c19-bfd2-87bd8bb740c6","doc_no":"A.3.5.2.2","title":"Kicker Module","type":"Core","depth":4,"parentId":"ddb90fee-2851-4bf0-b924-f1d73e30ce7a","order":2853,"content":"The Kicker Module allows funds to be transferred from the Surplus Buffer to the Splitter as long as the Surplus Buffer is above a specified signed threshold. This allows funds to be transferred from the Surplus Buffer to the Splitter even when the Surplus Buffer is negative, as long as the Surplus Buffer is above the specified threshold.","contentHash":"cc67b97c1f2314126a59adff613fc73b0681e7d10b15167613e32d39512192d0","addressRefs":[]},"433c317d-0c92-4a3e-9734-0eb26a9a7606":{"id":"433c317d-0c92-4a3e-9734-0eb26a9a7606","doc_no":"A.3.5.2.2.1","title":"Kicker Module Parameters","type":"Core","depth":5,"parentId":"92e9ad85-2bbd-4c19-bfd2-87bd8bb740c6","order":2854,"content":"The parameters of the Kicker Module are defined in the documents herein.","contentHash":"31ea06799050f172cb163423af49f90799cc337d31bf4d7871b4c4a343f7b893","addressRefs":[]},"ec7a5067-db8f-421b-ba85-074a5fa9845b":{"id":"ec7a5067-db8f-421b-ba85-074a5fa9845b","doc_no":"A.3.5.2.2.1.1","title":"Kicker Threshold Parameter","type":"Core","depth":6,"parentId":"433c317d-0c92-4a3e-9734-0eb26a9a7606","order":2855,"content":"The `khump` parameter is the minimum value of the Surplus Buffer for funds to be transferred from the Surplus Buffer to the Splitter contract. It is a signed integer with `RAD` precision.","contentHash":"3e9d25a68072f2602cf4b7e4b9eec167363d4653bd4eaf1f96daed35c963b616","addressRefs":[]},"ce3affe8-9e1f-4825-82bd-40c320a1c220":{"id":"ce3affe8-9e1f-4825-82bd-40c320a1c220","doc_no":"A.3.5.2.2.1.1.1","title":"Kicker Threshold Current Value","type":"Core","depth":6,"parentId":"433c317d-0c92-4a3e-9734-0eb26a9a7606","order":2856,"content":"The current value of the `khump` parameter is specified in [A.3.5.2 - Smart Burn Engine Parameters](ddb90fee-2851-4bf0-b924-f1d73e30ce7a).","contentHash":"0ef83b45c99589b5a7ac5576686275077c5d87b2525f0da8fec06de4f42e40a0","addressRefs":[]},"fc9cece1-84bf-4133-a2ef-ef2182a23a35":{"id":"fc9cece1-84bf-4133-a2ef-ef2182a23a35","doc_no":"A.3.5.2.2.1.2","title":"Kicker Lot Size Parameter","type":"Core","depth":6,"parentId":"433c317d-0c92-4a3e-9734-0eb26a9a7606","order":2857,"content":"The `kbump` parameter is the amount of funds transferred from the Surplus Buffer to the Splitter every `splitter.hop` interval when the Surplus Buffer is greater than `kbump`. Together with the `splitter.hop` parameter, it controls the rate at which funds are transferred from the Surplus Buffer to the Splitter.","contentHash":"e6b81d29014ae89147e5f6a6b2852093b55749699d7c7980318f4db6d9c7328f","addressRefs":[]},"443e0ae4-11d6-43f9-9988-f0e73926bf60":{"id":"443e0ae4-11d6-43f9-9988-f0e73926bf60","doc_no":"A.3.5.2.2.1.2.1","title":"Kicker Lot Size Current Value","type":"Core","depth":6,"parentId":"433c317d-0c92-4a3e-9734-0eb26a9a7606","order":2858,"content":"The current value of the kbump parameter is specified in [A.3.5.2 - Smart Burn Engine Parameters](ddb90fee-2851-4bf0-b924-f1d73e30ce7a).","contentHash":"2a5290ac52bc868faff6f477f43eb302b74cdf31de26e908c3832e0521e5c434","addressRefs":[]},"0803e6b5-5755-431c-9ef0-999115f6f897":{"id":"0803e6b5-5755-431c-9ef0-999115f6f897","doc_no":"A.3.5.2.2.2","title":"Deployment","type":"Core","depth":5,"parentId":"92e9ad85-2bbd-4c19-bfd2-87bd8bb740c6","order":2859,"content":"The activation of the Kicker Module will be executed in the October 30, 2025 Executive Vote. This action is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"f1af871b6e283426d0c042c95316f5e74fd2d48bd5588a0b13d728daadc1eb37","addressRefs":[]},"499570de-9fae-4009-be34-c3330266030a":{"id":"499570de-9fae-4009-be34-c3330266030a","doc_no":"A.3.5.2.3","title":"Modification","type":"Core","depth":4,"parentId":"ddb90fee-2851-4bf0-b924-f1d73e30ce7a","order":2860,"content":"The parameters of the Smart Burn Engine can be modified pursuant to the Operational Weekly Cycle. The Core Facilitator, in consultation with the Core Council Risk Advisor, can propose changes to the `kbump` and `hop` parameters directly via an Executive Vote without requiring a Governance Poll. LSEV2-SKY-A-USDS rewardsDuration should always match the value of the hop parameter without requiring prior governance authorization. Changes to other parameters require a Governance Poll followed by an Executive Vote.\n\nThe Smart Burn Engine parameters must be updated as necessary to implement the allocation specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121). Such updates are authorized to proceed directly to an Executive Vote without requiring a prior Governance Poll.","contentHash":"f8619a612d16d39dc2491652726b853435e25e777ee4056825b4fdd32b6099fb","addressRefs":[]},"f45ca50a-e1d3-4504-8e40-dd45b5fb3f83":{"id":"f45ca50a-e1d3-4504-8e40-dd45b5fb3f83","doc_no":"A.3.5.3","title":"Sky Capital","type":"Section","depth":3,"parentId":"3eb6f099-2736-4f62-9cb8-096a8fcca757","order":2861,"content":"This Section defines the different types of Sky capital and rules related to that capital.","contentHash":"b0115327eff633c317a1f747e68c6f19fdd51b2e5731882d8c241a90afb6b80a","addressRefs":[]},"d6973edf-ce53-4f77-b656-677002dfd6b4":{"id":"d6973edf-ce53-4f77-b656-677002dfd6b4","doc_no":"A.3.5.3.1","title":"Capital Types","type":"Core","depth":4,"parentId":"f45ca50a-e1d3-4504-8e40-dd45b5fb3f83","order":2862,"content":"The documents herein define the different types of Sky capital.","contentHash":"4e763749fe5ff7ae2235dfe5034ff3a1a85a5defaf19a18e7a1371e084f59f43","addressRefs":[]},"cd36d152-1ba6-4958-9afd-d182e488e358":{"id":"cd36d152-1ba6-4958-9afd-d182e488e358","doc_no":"A.3.5.3.1.1","title":"Aggregate Capital Buffer","type":"Core","depth":5,"parentId":"d6973edf-ce53-4f77-b656-677002dfd6b4","order":2863,"content":"The Aggregate Capital Buffer is the sum of (1) the Sky Surplus Buffer (see [A.3.5.1 - Surplus Buffer](9782cdc5-c274-45c2-bf4a-690f22c6a294)), (2) the Core Council Buffer (see [A.2.3.1.2.2.2.1 - Core Council Buffer](8b6781d7-f35c-4ffe-b8ed-299fa98e3da7)), (3) the Aligned Delegates Buffer (see [A.2.3.1.2.2.2.2 - Aligned Delegates Buffer](05fa5c41-26ca-4c25-94dd-834ef72c318a)), and (4) the capital held in the SubProxy of each Prime Agent. The Aggregate Capital Buffer provides a useful metric for assessing the capital level of the entire Sky Ecosystem on a consolidated basis.","contentHash":"6bc849bcd047895cf7c45b64943ac8e0983fcd9f35ba4a2cba1240ac2e0fc22b","addressRefs":[]},"6dbead44-5ac4-4c5b-be3c-64eddd004e5c":{"id":"6dbead44-5ac4-4c5b-be3c-64eddd004e5c","doc_no":"A.3.5.3.1.2","title":"Aggregate Backstop Capital","type":"Core","depth":5,"parentId":"d6973edf-ce53-4f77-b656-677002dfd6b4","order":2864,"content":"Aggregate Backstop Capital is (1) the sum of the Genesis Capital held in the SubProxy of each Genesis Agent minus (2) the Allocated Genesis Capital. Aggregate Backstop Capital represents the \"safety net\" of excess capital backing USDS beyond standard collateral.","contentHash":"1bea7d4cae202702744dc59b8f8454eab059b6d01555e5652d74315900483c06","addressRefs":[]},"c3b6546e-48f9-42ac-9a6c-524ed7ac91cb":{"id":"c3b6546e-48f9-42ac-9a6c-524ed7ac91cb","doc_no":"A.3.5.3.1.3","title":"Allocated Genesis Capital","type":"Core","depth":5,"parentId":"d6973edf-ce53-4f77-b656-677002dfd6b4","order":2865,"content":"Allocated Genesis Capital is the negative of the Surplus Buffer. Allocated Genesis Capital represents the funds Sky Core has deployed into the Genesis Agents to bootstrap innovation and Agent diversity.","contentHash":"4d411405bf837eb261f29e629ac578570dd19f764cd462fa49b90ecacddec696","addressRefs":[]},"3b829981-2fe0-49dd-bfef-8a44edc9514d":{"id":"3b829981-2fe0-49dd-bfef-8a44edc9514d","doc_no":"A.3.5.3.2","title":"Capital Targets","type":"Core","depth":4,"parentId":"f45ca50a-e1d3-4504-8e40-dd45b5fb3f83","order":2866,"content":"The documents herein define capital targets for Sky and processes for achieving those targets over time.","contentHash":"09c9ab55c88096e149b7830231b35bbd8519fbd20ea59b9c4e497dc9a6eb0ca2","addressRefs":[]},"f73dda95-0b1c-4bdc-b957-469253d27281":{"id":"f73dda95-0b1c-4bdc-b957-469253d27281","doc_no":"A.3.5.3.2.1","title":"Target Aggregate Backstop Capital","type":"Core","depth":5,"parentId":"3b829981-2fe0-49dd-bfef-8a44edc9514d","order":2867,"content":"The Target Aggregate Backstop Capital is one and one half percent (1.5%) of the total supply of USDS.","contentHash":"fa589dc4bd5a81fa2e696b400f4999ec02f0637b8739643338110192b5e9c30a","addressRefs":[]},"db2aaf07-4ebb-4e5d-ae5e-575717d8fbcd":{"id":"db2aaf07-4ebb-4e5d-ae5e-575717d8fbcd","doc_no":"A.3.5.3.2.2","title":"Turbo-Fill Floor","type":"Core","depth":5,"parentId":"3b829981-2fe0-49dd-bfef-8a44edc9514d","order":2868,"content":"The current Turbo-Fill Floor for the Aggregate Backstop Capital is 150 million USDS. The Turbo-Fill Floor is the level below which an accelerated retention rate applies, as specified in [A.2.3.1.2.3 - Step 2: Aggregate Backstop Capital](2b28d464-e683-48ba-9a66-2fee05ea0a88).","contentHash":"ab7b817db96ca1619ea8f0eeccd950c3bf6798d326318e28390ed123b592da58","addressRefs":[]},"ae3b42cd-cdda-424a-b09a-87e2796538ba":{"id":"ae3b42cd-cdda-424a-b09a-87e2796538ba","doc_no":"A.3.5.3.2.3","title":"Capital Retention To Achieve Target Aggregate Backstop Capital","type":"Core","depth":5,"parentId":"3b829981-2fe0-49dd-bfef-8a44edc9514d","order":2869,"content":"When Aggregate Backstop Capital is below Target Aggregate Backstop Capital, a portion of Step 2 Capital is retained to grow Aggregate Backstop Capital, as specified in [A.2.3.1.2.3 - Step 2: Aggregate Backstop Capital](2b28d464-e683-48ba-9a66-2fee05ea0a88).","contentHash":"0ef4ba2c15bb79101879b5fe796f9b3bcc4f0a759f11f6bf3559d9977e26e4b1","addressRefs":[]},"4d8b0d82-97da-4041-b185-4b98c2779cbe":{"id":"4d8b0d82-97da-4041-b185-4b98c2779cbe","doc_no":"A.3.6","title":"SKY Backstop","type":"Article","depth":2,"parentId":"d56538fc-2220-491a-a4d2-7ad6e461d707","order":2870,"content":"This Article governs the SKY Backstop. If the USDS Stablecoin becomes undercollateralized, the Sky Protocol will automatically generate and sell SKY to recapitalize the system. The period when the recapitalization mechanism is actively minting and selling SKY to close the shortfall is termed a \"SKY Backstop Event.\"","contentHash":"993ee55a0b47f7eb16e7af0b47d46aa63df92a786c8939966dcee62d9d72f8fb","addressRefs":[]},"463b58c0-79fa-4e50-85e6-20560f3da9a3":{"id":"463b58c0-79fa-4e50-85e6-20560f3da9a3","doc_no":"A.3.6.1","title":"Emission Rate","type":"Section","depth":3,"parentId":"4d8b0d82-97da-4041-b185-4b98c2779cbe","order":2871,"content":"An emissions rate for the SKY backstop function that prevents risk of sudden failure must be defined. This must be continuously assessed and improved to maximize stability of the system in worst case scenarios.","contentHash":"7e7f9737958f460b48ffe0f086160ee84384fa7045e63b7efaab9db3c4a0473d","addressRefs":[]},"193d8b40-bb67-4f22-b452-845e63481737":{"id":"193d8b40-bb67-4f22-b452-845e63481737","doc_no":"A.3.6.1.1","title":"Limitless","type":"Core","depth":4,"parentId":"463b58c0-79fa-4e50-85e6-20560f3da9a3","order":2872,"content":"The SKY Backstop is temporarily limitless.","contentHash":"13f4636afc1ad8b54a049c3f20f67d7414060b0749f5d94bed1171ddf4c0d510","addressRefs":[]},"0e898ec0-e618-4deb-a7cb-f5ca47c00e71":{"id":"0e898ec0-e618-4deb-a7cb-f5ca47c00e71","doc_no":"A.3.6.2","title":"Maximum Level Of Emission","type":"Section","depth":3,"parentId":"4d8b0d82-97da-4041-b185-4b98c2779cbe","order":2873,"content":"A maximum level of SKY emission per undercollateralization event must be defined. This must be continuously assessed and improved to maximize stability of the system in worst-case scenarios.","contentHash":"7296611873d4fe1c75bc7b2ba65c9ae80ebd3bec55f5e15f627a4ad07f3780bf","addressRefs":[]},"ed24e054-5c3f-4fc5-9992-d19462a47052":{"id":"ed24e054-5c3f-4fc5-9992-d19462a47052","doc_no":"A.3.6.3","title":"Override Mechanism","type":"Section","depth":3,"parentId":"4d8b0d82-97da-4041-b185-4b98c2779cbe","order":2874,"content":"The Protocol must include an override mechanism that allows Sky Governance to continue emitting SKY beyond the maximum level. This Section must specify research processes and principles to guide when and how the override mechanism can be safely used.","contentHash":"b808de2c47c2267639c61c152e0a47d3f3ac88ccc69c02b78836f1cd440f30e2","addressRefs":[]},"28f36566-e26e-4b51-bf68-f6ddd584c172":{"id":"28f36566-e26e-4b51-bf68-f6ddd584c172","doc_no":"A.3.6.4","title":"Halt Mechanism","type":"Section","depth":3,"parentId":"4d8b0d82-97da-4041-b185-4b98c2779cbe","order":2875,"content":"The Protocol must contain a SKY backstop halt mechanism that immediately halts the backstop event in case of severe risk of total failure.","contentHash":"c8cabb3e8d56df912feac668dd497f7ea4edef8796035178935fea882ac3955a","addressRefs":[]},"1008d9c7-98be-4fde-9473-5a5441160a20":{"id":"1008d9c7-98be-4fde-9473-5a5441160a20","doc_no":"A.3.6.5","title":"Mitigate Worst Case Scenario","type":"Section","depth":3,"parentId":"4d8b0d82-97da-4041-b185-4b98c2779cbe","order":2876,"content":"In case the backstop limit is reached and not overridden, or in case the backstop is halted during the event, the USDS target price receives a haircut to settle the remaining bad debt of the system. This Section must define elements and infrastructure to address this worst-case scenario, including research concerning ways to mitigate damage.","contentHash":"3aa7f75b7bb1f1199f597879e42a1f7a2140eedffad666f8e4a89a4f2321790f","addressRefs":[]},"5e795fa2-77d7-4f2a-8494-545d4bb2d955":{"id":"5e795fa2-77d7-4f2a-8494-545d4bb2d955","doc_no":"A.3.6.6","title":"Relation To Genesis Capital Backstop","type":"Section","depth":3,"parentId":"4d8b0d82-97da-4041-b185-4b98c2779cbe","order":2877,"content":"The SKY Backstop may not be invoked unless the Genesis Capital Backstop (see [A.3.7.1.6 - Genesis Capital Backstop](a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98)) has been applied and USDS remains undercollateralized.","contentHash":"c4e353400c913d5d299883cdaa98253b3ca520ba377019c249feeda0f1831f18","addressRefs":[]},"94ed62af-6e69-4831-938a-69963e6c0a1f":{"id":"94ed62af-6e69-4831-938a-69963e6c0a1f","doc_no":"A.3.7","title":"Measures For Endgame Transition","type":"Article","depth":2,"parentId":"d56538fc-2220-491a-a4d2-7ad6e461d707","order":2878,"content":"This Article defines temporary measures for implementing the Stability Scope during the transition to the Endgame State.","contentHash":"44cbd1326830edd42a196ba33359279f8c5c8ee4cd6444caa02c5ad4ef8deaf7","addressRefs":[]},"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8":{"id":"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8","doc_no":"A.3.7.1","title":"Measures For Endgame Transition","type":"Section","depth":3,"parentId":"94ed62af-6e69-4831-938a-69963e6c0a1f","order":2879,"content":"This Section defines temporary measures to give effect to the Stability Scope during the Endgame transition.","contentHash":"bd64fd9f51cd5b6b13ec8b5ae1e0df63333140214ee042890bc8bdbd10e649d4","addressRefs":[]},"950c138e-c5f6-4ff9-92c0-35a3e1ef0ad3":{"id":"950c138e-c5f6-4ff9-92c0-35a3e1ef0ad3","doc_no":"A.3.7.1.1","title":"Native Vault Engine","type":"Core","depth":4,"parentId":"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8","order":2880,"content":"The Sky Core Vaults are gradually being deprecated over time to incentivize users to migrate to SparkLend and other borrowing platforms offered by Prime Agents (see [A.3.7.1.1.2.3 - Stability Fee](0257a420-e92e-4942-b794-a559f299365f)). During the transition period, the Core Vaults will have a limited set of collateral types and risk parameters that Core GovOps, in consultation with the Core Council Risk Advisor, must implement according to the following subdocuments.","contentHash":"a9dec06e7da2d4c9fdc66df254dd523edbb1bd8a409a7889fa1b17249113ef89","addressRefs":[]},"64971463-0650-4462-b9c4-1eecb704fa1a":{"id":"64971463-0650-4462-b9c4-1eecb704fa1a","doc_no":"A.3.7.1.1.1","title":"Vault Types","type":"Core","depth":5,"parentId":"950c138e-c5f6-4ff9-92c0-35a3e1ef0ad3","order":2881,"content":"The collateral types of the Native Vault Engine and their parameters are defined in the subdocuments herein.","contentHash":"ff3faac07ef8b28b3e4b9b50c797496d042a74958b8e21c12620fa64a792a9db","addressRefs":[]},"f97321f8-c677-4a6c-aa87-8f9a93f8acd3":{"id":"f97321f8-c677-4a6c-aa87-8f9a93f8acd3","doc_no":"A.3.7.1.1.1.1","title":"ETH-A","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2882,"content":"Current ETH-A parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 145%,\n- DC-IAM `line`: 15,000,000,000 Dai,\n- DC-IAM `gap`: 150,000,000 Dai,\n- DC-IAM `ttl`: 21,600 seconds,\n- `cut`: 99.00%,\n- `step`: 90 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 7,200 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 13%,\n- `hole`: 40,000,000 Dai,\n- `dust`: 7,500 Dai","contentHash":"a9d1aa4af40e13116d83c17b86543d88672b4277418dd9523e06fc912c8badf2","addressRefs":[]},"87fd7fd2-495f-452f-abed-4a887ba02c7c":{"id":"87fd7fd2-495f-452f-abed-4a887ba02c7c","doc_no":"A.3.7.1.1.1.2","title":"ETH-B","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2883,"content":"Current ETH-B parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 130%,\n- DC-IAM `line`: 250,000,000 Dai,\n- DC-IAM `gap`: 20,000,000 Dai,\n- DC-IAM `ttl`: 21,600 seconds,\n- `cut`: 99.00%,\n- `step`: 60 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 4,800 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 13%,\n- `hole`: 15,000,000 Dai,\n- `dust`: 25,000 Dai","contentHash":"9de4206b5d7a8784f9c1327a47ccd4a37b73a63474bc4e2b51a0274dacd58f83","addressRefs":[]},"896ce563-a4f1-4a9d-ad23-fc5840ea2f28":{"id":"896ce563-a4f1-4a9d-ad23-fc5840ea2f28","doc_no":"A.3.7.1.1.1.3","title":"ETH-C","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2884,"content":"Current ETH-C parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 170%,\n- DC-IAM `line`: 2,000,000,000 Dai,\n- DC-IAM `gap`: 100,000,000 Dai,\n- DC-IAM `ttl`: 28,800 seconds,\n- `cut`: 99.00%,\n- `step`: 90 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 7,200 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 13%,\n- `hole`: 35,000,000 Dai,\n- `dust`: 3,500 Dai","contentHash":"682c2c7a92f210edaaf5932839a780eab65461a4238c69cc01e7bccd2e64beb7","addressRefs":[]},"1dbc84b7-a17e-40af-aef5-63a9b78e85b3":{"id":"1dbc84b7-a17e-40af-aef5-63a9b78e85b3","doc_no":"A.3.7.1.1.1.4","title":"WSTETH-A","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2885,"content":"Current WSTETH-A parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 150%,\n- DC-IAM `line`: 750,000,000 Dai,\n- DC-IAM `gap`: 30,000,000 Dai,\n- DC-IAM `ttl`: 43,200 seconds,\n- `cut`: 99.00%,\n- `step`: 90 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 7,200 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 13%,\n- `hole`: 30,000,000 Dai,\n- `dust`: 7,500 Dai","contentHash":"9819e106b074a230b3239bf31d2034f979022c1c5707e2dc30604ed1528da464","addressRefs":[]},"cfb76935-bcd4-4973-967c-7625c1524e58":{"id":"cfb76935-bcd4-4973-967c-7625c1524e58","doc_no":"A.3.7.1.1.1.5","title":"WSTETH-B","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2886,"content":"Current WSTETH-B parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 175%,\n- DC-IAM `line`: 1,000,000,000 Dai,\n- DC-IAM `gap`: 45,000,000 Dai,\n- DC-IAM `ttl`: 43,200 seconds,\n- `cut`: 99.00%,\n- `step`: 90 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 7,200 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 13%,\n- `hole`: 20,000,000 Dai,\n- `dust`: 3,500 Dai","contentHash":"8c435c0ff84d11a8fa79a174cc8c3017ef555de978af87c433da7d79919908ba","addressRefs":[]},"dba74f38-58f3-432a-b14b-bf5bc95ac5ed":{"id":"dba74f38-58f3-432a-b14b-bf5bc95ac5ed","doc_no":"A.3.7.1.1.1.6","title":"WBTC-A","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2887,"content":"Current WBTC-A parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 150%,\n- DC-IAM `line`: 0 Dai,\n- DC-IAM `gap`: 4,000,000 Dai,\n- DC-IAM `ttl`: 86,400 seconds,\n- `cut`: 99.00%,\n- `step`: 90 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 7,200 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 0%,\n- `hole`: 10,000,000 Dai,\n- `dust`: 7,500 Dai","contentHash":"c87482a55db67df18f6ce59724db221e90044f7538fa5631a8008f6e8e99ec92","addressRefs":[]},"307ba340-c3d3-42c8-8121-e98c5de607d0":{"id":"307ba340-c3d3-42c8-8121-e98c5de607d0","doc_no":"A.3.7.1.1.1.7","title":"WBTC-B","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2888,"content":"Current WBTC-B parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 150%,\n- DC-IAM `line`: 0 Dai,\n- DC-IAM `gap`: 2,000,000 Dai,\n- DC-IAM `ttl`: 86,400 seconds,\n- `cut`: 99.00%,\n- `step`: 60 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 4,800 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 0%,\n- `hole`: 5,000,000 Dai,\n- `dust`: 25,000 Dai","contentHash":"1c9753412cd3741cf70ac148b1a8c6b785b6c4c6b5edde5092dc7803a1a2aa57","addressRefs":[]},"2f42fd1f-a79b-4208-ac07-bbfa9a447c18":{"id":"2f42fd1f-a79b-4208-ac07-bbfa9a447c18","doc_no":"A.3.7.1.1.1.8","title":"WBTC-C","type":"Core","depth":6,"parentId":"64971463-0650-4462-b9c4-1eecb704fa1a","order":2889,"content":"Current WBTC-C parameters are:\n\n- Stability Fee: set by the SP-BEAM specified in A.3.9 - Measures For Endgame Transition - Stability Parameter Bounded External Access Module,\n- Liquidation Ratio: 175%,\n- DC-IAM `line`: 0 Dai,\n- DC-IAM `gap`: 8,000,000 Dai,\n- DC-IAM `ttl`: 86,400 seconds,\n- `cut`: 99.00%,\n- `step`: 90 seconds,\n- `buf`: 110.00%,\n- `cusp`: 45.00%,\n- `tail`: 7,200 seconds,\n- `chip`: 0.10%,\n- `tip`: 250,\n- `chop`: 0%,\n- `hole`: 10,000,000 Dai,\n- `dust`: 3,500 Dai","contentHash":"19946a59791394c7e682a40f0159166aa4c3b26102a75a402c2ad3dfd3984422","addressRefs":[]},"8eb26d06-d2b3-493f-a79f-e3509326ddc6":{"id":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","doc_no":"A.3.7.1.1.2","title":"Risk Parameter Definitions","type":"Core","depth":5,"parentId":"950c138e-c5f6-4ff9-92c0-35a3e1ef0ad3","order":2890,"content":"The Native Vault Engine risk parameters are defined in the subdocuments herein.","contentHash":"805b7b97282a3680108c5cfb98d403207ba2566b5d3f553c640e90dcf471c185","addressRefs":[]},"9ce4d08e-aa5b-4cab-884e-7a53e937bdb8":{"id":"9ce4d08e-aa5b-4cab-884e-7a53e937bdb8","doc_no":"A.3.7.1.1.2.1","title":"Liquidation Ratio","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2891,"content":"The Liquidation Ratio parameter limits the maximum amount of Dai debt that a vault user can draw from their vault given the value of their collateral locked in that vault. In practice, it expresses the minimum collateral in percentage terms that can support a given Dai debt. If the ratio of a Vault user's collateral to their debt drops below this value, their vault can be liquidated. Each vault type has its own Liquidation Ratio. The Liquidation Ratio for each vault type is expressed as a percentage value of the collateral that must be present in the vault to support its debt.\n\nChanges to the Liquidation Ratio are subject to the Operational Weekly Cycle, requiring a Governance Poll followed by an Executive Vote.","contentHash":"50c39d007581f21e951a9857a453b5c5d87c2c7c9fc68f31ee4efa3cf300e20f","addressRefs":[]},"b490d4d0-8eb8-4dc6-9ef3-c85d357f1f4b":{"id":"b490d4d0-8eb8-4dc6-9ef3-c85d357f1f4b","doc_no":"A.3.7.1.1.2.2","title":"Debt Ceiling Limit","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2892,"content":"The Debt Ceiling Limit is numerically provided and acts as an upper limit. Core GovOps, in consultation with the Core Council Risk Advisor, can propose changes within this limit.\n\nDebt Ceiling Limit = Unlimited is defined as large enough to avoid being reached in the near future.\n\nThe DC-IAM methodology contained in [A.3.7.1.1.2.4 - Debt Ceiling Instant Access Module (DC-IAM)](93c9f662-4e0d-477e-8fc9-e3726877e842) acts as a risk mitigation tool. It limits the rate at which exposure can increase in a short period of time in the event of an unexpected emergency.","contentHash":"b222ceeca0e7e918520de83144e8fb899d36e825fccc26830f7857a7efc49aa6","addressRefs":[]},"0257a420-e92e-4942-b794-a559f299365f":{"id":"0257a420-e92e-4942-b794-a559f299365f","doc_no":"A.3.7.1.1.2.3","title":"Stability Fee","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2893,"content":"The Stability Fee parameter is an annual percentage fee charged on the Dai generated on Vaults. It is expressed as an annual percentage yield but it is charged on a per-block basis in Dai. The Dai from this fee is minted, added to the Dai debt for the vault, and then transferred into the Surplus Buffer which is under the control of Sky Governance. Each vault type has its own Stability Fee that can be adjusted independently.\n\nThe Stability Fees can be modified through either Executive Votes or the Stability Parameter Bounded External Access Module. See [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n\nThe Stability Fees must be gradually increased over time to incentivize users to migrate to SparkLend and other borrowing platforms offered by Prime Agents.","contentHash":"e25209913825bab95338584473b83c83705bba808a325b327f7792862518073e","addressRefs":[]},"93c9f662-4e0d-477e-8fc9-e3726877e842":{"id":"93c9f662-4e0d-477e-8fc9-e3726877e842","doc_no":"A.3.7.1.1.2.4","title":"Debt Ceiling Instant Access Module (DC-IAM)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2894,"content":"The DC-IAM allows any user to adjust the Debt Ceiling of a supported vault type according to the rules defined in the DC-IAM smart contract logic and parameters set by the Stability Facilitators. The DC-IAM holds three parameters that can be set by Sky Governance for each vault type, (i) Maximum Debt Ceiling (`line`), (ii) Target Available Debt (`gap`), and (iii) Ceiling Increase Cooldown (`ttl`).","contentHash":"aafce24c6d6e3563dfb5789b5d34b5bdd5192c4e88f57a27b1a1cc245c52b0bb","addressRefs":[]},"6ba18f25-dae8-4fa5-929e-3c7071b70107":{"id":"6ba18f25-dae8-4fa5-929e-3c7071b70107","doc_no":"A.3.7.1.1.2.4.1","title":"Maximum Debt Ceiling (line)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2895,"content":"The `line` parameter refers to the maximum value for the Debt Ceiling that the DC-IAM will allow in the given vault type. When using the DC-IAM to manage the Debt Ceiling of a vault type, the `line` parameter essentially replaces the Debt Ceiling parameter for that vault type. Rather than Sky Governance setting the Debt Ceiling directly, they will need to set the Maximum Debt Ceiling `line` in the DC-IAM. The `line` parameter is defined in Dai.\n\nThe Maximum Debt Ceiling is defined in [A.3.7.1.1.2.2 - Debt Ceiling Limit](b490d4d0-8eb8-4dc6-9ef3-c85d357f1f4b) and is currently unlimited.","contentHash":"99542607c532a2d10d5cb07fcaffb2de9ca269d82468d917f3b6a6ac2e80da17","addressRefs":[]},"07353080-4346-4ffd-bfc8-913cac78776a":{"id":"07353080-4346-4ffd-bfc8-913cac78776a","doc_no":"A.3.7.1.1.2.4.2","title":"Target Available Debt (gap)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2896,"content":"The `gap` parameter controls how much of a gap the DC-IAM aims to maintain between the current debt usage and the Debt Ceiling of the vault type. The higher this value, the more risk there is from large collateral drops in very short amounts of time. The smaller this value, the more vault use is negatively affected. The `gap` parameter is defined in Dai.","contentHash":"1b87261bf3ffe5e1670863383c6fb5d01ba883145e3361781225c8338155def2","addressRefs":[]},"a5ae79ad-9460-41a3-8dbf-65605f54b79b":{"id":"a5ae79ad-9460-41a3-8dbf-65605f54b79b","doc_no":"A.3.7.1.1.2.4.3","title":"Ceiling Increase Cooldown (ttl)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2897,"content":"The Ceiling Increase Cooldown (`ttl`) parameter controls how frequently the Debt Ceiling can be increased by the DC-IAM. If a user attempts to use the DC-IAM to increase the Debt Ceiling of a vault type before this time expires, the transaction will fail to execute and the Debt Ceiling will remain unchanged. The `ttl` parameter in combination with the `gap` parameter enforces a maximum rate at which debt usage can increase over time using a given vault type. These parameters should be set such that the maximum increase over time can accommodate all reasonable usage of the vault type in question. The `ttl` parameter is defined in seconds.","contentHash":"8b6b2502e1d244904fe5ff0e84d0d112d32e9376a7a583c15a5faebd5b3a24a6","addressRefs":[]},"5774fd7c-ecd9-46ea-b33d-77ea9c6de4f3":{"id":"5774fd7c-ecd9-46ea-b33d-77ea9c6de4f3","doc_no":"A.3.7.1.1.2.5","title":"Auction Parameters","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2898,"content":"A clear justification and analysis must be provided to validate any proposed changes to the parameters specified in this document. Before these changes are added to an Executive Vote, Core GovOps, in consultation with the Core Council Risk Advisor, must obtain approval through a Governance Poll. However, in an emergency, Core GovOps, in consultation with the Core Council Risk Advisor, has the authority to bypass the Governance Poll and add the proposed parameters directly to an Executive Vote. The parameters contained herein must be regularly monitored and updated if needed.","contentHash":"1e16919d93cc3ac6eccf78b6aa826ca7c0ed589e290d6f22bd4e26c576948f17","addressRefs":[]},"fc7341c8-5a58-4be4-be8c-201f858e3861":{"id":"fc7341c8-5a58-4be4-be8c-201f858e3861","doc_no":"A.3.7.1.1.2.5.1","title":"Auction Price Function (calc)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2899,"content":"The Auction Price Function is the mathematical function that determines how the collateral price changes over time during a collateral auction. Collateral auctions use a falling price auction, where the price starts high and decreases according to the function defined in this parameter.\n\nThe Exponential Stair Step function contains two key parameters, `cut` and `step`, defined in [A.3.7.1.1.2.5.1.1 - Auction Price Function (cut)](1ff3ceac-abd0-4195-9a60-a4aaf48c3d31) and [A.3.7.1.1.2.5.1.2 - Auction Price Function (step)](4b46633c-4d6c-4a9c-9be0-93d242ce9db9), respectively.","contentHash":"c8ecf1a72068c2e08781b4c7eef12a27e5ae679f200bbce8bf18b83b1d3734aa","addressRefs":[]},"1ff3ceac-abd0-4195-9a60-a4aaf48c3d31":{"id":"1ff3ceac-abd0-4195-9a60-a4aaf48c3d31","doc_no":"A.3.7.1.1.2.5.1.1","title":"Auction Price Function (cut)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2900,"content":"The `cut` parameter controls the ‘depth’ of each step in the function. A smaller `cut` means a smoother line; a large one means more pronounced steps. The `cut` parameter is defined as a multiplicative factor. For example, 0.99 equated to a 1% price drop.","contentHash":"8ac804b8ee940cdbffce0ae2c37c5d204afbe4dbb6b644ed429fa1f31a575f28","addressRefs":[]},"4b46633c-4d6c-4a9c-9be0-93d242ce9db9":{"id":"4b46633c-4d6c-4a9c-9be0-93d242ce9db9","doc_no":"A.3.7.1.1.2.5.1.2","title":"Auction Price Function (step)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2901,"content":"The `step` parameter controls the length of time between price drops. A smaller step means a smoother line; a large one means more pronounced steps. The `step` parameter is defined in seconds.","contentHash":"58ab739cc09fb35f0d981dda4735c802b7e77aa5ac5f47efa479e52d14b3109a","addressRefs":[]},"2bcdc1c9-6e43-4059-8a46-0a68c17f487d":{"id":"2bcdc1c9-6e43-4059-8a46-0a68c17f487d","doc_no":"A.3.7.1.1.2.5.2","title":"Auction Price Multiplier (buf)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2902,"content":"The `buf` parameter is a multiplier that is applied to the starting price of a collateral auction. Each vault type has its own Auction Price Multiplier that can be adjusted by Sky Governance separately. This multiplier is intended to be greater than 1.0x because Liquidations 2.0 uses falling price auctions. This means that it is generally preferable for the auction price to begin above the market price and then fall to the correct value over some amount of time. The `buf` parameter is defined as a multiplicative factor.","contentHash":"cd838c9c150d1363178fec44141b4ffac790a750fa1279fcc756fb53e2ae2e80","addressRefs":[]},"fc472dd5-3c2a-4335-ad2f-4988dbeb1c89":{"id":"fc472dd5-3c2a-4335-ad2f-4988dbeb1c89","doc_no":"A.3.7.1.1.2.5.3","title":"Max Auction Drawdown (cusp)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2903,"content":"The Max Auction Drawdown is the maximum percentage drop in collateral price during a collateral auction before the auction is reset. 'Collateral price' in this context refers to the collateral auction price rather than the collateral market price.\n\nThe Max Auction Drawdown parameter overlaps with the Max Auction Duration parameter in that an auction will need to be reset once either maximum is exceeded.","contentHash":"ed16370bed39775c4657e9b5238a7d1392acadc8f1e397b4696d9f879ae91b29","addressRefs":[]},"cd5a3cb9-e658-4bc5-8f82-b4dab52f32d9":{"id":"cd5a3cb9-e658-4bc5-8f82-b4dab52f32d9","doc_no":"A.3.7.1.1.2.5.4","title":"Max Auction Duration (tail)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2904,"content":"The Max Auction Duration parameter sets the maximum time that can elapse before an auction needs to reset for a particular vault type. Expressed in seconds, this parameter determines when an auction can no longer settle and must be reset.\n\nThe Max Auction Duration parameter overlaps with the Max Auction Drawdown parameter in that an auction will need to be reset once either maximum is exceeded.","contentHash":"f38446b399f815d51b39119b535fac6f65c546ea543a0e6781be9610c5664534","addressRefs":[]},"e92d5797-9d72-455b-95a3-7fca9bb68071":{"id":"e92d5797-9d72-455b-95a3-7fca9bb68071","doc_no":"A.3.7.1.1.2.5.5","title":"Proportional Kick Incentive (chip)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2905,"content":"The Proportional Kick Incentive parameter represents a reward in Dai paid to the keepers that trigger collateral liquidation auctions in the Sky Protocol. The Proportional Kick Incentive is set as a percentage and represents a portion of Dai based on the debt of the vault that is being liquidated. The Dai is rewarded for each liquidation auction at the point the auction is triggered. Each vault type has its own Proportional Kick Incentive that may be adjusted separately by Sky Governance.","contentHash":"93fa05fe9f821b18673f6ccf5ec00897b866260eba6cb45d70ff95d8d5bee027","addressRefs":[]},"e883adc9-b624-438b-8a4b-981ffe741478":{"id":"e883adc9-b624-438b-8a4b-981ffe741478","doc_no":"A.3.7.1.1.2.5.6","title":"Flat Kick Incentive (tip)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2906,"content":"The Flat Kick Incentive parameter represents a reward in Dai paid to the keepers that trigger collateral liquidation auctions in the Sky Protocol. The Flat Kick Incentive is a fixed amount of Dai that is rewarded for each liquidation auction at the point the auction is triggered. Each vault type has its own Flat Kick Incentive that may be adjusted separately by Sky Governance.","contentHash":"2cafa61af4ae973ca1ad6a16395922e892f596eb90daf3870d469dac29bc2fd7","addressRefs":[]},"7f2f2eba-1933-4974-8436-54372d3188b1":{"id":"7f2f2eba-1933-4974-8436-54372d3188b1","doc_no":"A.3.7.1.1.2.5.7","title":"Liquidation Penalty (chop)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2907,"content":"The Liquidation Penalty parameter controls the fee vault owners must pay when their position is liquidated due to insufficient collateral. For a vault holder to receive any collateral back from the liquidations process, the debt and Liquidation Penalty must be covered by the collateral auction. Each vault type has its own Liquidation Penalty that can be adjusted by Sky Governance.","contentHash":"2dcbebd772fc6e75d9f2d0ac39a4a4231f03e8232a0ad9a994f6c9229f48e6eb","addressRefs":[]},"5d10220e-0541-4537-82d2-d853fa65ec97":{"id":"5d10220e-0541-4537-82d2-d853fa65ec97","doc_no":"A.3.7.1.1.2.5.8","title":"Local Liquidation Limit (hole)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2908,"content":"The Local Liquidation Limit sets the maximum amount of Dai debt for which collateral auctions can be active at any one time within a particular vault type. When the total Dai value of auctions exceeds this maximum for a particular vault type, no more collateral can be auctioned using that vault type until others are completed. Each vault type has a separate Local Liquidation Limit.","contentHash":"820b8d7a4e38a0666449ece123fb78d956be9a030385dd97f850f80dec63567c","addressRefs":[]},"d6e0c32d-aea2-4bc7-9ec3-97d54bdbd9a7":{"id":"d6e0c32d-aea2-4bc7-9ec3-97d54bdbd9a7","doc_no":"A.3.7.1.1.2.6","title":"Debt Floor (dust)","type":"Core","depth":6,"parentId":"8eb26d06-d2b3-493f-a79f-e3509326ddc6","order":2909,"content":"The Debt Floor parameter controls the minimum amount of Dai that can be minted using a specific vault type for an individual vault. If a user tries to mint Dai and the amount of Dai minted would not put the vault's amount of Dai minted above its Debt Floor, the transaction will fail and no DAi will be minted. Likewise, if a user attempts to pay back debt such that their debt will equal less than the Debt Floor and greater than zero, the transaction will fail and no Dai will be paid back. Each vault type has its own Debt Floor that can be adjusted by Sky Governance.","contentHash":"d752c182135f35ddd25036e586a06296e4f12b4f4dad783fdf40ecf811442836","addressRefs":[]},"05f29c65-4d92-43b3-aacb-3dd75b9f6794":{"id":"05f29c65-4d92-43b3-aacb-3dd75b9f6794","doc_no":"A.3.7.1.1.3","title":"Collateral Offboarding","type":"Core","depth":5,"parentId":"950c138e-c5f6-4ff9-92c0-35a3e1ef0ad3","order":2910,"content":"The processes for offboarding Native Vault Engine collateral are defined in the subdocuments herein.","contentHash":"ed99fbd7144f64165129f152431ae3f6ef14fa712390d22cdbfe3365104640f1","addressRefs":[]},"2c7a4db9-497e-4ed5-b91b-9543af3d58b3":{"id":"2c7a4db9-497e-4ed5-b91b-9543af3d58b3","doc_no":"A.3.7.1.1.3.1","title":"Offboarding Low Usage Collateral","type":"Core","depth":6,"parentId":"05f29c65-4d92-43b3-aacb-3dd75b9f6794","order":2911,"content":"To protect the Protocol from unnecessary complexity, the Stability Facilitators must offboard collateral types specified in [A.3.7.1.1.1 - Vault Types](64971463-0650-4462-b9c4-1eecb704fa1a) if they fall below a total debt of 20 million.","contentHash":"d27e553271939e1387285b443d58739e5aabe555092fbb522af2ad5bc4882990","addressRefs":[]},"f6762223-29f3-46c1-8fa4-a5c27636772d":{"id":"f6762223-29f3-46c1-8fa4-a5c27636772d","doc_no":"A.3.7.1.1.3.2","title":"Offboarding WBTC Collateral","type":"Core","depth":6,"parentId":"05f29c65-4d92-43b3-aacb-3dd75b9f6794","order":2912,"content":"WBTC-A, WBTC-B and WBTC-C are defined in [A.3.7.1.1.1 - Vault Types](64971463-0650-4462-b9c4-1eecb704fa1a) only for the purpose of Stability Fee consistency. These are otherwise not considered Native Vault Engine collateral and should be offboarded according to [A.3.7.1.1.3.3 - Offboarding Other Collateral](fe6595fc-173a-4d75-83ca-9f29dbbb63a3).","contentHash":"b1f0ecc9edffc9b7811a81bdd2b459a95835752be6c32ba65d0a6392e941a07f","addressRefs":[]},"fe6595fc-173a-4d75-83ca-9f29dbbb63a3":{"id":"fe6595fc-173a-4d75-83ca-9f29dbbb63a3","doc_no":"A.3.7.1.1.3.3","title":"Offboarding Other Collateral","type":"Core","depth":6,"parentId":"05f29c65-4d92-43b3-aacb-3dd75b9f6794","order":2913,"content":"All other collateral types should be offboarded when the Stability Facilitators deem it appropriate and when new mechanisms are in place to take over the roles previously covered by the offboarded collateral.","contentHash":"98801df547d6e3cc70d81a1d0a37f5c4ab82e90e1635fc9ae7f5edf26d520135","addressRefs":[]},"9f87ff7a-d3a8-4999-ae20-b4c0773c732c":{"id":"9f87ff7a-d3a8-4999-ae20-b4c0773c732c","doc_no":"A.3.7.1.1.3.4","title":"Collateral Offboarding Process","type":"Core","depth":6,"parentId":"05f29c65-4d92-43b3-aacb-3dd75b9f6794","order":2914,"content":"The Stability Facilitators, in consultation with the Core Council Risk Advisor, must use the Operational Weekly Cycle to offboard Native Vault Engine collateral pursuant to [A.3.7.1.1.3 - Collateral Offboarding](05f29c65-4d92-43b3-aacb-3dd75b9f6794) and its subdocuments.","contentHash":"32b3541586a0546770cd7b6ea61eb962b5d0e3cb8fca39cdd41816592341c7e6","addressRefs":[]},"a38e05bf-0820-4916-a71c-cff4f54e45df":{"id":"a38e05bf-0820-4916-a71c-cff4f54e45df","doc_no":"A.3.7.1.1.4","title":"Oracles","type":"Core","depth":5,"parentId":"950c138e-c5f6-4ff9-92c0-35a3e1ef0ad3","order":2915,"content":"The Native Vault Engine collateral types of ETH, STETH, WBTC will specifically use the Chronicle v3 oracle solution, until at least January 1st 2026. The Native Vault Engine collateral types must be migrated to the new version of the Chronicle v3 oracle when it is feasible to do so.\n\nOther oracle solutions, including diversified oracles, will only be considered until January 1st, 2026, and only if there are unresolvable security concerns with the Chronicle v3 oracles.","contentHash":"a1e5fc6d8788fde895f824226f6cbc658414a67853d65ced3bcb6897b2a897d3","addressRefs":[]},"2107f160-751d-4fea-abc0-f0bef76a30d5":{"id":"2107f160-751d-4fea-abc0-f0bef76a30d5","doc_no":"A.3.7.1.1.5","title":"Updates","type":"Core","depth":5,"parentId":"950c138e-c5f6-4ff9-92c0-35a3e1ef0ad3","order":2916,"content":"If not otherwise specified, Core GovOps, in consultation with the Core Council Risk Advisor, has the ability to modify any of the parameters defined in [A.3.7.1.1.2 - Risk Parameter Definitions](8eb26d06-d2b3-493f-a79f-e3509326ddc6) for any of the Vault Types in [A.3.7.1.1.1 - Vault Types](64971463-0650-4462-b9c4-1eecb704fa1a). As a general rule, the modification of said parameters is pursuant to the Operational Weekly Cycle and can be effected directly via an Executive Vote, without requiring a Governance Poll. Exceptions to this general rule must be clearly stated in the relevant Atlas document.","contentHash":"7e48760bab10b905a2f5f39fb5d1cc6d2b482114a351a6e620fca0f93aaacc60","addressRefs":[]},"1c09308d-b7cd-495c-b547-baf628a6e323":{"id":"1c09308d-b7cd-495c-b547-baf628a6e323","doc_no":"A.3.7.1.2","title":"Prime Allocator Vaults","type":"Core","depth":4,"parentId":"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8","order":2917,"content":"The subdocuments herein govern the Allocator Vaults utilized by Prime Agents to access Sky Ecosystem liquidity. These documents define the specific risk parameters for each vault and the governance process for updating them.","contentHash":"96cd068ef4c5df96c76dc9a0e507df527f9630e829288bae36d59b273d58c8cb","addressRefs":[]},"305a31ea-ae42-478f-8a92-94d7e9d88067":{"id":"305a31ea-ae42-478f-8a92-94d7e9d88067","doc_no":"A.3.7.1.2.1","title":"Prime Allocator Vault Risk Parameters","type":"Core","depth":5,"parentId":"1c09308d-b7cd-495c-b547-baf628a6e323","order":2918,"content":"The subdocuments herein define the risk parameters for each active Allocator Vault.","contentHash":"a7e141022f2f92567c74bf7da337df499f591616e94a9bfee3f1fe75e2d2ee34","addressRefs":[]},"47d69b3d-a650-4dcd-a8f7-0c4f6bf5e8d2":{"id":"47d69b3d-a650-4dcd-a8f7-0c4f6bf5e8d2","doc_no":"A.3.7.1.2.1.1","title":"ALLOCATOR-SPARK-A Parameters","type":"Core","depth":6,"parentId":"305a31ea-ae42-478f-8a92-94d7e9d88067","order":2919,"content":"The parameters for the Spark Allocator Vault are:\n\n- `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n- `line`: controlled by DC-IAM\n- DC-IAM parameters:\n    - `gap`: 500 million USDS\n    - `line`: 10 billion USDS\n    - `ttl`: 24 hours","contentHash":"4c0bc7a3f02fbe3098cea0efec6c62968ae69ec2142aa5b4be87b9f2cdc3f31a","addressRefs":[]},"53cba245-68c6-4af9-a280-b200dabebec7":{"id":"53cba245-68c6-4af9-a280-b200dabebec7","doc_no":"A.3.7.1.2.1.2","title":"ALLOCATOR-BLOOM-A Parameters","type":"Core","depth":6,"parentId":"305a31ea-ae42-478f-8a92-94d7e9d88067","order":2920,"content":"The parameters for the Grove Allocator Vault are:\n\n- `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n- `line`: controlled by DC-IAM\n- DC-IAM parameters:\n    - `gap`: 500 million USDS\n    - `line`: 5 billion USDS\n    - `ttl`: 24 hours","contentHash":"2fb8367b65e49339e77263e631a45fb33c91ed731e1787d4ded1d1d6beff824a","addressRefs":[]},"08321783-f31a-4a80-8f0c-898afb4d8f9b":{"id":"08321783-f31a-4a80-8f0c-898afb4d8f9b","doc_no":"A.3.7.1.2.1.3","title":"ALLOCATOR-NOVA-A Parameters","type":"Core","depth":6,"parentId":"305a31ea-ae42-478f-8a92-94d7e9d88067","order":2921,"content":"The parameters for the Keel Allocator Vault are:\n\n- `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n- `line`: 0 USDS","contentHash":"4ea6119191cff89e816a9585c7df5fecbf22e7332195182d88c68cb549fa7c69","addressRefs":[]},"1ee3efd3-fe75-4766-bc6a-ec204f6a3bca":{"id":"1ee3efd3-fe75-4766-bc6a-ec204f6a3bca","doc_no":"A.3.7.1.2.1.4","title":"ALLOCATOR-OBEX-A Parameters","type":"Core","depth":6,"parentId":"305a31ea-ae42-478f-8a92-94d7e9d88067","order":2922,"content":"The parameters for the Obex Allocator Vault are:\n\n- `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n- `line`: controlled by DC-IAM\n- DC-IAM parameters:\n    - `gap`: 50 million USDS\n    - `line`: 2.5 billion USDS\n    - `ttl`: 24 hours","contentHash":"e8fd36bf1bed4de5f073ff21e5fd78236ff1a85fda9fd328f1561ac1a166c3ac","addressRefs":[]},"322e7ccc-6dcb-4f83-96e5-d8f2fa87cd00":{"id":"322e7ccc-6dcb-4f83-96e5-d8f2fa87cd00","doc_no":"A.3.7.1.2.1.5","title":"ALLOCATOR-PATTERN-A Parameters","type":"Core","depth":6,"parentId":"305a31ea-ae42-478f-8a92-94d7e9d88067","order":2923,"content":"The parameters for the Pattern Allocator Vault are:\n\n- `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n- `line`: controlled by DC-IAM\n- DC-IAM parameters:\n    - `gap`: 50 million USDS\n    - `line`: 2.5 billion USDS\n    - `ttl`: 24 hours","contentHash":"96a85d7d991e07ea4cdb56193cd5c0c95d4a56cd89e43b119ba7237465e414eb","addressRefs":[]},"17630a67-b287-4f44-bc60-f2a4f5d16cfa":{"id":"17630a67-b287-4f44-bc60-f2a4f5d16cfa","doc_no":"A.3.7.1.2.1.6","title":"ALLOCATOR-PRYSM-A Parameters","type":"Core","depth":6,"parentId":"305a31ea-ae42-478f-8a92-94d7e9d88067","order":2924,"content":"The parameters for the Launch Agent 6 Allocator Vault are:\n\n- `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n- `line`: controlled by DC-IAM\n- DC-IAM parameters:\n    - `gap`: 10 million USDS\n    - `line`: 10 million USDS\n    - `ttl`: 24 hours","contentHash":"e950d84fcdb2ea03c99d823beac1998c98ab6cae224a99ea6635f510969f56b2","addressRefs":[]},"cdbdd083-cb1c-4958-9cf0-18a088535c9d":{"id":"cdbdd083-cb1c-4958-9cf0-18a088535c9d","doc_no":"A.3.7.1.2.1.7","title":"ALLOCATOR-INTERVAL-A Parameters","type":"Core","depth":6,"parentId":"305a31ea-ae42-478f-8a92-94d7e9d88067","order":2925,"content":"The parameters for the Launch Agent 7 Allocator Vault are:\n\n- `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a).\n- `line`: controlled by DC-IAM\n- DC-IAM parameters:\n    - `gap`: 10 million USDS\n    - `line`: 10 million USDS\n    - `ttl`: 24 hours","contentHash":"e62bff4beda0c826197ee9cff6129260f2f2705e5fa345df7da80be1fadc31a3","addressRefs":[]},"41a1ae38-4f5c-468f-b6ba-47e16ecc5aec":{"id":"41a1ae38-4f5c-468f-b6ba-47e16ecc5aec","doc_no":"A.3.7.1.2.2","title":"Update Process","type":"Core","depth":5,"parentId":"1c09308d-b7cd-495c-b547-baf628a6e323","order":2926,"content":"Core GovOps, in consultation with the Core Council Risk Advisor, has the ability to modify any of the Prime Allocator Vault Risk Parameters listed under [A.3.7.1.2.1 - Prime Allocator Vault Risk Parameters](305a31ea-ae42-478f-8a92-94d7e9d88067). The modification of said parameters is pursuant to the Operational Weekly Cycle and can be effected directly via an Executive Vote, without requiring a prior Governance Poll.","contentHash":"638bb9fc78341e16bb38b2f45cb0b2521409c1d4cc116b6bb31024ef5ebb9867","addressRefs":[]},"47b8b035-8abd-42e6-86b8-33f852fa953a":{"id":"47b8b035-8abd-42e6-86b8-33f852fa953a","doc_no":"A.3.7.1.3","title":"Stability Parameter Bounded External Access Module","type":"Core","depth":4,"parentId":"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8","order":2927,"content":"The Stability Parameter Bounded External Access Module (SP-BEAM) enables designated, Governance-whitelisted operators to adjust the Stability Fees of supported vault types, the Dai Savings Rate (DSR), and the Sky Savings Rate (SSR). Adjustments are governed by the SP-BEAM smart contract logic and specific parameters set by Sky Governance. SP-BEAM holds four parameters that can be set for each vault type or savings rate: (i) `min`, (ii) `max`, (iii) `step`, and (iv) `tau`.","contentHash":"71bcb6c35ee3af54b5004a478e50c20ca6215142adfc7c0f073208776e46faf4","addressRefs":[]},"b113ca06-9a25-4abf-81f1-53f419ffe2d2":{"id":"b113ca06-9a25-4abf-81f1-53f419ffe2d2","doc_no":"A.3.7.1.3.1","title":"Definitions","type":"Core","depth":5,"parentId":"47b8b035-8abd-42e6-86b8-33f852fa953a","order":2928,"content":"The documents herein define the parameters of the Stability Parameter Bounded External Access Module.","contentHash":"3918944897e70ad1aa50e2a46828ac59e7f864a5b1d1595080ef482f65199aa0","addressRefs":[]},"1896350c-5f87-4be5-b32f-f1114dc2c271":{"id":"1896350c-5f87-4be5-b32f-f1114dc2c271","doc_no":"A.3.7.1.3.1.1","title":"Min Definition","type":"Core","depth":6,"parentId":"b113ca06-9a25-4abf-81f1-53f419ffe2d2","order":2929,"content":"The `min` parameter defines the minimum value for rates in basis points that can be set using the Stability Parameter Bounded External Access Module. Each rate parameter added to the SP-BEAM has a specific `min`.","contentHash":"0fab81bd86aeb00de79ba7eaa0a2ffe379dea8a08e302ef7245d31bf609e2598","addressRefs":[]},"67747090-8545-49b4-95e8-673af9836aa5":{"id":"67747090-8545-49b4-95e8-673af9836aa5","doc_no":"A.3.7.1.3.1.2","title":"Max Definition","type":"Core","depth":6,"parentId":"b113ca06-9a25-4abf-81f1-53f419ffe2d2","order":2930,"content":"The `max` parameter defines the maximum value for rates in basis points that can be set using the Stability Parameter Bounded External Access Module. Each rate parameter added to the SP-BEAM has a specific `max`.","contentHash":"f8f1530a3d511d7da845768ce949ee558bddf5fb5fcc926bb937494231ba1c2d","addressRefs":[]},"4e2910c0-fd52-4e18-97e0-2fbd35569070":{"id":"4e2910c0-fd52-4e18-97e0-2fbd35569070","doc_no":"A.3.7.1.3.1.2.1","title":"Max Technical Upper Limit","type":"Core","depth":6,"parentId":"b113ca06-9a25-4abf-81f1-53f419ffe2d2","order":2931,"content":"Although the `max` parameter can be set higher, the SP-BEAM cannot be used to set a rate higher than 50% (5,000 basis points) due to technical limitations. Attempts to use the SP-BEAM in this manner will revert. To avoid confusion, `max` should not be set to a value higher than 50% (5,000 basis points).","contentHash":"dec3142a8766560989f528970939c933ad379188e57570788fba80f18a3a4bc2","addressRefs":[]},"bcfac0d1-3d17-46e1-bf88-5a7937816d53":{"id":"bcfac0d1-3d17-46e1-bf88-5a7937816d53","doc_no":"A.3.7.1.3.1.3","title":"Step Definition","type":"Core","depth":6,"parentId":"b113ca06-9a25-4abf-81f1-53f419ffe2d2","order":2932,"content":"The `step` parameter limits how much the rates can be increased or decreased in a single transaction in basis points, bound by the `tau` parameter. Each rate parameter added to the SP-BEAM has a specific `step`.","contentHash":"1d99ded72a1f0586d88286b53169ee1dbfd62b2aa0abfb310f26497a7fcbfea6","addressRefs":[]},"8747effa-1080-4066-89da-4c25121a02ba":{"id":"8747effa-1080-4066-89da-4c25121a02ba","doc_no":"A.3.7.1.3.1.4","title":"Tau Definition","type":"Core","depth":6,"parentId":"b113ca06-9a25-4abf-81f1-53f419ffe2d2","order":2933,"content":"The `tau` parameter defines the minimum time interval, in seconds, that must elapse between consecutive uses or operations of the Stability Parameter Bounded External Access Module.\n\nAn SP-BEAM operation may adjust one or more parameters. Once an SP-BEAM operation is executed, the `tau` duration must expire before any subsequent SP-BEAM operation can be performed.","contentHash":"656bcd72ebf438ec4b76d6abe6ba45177dbb567d1374e6668473610434d6c515","addressRefs":[]},"dd9472e5-9796-4aff-a2b1-7a847e008c9b":{"id":"dd9472e5-9796-4aff-a2b1-7a847e008c9b","doc_no":"A.3.7.1.3.1.4.1","title":"Tau Current Value","type":"Core","depth":6,"parentId":"b113ca06-9a25-4abf-81f1-53f419ffe2d2","order":2934,"content":"The `tau` is currently set to 57,600 seconds (16 hours).","contentHash":"f9f09a82c135f91f6cef192b7029a65b12c7d8d74e14c9dab65144c6ae2f89d5","addressRefs":[]},"968d4388-a655-42ee-bab0-08e6583d1980":{"id":"968d4388-a655-42ee-bab0-08e6583d1980","doc_no":"A.3.7.1.3.2","title":"Native Vault Parameters","type":"Core","depth":5,"parentId":"47b8b035-8abd-42e6-86b8-33f852fa953a","order":2935,"content":"The Stability Parameter Bounded External Access Module parameters for the Native Vaults are defined in the subdocuments herein. When new vaults are added to the protocol, they must also be added to the SP-BEAM. Unless specified otherwise within the relevant subdocument herein, the SP-BEAM parameters for any newly added Native Vault type shall default to match the parameters defined herein for the ETH-A vault type.","contentHash":"64311cab5acc16effc2c5ed7406622949e0a457044b9345209b72c6d862b7aa7","addressRefs":[]},"c9cd99f2-9c40-4b06-94a1-630a26116bce":{"id":"c9cd99f2-9c40-4b06-94a1-630a26116bce","doc_no":"A.3.7.1.3.2.1","title":"ETH-A Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2936,"content":"The Stability Parameter Bounded External Access Module parameters for the ETH-A Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"3682e99c392ef0a3b9270e4d68585ad1b00c4477b92327b0e750040fed2f3051","addressRefs":[]},"6f28d962-1e40-4753-ab39-865795b349f4":{"id":"6f28d962-1e40-4753-ab39-865795b349f4","doc_no":"A.3.7.1.3.2.2","title":"ETH-B Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2937,"content":"The Stability Parameter Bounded External Access Module parameters for the ETH-B Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"e635e9ffbf1bfae6a2ad4f5c675cdb1af6c8d13fc8db614dc73e0ce1f2ae9ab4","addressRefs":[]},"748db209-f31e-444b-b134-55a8826a5d7a":{"id":"748db209-f31e-444b-b134-55a8826a5d7a","doc_no":"A.3.7.1.3.2.3","title":"ETH-C Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2938,"content":"The Stability Parameter Bounded External Access Module parameters for the ETH-C Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"ccafa2b23dbb12633f57b6628439b19502b42fb93a65775d2047447b2764f043","addressRefs":[]},"e134990f-7d06-46e3-a2c3-2277bb65e45c":{"id":"e134990f-7d06-46e3-a2c3-2277bb65e45c","doc_no":"A.3.7.1.3.2.4","title":"WSTETH-A Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2939,"content":"The Stability Parameter Bounded External Access Module parameters for the WSTETH-A Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"ca837fdb35e4d59beffd9fac4989f3abe0aaf200a8435826e1f2052f9665340a","addressRefs":[]},"f27c3fa3-dcd6-4ba8-9d74-426807ac010c":{"id":"f27c3fa3-dcd6-4ba8-9d74-426807ac010c","doc_no":"A.3.7.1.3.2.5","title":"WSTETH-B Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2940,"content":"The Stability Parameter Bounded External Access Module parameters for the WSTETH-B Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"649e0d45cc4e3a8f645e721e2894d0c3229f2eaf61170a11c09f7d8fc866f376","addressRefs":[]},"e0ead8d6-7d1d-48f0-addb-702e21ef5a9e":{"id":"e0ead8d6-7d1d-48f0-addb-702e21ef5a9e","doc_no":"A.3.7.1.3.2.6","title":"WBTC-A Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2941,"content":"The Stability Parameter Bounded External Access Module parameters for the WBTC-A Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"6d5d48e0bfc14ec61a6893e1efc45056a1e2cc8b4e6aec91419878fafa4147a0","addressRefs":[]},"dba279e1-bb04-4574-a45b-87788be40a78":{"id":"dba279e1-bb04-4574-a45b-87788be40a78","doc_no":"A.3.7.1.3.2.7","title":"WBTC-B Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2942,"content":"The Stability Parameter Bounded External Access Module parameters for the WBTC-B Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"03e54542e3c3616e47078f4bf4f6ec6f35913f21512860b2029a8d800dff9a3e","addressRefs":[]},"74ccae87-580f-492b-b260-fa3ef6613979":{"id":"74ccae87-580f-492b-b260-fa3ef6613979","doc_no":"A.3.7.1.3.2.8","title":"WBTC-C Parameters","type":"Core","depth":6,"parentId":"968d4388-a655-42ee-bab0-08e6583d1980","order":2943,"content":"The Stability Parameter Bounded External Access Module parameters for the WBTC-C Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 200 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"30a9ab2f33065c52c0d44aeea9cf9ffde0279f98efac652ba31cb34165cfc0f8","addressRefs":[]},"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa":{"id":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","doc_no":"A.3.7.1.3.3","title":"Allocator Vault Parameters","type":"Core","depth":5,"parentId":"47b8b035-8abd-42e6-86b8-33f852fa953a","order":2944,"content":"The Stability Parameter Bounded External Access Module parameters for the Allocator Vaults are defined in the subdocuments herein. When new Allocator Vaults are added, they must also be added to the SP-BEAM. Unless specified otherwise within the relevant subdocument herein, the SP-BEAM parameters for any newly added Allocator Vault type shall default to match the parameters defined herein for the ALLOCATOR-SPARK-A vault type.","contentHash":"92bd4b130f1515d246d001c397674d0cb852f97c86a57c9d67a9a3b1d1fa7ea2","addressRefs":[]},"3f6791ef-1f90-45b2-96db-0c85aa2035a1":{"id":"3f6791ef-1f90-45b2-96db-0c85aa2035a1","doc_no":"A.3.7.1.3.3.1","title":"ALLOCATOR-SPARK-A Parameters","type":"Core","depth":6,"parentId":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","order":2945,"content":"The Stability Parameter Bounded External Access Module parameters for the ALLOCATOR-SPARK-A Allocator Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"eb08bf0379f8bc8c2a603ada5033ffa06c8313aad9cc5438fd4f84ac350800e0","addressRefs":[]},"092b62b9-b9b8-4322-8b39-5c32ad420be3":{"id":"092b62b9-b9b8-4322-8b39-5c32ad420be3","doc_no":"A.3.7.1.3.3.2","title":"ALLOCATOR-NOVA-A Parameters","type":"Core","depth":6,"parentId":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","order":2946,"content":"The Stability Parameter Bounded External Access Module parameters for the ALLOCATOR-NOVA-A Allocator Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"368cd2794171cb0bb4ac782fbe1fcdc73fe0b69bc72f6ffea3969c5833928749","addressRefs":[]},"1cca9f9f-1a60-4de6-8ec2-694b87d3ee91":{"id":"1cca9f9f-1a60-4de6-8ec2-694b87d3ee91","doc_no":"A.3.7.1.3.3.3","title":"ALLOCATOR-BLOOM-A Parameters","type":"Core","depth":6,"parentId":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","order":2947,"content":"The Stability Parameter Bounded External Access Module parameters for the ALLOCATOR-BLOOM-A Allocator Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"01100a4c6f546e0765788350e16c98682c27a00f1434c525437ef0d8fc940aec","addressRefs":[]},"d52799ce-589d-4ef8-9ee3-ef940866291a":{"id":"d52799ce-589d-4ef8-9ee3-ef940866291a","doc_no":"A.3.7.1.3.3.4","title":"ALLOCATOR-OBEX-A Parameters","type":"Core","depth":6,"parentId":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","order":2948,"content":"The Stability Parameter Bounded External Access Module parameters for the ALLOCATOR-OBEX-A Allocator Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"c8451e9b832a5f038a57cf5fa200b4c811da4f30bf4cd5c9a8b69db104d7ec91","addressRefs":[]},"505130f5-cf13-47e0-bcb6-e4810a36a46c":{"id":"505130f5-cf13-47e0-bcb6-e4810a36a46c","doc_no":"A.3.7.1.3.3.5","title":"ALLOCATOR-PATTERN-A Parameters","type":"Core","depth":6,"parentId":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","order":2949,"content":"The Stability Parameter Bounded External Access Module parameters for the ALLOCATOR-PATTERN-A Allocator Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"a5ee19f1cbb3ead2c2696628d44ed05fe8321f19a2a24012e9877997c6a5079d","addressRefs":[]},"f09e5c6d-80cd-4d7d-b833-f64a96d23c15":{"id":"f09e5c6d-80cd-4d7d-b833-f64a96d23c15","doc_no":"A.3.7.1.3.3.6","title":"ALLOCATOR-PRYSM-A Parameters","type":"Core","depth":6,"parentId":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","order":2950,"content":"The Stability Parameter Bounded External Access Module parameters for the ALLOCATOR-PRYSM-A Allocator Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"cefaee70891a4adc0c263d738989326b0b66157aad8bf7579c2b8ae2994862cc","addressRefs":[]},"8766f5be-1a3b-4c74-ac5e-0e22aba94f9a":{"id":"8766f5be-1a3b-4c74-ac5e-0e22aba94f9a","doc_no":"A.3.7.1.3.3.7","title":"ALLOCATOR-INTERVAL-A Parameters","type":"Core","depth":6,"parentId":"6ab6bd12-93d3-419f-96e2-a7f79bfe1afa","order":2951,"content":"The Stability Parameter Bounded External Access Module parameters for the ALLOCATOR-INTERVAL-A Allocator Vault are as follows:\n\n- `max` - 3,000 basis points,\n- `min` - 0 basis points,\n- `step` - 400 basis points,\n- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b).","contentHash":"3dd3396e1f42b52c27e190768b08ce1524ef4b93f710ebc0ea34b325428849dc","addressRefs":[]},"2d4aa875-b7ea-49c3-9506-479f0b5d157c":{"id":"2d4aa875-b7ea-49c3-9506-479f0b5d157c","doc_no":"A.3.7.1.3.4","title":"Parameter Adjustments","type":"Core","depth":5,"parentId":"47b8b035-8abd-42e6-86b8-33f852fa953a","order":2952,"content":"All Stability Parameter Bounded External Access Module parameters can be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.","contentHash":"d665560eb3109c1f3ba93cd0b8cc0470c2a77e2baf2d4179fe4ea8a16fec0a09","addressRefs":[]},"91f8b696-2c6b-4234-9126-2576a385882d":{"id":"91f8b696-2c6b-4234-9126-2576a385882d","doc_no":"A.3.7.1.3.5","title":"Operators","type":"Core","depth":5,"parentId":"47b8b035-8abd-42e6-86b8-33f852fa953a","order":2953,"content":"The Stability Parameter Bounded External Access Module (SP-BEAM) Operator is a whitelisted entity that can directly alter the current parameters of vault types or savings rates that have been added to the SP-BEAM. Changes to rates are limited by the `max`, `min`, `step`, and `tau` parameters. Operators can be added or removed by an Executive Vote.","contentHash":"8649cb62ec43e935d3966c2301e16bc390c976a521760ad411d3b72ff0ddda57","addressRefs":[]},"f0cc7297-8ab9-4255-9365-d9ba87764f13":{"id":"f0cc7297-8ab9-4255-9365-d9ba87764f13","doc_no":"A.3.7.1.3.5.1","title":"Operator Multisig","type":"Core","depth":6,"parentId":"91f8b696-2c6b-4234-9126-2576a385882d","order":2954,"content":"The Operator Multisig is the Operator of the Stability Parameter Bounded External Access Module and is controlled by Core GovOps.","contentHash":"b5816c427185272d6648402dc5f07dd924791cd4a2399a9b8c2a52001d0c1db4","addressRefs":[]},"793d4595-9f1f-4387-a3a6-b9c7b20266c3":{"id":"793d4595-9f1f-4387-a3a6-b9c7b20266c3","doc_no":"A.3.7.1.3.5.1.1","title":"Operator Multisig Address","type":"Core","depth":6,"parentId":"91f8b696-2c6b-4234-9126-2576a385882d","order":2955,"content":"The address of the Operator Multisig on the Ethereum Mainnet is `0xe1c6f81D0c3CD570A77813b81AA064c5fff80309`.","contentHash":"6bf77f7b1bdd68b62b1a8f144e2f94d7b47c194661a11674d688036df7e9bd42","addressRefs":["0xe1c6f81d0c3cd570a77813b81aa064c5fff80309"]},"591ac4d7-5699-4a81-8b4a-d10c8d8c3457":{"id":"591ac4d7-5699-4a81-8b4a-d10c8d8c3457","doc_no":"A.3.7.1.3.5.1.2","title":"Operator Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"91f8b696-2c6b-4234-9126-2576a385882d","order":2956,"content":"The Operator Multisig currently has a 2/3 signing requirement.","contentHash":"3225d2e5c6230021467c67d01dab2e69e4801361f019a44512d61b5db54c0bdc","addressRefs":[]},"154be1f7-3e96-417a-b125-f978c47e2301":{"id":"154be1f7-3e96-417a-b125-f978c47e2301","doc_no":"A.3.7.1.3.5.1.3","title":"Operator Multisig Signers","type":"Core","depth":6,"parentId":"91f8b696-2c6b-4234-9126-2576a385882d","order":2957,"content":"The signers of the Operator Multisig are three (3) addresses controlled by Core GovOps.","contentHash":"3117e971a05c70e18ab436af461246763f0cc78c29259375f8fa1d3d5c37ece1","addressRefs":[]},"9e2f39aa-0568-46a3-ad5c-898eba6e50c0":{"id":"9e2f39aa-0568-46a3-ad5c-898eba6e50c0","doc_no":"A.3.7.1.3.5.1.4","title":"Operator Multisig Usage Standards","type":"Core","depth":6,"parentId":"91f8b696-2c6b-4234-9126-2576a385882d","order":2958,"content":"The signers of the Operator Multisig must use the multisig to operate the Stability Parameter Bounded External Access Module in accordance with the instructions specified in [A.3.7.1.3.6 - Update Process](823aa477-5400-40e5-881f-acb9cf724c21).","contentHash":"a093b75a5fcd76d8376acad3cbdf222471ad8f79a65c23c6c16d5354e6c14341","addressRefs":[]},"24b8a5d0-b2b0-4bdf-94cf-f873d7468d48":{"id":"24b8a5d0-b2b0-4bdf-94cf-f873d7468d48","doc_no":"A.3.7.1.3.5.1.5","title":"Operator Multisig Modification","type":"Core","depth":6,"parentId":"91f8b696-2c6b-4234-9126-2576a385882d","order":2959,"content":"Core GovOps can change the signers of the Operator Multisig at any time, so long as there are at least three (3) signers and at least a majority of signers are required to execute transactions.","contentHash":"9fff0b4b32fb21aa813435687155758ebb9f9428203e2d91939da6781fd9dce6","addressRefs":[]},"ae2b5d27-b666-4796-8791-b59d151daf41":{"id":"ae2b5d27-b666-4796-8791-b59d151daf41","doc_no":"A.3.7.1.3.5.2","title":"Operator Update Process","type":"Core","depth":6,"parentId":"91f8b696-2c6b-4234-9126-2576a385882d","order":2960,"content":"Stability Parameter Bounded External Access Module Operators can be modified by the Stability Facilitators, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.","contentHash":"1ca35d1a6e86db634f7a05e6d0a5e1f2ede630cf1a426822183eea21c92b4bb6","addressRefs":[]},"823aa477-5400-40e5-881f-acb9cf724c21":{"id":"823aa477-5400-40e5-881f-acb9cf724c21","doc_no":"A.3.7.1.3.6","title":"Update Process","type":"Core","depth":5,"parentId":"47b8b035-8abd-42e6-86b8-33f852fa953a","order":2961,"content":"The rates set by the Stability Parameter Bounded External Access Module (SP-BEAM) are managed by the SP-BEAM Operators. The SP-BEAM Operators' use of this authority must wholly adhere to instructions provided by the Core Council Risk Advisor.","contentHash":"7dfe31c77c2ad25abb534c1b6c0ec642bbefbd6ca65d5cf7852c0e080f8a71ed","addressRefs":[]},"0f718693-f764-48e5-8b0c-ad36389ba3a0":{"id":"0f718693-f764-48e5-8b0c-ad36389ba3a0","doc_no":"A.3.7.1.3.6.1","title":"Request By Core Council Risk Advisor","type":"Core","depth":6,"parentId":"823aa477-5400-40e5-881f-acb9cf724c21","order":2962,"content":"Any requests to change rates set by the SP-BEAM must be posted to the Sky Forum by the Core Council Risk Advisor that is recommending the change.","contentHash":"6391af0f675e78aac6abf44e12f7988368e7e318211d95e57b15ac149826bc9a","addressRefs":[]},"c49357ad-4961-497b-9449-662922cb70a7":{"id":"c49357ad-4961-497b-9449-662922cb70a7","doc_no":"A.3.7.1.3.6.2","title":"Operator Execution","type":"Core","depth":6,"parentId":"823aa477-5400-40e5-881f-acb9cf724c21","order":2963,"content":"Once a rate change request has been posted to the Sky Forum by the Core Council Risk Advisor, the SP-BEAM Operators must prepare and execute the proposed changes in a timely manner. Preparation can include the creation of transaction simulations to verify inputs.","contentHash":"28f82d33f50f756f6506ee71d4cbec3ec3e6d9016ef6b6e3d6d8fb53311c7364","addressRefs":[]},"30a9cafe-92cc-4c9b-af94-c341915a1dfc":{"id":"30a9cafe-92cc-4c9b-af94-c341915a1dfc","doc_no":"A.3.7.1.3.6.3","title":"Public Communication","type":"Core","depth":6,"parentId":"823aa477-5400-40e5-881f-acb9cf724c21","order":2964,"content":"Once a change in rates set by the SP-BEAM has been executed, the execution must be publicly communicated to the Sky Ecosystem. This communication may take the form of either (1) a Forum post or (2) inclusion of the execution in an informational dashboard that allows community members to see each rate change executed by the SP-BEAM.","contentHash":"5832893ce8695f8a3ff03313d74e7256fef6b656e0ae86841a7c34d703f586c1","addressRefs":[]},"f2bba617-0bc5-4983-8885-4ab686ae4fc7":{"id":"f2bba617-0bc5-4983-8885-4ab686ae4fc7","doc_no":"A.3.7.1.4","title":"Keepers","type":"Core","depth":4,"parentId":"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8","order":2965,"content":"Keepers are a critical component of the Sky Protocol infrastructure. They are automated systems responsible for controlling, monitoring, and supporting backend operations, thereby ensuring the stability, security, and overall integrity of the Sky Protocol and its users. Due to their importance, it is essential that keepers operate continuously and reliably. They must also maintain sufficient funding to cover gas costs required for their execution. The subdocuments herein specify the current keeper providers and, where applicable, their associated payment streams.","contentHash":"ab6be8bb05267aa16d1903e2dac5dac862c6bee02a93f9eba2df565db25be6b9","addressRefs":[]},"af29fc28-e4d4-4921-98e5-9468f06068ec":{"id":"af29fc28-e4d4-4921-98e5-9468f06068ec","doc_no":"A.3.7.1.4.1","title":"Chainlink Automation","type":"Core","depth":5,"parentId":"f2bba617-0bc5-4983-8885-4ab686ae4fc7","order":2966,"content":"Chainlink Automation\n\nBudget: 1,500 USDS per day\nStream Duration: 3 years (start date 29 May 2023).","contentHash":"63bd8bacaa001732268bced09c9596abe849833eeea4282f9890b89ce1a25a4a","addressRefs":[]},"cc7914f8-61bd-4cc6-933c-715ceff3ea19":{"id":"cc7914f8-61bd-4cc6-933c-715ceff3ea19","doc_no":"A.3.7.1.4.2","title":"TechOps Services","type":"Core","depth":5,"parentId":"f2bba617-0bc5-4983-8885-4ab686ae4fc7","order":2967,"content":"TechOps Services operates the `SKY` lane in the dss-cron Sequencer, handling keeper creation, setup, and regularly scheduled automatic execution with 24/7 support services for the Sky Protocol.","contentHash":"adff1befa92e5beea42bacd0d8d49a232e5e60acd3f5f4379eeea08dd8254b95","addressRefs":[]},"3da8a0fd-952c-4f80-b674-f60c9a293cb9":{"id":"3da8a0fd-952c-4f80-b674-f60c9a293cb9","doc_no":"A.3.7.1.5","title":"Offboarding Process","type":"Core","depth":4,"parentId":"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8","order":2968,"content":"The subdocuments herein define the process by which Sky vault users should be notified about collateral offboarding.","contentHash":"78d14510b9691d584b5c367f9aeda7143123d87e9f6cd88a8f4619658820dd96","addressRefs":[]},"6e08fc61-dc0d-4f18-8f4d-faa75f7dc59a":{"id":"6e08fc61-dc0d-4f18-8f4d-faa75f7dc59a","doc_no":"A.3.7.1.5.1","title":"Legacy Context","type":"Core","depth":5,"parentId":"3da8a0fd-952c-4f80-b674-f60c9a293cb9","order":2969,"content":"Periodically, collateral and vault types (ilks) are re-evaluated, which sometimes results in an offboarding of that collateral or vault type.\n\nThere have been several instances where users entered official Sky forums/chats to understand why they had been suddenly liquidated, despite historically comfortable collateralization ratios ([https://forum.skyeco.com/t/an-assessment-first-hand-experience-and-recommendations-from-the-aave-offboarding/11836](https://forum.skyeco.com/t/an-assessment-first-hand-experience-and-recommendations-from-the-aave-offboarding/11836)). This is, understandably, a poor user experience.\n\nEven with liquidation penalties set to 0%, the forced unwinding of levered positions conceivably can result in user losses, as well as potentially taxable events.\n\nThis Section defines procedures concerning the dissemination of information about upcoming collateral offboarding on a best-effort basis. The objective is to minimize the number of users who are unaware of the offboarding prior to getting their positions liquidated.","contentHash":"8570c83dd9a43696385a865caa8909f6c3cc6e9bcc6117e24038bc36b0315b7a","addressRefs":[]},"dd7c5813-2026-4d1c-9bc8-33cf8fbee15a":{"id":"dd7c5813-2026-4d1c-9bc8-33cf8fbee15a","doc_no":"A.3.7.1.5.1.1","title":"Legacy Context Specific Goals","type":"Core","depth":6,"parentId":"6e08fc61-dc0d-4f18-8f4d-faa75f7dc59a","order":2970,"content":"Specific Goals:\n\n1. Codify a series of good-faith communication efforts.\n2. Provide an easy-to-follow process for Sky contributors to follow without significant burden.\n3. Minimize the number of users unaware of a collateral offboarding.\n4. Provide a method to bypass these requirements in the event a collateral is being offboarded due to serious security or solvency concerns.","contentHash":"647c4219e12c6537df10c34b73160400e597c926c366a9fb675f529f563aa839","addressRefs":[]},"305e2bd6-a594-4aec-8713-adbe7bc87120":{"id":"305e2bd6-a594-4aec-8713-adbe7bc87120","doc_no":"A.3.7.1.5.2","title":"Technical Process","type":"Core","depth":5,"parentId":"3da8a0fd-952c-4f80-b674-f60c9a293cb9","order":2971,"content":"The subdocuments herein specify actions to be taken by specific actors within Sky when offboarding a vault type.","contentHash":"924e4434dc261af9442ed940cb6d14debf219f26322ea26de851c0e0c56bfcd8","addressRefs":[]},"200a9e67-ed5d-4d60-b826-860a2a247dcc":{"id":"200a9e67-ed5d-4d60-b826-860a2a247dcc","doc_no":"A.3.7.1.5.2.1","title":"Immediate Actions","type":"Core","depth":6,"parentId":"305e2bd6-a594-4aec-8713-adbe7bc87120","order":2972,"content":"Upon approval by Sky Governance to offboard a permissionless collateral type or vault type, the following actions are taken as soon as is practicable:\n\n- Set debt ceiling to zero (0) Dai or USDS.\n- Make an initial public announcement on all communication channels listed in [A.3.7.1.5.3.0.6.1 - Communication Channels And Media Assets Listing](9ac8a70b-8b6a-4825-a5e0-5e9019e50bc4).\n- Make a second public announcement on all communication channels in the above cited document no later than 14 calendar days after the initial public announcement.\n- Once the second public announcements have been made, set the liquidation penalty to 0%.","contentHash":"b747dd2382d7299ff24dcca91f6f4eb428730ce2cca722af6a695e695db03ac3","addressRefs":[]},"e0891d48-c684-4372-96e8-988aba8cccee":{"id":"e0891d48-c684-4372-96e8-988aba8cccee","doc_no":"A.3.7.1.5.2.2","title":"Following Actions","type":"Core","depth":6,"parentId":"305e2bd6-a594-4aec-8713-adbe7bc87120","order":2973,"content":"Parameter changes designed to offboard users, such as changes to the liquidation ratio or stability fee, can only be implemented once 14 calendar days have passed following a second public announcement.","contentHash":"db8bba4f775d1cf9c851cfc08d1061ba129858d84d6b193e50635fa5f1387f9f","addressRefs":[]},"9d418790-3081-43b4-a6f6-1c49ff5b4be8":{"id":"9d418790-3081-43b4-a6f6-1c49ff5b4be8","doc_no":"A.3.7.1.5.3","title":"Communication Channels And Media Assets","type":"Active Data Controller","depth":5,"parentId":"3da8a0fd-952c-4f80-b674-f60c9a293cb9","order":2974,"content":"The process for adding, removing, and modifying communication channels and media assets, and the order of announcement publication, are defined as Active Data in [A.3.7.1.5.3.0.6.1 - Communication Channels And Media Assets Listing](9ac8a70b-8b6a-4825-a5e0-5e9019e50bc4).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Core GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"76d2bb1b1a58f1a28e39751ce6cc1356c9eedc54b76761dd527ccb8907392317","addressRefs":[]},"9ac8a70b-8b6a-4825-a5e0-5e9019e50bc4":{"id":"9ac8a70b-8b6a-4825-a5e0-5e9019e50bc4","doc_no":"A.3.7.1.5.3.0.6.1","title":"Communication Channels And Media Assets Listing","type":"Active Data","depth":6,"parentId":"9d418790-3081-43b4-a6f6-1c49ff5b4be8","order":2975,"content":"The following channels should be used for initial and second public announcements of collateral offboarding. The order of announcement publication is as follows:\n\n1. The author of the collateral offboarding notice shall post to the Sky Forum detailing the recommended offboarding. This forum thread is used to inform downstream announcements on other channels.\n2. Core GovOps publishes the associated notices to:\n    - All public Sky Calendars\n    - The Sky Official Discord’s Announcement channel.\n    - The official Sky subreddit.\n3. Partner Relationship Leads from relevant Ecosystem Actors reach out to:\n    - Affected collateral partners (e.g., Aave)\n    - Affected frontend service providers (e.g., Oasis, DeFi Saver)\n\nAdditionally, outreach may be done to cover more channels not listed here. These may include other Ecosystem Actor or Facilitator owned Twitter accounts, communication channels, and platforms.\n\nUnless otherwise noted in [A.3.7.1.5 - Offboarding Process](3da8a0fd-952c-4f80-b674-f60c9a293cb9) and its subdocuments, Core GovOps will take the lead in coordinating channels announcements.","contentHash":"2d144a0eea86dd9d1f45fcee8f5f6fdd8658ff93896ab5eecbcc5028928f2488","addressRefs":[]},"f9894690-fb43-431c-84ae-c6f5886745e9":{"id":"f9894690-fb43-431c-84ae-c6f5886745e9","doc_no":"A.3.7.1.5.4","title":"Expedited Offboarding","type":"Core","depth":5,"parentId":"3da8a0fd-952c-4f80-b674-f60c9a293cb9","order":2976,"content":"The subdocuments herein define an expedited offboarding process in the event a collateral type needs to be removed quickly due to security or solvency concerns.","contentHash":"93bafcf7b4cc051abc7935f1c2cd80101baaee12f0d4be57d6a0f480895d72ba","addressRefs":[]},"5f2109db-6680-478b-b72a-45f30065b626":{"id":"5f2109db-6680-478b-b72a-45f30065b626","doc_no":"A.3.7.1.5.4.1","title":"Requirements","type":"Core","depth":6,"parentId":"f9894690-fb43-431c-84ae-c6f5886745e9","order":2977,"content":"When a collateral type threatens the security or solvency of the Sky Protocol, an expedited offboarding is in order. Expedited offboardings override the timeline specified in [A.3.7.1.5.2 - Technical Process](305e2bd6-a594-4aec-8713-adbe7bc87120) and allow the immediate modification of all relevant parameters.\n\nExpedited offboardings must proceed pursuant to the following requirements:\n\n- The Offboarding Proposal must state that the offboarding should be expedited due to an emergency or urgent concern, as defined in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225)**.**\n- The Offboarding Proposal must explicitly reference this Atlas document.","contentHash":"37419cd6a59939105081b58d3b2da777db77cf38ba5a12c3d0fd58faa05ca7de","addressRefs":[]},"b83a3a8b-a5ab-4eed-abf0-31842ebbfa29":{"id":"b83a3a8b-a5ab-4eed-abf0-31842ebbfa29","doc_no":"A.3.7.1.5.4.2","title":"Announcements","type":"Core","depth":6,"parentId":"f9894690-fb43-431c-84ae-c6f5886745e9","order":2978,"content":"The public announcements defined in [A.3.7.1.5.2 - Technical Process](305e2bd6-a594-4aec-8713-adbe7bc87120) must still be carried out. However, the timing of these announcements no longer constrains the modification of parameters. These announcements must also state that the offboarding is being expedited and explain the reasons for this accelerated process.","contentHash":"39cfd2295e75e3a96dda07746c758988002f342cb8238ddf86d65cc840782a04","addressRefs":[]},"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98":{"id":"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98","doc_no":"A.3.7.1.6","title":"Genesis Capital Backstop","type":"Core","depth":4,"parentId":"92b5164c-2a55-4947-bb8a-9b05ca5ed8c8","order":2979,"content":"If losses exceed a Prime Agent’s capital and cannot be absorbed by the Sky Surplus Buffer, the Sky Protocol must apply a pro‑rata haircut across each Genesis Agent’s Genesis Capital, implemented as a transfer of eligible assets from each Agent to the Sky Surplus Buffer. The haircut must be sized to cover the portion of the loss that exceeds what the Prime Agent’s capital and the Sky Surplus Buffer can absorb, up to a maximum of the Aggregate Backstop Capital (see [A.3.5.3.1.2 - Aggregate Backstop Capital](6dbead44-5ac4-4c5b-be3c-64eddd004e5c)).","contentHash":"876108da23934dd549580ade0ab2bb3542fb7f2ad00014ce10e8e8ccde60f006","addressRefs":[]},"4381df75-0d4f-4f17-a263-f796cc33be27":{"id":"4381df75-0d4f-4f17-a263-f796cc33be27","doc_no":"A.3.7.1.6.1","title":"Implementation","type":"Core","depth":5,"parentId":"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98","order":2980,"content":"In the near term, transfers are made through Executive Votes and may be made through Emergency Spells (see [A.1.10.5 - Emergency Spells](b8266c11-3a84-4bbe-abe2-de9474f74ffd)) as part of the Emergency Response System (see [A.1.9.1 - Emergency Response](20dcf582-8862-48b3-9ca9-c3703871bd14)).\n\nA solution must be developed to allow these transfers to be accomplished on an automated basis without waiting for the GSM Pause Delay (see [A.1.10.3 - Governance Security Delay Requirements](c5f0e955-0441-42e0-a6fc-eab875bba568)).","contentHash":"b210b1f2518270c5e63df346fa06320d38204fc35285f19cc52734608494b07f","addressRefs":[]},"1edfed11-0234-4d15-b52b-37d7493565cd":{"id":"1edfed11-0234-4d15-b52b-37d7493565cd","doc_no":"A.3.7.1.6.2","title":"Post Backstop Settlement","type":"Core","depth":5,"parentId":"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98","order":2981,"content":"If, after the haircut, losses still exceed the combined capacity of the Prime Agent’s capital and Aggregate Backstop Capital (see [A.3.5.3.1.2 - Aggregate Backstop Capital](6dbead44-5ac4-4c5b-be3c-64eddd004e5c)), the SKY Backstop (see [A.3.6 - SKY Backstop](4d8b0d82-97da-4041-b185-4b98c2779cbe)) is activated. The SKY mint must be sized to cover the remaining loss. If losses still exceed what the SKY Backstop can absorb, Sky will adjust the USDS target price below $1 to the extent necessary to settle the remaining deficit; Sky will then distribute 24 billion SKY to USDS holders via an airdrop.","contentHash":"f75f6704f71b7a39e7bab4dc9409729f8969ffb553aa17af3cbc2533827199df","addressRefs":[]},"81bacfed-5cc9-4980-bf71-1e5edcbdadba":{"id":"81bacfed-5cc9-4980-bf71-1e5edcbdadba","doc_no":"A.3.7.1.6.3","title":"Genesis Agent Capital Shortfalls","type":"Core","depth":5,"parentId":"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98","order":2982,"content":"Transfers of capital from Genesis Agents may cause capital shortfalls for Genesis Agents under the Risk Framework (see [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4)). Sky will work in good faith with such Agents to waive penalties for a reasonable period of time to allow the Agents to rebuild their capital.","contentHash":"ec1becef5d5255286547f73ff31fa587add58abea3a40c2ed17a32a6b9cf1c2a","addressRefs":[]},"3b7324cd-8246-4eed-9da9-56599dcac5b4":{"id":"3b7324cd-8246-4eed-9da9-56599dcac5b4","doc_no":"A.3.7.1.6.4","title":"Relation To SKY Backstop","type":"Core","depth":5,"parentId":"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98","order":2983,"content":"The Genesis Capital Backstop must be applied before the SKY Backstop (see [A.3.6 - SKY Backstop](4d8b0d82-97da-4041-b185-4b98c2779cbe)).","contentHash":"d129e4361e65d27dba06e174dfac6676c2c0587e17ef0f5454a287ab38b02094","addressRefs":[]},"8952aac5-24fb-4da1-ae10-49f86d30aecd":{"id":"8952aac5-24fb-4da1-ae10-49f86d30aecd","doc_no":"A.3.7.1.6.5","title":"Genesis Agents","type":"Core","depth":5,"parentId":"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98","order":2984,"content":"Genesis Agents are Agents that receive capital contributions from Sky, including, without limitation:\n\n- Spark\n- Grove\n- Keel\n- Skybase\n- Obex\n- Launch Agent 6\n- Core Council Executor Agent 1\n- Amatsu\n- Ozone","contentHash":"3f1e1d81ee47f94d611a88eb6d77ccc8aee0978c3a1b82648cc6aaef52e8560c","addressRefs":[]},"18f3de06-064b-4b08-a855-4720240e37f5":{"id":"18f3de06-064b-4b08-a855-4720240e37f5","doc_no":"A.3.7.1.6.6","title":"Genesis Capital","type":"Core","depth":5,"parentId":"a9965d58-8cda-49fc-8a7f-f8cc2e0d6b98","order":2985,"content":"The Genesis Capital of an Agent is the lesser of (1) the Eligible Genesis Capital of the Agent and (2) the total capital of the Agent. The Eligible Genesis Capital of an Agent is the amount of capital contributed by Sky to the Agent (see [A.3.7.1.6.6.1 - Amount Of Capital Contributed By Sky To Agents](0331556e-e7ae-48a2-a693-75468c416321)) minus the Phased-Out Genesis Capital of the Agent (see [A.3.7.1.6.6.2.3.0.6.1 - Current Phased-Out Genesis Capital](41bf89b5-dae5-47f3-bd6b-73b5598d9a0d)).","contentHash":"41f3f969c17f7e3e00ba5a5ce39e8ac2ecb481c655798e9fc38ff33d6d86bcb5","addressRefs":[]},"0331556e-e7ae-48a2-a693-75468c416321":{"id":"0331556e-e7ae-48a2-a693-75468c416321","doc_no":"A.3.7.1.6.6.1","title":"Amount Of Capital Contributed By Sky To Agents","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2986,"content":"The amount of capital contributed by Sky to Agents is:\n\n- Spark - 25,000,000 USDS\n- Grove - 25,000,000 USDS\n- Obex - 21,000,000 USDS\n- Skybase - 15,000,000 USDS\n- Core Council Executor Agent 1 - 25,000,000 USDS\n- Keel - 10,000,000 USDS\n- Launch Agent 6 - 10,500,000 USDS\n- Amatsu - 25,000,000 USDS\n- Ozone - 25,000,000 USDS","contentHash":"5e031f551e43a4adc754fed29eff8577b54e523c76f4e429c147da9c2b9719f4","addressRefs":[]},"9c06226e-b9ed-49e7-8d82-557b9414b294":{"id":"9c06226e-b9ed-49e7-8d82-557b9414b294","doc_no":"A.3.7.1.6.6.2","title":"Genesis Capital Phase-Out","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2987,"content":"As the ecosystem matures and Aggregate Backstop Capital (see [A.3.5.3.1.2 - Aggregate Backstop Capital](6dbead44-5ac4-4c5b-be3c-64eddd004e5c)) reaches a sufficient level, Genesis Capital will phase out. The documents herein define the eligibility conditions and phase-out amounts.","contentHash":"dae2daf3305d28e5b00951951886a659faa2469f22aa70d4bb82fac09e02359d","addressRefs":[]},"6038d06a-6a02-4f8f-9e7d-32f4f2d1f624":{"id":"6038d06a-6a02-4f8f-9e7d-32f4f2d1f624","doc_no":"A.3.7.1.6.6.2.1","title":"Phase-Out Eligibility","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2988,"content":"The documents herein define the conditions under which Genesis Capital phase-out is active. Both Sky-level and Prime Agent-level conditions must be satisfied.","contentHash":"fe6c32863078abd63dbe1ea9db456f20e06e28232f8a72a5d84ce792bc5dcf58","addressRefs":[]},"5396bafc-8d6e-4006-bd8b-ee08ac35c729":{"id":"5396bafc-8d6e-4006-bd8b-ee08ac35c729","doc_no":"A.3.7.1.6.6.2.1.1","title":"Sky Phase-Out Eligibility Conditions","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2989,"content":"Genesis Capital phase-out is active when Aggregate Backstop Capital is at or above 125 million USDS. If Aggregate Backstop Capital falls below 125 million USDS at any point, phase-out pauses for all Genesis Agents until Aggregate Backstop Capital is once again at or above the threshold.","contentHash":"0fe98e8909a74123656689166feca6f7a3444edb4efc76efd1492724e2c630f4","addressRefs":[]},"392f7cb8-b2cf-4e2c-91e4-4b1eb6edf68f":{"id":"392f7cb8-b2cf-4e2c-91e4-4b1eb6edf68f","doc_no":"A.3.7.1.6.6.2.1.2","title":"Genesis Agent Phase-Out Eligibility Conditions","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2990,"content":"A Genesis Agent becomes eligible for Genesis Capital phase-out when it has launched a liquid token with at least ten (10) million USDS in average daily trading volume over a thirty (30) day period.","contentHash":"9ade5ef985b3a37320480079a579b5acb1d59848a7b8ddecfc89b55f71730bee","addressRefs":[]},"32e3b6cf-c3f7-4756-a8af-31920fc81319":{"id":"32e3b6cf-c3f7-4756-a8af-31920fc81319","doc_no":"A.3.7.1.6.6.2.2","title":"Phase-Out Amount","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2991,"content":"For each eligible Genesis Agent whose eligibility conditions are satisfied, the phase-out amount per month (the Total Phase-Out Amount) is the sum of the Base Phase-Out Amount and the Additional Phase-Out Amount, as specified in the documents herein. Following each Monthly Settlement Cycle, the Current Phased-Out Genesis Capital (see [A.3.7.1.6.6.2.3.0.6.1 - Current Phased-Out Genesis Capital](41bf89b5-dae5-47f3-bd6b-73b5598d9a0d)) for each Agent must be increased by the Total Phase-Out Amount for that Agent, but must not exceed the amount of capital contributed by Sky to that Agent (see [A.3.7.1.6.6.1 - Amount Of Capital Contributed By Sky To Agents](0331556e-e7ae-48a2-a693-75468c416321)).","contentHash":"a0cf3fd7dbc36ebb295ea8719b84bdeab22811fc97ea1a8db2a398b94e5dbd4f","addressRefs":[]},"7584440d-182b-4d6d-bb8e-d85ee5a37291":{"id":"7584440d-182b-4d6d-bb8e-d85ee5a37291","doc_no":"A.3.7.1.6.6.2.2.1","title":"Base Phase-Out Amount","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2992,"content":"The Base Phase-Out Amount is one (1) million USDS per eligible Genesis Agent per month.","contentHash":"4388f35801f37289cf724af7617cd73334a568945b4d845cafa3088e27b6411c","addressRefs":[]},"ed547147-bb36-42fa-9008-96af46f9640d":{"id":"ed547147-bb36-42fa-9008-96af46f9640d","doc_no":"A.3.7.1.6.6.2.2.2","title":"Additional Phase-Out Amount","type":"Core","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2993,"content":"The Additional Phase-Out Amount per eligible Genesis Agent per month is the amount by which Aggregate Backstop Capital exceeds 125 million USDS, divided by 10.","contentHash":"903d6c48a09e9e3959d6c95df69838a29825c9aabce2285365326f45a1a56569","addressRefs":[]},"8f813186-1317-41b1-86d1-47fce7f42af5":{"id":"8f813186-1317-41b1-86d1-47fce7f42af5","doc_no":"A.3.7.1.6.6.2.3","title":"Phased-Out Genesis Capital","type":"Active Data Controller","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2994,"content":"The Phased-Out Genesis Capital for each Genesis Agent is defined as Active Data in [A.3.7.1.6.6.2.3.0.6.1 - Current Phased-Out Genesis Capital](41bf89b5-dae5-47f3-bd6b-73b5598d9a0d).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Core Council Risk Advisor.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"5a5107fb923b9dd9faca429c849d5497f00afb286a85dfba913db0606e151cf5","addressRefs":[]},"41bf89b5-dae5-47f3-bd6b-73b5598d9a0d":{"id":"41bf89b5-dae5-47f3-bd6b-73b5598d9a0d","doc_no":"A.3.7.1.6.6.2.3.0.6.1","title":"Current Phased-Out Genesis Capital","type":"Active Data","depth":6,"parentId":"18f3de06-064b-4b08-a855-4720240e37f5","order":2995,"content":"The current Phased-Out Genesis Capital for each Genesis Agent is:\n\n- Spark - 0 USDS\n- Obex - 0 USDS\n- Skybase - 0 USDS\n- Core Council Executor Agent 1 - 0 USDS\n- Keel - 0 USDS\n- Launch Agent 6 - 0 USDS\n- Amatsu - 0 USDS\n- Ozone - 0 USDS","contentHash":"507fe7dcb7a19824ae3659b2485b7cc45f3d75c03219c3719779f118c54c62ac","addressRefs":[]},"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b":{"id":"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b","doc_no":"A.4","title":"The Protocol Scope","type":"Scope","depth":1,"parentId":null,"order":2996,"content":"The Protocol Scope regulates the maintenance and development of the core Sky Protocol and its critical, non-collateral components. The Protocol Scope defines all rules for protocol engineering.","contentHash":"3f1256ce530d4a6d762ea19d060ecc7d8b9fa2d985975784ee4d3cf49491e29c","addressRefs":[]},"e5089a2a-22b0-47fd-b0c2-a93017a2c71a":{"id":"e5089a2a-22b0-47fd-b0c2-a93017a2c71a","doc_no":"A.4.1","title":"Core Tokens","type":"Article","depth":2,"parentId":"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b","order":2997,"content":"The two core tokens, USDS and SKY, play the central role in the usability and tokenomics of the Sky Ecosystem.","contentHash":"5c242162337b91da42c77fa5d9cd0f113c870f7a58bb32f0f30cfa28c7fb27a4","addressRefs":[]},"7e356a45-3d05-4125-9fd7-d3d454e54cdb":{"id":"7e356a45-3d05-4125-9fd7-d3d454e54cdb","doc_no":"A.4.1.1","title":"USDS","type":"Section","depth":3,"parentId":"e5089a2a-22b0-47fd-b0c2-a93017a2c71a","order":2998,"content":"USDS is the Stablecoin product of the Sky Protocol. It is designed to remain stable against USD, and its supply is regulated through the Peg Stability Module and the Allocation System, as governed by the Stability Scope.","contentHash":"b05404d164c315e90406d605660299c5bf4d06f0b859cbbbd2f0973b6bbd000f","addressRefs":[]},"3e00cf4d-8b10-4182-bb3d-08b63bc55aeb":{"id":"3e00cf4d-8b10-4182-bb3d-08b63bc55aeb","doc_no":"A.4.1.1.1","title":"USDS Launch","type":"Core","depth":4,"parentId":"7e356a45-3d05-4125-9fd7-d3d454e54cdb","order":2999,"content":"In the Endgame Token Launch Phase, USDS was launched as an upgrade to Dai, offering new features, including Token Rewards. Dai can be exchanged to and from USDS at a rate of 1:1.","contentHash":"62e91da84774a73ca88eeec4eaf7a818b9ab4c30923f2ed3f4f09eff9b1133a7","addressRefs":[]},"8f721d05-6f9b-4efe-b737-18f634f9703d":{"id":"8f721d05-6f9b-4efe-b737-18f634f9703d","doc_no":"A.4.1.1.1.1","title":"Gnosis Payment","type":"Core","depth":5,"parentId":"3e00cf4d-8b10-4182-bb3d-08b63bc55aeb","order":3000,"content":"Sky has agreed to compensate Gnosis for the difference between the Sky Savings Rate and the Dai Savings Rate on xDai balances for the period between March 1, 2025 and October 28, 2025.\n\nThe amount of this payment is 1,806,670 USDS and the recipient address on the Ethereum Mainnet is `0x849d52316331967b6ff1198e5e32a0eb168d039d`. This payment should be included in the next available Executive Vote as determined by the Core Facilitator and is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"91594580ee7966d9d4c801e0fde4d42b59ac9de11e62650df4ceae27358f7e3d","addressRefs":["0x849d52316331967b6ff1198e5e32a0eb168d039d"]},"8e505278-67d9-4c89-afe4-992d5d846fb8":{"id":"8e505278-67d9-4c89-afe4-992d5d846fb8","doc_no":"A.4.1.2","title":"SKY","type":"Section","depth":3,"parentId":"e5089a2a-22b0-47fd-b0c2-a93017a2c71a","order":3001,"content":"SKY is the governance token of the Sky Protocol. It grants voting rights in the Sky Governance system. Its liquidity is boosted by the Smart Burn Engine, as governed by the Stability Scope.","contentHash":"b089d20f5f39036a9dd089eeb2151e29792cfc749588f7f8333b12bc9bedc8f4","addressRefs":[]},"6bb8b5b2-a2a8-4728-bddb-28bf054de9b6":{"id":"6bb8b5b2-a2a8-4728-bddb-28bf054de9b6","doc_no":"A.4.1.2.1","title":"MKR To SKY Upgrade","type":"Core","depth":4,"parentId":"8e505278-67d9-4c89-afe4-992d5d846fb8","order":3002,"content":"Historically, MKR was the governance token of the Sky Protocol. As part of the transition to the Endgame, the technical infrastructure of the Sky Protocol was upgraded to use SKY as its governance token rather than MKR.","contentHash":"60bc8c70913ca69f92c2f0a5875ce4bf351b01fd88c6413eacf4c5ae5e66640d","addressRefs":[]},"eaa5f1ae-f336-49f8-b5d3-7bb01984ba0e":{"id":"eaa5f1ae-f336-49f8-b5d3-7bb01984ba0e","doc_no":"A.4.1.2.1.1","title":"MKR To SKY Upgrade Approval","type":"Core","depth":5,"parentId":"6bb8b5b2-a2a8-4728-bddb-28bf054de9b6","order":3003,"content":"**MKR holders have voted to approve the deprecation of MKR as the governance token of the Sky Protocol with full knowledge of the changes being proposed. See **[**https://vote.makerdao.com/polling/QmcZNZg3**](https://vote.makerdao.com/polling/QmcZNZg3)**. This deprecation includes all actions defined in **[**A.4.1.2.1 - MKR To SKY Upgrade**](6bb8b5b2-a2a8-4728-bddb-28bf054de9b6)**, including, but not limited to, the removal of voting rights from MKR and the Delayed Upgrade Penalty**.","contentHash":"4953d5890ba95e7e3b98323791d3897599a0d3fb949354dc990a1ee7c7211db2","addressRefs":[]},"0a26f6d0-1b50-4015-b094-499724796f9e":{"id":"0a26f6d0-1b50-4015-b094-499724796f9e","doc_no":"A.4.1.2.1.1.1","title":"MKR To SKY Conversion Contract","type":"Core","depth":6,"parentId":"eaa5f1ae-f336-49f8-b5d3-7bb01984ba0e","order":3004,"content":"The MKR to SKY conversion contract MKR_SKY allows users to upgrade from MKR to SKY at a conversion rate of 1 MKR to 24,000 SKY, subject to the Delayed Upgrade Penalty specified in [A.4.1.2.1.1.1.1 - MKR To SKY Upgrade Penalty](ec820ddb-5d12-43d8-81b7-a7602a70332a).","contentHash":"3ca8ce11800d11d4b369ce267b3dddc16fc5c0b7eb1603e0060e9833c8699a69","addressRefs":[]},"ec820ddb-5d12-43d8-81b7-a7602a70332a":{"id":"ec820ddb-5d12-43d8-81b7-a7602a70332a","doc_no":"A.4.1.2.1.1.1.1","title":"MKR To SKY Upgrade Penalty","type":"Core","depth":6,"parentId":"eaa5f1ae-f336-49f8-b5d3-7bb01984ba0e","order":3005,"content":"In the September 18, 2025 Executive Vote, the Delayed Upgrade Penalty for the MKR to SKY conversion contract was set to 1%. The Delayed Upgrade Penalty will be increased gradually at the rate of 1 percentage point per 3 months thereafter.","contentHash":"4c4ae36013204991874d17dab73621b4c1df8c48c626c4163cd5adf696609aa0","addressRefs":[]},"c72ca16f-14d1-4aca-978e-ba9efe6d80bc":{"id":"c72ca16f-14d1-4aca-978e-ba9efe6d80bc","doc_no":"A.4.1.2.2","title":"Deflationary Tokenomics","type":"Core","depth":4,"parentId":"8e505278-67d9-4c89-afe4-992d5d846fb8","order":3006,"content":"The documents herein set forth the core deflationary tokenomics of the SKY token.","contentHash":"8de966b957e57ccfa474ea9e2bf1c57a3f744c246e0f89811d3dad310332ab67","addressRefs":[]},"fd196f2c-c36f-479f-9254-c03c8886b559":{"id":"fd196f2c-c36f-479f-9254-c03c8886b559","doc_no":"A.4.1.2.2.1","title":"Initial Token Supply","type":"Core","depth":5,"parentId":"c72ca16f-14d1-4aca-978e-ba9efe6d80bc","order":3007,"content":"The initial token supply of SKY tokens is derived from the total number of legacy MKR tokens as of the launch of Sky, multiplied by the conversion ratio of 24,000. SKY is the exclusive governance token of the Sky Protocol and takes over all governance and economic rights previously held by MKR. See [A.4.1.2.1 - MKR To SKY Upgrade](6bb8b5b2-a2a8-4728-bddb-28bf054de9b6).","contentHash":"e467411d32b987b6fb9116684fe684ea9e2b51c3f176dc36e19d0fa0f7e13c4b","addressRefs":[]},"60519e2c-77f7-43ed-8eb4-a7b138bebf2d":{"id":"60519e2c-77f7-43ed-8eb4-a7b138bebf2d","doc_no":"A.4.1.2.2.2","title":"No New Token Emissions","type":"Core","depth":5,"parentId":"c72ca16f-14d1-4aca-978e-ba9efe6d80bc","order":3008,"content":"No new SKY tokens may be emitted except for (1) emissions required to recapitalize the protocol if it is at risk of insolvency (see [A.3.6 - SKY Backstop](4d8b0d82-97da-4041-b185-4b98c2779cbe)) and (2) temporary emissions that are being deprecated and fully offset by corresponding burns, resulting in no net increase to the intended long-term token supply (see [A.4.1.2.2.4 - Deprecated Emissions Mechanisms](2f3962e4-c79e-4583-82df-31239dfb84a4)).","contentHash":"5522a89c2a18419596d8da59619a1a245aa116763fc3a075606be5e19e47f6fb","addressRefs":[]},"5b94d42a-28fa-40fa-8948-ba3113a4d5b8":{"id":"5b94d42a-28fa-40fa-8948-ba3113a4d5b8","doc_no":"A.4.1.2.2.3","title":"Burning Of Existing Tokens","type":"Core","depth":5,"parentId":"c72ca16f-14d1-4aca-978e-ba9efe6d80bc","order":3009,"content":"At the same time that no new SKY tokens are issued, SKY tokens are bought back and burned on a regular basis, using a portion of the Net Revenue of the Protocol as dictated by the Treasury Management Function. See [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121). As a result, the total supply of SKY tokens will continue to decrease over time.","contentHash":"31a3ba1033f3942aca8edeb3133c6c9d318ddaaa75395b68e67871b039e18eb2","addressRefs":[]},"2f3962e4-c79e-4583-82df-31239dfb84a4":{"id":"2f3962e4-c79e-4583-82df-31239dfb84a4","doc_no":"A.4.1.2.2.4","title":"Deprecated Emissions Mechanisms","type":"Core","depth":5,"parentId":"c72ca16f-14d1-4aca-978e-ba9efe6d80bc","order":3010,"content":"The subdocuments herein define legacy mechanisms involving the issuance of new SKY tokens. Each of these mechanisms has been deprecated. While these mechanisms did not increase the net supply of SKY tokens, they have been replaced with solutions that do not involve any emissions of SKY tokens, as defined in the documents herein.","contentHash":"1df3c146935b894a2595abdbb52f1d02823ac7598010aa70e8d7ece39f23dc9b","addressRefs":[]},"8189e776-d631-44a0-81e5-3b2d5d88ef54":{"id":"8189e776-d631-44a0-81e5-3b2d5d88ef54","doc_no":"A.4.1.2.2.4.1","title":"SKY Token Rewards Emissions","type":"Core","depth":6,"parentId":"2f3962e4-c79e-4583-82df-31239dfb84a4","order":3011,"content":"USDS users may be able to earn SKY Rewards. See [A.4.3.2 - Token Reward Mechanism](3ff5a7b2-db91-41ab-be19-ddb068b36cc7). These rewards were previously funded by emissions of new SKY tokens.\n\nThese ongoing emissions were eliminated and replaced with a solution that funds these rewards using SKY held by the Sky Protocol.\n\nAt the same time that this new solution was implemented, SKY tokens equal to the total SKY emissions previously used to fund SKY Rewards, including the Early Bird Reward (see [A.5.3.1.1.1 - Token Distribution](eaf8cf29-90fd-4b9b-b0a8-02ce8386908c)), were burned from SKY held by the Sky Protocol.\n\nThe combination of these actions achieved a state where the number of total SKY tokens is exactly the same as if SKY Rewards had never been funded with protocol emissions.","contentHash":"914a5878603d0a6ca87bb6611a60e8546d87865deb81ceb09346d7a3116d16f8","addressRefs":[]},"676636df-729d-46e3-bf34-89d0d33e8051":{"id":"676636df-729d-46e3-bf34-89d0d33e8051","doc_no":"A.4.1.2.2.4.2","title":"MKR To SKY Conversion Emissions","type":"Core","depth":6,"parentId":"2f3962e4-c79e-4583-82df-31239dfb84a4","order":3012,"content":"The legacy MKR to SKY conversion contract (Legacy Conversion Contract) burned MKR and minted new SKY. The new MKR to SKY conversion contract (New Conversion Contract) instead burns MKR and issues SKY from the existing supply of preminted SKY.\n\nThe Legacy Conversion Contract was disabled as specified in [A.4.1.2.2.4.2.1 - Disabling Legacy Conversion Contract](1b8248bf-5d88-4d67-8c4a-21981a0aa937). To offset SKY minted by the Legacy Conversion Contract after the deployment of the New Conversion Contract, an equivalent amount of preminted SKY was burned. This action ensured the total SKY token supply remains as if these specific emissions from the Legacy Conversion Contract had not occurred.","contentHash":"f193b42434017751b7335f78b01a7f5b90220c659e56af754200a6cb6192c378","addressRefs":[]},"1b8248bf-5d88-4d67-8c4a-21981a0aa937":{"id":"1b8248bf-5d88-4d67-8c4a-21981a0aa937","doc_no":"A.4.1.2.2.4.2.1","title":"Disabling Legacy Conversion Contract","type":"Core","depth":6,"parentId":"2f3962e4-c79e-4583-82df-31239dfb84a4","order":3013,"content":"The disabling of the Legacy Conversion Contract was executed in the June 26, 2025 Executive Vote.","contentHash":"8daf7c844e934688f636691bcc510fb5fc7b848d13e55063c3d29db46e855356","addressRefs":[]},"f6d2bae6-7ebc-42cd-a507-900f4bcfb98f":{"id":"f6d2bae6-7ebc-42cd-a507-900f4bcfb98f","doc_no":"A.4.2","title":"SkyLink","type":"Article","depth":2,"parentId":"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b","order":3014,"content":"SkyLink is a multichain system that enables native crosschain transfer of Sky Ecosystem-related tokens to other blockchains, including Ethereum L2s and major L1s.","contentHash":"d9bcfabf835f35101e6fd4afc20a4ec735b87ed1f3eb75fcb7a5bf7b59f7b3df","addressRefs":[]},"9538d851-c874-4eba-9efd-0c3e0f29a0d4":{"id":"9538d851-c874-4eba-9efd-0c3e0f29a0d4","doc_no":"A.4.2.1","title":"Multichain Support Native Mechanisms","type":"Section","depth":3,"parentId":"f6d2bae6-7ebc-42cd-a507-900f4bcfb98f","order":3015,"content":"SkyLink deployments support features including the Savings Rate Mechanism (including sUSDS), the Token Rewards Mechanism and the SKY Staking Mechanism.","contentHash":"d08f7012012fa0eb29c6836dfb3aca9a657844f737179b1332f0bf454d87ffb9","addressRefs":[]},"c64a37d4-08a8-41bb-beae-4e976b6d0982":{"id":"c64a37d4-08a8-41bb-beae-4e976b6d0982","doc_no":"A.4.3","title":"Savings Rate And Token Reward Mechanism","type":"Article","depth":2,"parentId":"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b","order":3016,"content":"This Article regulates the rewards benefiting Dai users and USDS users for holding each Stablecoin. DAI users can access the legacy DAI Savings Rate Mechanism. USDS users can access a built-in Savings Rate, and also potentially earn rewards through Token Reward Mechanisms, including SKY and Agent tokens, as specified in the subdocuments herein.","contentHash":"9e69fc0fd1d86a9924af8bd6d3015b822fe19308c433ac76559e99d46fb5476f","addressRefs":[]},"95f2454b-c1c3-476c-b5f8-3f4fead2e2cc":{"id":"95f2454b-c1c3-476c-b5f8-3f4fead2e2cc","doc_no":"A.4.3.1","title":"Savings Rates","type":"Section","depth":3,"parentId":"c64a37d4-08a8-41bb-beae-4e976b6d0982","order":3017,"content":"The Savings Rate Mechanism includes both the legacy Dai Savings Rate Mechanism and the Sky Savings Rate. The Sky Savings Rate includes a built-in sUSDS mechanism. The Savings Rate is governed by the Stability Scope.","contentHash":"266f575a31242c5b74e6ee891415b6187297b6866a97df03a9b1a1f9ab77c844","addressRefs":[]},"3ff5a7b2-db91-41ab-be19-ddb068b36cc7":{"id":"3ff5a7b2-db91-41ab-be19-ddb068b36cc7","doc_no":"A.4.3.2","title":"Token Reward Mechanism","type":"Section","depth":3,"parentId":"c64a37d4-08a8-41bb-beae-4e976b6d0982","order":3018,"content":"The Token Rewards Mechanism allows USDS users to potentially earn SKY and Agent token rewards as specified in the subdocuments herein.","contentHash":"7573e6838a4b50d5516ae3f959012390d4fe9e46d98dd353d717e4499b1528ca","addressRefs":[]},"caba97e4-4d4d-4aa9-9ed4-f0d1c8b1c552":{"id":"caba97e4-4d4d-4aa9-9ed4-f0d1c8b1c552","doc_no":"A.4.3.2.1","title":"SKY Token Rewards","type":"Core","depth":4,"parentId":"3ff5a7b2-db91-41ab-be19-ddb068b36cc7","order":3019,"content":"SKY token rewards are not currently available to USDS users.","contentHash":"e3017015a3b5f53a81e89a4ff65ec385312149ee39825843f034d5aed493423e","addressRefs":[]},"4f56e3a5-7d4d-4da7-9045-d4d88fabc756":{"id":"4f56e3a5-7d4d-4da7-9045-d4d88fabc756","doc_no":"A.4.3.2.2","title":"SPK Token Rewards","type":"Core","depth":4,"parentId":"3ff5a7b2-db91-41ab-be19-ddb068b36cc7","order":3020,"content":"SPK token rewards are available to USDS users as specified in [A.2.8.2.2.2.1.2.2.2 - Spark Token Reward Distribution Schedule](1f412288-af14-4aab-84e9-79f2e0c39100).","contentHash":"0fd1083609a3ab88dcba480f9eeb3e58bb71f2a5147d8f071d0b15c815106e6f","addressRefs":[]},"b8891a30-f255-4694-895c-4399df916da3":{"id":"b8891a30-f255-4694-895c-4399df916da3","doc_no":"A.4.4","title":"SKY Staking Mechanism","type":"Article","depth":2,"parentId":"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b","order":3021,"content":"This Article governs the SKY Staking Mechanism that grants rewards on staked SKY tokens and its associated SKY-backed borrowing mechanism funded via the stUSDS token.","contentHash":"7ad8e4d0146e1820fcb9d59d9fb0e6cd9bf1156b7eb864259e808fbb7ba0ab89","addressRefs":[]},"626bd71c-b413-41b7-a5fe-39fd0d43dbf5":{"id":"626bd71c-b413-41b7-a5fe-39fd0d43dbf5","doc_no":"A.4.4.1","title":"SKY Staking","type":"Section","depth":3,"parentId":"b8891a30-f255-4694-895c-4399df916da3","order":3022,"content":"SKY holders can stake their tokens via the SKY Staking Mechanism available on Ethereum Mainnet and SkyLink Deployments. SKY stakers earn rewards sourced from the Sky Treasury Management Function. SKY stakers may be able to earn USDS rewards, SKY rewards, and Agent Token Rewards, as determined by Sky Governance. SKY stakers can also borrow USDS against their staked collateral using the SKY-backed borrowing mechanism defined herein.","contentHash":"f4f98de804e44522ae05f99282677830c2cd5186b2cca364afd29c3f94e924a8","addressRefs":[]},"e945372c-f526-45b9-af12-135f0eb6e830":{"id":"e945372c-f526-45b9-af12-135f0eb6e830","doc_no":"A.4.4.1.1","title":"SKY Unstaking","type":"Core","depth":4,"parentId":"626bd71c-b413-41b7-a5fe-39fd0d43dbf5","order":3023,"content":"SKY stakers can unstake their staked SKY at any time without penalty, provided the SKY is unencumbered by any borrowed USDS.","contentHash":"7db10ee72066bf4ae9b8a9f16be8ecb1ebfe82a1ec107078e68505a18b75ba81","addressRefs":[]},"a98a1bfe-5713-43f5-a8bd-83c5808900b8":{"id":"a98a1bfe-5713-43f5-a8bd-83c5808900b8","doc_no":"A.4.4.1.2","title":"SKY Staking Rewards","type":"Core","depth":4,"parentId":"626bd71c-b413-41b7-a5fe-39fd0d43dbf5","order":3024,"content":"The documents herein define the SKY Staking Rewards. SKY stakers may choose between receiving USDS, SKY, or Agent Token rewards.","contentHash":"71756911f78a4faa3d7147bd66b96382c0783fc2976304e7ce3a8f7d6e26868e","addressRefs":[]},"e1c77a6a-5b94-4d40-a205-43c703a780e2":{"id":"e1c77a6a-5b94-4d40-a205-43c703a780e2","doc_no":"A.4.4.1.2.1","title":"Sources Of Rewards","type":"Core","depth":5,"parentId":"a98a1bfe-5713-43f5-a8bd-83c5808900b8","order":3025,"content":"SKY stakers are eligible to receive rewards sourced from the Sky Treasury Management Function (TMF) or the Agent Token Distribution mechanism defined in [A.4.5 - Distribution Of Agent Tokens](e2f1f01f-3303-41c3-b337-f09eb41ba6be).","contentHash":"5d94bbe2bcce7b0815712647f560aedd36b31f85e154e13b4deec515b45d3e39","addressRefs":[]},"6cacdc1c-bdfa-4f68-bdb4-bf31943dcfba":{"id":"6cacdc1c-bdfa-4f68-bdb4-bf31943dcfba","doc_no":"A.4.4.1.2.1.1","title":"Treasury Management Function-Derived Rewards","type":"Core","depth":6,"parentId":"e1c77a6a-5b94-4d40-a205-43c703a780e2","order":3026,"content":"USDS rewards and SKY rewards for SKY stakers are funded from the Staking Rewards allocation of the Sky Treasury Management Function (see [A.2.3.1.2.5 - Step 4: Staking Rewards](bb163691-630e-4fda-88f1-96381a649fa0)) and distributed continuously, pro-rata based on the SKY stake of eligible wallets. Distribution parameters are updated at each Monthly Settlement Cycle.","contentHash":"266231fa3fa47099654f9ffa300b7545c338d38d7ae845ca7f0eb67c1d1d6c14","addressRefs":[]},"6aa85298-4f1c-4dc5-a973-99bc1e5293d1":{"id":"6aa85298-4f1c-4dc5-a973-99bc1e5293d1","doc_no":"A.4.4.1.2.1.2","title":"Agent Token Distribution Rewards","type":"Core","depth":6,"parentId":"e1c77a6a-5b94-4d40-a205-43c703a780e2","order":3027,"content":"SKY stakers are eligible to receive Agent Token rewards as specified in [A.4.5 - Distribution Of Agent Tokens](e2f1f01f-3303-41c3-b337-f09eb41ba6be). Agent Tokens are distributed continuously, pro‑rata by staked SKY, among wallets that have opted to receive a specific Agent Token. Distribution parameters are updated at each Monthly Settlement Cycle.","contentHash":"304ba5bc39dd2c923da5045d4628a48393b91222aa825b349c751e28f969ad62","addressRefs":[]},"264b1787-cd75-4d28-9c14-c7d5a724eba7":{"id":"264b1787-cd75-4d28-9c14-c7d5a724eba7","doc_no":"A.4.4.1.3","title":"SKY-Backed Borrowing","type":"Core","depth":4,"parentId":"626bd71c-b413-41b7-a5fe-39fd0d43dbf5","order":3028,"content":"SKY stakers can borrow USDS against their staked SKY collateral. This borrowing will be facilitated exclusively by the stUSDS system which will provide protocol-independent, or segregated, risk capital. The stUSDS elements are outlined in the subdocuments below.","contentHash":"0eb66909353e86e845d61f918f42b6d7f696767224e8e4de1935d7e8f24f4272","addressRefs":[]},"f81ed4c8-ccfc-492a-b8f8-6f284158d8c3":{"id":"f81ed4c8-ccfc-492a-b8f8-6f284158d8c3","doc_no":"A.4.4.1.3.1","title":"stUSDS Function","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3029,"content":"stUSDS is a yield-bearing token representing USDS deposited into the stUSDS contract. Its primary function is to provide segregated risk capital for the SKY-backed borrowing mechanism. Users convert USDS to stUSDS to provide this capital and earn the stUSDS Rate. See [A.4.4.1.3.2 - stUSDS Rate](7e51d5a7-0707-4fba-999b-a1becd5f0192). stUSDS can be converted back to USDS subject to available unutilized liquidity in the stUSDS converter contract.","contentHash":"798f79298a2f52ba4eee6e6ede41080a639fea2b1d61055719dad53af6fff4d2","addressRefs":[]},"7e51d5a7-0707-4fba-999b-a1becd5f0192":{"id":"7e51d5a7-0707-4fba-999b-a1becd5f0192","doc_no":"A.4.4.1.3.2","title":"stUSDS Rate","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3030,"content":"The variable yield earned by stUSDS holders is calculated using the formula:\n\n`stUSDS Rate = Sky Savings Rate + (SKY Borrow Rate - SKY Borrow Minimum Rate) * Utilization - Rfactor * f(Utilization)`","contentHash":"e7e2b9882a9241ded7040c72ec6e348da6eb028fa2de63924fc326a4041e51ef","addressRefs":[]},"b9a9d09d-57c5-42cd-994f-f5689996f635":{"id":"b9a9d09d-57c5-42cd-994f-f5689996f635","doc_no":"A.4.4.1.3.2.1","title":"Parameters Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3031,"content":"The parameters of the stUSDS Rate formula are further defined in the documents herein.","contentHash":"71816787bf94df530f2b787b7cde9864b06ce66107ad65ab2192346d94a685ce","addressRefs":[]},"5878457b-4ff8-4621-bf8e-abd52f02ec6a":{"id":"5878457b-4ff8-4621-bf8e-abd52f02ec6a","doc_no":"A.4.4.1.3.2.1.1","title":"Sky Savings Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3032,"content":"`Sky Savings Rate` is the Sky Savings Rate defined in [A.3.1.2.2 - Sky Savings Rate](2674cccb-d779-4868-b83f-8cb86648c88a).","contentHash":"671a1405af899f0a13b31be3bfa147d68d998136dce9c5f8190fc917b8a459b7","addressRefs":[]},"78cab555-534d-4e7e-989c-d22d90d02d9e":{"id":"78cab555-534d-4e7e-989c-d22d90d02d9e","doc_no":"A.4.4.1.3.2.1.2","title":"SKY Borrow Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3033,"content":"`SKY Borrow Rate` is the SKY Borrow Rate defined in [A.4.4.1.3.5 - SKY Borrow Rate](5e546766-a0c0-4744-9ca9-5509db14bc30).","contentHash":"a12708a273890aa8e0642396d51451fc95c090865bd823bb4c3c752d91b44ba8","addressRefs":[]},"2126d7ac-b0e2-46f2-95e8-b9973e09a630":{"id":"2126d7ac-b0e2-46f2-95e8-b9973e09a630","doc_no":"A.4.4.1.3.2.1.3","title":"SKY Borrow Minimum Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3034,"content":"`SKY Borrow Minimum Rate` is the SKY Borrow Minimum Rate defined in [A.4.4.1.3.5.2 - SKY Borrow Minimum Rate](6e329dd6-eda5-43ce-9899-b3a03ede8d0b).","contentHash":"ffe64ada360880938032997309e2ecf2b224fec1c7fcfc5fb1ef7b1661978b22","addressRefs":[]},"337c4f67-685f-42bd-8237-553ed913b89f":{"id":"337c4f67-685f-42bd-8237-553ed913b89f","doc_no":"A.4.4.1.3.2.1.4","title":"Utilization Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3035,"content":"`Utilization` is the percent of funds in the stUSDS contract that are used to fund borrowing against staked SKY.","contentHash":"006e96523061925c93721ce6125dcc304e8e6e00878ecbc49f02970ff9f8abae","addressRefs":[]},"4af5cfaf-30b3-41b9-bb22-3253218c62d0":{"id":"4af5cfaf-30b3-41b9-bb22-3253218c62d0","doc_no":"A.4.4.1.3.2.1.4.1","title":"Utilization Calculation","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3036,"content":"The `Utilization` is calculated as a time-weighted utilization over a one (1) day interval.","contentHash":"5c0a96bdd5f0669a3cfe9d1a616e9e68f8c1d617cc80907121550680ec2f4910","addressRefs":[]},"33303813-37b7-4aa2-a8e0-3c779c0ed600":{"id":"33303813-37b7-4aa2-a8e0-3c779c0ed600","doc_no":"A.4.4.1.3.2.1.4.1.1","title":"Time-Weighted Utilization","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3037,"content":"The documents herein define the process to calculate time-weighted utilization.","contentHash":"9eff8903baf68c4e1cd7ec452d208286c331e3e95c2358fc126754ffb52e25c5","addressRefs":[]},"0110848f-719f-47e7-8f5a-219d6b3e4ee5":{"id":"0110848f-719f-47e7-8f5a-219d6b3e4ee5","doc_no":"A.4.4.1.3.2.1.4.1.1.1","title":"Determine Start And End Times","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3038,"content":"First, the start time $T_{0}$ and end time $T_{n}$ of the interval, over which time-weighted utilization are to be calculated, are selected.","contentHash":"cc6376fa7ba870495b6c354538f351a7b8e28a16a1db72d761229ce8791e0abc","addressRefs":[]},"e196d2f1-fb65-4e31-b511-5ed9ebbaa164":{"id":"e196d2f1-fb65-4e31-b511-5ed9ebbaa164","doc_no":"A.4.4.1.3.2.1.4.1.1.2","title":"Collect Borrow And Supply Events","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3039,"content":"Data is then collected on all supply and borrow events, sorted by time, where:\n\n- $t_{i}$ is the timestamp of event $i$;\n- $B_{i}$ is the total amount borrowed at time $t_{i}$;\n- $S_{i}$ is the total amount supplied at time $t_{i}$; and\n- $U_{i}$ is the utilization at time $t_{i}$, $\\frac{B_{i}}{S_{i}}$.","contentHash":"a1ea6dbc2c6aff3382bd61f9a5ce1de8e738228c6edd1141cb68cb3001010652","addressRefs":[]},"9242854f-4b5b-4ca0-9fd4-ca0a4f7dc516":{"id":"9242854f-4b5b-4ca0-9fd4-ca0a4f7dc516","doc_no":"A.4.4.1.3.2.1.4.1.1.3","title":"Insert Synthetic Events","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3040,"content":"If $t_{0}$ is greater than $T_{0}$ then a synthetic event is inserted at $T_{0}$ with values $B_{0}$ and $S_{0}$. Similarly, if $t_{n}$ is less than $T_{n}$ then a synthetic event is inserted at $T_{n}$ with values $B_{n}$ and $S_{n}$.","contentHash":"3df2443dfc75b19fabade99938dbee5902ba139cc487472f2779e3aeb5de6996","addressRefs":[]},"08735694-ee69-4315-8ba6-6d08760bdb1c":{"id":"08735694-ee69-4315-8ba6-6d08760bdb1c","doc_no":"A.4.4.1.3.2.1.4.1.1.4","title":"Calculate Time-Weighted Utilization","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3041,"content":"Finally, the time-weighted utilization is calculated using the following formula:\n\n$$\\text{Util}_{\\mathrm{avg}} = \\frac{\\sum_{i=0}^{n-1} U_i \\cdot (t_{i+1} - t_i)}{T_n - T_0}$$","contentHash":"c016813f7404354958096da7cd5f34deeb178029c8ca2b878d8ef2080b381bfd","addressRefs":[]},"53ed66f4-d010-4370-b83b-e36a185f12ad":{"id":"53ed66f4-d010-4370-b83b-e36a185f12ad","doc_no":"A.4.4.1.3.2.1.4.1.1.5","title":"Reference Implementation","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3042,"content":"A reference implementation of the time-weighted utilization formula is included herein. The reference implementation uses sample data and a 30 day interval for illustrative purposes.\n\n```\n# Your list of real events: (timestamp, total_borrowed, total_supply)\nevents = [\n(datetime(2025, 7, 25, 10), 100_000, 200_000),\n(datetime(2025, 7, 25, 16), 120_000, 210_000),\n(datetime(2025, 7, 26, 8), 130_000, 220_000),\n(datetime(2025, 7, 27, 12), 110_000, 215_000),\n(datetime(2025, 7, 28, 9), 140_000, 225_000),\n]\n\n# Ensure events are sorted\nevents.sort()\n\n# Get time window\nnow = datetime.utcnow()\nstart_time = now - timedelta(days=30)\n\n# Add synthetic first event (30d ago) using earliest known borrow/supply\nfirst_real_ts, first_borrow, first_supply = events[0]\nif first_real_ts > start_time:\nevents.insert(0, (start_time, first_borrow, first_supply))\n\n# Add synthetic final event (now) using most recent known borrow/supply\nlast_real_ts, last_borrow, last_supply = events[-1]\nif last_real_ts < now:\nevents.append((now, last_borrow, last_supply))\n\n# Step 1: Compute utilization per event\nutilizations = []\nfor ts, borrow, supply in events:\nutilization = borrow / supply if supply != 0 else 0\nutilizations.append((ts, utilization))\n\n# Step 2: Compute time-weighted utilization average\nweighted_sum = 0\ntotal_time = 0\n\nfor i in range(len(utilizations) - 1):\nts1, util1 = utilizations[i]\nts2, _ = utilizations[i + 1]\n\ntime_diff = (ts2 - ts1).total_seconds()\nweighted_sum += util1 * time_diff\ntotal_time += time_diff\n\navg_utilization = weighted_sum / total_time if total_time > 0 else 0\n\nprint(f\"30-day time-weighted average utilization: {avg_utilization:.2%}\")\n```","contentHash":"744290adc8a61c51387df2b8911e511c7d01695b584aff13d2e3f836bc874dd4","addressRefs":[]},"6300d908-4ed3-4174-95a5-d9d43864a5a6":{"id":"6300d908-4ed3-4174-95a5-d9d43864a5a6","doc_no":"A.4.4.1.3.2.1.5","title":"Rfactor Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3043,"content":"`Rfactor` is calculated using the formula:\n\n$$\nRfactor = \\frac{2u_m - 1}{2u_m \\left( u_{opt}(\\alpha + 1) - 1 + \\frac{\\beta u_{opt}}{slope1} \\right)}\n$$\n\nThe parameters of this formula are specified in the documents herein.","contentHash":"8d349c5da61ea063be3d7616ce8c95809793de6e38c0c263ef9b4e73fac85539","addressRefs":[]},"be7b6a5a-cd25-4822-a20a-e17c0d1176de":{"id":"be7b6a5a-cd25-4822-a20a-e17c0d1176de","doc_no":"A.4.4.1.3.2.1.5.1","title":"Maximum Profit Utilization Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3044,"content":"$u_{m}$ is the maximum profit utilization.","contentHash":"bf73ad893597f5bf4455cc7b860331051472429124b6554611eb09c67f4b916d","addressRefs":[]},"846452c4-509d-42b0-8e8c-e426bbcc4ce0":{"id":"846452c4-509d-42b0-8e8c-e426bbcc4ce0","doc_no":"A.4.4.1.3.2.1.5.1.1","title":"Maximum Profit Utilization Current Value","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3045,"content":"The current value of $u_{m}$ is 70%.","contentHash":"8ad7354afdb1b6d10088aad7fc419efb9b8c59562b3cd67718fc6bab6e330682","addressRefs":[]},"1481bf21-dc05-4fea-a929-9741ea903206":{"id":"1481bf21-dc05-4fea-a929-9741ea903206","doc_no":"A.4.4.1.3.2.1.5.2","title":"Target Utilization Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3046,"content":"$u_{opt}$ is the target utilization specified in [A.4.4.1.3.5.1 - Rate Setting Mechanism](5ad3e32c-9b5c-431a-bc20-e236194b65e8).","contentHash":"e2e93e031e8b36af031c15d029e700537ffeaee6838433bad60fd4ad8b2daafd","addressRefs":[]},"e9cfb75d-2d5b-448e-a3e1-784326a94ac4":{"id":"e9cfb75d-2d5b-448e-a3e1-784326a94ac4","doc_no":"A.4.4.1.3.2.1.5.3","title":"Alpha Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3047,"content":"$\\alpha$ is calculated using the formula:\n\n`alpha = ((SKY Borrow Maximum Rate - SKY Borrow Minimum Rate) / Slope 1) - 1`\n\nThe parameters of this formula are specified in the documents herein.","contentHash":"01c7c64bfe15bfab768ca3fcd40d629a37ab2aae07787e8ce47b84e3b9e19373","addressRefs":[]},"eb77a744-db25-40b0-b51c-dd3187941cc5":{"id":"eb77a744-db25-40b0-b51c-dd3187941cc5","doc_no":"A.4.4.1.3.2.1.5.3.1","title":"SKY Borrow Maximum Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3048,"content":"`SKY Borrow Maximum Rate` is the maximum value of the SKY Borrow Rate at 100% Utilization.","contentHash":"14709d06879383ed7ed8e5af9e7bb2c29f1435d28ef4d876ad3b0377f4f73f71","addressRefs":[]},"609ca82c-d3c8-4ad9-bc14-d601dace4e40":{"id":"609ca82c-d3c8-4ad9-bc14-d601dace4e40","doc_no":"A.4.4.1.3.2.1.5.3.1.1","title":"SKY Borrow Maximum Rate Current Value","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3049,"content":"The current value of the `SKY Borrow Maximum Rate` is 30%.","contentHash":"38ce0b2775bfe5a088d83401cda7078aea2ee0e2cdb4ee5a341bda02485bd442","addressRefs":[]},"b0831a3c-b37b-4daa-838a-74a32a0cbe76":{"id":"b0831a3c-b37b-4daa-838a-74a32a0cbe76","doc_no":"A.4.4.1.3.2.1.5.3.2","title":"SKY Borrow Minimum Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3050,"content":"`SKY Borrow Minimum Rate` is the SKY Borrow Minimum Rate specified in [A.4.4.1.3.5.2 - SKY Borrow Minimum Rate](6e329dd6-eda5-43ce-9899-b3a03ede8d0b).","contentHash":"44770a1f9fbac92729b7b67ef50a06b6ba02cf398499c7442fb37a5fe9c0e24a","addressRefs":[]},"f9ad84ee-2e98-4d74-b61a-efd25e8d17b8":{"id":"f9ad84ee-2e98-4d74-b61a-efd25e8d17b8","doc_no":"A.4.4.1.3.2.1.5.3.3","title":"Slope 1 Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3051,"content":"`Slope 1` is the Slope 1 parameter specified in [A.4.4.1.3.5.1.1.4 - Slope 1](f22da959-a76e-477a-a87b-a32c429d2ec0).","contentHash":"ead39cd84f59764fdf36a738d78471ca99d8a20600abff6feabe99dd17200fdc","addressRefs":[]},"182418ba-47ad-416b-a5fe-440ac92511ec":{"id":"182418ba-47ad-416b-a5fe-440ac92511ec","doc_no":"A.4.4.1.3.2.1.5.4","title":"Beta Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3052,"content":"$\\beta$ is a tuning parameter that determines how much profit is made at maximum utilization.","contentHash":"8562db404f12e8f1ed5a503479968a3df7112ed2f850c0c7010ff60913982882","addressRefs":[]},"47c60bd6-c75f-4772-a5f6-18b8054eeb9f":{"id":"47c60bd6-c75f-4772-a5f6-18b8054eeb9f","doc_no":"A.4.4.1.3.2.1.5.4.1","title":"Beta Current Value","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3053,"content":"The current value of $\\beta$ is 100%.","contentHash":"c6673c8d8d96e143d08d1fe51e8484e3c6775252470f1297998301a14d22ca7d","addressRefs":[]},"837aa41f-d5d2-4482-a33f-7538a6431e7f":{"id":"837aa41f-d5d2-4482-a33f-7538a6431e7f","doc_no":"A.4.4.1.3.2.1.5.5","title":"Slope 1 Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3054,"content":"$slope1$ is the Slope 1 parameter specified in [A.4.4.1.3.5.1.1.4 - Slope 1](f22da959-a76e-477a-a87b-a32c429d2ec0).","contentHash":"692676a260a815978206f57b3fbcd634673e5b2d0023f4adb558f934cfb55a65","addressRefs":[]},"4088de4a-8e43-4988-94ca-43908a225047":{"id":"4088de4a-8e43-4988-94ca-43908a225047","doc_no":"A.4.4.1.3.2.1.6","title":"Utilization Function Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3055,"content":"`f(Utilization)` is calculated using the formula:\n\n`f(Utilization) = Utilization * ((SKY Borrow Maximum Rate - SKY Borrow Minimum Rate + Beta) * Utilization + SKY Borrow Minimum Rate - SKY Borrow Rate)`\n\nThe parameters of this formula are specified in the documents herein.","contentHash":"3adb35bd31f21d4f513088e72f5fbe467b113bd139e4f94352f7dc76cf89d25d","addressRefs":[]},"8ff2ac6c-c34e-4b00-9125-05a5404d75eb":{"id":"8ff2ac6c-c34e-4b00-9125-05a5404d75eb","doc_no":"A.4.4.1.3.2.1.6.1","title":"Utilization Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3056,"content":"`Utilization` is the utilization as specified in [A.4.4.1.3.2.1.4 - Utilization Definition](337c4f67-685f-42bd-8237-553ed913b89f).","contentHash":"17f0efa5de3a47ca84f8422d1820d8cbd997604f53133775f24ed8c4a4aeca59","addressRefs":[]},"3815fba3-bc80-482a-9baf-d201931b26c9":{"id":"3815fba3-bc80-482a-9baf-d201931b26c9","doc_no":"A.4.4.1.3.2.1.6.2","title":"SKY Borrow Maximum Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3057,"content":"`SKY Borrow Maximum Rate` is the SKY Borrow Maximum Rate specified in [A.4.4.1.3.2.1.5.3.1 - SKY Borrow Maximum Rate Definition](eb77a744-db25-40b0-b51c-dd3187941cc5).","contentHash":"661e7229812dfea74d76dbd4a1a9ab757a8961afc4063a7462688d14c84ce996","addressRefs":[]},"d1015b48-32c0-454a-b0a0-7a884f405092":{"id":"d1015b48-32c0-454a-b0a0-7a884f405092","doc_no":"A.4.4.1.3.2.1.6.3","title":"SKY Borrow Minimum Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3058,"content":"`SKY Borrow Minimum Rate` is the SKY Borrow Minimum Rate specified in [A.4.4.1.3.5.2 - SKY Borrow Minimum Rate](6e329dd6-eda5-43ce-9899-b3a03ede8d0b).","contentHash":"44770a1f9fbac92729b7b67ef50a06b6ba02cf398499c7442fb37a5fe9c0e24a","addressRefs":[]},"436398ad-9660-4a8c-9556-6631888586fb":{"id":"436398ad-9660-4a8c-9556-6631888586fb","doc_no":"A.4.4.1.3.2.1.6.4","title":"Beta Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3059,"content":"`Beta` is the beta specified in [A.4.4.1.3.2.1.5.4 - Beta Definition](182418ba-47ad-416b-a5fe-440ac92511ec).","contentHash":"92427b733feb05227fe0444a34291b46d6536dc9e5cd8cd49e02ea18a2c7d3d6","addressRefs":[]},"3bcb6e31-d14f-434e-b3fe-8469a4a49011":{"id":"3bcb6e31-d14f-434e-b3fe-8469a4a49011","doc_no":"A.4.4.1.3.2.1.6.5","title":"SKY Borrow Rate Definition","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3060,"content":"`SKY Borrow Rate` is the SKY Borrow Rate specified in [A.4.4.1.3.5 - SKY Borrow Rate](5e546766-a0c0-4744-9ca9-5509db14bc30).","contentHash":"24c1b38e9a738138cfbc5158dc59ada570f62aad1c1c4c94753e9bbe943c872e","addressRefs":[]},"a63c529d-890f-4955-89b3-e671e5eb5ff7":{"id":"a63c529d-890f-4955-89b3-e671e5eb5ff7","doc_no":"A.4.4.1.3.2.2","title":"Parameters Modification","type":"Core","depth":6,"parentId":"7e51d5a7-0707-4fba-999b-a1becd5f0192","order":3061,"content":"The parameters specified in [A.4.4.1.3.2.1 - Parameters Definition](b9a9d09d-57c5-42cd-994f-f5689996f635) that are set by governance may be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.","contentHash":"14a6e723e4613e827f430486872397ffdc7bff0af656881198a25330998e2edd","addressRefs":[]},"60a37c03-9122-4ef6-9669-2466c335224c":{"id":"60a37c03-9122-4ef6-9669-2466c335224c","doc_no":"A.4.4.1.3.3","title":"stUSDS Holders’ Risk Bearing","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3062,"content":"Holders of stUSDS accept the risk associated with providing capital for SKY-backed borrowing. In the event that the liquidation of a borrower’s staked SKY collateral does not cover the outstanding debt, stUSDS balances will be subject to a haircut proportional to the shortfall. This mechanism ensures that the Sky Protocol is isolated from losses originating from the SKY-backed borrowing facility.","contentHash":"85c56701ca89e87477b5ad2b68322c572cc6535e363f7789d64ac4b82227426f","addressRefs":[]},"f7c00726-64a0-4ba5-8c0d-231d0e27e54c":{"id":"f7c00726-64a0-4ba5-8c0d-231d0e27e54c","doc_no":"A.4.4.1.3.4","title":"Debt Ceiling","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3063,"content":"The maximum amount of USDS that can be borrowed against staked SKY is dynamically determined by, and equal to, the total amount of USDS currently held within the stUSDS contract. This dynamic ceiling will replace the static `DC-IAM` module and parameters associated with protocol-dependent, SKY-backed borrowing.","contentHash":"8026bc6b5efbeda6d47d0f2c9d8174209a616f2dd35df251bd7a611c441d004c","addressRefs":[]},"5e546766-a0c0-4744-9ca9-5509db14bc30":{"id":"5e546766-a0c0-4744-9ca9-5509db14bc30","doc_no":"A.4.4.1.3.5","title":"SKY Borrow Rate","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3064,"content":"The interest rate charged to borrowers (SKY Borrow Rate) is dynamic and market-driven, based on the utilization of funds within the stUSDS contract. This dynamic rate will replace the static `Stability Fee` parameter associated with protocol-dependent, SKY-backed borrowing.","contentHash":"22a3656a0f37192fd2752de26dc5bcda963c5529089927c51587efb5197e6453","addressRefs":[]},"5ad3e32c-9b5c-431a-bc20-e236194b65e8":{"id":"5ad3e32c-9b5c-431a-bc20-e236194b65e8","doc_no":"A.4.4.1.3.5.1","title":"Rate Setting Mechanism","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3065,"content":"The SKY Borrow Rate adjusts to target a 90% utilization rate of the USDS in the stUSDS contract. When stUSDS utilization is below 90%, the rate gradually decreases; when above 90%, it gradually increases. The SKY Borrow Rate cannot fall below the SKY Borrow Minimum Rate. See [A.4.4.1.3.5.2 - SKY Borrow Minimum Rate](6e329dd6-eda5-43ce-9899-b3a03ede8d0b).\n\nThe specific parameters and formula governing the rate of adjustment are specified in the documents herein.","contentHash":"65057ce7964eaa9d105ba23b68779df97f159a932d1c297bf32b7316260ca004","addressRefs":[]},"7e07b3d3-0eb5-449b-abcd-7373b9037691":{"id":"7e07b3d3-0eb5-449b-abcd-7373b9037691","doc_no":"A.4.4.1.3.5.1.1","title":"Rate Setting Parameters","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3066,"content":"The parameters of the rate setting mechanism are specified in the documents herein.","contentHash":"38c7c038248dc01c3a82c435a9e9905fae109c21068d045fb3ed4944c43e84a7","addressRefs":[]},"06440c14-0fc8-42e8-bb16-62c75c007453":{"id":"06440c14-0fc8-42e8-bb16-62c75c007453","doc_no":"A.4.4.1.3.5.1.1.1","title":"Utilization","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3067,"content":"`Utilization` is the percentage of funds in the stUSDS contract that are used to fund borrowing against staked SKY specified in [A.4.4.1.3.2.1.4 - Utilization Definition](337c4f67-685f-42bd-8237-553ed913b89f).","contentHash":"bd579030aab6f70b1c7deb56712e09f9d37f6bb937f19f532b3fd214f36512a3","addressRefs":[]},"d4f5b180-ea44-4962-a79a-9f09b734758d":{"id":"d4f5b180-ea44-4962-a79a-9f09b734758d","doc_no":"A.4.4.1.3.5.1.1.2","title":"Target Utilization","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3068,"content":"`Target Utilization` is the target utilization rate of USDS in the stUSDS contract specified in [A.4.4.1.3.5.1 - Rate Setting Mechanism](5ad3e32c-9b5c-431a-bc20-e236194b65e8).","contentHash":"5968655caa02a9766c42471d315cd98b99afdf19837806443451ef37ec59064d","addressRefs":[]},"30577c68-7d3f-4f96-a228-1ad9c5c8ddd0":{"id":"30577c68-7d3f-4f96-a228-1ad9c5c8ddd0","doc_no":"A.4.4.1.3.5.1.1.3","title":"SKY Borrow Minimum Rate","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3069,"content":"`SKY Borrow Minimum Rate` is the rate that the SKY Borrow Rate cannot fall below specified in [A.4.4.1.3.5.2 - SKY Borrow Minimum Rate](6e329dd6-eda5-43ce-9899-b3a03ede8d0b).","contentHash":"d425a1a4b1c90907d65e0568ab0f600262940d6ed6d19e2c1b4b865e4b7bfe4d","addressRefs":[]},"f22da959-a76e-477a-a87b-a32c429d2ec0":{"id":"f22da959-a76e-477a-a87b-a32c429d2ec0","doc_no":"A.4.4.1.3.5.1.1.4","title":"Slope 1","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3070,"content":"`Slope 1` represents the spread of the SKY Borrow Rate over the SKY Borrow Minimum Rate when Utilization is at Target Utilization.","contentHash":"b8e792373ea28eef8bf68c9cbdfdd166448d732ba9acf89a16957a5e5f37c8de","addressRefs":[]},"ef387e32-b649-45ec-bd7a-c63842802134":{"id":"ef387e32-b649-45ec-bd7a-c63842802134","doc_no":"A.4.4.1.3.5.1.1.4.1","title":"Slope 1 Current Value","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3071,"content":"The current value of the `Slope 1` parameter is 12.575%.","contentHash":"b5633357233c806254c866d43923de911b12453e6ce4f969de25e406356cbe1c","addressRefs":[]},"5ea82a74-73e3-4f35-83ef-02d7af0cf58b":{"id":"5ea82a74-73e3-4f35-83ef-02d7af0cf58b","doc_no":"A.4.4.1.3.5.1.1.4.2","title":"Slope 1 Modification","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3072,"content":"The `Slope 1` parameter may be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.","contentHash":"42b8c143d23a6fe09e6a4ca0f58e7e539d831b14a8b2b3bffa72fb5db3894be9","addressRefs":[]},"fb127571-4e01-4deb-b4cf-8fad2f7c9b71":{"id":"fb127571-4e01-4deb-b4cf-8fad2f7c9b71","doc_no":"A.4.4.1.3.5.1.1.5","title":"Slope 2","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3073,"content":"`Slope 2` represents the spread of the SKY Borrow Rate at 100% Utilization over the SKY Borrow Rate at Target Utilization.","contentHash":"76876135ef4b45a6f4af19c4b7416d7bba4167ef386bac8f9d36046689fe7298","addressRefs":[]},"6d557d64-e579-4285-92b6-ff8f709dab29":{"id":"6d557d64-e579-4285-92b6-ff8f709dab29","doc_no":"A.4.4.1.3.5.1.1.5.1","title":"Slope 2 Current Value","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3074,"content":"The current value of the `Slope 2` parameter is 12.575%.","contentHash":"ce8c2adde54d364800bd7718d867bb13811a9baab623e992533ff38ac77936de","addressRefs":[]},"4446f92c-bb70-4f94-bcf7-d44749ed87b7":{"id":"4446f92c-bb70-4f94-bcf7-d44749ed87b7","doc_no":"A.4.4.1.3.5.1.1.5.2","title":"Slope 2 Modification","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3075,"content":"The `Slope 2` parameter may be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.","contentHash":"bfa307bf940350090ac6ba2afa48ded24e62f86020b55f55fc082a63f038c062","addressRefs":[]},"dbc8ec1b-c9cb-40c1-8ccd-bd7478c42466":{"id":"dbc8ec1b-c9cb-40c1-8ccd-bd7478c42466","doc_no":"A.4.4.1.3.5.1.1.5.3","title":"Slope 2 Methodology","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3076,"content":"Under normal circumstances governance should set the `Slope 2` parameter based on the following formula:\n\n`Slope 2 = Slope 1 * alpha`\n\nThe parameters of this formula are specified in the documents herein.","contentHash":"2f94152c2db472af56dc761093b6948df933f253165d0f13e19110c274290a22","addressRefs":[]},"664f473c-a48a-4961-8352-5dd93b8c5410":{"id":"664f473c-a48a-4961-8352-5dd93b8c5410","doc_no":"A.4.4.1.3.5.1.1.5.3.1","title":"Slope 1 Definition","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3077,"content":"The `Slope 1` parameter is specified in [A.4.4.1.3.5.1.1.4 - Slope 1](f22da959-a76e-477a-a87b-a32c429d2ec0).","contentHash":"98c360d516c4b97b421b54f71702a9846c96b0fa5e9b5dc34a3d0c773f26d9d2","addressRefs":[]},"03a02181-fb87-4bac-83cc-f062cc7dc593":{"id":"03a02181-fb87-4bac-83cc-f062cc7dc593","doc_no":"A.4.4.1.3.5.1.1.5.3.2","title":"Alpha Definition","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3078,"content":"The `alpha` parameter is specified in [A.4.4.1.3.2.1.5.3 - Alpha Definition](e9cfb75d-2d5b-448e-a3e1-784326a94ac4).","contentHash":"6227e6d2230f36d03925dc1dbe0df8be5bd0136733353bd1b0b5617ea91dc1dc","addressRefs":[]},"05e97d4d-37e2-4ed8-acea-a8728fbe0402":{"id":"05e97d4d-37e2-4ed8-acea-a8728fbe0402","doc_no":"A.4.4.1.3.5.1.2","title":"Rate Setting Formula","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3079,"content":"The Sky Borrow Rate is calculated according to the following formula when Utilization is less than or equal to Target Utilization:\n\n`SKY Borrow Rate = SKY Borrow Minimum Rate + Utilization / Target Utilization * Slope 1`\n\nThe SKY Borrow Rate is calculated according to the following formula when Utilization is greater than Target Utilization:\n\n`SKY Borrow Rate = SKY Borrow Minimum Rate + Slope 1 + (Utilization - Target Utilization) / (1 - Target Utilization) * Slope 2`","contentHash":"aee086b7522cc173e37470a47c2b135c6ce255744b1164c623caba40182d1222","addressRefs":[]},"6e329dd6-eda5-43ce-9899-b3a03ede8d0b":{"id":"6e329dd6-eda5-43ce-9899-b3a03ede8d0b","doc_no":"A.4.4.1.3.5.2","title":"SKY Borrow Minimum Rate","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3080,"content":"The SKY Borrow Minimum Rate is calculated according to the following formula:\n\n`SKY Borrow Minimum Rate = Sky Savings Rate + stUSDS Distribution Reward`\n\nThe formula ensures the SKY Borrow Minimum Rate covers the baseline cost of capital (Sky Savings Rate) plus the incentive cost (stUSDS Distribution Reward), preventing value-draining arbitrage where users could borrow below the Sky Savings Rate.","contentHash":"842b7d66fec618861c93e7da72ee8d20ca85222111b45fdc3b146cc22f2fa017","addressRefs":[]},"63e86a25-18f6-4810-a362-d2831781ea2c":{"id":"63e86a25-18f6-4810-a362-d2831781ea2c","doc_no":"A.4.4.1.3.5.2.1","title":"Parameters Definition","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3081,"content":"The parameters of the SKY Borrow Minimum Rate formula are further defined in the documents herein.","contentHash":"3d59953aa613a73d8f8633f2f2c565cd5e0d760fdb49a404342e41c22d4ca0cd","addressRefs":[]},"27839098-86b9-479f-87b7-ffd467c825c8":{"id":"27839098-86b9-479f-87b7-ffd467c825c8","doc_no":"A.4.4.1.3.5.2.1.1","title":"Sky Savings Rate Definition","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3082,"content":"`Sky Savings Rate` is defined in [A.3.1.2.2 - Sky Savings Rate](2674cccb-d779-4868-b83f-8cb86648c88a).","contentHash":"59d126496de0a5c68d559844410a813b6a4941eafc07b4c9fb28c7712709b883","addressRefs":[]},"a61d98e3-ca01-4945-ba76-46955be3631c":{"id":"a61d98e3-ca01-4945-ba76-46955be3631c","doc_no":"A.4.4.1.3.5.2.1.2","title":"stUSDS Distribution Reward Definition","type":"Core","depth":6,"parentId":"5e546766-a0c0-4744-9ca9-5509db14bc30","order":3083,"content":"`stUSDS Distribution Reward` is defined in [A.4.4.1.3.7 - stUSDS Distribution Reward](673676d8-62a4-4422-b870-fbcdb3c0aabd).","contentHash":"bf8ed085fc0eab42318492fb41e602cf70f5cbd97f8820db19aafa1433e91838","addressRefs":[]},"fac38a01-4c67-4810-af22-3e7b2d855567":{"id":"fac38a01-4c67-4810-af22-3e7b2d855567","doc_no":"A.4.4.1.3.6","title":"stUSDS Risk Parameters","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3084,"content":"The liquidation parameters for SKY-backed loans funded via stUSDS are:\n\n- Liquidation Ratio: 120%\n- `Calc`: StairstepExponentialDecrease\n- `Tau`: 0 days\n- `Tolerance`: 0.5\n- `Cut`: 0.99\n- `Step`: 60 seconds\n- `Buf`: 120%\n- `Cusp`: 40%\n- `Tail`: 6,000 seconds\n- `Chip`: 0.1%\n- `Stopped`: 3\n- `Tip`: 300 USDS\n- `Chop`: 13%\n- `Hole`: 250,000\n- `Dust`: 30,000","contentHash":"5c5101cccc3fa8abed22e45d6d72987e574d27c65a34be0ee63a9b7c314fe701","addressRefs":[]},"1aa35c85-6a96-4921-a6f0-87a58f3d57d6":{"id":"1aa35c85-6a96-4921-a6f0-87a58f3d57d6","doc_no":"A.4.4.1.3.6.1","title":"Modification Of stUSDS Risk Parameters","type":"Core","depth":6,"parentId":"fac38a01-4c67-4810-af22-3e7b2d855567","order":3085,"content":"Except as specified in [A.4.4.1.3.6.1.1 - Modification Of stUSDS Auction Parameters](0296f17f-b615-4f93-9505-94bd78c24324), the Core Executor Agents, in consultation with the Core Council Risk Advisor, have the ability to modify any of the parameters defined in [A.4.4.1.3.6 - stUSDS Risk Parameters](fac38a01-4c67-4810-af22-3e7b2d855567). The modification of said parameters is pursuant to the Operational Weekly Cycle and can be effected directly via an Executive Vote, without requiring a Governance Poll.","contentHash":"796b535900faf554a1cad1b6f0b7048e58e8c750db215e863eafaab8bc6db01d","addressRefs":[]},"0296f17f-b615-4f93-9505-94bd78c24324":{"id":"0296f17f-b615-4f93-9505-94bd78c24324","doc_no":"A.4.4.1.3.6.1.1","title":"Modification Of stUSDS Auction Parameters","type":"Core","depth":6,"parentId":"fac38a01-4c67-4810-af22-3e7b2d855567","order":3086,"content":"A clear justification and analysis must be provided to validate any proposed changes to the `Calc`, `Tau`, `Buf`, `Cusp`, `Tail`, `Chip`, `Tip`, `Chop`, or `Hole` parameters. Before these changes are added to an Executive Vote, the Core Executor Agents must obtain approval through a Governance Poll. However, in an emergency, the Core Executor Agents have the authority to bypass the Governance Poll and add the proposed parameters directly to an Executive Vote. These parameters must be regularly monitored and updated if needed.","contentHash":"668ea40ceb75961769f65bfb4f844bd32861e2c35ed909f56f32b6a08a505938","addressRefs":[]},"673676d8-62a4-4422-b870-fbcdb3c0aabd":{"id":"673676d8-62a4-4422-b870-fbcdb3c0aabd","doc_no":"A.4.4.1.3.7","title":"stUSDS Distribution Reward","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3087,"content":"The stUSDS Distribution Reward is an incentive mechanism, similar to the USDS Distribution Reward, designed to encourage Prime Agents and Integrators to promote stUSDS adoption. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6). It is calculated as a percentage of the stUSDS balance associated with a Reward Code. The reward is initially set at 0.05% for the Integrator portion and 0.05% for the Prime Agent Management Fee, totaling 0.1%.","contentHash":"8b4d15d8a1b1680bfde35f05feb4f28a14f6c439a4a9b0d7fb5e5a76b5a9fd3c","addressRefs":[]},"37f8f82e-7239-4cfb-8f95-d2cc40515cd9":{"id":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","doc_no":"A.4.4.1.3.8","title":"stUSDS Bounded External Access Module","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3088,"content":"The stUSDS Bounded External Access Module (stUSDS BEAM) enables designated, Governance-whitelisted operators to adjust the stUSDS Rate (`str`), the SKY Borrow Rate (`duty`), the maximum amount that users can deposit into the stUSDS contract (`cap`), and the maximum Debt Ceiling (`line`). Adjustments are governed by the stUSDS BEAM smart contract logic and specific parameters set by Sky Governance. stUSDS BEAM holds four parameters that can be set for each stUSDS parameter: (i) `min`, (ii) `max`, (iii) `step`, and (iv) `tau`.","contentHash":"4bae6f56ef90782262709c1f722078660c00edfb9cdfe8d380fe20b352f085fb","addressRefs":[]},"2875f146-08b2-4b83-84ed-282af9379762":{"id":"2875f146-08b2-4b83-84ed-282af9379762","doc_no":"A.4.4.1.3.8.1","title":"Definitions","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3089,"content":"The documents herein define the parameters of the stUSDS BEAM.","contentHash":"71b6146d8dde542d0416e4f7bacfc9cb2034c1f59943e38ea1e718058bc3e40d","addressRefs":[]},"f1ed4794-7642-4ce4-ae80-c5f4e2ec0eed":{"id":"f1ed4794-7642-4ce4-ae80-c5f4e2ec0eed","doc_no":"A.4.4.1.3.8.1.1","title":"Min Definition","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3090,"content":"The `min` parameter defines the minimum value for the `str` and `duty` parameters that can be set using the stUSDS BEAM. Each of the `str` and `duty` parameters has a specific `min`.","contentHash":"ec3ff38e623e014c831c869f14393f6fd7ad1165163489c51b0a6804b083e7d0","addressRefs":[]},"dbb7b9f3-be84-4eaa-93a0-afe997916ce2":{"id":"dbb7b9f3-be84-4eaa-93a0-afe997916ce2","doc_no":"A.4.4.1.3.8.1.2","title":"Max Definition","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3091,"content":"The `max` parameter defines the maximum value for the `str` and `duty` parameters that can be set using the stUSDS BEAM. Each of the `str` and `duty` parameters has a specific `max`.","contentHash":"279cccdbffa9d068ec17613bb074a0198b57e88e8539f29d243d86cc2c429108","addressRefs":[]},"9d4cd92b-7e77-475b-a8f5-245ea29fe344":{"id":"9d4cd92b-7e77-475b-a8f5-245ea29fe344","doc_no":"A.4.4.1.3.8.1.3","title":"Step Definition","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3092,"content":"The `step` parameter limits how much the `str` and `duty` parameters can be increased or decreased in a single transaction, bound by the `tau` parameter. Each of the `str` and `duty` parameters has a specific `step`.","contentHash":"56814868f11f44438b2e82320f05901beb15f70d6046dec54625ad47487eec4c","addressRefs":[]},"2ddd3c5d-7fc3-422c-8a61-03404e182270":{"id":"2ddd3c5d-7fc3-422c-8a61-03404e182270","doc_no":"A.4.4.1.3.8.1.4","title":"Max Cap Definition","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3093,"content":"The `maxCap` parameter defines the maximum value for the `cap` parameter that can be set by the stUSDS BEAM.","contentHash":"9516786dbf7fd6b57fb36c33c0ade77f981fad380db4a4f5a1cdcc065e6140eb","addressRefs":[]},"fca6bbee-6c6f-4e0b-a208-d56b136ce729":{"id":"fca6bbee-6c6f-4e0b-a208-d56b136ce729","doc_no":"A.4.4.1.3.8.1.4.1","title":"Max Cap Current Value","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3094,"content":"The `maxCap` is currently set to 1,000,000,000 USDS.","contentHash":"4833c961028dbf92befd52151831a4ec030186e63aee22edb3ee42dff194efab","addressRefs":[]},"96dd5de9-b5ba-4249-bcce-09f598d34019":{"id":"96dd5de9-b5ba-4249-bcce-09f598d34019","doc_no":"A.4.4.1.3.8.1.5","title":"Max Line Definition","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3095,"content":"The `maxLine` parameter defines the maximum value for the `line` parameter that can be set by the stUSDS BEAM.","contentHash":"610cb147bd4c264a1501a0b654bfd5fdf69955c5f624246393a5de867e72075b","addressRefs":[]},"3067ff3e-5450-48b7-b8b3-fd671739c6b5":{"id":"3067ff3e-5450-48b7-b8b3-fd671739c6b5","doc_no":"A.4.4.1.3.8.1.5.1","title":"Max Line Current Value","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3096,"content":"The `maxLine` is currently set to 1,000,000,000 USDS.","contentHash":"f92035f3f7dbd6a91a696b5a630e25620fcb899171cd15f4b50b753f5b99ea4e","addressRefs":[]},"4f82fc17-4bcc-4623-b09b-b495c43b06f7":{"id":"4f82fc17-4bcc-4623-b09b-b495c43b06f7","doc_no":"A.4.4.1.3.8.1.6","title":"Tau Definition","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3097,"content":"The `tau` parameter defines the minimum time interval, in seconds, that must elapse between consecutive uses or operations of the stUSDS BEAM.\n\nA stUSDS BEAM operation may adjust one or more parameters. Once a stUSDS BEAM operation is executed, the `tau` duration must expire before any subsequent stUSDS BEAM operation can be performed.","contentHash":"e263de7c0803f2ee45b28c36e4c4917338359b49f6dd86ee29df18489167dec6","addressRefs":[]},"9e7e18f3-36b2-497a-817a-2fe9054b8745":{"id":"9e7e18f3-36b2-497a-817a-2fe9054b8745","doc_no":"A.4.4.1.3.8.1.6.1","title":"Tau Current Value","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3098,"content":"The `tau` is currently set to 57,600 seconds (16 hours).","contentHash":"f9f09a82c135f91f6cef192b7029a65b12c7d8d74e14c9dab65144c6ae2f89d5","addressRefs":[]},"74b7d8e7-5f55-4760-8f4d-1e5e9bda4279":{"id":"74b7d8e7-5f55-4760-8f4d-1e5e9bda4279","doc_no":"A.4.4.1.3.8.2","title":"stUSDS Parameters","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3099,"content":"The stUSDS BEAM parameters for each stUSDS parameter set by the stUSDS BEAM are defined in the subdocuments herein.","contentHash":"dc9581f19ad5076d7e56a16a51f379c3b0fc30cb08daa53a8ccfe1695b57426b","addressRefs":[]},"516eccc7-dd7f-4782-84d5-55121bc1ae44":{"id":"516eccc7-dd7f-4782-84d5-55121bc1ae44","doc_no":"A.4.4.1.3.8.2.1","title":"Str Parameters","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3100,"content":"The stUSDS BEAM parameters for the `str` stUSDS parameter are as follows:\n\n- `max` - 5,000 basis points,\n- `min` - 200 basis points,\n- `step` - 1,500 basis points.","contentHash":"7b2317008e5b622662d66d194cc891f1238e3513ea9963491015e438b060c9a3","addressRefs":[]},"94da2be4-e21c-4de7-8c0c-21e17718d32b":{"id":"94da2be4-e21c-4de7-8c0c-21e17718d32b","doc_no":"A.4.4.1.3.8.2.2","title":"Duty Parameters","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3101,"content":"The stUSDS BEAM parameters for the `duty` stUSDS parameter are as follows:\n\n- `max` - 5,000 basis points,\n- `min` - 210 basis points,\n- `step` - 1,500 basis points.","contentHash":"204337877821a82d0c56f2299a49e0b19e52fe5f0f38e8131d8f81ceda50eab8","addressRefs":[]},"91152a4b-6f97-4b8a-831a-0f85c16a78ab":{"id":"91152a4b-6f97-4b8a-831a-0f85c16a78ab","doc_no":"A.4.4.1.3.8.3","title":"Parameter Adjustments","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3102,"content":"All stUSDS BEAM parameters can be modified by Core GovOps, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.","contentHash":"f378c2511e0c5fe405fad7ea06005c1ae5f5069b4b2eef95244674b002c20de8","addressRefs":[]},"8fd15f15-c8cd-480d-86b7-cad524cfa9f1":{"id":"8fd15f15-c8cd-480d-86b7-cad524cfa9f1","doc_no":"A.4.4.1.3.8.4","title":"Operators","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3103,"content":"The stUSDS BEAM Operators are whitelisted entities that can directly alter the stUSDS parameters set by the stUSDS BEAM. Changes to stUSDS parameters are limited by the `max`, `min`, `step`, and `tau` parameters. Operators can be added or removed by an Executive Vote.","contentHash":"d0fe6b060619ca3aeceaa4a5503938cc4159fabece7e2da2a2df4cead922a3f3","addressRefs":[]},"ee9e13e0-23ca-41a3-a1d1-0f1181882c84":{"id":"ee9e13e0-23ca-41a3-a1d1-0f1181882c84","doc_no":"A.4.4.1.3.8.4.1","title":"Operator Multisig","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3104,"content":"The Operator Multisig is an Operator of the stUSDS BEAM and is controlled by Core GovOps.","contentHash":"d7d6ccae83ba4267e623e56e0bb0c5e9fd8669c395c5b34752585d2e788c9854","addressRefs":[]},"45679e08-a575-444a-8fae-d7ef6472b073":{"id":"45679e08-a575-444a-8fae-d7ef6472b073","doc_no":"A.4.4.1.3.8.4.1.1","title":"Operator Multisig Address","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3105,"content":"The address of the Operator Multisig on the Ethereum Mainnet is `0xBB865F94B8A92E57f79fCc89Dfd4dcf0D3fDEA16`.","contentHash":"d6c0967623840ec4bf1625d166af5b4bc2fec39db1086a3b1858a4c95b15d958","addressRefs":["0xbb865f94b8a92e57f79fcc89dfd4dcf0d3fdea16"]},"88438441-b858-4a0a-b1bb-f79cc19e7490":{"id":"88438441-b858-4a0a-b1bb-f79cc19e7490","doc_no":"A.4.4.1.3.8.4.1.2","title":"Operator Multisig Required Number Of Signers","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3106,"content":"The Operator Multisig currently has a 2/3 signing requirement.","contentHash":"3225d2e5c6230021467c67d01dab2e69e4801361f019a44512d61b5db54c0bdc","addressRefs":[]},"a9a7503a-d4e2-474f-bbbe-51b45385a00f":{"id":"a9a7503a-d4e2-474f-bbbe-51b45385a00f","doc_no":"A.4.4.1.3.8.4.1.3","title":"Operator Multisig Signers","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3107,"content":"The signers of the Operator Multisig are three (3) addresses controlled by Core GovOps.","contentHash":"3117e971a05c70e18ab436af461246763f0cc78c29259375f8fa1d3d5c37ece1","addressRefs":[]},"71e28a28-82b9-43eb-9e93-6aee2d5bbbc0":{"id":"71e28a28-82b9-43eb-9e93-6aee2d5bbbc0","doc_no":"A.4.4.1.3.8.4.1.4","title":"Operator Multisig Usage Standards","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3108,"content":"The signers of the Operator Multisig must use the multisig to operate the stUSDS BEAM in accordance with the instructions specified in [A.4.4.1.3.8.5.2 - Manual Parameter Updates By Operator Multisig](944c2573-1184-4d6b-bbe9-0b84c11956cf).","contentHash":"368d39db99a915cf1a146ee65ef66c555213735e5115789c01a2dfef3e10625f","addressRefs":[]},"303ccb86-1411-409f-a3e4-1193e0aa7b9a":{"id":"303ccb86-1411-409f-a3e4-1193e0aa7b9a","doc_no":"A.4.4.1.3.8.4.1.5","title":"Operator Multisig Modification","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3109,"content":"Core GovOps can change the signers of the Operator Multisig at any time, so long as there are at least three (3) signers and at least a majority of signers are required to execute transactions.","contentHash":"9fff0b4b32fb21aa813435687155758ebb9f9428203e2d91939da6781fd9dce6","addressRefs":[]},"bddf50ca-02ef-4991-abb0-53e09831ee6f":{"id":"bddf50ca-02ef-4991-abb0-53e09831ee6f","doc_no":"A.4.4.1.3.8.4.2","title":"Operator Hot Wallet","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3110,"content":"The Operator Hot Wallet is a hot wallet controlled by a bot that will update stUSDS parameters on an automated basis as specified in [A.4.4.1.3.8.5.3 - Automatic Updates By Operator Hot Wallet](a6e1735f-bd82-4ab6-982b-218013c3455f). The wallet is controlled by Ecosystem Actor TechOps Services under the supervision of Core GovOps in consultation with the Core Council Risk Advisor. The addition of the Hot Wallet as an Operator of the stUSDS BEAM is authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"1a4ac70e83f85e5cd9c0d2b83d68748292460ed1f82ea15d837505314b49e71e","addressRefs":[]},"bc29e096-972c-4bcc-b589-dad148374d33":{"id":"bc29e096-972c-4bcc-b589-dad148374d33","doc_no":"A.4.4.1.3.8.4.2.1","title":"Operator Hot Wallet Address","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3111,"content":"The address of the Operator Hot Wallet on the Ethereum Mainnet is `0xd06C14820048de2Fb7c9de611EcFdaCE18eC8896`.","contentHash":"23ef280b91ecb961f0ba4ceebdda42398b2cdb07cd9e343daa63d68c6bdd3e96","addressRefs":["0xd06c14820048de2fb7c9de611ecfdace18ec8896"]},"877f2d58-df39-4cb9-97cc-e529a5c62146":{"id":"877f2d58-df39-4cb9-97cc-e529a5c62146","doc_no":"A.4.4.1.3.8.4.2.2","title":"Update Of stUSDS Parameters For Hot Wallet","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3112,"content":"When the Operator Hot Wallet is added as an Operator of the stUSDS Rate, the stUSDS BEAM parameters must be updated as follows:\n\n- The `step` parameters for the `str` and `duty` parameters must be reduced to 400 basis points; and\n- The `tau` parameter must be reduced to 4 hours.\n\nThese changes are authorized to proceed directly to an Executive Vote without a prior Governance Poll.","contentHash":"b533056f765bae4ecb6bac874b3a9e797d26f73bfb4532d4ef4c9003db6ea77e","addressRefs":[]},"64d7e377-9870-4563-a073-768bb7d259a4":{"id":"64d7e377-9870-4563-a073-768bb7d259a4","doc_no":"A.4.4.1.3.8.4.3","title":"Operator Update Process","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3113,"content":"stUSDS BEAM Operators can be modified by Core GovOps, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.","contentHash":"83d8bfeca5242998b69b87ce7441f1fef7bfdfb78cff9e3e86f625a25a47a423","addressRefs":[]},"7e58f5eb-c339-4f04-aca8-681e9acd0752":{"id":"7e58f5eb-c339-4f04-aca8-681e9acd0752","doc_no":"A.4.4.1.3.8.5","title":"Update Process","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3114,"content":"The stUSDS parameters set by the stUSDS BEAM are managed by the stUSDS BEAM Operators as specified in the documents herein.","contentHash":"3b31ece4949f292dd0702d61331f7a358bd30f8f0917db435092ab94f9cc0a9f","addressRefs":[]},"13c51e11-8ea3-4d4e-b631-2e99c559a914":{"id":"13c51e11-8ea3-4d4e-b631-2e99c559a914","doc_no":"A.4.4.1.3.8.5.1","title":"Initial Parameter Values Set In Executive Vote","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3115,"content":"The initial parameters set by the stUSDS BEAM in the Executive Vote deploying stUSDS and the stUSDS BEAM are:\n\n- `str` - 0 basis points\n- `duty` - 2,000 basis points\n- `cap` - 200,000,000 USDS\n- `line` - 200,000,000 USDS","contentHash":"64e2344e2fd81f397c301e5c53d535ffec838d6b2ec86ef8d1cbdd2046d010c1","addressRefs":[]},"944c2573-1184-4d6b-bbe9-0b84c11956cf":{"id":"944c2573-1184-4d6b-bbe9-0b84c11956cf","doc_no":"A.4.4.1.3.8.5.2","title":"Manual Parameter Updates By Operator Multisig","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3116,"content":"Initially, the stUSDS parameters set by the stUSDS BEAM are managed by the Operator Multisig based on instructions provided by the Core Council Risk Advisor.","contentHash":"49ef0fdab3e2708218c866759cda639f6ab830ccc370a004c31b8a98a95a6a1e","addressRefs":[]},"cfd01132-42f2-46c9-867c-bd9aa62bf78a":{"id":"cfd01132-42f2-46c9-867c-bd9aa62bf78a","doc_no":"A.4.4.1.3.8.5.2.1","title":"Instructions By Core Council Risk Advisor","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3117,"content":"The Core Council Risk Advisor will develop and maintain a stUSDS Dashboard. The stUSDS Dashboard must display the recommended values for each of the stUSDS parameters as of any point in time. The stUSDS Dashboard is located at [https://stusds.herddefi.com/](https://stusds.herddefi.com/).\n\nThe recommended values for each of the stUSDS parameters should be based on the methodology specified in [A.4.4.1.3.8.6 - Update Methodology](e37d1045-215d-4f85-bbc3-70aa2c1b818b) but the Core Council Risk Advisor may deviate from this methodology if they determine that another methodology is advisable to support the growth of USDS and the interests of the Sky Protocol.","contentHash":"5a74c7b5c2189783d28aaaa98a931336bd1305ab2fcf95d116b488511aa68563","addressRefs":[]},"420d6ca3-405a-41be-ba0f-cdc52746477c":{"id":"420d6ca3-405a-41be-ba0f-cdc52746477c","doc_no":"A.4.4.1.3.8.5.2.2","title":"Operator Execution","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3118,"content":"On a regular basis, the stUSDS BEAM Operators must prepare and execute changes so that the stUSDS parameters reflect the recommended values in the stUSDS Dashboard. In determining when to make changes, the stUSDS BEAM Operators, in consultation with the Core Council Risk Advisor, should consider factors including:\n\n- the materiality of the change;\n- the occurrence of weekends and holidays, including Calendar Exceptions to the Monthly Governance Cycle (see [A.1.12.1 - Calendar Exceptions](6c0810e2-390d-4efb-8b31-f36a7f6e1a05)); and\n- such other factors as the stUSDS BEAM Operators and the Core Council Risk Advisor deem relevant.","contentHash":"b8922f0f48ddb80dc523d7b3dc6961a7f449adf0578321d60835ee80517eff57","addressRefs":[]},"7318d160-e182-4276-bdf9-7dfc86ca77a5":{"id":"7318d160-e182-4276-bdf9-7dfc86ca77a5","doc_no":"A.4.4.1.3.8.5.2.3","title":"Review By Core Facilitator And Core Council Risk Advisor","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3119,"content":"The Core Facilitator and the Core Council Risk Advisor must review the actions of the stUSDS BEAM Operators on a regular basis. If they determine that the stUSDS BEAM Operators are not updating the stUSDS parameters in a way that reflects the recommended values in the stUSDS Dashboard on a timely basis, they must report this to the Core Council.","contentHash":"9b21b5cf01ea8567172af69623b10390a0fde2faa356836a7180f5d704e92c46","addressRefs":[]},"a6e1735f-bd82-4ab6-982b-218013c3455f":{"id":"a6e1735f-bd82-4ab6-982b-218013c3455f","doc_no":"A.4.4.1.3.8.5.3","title":"Automatic Updates By Operator Hot Wallet","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3120,"content":"Once the Operator Hot Wallet has been added as an Operator of the stUSDS BEAM (see [A.4.4.1.3.8.4.2 - Operator Hot Wallet](bddf50ca-02ef-4991-abb0-53e09831ee6f)), the stUSDS parameters set by the stUSDS BEAM must be set by the Operator Hot Wallet. These changes must be based on the update methodology specified in [A.4.4.1.3.8.6 - Update Methodology](e37d1045-215d-4f85-bbc3-70aa2c1b818b) and the results must be publicly visible on an information dashboard.","contentHash":"fccf6f88e9f714aab95b8962f85c1e8920dc73ea7120ccf087a59f20d657d941","addressRefs":[]},"e37d1045-215d-4f85-bbc3-70aa2c1b818b":{"id":"e37d1045-215d-4f85-bbc3-70aa2c1b818b","doc_no":"A.4.4.1.3.8.6","title":"Update Methodology","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3121,"content":"The documents herein define the methodology that should be used for determining when and how to update stUSDS parameters with the stUSDS BEAM.","contentHash":"9d1b259efa20cd15fec5672b7e550b46bf89b244aaee3d0a024ae1183c59737e","addressRefs":[]},"c296a253-f737-4d17-bea0-4b1dab903096":{"id":"c296a253-f737-4d17-bea0-4b1dab903096","doc_no":"A.4.4.1.3.8.6.1","title":"Short Term Process","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3122,"content":"Initially when stUSDS parameters are set manually by the Operator Multisig (see [A.4.4.1.3.8.5.2 - Manual Parameter Updates By Operator Multisig](944c2573-1184-4d6b-bbe9-0b84c11956cf)), the Core Council Risk Advisor may deviate from the long term process specified in [A.4.4.1.3.8.6.2 - Long Term Process](b349277c-4e61-474a-85bd-18802324a3a6) in their best judgment based on the guidelines specified herein.","contentHash":"e7a89b077700995c81dc86790e95f2360974a2bc98d1a1f8544e93a91dfd76ee","addressRefs":[]},"c4523493-97ba-4f57-ae2f-d407ab6e0f98":{"id":"c4523493-97ba-4f57-ae2f-d407ab6e0f98","doc_no":"A.4.4.1.3.8.6.1.1","title":"Initial Supply Rate","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3123,"content":"The initial value of the `str` parameter must be set extraordinarily high to a value of approximately 40% initially to incentivize deposits. This rate is not sustainable and must be lowered as specified in [A.4.4.1.3.8.6.1.2 - Gradual Reduction In Supply Rate](8441e561-ef59-4a7e-a6d6-438f1bf797be).","contentHash":"6f08a81e20f5d3b39b62938add3659a64e829f4c1c00e51bdcc91b4524212d65","addressRefs":[]},"8441e561-ef59-4a7e-a6d6-438f1bf797be":{"id":"8441e561-ef59-4a7e-a6d6-438f1bf797be","doc_no":"A.4.4.1.3.8.6.1.2","title":"Gradual Reduction In Supply Rate","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3124,"content":"The `str` parameter must be gradually lowered to a more sustainable level as the market approaches the optimal target of 90% utilization.","contentHash":"46d4b777956f050f9f665c03b685161368c7e8ac896e7a3337ae5c057c8303fe","addressRefs":[]},"0d2ea70b-e031-498e-8f3a-aeb967deb736":{"id":"0d2ea70b-e031-498e-8f3a-aeb967deb736","doc_no":"A.4.4.1.3.8.6.1.3","title":"Growth Of Market Size","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3125,"content":"The `cap` and `line` parameters must be scaled up over time. By the time the market reaches 300,000,000 USDS the `str` parameter must be normalized to a level that is in line with the Interest Rate Model.","contentHash":"c058bbfca36e182d52db313289f00b2d492d5bc3e7ce1c0eb04f3c898c041384","addressRefs":[]},"b349277c-4e61-474a-85bd-18802324a3a6":{"id":"b349277c-4e61-474a-85bd-18802324a3a6","doc_no":"A.4.4.1.3.8.6.2","title":"Long Term Process","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3126,"content":"Once the process is fully automated (see [A.4.4.1.3.8.5.3 - Automatic Updates By Operator Hot Wallet](a6e1735f-bd82-4ab6-982b-218013c3455f)) the automated process must fully conform to the specifications herein.","contentHash":"3a013a30a3df82d43aa35af3999d35630e6bc0edfeca011fea61e04e2769964c","addressRefs":[]},"ce0d4199-da56-4d75-b584-d89cf742597e":{"id":"ce0d4199-da56-4d75-b584-d89cf742597e","doc_no":"A.4.4.1.3.8.6.2.1","title":"Conditions For Update","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3127,"content":"The stUSDS parameters should be updated if (1) the current Utilization (see [A.4.4.1.3.2.1.4 - Utilization Definition](337c4f67-685f-42bd-8237-553ed913b89f)) deviates from the Utilization as of the last time the stUSDS parameters were set by more than 2.4% and (2) the time since the last update is greater than `tau` (see [A.4.4.1.3.8.1.6 - Tau Definition](4f82fc17-4bcc-4623-b09b-b495c43b06f7)).","contentHash":"6962a612dfa36b4675d1ef95c31934360ba11878d0c19ba4608ffcae5dddb967","addressRefs":[]},"01be0bd3-0621-4c22-95c7-395542181008":{"id":"01be0bd3-0621-4c22-95c7-395542181008","doc_no":"A.4.4.1.3.8.6.2.2","title":"Calculations For Update","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3128,"content":"The new values for each stUSDS parameter should be set to be as close as possible to the values specified in the documents herein.","contentHash":"a051f09ff7abba6a0668dc06ff18775639ff9186a77ecb95722c7334a1ebdd41","addressRefs":[]},"aaf4b844-0a8b-4679-969b-382263de86ec":{"id":"aaf4b844-0a8b-4679-969b-382263de86ec","doc_no":"A.4.4.1.3.8.6.2.2.1","title":"Str Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3129,"content":"The `str` must be calculated as specified in [A.4.4.1.3.2 - stUSDS Rate](7e51d5a7-0707-4fba-999b-a1becd5f0192).","contentHash":"65041e26b1bfbf618dd117c6f5fd6fb1378b895da923070782146ab7b84ef1b0","addressRefs":[]},"76a96743-9197-4340-9367-74262cc32efd":{"id":"76a96743-9197-4340-9367-74262cc32efd","doc_no":"A.4.4.1.3.8.6.2.2.2","title":"Duty Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3130,"content":"The `duty` must be calculated as specified in [A.4.4.1.3.5.1.2 - Rate Setting Formula](05e97d4d-37e2-4ed8-acea-a8728fbe0402).","contentHash":"f6b207f35d74daa78433462a7d432937f47d65f2671bbb349e522cc92382f3a1","addressRefs":[]},"f5dafbc7-96b2-48e8-8b06-d66714d8b8a6":{"id":"f5dafbc7-96b2-48e8-8b06-d66714d8b8a6","doc_no":"A.4.4.1.3.8.6.2.2.3","title":"Cap Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3131,"content":"The Core Council Risk Advisor must calculate the maximum amount that users can deposit into the stUSDS contract (`cap`) as specified in the documents herein.","contentHash":"5cbdf72e12470bcf939178fbf0bf070a8472372c9a89cff4ee8db2b9e782f30f","addressRefs":[]},"21c4b33d-8644-4c1c-88e2-65f1243abd56":{"id":"21c4b33d-8644-4c1c-88e2-65f1243abd56","doc_no":"A.4.4.1.3.8.6.2.2.3.1","title":"Short Term Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3132,"content":"In the short term while Utilization is above 100%, the `cap` must be set to 200,000,000 USDS.","contentHash":"6f0a0f38c04f53eaf180782d2d7c1f832e240596f1e9748bbadc157dce34dc0d","addressRefs":[]},"bf917cfa-6438-4c91-932d-b4db8cc98af0":{"id":"bf917cfa-6438-4c91-932d-b4db8cc98af0","doc_no":"A.4.4.1.3.8.6.2.2.3.2","title":"Long Term Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3133,"content":"In the long term, the `cap` must be gradually increased when Utilization is above 85% according to the following formula:\n\n`cap = 1.2 * current SKY borrowing`","contentHash":"7f0b522db595610c0cf4afdc54615dab670e0de9cba185750e8446994b5c990a","addressRefs":[]},"ee92fe50-b3c1-4d44-9d99-8efc671cc67e":{"id":"ee92fe50-b3c1-4d44-9d99-8efc671cc67e","doc_no":"A.4.4.1.3.8.6.2.2.4","title":"Line Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3134,"content":"The Core Council Risk Advisor must calculate the maximum amount that users can borrow against their staked SKY (`line`) as specified in the documents herein.","contentHash":"754593ec56ad38d784b08afae103aa7ac19eacafac5c11aaee8ca6d7ef1613eb","addressRefs":[]},"be4d269c-7064-4886-bdd5-8a8ff9d4abe2":{"id":"be4d269c-7064-4886-bdd5-8a8ff9d4abe2","doc_no":"A.4.4.1.3.8.6.2.2.4.1","title":"Short Term Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3135,"content":"In the short term while Utilization is above 100%, the `line` must be set to 200,000,000 USDS.","contentHash":"89811b47a1e5b09943fb644c461d45d3db7d4daa8fb5bb82cc47f5eb7f4e4411","addressRefs":[]},"ca92131b-a383-48c9-ab11-4ceeaca180d3":{"id":"ca92131b-a383-48c9-ab11-4ceeaca180d3","doc_no":"A.4.4.1.3.8.6.2.2.4.2","title":"Long Term Calculation","type":"Core","depth":6,"parentId":"37f8f82e-7239-4cfb-8f95-d2cc40515cd9","order":3136,"content":"In the long term, the `line` must be gradually increased when Utilization is above 85% according to the following formula:\n\n`line = 1.14 * current SKY borrowing`","contentHash":"6226962f50b2b9ebd685056adde16158c8852519d8a408c907300c23b5d0099d","addressRefs":[]},"c0fbc4e6-754c-4838-aa27-4ef6226f2769":{"id":"c0fbc4e6-754c-4838-aa27-4ef6226f2769","doc_no":"A.4.4.1.3.9","title":"SKY-Backed Borrowing Capped OSM Wrapper","type":"Core","depth":5,"parentId":"264b1787-cd75-4d28-9c14-c7d5a724eba7","order":3137,"content":"In order to prevent excessive price spikes if there is high demand for leverage against SKY tokens, which could potentially lead to excessive USDS borrowing against SKY, a wrapper for the SKY OSM contract has been developed.\n\nThe wrapper enforces an upper limit on the price of SKY for the purposes of SKY-Backed Borrowing, which is set to be the minimum value of:\n\n1. The current price reported by PIP_SKY.\n2. The `cap` that has been set on the OSM wrapper contract.","contentHash":"283254304eca9ae2f42f2c98dfd88333d8e1ad7b0fa2af5d8f818eb0797c7f3a","addressRefs":[]},"532ed9cb-51de-4ac2-ade9-58c07b3ea3d5":{"id":"532ed9cb-51de-4ac2-ade9-58c07b3ea3d5","doc_no":"A.4.4.1.3.9.1","title":"Cap Parameter","type":"Core","depth":6,"parentId":"c0fbc4e6-754c-4838-aa27-4ef6226f2769","order":3138,"content":"The subdocuments herein further describe the `cap` parameter and the process for its modification.","contentHash":"27771f3767a4a6b43e944d7efdb963162a0149ee791a8225ec5c597647b8cd95","addressRefs":[]},"b65c4542-5fb3-4379-9412-8113f4d2444a":{"id":"b65c4542-5fb3-4379-9412-8113f4d2444a","doc_no":"A.4.4.1.3.9.1.1","title":"Definition","type":"Core","depth":6,"parentId":"c0fbc4e6-754c-4838-aa27-4ef6226f2769","order":3139,"content":"The `cap` parameter represents one of the potential inputs for the SKY-Backed Borrowing Capped OSM Wrapper. The OSM wrapper uses the minimum value of the `cap` or the PIP_SKY oracle price to determine the price utilized for SKY-backed borrowing.","contentHash":"d260e117efbd76f328d0f0699178099621aa7cf8b7ad571aa3df06a0e463abf1","addressRefs":[]},"0d86a609-e432-4312-8989-4e6c1eb9be83":{"id":"0d86a609-e432-4312-8989-4e6c1eb9be83","doc_no":"A.4.4.1.3.9.1.2","title":"Modification","type":"Core","depth":6,"parentId":"c0fbc4e6-754c-4838-aa27-4ef6226f2769","order":3140,"content":"The Core Facilitator, in consultation with the Core Council Risk Advisor, has the ability to modify the `cap` parameter. The modification of said parameter is pursuant to the Operational Weekly Cycle and can be effected directly via an Executive Vote, without requiring a prior Governance Poll.","contentHash":"1fb455f8306f51f14da6a8aeb025440e0a9c175582c091eb677ad3bcb5bd51cf","addressRefs":[]},"161ee404-89b3-43a1-80a9-f387f73c0f6f":{"id":"161ee404-89b3-43a1-80a9-f387f73c0f6f","doc_no":"A.4.4.1.3.9.1.3","title":"Current Value","type":"Core","depth":6,"parentId":"c0fbc4e6-754c-4838-aa27-4ef6226f2769","order":3141,"content":"The current value of the `cap` parameter is:\n\n- 0.025 USDS.","contentHash":"3c349415f5a43694337383723452c684bf84e438425bd18406c4e1c03e2a2209","addressRefs":[]},"22b8f8bf-b477-4439-86f7-ec605d3c657a":{"id":"22b8f8bf-b477-4439-86f7-ec605d3c657a","doc_no":"A.4.4.1.4","title":"Short Term Transitionary Measures","type":"Core","depth":4,"parentId":"626bd71c-b413-41b7-a5fe-39fd0d43dbf5","order":3142,"content":"The documents herein define the implementation of short-term SKY staking rewards pending the full implementation of the Sky Treasury Management Function. The policy governing the allocation of capital to staking rewards is specified in [A.2.3.1.2.5 - Step 4: Staking Rewards](bb163691-630e-4fda-88f1-96381a649fa0).","contentHash":"9ea2431849f40c8bab46965ee2ec29a87cb1f883f866d6ca58df09b800ce849c","addressRefs":[]},"aad249a0-1332-4b5f-9b46-d89873e73b86":{"id":"aad249a0-1332-4b5f-9b46-d89873e73b86","doc_no":"A.4.4.1.4.1","title":"Short Term USDS Rewards For SKY Stakers","type":"Core","depth":5,"parentId":"22b8f8bf-b477-4439-86f7-ec605d3c657a","order":3143,"content":"USDS rewards for SKY stakers are available as specified in [A.2.3.1.2.5 - Step 4: Staking Rewards](bb163691-630e-4fda-88f1-96381a649fa0).","contentHash":"53132c736e063b4e96af90b0e1e7dfaa5da3d2393b68b972caf411a6022e22a6","addressRefs":[]},"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310":{"id":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","doc_no":"A.4.4.1.4.2","title":"Short Term SKY Rewards For SKY Stakers","type":"Core","depth":5,"parentId":"22b8f8bf-b477-4439-86f7-ec605d3c657a","order":3144,"content":"Pending activation of the USDS Staking Rewards specified in [A.2.3.1.2.4 - Step 3: Smart Burn Engine](5ce73730-4d5d-479c-b01e-40e87f072121), SKY rewards for SKY stakers are funded by SKY from the Protocol Treasury at the rate specified in [A.2.3.1.4.1 - Short Term SKY Staking Rewards Rate](de233df4-34cc-4e88-a065-9a9dde9add3c) and through the implementation specified in [A.4.4.1.4.2.1 - Implementation](ca151bc7-87fc-4749-9776-ea4308817e81); this interim mechanism will be discontinued once the USDS Staking Rewards become operational.","contentHash":"a2ddd70ab114cd73ef024e021a9919bdc0879d9d1d2d55d9b9e3a4a30392ed7d","addressRefs":[]},"ca151bc7-87fc-4749-9776-ea4308817e81":{"id":"ca151bc7-87fc-4749-9776-ea4308817e81","doc_no":"A.4.4.1.4.2.1","title":"Implementation","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3145,"content":"SKY rewards for SKY stakers are implemented through the Staking Rewards contract, the Vested Rewards Distribution contract, and the Vesting Stream contract, as specified in the documents herein.","contentHash":"54b795f2b4ceb69999c4e488349f6414d231ea5fe5956d31d66c2d0cf9b9c371","addressRefs":[]},"cf65f0d8-ae2f-45df-80bd-1014ce66509d":{"id":"cf65f0d8-ae2f-45df-80bd-1014ce66509d","doc_no":"A.4.4.1.4.2.1.1","title":"Staking Rewards Contract","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3146,"content":"The Staking Rewards contract is the user facing contract that allows SKY stakers to stake their SKY to receive SKY rewards. It maintains the balance of staked SKY receiving SKY rewards for each user and the associated accumulated rewards balance.","contentHash":"0858ce26a74193d3e9dabf1009ae2210b39c04f9d174118a63dd51747a801b6e","addressRefs":[]},"b4989cd9-f45e-4747-8861-fac4175624cc":{"id":"b4989cd9-f45e-4747-8861-fac4175624cc","doc_no":"A.4.4.1.4.2.1.1.1","title":"Staking Rewards Contract Address","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3147,"content":"The address of the Staking Rewards contract on the Ethereum Mainnet is `0xB44C2Fb4181D7Cb06bdFf34A46FdFe4a259B40Fc`.","contentHash":"8243037bb9f3de66b205a86824074c3d6512de0f24c3e8fec8683df295cce514","addressRefs":["0xb44c2fb4181d7cb06bdff34a46fdfe4a259b40fc"]},"2bfed9a4-9d7f-4544-b331-5e196a13a108":{"id":"2bfed9a4-9d7f-4544-b331-5e196a13a108","doc_no":"A.4.4.1.4.2.1.1.2","title":"Staking Rewards Contract Parameters","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3148,"content":"The parameters of the Staking Rewards contract are specified in the documents herein.","contentHash":"971269bce4e05c848c1c4ca9c577c16df474c25492473743f7d32f8b8b2ad3fe","addressRefs":[]},"3db49535-c663-425d-81b9-3ffa6e2e722d":{"id":"3db49535-c663-425d-81b9-3ffa6e2e722d","doc_no":"A.4.4.1.4.2.1.1.2.1","title":"Owner","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3149,"content":"The `owner` of the Staking Rewards contract is the contract that has the ability to control administrative functions for the Staking Rewards contract. The value of the `owner` parameter is the `MCD_PAUSE_PROXY`.","contentHash":"2da0699a11387a523c74b261645c6f941ee579ca1bf996348a382c70d2502fc9","addressRefs":[]},"12b11af8-08d6-4b42-a323-cac0a60e78d3":{"id":"12b11af8-08d6-4b42-a323-cac0a60e78d3","doc_no":"A.4.4.1.4.2.1.1.2.2","title":"Rewards Distribution Contract Address","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3150,"content":"The Rewards Distribution contract address `rewardsDistribution` is the address of the Rewards Distribution contract associated with the Staking Rewards contract. The value of the `rewardsDistribution` parameter is the address of the Rewards Distribution contract specified in [A.4.4.1.4.2.1.2.1 - Rewards Distribution Contract Address](fdebe206-2f58-4056-8adf-c42dffb47026).","contentHash":"180c7a8cbc52433473711ae19565527ef6c13751df5d68fd8be58000d776c47e","addressRefs":[]},"9c3bd61a-25ee-43bc-8c93-89142dce6b49":{"id":"9c3bd61a-25ee-43bc-8c93-89142dce6b49","doc_no":"A.4.4.1.4.2.1.1.2.3","title":"Rewards Token","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3151,"content":"The Rewards Token `rewardsToken` is the token that users receive as rewards. The value of the `rewardsToken` parameter is `SKY`, representing SKY Tokens.","contentHash":"19d8179d09fcdcc95805298ad13c7950a96fda86e77008739d068b30885362a9","addressRefs":[]},"7e88d6b2-a76b-4aae-a045-bc0eb44d9657":{"id":"7e88d6b2-a76b-4aae-a045-bc0eb44d9657","doc_no":"A.4.4.1.4.2.1.1.2.4","title":"Staking Token","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3152,"content":"The Staking Token `stakingToken` is the token that users stake to earn rewards. The value of the `stakingToken` parameter is `LSSKY`, representing staked SKY Tokens.","contentHash":"a6c106a3d100fd688ab5d624b20c959f3ff3dccd80ec7966aac291a928ae7df8","addressRefs":[]},"1317764a-d07f-40de-8ff7-f43a3337ca19":{"id":"1317764a-d07f-40de-8ff7-f43a3337ca19","doc_no":"A.4.4.1.4.2.1.2","title":"Rewards Distribution Contract","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3153,"content":"The Rewards Distribution contract is the contract that handles the regular transfer of reward tokens from the Vesting Stream contract to the Staking Rewards contract for distribution to end users.","contentHash":"53b1e7a806bf8ded259851d69ec62d720c2063a79dae4749201eb1b493a67225","addressRefs":[]},"fdebe206-2f58-4056-8adf-c42dffb47026":{"id":"fdebe206-2f58-4056-8adf-c42dffb47026","doc_no":"A.4.4.1.4.2.1.2.1","title":"Rewards Distribution Contract Address","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3154,"content":"The address of the Rewards Distribution contract on the Ethereum Mainnet is `0x675671A8756dDb69F7254AFB030865388Ef699Ee`.","contentHash":"ad62608ff4d491f172c090534d19b07de6e17c89942a3217c5e194e5ea61eba3","addressRefs":["0x675671a8756ddb69f7254afb030865388ef699ee"]},"c13efebc-94fe-408f-93a7-5ee5badb109f":{"id":"c13efebc-94fe-408f-93a7-5ee5badb109f","doc_no":"A.4.4.1.4.2.1.2.2","title":"Rewards Distribution Contract Parameters","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3155,"content":"The parameters of the Rewards Distribution contract are specified in the documents herein.","contentHash":"5173cfa3d8ebc445c260d34f49c9f676ad0dda3a9f05add46f11546a7f274e2b","addressRefs":[]},"dd30a514-3abb-4e2b-8cc3-03ef2fbf7834":{"id":"dd30a514-3abb-4e2b-8cc3-03ef2fbf7834","doc_no":"A.4.4.1.4.2.1.2.2.1","title":"Staking Rewards Contract Address","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3156,"content":"The Staking Rewards contract address `stakingRewards` is the address of the Staking Rewards contract associated with the Rewards Distribution contract. The value of the `stakingRewards` parameter is the address of the Staking Rewards contract specified in [A.4.4.1.4.2.1.1.1 - Staking Rewards Contract Address](b4989cd9-f45e-4747-8861-fac4175624cc).","contentHash":"50f17feba9f486abd34f2d52123ee0ea2e95f5b48c6246254b1f82bcb8011583","addressRefs":[]},"5348e6c1-13f4-4e5c-8d75-83239ad999ea":{"id":"5348e6c1-13f4-4e5c-8d75-83239ad999ea","doc_no":"A.4.4.1.4.2.1.2.2.2","title":"Vesting Stream Contract Address","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3157,"content":"The Vesting Stream contract address `dssVest` is the address of the Vesting Stream contract associated with the Rewards Distribution contract. The value of the `dssVest` parameter is the address of the Vesting Stream contract specified in [A.4.4.1.4.2.1.3.1 - Vesting Stream](89155294-6652-481f-938f-a562d5b40e65).","contentHash":"2177e9607c98d66f38a67409bc62e536afad52c45c87a7d6defc4a48f575339e","addressRefs":[]},"21a8978d-10a5-4151-b99a-ca8115fe0a6d":{"id":"21a8978d-10a5-4151-b99a-ca8115fe0a6d","doc_no":"A.4.4.1.4.2.1.3","title":"Vesting Stream Contract","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3158,"content":"The Vesting Stream contract manages various vesting streams that vest SKY Tokens from the Protocol Treasury. One of these vesting streams regularly vests SKY Tokens to the Staking Rewards contract.","contentHash":"18d33fedf8787d9350a1d918e876da3d069b0b500b801d43e640b44ed87e20b6","addressRefs":[]},"89155294-6652-481f-938f-a562d5b40e65":{"id":"89155294-6652-481f-938f-a562d5b40e65","doc_no":"A.4.4.1.4.2.1.3.1","title":"Vesting Stream","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3159,"content":"The address of the Vesting Stream contract is the address corresponding to the `MCD_VEST_SKY_TREASURY` key in the Chainlog.","contentHash":"4b53cbff96610194f2c5d3fb99160a4f23f4d08873e2e23f4ca48bb3fdb4d3ee","addressRefs":[]},"148e2c86-0f30-49c1-923c-9b32f92aa40f":{"id":"148e2c86-0f30-49c1-923c-9b32f92aa40f","doc_no":"A.4.4.1.4.2.1.3.2","title":"Vesting Stream Contract Parameters","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3160,"content":"The parameters of the vesting stream managed by the Vesting Stream contract that vests SKY Tokens to the Staking Rewards contract are specified in the documents herein.","contentHash":"f5df38e368950e48fa6c7b4de36e4d9555c6396936d270c98677f510a9e628a6","addressRefs":[]},"9cad1b65-5dea-4510-a1cd-c47eddb66309":{"id":"9cad1b65-5dea-4510-a1cd-c47eddb66309","doc_no":"A.4.4.1.4.2.1.3.2.1","title":"Vesting Duration","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3161,"content":"The Vesting Duration `vestTau` is the total duration over which the Vesting Total number of tokens are to be vested linearly.","contentHash":"2846d9e0bb66db30c5a481f66e5caf50df3c1380f41954d86e4d2e1ac0cb46ac","addressRefs":[]},"8bc59b3a-5bf4-4e2c-a793-b51a4ff58ef6":{"id":"8bc59b3a-5bf4-4e2c-a793-b51a4ff58ef6","doc_no":"A.4.4.1.4.2.1.3.2.2","title":"Vesting Total","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3162,"content":"The Vesting Total `vestTot` is the number of rewards tokens to be vested in total over the Vesting Duration.","contentHash":"50c329a6b8d91ab4cae714aaa26263835610ac0a7f2627aa8b9ff51dc3d9c96f","addressRefs":[]},"7da0cd7a-238f-400f-89a7-a419ed25ce37":{"id":"7da0cd7a-238f-400f-89a7-a419ed25ce37","doc_no":"A.4.4.1.4.2.1.3.3","title":"Vesting Stream Parameter Modification","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3163,"content":"The Core Facilitator, in consultation with the Core Council Risk Advisor, may modify the parameters of the vesting stream to achieve the target reward rate as specified in [A.2.3.1.4.1 - Short Term SKY Staking Rewards Rate](de233df4-34cc-4e88-a065-9a9dde9add3c). Such modifications can be effected directly via an Executive Vote, without a prior Governance Poll.","contentHash":"9bd5e8b45b8cf17375ebb38697120a8383658c8666c3fcc14077795116262167","addressRefs":[]},"349a350c-c9b7-4232-a83f-2fb49b91fc74":{"id":"349a350c-c9b7-4232-a83f-2fb49b91fc74","doc_no":"A.4.4.1.4.2.2","title":"Source Of SKY Rewards","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3164,"content":"The `vestTot` and `vestTau` parameters of the Vesting Stream contract are set such that SKY rewards are funded by SKY acquired through buybacks or SKY reserves.","contentHash":"2dfe563aceceb62aaa62fe4dd7c5f11114d794be9b4e82d745217d775bbf6d66","addressRefs":[]},"2789177b-5bc7-486f-8aab-75ea16e21035":{"id":"2789177b-5bc7-486f-8aab-75ea16e21035","doc_no":"A.4.4.1.4.2.2.1","title":"Authorization Of Transfer By Sky Frontier Foundation","type":"Core","depth":6,"parentId":"aed6511f-f5f0-4b46-a56e-9a7bbc6ea310","order":3165,"content":"Sky Governance hereby confirms that the transfer of 500,000,000 SKY tokens to initially fund SKY rewards for SKY stakers is consistent with the terms of the grant to the Sky Frontier Foundation. See [A.2.13.1 - Ecosystem Entity Grants](5d5759e4-8077-4af5-9a1a-eaeab5088dd7).","contentHash":"47e779c33a547f4e9b9bb36693785026bc46973a88e33a27d53e6ecdf0a4bf24","addressRefs":[]},"e2f1f01f-3303-41c3-b337-f09eb41ba6be":{"id":"e2f1f01f-3303-41c3-b337-f09eb41ba6be","doc_no":"A.4.5","title":"Distribution Of Agent Tokens","type":"Article","depth":2,"parentId":"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b","order":3166,"content":"When Sky invests capital in Agents, the tokens Sky receives in exchange are distributed in accordance with the terms of the Ecosystem Accord between Sky and the respective Agent.","contentHash":"bd466e968f415559910ccb82382b36e82eb5b54719eaa9f038e5923e1f64d492","addressRefs":[]},"635afa14-3a3c-47fb-b338-a3d64f644b69":{"id":"635afa14-3a3c-47fb-b338-a3d64f644b69","doc_no":"A.4.6","title":"Protocol Mechanisms","type":"Article","depth":2,"parentId":"5c20d9af-0bb9-4ca1-a944-1e2cb6f8bb6b","order":3167,"content":"This Article defines maintenance or housekeeping mechanisms and contracts used to administer the Sky Ecosystem.","contentHash":"b4f28a45e8cf0306f5d1ad0468257d8ef47fc456a9d8608a5559578060c56e8f","addressRefs":[]},"490bc47f-f3fe-4d88-8cc3-be034973fa61":{"id":"490bc47f-f3fe-4d88-8cc3-be034973fa61","doc_no":"A.4.6.1","title":"Token Transfers To Sky","type":"Section","depth":3,"parentId":"635afa14-3a3c-47fb-b338-a3d64f644b69","order":3168,"content":"This Section defines standard procedures for sending tokens to Sky.","contentHash":"9fe392c4330df78419d421d4997ddb216085f8fe28d79192c5420cf914d2e6e6","addressRefs":[]},"e6807f67-0d3c-4b6a-a3df-6da987147b72":{"id":"e6807f67-0d3c-4b6a-a3df-6da987147b72","doc_no":"A.4.6.1.1","title":"Process for Returning Tokens To Sky When No Specific Process Exists","type":"Core","depth":4,"parentId":"490bc47f-f3fe-4d88-8cc3-be034973fa61","order":3169,"content":"The documents herein define processes for sending tokens to Sky. These include the DssBlow2 contract for adding Dai and USDS to the Surplus Buffer, and the Pause Proxy contract for non-stablecoins.","contentHash":"045cf3cbc133d718c4b70d10873c0e9ff2e5169f2337c587097e1065e9c2a811","addressRefs":[]},"c2fdee1e-60f4-464c-8d35-3b2bb5f05870":{"id":"c2fdee1e-60f4-464c-8d35-3b2bb5f05870","doc_no":"A.4.6.1.1.1","title":"Transfer Of Stablecoins To Sky Protocol","type":"Core","depth":5,"parentId":"e6807f67-0d3c-4b6a-a3df-6da987147b72","order":3170,"content":"The documents herein define the instructions for transferring stablecoins to Sky.","contentHash":"82bc2c9d9c8e3025eba7725397384f2785825fc4215a9608aa51bf11d84a3587","addressRefs":[]},"c4137383-6a3c-4c0d-bf65-a6efab26ce0c":{"id":"c4137383-6a3c-4c0d-bf65-a6efab26ce0c","doc_no":"A.4.6.1.1.1.1","title":"Send Dai Or USDS To DssBlow2 Contract","type":"Core","depth":6,"parentId":"c2fdee1e-60f4-464c-8d35-3b2bb5f05870","order":3171,"content":"Transfers of Dai or USDS that are not required to pay down vault debt should result in an increase to the Sky Protocol Surplus Buffer (see [A.3.5.1 - Surplus Buffer](9782cdc5-c274-45c2-bf4a-690f22c6a294)). This process is handled via the DssBlow2 contract, as described in the subdocuments.","contentHash":"270c37de355d901f0ab13928dcaea99331b3cbc146416e2a4d0792d0638c8412","addressRefs":[]},"764ec592-5ff7-462c-9617-759914e1077b":{"id":"764ec592-5ff7-462c-9617-759914e1077b","doc_no":"A.4.6.1.1.1.1.1","title":"DssBlow2","type":"Core","depth":6,"parentId":"c2fdee1e-60f4-464c-8d35-3b2bb5f05870","order":3172,"content":"Dai or USDS tokens can be transferred to the DssBlow2 contract, MCD_BLOW2, at `0x81EFc7Dd25241acd8E5620F177E42F4857A02B79`. Calling the `blow` function on this contract will cause any Dai or USDS tokens held by it to be added to the Surplus Buffer. During this process, the ERC-20 tokens are burned and the tokens are instead reflected as an internal balance in the MCD_VAT contract.","contentHash":"eb1e3c976b03af8cf76110742576609a46edcff5e9570c77374fcac821583a2c","addressRefs":["0x81efc7dd25241acd8e5620f177e42f4857a02b79"]},"736476a2-1dd3-4ce5-85e2-e003a1e6a1ed":{"id":"736476a2-1dd3-4ce5-85e2-e003a1e6a1ed","doc_no":"A.4.6.1.1.1.1.1.1","title":"Unrecoverability Of Non-Dai Or USDS Tokens","type":"Core","depth":6,"parentId":"c2fdee1e-60f4-464c-8d35-3b2bb5f05870","order":3173,"content":"Only Dai or USDS are supported by DssBlow2. Any other tokens sent to DssBlow2 are not recoverable by Sky. Senders bear full responsibility; such transfers are not considered a valid receipt of funds owed.","contentHash":"a89f5efd839faef23ff544f487b8aa57b52683287e83d4426db76e65ad7aa9df","addressRefs":[]},"2e2e0d0b-f021-4958-8863-92cca851736f":{"id":"2e2e0d0b-f021-4958-8863-92cca851736f","doc_no":"A.4.6.1.1.1.2","title":"Transfer Of Other Stablecoins","type":"Core","depth":6,"parentId":"c2fdee1e-60f4-464c-8d35-3b2bb5f05870","order":3174,"content":"Stablecoins other than Dai or USDS cannot be added to the Surplus Buffer via DssBlow2. They should either (1) be converted to Dai or USDS and sent to DssBlow2 or (2) be sent to the Pause Proxy contract without conversion. Receipt of Dai or USDS is Sky’s preferred method of receiving stablecoins.","contentHash":"033b4e220fa7a4e3400300870eb5e9158fc89a1bea5f3a53599fe02199ab8925","addressRefs":[]},"3c8849b2-f2c6-47be-ba54-b99215d9427d":{"id":"3c8849b2-f2c6-47be-ba54-b99215d9427d","doc_no":"A.4.6.1.1.2","title":"Transfer Of Non-Stablecoins To Sky Protocol","type":"Core","depth":5,"parentId":"e6807f67-0d3c-4b6a-a3df-6da987147b72","order":3175,"content":"The documents herein define the instructions for transferring non-stablecoins to Sky.","contentHash":"11b3d14a70cceb12b12a6f650a7a3e8eeff30016da5a09c6f965fa1c075c36fa","addressRefs":[]},"e1bb61ef-6f67-48ed-9b45-88023926607e":{"id":"e1bb61ef-6f67-48ed-9b45-88023926607e","doc_no":"A.4.6.1.1.2.1","title":"Send Non-Stablecoins To Pause Proxy","type":"Core","depth":6,"parentId":"3c8849b2-f2c6-47be-ba54-b99215d9427d","order":3176,"content":"Transfers of non-stablecoins to Sky should be sent to the Pause Proxy contract.","contentHash":"9238f48e71c15114f24ec6b73971dca0b30842c4f352a5b49dcb41a77944b345","addressRefs":[]},"8d8cc32d-f724-4eac-bca8-bab0e6d990ba":{"id":"8d8cc32d-f724-4eac-bca8-bab0e6d990ba","doc_no":"A.4.6.1.1.2.1.1","title":"Pause Proxy","type":"Core","depth":6,"parentId":"3c8849b2-f2c6-47be-ba54-b99215d9427d","order":3177,"content":"The Pause Proxy Contract, MCD_PAUSE_PROXY, at `0xbe8e3e3618f7474f8cb1d074a26affef007e98fb`, is under the direct control of Sky Governance. Sky Governance may take actions through Executive Votes to interact with the tokens held by the Pause Proxy, including selling these tokens.","contentHash":"063d100c17dc6283e38321552a97b1a4b0731c78f5fb58b2bd1ad197f8275103","addressRefs":["0xbe8e3e3618f7474f8cb1d074a26affef007e98fb"]},"99b1b47d-3c7a-4859-ac00-8c0849f9070e":{"id":"99b1b47d-3c7a-4859-ac00-8c0849f9070e","doc_no":"A.5","title":"The Accessibility Scope","type":"Scope","depth":1,"parentId":null,"order":3178,"content":"The Accessibility Scope governs accessibility and distribution efforts, and regulates user-facing frontends.","contentHash":"bb9df4d42cc5caebbc1c19d0819c9f89686a9f90ac2b5c1c2580e2b35028c42b","addressRefs":[]},"580a0254-4406-4e30-a148-123ac71507fd":{"id":"580a0254-4406-4e30-a148-123ac71507fd","doc_no":"A.5.1","title":"Brand Identity","type":"Article","depth":2,"parentId":"99b1b47d-3c7a-4859-ac00-8c0849f9070e","order":3179,"content":"This Article governs the brand identity of Sky.","contentHash":"f328d135c7ac5ee54ccfa2efbb38e2a81f08ec7260d763d0bb7341afe40fabde","addressRefs":[]},"ccb424f7-af2c-45eb-a702-5586fd783b44":{"id":"ccb424f7-af2c-45eb-a702-5586fd783b44","doc_no":"A.5.1.1","title":"Brand Identity","type":"Section","depth":3,"parentId":"580a0254-4406-4e30-a148-123ac71507fd","order":3180,"content":"This Section defines the management and use of Sky’s brand identity.","contentHash":"6aba07b54996aa3d2c2b64bebd1429fc1087406b8b2a5822908bce286fcf9977","addressRefs":[]},"ff80ab10-5b93-4eb2-a347-937e6ee0c625":{"id":"ff80ab10-5b93-4eb2-a347-937e6ee0c625","doc_no":"A.5.1.1.1","title":"Website And Domain","type":"Core","depth":4,"parentId":"ccb424f7-af2c-45eb-a702-5586fd783b44","order":3181,"content":"The IP rights of the Sky website must be transferred to an entity similar to the Dai Foundation.","contentHash":"ec9dfba69256f582d2ec81d565be596d4a35e35db4a63bd60df053b995c4b68e","addressRefs":[]},"fa6e009c-d487-4b32-a5c1-109bff7a6ff0":{"id":"fa6e009c-d487-4b32-a5c1-109bff7a6ff0","doc_no":"A.5.1.1.2","title":"Dai","type":"Core","depth":4,"parentId":"ccb424f7-af2c-45eb-a702-5586fd783b44","order":3182,"content":"Dai must remain as a valid token and product, with no actively maintained brand presence beyond community assets, educational material and its token name.","contentHash":"eba64f2c8bc75f6d6d3c4743eea72ff0d99d986b8891d9db42b9523d4051365e","addressRefs":[]},"e47feeb0-2b82-4908-aa5b-2c78e0c21d68":{"id":"e47feeb0-2b82-4908-aa5b-2c78e0c21d68","doc_no":"A.5.2","title":"Accessibility Communication Channels","type":"Article","depth":2,"parentId":"99b1b47d-3c7a-4859-ac00-8c0849f9070e","order":3183,"content":"This Article regulates accessibility assets, including communication channels and Sky’s communication presence on external websites.","contentHash":"6cb20efdf3f271d42de4c985459d93da77a2bba943a875e1bb31f566e960a95e","addressRefs":[]},"8942c3c7-61bd-4cf6-a3f5-4366290801b4":{"id":"8942c3c7-61bd-4cf6-a3f5-4366290801b4","doc_no":"A.5.2.1","title":"Accessibility Communication Channels","type":"Section","depth":3,"parentId":"e47feeb0-2b82-4908-aa5b-2c78e0c21d68","order":3184,"content":"This Section defines rules for managing accessible communication channels to enhance public access to, and interaction with, the Sky Ecosystem. These communication channels are distinct from Sky’s governance-focused communication channels.","contentHash":"e6180f55e9f0491cf34256e3790fd204fcb4a052597ab10b23d208ba1a76d8e6","addressRefs":[]},"a4a1d3b4-fdcc-41ec-9af6-f501376599a0":{"id":"a4a1d3b4-fdcc-41ec-9af6-f501376599a0","doc_no":"A.5.2.1.1","title":"External Platforms","type":"Core","depth":4,"parentId":"8942c3c7-61bd-4cf6-a3f5-4366290801b4","order":3185,"content":"Sky must support the accessibility of the Sky Ecosystem by paying Ecosystem Actors to maintain accounts and channels on external platforms, such as Twitter and Telegram. These accounts may develop and share Accessibility content that follows the brand guidelines.","contentHash":"a8c3702717cccd25d3cd8ac2bf4cc6d037c7396116f667f7816ef8c73ef41938","addressRefs":[]},"005b77d2-d3c8-4b6d-8722-b86a18aba2e6":{"id":"005b77d2-d3c8-4b6d-8722-b86a18aba2e6","doc_no":"A.5.2.1.2","title":"Moderation","type":"Core","depth":4,"parentId":"8942c3c7-61bd-4cf6-a3f5-4366290801b4","order":3186,"content":"Accessibility Communication channels are subject to the moderation policies specified in [A.2.7.1.2 - Moderation](be3da4c5-6882-4694-9ccd-3fa7c5f6e09a).","contentHash":"4c4d6034129be699ca9710de046dbd89e818a2ebbe02bfb4d6945bab81f048d8","addressRefs":[]},"985891a2-71e0-4e45-a004-f31e6fd72281":{"id":"985891a2-71e0-4e45-a004-f31e6fd72281","doc_no":"A.5.2.1.3","title":"Budget","type":"Core","depth":4,"parentId":"8942c3c7-61bd-4cf6-a3f5-4366290801b4","order":3187,"content":"The Accessibility communication channel budget is available to maintain the tasks described in [A.5.2.1 - Accessibility Communication Channels](8942c3c7-61bd-4cf6-a3f5-4366290801b4) and its subdocuments.","contentHash":"c361dafa2dc65a5a0daaab5414f9e1689717dacc2bfbcfa5079ed5e42b5fa346","addressRefs":[]},"65625a56-0d3e-45b3-958d-0517fd861bd2":{"id":"65625a56-0d3e-45b3-958d-0517fd861bd2","doc_no":"A.5.2.1.3.1","title":"Amount","type":"Core","depth":5,"parentId":"985891a2-71e0-4e45-a004-f31e6fd72281","order":3188,"content":"The Accessibility communication channel budget is:\n\n- 0 USDS per month, implemented with DssVest.\n\nIt is a monthly recurring budget.","contentHash":"73476809c4968ee6d982027216c19cf080de21b0ef7a9136fe39b6b12dd45c48","addressRefs":[]},"8b12566b-31d0-4b87-818b-3949cd1a2f74":{"id":"8b12566b-31d0-4b87-818b-3949cd1a2f74","doc_no":"A.5.3","title":"Accessibility Campaigns","type":"Article","depth":2,"parentId":"99b1b47d-3c7a-4859-ac00-8c0849f9070e","order":3189,"content":"This Article regulates accessibility campaigns.","contentHash":"565604e18bd312b846af6a2434802c3e5885e5f5a22dff59442de5ad8f97b114","addressRefs":[]},"332d3fb0-2d8b-4b5e-aac4-8cdd2659c4ca":{"id":"332d3fb0-2d8b-4b5e-aac4-8cdd2659c4ca","doc_no":"A.5.3.1","title":"Accessibility Campaigns","type":"Section","depth":3,"parentId":"8b12566b-31d0-4b87-818b-3949cd1a2f74","order":3190,"content":"This Section defines infrastructure and processes pertaining to accessibility campaigns.","contentHash":"cff8b60c076d3d6a89e8d20bf9c5cf631e79d07253e8785f3ccfbd49f344eace","addressRefs":[]},"88c9f2dc-1963-419b-852b-204e13f377be":{"id":"88c9f2dc-1963-419b-852b-204e13f377be","doc_no":"A.5.3.1.1","title":"Early Bird Reward","type":"Core","depth":4,"parentId":"332d3fb0-2d8b-4b5e-aac4-8cdd2659c4ca","order":3191,"content":"As a part of the brand reveal phase, the Accessibility Facilitators set up an Early Bird Reward System. The Early Bird Reward System rewarded all users signing up before the launch date of USDS and SKY with double the SKY rewards for the first month following launch.\n\nThe accumulated SKY rewards were paid out as an airdrop as specified in [A.5.3.1.1.1 - Token Distribution](eaf8cf29-90fd-4b9b-b0a8-02ce8386908c).","contentHash":"466fe6c44e080e43feb242b2dcade005655618ef353a236c016b231bb9d94429","addressRefs":[]},"eaf8cf29-90fd-4b9b-b0a8-02ce8386908c":{"id":"eaf8cf29-90fd-4b9b-b0a8-02ce8386908c","doc_no":"A.5.3.1.1.1","title":"Token Distribution","type":"Core","depth":5,"parentId":"88c9f2dc-1963-419b-852b-204e13f377be","order":3192,"content":"To distribute the Early Bird Reward the following actions have been or will be taken:\n\n- 27,222,832.8 newly minted SKY, equal to 120% of the total estimated Early Bird Reward distributions, was transferred to the multisig wallet operated by the Accessibility Facilitators at the address `0x14D98650d46BF7679BBD05D4f615A1547C87Bf68` on the Ethereum Mainnet.\n- The remaining SKY in the `0x14D98650d46BF7679BBD05D4f615A1547C87Bf68` multisig that is not used to fund the MerkleDistributor will be burned by calling the `burn` function on the multisig. The estimated amount of SKY needed to fund the MerkleDistributor is 22,685,694.","contentHash":"30ba5bf5b92417211639f28457409c04ee3fad73c5689b45d31b21150242aba4","addressRefs":["0x14d98650d46bf7679bbd05d4f615a1547c87bf68"]},"c8ed0b06-2be7-4651-9982-91cea0622519":{"id":"c8ed0b06-2be7-4651-9982-91cea0622519","doc_no":"A.5.4","title":"Location Resilience","type":"Article","depth":2,"parentId":"99b1b47d-3c7a-4859-ac00-8c0849f9070e","order":3193,"content":"This Article defines the location-filtering rules applicable to Ecosystem Actors that operate Frontends on behalf of Agents; and Ecosystem Actors that operate Frontends and receive Distribution Rewards.","contentHash":"e76ac3c9ad26c7f8069854ab39ee0ad7e64097d1ab237882f2a0c898c3079011","addressRefs":[]},"396e9ea2-c964-43be-9164-edb302ab62cf":{"id":"396e9ea2-c964-43be-9164-edb302ab62cf","doc_no":"A.5.4.1","title":"Location Resilience","type":"Section","depth":3,"parentId":"c8ed0b06-2be7-4651-9982-91cea0622519","order":3194,"content":"This Section defines requirements for Ecosystem Actors and Agents to implement limited filtering and full blocking of IPs.","contentHash":"fc0123b00d174d292615847d2c0f8a65d8ac273b70516323565d9f4facbf2a63","addressRefs":[]},"58f85237-4d1d-424b-be03-6eea1e8a8d0d":{"id":"58f85237-4d1d-424b-be03-6eea1e8a8d0d","doc_no":"A.5.4.1.1","title":"Reduce Exposure To Locations","type":"Core","depth":4,"parentId":"396e9ea2-c964-43be-9164-edb302ab62cf","order":3195,"content":"Ecosystem Actors in the Sky Ecosystem must actively explore and implement reasonably available options to reduce their infrastructure's exposure to locations identified in the following subdocuments as subject to either IP filtering (\"limited filtering\") or IP blocking (\"full block\").","contentHash":"e058e4d9353141a229404a27390027d4661bdf1338953d0e877c78577a305b50","addressRefs":[]},"b93c94ed-34dd-4269-808d-58ce180a7103":{"id":"b93c94ed-34dd-4269-808d-58ce180a7103","doc_no":"A.5.4.1.2","title":"Consequence For Non-Compliance","type":"Core","depth":4,"parentId":"396e9ea2-c964-43be-9164-edb302ab62cf","order":3196,"content":"All frontends operated by Ecosystem Actors on behalf of Agents are required to follow the location-filtering rules defined in [A.5.4.1 - Location Resilience](396e9ea2-c964-43be-9164-edb302ab62cf) and its subdocuments. The failure to adhere to these rules will result in penalties.","contentHash":"34a9c8b1ffb3ab6461b119ab45583a6ec0911d4c6dff5d8b448a5680597e585a","addressRefs":[]},"eac552cb-4c8d-4a79-bb8c-cfbe264b880f":{"id":"eac552cb-4c8d-4a79-bb8c-cfbe264b880f","doc_no":"A.5.4.1.3","title":"Limited Filtering Of Features & IPs","type":"Core","depth":4,"parentId":"396e9ea2-c964-43be-9164-edb302ab62cf","order":3197,"content":"Limited filtering requires frontends operated by Ecosystem Actors to avoid displaying or describing features to users with IPs flagged for limited filtering.","contentHash":"f2ead0c2b31f424f4076b9a567993d95970ecd595a6681c3c97ef6cfde4b1b7d","addressRefs":[]},"8dc8867d-61cc-4143-a09f-d6035ade5a4a":{"id":"8dc8867d-61cc-4143-a09f-d6035ade5a4a","doc_no":"A.5.4.1.3.1","title":"Restricted Features","type":"Core","depth":5,"parentId":"eac552cb-4c8d-4a79-bb8c-cfbe264b880f","order":3198,"content":"The features that must be restricted from being displayed or described to users flagged for Limited Filtering are:\n\n- Staking Rewards\n- Sky Savings Rate\n- Any other feature related to yield or rewards.","contentHash":"7996e7b6f54ed082aaca8425d4278c0808f39446bc8684ac6a578a3b86285787","addressRefs":[]},"db9e3649-3ccb-4cc4-aede-78ca1d870101":{"id":"db9e3649-3ccb-4cc4-aede-78ca1d870101","doc_no":"A.5.4.1.3.2","title":"Flagged IPs","type":"Core","depth":5,"parentId":"eac552cb-4c8d-4a79-bb8c-cfbe264b880f","order":3199,"content":"Frontends must develop internal processes to determine their strategy for limited filtering, to ensure optimal balance of resilience and accessibility.","contentHash":"b71966f34bc058837174522b795c70451cb50b5fcc1c2dbaa3c04c7b4da01101","addressRefs":[]},"bd6fa353-4f61-4834-887a-37db9f5c8416":{"id":"bd6fa353-4f61-4834-887a-37db9f5c8416","doc_no":"A.5.4.1.4","title":"Full Block","type":"Core","depth":4,"parentId":"396e9ea2-c964-43be-9164-edb302ab62cf","order":3200,"content":"Full block requires frontends operated by Ecosystem Actors to deny service of any kind to users with IPs flagged for Full Block.","contentHash":"a12eebfccd7b5dfbd32b9e36fbd4b894a96ff438e5a4da6bdb68a51bb819db0c","addressRefs":[]},"e6b9065e-8dd7-4f23-b7e4-4e3d2736bee4":{"id":"e6b9065e-8dd7-4f23-b7e4-4e3d2736bee4","doc_no":"A.5.4.1.4.1","title":"Flagged IPs","type":"Core","depth":5,"parentId":"bd6fa353-4f61-4834-887a-37db9f5c8416","order":3201,"content":"User IPs flagged for Full Block are:\n\n- Cuba\n- Iran\n- Syria\n- North Korea\n- Afghanistan\n- Belarus\n- Burma\n- Russia\n- Venezuela\n- Crimea and Sevastopol\n- Donetsk People’s Republic\n- Luhansk People’s Republic of Ukraine\n- Kherson Oblast\n- Zaporizhzhia Oblast","contentHash":"454152597d4762c0eef37bcff77febdad1e3f0880d33bd6ae0a6822ae6543244","addressRefs":[]},"4a08ca6c-e652-49e4-9b79-4831b20e600a":{"id":"4a08ca6c-e652-49e4-9b79-4831b20e600a","doc_no":"A.6","title":"The Agent Scope","type":"Scope","depth":1,"parentId":null,"order":3202,"content":"The Agent Scope regulates all Agents within the Sky Ecosystem and comprises all Agent Artifacts. Each Agent Artifact governs the operations of a particular Agent.","contentHash":"21124348f59a950845badcaad748af6789a94997bac52c981d2c50f36bd4693c","addressRefs":[]},"6889e3e5-1e95-425c-843b-6924b0f164ae":{"id":"6889e3e5-1e95-425c-843b-6924b0f164ae","doc_no":"A.6.1","title":"Agent Artifacts","type":"Article","depth":2,"parentId":"4a08ca6c-e652-49e4-9b79-4831b20e600a","order":3203,"content":"This Article includes the Artifacts of each Agent.","contentHash":"22f49206a474cd5799c91fb64b618ed45b621d12bedacb786f8d7604d3de8a90","addressRefs":[]},"9fb7f1cc-f60b-4195-892d-5e540f969973":{"id":"9fb7f1cc-f60b-4195-892d-5e540f969973","doc_no":"A.6.1.1","title":"List Of Prime Agent Artifacts","type":"Section","depth":3,"parentId":"6889e3e5-1e95-425c-843b-6924b0f164ae","order":3204,"content":"The documents herein each set out the unique Artifact for a particular Prime Agent. Prime Agent Artifacts contain all rules, processes, parameters, and information relevant to the Prime Agent. Prime Agent Artifacts are collections of documents that define each Agent’s strategic vision and day-to-day operational logic.","contentHash":"1fd8758603c3b78d631ff918caa34c0a80ba73e4d30f4238fdac2312b48b0fc0","addressRefs":[]},"dee2f5a4-279a-488c-9a9d-9583e3216fbf":{"id":"dee2f5a4-279a-488c-9a9d-9583e3216fbf","doc_no":"A.6.1.1.1","title":"Spark","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":3205,"content":"The documents herein specify all of the logic for Spark, including Spark’s strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"619281388cd42928ddc69ea82f6a43a043d0d19a4cd67fb1e7072ce1e4121331","addressRefs":[]},"fee4e7c1-bc69-496e-8e1b-a1f7a76daa70":{"id":"fee4e7c1-bc69-496e-8e1b-a1f7a76daa70","doc_no":"A.6.1.1.1.1","title":"Introduction","type":"Core","depth":5,"parentId":"dee2f5a4-279a-488c-9a9d-9583e3216fbf","order":3206,"content":"Spark is an Agent focused on building on USDS in the Ethereum and adjacent DeFi ecosystem. This includes driving adoption of USDS and deploying collateral backing USDS at attractive risk-adjusted returns. Spark does this through the Spark Liquidity Layer, SparkLend, and Spark Savings.\n\n- The Spark Liquidity Layer directly provides USDS, sUSDS, and USDC liquidity across networks and DeFi markets.\n- SparkLend is a lending market focused on USDS borrowing, sourcing liquidity directly from Sky to provide the best borrow rates for USDS.\n- Spark Savings enables stablecoin holders to earn the best risk-adjusted rate in DeFi, at large scale, with minimal liquidity constraints.","contentHash":"e384b061909f9008176607fc24637e2fbd6a88c89d93bea67aef5e605ed3661b","addressRefs":[]},"1bc21199-26d0-4cdd-8d66-454ac62204b9":{"id":"1bc21199-26d0-4cdd-8d66-454ac62204b9","doc_no":"A.6.1.1.1.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"dee2f5a4-279a-488c-9a9d-9583e3216fbf","order":3207,"content":"The documents herein implement the Sky Primitives for Spark. See [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"8906d60b6efa5e41ddce27a40926784fb2d84cda779b3b9b72b4287187e7ce5b","addressRefs":[]},"cccaa367-6157-4640-ba62-3fccd987d07c":{"id":"cccaa367-6157-4640-ba62-3fccd987d07c","doc_no":"A.6.1.1.1.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3208,"content":"The documents herein implement the Genesis Primitives for Spark. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"38b77d0a9aa28513fcf0d6ddea1177bfc5df8f377b9ed431d2493a4290869488","addressRefs":[]},"5f670f2b-16e4-4a3d-84bc-9a302e32b671":{"id":"5f670f2b-16e4-4a3d-84bc-9a302e32b671","doc_no":"A.6.1.1.1.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3209,"content":"The documents herein contain all data and specifications for Spark’s Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"045856f6f44a56f7f5492688470d57dcdd82cb89376502528d6151baa69627c6","addressRefs":[]},"30cd682c-0688-4b2f-a72e-7cded8feb180":{"id":"30cd682c-0688-4b2f-a72e-7cded8feb180","doc_no":"A.6.1.1.1.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3210,"content":"The documents herein organize all base information relevant to Spark’s usage of the Agent Creation Primitive.","contentHash":"f1310518e866b50f9d076d9c7186a41c201873f3a874f0cb4e14375a4f8756b8","addressRefs":[]},"5763b3c1-1605-4171-8928-4545ccb67cad":{"id":"5763b3c1-1605-4171-8928-4545ccb67cad","doc_no":"A.6.1.1.1.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3211,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"c9b60d7e-7009-4614-8975-aa481a8ef1de":{"id":"c9b60d7e-7009-4614-8975-aa481a8ef1de","doc_no":"A.6.1.1.1.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3212,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"4620942e-d34c-4383-b3f4-6faab0eaad27":{"id":"4620942e-d34c-4383-b3f4-6faab0eaad27","doc_no":"A.6.1.1.1.2.1.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3213,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"d1fbe16e-f2a5-4e3a-9352-fa6f8a69b445":{"id":"d1fbe16e-f2a5-4e3a-9352-fa6f8a69b445","doc_no":"A.6.1.1.1.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3214,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.1.1.3.1 - Single Instance Configuration Document](8f26332f-df39-4ff5-bec4-ec34a6bcc0c3).","contentHash":"674906d34bb9ef5dda706f800fe8a66d22816fc06ece354012fc8706d17742e3","addressRefs":[]},"5c48cc46-b6f9-4204-a16f-b3043903135e":{"id":"5c48cc46-b6f9-4204-a16f-b3043903135e","doc_no":"A.6.1.1.1.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3215,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"d50b68ce-a255-4fd9-ba02-7a7b46b7f0ce":{"id":"d50b68ce-a255-4fd9-ba02-7a7b46b7f0ce","doc_no":"A.6.1.1.1.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3216,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"912254f8-e19d-447f-9f6d-59ff488b8fbc":{"id":"912254f8-e19d-447f-9f6d-59ff488b8fbc","doc_no":"A.6.1.1.1.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3217,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"67bf2190-7ec8-4146-bd23-a714c964e0d9":{"id":"67bf2190-7ec8-4146-bd23-a714c964e0d9","doc_no":"A.6.1.1.1.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3218,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"a0212282-b803-44f8-acdf-58529306a95c":{"id":"a0212282-b803-44f8-acdf-58529306a95c","doc_no":"A.6.1.1.1.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3219,"content":"The subtrees for Instances of the Agent Creation Primitive with `Suspended` Status are stored here.","contentHash":"183d20b3c12bea99884c81ff611bff6d5be670766bb91a4f4ccf5339e0a26636","addressRefs":[]},"6879edeb-735e-43ef-ab35-e8fc3fc0e5aa":{"id":"6879edeb-735e-43ef-ab35-e8fc3fc0e5aa","doc_no":"A.6.1.1.1.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3220,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"5eff8c9f-8499-41ff-9aed-2e31d9f5f139":{"id":"5eff8c9f-8499-41ff-9aed-2e31d9f5f139","doc_no":"A.6.1.1.1.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3221,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"8f26332f-df39-4ff5-bec4-ec34a6bcc0c3":{"id":"8f26332f-df39-4ff5-bec4-ec34a6bcc0c3","doc_no":"A.6.1.1.1.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3222,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"78bd0c0c-bdf0-4f75-86f2-47cbfa2e3dfc":{"id":"78bd0c0c-bdf0-4f75-86f2-47cbfa2e3dfc","doc_no":"A.6.1.1.1.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3223,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"6bb5016e-2252-4317-a5a5-6affc59b5209":{"id":"6bb5016e-2252-4317-a5a5-6affc59b5209","doc_no":"A.6.1.1.1.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3224,"content":"The name of the Agent is Spark.","contentHash":"7155ff56e99b6226e8129034a9a7fb0dbf4b46e84cf8545a1ca6b6637c9e26e8","addressRefs":[]},"378950e0-85c9-4f12-94cd-fb36cde59ba9":{"id":"378950e0-85c9-4f12-94cd-fb36cde59ba9","doc_no":"A.6.1.1.1.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3225,"content":"The address of Spark’s SubProxy Account on the Ethereum Mainnet is `0x3300f198988e4C9C63F75dF86De36421f06af8c4`.","contentHash":"1d2ce8f2db57cce4b18623eb04df43e80289d960e7bec90fad4e7acca2fbef03","addressRefs":["0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"e160e2e9-a1f2-4beb-af44-b7bc86ab163f":{"id":"e160e2e9-a1f2-4beb-af44-b7bc86ab163f","doc_no":"A.6.1.1.1.2.1.1.3.1.1.3","title":"Genesis Account","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3226,"content":"The address of Spark’s Genesis Account will be specified in a future iteration of the Spark Artifact.","contentHash":"979c6e65372935349f66e60f01da30568fd02b9ea3b24dcb281fe067939c9c69","addressRefs":[]},"4bc28587-5f7f-4297-840d-ec2109f2e6be":{"id":"4bc28587-5f7f-4297-840d-ec2109f2e6be","doc_no":"A.6.1.1.1.2.1.1.3.1.1.4","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3227,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"166669dd-467a-4d82-b7e5-5ea18cae5b61":{"id":"166669dd-467a-4d82-b7e5-5ea18cae5b61","doc_no":"A.6.1.1.1.2.1.1.3.1.1.4.1","title":"Spark Foundation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3228,"content":"The Spark Foundation is the Prime Foundation associated with Spark. Its mandate is to support the development, growth, and adoption of Spark.","contentHash":"5458626f525c2219693dbc36cab1e8e6d1f7f1ee99961dbca5ccd1a680e3fcf5","addressRefs":[]},"dd82336a-db68-4e58-a624-22d6de00be4c":{"id":"dd82336a-db68-4e58-a624-22d6de00be4c","doc_no":"A.6.1.1.1.2.1.1.3.1.1.4.2","title":"Phoenix Labs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3229,"content":"Phoenix Labs is a development company that provides services to the Spark Foundation. Phoenix Labs is a \"Nested Contributor\", i.e., a core contributor to both Spark and Sky.","contentHash":"4133c51520833cb49708b56d9f187213b0c172eee9181dbf1463d5112e4fb4c7","addressRefs":[]},"4d70e4a7-6f65-421c-b22a-ac5a6eae8170":{"id":"4d70e4a7-6f65-421c-b22a-ac5a6eae8170","doc_no":"A.6.1.1.1.2.1.1.3.1.1.4.3","title":"Spark Assets Foundation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3230,"content":"Spark Assets Foundation is an entity, the purpose of which is to support the Spark Liquidity Layer through real world engagements and allocations. Spark Assets Foundation will deploy assets which are held in the ALM Contracts.","contentHash":"c4a0037ff8f7782cd725ccd16ab07f87ddf599a97febdff1b9c16d40cbcee0dd","addressRefs":[]},"b660c45c-7837-4cc8-b91a-6911c74e9342":{"id":"b660c45c-7837-4cc8-b91a-6911c74e9342","doc_no":"A.6.1.1.1.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3231,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"f1490752-03fe-4e21-ae1f-68a1ec44dbcc":{"id":"f1490752-03fe-4e21-ae1f-68a1ec44dbcc","doc_no":"A.6.1.1.1.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3232,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"d48938da-ffb4-4470-b6ea-c22d25f3cced":{"id":"d48938da-ffb4-4470-b6ea-c22d25f3cced","doc_no":"A.6.1.1.1.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3233,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"e52ba148-0e92-4155-9df7-b35797ee4078":{"id":"e52ba148-0e92-4155-9df7-b35797ee4078","doc_no":"A.6.1.1.1.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3234,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"84c5a139-3778-4542-8631-c13283a2cc1c":{"id":"84c5a139-3778-4542-8631-c13283a2cc1c","doc_no":"A.6.1.1.1.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3235,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"1974618c-b054-41c3-a6aa-860ea7875d02":{"id":"1974618c-b054-41c3-a6aa-860ea7875d02","doc_no":"A.6.1.1.1.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3236,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"0037156e-3b1d-4baa-8a4a-a62936daeb3e":{"id":"0037156e-3b1d-4baa-8a4a-a62936daeb3e","doc_no":"A.6.1.1.1.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3237,"content":"The documents herein contain all data and specifications for Spark’s Instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"7d90c7c8d6cc3c0ddc9c42a7b7cdecdd2ef14cf0391d691e5df436be2d7388fe","addressRefs":[]},"6dd6571c-f210-4e9e-850a-206275d2074e":{"id":"6dd6571c-f210-4e9e-850a-206275d2074e","doc_no":"A.6.1.1.1.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3238,"content":"The documents herein organize all base information relevant to Spark’s usage of the Prime Transformation Primitive.","contentHash":"39621c91bd666d279f26e0ca2c122415d0babd531b3189b23af8d4ba98bfe42f","addressRefs":[]},"192b3c63-90d9-430c-8046-d60b96d20903":{"id":"192b3c63-90d9-430c-8046-d60b96d20903","doc_no":"A.6.1.1.1.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3239,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"3bab6c0a-31a2-41d6-9bc8-560e3ff7ca95":{"id":"3bab6c0a-31a2-41d6-9bc8-560e3ff7ca95","doc_no":"A.6.1.1.1.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3240,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"c30a1946-aaf2-4523-b0c5-e5c8847e9ea9":{"id":"c30a1946-aaf2-4523-b0c5-e5c8847e9ea9","doc_no":"A.6.1.1.1.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3241,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"2a9efb32-b644-4f2e-aea4-e92c8a53f8ab":{"id":"2a9efb32-b644-4f2e-aea4-e92c8a53f8ab","doc_no":"A.6.1.1.1.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3242,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.1.2.3.1 - Single Instance Configuration Document](925c39a5-51a5-4d75-bac2-bae3af5f3861).","contentHash":"fea6659666dc0c414f3d7488e5495fd0cd8368ad0aa3c36ac2947c91de5d231e","addressRefs":[]},"87a1cc55-f46d-4933-b53d-aff285fe5fec":{"id":"87a1cc55-f46d-4933-b53d-aff285fe5fec","doc_no":"A.6.1.1.1.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3243,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"2bf9316e-8ef2-45e4-b6a1-66db55a22bc6":{"id":"2bf9316e-8ef2-45e4-b6a1-66db55a22bc6","doc_no":"A.6.1.1.1.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3244,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"50b95590-6c73-44ac-a09d-d7bac5995f7d":{"id":"50b95590-6c73-44ac-a09d-d7bac5995f7d","doc_no":"A.6.1.1.1.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3245,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"50a8cdc0-f406-436a-84f6-2d554531da76":{"id":"50a8cdc0-f406-436a-84f6-2d554531da76","doc_no":"A.6.1.1.1.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3246,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"5c1785b4-152d-453a-91bb-f4d88e9eb1c8":{"id":"5c1785b4-152d-453a-91bb-f4d88e9eb1c8","doc_no":"A.6.1.1.1.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3247,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"48617d95-a95d-4ded-857d-479306443de5":{"id":"48617d95-a95d-4ded-857d-479306443de5","doc_no":"A.6.1.1.1.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3248,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"cf387ed3-7d5a-4e7b-9d2d-54c1f856f39c":{"id":"cf387ed3-7d5a-4e7b-9d2d-54c1f856f39c","doc_no":"A.6.1.1.1.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3249,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"925c39a5-51a5-4d75-bac2-bae3af5f3861":{"id":"925c39a5-51a5-4d75-bac2-bae3af5f3861","doc_no":"A.6.1.1.1.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3250,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"d141615a-ab1a-4b5a-a483-aad1fcadc0e2":{"id":"d141615a-ab1a-4b5a-a483-aad1fcadc0e2","doc_no":"A.6.1.1.1.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3251,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"053995ec-4b58-4c4b-a3c1-029d65cd7b00":{"id":"053995ec-4b58-4c4b-a3c1-029d65cd7b00","doc_no":"A.6.1.1.1.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3252,"content":"Spark is a Prime Agent.","contentHash":"4c7ff091e2afd5289e2206dd217cb147bf7f838215e8a109d9b7e4796d6a51fc","addressRefs":[]},"e0a0c589-4952-4ccf-8af9-d0bd56abbe6a":{"id":"e0a0c589-4952-4ccf-8af9-d0bd56abbe6a","doc_no":"A.6.1.1.1.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3253,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"dcba1b43-498c-4947-9142-a2e8804a62e2":{"id":"dcba1b43-498c-4947-9142-a2e8804a62e2","doc_no":"A.6.1.1.1.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3254,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"48223101-7247-4ddc-88d0-d502552708a0":{"id":"48223101-7247-4ddc-88d0-d502552708a0","doc_no":"A.6.1.1.1.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3255,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"b8c4fa46-ae4e-4caf-b5eb-09a3b0a45b80":{"id":"b8c4fa46-ae4e-4caf-b5eb-09a3b0a45b80","doc_no":"A.6.1.1.1.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3256,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"dd32b7e4-8905-4ce8-b5a1-4478ef4f9028":{"id":"dd32b7e4-8905-4ce8-b5a1-4478ef4f9028","doc_no":"A.6.1.1.1.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3257,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"7d7d5045-d2f5-4668-ad1f-d943f941238a":{"id":"7d7d5045-d2f5-4668-ad1f-d943f941238a","doc_no":"A.6.1.1.1.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3258,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"4c591869-ad1c-4007-9159-78705b24e43a":{"id":"4c591869-ad1c-4007-9159-78705b24e43a","doc_no":"A.6.1.1.1.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3259,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"cf323ace-ea1f-4272-b4b6-152dd36eea9e":{"id":"cf323ace-ea1f-4272-b4b6-152dd36eea9e","doc_no":"A.6.1.1.1.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3260,"content":"The documents herein contain all data and specifications for Spark’s Instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"63d5cdf6a87b87b5b82637c1c13af7a3bbbb451624f956fd9d697e83334fcb1a","addressRefs":[]},"4130ff50-bc52-4c82-b461-df14bc9aece2":{"id":"4130ff50-bc52-4c82-b461-df14bc9aece2","doc_no":"A.6.1.1.1.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3261,"content":"The documents herein organize all base information relevant to Spark’s usage of the Executor Transformation Primitive.","contentHash":"bcbecfc82978e1a37b69589cc3d1b63e43ae421f75d39c18111bb3f9ff7139da","addressRefs":[]},"fead0e9f-9f57-4bf8-9a17-c91655748023":{"id":"fead0e9f-9f57-4bf8-9a17-c91655748023","doc_no":"A.6.1.1.1.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3262,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"d05a0506-d0d7-4160-abc9-3d140624f637":{"id":"d05a0506-d0d7-4160-abc9-3d140624f637","doc_no":"A.6.1.1.1.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3263,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"c6a88406-677b-4135-af1f-a82f08196b92":{"id":"c6a88406-677b-4135-af1f-a82f08196b92","doc_no":"A.6.1.1.1.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3264,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"99eee71b-341b-4446-bffd-3b3f81a0887a":{"id":"99eee71b-341b-4446-bffd-3b3f81a0887a","doc_no":"A.6.1.1.1.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3265,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"7aa32207-e371-4e7a-8510-e52a6e04457a":{"id":"7aa32207-e371-4e7a-8510-e52a6e04457a","doc_no":"A.6.1.1.1.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3266,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"0a661998-4951-4edf-9bcd-c9f06edca281":{"id":"0a661998-4951-4edf-9bcd-c9f06edca281","doc_no":"A.6.1.1.1.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3267,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"2d9ca145-3e86-4214-94f4-e7343b3aae9d":{"id":"2d9ca145-3e86-4214-94f4-e7343b3aae9d","doc_no":"A.6.1.1.1.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3268,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"a8b09d72-8d9b-4f07-9e1a-7a3542f3989e":{"id":"a8b09d72-8d9b-4f07-9e1a-7a3542f3989e","doc_no":"A.6.1.1.1.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3269,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"25082eb4-526e-4132-b8cb-f1b035b979bc":{"id":"25082eb4-526e-4132-b8cb-f1b035b979bc","doc_no":"A.6.1.1.1.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3270,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"c0754ba7-c179-40b1-b4c5-f5cc54052004":{"id":"c0754ba7-c179-40b1-b4c5-f5cc54052004","doc_no":"A.6.1.1.1.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3271,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"ea1e82bb-a5e5-48a4-bbf5-520da8282f78":{"id":"ea1e82bb-a5e5-48a4-bbf5-520da8282f78","doc_no":"A.6.1.1.1.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3272,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"676bc853-5516-41e6-911e-9e4dde93157c":{"id":"676bc853-5516-41e6-911e-9e4dde93157c","doc_no":"A.6.1.1.1.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3273,"content":"The documents herein contain all data and specifications for Spark’s Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"967421e6aeecf8d61d1fb8641798b9dff0a88dc74d91ec26e1209664dd77bf67","addressRefs":[]},"4476d153-381e-4120-8230-68d1bd60ec6d":{"id":"4476d153-381e-4120-8230-68d1bd60ec6d","doc_no":"A.6.1.1.1.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3274,"content":"The documents herein organize all base information relevant to Spark’s usage of the Agent Token Primitive.","contentHash":"ec8f3aa80540416b5f2b3a2600b9d9a84cbe643dcbc179ab59db34f53ebdb928","addressRefs":[]},"dfbc2220-3077-4f33-9bf1-f53e78b08c26":{"id":"dfbc2220-3077-4f33-9bf1-f53e78b08c26","doc_no":"A.6.1.1.1.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3275,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"50fb42cb-2f3b-43ef-ad1a-51e5022aeacf":{"id":"50fb42cb-2f3b-43ef-ad1a-51e5022aeacf","doc_no":"A.6.1.1.1.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3276,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"650e12f5-5126-476b-ad46-d686a6d2b22a":{"id":"650e12f5-5126-476b-ad46-d686a6d2b22a","doc_no":"A.6.1.1.1.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3277,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.1.4.2.1 - Single Instance Configuration Document](b2b8b39e-e4d2-496c-b7ea-745ba9202197).","contentHash":"58d40e2a5d4e8064ca9a9a5541f37527f7c7bb631512e8105221ea26fc375484","addressRefs":[]},"8c135060-f236-4b4e-bb85-85d07c41330b":{"id":"8c135060-f236-4b4e-bb85-85d07c41330b","doc_no":"A.6.1.1.1.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3278,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"90400c3d-7111-4e27-afaf-ed85b7d857f4":{"id":"90400c3d-7111-4e27-afaf-ed85b7d857f4","doc_no":"A.6.1.1.1.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3279,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"294d8064-3368-48df-a1ad-d03a33afe123":{"id":"294d8064-3368-48df-a1ad-d03a33afe123","doc_no":"A.6.1.1.1.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3280,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"79c042f5-1086-4526-a27f-45421672a17e":{"id":"79c042f5-1086-4526-a27f-45421672a17e","doc_no":"A.6.1.1.1.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3281,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"db932cf1-db58-40fe-8a12-0114c76cb901":{"id":"db932cf1-db58-40fe-8a12-0114c76cb901","doc_no":"A.6.1.1.1.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3282,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"aaefe5c5-bd0c-4807-a25a-4d79be68943f":{"id":"aaefe5c5-bd0c-4807-a25a-4d79be68943f","doc_no":"A.6.1.1.1.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3283,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"1daf6d99-415f-4d4d-9de9-9a7300d591f5":{"id":"1daf6d99-415f-4d4d-9de9-9a7300d591f5","doc_no":"A.6.1.1.1.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3284,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"b2b8b39e-e4d2-496c-b7ea-745ba9202197":{"id":"b2b8b39e-e4d2-496c-b7ea-745ba9202197","doc_no":"A.6.1.1.1.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3285,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"2e59431e-a058-4495-8c3b-a3619761754b":{"id":"2e59431e-a058-4495-8c3b-a3619761754b","doc_no":"A.6.1.1.1.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3286,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"23f952e8-47a7-4992-8066-18f200d4dddc":{"id":"23f952e8-47a7-4992-8066-18f200d4dddc","doc_no":"A.6.1.1.1.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3287,"content":"The name of Spark’s token is Spark.","contentHash":"8be8bb41484a8e473e8e617b8f55816f8203d982c42043cf89b297ac2de1ce40","addressRefs":[]},"f3dc9c8a-fc65-4856-82bc-13ecd956e7c8":{"id":"f3dc9c8a-fc65-4856-82bc-13ecd956e7c8","doc_no":"A.6.1.1.1.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3288,"content":"The symbol of Spark’s token is SPK.","contentHash":"8b700b22ab59f655a1c68c6360797bdb8b7682c98b60d486bc02a623d83c6c09","addressRefs":[]},"d238a8ef-985b-470f-b88d-0c3f1a449693":{"id":"d238a8ef-985b-470f-b88d-0c3f1a449693","doc_no":"A.6.1.1.1.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3289,"content":"The Genesis Supply of SPK is 10 billion.","contentHash":"44071673c465b40715054fc657ef221dfa84c377df1c7932f9a924222e297b1c","addressRefs":[]},"6ade0500-77d0-4d54-9bc3-0f6bad64f35f":{"id":"6ade0500-77d0-4d54-9bc3-0f6bad64f35f","doc_no":"A.6.1.1.1.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3290,"content":"The address of SPK on the Ethereum Mainnet is `0xc20059e0317DE91738d13af027DfC4a50781b066`. The address of SPK on Base is `0x24327d9138F9f3fc77BEcB10d9BDc2ABb324EE50`.","contentHash":"8d4d3709d31f3b9e76d06415c99f5885bfbde51e97e7403550de5b3e40862f90","addressRefs":["0x24327d9138f9f3fc77becb10d9bdc2abb324ee50","0xc20059e0317de91738d13af027dfc4a50781b066"]},"b6153010-c6f7-41f0-b569-b2687b206ca2":{"id":"b6153010-c6f7-41f0-b569-b2687b206ca2","doc_no":"A.6.1.1.1.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3291,"content":"The token Admin is Spark’s SubProxy Account on the Ethereum Mainnet at `0x3300f198988e4C9C63F75dF86De36421f06af8c4`.","contentHash":"da26fa2376d9ce21870d5d47b4b24fc0071099105e9e6218743d3983572a18e5","addressRefs":["0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"6ff424a3-cb63-4eba-9966-771179ffa3ce":{"id":"6ff424a3-cb63-4eba-9966-771179ffa3ce","doc_no":"A.6.1.1.1.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3292,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Spark Governance. Sky Governance retains the ability to revert where Spark is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"fdff3b4dad17e7e9874043f31be95d76706451ff9d3796b8101091ed0bd9a2ed","addressRefs":[]},"2debc8e3-b25a-41c6-aeb5-5f3b18dbc485":{"id":"2debc8e3-b25a-41c6-aeb5-5f3b18dbc485","doc_no":"A.6.1.1.1.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3293,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"1bdf366d-1955-4ddb-8fb7-794ddcf1dc1e":{"id":"1bdf366d-1955-4ddb-8fb7-794ddcf1dc1e","doc_no":"A.6.1.1.1.2.1.4.2.1.1.7.1","title":"Staking","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3294,"content":"SPK token holders can stake their tokens. The rewards for staking will be specified in a future iteration of the Spark Artifact.","contentHash":"fdea9fa64c38d5e22c72ac4c7e39e3103571166ad82bb25e7d4dd6fdc89da3c4","addressRefs":[]},"978226ce-4c97-4a57-b4e0-d05b3e575c2d":{"id":"978226ce-4c97-4a57-b4e0-d05b3e575c2d","doc_no":"A.6.1.1.1.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3295,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.","contentHash":"40152f8fe8f97c4c79218ed3bfd930929f789afccf070bc7cd80ffdbdea8fbaf","addressRefs":[]},"8b3b46b1-e16a-4d1a-b4d0-52b4cc01ca4f":{"id":"8b3b46b1-e16a-4d1a-b4d0-52b4cc01ca4f","doc_no":"A.6.1.1.1.2.1.4.2.1.2.1","title":"Minting Of Tokens To SPK Company Ltd","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3296,"content":"The Genesis Supply was minted to an account owned by SPK Company Ltd. The address of the account on the Ethereum Mainnet is `0x6FE588FDCC6A34207485cc6e47673F59cCEDF92B`.","contentHash":"bcd275b081ec55ee97fdc35924e6e7b26fdd46a004a3956a2e5f10b99a7bf8d9","addressRefs":["0x6fe588fdcc6a34207485cc6e47673f59ccedf92b"]},"56e08ecf-3a37-45e3-9dce-c75271fcff6b":{"id":"56e08ecf-3a37-45e3-9dce-c75271fcff6b","doc_no":"A.6.1.1.1.2.1.4.2.1.2.2","title":"Transfer Of Tokens To Sky","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3297,"content":"SPK Company Ltd transferred 6.5 billion SPK tokens from the SPK Company Ltd account to the Sky Pause Proxy. The SPK Company Ltd account is specified in [A.6.1.1.1.2.1.4.2.1.2.1 - Minting Of Tokens To SPK Company Ltd](8b3b46b1-e16a-4d1a-b4d0-52b4cc01ca4f).","contentHash":"2c9f620f6f5c1baa896cf9e7d72c8bbed7887c31f8264e70e819a86a1a997277","addressRefs":[]},"34c854ac-2a38-4e44-9d49-ad5d1c1c1605":{"id":"34c854ac-2a38-4e44-9d49-ad5d1c1c1605","doc_no":"A.6.1.1.1.2.1.4.2.1.2.3","title":"Transfer Of Tokens To Spark SubProxy Account","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3298,"content":"SPK Company Ltd transferred 918,760,451 SPK tokens from the SPK Company Ltd account to the Spark SubProxy Account. The SPK Company Ltd account is specified in [A.6.1.1.1.2.1.4.2.1.2.1 - Minting Of Tokens To SPK Company Ltd](8b3b46b1-e16a-4d1a-b4d0-52b4cc01ca4f).\n\nThe Spark SubProxy Account is specified in [A.6.1.1.1.2.1.1.3.1.1.2 - SubProxy Account](378950e0-85c9-4f12-94cd-fb36cde59ba9).","contentHash":"9a78d69a7957c76fac51dd17ee6ab2741c1a488357ad17521d9146d5c5bcb359","addressRefs":[]},"950458c9-dfa7-4c1f-a30a-05d7468fa1c6":{"id":"950458c9-dfa7-4c1f-a30a-05d7468fa1c6","doc_no":"A.6.1.1.1.2.1.4.2.1.2.4","title":"Transfer Of Tokens For Token Launch","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3299,"content":"The SPK Company Ltd account will transfer SPK tokens in connection with the token launch. The SPK Company Ltd account is specified in [A.6.1.1.1.2.1.4.2.1.2.1 - Minting Of Tokens To SPK Company Ltd](8b3b46b1-e16a-4d1a-b4d0-52b4cc01ca4f).\n\nThe amount and nature of these distributions will be specified in a future iteration of the Spark Artifact.","contentHash":"87f48189c1300f018210a21f5cb547b3a25eac9e834c686a04ab53d382aef296","addressRefs":[]},"e68b9cb2-81b0-414d-bea0-f05dbd6ed5a7":{"id":"e68b9cb2-81b0-414d-bea0-f05dbd6ed5a7","doc_no":"A.6.1.1.1.2.1.4.2.1.2.5","title":"Transfer Of Tokens To Spark Foundation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3300,"content":"The SPK Company Ltd account will transfer all of the SPK tokens held by it, other than the tokens specified in [A.6.1.1.1.2.1.4.2.1.2.4 - Transfer Of Tokens For Token Launch](950458c9-dfa7-4c1f-a30a-05d7468fa1c6), to the Spark Foundation. The SPK Company Ltd account is specified in [A.6.1.1.1.2.1.4.2.1.2.1 - Minting Of Tokens To SPK Company Ltd](8b3b46b1-e16a-4d1a-b4d0-52b4cc01ca4f).\n\nThe address of the Spark Foundation on the Ethereum Mainnet is `0x92e4629a4510AF5819d7D1601464C233599fF5ec`.","contentHash":"5ff52e05800923f5a0be8748c1f5ca5ceb6f02dd8e86fea7c39152bc14ac1828","addressRefs":["0x92e4629a4510af5819d7d1601464c233599ff5ec"]},"a0504bd2-0147-406a-bfa3-ba5dcf518f84":{"id":"a0504bd2-0147-406a-bfa3-ba5dcf518f84","doc_no":"A.6.1.1.1.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3301,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"5313f73b-6327-4bdd-8187-eba5f99620f9":{"id":"5313f73b-6327-4bdd-8187-eba5f99620f9","doc_no":"A.6.1.1.1.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3302,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"75619f28-0a62-49cb-9afa-9e9e34f37ef5":{"id":"75619f28-0a62-49cb-9afa-9e9e34f37ef5","doc_no":"A.6.1.1.1.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3303,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"ed197cc5-6ec7-4905-8b23-502940e1dd27":{"id":"ed197cc5-6ec7-4905-8b23-502940e1dd27","doc_no":"A.6.1.1.1.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3304,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"6e713ffe-caf0-48dd-94e2-f1c9b1162aaa":{"id":"6e713ffe-caf0-48dd-94e2-f1c9b1162aaa","doc_no":"A.6.1.1.1.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3305,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"bf55643f-a3db-4d19-9b83-d2da73acd0a5":{"id":"bf55643f-a3db-4d19-9b83-d2da73acd0a5","doc_no":"A.6.1.1.1.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3306,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"47f0c7ef-1b0a-4431-a9de-bc698fe51a46":{"id":"47f0c7ef-1b0a-4431-a9de-bc698fe51a46","doc_no":"A.6.1.1.1.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3307,"content":"The documents herein implement the Operational Primitives for Spark. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"d42efb6868ad50b6ce8c25dcdd87211abe9f17676d0f9b47ec00d2f6dcbc3d16","addressRefs":[]},"beff3df7-ff44-46f9-84ab-30cae1a03a06":{"id":"beff3df7-ff44-46f9-84ab-30cae1a03a06","doc_no":"A.6.1.1.1.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3308,"content":"The documents herein contain all data and specifications for Spark’s Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"8b2c8b83f242fc8c3820d93ee728e0be348b9a1e4db7d18ae7b61dd433ef7da7","addressRefs":[]},"7a6b27e0-4239-4481-9035-b16bf89e6a1d":{"id":"7a6b27e0-4239-4481-9035-b16bf89e6a1d","doc_no":"A.6.1.1.1.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3309,"content":"The documents herein organize all base information relevant to Spark’s usage of the Executor Accord Primitive.","contentHash":"947f9bea9bd0c4b1fe611ec571f2c9bbcb4641253c58d1e5fabf3e5a787dea20","addressRefs":[]},"14ed5074-bac5-4328-9980-cd02d8ea4844":{"id":"14ed5074-bac5-4328-9980-cd02d8ea4844","doc_no":"A.6.1.1.1.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3310,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"21e12538-4068-4bfe-978b-ebab93ccbfe7":{"id":"21e12538-4068-4bfe-978b-ebab93ccbfe7","doc_no":"A.6.1.1.1.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3311,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"bae55a03-dd1f-40c1-8675-3d2b8349a264":{"id":"bae55a03-dd1f-40c1-8675-3d2b8349a264","doc_no":"A.6.1.1.1.2.2.1.1.2.1","title":"Amatsu Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3312,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.2.1.2.1 - Amatsu Instance Configuration Document](79147a0f-b07e-4137-a23c-a7ffbbf8b532).","contentHash":"0dac7a2fd7811b3e3a6734f0f5fd61b111c017d8285ba229a8097bc12c4bdcb6","addressRefs":[]},"beff536d-7bf2-42b1-87f3-d3163d0599c1":{"id":"beff536d-7bf2-42b1-87f3-d3163d0599c1","doc_no":"A.6.1.1.1.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3313,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"9d112903-70a7-4e8d-b1a9-c264c1273414":{"id":"9d112903-70a7-4e8d-b1a9-c264c1273414","doc_no":"A.6.1.1.1.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3314,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.2.1.1.2 - Active Instances Directory](21e12538-4068-4bfe-978b-ebab93ccbfe7), whereas failed Invocations are Archived in [A.6.1.1.1.2.2.1.1.5 - Hub Data Repository](0bb8ba87-72eb-4219-b039-fa0ce29ae396).","contentHash":"63d4b775aeb51e20bbcbe9be669af9e3f2c91c62865e821420dfc49cdec66107","addressRefs":[]},"0bb8ba87-72eb-4219-b039-fa0ce29ae396":{"id":"0bb8ba87-72eb-4219-b039-fa0ce29ae396","doc_no":"A.6.1.1.1.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3315,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"d1ba7168-7093-4b73-828d-a92f9cdb1bb4":{"id":"d1ba7168-7093-4b73-828d-a92f9cdb1bb4","doc_no":"A.6.1.1.1.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3316,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"f4b2c045-75a0-454a-8e5a-f92ac1895df4":{"id":"f4b2c045-75a0-454a-8e5a-f92ac1895df4","doc_no":"A.6.1.1.1.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3317,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"5fe424d1-c2f7-42a0-8925-53f2b22b8ca2":{"id":"5fe424d1-c2f7-42a0-8925-53f2b22b8ca2","doc_no":"A.6.1.1.1.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3318,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"a092c9ca-35c7-4618-a85e-e3d12b6c8f3a":{"id":"a092c9ca-35c7-4618-a85e-e3d12b6c8f3a","doc_no":"A.6.1.1.1.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3319,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"79147a0f-b07e-4137-a23c-a7ffbbf8b532":{"id":"79147a0f-b07e-4137-a23c-a7ffbbf8b532","doc_no":"A.6.1.1.1.2.2.1.2.1","title":"Amatsu Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3320,"content":"The documents herein contain the Instance Configuration Document for the Amatsu Executor Accord Primitive Instance.","contentHash":"1c21c6e9bcc0a4917d31cb0e3687e2950886c0069d29ade1eaf0b26555b89dae","addressRefs":[]},"ee6c93b6-2f9c-41c0-8a4e-9c83f2d726ef":{"id":"ee6c93b6-2f9c-41c0-8a4e-9c83f2d726ef","doc_no":"A.6.1.1.1.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3321,"content":"The documents herein define the parameters of the Amatsu Instance of the Executor Accord Primitive.","contentHash":"4b845300c01bbf362ffc24169c2bf2ea87cf81f1f7ffe9edfdbf4d58ffe27828","addressRefs":[]},"7deff9e4-fa77-4f35-aac6-c73b3d014091":{"id":"7deff9e4-fa77-4f35-aac6-c73b3d014091","doc_no":"A.6.1.1.1.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3322,"content":"The Operational Facilitator and Operational GovOps for Amatsu are specified in [A.6.1.2.1 - Operational Executor Agent Amatsu](c57df14a-fde0-43f3-89ed-c2e4981d6bd5).","contentHash":"76d9fe55fd4705270171ce3e516634decfc626df9dfd732669b6336d1959d1fe","addressRefs":[]},"df6dc78f-3340-4659-a1d8-60df78f6325e":{"id":"df6dc78f-3340-4659-a1d8-60df78f6325e","doc_no":"A.6.1.1.1.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3323,"content":"The documents herein define the custom parameters of the Amatsu Instance of the Executor Accord Primitive, if any.","contentHash":"ad1cc46e684a82e8dbb992bc64497d98c2b32842daf0c18d9a1ea7a5e46c6686","addressRefs":[]},"686bfbe0-9cce-46f5-ae47-ec69eb0fe561":{"id":"686bfbe0-9cce-46f5-ae47-ec69eb0fe561","doc_no":"A.6.1.1.1.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3324,"content":"The documents herein define the process for the ongoing management of the Amatsu Instance of the Executor Accord Primitive.","contentHash":"66a5c505b65a5841595a3aa7d3e91ab5e833ac6f0bf82abcb7cbdd5062b75a6c","addressRefs":[]},"c1ee03df-67b9-4afc-ad4c-b681260412d9":{"id":"c1ee03df-67b9-4afc-ad4c-b681260412d9","doc_no":"A.6.1.1.1.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3325,"content":"The documents herein contain data relevant to the Amatsu Instance of the Executor Accord Primitive.","contentHash":"013ff159b352a95ad5edd2625d11e0b5f7e8d04a27f16c9d3de86248d6580acf","addressRefs":[]},"1f60a729-4f0e-4310-8742-2f26395cd7de":{"id":"1f60a729-4f0e-4310-8742-2f26395cd7de","doc_no":"A.6.1.1.1.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3326,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"ff21545c-e0d4-4057-8098-146a8c386f52":{"id":"ff21545c-e0d4-4057-8098-146a8c386f52","doc_no":"A.6.1.1.1.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3327,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"7ae391f1-e544-4ff5-b6d9-23fa95c75489":{"id":"7ae391f1-e544-4ff5-b6d9-23fa95c75489","doc_no":"A.6.1.1.1.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3328,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"bf932245-fe5e-40cf-a79c-896f3220f3ec":{"id":"bf932245-fe5e-40cf-a79c-896f3220f3ec","doc_no":"A.6.1.1.1.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3329,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"30014177-2d03-44f5-ab3d-37c88cfd68e8":{"id":"30014177-2d03-44f5-ab3d-37c88cfd68e8","doc_no":"A.6.1.1.1.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3330,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.2.1.2 - Active Instances](a092c9ca-35c7-4618-a85e-e3d12b6c8f3a).","contentHash":"40b6ff88d8fde4df95aa5b354c0df42ba09fae7bd229df6ca851a038c9197788","addressRefs":[]},"f60887de-a4eb-4e4b-8aa6-e22cf724772a":{"id":"f60887de-a4eb-4e4b-8aa6-e22cf724772a","doc_no":"A.6.1.1.1.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3331,"content":"The documents herein contain all data and specifications for Spark’s Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"c9ec76ea9ff00ba1c3efb6491f34b8338cc92e3f53ce6741dab68f5ff3a86586","addressRefs":[]},"c47922e8-4dca-49d9-ad95-79ca8ec04731":{"id":"c47922e8-4dca-49d9-ad95-79ca8ec04731","doc_no":"A.6.1.1.1.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3332,"content":"The documents herein organize all base information relevant to Spark’s usage of the Root Edit Primitive.","contentHash":"1477814d722ed99416b8b45238aaf243c28d439623098682b75c6f8e2ce9f18a","addressRefs":[]},"9376926c-21db-43d6-ab51-382e99142367":{"id":"9376926c-21db-43d6-ab51-382e99142367","doc_no":"A.6.1.1.1.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3333,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"8d46f816-d641-43bd-87a0-91892b8794b8":{"id":"8d46f816-d641-43bd-87a0-91892b8794b8","doc_no":"A.6.1.1.1.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3334,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"10cfec9a-f357-40cf-9653-05e1e53c693a":{"id":"10cfec9a-f357-40cf-9653-05e1e53c693a","doc_no":"A.6.1.1.1.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3335,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.2.2.2.1 - Single Instance Configuration Document](2b2e324c-9ee1-4b25-b3b5-95ad85d6afeb).","contentHash":"762b170068eca1db1eb59c72d9f16af85769d7a6b1c9107f7c949f215212a471","addressRefs":[]},"08ee19bb-c8b6-4b13-9a5b-88d610a130a3":{"id":"08ee19bb-c8b6-4b13-9a5b-88d610a130a3","doc_no":"A.6.1.1.1.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3336,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"8fdc9d44-a0b0-488c-b244-8a84bd02a835":{"id":"8fdc9d44-a0b0-488c-b244-8a84bd02a835","doc_no":"A.6.1.1.1.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3337,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"b6f05764-eb33-4263-ba7d-c849ea87d478":{"id":"b6f05764-eb33-4263-ba7d-c849ea87d478","doc_no":"A.6.1.1.1.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3338,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"25f11e43-3772-4acb-8be8-4d66490e5587":{"id":"25f11e43-3772-4acb-8be8-4d66490e5587","doc_no":"A.6.1.1.1.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3339,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"40fdf4da-fd1a-434a-9d8a-5741ea76f864":{"id":"40fdf4da-fd1a-434a-9d8a-5741ea76f864","doc_no":"A.6.1.1.1.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3340,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"6d59ed03-55af-4fff-a5f2-933e1f49115c":{"id":"6d59ed03-55af-4fff-a5f2-933e1f49115c","doc_no":"A.6.1.1.1.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3341,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"75dc70de-f209-4c76-87b8-7a49bf989b3a":{"id":"75dc70de-f209-4c76-87b8-7a49bf989b3a","doc_no":"A.6.1.1.1.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3342,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"2b2e324c-9ee1-4b25-b3b5-95ad85d6afeb":{"id":"2b2e324c-9ee1-4b25-b3b5-95ad85d6afeb","doc_no":"A.6.1.1.1.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3343,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"2708e477-b1ae-40f7-a206-9c736cb40491":{"id":"2708e477-b1ae-40f7-a206-9c736cb40491","doc_no":"A.6.1.1.1.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3344,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.1.2.2.2.2.1.2 - Operational Process Definition](a9c97e28-6ac7-4e04-aac1-9d5dd617c6e0).","contentHash":"9324c8ca189ae6785f20155bc2e263107f75109c4bed453ee08c691883bdfbb5","addressRefs":[]},"a9c97e28-6ac7-4e04-aac1-9d5dd617c6e0":{"id":"a9c97e28-6ac7-4e04-aac1-9d5dd617c6e0","doc_no":"A.6.1.1.1.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3345,"content":"The documents herein define the process for using the Root Edit Primitive to update the Spark Agent Artifact. Information on Spark governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.1.3.1 - Governance Information Unrelated To Root Edit Primitive](3dffc0f5-edbc-48e9-bf13-7d752a64de5a).","contentHash":"ae5e41238c4cf2f1f1e1e7dd58d3825979d015fb9827e841de49035def030cb0","addressRefs":[]},"5c499f3a-d38e-4211-8394-4dc7d05cd383":{"id":"5c499f3a-d38e-4211-8394-4dc7d05cd383","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3346,"content":"The documents herein define the process for using the Root Edit Primitive to update the Spark Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"eb638b2f7445211dd6b71f3bc66c3710dc309c1a538d778910a3aede5f5bccc8","addressRefs":[]},"c9f7cc6e-0548-4599-9f9d-bfa1d2bb7577":{"id":"c9f7cc6e-0548-4599-9f9d-bfa1d2bb7577","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3347,"content":"The Root Edit process begins with a SPK token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. A SPK token holder must hold at least 1% of the total token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Spark Prime\" category. The proposal must include an upfront review of opportunities and associated risks, outlining expected benefits, potential risks, and corresponding mitigation strategies for consideration by the community.","contentHash":"ed946532ac33a0d771b4948e198e2714bd201bdccf2381c142d3906f2fe40ec1","addressRefs":[]},"cc4e9d94-1cba-45c0-938e-9260f9d8e458":{"id":"cc4e9d94-1cba-45c0-938e-9260f9d8e458","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.1.1","title":"Root Edit Proposal Submission Requirements Exception For Nested Contributors","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3348,"content":"Nested Contributors are always authorized to submit Artifact Edit Proposals and do not have to fulfill the token-holding requirements defined in [A.6.1.1.1.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](c9f7cc6e-0548-4599-9f9d-bfa1d2bb7577). However, all other procedural requirements within the Root Edit process continue to apply.\n\nTo see the Agent’s Nested Contributors, see [A.6.1.1.1.2.1.1.3.1.1.4.2 - Phoenix Labs](dd82336a-db68-4e58-a624-22d6de00be4c).","contentHash":"00018fc290de227bc68314d4828164825313692f0abd4806a79024488bf91fd0","addressRefs":[]},"3a6675c3-2bd6-49b0-8d2c-e9d4fe847a62":{"id":"3a6675c3-2bd6-49b0-8d2c-e9d4fe847a62","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.1.2","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3349,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, SPK token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Spark Prime\" category. The title of the post must include the text \"Spark Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total SPK token supply specified in [A.6.1.1.1.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](c9f7cc6e-0548-4599-9f9d-bfa1d2bb7577).","contentHash":"2f70742067c75b2d6dd647958f23f4f11427c91d71a664020725f11d22a60d1a","addressRefs":[]},"67fec75c-8289-4535-90bf-414417608254":{"id":"67fec75c-8289-4535-90bf-414417608254","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3350,"content":"All Spark Root Edit proposals must be reviewed by the Spark Risk Council. The mandate, scope, and review process of the SRC are specified in [A.6.1.1.1.3.1.4 - Spark Risk Council](cf019fb3-d792-4867-abf7-cfe4d0b73e5d).","contentHash":"162907ebad3f562504f61506ac06a047dace15d00ff56098992feae8a6e5f99f","addressRefs":[]},"32bad904-ba90-4abb-9115-0b304a792521":{"id":"32bad904-ba90-4abb-9115-0b304a792521","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3351,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment. The Operational Facilitator also checks if the author of the proposal complies with the requirements in [A.6.1.1.1.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](c9f7cc6e-0548-4599-9f9d-bfa1d2bb7577).\n\nIf the proposal is aligned, and the author is entitled to submit it, the Operational Facilitator must respond to the Forum post to announce their finding. In their Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, or the author is not entitled to submit it, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"e3bf33b45f71dfb4e4e085b5448404bb9e265c4f1dd07e35295c6c5747bd8aa6","addressRefs":[]},"b60cfc4e-4cc5-4040-9610-f2113980831b":{"id":"b60cfc4e-4cc5-4040-9610-f2113980831b","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3352,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Spark Artifact, and where the proposal passes review by the SRC (defined as \"Passed SRC Review\" in [A.6.1.1.1.3.1.4.3.1 - SRC Risk Review](968b4807-8032-42a3-b09d-f787cdb4ef87).), the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. Token holders may vote directly or through Delegates. See [A.6.1.1.1.3.1.3 - Delegation Framework](afa6a37e-e7f1-4efb-bca7-f02bbbf5cf26). The poll is open for three (3) days. A poll must have more than 50% of votes cast, excluding abstentions, in favor to be approved.\n\nSpark’s governance runs in a weekly cycle that begins every Monday. Upon receiving all approvals, the proposal is automatically included in the next cycle. The cut-off time is Friday 8:00 am UTC to ensure the Operational Facilitator has sufficient time to prepare the needed polls for the following Monday. After the cut-off time, it is at the discretion of the Operational Facilitator whether the proposal can be included in the immediate next cycle, or the following cycle.","contentHash":"909ce74fae8b706a0ab4ea10f01e4332173cdc2cafe891d7fb807b7a8cdfddfc","addressRefs":[]},"a9cecbeb-6f07-46fa-b5ad-68dd8ae4b0f0":{"id":"a9cecbeb-6f07-46fa-b5ad-68dd8ae4b0f0","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3353,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"6a9b3956-c4f0-4f59-bc7d-2028a642fc19":{"id":"6a9b3956-c4f0-4f59-bc7d-2028a642fc19","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.5.1","title":"Short Term Transitionary Measures","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3354,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"535cd1c9-1d4d-42e3-bb44-6c128690dd2d":{"id":"535cd1c9-1d4d-42e3-bb44-6c128690dd2d","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3355,"content":"The Spark Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"e8c65e023d9f8da30aa9908fce25345c1f1539856fe71722c13e2fa403639e79","addressRefs":[]},"cc60f445-1ed9-479e-9b44-00de9884a7b5":{"id":"cc60f445-1ed9-479e-9b44-00de9884a7b5","doc_no":"A.6.1.1.1.2.2.2.2.1.2.1.6.1","title":"Time-Limited Root Edit Restrictions On Removal Of Nested Contributors","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3356,"content":"For a period of three years after June 4, 2025, any Artifact Edit that would have the effect of removing a Nested Contributor must be approved by a vote of SKY holders in addition to a vote of SPK holders to be effective.","contentHash":"7119fec0d1f488a23223e27228153eb54c425a4409eceabe77c977318364e37c","addressRefs":[]},"2ae0d2a3-5c06-4ecf-ab1d-abd797477642":{"id":"2ae0d2a3-5c06-4ecf-ab1d-abd797477642","doc_no":"A.6.1.1.1.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3357,"content":"The documents herein define the process for using the Root Edit Primitive to update the Spark Agent Artifact in non-routine conditions.","contentHash":"3d8ce364c16424a0df3803342a5686ce3901fd8ea210085bcb7908697459269f","addressRefs":[]},"7e4dd939-49ec-4cbc-80f5-eb1c71a80a50":{"id":"7e4dd939-49ec-4cbc-80f5-eb1c71a80a50","doc_no":"A.6.1.1.1.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3358,"content":"The documents herein define the process for using the Root Edit Primitive to update the Spark Agent Artifact in urgent or emergency situations.","contentHash":"c6da456e60b9ce02ef1ff629c6c17724a7ae4da85bcc63ca3fecf54d0cc64cbf","addressRefs":[]},"0310ac15-5915-4174-8270-29b3119ce39b":{"id":"0310ac15-5915-4174-8270-29b3119ce39b","doc_no":"A.6.1.1.1.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process in Urgent and Emergency Situations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3359,"content":"In an Urgent or Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Spark Prime\" category), unless doing so would endanger Spark or its users.","contentHash":"793868707ef63f3f4a862df70e102130570f347a11bb3fe73f14cdf73e340866","addressRefs":[]},"6ecef2b2-42c7-4bea-80f0-1cb1cd4e735d":{"id":"6ecef2b2-42c7-4bea-80f0-1cb1cd4e735d","doc_no":"A.6.1.1.1.2.2.2.2.1.2.4","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3360,"content":"The parameters specified in [A.6.1.1.1.2.6.1 - Allocation System Primitive](cd70b9f1-1a59-407c-9945-05e52bf5a3b6) and [A.6.1.1.1.3.2.1 - SparkLend](d9ff0cd2-8999-4d3d-9670-2c7b49c1fe51) will be controlled by Sky Core Governance until Sky determines that the SPK token is decentralized enough to allow for meaningful governance by tokenholders. At such time, which is currently estimated for September 17, 2025, control will transition to Spark Governance. This transitionary measure ensures better decentralization of the SPK token before Spark Governance takes full control of the named parameters under the Root Edit Primitive.","contentHash":"ab7381ab49bbf594c84a3ebda8a517ca9d42fd011806e352646561952d161c48","addressRefs":[]},"67a53565-e1f0-4555-8223-fd6a4ba90814":{"id":"67a53565-e1f0-4555-8223-fd6a4ba90814","doc_no":"A.6.1.1.1.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3361,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"f36d73f1-3ea3-4293-8902-15f7e8510a82":{"id":"f36d73f1-3ea3-4293-8902-15f7e8510a82","doc_no":"A.6.1.1.1.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3362,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"42aca05d-0f81-4e6a-a5df-4a0bd627bd94":{"id":"42aca05d-0f81-4e6a-a5df-4a0bd627bd94","doc_no":"A.6.1.1.1.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3363,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"8d76138a-8705-4a4f-bae0-b4dcedce56e7":{"id":"8d76138a-8705-4a4f-bae0-b4dcedce56e7","doc_no":"A.6.1.1.1.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3364,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"69483c09-487b-448e-aeda-06fbaa7eec4f":{"id":"69483c09-487b-448e-aeda-06fbaa7eec4f","doc_no":"A.6.1.1.1.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3365,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"0285add0-af7b-4026-a79b-0f6db72d8348":{"id":"0285add0-af7b-4026-a79b-0f6db72d8348","doc_no":"A.6.1.1.1.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3366,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"2ebe2537-74e6-476c-81a3-88a1abb76a6b":{"id":"2ebe2537-74e6-476c-81a3-88a1abb76a6b","doc_no":"A.6.1.1.1.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3367,"content":"The documents herein contain all data and specifications for Spark’s Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"59bf2c9aeeff236f4485d75f2c919390011fc942862d679851e9548240447d9a","addressRefs":[]},"35ba196a-9dee-45f2-8d9f-2aa48a4d2816":{"id":"35ba196a-9dee-45f2-8d9f-2aa48a4d2816","doc_no":"A.6.1.1.1.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3368,"content":"The documents herein organize all base information relevant to Spark’s usage of the Light Agent Primitive.","contentHash":"eccaeec4e33693d5cbdd5a39dd2c451a46106dcad1d77569eed8c7226f9c09a6","addressRefs":[]},"b050468a-8e2c-4143-b0a1-6cb170875143":{"id":"b050468a-8e2c-4143-b0a1-6cb170875143","doc_no":"A.6.1.1.1.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3369,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"c6c64d06-3533-491c-920c-5b58ee328a48":{"id":"c6c64d06-3533-491c-920c-5b58ee328a48","doc_no":"A.6.1.1.1.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3370,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"38fe6523-224d-4adf-9048-157879ca89a0":{"id":"38fe6523-224d-4adf-9048-157879ca89a0","doc_no":"A.6.1.1.1.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3371,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"1fed54f6-a68b-4d70-a790-e3da5a1fb6f7":{"id":"1fed54f6-a68b-4d70-a790-e3da5a1fb6f7","doc_no":"A.6.1.1.1.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3372,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.2.3.1.2 - Active Instances Directory](c6c64d06-3533-491c-920c-5b58ee328a48), whereas failed Invocations are Archived in [A.6.1.1.1.2.2.3.1.5 - Hub Data Repository](aafad299-5a5d-48af-9e0f-519f2aee0f79).","contentHash":"9f8791bf029399a3b83cd74b06d6cb7da1d0333a7e31e053ab16fdf218ce38af","addressRefs":[]},"aafad299-5a5d-48af-9e0f-519f2aee0f79":{"id":"aafad299-5a5d-48af-9e0f-519f2aee0f79","doc_no":"A.6.1.1.1.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3373,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"22c57270-fa9b-4bee-ab75-da8170e73eb4":{"id":"22c57270-fa9b-4bee-ab75-da8170e73eb4","doc_no":"A.6.1.1.1.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3374,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"d42821f2-4d0c-4b84-aace-e9f7c5c9d4b0":{"id":"d42821f2-4d0c-4b84-aace-e9f7c5c9d4b0","doc_no":"A.6.1.1.1.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3375,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"be668bea-0d71-46d7-98a5-455241823088":{"id":"be668bea-0d71-46d7-98a5-455241823088","doc_no":"A.6.1.1.1.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3376,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"4c45583a-b948-4a1c-bd85-0adae4179761":{"id":"4c45583a-b948-4a1c-bd85-0adae4179761","doc_no":"A.6.1.1.1.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3377,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"e001058f-bd04-45d0-b13a-53a8f3c66525":{"id":"e001058f-bd04-45d0-b13a-53a8f3c66525","doc_no":"A.6.1.1.1.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3378,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"ac5409c5-58d7-4e8a-b41a-49c7455cb42c":{"id":"ac5409c5-58d7-4e8a-b41a-49c7455cb42c","doc_no":"A.6.1.1.1.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3379,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.2.3.2 - Active Instances](4c45583a-b948-4a1c-bd85-0adae4179761).","contentHash":"a25c9c0bfb4d955cb44118da16ec295d635a6d0bf98df1707d23c2f49165b156","addressRefs":[]},"4547691b-3607-4b30-b7f1-4d04bfe3c912":{"id":"4547691b-3607-4b30-b7f1-4d04bfe3c912","doc_no":"A.6.1.1.1.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3380,"content":"The documents herein implement the Ecosystem Upkeep Primitives for Spark. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"d306997460443fc602e8201e76a1f62efd82ae0524ed9f52f20d38b73c156d60","addressRefs":[]},"cc285753-1f2a-4a05-a9a9-e52da1168790":{"id":"cc285753-1f2a-4a05-a9a9-e52da1168790","doc_no":"A.6.1.1.1.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3381,"content":"The documents herein contain all data and specifications for Spark’s Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"da671a6b72fba13258727c165e14bade4c2a9f843e9c894bdb3e93bfc1673922","addressRefs":[]},"4a0fea8a-d2e3-4ebd-8c3b-a5e27c74dac0":{"id":"4a0fea8a-d2e3-4ebd-8c3b-a5e27c74dac0","doc_no":"A.6.1.1.1.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3382,"content":"The documents herein organize all base information relevant to Spark’s usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"e923df66666645afe5a08aab48ec54e346a1d4c9e5c2fc46089e4d100fe12af9","addressRefs":[]},"66017146-97af-401a-92ae-9c1665e17492":{"id":"66017146-97af-401a-92ae-9c1665e17492","doc_no":"A.6.1.1.1.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3383,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"93ce0ff1-a4c3-48e7-b147-cd27283fe307":{"id":"93ce0ff1-a4c3-48e7-b147-cd27283fe307","doc_no":"A.6.1.1.1.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3384,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"44ef4e9c-5308-4cba-bf2a-e44951c67256":{"id":"44ef4e9c-5308-4cba-bf2a-e44951c67256","doc_no":"A.6.1.1.1.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3385,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.3.1.2.1 - Single Instance Configuration Document](0eff0bd2-25e6-4f13-8164-f4b41c9afe07).","contentHash":"9411b47edebac11c2df7070c2d5871c96d41ada8cdbd3af91b9f3c02ff2768d5","addressRefs":[]},"49f65762-a90f-4096-aed2-ac913e3449ac":{"id":"49f65762-a90f-4096-aed2-ac913e3449ac","doc_no":"A.6.1.1.1.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3386,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"548b47ca-dc50-465c-b7ec-09805cc52af2":{"id":"548b47ca-dc50-465c-b7ec-09805cc52af2","doc_no":"A.6.1.1.1.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3387,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"48dd15d4-4cd4-4fb0-abe4-bccda146f08d":{"id":"48dd15d4-4cd4-4fb0-abe4-bccda146f08d","doc_no":"A.6.1.1.1.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3388,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ac8e9902-f252-4b84-bdd3-f5d255639e88":{"id":"ac8e9902-f252-4b84-bdd3-f5d255639e88","doc_no":"A.6.1.1.1.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3389,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"b9e2baa0-22cd-49f9-a3ed-65971ddb39ac":{"id":"b9e2baa0-22cd-49f9-a3ed-65971ddb39ac","doc_no":"A.6.1.1.1.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3390,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"b2aecba9-fdc6-41e9-ab42-3367effd17d9":{"id":"b2aecba9-fdc6-41e9-ab42-3367effd17d9","doc_no":"A.6.1.1.1.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3391,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"602f7677-417b-435a-96bd-eba64963c9e1":{"id":"602f7677-417b-435a-96bd-eba64963c9e1","doc_no":"A.6.1.1.1.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3392,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"0eff0bd2-25e6-4f13-8164-f4b41c9afe07":{"id":"0eff0bd2-25e6-4f13-8164-f4b41c9afe07","doc_no":"A.6.1.1.1.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3393,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"eb1a5166-e3e1-4809-aa0b-77c985bd48c1":{"id":"eb1a5166-e3e1-4809-aa0b-77c985bd48c1","doc_no":"A.6.1.1.1.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3394,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"0e1280e0-9781-4356-81f0-4540e06b380a":{"id":"0e1280e0-9781-4356-81f0-4540e06b380a","doc_no":"A.6.1.1.1.2.3.1.2.1.1.1","title":"Terms","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3395,"content":"Spark will pay 0.50% of its market capitalization per year in USDS.","contentHash":"b1bdad53c91683a53371930eca80be1026757e38e8892666c21af09aa16a6b4b","addressRefs":[]},"42b0e1c9-7b51-4cb7-865e-19911e4b8835":{"id":"42b0e1c9-7b51-4cb7-865e-19911e4b8835","doc_no":"A.6.1.1.1.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3396,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"c8194db1-d94b-4bfc-8fc6-075f255a0fd9":{"id":"c8194db1-d94b-4bfc-8fc6-075f255a0fd9","doc_no":"A.6.1.1.1.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3397,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"77c46d45-8fd7-4125-ae0a-ed6466e965d4":{"id":"77c46d45-8fd7-4125-ae0a-ed6466e965d4","doc_no":"A.6.1.1.1.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3398,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"35af6171-70b6-4ccd-81ed-95b5548e8406":{"id":"35af6171-70b6-4ccd-81ed-95b5548e8406","doc_no":"A.6.1.1.1.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3399,"content":"The process to pay 0.50% of Spark’s market capitalization per year in USDS will be specified in future iterations of the Spark Artifact.","contentHash":"289879f2d79ae40d17c2816fe40365e99356298810f6d8011a207e4743a7cc78","addressRefs":[]},"f6ea2cb2-ce88-4dda-aed1-8d2f4f0c9a97":{"id":"f6ea2cb2-ce88-4dda-aed1-8d2f4f0c9a97","doc_no":"A.6.1.1.1.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3400,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"14080c77-753f-4daa-ad7c-1b1ca203cb9a":{"id":"14080c77-753f-4daa-ad7c-1b1ca203cb9a","doc_no":"A.6.1.1.1.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3401,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"928ae046-ac8d-47ff-a8c7-3b9abe2b9879":{"id":"928ae046-ac8d-47ff-a8c7-3b9abe2b9879","doc_no":"A.6.1.1.1.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3402,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"e6f23920-b611-41f2-8d80-97b0e79b7ca1":{"id":"e6f23920-b611-41f2-8d80-97b0e79b7ca1","doc_no":"A.6.1.1.1.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3403,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"b8f8acf8-fbdc-47aa-9ff4-2e2fcee33815":{"id":"b8f8acf8-fbdc-47aa-9ff4-2e2fcee33815","doc_no":"A.6.1.1.1.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3404,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"aec8ac86-35d4-4ff7-a8c8-61a8056063b3":{"id":"aec8ac86-35d4-4ff7-a8c8-61a8056063b3","doc_no":"A.6.1.1.1.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3405,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"9c60c0c9-19df-4cb1-afa8-2897932dafe5":{"id":"9c60c0c9-19df-4cb1-afa8-2897932dafe5","doc_no":"A.6.1.1.1.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3406,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"f7b2e25f-fc99-4266-af87-f04239a97b1b":{"id":"f7b2e25f-fc99-4266-af87-f04239a97b1b","doc_no":"A.6.1.1.1.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3407,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"b39e05c8-cfcc-4671-b142-b691437cb98e":{"id":"b39e05c8-cfcc-4671-b142-b691437cb98e","doc_no":"A.6.1.1.1.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3408,"content":"The documents herein contain all data and specifications for Spark’s Instance of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"dbeb1620e599e50bc14a65c4e6f00956d30c89f3568408ce3e90be2f72ea564e","addressRefs":[]},"4b400b96-b0a3-4b7d-81b9-b22d4f12f16f":{"id":"4b400b96-b0a3-4b7d-81b9-b22d4f12f16f","doc_no":"A.6.1.1.1.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3409,"content":"The documents herein organize all base information relevant to Spark’s usage of the Upkeep Rebate Primitive.","contentHash":"f1f6e2156c82424354fd809e3fc3eb0fb13690241221bf01b93e42b9532d48b6","addressRefs":[]},"d87daf19-7400-4a78-b7e8-4a5cb86f49d2":{"id":"d87daf19-7400-4a78-b7e8-4a5cb86f49d2","doc_no":"A.6.1.1.1.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3410,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"5f604d2e-2934-4347-b97a-3ab213e0b413":{"id":"5f604d2e-2934-4347-b97a-3ab213e0b413","doc_no":"A.6.1.1.1.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3411,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"6cc8b26a-5b3c-49d6-9358-cbdbe9cb85cf":{"id":"6cc8b26a-5b3c-49d6-9358-cbdbe9cb85cf","doc_no":"A.6.1.1.1.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3412,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.3.2.2.1 - Single Instance Configuration Document](64a12cf8-b7dc-4fd3-895b-bef979339bd1).","contentHash":"6ff29711d60c0f78150fda22a513b63454cc6debae2ba5e01c14f35b5973c617","addressRefs":[]},"32779877-5fcb-49ff-b4c4-8246d8234a41":{"id":"32779877-5fcb-49ff-b4c4-8246d8234a41","doc_no":"A.6.1.1.1.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3413,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"f13ef252-e2b3-4966-a554-279cae4f41ee":{"id":"f13ef252-e2b3-4966-a554-279cae4f41ee","doc_no":"A.6.1.1.1.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3414,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"7dabf38f-5d1d-481b-bd96-eb3b2dcf8e8c":{"id":"7dabf38f-5d1d-481b-bd96-eb3b2dcf8e8c","doc_no":"A.6.1.1.1.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3415,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"66af8a51-58a2-4a98-a510-4862bfb81cf6":{"id":"66af8a51-58a2-4a98-a510-4862bfb81cf6","doc_no":"A.6.1.1.1.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3416,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"0c53aaf7-ef3f-432a-bcac-c7c8c0e434b9":{"id":"0c53aaf7-ef3f-432a-bcac-c7c8c0e434b9","doc_no":"A.6.1.1.1.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3417,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"e1cf5c38-9e90-43c4-b133-faea5daf0ee5":{"id":"e1cf5c38-9e90-43c4-b133-faea5daf0ee5","doc_no":"A.6.1.1.1.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3418,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"507755d9-c459-475d-8099-63c0417f9335":{"id":"507755d9-c459-475d-8099-63c0417f9335","doc_no":"A.6.1.1.1.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3419,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"64a12cf8-b7dc-4fd3-895b-bef979339bd1":{"id":"64a12cf8-b7dc-4fd3-895b-bef979339bd1","doc_no":"A.6.1.1.1.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3420,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"c67462b5-3423-4323-b94b-f9e5270eda28":{"id":"c67462b5-3423-4323-b94b-f9e5270eda28","doc_no":"A.6.1.1.1.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3421,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"bb605dda-ce85-46f2-8055-6d07d68b7214":{"id":"bb605dda-ce85-46f2-8055-6d07d68b7214","doc_no":"A.6.1.1.1.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3422,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"b0882539-16b9-405f-9e7c-c98bdca1d8e7":{"id":"b0882539-16b9-405f-9e7c-c98bdca1d8e7","doc_no":"A.6.1.1.1.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3423,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"9f9ad799-8c8d-43ad-a99e-24786f46dd40":{"id":"9f9ad799-8c8d-43ad-a99e-24786f46dd40","doc_no":"A.6.1.1.1.2.3.2.2.1.2.1.1","title":"Spark Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3424,"content":"Spark keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"3fe63ed69b3c32708af5f5307f31b6cd11e4acb99b84dbd4fae6a02fb44f09a1","addressRefs":[]},"d14e7fce-217d-49bc-b0c3-c5305c17ea28":{"id":"d14e7fce-217d-49bc-b0c3-c5305c17ea28","doc_no":"A.6.1.1.1.2.3.2.2.1.2.1.2","title":"Spark Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3425,"content":"When paying Ecosystem Upkeep fees, Spark deducts the rebate from the fees it pays.","contentHash":"55bc6d8f986adcea2a8481a336dfd99d02e63491738ab53859d2692e74fc2c13","addressRefs":[]},"93503e51-089a-4c63-a353-7c12574ea5b9":{"id":"93503e51-089a-4c63-a353-7c12574ea5b9","doc_no":"A.6.1.1.1.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3426,"content":"Operational GovOps reviews Spark’s calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Spark Prime\" category and work with Spark to resolve the disagreement. If Operational GovOps and Spark cannot resolve the disagreement, it must be escalated to Core GovOps.","contentHash":"ed3df704d6188bf844609e3d7b085a887ae576f15a430b26651c463568258982","addressRefs":[]},"a131e0d2-1946-4da2-b3a3-cfaace9d3978":{"id":"a131e0d2-1946-4da2-b3a3-cfaace9d3978","doc_no":"A.6.1.1.1.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3427,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"03646635-39d9-4efb-9628-1f567cd2da99":{"id":"03646635-39d9-4efb-9628-1f567cd2da99","doc_no":"A.6.1.1.1.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3428,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"c0f8debb-8b20-428e-bdaa-8341c00fb0ee":{"id":"c0f8debb-8b20-428e-bdaa-8341c00fb0ee","doc_no":"A.6.1.1.1.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3429,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"5bd30523-e635-41e2-9929-d458b0bc29db":{"id":"5bd30523-e635-41e2-9929-d458b0bc29db","doc_no":"A.6.1.1.1.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3430,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"be8f07a7-247f-466d-a68f-fd26fd84df9b":{"id":"be8f07a7-247f-466d-a68f-fd26fd84df9b","doc_no":"A.6.1.1.1.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3431,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"7997ed4f-6484-4aab-9b46-55b4db6e4e23":{"id":"7997ed4f-6484-4aab-9b46-55b4db6e4e23","doc_no":"A.6.1.1.1.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3432,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"29ea3609-b1d4-4488-9fa0-15e26dfd4c26":{"id":"29ea3609-b1d4-4488-9fa0-15e26dfd4c26","doc_no":"A.6.1.1.1.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3433,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"2008b69e-a0de-4274-b459-e2f613425a4b":{"id":"2008b69e-a0de-4274-b459-e2f613425a4b","doc_no":"A.6.1.1.1.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3434,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"bdb0c16b-8077-49c1-b925-bbc93884b04a":{"id":"bdb0c16b-8077-49c1-b925-bbc93884b04a","doc_no":"A.6.1.1.1.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3435,"content":"The documents herein implement the SkyLink Primitives for Spark. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"6d5bdc10b73dde0c17876c49b8dac0419249123006719187482842047538211d","addressRefs":[]},"148ada53-0815-49bc-a454-57bdf08a556e":{"id":"148ada53-0815-49bc-a454-57bdf08a556e","doc_no":"A.6.1.1.1.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3436,"content":"The documents herein contain all data and specifications for Spark’s instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"fc7b2e4c49658526613da82951c8c6dfeaaaca30812638d7ab6fe8c83b52c6dc","addressRefs":[]},"88de14eb-6470-4980-add9-992726d6e006":{"id":"88de14eb-6470-4980-add9-992726d6e006","doc_no":"A.6.1.1.1.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3437,"content":"The documents herein organize all base information relevant to Spark’s usage of the Token SkyLink Primitive.","contentHash":"5012405e8bdfea4064fd49c68edd4b669b0c2b2f7c7580a91a07d07fe3c6e7ab","addressRefs":[]},"e8b72d23-67b6-490e-9a3a-80953958e5b2":{"id":"e8b72d23-67b6-490e-9a3a-80953958e5b2","doc_no":"A.6.1.1.1.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3438,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"144380dc-5a6c-48e1-9004-12e0ca96ed10":{"id":"144380dc-5a6c-48e1-9004-12e0ca96ed10","doc_no":"A.6.1.1.1.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3439,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"6be69464-0e1c-4f5f-9282-040f0a7b259b":{"id":"6be69464-0e1c-4f5f-9282-040f0a7b259b","doc_no":"A.6.1.1.1.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3440,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"25dbed2d-67a4-43c5-8877-189832337e68":{"id":"25dbed2d-67a4-43c5-8877-189832337e68","doc_no":"A.6.1.1.1.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3441,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.4.1.1.2 - Active Instances Directory](144380dc-5a6c-48e1-9004-12e0ca96ed10), whereas failed Invocations are Archived in [A.6.1.1.1.2.4.1.1.5 - Hub Data Repository](f2c09f57-213c-4157-b336-949924d2aa26).","contentHash":"a34d7f1d9c896618942830ca11174908f38cdcbb1932aab320b5d010702730b4","addressRefs":[]},"f2c09f57-213c-4157-b336-949924d2aa26":{"id":"f2c09f57-213c-4157-b336-949924d2aa26","doc_no":"A.6.1.1.1.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3442,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"8c6fc006-026d-48eb-8dfa-a06d3f6a3a92":{"id":"8c6fc006-026d-48eb-8dfa-a06d3f6a3a92","doc_no":"A.6.1.1.1.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3443,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"d4257fc6-98a9-439b-a424-0d309efed41a":{"id":"d4257fc6-98a9-439b-a424-0d309efed41a","doc_no":"A.6.1.1.1.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3444,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"7fc67d63-28aa-43c3-8a1d-36921f581df6":{"id":"7fc67d63-28aa-43c3-8a1d-36921f581df6","doc_no":"A.6.1.1.1.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3445,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"02016186-2953-489d-ae5d-aca30085c2b9":{"id":"02016186-2953-489d-ae5d-aca30085c2b9","doc_no":"A.6.1.1.1.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3446,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"dd1f8a40-8037-4cb6-961c-bb2448cbfc90":{"id":"dd1f8a40-8037-4cb6-961c-bb2448cbfc90","doc_no":"A.6.1.1.1.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3447,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"873c56da-485b-47cc-b926-08d62a471805":{"id":"873c56da-485b-47cc-b926-08d62a471805","doc_no":"A.6.1.1.1.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3448,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.4.1.2 - Active Instances](02016186-2953-489d-ae5d-aca30085c2b9).","contentHash":"7ea34b2bc210d779345609c6a3a1567cf0cf548bbadf2cf232d39ecaaa9dc4c9","addressRefs":[]},"56116244-c569-4cb0-8399-eaae1ab36e97":{"id":"56116244-c569-4cb0-8399-eaae1ab36e97","doc_no":"A.6.1.1.1.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3449,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Spark. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"e7e27699cd7eeb343d27bbba22ef6259ecd233b49b128f2722fce0f9d675a794","addressRefs":[]},"87916659-3b1e-4e65-8080-d6e1baab74e4":{"id":"87916659-3b1e-4e65-8080-d6e1baab74e4","doc_no":"A.6.1.1.1.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3450,"content":"The documents herein contain all data and specifications for Spark’s instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"1f2da23da0cbd7a9b7e40147586bfadb01265f1c7181b216fa750b23be2ebd08","addressRefs":[]},"8dece7e0-529f-4522-9742-d883cc0939a7":{"id":"8dece7e0-529f-4522-9742-d883cc0939a7","doc_no":"A.6.1.1.1.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3451,"content":"The documents herein organize all base information relevant to Spark’s usage of the Distribution Reward Primitive.","contentHash":"2c519d4520bb97b5855e4d6a8fdf14e0d80daeb7c3e4b254cec70ac2794c6079","addressRefs":[]},"b7f5818c-2c5c-4fda-aff0-58321cfbab35":{"id":"b7f5818c-2c5c-4fda-aff0-58321cfbab35","doc_no":"A.6.1.1.1.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3452,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"fd278ccf-3054-4437-a052-ccb0291c3025":{"id":"fd278ccf-3054-4437-a052-ccb0291c3025","doc_no":"A.6.1.1.1.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3453,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"9537232d-674a-4821-b0ce-8ea5ce79b91e":{"id":"9537232d-674a-4821-b0ce-8ea5ce79b91e","doc_no":"A.6.1.1.1.2.5.1.1.2.1","title":"SparkLend Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3454,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.5.1.2.1 - SparkLend Instance Configuration Document](fd4059de-4a35-4147-a6ff-f7ecc88ceae6).","contentHash":"cc91e7ef172eac19c46019f2b0d1055215432b227738478c5e66d094d2a60b92","addressRefs":[]},"7b60bfe0-3dbb-4a19-9c6c-88f0fdb9479b":{"id":"7b60bfe0-3dbb-4a19-9c6c-88f0fdb9479b","doc_no":"A.6.1.1.1.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3455,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"798b67c4-749e-4d70-be25-7f7b9ff88268":{"id":"798b67c4-749e-4d70-be25-7f7b9ff88268","doc_no":"A.6.1.1.1.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3456,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.5.1.1.2 - Active Instances Directory](fd278ccf-3054-4437-a052-ccb0291c3025), whereas failed Invocations are Archived in [A.6.1.1.1.2.5.1.1.5 - Hub Data Repository](fad965ad-63a7-4814-97db-bc1809dee69c).","contentHash":"48cb85236bc1edbb0a00e50dc3b6925d9a462458a0416b745d7e057feb66f345","addressRefs":[]},"fad965ad-63a7-4814-97db-bc1809dee69c":{"id":"fad965ad-63a7-4814-97db-bc1809dee69c","doc_no":"A.6.1.1.1.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3457,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"470664fd-8220-4745-8e5c-0fec350cc21f":{"id":"470664fd-8220-4745-8e5c-0fec350cc21f","doc_no":"A.6.1.1.1.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3458,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"46ccaf77-f048-47fe-adfd-ef66fb0e2a93":{"id":"46ccaf77-f048-47fe-adfd-ef66fb0e2a93","doc_no":"A.6.1.1.1.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3459,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"d8edb5d5-2a21-46e0-a894-1cd452999763":{"id":"d8edb5d5-2a21-46e0-a894-1cd452999763","doc_no":"A.6.1.1.1.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3460,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"53a54bee-41b6-4135-9fa0-cf7876955a28":{"id":"53a54bee-41b6-4135-9fa0-cf7876955a28","doc_no":"A.6.1.1.1.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3461,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"fd4059de-4a35-4147-a6ff-f7ecc88ceae6":{"id":"fd4059de-4a35-4147-a6ff-f7ecc88ceae6","doc_no":"A.6.1.1.1.2.5.1.2.1","title":"SparkLend Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3462,"content":"The documents herein contain the Instance Configuration Document for the SparkLend Distribution Reward Primitive Instance.","contentHash":"13355dbc43acdb0c915ef29c802af90514293eefeb00d54fdd1b6bf1a578d409","addressRefs":[]},"d737b3b2-f574-41e9-8ebc-3b828174f6fc":{"id":"d737b3b2-f574-41e9-8ebc-3b828174f6fc","doc_no":"A.6.1.1.1.2.5.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3463,"content":"The documents herein define the parameters of the SparkLend Instance of the Distribution Reward Primitive.","contentHash":"97077e16a5e65e57958e477031a51cca235320b3ff409313c3e9bd5a6d4838b1","addressRefs":[]},"1e5d71a8-5e79-40da-8b86-c07b3f341344":{"id":"1e5d71a8-5e79-40da-8b86-c07b3f341344","doc_no":"A.6.1.1.1.2.5.1.2.1.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3464,"content":"`128`.","contentHash":"959594f2c0a3184b5034df2d4537b115b27470fdd80a1d1728d16c5cc7f1fd29","addressRefs":[]},"101bce08-907e-442b-b6b3-754d3ad1455b":{"id":"101bce08-907e-442b-b6b3-754d3ad1455b","doc_no":"A.6.1.1.1.2.5.1.2.1.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3465,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"6c15d6b4-24b9-49e3-b7eb-c955c4a8d7cd":{"id":"6c15d6b4-24b9-49e3-b7eb-c955c4a8d7cd","doc_no":"A.6.1.1.1.2.5.1.2.1.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3466,"content":"The documents herein define the custom parameters of the SparkLend Instance of the Distribution Reward Primitive, if any.","contentHash":"5f03e903bca889d24584c34f91fab498a74f74e35b7f8a5c86435eab3643a5bd","addressRefs":[]},"8dd6242a-e7ca-4cb9-bfd0-c0393886485f":{"id":"8dd6242a-e7ca-4cb9-bfd0-c0393886485f","doc_no":"A.6.1.1.1.2.5.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3467,"content":"The documents herein define the process for the ongoing management of the SparkLend Instance of the Distribution Reward Primitive.","contentHash":"61df2779d0ed7621ba35fca1522e49f76fabb14f610e1d30e8dab683684c6d1e","addressRefs":[]},"a419b055-7d92-41b9-89f4-8f1fe082b814":{"id":"a419b055-7d92-41b9-89f4-8f1fe082b814","doc_no":"A.6.1.1.1.2.5.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3468,"content":"This document defines the protocol for routine ongoing management of the SparkLend Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Spark Artifact, a version of the full process definition customized to Spark will be included herein.","contentHash":"9c76bb5d93445464421ee7a6e0f03a2ff0b47765f500f02a54c3993c5eb0179b","addressRefs":[]},"620944c3-caa2-4c8c-823f-8ec08417221c":{"id":"620944c3-caa2-4c8c-823f-8ec08417221c","doc_no":"A.6.1.1.1.2.5.1.2.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3469,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"56404af1-c2ec-4bd5-876d-aa5db178ff40":{"id":"56404af1-c2ec-4bd5-876d-aa5db178ff40","doc_no":"A.6.1.1.1.2.5.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3470,"content":"The documents herein define the protocol for non-routine ongoing management of the SparkLend Instance of this Distribution Reward Primitive.","contentHash":"cebe8ed24175c25636214113093707627ba55e734324519445eb707c7178d382","addressRefs":[]},"221f522d-789e-418c-9d47-1d3c1bfcd803":{"id":"221f522d-789e-418c-9d47-1d3c1bfcd803","doc_no":"A.6.1.1.1.2.5.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3471,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the SparkLend Instance of this Distribution Reward Primitive.","contentHash":"cfd8ccf85a7d6a16cadaf73c9d439741840e59c452f03074a9846774ee8c3903","addressRefs":[]},"cfe05f3a-5017-442a-998d-8b71ba3f6845":{"id":"cfe05f3a-5017-442a-998d-8b71ba3f6845","doc_no":"A.6.1.1.1.2.5.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3472,"content":"The documents herein contain data relevant to the SparkLend Instance of the Distribution Reward Primitive.","contentHash":"6d0a98c10a77b3081fb8dc61e72c948ea6b3d0cf942e1b6b811b370889f4089d","addressRefs":[]},"09138ffc-9484-4a3a-b12a-d2fb2fc8f6ac":{"id":"09138ffc-9484-4a3a-b12a-d2fb2fc8f6ac","doc_no":"A.6.1.1.1.2.5.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3473,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"aaf76715-a3f3-4dc1-82d4-b10d7975f10b":{"id":"aaf76715-a3f3-4dc1-82d4-b10d7975f10b","doc_no":"A.6.1.1.1.2.5.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3474,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"41bffca2-7594-437c-84df-50827e8c001b":{"id":"41bffca2-7594-437c-84df-50827e8c001b","doc_no":"A.6.1.1.1.2.5.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3475,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"971d047b-4e7b-4545-9090-6d509e572aa0":{"id":"971d047b-4e7b-4545-9090-6d509e572aa0","doc_no":"A.6.1.1.1.2.5.1.2.1.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3476,"content":"The Distribution Reward payments for the SparkLend Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"08a846048a9027c51adae2b53a29a4a61e321e2d764d18d04f5be0750e582383","addressRefs":[]},"055fe10c-2d08-49a1-90c5-e124e2e0b4f9":{"id":"055fe10c-2d08-49a1-90c5-e124e2e0b4f9","doc_no":"A.6.1.1.1.2.5.1.2.1.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3477,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"6552c0fe-f9f7-4828-893b-cf278ce5161f":{"id":"6552c0fe-f9f7-4828-893b-cf278ce5161f","doc_no":"A.6.1.1.1.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3478,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"701a2dc3-bcfe-494e-8a4c-af18cfbffc54":{"id":"701a2dc3-bcfe-494e-8a4c-af18cfbffc54","doc_no":"A.6.1.1.1.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3479,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.5.1.2 - Active Instances](53a54bee-41b6-4135-9fa0-cf7876955a28).","contentHash":"4454db0b90cc6b7e49ec58e506c63c014332936c01e7a8a161db6929f2b28695","addressRefs":[]},"e9f5a7e8-2260-484f-a725-871782a9bc01":{"id":"e9f5a7e8-2260-484f-a725-871782a9bc01","doc_no":"A.6.1.1.1.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3480,"content":"The documents herein contain all data and specifications for Spark’s Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"142f98f052763c7c83b0c1d93226682853d2a7fc11d6493fa0c07fd2a7e5b893","addressRefs":[]},"8afae5a1-8734-4b98-bfd6-1dbe7842f146":{"id":"8afae5a1-8734-4b98-bfd6-1dbe7842f146","doc_no":"A.6.1.1.1.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3481,"content":"The documents herein organize all base information relevant to Spark’s usage of the Integration Boost Primitive.","contentHash":"2631a0fcf6b1e87453657936b21cfabf51ef74bb2c0fa62415d73b743c8bf080","addressRefs":[]},"305ab02d-23c0-45e7-9cc3-04122a339662":{"id":"305ab02d-23c0-45e7-9cc3-04122a339662","doc_no":"A.6.1.1.1.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3482,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"bb23a141-5119-4473-be3a-8f3c2a6f181a":{"id":"bb23a141-5119-4473-be3a-8f3c2a6f181a","doc_no":"A.6.1.1.1.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3483,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"c175e30d-5470-46b0-ad5f-433c3e934d1f":{"id":"c175e30d-5470-46b0-ad5f-433c3e934d1f","doc_no":"A.6.1.1.1.2.5.2.1.2.1","title":"Aave Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3484,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.5.2.2.1 - Aave Instance Configuration Document](c88763c9-f2af-4d4e-81d5-6ea0dfdd05c5).","contentHash":"96b2dc48a7afe5cfbec74407aa8b622d3f20fb8093026a5417178d87a63a460e","addressRefs":[]},"3c1fa1ea-752d-4438-aa3c-00634dcdb45a":{"id":"3c1fa1ea-752d-4438-aa3c-00634dcdb45a","doc_no":"A.6.1.1.1.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3485,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"786859ec-1f50-4343-8bed-82ef86781356":{"id":"786859ec-1f50-4343-8bed-82ef86781356","doc_no":"A.6.1.1.1.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3486,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.5.2.1.2 - Active Instances Directory](bb23a141-5119-4473-be3a-8f3c2a6f181a),; whereas failed Invocations are Archived in [A.6.1.1.1.2.5.2.1.5 - Hub Data Repository](469f9e75-4ac6-49d4-90d5-b6f3869d1fe8).","contentHash":"099da624c1c1330639dc7fb7f9e0bfb9f5c8f87d67e2995ecca6cd4f6b7ff4b7","addressRefs":[]},"469f9e75-4ac6-49d4-90d5-b6f3869d1fe8":{"id":"469f9e75-4ac6-49d4-90d5-b6f3869d1fe8","doc_no":"A.6.1.1.1.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3487,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"1a8018fb-c663-4e4b-9f4a-f08e1101ffe7":{"id":"1a8018fb-c663-4e4b-9f4a-f08e1101ffe7","doc_no":"A.6.1.1.1.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3488,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"a741a948-18c5-443c-a10e-d66f5f586363":{"id":"a741a948-18c5-443c-a10e-d66f5f586363","doc_no":"A.6.1.1.1.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3489,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"c5ec7cb4-18ed-4551-a1ea-dba32dfc2b80":{"id":"c5ec7cb4-18ed-4551-a1ea-dba32dfc2b80","doc_no":"A.6.1.1.1.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3490,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"97e3a3e5-fa1c-4a33-8bb2-ae706201d1df":{"id":"97e3a3e5-fa1c-4a33-8bb2-ae706201d1df","doc_no":"A.6.1.1.1.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3491,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"c88763c9-f2af-4d4e-81d5-6ea0dfdd05c5":{"id":"c88763c9-f2af-4d4e-81d5-6ea0dfdd05c5","doc_no":"A.6.1.1.1.2.5.2.2.1","title":"Aave Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3492,"content":"The documents herein contain the Instance Configuration Document for the Aave Integration Boost Primitive Instance.","contentHash":"29752634256889dade68fa9d76581f1c9569209ff39e9b5bb98f7bc95d60cd71","addressRefs":[]},"a20ae261-ace1-4a64-b884-46d39d5a0c70":{"id":"a20ae261-ace1-4a64-b884-46d39d5a0c70","doc_no":"A.6.1.1.1.2.5.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3493,"content":"The documents herein define the parameters of the Aave Instance of the Integration Boost Primitive.","contentHash":"94021446ab77590481ae8af1998db6fbed634c453722c9724fe535634b6bf22b","addressRefs":[]},"9508a55a-b9a9-492c-a6c8-c4374865ff24":{"id":"9508a55a-b9a9-492c-a6c8-c4374865ff24","doc_no":"A.6.1.1.1.2.5.2.2.1.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3494,"content":"The partner for the Aave Integration Boost is Aave.","contentHash":"9188f488602523d089ea5271cafda77d77f820dfa39ea6b4a87d1540e61baed8","addressRefs":[]},"5b5f88ff-8125-4103-8d00-2fd71052dabd":{"id":"5b5f88ff-8125-4103-8d00-2fd71052dabd","doc_no":"A.6.1.1.1.2.5.2.2.1.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3495,"content":"The reward address for the Aave Integration Boost is `0xac140648435d03f784879cd789130F22Ef588Fcd` on the Ethereum Mainnet.","contentHash":"22de8989343827ae28b73d467cc7d9a2334eccf9cfb351ddfe1916447c65ae02","addressRefs":["0xac140648435d03f784879cd789130f22ef588fcd"]},"7b41a7ac-e52d-4b5f-abbd-e7d5a9998195":{"id":"7b41a7ac-e52d-4b5f-abbd-e7d5a9998195","doc_no":"A.6.1.1.1.2.5.2.2.1.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3496,"content":"The Aave Integration Boost is on the Ethereum Mainnet.","contentHash":"14dc7c2cfae9a476f52506c1a903d85e611e7efad41ac640653e6cff40a3df83","addressRefs":[]},"a0d627a7-4284-4f2b-a919-5c2bae45a583":{"id":"a0d627a7-4284-4f2b-a919-5c2bae45a583","doc_no":"A.6.1.1.1.2.5.2.2.1.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3497,"content":"The payment cadence for the Aave Integration Boost is weekly.","contentHash":"5bc035191468c719649770ea84bd2aaba0d8db1936df6f78377833e324b7fe36","addressRefs":[]},"6bbd42bc-d487-454a-82f6-9631a0830017":{"id":"6bbd42bc-d487-454a-82f6-9631a0830017","doc_no":"A.6.1.1.1.2.5.2.2.1.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3498,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/incentivized-pools/](https://info-sky.blockanalitica.com/api/v1/incentivized-pools/).","contentHash":"339305c044beccbd3105f2f5089bc68091a1c763a69acbdd943bfe1ddeee6fa4","addressRefs":[]},"0a654b1c-9dfe-4ddb-ab79-c3912d2a24bc":{"id":"0a654b1c-9dfe-4ddb-ab79-c3912d2a24bc","doc_no":"A.6.1.1.1.2.5.2.2.1.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3499,"content":"The Data Submission Responsible Actor is the Core Council Risk Advisor.","contentHash":"2cbca921ff14149c82115c863b485464fa2f513275638558c3d7884fee9c26b1","addressRefs":[]},"41925f82-cd71-4abe-92ea-6ab5f660a23b":{"id":"41925f82-cd71-4abe-92ea-6ab5f660a23b","doc_no":"A.6.1.1.1.2.5.2.2.1.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3500,"content":"The Integration Boost is calculated based on per block values for USDS in Aave and the Sky Savings Rate.","contentHash":"c87e6e01ae5919064484b70da1154aa072b4951e1b22259d9ba787333d3fe68f","addressRefs":[]},"c8b1fc3d-c3fa-4fac-8e2a-9b0cdd65dd35":{"id":"c8b1fc3d-c3fa-4fac-8e2a-9b0cdd65dd35","doc_no":"A.6.1.1.1.2.5.2.2.1.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3501,"content":"The documents herein define the custom parameters of the Aave Instance of the Integration Boost Primitive, if any.","contentHash":"90b95b1b482c3e1e6e638707d395d01eed933d47e6546df3df98fe5936201e8a","addressRefs":[]},"4cb1e983-4eb7-44de-b165-db352e6638c6":{"id":"4cb1e983-4eb7-44de-b165-db352e6638c6","doc_no":"A.6.1.1.1.2.5.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3502,"content":"The documents herein define the process for the ongoing management of the Aave Instance of the Integration Boost Primitive.","contentHash":"b68332f121b75215ad50687d26d6259369762294737efb0f21a584e3fe97f5b8","addressRefs":[]},"57fa2a62-f7d5-4926-b07a-50689a519942":{"id":"57fa2a62-f7d5-4926-b07a-50689a519942","doc_no":"A.6.1.1.1.2.5.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3503,"content":"This document defines the protocol for routine ongoing management of the Aave Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.2.2.4 - Instance Ongoing Management Protocol](805381e5-89e7-4fb9-bda7-a97e84b531ba), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Spark Artifact, a version of the full process definition customized to Spark will be included herein.","contentHash":"444085bcf3d30e72b59ccf0fbd1987dfbebf183b61d65ea1a9e4a245e74259bb","addressRefs":[]},"c93f2fb8-89a5-4f17-8446-ed994a684b5a":{"id":"c93f2fb8-89a5-4f17-8446-ed994a684b5a","doc_no":"A.6.1.1.1.2.5.2.2.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3504,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"b0601983-b6ad-44fb-abda-907a3fe53048":{"id":"b0601983-b6ad-44fb-abda-907a3fe53048","doc_no":"A.6.1.1.1.2.5.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3505,"content":"The documents herein define the protocol for non-routine ongoing management of the Aave Instance of this Integration Boost Primitive.","contentHash":"bd473b19bf9081839dd06a01d22711fcd922de0d2ec1818e2b2fe1648ed19989","addressRefs":[]},"66a730fa-47a9-4e2f-bc32-6f2c2de43b2f":{"id":"66a730fa-47a9-4e2f-bc32-6f2c2de43b2f","doc_no":"A.6.1.1.1.2.5.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3506,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Aave Instance of this Integration Boost Primitive.","contentHash":"843204a9a25176426596d7efd751622a6d4473be5bb566e8d1f8d4328926510e","addressRefs":[]},"00e05f96-a641-4d12-b907-22be1f04d569":{"id":"00e05f96-a641-4d12-b907-22be1f04d569","doc_no":"A.6.1.1.1.2.5.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3507,"content":"The documents herein contain data relevant to the Aave Instance of the Integration Boost Primitive.","contentHash":"7dccf23cf5fd873c9c4b9d32fc4936584a67b15b2465594bfa655856a39e104b","addressRefs":[]},"5a5c988e-6d19-4e82-9b27-ae0c0c02dd53":{"id":"5a5c988e-6d19-4e82-9b27-ae0c0c02dd53","doc_no":"A.6.1.1.1.2.5.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3508,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0628d063-99e1-4b59-a734-d2b07bee828f":{"id":"0628d063-99e1-4b59-a734-d2b07bee828f","doc_no":"A.6.1.1.1.2.5.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3509,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"6e4e9afb-cf23-4098-ae0b-1afcdc03e6c4":{"id":"6e4e9afb-cf23-4098-ae0b-1afcdc03e6c4","doc_no":"A.6.1.1.1.2.5.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3510,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"c3ca980e-56a7-42fc-a3f2-76516fb42088":{"id":"c3ca980e-56a7-42fc-a3f2-76516fb42088","doc_no":"A.6.1.1.1.2.5.2.2.1.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3511,"content":"The Integration Boost payments for the Aave Instance of the Integration Boost Primitive are defined as Active Data.\nThe Integration Boost payments for the Aave Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"28f4008309a00b085368fcfa7db74e297fdbb9494f9b2642cb9a1b936ab5165e","addressRefs":[]},"839e995c-cc05-40a7-ba31-a72bce152328":{"id":"839e995c-cc05-40a7-ba31-a72bce152328","doc_no":"A.6.1.1.1.2.5.2.2.1.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3512,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"d492e503-1776-4956-a1ca-dbf604818400":{"id":"d492e503-1776-4956-a1ca-dbf604818400","doc_no":"A.6.1.1.1.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3513,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"f1427e80-b5a8-488b-b140-1685063efe39":{"id":"f1427e80-b5a8-488b-b140-1685063efe39","doc_no":"A.6.1.1.1.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3514,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.5.2.2 - Active Instances](97e3a3e5-fa1c-4a33-8bb2-ae706201d1df).","contentHash":"7f5cc5c736753876ea33c8fbff5d25e58425b636b482fad3e0db5572f90e10d1","addressRefs":[]},"949247f8-c643-4f52-b0f1-cbf3c731da89":{"id":"949247f8-c643-4f52-b0f1-cbf3c731da89","doc_no":"A.6.1.1.1.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3515,"content":"The documents herein contain all data and specifications for Spark’s Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"553aaa2802401e839ead37332b02f6c75398c31928f4c319ecd8c26bb3610acc","addressRefs":[]},"0e476c6e-9dda-4366-9be6-d877df7356e3":{"id":"0e476c6e-9dda-4366-9be6-d877df7356e3","doc_no":"A.6.1.1.1.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3516,"content":"The documents herein organize all base information relevant to Spark’s usage of the Pioneer Chain Primitive.","contentHash":"f10808e9a8b461a16b181aaafe34633f9ce772c0122e6931f7d2fa9432b97c41","addressRefs":[]},"697097a7-2c53-4e65-9543-4fa26c1f9e67":{"id":"697097a7-2c53-4e65-9543-4fa26c1f9e67","doc_no":"A.6.1.1.1.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3517,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"637d1fb7-4fe0-455b-b8c4-2a309fd01226":{"id":"637d1fb7-4fe0-455b-b8c4-2a309fd01226","doc_no":"A.6.1.1.1.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3518,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"ed49aa25-b5e4-4a44-a897-c93d6764b099":{"id":"ed49aa25-b5e4-4a44-a897-c93d6764b099","doc_no":"A.6.1.1.1.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3519,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"4fed57e7-8850-4577-8138-c83065c337af":{"id":"4fed57e7-8850-4577-8138-c83065c337af","doc_no":"A.6.1.1.1.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3520,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.5.3.1.2 - Active Instances Directory](637d1fb7-4fe0-455b-b8c4-2a309fd01226), whereas failed Invocations are Archived in [A.6.1.1.1.2.5.3.1.5 - Hub Data Repository](f941ecfc-13f1-40d6-b344-3e1d8d3f2321).","contentHash":"db2f4ff72da8a50b4849624bc7be5742eb6fbdf96656a6daec84f1d10de08e98","addressRefs":[]},"f941ecfc-13f1-40d6-b344-3e1d8d3f2321":{"id":"f941ecfc-13f1-40d6-b344-3e1d8d3f2321","doc_no":"A.6.1.1.1.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3521,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e49228b0-520d-4297-8a02-015238563397":{"id":"e49228b0-520d-4297-8a02-015238563397","doc_no":"A.6.1.1.1.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3522,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"bb2ed81d-87e3-4e90-8b83-b0e8b5596ccb":{"id":"bb2ed81d-87e3-4e90-8b83-b0e8b5596ccb","doc_no":"A.6.1.1.1.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3523,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"f08e97af-9f90-4d0f-81b3-3d3bb23f8cbf":{"id":"f08e97af-9f90-4d0f-81b3-3d3bb23f8cbf","doc_no":"A.6.1.1.1.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3524,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"6dea3eb2-2f2d-4172-9026-6fd8f0226b1f":{"id":"6dea3eb2-2f2d-4172-9026-6fd8f0226b1f","doc_no":"A.6.1.1.1.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3525,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"1bd7fe5c-0279-4184-b82e-e58d8f2c850e":{"id":"1bd7fe5c-0279-4184-b82e-e58d8f2c850e","doc_no":"A.6.1.1.1.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3526,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"3065c418-cfc5-4963-96ab-36cddfd66bea":{"id":"3065c418-cfc5-4963-96ab-36cddfd66bea","doc_no":"A.6.1.1.1.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3527,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.5.3.2 - Active Instances](6dea3eb2-2f2d-4172-9026-6fd8f0226b1f).","contentHash":"f975144605163611e4b0c24e6bf9e5039539aa28e484aaf19ff1cd7f712d4424","addressRefs":[]},"683e3f9a-df0d-4bdb-adb4-f86dbc6530c6":{"id":"683e3f9a-df0d-4bdb-adb4-f86dbc6530c6","doc_no":"A.6.1.1.1.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3528,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Spark. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"242e6b1e7311c61923e9e61a17e217f3ae3c3f34d7918d7e04e7795506a9b699","addressRefs":[]},"cd70b9f1-1a59-407c-9945-05e52bf5a3b6":{"id":"cd70b9f1-1a59-407c-9945-05e52bf5a3b6","doc_no":"A.6.1.1.1.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3529,"content":"The documents herein contain all data and specifications for Spark’s Allocation System Primitive Instances. Spark implements the Allocation System Primitive using the Spark Liquidity Layer. Developed prior to the introduction of the Sky Primitives, the Spark Liquidity Layer serves as the prototype for all Prime Agents’ Allocation Systems.","contentHash":"5628f31a0aa014d23fc39477b318044cd2c73cfc630d55fd1246a6f190bc0242","addressRefs":[]},"845ef31b-7b6e-4407-87ad-a5a4c8bce049":{"id":"845ef31b-7b6e-4407-87ad-a5a4c8bce049","doc_no":"A.6.1.1.1.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3530,"content":"The documents herein organize all base information relevant to Spark’s usage of the Spark Liquidity Layer.","contentHash":"69e75ccfabebb0921acee4f59c2c8a8d76d831b48e9868c7ed47505a3a38fffa","addressRefs":[]},"f7a32d78-dabc-406e-a822-0a337a03b3e2":{"id":"f7a32d78-dabc-406e-a822-0a337a03b3e2","doc_no":"A.6.1.1.1.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3531,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"20e0bc23-8a73-4ea3-b626-56f6286aded9":{"id":"20e0bc23-8a73-4ea3-b626-56f6286aded9","doc_no":"A.6.1.1.1.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3532,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"e52dc682-bdab-4c3e-ae43-81666ff518e6":{"id":"e52dc682-bdab-4c3e-ae43-81666ff518e6","doc_no":"A.6.1.1.1.2.6.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3533,"content":"The documents herein contain a Directory of all Instances on the Ethereum Mainnet of the Allocation System Primitive with Instance status of `Active`.","contentHash":"886bcf6fa542b5a20f09fe633a92b366fc593e9f17a10e8d06664ee1c2c5ec4a","addressRefs":[]},"c4a1d0ca-0794-4ad0-9920-7f8a837b6bfa":{"id":"c4a1d0ca-0794-4ad0-9920-7f8a837b6bfa","doc_no":"A.6.1.1.1.2.6.1.1.2.1.1","title":"SparkLend","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3534,"content":"The Ethereum Mainnet Instances Directory of the SparkLend Protocol with `Active` Status are stored herein.","contentHash":"322e90aa777f7a5ca5264c36965ffb77a3ddea65f47620538d58afa96ded6a19","addressRefs":[]},"fcb18db8-8a6a-4dfb-bfc9-f4b6e5f5a53a":{"id":"fcb18db8-8a6a-4dfb-bfc9-f4b6e5f5a53a","doc_no":"A.6.1.1.1.2.6.1.1.2.1.1.1","title":"Ethereum Mainnet - SparkLend USDS Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3535,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.1.1 - Ethereum Mainnet - SparkLend USDS Instance Configuration Document](4940f6ee-28e8-47a8-a7df-f2b30bd7dcc2).","contentHash":"94b8fb7275dbac24c2ea070e1cbc2d388a1358b98982d4914927b5029f8d8020","addressRefs":[]},"c4d4ae3a-f133-41e2-a5e6-1ed61b8d273a":{"id":"c4d4ae3a-f133-41e2-a5e6-1ed61b8d273a","doc_no":"A.6.1.1.1.2.6.1.1.2.1.1.2","title":"Ethereum Mainnet - SparkLend USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3536,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.1.2 - Ethereum Mainnet - SparkLend USDC Instance Configuration Document](7cd0ec35-9449-48ce-a764-454ed33e72de).","contentHash":"b219fedbe1db9d1a2fe612b967b89acf3136ca6fcae41d93bfc3a883ec1fc167","addressRefs":[]},"b274ae84-b301-4935-b5d5-c3832d61f1b6":{"id":"b274ae84-b301-4935-b5d5-c3832d61f1b6","doc_no":"A.6.1.1.1.2.6.1.1.2.1.1.3","title":"Ethereum Mainnet - SparkLend Dai Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3537,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.1.3 - Ethereum Mainnet - SparkLend Dai Instance Configuration Document](7e8135d5-7b45-48a7-bf9a-881f0bbf115c).","contentHash":"2d2a6edd10cbe95f6ad56f36b27f5902fba8c1522e6d76bca38784b136a7bed2","addressRefs":[]},"2e0c5808-290a-4a39-ad87-ee4f7a7e457b":{"id":"2e0c5808-290a-4a39-ad87-ee4f7a7e457b","doc_no":"A.6.1.1.1.2.6.1.1.2.1.1.4","title":"Ethereum Mainnet - SparkLend USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3538,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.1.4 - Ethereum Mainnet - SparkLend USDT Instance Configuration Document](dbd8d0fc-d055-415c-a7ef-4796c5e33a87).","contentHash":"d6ca37f9b5222517e308c6b1b78918a895448debc70b843bfd727711657a49a3","addressRefs":[]},"a98d046d-1cac-4987-a750-9b94137f7c91":{"id":"a98d046d-1cac-4987-a750-9b94137f7c91","doc_no":"A.6.1.1.1.2.6.1.1.2.1.1.5","title":"Ethereum Mainnet - SparkLend pyUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3539,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.1.5 - Ethereum Mainnet - SparkLend pyUSD Instance Configuration Document](84a0c43e-b64b-4018-bb2c-3d5c5a635c03).","contentHash":"4f4fedc5f83e00b953a2f72878266c4cb68ad1f49ca556cc8281fedf37769aa4","addressRefs":[]},"baa53679-f8ba-4e8c-99dd-668638dd94b7":{"id":"baa53679-f8ba-4e8c-99dd-668638dd94b7","doc_no":"A.6.1.1.1.2.6.1.1.2.1.1.6","title":"Ethereum Mainnet - SparkLend ETH Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3540,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.1.6 - Ethereum Mainnet - SparkLend ETH Instance Configuration Document](1eb4affe-3116-4d17-a3c1-0a06b6ac618b).","contentHash":"a614367b391cd1611022af7a8b10c06d03e18f9e581864a04deb37be8b14d8f8","addressRefs":[]},"b9745e5e-26bf-4abe-bff1-f3fdcfa93aca":{"id":"b9745e5e-26bf-4abe-bff1-f3fdcfa93aca","doc_no":"A.6.1.1.1.2.6.1.1.2.1.2","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3541,"content":"The Ethereum Mainnet Instances Directory of the Aave Protocol with `Active` Status are stored herein.","contentHash":"b2ae795e6fd7562128444dde233fcdbc8a91447b067dd41d7d29e277e79228eb","addressRefs":[]},"a1e31eab-caa2-4e20-8f55-49a23c5ce6e8":{"id":"a1e31eab-caa2-4e20-8f55-49a23c5ce6e8","doc_no":"A.6.1.1.1.2.6.1.1.2.1.2.1","title":"Ethereum Mainnet - Aave Prime USDS Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3542,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.2.1 - Ethereum Mainnet - Aave Prime USDS Instance Configuration Document](bf8743ff-bd2e-4fb4-9b2f-2989f0361697).","contentHash":"1996afb2e5d734ed6502d32dd1a53edb8ecd3e74fcba1d5422b906799b9136de","addressRefs":[]},"7b690555-9610-4a34-ba8f-90527894526a":{"id":"7b690555-9610-4a34-ba8f-90527894526a","doc_no":"A.6.1.1.1.2.6.1.1.2.1.2.2","title":"Ethereum Mainnet - Aave Core USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3543,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.2.2 - Ethereum Mainnet - Aave Core USDC Instance Configuration Document](bba861d8-9307-4e7f-ac54-f636232baff1).","contentHash":"44f2292cbf1f1b75449cdb22bbe6bd848d9a4bef6cf5f4a8e4645877f1e22a59","addressRefs":[]},"fa291f5f-45bf-4798-b19f-90d5ab3ad593":{"id":"fa291f5f-45bf-4798-b19f-90d5ab3ad593","doc_no":"A.6.1.1.1.2.6.1.1.2.1.2.3","title":"Ethereum Mainnet - Aave Core USDS Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3544,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.2.3 - Ethereum Mainnet - Aave Core USDS Instance Configuration Document](1191f33a-dc78-4c2f-bc5e-e85802471c60).","contentHash":"9b1fa6730ccb12a9d796602c770096d12888d26a618ddc84606100046d169faa","addressRefs":[]},"628a294b-ece9-4446-81db-e25c56ed02e4":{"id":"628a294b-ece9-4446-81db-e25c56ed02e4","doc_no":"A.6.1.1.1.2.6.1.1.2.1.2.4","title":"Ethereum Mainnet - Aave Core USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3545,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.2.4 - Ethereum Mainnet - Aave Core USDT Instance Configuration Document](c8bcfd26-cab2-43f6-9c35-ad13571fcf1e).","contentHash":"e8d70f74a7e50bf0acd4c57e199862f3808efc4a2c1f1121daf8eda7fc69ed68","addressRefs":[]},"afea3002-f7b8-442e-a4f0-90bfd6c676f3":{"id":"afea3002-f7b8-442e-a4f0-90bfd6c676f3","doc_no":"A.6.1.1.1.2.6.1.1.2.1.2.5","title":"Ethereum Mainnet - Aave USDe Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3546,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.2.5 - Ethereum Mainnet - Aave USDe Instance Configuration Document](8bd798af-96fc-4fc4-9fb7-5b351740a962).","contentHash":"9af763b6f000903cd6d13f92338b53ddec3038ab46a35c7aab87f7d2cc96bdff","addressRefs":[]},"907ddd8e-0c22-4232-92d1-00144443c4fc":{"id":"907ddd8e-0c22-4232-92d1-00144443c4fc","doc_no":"A.6.1.1.1.2.6.1.1.2.1.3","title":"Maple","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3547,"content":"The Ethereum Mainnet Instances Directory of the Maple Protocol with `Active` Status are stored herein.","contentHash":"23d31010d23f63ecd6441f2d5871677626acdbf4cc73a664c3cb7e7130524d34","addressRefs":[]},"12e43339-6c32-47ab-a2ec-43bb38f4f737":{"id":"12e43339-6c32-47ab-a2ec-43bb38f4f737","doc_no":"A.6.1.1.1.2.6.1.1.2.1.3.1","title":"Ethereum Mainnet - Maple USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3548,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.3.1 - Ethereum Mainnet - Maple USDC Instance Configuration Document](06a83573-f319-4a56-a2bd-4389086dd2bf).","contentHash":"9c556096aea05915c6b7c0d270d2e512044b249d0eaee91f3a086aa8648f1116","addressRefs":[]},"46c72ef7-97f6-42c0-9d87-f28cff62bc97":{"id":"46c72ef7-97f6-42c0-9d87-f28cff62bc97","doc_no":"A.6.1.1.1.2.6.1.1.2.1.3.2","title":"Ethereum Mainnet - Maple USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3549,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.3.2 - Ethereum Mainnet - Maple USDT Instance Configuration Document](5302863d-f777-461e-8238-2178fc9899c4).","contentHash":"c02d441140498fc4f78c3540201f8565abb3acc7b4ceccf66f2e410390b23aba","addressRefs":[]},"83f266b4-9b3b-44a2-a547-faa8c29a8833":{"id":"83f266b4-9b3b-44a2-a547-faa8c29a8833","doc_no":"A.6.1.1.1.2.6.1.1.2.1.4","title":"Ethena","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3550,"content":"The Ethereum Mainnet Instances Directory of the Ethena Protocol with `Active` Status are stored herein.","contentHash":"b0fd85f1061c67de4e42dd0262f4195e686077c304093d2e2eb077ff127143f8","addressRefs":[]},"b2bc23a2-2870-47ce-b32a-7b360b902782":{"id":"b2bc23a2-2870-47ce-b32a-7b360b902782","doc_no":"A.6.1.1.1.2.6.1.1.2.1.4.1","title":"Ethereum Mainnet - Ethena USDe Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3551,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.4.1 - Ethereum Mainnet - Ethena USDe Instance Configuration Document](6be3e516-5374-41a0-8566-1c50656af772).","contentHash":"ae8e66f50fa967c1b65aefb6f7023f10d7d0df2720a47f18bc37672f346f8b57","addressRefs":[]},"822350a5-27e8-4cb9-80c5-9fca9e84cb49":{"id":"822350a5-27e8-4cb9-80c5-9fca9e84cb49","doc_no":"A.6.1.1.1.2.6.1.1.2.1.4.2","title":"Ethereum Mainnet - Ethena sUSDe Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3552,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.4.2 - Ethereum Mainnet - Ethena sUSDe Instance Configuration Document](1903250a-4499-4ce4-bdcb-5835102a6553).","contentHash":"413064724e0e602f1a3d14b88dfd55a4abef84094563706acbefdd8f81824d05","addressRefs":[]},"c5e6035f-2712-4e64-a913-124b779605a4":{"id":"c5e6035f-2712-4e64-a913-124b779605a4","doc_no":"A.6.1.1.1.2.6.1.1.2.1.5","title":"Fluid","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3553,"content":"The Ethereum Mainnet Instances Directory of the Fluid Protocol with `Active` Status are stored herein.","contentHash":"e0d45b8d76ad46cd9df7c6e48e2b1bb83a9afc930e7d48e283076c487d8eacbd","addressRefs":[]},"2121074b-2a51-4330-952a-c05b628947cf":{"id":"2121074b-2a51-4330-952a-c05b628947cf","doc_no":"A.6.1.1.1.2.6.1.1.2.1.5.1","title":"Ethereum Mainnet - Fluid sUSDS ERC4626 Vault Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3554,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.5.1 - Ethereum Mainnet - Fluid sUSDS ERC4626 Vault Instance Configuration Document](8da18a0c-2d5a-4895-ac53-804578b00a5b).","contentHash":"7d1e9a847d8f19da30cf5b58c1ffce39ff01f663cc2eb221ee5d0f5b9a43a9db","addressRefs":[]},"e502e83d-467d-4b58-a4bd-292a3985c7ff":{"id":"e502e83d-467d-4b58-a4bd-292a3985c7ff","doc_no":"A.6.1.1.1.2.6.1.1.2.1.6","title":"Superstate","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3555,"content":"The Ethereum Mainnet Instances Directory of the Superstate Protocol with `Active` Status are stored herein.","contentHash":"4df0121f1ea57d4f4b7f6e9b6f4c4775a8d8fd118866d84397b8912c1468c4b9","addressRefs":[]},"aed21e59-19b9-4b11-ac3f-55bb5a387772":{"id":"aed21e59-19b9-4b11-ac3f-55bb5a387772","doc_no":"A.6.1.1.1.2.6.1.1.2.1.6.1","title":"Ethereum Mainnet - Superstate USTB Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3556,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.6.1 - Ethereum Mainnet - Superstate USTB Instance Configuration Document](4ad2419c-7966-42de-bc2a-d8ca8ce61b90).","contentHash":"2735c96afc0376b3a4a844200b9e40403fc6a374472306a079aa8d7a49561b29","addressRefs":[]},"d9cf6d6b-74a3-4bb6-b931-bfa3b5b8f70e":{"id":"d9cf6d6b-74a3-4bb6-b931-bfa3b5b8f70e","doc_no":"A.6.1.1.1.2.6.1.1.2.1.7","title":"Curve","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3557,"content":"The Ethereum Mainnet Instances Directory of the Curve Protocol with `Active` Status are stored herein.","contentHash":"e1a668176ab5e2b5a4874a9df8fbf4531edc87b29365354a999aaf4b76113b09","addressRefs":[]},"af6a87f7-9b67-4f30-a345-f0c46f97c039":{"id":"af6a87f7-9b67-4f30-a345-f0c46f97c039","doc_no":"A.6.1.1.1.2.6.1.1.2.1.7.1","title":"Ethereum Mainnet - Curve sUSDS/USDT Pool Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3558,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.7.1 - Ethereum Mainnet - Curve sUSDS/USDT Pool Instance Configuration Document](4e840dad-944c-4c45-9c5e-277dcb1830a8).","contentHash":"4b604e63e82a39ddca8de31d4e9036df5254758b5f416a5d168ae310eb962123","addressRefs":[]},"dbbac28b-8627-462f-9326-f50bfdb50867":{"id":"dbbac28b-8627-462f-9326-f50bfdb50867","doc_no":"A.6.1.1.1.2.6.1.1.2.1.7.2","title":"Ethereum Mainnet - Curve USDC/USDT Pool Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3559,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.7.2 - Ethereum Mainnet - Curve USDC/USDT Pool Instance Configuration Document](30d359a0-287b-4b3b-93fd-4e70bf0b19a7).","contentHash":"53f4ef416c499078571c34407ac6e22e73d5a81fc7179dc69becd0d742210d63","addressRefs":[]},"7fe97dfc-8126-4c33-bc3d-74b7e1a1a88f":{"id":"7fe97dfc-8126-4c33-bc3d-74b7e1a1a88f","doc_no":"A.6.1.1.1.2.6.1.1.2.1.7.3","title":"Ethereum Mainnet - Curve pyUSD/USDC Pool Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3560,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.7.3 - Ethereum Mainnet - Curve pyUSD/USDC Pool Instance Configuration Document](e1fdaf49-0b32-4644-b021-9cae6e270c7a).","contentHash":"e31033f22dea255654fee23ca916af531696a879a70bb20f42ce50d6a0353899","addressRefs":[]},"881d31bd-e24b-45f7-9f8a-fa18b8effc8d":{"id":"881d31bd-e24b-45f7-9f8a-fa18b8effc8d","doc_no":"A.6.1.1.1.2.6.1.1.2.1.7.4","title":"Ethereum Mainnet - Curve pyUSD/USDS Pool Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3561,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.7.4 - Ethereum Mainnet - Curve pyUSD/USDS Pool Instance Configuration Document](7635eff1-1fa0-4356-8953-2564a7f0693c).","contentHash":"b4a545166d07995a13a64362e2cfbf0850023a30b8fc139d70d282b2e6adcbf2","addressRefs":[]},"350d7312-0a09-43cd-bd31-265fda5a14a1":{"id":"350d7312-0a09-43cd-bd31-265fda5a14a1","doc_no":"A.6.1.1.1.2.6.1.1.2.1.8","title":"Morpho","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3562,"content":"The Ethereum Mainnet Instances Directory of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"416cd4540aa798f84e3260980cd196fcbc9fcc59fb1cde760d6f95c03ba7fcc1","addressRefs":[]},"3e92042e-1756-4c8f-a31d-6052176e87e5":{"id":"3e92042e-1756-4c8f-a31d-6052176e87e5","doc_no":"A.6.1.1.1.2.6.1.1.2.1.8.1","title":"Ethereum Mainnet - Morpho Dai Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3563,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.8.1 - Ethereum Mainnet - Morpho Dai Instance Configuration Document](626dd4bf-108b-48bd-a1e1-c26d290c3a72).","contentHash":"b4a8138e1a51ecade76d64554fbef58ecc11eefce633d6fd29ea6deb978ba86f","addressRefs":[]},"79a60537-e5b6-4701-bde6-a98b33bca461":{"id":"79a60537-e5b6-4701-bde6-a98b33bca461","doc_no":"A.6.1.1.1.2.6.1.1.2.1.8.2","title":"Ethereum Mainnet - Morpho USDS Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3564,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.8.2 - Ethereum Mainnet - Morpho USDS Instance Configuration Document](138be894-8a4a-4e8c-9fdd-0f8183935d24).","contentHash":"cc73a74c138c94daa5cb2140e505e5e4cf5d325376587396a60b49967691509a","addressRefs":[]},"3adb6bf9-e0f8-4583-996b-152bcdc1d51d":{"id":"3adb6bf9-e0f8-4583-996b-152bcdc1d51d","doc_no":"A.6.1.1.1.2.6.1.1.2.1.8.3","title":"Ethereum Mainnet - Morpho USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3565,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.8.3 - Ethereum Mainnet - Morpho USDC Instance Configuration Document](f3063596-4f85-4a51-b52c-58221d043d3e).","contentHash":"12dc7235d27a15f6d50dea628e4528ea46cf64b714136278a0e34692fad02edc","addressRefs":[]},"5b70027d-bea1-4899-946f-6a2094a8ca55":{"id":"5b70027d-bea1-4899-946f-6a2094a8ca55","doc_no":"A.6.1.1.1.2.6.1.1.2.1.8.4","title":"Ethereum Mainnet - Morpho USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3566,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.8.4 - Ethereum Mainnet - Morpho USDT Instance Configuration Document](a2f66f86-ddea-4260-820a-cde66a861413).","contentHash":"13174593311346c0ea740e5a9c27fb79da05a6a95e09a85637da2b81e2aeb600","addressRefs":[]},"e59ca947-aa8d-4ab7-84b1-78422348a2d5":{"id":"e59ca947-aa8d-4ab7-84b1-78422348a2d5","doc_no":"A.6.1.1.1.2.6.1.1.2.1.9","title":"Spark Savings V2","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3567,"content":"The Ethereum Mainnet Instances Directory of the Spark Savings v2 with `Active` Status are stored herein.","contentHash":"edec11d1ee062ca76684d5df3d51cc97da582d2ccf67ce80ef26b562d84aec27","addressRefs":[]},"2358e292-c9d1-4c23-9ef2-bb4a48304968":{"id":"2358e292-c9d1-4c23-9ef2-bb4a48304968","doc_no":"A.6.1.1.1.2.6.1.1.2.1.9.1","title":"Ethereum Mainnet - Spark Savings v2 ETH Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3568,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.9.1 - Ethereum Mainnet - Spark Savings v2 ETH Instance Configuration Document](831b4fd8-06c6-4734-bb3a-93678082d8cc).","contentHash":"52cb6578183c486cef663e2a4d20bd2726284316d532dc748903c74fa064102f","addressRefs":[]},"de15c2bf-cb03-45cc-9ee2-4acd1695ebc2":{"id":"de15c2bf-cb03-45cc-9ee2-4acd1695ebc2","doc_no":"A.6.1.1.1.2.6.1.1.2.1.9.2","title":"Ethereum Mainnet - Spark Savings v2 USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3569,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.9.2 - Ethereum Mainnet - Spark Savings v2 USDC Instance Configuration Document](eeb34a6e-e377-4115-92f9-d299f6d2a5d9).","contentHash":"3a3a2d15f516b561f77a9692748cbcc1ae19a904783801df7d22189631e774f9","addressRefs":[]},"113bbaa4-ac97-4ba7-9f31-20b8102b7a1a":{"id":"113bbaa4-ac97-4ba7-9f31-20b8102b7a1a","doc_no":"A.6.1.1.1.2.6.1.1.2.1.9.3","title":"Ethereum Mainnet - Spark Savings v2 USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3570,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.9.3 - Ethereum Mainnet - Spark Savings v2 USDT Instance Configuration Document](0cc91e92-4523-4d3b-87a5-bb9a695d696c).","contentHash":"b6ea98d22fa769dfa0b327a2ee2a1a167778339efde54952db0562aab5a1dba6","addressRefs":[]},"3dabe1bb-244d-4546-993a-449b988d9199":{"id":"3dabe1bb-244d-4546-993a-449b988d9199","doc_no":"A.6.1.1.1.2.6.1.1.2.1.9.4","title":"Ethereum Mainnet - Spark Savings v2 PYUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3571,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.9.4 - Ethereum Mainnet - Spark Savings v2 spPYUSD Instance Configuration Document](0b280652-ea99-4a53-8c9e-fb23b200d446).","contentHash":"0f34f8dbc3d3352c628a549a2003c642e7db98e6e9ee4cdd8e8a0ef5f50d877b","addressRefs":[]},"8e76f6f2-fb70-4ed0-a78d-7be94244819b":{"id":"8e76f6f2-fb70-4ed0-a78d-7be94244819b","doc_no":"A.6.1.1.1.2.6.1.1.2.1.10","title":"Arkis","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3572,"content":"The Ethereum Instances Directory of the Arkis Protocol with `Active` Status are stored herein.","contentHash":"5d1f8df707ab5441ae75f9b8d687d2ffd8bdd8e1d1ce87691911c79004228526","addressRefs":[]},"a25915c0-0fc4-48f7-845b-92f446dbbba3":{"id":"a25915c0-0fc4-48f7-845b-92f446dbbba3","doc_no":"A.6.1.1.1.2.6.1.1.2.1.10.1","title":"Ethereum Mainnet - Arkis Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3573,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.10.1 - Ethereum Mainnet - Arkis Instance Configuration Document](4bb58af1-fc25-442f-83a9-dd40989a7d37).","contentHash":"1c67ea735b83351990e5ef4b48273c675e78b958a5876397c3cfe6a2a5950014","addressRefs":[]},"4ef25928-26c1-4864-9670-88c5d676b8e4":{"id":"4ef25928-26c1-4864-9670-88c5d676b8e4","doc_no":"A.6.1.1.1.2.6.1.1.2.1.11","title":"Uniswap v4","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3574,"content":"The Ethereum Mainnet Instances Directory of the Uniswap v4 with `Active` Status are stored herein.","contentHash":"c2453d784865fa199e63a42b69ab77b167dd84e7b21074edd4d9feee089558ca","addressRefs":[]},"5e1d4f42-84aa-4907-ad6f-eb62b26d28e3":{"id":"5e1d4f42-84aa-4907-ad6f-eb62b26d28e3","doc_no":"A.6.1.1.1.2.6.1.1.2.1.11.1","title":"Ethereum Mainnet - Uniswap v4 PYUSD/USDS Pool Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3575,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.11.1 - Ethereum Mainnet - Uniswap v4 PYUSD/USDS Pool Instance Configuration Document](c5d16727-69f7-454a-a3da-85c46dd9eed2).","contentHash":"dba7663645440af0f28eb9f40fcdef82e890b7477734ca5526d83e4a79049cf1","addressRefs":[]},"55e7dee1-dab9-4bc6-b8db-9aa8191597a1":{"id":"55e7dee1-dab9-4bc6-b8db-9aa8191597a1","doc_no":"A.6.1.1.1.2.6.1.1.2.1.11.2","title":"Ethereum Mainnet - Uniswap v4 USDT/USDS Pool Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3576,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.11.2 - Ethereum Mainnet - Uniswap v4 USDT/USDS Pool Instance Configuration Document](3c4cfb29-1579-4abe-a17b-5b5574972b73).","contentHash":"88346e3953ddab756748df4c395ca98fcf7e898644b4e0e8789a1d62612c76d7","addressRefs":[]},"c6e67244-8bdc-487a-b5bf-61025f623d22":{"id":"c6e67244-8bdc-487a-b5bf-61025f623d22","doc_no":"A.6.1.1.1.2.6.1.1.2.1.12","title":"Paxos","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3577,"content":"The Ethereum Mainnet Instances Directory of Paxos with `Active` Status are stored herein.","contentHash":"53a846e05e862f2f1d1dbdb56a62fecf088d7294891d275141f914413d36d830","addressRefs":[]},"65702dc0-78d3-4d0e-84bc-0d642fb42e73":{"id":"65702dc0-78d3-4d0e-84bc-0d642fb42e73","doc_no":"A.6.1.1.1.2.6.1.1.2.1.12.1","title":"Ethereum Mainnet - Paxos Transfer USDC to Paxos (receive PYUSD) Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3578,"content":"This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Transfer USDC to Paxos (receive PYUSD) Instance Configuration Document - A.6.1.1.1.2.6.1.3.1.12.1](efc57615-b3ac-4122-8fd3-6a8d68ce71a1).","contentHash":"504e2a3d796d7ea9d2613c4b1bae99fd21fe359419d9f4b02125c987dc1f1794","addressRefs":[]},"0a76cc35-3c37-421f-b123-e325cb581189":{"id":"0a76cc35-3c37-421f-b123-e325cb581189","doc_no":"A.6.1.1.1.2.6.1.1.2.1.12.2","title":"Ethereum Mainnet - Paxos Transfer PYUSD to Paxos (receive USDC) Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3579,"content":"This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Transfer PYUSD to Paxos (receive USDC) Instance Configuration Document - A.6.1.1.1.2.6.1.3.1.12.2](28544284-0ee1-49da-a27f-b13dba9b5842).","contentHash":"b546a8d2a80ddf383405097cc4828efd96d60c48fcbcc84a8973c4534f083d83","addressRefs":[]},"5fdf2214-5345-4ca2-9fd6-b71981a438d9":{"id":"5fdf2214-5345-4ca2-9fd6-b71981a438d9","doc_no":"A.6.1.1.1.2.6.1.1.2.1.12.3","title":"Ethereum Mainnet - Paxos Transfer PYUSD to Paxos (receive USDG) Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3580,"content":"This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Transfer PYUSD to Paxos (receive USDG) Instance Configuration Document - A.6.1.1.1.2.6.1.3.1.12.3](f6b739d1-c637-48f8-abf7-8c8f173bb392).","contentHash":"b0f4c99adebffe395bf47c9843ac0a7c13477d6081ba4ca9d518440174d1b6bf","addressRefs":[]},"60055026-14c1-41ab-99ba-be28acbb4c1c":{"id":"60055026-14c1-41ab-99ba-be28acbb4c1c","doc_no":"A.6.1.1.1.2.6.1.1.2.1.12.4","title":"Ethereum Mainnet - Paxos Transfer USDG to Paxos (receive PYUSD) Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3581,"content":"This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Transfer USDG to Paxos (receive PYUSD) Instance Configuration Document - A.6.1.1.1.2.6.1.3.1.12.4](bef47e5b-5568-4df4-9294-2eb108a006c6).","contentHash":"9c8bcd57c8d1f45f8acbeade2096804979e84517a9fa3386921acabe2f239de4","addressRefs":[]},"3e5b044d-1aeb-4664-bfb3-16fa613e0df7":{"id":"3e5b044d-1aeb-4664-bfb3-16fa613e0df7","doc_no":"A.6.1.1.1.2.6.1.1.2.1.13","title":"Anchorage","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3582,"content":"The Ethereum Mainnet Instances Directory of Anchorage with `Active` Status are stored herein.","contentHash":"e22813fa739b2ba35e7625a267aaef643d6711fcb8bef080e82a85016fb759cd","addressRefs":[]},"0793bcc1-4b69-437d-bbf3-38e1ac6d29b6":{"id":"0793bcc1-4b69-437d-bbf3-38e1ac6d29b6","doc_no":"A.6.1.1.1.2.6.1.1.2.1.13.1","title":"Ethereum Mainnet - Anchorage USAT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3583,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.13.1 - Ethereum Mainnet - Anchorage USAT Instance Configuration Document](8048e396-7bb4-4541-a68f-6dd7ec0a6015).","contentHash":"0f9bef7016a0fb991c7c705269b8ed94818b7f1eedaec5641626ea3580e76020","addressRefs":[]},"905c5726-8d51-4bf3-80c7-2b4f48bf66cd":{"id":"905c5726-8d51-4bf3-80c7-2b4f48bf66cd","doc_no":"A.6.1.1.1.2.6.1.1.2.1.13.2","title":"Ethereum Mainnet - Anchorage USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3584,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.1.13.2 - Ethereum Mainnet - Anchorage USDT Instance Configuration Document](4eee15e5-46e2-4438-8299-6c85c46bb85b).","contentHash":"bb0fe27295153eb212b3fb6a11c62a74ff892c781c1b6f3ba54ee03637c59605","addressRefs":[]},"305a6351-bb16-4e4d-8912-7ef1c3ff26bb":{"id":"305a6351-bb16-4e4d-8912-7ef1c3ff26bb","doc_no":"A.6.1.1.1.2.6.1.1.2.2","title":"Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3585,"content":"The documents herein contain a Directory of all Instances on Base of the Allocation System Primitive with Instance status of `Active`.","contentHash":"363e1e58ddee16c81293bb03988fcc80ea62b287ebe038b93144629bbd81d2c5","addressRefs":[]},"368907a1-0c9f-43b9-98dc-8132ef38b450":{"id":"368907a1-0c9f-43b9-98dc-8132ef38b450","doc_no":"A.6.1.1.1.2.6.1.1.2.2.1","title":"Morpho","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3586,"content":"The Base Instances Directory of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"d86ac0eac7329098e5d8c01763d9e21541ae13693e422c974e667216751d8a27","addressRefs":[]},"dbd3aa7c-2a3d-4a2e-be5d-5d25a5d9dd8e":{"id":"dbd3aa7c-2a3d-4a2e-be5d-5d25a5d9dd8e","doc_no":"A.6.1.1.1.2.6.1.1.2.2.1.1","title":"Base - Morpho Blue USDC ERC4626 Vault Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3587,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.2.1.1 - Base - Morpho Blue USDC ERC4626 Vault Instance Configuration Document](97c54a67-ff3d-40c3-a702-f632f2b81f2d).","contentHash":"668f739f579b2898bef0dce68501360c56c198bb6467e57a25ef92f2c961d39b","addressRefs":[]},"aaabd71c-637f-4680-841f-6a00db261095":{"id":"aaabd71c-637f-4680-841f-6a00db261095","doc_no":"A.6.1.1.1.2.6.1.1.2.2.2","title":"Fluid","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3588,"content":"The Base Instances Directory of the Fluid Protocol with `Active` Status are stored herein.","contentHash":"aba07bb0cd2f403fd486b42377627cc60ac4624945256e7d09264bda3b3c9f30","addressRefs":[]},"cb87926d-f011-47ff-a0ab-81a057016ed6":{"id":"cb87926d-f011-47ff-a0ab-81a057016ed6","doc_no":"A.6.1.1.1.2.6.1.1.2.2.2.1","title":"Base - Fluid sUSDS ERC4626 Vault Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3589,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.2.2.1 - Base Mainnet - Fluid sUSDS ERC4626 Vault Instance Configuration Document](b955e881-1ad7-479f-9858-efebe8e23bdc).","contentHash":"ff7ae3e9d53e7602c9c438d9b5d829f9ff6e81fa16e36c56d1159d7b8cb95518","addressRefs":[]},"51cc6fa3-1e1a-4f07-bbad-c54ba6645e71":{"id":"51cc6fa3-1e1a-4f07-bbad-c54ba6645e71","doc_no":"A.6.1.1.1.2.6.1.1.2.2.3","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3590,"content":"The Base Instances Directory of the Aave Protocol with `Active` Status are stored herein.","contentHash":"370c535f50fd82ba637c3ade7bd87c1f55e782a84025a44a1709bae7f6c9faa1","addressRefs":[]},"a61290d6-caae-4cb2-a2bc-8fc99ec2d7e6":{"id":"a61290d6-caae-4cb2-a2bc-8fc99ec2d7e6","doc_no":"A.6.1.1.1.2.6.1.1.2.2.3.1","title":"Base - Aave USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3591,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.2.3.1 - Base - Aave USDC Instance Configuration Document](adfe1844-38ae-4eac-9060-f79978751765).","contentHash":"79fefa9527140f13fa9c005ed82af1926268f0b14c63e9cb42539cd99ee24f49","addressRefs":[]},"9e3cf2d4-99b5-4b25-a552-1eb8becef4ae":{"id":"9e3cf2d4-99b5-4b25-a552-1eb8becef4ae","doc_no":"A.6.1.1.1.2.6.1.1.2.3","title":"Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3592,"content":"The documents herein contain a Directory of all Instances on Arbitrum of the Allocation System Primitive with Instance status of `Active`.","contentHash":"52964ad7c99f2089aa4934657c5d7d655209e9bea2ea068581ef0b16305abef8","addressRefs":[]},"78bfa934-14f8-45eb-aec1-945d4e262dd7":{"id":"78bfa934-14f8-45eb-aec1-945d4e262dd7","doc_no":"A.6.1.1.1.2.6.1.1.2.3.1","title":"Fluid","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3593,"content":"The Arbitrum Instances Directory of the Fluid Protocol with `Active` Status are stored herein.","contentHash":"3864294adbaf168f68e1933885c108afbf1da91d933f84d7a629b3e571a917cc","addressRefs":[]},"e49ce8a1-1e28-4fcf-a991-589d604fb12e":{"id":"e49ce8a1-1e28-4fcf-a991-589d604fb12e","doc_no":"A.6.1.1.1.2.6.1.1.2.3.1.1","title":"Arbitrum - Fluid sUSDS ERC4626 Vault Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3594,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.3.1.1 - Arbitrum - Fluid sUSDS ERC4626 Vault Instance Configuration Document](e6a55c76-91f7-4503-9349-b082c762ec76).","contentHash":"06dfe45d544d0f6650de86431c92acad54d0b664a90cd0ea75d3c3837667cdf3","addressRefs":[]},"7e0e5a2d-0dd8-4184-9eea-c8ef4284cbcb":{"id":"7e0e5a2d-0dd8-4184-9eea-c8ef4284cbcb","doc_no":"A.6.1.1.1.2.6.1.1.2.3.2","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3595,"content":"The Arbitrum Instances Directory of the Aave Protocol with `Active` Status are stored herein.","contentHash":"50de823e955d193c95fd09e9c716e4685c9a4365eadc6f91e996eccebaade592","addressRefs":[]},"6a9a6b83-5337-4f61-b01c-757809bd90b9":{"id":"6a9a6b83-5337-4f61-b01c-757809bd90b9","doc_no":"A.6.1.1.1.2.6.1.1.2.3.2.1","title":"Arbitrum - Aave USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3596,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.3.2.1 - Arbitrum - Aave USDC Instance Configuration Document](e11091aa-e569-4ca9-9151-dc5e1a8e1062).","contentHash":"75c260afb8fe41f7bcdd9b974f86be86f05b9578df90ba0d5c3cc0ccb6a59d4a","addressRefs":[]},"4f0c9316-383c-464f-8266-d6c7a6f5ef08":{"id":"4f0c9316-383c-464f-8266-d6c7a6f5ef08","doc_no":"A.6.1.1.1.2.6.1.1.2.4","title":"Avalanche","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3597,"content":"The documents herein contain a Directory of all Instances on Avalanche of the Allocation System Primitive with Instance status of `Active`.","contentHash":"7068bc1569c6240c570089a214f3cc3ce5cb384415ba56112ccc77ee89e09198","addressRefs":[]},"830b9c54-37df-41f1-9ae1-e114bc47636c":{"id":"830b9c54-37df-41f1-9ae1-e114bc47636c","doc_no":"A.6.1.1.1.2.6.1.1.2.4.1","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3598,"content":"The Avalanche Instances Directory of the Aave Protocol with `Active` Status are stored herein","contentHash":"0ed7f36278e7db080d373a22f98314cf900d3e2cd8cae03fab464252a6f898cb","addressRefs":[]},"85bc9184-abf0-4767-ae07-cda159c63f6f":{"id":"85bc9184-abf0-4767-ae07-cda159c63f6f","doc_no":"A.6.1.1.1.2.6.1.1.2.4.1.1","title":"Avalanche - Aave v3 USDC Vault Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3599,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.4.1.1 - Avalanche - Aave v3 USDC Vault Instance Configuration Document](ae06054a-1ed8-410b-983d-1789b49f1f19).","contentHash":"af0e2d42763773842f590ab691c8d643876c9223d487a61cb65e24ed13f25e28","addressRefs":[]},"805d95ac-c6fa-4326-bade-380c3635306c":{"id":"805d95ac-c6fa-4326-bade-380c3635306c","doc_no":"A.6.1.1.1.2.6.1.1.2.4.2","title":"Spark Savings V2","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3600,"content":"The Avalanche Instances Directory of the Spark Savings v2 Protocol with `Active` Status are stored herein","contentHash":"69e7ed82fd742ec4e6570fa88c3812f0972fe41304ab358d187e0af932cca345","addressRefs":[]},"82ccfe21-2172-41cc-b845-231ed61b101d":{"id":"82ccfe21-2172-41cc-b845-231ed61b101d","doc_no":"A.6.1.1.1.2.6.1.1.2.4.2.1","title":"Avalanche - Spark Savings v2 USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3601,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.3.4.2.1 - Avalanche - Spark Savings v2 USDC Instance Configuration Document](afa35a43-18e2-4084-b36c-eb584f4749ac)","contentHash":"65a86bab8bb21d0dbb85fb28408945ac015fcc6dd8987bc75f4a26f2195ee886","addressRefs":[]},"1df4d054-4443-4c64-b34b-c9fce456276b":{"id":"1df4d054-4443-4c64-b34b-c9fce456276b","doc_no":"A.6.1.1.1.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3602,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"e4ec840c-dee5-4afe-9f41-c9061c70a0d9":{"id":"e4ec840c-dee5-4afe-9f41-c9061c70a0d9","doc_no":"A.6.1.1.1.2.6.1.1.3.1","title":"Blackrock","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3603,"content":"The Ethereum Mainnet Instances Directory of the Blackrock Protocol with `Completed` Status are stored herein.","contentHash":"6d92c027ea3125da383a30d6a904229152799b6349ee497449d6265fd316cfc6","addressRefs":[]},"6d30c514-ea40-45ca-93cd-0771830b3617":{"id":"6d30c514-ea40-45ca-93cd-0771830b3617","doc_no":"A.6.1.1.1.2.6.1.1.3.1.1","title":"Ethereum Mainnet - Blackrock USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3604,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.4.1.1 - Ethereum Mainnet - Blackrock USDC Instance Configuration Document](7a52fb87-96bf-4135-9a61-f2dc068af12c).","contentHash":"b092c6080c05bc0b96e18056368ea6c81e91c25c28302e32047c7abd092e2518","addressRefs":[]},"5e56bd40-1e89-4549-adaa-54776089fe13":{"id":"5e56bd40-1e89-4549-adaa-54776089fe13","doc_no":"A.6.1.1.1.2.6.1.1.3.2","title":"Centrifuge","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3605,"content":"The Ethereum Mainnet Instances Directory of the Centrifuge Protocol with `Completed` Status are stored herein.","contentHash":"b6c93de1da39ab4e0379b0b843e4e1a274dadd35cebdb9dbd5179f3988b7632b","addressRefs":[]},"495b8996-fd2c-46ba-8e46-945b22eff733":{"id":"495b8996-fd2c-46ba-8e46-945b22eff733","doc_no":"A.6.1.1.1.2.6.1.1.3.2.1","title":"Ethereum Mainnet - Centrifuge USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3606,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.1.2.6.1.4.2.1 - Ethereum Mainnet - Centrifuge USDC Instance Configuration Document](289555ee-996e-43a7-b05f-a0b06d1238f5).","contentHash":"39045856603f12cbb4dc17cdfb25b6406abca3933a1f5a439121318ce0d19522","addressRefs":[]},"73a22cb8-06cd-4324-b0fe-f37bf538f7a9":{"id":"73a22cb8-06cd-4324-b0fe-f37bf538f7a9","doc_no":"A.6.1.1.1.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3607,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.6.1.1.2 - Active Instances Directory](20e0bc23-8a73-4ea3-b626-56f6286aded9), whereas failed Invocations are Archived in [A.6.1.1.1.2.6.1.1.5 - Hub Data Repository](143d1560-f068-4f83-9b50-c5e80fc9ec21).","contentHash":"48dfe7b911f14832af0f130b198b87706dead0b7e0baef086186583b31acd2dc","addressRefs":[]},"143d1560-f068-4f83-9b50-c5e80fc9ec21":{"id":"143d1560-f068-4f83-9b50-c5e80fc9ec21","doc_no":"A.6.1.1.1.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3608,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e0c8e24c-9b21-4281-8ea7-dfbb2bbdeb15":{"id":"e0c8e24c-9b21-4281-8ea7-dfbb2bbdeb15","doc_no":"A.6.1.1.1.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3609,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"63b469da-4eb4-48b9-8b91-83edcc819dd9":{"id":"63b469da-4eb4-48b9-8b91-83edcc819dd9","doc_no":"A.6.1.1.1.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3610,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"6506b603-5723-4b1c-b82c-25ed31ac429a":{"id":"6506b603-5723-4b1c-b82c-25ed31ac429a","doc_no":"A.6.1.1.1.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3611,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"e4ba3491-5b24-49b0-91f1-c9ad9438b190":{"id":"e4ba3491-5b24-49b0-91f1-c9ad9438b190","doc_no":"A.6.1.1.1.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3612,"content":"The documents herein provide general specifications of the Spark Liquidity Layer and define Spark’s overarching strategy and operational framework for managing across all Instances.","contentHash":"cd0046828117aaa631e2b010d3b4b27bef5acfc813743d365bcdba1a28b90a0b","addressRefs":[]},"137b4d21-d68c-4cdd-9f7f-58b9a28bb048":{"id":"137b4d21-d68c-4cdd-9f7f-58b9a28bb048","doc_no":"A.6.1.1.1.2.6.1.2.1","title":"General Specifications","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3613,"content":"The documents herein contain general specifications for the Spark Liquidity Layer.","contentHash":"628323eb9f2ce1e7465c983e2e0dadefc68e54f37915275af55f7cb36d3e0453","addressRefs":[]},"e9d83462-27f2-4bc0-a63a-596dd7c517b4":{"id":"e9d83462-27f2-4bc0-a63a-596dd7c517b4","doc_no":"A.6.1.1.1.2.6.1.2.1.1","title":"Spark Liquidity Layer Architecture","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3614,"content":"The documents herein describe the high-level design of the Spark Liquidity Layer, including its key smart contracts and their functionality.","contentHash":"3db11edbdb6656e77b803b6086d37d76c3180566d41c2cf30cb5233ee44b354b","addressRefs":[]},"f3885398-6641-437b-a413-276ac48e624a":{"id":"f3885398-6641-437b-a413-276ac48e624a","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1","title":"Spark Liquidity Layer Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3615,"content":"The subdocuments herein provide the addresses of the Spark Liquidity Layer’s constituent contracts.","contentHash":"a44641936fa5ee57106ed88a92b01c49111e795256d6f42f1ed42c3ea5811cfa","addressRefs":[]},"fd4ca647-2eb2-403c-975b-4da0601bffba":{"id":"fd4ca647-2eb2-403c-975b-4da0601bffba","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.1","title":"Allocator Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3616,"content":"The documents herein contain global key addresses for the Allocator Contracts.","contentHash":"a99119eb26b8e6fbaae81a45fa911afc0af3344a9ea2bbcb90fc7cf9bd94fe9c","addressRefs":[]},"86a5b9c5-8d49-4538-9995-c8c1200f5942":{"id":"86a5b9c5-8d49-4538-9995-c8c1200f5942","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.1.1","title":"Allocator Buffer Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3617,"content":"The address of the ALLOCATOR_BUFFER contract is: `0xc395D150e71378B47A1b8E9de0c1a83b75a08324`","contentHash":"e03a45ed30ee8d905a03ebe7f42a82f2a21ef0e9a5809807d4882a5a8d00bede","addressRefs":["0xc395d150e71378b47a1b8e9de0c1a83b75a08324"]},"fcad0844-97d7-429b-b4bf-8ba4c657a0fc":{"id":"fcad0844-97d7-429b-b4bf-8ba4c657a0fc","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.1.2","title":"Allocator Oracle Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3618,"content":"The address of the ALLOCATOR_ORACLE contract is: `0xc7B91C401C02B73CBdF424dFaaa60950d5040dB7`","contentHash":"3915a8e9d83e0d12a43a164e763cda42d8b41817675dff88c98314a34152cb8e","addressRefs":["0xc7b91c401c02b73cbdf424dfaaa60950d5040db7"]},"6936b2a0-5933-4550-88eb-ee87c9227d8e":{"id":"6936b2a0-5933-4550-88eb-ee87c9227d8e","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.1.3","title":"Allocator Registry Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3619,"content":"The address of the ALLOCATOR_REGISTRY contract is: `0xCdCFA95343DA7821fdD01dc4d0AeDA958051bB3B`","contentHash":"b7d71c2ecb2f67f2fe2ddf5b5835dec050bd7652285c86dba07b3fb3e96f8275","addressRefs":["0xcdcfa95343da7821fdd01dc4d0aeda958051bb3b"]},"b64d1f0a-3c6d-48af-bb79-0504e4e58a88":{"id":"b64d1f0a-3c6d-48af-bb79-0504e4e58a88","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.1.4","title":"Allocator Roles Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3620,"content":"The address of the ALLOCATOR_ROLES contract is: `0x9A865A710399cea85dbD9144b7a09C889e94E803`","contentHash":"458d4bfa62334f282ee18ad433673de3de9a11f7e2c97fd190afc1bef481a49d","addressRefs":["0x9a865a710399cea85dbd9144b7a09c889e94e803"]},"a9b28dbc-1993-43ba-9b24-dcca91f08f14":{"id":"a9b28dbc-1993-43ba-9b24-dcca91f08f14","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.1.5","title":"Allocator Vault (Spark-A) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3621,"content":"The address of the ALLOCATOR_VAULT (ALLOCATOR-SPARK-A) contract is: `0x691a6c29e9e96dd897718305427Ad5D534db16BA`","contentHash":"e26dcdce80a04b711cd9325f1a33c6370e9d2edc85c28d3a389257524c86a94e","addressRefs":["0x691a6c29e9e96dd897718305427ad5d534db16ba"]},"7db865de-8519-464b-8752-f39ecaf54fd2":{"id":"7db865de-8519-464b-8752-f39ecaf54fd2","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2","title":"ALM Contracts","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3622,"content":"The documents herein contain addresses for the ALM Contracts for the Spark Liquidity Layer on each blockchain.","contentHash":"bf1ed797cb95907834c6f4bc73e2ec5b539ecbbd3b4a6e85352da5f978ecf22c","addressRefs":[]},"834b9f4a-a39f-4b1f-95d9-d841fabfa7a2":{"id":"834b9f4a-a39f-4b1f-95d9-d841fabfa7a2","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3623,"content":"The documents herein contain the ALM Contract Addresses for the Spark Liquidity Layer on the Ethereum Mainnet.","contentHash":"5dbcf89003bbaca819fb20a4e6b15da18881b72e920ec42848c925ad3e423b4a","addressRefs":[]},"3546c2d3-7b7c-4446-aa16-ff357c1a7a0f":{"id":"3546c2d3-7b7c-4446-aa16-ff357c1a7a0f","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.1.1","title":"ALM Controller (MainnetController) Contract Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3624,"content":"The address of the ALM_CONTROLLER (MainnetController) contract is: `0x577Fa18a498e1775939b668B0224A5e5a1e56fc3`","contentHash":"be5f2ee13443816ca07adba7435e9461763d1ffe4b889b99a898fb1dd9e38500","addressRefs":["0x577fa18a498e1775939b668b0224a5e5a1e56fc3"]},"d7b0b6a0-0bac-4169-a006-4a375cba4baa":{"id":"d7b0b6a0-0bac-4169-a006-4a375cba4baa","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.1.2","title":"ALM Controller (MainnetController) Contract Version","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3625,"content":"The ALM_CONTROLLER (MainnetController) contract version is: 1.10","contentHash":"8f2427228bc78911d3bda5e75d316fb047a2c955be33e197183f8837d1b1fdf7","addressRefs":[]},"8d6c5c86-4b70-4115-b712-65106416aa77":{"id":"8d6c5c86-4b70-4115-b712-65106416aa77","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.1.3","title":"ALM Freezer Multisig (Mainnet) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3626,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.1.2.6.1.2.1.2.2.3.1 - Address](51777bdd-df5f-4a6e-93f5-8163d981f595).","contentHash":"e0ef25305d225ffccdb51eb6652436d16a31eaa88cf794e86ca91ca9f31da90b","addressRefs":[]},"f8958f39-6893-471a-bfd0-f72cb0aa0e4c":{"id":"f8958f39-6893-471a-bfd0-f72cb0aa0e4c","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.1.4","title":"ALM Relayer Multisig (Mainnet) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3627,"content":"The address of the Multisigs that has the Relayer Role are specified in [A.6.1.1.1.2.6.1.2.1.2.2.1.1 - Address](67bf2799-8d57-44be-82e4-827912ff30df) and [A.6.1.1.1.2.6.1.2.1.2.2.2.1 - Address](567e4905-2b05-493e-95ac-8a4d20afed2b).","contentHash":"2757d453e9b9ca2cef2bf87d7a97a023b7cfac3977b97219687cf712c88d19ce","addressRefs":[]},"a29a6751-4809-446c-a659-0dd93ca40379":{"id":"a29a6751-4809-446c-a659-0dd93ca40379","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.1.5","title":"ALM Proxy (Mainnet) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3628,"content":"The address of the ALM_PROXY contract is: `0x1601843c5E9bC251A3272907010AFa41Fa18347E`","contentHash":"f8e9faab4c62ee63f66a92e294861c5f76d92b335411df2be77fdc2566f1e764","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e"]},"3d7c06c5-18ab-4c30-82f1-4de153e2bc76":{"id":"3d7c06c5-18ab-4c30-82f1-4de153e2bc76","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.1.6","title":"ALM Rate Limits (Mainnet) Contract Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3629,"content":"The address of the ALM_RATE_LIMITS contract is: `0x7A5FD5cf045e010e62147F065cEAe59e5344b188`","contentHash":"d346d24664e3595f606f6d5f4460aac6b6f13cc97c9add03e9724a74d61e7641","addressRefs":["0x7a5fd5cf045e010e62147f065ceae59e5344b188"]},"339e27da-297e-458f-8420-546e085a51dd":{"id":"339e27da-297e-458f-8420-546e085a51dd","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.2","title":"Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3630,"content":"The documents herein list the ALM Contract Addresses for the Spark Liquidity Layer on Base.","contentHash":"41bbb91bfb980ecafdd678a9b3d067e5a3160bdbd1e7acbea4b3c318e4b60c58","addressRefs":[]},"eaa1d582-a814-49ef-a3ec-3fbffa414a3a":{"id":"eaa1d582-a814-49ef-a3ec-3fbffa414a3a","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.2.1","title":"ALM Controller (ForeignController Base) Contract Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3631,"content":"The address of the ALM_CONTROLLER (ForeignController) contract is: `0xC0bcbb2554D4694fe7b34bB68b9DdfbB55D896BC`","contentHash":"5deaca0553886c9da7f7821478099812b5473af1cb116b2d7df34db07c175d8c","addressRefs":["0xc0bcbb2554d4694fe7b34bb68b9ddfbb55d896bc"]},"2f264586-051d-4944-9c15-c271a2a8a0b5":{"id":"2f264586-051d-4944-9c15-c271a2a8a0b5","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.2.2","title":"ALM Controller (ForeignController Base) Contract Version Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3632,"content":"The ALM_CONTROLLER (ForeignController) contract version is: 1.8","contentHash":"cdb7cff4433591b88c2367e5d5d12f432a982be57a113126012a35982f90d59e","addressRefs":[]},"5147079e-3ff5-44c5-8039-5b1d3895ceec":{"id":"5147079e-3ff5-44c5-8039-5b1d3895ceec","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.2.3","title":"ALM Freezer Multisig (Base) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3633,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.1.2.6.1.2.1.2.2.3.1 - Address](51777bdd-df5f-4a6e-93f5-8163d981f595).","contentHash":"e0ef25305d225ffccdb51eb6652436d16a31eaa88cf794e86ca91ca9f31da90b","addressRefs":[]},"0d92d953-ce09-4f3a-a788-2f1dc7b190ed":{"id":"0d92d953-ce09-4f3a-a788-2f1dc7b190ed","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.2.4","title":"ALM Relayer Multisig (Base) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3634,"content":"The address of the Multisigs that has the Relayer Role are specified in [A.6.1.1.1.2.6.1.2.1.2.2.1.1 - Address](67bf2799-8d57-44be-82e4-827912ff30df) and [A.6.1.1.1.2.6.1.2.1.2.2.2.1 - Address](567e4905-2b05-493e-95ac-8a4d20afed2b).","contentHash":"2757d453e9b9ca2cef2bf87d7a97a023b7cfac3977b97219687cf712c88d19ce","addressRefs":[]},"425339ce-8e44-430b-ab8c-6c69f0b757e9":{"id":"425339ce-8e44-430b-ab8c-6c69f0b757e9","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.2.5","title":"ALM Proxy (Base) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3635,"content":"The address of the ALM_PROXY contract is: `0x2917956eFF0B5eaF030abDB4EF4296DF775009cA`","contentHash":"91632153c5cfa8aa62ee3d1866d4f4394797ea7a30d3d860dcbf605ae58850b9","addressRefs":["0x2917956eff0b5eaf030abdb4ef4296df775009ca"]},"576b33fc-ee31-40a4-8a04-2b6c0e618a58":{"id":"576b33fc-ee31-40a4-8a04-2b6c0e618a58","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.2.6","title":"ALM Rate Limits (Base) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3636,"content":"The address of the ALM_RATE_LIMITS contract is: `0x983eC82E45C61a42FDDA7B3c43B8C767004c8A74`","contentHash":"105780f149b04cf201d8e9ded3ae727314d13eddcd7b9b11e95eeba60cd92190","addressRefs":["0x983ec82e45c61a42fdda7b3c43b8c767004c8a74"]},"de02348b-d300-4b85-b7f9-5546106c5191":{"id":"de02348b-d300-4b85-b7f9-5546106c5191","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.3","title":"Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3637,"content":"This document contains the ALM Contract Addresses for the Spark Liquidity Layer on Arbitrum.","contentHash":"e13701d2cd2a983538189971ede795819199f86ce9d0527757b426744a479ab5","addressRefs":[]},"60979099-707d-497d-ad65-4fd6dd6c7cb0":{"id":"60979099-707d-497d-ad65-4fd6dd6c7cb0","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.3.1","title":"ALM Controller (ForeignController Arbitrum) Contract Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3638,"content":"The address of the ALM_CONTROLLER (ForeignController) contract is:\nTBC","contentHash":"10b9fea41cb220714e42f91f152ea30e71f27d24713b1180a1c59a655aec72bb","addressRefs":[]},"ea182fbb-586b-4df2-ac03-ea8291702649":{"id":"ea182fbb-586b-4df2-ac03-ea8291702649","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.3.2","title":"ALM Controller (ForeignController Arbitrum) Contract Version","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3639,"content":"The ALM_CONTROLLER (ForeignController) contract version is: 1.8","contentHash":"cdb7cff4433591b88c2367e5d5d12f432a982be57a113126012a35982f90d59e","addressRefs":[]},"294230e0-d7f9-43c5-9f38-d19074b61d47":{"id":"294230e0-d7f9-43c5-9f38-d19074b61d47","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.3.3","title":"ALM Freezer Multisig (Arbitrum) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3640,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.1.2.6.1.2.1.2.2.3.1 - Address](51777bdd-df5f-4a6e-93f5-8163d981f595).","contentHash":"e0ef25305d225ffccdb51eb6652436d16a31eaa88cf794e86ca91ca9f31da90b","addressRefs":[]},"d9bbc9dc-a8e9-413c-83ee-b6d1d3a2c2ec":{"id":"d9bbc9dc-a8e9-413c-83ee-b6d1d3a2c2ec","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.3.4","title":"ALM Relayer Multisig (Arbitrum) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3641,"content":"The address of the Multisigs that has the Relayer Role are specified in [A.6.1.1.1.2.6.1.2.1.2.2.1.1 - Address](67bf2799-8d57-44be-82e4-827912ff30df) and [A.6.1.1.1.2.6.1.2.1.2.2.2.1 - Address](567e4905-2b05-493e-95ac-8a4d20afed2b).","contentHash":"2757d453e9b9ca2cef2bf87d7a97a023b7cfac3977b97219687cf712c88d19ce","addressRefs":[]},"c671b407-fcb2-48eb-8217-2ec156b581ad":{"id":"c671b407-fcb2-48eb-8217-2ec156b581ad","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.3.5","title":"ALM Proxy (Arbitrum) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3642,"content":"The address of the ALM_PROXY contract is: `0x92afd6F2385a90e44da3a8B60fe36f6cBe1D8709`","contentHash":"5b55eec1b1087a73b9aec8c49dde2e346b10a267f77f7154f72d99c9cc556f8f","addressRefs":["0x92afd6f2385a90e44da3a8b60fe36f6cbe1d8709"]},"83f8da05-267e-4dd7-beaa-7561c9b8c5c1":{"id":"83f8da05-267e-4dd7-beaa-7561c9b8c5c1","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.3.6","title":"ALM Rate Limits (Arbitrum) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3643,"content":"The address of the ALM_RATE_LIMITS contract is: `0x19D08879851FB54C2dCc4bb32b5a1EA5E9Ad6838`","contentHash":"ef4f0954bcb0e399f3b1dc3c5b42ac94205a801493264a207376bf3c0528b5e8","addressRefs":["0x19d08879851fb54c2dcc4bb32b5a1ea5e9ad6838"]},"6cd31b91-4309-49ae-8d23-2486129f3b20":{"id":"6cd31b91-4309-49ae-8d23-2486129f3b20","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.4","title":"Unichain","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3644,"content":"This document contains the ALM Contract Addresses for the Spark Liquidity Layer on Unichain.","contentHash":"6fd264007bda95ed04b44afa566402305389f08dab4a9c221350d2b81ba75d3c","addressRefs":[]},"bcc685eb-d28c-4306-8b78-5639b1d31f6b":{"id":"bcc685eb-d28c-4306-8b78-5639b1d31f6b","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.4.1","title":"ALM Controller (ForeignController Unichain) Contract Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3645,"content":"The address of the ALM_CONTROLLER (ForeignController) contract is: TBC","contentHash":"7e8b3c088e12c2186235b9c8b75ad35ba008827f5f11ca4daa7e1cbbef27f36f","addressRefs":[]},"17ff233f-2ada-4856-be5f-f3ba2616c1b7":{"id":"17ff233f-2ada-4856-be5f-f3ba2616c1b7","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.4.2","title":"ALM Controller (ForeignController Unichain) Contract Version","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3646,"content":"The ALM_CONTROLLER (ForeignController) contract version is: 1.8","contentHash":"cdb7cff4433591b88c2367e5d5d12f432a982be57a113126012a35982f90d59e","addressRefs":[]},"23bb04f0-d312-4230-930d-27782b73b04f":{"id":"23bb04f0-d312-4230-930d-27782b73b04f","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.4.3","title":"ALM Freezer Multisig (Unichain) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3647,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.1.2.6.1.2.1.2.2.3.1 - Address](51777bdd-df5f-4a6e-93f5-8163d981f595).","contentHash":"e0ef25305d225ffccdb51eb6652436d16a31eaa88cf794e86ca91ca9f31da90b","addressRefs":[]},"351fc37c-0567-4fbc-bae0-975427192f29":{"id":"351fc37c-0567-4fbc-bae0-975427192f29","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.4.4","title":"ALM Relayer Multisig (Unichain) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3648,"content":"The address of the Multisigs that has the Relayer Role are specified in [A.6.1.1.1.2.6.1.2.1.2.2.1.1 - Address](67bf2799-8d57-44be-82e4-827912ff30df) and [A.6.1.1.1.2.6.1.2.1.2.2.2.1 - Address](567e4905-2b05-493e-95ac-8a4d20afed2b).","contentHash":"2757d453e9b9ca2cef2bf87d7a97a023b7cfac3977b97219687cf712c88d19ce","addressRefs":[]},"6affe08d-0c1c-4cbf-a100-4a04c58220bb":{"id":"6affe08d-0c1c-4cbf-a100-4a04c58220bb","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.4.5","title":"ALM Proxy (Unichain) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3649,"content":"The address of the ALM_PROXY contract is: `0x345E368fcCd62266B3f5F37C9a131FD1c39f5869`","contentHash":"a6e093d803c7dcff754d26e21c1d7d602af71ea287a56befe65cae911d408c41","addressRefs":["0x345e368fccd62266b3f5f37c9a131fd1c39f5869"]},"422a99bd-357f-4c48-882b-2608e0526282":{"id":"422a99bd-357f-4c48-882b-2608e0526282","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.4.6","title":"ALM Rate Limits (Unichain) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3650,"content":"The address of the ALM_RATE_LIMITS contract is: `0x5A1a44D2192Dd1e21efB9caA50E32D0716b35535`","contentHash":"c4260cac5fde1ef151792467e4a876a17d4aa9777850f3970542c8828e08c935","addressRefs":["0x5a1a44d2192dd1e21efb9caa50e32d0716b35535"]},"2c97bd03-ef58-411f-b2cc-1db6d8396d95":{"id":"2c97bd03-ef58-411f-b2cc-1db6d8396d95","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.5","title":"Optimism","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3651,"content":"This document contains the ALM Contract Addresses for the Spark Liquidity Layer on Optimism.","contentHash":"3d244fdaed525afe6f6b65e308f4cf39bccd274003447779dbb8ece4b54b6a0e","addressRefs":[]},"1eaa9220-d5e2-44f2-83eb-232add8f04ff":{"id":"1eaa9220-d5e2-44f2-83eb-232add8f04ff","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.5.1","title":"ALM Controller (ForeignController Optimism) Contract Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3652,"content":"The address of the ALM_CONTROLLER (ForeignController) contract is: TBC","contentHash":"7e8b3c088e12c2186235b9c8b75ad35ba008827f5f11ca4daa7e1cbbef27f36f","addressRefs":[]},"715c19b6-63bc-4eae-b8a4-0327e9a10c71":{"id":"715c19b6-63bc-4eae-b8a4-0327e9a10c71","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.5.2","title":"ALM Controller (ForeignController Optimism) Contract Version","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3653,"content":"The ALM_CONTROLLER (ForeignController) contract version is: 1.8","contentHash":"cdb7cff4433591b88c2367e5d5d12f432a982be57a113126012a35982f90d59e","addressRefs":[]},"a4cb2345-64a9-4e1f-b084-c25f6df7082a":{"id":"a4cb2345-64a9-4e1f-b084-c25f6df7082a","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.5.3","title":"ALM Freezer Multisig (Optimism) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3654,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.1.2.6.1.2.1.2.2.3.1 - Address](51777bdd-df5f-4a6e-93f5-8163d981f595).","contentHash":"e0ef25305d225ffccdb51eb6652436d16a31eaa88cf794e86ca91ca9f31da90b","addressRefs":[]},"1ce78bd7-1a4f-4389-b4dc-f2f7ab9e2b33":{"id":"1ce78bd7-1a4f-4389-b4dc-f2f7ab9e2b33","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.5.4","title":"ALM Relayer Multisig (Optimism) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3655,"content":"The address of the Multisigs that has the Relayer Role are specified in [A.6.1.1.1.2.6.1.2.1.2.2.1.1 - Address](67bf2799-8d57-44be-82e4-827912ff30df) and [A.6.1.1.1.2.6.1.2.1.2.2.2.1 - Address](567e4905-2b05-493e-95ac-8a4d20afed2b).","contentHash":"2757d453e9b9ca2cef2bf87d7a97a023b7cfac3977b97219687cf712c88d19ce","addressRefs":[]},"f1895dfc-a18c-4009-bfd3-1c16c9a62092":{"id":"f1895dfc-a18c-4009-bfd3-1c16c9a62092","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.5.5","title":"ALM Proxy (Optimism) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3656,"content":"The address of the ALM_PROXY contract is: `0x876664f0c9Ff24D1aa355Ce9f1680AE1A5bf36fB`","contentHash":"ee99298eeea568394d7b4a381ed7c13bcc3abf7b5992342f10e67847ebcf64d7","addressRefs":["0x876664f0c9ff24d1aa355ce9f1680ae1a5bf36fb"]},"71eaf0a6-1d32-4b8c-b55f-c56c9af11634":{"id":"71eaf0a6-1d32-4b8c-b55f-c56c9af11634","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.5.6","title":"ALM Rate Limits (Optimism) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3657,"content":"The address of the ALM_RATE_LIMITS contract is: `0x6B34A6B84444dC3Fc692821D5d077a1e4927342d`","contentHash":"2164e5bc80a7414e30ea98f65838e4519705bf26d3daff6b44137b4a6f0bc930","addressRefs":["0x6b34a6b84444dc3fc692821d5d077a1e4927342d"]},"4299d551-8954-4290-acb8-e97b501f8f08":{"id":"4299d551-8954-4290-acb8-e97b501f8f08","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.6","title":"Avalanche","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3658,"content":"This document contains the ALM Contract Addresses for the Spark Liquidity Layer on Avalanche.","contentHash":"53dc3602f6d7025164f98acf71cf8eb34b168550ec9d7d0177d266d3c6617c05","addressRefs":[]},"2a9bf1bb-81f7-40d2-a26d-2cc7e729913f":{"id":"2a9bf1bb-81f7-40d2-a26d-2cc7e729913f","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.6.1","title":"ALM Controller (ForeignController Avalanche) Contract Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3659,"content":"The address of the ALM_CONTROLLER (ForeignController) contract address is: `0x4E64b576F72c237690F27727376186639447f096`","contentHash":"ac274cbb5efc9e71f467143a9fa1d50833a8c79c8d85659919c520cf2b8e87cb","addressRefs":["0x4e64b576f72c237690f27727376186639447f096"]},"0bf9305e-df4e-4f12-9051-a4974fd7272c":{"id":"0bf9305e-df4e-4f12-9051-a4974fd7272c","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.6.2","title":"ALM Controller (ForeignController Avalanche) Contract Version","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3660,"content":"The ALM_CONTROLLER (ForeignController) contract version is: 1.8","contentHash":"cdb7cff4433591b88c2367e5d5d12f432a982be57a113126012a35982f90d59e","addressRefs":[]},"abe7f425-65fd-4a3a-b70c-55a8f30e708d":{"id":"abe7f425-65fd-4a3a-b70c-55a8f30e708d","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.6.3","title":"ALM Freezer Multisig (Avalanche) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3661,"content":"The address of the Multisig that has the Freezer Role is specified in TBD.","contentHash":"0709b5d2cdffdfbf2f1347d60200f681fc803cbef4c905dff83263bdfc48a7ae","addressRefs":[]},"229a9ce0-30bd-4069-a8a9-2ff911185b66":{"id":"229a9ce0-30bd-4069-a8a9-2ff911185b66","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.6.4","title":"ALM Relayer Multisig (Avalanche) Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3662,"content":"The address of the Multisigs that has the Relayer Role will be specified in a future iteration of the artifact.","contentHash":"6288f7003a008f40b681183001028e941a89ae0acbfe344bc55258cbd7385547","addressRefs":[]},"179f186a-079b-4663-b06c-b21f9dec85ca":{"id":"179f186a-079b-4663-b06c-b21f9dec85ca","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.6.5","title":"ALM Proxy (Avalanche) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3663,"content":"The address of the ALM_PROXY contract is: `TBD`","contentHash":"48e8a254e5eadf7ba42c4ca4be2ef49a3f3b4234b7764d61be85ca2752ea019b","addressRefs":[]},"43462d47-89bf-4166-88de-8601eb6ac7ad":{"id":"43462d47-89bf-4166-88de-8601eb6ac7ad","doc_no":"A.6.1.1.1.2.6.1.2.1.1.1.2.6.6","title":"ALM Rate Limits (Avalanche) Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3664,"content":"The address of the ALM_RATE_LIMITS contract is: `TBD`","contentHash":"a58f74b7c4f2dd484c5951bc5447face78a172463834a119db53f238e26c44fd","addressRefs":[]},"257dcfcb-9bb8-4989-a063-69ae4f01f224":{"id":"257dcfcb-9bb8-4989-a063-69ae4f01f224","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2","title":"Off-Chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3665,"content":"The documents herein list the off-chain operational parameters for the Spark Liquidity Layer on each blockchain. These operational parameters are protocol settings managed outside of smart contracts (off-chain), used by operators and off-chain systems to guide the functioning of the Spark Liquidity Layer.","contentHash":"d460288c5be62f90871a6862cba54e817bf179c19a3e593c280bae3464322892","addressRefs":[]},"82d5f557-3a13-4426-a10f-afbbc763df22":{"id":"82d5f557-3a13-4426-a10f-afbbc763df22","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.1","title":"Off-chain Operational Parameters For Ethereum Mainnet","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3666,"content":"The document herein lists the current off-chain operational parameters for the Spark Liquidity Layer on Ethereum Mainnet.","contentHash":"2d555f7352a2667a0fb5bbc03de98ff1cca78b7a2e45aab889a88ebd22f75725","addressRefs":[]},"fc5d7d30-b863-4be9-8ce2-66f88ce51d74":{"id":"fc5d7d30-b863-4be9-8ce2-66f88ce51d74","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.1.1","title":"Minimum Operation Size Ethereum Mainnet","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3667,"content":"The minimum transaction size for operations on Ethereum Mainnet is (`MAINNET_MIN_OPERATION_SIZE`):\n\n- 500,000","contentHash":"6d9bcf195a240df23d4d42159caadaa455fad4465a0b8b0dba2620e6cf947efd","addressRefs":[]},"faa7bb3a-7e8c-4f00-b80f-fb10862d943c":{"id":"faa7bb3a-7e8c-4f00-b80f-fb10862d943c","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.1.2","title":"Debt Ceiling Buffer Ethereum Mainnet","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3668,"content":"The buffer amount below the maximum debt ceiling is (`DEBT_CEILING_BUFFER`):\n\n- 10,000","contentHash":"579ae939b8af4928503b4cc44bafc6c07cc0965f749c0af1c640bfd4282e28b9","addressRefs":[]},"0aa39269-9d5c-48af-a1de-6b1d5f5058b5":{"id":"0aa39269-9d5c-48af-a1de-6b1d5f5058b5","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.2","title":"Off-chain Operational Parameters For Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3669,"content":"The document herein lists the current off-chain operational parameters for the Spark Liquidity Layer on Base.","contentHash":"61e5747456cb49a35123cb5a5839d4cda48560d22ccb8c6ebbb5518d50f71620","addressRefs":[]},"c97c059e-23e4-4cf4-830f-e67020bb73d7":{"id":"c97c059e-23e4-4cf4-830f-e67020bb73d7","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.2.1","title":"Minimum Operation Size Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3670,"content":"The minimum transaction size for operations on Base is (`BASE_MIN_OPERATION_SIZE`):\n\n- 100,000","contentHash":"b030a70e7ae8a50722fcd464117874a1b635a316c9dbf190f9b9b0994d3449f4","addressRefs":[]},"73d73cb8-3692-4dcf-9446-e25243715bcf":{"id":"73d73cb8-3692-4dcf-9446-e25243715bcf","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.2.2","title":"Minimum Maintained Balance Of USDC On Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3671,"content":"The minimum balance of USDC that must be maintained in a Base account within the Spark Liquidity Layer is (`USDC_MIN_BALANCE_BASE`):\n\n- 800,000","contentHash":"9174e490fbb9244fe0f37f8b65e2f6faf80ad6409ed292732b17c252807f3dd2","addressRefs":[]},"e7641f75-dfd5-4f65-8294-052475389ac2":{"id":"e7641f75-dfd5-4f65-8294-052475389ac2","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.2.3","title":"Ideal Balance Of USDC On Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3672,"content":"The ideal balance of USDC that should be maintained in a Base account within the Spark Liquidity Layer is (`USDC_OPTIMAL_BALANCE_BASE`):\n\n- 800,000","contentHash":"2523b888d7477bde7592d39ecc3dc5030d902261b89248cc92ca9a8a0f7b0b85","addressRefs":[]},"96791401-16fb-498f-9f00-34ff820c325a":{"id":"96791401-16fb-498f-9f00-34ff820c325a","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.2.4","title":"Maximum Balance Of USDC On Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3673,"content":"The maximum balance of USDC that should be maintained in a Base account within the Spark Liquidity Layer is (`USDC_MAX_BALANCE_BASE`):\n\n- 800,000","contentHash":"8ff1b1f69ecca39981d8335d3816b721cccb5a4313b5e00e254f53ee22380257","addressRefs":[]},"0f305c45-a2a2-4007-ae0e-9d829a09aba7":{"id":"0f305c45-a2a2-4007-ae0e-9d829a09aba7","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.3","title":"Off-chain Operational Parameters For Arbitrum Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3674,"content":"The documents herein list the current off-chain operational parameters for the Spark Liquidity Layer on Arbitrum.","contentHash":"2a70527570a1050a30d9db530d6415f7a96558253e954a8853e4efc87128f78e","addressRefs":[]},"57117d7b-c4ad-4848-beda-894eab3cdbda":{"id":"57117d7b-c4ad-4848-beda-894eab3cdbda","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.3.1","title":"Minimum Operation Size Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3675,"content":"The minimum transaction size for operations on Arbitrum is (`ARBITRUM_MIN_OPERATION_SIZE`):\n\n- 100,000","contentHash":"ac0a0621d0bf433307f5a35cd2d1ff196c354b5c41d3b72a90af22ca3e695e14","addressRefs":[]},"d6bcfcf6-851d-48b4-9a29-4f85be428475":{"id":"d6bcfcf6-851d-48b4-9a29-4f85be428475","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.3.2","title":"Minimum Maintained Balance Of USDC On Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3676,"content":"The minimum balance of USDC that must be maintained in an Arbitrum account within the Spark Liquidity Layer is (`USDC_MIN_BALANCE_ARBITRUM`):\n\n- This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"1d53db32ffc37612aed4400c20b3c64ba97d06b915efff5e05de274538af70a2","addressRefs":[]},"8f1288a8-bf03-4190-a44b-b63aa31428c1":{"id":"8f1288a8-bf03-4190-a44b-b63aa31428c1","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.3.3","title":"Ideal Balance Of USDC On Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3677,"content":"The ideal balance of USDC that should be maintained in an Arbitrum account within the Spark Liquidity Layer is (`USDC_OPTIMAL_BALANCE_ARBITRUM`):\n\n- This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"c9e814e7870b0f186be9f8a51cf1254563fe0c37b4f49ef5fd0e64da2abb1fac","addressRefs":[]},"b8c1a6c1-c1a4-404c-ad41-5e1ed4dd672c":{"id":"b8c1a6c1-c1a4-404c-ad41-5e1ed4dd672c","doc_no":"A.6.1.1.1.2.6.1.2.1.1.2.3.4","title":"Maximum Balance Of USDC On Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3678,"content":"The maximum balance of USDC that should be maintained in an Arbitrum account within the Spark Liquidity Layer is (`USDC_MAX_BALANCE_ARBITRUM`):\n\n- This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"9481b20b810e58fe87e9cb61b02dbb68079b0281a72c319f8a7451386a82a9db","addressRefs":[]},"cdf6df73-045a-4bcb-a456-03441aa4530e":{"id":"cdf6df73-045a-4bcb-a456-03441aa4530e","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3","title":"RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3679,"content":"The documents herein list the `Ratelimits` for the Spark Liquidity Layer on each blockchain.","contentHash":"9551292bc70b1e2474c54254f23dae6ce358e56fd4c15b18caaac6b4bda2589a","addressRefs":[]},"91227e5c-65e5-4858-bfb2-41ab65c3bc87":{"id":"91227e5c-65e5-4858-bfb2-41ab65c3bc87","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3680,"content":"The documents herein list the current `RateLimits` for the Spark Liquidity Layer on Ethereum Mainnet.","contentHash":"e56710bba59cfae6dca380266b9af3af55354731a673eb4c643a2b3b8c850f5c","addressRefs":[]},"ae234813-233e-4231-926b-5d0a8c09c684":{"id":"ae234813-233e-4231-926b-5d0a8c09c684","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.1.1","title":"USDS Mint Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3681,"content":"The maximum amount of USDS that can be minted within the Spark Liquidity Layer (`LIMIT_USDS_MINT`) is specified in the document herein.\n\n- `maxAmount` (USDS): 500,000,000\n- `slope` (USDS/ day): 500,000,000","contentHash":"b3cb78f2d7b0a52a5030ef7fcb6fb08c3eb654a6e01f5d298060334c24bbc95a","addressRefs":[]},"85d01cb5-2bbf-4df9-998c-63131d83d9db":{"id":"85d01cb5-2bbf-4df9-998c-63131d83d9db","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.1.2","title":"USDS Burn Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3682,"content":"The maximum amount of USDS that can be burned within the Spark Liquidity Layer (`LIMIT_USDS_BURN`) is specified in the document herein.\n\n- `maxAmount` (USDS): 0\n- `slope` (USDS/ day): 0","contentHash":"803836b533d5baf41d18231bb58f2c9ede09dd74a0b5b32b4468afde4cfba709","addressRefs":[]},"cd6ad021-80f4-432d-b00f-1d26e7984297":{"id":"cd6ad021-80f4-432d-b00f-1d26e7984297","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.1.3","title":"USDS For USDC Swap Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3683,"content":"The maximum amount of USDS that can be swapped for USDC by the Spark Liquidity Layer in the Mainnet PSM (`LIMIT_USDS_TO_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): 500,000,000\n- `slope` (USDC/ day): 300,000,000","contentHash":"611263d7c626488ab1aafed622b0931d3947f4163c52874cd02baf2e064c5f0e","addressRefs":[]},"9024c8ce-40a6-4eb7-90c7-62dee7d5e408":{"id":"9024c8ce-40a6-4eb7-90c7-62dee7d5e408","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.1.4","title":"USDC Mainnet ALM Proxy Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3684,"content":"The maximum amount of USDC that can be sent to the Ethereum Mainnet ALM Proxy (`LIMIT_USDC_TO_DOMAIN`, hashed with Ethereum domain) is specified in the document herein.\n\n- `maxAmount` (USDC): 4,000,000\n- `slope` (USDC/ day): 2,000,000","contentHash":"7259d17c9ee4379004d19a6d8e979d1c0d43c0a5a171c40449264f2a5a3b5cf2","addressRefs":[]},"77d2f2c3-c1a6-4d63-ac8f-dd1b8dedaab8":{"id":"77d2f2c3-c1a6-4d63-ac8f-dd1b8dedaab8","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.1.4.1","title":"USDC Mainnet ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3685,"content":"The maximum amount of USDC that can be bridged to Ethereum Mainnet ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_ETH`) is specified in the document herein.\n\n- `maxAmount` (USDC): 200,000,000\n- `slope` (USDC/ day): 500,000,000","contentHash":"3875379014a9bb699804f06dc3e205196e1cd6208fca260d191ebfa351c99786","addressRefs":[]},"e2055ff1-f601-4923-b186-57513a2cf682":{"id":"e2055ff1-f601-4923-b186-57513a2cf682","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2","title":"Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3686,"content":"The documents herein list the current `RateLimits` for the Spark Liquidity Layer on Base.","contentHash":"647f940f35d4d767f1efe3a7c91dafee79cc46c11075e96e5f5ec771dfa3629b","addressRefs":[]},"6cd396d6-8f98-4ca8-a61d-8b49def2a793":{"id":"6cd396d6-8f98-4ca8-a61d-8b49def2a793","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.1","title":"Base USDC Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3687,"content":"The maximum amount of USDC that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): 50,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"3f69d7833a517d8abc4cf7bc52961ff8d4c3c21565d6013190947b8a7bfe45b8","addressRefs":[]},"3cd83281-90cf-4c29-a3a5-6dc83099750b":{"id":"3cd83281-90cf-4c29-a3a5-6dc83099750b","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.2","title":"Base USDC Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3688,"content":"The maximum amount of USDC that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): 50,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"fca73dc5de240af9e7dee8786edc98f917d92667b50fa2da582a5e0b621d0f6c","addressRefs":[]},"38d0e2c3-3702-4906-b230-66a152dd998d":{"id":"38d0e2c3-3702-4906-b230-66a152dd998d","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.3","title":"Base USDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3689,"content":"The maximum amount of USDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): Unlimited\n- `slope` (USDS/ day): Unlimited","contentHash":"5a7bbfdab56beb1fcbc4fa2a103f55200ae9700a56b85741cb49e9200b78f8a8","addressRefs":[]},"2cac91fb-e1e2-443d-ad12-ee45211eba1d":{"id":"2cac91fb-e1e2-443d-ad12-ee45211eba1d","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.4","title":"Base USDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3690,"content":"The maximum amount of USDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): max\n- `slope` (USDS/ day): 0","contentHash":"29f141edf4271e104624ff9f7ae9827aa7ff13433658489a7540c290076951fa","addressRefs":[]},"f9e926e1-e127-42ec-883d-d11baecb0fd6":{"id":"f9e926e1-e127-42ec-883d-d11baecb0fd6","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.5","title":"Base sUSDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3691,"content":"The maximum amount of sUSDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (sUSDS): Unlimited\n- `slope` (sUSDS/ day): Unlimited","contentHash":"93b5d251a5d1c26f7670f3a3c8ee73a0cf7233fbeb0b7a818cf1e66fcff2d061","addressRefs":[]},"521cc062-0b43-4d93-91c3-fdc29e4792f1":{"id":"521cc062-0b43-4d93-91c3-fdc29e4792f1","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.6","title":"Base sUSDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3692,"content":"The maximum amount of sUSDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (sUSDS): max\n- `slope` (sUSDS/ day): 0","contentHash":"9884f7f6c9ed790fab6ab610d32f81efaea23b01c2f91c42761a7eb67a440163","addressRefs":[]},"59bc4c89-3edf-4a1b-a288-151cd5cfc624":{"id":"59bc4c89-3edf-4a1b-a288-151cd5cfc624","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.7","title":"USDC Base ALM Proxy Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3693,"content":"The maximum amount of USDC that can be sent to the Base ALM Proxy (`LIMIT_USDC_TO_DOMAIN`, hashed with Base domain) is specified in the document herein.\n\n- `maxAmount` (USDC): 4,000,000\n- `slope` (USDC/ day): 2,000,000","contentHash":"184134be6fb6bc9d29efbdcfc1a01bdad72bc1830e6a035247699d0aba874988","addressRefs":[]},"2a8a7903-983a-4dc5-9f77-0b90ab66f9ae":{"id":"2a8a7903-983a-4dc5-9f77-0b90ab66f9ae","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.2.7.1","title":"USDC Base ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3694,"content":"The maximum amount of USDC that can be bridged to Base ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_BASE`) is specified in the document herein.\n\n- `maxAmount` (USDC): 200,000,000\n- `slope` (USDC/ day): 500,000,000","contentHash":"ebd67d9e99c1e414eea8a4ae0790773169fe32ba57bd32c4bb7dfb5b89fecea8","addressRefs":[]},"626bcaea-4de3-4262-9098-82c454c4fb9c":{"id":"626bcaea-4de3-4262-9098-82c454c4fb9c","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.3","title":"Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3695,"content":"The documents herein list the current `RateLimits` for the Spark Liquidity Layer on Arbitrum.","contentHash":"801e9d2b04b37c983ee2c6937c4ad0f0e9901def5cc6c5a9c025599a5f5fa7ef","addressRefs":[]},"ffbc3f81-fd95-4a38-9f95-6c834d01212a":{"id":"ffbc3f81-fd95-4a38-9f95-6c834d01212a","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.3.1","title":"Arbitrum USDC Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3696,"content":"The maximum amount of USDC that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope` (USDC/ day): This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"c8677550306e7e87d5b793c3d9ddeb8eed86891c16e9425f961fdba9721465dc","addressRefs":[]},"f7e5dc3b-b26c-4a44-9e0b-0b385ad22704":{"id":"f7e5dc3b-b26c-4a44-9e0b-0b385ad22704","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.3.2","title":"Arbitrum USDC Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3697,"content":"The maximum amount of USDC that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope` (USDC/ day): This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"957e6139dee82595a04d446f9636d34365c2b145faa36cddde287d2c87d13c09","addressRefs":[]},"ddf6a5b7-5c41-4c80-8ad9-0222ef558fb4":{"id":"ddf6a5b7-5c41-4c80-8ad9-0222ef558fb4","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.3.3","title":"Arbitrum USDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3698,"content":"The maximum amount of USDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope` (USDS/ day): This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"ea9b92a06b45a8d5272b04fb8aa5e05ff7acf0b22a998f437148114deada0f28","addressRefs":[]},"f5a14451-b476-46ea-91e8-009f6230ac3e":{"id":"f5a14451-b476-46ea-91e8-009f6230ac3e","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.3.4","title":"Arbitrum USDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3699,"content":"The maximum amount of USDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope` (USDS/ day): This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"405c4ea4c3e98ee1f76a370a3141c47c172aeb4c0474b039a8c5a09c4f2838db","addressRefs":[]},"8be6ab2f-9b82-4727-be24-e2d6ac5c4c5f":{"id":"8be6ab2f-9b82-4727-be24-e2d6ac5c4c5f","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.3.5","title":"Arbitrum sUSDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3700,"content":"The maximum amount of sUSDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (USDS worth of sUSDS): 10,000,000\n- `slope` (USDS worth of sUSDS): 5,000,000","contentHash":"24c7464e90bdeb5ee2277c889c20c505057537f06d21f6c4f23db49612ffd3d6","addressRefs":[]},"127e7438-d797-4b3e-a464-230f8253f0d2":{"id":"127e7438-d797-4b3e-a464-230f8253f0d2","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.3.6","title":"Arbitrum sUSDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3701,"content":"The maximum amount of sUSDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (sUSDS): Unlimited","contentHash":"19669a82886da0f2d8d65ea5cc5e8efa336d0e7ee7aaf4ed7f0cc4a81e67b35c","addressRefs":[]},"40eb29f0-9d83-4c83-ae68-ea46b9f1bcac":{"id":"40eb29f0-9d83-4c83-ae68-ea46b9f1bcac","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.4","title":"Unichain","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3702,"content":"The documents herein list the current `RateLimits` for the Spark Liquidity Layer on Unichain.","contentHash":"37e09cd1501dfac3c00651022fd04249b1ad91a81473d6fa37d069e3ce17dab9","addressRefs":[]},"c02294b9-1938-40b5-af8c-57b82c7b1f51":{"id":"c02294b9-1938-40b5-af8c-57b82c7b1f51","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.4.1","title":"Unichain USDC Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3703,"content":"The maximum amount of USDC that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): 50,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"3f69d7833a517d8abc4cf7bc52961ff8d4c3c21565d6013190947b8a7bfe45b8","addressRefs":[]},"cb146c46-207d-4a52-be6d-9a4623f2d921":{"id":"cb146c46-207d-4a52-be6d-9a4623f2d921","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.4.2","title":"Unichain USDC Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3704,"content":"The maximum amount of USDC that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): 50,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"fca73dc5de240af9e7dee8786edc98f917d92667b50fa2da582a5e0b621d0f6c","addressRefs":[]},"f998ce83-747f-4c60-95ba-26f1f2facdb8":{"id":"f998ce83-747f-4c60-95ba-26f1f2facdb8","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.4.3","title":"Unichain USDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3705,"content":"The maximum amount of USDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): Unlimited\n- `slope` (USDS/ day): Unlimited","contentHash":"5a7bbfdab56beb1fcbc4fa2a103f55200ae9700a56b85741cb49e9200b78f8a8","addressRefs":[]},"3a6e6efd-314a-4f21-b238-0ffa148fb8e3":{"id":"3a6e6efd-314a-4f21-b238-0ffa148fb8e3","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.4.4","title":"Unichain USDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3706,"content":"The maximum amount of USDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): Unlimited\n- `slope` (USDS/ day): Unlimited","contentHash":"d951ddf4e752d43ddf75312868d0fd3864e4f8134053c8c784829e0d17385e94","addressRefs":[]},"1741e5ba-e45a-4960-b193-f8bee9d595c9":{"id":"1741e5ba-e45a-4960-b193-f8bee9d595c9","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.4.5","title":"Unichain sUSDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3707,"content":"The maximum amount of sUSDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (USDS worth of sUSDS): Unlimited\n- `slope` (USDS worth of sUSDS): Unlimited","contentHash":"ad9dc7fed93f2d9c4ed426274fc1280a8c9e0fb73a8fff0a7207cf0c0c045890","addressRefs":[]},"16004284-de05-4ee4-a9db-762de1270de9":{"id":"16004284-de05-4ee4-a9db-762de1270de9","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.4.6","title":"Unichain sUSDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3708,"content":"The maximum amount of sUSDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (sUSDS): Unlimited","contentHash":"19669a82886da0f2d8d65ea5cc5e8efa336d0e7ee7aaf4ed7f0cc4a81e67b35c","addressRefs":[]},"13bda6de-0abf-4b64-9379-4653c8f4875e":{"id":"13bda6de-0abf-4b64-9379-4653c8f4875e","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.5","title":"Optimism","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3709,"content":"The documents herein list the current `RateLimits` for the Spark Liquidity Layer on Optimism.","contentHash":"975ae4852b26bbdb3ba1745800a48ee01c8a990615c2ee966f15e7fa1a446b5d","addressRefs":[]},"3f08e295-8edc-489a-8d46-9b4b7ca83d01":{"id":"3f08e295-8edc-489a-8d46-9b4b7ca83d01","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.5.1","title":"Optimism USDC Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3710,"content":"The maximum amount of USDC that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): 50,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"3f69d7833a517d8abc4cf7bc52961ff8d4c3c21565d6013190947b8a7bfe45b8","addressRefs":[]},"90c809f2-3f2c-4a76-beb8-06140822e2cd":{"id":"90c809f2-3f2c-4a76-beb8-06140822e2cd","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.5.2","title":"Optimism USDC Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3711,"content":"The maximum amount of USDC that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): 50,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"fca73dc5de240af9e7dee8786edc98f917d92667b50fa2da582a5e0b621d0f6c","addressRefs":[]},"f162baa7-9400-4368-adf8-5793415de5b3":{"id":"f162baa7-9400-4368-adf8-5793415de5b3","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.5.3","title":"Optimism USDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3712,"content":"The maximum amount of USDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): Unlimited\n- `slope` (USDS/ day): Unlimited","contentHash":"5a7bbfdab56beb1fcbc4fa2a103f55200ae9700a56b85741cb49e9200b78f8a8","addressRefs":[]},"f04f600b-3cc0-4c10-8540-1dce56d130e2":{"id":"f04f600b-3cc0-4c10-8540-1dce56d130e2","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.5.4","title":"Optimism USDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3713,"content":"The maximum amount of USDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDS`) is specified in the document herein.\n\n- `maxAmount` (USDS): Unlimited\n- `slope` (USDS/ day): Unlimited","contentHash":"d951ddf4e752d43ddf75312868d0fd3864e4f8134053c8c784829e0d17385e94","addressRefs":[]},"ae241843-1492-42b4-8a66-687701ba4dc0":{"id":"ae241843-1492-42b4-8a66-687701ba4dc0","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.5.5","title":"Optimism sUSDS Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3714,"content":"The maximum amount of sUSDS that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (USDS worth of sUSDS): Unlimited\n- `slope` (USDS worth of sUSDS): Unlimited","contentHash":"ad9dc7fed93f2d9c4ed426274fc1280a8c9e0fb73a8fff0a7207cf0c0c045890","addressRefs":[]},"a9d4793d-da6a-440e-9435-993070700b60":{"id":"a9d4793d-da6a-440e-9435-993070700b60","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.5.6","title":"Optimism sUSDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3715,"content":"The maximum amount of sUSDS that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_SUSDS`) is specified in the document herein.\n\n- `maxAmount` (sUSDS): Unlimited","contentHash":"19669a82886da0f2d8d65ea5cc5e8efa336d0e7ee7aaf4ed7f0cc4a81e67b35c","addressRefs":[]},"bf7f9935-ef38-4d33-a871-d4273cb341e0":{"id":"bf7f9935-ef38-4d33-a871-d4273cb341e0","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.6","title":"Avalanche","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3716,"content":"The documents herein list the current `RateLimits` for the Spark Liquidity Layer on Avalanche.","contentHash":"bc253b7b1fb63b4ac5d7581512cd12f466a89f8a372468636cfcd4be1b8bd090","addressRefs":[]},"3d180927-6af0-462e-b507-ecd3b76aead9":{"id":"3d180927-6af0-462e-b507-ecd3b76aead9","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.6.1","title":"Avalanche USDC Deposit Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3717,"content":"The maximum amount of USDC that can be deposited into the PSM (`LIMIT_PSM_DEPOSIT_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): Unlimited\n- `slope` (USDC/ day): Unlimited","contentHash":"943fa4170befc2825bd884c318382df1c892945f49141bc45d393795cb0afa0d","addressRefs":[]},"8b9fa488-8005-488a-8537-11a8bdcb205b":{"id":"8b9fa488-8005-488a-8537-11a8bdcb205b","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.6.2","title":"Avalanche USDC Withdrawal Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3718,"content":"The maximum amount of USDC that can be withdrawn from the PSM (`LIMIT_PSM_WITHDRAW_USDC`) is specified in the document herein.\n\n- `maxAmount` (USDC): Unlimited\n- `slope` (USDC/ day): Unlimited","contentHash":"7137965d644ba0ae8917897cad451c5945f734736ecefab38433797a9185ab29","addressRefs":[]},"59673606-e50f-4c75-86e1-6bbc968321f0":{"id":"59673606-e50f-4c75-86e1-6bbc968321f0","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.6.3","title":"USDC Avalanche ALM Proxy Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3719,"content":"The maximum amount of USDC that can be sent to the Avalanche ALM Proxy (`LIMIT_USDC_TO_DOMAIN`, hashed with Avalanche domain) is specified in the document herein.\n\n- `maxAmount` (USDC): 100,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"60f367c49bed8fcc61b7c5ddac5693ba17f38b588f501ea40c41044254bab76b","addressRefs":[]},"0de9f0f1-ccef-4f17-b699-7dedb79673b9":{"id":"0de9f0f1-ccef-4f17-b699-7dedb79673b9","doc_no":"A.6.1.1.1.2.6.1.2.1.1.3.6.3.1","title":"USDC Avalanche ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3720,"content":"The maximum amount of USDC that can be bridged to Avalanche ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_AVALANCHE`) is specified in the document herein.\n\n- `maxAmount` (USDC): 100,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"2489516d50aa1c97cb525cda8910b4f9018d7d1bc1aeac2b0c388cb171d86597","addressRefs":[]},"9e74aa40-898f-4389-ba3d-8590c12f075d":{"id":"9e74aa40-898f-4389-ba3d-8590c12f075d","doc_no":"A.6.1.1.1.2.6.1.2.1.2","title":"Governance Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3721,"content":"The documents herein describe the specific governance processes for the Spark Liquidity Layer.","contentHash":"6ce579e6a84bc58452721a5ec39ca36a7dd49363760b6dd58aefb01d0d9bfbbd","addressRefs":[]},"da88ec3d-3ce8-4f28-bb8e-bbdd3deb2b14":{"id":"da88ec3d-3ce8-4f28-bb8e-bbdd3deb2b14","doc_no":"A.6.1.1.1.2.6.1.2.1.2.1","title":"Invoking New Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3722,"content":"The governance process to invoke a new Instance of the Allocation System Primitive follows the Root Edit process see [A.6.1.1.1.2.2.2.2.1.2 - Operational Process Definition](a9c97e28-6ac7-4e04-aac1-9d5dd617c6e0).","contentHash":"6a8f22ee7309e68f7a5ee8f4dc14148ac48b54f1be0388f8ced2467fc7a57a79","addressRefs":[]},"631973de-6f13-440b-8f66-478dfdda4d60":{"id":"631973de-6f13-440b-8f66-478dfdda4d60","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2","title":"Multisigs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3723,"content":"The documents herein define multisigs that have privileged access to manage the Spark Liquidity Layer.","contentHash":"a387892d07e70d9c3e2ba25474f7783ec8283116517836761144d4ec38424ff0","addressRefs":[]},"d4628bb9-978c-4e4a-884c-7e0b3b7e1daf":{"id":"d4628bb9-978c-4e4a-884c-7e0b3b7e1daf","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.1","title":"Prime Relayer Multisig","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3724,"content":"The Prime Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.1.2.6.1.2.2.1.1.2 - Relayer Role](cc2f7956-90ce-4025-9642-bfe403dc3ccc) and is controlled by Phoenix Labs.","contentHash":"688ba126a2cbc75762bb7d29af3eb6963d2b589d1bc5f62c1f625c19f96e9505","addressRefs":[]},"67bf2799-8d57-44be-82e4-827912ff30df":{"id":"67bf2799-8d57-44be-82e4-827912ff30df","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.1.1","title":"Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3725,"content":"The address of the Prime Relayer Multisig on the Ethereum Mainnet, Base, and Arbitrum is `0x8a25A24EDE9482C4Fc0738F99611BE58F1c839AB`.","contentHash":"31fabd3aadc526b288594fe0381a47f680cece30fa29d044a6e099dace354a6a","addressRefs":["0x8a25a24ede9482c4fc0738f99611be58f1c839ab"]},"8deac2a8-c728-4d0c-9f05-6fcf3965bdc9":{"id":"8deac2a8-c728-4d0c-9f05-6fcf3965bdc9","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.1.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3726,"content":"The Prime Relayer Multisig currently has a 1/2 signing requirement.","contentHash":"c72c182f9db5e595a36418e6949dad97a031f20153b4f1b95aa235e5a462bc27","addressRefs":[]},"bad3c652-ddda-4161-9ec8-5cef7a74b3f4":{"id":"bad3c652-ddda-4161-9ec8-5cef7a74b3f4","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.1.3","title":"Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3727,"content":"The signers of the Prime Relayer Multisig are two (2) addresses controlled by Ecosystem Actor Phoenix Labs.","contentHash":"e98f823e68af3aa9dd9ebe07103ee70a18721a812376f0be0d303faceb53072a","addressRefs":[]},"d800ab5e-4efa-45db-8d31-435f090a9678":{"id":"d800ab5e-4efa-45db-8d31-435f090a9678","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.1.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3728,"content":"The signers of the Prime Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Spark Artifact.","contentHash":"e004191e5adb3b8f57ede22725b5fcbcbddda3eff2cab32d0de4a6904074ea7c","addressRefs":[]},"19d05632-97ef-4717-a47d-c0de16631fac":{"id":"19d05632-97ef-4717-a47d-c0de16631fac","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.1.5","title":"Modification","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3729,"content":"Ecosystem Actor Phoenix Labs can change the signers of the Prime Relayer Multisig at any time, so long as there are at least two (2) signers and at least a majority of signers are required to execute transactions.","contentHash":"a6d979dfdb8a38f1373b2ae1599d694a41bb95eb950783c1fbe2ddb9cc61b1fc","addressRefs":[]},"8286092a-69f2-46af-a989-c694a1756753":{"id":"8286092a-69f2-46af-a989-c694a1756753","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.2","title":"Core Operator Relayer Multisig","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3730,"content":"The Core Operator Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.1.2.6.1.2.2.1.1.2 - Relayer Role](cc2f7956-90ce-4025-9642-bfe403dc3ccc) and is jointly controlled by Operational GovOps Soter Labs and the Spark Assets Foundation in accordance with [A.6.1.1.1.2.1.1.3.1.1.4.3 - Spark Assets Foundation](4d70e4a7-6f65-421c-b22a-ac5a6eae8170).","contentHash":"482df7c5043d33a4e17f7e9cea6986c7a515cf236afb73baf83fbf785de1a833","addressRefs":[]},"567e4905-2b05-493e-95ac-8a4d20afed2b":{"id":"567e4905-2b05-493e-95ac-8a4d20afed2b","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.2.1","title":"Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3731,"content":"The address of the Core Operator Relayer Multisig on the Ethereum Mainnet, Base, and Arbitrum is `0x8Cc0Cb0cfB6B7e548cfd395B833c05C346534795`.","contentHash":"8c2f0dc1a36cecc42789df619e7b6e851d72643fd0b992d1a6d2ad594fc53c3a","addressRefs":["0x8cc0cb0cfb6b7e548cfd395b833c05c346534795"]},"d397fcef-85da-4c07-b675-14ec66d4cff9":{"id":"d397fcef-85da-4c07-b675-14ec66d4cff9","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.2.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3732,"content":"The Core Operator Relayer Multisig currently has a 2/5 signing requirement.","contentHash":"94f926122c1ea530de646f6bebc8ba51b23f2aaced26518a34cdb39a69c79916","addressRefs":[]},"1563f1ee-0097-4bb3-a03a-01162d00788b":{"id":"1563f1ee-0097-4bb3-a03a-01162d00788b","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.2.3","title":"Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3733,"content":"The Core Operator Relayer Multisig comprises the following signers:\n\n- Operational GovOps Soter Labs: 2 signers\n- Spark Assets Foundation (SAF): 2 signers\n- Phoenix Labs (PL): 1 signer\n\nPhoenix Labs' signer may create and propose transactions; execution requires meeting the 2/5 threshold.","contentHash":"142c3cf93750d758f4a4fbe646307f8ecb9d0b8bb71bf403aed99f27c6124036","addressRefs":[]},"846f23a1-eca3-4d55-8ed7-2c14c618d722":{"id":"846f23a1-eca3-4d55-8ed7-2c14c618d722","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.2.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3734,"content":"The signers of the Core Operator Relayer Multisig must use the multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Spark Artifact.","contentHash":"c83f225400842ad2301aa5cbd04ab8b3a8ebfe956b3393510b98010a4e135991","addressRefs":[]},"31c59017-769f-4a5b-88f7-8bef200dcc71":{"id":"31c59017-769f-4a5b-88f7-8bef200dcc71","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.2.5","title":"Modification","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3735,"content":"Operational GovOps Soter Labs can change the signers of the Core Operator Relayer Multisig at any time, so long as there are at least three (3) signers and at least two-thirds of signers are required to execute transactions.","contentHash":"050db4ce28c6bd1736123e3211a765079215503656f41e97eb06d3e0f0f22af0","addressRefs":[]},"c805c872-05df-4157-a869-dff28535bf81":{"id":"c805c872-05df-4157-a869-dff28535bf81","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.3","title":"Freezer Multisig","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3736,"content":"The Freezer Multisig has the `FREEZER_ROLE` as defined in [A.6.1.1.1.2.6.1.2.2.1.1.4 - Freezer Role](02a614ea-1d6b-4197-b39b-49de676092cb) and is controlled by Spark Assets Foundation, Phoenix Labs, and VoteWizard.","contentHash":"daddb1b4870b35ea9a4d50a181274596f12aaeca4d872e83e122caecc921619a","addressRefs":[]},"51777bdd-df5f-4a6e-93f5-8163d981f595":{"id":"51777bdd-df5f-4a6e-93f5-8163d981f595","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.3.1","title":"Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3737,"content":"The address of the Freezer Multisig on the Ethereum Mainnet, Base, and Arbitrum is `0x90D8c80C028B4C09C0d8dcAab9bbB057F0513431`.","contentHash":"876045d411a44fee01814f836f5e0a473696911d7336f12aa1103e0786e13cda","addressRefs":["0x90d8c80c028b4c09c0d8dcaab9bbb057f0513431"]},"cf7acab9-9363-402b-b636-395f6bb5f6f7":{"id":"cf7acab9-9363-402b-b636-395f6bb5f6f7","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.3.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3738,"content":"The Freezer Multisig currently has a 1/4 signing requirement.","contentHash":"e8033455378ec2ebcc8b994cf61a6917a80efcf8ab2f0cea14c74aa12c31c782","addressRefs":[]},"f76b5952-9060-4fe6-b64e-5533ef205919":{"id":"f76b5952-9060-4fe6-b64e-5533ef205919","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.3.3","title":"Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3739,"content":"The Freezer Multisig has the following signers:\n\n- Spark Assets Foundation (SAF): 1 signer\n- Phoenix Labs (PL): 2 signers\n- VoteWizard: 1 signer","contentHash":"e912ecf31fdfe5529fe23ab19edd59adac6d928c43d56ebe8a7cc34717cff3a3","addressRefs":[]},"4c33239e-59c9-4d5b-8872-bf7176d205dc":{"id":"4c33239e-59c9-4d5b-8872-bf7176d205dc","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.3.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3740,"content":"The signers of the Freezer Multisig should exercise their authority to freeze the Spark Liquidity Layer in the event that Spark is not complying with rules regarding Risk Capital or Asset Liability Management, or in the event of another emergency. The signers should consult with Operational GovOps Soter Labs before exercising such authority, unless such consultation would cause a delay that could result in a loss of user funds or harm to Sky or Spark. Operational GovOps Soter Labs may also ask the signers to exercise the Freezer Multisig in an emergency. The signers will work with Operational GovOps Soter Labs and, if necessary, other Ecosystem Actors, in good faith in determining whether to exercise their authority based on such request.\n\nEach action executed by the Freezer Multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum.","contentHash":"b0573f57b7437c828c085e348c9103f8193e24d1f7004ccfc66ce3faba010c81","addressRefs":[]},"658b3a32-0416-4380-b960-f86f3a2f3cfa":{"id":"658b3a32-0416-4380-b960-f86f3a2f3cfa","doc_no":"A.6.1.1.1.2.6.1.2.1.2.2.3.5","title":"Modification","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3741,"content":"Modification of the signers of the Freezer Multisig must be approved through a Governance Poll; no Executive Vote is required.\n\nThe only exceptions to this are if: 1) a signer self-reports a loss of access to their private key due to any reason; or 2) a signer explicitly expresses their wish to be removed as a signer. In both cases, the signer is required to communicate the loss of access to their private key, or the wish to be removed as a signer, in the form of a public Sky Forum post. The specific signer should be replaced as soon as possible, which does not require a Governance Poll.\n\nAny changes to the multisig signers that do not fall within the two exceptions listed above, or that have not been ratified by Sky Governance, should be questioned immediately and treated as malicious. Where malicious activity is suspected, the Core Facilitator must prepare an expedited Executive Vote so that Sky Governance can vote on removing external security access from the multisig.","contentHash":"b5351e4115202c5dd8b420111509765d5056313b9dc188f25474079e309b8a5c","addressRefs":[]},"ea73f176-0b94-4e93-b1ee-ca498ac5a6c6":{"id":"ea73f176-0b94-4e93-b1ee-ca498ac5a6c6","doc_no":"A.6.1.1.1.2.6.1.2.1.2.3","title":"Token Claim Authorization","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3742,"content":"Phoenix Labs is authorized to propose the inclusion of transfers of accrued treasury and collector revenues from the Active Instances to the Spark ALM Proxy in a Spark Spell. Additionally, for non-USD-denominated reserve assets, or USD-denominated reserve assets that are not supported by the Spark Liquidity Layer, the reserves can be transferred to the Spark Operations Multisig at address (`0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC`) to be liquidated for USDS, with the proceeds of sale transferred to the Spark SubDAO Proxy. This request must be posted to the Sky Forum under the Spark Prime category. The Operational Executor Agent must formally approve the inclusion of the transfer in a Spark Spell, with no token holder vote needed.","contentHash":"c62447808882868a756fc03fb4a98bfe758ade550fffb8054b2add0fd4257d9d","addressRefs":["0x2e1b01adabb8d4981863394bea23a1263cbaedfc"]},"ff7add39-b942-4df0-a710-75f70a05b49d":{"id":"ff7add39-b942-4df0-a710-75f70a05b49d","doc_no":"A.6.1.1.1.2.6.1.2.1.3","title":"Total Risk Capital (TRC) Management","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3743,"content":"The documents herein** **specify requirements related to Spark’s Total Risk Capital (TRC) management.","contentHash":"70af0145c28f6303507c87c4b401c913ef34a620b667a522e98ec3295d61c2a4","addressRefs":[]},"23f7ed09-99ca-45aa-8e12-dffcf55170af":{"id":"23f7ed09-99ca-45aa-8e12-dffcf55170af","doc_no":"A.6.1.1.1.2.6.1.2.1.3.1","title":"Spark’s Operation Of Spark Liquidity Layer And Agreement Regarding Encumbrance Ratio","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3744,"content":"Spark will continue to operate the Spark Liquidity Layer and agrees to stay at or below a 90% Encumbrance Ratio. See [A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9).","contentHash":"4293109e6346b10383a72b43cfefad0acb475061c9cc327b01d8aca8618d6859","addressRefs":[]},"ed9602b1-c7fe-4e2b-b4c4-37a1fd21fafd":{"id":"ed9602b1-c7fe-4e2b-b4c4-37a1fd21fafd","doc_no":"A.6.1.1.1.2.6.1.2.1.3.2","title":"Spark’s Total Risk Capital (TRC) Management Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3745,"content":"As operators of the Spark Liquidity Layer, Spark automatically inherits, and is subject to, the base class of operational requirements related to Total Risk Capital management defined in [A.2.2.9.1.1.3.2.1.2 - Primes’ Total Risk Capital (TRC) Management](3af8a3a2-25e5-44b3-87a4-7df1f2712685). Modifications to the base operational logic automatically propagate to the Spark Artifact.","contentHash":"3b7cf0de350d60a397d9e3a9b7d8de43ea78489837b4d9200cfa6ca45dc28888","addressRefs":[]},"f6c90935-4266-4987-9060-d1f1675ff24b":{"id":"f6c90935-4266-4987-9060-d1f1675ff24b","doc_no":"A.6.1.1.1.2.6.1.2.2","title":"Spark Liquidity Layer Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3746,"content":"The documents herein describe common operational procedures for the Spark Liquidity Layer applicable across multiple Instances.","contentHash":"2afe09b26b06a857d3c6eef80a5a8b1eeb43842990049916788fc81e678ba3ea","addressRefs":[]},"7f69f60f-a0eb-429e-a8a7-228b42b456a2":{"id":"7f69f60f-a0eb-429e-a8a7-228b42b456a2","doc_no":"A.6.1.1.1.2.6.1.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3747,"content":"The documents herein define the protocol for routine ongoing management of the Spark Liquidity Layer and its active Instances.","contentHash":"5c7423f7aa41bc106420438590a368fdcc52255d569f824b2dc653d4e8f8ad15","addressRefs":[]},"e72290a8-e1af-494b-931d-778f5d697d4d":{"id":"e72290a8-e1af-494b-931d-778f5d697d4d","doc_no":"A.6.1.1.1.2.6.1.2.2.1.1","title":"Role Hierarchy And Permissions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3748,"content":"The documents herein defines roles (Admin, Relayer, Freezer) and their responsibilities/permissions for managing the Spark Liquidity Layer.","contentHash":"2165ef72783d357cd67ddc57fd336377626d1d55ff6498a6ee202fd3294165d4","addressRefs":[]},"da2e149b-e70c-4373-94da-6da6c4c26048":{"id":"da2e149b-e70c-4373-94da-6da6c4c26048","doc_no":"A.6.1.1.1.2.6.1.2.2.1.1.1","title":"Default Admin Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3749,"content":"The admin role (`DEFAULT_ADMIN_ROLE`) is the role that can grant and revoke any role, including itself and all other roles defined in the contract. The admin role is also used for general admin functions in all contracts. This role is fully controlled by Sky Governance via the Spark Proxy.\n\n```\nconstructor(address admin) {\n        _grantRole(DEFAULT_ADMIN_ROLE, admin);\n```","contentHash":"5efed7d823a6f74ec6ed765cc64f520ee886bac1e2ed323e7b3f75be5d4a3a6f","addressRefs":[]},"cc2f7956-90ce-4025-9642-bfe403dc3ccc":{"id":"cc2f7956-90ce-4025-9642-bfe403dc3ccc","doc_no":"A.6.1.1.1.2.6.1.2.2.1.1.2","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3750,"content":"The `RELAYER_ROLE` is the address for the Spark Liquidity Layer ALM Planner off-chain system that calls functions on `Controller` contracts to perform actions on behalf of the `ALMProxy` contract. The Relayer Role may be granted to an address by any address holding the `DEFAULT_ADMIN_ROLE`. The Relayer Role may be removed from an address by any address holding the `DEFAULT_ADMIN_ROLE` or the `FREEZER_ROLE`.","contentHash":"477d5b83ac7ed0e2599e30964db1d3d5c49774a19baff79f9a6174b1715adde1","addressRefs":[]},"846e460d-db29-4ad0-82f7-5174fcb9b195":{"id":"846e460d-db29-4ad0-82f7-5174fcb9b195","doc_no":"A.6.1.1.1.2.6.1.2.2.1.1.3","title":"ALM Controller Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3751,"content":"The `ALM_CONTROLLER_ROLE` is the address of the role that can call the `call` functions on the `ALMProxy` contract and update `RateLimits` contract. It includes the `MainnetController` and `ForeignController` contracts. ALM Controller contracts are accessed and modified via the Relayer Role.","contentHash":"2338ec34a7da2944765e15ca9792b0c4ec0cffcbf72218d25d3c57bffdc821f2","addressRefs":[]},"02a614ea-1d6b-4197-b39b-49de676092cb":{"id":"02a614ea-1d6b-4197-b39b-49de676092cb","doc_no":"A.6.1.1.1.2.6.1.2.2.1.1.4","title":"Freezer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3752,"content":"The `FREEZER_ROLE` is the address of the emergency role that can remove a compromised Relayer.","contentHash":"5613adb996d95581a1f27d5ec22a32a62f59e9d8f62e6ff43f248f6bd75f410f","addressRefs":[]},"92e30e64-76dd-493d-be14-2088892e11b1":{"id":"92e30e64-76dd-493d-be14-2088892e11b1","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2","title":"Controller Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3753,"content":"The documents herein describe the purpose and operational use of key functions within Spark Liquidity Layer `MainnetController` and `ForeignController` contracts: USDS management (mint/burn USDS), Asset Transfer Management (direct transfers, protocol deposits/withdrawals), Cross-chain Operations (CCTP bridging).","contentHash":"f2fd4ada9035ba286c4caa9739362da63564abf22de8f920b86916fe3a3f9986","addressRefs":[]},"9d9c441e-b5c9-4d5a-a776-b89d6b85f568":{"id":"9d9c441e-b5c9-4d5a-a776-b89d6b85f568","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1","title":"Mainnet Controller Contract Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3754,"content":"The documents herein define the functions controlled by the Controller contract for Spark Liquidity Layer operations on Ethereum Mainnet.","contentHash":"15a11d2f8a18e6b7092926e2920598d1e4f5fb03af723318b989467d159230d0","addressRefs":[]},"1c6ea8a1-71a7-4d56-ba74-68de7ed59f2b":{"id":"1c6ea8a1-71a7-4d56-ba74-68de7ed59f2b","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.1","title":"Admin Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3755,"content":"The documents herein define the operations performed by the `DEFAULT_ADMIN_ROLE` within the `MainnetController` contract.","contentHash":"ef2dd126343ef27e44dac91a9fa8ab84a7f77022ba19f45cde2dc73282dee02e","addressRefs":[]},"6e08ac53-a63b-4c23-8a52-7644f25cb8cf":{"id":"6e08ac53-a63b-4c23-8a52-7644f25cb8cf","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.1.1","title":"Set The Mint Recipient","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3756,"content":"The documents herein define the process to set the `mintRecipient` for a specific `destinationDomain`. This is used in cross-chain transfers to specify the address that will receive minted tokens on the target chain.","contentHash":"ac97c3006b959eb2702d4a42dcb6fb6a4184ae1b18c18f6c4faa299dfe270cca","addressRefs":[]},"a6f085f5-4670-443e-ad83-b538527b8c24":{"id":"a6f085f5-4670-443e-ad83-b538527b8c24","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.1.1.1","title":"Admin Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3757,"content":"The operator must ensure they are working as an Admin. Only the `DEFAULT_ADMIN_ROLE` is allowed to `setMintRecipient`.\n\n```\nfunction setMintRecipient(uint32 destinationDomain, bytes32 mintRecipient)\n        external\n        onlyRole(DEFAULT_ADMIN_ROLE)\n```","contentHash":"3f1c51fb46e2051ba3377fc73d9219df217b504bb94821996593aacc403ca1fa","addressRefs":[]},"0d7bbcaf-477f-4b07-bb8b-fca7cf316f57":{"id":"0d7bbcaf-477f-4b07-bb8b-fca7cf316f57","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.1.1.2","title":"Associate Mint Recipient With Domain","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3758,"content":"The operator must associate the `mintRecipient` with the `destinationDomain` such that any tokens minted on this domain will go to this recipient.\n\n```\n{\n        mintRecipients[destinationDomain] = mintRecipient;\n```","contentHash":"ddd587772be59ecbcba6eb93f151952b736aa8017d6598b7e0226d9e66d62f66","addressRefs":[]},"6ced376c-a922-4626-82ea-ab6001a17257":{"id":"6ced376c-a922-4626-82ea-ab6001a17257","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.1.1.3","title":"Emit Event To Logs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3759,"content":"The operator must emit the event to the blockchain logs.\n\n```\n        emit MintRecipientSet(destinationDomain, mintRecipient);\n    }\n```","contentHash":"415b45bf98a676ded63a74f18970eba4e7c85abcb498ac8d005e164fa3df3fa4","addressRefs":[]},"3d1d2f04-1f4d-4af8-9dcb-2e8dfd3aa704":{"id":"3d1d2f04-1f4d-4af8-9dcb-2e8dfd3aa704","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2","title":"Relayer Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3760,"content":"The documents herein define the operations performed by the `RELAYER_ROLE` within the `MainnetController` contract.","contentHash":"989229be02e35772e8a77e872cb3a4a77ae1b104064f991b448513ef70d3ee1f","addressRefs":[]},"55532d77-304b-4844-ba7f-781c014e99fa":{"id":"55532d77-304b-4844-ba7f-781c014e99fa","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1","title":"Core Vault Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3761,"content":"The documents herein define the operations that are performed to maintain the desired level of liquidity and debt balance of the Spark Liquidity Layer.","contentHash":"a35bd25a8d153162eeba9b50964db6a81c9eee350eda2c6235712e551f68235b","addressRefs":[]},"8e62cfdb-189c-4ea1-88e0-a1eaf5c55716":{"id":"8e62cfdb-189c-4ea1-88e0-a1eaf5c55716","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1","title":"Mint USDS","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3762,"content":"The documents herein define the steps for an operator to `mint` USDS from the Sky Allocation Vault to the Spark ALM Proxy.","contentHash":"18b6bd40fd85e7884ebdc56f188d29681d9610f0cc473e1cb1e5a8d19268dc62","addressRefs":[]},"a0424398-100e-4c6e-9691-f59efbda6fcd":{"id":"a0424398-100e-4c6e-9691-f59efbda6fcd","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3763,"content":"The operator must ensure they are working as a `Relayer`. Only the `RELAYER` role is allowed to `mintUSDS`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction mintUSDS(uint256 usdsAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"0699ff9050f80c6ee37bd3244def5da428b2974d6781bcf0761bb8f3c7ebfe40","addressRefs":[]},"4414c19c-3194-4481-8db1-42b6dd718c5a":{"id":"4414c19c-3194-4481-8db1-42b6dd718c5a","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3764,"content":"The operator must ensure the `RateLimits` allow for minting the required amount.\n\n` rateLimited(LIMIT_USDS_MINT, usdsAmount)`","contentHash":"da490100c1b298300ed302bb31ffd2e60392211f985d89fc86e9fa10679e1de5","addressRefs":[]},"3d84f6a0-5bcf-4140-913b-072a97663b07":{"id":"3d84f6a0-5bcf-4140-913b-072a97663b07","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.3","title":"Mint USDS To Buffer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3765,"content":"The operator must call the `MainnetController` contract to `mint` USDS into the Buffer.","contentHash":"bcb64f3f855b3d4068265a5b4ea78963fb8d3b08148e6c758ff2e2da8968d3ac","addressRefs":[]},"c7b2c565-d1b5-4239-9139-89762423443d":{"id":"c7b2c565-d1b5-4239-9139-89762423443d","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.3.1","title":"Encode Mint Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3766,"content":"The operator must encode the `mint` function call, using `abi.encodeCall` with the address `vault` from which USDS will be `drawn`, and the `amount` of USDS to `mint`.","contentHash":"4c99b77c0615870f8869ac156e6e9d96d83b9338dd4da95ce353cbf79acc52ac","addressRefs":[]},"a171748b-6070-4b76-bda0-2268e2e1938d":{"id":"a171748b-6070-4b76-bda0-2268e2e1938d","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.3.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3767,"content":"The operator must send the encoded call using `proxy.doCall()` to the `draw` function of the vault contract.\n\n```\n    {\n        // Mint USDS into the buffer\n        proxy.doCall(\n            address(vault),\n            abi.encodeCall(vault.draw, (usdsAmount))\n        );\n```","contentHash":"3480937f177e06db1a50f4d8894bd5a83f2c4e58875f17c72868f7197b249374","addressRefs":[]},"a35cb461-3087-4093-8a06-ed7c69a11385":{"id":"a35cb461-3087-4093-8a06-ed7c69a11385","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.4","title":"Transfer USDS To ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3768,"content":"The operator must call the `MainnetController` contract to `transfer` USDS from the Buffer to the ALM Proxy.","contentHash":"6b72d63683b9d08af48b249473750c262951b1f684a9d7556a750574b1964810","addressRefs":[]},"b46d9837-cca9-4d36-8363-a32379d28f93":{"id":"b46d9837-cca9-4d36-8363-a32379d28f93","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.4.1","title":"Encode Transfer Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3769,"content":"The operator must encode the `transfer` function call, using `abi.encodeCall` with the `buffer` address USDS will be transferred from, the `proxy` address that will receive USDS (i.e. ALM Proxy), and the `amount` of USDS to `transfer`.","contentHash":"588f50bd1c7e39dac696ec016acc75209ce80993fc3aa9bc0f3657fa1ea4df69","addressRefs":[]},"39ed68c1-6341-44a3-a8ee-4ae982acf341":{"id":"39ed68c1-6341-44a3-a8ee-4ae982acf341","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.1.4.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3770,"content":"The operator must send the encoded call using `proxy.doCall()` to the `transferFrom` function of the USDS contract.\n\n```\n        // Transfer USDS from the buffer to the proxy\n        proxy.doCall(\n            address(usds),\n            abi.encodeCall(usds.transferFrom, (buffer, address(proxy), usdsAmount))\n        );\n    }\n```","contentHash":"67f2acb5f4b95d74069aa58e6ab32c49407ade41afce41f0638ae6bc331b9cde","addressRefs":[]},"fc8b57fd-c0c8-422d-b0a9-e124b3cac439":{"id":"fc8b57fd-c0c8-422d-b0a9-e124b3cac439","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2","title":"Burn USDS","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3771,"content":"The documents herein define the steps for an operator to return and then `burn` Spark’s USDS debt in the Sky Allocation Vault.","contentHash":"7b6fe310b06b30314fcca0f9261ca6f66605457d63d932204dd7e763871e97a2","addressRefs":[]},"bcb7d73b-3f6d-4b79-8c8f-6cbbb438dcf3":{"id":"bcb7d73b-3f6d-4b79-8c8f-6cbbb438dcf3","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3772,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `burnUSDS`. They must also ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction burnUSDS(uint256 usdsAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"1d6c1d3f6bcf55c3bb899a25bc5960733f56aade04c445e94a4a2e6f6f796587","addressRefs":[]},"efbe3b04-022f-4181-b7c9-402728536931":{"id":"efbe3b04-022f-4181-b7c9-402728536931","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3773,"content":"The operator must ensure the `RateLimits` allow for minting the required amount.\n\n`cancelRateLimit(LIMIT_USDS_MINT, usdsAmount)`","contentHash":"95e303d09b876fff8c521a255f110a01372512b9fada00d5337744afcb016fc0","addressRefs":[]},"33dfd992-2e15-4af6-9331-d15f62f55045":{"id":"33dfd992-2e15-4af6-9331-d15f62f55045","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.3","title":"Transfer USDS To Buffer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3774,"content":"The operator must call the `MainnetController` to `transfer` USDS from the ALM Proxy to the Buffer.","contentHash":"401cc3785586d8544ed0df3293259456266e6e392b9c60870f982e1f2585438d","addressRefs":[]},"14dd94bf-536e-444a-8d92-e5bb186b3a9f":{"id":"14dd94bf-536e-444a-8d92-e5bb186b3a9f","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.3.1","title":"Encode Transfer Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3775,"content":"The operator must encode the `transfer` function call, using `abi.encodeCall` with the `buffer` address USDS will be transferred to, and the `amount` of USDS to `transfer`.","contentHash":"9d86e385ddb6e6cf057c06109ebb52031cbeae824027aea8dc353fc097116408","addressRefs":[]},"a0dff4ff-a21f-40a4-b774-c0483ac9c90d":{"id":"a0dff4ff-a21f-40a4-b774-c0483ac9c90d","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.3.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3776,"content":"The operator must send the encoded call using `proxy.doCall()` to the `transfer` function of the USDS contract.\n\n```\n     {\n        // Transfer USDS from the proxy to the buffer\n        proxy.doCall(\n            address(usds),\n            abi.encodeCall(usds.transfer, (buffer, usdsAmount))\n        );\n```","contentHash":"61da017b0e9ee747ab185acb44b9168cd5b506dcafa82c29fa2d544d9ee3f47d","addressRefs":[]},"807a0401-2c4d-46f3-b7c7-aba18e0bd8c1":{"id":"807a0401-2c4d-46f3-b7c7-aba18e0bd8c1","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.4","title":"Burn USDS","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3777,"content":"The operator must call the `MainnetController` contract to `burn` USDS.","contentHash":"dfe3eea25e20ed18f64619ce68bf982eda36d69d0bcb5c053c5da3b304b09708","addressRefs":[]},"6d28bbc7-7124-4eb3-a594-8684214b5ecb":{"id":"6d28bbc7-7124-4eb3-a594-8684214b5ecb","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.4.1","title":"Encode Wipe Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3778,"content":"The operator must encode the `wipe` function call, using `abi.encodeCall` with the address `vault` from which USDS will be `burned`, and the `amount` of USDS to `burn`.","contentHash":"c846ae13325433633f5f11f1013ca3576a039a683d6cb22288256ccb74b63212","addressRefs":[]},"5db8d9fd-015e-414e-a35e-450fea7f9e8b":{"id":"5db8d9fd-015e-414e-a35e-450fea7f9e8b","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2.4.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3779,"content":"The operator must send the encoded call using `proxy.doCall()` to the `wipe` function of the vault contract.\n\n```\n// Burn USDS from the buffer\n        proxy.doCall(\n            address(vault),\n            abi.encodeCall(vault.wipe, (usdsAmount))\n        );\n    }\n```","contentHash":"ad225ee32d721ae7b398858b289c8ab16409c0bf14d054985de370fd758cf722","addressRefs":[]},"e386a0df-9e0b-4ffd-9879-49131f795b0b":{"id":"e386a0df-9e0b-4ffd-9879-49131f795b0b","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.2","title":"ERC-4626 Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3780,"content":"The documents herein define the general Spark Liquidity Layer operational procedures for interacting with ERC4626-compliant tokenized vaults. ERC4626 is a standard interface for vaults representing shares of an underlying ERC20 token. Spark Liquidity Layer can integrate with various ERC4626 vaults (e.g., Fluid Finance).","contentHash":"e4d28b6c00835e174c409024e90a007b10884f0ed37f5004f295cd48de77f02e","addressRefs":[]},"862f4064-47e5-4f76-908d-64edfcfe0ddd":{"id":"862f4064-47e5-4f76-908d-64edfcfe0ddd","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.1","title":"General Deposit to ERC-4626 Tokens Procedure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3781,"content":"This document defines the steps for an operator to deposit assets from the ALM Proxy to the ERC-4626 vault to receive yield-bearing shares.\n\n- The Spark Liquidity Layer Operator, acting as `RELAYER`, initiates a deposit.\n- Pre-conditions are checked: Spark Liquidity Layer contract `isActive`, ALM Proxy has sufficient underlying asset, and the deposit amount is within instance-specific `RateLimits` (defined in the relevant Instance Configuration Document).\n- The Spark Liquidity Layer Operator approves the target ERC4626 vault (identified by its `token` address in the Instance Configuration Document) to spend the underlying `asset` from the ALM Proxy.\n- The Spark Liquidity Layer Operator calls the `deposit(uint256 amount, address receiver)` function on the target ERC4626 vault, specifying the `amount` of underlying asset and the ALM `proxy` as the receiver of vault shares.\n- The number of shares received is recorded.\n- For detailed call structures, instance-specific parameters (vault address, asset address, rate limits), and operational examples, refer to the specific ERC4626 Instance Configuration Document (ICD) (e.g., [A.6.1.1.1.2.6.1.3.1.5.1.3 - Instance-specific Operational Processes](3bc424bf-079e-4b6b-8749-58c942c7d57b) or other relevant ERC4626 ICDs).","contentHash":"fba37969f03fecb1d70f757b4dc1f095b3425c087c5e2b34c71a5804027cc5ff","addressRefs":[]},"e797d1cc-9161-4b7a-8c16-db20a026d001":{"id":"e797d1cc-9161-4b7a-8c16-db20a026d001","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.2","title":"General Withdraw from ERC-4626 Tokens Procedure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3782,"content":"This document defines the steps for an operator to withdraw a yield-earning balance from the ERC-4626 vault to the ALM Proxy.\n\n- The Spark Liquidity Layer Operator, acting as `RELAYER`, initiates a withdrawal.\n- Pre-conditions are checked: Spark Liquidity Layer contract `isActive`, ALM Proxy has sufficient shares of the ERC4626 vault token, and the withdrawal amount is within instance-specific `RateLimits` (defined in the relevant ICD).\n- The Spark Liquidity Layer Operator calls the `withdraw(uint256 assets, address receiver, address owner)` function on the target ERC4626 vault, specifying the `amount` of underlying assets to withdraw, with the ALM `proxy` as both `receiver` (of assets) and `owner` (of shares being burned).\n- The number of shares burned is recorded.\n- For detailed call structures, instance-specific parameters, and operational examples, refer to the specific ERC4626 Instance Configuration Document.","contentHash":"98444cd6e69cb93a3742ee4c11e1a78a333d326fdb57e287185e50d3feb6c88f","addressRefs":[]},"ed774ab7-c761-444b-963d-7407bf91e243":{"id":"ed774ab7-c761-444b-963d-7407bf91e243","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.3","title":"General Redeem from ERC-4626 Tokens Procedure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3783,"content":"This document defines the steps for an operator to redeem yield-bearing shares from the ERC-4626 vault, receiving the corresponding amount of underlying assets into the ALM Proxy.\n\n- The Spark Liquidity Layer Operator, acting as `RELAYER`, initiates a redemption of shares.\n- Pre-conditions are checked: Spark Liquidity Layer contract `isActive`, ALM Proxy has sufficient shares of the ERC4626 vault token.\n- The Spark Liquidity Layer Operator calls the `redeem(uint256 shares, address receiver, address owner)` function on the target ERC4626 vault, specifying the number of `shares` to redeem, with the ALM `proxy` as both `receiver` (of assets) and `owner` (of shares being redeemed).\n- The amount of underlying assets received is recorded, and relevant `RateLimits` (for withdrawal) are updated.\n- For detailed call structures, instance-specific parameters, and operational examples, refer to the specific ERC4626 Instance Configuration Document.","contentHash":"4d53196bc5d815848d482c184befc126453ba4737ec57874a4bb01f6757fa37c","addressRefs":[]},"9922dcf0-4562-445b-9a46-712f677cce64":{"id":"9922dcf0-4562-445b-9a46-712f677cce64","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.3","title":"Aave Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3784,"content":"The documents herein describe the general Spark Liquidity Layer operational procedures for depositing to and withdrawing from Aave lending pools.","contentHash":"a1e7b30da1d990b7b94474b00a29f3924a6fedd9bd85972ff1ff577fc6390a4a","addressRefs":[]},"316008c1-0c1f-487a-a5bf-1966e86fb946":{"id":"316008c1-0c1f-487a-a5bf-1966e86fb946","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.3.1","title":"General Deposit to Aave ATokens Procedure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3785,"content":"This document defines the steps for an operator to deposit to Aave lending pools.\n\n- The Spark Liquidity Layer Operator, acting as `RELAYER`, initiates a deposit to an Aave instance.\n- Pre-conditions are checked: Spark Liquidity Layer contract `isActive`, ALM Proxy has sufficient underlying asset, and the deposit amount is within instance-specific `RateLimits` (defined in the relevant Aave ICD).\n- The Spark Liquidity Layer Operator identifies the `underlying` asset address and Aave `pool` address from the specific Aave ICD.\n- The Spark Liquidity Layer Operator approves the Aave `pool` to spend the `underlying` asset from the ALM Proxy.\n- The Spark Liquidity Layer Operator calls the `supply(address asset, uint256 amount, address onBehalfOf, uint16 referralCode)` function on the Aave `pool`, providing the `underlying` asset address, `amount`, ALM `proxy` address (as `onBehalfOf`), and referral code (typically 0).\n- The ALM Proxy receives `aTokens` representing the deposited assets.\n- For detailed call structures, instance-specific parameters (aToken address, underlying asset address, pool address, rate limits), and operational examples, refer to the specific Aave Instance Configuration Document (ICD) (e.g., [A.6.1.1.1.2.6.1.3.1.2.1.3 - Instance-specific Operational Processes](7895798c-50e2-4fa6-b4e9-5b9f259f822d) or other relevant Aave ICDs).","contentHash":"d6d5e5d9605c880fa9faae6728c7d4a413b35f1d9bb6bcdc208b81b0b3a78b05","addressRefs":[]},"6e75a2bd-70b7-4081-bb9f-39cf6b321066":{"id":"6e75a2bd-70b7-4081-bb9f-39cf6b321066","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.3.2","title":"General Withdraw from Aave ATokens Procedure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3786,"content":"This document defines the steps for an operator to withdraw from Aave lending pools.\n\n- The Spark Liquidity Layer Operator, acting as `RELAYER`, initiates a withdrawal from an Aave instance.\n- Pre-conditions are checked: Spark Liquidity Layer contract `isActive`, ALM Proxy has sufficient `aTokens` for the instance, and the withdrawal amount is within instance-specific `RateLimits` (defined in the relevant Aave ICD).\n- The Spark Liquidity Layer Operator identifies the `underlying` asset address and Aave `pool` address from the specific Aave ICD.\n- The Spark Liquidity Layer Operator calls the `withdraw(address asset, uint256 amount, address to)` function on the Aave `pool`, providing the `underlying` asset address, `amount` to withdraw, and the ALM `proxy` address (as `to`).\n- The amount of underlying assets withdrawn is recorded, and relevant `RateLimits` are updated.\n- For detailed call structures, instance-specific parameters, and operational examples, refer to the specific Aave ICD.","contentHash":"9f87710397381202cc4cc0bc65413a7bf4e21f49422acea0ede9bf8e52e289de","addressRefs":[]},"70785812-c0aa-4efc-8790-093e6c23ef52":{"id":"70785812-c0aa-4efc-8790-093e6c23ef52","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4","title":"PSM Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3787,"content":"The documents herein define the swap operations performed by the Spark Liquidity Layer in the PSM.","contentHash":"db8e6871f23c9151483787e83cc3746606cee607c81ea45175d0433c0438fda1","addressRefs":[]},"f6b656c2-dc00-4c07-9452-34b01ef2e1ea":{"id":"f6b656c2-dc00-4c07-9452-34b01ef2e1ea","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1","title":"Swap USDS to USDC","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3788,"content":"The documents herein define a series of operations for an operator to `swap` USDS to USDC through the PSM.","contentHash":"564fc251dbabe1de4723b87aa7179a9f9f901ef1b48e8c75549e98fefb798c1b","addressRefs":[]},"a84b5647-13f5-4a47-92fa-a1de76059c31":{"id":"a84b5647-13f5-4a47-92fa-a1de76059c31","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3789,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `swapUSDSToUSDC`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction swapUSDSToUSDC(uint256 usdcAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"c3b17d9e48f51665258702f1a188bc93d15edf34ac754e1de087b8b04a254d24","addressRefs":[]},"a1dddb9b-93cf-4064-816e-928f761a1239":{"id":"a1dddb9b-93cf-4064-816e-928f761a1239","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3790,"content":"The operator must ensure that `RateLimits` allows for swapping the required USDS amount to USDC.\n\n`rateLimited(LIMIT_USDS_TO_USDC, usdcAmount)`","contentHash":"517eec48e7b8c02b7d4828b7745f4edc49f59204a5fd66079cece35c481809ec","addressRefs":[]},"6eebacbd-ab75-4ecc-ac3b-5ff882dd4037":{"id":"6eebacbd-ab75-4ecc-ac3b-5ff882dd4037","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.3","title":"Convert To 18 Token Format","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3791,"content":"The operator must convert USDC amounts to an 18 token decimal format using `psmTo18ConversionFactor`.\n\n```\n{\n        uint256 usdsAmount = usdcAmount * psmTo18ConversionFactor;\n```","contentHash":"79d74874f2de3ba98c3736afa0d281d0e34dfc2023b2a2004ca7732eb0bfd435","addressRefs":[]},"01af3b1c-a370-4ede-8f8c-c915a5885591":{"id":"01af3b1c-a370-4ede-8f8c-c915a5885591","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.4","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3792,"content":"The operator must ensure that the ALM Proxy has enough USDS balance to `swap` for the required USDC amount.","contentHash":"46838f3aa1e3d6ddd36efe61d71f57682926a235ff432405904e66ec4d9e3371","addressRefs":[]},"f3f447b4-22c4-4e49-a128-1672c38a2fb9":{"id":"f3f447b4-22c4-4e49-a128-1672c38a2fb9","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.5","title":"Approve Contract Spend","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3793,"content":"The operator must approve the `daiUsds` contract to spend the `usdsAmount` on behalf of the `proxy`. `daiUsds` is a contract that facilitates a 1:1 swap between USDS and DAI.\n\n```\nproxy.doCall(\n            address(usds),\n            abi.encodeCall(usds.approve, (address(daiUsds), usdsAmount))\n        );\n```","contentHash":"aa75d340b6e82041989fde64dfe26f372f7689d2d0c8c5771b8c6c71b60fb425","addressRefs":[]},"da1d0829-5676-4713-988f-13eea2a6924f":{"id":"da1d0829-5676-4713-988f-13eea2a6924f","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.6","title":"Swap USDS To DAI","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3794,"content":"The operator must swap USDS to DAI. USDS is swapped to DAI in a 1:1 ratio through the `daiUsds` contract and sent back to the `proxy`.\n\n```\nproxy.doCall(\n    address(daiUsds),\n    abi.encodeCall(daiUsds.usdsToDai, (address(proxy), usdsAmount))\n);\n```","contentHash":"9d4dc459dc591e4721a2c68533fba01098ebff4de2f7d48c0eaf9c6a1dc15f81","addressRefs":[]},"e5b56658-1fe0-4d3f-b911-8e66b9d16a6e":{"id":"e5b56658-1fe0-4d3f-b911-8e66b9d16a6e","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.7","title":"Approve PSM Spend","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3795,"content":"The operator must approve the PSM to spend the newly acquired DAI. The approval is needed for the PSM to be able to `swap` DAI for USDC.\n\n```\nproxy.doCall(\n    address(dai),\n    abi.encodeCall(dai.approve, (address(psm), usdsAmount))\n);\n```","contentHash":"30a5e1ff278c71260ad2598dd8edc8646f1b17d9adfe06780b15b82b3421b4aa","addressRefs":[]},"58bd2f3d-0d7e-41e9-a3f1-43e8deedaea9":{"id":"58bd2f3d-0d7e-41e9-a3f1-43e8deedaea9","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.1.8","title":"Swap DAI To USDC","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3796,"content":"The operator must swap DAI to USDC. DAI is swapped to USDC in the PSM at a 1:1 ratio with no fee, using the `buyGemNoFee` function and return USDC to the `proxy`.\n\n```\n        proxy.doCall(\n            address(psm),\n            abi.encodeCall(psm.buyGemNoFee, (address(proxy), usdcAmount))\n        );\n    }\n```","contentHash":"7a7036d3a0062c6355098fa48214aea708091386738b0400901a36d15cf10924","addressRefs":[]},"8b7c4526-ea6a-488d-925a-884704a7bc80":{"id":"8b7c4526-ea6a-488d-925a-884704a7bc80","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2","title":"Swap USDC to USDS","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3797,"content":"The documents herein define a series of operations for an operator to `swap` USDC to USDS through the PSM.","contentHash":"f55bbceca04d743a7ae5c9c46fa9d3d34fd14dab41a5f282da781a788be9ba83","addressRefs":[]},"bceb6404-8060-4bb7-86f5-8a5c98f6ebea":{"id":"bceb6404-8060-4bb7-86f5-8a5c98f6ebea","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3798,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `swapUSDCToUSDS`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction swapUSDCToUSDS(uint256 usdcAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"f3ee36a72607de63195d31bc66fe14f5dcb34cee78f4d659008d3c4a90cb2306","addressRefs":[]},"084174bc-eaa4-4474-80ca-8a7ab0d21c6e":{"id":"084174bc-eaa4-4474-80ca-8a7ab0d21c6e","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3799,"content":"The operator must ensure that `RateLimits` allows for swapping the required USDC amount to USDS.\n\n`cancelRateLimit(LIMIT_USDS_TO_USDC, usdcAmount)`","contentHash":"4fe17333b51ce4e616f144d362e287fecaeba978eeb9b3f15c12be77f567ae95","addressRefs":[]},"a373fb80-cb38-4564-a386-454604ba5221":{"id":"a373fb80-cb38-4564-a386-454604ba5221","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.3","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3800,"content":"The operator must ensure ALM Proxy has enough USDC balance to `swap` for the required USDS amount.","contentHash":"910b3439932669d61c78560e750ba1140bb6661d2fdce964872093d0c2907261","addressRefs":[]},"b1d47385-8512-475a-8860-9ae927677785":{"id":"b1d47385-8512-475a-8860-9ae927677785","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.4","title":"Approve Contract Spend","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3801,"content":"The operator must approve the PSM to spend USDC. The approval is needed for the PSM to be able to execute a `swap` of USDC.\n\n```\nproxy.doCall(\n    address(usdc),\n    abi.encodeCall(usdc.approve, (address(psm), usdcAmount))\n);\n```","contentHash":"109d7b51f311e7cbfb33a70c06703a4401618fb6de1d01a00ce0ab42e5ec0a64","addressRefs":[]},"f16d98d9-dbba-44ab-8764-445693b81ff5":{"id":"f16d98d9-dbba-44ab-8764-445693b81ff5","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.5","title":"Calculate Swap Limit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3802,"content":"The operator must calculate the `swap` `limit` per transaction. The maximum amount of USDC that can be swapped to DAI in one transaction is calculated based on the DAI balance held by the PSM. `psmTo18ConversionFactor` converts DAI’s 18 token decimals to USDC’s 6 token decimals.\n\n`uint256 limit = dai.balanceOf(address(psm)) / psmTo18ConversionFactor;`","contentHash":"61d1c09ef3218a346d559a17127f79742ded36dde2c5ff55fd7dc96e0ef9270b","addressRefs":[]},"6a6ddd58-9215-4dae-9d34-8bd4622720bd":{"id":"6a6ddd58-9215-4dae-9d34-8bd4622720bd","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.6","title":"Swap USDC To DAI Directly If Possible","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3803,"content":"The operator must perform a `direct swap` feasibility check and `swap` USDC to DAI, if possible. If the `usdcAmount` is less than or equal to the `limit`, a direct swap should be performed. `_swapUSDCToDAI` is called to execute the swap from `USDC` to `DAI`.\n\n```\nif (usdcAmount <= limit) {\n    _swapUSDCToDAI(usdcAmount);\n}\n```","contentHash":"790bda381c653805cda375e135061e899ebaf7b715c38e41b548105814a4a9db","addressRefs":[]},"38e66872-ee2e-49f4-ada4-a1dec515f6d9":{"id":"38e66872-ee2e-49f4-ada4-a1dec515f6d9","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.7","title":"Swap USDC To DAI Iteratively If Needed","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3804,"content":"If `direct swap` is not possible, the operator must perform an `iterative swap` of USDC to DAI with DAI `refilling`.","contentHash":"ee5e385ba0724f63abf9216ac30cf03680fa63685c2787879e0010836a2889ef","addressRefs":[]},"99e4d243-b61f-48b6-b127-b5d1855a849c":{"id":"99e4d243-b61f-48b6-b127-b5d1855a849c","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.8","title":"Split Into Multiple Swaps If Limit Exceeded","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3805,"content":"If the `usdcAmount` exceeds the limit, the operator must split the swap into multiple smaller swaps as follows.\n\n1. The operator must refill the PSM with DAI by calling `psm.fill()`.\n2. The operator must recalculate the limit to see how much USDC can be swapped after the refill.\n3. The operator must swap the maximum possible USDC amount that doesn't exceed the limit.\n4. The operator must update `remainingUsdcToSwap` by subtracting the amount just swapped.\n5. The operator must repeat the process until the full `usdcAmount` is swapped.","contentHash":"1513220c29993c03fc315cd22d728231420a9102d181e899087c81148dc0d209","addressRefs":[]},"5b50fe5d-22a9-4ea4-a9e1-de7feba453a3":{"id":"5b50fe5d-22a9-4ea4-a9e1-de7feba453a3","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.9","title":"Split Into Multiple Swaps If Limit Exceeded","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3806,"content":"If the PSM can't be filled, the transaction reverts with `DssLitePsm/nothing-to-fill`.\n\n```\nelse {\n    uint256 remainingUsdcToSwap = usdcAmount;\n\n    while (remainingUsdcToSwap > 0) {\n        psm.fill();\n\n        limit = dai.balanceOf(address(psm)) / psmTo18ConversionFactor;\n\n        uint256 swapAmount = remainingUsdcToSwap < limit ? remainingUsdcToSwap : limit;\n\n        _swapUSDCToDAI(swapAmount);\n\n        remainingUsdcToSwap -= swapAmount;\n    }\n}\n```","contentHash":"b361b53607cb955315980849416124f17c767e98d8c50f0e441e685a7cff4054","addressRefs":[]},"12b79490-4a18-466b-91fc-45f1a966b78a":{"id":"12b79490-4a18-466b-91fc-45f1a966b78a","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.10","title":"Convert USDC Amount To DAI Amount","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3807,"content":"The operator must convert the USDC amount to the DAI amount, accounting for the token decimal difference.\n\n```\n{\n        uint256 daiAmount = usdcAmount * psmTo18ConversionFactor;\n```","contentHash":"bae4099a43fd4e11d306c82ef102857628a691166a482e1fe164d09d22bc5f31","addressRefs":[]},"3cf7c26f-7c3b-4d32-8610-b935d57721a6":{"id":"3cf7c26f-7c3b-4d32-8610-b935d57721a6","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.11","title":"Approve Contract Spend","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3808,"content":"The operator must approve the `daiUsds` contract to spend the `daiAmount` on behalf of the `proxy`.\n\n```\nproxy.doCall(\n    address(dai),\n    abi.encodeCall(dai.approve, (address(daiUsds), daiAmount))\n);\n```","contentHash":"8558eaa3103ec44c188810c3642f41b9f5c74c386af6e06abbc7f35df8b21072","addressRefs":[]},"25fac618-a634-4762-983d-c3451e690f5f":{"id":"25fac618-a634-4762-983d-c3451e690f5f","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2.12","title":"Swap DAI to USDS","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3809,"content":"The operator must swap DAI to USDS. DAI is swapped to USDS at a 1:1 ratio through the `daiUsds` contract and sent back to the `proxy`.\n\n```\nproxy.doCall(\n            address(daiUsds),\n            abi.encodeCall(daiUsds.daiToUsds, (address(proxy), daiAmount))\n        );\n    }\n```","contentHash":"ed1825d2b0588ecb2bd768fca3b52c7c5fd1d7757e70adddf41745ae997b3949","addressRefs":[]},"36748aac-f4af-4c2d-ae4b-0416bc84b680":{"id":"36748aac-f4af-4c2d-ae4b-0416bc84b680","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5","title":"Bridging Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3810,"content":"The documents herein define the operations performed by an operator to bridge liquidity between Ethereum Mainnet and the destination blockchains for the Spark Liquidity Layer.","contentHash":"45b7729ac9c00eca7f326546b40aec7e5ca45f2842122090f6985588888697f2","addressRefs":[]},"956f0941-5121-4dce-99d8-2fd1af00ffa6":{"id":"956f0941-5121-4dce-99d8-2fd1af00ffa6","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1","title":"Bridge USDC Using Circle Cross-Chain Transfer Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3811,"content":"The documents herein define the process to bridge USDC using the Circle Cross-Chain Transfer Protocol.","contentHash":"4eacd6bae394ca7f266b3fe7b7be2efc53a5623ca734b8d34d428be16298fca7","addressRefs":[]},"eb5d0ce2-ae57-4a99-b020-02e611667fbe":{"id":"eb5d0ce2-ae57-4a99-b020-02e611667fbe","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3812,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `transferUSDCToCCTP`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction transferUSDCToCCTP(uint256 usdcAmount, uint32 destinationDomain)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"0e180700955f9f50e48f4ebdd8b5b3ef83e15dc455d58dc8cca2adb5e695a617","addressRefs":[]},"27da6bef-8e24-4aa5-86fc-9b47f1a896e0":{"id":"27da6bef-8e24-4aa5-86fc-9b47f1a896e0","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3813,"content":"The operator must ensure the bridging transaction complies with `RateLimits`. The `LIMIT_USDC_TO_CCTP` parameter enforces a rate limit on total USDC transferred via CCTP. The `LIMIT_USDC_TO_DOMAIN` parameter enforces a rate limit on USDC transferred to a specific `destinationDomain`.\n\n```\nrateLimited(LIMIT_USDC_TO_CCTP, usdcAmount)\n        rateLimited(\n            RateLimitHelpers.makeDomainKey(LIMIT_USDC_TO_DOMAIN, destinationDomain),\n            usdcAmount\n        )\n```","contentHash":"80ca8a33878c6ac56daaf9114bd74553d3a36f9a166fc38f1fbfb2a3d9e45a4e","addressRefs":[]},"469d9616-010c-4648-8fc4-66eeff7398c3":{"id":"469d9616-010c-4648-8fc4-66eeff7398c3","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.3","title":"Verify Mint Recipient","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3814,"content":"** **The operator must verify the `mint` recipient. They must check that a mint recipient (mapping from domain IDs to recipient addresses) is configured for the `destinationDomain`. If no recipient is configured, the transaction will revert with an error message.\n\n```\nbytes32 mintRecipient = mintRecipients[destinationDomain];\nrequire(mintRecipient != 0, \"MainnetController/domain-not-configured\");\n```","contentHash":"d1311696bc7efb9c82f0b38636a68614034e881e95cc998fe07f5993982b22d3","addressRefs":[]},"757267df-e76d-4d58-86e3-218d4e6f9efd":{"id":"757267df-e76d-4d58-86e3-218d4e6f9efd","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.4","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3815,"content":"The operator must ensure the ALM Proxy has enough USDC to cover the amount instructed in the transfer.","contentHash":"86c9757fb31ee65e7a0fcbf1419c837cb546a8d19fb65e1ae9304db6d7ca49bc","addressRefs":[]},"f7ef5ebb-e30e-4941-918c-63706690b7e0":{"id":"f7ef5ebb-e30e-4941-918c-63706690b7e0","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.5","title":"Approve Contract Spend","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3816,"content":"The operator must approve the CCTP to spend USDC on behalf of the `proxy`. This action is necessary for the CCTP contract to initiate the cross-chain transfer.\n\n```\nproxy.doCall(\n    address(usdc),\n    abi.encodeCall(usdc.approve, (address(cctp), usdcAmount))\n);\n```","contentHash":"005da1ac6f8f8f3cbe41114b1dbbf80972e6994731bcaacab1cb82b9d4fb2a27","addressRefs":[]},"ea3d54cc-49af-47e6-a11c-b9055f72db75":{"id":"ea3d54cc-49af-47e6-a11c-b9055f72db75","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.6","title":"Initiate USDC Transfer Through CCTP","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3817,"content":"The operator must initiate the USDC transfer through CCTP.","contentHash":"44b75d47f1932784177c258a4b4fe6f9a77e73378ed3af78beca83b1ede6b440","addressRefs":[]},"b25fcca3-374b-408d-9715-bb514ee209b1":{"id":"b25fcca3-374b-408d-9715-bb514ee209b1","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.6.1","title":"Check CCTP Transfer Limit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3818,"content":"The operator must check the `transfer limit`. They must retrieve the maximum amount of USDC that can be transferred in a single CCTP message. This limit is fetched from the `localMinter` contract associated with CCTP.\n\n`uint256 burnLimit = cctp.localMinter().burnLimitsPerMessage(address(usdc));`","contentHash":"f1fa29bffd369b2c83b8bb8274f05375d78d664b0767c5401e39bd7cc2f411a6","addressRefs":[]},"22cb4839-7520-435f-b99b-086446d6a64a":{"id":"22cb4839-7520-435f-b99b-086446d6a64a","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.6.2","title":"Initiate Single Transaction If Possible","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3819,"content":"If a single transaction is possible within the per-message limit, the operator must initiate the CCTP transfer for the entire USDC amount.\n\n```\n {\n    _initiateCCTPTransfer(usdcAmount, destinationDomain, mintRecipient);\n}\n```","contentHash":"2b1af8a07644fe97e444f09db04b76b6fef901f4d7adb06dae0bea3a744c373d","addressRefs":[]},"6423437d-d062-4a4f-ac03-7f056938d3c6":{"id":"6423437d-d062-4a4f-ac03-7f056938d3c6","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.6.3","title":"Initiate Smaller Transactions If Needed","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3820,"content":"If `usdcAmount` exceeds the per-message limit, the transfer must be split into multiple smaller batches executing the following loop until the remaining amount is less than or equal to the limit.\n\n1. The operator must transfer the maximum allowed (`burnLimit`) using `_initiateCCTPTransfer`.\n2. The operator must reduce the remaining `usdcAmount` by the `burnLimit`.\n\n```\nwhile (usdcAmount > burnLimit) {\n    _initiateCCTPTransfer(burnLimit, destinationDomain, mintRecipient);\n    usdcAmount -= burnLimit;\n}\n```","contentHash":"967990c142695eaec1c5c6e697247f7d4812609ca4db7a5d60594de5d37d9fcb","addressRefs":[]},"fd4f7715-ce73-4906-a9ed-cfdcc905cccb":{"id":"fd4f7715-ce73-4906-a9ed-cfdcc905cccb","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1.6.4","title":"Send Remaining USDC","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3821,"content":"The operator must send the remaining USDC amount (if applicable). If there is any `usdcAmount` left after the loop, they must send the remaining amount in a single transfer, ensuring the entire amount is transferred, even if it didn't divide evenly by the `burnLimit`.\n\n```\nif (usdcAmount > 0) {\n    _initiateCCTPTransfer(usdcAmount, destinationDomain, mintRecipient);\n}\n```","contentHash":"4d86cf4426e2e4ef3e50a136b6472b303f8da5f973da773add4387a9d64fc57d","addressRefs":[]},"46502b5d-e272-4aca-a979-6dce6f9230d8":{"id":"46502b5d-e272-4aca-a979-6dce6f9230d8","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.2","title":"Bridge USDS / sUSDS Using OP Token Bridge","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3822,"content":"This document defines the process for an operator to bridge USDS or sUSDS using the OP Token Bridge. This process will be specified in a future iteration of the Spark Artifact.","contentHash":"ccce96eaf9401a0b22c6b56ad7675e7b1782c1d89248c0da13d86b188b0aaa4e","addressRefs":[]},"fc5b3ff6-6458-4e5a-8372-5fada3f51572":{"id":"fc5b3ff6-6458-4e5a-8372-5fada3f51572","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2","title":"Foreign Controller Contract Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3823,"content":"The documents herein define the functions controlled by the Controller contract for Spark Liquidity Layer cross-chain operations on a destination blockchain.","contentHash":"1ab3ff1c411166b60c440732e088dd338a36ab69e1c0d4f101ece780bd71ef1d","addressRefs":[]},"f8e60eae-5df8-45dc-88d9-52168583686d":{"id":"f8e60eae-5df8-45dc-88d9-52168583686d","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.1","title":"Admin Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3824,"content":"The documents herein define the operations performed by the `DEFAULT_ADMIN_ROLE` within the `ForeignController` contract.","contentHash":"a8c2f0ddc892d1dba8570e308458f56c920461cc8461fec7d83db14f5e57741e","addressRefs":[]},"0388bcfb-e181-45f0-9ef6-ee3d7b5daf34":{"id":"0388bcfb-e181-45f0-9ef6-ee3d7b5daf34","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.1.1","title":"Set The Mint Recipient","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3825,"content":"The documents herein define the process for an operator to set a `mintRecipient` for a specific `destinationDomain`. This is used in cross-chain transfers to specify the address that will receive minted tokens on the target chain.","contentHash":"289593e9d63c3dab347385e4000f38669cc5dce1ba1a0884a501756db31f14c6","addressRefs":[]},"80c322c2-586d-46be-9421-acdb69cbc622":{"id":"80c322c2-586d-46be-9421-acdb69cbc622","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.1.1.1","title":"Admin Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3826,"content":"The operator must ensure they are working as an Admin. Only the `DEFAULT_ADMIN_ROLE` is allowed to `setMintRecipient`.\n\n```\nfunction setMintRecipient(uint32 destinationDomain, bytes32 mintRecipient)\n        external\n        onlyRole(DEFAULT_ADMIN_ROLE)\n```","contentHash":"3f1c51fb46e2051ba3377fc73d9219df217b504bb94821996593aacc403ca1fa","addressRefs":[]},"d8c986af-3586-4b01-b03e-eb75cb39bb28":{"id":"d8c986af-3586-4b01-b03e-eb75cb39bb28","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.1.1.2","title":"Associate Mint Recipient With Domain","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3827,"content":"The operator must associate the `mintRecipient` with the `destinationDomain`, meaning that whenever tokens are minted on this domain, they will go to this recipient.\n\n```\n{\n        mintRecipients[destinationDomain] = mintRecipient;\n```","contentHash":"d04aec576caf076cf33203758dd44df5368ae8c570a5d3fc5673322b94a03332","addressRefs":[]},"1bf12913-0a08-4c83-9b05-7fa576ff8cd6":{"id":"1bf12913-0a08-4c83-9b05-7fa576ff8cd6","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.1.1.3","title":"Emit Event To Logs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3828,"content":"The operator must emit the event to the blockchain logs.\n\n```\n        emit MintRecipientSet(destinationDomain, mintRecipient);\n    }\n```","contentHash":"415b45bf98a676ded63a74f18970eba4e7c85abcb498ac8d005e164fa3df3fa4","addressRefs":[]},"7c384ca5-6a23-4539-801a-de35adebc1b7":{"id":"7c384ca5-6a23-4539-801a-de35adebc1b7","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2","title":"Relayer Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3829,"content":"The documents herein define the operations performed by the `RELAYER_ROLE` within the `ForeignController` contract.","contentHash":"c28c1107cff496a31259acef98ead82034ee7e2dbe438e3d824e3b1370327d11","addressRefs":[]},"f9225946-9172-4013-bd04-5e032a998e05":{"id":"f9225946-9172-4013-bd04-5e032a998e05","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.1","title":"ERC-4626 Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3830,"content":"The documents herein define the operations that are performed to deposit and withdraw liquidity from yield-bearing Integrator vaults.","contentHash":"c13fdf2e06261db8e8f67875028ab4de8a33650d6aa2d38602682a2039d55bb7","addressRefs":[]},"8ffb4820-ae4a-408e-a328-1b1a39d6b374":{"id":"8ffb4820-ae4a-408e-a328-1b1a39d6b374","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.1.1","title":"Deposit to ERC-4626 Vault","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3831,"content":"This document defines the steps to deposit assets from the ALM Proxy to the ERC-4626 vault to receive yield-bearing shares.\n\nThe process for depositing to ERC-4626 Tokens on destination blockchain through the `ForeignController` contract is the same as the one for depositing to ERC-4626 Tokens on Ethereum Mainnet through the `MainnetController` contract; see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.1 - General Deposit to ERC-4626 Tokens Procedure](862f4064-47e5-4f76-908d-64edfcfe0ddd).","contentHash":"df22021df89ddc0417190c797839f6f1a727b628c899fb6785906f3317b64729","addressRefs":[]},"c2bbf44a-496c-4cf6-b0f6-25f77e66465b":{"id":"c2bbf44a-496c-4cf6-b0f6-25f77e66465b","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.1.2","title":"Withdraw ERC-4626 Tokens","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3832,"content":"This document defines the steps to withdraw a yield-earning balance from the ERC-4626 vault to the ALM Proxy.\n\nThe process for withdrawing ERC-4626 Tokens on destination blockchain through the `ForeignController` contract is the same as the one for withdrawing ERC-4626 Tokens on Ethereum Mainnet through the `MainnetController` contract, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.2 - General Withdraw from ERC-4626 Tokens Procedure](e797d1cc-9161-4b7a-8c16-db20a026d001).","contentHash":"68a5edb5354b6a6364fecd76268acda263fc2dffd22f5d79a545d2434c455117","addressRefs":[]},"ab5eb90f-1007-4560-a0ea-1c25d433c602":{"id":"ab5eb90f-1007-4560-a0ea-1c25d433c602","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.1.3","title":"Redeem ERC-4626 Tokens","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3833,"content":"This document defines the steps for an operator to redeem yield-bearing shares from the ERC-4626 vault, receiving the corresponding amount of underlying assets into the ALM Proxy.\n\nThe process for redeeming ERC-4626 Tokens on destination blockchain through the `ForeignController` contract is the same as the one for redeeming ERC-4626 Tokens on Ethereum Mainnet through the `MainnetController` contract, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.3 - General Redeem from ERC-4626 Tokens Procedure](ed774ab7-c761-444b-963d-7407bf91e243).","contentHash":"adf882b873d5605029ee369c07a6b4171ffb20ae7f6ccfb5a1c109067684b66d","addressRefs":[]},"652877a2-0d8f-42cf-afef-8721fc988046":{"id":"652877a2-0d8f-42cf-afef-8721fc988046","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.2","title":"Aave Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3834,"content":"The documents herein define the operations that are performed to deposit and withdraw liquidity from yield-bearing Aave deployments.","contentHash":"394b11dead68332d3ce9bfd6dae455949fb385fbb6a768b2e0b832d56d351964","addressRefs":[]},"4b3ec104-dc60-4cb0-8e90-5b96c495c974":{"id":"4b3ec104-dc60-4cb0-8e90-5b96c495c974","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.2.1","title":"Deposit to Aave ATokens","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3835,"content":"This document defines the steps to deposit assets from the ALM Proxy to the Aave pool to receive yield-bearing ATokens.\n\nThe process for depositing to Aave ATokens on destination blockchain through the `ForeignController` contract is the same as the one for depositing to Aave ATokens on Ethereum Mainnet through the `MainnetController` contract, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3.1 - General Deposit to Aave ATokens Procedure](316008c1-0c1f-487a-a5bf-1966e86fb946).","contentHash":"2bba00d5454e7a914e824ef3f580a7c75460047d4c2f73b5d74af4b9ffaf069a","addressRefs":[]},"5b090e5a-a2e7-4548-a1b4-53be86db6516":{"id":"5b090e5a-a2e7-4548-a1b4-53be86db6516","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.2.2","title":"Withdraw Aave ATokens","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3836,"content":"This document defines the steps to withdraw a yield-earning balance from the Aave AToken vaults to the ALM Proxy.\n\nThe process for withdrawing Aave ATokens on destination blockchain through the `ForeignController` contract is the same as the one for withdrawing Aave ATokens on Ethereum Mainnet through the `MainnetController` contract, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3.2 - General Withdraw from Aave ATokens Procedure](6e75a2bd-70b7-4081-bb9f-39cf6b321066).","contentHash":"9198911f70d372fddca7307b0911c52cc4369d1984fc7e75f0577f21c30456d9","addressRefs":[]},"35cf8ecc-ce16-4498-81f5-d96073ec5724":{"id":"35cf8ecc-ce16-4498-81f5-d96073ec5724","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.2.3","title":"Withdraw Aave ATokens","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3837,"content":"This document defines the steps to withdraw a yield-earning balance from the Aave AToken vaults to the ALM Proxy.\n\nThe process for withdrawing Aave ATokens on destination blockchain through the `ForeignController` contract is the same as the one for withdrawing Aave ATokens on Ethereum Mainnet through the `MainnetController` contract, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3.2 - General Withdraw from Aave ATokens Procedure](6e75a2bd-70b7-4081-bb9f-39cf6b321066).","contentHash":"9198911f70d372fddca7307b0911c52cc4369d1984fc7e75f0577f21c30456d9","addressRefs":[]},"6c18d284-b720-49b4-ac11-904d512fc841":{"id":"6c18d284-b720-49b4-ac11-904d512fc841","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.3","title":"PSM Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3838,"content":"The documents herein define the swap operations that are performed by the Spark Liquidity Layer in the Spark Base PSM.","contentHash":"a09ef36a563f1b41b54263ecd08cdf79668503f36d2e9007cd6b00a154cf27c4","addressRefs":[]},"0328a7f5-d4fd-40a6-a521-4f443687993e":{"id":"0328a7f5-d4fd-40a6-a521-4f443687993e","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.3.1","title":"Deposit Asset Into The PSM","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3839,"content":"The documents herein define a series of operations for an operator to `deposit` an asset into the PSM.","contentHash":"252464b8ec795ea18fd31b43c60b2ec4551876c77b71458f7e25ce44d653d4d6","addressRefs":[]},"c102ced7-782f-403d-99a8-82d10a089fc7":{"id":"c102ced7-782f-403d-99a8-82d10a089fc7","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.3.2","title":"Withdraw The Maximum Amount Of Asset From The PSM","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3840,"content":"The documents herein define a series of operations for an operator to `withdraw` an asset from the PSM.","contentHash":"e43172f6b6c82336c89a7bfdc4a26e1f0bd3667f0d6135c70950d9b78fed6301","addressRefs":[]},"4621745d-65b3-44e0-9261-004430118551":{"id":"4621745d-65b3-44e0-9261-004430118551","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.4","title":"Bridging Functions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3841,"content":"The documents herein define the operations that are performed to bridge liquidity between the destination blockchain and Ethereum Mainnet for the Spark Liquidity Layer.","contentHash":"2f71f31890e9be1459b92032cad320d0804ea7773dba20c1c89e0622b3ad64aa","addressRefs":[]},"b871295a-f74a-4bf3-aca7-2bdba2b0292a":{"id":"b871295a-f74a-4bf3-aca7-2bdba2b0292a","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.4.1","title":"Bridge USDC Using Circle Cross-Chain Transfer Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3842,"content":"This document defines the process to bridge USDC using the Circle Cross-Chain Transfer Protocol. The process for bridging USDC using CCTP through the `ForeignController` contract is the same as the one for bridging USDC using CCTP through the `MainnetController` contract; see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1 - Bridge USDC Using Circle Cross-Chain Transfer Protocol](956f0941-5121-4dce-99d8-2fd1af00ffa6).","contentHash":"a4ab603073c7f1a8d8f2da6dda47f832ff6902c79f6f6c15425ee89f4b442ecf","addressRefs":[]},"5fe16ede-05e3-48eb-b43a-e4ea84d86e25":{"id":"5fe16ede-05e3-48eb-b43a-e4ea84d86e25","doc_no":"A.6.1.1.1.2.6.1.2.2.1.2.2.2.4.2","title":"Bridge USDS / sUSDS using OP Token Bridge","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3843,"content":"The documents herein define the process to bridge USDS / sUSDS using the OP Token Bridge. This process will be specified in a future iteration of the Spark Artifact.","contentHash":"73de0f33b5e46ed64a9ba9aab48f4d3dd5fbf4bf9630b4aa77d6526b86a25113","addressRefs":[]},"554a654f-930a-419e-a8a4-f49dd5599ee8":{"id":"554a654f-930a-419e-a8a4-f49dd5599ee8","doc_no":"A.6.1.1.1.2.6.1.2.2.1.3","title":"Rate Limit Management","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3844,"content":"The documents herein define the protocol for querying, setting, and adjusting `RateLimits` for Instances using their `RateLimitID`s. The ratelimits must be maintained in line with Spark’s strategy, market conditions, and security considerations.","contentHash":"f596d4da6c7820597073dc6c69584dddc2394e41d0838a3ca29533ae6f581176","addressRefs":[]},"89577062-a38b-4cf7-a1ae-33c0bcff1cca":{"id":"89577062-a38b-4cf7-a1ae-33c0bcff1cca","doc_no":"A.6.1.1.1.2.6.1.2.2.1.3.1","title":"RateLimits Query","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3845,"content":"The following code sets out instructions for the operator to query the current `RateLimits` for a specific key:\n\n```\nFunction getRateLimitData(bytes32 key) external override view returns (RateLimitData memory) {\n        return _data[key];\n    }\n\n    function getCurrentRateLimit(bytes32 key) public override view returns (uint256) {\n        RateLimitData memory d = _data[key];\n\n        // Unlimited rate limit case\n        if (d.maxAmount == type(uint256).max) {\n            return type(uint256).max;\n        }\n\n        return _min(\n            d.slope * (block.timestamp - d.lastUpdated) + d.lastAmount,\n            d.maxAmount\n        );\n    }\n```","contentHash":"a3880073976bd68f69cc7f7c24a8996d997019336a9ab49625d5b63ff9486b99","addressRefs":[]},"24e955c5-4555-41f5-b4f3-e9bcf6baf0e9":{"id":"24e955c5-4555-41f5-b4f3-e9bcf6baf0e9","doc_no":"A.6.1.1.1.2.6.1.2.2.1.3.2","title":"Set RateLimit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3846,"content":"The following code sets out instructions for the operator to set the `RateLimit` for a specific key:\n\n```\nfunction setRateLimitData(\n        bytes32 key,\n        uint256 maxAmount,\n        uint256 slope,\n        uint256 lastAmount,\n        uint256 lastUpdated\n    )\n        public override onlyRole(DEFAULT_ADMIN_ROLE)\n    {\n        require(lastAmount  <= maxAmount,       \"RateLimits/invalid-lastAmount\");\n        require(lastUpdated <= block.timestamp, \"RateLimits/invalid-lastUpdated\");\n\n        _data[key] = RateLimitData({\n            maxAmount:   maxAmount,\n            slope:       slope,\n            lastAmount:  lastAmount,\n            lastUpdated: lastUpdated\n        });\n\n        emit RateLimitDataSet(key, maxAmount, slope, lastAmount, lastUpdated);\n    }\n\n    function setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope) external override {\n        setRateLimitData(key, maxAmount, slope, maxAmount, block.timestamp);\n    }\n```","contentHash":"8ad154718350805bbb3472f1fbd4c9ac76bc609adc0564afa974a040128f272d","addressRefs":[]},"241dde83-2f9b-486d-be55-19895291c183":{"id":"241dde83-2f9b-486d-be55-19895291c183","doc_no":"A.6.1.1.1.2.6.1.2.2.1.3.3","title":"Set Unlimited RateLimit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3847,"content":"The following code sets out instructions for the operator to set an unlimited `RateLimit` for a specific key:\n\n```\nfunction setUnlimitedRateLimitData(bytes32 key) external override {\n        setRateLimitData(key, type(uint256).max, 0, type(uint256).max, block.timestamp);\n```","contentHash":"a15f532e5596116bc6348a54ad1bc2f66083fa758ab7741f901daa0baefbb293","addressRefs":[]},"c58e3657-404b-40f7-b83e-26063d908155":{"id":"c58e3657-404b-40f7-b83e-26063d908155","doc_no":"A.6.1.1.1.2.6.1.2.2.1.3.4","title":"Set Trigger For RateLimit Decrease","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3848,"content":"The following code sets out instructions for the operator to trigger a decrease of a `RateLimit` for a specific key:\n\n```\nfunction triggerRateLimitDecrease(bytes32 key, uint256 amountToDecrease)\n        external override onlyRole(CONTROLLER) returns (uint256 newLimit)\n    {\n        RateLimitData storage d = _data[key];\n        uint256 maxAmount = d.maxAmount;\n\n        require(maxAmount > 0, \"RateLimits/zero-maxAmount\");\n        if (maxAmount == type(uint256).max) return type(uint256).max;  // Special case unlimited\n\n        uint256 currentRateLimit = getCurrentRateLimit(key);\n\n        require(amountToDecrease <= currentRateLimit, \"RateLimits/rate-limit-exceeded\");\n\n        d.lastAmount = newLimit = currentRateLimit - amountToDecrease;\n        d.lastUpdated = block.timestamp;\n\n        emit RateLimitDecreaseTriggered(key, amountToDecrease, currentRateLimit, newLimit);\n    }\n```","contentHash":"551f31c21344d606c3b5ffe10a2b607aecea098b75d113c9f791f1c147f35f82","addressRefs":[]},"873c7ba8-1bff-451f-8987-0c21a62c6993":{"id":"873c7ba8-1bff-451f-8987-0c21a62c6993","doc_no":"A.6.1.1.1.2.6.1.2.2.1.3.5","title":"Set Trigger For RateLimit Increase","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3849,"content":"The following code sets out instructions for the operator to trigger an increase of a `RateLimit` for a specific key:\n\n```\nfunction triggerRateLimitIncrease(bytes32 key, uint256 amountToIncrease)\n        external override onlyRole(CONTROLLER) returns (uint256 newLimit)\n    {\n        RateLimitData storage d = _data[key];\n        uint256 maxAmount = d.maxAmount;\n\n        require(maxAmount > 0, \"RateLimits/zero-maxAmount\");\n        if (maxAmount == type(uint256).max) return type(uint256).max;  // Special case unlimited\n\n        uint256 currentRateLimit = getCurrentRateLimit(key);\n\n        d.lastAmount = newLimit = _min(currentRateLimit + amountToIncrease, maxAmount);\n        d.lastUpdated = block.timestamp;\n\n        emit RateLimitIncreaseTriggered(key, amountToIncrease, currentRateLimit, newLimit);\n```","contentHash":"f2897f1ca340a3c532410b62a8e750acf1b70691e7576e4966ea6e320d5fb324","addressRefs":[]},"edbc0297-0640-4833-9e15-b0e4bce960b8":{"id":"edbc0297-0640-4833-9e15-b0e4bce960b8","doc_no":"A.6.1.1.1.2.6.1.2.2.1.4","title":"Instance Lifecycle Management","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3850,"content":"The documents herein define processes for invoking (onboarding) new Spark Liquidity Layer Instances and offboarding existing ones. This process will be specified in a future iteration of the Spark Artifact.","contentHash":"495919b3fbe8e7c8702e32619f726bc9ab56f0435ef779ae3158e0f93f8bdf0b","addressRefs":[]},"438042de-d556-4ea6-9434-cb4c070481d0":{"id":"438042de-d556-4ea6-9434-cb4c070481d0","doc_no":"A.6.1.1.1.2.6.1.2.2.1.5","title":"Upgrading Controller","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3851,"content":"The documents herein define the process for deploying new Controller contracts. This process will be specified in a future iteration of the Spark Artifact.","contentHash":"7e146ed38ded61dba7a2e75724378e7368086db4443afd3fede6fa1d8f2d68ce","addressRefs":[]},"00cebdd9-db63-4ddb-95e0-93b4dc456be7":{"id":"00cebdd9-db63-4ddb-95e0-93b4dc456be7","doc_no":"A.6.1.1.1.2.6.1.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3852,"content":"The documents herein define the process for non-routine ongoing management of the Spark Liquidity Layer and its active Instances.","contentHash":"76f3eacfd218457d2045cf0b7f4606cbe415d4aad93c7c29df3c890182458fff","addressRefs":[]},"0b96f0e0-e490-4b4c-a65f-5625f9352aaa":{"id":"0b96f0e0-e490-4b4c-a65f-5625f9352aaa","doc_no":"A.6.1.1.1.2.6.1.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3853,"content":"The documents herein define all the possible actions that can be taken in case of an emergency within Spark Liquidity Layer operations.","contentHash":"26225b33d38ccb4e22ac8040c349023b2a3027709d98ba66dd25ffba234dbb42","addressRefs":[]},"7bd4a4cc-315b-4365-a793-923cd4aaacff":{"id":"7bd4a4cc-315b-4365-a793-923cd4aaacff","doc_no":"A.6.1.1.1.2.6.1.2.2.3.1","title":"Remove Compromised Relayer As Freezer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3854,"content":"In the event of a compromised Relayer, the `FREEZER_ROLE` can call the function to `removeRelayer` from the Controller contract. This function takes an address, and then the Freezer can remove the compromised Relayer, thereby preventing it from doing any harm to the system. The backstop relayer can then take over. This function should only be used if the keys to the relayer multisig have been leaked or compromised, and the relayer is now in the hands of an external bad actor.\n\n`mainnetController.removeRelayer(compromisedRelayer)`","contentHash":"8078ea8d196688f48ef19c5d259035c21615ce8ccd53856b0f87b469189f655d","addressRefs":[]},"962b1da7-0f80-4abc-a7a9-ef229b0f1c13":{"id":"962b1da7-0f80-4abc-a7a9-ef229b0f1c13","doc_no":"A.6.1.1.1.2.6.1.2.2.3.2","title":"Redeem All L2 Positions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3855,"content":"The documents herein list the actions that should be performed by an operator if there is a need to recover the liquidity from L2 Protocols and centralize it in the L2 Spark ALM Proxy.","contentHash":"655d3535dbbe51c3d1ca9bf4596337ee11e6c965f071fdffae503385f784623d","addressRefs":[]},"aad3683d-38d4-4e94-b2bf-88b408c2290e":{"id":"aad3683d-38d4-4e94-b2bf-88b408c2290e","doc_no":"A.6.1.1.1.2.6.1.2.2.3.2.1","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3856,"content":"In order to withdraw all ERC-4626 balances, the operator must execute the following action:\n\n```\nforeignController.redeemERC4626(address(token), token.balanceOf(address(proxy)))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.2.2.1.2 - Withdraw ERC-4626 Tokens](c2bbf44a-496c-4cf6-b0f6-25f77e66465b) and [A.6.1.1.1.2.6.1.2.2.1.2.2.2.1.3 - Redeem ERC-4626 Tokens](ab5eb90f-1007-4560-a0ea-1c25d433c602).","contentHash":"e14e2bf942e5e8b9e2fbeb14989e79b0eaf4c1afbfcc00de07ba8961fac207fa","addressRefs":[]},"29bb82e9-a308-448f-ace1-e8b0397a0995":{"id":"29bb82e9-a308-448f-ace1-e8b0397a0995","doc_no":"A.6.1.1.1.2.6.1.2.2.3.2.2","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3857,"content":"[A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.3 - General Redeem from ERC-4626 Tokens Procedure](ed774ab7-c761-444b-963d-7407bf91e243)","contentHash":"43e92a7ffed547fd319477ee9f96156f5a2aacf0fb32a05c03965ffd26d5d4d9","addressRefs":[]},"2560adbb-4a5c-4c95-86cb-04647bb33836":{"id":"2560adbb-4a5c-4c95-86cb-04647bb33836","doc_no":"A.6.1.1.1.2.6.1.2.2.3.2.3","title":"Aave AToken Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3858,"content":"In order to withdraw all AToken balances, the operator must execute the following action:\n\n```\nforeignController.withdrawAave(aToken, aToken.balanceOf(address(proxy)))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.2.2.2.2 - Withdraw Aave ATokens](5b090e5a-a2e7-4548-a1b4-53be86db6516).","contentHash":"79cfe6b9b22e10529487a04dc9e64851247ad60c4ee6be77345f196cb800b63d","addressRefs":[]},"c1f708eb-7373-448d-a54c-b178d0fd909a":{"id":"c1f708eb-7373-448d-a54c-b178d0fd909a","doc_no":"A.6.1.1.1.2.6.1.2.2.3.2.4","title":"Aave AToken Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3859,"content":"In order to withdraw all AToken balances, the operator must execute the following action:\n\n```\nforeignController.withdrawAave(aToken, aToken.balanceOf(address(proxy))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3.2 - General Withdraw from Aave ATokens Procedure](6e75a2bd-70b7-4081-bb9f-39cf6b321066).","contentHash":"c3d709f3191a2a0edc8cb21cfafcda15b545327a0be285aca70c47d95a6b86b8","addressRefs":[]},"3bd03154-f7f0-408e-b3bf-654aaaf7e8cf":{"id":"3bd03154-f7f0-408e-b3bf-654aaaf7e8cf","doc_no":"A.6.1.1.1.2.6.1.2.2.3.2.5","title":"All PSM Assets Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3860,"content":"In order to withdraw all Assets from the PSM, the operator must execute the following action:\n\n```\nforeignController.withdrawPSM(address(usdc), type(uint256).max)\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.2.2.3.2 - Withdraw The Maximum Amount Of Asset From The PSM](c102ced7-782f-403d-99a8-82d10a089fc7).","contentHash":"e351bcf5577d8a72f82677aa263bcce7d98f3865e0ec2b842627d4d7a3072ef1","addressRefs":[]},"c4ed7a34-4c1c-43ec-8eb2-7285c9a46184":{"id":"c4ed7a34-4c1c-43ec-8eb2-7285c9a46184","doc_no":"A.6.1.1.1.2.6.1.2.2.3.3","title":"Bridge Liquidity From L2 ALM Proxy To Mainnet","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3861,"content":"The documents herein define the actions that should be performed by an operator if there is a need to bring all liquidity from the Spark ALM Proxy on the destination domain to the Spark ALM Proxy on Ethereum Mainnet.","contentHash":"338cc8d4febf3391dcb5abf726188853d25d7d48beeee2970789b314f734feb8","addressRefs":[]},"3c47986f-3a20-4593-b4c1-cd5f8a0837c8":{"id":"3c47986f-3a20-4593-b4c1-cd5f8a0837c8","doc_no":"A.6.1.1.1.2.6.1.2.2.3.3.1","title":"USDC Bridging Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3862,"content":"In order to bridge USDC, the operator must execute the following action:\n\n```\nforeignController.transferUSDCToCCTP(usdc.balanceOf(address(proxy)), 0);\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.5.1 - Bridge USDC Using Circle Cross-Chain Transfer Protocol](956f0941-5121-4dce-99d8-2fd1af00ffa6).","contentHash":"391f26c0f8a9ff72953a6e9f34a5783986ea0f3f852ed04e2307ea5be555a78b","addressRefs":[]},"188124a1-32fe-4ed3-90bb-1774cbcf18c5":{"id":"188124a1-32fe-4ed3-90bb-1774cbcf18c5","doc_no":"A.6.1.1.1.2.6.1.2.2.3.3.2","title":"USDS and sUSDS Bridging Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3863,"content":"The function to bridge USDS and sUSDS is currently actioned by an Executive Vote by Sky Governance. This process will be managed by the operator of the Spark Liquidity Layer in the future.","contentHash":"469a31bda2a7afde53a88d6f7a956dbed69126b71275e8fdb97378a11a0c3b32","addressRefs":[]},"77067d73-922a-45e1-9f74-2b6947108d3b":{"id":"77067d73-922a-45e1-9f74-2b6947108d3b","doc_no":"A.6.1.1.1.2.6.1.2.2.3.4","title":"Redeem All Mainnet Positions","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3864,"content":"The documents herein define the actions that should be performed by an operator if there is a need to recover the liquidity from Mainnet Protocols and centralize it in the Mainnet Spark ALM Proxy.","contentHash":"ac7905bb3b48fa66ba3acef8a735b10481ff92101b1247e5152396cbad003df8","addressRefs":[]},"f92ddc3f-672a-4f52-931f-5263a9f709b9":{"id":"f92ddc3f-672a-4f52-931f-5263a9f709b9","doc_no":"A.6.1.1.1.2.6.1.2.2.3.4.1","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3865,"content":"In order to withdraw all ERC-4626 balances, the operator must execute the following action:\n\n```\nmainnetController.redeemERC4626(address(token), token.balanceOf(address(proxy)))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.2 - General Withdraw from ERC-4626 Tokens Procedure](e797d1cc-9161-4b7a-8c16-db20a026d001) and [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.3 - General Redeem from ERC-4626 Tokens Procedure](ed774ab7-c761-444b-963d-7407bf91e243).","contentHash":"4061fe27df41fe07576fd4727d1202610c66ded909c17d0cca226ae6df269aa9","addressRefs":[]},"eb2056e5-2987-45fc-bb7d-453f09a3d5b7":{"id":"eb2056e5-2987-45fc-bb7d-453f09a3d5b7","doc_no":"A.6.1.1.1.2.6.1.2.2.3.4.2","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3866,"content":"[A.6.1.1.1.2.6.1.2.2.1.2.1.2.2.3 - General Redeem from ERC-4626 Tokens Procedure](ed774ab7-c761-444b-963d-7407bf91e243)","contentHash":"43e92a7ffed547fd319477ee9f96156f5a2aacf0fb32a05c03965ffd26d5d4d9","addressRefs":[]},"09de757a-e742-4061-a1d4-7e5d70e9c0df":{"id":"09de757a-e742-4061-a1d4-7e5d70e9c0df","doc_no":"A.6.1.1.1.2.6.1.2.2.3.4.3","title":"Aave AToken Withdrawal Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3867,"content":"In order to withdraw all Aave AToken balances, the operator must execute the following action:\n\n```\nmainnetController.withdrawAave(aToken, aToken.balanceOf(address(proxy))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3.2 - General Withdraw from Aave ATokens Procedure](6e75a2bd-70b7-4081-bb9f-39cf6b321066).","contentHash":"5095d3c19c98f3dda17fcfa66b4aa6ed09237a38033fa40adde281ce6c0403f0","addressRefs":[]},"62bf500a-56be-4766-8390-c6c1aaa4aeb9":{"id":"62bf500a-56be-4766-8390-c6c1aaa4aeb9","doc_no":"A.6.1.1.1.2.6.1.2.2.3.5","title":"USDC to USDS Swap Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3868,"content":"This document defines the action that should be performed by an operator if there is a need to centralize all recovered liquidity in USDS.\n\n```\nmainnetController.swapUSDCToUSDS(usdc.balanceOf(address(proxy))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.4.2 - Swap USDC to USDS](8b7c4526-ea6a-488d-925a-884704a7bc80).","contentHash":"dad208fc01b53ad22dfb9538190c4673700ed947cf9f993a5029819f6a1d190d","addressRefs":[]},"dadf134c-5faa-4dfb-b31b-62f0bacc9519":{"id":"dadf134c-5faa-4dfb-b31b-62f0bacc9519","doc_no":"A.6.1.1.1.2.6.1.2.2.3.6","title":"USDS Burn Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3869,"content":"This document defines the action that should be performed if there is a need to repay and then burn Spark’s USDS debt.\n\n```\nmainnetController.burnUSDS(usds.balanceOf(address(proxy))\n```\nMore detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.1.2 - Burn USDS](fc8b57fd-c0c8-422d-b0a9-e124b3cac439).","contentHash":"336af5a5a006179688c3778ab70377176ec69766749fdec0302ad5c939f9eaa2","addressRefs":[]},"138f0270-4aa7-41c4-9a00-c4c661d2d426":{"id":"138f0270-4aa7-41c4-9a00-c4c661d2d426","doc_no":"A.6.1.1.1.2.6.1.2.3","title":"Allocation Strategy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3870,"content":"In the future, additional logic will be added herein regarding the strategy by which capital is allocated between different Instances of the Spark Liquidity Layer.","contentHash":"76d7254d83af675f996772a6eff85634137ea76294686b056c25aec595a96763","addressRefs":[]},"f7c9fdda-3d42-4b9d-852d-610d7ae4f6c0":{"id":"f7c9fdda-3d42-4b9d-852d-610d7ae4f6c0","doc_no":"A.6.1.1.1.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3871,"content":"The Instances of the Spark Liquidity Layer with `Active` Status are stored herein. The `RRC Framework Full Implementation` status defines whether the Instance Financial RRC is calculated based on a fully implemented risk model (see [A.3.2.1.1.4.3.1 - Fully Implemented Risk Models](419a1d00-fbae-4d26-bd47-8f57677d8001)) or a pending risk model (see [A.3.2.1.1.4.3.2 - Pending Risk Models](81ca88bf-3f6a-4d10-a3e2-d47cf6636d7d)). If the Instance Financial RRC is calculated based on a fully implemented risk model the status is `Covered`. If the Instance Financial RRC is calculated based on a pending risk model the status is `Pending`.","contentHash":"7528b704158b9e09fc653c68694a0312291b05b596729ed416861cc8b1f76494","addressRefs":[]},"cce62366-93d3-4856-9dcb-d700695a8a96":{"id":"cce62366-93d3-4856-9dcb-d700695a8a96","doc_no":"A.6.1.1.1.2.6.1.3.1","title":"Ethereum Mainnet Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3872,"content":"The Ethereum Mainnet Instances of the Spark Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"07d4c92ce214d67e313cd00e068ed2d9741b07582da76a1d7c3b4751295eb076","addressRefs":[]},"1fdebcff-990a-40ac-8db6-8ef993edd57a":{"id":"1fdebcff-990a-40ac-8db6-8ef993edd57a","doc_no":"A.6.1.1.1.2.6.1.3.1.1","title":"SparkLend","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3873,"content":"The Ethereum Mainnet Instances of the SparkLend Protocol with `Active` Status are stored herein.","contentHash":"4c0c8211d1b30de64573554c13cafbc9f190a8ee4388c9a3d708eef7329d4ac5","addressRefs":[]},"4940f6ee-28e8-47a8-a7df-f2b30bd7dcc2":{"id":"4940f6ee-28e8-47a8-a7df-f2b30bd7dcc2","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1","title":"Ethereum Mainnet - SparkLend USDS Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3874,"content":"The documents herein contain the Instance Configuration Document for the SparkLend USDS Instance.","contentHash":"9023e5b850e272659bb11f336a66a2ec15155a2de198987f63b7e0cede675f37","addressRefs":[]},"56203f5d-8205-48ac-a278-66218fda9c2e":{"id":"56203f5d-8205-48ac-a278-66218fda9c2e","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3875,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"e79d6215-c40b-45c1-9660-eda89b17325e":{"id":"e79d6215-c40b-45c1-9660-eda89b17325e","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3876,"content":"The documents herein define the parameters of the SparkLend USDS Instance of the Allocation System Primitive.","contentHash":"05d65bbc7a3fed3926ce4720dcff6012fe64efc73ea1240f33c858cc12170284","addressRefs":[]},"813cf6b5-ee1b-4767-a05b-4cf03c0bd37f":{"id":"813cf6b5-ee1b-4767-a05b-4cf03c0bd37f","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3877,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"8a6a8cf9-289d-42e1-842c-dcb722b6225c":{"id":"8a6a8cf9-289d-42e1-842c-dcb722b6225c","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3878,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"403b96e6-977f-4eaf-91e3-d9c6a9cb9b2f":{"id":"403b96e6-977f-4eaf-91e3-d9c6a9cb9b2f","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3879,"content":"SparkLend Protocol","contentHash":"502533b7b75b61116678924a53cd7ddd355f6e0d83855732010ce6e38cd35177","addressRefs":[]},"ab86175c-e81a-41b0-98cb-e35971d08363":{"id":"ab86175c-e81a-41b0-98cb-e35971d08363","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3880,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"65988a53-f492-49b6-b693-6e98f82b2c29":{"id":"65988a53-f492-49b6-b693-6e98f82b2c29","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3881,"content":"spUSDS","contentHash":"93444288135ea634049e12504be969432cf452c33bb7399ce8d7f90667981a0d","addressRefs":[]},"02bf0b42-0993-431f-af52-3b1f7e0c3675":{"id":"02bf0b42-0993-431f-af52-3b1f7e0c3675","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3882,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"a8171359-d11e-4014-bd9b-ef19712e556d":{"id":"a8171359-d11e-4014-bd9b-ef19712e556d","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3883,"content":"`0xC02aB1A5eaA8d1B114EF786D9bde108cD4364359`","contentHash":"39f843ac2e963c1fbd860c8eaa559f192b0cd81af0851af1acb5fa52fe2c6f51","addressRefs":["0xc02ab1a5eaa8d1b114ef786d9bde108cd4364359"]},"aeb1bcc7-1214-4544-b686-687d1bb2fa70":{"id":"aeb1bcc7-1214-4544-b686-687d1bb2fa70","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3884,"content":"`0xdC035D45d973E3EC169d2276DDab16f1e407384F`","contentHash":"70054b0ff65437cb32b35df32f8e11d1cc8ea540e9916e08d1cd96696d95e083","addressRefs":["0xdc035d45d973e3ec169d2276ddab16f1e407384f"]},"66b08d31-c12e-401b-8270-6e1aeb445140":{"id":"66b08d31-c12e-401b-8270-6e1aeb445140","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3885,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"85106bf0-7367-4355-acf1-5fb22199d135":{"id":"85106bf0-7367-4355-acf1-5fb22199d135","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3886,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"4fae5f20-61df-4df3-8018-2be0a287de79":{"id":"4fae5f20-61df-4df3-8018-2be0a287de79","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3887,"content":"The inflow rate limits are:\n\n- `maxAmount`: 200,000,000 USDS\n- `slope`: 400,000,000 USDS per day","contentHash":"16ada8b082826dd3883a48cf90a2d788a299ef5c6a51a5e71c41bd68ee3549ee","addressRefs":[]},"e2216e6c-7075-464e-9df6-98b02d8ee4a0":{"id":"e2216e6c-7075-464e-9df6-98b02d8ee4a0","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3888,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"569b0f886c9aedda81b4e87d26e1e21d96763dd2e909e2e9865edcf064b320e5","addressRefs":[]},"26826191-9e5c-4337-b274-43d064d7a63a":{"id":"26826191-9e5c-4337-b274-43d064d7a63a","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3889,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"1cc294ee-5bea-41c8-ac48-deb47aa95ec6":{"id":"1cc294ee-5bea-41c8-ac48-deb47aa95ec6","doc_no":"A.6.1.1.1.2.6.1.3.1.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3890,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"7cd0ec35-9449-48ce-a764-454ed33e72de":{"id":"7cd0ec35-9449-48ce-a764-454ed33e72de","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2","title":"Ethereum Mainnet - SparkLend USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3891,"content":"The documents herein contain the Instance Configuration Document for the SparkLend USDC Instance.","contentHash":"05bf4b98e7b1cdbcf3074855770b121e66ddd36cc9a5871505ff26172b971c95","addressRefs":[]},"404340ff-76f9-44fd-9c05-7a4f36780e71":{"id":"404340ff-76f9-44fd-9c05-7a4f36780e71","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3892,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"62cae553-442b-4a02-a550-b11c318fa124":{"id":"62cae553-442b-4a02-a550-b11c318fa124","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3893,"content":"The documents herein define the parameters of the SparkLend USDC Instance of the Allocation System Primitive.","contentHash":"54a4e5afecc821efd45088e49f09dfabaaf0cd1c001647c34a420f7d1de08405","addressRefs":[]},"639e838f-8153-446d-8e1b-80d16c7c7495":{"id":"639e838f-8153-446d-8e1b-80d16c7c7495","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3894,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"f81f92a6-e867-4713-8d75-bb65407f8c4a":{"id":"f81f92a6-e867-4713-8d75-bb65407f8c4a","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3895,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"33ff048b-1c73-449a-af30-ebb5261d5bf1":{"id":"33ff048b-1c73-449a-af30-ebb5261d5bf1","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3896,"content":"SparkLend Protocol","contentHash":"502533b7b75b61116678924a53cd7ddd355f6e0d83855732010ce6e38cd35177","addressRefs":[]},"bc4fbbb2-eacc-40bb-8197-da8f3ae38db9":{"id":"bc4fbbb2-eacc-40bb-8197-da8f3ae38db9","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3897,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"aee5e636-70e0-4fd9-b52a-814a7bac123c":{"id":"aee5e636-70e0-4fd9-b52a-814a7bac123c","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3898,"content":"spUSDC","contentHash":"a61b2e3fb9c87e9d690350f9c017c4828dceaccb7d7f2c7e156a5139615620b3","addressRefs":[]},"e5440caf-87d0-4e09-a5f9-1736f2c6e55f":{"id":"e5440caf-87d0-4e09-a5f9-1736f2c6e55f","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3899,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"de211b16-8d7a-4560-9cb9-52a98941fb43":{"id":"de211b16-8d7a-4560-9cb9-52a98941fb43","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3900,"content":"`0x377C3bd93f2a2984E1E7bE6A5C22c525eD4A4815`","contentHash":"dd1a784dfbf0f8596ece47ac9ff6a4752c1e5d97a1ce73b0add1dcc32b1e78ae","addressRefs":["0x377c3bd93f2a2984e1e7be6a5c22c525ed4a4815"]},"c78afa3b-9e4b-4c25-a85f-28492d7729aa":{"id":"c78afa3b-9e4b-4c25-a85f-28492d7729aa","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3901,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"6b9ef39f-99f9-4dad-b687-f397f5f36b64":{"id":"6b9ef39f-99f9-4dad-b687-f397f5f36b64","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3902,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"969d566b-46b5-41ad-8317-0bc4b8981c6a":{"id":"969d566b-46b5-41ad-8317-0bc4b8981c6a","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3903,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"4e05fefc-c013-4f04-8173-7f96cdb90d1e":{"id":"4e05fefc-c013-4f04-8173-7f96cdb90d1e","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3904,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,000 USDC\n- `slope`: 200,000,000 USDC per day","contentHash":"746b712055693fa438bcb6182d1c1de2ed087ad15c63d247db1d389660ce6025","addressRefs":[]},"ff880422-b0e0-401d-8d01-e541f7643ffc":{"id":"ff880422-b0e0-401d-8d01-e541f7643ffc","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3905,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"569b0f886c9aedda81b4e87d26e1e21d96763dd2e909e2e9865edcf064b320e5","addressRefs":[]},"e3ffdba1-d90d-4c9e-a0b7-3ba14293ec41":{"id":"e3ffdba1-d90d-4c9e-a0b7-3ba14293ec41","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3906,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"0e700537-6981-4b70-bca5-08937cf30f73":{"id":"0e700537-6981-4b70-bca5-08937cf30f73","doc_no":"A.6.1.1.1.2.6.1.3.1.1.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3907,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"7e8135d5-7b45-48a7-bf9a-881f0bbf115c":{"id":"7e8135d5-7b45-48a7-bf9a-881f0bbf115c","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3","title":"Ethereum Mainnet - SparkLend Dai Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3908,"content":"The documents herein contain the Instance Configuration Document for the SparkLend Dai Instance.","contentHash":"c2dc4b97b378767e0e9c8ea3e198dd718cfaef8a689023f475cd93f9d0658ede","addressRefs":[]},"a0131763-e837-4a90-a3e7-710c5a2068d9":{"id":"a0131763-e837-4a90-a3e7-710c5a2068d9","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3909,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"92a92ef9-daa9-4285-814a-697a36d55997":{"id":"92a92ef9-daa9-4285-814a-697a36d55997","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3910,"content":"The documents herein define the parameters of the SparkLend Dai Instance of the Allocation System Primitive.","contentHash":"1d0b4de889faf9b59dbcdb248a4952072481dcf845a361bf3b38045c2d7a6b89","addressRefs":[]},"3c64b11d-c123-48de-ba91-97e9c2f461e7":{"id":"3c64b11d-c123-48de-ba91-97e9c2f461e7","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3911,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"2c800a97-c0a8-4ddd-8e03-b149b779bd9a":{"id":"2c800a97-c0a8-4ddd-8e03-b149b779bd9a","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3912,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"9a89ca9d-4351-4ff7-9a3a-99728545846f":{"id":"9a89ca9d-4351-4ff7-9a3a-99728545846f","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3913,"content":"SparkLend Protocol","contentHash":"502533b7b75b61116678924a53cd7ddd355f6e0d83855732010ce6e38cd35177","addressRefs":[]},"bffaf20b-5502-42c8-9c15-25bec3816430":{"id":"bffaf20b-5502-42c8-9c15-25bec3816430","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3914,"content":"Dai","contentHash":"41409b0b8b16323a6dbf78c6efdc74b207b406e4a360b7be4281455d4045c2ee","addressRefs":[]},"85b21780-1fcf-4a91-a5f8-4d0d301e5de5":{"id":"85b21780-1fcf-4a91-a5f8-4d0d301e5de5","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3915,"content":"spDai","contentHash":"0f71f7a631e9d42792913195576fc046b83a69bfaa31c91e4fc6645708adebd7","addressRefs":[]},"2d82fc81-ed61-4097-a122-5ab0a0c34e3c":{"id":"2d82fc81-ed61-4097-a122-5ab0a0c34e3c","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3916,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"edbdeb06-4b87-4dd6-960a-cba704f7bf94":{"id":"edbdeb06-4b87-4dd6-960a-cba704f7bf94","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3917,"content":"`0x4DEDf26112B3Ec8eC46e7E31EA5e123490B05B8B`","contentHash":"89e12de8c8c2e67096d77108ba79470211f6d336a02765f84fa3681d4f563f52","addressRefs":["0x4dedf26112b3ec8ec46e7e31ea5e123490b05b8b"]},"388c73f9-17cc-4518-9af9-4bc619963172":{"id":"388c73f9-17cc-4518-9af9-4bc619963172","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3918,"content":"`0x6B175474E89094C44Da98b954EedeAC495271d0F`","contentHash":"d80fdc7ccee4b09cd1e64ad674b56132ee4ac90ad5b61477c2096cdf6e4746a6","addressRefs":["0x6b175474e89094c44da98b954eedeac495271d0f"]},"ec3317a7-e330-45a8-a797-9c8f4bf3b606":{"id":"ec3317a7-e330-45a8-a797-9c8f4bf3b606","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.3","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3919,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"381c40f3-008e-4541-81c7-6192a186def7":{"id":"381c40f3-008e-4541-81c7-6192a186def7","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.3.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3920,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,000 DAI\n- `slope`: 50,000,000 DAI per day","contentHash":"8483a8e55f416f6ca1b3a533a2626c6cc88755c1b570726b7a177f21bb1a9f02","addressRefs":[]},"101cf682-0eda-4e40-81e0-601e3d2895aa":{"id":"101cf682-0eda-4e40-81e0-601e3d2895aa","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.2.3.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3921,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"9427c9de-cc7b-4ea0-ad1f-d1ceb6d7e866":{"id":"9427c9de-cc7b-4ea0-ad1f-d1ceb6d7e866","doc_no":"A.6.1.1.1.2.6.1.3.1.1.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3922,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"dbd8d0fc-d055-415c-a7ef-4796c5e33a87":{"id":"dbd8d0fc-d055-415c-a7ef-4796c5e33a87","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4","title":"Ethereum Mainnet - SparkLend USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3923,"content":"The documents herein contain the Instance Configuration Document for the SparkLend USDT Instance.","contentHash":"6045f97403ecc8538707fad095970ecbc56f87ea24a33f8261ff776e0933df55","addressRefs":[]},"cf25dc95-3f66-47aa-854e-25e54e56f855":{"id":"cf25dc95-3f66-47aa-854e-25e54e56f855","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3924,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"7dbcc194-323c-41ff-b5ef-31fc104fb2e2":{"id":"7dbcc194-323c-41ff-b5ef-31fc104fb2e2","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3925,"content":"The documents herein define the parameters of the SparkLend USDT Instance of the Allocation System Primitive.","contentHash":"4a8a977868340a4263a2dde9d6b1801fc87706a6b47168b1705e5ad077827544","addressRefs":[]},"c1116956-306b-4b51-afcd-bf0e895ea738":{"id":"c1116956-306b-4b51-afcd-bf0e895ea738","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3926,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"adfe7e8c-3626-4168-a422-59bb008df5f5":{"id":"adfe7e8c-3626-4168-a422-59bb008df5f5","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3927,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"3514f1da-184b-4c4a-bb28-7e5bf98136d3":{"id":"3514f1da-184b-4c4a-bb28-7e5bf98136d3","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3928,"content":"SparkLend Protocol","contentHash":"502533b7b75b61116678924a53cd7ddd355f6e0d83855732010ce6e38cd35177","addressRefs":[]},"fe96e727-c44b-4c2d-93bf-bdff1ae10373":{"id":"fe96e727-c44b-4c2d-93bf-bdff1ae10373","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3929,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"86c2b46c-afa4-456a-a261-fc20c9840441":{"id":"86c2b46c-afa4-456a-a261-fc20c9840441","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3930,"content":"spUSDT","contentHash":"4a7b4af932f648d799dc87c5bbab407da15e1e1cfaa0ce5946b7dc55a529fc74","addressRefs":[]},"a657da06-c319-4b61-9e2c-f09e383672f9":{"id":"a657da06-c319-4b61-9e2c-f09e383672f9","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3931,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"85a280c2-a45d-4e67-ab6e-7cdcf5746106":{"id":"85a280c2-a45d-4e67-ab6e-7cdcf5746106","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3932,"content":"`0xe7dF13b8e3d6740fe17CBE928C7334243d86c92f`","contentHash":"d09e4a6c0949145d4e02b1e42a1d29658abcdb47f0c62f9de8ff70be7b8a2bd1","addressRefs":["0xe7df13b8e3d6740fe17cbe928c7334243d86c92f"]},"a7f5e722-e39c-4f9c-be0d-c43484cc18ae":{"id":"a7f5e722-e39c-4f9c-be0d-c43484cc18ae","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3933,"content":"`0xdAC17F958D2ee523a2206206994597C13D831ec7`","contentHash":"d674f514fb5256107f891afe7b796353b6535b08717e30bc071e1ccdf11a1fbf","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"2857a038-a0c7-41e5-b547-8a067a854155":{"id":"2857a038-a0c7-41e5-b547-8a067a854155","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3934,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"3662bfb6-2730-40f3-bdb2-7944e5f591ad":{"id":"3662bfb6-2730-40f3-bdb2-7944e5f591ad","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3935,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"4a4f3cb4-fc31-4901-b684-c26234dca7bb":{"id":"4a4f3cb4-fc31-4901-b684-c26234dca7bb","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3936,"content":"The inflow rate limits are:\n\n- `maxAmount`: 500,000,000 USDT\n- `slope`: 2,000,000,000 USDT per day","contentHash":"a91aa4ca7bc464054b9dc1cde0be75a6a501a1ca97f53568d412c0ddda0cecb0","addressRefs":[]},"dadcd267-a47c-4bc0-9216-98369b470b72":{"id":"dadcd267-a47c-4bc0-9216-98369b470b72","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3937,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"126b8574-c161-4c0e-b7a6-a5ceb032a395":{"id":"126b8574-c161-4c0e-b7a6-a5ceb032a395","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3938,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"9c6b2c92-ede8-43a8-8a17-25617429e4f0":{"id":"9c6b2c92-ede8-43a8-8a17-25617429e4f0","doc_no":"A.6.1.1.1.2.6.1.3.1.1.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3939,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"84a0c43e-b64b-4018-bb2c-3d5c5a635c03":{"id":"84a0c43e-b64b-4018-bb2c-3d5c5a635c03","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5","title":"Ethereum Mainnet - SparkLend pyUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3940,"content":"The documents herein contain the Instance Configuration Document for the SparkLend pyUSD Instance.","contentHash":"a38d5679ddb6f727b5d684656395c14e444a1005af3b65d4449c946e003c9364","addressRefs":[]},"26b618a9-205b-4eca-9592-1491108ece2e":{"id":"26b618a9-205b-4eca-9592-1491108ece2e","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3941,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"2ce01191-6e84-46b2-ac07-0c368829b638":{"id":"2ce01191-6e84-46b2-ac07-0c368829b638","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3942,"content":"The documents herein define the parameters of the SparkLend pyUSD Instance of the Allocation System Primitive.","contentHash":"1b85d3c7b82bd74807a449c9698987849b4dd87f69c3f9f97bf1a5390e7d8998","addressRefs":[]},"1645641e-bf06-4d30-b7e4-71f79feb46ab":{"id":"1645641e-bf06-4d30-b7e4-71f79feb46ab","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3943,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"9562ff84-c0b8-4a19-b6be-7e0f40b7613d":{"id":"9562ff84-c0b8-4a19-b6be-7e0f40b7613d","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3944,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"40994499-298a-4f7b-af05-e22688b729f5":{"id":"40994499-298a-4f7b-af05-e22688b729f5","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3945,"content":"SparkLend Protocol","contentHash":"502533b7b75b61116678924a53cd7ddd355f6e0d83855732010ce6e38cd35177","addressRefs":[]},"f4c28b2b-3c0a-4356-b7d7-3132833a7d67":{"id":"f4c28b2b-3c0a-4356-b7d7-3132833a7d67","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3946,"content":"pyUSD","contentHash":"397d68f0518c2726dc0f2662dad8d733bed2531140c49fbb1697da8bb3c076b9","addressRefs":[]},"8e4fe4a2-bc78-4d01-bd3d-668bbb247353":{"id":"8e4fe4a2-bc78-4d01-bd3d-668bbb247353","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3947,"content":"sppyUSD","contentHash":"9998eb28f0138c494cea45a625517af850f71bbddc0fb64138cd1197edaa6d8a","addressRefs":[]},"4dfb8749-96b0-42f7-80fb-0683f915aeb0":{"id":"4dfb8749-96b0-42f7-80fb-0683f915aeb0","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3948,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"9730bb57-1bab-44c2-bdfb-805b992d53d0":{"id":"9730bb57-1bab-44c2-bdfb-805b992d53d0","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3949,"content":"`0x779224df1c756b4EDD899854F32a53E8c2B2ce5d`","contentHash":"6abfc6cd9c1d267c6104e35f1bcbd173fdeb81defa5e8fdf61f74e344e3ac8ac","addressRefs":["0x779224df1c756b4edd899854f32a53e8c2b2ce5d"]},"af95c4ee-4010-436b-8717-c747f5a46d96":{"id":"af95c4ee-4010-436b-8717-c747f5a46d96","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3950,"content":"`0x6c3ea9036406852006290770BEdFcAbA0e23A0e8`","contentHash":"cf0daac71d35ab865b50b412b6507da80922d98319a1d85cb7bbc731958009eb","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"9c845059-1b83-4b6c-b823-1e686fc7593e":{"id":"9c845059-1b83-4b6c-b823-1e686fc7593e","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3951,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"abaee24f-40a5-4584-8525-7363e7a7eb46":{"id":"abaee24f-40a5-4584-8525-7363e7a7eb46","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3952,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"be156d9d-6c3b-4694-b598-0beb95ee57e9":{"id":"be156d9d-6c3b-4694-b598-0beb95ee57e9","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3953,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,000 pyUSD\n- `slope`: 100,000,000 pyUSD per day","contentHash":"f80782c2c744fbbfb08a3495855d92cfbb58a14a09705290306734785335a5c2","addressRefs":[]},"42fbe675-1c41-432c-93cc-67fe79e2718d":{"id":"42fbe675-1c41-432c-93cc-67fe79e2718d","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3954,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"74c6841c-6608-4673-9baa-ffea94f9f699":{"id":"74c6841c-6608-4673-9baa-ffea94f9f699","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3955,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"82a7b2ed-f831-45b5-a888-35ace26aa267":{"id":"82a7b2ed-f831-45b5-a888-35ace26aa267","doc_no":"A.6.1.1.1.2.6.1.3.1.1.5.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3956,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"1eb4affe-3116-4d17-a3c1-0a06b6ac618b":{"id":"1eb4affe-3116-4d17-a3c1-0a06b6ac618b","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6","title":"Ethereum Mainnet - SparkLend ETH Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3957,"content":"The documents herein contain the Instance Configuration Document for the SparkLend ETH Instance.","contentHash":"ecea802a4a2f4fc6471d21c7f42a5ad16aa66afe08406d6f562ec061c07db3e0","addressRefs":[]},"230d8210-e3a2-41d7-8fcc-957f44d9f296":{"id":"230d8210-e3a2-41d7-8fcc-957f44d9f296","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3958,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"a128bf36-a93a-4fc0-aee3-36ff07d542bd":{"id":"a128bf36-a93a-4fc0-aee3-36ff07d542bd","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3959,"content":"The documents herein define the parameters of the SparkLend ETH Instance of the Allocation System Primitive.","contentHash":"906645412fa8dc6a36556ede4a88f04f3f883e14b67796f54223474a7b89fb15","addressRefs":[]},"ec1c764c-f37d-4090-9504-ba4a1f9e74e2":{"id":"ec1c764c-f37d-4090-9504-ba4a1f9e74e2","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3960,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"faa97600-1a42-4d8e-a020-398eef686d5c":{"id":"faa97600-1a42-4d8e-a020-398eef686d5c","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3961,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"8aa492e2-95b4-4806-92b8-626da4d66f96":{"id":"8aa492e2-95b4-4806-92b8-626da4d66f96","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3962,"content":"SparkLend Protocol","contentHash":"502533b7b75b61116678924a53cd7ddd355f6e0d83855732010ce6e38cd35177","addressRefs":[]},"c1c7c252-219c-4cfe-a9c0-998e0520afce":{"id":"c1c7c252-219c-4cfe-a9c0-998e0520afce","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3963,"content":"wETH","contentHash":"03148f9088c3c45c648def5b62ee6c9017f41526d51f77fd7d8560f6721c35d3","addressRefs":[]},"8356bb07-85ee-41a0-a1a7-4071c37dd5a7":{"id":"8356bb07-85ee-41a0-a1a7-4071c37dd5a7","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3964,"content":"spwETH","contentHash":"b0ae15b8eba20521136d76eb1a553d60dedad6dac441375d91bf0bee83f84f7f","addressRefs":[]},"65dd7b46-41e4-4f5e-8f32-ccecf58bf5c2":{"id":"65dd7b46-41e4-4f5e-8f32-ccecf58bf5c2","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3965,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"fa19fb59-fb98-4082-826b-649ce7cdc037":{"id":"fa19fb59-fb98-4082-826b-649ce7cdc037","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3966,"content":"`0x59cD1C87501baa753d0B5B5Ab5D8416A45cD71DB`","contentHash":"15c011472637032e3fc5db3eeb7a6321bc1f6098473392016293b499a878002d","addressRefs":["0x59cd1c87501baa753d0b5b5ab5d8416a45cd71db"]},"3267c66e-aefa-48ec-8f76-62e50eddd1b4":{"id":"3267c66e-aefa-48ec-8f76-62e50eddd1b4","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3967,"content":"`0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`","contentHash":"5ef212c07212264f2e18a396322922471d4c261110a4d732f7bc966d8277fe71","addressRefs":["0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"]},"70bf8d47-0bb2-4650-8830-1d5856eef740":{"id":"70bf8d47-0bb2-4650-8830-1d5856eef740","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3968,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"cef889e791f2b83bcbb0a9c31a4ac27908ed8e42d81e0663f3596e7e35abb973","addressRefs":[]},"22d5d878-bed1-4918-b9e3-fc3b00c56204":{"id":"22d5d878-bed1-4918-b9e3-fc3b00c56204","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.3.1","title":"Inflow Rate Limit ID","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3969,"content":"The inflow RateLimitID is: `0xfd90d9b1f97fedb7eab52e6be9ba5c54b48164e3bef7f0fade829e807354da77`","contentHash":"04bb099b08f3894a12618ef14f79d9f049181e62a6743ea64aaf1aae3b705d7a","addressRefs":[]},"27e77ee3-b59b-4c8b-a729-741627952fb3":{"id":"27e77ee3-b59b-4c8b-a729-741627952fb3","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.3.2","title":"Outflow Rate Limit ID","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3970,"content":"The outflow RateLimitID is: `0x2373d5805bbf5d42574ae53a80e39a0bb90f497f312ccf0b96de71fc6f980909`","contentHash":"556cc989d2bfc5039b1906690a58d7f511a1afac76985d588669bcf72af7e61f","addressRefs":[]},"3ef61462-8f74-4b84-ac42-8b847714b9e8":{"id":"3ef61462-8f74-4b84-ac42-8b847714b9e8","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3971,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"c8320b60-3cf3-4047-aad1-e12cc6ca46f8":{"id":"c8320b60-3cf3-4047-aad1-e12cc6ca46f8","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3972,"content":"The inflow rate limits are:\n\n- `maxAmount`: 50,000 ETH\n- `slope`: 250,000 ETH per day","contentHash":"f3f066676bbd0b758ca0e8db4171b6f37a0087dd3b2617879655d21559fe7b21","addressRefs":[]},"68716e71-a257-4f6c-b227-fba7abc8ec31":{"id":"68716e71-a257-4f6c-b227-fba7abc8ec31","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3973,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"ab2d6946-b18e-4199-a27c-61f44dd1fe7a":{"id":"ab2d6946-b18e-4199-a27c-61f44dd1fe7a","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3974,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"1f909758-9b95-4e50-ba97-4688157d02a5":{"id":"1f909758-9b95-4e50-ba97-4688157d02a5","doc_no":"A.6.1.1.1.2.6.1.3.1.1.6.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3975,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"85b11a45-1718-4ed3-9c64-1471d0887e63":{"id":"85b11a45-1718-4ed3-9c64-1471d0887e63","doc_no":"A.6.1.1.1.2.6.1.3.1.2","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3976,"content":"The Ethereum Mainnet Instances of the Aave Protocol with `Active` Status are stored herein.","contentHash":"c1bc7a2945a5f116328c82aab498852617fa21ae00da6ad74a48e24a86f53ca8","addressRefs":[]},"bf8743ff-bd2e-4fb4-9b2f-2989f0361697":{"id":"bf8743ff-bd2e-4fb4-9b2f-2989f0361697","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1","title":"Ethereum Mainnet - Aave Prime USDS Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3977,"content":"The documents herein contain the Instance Configuration Document for the Aave Prime USDS Instance.","contentHash":"3bf0357c9a5051a9281d152d0889143338751534b974285d55c4d923b4b35ef9","addressRefs":[]},"a11b86fd-7f8b-413f-9e38-99041fa877a2":{"id":"a11b86fd-7f8b-413f-9e38-99041fa877a2","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3978,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"4ff0a9da-8ac6-4b83-882c-8df9602ab191":{"id":"4ff0a9da-8ac6-4b83-882c-8df9602ab191","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3979,"content":"The documents herein define the parameters of the Aave Prime USDS Instance of the Allocation System Primitive.","contentHash":"9eab7f2d43e546af19baed3df8e5719a797c52ebfba12d4856f741fc240c917f","addressRefs":[]},"8f7cadc9-b03e-46ac-a8ea-611777540ef6":{"id":"8f7cadc9-b03e-46ac-a8ea-611777540ef6","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3980,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"e10e7d15-186e-4f26-9746-cf26d0546a19":{"id":"e10e7d15-186e-4f26-9746-cf26d0546a19","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3981,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"1eb3724b-92f7-463a-81a4-6ef14a518383":{"id":"1eb3724b-92f7-463a-81a4-6ef14a518383","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3982,"content":"Aave Prime","contentHash":"6012213c6d9ae6c10585a350a717670fe508aff55fad4c5b43a23be18f1e6bd4","addressRefs":[]},"27e2624c-a0c4-449c-9a04-c08225c1155b":{"id":"27e2624c-a0c4-449c-9a04-c08225c1155b","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3983,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"81123b01-7547-4ad2-a82c-7ee496445525":{"id":"81123b01-7547-4ad2-a82c-7ee496445525","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3984,"content":"aEthLidoUSDS","contentHash":"d2253cc070902f1ddd72951630a8d7ce1a1939167ec1e488e7e8f983ba6fd20f","addressRefs":[]},"afd62e51-3af1-40d6-8918-72c3b7fb95ab":{"id":"afd62e51-3af1-40d6-8918-72c3b7fb95ab","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3985,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"5c10f62b-25cc-4daf-877c-36f9291d585d":{"id":"5c10f62b-25cc-4daf-877c-36f9291d585d","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3986,"content":"`0x09AA30b182488f769a9824F15E6Ce58591Da4781`","contentHash":"466566eb1c8b04960711bcdec495bdac18927ed208416dd0b007b8cd1a962088","addressRefs":["0x09aa30b182488f769a9824f15e6ce58591da4781"]},"6a4979e7-46f8-49ce-acbe-fa8b28d2693a":{"id":"6a4979e7-46f8-49ce-acbe-fa8b28d2693a","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3987,"content":"`0xdC035D45d973E3EC169d2276DDab16f1e407384F`","contentHash":"70054b0ff65437cb32b35df32f8e11d1cc8ea540e9916e08d1cd96696d95e083","addressRefs":["0xdc035d45d973e3ec169d2276ddab16f1e407384f"]},"c358ae91-bc20-4c39-9a31-7f867fab56e4":{"id":"c358ae91-bc20-4c39-9a31-7f867fab56e4","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.2.3","title":"Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3988,"content":"This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"ea3c5d84119733fb3a2a429f279628dcce722f210f012ad0286de1cf9435e132","addressRefs":[]},"7e6afc3c-5c09-4ca4-9c2c-05aa9ed85e67":{"id":"7e6afc3c-5c09-4ca4-9c2c-05aa9ed85e67","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3989,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"46a1c28f-f4e4-4c45-9a89-1d88b50bf57b":{"id":"46a1c28f-f4e4-4c45-9a89-1d88b50bf57b","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3990,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"4ed25455-3128-4395-9b58-cf24e275498c":{"id":"4ed25455-3128-4395-9b58-cf24e275498c","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3991,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 50,000,000 USDS per day","contentHash":"2752257a58ac813d1e36f0e711717d108a09435b51383e4c47e86342064eff56","addressRefs":[]},"6dc14672-e655-49fd-a351-45537408c74b":{"id":"6dc14672-e655-49fd-a351-45537408c74b","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3992,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: Unlimited","contentHash":"55f2afe4138f46e4ed73589852a0887ee907f02eb1fc355e4edab05a25597846","addressRefs":[]},"25a46c53-dca4-43ef-876a-64b5cea91fb6":{"id":"25a46c53-dca4-43ef-876a-64b5cea91fb6","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3993,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"7895798c-50e2-4fa6-b4e9-5b9f259f822d":{"id":"7895798c-50e2-4fa6-b4e9-5b9f259f822d","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3994,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes. For the general operational procedures applicable to all Aave-type instances. See [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3 - Aave Functions](9922dcf0-4562-445b-9a46-712f677cce64) and [A.6.1.1.1.2.6.1.2.2.3.2.3 - Aave AToken Withdrawal Action](2560adbb-4a5c-4c95-86cb-04647bb33836).","contentHash":"456451a11c408aeaf25fc6b30c64b161f1fe752751e2a9b897062de3468ebcff","addressRefs":[]},"fa2520ac-4779-4aeb-abe4-2c1b89e7ca51":{"id":"fa2520ac-4779-4aeb-abe4-2c1b89e7ca51","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1","title":"Process Definition For Depositing","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3995,"content":"The documents herein define the steps to deposit assets from the ALM Proxy to the Aave pool to receive yield-bearing ATokens.","contentHash":"54469270ab9fb27ed4237105a013e0f8e3a372217d9ac3997edef790657c23c3","addressRefs":[]},"25fd8f89-cb76-464e-b659-e2e1885ac4c5":{"id":"25fd8f89-cb76-464e-b659-e2e1885ac4c5","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3996,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `depositAave`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction depositAave(address aToken, uint256 amount)\nexternal\nonlyRole(RELAYER)\nisActive\n```","contentHash":"99be85f86c2e2f162924d1199814cf6217893711a05d27893c08c59fd527e7a3","addressRefs":[]},"d3977382-1434-4958-8910-b0f61a5aecc7":{"id":"d3977382-1434-4958-8910-b0f61a5aecc7","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.2","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3997,"content":"The operator must ensure ALM Proxy holds enough of the underlying asset to cover the instructed `deposit` amount.","contentHash":"74cbd2e77dd43fb3cbf812063fa76f321bcacf34aeff447a05fcf21da7a3a5e5","addressRefs":[]},"bda7b89b-9065-4fa0-b7c1-903ef0b9a41b":{"id":"bda7b89b-9065-4fa0-b7c1-903ef0b9a41b","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.3","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3998,"content":"The operator must ensure the `deposit` amount is allowed within the `RateLimits`.\n\n        `rateLimited(\nRateLimitHelpers.makeAssetKey(LIMIT_AAVE_DEPOSIT, aToken),\namount\n)`","contentHash":"4912917bf903a80c39864fd1a0cffbbc22a2896bd3400dd321af0ab561f92a08","addressRefs":[]},"87922fd8-ff01-40d4-b6cc-c72f4a1b322e":{"id":"87922fd8-ff01-40d4-b6cc-c72f4a1b322e","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.4","title":"Initialize ERC-20 Token Interface","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":3999,"content":"The operator must initialize the `underlying` variable as an ERC-20 token interface.","contentHash":"4f1b68514343a2d4a9346d2f67519e332e05651a2b2b52f590546f35745d65b9","addressRefs":[]},"19fbd6f2-f303-4ad2-a56c-b3761bfc3b13":{"id":"19fbd6f2-f303-4ad2-a56c-b3761bfc3b13","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.4.1","title":"Initialize Interface For Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4000,"content":"The operator must initialize the interface for the `address of the underlying asset` retrieved from the `aToken` contract (the contract that represents the deposited assets in Aave). The `IERC20` interface allows interaction with ERC-20 tokens, including performing actions like transferring, approving, and checking balances.\n\n```\n {\nIERC20    underlying = IERC20(IATokenWithPool(aToken).UNDERLYING_ASSET_ADDRESS());\n```","contentHash":"fe27f5c57c8c91735e963cbb67bd11a28c8b26c90f2f6fb9c437cfd8751e6dbb","addressRefs":[]},"7ab77ba4-3513-4661-b08c-41b24f73cb59":{"id":"7ab77ba4-3513-4661-b08c-41b24f73cb59","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.5","title":"Initialize Pool Variable","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4001,"content":"The operator must initialize the `pool` variable as an interface for the Aave pool.","contentHash":"c4d585f0a137f69d18237fcc3dd0eecced4b9918d2b2542b08eeca700a0fe6b9","addressRefs":[]},"5b405222-e981-44b7-853b-09d1976fdbbb":{"id":"5b405222-e981-44b7-853b-09d1976fdbbb","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.5.1","title":"Retrieve Aave Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4002,"content":"The operator must retrieve the Aave pool contract address associated with the given `aToken`. This address represents the Aave lending pool where the assets are deposited. `IAavePool` interface allows interaction with the Aave pool's functions (like `supply`).\n\n`    IAavePool pool       = IAavePool(IATokenWithPool(aToken).POOL());`","contentHash":"faa8e98c96420e1a6e47a85c4a65c180e3bec20b9ba0583e39f3ce72401393ba","addressRefs":[]},"989427e7-7ced-49a9-88b1-df3c461b15b6":{"id":"989427e7-7ced-49a9-88b1-df3c461b15b6","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.6","title":"Call Approve Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4003,"content":"The operator must call the `approve` function to update the allowance of the `underlying` asset contract.","contentHash":"c383dbdf14bef5140bb79d4c709ebf8488299088f4e6a1c074ec9b518eb438af","addressRefs":[]},"b4c5ecdf-c38f-47fa-93ff-d914ea520c19":{"id":"b4c5ecdf-c38f-47fa-93ff-d914ea520c19","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.6.1","title":"Encode Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4004,"content":"The operator must encode the `approve` function call, using `abi.encodeCall` allowing the Aave `pool` address to spend up to `amount` of the `underlying` token from the ALM Proxy’s balance.","contentHash":"7a3109f22d431339bab5847bb6864f308b917d07a13fa1163336ca696a962207","addressRefs":[]},"79ba7e11-2adf-45fa-a73f-4c20ba1efc27":{"id":"79ba7e11-2adf-45fa-a73f-4c20ba1efc27","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.6.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4005,"content":"The operator must send the encoded call using `proxy.doCall()` specifying the `address` of the `asset` contract they want to deposit into.\n\n       `// Approve underlying to Aave pool from the proxy (assumes the proxy has enough underlying).\nproxy.doCall(\naddress(underlying),\nabi.encodeCall(underlying.approve, (address(pool), amount))\n);`","contentHash":"11198044d1a6439797e109face3013a079d27cfa36d924bfc2aa6bae0d677e39","addressRefs":[]},"ce52a39f-a0dc-4df4-8a34-1f4be4b3443a":{"id":"ce52a39f-a0dc-4df4-8a34-1f4be4b3443a","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.7","title":"Call Deposit Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4006,"content":"The operator must call the `deposit` function to transfer the `underlying` asset to the Aave lending pool and receive the `aTokens`.","contentHash":"1e3d0d6be5223caa6ade65c7728f623b968ebda0ea95e2dd29daa45314a3a0cd","addressRefs":[]},"7d5b7673-1d17-4d64-9777-9d584d99ada6":{"id":"7d5b7673-1d17-4d64-9777-9d584d99ada6","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.7.1","title":"Encode Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4007,"content":"The operator must encode the `deposit` function call, using `abi.encodeCall` with the address of the `underlying` token, the `amount` of the underlying asset to `deposit` and the `address(proxy)` that will receive the resulting `aTokens` (i.e. ALM Proxy).","contentHash":"253363111e8d68af3c3f961d64b8a6af22a656e3285bbeb019310dd40f022b47","addressRefs":[]},"58ca518e-9ff1-4008-9616-18f135a33772":{"id":"58ca518e-9ff1-4008-9616-18f135a33772","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.1.7.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4008,"content":"The operator must send the encoded call using `proxy.doCall()` to the `supply` function on Aave (`pool`).\n\n        `// Deposit underlying into Aave pool, proxy receives aTokens\nproxy.doCall(\naddress(pool),\nabi.encodeCall(pool.supply, (address(underlying), amount, address(proxy), 0))\n);\n}`","contentHash":"24a8b5fd045e64677d7b0d114fb03538e3d6f6fe7be68ba6cabe7f5aed6d97bd","addressRefs":[]},"35e32620-a28c-4101-a881-2b7c2b9e42f2":{"id":"35e32620-a28c-4101-a881-2b7c2b9e42f2","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2","title":"Process Definition For Withdrawing","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4009,"content":"The documents herein define the steps for an operator to withdraw a yield-earning balance from the Aave AToken vaults to the ALM Proxy.","contentHash":"d4eb53c797ac43e3a7a5b2ca879a1f945e15b4449a425fd4919e36d0cdd0270e","addressRefs":[]},"9daa0cad-61ef-43e3-9e78-aaddde2e5c35":{"id":"9daa0cad-61ef-43e3-9e78-aaddde2e5c35","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4010,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `withdrawAave` tokens. Also, they ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction withdrawAave(address aToken, uint256 amount)\nexternal\nonlyRole(RELAYER)\nisActive\n```","contentHash":"3c899d9c1c0f44670fefdf3ce6ce6bdf4227fb60fbd6749aa803a66c0d41177c","addressRefs":[]},"4a206a15-75a3-44b5-a95d-faad248ded5e":{"id":"4a206a15-75a3-44b5-a95d-faad248ded5e","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.2","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4011,"content":"The operator must ensure the ALM Proxy holds sufficient `aTokens` to cover the instructed `withdraw` amount.","contentHash":"5937bb29add1ee221964695f00f946d7ac50f64bc302b9d57f9149037bb2f6d4","addressRefs":[]},"e5e9c15f-dd74-44c3-b6fc-e9855a66bcba":{"id":"e5e9c15f-dd74-44c3-b6fc-e9855a66bcba","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.3","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4012,"content":"The operator must ensure the `withdraw` amount is allowed within the `RateLimits`.\n\n```\n// Check withdrawal limits.\nrateLimited(\nRateLimitHelpers.makeAssetKey(LIMIT_AAVE_WITHDRAW, aToken),\namount\n)\n```","contentHash":"ea9950ce4f22332d15a15347e4e8c964f6b878460e45928209c151b85ccd5c45","addressRefs":[]},"8c529eb7-aaaa-4c25-9040-6513d5ca02a5":{"id":"8c529eb7-aaaa-4c25-9040-6513d5ca02a5","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.4","title":"Initialize Pool Variable","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4013,"content":"The operator must initialize the `pool` variable as an interface for the Aave pool.","contentHash":"c4d585f0a137f69d18237fcc3dd0eecced4b9918d2b2542b08eeca700a0fe6b9","addressRefs":[]},"9349014e-68e7-4832-bbab-d0d9fa34607b":{"id":"9349014e-68e7-4832-bbab-d0d9fa34607b","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.5","title":"Retrieve Aave Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4014,"content":"The operator must retrieve the Aave pool contract address associated with the given `aToken`. This address represents the Aave lending pool from which the assets are withdrawn.\n\n    `IAavePool pool       = IAavePool(IATokenWithPool(aToken).POOL());`","contentHash":"d1166e488839619af70630215de859d6c107b40a4083ed7896efc825d07cd62f","addressRefs":[]},"5fb6e805-a394-4cfd-a788-bdb9bb4ff1c9":{"id":"5fb6e805-a394-4cfd-a788-bdb9bb4ff1c9","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.6","title":"Call Withdraw Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4015,"content":"The operator must call the `withdraw` function to withdraw a required amount of `underlying` asset from Aave `pool` address and receive the corresponding `aTokens`.","contentHash":"ef15bd0c2153c45e4700b0b45fec2107747d006d83fb924ac5543d5e955bdf6f","addressRefs":[]},"d0168bc6-231f-44b8-87f6-b1cad0d742cc":{"id":"d0168bc6-231f-44b8-87f6-b1cad0d742cc","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.6.1","title":"Encode Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4016,"content":"The operator must encode the `withdraw` function using `abi.encodeCall` with the `underlying asset address` from the `aToken` contract, specifying which token is being withdrawn, the `amount` of the underlying asset to `withdraw`, and the `address(proxy)` of the recipient of the withdrawn assets (i.e. ALM Proxy).","contentHash":"52d32b36888d8a0303e6a1218e16bf059e52610ef313fcb5a4b79c4be6d72d54","addressRefs":[]},"664e5cea-9efb-4db8-96b1-3afee35d4860":{"id":"664e5cea-9efb-4db8-96b1-3afee35d4860","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.6.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4017,"content":"The operator must send the encoded call using `proxy.doCall()` to the `withdraw` function of the Aave `pool` contract.","contentHash":"d6f977af00413d8d758e182665b36e70c543a3279b8e1098b780de28a3f066bb","addressRefs":[]},"c4eb149e-8d0b-4e5b-93c6-49c67b2221a3":{"id":"c4eb149e-8d0b-4e5b-93c6-49c67b2221a3","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.6.3","title":"Decode For Underlying Assets","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4018,"content":"The operator must decode the raw bytes data returned from the `doCall()` function into `uint256` value, representing the amount of underlying assets that were successfully withdrawn from the Aave pool (`amountWithdrawn`).\n\n       ` // Withdraw underlying from Aave pool, decode resulting amount withdrawn.\n// Assumes proxy has adequate aTokens.\namountWithdrawn = abi.decode(\nproxy.doCall(\naddress(pool),\nabi.encodeCall(\npool.withdraw,\n(IATokenWithPool(aToken).UNDERLYING_ASSET_ADDRESS(), amount, address(proxy))\n)\n),\n(uint256)\n);`","contentHash":"9bbdbfb6468c7937a06d3957b9130b6baea31b7f198da3e3d1aade356573b5cc","addressRefs":[]},"835ceecc-82b0-4c00-8ba3-86d5a8cd782e":{"id":"835ceecc-82b0-4c00-8ba3-86d5a8cd782e","doc_no":"A.6.1.1.1.2.6.1.3.1.2.1.3.2.7","title":"Decrease RateLimit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4019,"content":"The operator must decrease the `RateLimit` based on the assets redeemed.\n\n```\nrateLimits.triggerRateLimitDecrease(\n            RateLimitHelpers.makeAssetKey(LIMIT_AAVE_WITHDRAW, aToken),\n            amountWithdrawn\n        );\n    }\n```","contentHash":"85c0bd332b0d98ef2bb4873345a374d9c010209a6e8198b96eec41c5f9248600","addressRefs":[]},"bba861d8-9307-4e7f-ac54-f636232baff1":{"id":"bba861d8-9307-4e7f-ac54-f636232baff1","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2","title":"Ethereum Mainnet - Aave Core USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4020,"content":"The documents herein contain the Instance Configuration Document for the Aave Core USDC Instance.","contentHash":"385f25d28338d3c0c62ac9472151a67fb0c969c9b25cce27e10d1893180d7b65","addressRefs":[]},"8c579e3f-9096-4825-911b-db2864752443":{"id":"8c579e3f-9096-4825-911b-db2864752443","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4021,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"e267a558-6217-4016-b86e-0bfe96a4b2f1":{"id":"e267a558-6217-4016-b86e-0bfe96a4b2f1","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4022,"content":"The documents herein define the parameters of the Aave Core USDC Instance of the Allocation System Primitive.","contentHash":"b9e5dcd4ff4dbace058d5cc3c9a04307b658beba97ab656e108b6a8d9b939ccf","addressRefs":[]},"eb139f3f-92ca-47f1-950c-bd226382a5e5":{"id":"eb139f3f-92ca-47f1-950c-bd226382a5e5","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4023,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"74de563a-acff-48ae-abf5-088d1eb75b1d":{"id":"74de563a-acff-48ae-abf5-088d1eb75b1d","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4024,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"74942ea3-011d-47fa-8020-709ec4b008df":{"id":"74942ea3-011d-47fa-8020-709ec4b008df","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4025,"content":"Aave Core","contentHash":"d07b51f839531e3a0f2e42359b9fffd1799e829bc696651eeb7889d98f7b2c3d","addressRefs":[]},"e339e615-59df-4714-9d05-9fa9864abd00":{"id":"e339e615-59df-4714-9d05-9fa9864abd00","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4026,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"25ce1351-b3f8-45d1-9a50-ac199f099c33":{"id":"25ce1351-b3f8-45d1-9a50-ac199f099c33","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4027,"content":"aEthUSDC","contentHash":"d71f3701842f707489c99da586c42ac19abe79e7f02ab0d27aaa872e3606098c","addressRefs":[]},"4e9d183a-5b07-46a1-8591-f43fd13c32a0":{"id":"4e9d183a-5b07-46a1-8591-f43fd13c32a0","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4028,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"2f0e8c66-aabb-48c0-a9ed-d9a7d0652737":{"id":"2f0e8c66-aabb-48c0-a9ed-d9a7d0652737","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4029,"content":"`0x98C23E9d8f34FEFb1B7BD6a91B7FF122F4e16F5c`","contentHash":"b05fdf296174c1f48064da3b1bde6684a1902c132484896fd2d67d96807c529e","addressRefs":["0x98c23e9d8f34fefb1b7bd6a91b7ff122f4e16f5c"]},"a11796f1-e89e-4dfc-b53e-0ab6527cc025":{"id":"a11796f1-e89e-4dfc-b53e-0ab6527cc025","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4030,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"b3b677e8-a154-4c5a-9e88-5222716a806d":{"id":"b3b677e8-a154-4c5a-9e88-5222716a806d","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4031,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"4b08586e-4e28-404d-90c4-29a44fc29cb5":{"id":"4b08586e-4e28-404d-90c4-29a44fc29cb5","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4032,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"6b65dffb-15a2-4c2c-83a2-ef5325b1f8cc":{"id":"6b65dffb-15a2-4c2c-83a2-ef5325b1f8cc","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4033,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 25,000,000 USDC per day","contentHash":"7d84d9f4173122f32102d13ebffc575af717302b88c34986a1e928e96e92dfd2","addressRefs":[]},"89b3f4e4-c845-4a6c-bdce-a383bf11a947":{"id":"89b3f4e4-c845-4a6c-bdce-a383bf11a947","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4034,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: Unlimited","contentHash":"55f2afe4138f46e4ed73589852a0887ee907f02eb1fc355e4edab05a25597846","addressRefs":[]},"9ff8418d-457e-4ce3-83c4-18c5ae3b35d7":{"id":"9ff8418d-457e-4ce3-83c4-18c5ae3b35d7","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4035,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"5b51c049-870b-407e-bce9-2d383c8eb961":{"id":"5b51c049-870b-407e-bce9-2d383c8eb961","doc_no":"A.6.1.1.1.2.6.1.3.1.2.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4036,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"1191f33a-dc78-4c2f-bc5e-e85802471c60":{"id":"1191f33a-dc78-4c2f-bc5e-e85802471c60","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3","title":"Ethereum Mainnet - Aave Core USDS Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4037,"content":"The documents herein contain the Instance Configuration Document for the Aave Core USDS Instance.","contentHash":"03be0e0d20c897a316268c5516434fbae6fa32ac34d88eb7f71d44ebde34ec72","addressRefs":[]},"92f8531a-927d-43b4-aaea-7da957606df2":{"id":"92f8531a-927d-43b4-aaea-7da957606df2","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4038,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"c2823616-9db0-47f8-a25e-4bc5fa9bad77":{"id":"c2823616-9db0-47f8-a25e-4bc5fa9bad77","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4039,"content":"The documents herein define the parameters of the Aave Core USDS Instance of the Allocation System Primitive.","contentHash":"595475a5e621e5e53de7939ede1d12931ce5c33a52e5b19f31dd36a61973104f","addressRefs":[]},"f2255528-1c74-49f6-a745-d5e6ab6e1ffd":{"id":"f2255528-1c74-49f6-a745-d5e6ab6e1ffd","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4040,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"854b6f90-e44a-401c-9786-397f102e9206":{"id":"854b6f90-e44a-401c-9786-397f102e9206","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4041,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"247554ce-878e-4e52-9cc4-38dc6d9a280c":{"id":"247554ce-878e-4e52-9cc4-38dc6d9a280c","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4042,"content":"Aave Core","contentHash":"d07b51f839531e3a0f2e42359b9fffd1799e829bc696651eeb7889d98f7b2c3d","addressRefs":[]},"c2d4fcec-44fb-45ca-94d0-529b559797c8":{"id":"c2d4fcec-44fb-45ca-94d0-529b559797c8","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4043,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"527bb529-4641-47f9-94de-b9cdf54f8db2":{"id":"527bb529-4641-47f9-94de-b9cdf54f8db2","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4044,"content":"aEthUSDS","contentHash":"d4faa6facd0dd7bcd4ac9622c6dc6628d4ca8995647312b4cebbee0e777532a3","addressRefs":[]},"29dbed1a-ba1b-4424-b74e-b3a4842dbfca":{"id":"29dbed1a-ba1b-4424-b74e-b3a4842dbfca","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4045,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"b1c3fe3e-922f-4261-ab62-f0103b5a1cdd":{"id":"b1c3fe3e-922f-4261-ab62-f0103b5a1cdd","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4046,"content":"`0x32a6268f9Ba3642Dda7892aDd74f1D34469A4259`","contentHash":"46283d836d23cd561155b628b2b8b8008689a6ff95b5b8ee81c3d9de76b52a27","addressRefs":["0x32a6268f9ba3642dda7892add74f1d34469a4259"]},"f366a310-9e3a-4b4f-9437-4fa3bbf72d65":{"id":"f366a310-9e3a-4b4f-9437-4fa3bbf72d65","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4047,"content":"`0xdC035D45d973E3EC169d2276DDab16f1e407384F`","contentHash":"70054b0ff65437cb32b35df32f8e11d1cc8ea540e9916e08d1cd96696d95e083","addressRefs":["0xdc035d45d973e3ec169d2276ddab16f1e407384f"]},"e444d574-2b11-4187-a45f-9a80d75aae10":{"id":"e444d574-2b11-4187-a45f-9a80d75aae10","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4048,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"71151ae6-4224-426c-a8fa-5ba03cf64b5a":{"id":"71151ae6-4224-426c-a8fa-5ba03cf64b5a","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4049,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"27876101-2e16-4a33-811d-c662df211b2c":{"id":"27876101-2e16-4a33-811d-c662df211b2c","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4050,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 25,000,000 USDS per day","contentHash":"27e65a7ab7cf10617aff88a27fa5758b87812bfef0d8595f71d98b669935846f","addressRefs":[]},"c02c329a-9e38-472b-ae0f-b2974694982e":{"id":"c02c329a-9e38-472b-ae0f-b2974694982e","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4051,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: Unlimited","contentHash":"55f2afe4138f46e4ed73589852a0887ee907f02eb1fc355e4edab05a25597846","addressRefs":[]},"07ce54dc-92dd-4f7e-a9ef-53760b999de7":{"id":"07ce54dc-92dd-4f7e-a9ef-53760b999de7","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4052,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"c0533414-3031-43a7-9e9f-99160976b9b1":{"id":"c0533414-3031-43a7-9e9f-99160976b9b1","doc_no":"A.6.1.1.1.2.6.1.3.1.2.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4053,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"c8bcfd26-cab2-43f6-9c35-ad13571fcf1e":{"id":"c8bcfd26-cab2-43f6-9c35-ad13571fcf1e","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4","title":"Ethereum Mainnet - Aave Core USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4054,"content":"The documents herein contain the Instance Configuration Document for the Aave Core USDT Instance.","contentHash":"ec74df875e919f92d6cff5613ead5be3f59590b108941fe3a6c0081f9134745c","addressRefs":[]},"33dd70f8-51c4-487b-9e08-f2204349aaf3":{"id":"33dd70f8-51c4-487b-9e08-f2204349aaf3","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4055,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"2eabaaa2-b4a0-4a76-a872-20b1fa49949d":{"id":"2eabaaa2-b4a0-4a76-a872-20b1fa49949d","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4056,"content":"The documents herein define the parameters of the Aave Core USDT Instance of the Allocation System Primitive.","contentHash":"83a4e8a698178b58d66da497f89627b84e5ac7d1b1e9b74be23f81954e40ded0","addressRefs":[]},"25929517-be4b-4a41-bbc8-41f19a24885f":{"id":"25929517-be4b-4a41-bbc8-41f19a24885f","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4057,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"e041990b-f947-4c53-9bf7-5b12c7c45a37":{"id":"e041990b-f947-4c53-9bf7-5b12c7c45a37","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4058,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"7e47cc90-7bb8-465f-b528-266b6b967d05":{"id":"7e47cc90-7bb8-465f-b528-266b6b967d05","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4059,"content":"Aave Core","contentHash":"d07b51f839531e3a0f2e42359b9fffd1799e829bc696651eeb7889d98f7b2c3d","addressRefs":[]},"08e907a6-86fb-4e34-a795-01439955467c":{"id":"08e907a6-86fb-4e34-a795-01439955467c","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4060,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"36025c5c-99be-43f8-8f52-fe90fac62efb":{"id":"36025c5c-99be-43f8-8f52-fe90fac62efb","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4061,"content":"aEthUSDT","contentHash":"7b3e4f2ee432cc1071dc16e52139e1c6c462312220da2f9a5731dab21af15bcc","addressRefs":[]},"3264c038-e7ac-4127-81a7-bb74ffdfc3c9":{"id":"3264c038-e7ac-4127-81a7-bb74ffdfc3c9","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4062,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"6f712e66-f262-4db6-b846-282865e16156":{"id":"6f712e66-f262-4db6-b846-282865e16156","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4063,"content":"`0x23878914EFE38d27C4D67Ab83ed1b93A74D4086a`","contentHash":"74993864af526739467e126fe0c599a2b64d0e998b124307f5b5086aeeadaffb","addressRefs":["0x23878914efe38d27c4d67ab83ed1b93a74d4086a"]},"1f74c7a5-f038-4bc6-824b-6005ff313297":{"id":"1f74c7a5-f038-4bc6-824b-6005ff313297","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4064,"content":"`0xdAC17F958D2ee523a2206206994597C13D831ec7`","contentHash":"d674f514fb5256107f891afe7b796353b6535b08717e30bc071e1ccdf11a1fbf","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"b4612996-b947-467b-a982-9791daf37a1f":{"id":"b4612996-b947-467b-a982-9791daf37a1f","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4065,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"2b7b02e3-b63a-445f-86bb-098627ae20ed":{"id":"2b7b02e3-b63a-445f-86bb-098627ae20ed","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4066,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"42c4a115-4fed-4d24-a260-d86dc2a71bea":{"id":"42c4a115-4fed-4d24-a260-d86dc2a71bea","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4067,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,000 USDT\n- `slope`: 1,000,000,000 USDT per day","contentHash":"31ff6f5aa4187c8b1b8a073defc04598d376e3475eb13288e481756001f7ba9a","addressRefs":[]},"c52a5acc-ef73-4e13-ab15-8c1c1daf12a6":{"id":"c52a5acc-ef73-4e13-ab15-8c1c1daf12a6","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4068,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"569b0f886c9aedda81b4e87d26e1e21d96763dd2e909e2e9865edcf064b320e5","addressRefs":[]},"8587305b-0af4-49e0-b156-e270d64e69da":{"id":"8587305b-0af4-49e0-b156-e270d64e69da","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4069,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"70a5413e-80da-43b6-8e40-32865d9a28f9":{"id":"70a5413e-80da-43b6-8e40-32865d9a28f9","doc_no":"A.6.1.1.1.2.6.1.3.1.2.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4070,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"8bd798af-96fc-4fc4-9fb7-5b351740a962":{"id":"8bd798af-96fc-4fc4-9fb7-5b351740a962","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5","title":"Ethereum Mainnet - Aave USDe Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4071,"content":"The documents herein contain the Instance Configuration Document for the Aave USDe Instance.","contentHash":"cb43993371840bea1f138904d3fd339aa2ce5ef1592f71d7ad7cf1fe7ce19086","addressRefs":[]},"29315031-1577-49d5-b40f-f818c945a047":{"id":"29315031-1577-49d5-b40f-f818c945a047","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4072,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"bbfe8d2f-b82a-471e-a9d5-78892abc3465":{"id":"bbfe8d2f-b82a-471e-a9d5-78892abc3465","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4073,"content":"The documents herein define the parameters of the Aave Core USDe Instance of the Allocation System Primitive.","contentHash":"fa45df493c4cec595e6570ab8e54a489cf210b0b5e694285afe2f338bced1835","addressRefs":[]},"670dce17-03d2-4815-94b5-c58406b8b40d":{"id":"670dce17-03d2-4815-94b5-c58406b8b40d","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4074,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"12dde8d6-ff41-4c34-bf15-fe5c28e0f3c3":{"id":"12dde8d6-ff41-4c34-bf15-fe5c28e0f3c3","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4075,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"b5fc5332-162f-45ca-b7a4-c6669f42134e":{"id":"b5fc5332-162f-45ca-b7a4-c6669f42134e","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4076,"content":"Aave Core","contentHash":"d07b51f839531e3a0f2e42359b9fffd1799e829bc696651eeb7889d98f7b2c3d","addressRefs":[]},"4015efa4-bed3-476a-bfc8-dec3d2909604":{"id":"4015efa4-bed3-476a-bfc8-dec3d2909604","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4077,"content":"USDe","contentHash":"9613d0cae557ec7702d9883e3926c60f107d41e7349456c05d3806dd74a255b9","addressRefs":[]},"a40aaf6a-b29f-413b-987d-bdf3a8bbf9c3":{"id":"a40aaf6a-b29f-413b-987d-bdf3a8bbf9c3","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4078,"content":"aEthUSDe","contentHash":"e420c2912a68b0ebfb5f0db90a424634901bbf1dbcefb2bef054fa1d152265f9","addressRefs":[]},"54fac347-de59-4a8f-a9cf-bd7fe0ccdcfb":{"id":"54fac347-de59-4a8f-a9cf-bd7fe0ccdcfb","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4079,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"6f8813ff-3f2c-4eb1-be25-10b6b428781d":{"id":"6f8813ff-3f2c-4eb1-be25-10b6b428781d","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4080,"content":"`0x4F5923Fc5FD4a93352581b38B7cD26943012DECF`","contentHash":"3e412c3b90b5d40eaaf2f8328fa4a44485d4c4ba7efa7ff00bde9b2bb0738e50","addressRefs":["0x4f5923fc5fd4a93352581b38b7cd26943012decf"]},"a0682e7a-b111-4283-80c9-e806dd1bd225":{"id":"a0682e7a-b111-4283-80c9-e806dd1bd225","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4081,"content":"`0x4c9EDD5852cd905f086C759E8383e09bff1E68B3`","contentHash":"af8f3aca379b74340581939474b84e3badef16e17802b2b71cfa3cb6f05cb267","addressRefs":["0x4c9edd5852cd905f086c759e8383e09bff1e68b3"]},"4fbb1a36-0889-4258-a7e9-0f1ab7d2b00e":{"id":"4fbb1a36-0889-4258-a7e9-0f1ab7d2b00e","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4082,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"c8b82f71-acd7-4ccc-8067-ceab3bb46f53":{"id":"c8b82f71-acd7-4ccc-8067-ceab3bb46f53","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4083,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"ce159b4f-4e1a-48e9-9a73-b16c5fe19288":{"id":"ce159b4f-4e1a-48e9-9a73-b16c5fe19288","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4084,"content":"The inflow rate limits are:\n\n- `maxAmount`: 250,000,000 USDe\n- `slope`: 100,000,000 USDe per day","contentHash":"7e94e27b246ede497661a1e8eed573d41b50e2f38889ed4a8695c039234962f7","addressRefs":[]},"a773878d-3f7c-492c-9486-139788f5b50f":{"id":"a773878d-3f7c-492c-9486-139788f5b50f","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4085,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"569b0f886c9aedda81b4e87d26e1e21d96763dd2e909e2e9865edcf064b320e5","addressRefs":[]},"0d912386-ce60-4018-bc95-6403b2316fce":{"id":"0d912386-ce60-4018-bc95-6403b2316fce","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4086,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"fdb9edc5-6934-4a5a-8806-d835a6729de0":{"id":"fdb9edc5-6934-4a5a-8806-d835a6729de0","doc_no":"A.6.1.1.1.2.6.1.3.1.2.5.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4087,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"0d069124-5ef8-4152-96d8-30980e522df9":{"id":"0d069124-5ef8-4152-96d8-30980e522df9","doc_no":"A.6.1.1.1.2.6.1.3.1.3","title":"Maple","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4088,"content":"The Ethereum Mainnet Instances of the Maple Protocol with `Active` Status are stored herein.","contentHash":"8fc7c8ba100ab5d1abcce02e163a69acc6af84061a97d576f93c43fc63481e53","addressRefs":[]},"06a83573-f319-4a56-a2bd-4389086dd2bf":{"id":"06a83573-f319-4a56-a2bd-4389086dd2bf","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1","title":"Ethereum Mainnet - Maple USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4089,"content":"The documents herein contain the Instance Configuration Document for the Maple USDC Instance.","contentHash":"1f0b8dcfe605b4906709f0bad210660334f119702f681e347f3f6e7d7567a5ed","addressRefs":[]},"7cc5a238-418d-4301-bf78-de8f5fa5669c":{"id":"7cc5a238-418d-4301-bf78-de8f5fa5669c","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4090,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"305d6ee1-997d-47bd-94ed-4c28fc8a6e1c":{"id":"305d6ee1-997d-47bd-94ed-4c28fc8a6e1c","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4091,"content":"The documents herein define the parameters of the Maple USDC Instance of the Allocation System Primitive.","contentHash":"bc52815c6a6edbb05f61c0586baf40df733aaa345107b7fcd1ac535777faefd7","addressRefs":[]},"5005b27d-46a7-45a6-a8b7-68496fb343e5":{"id":"5005b27d-46a7-45a6-a8b7-68496fb343e5","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4092,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"0577f89a-0ecf-4f99-a43b-880885b0fb84":{"id":"0577f89a-0ecf-4f99-a43b-880885b0fb84","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4093,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"a2c71d09-8578-4854-98ae-8d122343dbed":{"id":"a2c71d09-8578-4854-98ae-8d122343dbed","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4094,"content":"Maple","contentHash":"187c93774dbd4c674ecaf745f0c304bb494ccfca31cd88c028251f97f09569c5","addressRefs":[]},"6431d5f7-1e50-4537-902f-0d772ee3f08e":{"id":"6431d5f7-1e50-4537-902f-0d772ee3f08e","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4095,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"5f4e0d3c-f3b4-4e1e-b3ea-59c3883df0c8":{"id":"5f4e0d3c-f3b4-4e1e-b3ea-59c3883df0c8","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4096,"content":"syrupUSDC","contentHash":"3b50b2203f4915b0b7b3098fc5d9205e27421a900c9bf60f5fe7d484e2a25003","addressRefs":[]},"0802482b-d11d-43d7-992a-8fde39fdcf2c":{"id":"0802482b-d11d-43d7-992a-8fde39fdcf2c","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4097,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"953bd87a-5781-42f1-b989-f9ab267bc707":{"id":"953bd87a-5781-42f1-b989-f9ab267bc707","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4098,"content":"`0x80ac24aA929eaF5013f6436cdA2a7ba190f5Cc0b`","contentHash":"c9da76a92fdbedaeaebc89f6ae1550989ebcbf6b96f68777626b48b5da9dfbce","addressRefs":["0x80ac24aa929eaf5013f6436cda2a7ba190f5cc0b"]},"acb94b04-e58a-4948-9a85-aaf6887d8f65":{"id":"acb94b04-e58a-4948-9a85-aaf6887d8f65","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4099,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"80ab522b-2f60-4d3a-bcd7-63f728f180f9":{"id":"80ab522b-2f60-4d3a-bcd7-63f728f180f9","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.2.3","title":"Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4100,"content":"`0x80ac24aA929eaF5013f6436cdA2a7ba190f5Cc0b`","contentHash":"c9da76a92fdbedaeaebc89f6ae1550989ebcbf6b96f68777626b48b5da9dfbce","addressRefs":["0x80ac24aa929eaf5013f6436cda2a7ba190f5cc0b"]},"8fd1f7ba-7c0b-4414-be6d-a45a1e263966":{"id":"8fd1f7ba-7c0b-4414-be6d-a45a1e263966","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4101,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"d3641a4d-6104-4dc9-90ff-d4c7d1766917":{"id":"d3641a4d-6104-4dc9-90ff-d4c7d1766917","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4102,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"b5d5ba32-342f-4d98-a51e-4d43ff458b48":{"id":"b5d5ba32-342f-4d98-a51e-4d43ff458b48","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4103,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"37b3e463c9d79a8ccd63f266485879aaf0f51aaf0168bd8c0196cddaf81375ec","addressRefs":[]},"ce4681b7-b94f-4acb-a2de-49b92b70245b":{"id":"ce4681b7-b94f-4acb-a2de-49b92b70245b","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4104,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"a9780d96ce4de9a37131f95d62343d62a56f0f2571930fca0d5ce2d044061ae6","addressRefs":[]},"c7791404-4478-4bf8-8292-7bd3ff676e01":{"id":"c7791404-4478-4bf8-8292-7bd3ff676e01","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4105,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"a0a08a60-a588-4586-b237-51273e259d8a":{"id":"a0a08a60-a588-4586-b237-51273e259d8a","doc_no":"A.6.1.1.1.2.6.1.3.1.3.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4106,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"5302863d-f777-461e-8238-2178fc9899c4":{"id":"5302863d-f777-461e-8238-2178fc9899c4","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2","title":"Ethereum Mainnet - Maple USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4107,"content":"The documents herein contain the Instance Configuration Document for the Maple USDT Instance.","contentHash":"ff8dce2867c795af30fb17cdb6861bd8262f43518899f8ed1337bcaa9a0863f1","addressRefs":[]},"1ed4dd56-1e0a-4c73-ba31-3fd6894c91bf":{"id":"1ed4dd56-1e0a-4c73-ba31-3fd6894c91bf","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4108,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"46c4446e-ce4f-4ab8-85fd-c1868636ff2b":{"id":"46c4446e-ce4f-4ab8-85fd-c1868636ff2b","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4109,"content":"The documents herein define the parameters of the Maple USDT Instance of the Allocation System Primitive.","contentHash":"a463683bb7568dc7864d797e5536684d518fddb204d101575ac68f8e00d9f92b","addressRefs":[]},"33273ac7-e169-48f6-a89b-eb3173050bfe":{"id":"33273ac7-e169-48f6-a89b-eb3173050bfe","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4110,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"e05459c2-ea54-4b1a-a68f-f87c0291d713":{"id":"e05459c2-ea54-4b1a-a68f-f87c0291d713","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4111,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"0d38db2a-1471-4f69-b0a6-37cabf5e7f4f":{"id":"0d38db2a-1471-4f69-b0a6-37cabf5e7f4f","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4112,"content":"Maple","contentHash":"187c93774dbd4c674ecaf745f0c304bb494ccfca31cd88c028251f97f09569c5","addressRefs":[]},"c2e6edf2-d064-4079-bb51-403d6963db0b":{"id":"c2e6edf2-d064-4079-bb51-403d6963db0b","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4113,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"39086a4b-4656-4884-894f-895c88bef238":{"id":"39086a4b-4656-4884-894f-895c88bef238","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4114,"content":"syrupUSDT","contentHash":"142275da36c6fed7a78dcea02d7a71186c3a7d539e824f6b234d997887413837","addressRefs":[]},"3147106a-6918-449e-bb1b-70a52ac1af26":{"id":"3147106a-6918-449e-bb1b-70a52ac1af26","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4115,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"348f78f4-07a2-4e72-8d2a-4a62a2e44bed":{"id":"348f78f4-07a2-4e72-8d2a-4a62a2e44bed","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4116,"content":"`0x356B8d89c1e1239Cbbb9dE4815c39A1474d5BA7D`","contentHash":"6e4755712ecdcec421e74a54f666ec722656242f474bbd1c4b6edb65244f8048","addressRefs":["0x356b8d89c1e1239cbbb9de4815c39a1474d5ba7d"]},"ffaf2d1b-8942-489f-8408-ab0e5718d3c5":{"id":"ffaf2d1b-8942-489f-8408-ab0e5718d3c5","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4117,"content":"`0xdAC17F958D2ee523a2206206994597C13D831ec7`","contentHash":"d674f514fb5256107f891afe7b796353b6535b08717e30bc071e1ccdf11a1fbf","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"3b9ecc4e-0cc5-491b-aebc-bf08d2e8c6f9":{"id":"3b9ecc4e-0cc5-491b-aebc-bf08d2e8c6f9","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.2.3","title":"Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4118,"content":"`0x356B8d89c1e1239Cbbb9dE4815c39A1474d5BA7D`","contentHash":"6e4755712ecdcec421e74a54f666ec722656242f474bbd1c4b6edb65244f8048","addressRefs":["0x356b8d89c1e1239cbbb9de4815c39a1474d5ba7d"]},"efc9f35a-40e1-4847-8a48-06eda4d17d85":{"id":"efc9f35a-40e1-4847-8a48-06eda4d17d85","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4119,"content":"- `deposit`: `0x207bb548ee62bbfd7b6906087f0de38e6c19d5be908e83166c0f089ccc2d97eb`\n- `withdraw`: `0xe701ee8a9573df3a49595c8d32a8df7809120a0541dd386e9bf54c148d969707`\n- `redeem`: `0x0562da8d8466582e6dc86134ab2ec5656cb4e3d5b57650f6bb1a0f3683bea329`","contentHash":"abca1d2c8b88c251bfa6b7e0bf72e0cc5312fc2588fa1323ec64df73b051a940","addressRefs":[]},"dfab21ad-13a4-48dd-8398-0c3d7dbc8996":{"id":"dfab21ad-13a4-48dd-8398-0c3d7dbc8996","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4120,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"9bf306d1-bc24-4214-9799-53a00ab04ab5":{"id":"9bf306d1-bc24-4214-9799-53a00ab04ab5","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4121,"content":"The inflow rate limits are:\n\n- `maxAmount`: 50,000,000 USDT\n- `slope`: 100,000,000 USDT per day","contentHash":"56021751b3d48d69f8e937e545dd63d84c595b538f9e11c73890a3132093b223","addressRefs":[]},"fc23d5a1-6e97-4e3e-bead-9a41955441c6":{"id":"fc23d5a1-6e97-4e3e-bead-9a41955441c6","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4122,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"569b0f886c9aedda81b4e87d26e1e21d96763dd2e909e2e9865edcf064b320e5","addressRefs":[]},"a9ece9ee-2c12-462e-928e-d1a69b5f83a3":{"id":"a9ece9ee-2c12-462e-928e-d1a69b5f83a3","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4123,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"3cd39fda-4e26-4f1b-ac32-93d3825a660b":{"id":"3cd39fda-4e26-4f1b-ac32-93d3825a660b","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4124,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"717e595c-d7ff-406e-802b-cb4351858f00":{"id":"717e595c-d7ff-406e-802b-cb4351858f00","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4125,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"34e632af-1fd9-4dbe-be28-633837cdfe67":{"id":"34e632af-1fd9-4dbe-be28-633837cdfe67","doc_no":"A.6.1.1.1.2.6.1.3.1.3.2.4.1","title":"Request Redemption Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4126,"content":"- `maxAmount`: Unlimited\n- `slope`: 500,000,000 USDT per day","contentHash":"adf710a9a77254246def34a230bacb0d2d15ecd07a09d6cdbc74ea4e572b8ddf","addressRefs":[]},"b23e9a6b-e78a-486f-9f6e-07cfdb437bee":{"id":"b23e9a6b-e78a-486f-9f6e-07cfdb437bee","doc_no":"A.6.1.1.1.2.6.1.3.1.4","title":"Ethena","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4127,"content":"The Ethereum Mainnet Instances of the Ethena Protocol with `Active` Status are stored herein.","contentHash":"a46b12fc115b5c429a0867aaa62fc9f890e2b41454c14d2cedd6a98cd7aca7ee","addressRefs":[]},"6be3e516-5374-41a0-8566-1c50656af772":{"id":"6be3e516-5374-41a0-8566-1c50656af772","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1","title":"Ethereum Mainnet - Ethena USDe Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4128,"content":"The documents herein contain the Instance Configuration Document for the Ethena USDe Instance.","contentHash":"d01ab446023a57350389d71ef2933997d3c15887c6ef7ba7f71671ce744615b0","addressRefs":[]},"c5c8cd59-5d39-462c-b27d-79a7f65630b7":{"id":"c5c8cd59-5d39-462c-b27d-79a7f65630b7","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4129,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"5218de11-dc55-4933-aea7-46916969a60d":{"id":"5218de11-dc55-4933-aea7-46916969a60d","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4130,"content":"The documents herein define the parameters of the Ethena USDe Instance of the Allocation System Primitive.","contentHash":"9d4049ea143affeca92b38cad142ac72cfd010268acd973089ce91fdf1637ce9","addressRefs":[]},"62efc9a3-79e0-46dc-b67c-83add146ed55":{"id":"62efc9a3-79e0-46dc-b67c-83add146ed55","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4131,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"67144d2b-382d-4817-b9a8-5b3483da164d":{"id":"67144d2b-382d-4817-b9a8-5b3483da164d","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4132,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"acb1b896-a531-498d-9e77-057b0c30d15b":{"id":"acb1b896-a531-498d-9e77-057b0c30d15b","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4133,"content":"Ethena Protocol","contentHash":"28a2ae066b62e4f0fb21dea9515c881e910e33f91c217edd740a8db8d8e0dab2","addressRefs":[]},"355a1d6b-6138-4e23-84dc-244b8f1ba26c":{"id":"355a1d6b-6138-4e23-84dc-244b8f1ba26c","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4134,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"aa5fd0d5-4e71-46e1-95ee-609337769f10":{"id":"aa5fd0d5-4e71-46e1-95ee-609337769f10","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4135,"content":"USDe","contentHash":"9613d0cae557ec7702d9883e3926c60f107d41e7349456c05d3806dd74a255b9","addressRefs":[]},"ea69bedc-c388-4925-af83-9fa5496d0d36":{"id":"ea69bedc-c388-4925-af83-9fa5496d0d36","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4136,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"deb2d957-2230-48d8-befb-8a9f44454c14":{"id":"deb2d957-2230-48d8-befb-8a9f44454c14","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4137,"content":"`0x4c9EDD5852cd905f086C759E8383e09bff1E68B3`","contentHash":"af8f3aca379b74340581939474b84e3badef16e17802b2b71cfa3cb6f05cb267","addressRefs":["0x4c9edd5852cd905f086c759e8383e09bff1e68b3"]},"e72457e9-cfd1-4a67-a694-4b487d38d3c0":{"id":"e72457e9-cfd1-4a67-a694-4b487d38d3c0","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4138,"content":"This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"ea3c5d84119733fb3a2a429f279628dcce722f210f012ad0286de1cf9435e132","addressRefs":[]},"e9625e37-993c-4690-b3e3-cf6a29fb8c96":{"id":"e9625e37-993c-4690-b3e3-cf6a29fb8c96","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.2.3","title":"EthenaMinter","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4139,"content":"`0xe3490297a08d6fC8Da46Edb7B6142E4F461b62D3`","contentHash":"c6649b3505a142e742c11a8df260a1f7d33ae2c52bfc7a72be661f1a9e6dd085","addressRefs":["0xe3490297a08d6fc8da46edb7b6142e4f461b62d3"]},"cc7955d0-0214-48cf-bc2b-7fc0692ef755":{"id":"cc7955d0-0214-48cf-bc2b-7fc0692ef755","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4140,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"54992e68-12d5-4036-9a7c-36403a2e17f8":{"id":"54992e68-12d5-4036-9a7c-36403a2e17f8","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4141,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"c45e65d9-9577-4414-b163-5f55c4335d3c":{"id":"c45e65d9-9577-4414-b163-5f55c4335d3c","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4142,"content":"The inflow rate limits are:\n\n- `maxAmount`: 250,000,000 USDC\n- `slope`: 100,000,000 USDC per day","contentHash":"d68394624490415912beb1bb49cf36a64ab60dd4436193c95ec4979bbede6e09","addressRefs":[]},"fecaf504-50ea-4f75-bd4d-b5f26c724bc2":{"id":"fecaf504-50ea-4f75-bd4d-b5f26c724bc2","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4143,"content":"The outflow rate limits are:\n\n- `maxAmount`: 500,000,000 USDe\n- `slope`: 200,000,000 USDe per day","contentHash":"3cda895620ca466e25c2017ddb6f2779ad59146ce589d4ccc5a7a6effea1db6f","addressRefs":[]},"c4f10363-7872-4d71-a8c4-4d5314c78f33":{"id":"c4f10363-7872-4d71-a8c4-4d5314c78f33","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4144,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"6a009815-fba1-452c-af33-7ac5454211f1":{"id":"6a009815-fba1-452c-af33-7ac5454211f1","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4145,"content":"The documents herein defines the operations performed to manage the Ethena Instance, including rate limiting, role-based access control, and cooldown functionality.","contentHash":"58b2397eb062afb8152fdca76b752c92b3db3807113193ab146ecbe45f82095a","addressRefs":[]},"e6722e78-c1f5-4704-8bf9-2b3ab7c1b811":{"id":"e6722e78-c1f5-4704-8bf9-2b3ab7c1b811","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.1","title":"Delegated Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4146,"content":"The documents herein contain the addresses authorized as `delegatedSigners` in the `ethenaMinter` contract. `delegatedSigners` are set up and removed in the `MainnetController` contract by the `Relayer` role.","contentHash":"54d5367ab740bb3a103513d78aca5d0edc975b5263610287df45d7c8ea9d3697","addressRefs":[]},"7fcbd408-2aef-427f-b88d-d301350bd41b":{"id":"7fcbd408-2aef-427f-b88d-d301350bd41b","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.1.1","title":"Addresses Of Delegated Signers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4147,"content":"`delegatedSigner` addresses\n\n- These addesses will be specified in a future iteration of the Spark Artifact.","contentHash":"5b9338f144d807718f415afa955c9b71dab50de745415e5a112d00a9a13fc5c1","addressRefs":[]},"4413579c-6ca5-4ff5-9dd5-ff669606eeb7":{"id":"4413579c-6ca5-4ff5-9dd5-ff669606eeb7","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.2","title":"Set A Delegated Signer In The EthenaMinter Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4148,"content":"The documents herein define the process for an operator to set a delegated signer to the EthenaMinter contract.","contentHash":"536f22c9f9effac0e19649cb0a50d5f172ce836df588f208fe7e59cf08e341f5","addressRefs":[]},"bb5f7a55-8c79-4678-a281-8264eb5de225":{"id":"bb5f7a55-8c79-4678-a281-8264eb5de225","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4149,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `setDelegatedSigner`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction setDelegatedSigner(address delegatedSigner)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"8aba311385597beba3c6e88b0cd3956f3db2d9c2ed5c79f4e1986f70d31ed92d","addressRefs":[]},"77e7f0e6-016f-4d66-b7cf-39efa5b4f0b2":{"id":"77e7f0e6-016f-4d66-b7cf-39efa5b4f0b2","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.2.2","title":"Encode Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4150,"content":"The operator must use `proxy.doCall()` to forward the call to the `ethenaMinter` contract and call `setDelegatedSigner` function to set the address that will be authorized as a `delegatedSigner`. To call on `ethenaMinter` contract, the function must be encoded using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(ethenaMinter),\n        abi.encodeCall(ethenaMinter.setDelegatedSigner, (address(delegatedSigner)))\n    );\n}\n```","contentHash":"0c3c7f255361938c1e6338fd220081f53c7cf2a4f34062d8a83a6243bb5e36d9","addressRefs":[]},"40d3f261-a7f3-4cd9-b92b-3a79872eb339":{"id":"40d3f261-a7f3-4cd9-b92b-3a79872eb339","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.3","title":"Remove A Delegated Signer In The Ethena Minter Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4151,"content":"The documents herein define the process for an operator to remove a delegated signer from the Ethena Minter contract.","contentHash":"1a1164093641b73d7a09a9385e332b963fff1a1f238406778a51e64cda44b798","addressRefs":[]},"157361f8-7758-4e6b-a04d-a592d40b3b41":{"id":"157361f8-7758-4e6b-a04d-a592d40b3b41","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.3.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4152,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `removeDelegatedSigner`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction removeDelegatedSigner(address delegatedSigner)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"234716df620a9ea3c1d8f770436770d50a6d81b73f966313833b2efccdf03b00","addressRefs":[]},"71d2f286-960f-4264-86db-b48154f38366":{"id":"71d2f286-960f-4264-86db-b48154f38366","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.3.2","title":"Encode Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4153,"content":"The operator must use `proxy.doCall()` to forward the call to the `ethenaMinter` contract and call `removeDelegatedSigner` function to remove the authorization for the `address` to act as a `delegatedSigner`. To call on `ethenaMinter` contract, the function must be encoded using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(ethenaMinter),\n        abi.encodeCall(ethenaMinter.removeDelegatedSigner, (address(delegatedSigner)))\n    );\n}\n```","contentHash":"d02a53fd56f9a7b6d99dc1825d43566618d4f451f67f021981116cdf80c417d4","addressRefs":[]},"43775285-0a42-44d8-bc3f-acc80f97a8f3":{"id":"43775285-0a42-44d8-bc3f-acc80f97a8f3","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.4","title":"Approve Minting of USDe By Ethena Minter Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4154,"content":"The documents herein define the process for an operator to approve the minting of USDe by the EthenaMinter contract.","contentHash":"418de9614e562e8591d06c18d24f7da224a6dbfbad13c132f188944599719921","addressRefs":[]},"41214aef-fb81-42d5-ade2-f7263b8fffb0":{"id":"41214aef-fb81-42d5-ade2-f7263b8fffb0","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.4.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4155,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `prepareUSDeMint`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction prepareUSDeMint(uint256 usdcAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"71c17f77da2d4ac63e8ce39c65eb7d17c5984d96b0e63c65d731fa707b800105","addressRefs":[]},"62adede2-12c9-4388-b078-dbb3ef41e875":{"id":"62adede2-12c9-4388-b078-dbb3ef41e875","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.4.2","title":"Enforce Rate Limit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4156,"content":"The operator must enforce a rate limit on how much USDC can be approved for minting USDe.\n\n`rateLimited(LIMIT_USDE_MINT, usdcAmount)`","contentHash":"7ca7f68376be8d5ab92d9877eea510aea8071346379d9140dc8bbc4fc8497965","addressRefs":[]},"097fc13f-6cdd-4cde-ac00-3db8aa94f3a5":{"id":"097fc13f-6cdd-4cde-ac00-3db8aa94f3a5","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.4.3","title":"Encode Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4157,"content":"The operator must use `proxy.doCall()` to send an approval call to the `usdc` contract, allowing the `ethenaMinter` contract to spend up to the specified `amount` of USDC. They must encode the function using `abi.encodeCall`.\n\n```\n {\n    proxy.doCall(\n        address(usdc),\n        abi.encodeCall(usdc.approve, (address(ethenaMinter), usdcAmount))\n    );\n}\n```","contentHash":"86e78931a13e473ea511aa636dcd83a0ad8bf7acef12cf17635448be5201f623","addressRefs":[]},"9df0fbc9-4d5f-4ddb-a184-d5a069cde43c":{"id":"9df0fbc9-4d5f-4ddb-a184-d5a069cde43c","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.5","title":"Approve Burning of USDe By EthenaMinter Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4158,"content":"The documents herein define the process for an operator to approve the burning of USDe by the EthenaMinter contract.","contentHash":"b96a6e3b9e0dfe3cfac2c3b1012ef3f80a75206d7371e4e109f6ad4a360243cc","addressRefs":[]},"083618d3-6102-4a1a-bc7a-dfa854d49197":{"id":"083618d3-6102-4a1a-bc7a-dfa854d49197","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.5.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4159,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `prepareUSDeBurn`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction prepareUSDeBurn(uint256 usdeAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"28bd44137567aab7c0f230706822093dd7d7b334ee2244e4b379b334fcc2d723","addressRefs":[]},"b31a63bd-3163-4d8d-8fe1-c664a989a709":{"id":"b31a63bd-3163-4d8d-8fe1-c664a989a709","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.5.2","title":"Enforce Rate Limit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4160,"content":"The operator must enforce a rate limit on how much USDe can be approved for burning.\n\n`rateLimited(LIMIT_USDE_BURN, usdeAmount)`","contentHash":"4384b668e75aed70fb58b96d7b40b659d53fd0fe945d3cd4533006ffe072f746","addressRefs":[]},"4f454648-637e-442a-9f0f-314958d15915":{"id":"4f454648-637e-442a-9f0f-314958d15915","doc_no":"A.6.1.1.1.2.6.1.3.1.4.1.3.5.3","title":"Encode Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4161,"content":"The operator must use `proxy.doCall()` to send an approval call to the `usde` contract, allowing the `ethenaMinter` contract to spend up to the specified `amount` of USDe. They must encode the function using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(usde),\n        abi.encodeCall(usde.approve, (address(ethenaMinter), usdeAmount))\n    );\n}\n```","contentHash":"e2f7b51f87aea6f0ff7c3c4f845d0bf658d68f685cf818ce3b9d22605e203b9b","addressRefs":[]},"1903250a-4499-4ce4-bdcb-5835102a6553":{"id":"1903250a-4499-4ce4-bdcb-5835102a6553","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2","title":"Ethereum Mainnet - Ethena sUSDe Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4162,"content":"The documents herein contain the Instance Configuration Document for the Ethena sUSDe Instance.","contentHash":"013709d56b596e1729075c5450c564b0cb0fdf3c05c3c6d985c16cf8a5eb0522","addressRefs":[]},"df6d3b8e-4ded-4918-b657-3f812783aad5":{"id":"df6d3b8e-4ded-4918-b657-3f812783aad5","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4163,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"47518c8c-fe69-45cc-b268-858c39c4462a":{"id":"47518c8c-fe69-45cc-b268-858c39c4462a","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4164,"content":"The documents herein define the parameters of the Ethena sUSDe Instance of the Allocation System Primitive.","contentHash":"bdafa68ac339ad6fcf55a243b9559fd7e3a9cd7bb8e935a99485437893c899c5","addressRefs":[]},"3499d700-688c-4586-9ab1-7033b092b150":{"id":"3499d700-688c-4586-9ab1-7033b092b150","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4165,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"54017580-366b-4358-b9ff-b6a05fe1c51e":{"id":"54017580-366b-4358-b9ff-b6a05fe1c51e","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4166,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"1112e047-b8b6-4fe9-bf10-f90a6111b4ea":{"id":"1112e047-b8b6-4fe9-bf10-f90a6111b4ea","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4167,"content":"Ethena Protocol","contentHash":"28a2ae066b62e4f0fb21dea9515c881e910e33f91c217edd740a8db8d8e0dab2","addressRefs":[]},"a147254d-5aa8-4473-81be-778e3b8eb7c4":{"id":"a147254d-5aa8-4473-81be-778e3b8eb7c4","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4168,"content":"USDe","contentHash":"9613d0cae557ec7702d9883e3926c60f107d41e7349456c05d3806dd74a255b9","addressRefs":[]},"5642013a-bd4d-49f2-8b25-c70287159da5":{"id":"5642013a-bd4d-49f2-8b25-c70287159da5","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4169,"content":"sUSDe","contentHash":"e401c6761be8363a66141080dd79aeb363bd7ae63a457335d764191f717f7a74","addressRefs":[]},"3f06cfb3-327d-4578-8a5c-9f93817441c4":{"id":"3f06cfb3-327d-4578-8a5c-9f93817441c4","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4170,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"da72f25e-649c-45b6-bac1-54e7c4f714a5":{"id":"da72f25e-649c-45b6-bac1-54e7c4f714a5","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4171,"content":"`0x9D39A5DE30e57443BfF2A8307A4256c8797A3497`","contentHash":"bfc04001766f78a641fffbae024f439d86f835031cab8f1bb23d43c4a6df7d80","addressRefs":["0x9d39a5de30e57443bff2a8307a4256c8797a3497"]},"36beeacb-b9c7-4dac-aa1a-db6a69f3af24":{"id":"36beeacb-b9c7-4dac-aa1a-db6a69f3af24","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4172,"content":"`0x4c9EDD5852cd905f086C759E8383e09bff1E68B3`","contentHash":"af8f3aca379b74340581939474b84e3badef16e17802b2b71cfa3cb6f05cb267","addressRefs":["0x4c9edd5852cd905f086c759e8383e09bff1e68b3"]},"534a5d66-47ec-4db3-b6d9-ffc21f22cc53":{"id":"534a5d66-47ec-4db3-b6d9-ffc21f22cc53","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.2.3","title":"EthenaMinter","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4173,"content":"`0xe3490297a08d6fC8Da46Edb7B6142E4F461b62D3`","contentHash":"c6649b3505a142e742c11a8df260a1f7d33ae2c52bfc7a72be661f1a9e6dd085","addressRefs":["0xe3490297a08d6fc8da46edb7b6142e4f461b62d3"]},"6364f050-3634-4baa-8032-cd5d964f2c80":{"id":"6364f050-3634-4baa-8032-cd5d964f2c80","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4174,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"3370ffb9-c14a-46ee-9b08-b54ce3296ae8":{"id":"3370ffb9-c14a-46ee-9b08-b54ce3296ae8","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4175,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"9acb1a46-3e4a-470f-b8b8-61edc40c3a04":{"id":"9acb1a46-3e4a-470f-b8b8-61edc40c3a04","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4176,"content":"The inflow rate limits are:\n\n- `maxAmount`: 250,000,000 USDe\n- `slope`: 100,000,000 USDe per day","contentHash":"7e94e27b246ede497661a1e8eed573d41b50e2f38889ed4a8695c039234962f7","addressRefs":[]},"a58592c6-f4f0-4874-bee1-ef11fb91c544":{"id":"a58592c6-f4f0-4874-bee1-ef11fb91c544","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4177,"content":"The outflow rate limits are:\n\n- `maxAmount`: unlimited\n- `slope`: unlimited","contentHash":"d203bbdf6281d01b57bd47618604541e76fe7348908ab03b5a2ed8a8d7d37505","addressRefs":[]},"3c72575c-ce4e-4379-ba45-080f335851a1":{"id":"3c72575c-ce4e-4379-ba45-080f335851a1","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4178,"content":"For operational processes defining the operations performed to manage the Ethena Instance, including rate limiting, role-based access control, and minting of USDe functionality see [A.6.1.1.1.2.6.1.3.1.4.1.3 - Instance-specific Operational Processes](6a009815-fba1-452c-af33-7ac5454211f1). For detailed logic specific for this instance see [A.6.1.1.1.2.6.1.3.1.4.2.3.1 - Initiate A sUSDe Cooldown Period](cf235e02-23fb-48e6-b39e-b4fd09dc7911), [A.6.1.1.1.2.6.1.3.1.4.2.3.2 - Cool Down sUSDe Shares](24171b90-4967-4c15-ac77-789d42b0fc80), [A.6.1.1.1.2.6.1.3.1.4.2.3.3 - Unstake sUSDe And Return It To ALM Proxy](57337963-ea1f-4d12-bea4-127896d35855) and [A.6.1.1.1.2.6.1.3.1.4.2.3.4 - Emergency Procedure To Withdraw Ethena Balances](037dc4f2-0b55-42a9-851c-8769b60b7122).","contentHash":"caaccd180becc4c9a5817cee3fb4309a0b95e222bc1e0cf7fdcfde44acb24dc8","addressRefs":[]},"cf235e02-23fb-48e6-b39e-b4fd09dc7911":{"id":"cf235e02-23fb-48e6-b39e-b4fd09dc7911","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.1","title":"Initiate A sUSDe Cooldown Period","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4179,"content":"The documents herein define the process for an operator to initiate a sUSDe Cooldown period.","contentHash":"f80daecd5b1112e1c5a57b2fb9f8cf5f067b9f53cc6b7ffe9349d772b7737873","addressRefs":[]},"463dba18-1e74-49bd-b06f-7df0b0cedae7":{"id":"463dba18-1e74-49bd-b06f-7df0b0cedae7","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4180,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `cooldownAssetsSUSDe`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction cooldownAssetsSUSDe(uint256 usdeAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"4dcb2050bfb27b88451fbcc291480ca53895b1fdeb5d32d790d7c6ce4986d0d9","addressRefs":[]},"11d78bab-58b4-4ee0-8d73-124e1f9a8972":{"id":"11d78bab-58b4-4ee0-8d73-124e1f9a8972","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.1.2","title":"Enforce Rate Limit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4181,"content":"The operator must enforce a rate limit on how much sUSDe can be cooled down.\n\n`rateLimited(LIMIT_SUSDE_COOLDOWN, usdeAmount)`","contentHash":"66229763b64764bbbde369b4676228796307a2f998650e73a86ac3b698b63c90","addressRefs":[]},"938f26c5-6028-420d-86bf-f41f5d7aeb7e":{"id":"938f26c5-6028-420d-86bf-f41f5d7aeb7e","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.1.3","title":"Encode Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4182,"content":"The operator must use `proxy.doCall()` to make a call to the `susde` contract, invoking the `cooldownAssets` function with the specified amount of sUSDe. They must encode the function using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(susde),\n        abi.encodeCall(susde.cooldownAssets, (usdeAmount))\n    );\n}\n```","contentHash":"67f25a96d2b15be438bda08ae22673ffd7a59ea12dd34038de512ce2263b33ef","addressRefs":[]},"24171b90-4967-4c15-ac77-789d42b0fc80":{"id":"24171b90-4967-4c15-ac77-789d42b0fc80","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.2","title":"Cool Down sUSDe Shares","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4183,"content":"The documents herein define the process for an operator to cool down sUSDe shares.","contentHash":"fdc6da6ff8a343a02c78b69ab29753353da7c356e1fef1749bd3731c30a93800","addressRefs":[]},"eacdbe29-1c6b-43b4-93a6-5e4eb9aa0fa7":{"id":"eacdbe29-1c6b-43b4-93a6-5e4eb9aa0fa7","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4184,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `cooldownSharesSUSDe`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction cooldownSharesSUSDe(uint256 susdeAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"574ebb22fd679cf3e289eca8ce6852fa04d586bf42942a214b87daec2ed21df1","addressRefs":[]},"8ab94554-c56e-4c2c-aa04-7be2d887beb3":{"id":"8ab94554-c56e-4c2c-aa04-7be2d887beb3","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.2.2","title":"Encode Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4185,"content":"The operator must use `proxy.doCall()` to make a call to the `susde` contract, initiating the `cooldown` on the specified amount of sUSDe shares. They must encode the function using `abi.encodeCall`.","contentHash":"67905094d5834ab89fe64850b0ebf027783b0920328b9cfd74544a4686a0f802","addressRefs":[]},"e2e16365-4a11-4df4-ab33-332fd9a14fac":{"id":"e2e16365-4a11-4df4-ab33-332fd9a14fac","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.2.2.1","title":"Decode For Underlying Shares","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4186,"content":"The operator must decode the result returned by the `cooldownShares` function into a `uint256` value, representing the amount of shares that were actually cooled down (`cooldownAmount`).\n\n```\n{\n    cooldownAmount = abi.decode(\n        proxy.doCall(\n            address(susde),\n            abi.encodeCall(susde.cooldownShares, (susdeAmount))\n        ),\n        (uint256)\n    );\n```","contentHash":"7201b6681d67856d70e64c7f3774a5e357610ac9ebd765240fe34951912b84b1","addressRefs":[]},"386c0363-ce6c-49bd-a440-fc1ab4fb733d":{"id":"386c0363-ce6c-49bd-a440-fc1ab4fb733d","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.2.3","title":"Decrease RateLimit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4187,"content":"The operator must decrease the `RateLimit`, effectively reducing the available `cooldown` limit, based on the `cooldownAmount`.\n\n```\nrateLimits.triggerRateLimitDecrease(LIMIT_SUSDE_COOLDOWN, cooldownAmount);\n}\n```","contentHash":"662ae53a032957233ab23a23dd153da09b0486d4c297289270a97e2a1d211f65","addressRefs":[]},"57337963-ea1f-4d12-bea4-127896d35855":{"id":"57337963-ea1f-4d12-bea4-127896d35855","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.3","title":"Unstake sUSDe And Return It To ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4188,"content":"The documents herein define the process for an operator to unstake sUSDe and return it to the ALM Proxy.","contentHash":"ab652ec461541aeda2c0abc68c9c4c47d0b270a281ff21515642c78a111a4d15","addressRefs":[]},"9984b00e-ecc2-4328-9e86-c0c2e913f79a":{"id":"9984b00e-ecc2-4328-9e86-c0c2e913f79a","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.3.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4189,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `unstakeSUSDe`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction unstakeSUSDe()\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"4cdbdae9dd15bfb5cd57da2e604cdb39b95ea943e43e856c5f9c1e38eab8dc8f","addressRefs":[]},"24486f09-3df1-4620-bd0f-8368b1e3ed7c":{"id":"24486f09-3df1-4620-bd0f-8368b1e3ed7c","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.3.2","title":"Encode Function","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4190,"content":"The operator must use `proxy.doCall()` to make a call to the `susde` contract to invoke the `unstake` function, which unstakes sUSDe and sends the resulting tokens back to the `proxy` address (i.e. ALM Proxy). They must encode the function using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(susde),\n        abi.encodeCall(susde.unstake, (address(proxy)))\n    );\n}\n```","contentHash":"67889e846ab9ad0e295de061ceb7c24d48a64a34a3f5bac1a12599e1357eb5f8","addressRefs":[]},"037dc4f2-0b55-42a9-851c-8769b60b7122":{"id":"037dc4f2-0b55-42a9-851c-8769b60b7122","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.4","title":"Emergency Procedure To Withdraw Ethena Balances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4191,"content":"In order to withdraw all Ethena balances, the operator must execute the following actions:","contentHash":"ea2b8b5def5df4f898a395262de817125b2816f5091161519d97f02eb76c6dcd","addressRefs":[]},"98ced6ee-3fa9-49b5-9212-6826a17adc27":{"id":"98ced6ee-3fa9-49b5-9212-6826a17adc27","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.4.1","title":"sUSDe Cooldown Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4192,"content":"The operator must start the cooldown for sUSDe using the following action:\n\n```\nmainnetController.cooldownSharesSUSDe(susde.balanceOf(address(proxy))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.3.1.4.2.3.2 - Cool Down sUSDe Shares](24171b90-4967-4c15-ac77-789d42b0fc80).","contentHash":"78a8ec45740df4579705b8dbb3dba791cc84fa0c06a2ab758a3ee323dd0c3a00","addressRefs":[]},"cef1fead-17d3-40ce-9d2f-ea592e51541d":{"id":"cef1fead-17d3-40ce-9d2f-ea592e51541d","doc_no":"A.6.1.1.1.2.6.1.3.1.4.2.3.4.2","title":"sUSDe Unstake Action","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4193,"content":"The operator must unstake sUSDe using the following action:\n\n```\nmainnetController.unstakeSUSDe()\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.1.2.6.1.3.1.4.2.3.3 - Unstake sUSDe And Return It To ALM Proxy](57337963-ea1f-4d12-bea4-127896d35855).","contentHash":"7fbaea1e3e14e9c044ce7f2e1f7f53511c57f85d549296d068e8e2295a54aa27","addressRefs":[]},"be04dae7-88d7-42e0-9162-88428080d43b":{"id":"be04dae7-88d7-42e0-9162-88428080d43b","doc_no":"A.6.1.1.1.2.6.1.3.1.5","title":"Fluid","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4194,"content":"The Ethereum Mainnet Instances of the Fluid Protocol with `Active` Status are stored herein.","contentHash":"39b9234a7020106c94eda04547a0a511818f66394e47f40e99e36be6a09cb17f","addressRefs":[]},"8da18a0c-2d5a-4895-ac53-804578b00a5b":{"id":"8da18a0c-2d5a-4895-ac53-804578b00a5b","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1","title":"Ethereum Mainnet - Fluid sUSDS ERC4626 Vault Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4195,"content":"The documents herein contain the Instance Configuration Document for the Fluid sUSDS ERC4626 Instance.","contentHash":"ff5d35a282ef42965ff1711b1bedfd7171972fdb4dace228be196ee7639537fb","addressRefs":[]},"a6215f0e-e4bd-4dc7-9afa-edbb9c09042c":{"id":"a6215f0e-e4bd-4dc7-9afa-edbb9c09042c","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4196,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"1c806523-7ef2-4f4c-8b6e-c609478d9112":{"id":"1c806523-7ef2-4f4c-8b6e-c609478d9112","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4197,"content":"The documents herein define the parameters of the Fluid sUSDS ERC4626 Vault Instance of the Allocation System Primitive.","contentHash":"c76335e444895dd188f1b3186a9ca3fa85c93663f1d3db4bab6da0e0b124254b","addressRefs":[]},"24967b50-8941-452a-b3f7-47034da4aa00":{"id":"24967b50-8941-452a-b3f7-47034da4aa00","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4198,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"5c50d8a2-bd79-47a8-b4bb-9f8b482c45d7":{"id":"5c50d8a2-bd79-47a8-b4bb-9f8b482c45d7","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4199,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"20caee73-7720-4acf-852f-c656922583cf":{"id":"20caee73-7720-4acf-852f-c656922583cf","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4200,"content":"Fluid Finance (ERC4626 Vault)","contentHash":"dce22b411372d756b541ceeeaf09ec6542de2afc444fa102196b8c77b1021acd","addressRefs":[]},"bf5832db-c854-4439-9207-b9d4cdddd8c8":{"id":"bf5832db-c854-4439-9207-b9d4cdddd8c8","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4201,"content":"sUSDS","contentHash":"fca5df225d787c8fd72534cf85993160140a59c4d215a8692340634c06d627c2","addressRefs":[]},"02c8c973-3f1e-45bc-bbf0-a099e1db33ce":{"id":"02c8c973-3f1e-45bc-bbf0-a099e1db33ce","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4202,"content":"fsUSDS","contentHash":"c16ee9508be095c21b7166a8e8bfa68feae03d80ccbdfa5f43d491397d359a80","addressRefs":[]},"0b34a94d-22f6-4aa0-b62b-5c0415cb6460":{"id":"0b34a94d-22f6-4aa0-b62b-5c0415cb6460","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4203,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"1f34b538-6081-4be9-9d69-3ae4bc75200f":{"id":"1f34b538-6081-4be9-9d69-3ae4bc75200f","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4204,"content":"`0x2BBE31d63E6813E3AC858C04dae43FB2a72B0D11`","contentHash":"8a663c2fd0af7352f09f058a3f7f05cd8ee252938ec74c81c2bfd30fad040b6e","addressRefs":["0x2bbe31d63e6813e3ac858c04dae43fb2a72b0d11"]},"dbe01ca1-3431-402b-a742-48ceb6d710d8":{"id":"dbe01ca1-3431-402b-a742-48ceb6d710d8","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4205,"content":"`0xa3931d71877C0E7a3148CB7Eb4463524FEc27fbD`","contentHash":"84d1fe4686ae19225b5c39d0544405a6240f17b414660d848e9e5c9d928ab00d","addressRefs":["0xa3931d71877c0e7a3148cb7eb4463524fec27fbd"]},"d3fe0ad8-786f-47dc-8193-f34d99a01d9f":{"id":"d3fe0ad8-786f-47dc-8193-f34d99a01d9f","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4206,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"426f42fa-c85c-48de-8859-205d2fa98c3e":{"id":"426f42fa-c85c-48de-8859-205d2fa98c3e","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4207,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"f9c88aaf-90d0-404e-b870-182846f58bf6":{"id":"f9c88aaf-90d0-404e-b870-182846f58bf6","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4208,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 5,000,000 sUSDS per day","contentHash":"d4662abaa7a03fffa773370bf61a7eeafc372ece1399208dce6e04ca1e7df68a","addressRefs":[]},"67155bd0-093a-49ff-9b96-eb6a8aa22c68":{"id":"67155bd0-093a-49ff-9b96-eb6a8aa22c68","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4209,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 5,000,000 fsUSDS per day","contentHash":"76162056a3a1678fb0869e9341ba56033ab0a7a61199862dfebef86081c8e302","addressRefs":[]},"1591a545-a8c6-4a41-aeea-f92d4fa30510":{"id":"1591a545-a8c6-4a41-aeea-f92d4fa30510","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4210,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"3bc424bf-079e-4b6b-8749-58c942c7d57b":{"id":"3bc424bf-079e-4b6b-8749-58c942c7d57b","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4211,"content":"The Instance follows the general ERC4626 procedures see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2 - ERC-4626 Functions](e386a0df-9e0b-4ffd-9879-49131f795b0b) and for emergency procedures see [A.6.1.1.1.2.6.1.2.2.3.4.1 - ERC-4626 Withdrawal Action](f92ddc3f-672a-4f52-931f-5263a9f709b9). For detailed example of the Spark Liquidity Layer interaction logic for depositing to, withdrawing from, and redeeming from this ERC4626 vault instance see [A.6.1.1.1.2.6.1.3.1.5.1.3.1 - Deposit ERC-4626 Tokens](e2ad525b-3f3f-4402-9e4d-3ae125b35b76) and [A.6.1.1.1.2.6.1.3.1.5.1.3.2 - Withdraw ERC-4626 Tokens](caa295f4-92f4-4ca9-9083-2a1b94c70d5f).","contentHash":"b89f6a6373effdd18fe878c76a39dd0a1275ab8b11159910da31ce93816f409d","addressRefs":[]},"e2ad525b-3f3f-4402-9e4d-3ae125b35b76":{"id":"e2ad525b-3f3f-4402-9e4d-3ae125b35b76","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1","title":"Deposit ERC-4626 Tokens","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4212,"content":"The documents herein define the steps for an operator to deposit assets from the ALM Proxy to the ERC-4626 vault (e.g., `[Instance_Fluid_USDS_Vault_Address_Placeholder]`) to receive yield-bearing shares.","contentHash":"b3c4380585ce2d689b254492a0ea1ffb6db29e0369e1dd5f67a642cbf16249d0","addressRefs":[]},"9ba1c843-7332-4602-a675-172d5312054d":{"id":"9ba1c843-7332-4602-a675-172d5312054d","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4213,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `depositERC4626` tokens. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction depositERC4626(address token, uint256 amount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"d18f2457987209f6bb6e68ef410ff00909d67a51f768c0b7b294e96051060485","addressRefs":[]},"089a461f-0ee1-4234-a3ae-f2496c79148c":{"id":"089a461f-0ee1-4234-a3ae-f2496c79148c","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.2","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4214,"content":"The operator must ensure the ALM Proxy holds enough of the underlying asset (e.g., `[Instance_USDS_Address_Placeholder]`) to cover the instructed `deposit` amount.","contentHash":"3603ce893edf12b7f505ce6265a1d508d87e1fdbf0f9396dac3486cbf1e0bfc0","addressRefs":[]},"eea8794f-8067-4f97-b03a-ae654d0793a8":{"id":"eea8794f-8067-4f97-b03a-ae654d0793a8","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.3","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4215,"content":"The operator must ensure the `deposit` amount is allowed within the `RateLimits` for this instance (e.g., using `[Instance_RateLimitID_Deposit_Placeholder]` for `token [Instance_Fluid_USDS_Vault_Address_Placeholder]`).\n\n```\n        rateLimited(\n            RateLimitHelpers.makeAssetKey([Instance_RateLimitID_Deposit_Placeholder], [Instance_Fluid_USDS_Vault_Address_Placeholder]),,\n            amount\n        )\n        returns (uint256 shares)\n    {\n        // Note that whitelist is done by rate limits\n        IERC20 asset = IERC20(IERC4626([Instance_Fluid_USDS_Vault_Address_Placeholder]).asset());\n```","contentHash":"1e321343ed8d84817c7cdcbe264fe36aa5a41815af263ea219b5d134e5863280","addressRefs":[]},"1e7bad6c-fce7-4832-8281-63a89de7fe47":{"id":"1e7bad6c-fce7-4832-8281-63a89de7fe47","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.4","title":"Update Allowance of Asset Contract","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4216,"content":"The operator must call the `approve` ERC-4626 function to update the allowance of the `asset` contract.","contentHash":"45a6a54124de0b7d6667209de615bcb48f792b7cc59b3027c0386f59b43e72fc","addressRefs":[]},"a2430308-7a82-457e-b505-ea9889bf90d5":{"id":"a2430308-7a82-457e-b505-ea9889bf90d5","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.4.1","title":"Encode Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4217,"content":"The operator must encode the function call to the ERC-4626 `approve` method, using `abi.encodeCall` to allow the `token` address (`[Instance_Fluid_USDS_Vault_Address_Placeholder`]) spend up to `amount` of a token from ALM Proxy’s balance.","contentHash":"2e29d930e9b597bcad32ec603ba23691dde21b7d69766afea589ea87159b75d1","addressRefs":[]},"07418471-50d1-4c6b-92a1-c883121f2622":{"id":"07418471-50d1-4c6b-92a1-c883121f2622","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.4.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4218,"content":"The operator must send the encoded call using `proxy.doCall()` specifying the `address` of the `asset` contract (`[Instance_USDS_Address_Placeholder]`) they want to deposit into.\n\n```\n        // Approve asset to token from the proxy (assumes the proxy has enough of the asset).\n        proxy.doCall(\n            address(asset),\n            abi.encodeCall(asset.approve, ([Instance_Fluid_USDS_Vault_Address_Placeholder], amount))\n        );\n```","contentHash":"95a98c88193e0a8d52fe92a364dcae3f5359b8024084cac8559c8c45d3d7f79d","addressRefs":[]},"78ff9c9a-a75e-4b94-a376-c8bc43e1d360":{"id":"78ff9c9a-a75e-4b94-a376-c8bc43e1d360","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.5","title":"Deposit Assets","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4219,"content":"The operator must call the `deposit` ERC-4626 function to transfer the underlying `asset` to ERC-4626 token and receive vault `shares`.","contentHash":"0d03507778f467fe653cfda1f6ff61eff5ddcf630162ebbf7e0d797422bdb60a","addressRefs":[]},"6eb71a3a-09b6-430d-9677-af0c3f9667f1":{"id":"6eb71a3a-09b6-430d-9677-af0c3f9667f1","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.5.1","title":"Encode Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4220,"content":"The operator must encode the function call to ERC-4626 `deposit` method, using `abi.encodeCall` with the address of the ERC-4626 `token` vault (`[Instance_Fluid_USDS_Vault_Address_Placeholder]`), the `amount` of the underlying asset to `deposit` and the `address(proxy)` that will receive the resulting shares (i.e. ALM Proxy).","contentHash":"2b5eb22a101f2b0282ed439502efc8cb6871454e4e530bfc59212b2411ee9554","addressRefs":[]},"6fd50750-0bee-4895-8ef4-ced22d81ce66":{"id":"6fd50750-0bee-4895-8ef4-ced22d81ce66","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.5.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4221,"content":"The operator must send the encoded call using `proxy.doCall()` to the `deposit` function on the ERC-4626 vault contract (`token`).","contentHash":"34582b891f0142ed96ba747621b8f0e3b63867cc79043409fbf2cc27b9d99649","addressRefs":[]},"1c4f95da-5479-4c47-bc8b-4e7875cf8139":{"id":"1c4f95da-5479-4c47-bc8b-4e7875cf8139","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.1.5.3","title":"Decode Vault Shares","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4222,"content":"The operator must decode the raw bytes data returned from the `doCall()` function into `uint256` value, representing the number of vault `shares` minted from the deposit.\n\n```\n        // Deposit asset into the token, proxy receives token shares, decode the resulting shares\n        shares = abi.decode(\n            proxy.doCall(\n                [Instance_Morpho_Fluid_Vault_Address_Placeholder],,\n                abi.encodeCall(IERC4626([Instance_Fluid_USDS_Vault_Address_Placeholder]).deposit, (amount, address(proxy)))\n            ),\n            (uint256)\n        );\n    }\n```","contentHash":"25d77cfba3d4a96ea6f8555c9de64e9676873073f8b77b2888f2a8e0d0685e43","addressRefs":[]},"caa295f4-92f4-4ca9-9083-2a1b94c70d5f":{"id":"caa295f4-92f4-4ca9-9083-2a1b94c70d5f","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2","title":"Withdraw ERC-4626 Tokens","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4223,"content":"The documents herein define the steps for an operator to withdraw a yield-earning balance from the ERC-4626 vault (e.g., `[Instance_Fluid_USDS_Vault_Address_Placeholder]`) to the ALM Proxy.","contentHash":"211416be48973911aa2de8593683185704e63efd183a2b200e005ee0b54bce0a","addressRefs":[]},"3ad29e6a-90fb-4739-aacf-434e467c070e":{"id":"3ad29e6a-90fb-4739-aacf-434e467c070e","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4224,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `withdrawERC4626` tokens. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction withdrawERC4626(address token, uint256 amount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"5c0c33698a676a3b345a24651281fe5b5881aa9177e55d604906950754a16da2","addressRefs":[]},"61a5f740-e2a6-432d-a3fc-728bff5312e5":{"id":"61a5f740-e2a6-432d-a3fc-728bff5312e5","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.2","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4225,"content":"The operator must ensure that the ALM Proxy holds sufficient shares of the ERC-4626 vault token (`[Instance_Fluid_USDS_Vault_Address_Placeholder]`) to cover the instructed `withdraw` amount.","contentHash":"e82ad4bd2d544c595fa9757ca4eb42c000fb4868c75010fd5b33ec180074e26c","addressRefs":[]},"5b77e7bb-5f31-48eb-9cdd-8fb799986788":{"id":"5b77e7bb-5f31-48eb-9cdd-8fb799986788","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.3","title":"Check RateLimits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4226,"content":"The operator must ensure the `withdraw` amount is allowed within the `RateLimits `for this instance (e.g. using `[Instance_RateLimitID_Withdraw_Placeholder]` for `token` `[Instance_Fluid_USDS_Vault_Address_Placeholder]`).\n\n```\n// Check withdrawal limits.\n        rateLimited(\n            RateLimitHelpers.makeAssetKey([Instance_RateLimitID_Withdraw_Placeholder], [Instance_Fluid_USDS_Vault_Address_Placeholder]),\n            amount\n        )\n        returns (uint256 shares)\n```","contentHash":"3c427ae0bd81651fe79af3fefba3dcb17f732070545525f0bc3d09f45151a9d7","addressRefs":[]},"91ec656f-417c-4357-b8ab-9c7a2404bc13":{"id":"91ec656f-417c-4357-b8ab-9c7a2404bc13","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.4","title":"Receive Vault Shares","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4227,"content":"The operator must call the `withdraw` ERC-4626 function to withdraw a required amount of underlying assets from an ERC-4626 vault and receive the corresponding vault shares.","contentHash":"284af47009ff39f3c38b1d5580c5bb5a7116a816fff715533f6ad160f17be901","addressRefs":[]},"e8053d8a-c24c-4acc-a928-c57fdbe11810":{"id":"e8053d8a-c24c-4acc-a928-c57fdbe11810","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.4.1","title":"Encode Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4228,"content":"The operator must encode the function call to the ERC-4626 `withdraw` method, using `abi.encodeCall` with the address of the ERC-4626 `token` vault (`[Instance_Fluid_USDS_Vault_Address_Placeholder]`), the `amount` of the underlying asset to `withdraw` and the `address(proxy)` of the recipient of the withdrawn assets and the sender of the shares (i.e. ALM Proxy).","contentHash":"e29c33ebba47737af27b2bfbaec2f8e4c4eb8bf58ea3bdf5dd3d655129d46887","addressRefs":[]},"d1889137-80a3-4e21-a5ea-522d23830574":{"id":"d1889137-80a3-4e21-a5ea-522d23830574","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.4.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4229,"content":"The operator must send the encoded call using `proxy.doCall()` to the `withdraw` function on the ERC-4626 vault contract (`token`).","contentHash":"4ecfcad5a69cd7c8d7c20ea312602e4a52b22f926315a6a7d4bfe30943d514c0","addressRefs":[]},"ca253911-1755-481f-ae63-1d4027d1a690":{"id":"ca253911-1755-481f-ae63-1d4027d1a690","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.4.3","title":"Decode Token Shares","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4230,"content":"The operator must decode the raw bytes data returned from the `doCall()` function into `uint256` value, representing the number of token `shares` burned in the withdrawal.\n\n```\n    {\n        // Withdraw asset from a token, decode resulting shares.\n        // Assumes proxy has adequate token shares.\n        shares = abi.decode(\n            proxy.doCall(\n                [Instance_Morpho_Fluid_Vault_Address_Placeholder],,\n                abi.encodeCall(IERC4626(token).withdraw, (amount, address(proxy), address(proxy)))\n            ),\n            (uint256)\n        );\n    }\n```","contentHash":"9db3184bfad53c22e8d54c537fcd66cc896157f7a3d75b0a863d58f108a1d086","addressRefs":[]},"d0acf55e-d5da-499a-b815-65a1bba8ed57":{"id":"d0acf55e-d5da-499a-b815-65a1bba8ed57","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.5","title":"Redeem Vault Shares For Assets","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4231,"content":"The operator must call the `redeem` ERC-4626 function to redeem a specific number of vault shares for the underlying asset.","contentHash":"dd72f7c8d62ff68db0f5039f44e364e40303eca78cdb7208ce6826501fa40231","addressRefs":[]},"13e8ea29-273a-45ce-9a61-10256fb7caf0":{"id":"13e8ea29-273a-45ce-9a61-10256fb7caf0","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.5.1","title":"Encode Function Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4232,"content":"The operator must encode the function call to the ERC-4626 `redeem` method, using `abi.encodeCall` with the address of the ERC-4626 `token` vault(`[Instance_Morpho_USDS_Vault_Address_Placeholder]`), the `shares` to `redeem` and the `address(proxy)` of the receiver of redeemed assets and the owner of shares being received (i.e. ALM Proxy).","contentHash":"00e59de26d8eeb3a96b36b06d25514e0aa02769d829c8c032d4db49e54bfba16","addressRefs":[]},"4992974d-f666-4b23-8623-4eedc3a96e91":{"id":"4992974d-f666-4b23-8623-4eedc3a96e91","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.5.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4233,"content":"The operator must send the encoded call using `proxy.doCall()` to the `redeem` function on the ERC-4626 vault contract (`token`).","contentHash":"abf24ea7c2f870c8dc977439af8ce8ff5f653c506fe96298cad084e89c5d0167","addressRefs":[]},"83c04cbf-fbd9-4bd0-9791-4fb7b02b091d":{"id":"83c04cbf-fbd9-4bd0-9791-4fb7b02b091d","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.5.3","title":"Decode For Underlying Assets","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4234,"content":"The operator must decode the raw bytes data returned from the `doCall()` function into `uint256` value, representing the number of underlying `assets` received for the redeemed `shares`.\n\n```\n function redeemERC4626(address token, uint256 shares)\n        external onlyRole(RELAYER) isActive returns (uint256 assets)\n    {\n        // Redeem shares for assets from the token, decode the resulting assets.\n        // Assumes proxy has adequate token shares.\n        assets = abi.decode(\n            proxy.doCall(\n                [Instance_Fluid_USDS_Vault_Address_Placeholder],\n                abi.encodeCall(IERC4626([Instance_Fluid_USDS_Vault_Address_Placeholder]).redeem, (shares, address(proxy), address(proxy)))\n            ),\n            (uint256)\n        );\n```","contentHash":"0f56a74d7685b80aff1ac16c5dbe37d3cf941d9726aa274f49d116eabd783d56","addressRefs":[]},"50c85778-c824-496b-ae01-7f8868ad341f":{"id":"50c85778-c824-496b-ae01-7f8868ad341f","doc_no":"A.6.1.1.1.2.6.1.3.1.5.1.3.2.6","title":"Decrease RateLimit","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4235,"content":"The operator must decrease the `RateLimit` based on the assets redeemed.\n\n```\nrateLimits.triggerRateLimitDecrease(\n            RateLimitHelpers.makeAssetKey([Instance_RateLimitID_Withdraw_Placeholder], [Instance_Fluid_USDS_Vault_Address_Placeholder]),\n            assets\n        );\n    }\n```","contentHash":"1a33a8723461cb861c3d2830f22e34ab9e3c21de784057be033b13314b0cc525","addressRefs":[]},"79d6bfdf-c542-4a60-a5f0-a17042d98d35":{"id":"79d6bfdf-c542-4a60-a5f0-a17042d98d35","doc_no":"A.6.1.1.1.2.6.1.3.1.6","title":"Superstate","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4236,"content":"The Ethereum Mainnet Instances of the Superstate Protocol with `Active` Status are stored herein.","contentHash":"edf73d4fc02c65e81ad84fa8724da508b0d320efa5e71aa8b0eebf2a872db41d","addressRefs":[]},"4ad2419c-7966-42de-bc2a-d8ca8ce61b90":{"id":"4ad2419c-7966-42de-bc2a-d8ca8ce61b90","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1","title":"Ethereum Mainnet - Superstate USTB Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4237,"content":"The documents herein contain the Instance Configuration Document for the Superstate USTB Instance.","contentHash":"343f48a7d355e7f786ac2c284cfc981fe750f28205dbe782050ae277b3e68e7e","addressRefs":[]},"0ecae4db-37e8-4505-b8e1-4211816bf9ed":{"id":"0ecae4db-37e8-4505-b8e1-4211816bf9ed","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4238,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"a5f05d4d-431b-45cc-a474-6070dc65ca83":{"id":"a5f05d4d-431b-45cc-a474-6070dc65ca83","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4239,"content":"The documents herein define the parameters of the Superstate USTB Instance of the Allocation System Primitive.","contentHash":"e847a8f4bbb217b7b0039181b46aa2f41555c9522cd3e039d025a94397a2e36a","addressRefs":[]},"cc925cb9-823f-426b-aaa2-0a82f646b03e":{"id":"cc925cb9-823f-426b-aaa2-0a82f646b03e","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4240,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"83773f20-1656-4a6c-ab60-a773e9f9e4c7":{"id":"83773f20-1656-4a6c-ab60-a773e9f9e4c7","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4241,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"a46217e1-c887-444c-b04d-fa9b412476b9":{"id":"a46217e1-c887-444c-b04d-fa9b412476b9","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4242,"content":"Superstate","contentHash":"347a9de5e7347f5b0d15d5ffe54be23087536fbdcafc045e231c3309a787113c","addressRefs":[]},"965e886d-7b27-41f3-ba61-d5e3f7f1b556":{"id":"965e886d-7b27-41f3-ba61-d5e3f7f1b556","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4243,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"e4b489eb-3c85-4585-8cd2-e6a7e9143a16":{"id":"e4b489eb-3c85-4585-8cd2-e6a7e9143a16","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4244,"content":"USTB","contentHash":"9a2c6aa563c2ba0c8f132c3f1df378edfeaf658d25e7666c4645977536d06011","addressRefs":[]},"20f898ec-d6f0-4608-9590-754161548dcf":{"id":"20f898ec-d6f0-4608-9590-754161548dcf","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4245,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"818944d2-c16f-4bd8-af85-09c3a31eccd3":{"id":"818944d2-c16f-4bd8-af85-09c3a31eccd3","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4246,"content":"`0x43415eB6ff9DB7E26A15b704e7A3eDCe97d31C4e`","contentHash":"da7444aaf4f28c3ff7d075952d20e9825ab629fee87d550c93bd46299305b96f","addressRefs":["0x43415eb6ff9db7e26a15b704e7a3edce97d31c4e"]},"b4e63a9d-65e7-4c61-826e-fe9733b3f00f":{"id":"b4e63a9d-65e7-4c61-826e-fe9733b3f00f","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4247,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"8e52e9d6-6cb0-44e9-9068-21257c1cde34":{"id":"8e52e9d6-6cb0-44e9-9068-21257c1cde34","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4248,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow is:\n\n- `USTB_DEPOSIT`: `0x43415eB6ff9DB7E26A15b704e7A3eDCe97d31C4e`\n- `USTB_REDEEM`: `0x43415eB6ff9DB7E26A15b704e7A3eDCe97d31C4e`\n- `USTB_REDEEM` (instant liquidity): `0x4c21B7577C8FE8b0B0669165ee7C8f67fa1454Cf`","contentHash":"3fbe136821ba98901b647baa58b250b2c49d163fd69ec959d8a11da983213da6","addressRefs":["0x43415eb6ff9db7e26a15b704e7a3edce97d31c4e","0x4c21b7577c8fe8b0b0669165ee7c8f67fa1454cf"]},"69e164bc-ef0c-4d74-a17d-e56bf498b7e0":{"id":"69e164bc-ef0c-4d74-a17d-e56bf498b7e0","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4249,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"04975455-99e4-447b-8629-0a6088174e69":{"id":"04975455-99e4-447b-8629-0a6088174e69","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4250,"content":"The inflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"50ba291aa7b4f4325c75d5b82a2643b58f2f31bb3bd3597ba4bb95c9ad09ee04","addressRefs":[]},"8639aa8f-3902-4f81-9c1e-a56b4c57f03d":{"id":"8639aa8f-3902-4f81-9c1e-a56b4c57f03d","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4251,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"a9780d96ce4de9a37131f95d62343d62a56f0f2571930fca0d5ce2d044061ae6","addressRefs":[]},"b2e85192-58da-4702-8a5f-f5d2011b008b":{"id":"b2e85192-58da-4702-8a5f-f5d2011b008b","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4252,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"5cb29bf7-30f4-43ef-aca8-020d26f66fcb":{"id":"5cb29bf7-30f4-43ef-aca8-020d26f66fcb","doc_no":"A.6.1.1.1.2.6.1.3.1.6.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4253,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"614f24ff-943e-40b2-853b-6c8a0a97ca3d":{"id":"614f24ff-943e-40b2-853b-6c8a0a97ca3d","doc_no":"A.6.1.1.1.2.6.1.3.1.7","title":"Curve","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4254,"content":"The Ethereum Mainnet Instances of the Curve Protocol with `Active` Status are stored herein.","contentHash":"bbe4a4b6ba2956afcb9c28db209d5c1012eb0afbc525d654cf3eab0d447ca42b","addressRefs":[]},"4e840dad-944c-4c45-9c5e-277dcb1830a8":{"id":"4e840dad-944c-4c45-9c5e-277dcb1830a8","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1","title":"Ethereum Mainnet - Curve sUSDS/USDT Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4255,"content":"The documents herein contain the Instance Configuration Document for the Curve sUSDS/USDT Pool Instance.","contentHash":"580c45e2e14ccd8b11e50e3025f549b8ce348ef87c8646dec78b66479cee4479","addressRefs":[]},"bcaaaa86-4799-44cc-ab84-0faf3610ae66":{"id":"bcaaaa86-4799-44cc-ab84-0faf3610ae66","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4256,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"b26af91d-675e-4b3f-8f70-e8db5b93c5c0":{"id":"b26af91d-675e-4b3f-8f70-e8db5b93c5c0","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4257,"content":"The documents herein define the parameters of the Curve sUSDS/USDT Pool Instance of the Allocation System Primitive.","contentHash":"baa65637a8459ec69098d28487aea5e147dbf1a5cbf48f542088f4cc05913f0f","addressRefs":[]},"1e14eb69-7e41-4113-9ff6-41863539e16b":{"id":"1e14eb69-7e41-4113-9ff6-41863539e16b","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4258,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"2e3df36f-4370-4613-8ba5-4c25ad502553":{"id":"2e3df36f-4370-4613-8ba5-4c25ad502553","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4259,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"470b6ae4-1392-4fff-8f31-2b9c306870d8":{"id":"470b6ae4-1392-4fff-8f31-2b9c306870d8","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4260,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"72b80d4d-ae2c-4980-87f4-79f734e0544f":{"id":"72b80d4d-ae2c-4980-87f4-79f734e0544f","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4261,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"29723ddf-4114-493d-ad46-901725a1bc14":{"id":"29723ddf-4114-493d-ad46-901725a1bc14","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4262,"content":"sUSDSUSDT","contentHash":"73fcc4d37e2ccce7a2284043c19274d2fbc78a9037521ad50ecb0d0d05a183b8","addressRefs":[]},"7acb9f43-9b9f-4cbd-909c-7e58f6357e5b":{"id":"7acb9f43-9b9f-4cbd-909c-7e58f6357e5b","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4263,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"8ce212dc-4f34-41a5-8621-01edd0ab2ea4":{"id":"8ce212dc-4f34-41a5-8621-01edd0ab2ea4","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4264,"content":"`0x00836Fe54625BE242BcFA286207795405ca4fD10`","contentHash":"627ec58ad075cc4ad8e92eb22e6a33d61b6f849e9e4424a6f99f905f4c5e118b","addressRefs":["0x00836fe54625be242bcfa286207795405ca4fd10"]},"6a780894-8075-4bed-88a9-42b0c3086a37":{"id":"6a780894-8075-4bed-88a9-42b0c3086a37","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4265,"content":"`0xdAC17F958D2ee523a2206206994597C13D831ec7`","contentHash":"d674f514fb5256107f891afe7b796353b6535b08717e30bc071e1ccdf11a1fbf","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"2957563b-3948-40b3-a247-15c6ddd41b03":{"id":"2957563b-3948-40b3-a247-15c6ddd41b03","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.2.3","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4266,"content":"`0xa3931d71877C0E7a3148CB7Eb4463524FEc27fbD`","contentHash":"84d1fe4686ae19225b5c39d0544405a6240f17b414660d848e9e5c9d928ab00d","addressRefs":["0xa3931d71877c0e7a3148cb7eb4463524fec27fbd"]},"e8833ae1-fdee-4e35-9e83-586c0289c6fd":{"id":"e8833ae1-fdee-4e35-9e83-586c0289c6fd","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4267,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"408f0d03-44cb-4e6f-b330-5782be816567":{"id":"408f0d03-44cb-4e6f-b330-5782be816567","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4268,"content":"The current `maxAmount,` `slope` and slippage for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"e252fc736995e50d221bb22f5a33f0e6726f8e9dddd52caf75ce25e998a43861","addressRefs":[]},"186761a1-5152-40f5-85f3-1e8868d8c6df":{"id":"186761a1-5152-40f5-85f3-1e8868d8c6df","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4269,"content":"The inflow rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 20,000,000 per day\n- Max slippage: 0.15%","contentHash":"3a7f02f9125a55872d16c0e05ba9fbfcf604852aaaefebd0c8356c1ef7078c89","addressRefs":[]},"f3f5e19c-f85b-484f-b0fb-4ee96e54a616":{"id":"f3f5e19c-f85b-484f-b0fb-4ee96e54a616","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4270,"content":"The outflow rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 20,000,000 per day\n- Max slippage: 0.15%","contentHash":"5e227c2a94641cb64ccddeca61849910ad73372bad173569d3aea181439ab1e9","addressRefs":[]},"6f9628a6-7574-4f63-a28f-797bd581e907":{"id":"6f9628a6-7574-4f63-a28f-797bd581e907","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4271,"content":"The swap rate limits are:\n\n- `maxAmount`: 10,000,000\n- `slope`: 200,000,000 per day\n- Max slippage: 0.25%","contentHash":"6438c7619138f55b6d194388a508c2d7fb1319f57e4c675e7301af5bfde76dd8","addressRefs":[]},"8d74f809-b54e-490f-aa7b-c1cb0aea5b7f":{"id":"8d74f809-b54e-490f-aa7b-c1cb0aea5b7f","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4272,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"60c4efad-67aa-411e-90d1-d5d0a427814a":{"id":"60c4efad-67aa-411e-90d1-d5d0a427814a","doc_no":"A.6.1.1.1.2.6.1.3.1.7.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4273,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"30d359a0-287b-4b3b-93fd-4e70bf0b19a7":{"id":"30d359a0-287b-4b3b-93fd-4e70bf0b19a7","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2","title":"Ethereum Mainnet - Curve USDC/USDT Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4274,"content":"The documents herein contain the Instance Configuration Document for the Curve USDC/USDT Pool Instance.","contentHash":"cfe9e7fca9a5c2cdb965d559eb75a5bd6767c1ec15ada3a95767dbb034f2d740","addressRefs":[]},"db6624bf-b38d-4516-96d3-04302bdc1dd3":{"id":"db6624bf-b38d-4516-96d3-04302bdc1dd3","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4275,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"e011af54-a277-4ecd-bd73-680ae96a7a51":{"id":"e011af54-a277-4ecd-bd73-680ae96a7a51","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4276,"content":"The documents herein define the parameters of the Curve USDC/USDT Pool Instance of the Allocation System Primitive.","contentHash":"902aa325b6dbe241e4b15e57305b02339d004af054ec9242d15a4a7fed3be19e","addressRefs":[]},"83513371-150d-46c3-82ae-671cc965d39e":{"id":"83513371-150d-46c3-82ae-671cc965d39e","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4277,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"54e1de2e-1301-4763-98d0-ef2aee8d3221":{"id":"54e1de2e-1301-4763-98d0-ef2aee8d3221","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4278,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"cc6acf48-9b55-4edf-a115-c463c0a78a9d":{"id":"cc6acf48-9b55-4edf-a115-c463c0a78a9d","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4279,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"b2bf10d6-adcc-4df4-99cc-9e3abeaeca1c":{"id":"b2bf10d6-adcc-4df4-99cc-9e3abeaeca1c","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4280,"content":"N/A - swap only","contentHash":"6adc1bfaa3d25c3520f75e4cbccc8b2ad1f9ddd970d2e7afa40cc5d41578c79c","addressRefs":[]},"0dc97998-edff-4d53-8251-18301991dd56":{"id":"0dc97998-edff-4d53-8251-18301991dd56","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4281,"content":"crv2pool","contentHash":"352779a5590ec32889527a65f7b23497415a731bf03188d4ed17c0ef3ebeffef","addressRefs":[]},"5b8c7810-5e84-44ba-b245-f3fa8f683b84":{"id":"5b8c7810-5e84-44ba-b245-f3fa8f683b84","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4282,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"a6a50db9-901d-44c4-84d9-cbd581637394":{"id":"a6a50db9-901d-44c4-84d9-cbd581637394","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4283,"content":"`0x4f493B7dE8aAC7d55F71853688b1F7C8F0243C85`","contentHash":"210618261bd695933e57aa83ce26a9e0a425ce32614faf8191c3d1931b07496f","addressRefs":["0x4f493b7de8aac7d55f71853688b1f7c8f0243c85"]},"43f3e5cd-12de-4bae-bcf0-ec4348a7e7e5":{"id":"43f3e5cd-12de-4bae-bcf0-ec4348a7e7e5","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4284,"content":"`0xdAC17F958D2ee523a2206206994597C13D831ec7`","contentHash":"d674f514fb5256107f891afe7b796353b6535b08717e30bc071e1ccdf11a1fbf","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"5e58a4bf-c0a0-4351-a069-b39b420edb5f":{"id":"5e58a4bf-c0a0-4351-a069-b39b420edb5f","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.2.3","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4285,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"25c72eb6-9a21-4592-b6f1-cede0644b607":{"id":"25c72eb6-9a21-4592-b6f1-cede0644b607","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4286,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"f2389063-4d57-4f28-844c-d63c991c5568":{"id":"f2389063-4d57-4f28-844c-d63c991c5568","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4287,"content":"The current `maxAmount,` `slope` and slippage for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"e252fc736995e50d221bb22f5a33f0e6726f8e9dddd52caf75ce25e998a43861","addressRefs":[]},"10ce5b4c-068d-44a8-bd34-a4afdb52ac9e":{"id":"10ce5b4c-068d-44a8-bd34-a4afdb52ac9e","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4288,"content":"The inflow rate limits are:\n\n- `maxAmount`: N/A - swap only\n- `slope`: N/A - swap only","contentHash":"bf146e8f36d9d3a5aa78aed53ec9db68b45a4df0a235bd0c0f5c52af2f08aa7f","addressRefs":[]},"997cbc11-99ee-4d26-87a8-a8a01e0a0537":{"id":"997cbc11-99ee-4d26-87a8-a8a01e0a0537","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4289,"content":"The outflow rate limits are:\n\n- `maxAmount`: N/A - swap only\n- `slope`: N/A - swap only","contentHash":"d1ff55299d510d3e8b62e4cec0c0297b6a31d15438f10a5a3f055505804d45dd","addressRefs":[]},"8b143018-298a-4878-9516-9b71049f1d0b":{"id":"8b143018-298a-4878-9516-9b71049f1d0b","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4290,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 20,000,000 per day\n- Max slippage: 0.05%","contentHash":"87b14acd20870a001998dc14116727fcf49fedcfb73018333ffe2427cea9ab8a","addressRefs":[]},"6a51a0d9-5b6d-4f68-8740-57033b74d1bc":{"id":"6a51a0d9-5b6d-4f68-8740-57033b74d1bc","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4291,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"d6bc0a40-0ed7-4366-902d-22eea7538c02":{"id":"d6bc0a40-0ed7-4366-902d-22eea7538c02","doc_no":"A.6.1.1.1.2.6.1.3.1.7.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4292,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"e1fdaf49-0b32-4644-b021-9cae6e270c7a":{"id":"e1fdaf49-0b32-4644-b021-9cae6e270c7a","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3","title":"Ethereum Mainnet - Curve pyUSD/USDC Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4293,"content":"The documents herein contain the Instance Configuration Document for the Curve pyUSD/USDC Pool Instance.","contentHash":"61451b0703be713431444200d8319363b8da3f82959c477971f44d9f2a957063","addressRefs":[]},"8f864934-c750-443f-b7f5-780d1e5cb47f":{"id":"8f864934-c750-443f-b7f5-780d1e5cb47f","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4294,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"2d44ce84-fb22-4435-93f2-ea5a62ccc130":{"id":"2d44ce84-fb22-4435-93f2-ea5a62ccc130","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4295,"content":"The documents herein define the parameters of the Curve pyUSD/USDC Pool Instance of the Allocation System Primitive.","contentHash":"383f716370b40fdc00cb7bf1a05846d77dc44fd55e5b3cd673b91566a569d627","addressRefs":[]},"b7328b28-d8cb-4a5d-9ef9-e9fe0d633d9d":{"id":"b7328b28-d8cb-4a5d-9ef9-e9fe0d633d9d","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4296,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"aba55fe1-bd3e-499c-a480-3ea7b860f4d5":{"id":"aba55fe1-bd3e-499c-a480-3ea7b860f4d5","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4297,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"a0794c17-0668-4bae-a5b1-141c61db12ef":{"id":"a0794c17-0668-4bae-a5b1-141c61db12ef","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4298,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"af3418ca-ed5f-4bee-b4ef-9cdd187cc4a1":{"id":"af3418ca-ed5f-4bee-b4ef-9cdd187cc4a1","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4299,"content":"N/A - swap only","contentHash":"6adc1bfaa3d25c3520f75e4cbccc8b2ad1f9ddd970d2e7afa40cc5d41578c79c","addressRefs":[]},"dd247f16-4d46-4780-9c19-2b1dec0e547b":{"id":"dd247f16-4d46-4780-9c19-2b1dec0e547b","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4300,"content":"PYUSDUSDC","contentHash":"d360c664829f635bfbb660382dde132d0dddb0a8fad1de996fbb0dbb3ee21742","addressRefs":[]},"2b15153d-8cd1-4096-b764-e56a1f38d9b7":{"id":"2b15153d-8cd1-4096-b764-e56a1f38d9b7","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4301,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"51de16a9-1184-45e9-a21f-1329d57ef3d7":{"id":"51de16a9-1184-45e9-a21f-1329d57ef3d7","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4302,"content":"`0x383E6b4437b59fff47B619CBA855CA29342A8559`","contentHash":"0ad4a6edbb190f29c92a9eac50f2e8c9dd299500985f670d6bc97ca6ab0ebb7a","addressRefs":["0x383e6b4437b59fff47b619cba855ca29342a8559"]},"c3d92c36-70ae-46f3-b887-64bb8419072c":{"id":"c3d92c36-70ae-46f3-b887-64bb8419072c","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4303,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"18e7ddf1-71e2-40fd-b74d-8ad6312b9a38":{"id":"18e7ddf1-71e2-40fd-b74d-8ad6312b9a38","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4304,"content":"The current `maxAmount`, `slope` and slippage for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"bcc9d2cc49801b82136efd2350649a7641bcf99add0f2d72285bd5add7cde1e0","addressRefs":[]},"893256f7-00f6-42e7-92cd-218af9beac76":{"id":"893256f7-00f6-42e7-92cd-218af9beac76","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4305,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0","contentHash":"3e721f12dd31e18c990bfaa45da49096f016361a53f7ba8f5426dd131717d811","addressRefs":[]},"dfcceae6-65f0-44e2-9d47-9ad2324d983d":{"id":"dfcceae6-65f0-44e2-9d47-9ad2324d983d","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4306,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0","contentHash":"a9068d1ca3f87e22045621ec05e7161c2f2dd8dcf1fb5716586265ea955441b2","addressRefs":[]},"2b4a19db-137d-404d-b475-3008eda3c82d":{"id":"2b4a19db-137d-404d-b475-3008eda3c82d","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4307,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 100,000,000 per day\n- Max slippage: 0.1%","contentHash":"d9e44e8e64f6952c7ad5f3c294a572763b6a7f3bd1cdd3660057972ca4a0a7e1","addressRefs":[]},"215cc709-a3e0-4cd5-98e1-ccb4430fc85d":{"id":"215cc709-a3e0-4cd5-98e1-ccb4430fc85d","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4308,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"cd57ed73-dc55-4543-a910-81a9ee4bc1e3":{"id":"cd57ed73-dc55-4543-a910-81a9ee4bc1e3","doc_no":"A.6.1.1.1.2.6.1.3.1.7.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4309,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"7635eff1-1fa0-4356-8953-2564a7f0693c":{"id":"7635eff1-1fa0-4356-8953-2564a7f0693c","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4","title":"Ethereum Mainnet - Curve pyUSD/USDS Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4310,"content":"The documents herein contain the Instance Configuration Document for the Curve pyUSD/USDS Pool Instance.","contentHash":"c50fc58bd39a135ef8a63bb6404f34c4f3a7aeb7eca79e94659d08e0f86f0e9d","addressRefs":[]},"464835ae-a3ce-44a7-84c8-11ab2d5138d8":{"id":"464835ae-a3ce-44a7-84c8-11ab2d5138d8","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4311,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"fdb613e0-4d7f-46a7-95c3-b84ea9dafa6a":{"id":"fdb613e0-4d7f-46a7-95c3-b84ea9dafa6a","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4312,"content":"The documents herein define the parameters of the Curve pyUSD/USDS Pool Instance of the Allocation System Primitive.","contentHash":"01ca78fbe208dc03b69250659aed9b880135500dc1c0df65171fa775942da40b","addressRefs":[]},"d3aa95cf-88e9-432b-90cf-0b4d1da094b5":{"id":"d3aa95cf-88e9-432b-90cf-0b4d1da094b5","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4313,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"4f3d5b84-1235-4932-8295-8df0e122e4c0":{"id":"4f3d5b84-1235-4932-8295-8df0e122e4c0","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4314,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"953adabd-347a-4d0c-aaa2-da618ee04151":{"id":"953adabd-347a-4d0c-aaa2-da618ee04151","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4315,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"c76d3c17-0be6-4d59-a73f-2952385164f1":{"id":"c76d3c17-0be6-4d59-a73f-2952385164f1","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4316,"content":"USDS and PYUSD","contentHash":"f15567c598355c9ed73c77fe5250a756a1eb38c9388b8497a2ed7fa8a42d0d09","addressRefs":[]},"2b34a305-2239-4b83-b829-dd1e7e8554ad":{"id":"2b34a305-2239-4b83-b829-dd1e7e8554ad","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4317,"content":"PYUSDUSDS","contentHash":"711bc5ee10bd22d6671560a2e4bba7d877de0495689322b148ef59ec9b89b67a","addressRefs":[]},"d386076c-607f-49fd-bd9c-07f4583cc1c9":{"id":"d386076c-607f-49fd-bd9c-07f4583cc1c9","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4318,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"aee3fc62-2c9a-4283-b447-149dc5f4a741":{"id":"aee3fc62-2c9a-4283-b447-149dc5f4a741","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4319,"content":"`0xA632D59b9B804a956BfaA9b48Af3A1b74808FC1f`","contentHash":"b80a642d598c5bc83f7cf2845d2d36212e8b59fe995ebf8660c32e4362e42258","addressRefs":["0xa632d59b9b804a956bfaa9b48af3a1b74808fc1f"]},"b86c4730-0a55-4a86-8c08-b01619e55e28":{"id":"b86c4730-0a55-4a86-8c08-b01619e55e28","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4320,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"82a8a51a-1650-438b-bdf4-3dc1b41132f3":{"id":"82a8a51a-1650-438b-bdf4-3dc1b41132f3","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4321,"content":"The current `maxAmount`, `slope` and slippage for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"bcc9d2cc49801b82136efd2350649a7641bcf99add0f2d72285bd5add7cde1e0","addressRefs":[]},"00d72073-ebb7-49d6-8ece-e5c506c7cf0c":{"id":"00d72073-ebb7-49d6-8ece-e5c506c7cf0c","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4322,"content":"The inflow rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 50,000,000 per day","contentHash":"193b763760c2d50334928c00497628d48596edd900c043e1dc466b758709e976","addressRefs":[]},"5547c29e-0dcd-40c0-9811-f88f4a906825":{"id":"5547c29e-0dcd-40c0-9811-f88f4a906825","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4323,"content":"The outflow rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 100,000,000 per day","contentHash":"2ed56bb1a0e4d4a970bb8522f89036184aa7d872599f63fc53891329b4360db1","addressRefs":[]},"664c8068-a848-42aa-b50a-3000f3081507":{"id":"664c8068-a848-42aa-b50a-3000f3081507","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4324,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 50,000,000 per day\n- Max slippage: 0.2%","contentHash":"c7e19d22e496bbdc9bab13ef6c5346583906cfb6baf5e3851507410660ffd692","addressRefs":[]},"4999136f-41f3-49a1-93db-2d72b14c2f17":{"id":"4999136f-41f3-49a1-93db-2d72b14c2f17","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4325,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"99474f36-6c37-4627-acdb-0372fdf216ef":{"id":"99474f36-6c37-4627-acdb-0372fdf216ef","doc_no":"A.6.1.1.1.2.6.1.3.1.7.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4326,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"cfc335a4-efcf-4f53-9609-1c9784cbb784":{"id":"cfc335a4-efcf-4f53-9609-1c9784cbb784","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5","title":"Ethereum Mainnet - Curve weETH/WETH-ng for Swaps Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4327,"content":"The documents herein contain the Instance Configuration Document for the Curve weETH/WETH-ng for Swaps Instance.","contentHash":"fe2845a7bea32c681a779759eeaf76c61fed571c6ed44ca46b7c30247796836e","addressRefs":[]},"1020417c-dc56-4808-b867-178ca4ca8681":{"id":"1020417c-dc56-4808-b867-178ca4ca8681","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4328,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"a1dc6fa3-bec8-41ca-bb5a-e60275c03dcf":{"id":"a1dc6fa3-bec8-41ca-bb5a-e60275c03dcf","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4329,"content":"The documents herein define the parameters of the Curve weETH/WETH-ng for Swaps Instance of the Allocation System Primitive.","contentHash":"c98f33de32093ce441396eea77e70cfd90dd854021297fcb417aa7d86f5bfa9e","addressRefs":[]},"b7f9fa20-dddb-4733-b0e1-9029e79a8aba":{"id":"b7f9fa20-dddb-4733-b0e1-9029e79a8aba","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4330,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"853b65c3-4b43-436d-9350-cf7ffbed559e":{"id":"853b65c3-4b43-436d-9350-cf7ffbed559e","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4331,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"2b599f55-2177-4aad-b9be-a2cda8608900":{"id":"2b599f55-2177-4aad-b9be-a2cda8608900","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4332,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"c7a2911c-faf7-40f4-9a90-c43e75bc2396":{"id":"c7a2911c-faf7-40f4-9a90-c43e75bc2396","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4333,"content":"N/A - swap only","contentHash":"6adc1bfaa3d25c3520f75e4cbccc8b2ad1f9ddd970d2e7afa40cc5d41578c79c","addressRefs":[]},"25de66b2-d391-44ab-b88c-9e558679640c":{"id":"25de66b2-d391-44ab-b88c-9e558679640c","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4334,"content":"crv2pool","contentHash":"352779a5590ec32889527a65f7b23497415a731bf03188d4ed17c0ef3ebeffef","addressRefs":[]},"dfbfa2ba-6fd5-4e56-9366-992e64d86ac1":{"id":"dfbfa2ba-6fd5-4e56-9366-992e64d86ac1","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4335,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"92a9fec3-7b4d-4388-bd05-7d18790bc584":{"id":"92a9fec3-7b4d-4388-bd05-7d18790bc584","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4336,"content":"`0xDB74dfDD3BB46bE8Ce6C33dC9D82777BCFc3dEd5`","contentHash":"96f0d5ef0fd6e1a81b97d28c10a92e30a9da1647b6dc710515edf7f24363a1ce","addressRefs":["0xdb74dfdd3bb46be8ce6c33dc9d82777bcfc3ded5"]},"c740d6f1-cda5-46d5-b7a7-6d2358c3770f":{"id":"c740d6f1-cda5-46d5-b7a7-6d2358c3770f","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4337,"content":"`0xCd5fE23C85820F7B72D0926FC9b05b43E359b7ee`","contentHash":"f940a033f7741146bdd367a479ff9c71212d5839efc99fb000d925541516842e","addressRefs":["0xcd5fe23c85820f7b72d0926fc9b05b43e359b7ee"]},"ad094f82-5619-4558-abd1-e793131e9ec0":{"id":"ad094f82-5619-4558-abd1-e793131e9ec0","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.2.3","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4338,"content":"`0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`","contentHash":"5ef212c07212264f2e18a396322922471d4c261110a4d732f7bc966d8277fe71","addressRefs":["0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"]},"96a50ef4-938b-475e-8244-40d376e95e6e":{"id":"96a50ef4-938b-475e-8244-40d376e95e6e","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.2.4","title":"Pool Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4339,"content":"`0xDB74dfDD3BB46bE8Ce6C33dC9D82777BCFc3dEd5`","contentHash":"96f0d5ef0fd6e1a81b97d28c10a92e30a9da1647b6dc710515edf7f24363a1ce","addressRefs":["0xdb74dfdd3bb46be8ce6c33dc9d82777bcfc3ded5"]},"7fabde01-b8a5-4226-85d4-b25f55d93b12":{"id":"7fabde01-b8a5-4226-85d4-b25f55d93b12","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4340,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"dac0cadf-a966-40d3-b739-09a0baceea30":{"id":"dac0cadf-a966-40d3-b739-09a0baceea30","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4341,"content":"The current `maxAmount`, `slope` and slippage for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"bcc9d2cc49801b82136efd2350649a7641bcf99add0f2d72285bd5add7cde1e0","addressRefs":[]},"8734b53f-0220-43df-acdc-3c8cb25f323a":{"id":"8734b53f-0220-43df-acdc-3c8cb25f323a","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4342,"content":"The inflow rate limits are:\n\n- maxAmount: N/A - swap only\n- slope: N/A - swap only","contentHash":"c502d4dcb51a97cda55f82062b7c0ee8b9222219a2779d922e954d829d6bc636","addressRefs":[]},"8280f97f-d69c-4fc3-a9d4-42407159a5ea":{"id":"8280f97f-d69c-4fc3-a9d4-42407159a5ea","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4343,"content":"The outflow rate limits are:\n\n- maxAmount: N/A - swap only\n- slope: N/A - swap only","contentHash":"d843bc67b7b5c9b45c7fc014717e848d546f9acb427f211e554c62d3d17c6128","addressRefs":[]},"b24f80d1-80cc-46c0-895c-d9bdc49e2e8b":{"id":"b24f80d1-80cc-46c0-895c-d9bdc49e2e8b","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4344,"content":"The swap rate limits are:\n\n- `maxAmount`: 1,000\n- `slope`: 50,000 per day\n- `Max slippage`: 0.25%","contentHash":"c7c98df24ea81442e31952b14d95b31988d7793391fb3eb3dc67f1ee2a79a8c2","addressRefs":[]},"a8106b30-ef8c-4ce5-a25a-80755ab624d0":{"id":"a8106b30-ef8c-4ce5-a25a-80755ab624d0","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4345,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"28a4bce9-e6d9-4840-8b0b-ed7d9f454dd1":{"id":"28a4bce9-e6d9-4840-8b0b-ed7d9f454dd1","doc_no":"A.6.1.1.1.2.6.1.3.1.7.5.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4346,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"8efd627c-7439-4ea9-aabc-ecdffb5cb2ec":{"id":"8efd627c-7439-4ea9-aabc-ecdffb5cb2ec","doc_no":"A.6.1.1.1.2.6.1.3.1.8","title":"Morpho","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4347,"content":"The Ethereum Mainnet Instances of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"e9eca72d304ea5bab98e0c173553d3a6061edbb10327e17a038f36999f8a339a","addressRefs":[]},"626dd4bf-108b-48bd-a1e1-c26d290c3a72":{"id":"626dd4bf-108b-48bd-a1e1-c26d290c3a72","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1","title":"Ethereum Mainnet - Morpho Dai Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4348,"content":"The documents herein contain the Instance Configuration Document for the Morpho Dai Instance.","contentHash":"f4e4edce05b7439be9d5425ea4556792e56c10e5787aa17004843e9ef3420711","addressRefs":[]},"a96c3d29-51b2-45b8-9820-56ec9edeffd3":{"id":"a96c3d29-51b2-45b8-9820-56ec9edeffd3","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4349,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"b0ae7680-7179-4fd6-93f0-56c03d6f91eb":{"id":"b0ae7680-7179-4fd6-93f0-56c03d6f91eb","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4350,"content":"The documents herein define the parameters of the Morpho Dai Instance of the Allocation System Primitive.","contentHash":"a6dcc2ee56ec27a258a2595444c6316b40317dd6741a6d7ecd5ac66b4462d53c","addressRefs":[]},"d378528c-192a-4b4b-b4ad-0fd39cf6d9a0":{"id":"d378528c-192a-4b4b-b4ad-0fd39cf6d9a0","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4351,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"acfbf398-dfe6-415a-8355-36aaf57b4322":{"id":"acfbf398-dfe6-415a-8355-36aaf57b4322","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4352,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"4de6d799-4ebf-4876-af77-c9cbfee16bac":{"id":"4de6d799-4ebf-4876-af77-c9cbfee16bac","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4353,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"5bde4982-cdea-482b-972a-372352c883a1":{"id":"5bde4982-cdea-482b-972a-372352c883a1","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4354,"content":"Dai","contentHash":"41409b0b8b16323a6dbf78c6efdc74b207b406e4a360b7be4281455d4045c2ee","addressRefs":[]},"a1eca238-d0bc-4372-899e-3cd3c42908cc":{"id":"a1eca238-d0bc-4372-899e-3cd3c42908cc","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4355,"content":"spDAI","contentHash":"26392c6349b06c05018ba39c5230892fab010d690ca778546af46fbfb85925db","addressRefs":[]},"1de795f6-94fe-4a9b-8952-f11375f2c330":{"id":"1de795f6-94fe-4a9b-8952-f11375f2c330","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4356,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"1614a57a-15d9-4081-862b-d1b1d80f59f4":{"id":"1614a57a-15d9-4081-862b-d1b1d80f59f4","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4357,"content":"`0x73e65DBD630f90604062f6E02fAb9138e713edD9`","contentHash":"a79b6bd43bf0361e4f91c1735ad1236d8d825b14e85dc8efbc13cde9521081b9","addressRefs":["0x73e65dbd630f90604062f6e02fab9138e713edd9"]},"faf749a9-9737-49c8-8783-e09034ab190d":{"id":"faf749a9-9737-49c8-8783-e09034ab190d","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4358,"content":"`0x6B175474E89094C44Da98b954EedeAC495271d0F`","contentHash":"d80fdc7ccee4b09cd1e64ad674b56132ee4ac90ad5b61477c2096cdf6e4746a6","addressRefs":["0x6b175474e89094c44da98b954eedeac495271d0f"]},"191e781d-17da-459c-9366-88d0efc8a4d8":{"id":"191e781d-17da-459c-9366-88d0efc8a4d8","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4359,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"9a6b7691-5bdf-497d-a8d3-0421624c23c1":{"id":"9a6b7691-5bdf-497d-a8d3-0421624c23c1","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4360,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"27c105d3-a93c-45b9-b951-050e60a50c51":{"id":"27c105d3-a93c-45b9-b951-050e60a50c51","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4361,"content":"The inflow rate limits are:\n\n- `maxAmount`: 200,000,000 DAI\n- `slope`: 100,000,000 DAI per day","contentHash":"15538825b94ea3340a60d2fc46b27ea8be09d11815b536abc29a1e7d0edaa9d2","addressRefs":[]},"5cbdb15a-3a5b-4ea3-9fc2-4098f512712c":{"id":"5cbdb15a-3a5b-4ea3-9fc2-4098f512712c","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4362,"content":"The outflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"f86f9b8db49561115373b94ce3c5597ef57303406aa4653493a0f3808edf7859","addressRefs":[]},"d39f115f-51e6-466a-a329-8761d4ae50c0":{"id":"d39f115f-51e6-466a-a329-8761d4ae50c0","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4363,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"e76bc120-89fd-438f-b338-7951f4660a7e":{"id":"e76bc120-89fd-438f-b338-7951f4660a7e","doc_no":"A.6.1.1.1.2.6.1.3.1.8.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4364,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"138be894-8a4a-4e8c-9fdd-0f8183935d24":{"id":"138be894-8a4a-4e8c-9fdd-0f8183935d24","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2","title":"Ethereum Mainnet - Morpho USDS Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4365,"content":"The documents herein contain the Instance Configuration Document for the Morpho USDS Instance.","contentHash":"672b6ceb240c6bbdd2492d0b7e0770461c19c4e82932c902b1a597d609dcf0de","addressRefs":[]},"0fd39503-617a-4850-8a11-2b0f2f7b5ae7":{"id":"0fd39503-617a-4850-8a11-2b0f2f7b5ae7","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4366,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"f1b8abcc-2254-4826-9a82-f03f78d4f846":{"id":"f1b8abcc-2254-4826-9a82-f03f78d4f846","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4367,"content":"The documents herein define the parameters of the Morpho USDS Instance of the Allocation System Primitive.","contentHash":"3ed5b6a6a5683b28541e1167933912f1aa240c1e59010e1235366b0b0bc30652","addressRefs":[]},"1676db92-f89e-4701-b4ea-dc14475b603c":{"id":"1676db92-f89e-4701-b4ea-dc14475b603c","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4368,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"146f0253-a524-4d2d-b047-68df518ea163":{"id":"146f0253-a524-4d2d-b047-68df518ea163","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4369,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"0e95f0b2-4d41-4676-8dcb-f5faeb2768ef":{"id":"0e95f0b2-4d41-4676-8dcb-f5faeb2768ef","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4370,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"0a270b1d-8ce7-487c-b571-1f7f114eb19e":{"id":"0a270b1d-8ce7-487c-b571-1f7f114eb19e","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4371,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"55807963-1266-4eb3-ba61-f1073dbcc685":{"id":"55807963-1266-4eb3-ba61-f1073dbcc685","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4372,"content":"sparkUSDS","contentHash":"8ed358edda06bf29b4098d92e1d5b73a5c78f6ea44f64d5f3c40faf6b80745dd","addressRefs":[]},"5bdcf2a4-85a3-45df-b525-3de5fce91391":{"id":"5bdcf2a4-85a3-45df-b525-3de5fce91391","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4373,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"972aa481-5c2c-44e0-956e-f649e86f6cc2":{"id":"972aa481-5c2c-44e0-956e-f649e86f6cc2","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4374,"content":"`0xe41a0583334f0dc4E023Acd0bFef3667F6FE0597`","contentHash":"fbedbf4cfc7b2e0fadb2daefab5baad5460972cc82a6d2e8028fdafd378842b5","addressRefs":["0xe41a0583334f0dc4e023acd0bfef3667f6fe0597"]},"64e52154-360d-49e5-882c-6ef389b7a2df":{"id":"64e52154-360d-49e5-882c-6ef389b7a2df","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4375,"content":"`0xdC035D45d973E3EC169d2276DDab16f1e407384F`","contentHash":"70054b0ff65437cb32b35df32f8e11d1cc8ea540e9916e08d1cd96696d95e083","addressRefs":["0xdc035d45d973e3ec169d2276ddab16f1e407384f"]},"e40cb4f0-7ff1-4c64-a936-5e33189952a5":{"id":"e40cb4f0-7ff1-4c64-a936-5e33189952a5","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.2.3","title":"Allocator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4376,"content":"`0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178`","contentHash":"0753c6929ebb76a77ed56ac1ffa3696c8c73a192969cdcbd25379332f8be1044","addressRefs":["0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"73b8b172-1562-4729-9d21-832bf1efdd19":{"id":"73b8b172-1562-4729-9d21-832bf1efdd19","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4377,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"aa89df3f-655e-4e91-952b-41db6b7e5671":{"id":"aa89df3f-655e-4e91-952b-41db6b7e5671","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4378,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"6fb6752a-a468-4f67-92a3-f86038be581d":{"id":"6fb6752a-a468-4f67-92a3-f86038be581d","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4379,"content":"The inflow rate limits are:\n\n- `maxAmount`: 200,000,000 USDS\n- `slope`: 100,000,000 USDS per day","contentHash":"229507971bea3dcdb31273e897cd83172d758db6647ad08b32d2c3c7a8605108","addressRefs":[]},"6f8914eb-62e1-4946-901a-ae70839845fc":{"id":"6f8914eb-62e1-4946-901a-ae70839845fc","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4380,"content":"The outflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"f86f9b8db49561115373b94ce3c5597ef57303406aa4653493a0f3808edf7859","addressRefs":[]},"731b87e1-bf2e-4214-9574-16074809b771":{"id":"731b87e1-bf2e-4214-9574-16074809b771","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4381,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"86e8dd23-9895-453f-a56a-460eaff0c0a2":{"id":"86e8dd23-9895-453f-a56a-460eaff0c0a2","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4382,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"e560d14b-b1f1-4351-9214-62a3d6d7fd53":{"id":"e560d14b-b1f1-4351-9214-62a3d6d7fd53","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4383,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"bfdae446-8562-4c34-8bf8-9f6d7d612d2e":{"id":"bfdae446-8562-4c34-8bf8-9f6d7d612d2e","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.4.1","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4384,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"ca1eb012-2401-4e24-9e9e-a76f869e422d":{"id":"ca1eb012-2401-4e24-9e9e-a76f869e422d","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.4.1.1","title":"Curator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4385,"content":"`0x0f963A8A8c01042B69054e787E5763ABbB0646A3`","contentHash":"a57f654d13b483afeed9b6d9529e6c2c9210b95a6467dc5bbc34878b9cc20805","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3"]},"86831263-5a01-4259-80e6-7829f062a1e6":{"id":"86831263-5a01-4259-80e6-7829f062a1e6","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.4.1.2","title":"Guardian Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4386,"content":"`0xf5748bBeFa17505b2F7222B23ae11584932C908B`","contentHash":"668a86bee4a9f2f78e24f2549b98c35e72d36e967e29827d12a4c7108e4269f6","addressRefs":["0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"bf0333e1-219a-4dc2-89d9-0ac64907c3d2":{"id":"bf0333e1-219a-4dc2-89d9-0ac64907c3d2","doc_no":"A.6.1.1.1.2.6.1.3.1.8.2.4.2","title":"Timelock","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4387,"content":"Timelock: 240 hours (10 days)","contentHash":"bd70db312c9585d38ff92e664b2ee51c62b5185a730a6bc4b8efaf617abbe565","addressRefs":[]},"f3063596-4f85-4a51-b52c-58221d043d3e":{"id":"f3063596-4f85-4a51-b52c-58221d043d3e","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3","title":"Ethereum Mainnet - Morpho USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4388,"content":"The documents herein contain the Instance Configuration Document for the Morpho USDC Instance.","contentHash":"05aa2adb10dd9e6c900c831b6ca274a1f430c8ecb027a5b3698a83b41427c70c","addressRefs":[]},"6e492a2b-7105-4c7f-a659-2fa62dc3617f":{"id":"6e492a2b-7105-4c7f-a659-2fa62dc3617f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4389,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"925286bb-f987-4d35-8c74-23279a2c018f":{"id":"925286bb-f987-4d35-8c74-23279a2c018f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4390,"content":"The documents herein define the parameters of the Morpho USDC Instance of the Allocation System Primitive.","contentHash":"1471abfad928be56ca77c6d9880c672b2dcf1e3dd3e7335b8399d5f0f501e4d0","addressRefs":[]},"46c99f91-4d4f-424f-a431-439103ad83f4":{"id":"46c99f91-4d4f-424f-a431-439103ad83f4","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4391,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"f02eb3b3-62df-4086-8e85-be37f7b80d85":{"id":"f02eb3b3-62df-4086-8e85-be37f7b80d85","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4392,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"ed302176-488b-43e5-ac32-51c77badf0fe":{"id":"ed302176-488b-43e5-ac32-51c77badf0fe","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4393,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"c1dd3047-57f6-4410-9c13-febcceae5971":{"id":"c1dd3047-57f6-4410-9c13-febcceae5971","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4394,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"f056c54a-476a-419c-8baf-2d5c5b70797f":{"id":"f056c54a-476a-419c-8baf-2d5c5b70797f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4395,"content":"sparkUSDCbc","contentHash":"4dd16d1f614572ae4c99130f6fe80c675c8fe9ca92de869af9716739823a5228","addressRefs":[]},"73277621-b349-47cf-af66-a5444f8f1c58":{"id":"73277621-b349-47cf-af66-a5444f8f1c58","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4396,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"711b3b1f-ecf8-42d4-8112-00d032cb4293":{"id":"711b3b1f-ecf8-42d4-8112-00d032cb4293","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4397,"content":"`0x56A76b428244a50513ec81e225a293d128fd581D`","contentHash":"0ab7b3d2a4ebe64ec341e6b7707ef54cbe904ea793833312f98eab41be072cd4","addressRefs":["0x56a76b428244a50513ec81e225a293d128fd581d"]},"cfad62db-289a-4840-a31b-1ec231c8a1da":{"id":"cfad62db-289a-4840-a31b-1ec231c8a1da","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4398,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"b63d90f5-1c8a-41e0-8ada-5db9986ec4a2":{"id":"b63d90f5-1c8a-41e0-8ada-5db9986ec4a2","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.2.3","title":"Allocator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4399,"content":"`0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178`","contentHash":"0753c6929ebb76a77ed56ac1ffa3696c8c73a192969cdcbd25379332f8be1044","addressRefs":["0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"5b0ead44-7dce-4af5-b750-422c8f97c4ce":{"id":"5b0ead44-7dce-4af5-b750-422c8f97c4ce","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4400,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"d24c412e-6ba8-4b1b-a3c6-ccb48b268e2f":{"id":"d24c412e-6ba8-4b1b-a3c6-ccb48b268e2f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4401,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"024d6105-55ae-4a54-b5be-c5e17987fb0f":{"id":"024d6105-55ae-4a54-b5be-c5e17987fb0f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4402,"content":"The inflow rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 25,000,000 USDC per day","contentHash":"124addf4b59ca489b8075ddba136ee430a3ef3a872b3a36890a80c95d062de59","addressRefs":[]},"7385df6a-1431-41ef-8f05-bc4e78d48ed3":{"id":"7385df6a-1431-41ef-8f05-bc4e78d48ed3","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4403,"content":"The outflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"f86f9b8db49561115373b94ce3c5597ef57303406aa4653493a0f3808edf7859","addressRefs":[]},"564ac34b-aa6c-46ec-9fd4-9f7caed7c31b":{"id":"564ac34b-aa6c-46ec-9fd4-9f7caed7c31b","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4404,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"d778fa59-35a2-4b5a-9e22-2880e99746a4":{"id":"d778fa59-35a2-4b5a-9e22-2880e99746a4","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4405,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"d30c7467-bdc4-42b7-a0fd-332828e5acd7":{"id":"d30c7467-bdc4-42b7-a0fd-332828e5acd7","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4406,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"a672e8f2-886e-4d1f-a217-364e638408d9":{"id":"a672e8f2-886e-4d1f-a217-364e638408d9","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.4.1","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4407,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"ac41be8b-f6c9-4df2-9fac-c543c77e0166":{"id":"ac41be8b-f6c9-4df2-9fac-c543c77e0166","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.4.1.1","title":"Curator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4408,"content":"`0x0f963A8A8c01042B69054e787E5763ABbB0646A3`","contentHash":"a57f654d13b483afeed9b6d9529e6c2c9210b95a6467dc5bbc34878b9cc20805","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3"]},"b7d0b9a8-4dba-4fba-8aab-b5afd645a6d0":{"id":"b7d0b9a8-4dba-4fba-8aab-b5afd645a6d0","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.4.1.2","title":"Guardian Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4409,"content":"`0xf5748bBeFa17505b2F7222B23ae11584932C908B`","contentHash":"668a86bee4a9f2f78e24f2549b98c35e72d36e967e29827d12a4c7108e4269f6","addressRefs":["0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"d2692d99-d52c-4586-8dbe-b23d8f835f29":{"id":"d2692d99-d52c-4586-8dbe-b23d8f835f29","doc_no":"A.6.1.1.1.2.6.1.3.1.8.3.4.2","title":"Timelock","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4410,"content":"Timelock: 240 hours (10 days)","contentHash":"bd70db312c9585d38ff92e664b2ee51c62b5185a730a6bc4b8efaf617abbe565","addressRefs":[]},"a2f66f86-ddea-4260-820a-cde66a861413":{"id":"a2f66f86-ddea-4260-820a-cde66a861413","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4","title":"Ethereum Mainnet - Morpho USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4411,"content":"The documents herein contain the Instance Configuration Document for the Morpho USDT Instance.","contentHash":"a5042f07928ac4b24c7290070d2be2239d9594538ded110123e27979daf13bd7","addressRefs":[]},"0679d377-0d6f-4511-a8a9-2c1fe7b5d78f":{"id":"0679d377-0d6f-4511-a8a9-2c1fe7b5d78f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4412,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"3c749393-8134-4483-ad35-c6820768421f":{"id":"3c749393-8134-4483-ad35-c6820768421f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4413,"content":"The documents herein define the parameters of the Morpho USDT Instance of the Allocation System Primitive.","contentHash":"65a600a4f919cd8972c32fb5e5f03a02e2dbe8149fca0a9d2f3d94d95a110252","addressRefs":[]},"077e23e8-fc30-4dc9-8c61-c08f7fe10864":{"id":"077e23e8-fc30-4dc9-8c61-c08f7fe10864","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4414,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"bea790d6-8b58-45fb-a974-2813284831ee":{"id":"bea790d6-8b58-45fb-a974-2813284831ee","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4415,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"a700da65-026f-4cf7-a1fb-a30cedc10189":{"id":"a700da65-026f-4cf7-a1fb-a30cedc10189","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4416,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"9ecacc4a-fe57-427b-a652-92409b64aef6":{"id":"9ecacc4a-fe57-427b-a652-92409b64aef6","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4417,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"46ea2f39-26c6-4ac4-9ee7-baf921d8e86e":{"id":"46ea2f39-26c6-4ac4-9ee7-baf921d8e86e","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4418,"content":"sparkUSDT","contentHash":"862b49f5f0c7796da1a420ed513d9fff317fa40a5ca699bdd85285b1382a5773","addressRefs":[]},"1eb8cc31-5d23-4aaa-b99e-b57654c9dbc4":{"id":"1eb8cc31-5d23-4aaa-b99e-b57654c9dbc4","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4419,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"c4629de2-eb51-4661-a4bc-6b955e267f5f":{"id":"c4629de2-eb51-4661-a4bc-6b955e267f5f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4420,"content":"`0xc7CDcFDEfC64631ED6799C95e3b110cd42F2bD22`","contentHash":"f10c13fb50187a17c75dcd3e4deeb7a92a2d9424b76b3d111b0d013cc1df3d09","addressRefs":["0xc7cdcfdefc64631ed6799c95e3b110cd42f2bd22"]},"a3ed9893-931b-4d4e-9cf9-35373d1ed005":{"id":"a3ed9893-931b-4d4e-9cf9-35373d1ed005","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4421,"content":"`0xdac17f958d2ee523a2206206994597c13d831ec7`","contentHash":"dd1fc2f3aabff090cd851e54a3247ad5101087a6bdf58e7a07b5ba17bc0840d4","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"30cdfa34-7b8d-4280-bda2-ec53940a8093":{"id":"30cdfa34-7b8d-4280-bda2-ec53940a8093","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.2.3","title":"Allocator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4422,"content":"`0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178`","contentHash":"0753c6929ebb76a77ed56ac1ffa3696c8c73a192969cdcbd25379332f8be1044","addressRefs":["0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"bde22f96-915b-4073-840f-ac0408aa8407":{"id":"bde22f96-915b-4073-840f-ac0408aa8407","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4423,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"7eaf8614-3343-4a6b-a637-8a92a7115bbb":{"id":"7eaf8614-3343-4a6b-a637-8a92a7115bbb","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4424,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"0c654529-b8b7-4071-bc72-5eee02d295c9":{"id":"0c654529-b8b7-4071-bc72-5eee02d295c9","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4425,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,000 USDT\n- `slope`: 1,000,000,000 USDT per day","contentHash":"31ff6f5aa4187c8b1b8a073defc04598d376e3475eb13288e481756001f7ba9a","addressRefs":[]},"6dab7518-caa3-4339-a573-718675fe19ee":{"id":"6dab7518-caa3-4339-a573-718675fe19ee","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4426,"content":"The outflow rate limits are:\n\n- `maxAmount`: unlimited\n- `slope`: unlimited","contentHash":"d203bbdf6281d01b57bd47618604541e76fe7348908ab03b5a2ed8a8d7d37505","addressRefs":[]},"3bb2d3ac-cdcc-4f25-a03c-71d2d0902582":{"id":"3bb2d3ac-cdcc-4f25-a03c-71d2d0902582","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4427,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"32759a33-f619-4a41-a4fd-fbcdb642a82a":{"id":"32759a33-f619-4a41-a4fd-fbcdb642a82a","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4428,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"06914650-b873-4c39-8389-5c615c64edf7":{"id":"06914650-b873-4c39-8389-5c615c64edf7","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4429,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"bcf45274-0125-4856-a405-ed2726fad468":{"id":"bcf45274-0125-4856-a405-ed2726fad468","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.1","title":"Market Exposure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4430,"content":"The documents herein contain exposure details for this Instance","contentHash":"97f49d23aa5183a63a8cd0221e9d4def703078a03c39366fd85c59a969622931","addressRefs":[]},"2187c7a6-d9d2-46c7-a794-5779939c708f":{"id":"2187c7a6-d9d2-46c7-a794-5779939c708f","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.1.1","title":"sUSDS/USDT 96.5% LLTV Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4431,"content":"- Pool ID: 0x3274643db77a064abd3bc851de77556a4ad2e2f502f4f0c80845fa8f909ecf0b\n- Absolute cap: Unlimited\n- Relative cap: 100%","contentHash":"71472ca418491f9a724c57d1453a82b9bbd7f2e2574957213aebc313de12a5b4","addressRefs":[]},"28068a47-d95a-4edb-a7cd-15a9fa769d01":{"id":"28068a47-d95a-4edb-a7cd-15a9fa769d01","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.1.2","title":"wstETH/USDT 86% LLTV Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4432,"content":"- Pool ID: 0xe7e9694b754c4d4f7e21faf7223f6fa71abaeb10296a4c43a54a7977149687d2\n- Absolute cap: 250 million\n- Relative cap: 100%","contentHash":"38bfff1d58597a1087342d0207de07211b0fe822c37680a00629c7da068985a0","addressRefs":[]},"c2b81ec6-62d4-4a8e-8195-411051e74708":{"id":"c2b81ec6-62d4-4a8e-8195-411051e74708","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.1.3","title":"WBTC/USDT 86% LLTV Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4433,"content":"- Pool ID: 0xa921ef34e2fc7a27ccc50ae7e4b154e16c9799d3387076c421423ef52ac4df99\n- Absolute cap: 100 million\n- Relative cap: 100%","contentHash":"a5fcce8101777e1919e00435c791ab3ac2b6e838ac4b4085165d8708f3c73bc1","addressRefs":[]},"b89ff2c9-be7e-4634-bddd-8ebbf5eb6769":{"id":"b89ff2c9-be7e-4634-bddd-8ebbf5eb6769","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.1.4","title":"cbBTC/USDT 86% LLTV Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4434,"content":"- Pool ID: 0x45671fb8d5dea1c4fbca0b8548ad742f6643300eeb8dbd34ad64a658b2b05bca\n- Absolute cap: 250 million\n- Relative cap: 100%","contentHash":"4200b3e675e11b4742f4ff5a2f3385aa60d70117c11b61f60ad08514c11c9c3a","addressRefs":[]},"c481d26c-a4b1-4c76-9031-478bd64a8aca":{"id":"c481d26c-a4b1-4c76-9031-478bd64a8aca","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4435,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"e71e777b-b5a8-41bb-8434-97650500467a":{"id":"e71e777b-b5a8-41bb-8434-97650500467a","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.2.1","title":"Curator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4436,"content":"`0x0f963A8A8c01042B69054e787E5763ABbB0646A3`","contentHash":"a57f654d13b483afeed9b6d9529e6c2c9210b95a6467dc5bbc34878b9cc20805","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3"]},"6e105430-ea5c-4368-b76f-725c0208afdc":{"id":"6e105430-ea5c-4368-b76f-725c0208afdc","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.2.2","title":"Guardian Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4437,"content":"`0xf5748bBeFa17505b2F7222B23ae11584932C908B`","contentHash":"668a86bee4a9f2f78e24f2549b98c35e72d36e967e29827d12a4c7108e4269f6","addressRefs":["0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"62c056de-3136-4faa-bb86-3b348e2e874c":{"id":"62c056de-3136-4faa-bb86-3b348e2e874c","doc_no":"A.6.1.1.1.2.6.1.3.1.8.4.4.3","title":"Timelock","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4438,"content":"Timelock: 240 hours (10 days)","contentHash":"bd70db312c9585d38ff92e664b2ee51c62b5185a730a6bc4b8efaf617abbe565","addressRefs":[]},"47f2b461-1d82-4ee8-8cd2-39c95184c51b":{"id":"47f2b461-1d82-4ee8-8cd2-39c95184c51b","doc_no":"A.6.1.1.1.2.6.1.3.1.9","title":"Spark Savings V2","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4439,"content":"The Ethereum Mainnet Instances of the Spark Savings v2 with `Active` Status are stored herein.","contentHash":"e394d438b9426bc0248f8b55dbea84b4298ea69628e5b358b437488b9949c741","addressRefs":[]},"831b4fd8-06c6-4734-bb3a-93678082d8cc":{"id":"831b4fd8-06c6-4734-bb3a-93678082d8cc","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1","title":"Ethereum Mainnet - Spark Savings v2 ETH Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4440,"content":"The documents herein contain the Instance Configuration Document for the Spark Savings v2 ETH Instance.","contentHash":"727ee1496bef0b2eda5f28188828a35368e27f97d55e75d858df95007c2ff52a","addressRefs":[]},"917d6e87-5dd3-4190-9ec6-909460d88b03":{"id":"917d6e87-5dd3-4190-9ec6-909460d88b03","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4441,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"e55eba15-5b8d-4a2d-bf5a-704dfceb6457":{"id":"e55eba15-5b8d-4a2d-bf5a-704dfceb6457","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4442,"content":"The documents herein define the parameters of the Spark Savings v2 ETH Instance of the Allocation System Primitive.","contentHash":"822805f853ab2ee994a3f6e819c0889194ee608be36c94d146ca6e1e89ef8d4a","addressRefs":[]},"95bbd1c5-f7c9-4f77-883c-a593fd930656":{"id":"95bbd1c5-f7c9-4f77-883c-a593fd930656","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4443,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"448d472c-0d5f-4a24-a4f0-6ee855f384ac":{"id":"448d472c-0d5f-4a24-a4f0-6ee855f384ac","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4444,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"ad53ae31-1644-4680-bcf3-ca894600199e":{"id":"ad53ae31-1644-4680-bcf3-ca894600199e","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4445,"content":"Spark Savings Protocol","contentHash":"ddf2cdda69c7d7d4d4ccba4cd3dd7f3deb1cca801180b93f57a14ca43a802f16","addressRefs":[]},"8d9ff794-c545-4179-8bb4-214943250467":{"id":"8d9ff794-c545-4179-8bb4-214943250467","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.1.3","title":"Asset Supplied By Users","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4446,"content":"wETH","contentHash":"03148f9088c3c45c648def5b62ee6c9017f41526d51f77fd7d8560f6721c35d3","addressRefs":[]},"964ef35e-bde9-4fa3-b07b-f423f35d2f80":{"id":"964ef35e-bde9-4fa3-b07b-f423f35d2f80","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4447,"content":"spETH","contentHash":"b1804147f008c19688e076f17575c21c166e325461b34ad0a6bd055941034439","addressRefs":[]},"a59789f1-bcad-42a3-98ba-bb9c0aa92b0d":{"id":"a59789f1-bcad-42a3-98ba-bb9c0aa92b0d","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4448,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"93f2939e-b2d2-4c2e-b74d-8af8b9fbf12e":{"id":"93f2939e-b2d2-4c2e-b74d-8af8b9fbf12e","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4449,"content":"`0xfE6eb3b609a7C8352A241f7F3A21CEA4e9209B8f`","contentHash":"77f734b5b23c18d2f6cc41a474c029a124c2acb4610829fe458ce57e460dd322","addressRefs":["0xfe6eb3b609a7c8352a241f7f3a21cea4e9209b8f"]},"cb300f77-edf2-45eb-8f2a-14d1455a7d1d":{"id":"cb300f77-edf2-45eb-8f2a-14d1455a7d1d","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4450,"content":"`0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2`","contentHash":"5ef212c07212264f2e18a396322922471d4c261110a4d732f7bc966d8277fe71","addressRefs":["0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"]},"0471c82b-6517-4f35-afe2-eebe6a02d052":{"id":"0471c82b-6517-4f35-afe2-eebe6a02d052","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4451,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"fef37e25ee6ae99b46a1e7920573dc23171ba7812ee156dde99b1069994255d3","addressRefs":[]},"318fa90a-2fd9-42cc-af6a-086063caebc6":{"id":"318fa90a-2fd9-42cc-af6a-086063caebc6","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4452,"content":"The specific `maxAmount` and `slope` for this conduit's inflow/outflow are not defined for this Instance.","contentHash":"7a7beff7b4c6ecb868851425e1b215b313106005b011131a0944d74e97d2d9fe","addressRefs":[]},"87c19bc8-2029-498e-887b-f5c9ec095107":{"id":"87c19bc8-2029-498e-887b-f5c9ec095107","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4453,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"c22fc43d-2947-4919-a266-9e5809a93736":{"id":"c22fc43d-2947-4919-a266-9e5809a93736","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4454,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"06f87be7-087d-480c-8cd8-4baa4ab4b170":{"id":"06f87be7-087d-480c-8cd8-4baa4ab4b170","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4455,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"7fde7297-118e-4485-b4bd-c844773e0233":{"id":"7fde7297-118e-4485-b4bd-c844773e0233","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.1","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4456,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"868225a7-68c0-4046-9ee9-9461963664a8":{"id":"868225a7-68c0-4046-9ee9-9461963664a8","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.1.1","title":"Spark Vault v2 Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4457,"content":"`0x1b992302652A92611DCd5090D1Cb388C6377f455`","contentHash":"13f481f26993d63a2d75a60223dc2a489f77b2a5adba1b55b59d27bba1a9bb66","addressRefs":["0x1b992302652a92611dcd5090d1cb388c6377f455"]},"3b166ec3-5185-4b14-8737-7febd99ec3e8":{"id":"3b166ec3-5185-4b14-8737-7febd99ec3e8","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.1.2","title":"Default admin","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4458,"content":"`0x3300f198988e4C9C63F75dF86De36421f06af8c4`","contentHash":"f428ffd85508f6ee93b14672cd7accb8ba8646f143a12d81dd70641788fb9bc0","addressRefs":["0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"a2802a44-0979-4af6-bbdf-ffb01f46120d":{"id":"a2802a44-0979-4af6-bbdf-ffb01f46120d","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.1.3","title":"Setter","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4459,"content":"`0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC`","contentHash":"a4be1caa48d1c4c87ad16384d3686b46723fadc9e7ac5bd267c2413470eeb82f","addressRefs":["0x2e1b01adabb8d4981863394bea23a1263cbaedfc"]},"e58963e6-b6a5-4ecd-a681-117ec7eaa2ae":{"id":"e58963e6-b6a5-4ecd-a681-117ec7eaa2ae","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.1.4","title":"Taker","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4460,"content":"`0x1601843c5E9bC251A3272907010AFa41Fa18347E`","contentHash":"aeed6d422ed874d65c9f2940a43b9369ddf73673dbeaa1f279263595d843dd3a","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e"]},"cafa5499-a804-479b-8af9-5a07cd4735af":{"id":"cafa5499-a804-479b-8af9-5a07cd4735af","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.2","title":"Risk Parameters Current Configuration","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4461,"content":"The subdocuments herein define the current configuration of the risk parameters.","contentHash":"ae95706409030fd9a4186329c0ae2d52597b2b1e0c27b553b62ee8b3d7690a86","addressRefs":[]},"94ab6b40-66aa-4a42-8df9-b9fb633ba306":{"id":"94ab6b40-66aa-4a42-8df9-b9fb633ba306","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.2.1","title":"Spark Savings ETH Risk Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4462,"content":"The Risk parameters are:\n\n- Supply cap: 250,000 WETH\n- Max yield: 5%\n- Current yield (at launch): 0%","contentHash":"8829163f37681733527c878891048ee6636e6d06adb15935df60e23132552279","addressRefs":[]},"e4e8eee4-c449-4adc-aae7-d7fa31f311e0":{"id":"e4e8eee4-c449-4adc-aae7-d7fa31f311e0","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.2.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4463,"content":"The current `maxAmount` for this conduit's take and transferAssets operations are defined in the subdocuments herein.","contentHash":"75b012e8bb8cfbabc557256dba223839a78a10ee18e841934ddae9f2475ba379","addressRefs":[]},"d516e83f-017b-45ac-88bc-67c4a8eb3e57":{"id":"d516e83f-017b-45ac-88bc-67c4a8eb3e57","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.2.3","title":"Take Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4464,"content":"The take rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"3426645201c930f3f055f6f9698d8cbca5aafe9562546059014160a4eef8e177","addressRefs":[]},"85e39357-e537-4175-be32-a6753f27d5f2":{"id":"85e39357-e537-4175-be32-a6753f27d5f2","doc_no":"A.6.1.1.1.2.6.1.3.1.9.1.4.2.4","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4465,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"80a6f78822ec8b4de950e3d80005c47c2c7cdf94a6e9e18f343796d2d9f596a5","addressRefs":[]},"eeb34a6e-e377-4115-92f9-d299f6d2a5d9":{"id":"eeb34a6e-e377-4115-92f9-d299f6d2a5d9","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2","title":"Ethereum Mainnet - Spark Savings v2 USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4466,"content":"The documents herein contain the Instance Configuration Document for the Spark Savings v2 USDC Instance.","contentHash":"1f50d1c544708b0b1ae82c8cc72471a857f0919ef86431f59c6362204247be5e","addressRefs":[]},"6852af1c-6e3c-4599-9f76-3b1587ec7c53":{"id":"6852af1c-6e3c-4599-9f76-3b1587ec7c53","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4467,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"14fe988d-d2a9-4c95-b0d3-63fe58ab40d5":{"id":"14fe988d-d2a9-4c95-b0d3-63fe58ab40d5","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4468,"content":"The documents herein define the parameters of the Spark Savings v2 ETH Instance of the Allocation System Primitive.","contentHash":"822805f853ab2ee994a3f6e819c0889194ee608be36c94d146ca6e1e89ef8d4a","addressRefs":[]},"a4a68c40-17d3-4a60-ac15-c2bfe0fa7a3e":{"id":"a4a68c40-17d3-4a60-ac15-c2bfe0fa7a3e","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4469,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"53035cdc-866c-4901-9744-74a92b537f75":{"id":"53035cdc-866c-4901-9744-74a92b537f75","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4470,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"e7fd4b6e-94a8-4078-ab32-4a4c719d033c":{"id":"e7fd4b6e-94a8-4078-ab32-4a4c719d033c","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4471,"content":"Spark Savings Protocol","contentHash":"ddf2cdda69c7d7d4d4ccba4cd3dd7f3deb1cca801180b93f57a14ca43a802f16","addressRefs":[]},"b67d52f5-8242-402a-8f22-b13ecd3874f6":{"id":"b67d52f5-8242-402a-8f22-b13ecd3874f6","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.1.3","title":"Asset Supplied By Users","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4472,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"6131b29c-52b3-492a-8197-0af376bb60bb":{"id":"6131b29c-52b3-492a-8197-0af376bb60bb","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4473,"content":"spUSDC","contentHash":"a61b2e3fb9c87e9d690350f9c017c4828dceaccb7d7f2c7e156a5139615620b3","addressRefs":[]},"d75699b9-f1d0-4da7-ba6b-23f244047072":{"id":"d75699b9-f1d0-4da7-ba6b-23f244047072","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4474,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"60e2171d-0b25-405c-9ca5-627e8049b8b1":{"id":"60e2171d-0b25-405c-9ca5-627e8049b8b1","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4475,"content":"`0x28B3a8fb53B741A8Fd78c0fb9A6B2393d896a43d`","contentHash":"20054e939006558c3e8dbbacda78e7884a9ef21d8dcd8d53dfedc749921f9093","addressRefs":["0x28b3a8fb53b741a8fd78c0fb9a6b2393d896a43d"]},"4065d210-a9ee-4d96-83f0-c4ff4ac09a07":{"id":"4065d210-a9ee-4d96-83f0-c4ff4ac09a07","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4476,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"fa5d229a-040c-447f-bd53-24ef6c5e735c":{"id":"fa5d229a-040c-447f-bd53-24ef6c5e735c","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4477,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"fef37e25ee6ae99b46a1e7920573dc23171ba7812ee156dde99b1069994255d3","addressRefs":[]},"d6d28ef9-cafd-434c-a106-8dfae2ff8908":{"id":"d6d28ef9-cafd-434c-a106-8dfae2ff8908","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4478,"content":"The specific `maxAmount` and `slope` for this conduit's inflow/outflow are not defined for this Instance.","contentHash":"7a7beff7b4c6ecb868851425e1b215b313106005b011131a0944d74e97d2d9fe","addressRefs":[]},"c4b21848-5450-4e0a-adac-dd97b4bd562b":{"id":"c4b21848-5450-4e0a-adac-dd97b4bd562b","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4479,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"5a7fa3ce-f71c-4c57-85f3-c3450881bd56":{"id":"5a7fa3ce-f71c-4c57-85f3-c3450881bd56","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4480,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"7ea9a810-7278-46c9-9adb-ad4d48c393f0":{"id":"7ea9a810-7278-46c9-9adb-ad4d48c393f0","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4481,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"fbff1bf2-67ae-48e4-9724-4126b24b5b24":{"id":"fbff1bf2-67ae-48e4-9724-4126b24b5b24","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.1","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4482,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"b7396d52-e3b6-4d56-a95f-9f4c8309d954":{"id":"b7396d52-e3b6-4d56-a95f-9f4c8309d954","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.1.1","title":"Spark Vault v2 Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4483,"content":"`0x1b992302652A92611DCd5090D1Cb388C6377f455`","contentHash":"13f481f26993d63a2d75a60223dc2a489f77b2a5adba1b55b59d27bba1a9bb66","addressRefs":["0x1b992302652a92611dcd5090d1cb388c6377f455"]},"5d658c45-cd8f-4598-b535-648a3a621526":{"id":"5d658c45-cd8f-4598-b535-648a3a621526","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.1.2","title":"Default admin","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4484,"content":"`0x3300f198988e4C9C63F75dF86De36421f06af8c4`","contentHash":"f428ffd85508f6ee93b14672cd7accb8ba8646f143a12d81dd70641788fb9bc0","addressRefs":["0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"ca64abf7-8cd3-4368-8c83-bca52968008d":{"id":"ca64abf7-8cd3-4368-8c83-bca52968008d","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.1.3","title":"Setter","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4485,"content":"`0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC`","contentHash":"a4be1caa48d1c4c87ad16384d3686b46723fadc9e7ac5bd267c2413470eeb82f","addressRefs":["0x2e1b01adabb8d4981863394bea23a1263cbaedfc"]},"35c9a6ce-92f8-4a3a-a95a-0e2513360afd":{"id":"35c9a6ce-92f8-4a3a-a95a-0e2513360afd","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.1.4","title":"Taker","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4486,"content":"`0x1601843c5E9bC251A3272907010AFa41Fa18347E`","contentHash":"aeed6d422ed874d65c9f2940a43b9369ddf73673dbeaa1f279263595d843dd3a","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e"]},"135300b0-5b11-4d6f-8b26-9aef99f5fb39":{"id":"135300b0-5b11-4d6f-8b26-9aef99f5fb39","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.2","title":"Risk Parameters Current Configuration","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4487,"content":"The subdocuments herein define the current configuration of the risk parameters.","contentHash":"ae95706409030fd9a4186329c0ae2d52597b2b1e0c27b553b62ee8b3d7690a86","addressRefs":[]},"2470f2c9-e160-40d8-8d9e-69b09bd8ee39":{"id":"2470f2c9-e160-40d8-8d9e-69b09bd8ee39","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.2.1","title":"Spark Savings USDC Risk Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4488,"content":"The Risk parameters are:\n\n- Supply cap: 1,000,000,000 USDC\n- Max yield: 10%\n- Current yield (at launch): 0%","contentHash":"d4e5cc19787d3597c6ec80854ff8087feb8a6f01803df8e070b171b0233e5344","addressRefs":[]},"9ea0e72b-2fc7-4291-b589-3414cdb7baac":{"id":"9ea0e72b-2fc7-4291-b589-3414cdb7baac","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.2.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4489,"content":"The current `maxAmount` for this conduit's take and transferAssets operations are defined in the subdocuments herein.","contentHash":"75b012e8bb8cfbabc557256dba223839a78a10ee18e841934ddae9f2475ba379","addressRefs":[]},"4b64fc4a-b6ef-49d9-b212-8894526b680d":{"id":"4b64fc4a-b6ef-49d9-b212-8894526b680d","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.2.3","title":"Take Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4490,"content":"The take rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"3426645201c930f3f055f6f9698d8cbca5aafe9562546059014160a4eef8e177","addressRefs":[]},"a3af1ab3-c7a5-4f27-90db-0c01ac73f39e":{"id":"a3af1ab3-c7a5-4f27-90db-0c01ac73f39e","doc_no":"A.6.1.1.1.2.6.1.3.1.9.2.4.2.4","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4491,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"80a6f78822ec8b4de950e3d80005c47c2c7cdf94a6e9e18f343796d2d9f596a5","addressRefs":[]},"0cc91e92-4523-4d3b-87a5-bb9a695d696c":{"id":"0cc91e92-4523-4d3b-87a5-bb9a695d696c","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3","title":"Ethereum Mainnet - Spark Savings v2 USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4492,"content":"The documents herein contain the Instance Configuration Document for the Spark Savings v2 USDT Instance.","contentHash":"a972fb7599f637507a5b9658cc55cc2eb2b42326911faa0619838033d4fb8f18","addressRefs":[]},"ff0f290d-12eb-4c72-ae60-a5097c6dd671":{"id":"ff0f290d-12eb-4c72-ae60-a5097c6dd671","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4493,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"f3eae5f3-db85-4f92-9fca-46c13af64d99":{"id":"f3eae5f3-db85-4f92-9fca-46c13af64d99","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4494,"content":"The documents herein define the parameters of the Spark Savings v2 USDT Instance of the Allocation System Primitive.","contentHash":"e0e737a06790c04eeaa3e0a0b10f696c5112f58e9a8099a30b53d1f3ed72667e","addressRefs":[]},"90db3809-ee39-43de-9a3a-07c9c3be77cc":{"id":"90db3809-ee39-43de-9a3a-07c9c3be77cc","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4495,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"5f4150e0-c263-49b9-802f-acbc93f9e5d7":{"id":"5f4150e0-c263-49b9-802f-acbc93f9e5d7","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4496,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"83932398-c228-4d62-b3b0-0b0a96c82fe9":{"id":"83932398-c228-4d62-b3b0-0b0a96c82fe9","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4497,"content":"Spark Savings Protocol","contentHash":"ddf2cdda69c7d7d4d4ccba4cd3dd7f3deb1cca801180b93f57a14ca43a802f16","addressRefs":[]},"10229012-9591-4ac2-a82f-744ffb2a38d0":{"id":"10229012-9591-4ac2-a82f-744ffb2a38d0","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.1.3","title":"Asset Supplied By Users","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4498,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"9bf00b29-a6e5-4850-9247-a46b9ee47f2b":{"id":"9bf00b29-a6e5-4850-9247-a46b9ee47f2b","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4499,"content":"spUSDT","contentHash":"4a7b4af932f648d799dc87c5bbab407da15e1e1cfaa0ce5946b7dc55a529fc74","addressRefs":[]},"f8105d2e-11cc-4f40-a2c2-0c919ae89422":{"id":"f8105d2e-11cc-4f40-a2c2-0c919ae89422","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4500,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"224538f9-fde7-43f3-aa9b-1c3cf6036663":{"id":"224538f9-fde7-43f3-aa9b-1c3cf6036663","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4501,"content":"`0xe2e7a17dFf93280dec073C995595155283e3C372`","contentHash":"e9f742f8ea7016b767a469b249ee0e1286b4a63bc1e294b857e52851167f3e03","addressRefs":["0xe2e7a17dff93280dec073c995595155283e3c372"]},"2959cf7c-9026-45d9-83d4-2ef755613d33":{"id":"2959cf7c-9026-45d9-83d4-2ef755613d33","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4502,"content":"`0xdAC17F958D2ee523a2206206994597C13D831ec7`","contentHash":"d674f514fb5256107f891afe7b796353b6535b08717e30bc071e1ccdf11a1fbf","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"d031b87f-ee09-4019-a7d8-1dcc6c698622":{"id":"d031b87f-ee09-4019-a7d8-1dcc6c698622","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4503,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"fef37e25ee6ae99b46a1e7920573dc23171ba7812ee156dde99b1069994255d3","addressRefs":[]},"ab480592-3e9b-4bdb-9e8d-80e4370a964e":{"id":"ab480592-3e9b-4bdb-9e8d-80e4370a964e","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4504,"content":"The specific `maxAmount` and `slope` for this conduit's inflow/outflow are not defined for this Instance.","contentHash":"7a7beff7b4c6ecb868851425e1b215b313106005b011131a0944d74e97d2d9fe","addressRefs":[]},"5059455b-0fc8-4ab7-b9c2-78cfd9ab253f":{"id":"5059455b-0fc8-4ab7-b9c2-78cfd9ab253f","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4505,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"0ae91e4f-3189-4aba-858f-eff906496b9b":{"id":"0ae91e4f-3189-4aba-858f-eff906496b9b","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4506,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"248a7063-2c28-4077-99af-d2db125d6c02":{"id":"248a7063-2c28-4077-99af-d2db125d6c02","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4507,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"1978c0cd-a433-4232-ab94-438ba1fbd511":{"id":"1978c0cd-a433-4232-ab94-438ba1fbd511","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.1","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4508,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"730c2ba9-d2d3-438c-881b-a36d7c698c2e":{"id":"730c2ba9-d2d3-438c-881b-a36d7c698c2e","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.1.1","title":"Spark Vault v2 Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4509,"content":"`0x1b992302652A92611DCd5090D1Cb388C6377f455`","contentHash":"13f481f26993d63a2d75a60223dc2a489f77b2a5adba1b55b59d27bba1a9bb66","addressRefs":["0x1b992302652a92611dcd5090d1cb388c6377f455"]},"a84b734e-7bcf-4a29-8173-bf2388756074":{"id":"a84b734e-7bcf-4a29-8173-bf2388756074","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.1.2","title":"Default admin","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4510,"content":"`0x3300f198988e4C9C63F75dF86De36421f06af8c4`","contentHash":"f428ffd85508f6ee93b14672cd7accb8ba8646f143a12d81dd70641788fb9bc0","addressRefs":["0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"dfda6276-2747-4135-996a-d516eb734855":{"id":"dfda6276-2747-4135-996a-d516eb734855","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.1.3","title":"Setter","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4511,"content":"`0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC`","contentHash":"a4be1caa48d1c4c87ad16384d3686b46723fadc9e7ac5bd267c2413470eeb82f","addressRefs":["0x2e1b01adabb8d4981863394bea23a1263cbaedfc"]},"5fdbbda4-844e-4280-bacd-0cad16dbf3de":{"id":"5fdbbda4-844e-4280-bacd-0cad16dbf3de","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.1.4","title":"Taker","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4512,"content":"`0x1601843c5E9bC251A3272907010AFa41Fa18347E`","contentHash":"aeed6d422ed874d65c9f2940a43b9369ddf73673dbeaa1f279263595d843dd3a","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e"]},"64c424db-af06-4910-b9f4-df2560236a99":{"id":"64c424db-af06-4910-b9f4-df2560236a99","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.2","title":"Risk Parameters Current Configuration","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4513,"content":"The subdocuments herein define the current configuration of the risk parameters.","contentHash":"ae95706409030fd9a4186329c0ae2d52597b2b1e0c27b553b62ee8b3d7690a86","addressRefs":[]},"473796c1-c41f-4924-80f6-468f966fa064":{"id":"473796c1-c41f-4924-80f6-468f966fa064","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.2.1","title":"Spark Savings USDT Risk Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4514,"content":"The Risk parameters are:\n\n- Supply cap: 2,000,000,000 USDT\n- Max yield: 10%\n- Current yield (at launch): 0%","contentHash":"642d5f4d8decfbefd88351afeab752cf06114829fa7ca0241abcb1d10200126f","addressRefs":[]},"3802d641-27cf-4ec1-bba4-6a09a84071af":{"id":"3802d641-27cf-4ec1-bba4-6a09a84071af","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.2.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4515,"content":"The current `maxAmount` for this conduit's take and transferAssets operations are defined in the subdocuments herein.","contentHash":"75b012e8bb8cfbabc557256dba223839a78a10ee18e841934ddae9f2475ba379","addressRefs":[]},"fc186f71-dce3-46d8-bf50-fcccdfad5e5d":{"id":"fc186f71-dce3-46d8-bf50-fcccdfad5e5d","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.2.3","title":"Take Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4516,"content":"The take rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"3426645201c930f3f055f6f9698d8cbca5aafe9562546059014160a4eef8e177","addressRefs":[]},"9c92bc84-cfdf-4356-8fc4-4df33937ec89":{"id":"9c92bc84-cfdf-4356-8fc4-4df33937ec89","doc_no":"A.6.1.1.1.2.6.1.3.1.9.3.4.2.4","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4517,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"80a6f78822ec8b4de950e3d80005c47c2c7cdf94a6e9e18f343796d2d9f596a5","addressRefs":[]},"0b280652-ea99-4a53-8c9e-fb23b200d446":{"id":"0b280652-ea99-4a53-8c9e-fb23b200d446","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4","title":"Ethereum Mainnet - Spark Savings v2 spPYUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4518,"content":"The documents herein contain the Instance Configuration Document for the Spark Savings v2 spPYUSD Instance.","contentHash":"244056ec77ddfea994b588d09961e8c7d4ab5b394a11cd69ee2288e587f7ea9b","addressRefs":[]},"bc708dab-227b-4512-9c0d-d6205b5db840":{"id":"bc708dab-227b-4512-9c0d-d6205b5db840","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4519,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"93f2f53e-1907-4828-b1a6-dbd0838e17ff":{"id":"93f2f53e-1907-4828-b1a6-dbd0838e17ff","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4520,"content":"The documents herein define the parameters of the Spark Savings v2 spPYUSD Instance of the Allocation System Primitive.","contentHash":"b8243506733b45dec091da2daec9259c75d37745bac7eb0eb98385c6cc5b61f4","addressRefs":[]},"d8f4f071-4dd2-4b24-b3fb-da99dc7e05c8":{"id":"d8f4f071-4dd2-4b24-b3fb-da99dc7e05c8","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4521,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"5df33a54-f040-4784-b3de-1eef0a6aa58a":{"id":"5df33a54-f040-4784-b3de-1eef0a6aa58a","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4522,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"4030df21-d528-4d68-a08a-861344b8db1c":{"id":"4030df21-d528-4d68-a08a-861344b8db1c","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4523,"content":"Spark Savings Protocol","contentHash":"ddf2cdda69c7d7d4d4ccba4cd3dd7f3deb1cca801180b93f57a14ca43a802f16","addressRefs":[]},"40afdb41-a6e3-4e33-b01c-c145aa234170":{"id":"40afdb41-a6e3-4e33-b01c-c145aa234170","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.1.3","title":"Asset Supplied By Users","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4524,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"bf8871b0-7a57-470c-8ac5-82f104220289":{"id":"bf8871b0-7a57-470c-8ac5-82f104220289","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4525,"content":"spPYUSD","contentHash":"ddbfa2102cca40c30d4ee5082fba538edfedbe747906ed0b0025913db83b967c","addressRefs":[]},"edc37448-90df-45c7-a0d8-f7aef9ff85a6":{"id":"edc37448-90df-45c7-a0d8-f7aef9ff85a6","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4526,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"32e9ffdc-e437-46cb-a2fc-272fb3e826a7":{"id":"32e9ffdc-e437-46cb-a2fc-272fb3e826a7","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4527,"content":"`0x80128DbB9f07b93DDE62A6daeadb69ED14a7D354`","contentHash":"c611c1e92ca0becdb31e51f42aecab2c9b1b89400d666a7aff5ff52e738cfd97","addressRefs":["0x80128dbb9f07b93dde62a6daeadb69ed14a7d354"]},"e3bf5dca-f865-45b0-87dd-1bb67b9b52af":{"id":"e3bf5dca-f865-45b0-87dd-1bb67b9b52af","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4528,"content":"`0x6c3ea9036406852006290770bedfcaba0e23a0e8`","contentHash":"ac7df8bf48b402a36c798cb7de5c858852ed1af979012ea4f6bc810a3a0dde38","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"2f06d1e8-bcc6-4ac2-92af-3006f1abaa02":{"id":"2f06d1e8-bcc6-4ac2-92af-3006f1abaa02","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4529,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"fef37e25ee6ae99b46a1e7920573dc23171ba7812ee156dde99b1069994255d3","addressRefs":[]},"8d9562b5-4277-4c63-96a2-923a36afb192":{"id":"8d9562b5-4277-4c63-96a2-923a36afb192","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4530,"content":"The specific `maxAmount` and `slope` for this conduit's inflow/outflow are not defined for this Instance.","contentHash":"7a7beff7b4c6ecb868851425e1b215b313106005b011131a0944d74e97d2d9fe","addressRefs":[]},"02970ea9-7538-4d59-b6fe-28220cfb61e2":{"id":"02970ea9-7538-4d59-b6fe-28220cfb61e2","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4531,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"14ccaa13-1c17-4161-bf53-005dcc75bfd9":{"id":"14ccaa13-1c17-4161-bf53-005dcc75bfd9","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4532,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"f1f811e3-5489-45ca-a293-495eff825381":{"id":"f1f811e3-5489-45ca-a293-495eff825381","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4533,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"cd1a9cac-7b69-45af-85ac-bbf39e0b7f12":{"id":"cd1a9cac-7b69-45af-85ac-bbf39e0b7f12","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.1","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4534,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"3ebbf669-af67-4b15-880e-4a5b5c74dce1":{"id":"3ebbf669-af67-4b15-880e-4a5b5c74dce1","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.1.1","title":"Spark Vault v2 Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4535,"content":"`0x1b992302652A92611DCd5090D1Cb388C6377f455`","contentHash":"13f481f26993d63a2d75a60223dc2a489f77b2a5adba1b55b59d27bba1a9bb66","addressRefs":["0x1b992302652a92611dcd5090d1cb388c6377f455"]},"f13af98a-f12f-48b6-8827-ba942ccacbcf":{"id":"f13af98a-f12f-48b6-8827-ba942ccacbcf","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.1.2","title":"Default admin","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4536,"content":"`0x3300f198988e4C9C63F75dF86De36421f06af8c4`","contentHash":"f428ffd85508f6ee93b14672cd7accb8ba8646f143a12d81dd70641788fb9bc0","addressRefs":["0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"2ece6e1d-b07a-4df5-9aa6-616756f64815":{"id":"2ece6e1d-b07a-4df5-9aa6-616756f64815","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.1.3","title":"Setter","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4537,"content":"`0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178`","contentHash":"0753c6929ebb76a77ed56ac1ffa3696c8c73a192969cdcbd25379332f8be1044","addressRefs":["0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"32dc1afe-59e0-472d-8f09-c2a923adb6bb":{"id":"32dc1afe-59e0-472d-8f09-c2a923adb6bb","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.1.4","title":"Taker","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4538,"content":"`0x1601843c5E9bC251A3272907010AFa41Fa18347E`","contentHash":"aeed6d422ed874d65c9f2940a43b9369ddf73673dbeaa1f279263595d843dd3a","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e"]},"5d4ed5ae-8141-43da-a20a-42238170e1a3":{"id":"5d4ed5ae-8141-43da-a20a-42238170e1a3","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.2","title":"Risk Parameters Current Configuration","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4539,"content":"The subdocuments herein define the current configuration of the risk parameters.","contentHash":"ae95706409030fd9a4186329c0ae2d52597b2b1e0c27b553b62ee8b3d7690a86","addressRefs":[]},"48e7ec46-a69b-41cc-ab24-eb9c05324a07":{"id":"48e7ec46-a69b-41cc-ab24-eb9c05324a07","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.2.1","title":"Spark Savings spPYUSD Risk Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4540,"content":"The Risk parameters are:\n\n- Supply cap: 250,000,000 PYUSD\n- Max yield: 10%\n- Current yield (at launch): 0%","contentHash":"0536d3dca99494849e9876520e5976f213affdf93f153df31ef17630eed82db8","addressRefs":[]},"8a75c7ba-4d34-4e0e-8f6e-25e765fcbe36":{"id":"8a75c7ba-4d34-4e0e-8f6e-25e765fcbe36","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.2.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4541,"content":"The current `maxAmount` for this conduit's take and transferAssets operations are defined in the subdocuments herein.","contentHash":"75b012e8bb8cfbabc557256dba223839a78a10ee18e841934ddae9f2475ba379","addressRefs":[]},"6343b9eb-fa3e-4ca6-8f98-90c08d400c0f":{"id":"6343b9eb-fa3e-4ca6-8f98-90c08d400c0f","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.2.3","title":"Take Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4542,"content":"The take rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"3426645201c930f3f055f6f9698d8cbca5aafe9562546059014160a4eef8e177","addressRefs":[]},"f291a712-4c0c-4ef4-8d2f-0b558fb9cbbe":{"id":"f291a712-4c0c-4ef4-8d2f-0b558fb9cbbe","doc_no":"A.6.1.1.1.2.6.1.3.1.9.4.4.2.4","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4543,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"80a6f78822ec8b4de950e3d80005c47c2c7cdf94a6e9e18f343796d2d9f596a5","addressRefs":[]},"61ad54f3-9faa-4a9a-9cee-e685fb8fc4cf":{"id":"61ad54f3-9faa-4a9a-9cee-e685fb8fc4cf","doc_no":"A.6.1.1.1.2.6.1.3.1.10","title":"Arkis","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4544,"content":"The Ethereum Mainnet Instances of the Arkis Protocol with `Active` Status are stored herein.","contentHash":"bd53c71ef2bbb8c43fd798cdf72c73db9957c7bfeaf960ae6bffb9b3e8a3b225","addressRefs":[]},"4bb58af1-fc25-442f-83a9-dd40989a7d37":{"id":"4bb58af1-fc25-442f-83a9-dd40989a7d37","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1","title":"Ethereum Mainnet - Arkis Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4545,"content":"The documents herein contain the Instance Configuration Document for the Arkis Instance.","contentHash":"e6e6ed3b5c7786cdcde14832ac56ce634dc998018d6eed5682bbd5a56517e45b","addressRefs":[]},"4ec36447-71fa-4a0f-865a-1353740b663d":{"id":"4ec36447-71fa-4a0f-865a-1353740b663d","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4546,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"e1921ad5-ff6f-4ffe-9e69-1d1796567296":{"id":"e1921ad5-ff6f-4ffe-9e69-1d1796567296","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4547,"content":"The documents herein define the parameters of the Arkis Instance of the Allocation System Primitive.","contentHash":"704b8ac6779202ec8568d533c32e3c5f1f41d51d3b31e2d6cd8f4335f4811af9","addressRefs":[]},"4aafd731-9770-4f4c-925a-7f54fcca8327":{"id":"4aafd731-9770-4f4c-925a-7f54fcca8327","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4548,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"cc527da6-8dce-4165-a1ea-22075da1b3e2":{"id":"cc527da6-8dce-4165-a1ea-22075da1b3e2","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4549,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"092f9755-377e-4d34-9abc-7b7293cf5f64":{"id":"092f9755-377e-4d34-9abc-7b7293cf5f64","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4550,"content":"Arkis","contentHash":"7247f96b39c8fb7116be3a3b50d74a8a74c0913f815ea3ef47d1fcab7ffb2de0","addressRefs":[]},"521360e7-dccc-4066-a69c-ea2a2c6a2306":{"id":"521360e7-dccc-4066-a69c-ea2a2c6a2306","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4551,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"d148fb40-413f-4ef7-a852-e26f613c8cd0":{"id":"d148fb40-413f-4ef7-a852-e26f613c8cd0","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4552,"content":"spUSDC","contentHash":"a61b2e3fb9c87e9d690350f9c017c4828dceaccb7d7f2c7e156a5139615620b3","addressRefs":[]},"39ee8922-db8a-47d7-a4ac-f183e1314975":{"id":"39ee8922-db8a-47d7-a4ac-f183e1314975","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4553,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"befde66f-e9f7-4f70-b107-ded60431052f":{"id":"befde66f-e9f7-4f70-b107-ded60431052f","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4554,"content":"`0x377C3bd93f2a2984E1E7bE6A5C22c525eD4A4815`","contentHash":"dd1a784dfbf0f8596ece47ac9ff6a4752c1e5d97a1ce73b0add1dcc32b1e78ae","addressRefs":["0x377c3bd93f2a2984e1e7be6a5c22c525ed4a4815"]},"fa448799-af8f-494d-9db8-5361ea02b576":{"id":"fa448799-af8f-494d-9db8-5361ea02b576","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4555,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"8efbce12-9417-4ab7-9e55-6194ee592bd4":{"id":"8efbce12-9417-4ab7-9e55-6194ee592bd4","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4556,"content":"The pool address will be specified in a future iteration of the Spark Artifact.","contentHash":"58cab11aeeefec482d399233c807dd3479996d98c6311426a56e02dc640886ed","addressRefs":[]},"541b2c98-6c5d-4e8d-9aef-30d3b15bd6bc":{"id":"541b2c98-6c5d-4e8d-9aef-30d3b15bd6bc","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4557,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"fde9903c-91a1-40f8-bc4a-a6511bb346aa":{"id":"fde9903c-91a1-40f8-bc4a-a6511bb346aa","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4558,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"ce2b927e-3338-4101-a538-ca1a02ae917c":{"id":"ce2b927e-3338-4101-a538-ca1a02ae917c","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4559,"content":"The inflow rate limits are:\n\n- `maxAmount`: 5,000,000 USDC\n- `slope`: 5,000,000 USDC per day","contentHash":"7a2a1083c70fed0cd1f483e2fa28e080c91bac8415938a5f1f7c3fc38a58df59","addressRefs":[]},"61f4c11f-73d0-49f2-ba54-abf214c60881":{"id":"61f4c11f-73d0-49f2-ba54-abf214c60881","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4560,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"389d1003-434b-4acb-a0db-7a587a5ee006":{"id":"389d1003-434b-4acb-a0db-7a587a5ee006","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4561,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"baf1fbad-0ef7-424e-832f-bd0c47377144":{"id":"baf1fbad-0ef7-424e-832f-bd0c47377144","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.5.1","title":"Maximum Exposure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4562,"content":"The Maximum Exposure for this Instance is $50 million.","contentHash":"c31a3b89e4edd7f52e0aa25a7de32cc332785eaaf6ce5893fb1fb776222cd031","addressRefs":[]},"c9cc845b-9971-4ee5-a5ec-e3d2771d85e2":{"id":"c9cc845b-9971-4ee5-a5ec-e3d2771d85e2","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.2.5.2","title":"Instance Capital Requirement Ratio","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4563,"content":"The Instance Capital Requirement Ratio for this Instance is 50%.","contentHash":"e6d80e0b64d4a3ca37a8caf1b893fcd0245e058829fd426b3960851f12a866a8","addressRefs":[]},"0a1caa15-48bb-4047-bf18-76f65ba20410":{"id":"0a1caa15-48bb-4047-bf18-76f65ba20410","doc_no":"A.6.1.1.1.2.6.1.3.1.10.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4564,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"6c5c956c-608f-40aa-9911-d1c04df4f99e":{"id":"6c5c956c-608f-40aa-9911-d1c04df4f99e","doc_no":"A.6.1.1.1.2.6.1.3.1.11","title":"Uniswap v4","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4565,"content":"The Ethereum Mainnet Instances of the Uniswap v4 Protocol with `Active` Status are stored herein.","contentHash":"1eddc2b1ff3eaa16d8caba10d9050193363655204d76b8edf163048d949db5da","addressRefs":[]},"c5d16727-69f7-454a-a3da-85c46dd9eed2":{"id":"c5d16727-69f7-454a-a3da-85c46dd9eed2","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1","title":"Ethereum Mainnet - Uniswap v4 PYUSD/USDS Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4566,"content":"The documents herein contain the Instance Configuration Document for the Uniswap v4 PYUSD/USDS Pool Instance.","contentHash":"80fafc5f9cdf40757a47f3fab56669f2a2372492005427f002aff5c02e01cb47","addressRefs":[]},"bd5042f9-cd5d-4574-b868-d0b9ad247a3a":{"id":"bd5042f9-cd5d-4574-b868-d0b9ad247a3a","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4567,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"4139b0ae-87f7-4b3f-aa48-78ee8efc1047":{"id":"4139b0ae-87f7-4b3f-aa48-78ee8efc1047","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4568,"content":"The documents herein define the parameters of the Uniswap v4 PYUSD/USDS Pool Instance of the Allocation System Primitive.","contentHash":"21da3e0914ddbcd7cac5c36913f184115bcd077e885dfe5aa9ba96f77942ab31","addressRefs":[]},"7efb34f5-5007-4ab4-93e7-e00e616df5b3":{"id":"7efb34f5-5007-4ab4-93e7-e00e616df5b3","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4569,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"94de254f-7f5e-4e40-a683-26935e3503ed":{"id":"94de254f-7f5e-4e40-a683-26935e3503ed","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4570,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"61fb4454-3c58-4757-b796-cc9890685e71":{"id":"61fb4454-3c58-4757-b796-cc9890685e71","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4571,"content":"Uniswap v4","contentHash":"9cd085da8ba3f6519d54035c6d91157c898e25315daacec374327ace360831e2","addressRefs":[]},"967a9605-4d90-46a7-a4bd-1ebcd7192b70":{"id":"967a9605-4d90-46a7-a4bd-1ebcd7192b70","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4572,"content":"USDS and PYUSD","contentHash":"f15567c598355c9ed73c77fe5250a756a1eb38c9388b8497a2ed7fa8a42d0d09","addressRefs":[]},"4d4123a0-312b-4351-aecc-28e56b1de290":{"id":"4d4123a0-312b-4351-aecc-28e56b1de290","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4573,"content":"PYUSDUSDS","contentHash":"711bc5ee10bd22d6671560a2e4bba7d877de0495689322b148ef59ec9b89b67a","addressRefs":[]},"fda1c342-7d97-4674-a383-d32544990ae9":{"id":"fda1c342-7d97-4674-a383-d32544990ae9","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4574,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"df34137f-2994-48fb-ba1d-1c533b1fc305":{"id":"df34137f-2994-48fb-ba1d-1c533b1fc305","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4575,"content":"`0xa632d59b9b804a956bfaa9b48af3a1b74808fc1f`","contentHash":"fbcc9aa84b6ec11a9b1d2e70498fb223dffcd81441621a2b5c63d8d618ca61e5","addressRefs":["0xa632d59b9b804a956bfaa9b48af3a1b74808fc1f"]},"1ec43acc-0aba-4e5e-96f9-cb6c4143c7f3":{"id":"1ec43acc-0aba-4e5e-96f9-cb6c4143c7f3","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.2.2","title":"Pool ID","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4576,"content":"`0xe63e32b2ae40601662f760d6bf5d771057324fbd97784fe1d3717069f7b75d45`","contentHash":"d818d2e9025a8e5cdf6a563160c6391cc3f3751f108a7447644fd8dca8f6afb9","addressRefs":[]},"7b94ebfe-42c9-4319-80ff-d57258f5773c":{"id":"7b94ebfe-42c9-4319-80ff-d57258f5773c","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4577,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"689f87d9-e66b-4eab-b984-9ad21ed4bb59":{"id":"689f87d9-e66b-4eab-b984-9ad21ed4bb59","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4578,"content":"The current `maxAmount,` `slope`, slippage, ticks, and fee for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"af03402ce646af2e0b91e5d24354dc92da9a7180a4cdf45f697ad113872ac145","addressRefs":[]},"02ca893e-879e-47fa-a2f1-ca783ccf2106":{"id":"02ca893e-879e-47fa-a2f1-ca783ccf2106","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4579,"content":"The inflow rate limits are:\n\n- `maxAmount`: 10,000,000\n- `slope`: 100,000,000 per day","contentHash":"08d1ef49bf4184a9a50f76de8b4d1fd059b1c0232d959cb02e81cf7b6cbb7096","addressRefs":[]},"7b1bcd5c-8af6-46bd-8fb0-cbac22bae80a":{"id":"7b1bcd5c-8af6-46bd-8fb0-cbac22bae80a","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4580,"content":"The outflow rate limits are:\n\n- `maxAmount`: 50,000,000\n- `slope`: 200,000,000 per day","contentHash":"40d569fe10606c3b14390328ea36b8777f5caca12d0f6ab5f1e93df521f63c35","addressRefs":[]},"1a2ba197-1389-4cdd-8e55-ca950ecacdca":{"id":"1a2ba197-1389-4cdd-8e55-ca950ecacdca","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4581,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 50,000,000 per day","contentHash":"495086bb1065c61710ee07915485f6bacb39aebf36af5c1c40eca144bd0a1612","addressRefs":[]},"0318bf34-70a0-42a0-9019-e5a48de96ec6":{"id":"0318bf34-70a0-42a0-9019-e5a48de96ec6","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.4.4","title":"Maximum Slippage","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4582,"content":"Max slippage: 0.1%","contentHash":"b816c2d18024d892aca93b8b6bcf80b103fa8c38d9e26001fe1492e90ed8787b","addressRefs":[]},"9e8e50cc-eb69-43f4-b0d6-dd2f0c4fc01a":{"id":"9e8e50cc-eb69-43f4-b0d6-dd2f0c4fc01a","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.4.5","title":"Tick Range and Width","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4583,"content":"- Min lower tick limit: 276,314 (-0.1%)\n- Max upper tick limit: 276,334 (+0.1%)\n- Max tick width: 10 ticks","contentHash":"98ab799b3ad416164d155368cc6dc25ae13822c126fddf976b935531ff00fd1e","addressRefs":[]},"3c776b0d-7ab4-4949-993e-ce290341654d":{"id":"3c776b0d-7ab4-4949-993e-ce290341654d","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.4.6","title":"Swap Fee","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4584,"content":"0.0005%","contentHash":"3a3241f99b57fcd4e044e125e0b5c948877b7fe6cc953a207d578ccfd19dc3b6","addressRefs":[]},"809b7844-1e15-4e43-bc33-b0af6074a725":{"id":"809b7844-1e15-4e43-bc33-b0af6074a725","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4585,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"c8bfb680-b56f-4cd2-835c-4fdec23be484":{"id":"c8bfb680-b56f-4cd2-835c-4fdec23be484","doc_no":"A.6.1.1.1.2.6.1.3.1.11.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4586,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"3c4cfb29-1579-4abe-a17b-5b5574972b73":{"id":"3c4cfb29-1579-4abe-a17b-5b5574972b73","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2","title":"Ethereum Mainnet - Uniswap v4 USDT/USDS Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4587,"content":"The documents herein contain the Instance Configuration Document for the Uniswap v4 USDT/USDS Pool Instance.","contentHash":"2ad994a115d3f0c637123377d953b9356312e7628d3845510b79be2e0e2aeb65","addressRefs":[]},"686428f2-87e7-4592-8656-60ab5bee3168":{"id":"686428f2-87e7-4592-8656-60ab5bee3168","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4588,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"d46584b0-4ec1-4450-b915-79969d7c3c74":{"id":"d46584b0-4ec1-4450-b915-79969d7c3c74","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4589,"content":"The documents herein define the parameters of the Uniswap v4 USDT/USDS Pool Instance of the Allocation System Primitive.","contentHash":"12e8c388b1a676f7f23d310ecbc2e16dcb3ce8dbca6a40507b9540daf1176f9b","addressRefs":[]},"0845627e-c64a-4e04-8be2-4f5bac7114d2":{"id":"0845627e-c64a-4e04-8be2-4f5bac7114d2","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4590,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"6d1a7aa5-3aab-461b-a0ab-aa68137ffd0d":{"id":"6d1a7aa5-3aab-461b-a0ab-aa68137ffd0d","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4591,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"1fdf2ecf-e70e-4294-91de-1596f991ca2a":{"id":"1fdf2ecf-e70e-4294-91de-1596f991ca2a","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4592,"content":"Uniswap v4","contentHash":"9cd085da8ba3f6519d54035c6d91157c898e25315daacec374327ace360831e2","addressRefs":[]},"13b49366-aaee-4f35-b2cd-e2317bc4b92c":{"id":"13b49366-aaee-4f35-b2cd-e2317bc4b92c","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4593,"content":"USDS and USDT","contentHash":"97335d2e37387ba999022ace0da0fc783655ebeed63d42f3c446efc8a4ec0cc7","addressRefs":[]},"a877ea22-2aae-451e-b0d6-912fdaca1796":{"id":"a877ea22-2aae-451e-b0d6-912fdaca1796","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4594,"content":"USDTUSDS","contentHash":"f4b787df22c2916e4287c93aed966af83c537703ac21df083d66665d0617de24","addressRefs":[]},"164e3bb8-8a61-41b7-9d34-797db864ac87":{"id":"164e3bb8-8a61-41b7-9d34-797db864ac87","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4595,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"c864e1c5-a653-433b-85e5-3bd1037fc7a1":{"id":"c864e1c5-a653-433b-85e5-3bd1037fc7a1","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4596,"content":"`0x00836Fe54625BE242BcFA286207795405ca4fD10`","contentHash":"627ec58ad075cc4ad8e92eb22e6a33d61b6f849e9e4424a6f99f905f4c5e118b","addressRefs":["0x00836fe54625be242bcfa286207795405ca4fd10"]},"6e231bfb-e04f-44e0-9023-7ab98c9b7568":{"id":"6e231bfb-e04f-44e0-9023-7ab98c9b7568","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.2.2","title":"Pool ID","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4597,"content":"`0x3b1b1f2e775a6db1664f8e7d59ad568605ea2406312c11aef03146c0cf89d5b9`","contentHash":"67490ebbb81bdbb5973b12dac0ca39be733434bf868aa974a1c93640963b3cf1","addressRefs":[]},"77850de8-afe7-47e2-aedd-e44de6922c6f":{"id":"77850de8-afe7-47e2-aedd-e44de6922c6f","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4598,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"91ad3746-e58c-43b3-a53d-0430b5e20a4c":{"id":"91ad3746-e58c-43b3-a53d-0430b5e20a4c","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4599,"content":"The current `maxAmount,` `slope`, slippage, ticks, and fee for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"af03402ce646af2e0b91e5d24354dc92da9a7180a4cdf45f697ad113872ac145","addressRefs":[]},"a6105d1a-16d8-4920-808c-780891e2112d":{"id":"a6105d1a-16d8-4920-808c-780891e2112d","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4600,"content":"The inflow rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 50,000,000 per day","contentHash":"193b763760c2d50334928c00497628d48596edd900c043e1dc466b758709e976","addressRefs":[]},"2a7d1855-feb9-4a16-b726-144f52c89dd3":{"id":"2a7d1855-feb9-4a16-b726-144f52c89dd3","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4601,"content":"The outflow rate limits are:\n\n- `maxAmount`: 50,000,000\n- `slope`: 200,000,000 per day","contentHash":"40d569fe10606c3b14390328ea36b8777f5caca12d0f6ab5f1e93df521f63c35","addressRefs":[]},"18355afe-c656-47a5-8867-206263d8cb09":{"id":"18355afe-c656-47a5-8867-206263d8cb09","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4602,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000\n- `slope`: 50,000,000 per day","contentHash":"495086bb1065c61710ee07915485f6bacb39aebf36af5c1c40eca144bd0a1612","addressRefs":[]},"fa48928b-af8a-4455-88ac-43a68631e329":{"id":"fa48928b-af8a-4455-88ac-43a68631e329","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.4.4","title":"Maximum Slippage","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4603,"content":"Max slippage: 0.2%","contentHash":"e0fc4925dde1f3a4320c4420dc8a848c541aa4b923a0eff28bf4af2a27166ead","addressRefs":[]},"e72be948-a47e-4303-b9b2-d1acb07cecd4":{"id":"e72be948-a47e-4303-b9b2-d1acb07cecd4","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.4.5","title":"Tick Range and Width","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4604,"content":"- Min lower tick limit: 276,304 (-0.2%)\n- Max upper tick limit: 276,344 (+0.2%)\n- Max tick width: 10 ticks","contentHash":"14c703b11eabb45843ddbd8c077d6edf5ba3e54426a637d55ce272ded462ba60","addressRefs":[]},"9f92e7b7-83e6-4b0c-9f3d-6ec66a259c98":{"id":"9f92e7b7-83e6-4b0c-9f3d-6ec66a259c98","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.4.6","title":"Swap Fee","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4605,"content":"0.0005%","contentHash":"3a3241f99b57fcd4e044e125e0b5c948877b7fe6cc953a207d578ccfd19dc3b6","addressRefs":[]},"bc14c22c-f7a7-4de9-afe9-4b121d05ee7a":{"id":"bc14c22c-f7a7-4de9-afe9-4b121d05ee7a","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4606,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"afd2544b-24de-439b-8d8f-44d5cd82a8bd":{"id":"afd2544b-24de-439b-8d8f-44d5cd82a8bd","doc_no":"A.6.1.1.1.2.6.1.3.1.11.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4607,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"e01f0c20-5d3d-4ca4-ac9e-0a1e51780b19":{"id":"e01f0c20-5d3d-4ca4-ac9e-0a1e51780b19","doc_no":"A.6.1.1.1.2.6.1.3.1.12","title":"Paxos","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4608,"content":"The Ethereum Mainnet Instances of the Paxos Protocol with `Active` Status are stored herein.","contentHash":"0194b0131d0a617debb172b304f3adb650ce35ac541091031d0a58d129a64afd","addressRefs":[]},"efc57615-b3ac-4122-8fd3-6a8d68ce71a1":{"id":"efc57615-b3ac-4122-8fd3-6a8d68ce71a1","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1","title":"Ethereum Mainnet - Transfer USDC to Paxos (receive PYUSD) Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4609,"content":"The documents herein contain the Instance Configuration Document for the Transfer USDC to Paxos (receive PYUSD) Instance.","contentHash":"e8e4351ed9079e186856e05bf264d5ce9839aa64ee071313fc6dac718ea16e5a","addressRefs":[]},"c9d05c8a-7e78-45f6-8422-64793b739434":{"id":"c9d05c8a-7e78-45f6-8422-64793b739434","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4610,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"99c9d288-1fd2-4608-b38e-085d40c12ce1":{"id":"99c9d288-1fd2-4608-b38e-085d40c12ce1","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4611,"content":"The documents herein define the parameters of the Transfer USDC to Paxos (receive PYUSD) of the Allocation System Primitive.","contentHash":"94c791b8ac5e8603e49a22b3be2110c58d9da8b7189741e4170c8a2fda3c435f","addressRefs":[]},"f8220beb-0c4c-420f-b7d5-9dc7f86ca84b":{"id":"f8220beb-0c4c-420f-b7d5-9dc7f86ca84b","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4612,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"b4acd29e-a541-4cd4-9df0-520ea85633ad":{"id":"b4acd29e-a541-4cd4-9df0-520ea85633ad","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4613,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"32c4f476-cbe3-4871-a63b-5501a17e3a0d":{"id":"32c4f476-cbe3-4871-a63b-5501a17e3a0d","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4614,"content":"Paxos","contentHash":"86067961d19af207fe385a6eb4c94c16ed1e62bd7ea8c61311669ff0ceca788a","addressRefs":[]},"9fe5aafe-b11c-4d00-9e4c-87d7a1903beb":{"id":"9fe5aafe-b11c-4d00-9e4c-87d7a1903beb","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4615,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"eb7e08a0-9fc6-48f8-97c4-eeace222f34c":{"id":"eb7e08a0-9fc6-48f8-97c4-eeace222f34c","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.1.4","title":"Token to Receive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4616,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"48ec53db-6ca2-4cdb-90bd-3860116bc551":{"id":"48ec53db-6ca2-4cdb-90bd-3860116bc551","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4617,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"78ba019c-013f-4352-8208-a273d15fa1e2":{"id":"78ba019c-013f-4352-8208-a273d15fa1e2","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4618,"content":"`0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48`","contentHash":"b4a18d9f7a7aa77246c398b4913811217c6df2d5f30be99fb2b7332cdda085c0","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"78c62b61-6ccc-42d0-9232-6e66c8d8a26f":{"id":"78c62b61-6ccc-42d0-9232-6e66c8d8a26f","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4619,"content":"`0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48`","contentHash":"b4a18d9f7a7aa77246c398b4913811217c6df2d5f30be99fb2b7332cdda085c0","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"c631c210-451e-4149-b375-c9e5105df0d5":{"id":"c631c210-451e-4149-b375-c9e5105df0d5","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.2.3","title":"Paxos Deposit Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4620,"content":"`0xFb1F749024b4544c425f5CAf6641959da31EdF37`","contentHash":"df4062f0ce6e9910fc6f80e196d27dad6fffcf205eff46e2ac0566bbf7bd37f8","addressRefs":["0xfb1f749024b4544c425f5caf6641959da31edf37"]},"3b67cada-07bb-4e5c-b0ab-84ddbe515d19":{"id":"3b67cada-07bb-4e5c-b0ab-84ddbe515d19","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4621,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"bd104480-24d4-4fb1-a8f0-13e5c04a2c18":{"id":"bd104480-24d4-4fb1-a8f0-13e5c04a2c18","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4622,"content":"The current TransferAsset rate limits for this conduit's transferAssets operations are defined in the subdocuments herein.","contentHash":"0257a734df1df778ecc60706444b442241fda35df2b79b9e96dcb12405c1c295","addressRefs":[]},"66f2a388-119c-4908-9ff7-f38190e9566d":{"id":"66f2a388-119c-4908-9ff7-f38190e9566d","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.4.1","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4623,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: 5,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"5cd5aff788c8d150caa4ad23641832f5b0d043b8d74282e65b8e43314d08296a","addressRefs":[]},"51453e8e-19c2-45e1-95e3-88ce99e9c80f":{"id":"51453e8e-19c2-45e1-95e3-88ce99e9c80f","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4624,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"9acd91e4-2705-42d9-a72a-b6e3cd0f6855":{"id":"9acd91e4-2705-42d9-a72a-b6e3cd0f6855","doc_no":"A.6.1.1.1.2.6.1.3.1.12.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4625,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"28544284-0ee1-49da-a27f-b13dba9b5842":{"id":"28544284-0ee1-49da-a27f-b13dba9b5842","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2","title":"Ethereum Mainnet - Transfer PYUSD to Paxos (receive USDC) Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4626,"content":"The documents herein contain the Instance Configuration Document for the Transfer PYUSD to Paxos (receive USDC) Instance.","contentHash":"697edfb1438e3a8f96431e150911177a339a5b22db91d47c48de71cb1146a9a8","addressRefs":[]},"253039f6-e11e-4356-9ee2-bcc87603e23c":{"id":"253039f6-e11e-4356-9ee2-bcc87603e23c","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4627,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"e156bb45-006d-4341-b9a0-d8dd39be06fd":{"id":"e156bb45-006d-4341-b9a0-d8dd39be06fd","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4628,"content":"The documents herein define the parameters of the Transfer PYUSD to Paxos (receive USDC) of the Allocation System Primitive.","contentHash":"5e6def7d3a21e9f8cf4c491ca074d24b5f2cd652cf83659b4c0f32085e0509f1","addressRefs":[]},"435d5c6e-32ed-43ea-8419-9d20cf998aed":{"id":"435d5c6e-32ed-43ea-8419-9d20cf998aed","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4629,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"1b33f32e-7133-478c-a053-bb3aa3d4ec91":{"id":"1b33f32e-7133-478c-a053-bb3aa3d4ec91","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4630,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"f07a80ae-654b-484e-8ccf-d2abd235a1a5":{"id":"f07a80ae-654b-484e-8ccf-d2abd235a1a5","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4631,"content":"Paxos","contentHash":"86067961d19af207fe385a6eb4c94c16ed1e62bd7ea8c61311669ff0ceca788a","addressRefs":[]},"06daf347-26de-45c6-844b-9894c09d16cc":{"id":"06daf347-26de-45c6-844b-9894c09d16cc","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4632,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"933af4c1-32da-4b82-a1db-138e838b3377":{"id":"933af4c1-32da-4b82-a1db-138e838b3377","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.1.4","title":"Token to Receive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4633,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"7cfef7de-2859-48fb-9436-46017ecefc9a":{"id":"7cfef7de-2859-48fb-9436-46017ecefc9a","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4634,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"c95f4d5b-a056-40ef-bf18-c5753c6f7182":{"id":"c95f4d5b-a056-40ef-bf18-c5753c6f7182","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4635,"content":"`0x6c3ea9036406852006290770bedfcaba0e23a0e8`","contentHash":"ac7df8bf48b402a36c798cb7de5c858852ed1af979012ea4f6bc810a3a0dde38","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"29802d42-1ddd-4c89-9e01-167abc1e5df7":{"id":"29802d42-1ddd-4c89-9e01-167abc1e5df7","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4636,"content":"`0x6c3ea9036406852006290770bedfcaba0e23a0e8`","contentHash":"ac7df8bf48b402a36c798cb7de5c858852ed1af979012ea4f6bc810a3a0dde38","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"4377a68b-2bc0-4c7b-96e6-e7d5c6527bd9":{"id":"4377a68b-2bc0-4c7b-96e6-e7d5c6527bd9","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.2.3","title":"Paxos Deposit Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4637,"content":"`0x2f7BE67e11A4D621E36f1A8371b0a5Fe16dE6B20`","contentHash":"ed29014efc91eb3f75c476241a4d9901b1cfb0a3ba7f0b063271712d52462389","addressRefs":["0x2f7be67e11a4d621e36f1a8371b0a5fe16de6b20"]},"cd38213e-84bf-4a72-8f14-9c803c721e19":{"id":"cd38213e-84bf-4a72-8f14-9c803c721e19","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4638,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"ad179de7-3167-476d-ae82-36fb715ec68f":{"id":"ad179de7-3167-476d-ae82-36fb715ec68f","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4639,"content":"The current TransferAsset rate limits for this conduit's transferAssets operations are defined in the subdocuments herein.","contentHash":"0257a734df1df778ecc60706444b442241fda35df2b79b9e96dcb12405c1c295","addressRefs":[]},"1f64320b-feca-4059-95d3-f73950382031":{"id":"1f64320b-feca-4059-95d3-f73950382031","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.4.1","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4640,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: 5,000,000 PYUSD\n- `slope`: 200,000,000 PYUSD per day","contentHash":"29668871dfd1d6dfcae29dc187adacc2fce5710c5b72fb7a0027cd181e3fa8dc","addressRefs":[]},"880763c4-9474-41e4-bd59-2afb8796ab8b":{"id":"880763c4-9474-41e4-bd59-2afb8796ab8b","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4641,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"ae19bb92-fec6-4939-83ed-43154b8db004":{"id":"ae19bb92-fec6-4939-83ed-43154b8db004","doc_no":"A.6.1.1.1.2.6.1.3.1.12.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4642,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"f6b739d1-c637-48f8-abf7-8c8f173bb392":{"id":"f6b739d1-c637-48f8-abf7-8c8f173bb392","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3","title":"Ethereum Mainnet - Transfer PYUSD to Paxos (receive USDG) Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4643,"content":"The documents herein contain the Instance Configuration Document for the Transfer PYUSD to Paxos (receive USDG) Instance.","contentHash":"b4f32b7fa9e51031b0056f61661b7c9b6a17dccc9ac66eeab836998cac7636a6","addressRefs":[]},"4010a8e3-6ef1-4ad1-ad18-46c8e6de8e6a":{"id":"4010a8e3-6ef1-4ad1-ad18-46c8e6de8e6a","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4644,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"d60d90db-4847-4c3a-b0c1-337cb0364350":{"id":"d60d90db-4847-4c3a-b0c1-337cb0364350","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4645,"content":"The documents herein define the parameters of the Transfer PYUSD to Paxos (receive USDG) of the Allocation System Primitive.","contentHash":"fecd147a2e4329a480c7dbb853efe8525f2c32d7cc22ac0976d61ef8f3d7fef2","addressRefs":[]},"539c956e-f77b-48cc-9ebf-e875178bf97a":{"id":"539c956e-f77b-48cc-9ebf-e875178bf97a","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4646,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"9ba2f854-f17a-4f66-8bd6-75da9633b032":{"id":"9ba2f854-f17a-4f66-8bd6-75da9633b032","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4647,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"94488493-0093-4f6d-979a-45194be5465c":{"id":"94488493-0093-4f6d-979a-45194be5465c","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4648,"content":"Paxos","contentHash":"86067961d19af207fe385a6eb4c94c16ed1e62bd7ea8c61311669ff0ceca788a","addressRefs":[]},"f4d4b3b4-e720-4047-8b52-e08dd377ece0":{"id":"f4d4b3b4-e720-4047-8b52-e08dd377ece0","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4649,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"bd9ef5f1-01ec-476e-82f0-00790a80c63b":{"id":"bd9ef5f1-01ec-476e-82f0-00790a80c63b","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.1.4","title":"Token to Receive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4650,"content":"USDG","contentHash":"b02ff0d462b8abbde681bcb62ecc1f0e60664ff3775977f96fe17da501d80f65","addressRefs":[]},"7faea6c2-408d-42c4-8be0-bdd712211562":{"id":"7faea6c2-408d-42c4-8be0-bdd712211562","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4651,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"51c7e0ae-a2b2-4e0b-a9bf-6b7c6acb58e3":{"id":"51c7e0ae-a2b2-4e0b-a9bf-6b7c6acb58e3","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4652,"content":"`0x6c3ea9036406852006290770bedfcaba0e23a0e8`","contentHash":"ac7df8bf48b402a36c798cb7de5c858852ed1af979012ea4f6bc810a3a0dde38","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"9951f14e-9d5e-489a-8479-de33afd6c1c4":{"id":"9951f14e-9d5e-489a-8479-de33afd6c1c4","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4653,"content":"`0x6c3ea9036406852006290770bedfcaba0e23a0e8`","contentHash":"ac7df8bf48b402a36c798cb7de5c858852ed1af979012ea4f6bc810a3a0dde38","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"d30c73f2-c1dc-4ae1-91a0-f8f1061d80d1":{"id":"d30c73f2-c1dc-4ae1-91a0-f8f1061d80d1","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.2.3","title":"Paxos Deposit Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4654,"content":"`0x227B1912C2fFE1353EA3A603F1C05F030Cc262Ff`","contentHash":"9c791076bafa36a65f5e24f1e4c9310e79e3f7dc84cf513a34c0885b8d48f3c8","addressRefs":["0x227b1912c2ffe1353ea3a603f1c05f030cc262ff"]},"c0f6ad05-ec97-4464-9627-82b14035bc17":{"id":"c0f6ad05-ec97-4464-9627-82b14035bc17","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4655,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"0d22ec04-8742-49d5-a285-3668ce6d4947":{"id":"0d22ec04-8742-49d5-a285-3668ce6d4947","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4656,"content":"The current TransferAsset rate limits for this conduit's transferAssets operations are defined in the subdocuments herein.","contentHash":"0257a734df1df778ecc60706444b442241fda35df2b79b9e96dcb12405c1c295","addressRefs":[]},"eb39ef45-405a-46d5-acac-c0ecc47b7ea2":{"id":"eb39ef45-405a-46d5-acac-c0ecc47b7ea2","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.4.1","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4657,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: 5,000,000 PYUSD\n- `slope`: 50,000,000 PYUSD per day","contentHash":"408236a359e2887ab02917e08312da7fac9bea0c3076ab878a5448ec8dcad0e9","addressRefs":[]},"58faa1d1-96fb-44cd-8902-81a48cf7d2a8":{"id":"58faa1d1-96fb-44cd-8902-81a48cf7d2a8","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4658,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"f9be22e8-f6dd-4b99-9821-17cc1f251be9":{"id":"f9be22e8-f6dd-4b99-9821-17cc1f251be9","doc_no":"A.6.1.1.1.2.6.1.3.1.12.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4659,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"bef47e5b-5568-4df4-9294-2eb108a006c6":{"id":"bef47e5b-5568-4df4-9294-2eb108a006c6","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4","title":"Ethereum Mainnet - Transfer USDG to Paxos (receive PYUSD) Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4660,"content":"The documents herein contain the Instance Configuration Document for the Transfer USDG to Paxos (receive PYUSD) Instance.","contentHash":"a47e6ae2f6dffbf83a1b173a864b2e9d1ecb9f2a0b610d23cb58fec60debf2ee","addressRefs":[]},"1154efd4-1d7f-4cf2-8d6a-09bdde842827":{"id":"1154efd4-1d7f-4cf2-8d6a-09bdde842827","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4661,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"bc5c8128-8fbf-428c-a90a-34afb7cf2107":{"id":"bc5c8128-8fbf-428c-a90a-34afb7cf2107","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4662,"content":"The documents herein define the parameters of the Transfer USDG to Paxos (receive PYUSD) of the Allocation System Primitive.","contentHash":"a86a78ee2a43ebcb1ce5caf765ed4ff915bb4952d974487ea00a83b1311b5134","addressRefs":[]},"5268a2a0-1dc1-442c-a3ee-64eb6c91fdbb":{"id":"5268a2a0-1dc1-442c-a3ee-64eb6c91fdbb","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4663,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"0df49dfc-3125-4b9c-8b5e-95d8036cb1f7":{"id":"0df49dfc-3125-4b9c-8b5e-95d8036cb1f7","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4664,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"47d5f804-35a8-4016-b816-1066c75c1914":{"id":"47d5f804-35a8-4016-b816-1066c75c1914","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4665,"content":"Paxos","contentHash":"86067961d19af207fe385a6eb4c94c16ed1e62bd7ea8c61311669ff0ceca788a","addressRefs":[]},"61bc115a-5433-44d3-b86b-e5991fe2f077":{"id":"61bc115a-5433-44d3-b86b-e5991fe2f077","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4666,"content":"USDG","contentHash":"b02ff0d462b8abbde681bcb62ecc1f0e60664ff3775977f96fe17da501d80f65","addressRefs":[]},"4aa26757-47fd-4cc3-845e-d0d1b8487182":{"id":"4aa26757-47fd-4cc3-845e-d0d1b8487182","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.1.4","title":"Token to Receive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4667,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"f16deb9b-1cba-4178-9fea-b228862c9cc4":{"id":"f16deb9b-1cba-4178-9fea-b228862c9cc4","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4668,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"b3f52d1f-e089-4f99-b597-71e310cee76f":{"id":"b3f52d1f-e089-4f99-b597-71e310cee76f","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4669,"content":"`0xe343167631d89B6Ffc58B88d6b7fB0228795491D`","contentHash":"167543c0e6a678426dbcf6f5b9f4811d1078822a8bc83684b8e0ed365ed87b7f","addressRefs":["0xe343167631d89b6ffc58b88d6b7fb0228795491d"]},"cb6e5759-1db7-4287-afec-612348ee545b":{"id":"cb6e5759-1db7-4287-afec-612348ee545b","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4670,"content":"`0xe343167631d89B6Ffc58B88d6b7fB0228795491D`","contentHash":"167543c0e6a678426dbcf6f5b9f4811d1078822a8bc83684b8e0ed365ed87b7f","addressRefs":["0xe343167631d89b6ffc58b88d6b7fb0228795491d"]},"61d68d4e-dc31-4f29-9d69-7d2839b79b59":{"id":"61d68d4e-dc31-4f29-9d69-7d2839b79b59","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.2.3","title":"Paxos Deposit Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4671,"content":"`0x035b322D0e79de7c8733CdDA5a7EF8b51a6cfcfa`","contentHash":"888da2587e7a852bf224cbc7ccf7056a8d5c536bf8058f7852945dc1f336233a","addressRefs":["0x035b322d0e79de7c8733cdda5a7ef8b51a6cfcfa"]},"18f1f756-3755-4875-8c2f-a93be31bb8fa":{"id":"18f1f756-3755-4875-8c2f-a93be31bb8fa","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4672,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"ffbfbbf7-8de6-47b8-aa8d-052e8273f33e":{"id":"ffbfbbf7-8de6-47b8-aa8d-052e8273f33e","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4673,"content":"The current TransferAsset rate limits for this conduit's transferAssets operations are defined in the subdocuments herein.","contentHash":"0257a734df1df778ecc60706444b442241fda35df2b79b9e96dcb12405c1c295","addressRefs":[]},"22e01de3-379b-4724-9ff6-136937c002d2":{"id":"22e01de3-379b-4724-9ff6-136937c002d2","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.4.1","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4674,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: 5,000,000 USDG\n- `slope`: 100,000,000 USDG per day","contentHash":"79245bb872c71d46f64dd397ff2ce495d10e8d68acf57b734c8df8c9be061bff","addressRefs":[]},"c8887b5e-fb8f-4364-bc4d-715a5393fbb3":{"id":"c8887b5e-fb8f-4364-bc4d-715a5393fbb3","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4675,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"56e556cc-0401-4cbd-9bda-8fea5d921f6d":{"id":"56e556cc-0401-4cbd-9bda-8fea5d921f6d","doc_no":"A.6.1.1.1.2.6.1.3.1.12.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4676,"content":"","contentHash":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","addressRefs":[]},"1565129f-7249-4f5b-babb-7f81d33eff13":{"id":"1565129f-7249-4f5b-babb-7f81d33eff13","doc_no":"A.6.1.1.1.2.6.1.3.1.13","title":"Anchorage","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4677,"content":"The Ethereum Mainnet Instances of the Anchorage Protocol with `Active` Status are stored herein.","contentHash":"1ea448df9984b4773f2c11f781167aac624cf03c46b51dd7f25e07a5f9349422","addressRefs":[]},"8048e396-7bb4-4541-a68f-6dd7ec0a6015":{"id":"8048e396-7bb4-4541-a68f-6dd7ec0a6015","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1","title":"Ethereum Mainnet - Anchorage USAT Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4678,"content":"The documents herein contain the Instance Configuration Document for the Anchorage USAT Instance.","contentHash":"c16c32c90a63f68a6008efc569980d66be81cdf7c902e935c3df11d45da42cb4","addressRefs":[]},"eff5d00f-b831-417f-8cb9-a9edfaccbbcd":{"id":"eff5d00f-b831-417f-8cb9-a9edfaccbbcd","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4679,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"78067cd5-bd11-47eb-bdf7-947038912cfa":{"id":"78067cd5-bd11-47eb-bdf7-947038912cfa","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4680,"content":"The documents herein define the parameters of the Anchorage USAT Instance of the Allocation System Primitive.","contentHash":"741001ec389bd27098f20fbc71465e8d8c03fbe044e49d30c2b9f9578a461ac6","addressRefs":[]},"65214651-962d-442b-99f1-dd1157a77c86":{"id":"65214651-962d-442b-99f1-dd1157a77c86","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4681,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"83f14764-63d8-4908-ac4e-ac7a46f37cac":{"id":"83f14764-63d8-4908-ac4e-ac7a46f37cac","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4682,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"882a4a15-b9e8-4ebe-b800-410cddc87ab1":{"id":"882a4a15-b9e8-4ebe-b800-410cddc87ab1","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4683,"content":"Anchorage","contentHash":"081c70b9160626ec8bc2f6580f87c619f9a39a0ef58d13428686581b7d3677c7","addressRefs":[]},"db820c09-0b14-45ea-8367-d7a301718fb9":{"id":"db820c09-0b14-45ea-8367-d7a301718fb9","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4684,"content":"USAT","contentHash":"8448a76a72d0c3742fca7d8490fc40a7185772e461080756734cfe7c4cce29ce","addressRefs":[]},"ac45e6ad-5076-4fed-8805-d48593e41778":{"id":"ac45e6ad-5076-4fed-8805-d48593e41778","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4685,"content":"USAT","contentHash":"8448a76a72d0c3742fca7d8490fc40a7185772e461080756734cfe7c4cce29ce","addressRefs":[]},"b9b80a90-766b-424b-b56d-334cacee4dd2":{"id":"b9b80a90-766b-424b-b56d-334cacee4dd2","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4686,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"cca5bcb2-eb4a-429a-b10c-a55c7c6bb683":{"id":"cca5bcb2-eb4a-429a-b10c-a55c7c6bb683","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4687,"content":"`0x07041776f5007aca2a54844f50503a18a72a8b68`","contentHash":"812983ff7e1b9dc10afa745a3389120192de73b916eed6b5d5eb8bdeb7c2f160","addressRefs":["0x07041776f5007aca2a54844f50503a18a72a8b68"]},"5396d5c2-6f79-4ab2-8978-61dc6209a00c":{"id":"5396d5c2-6f79-4ab2-8978-61dc6209a00c","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.2.2","title":"Destination Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4688,"content":"`0x49506C3Aa028693458d6eE816b2EC28522946872`","contentHash":"012a7740dfe738485a88afc62514ae56190bcb718ff3120f90dab833c8b7851f","addressRefs":["0x49506c3aa028693458d6ee816b2ec28522946872"]},"a7508ca1-0132-4a94-9efd-2288a30c3220":{"id":"a7508ca1-0132-4a94-9efd-2288a30c3220","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4689,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"132f9c53-0f2d-4e0a-9adb-649eadf9d95f":{"id":"132f9c53-0f2d-4e0a-9adb-649eadf9d95f","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4690,"content":"The current `maxAmount` and `slope` for this conduit’s transferAssets operations are defined in the subdocuments herein.","contentHash":"8c6851ec335ffbbd6d83a4dacdb6531aaa1d537e31250ce3fd951645f555ed35","addressRefs":[]},"4093b98b-2421-4642-982b-8c08b2f5ef20":{"id":"4093b98b-2421-4642-982b-8c08b2f5ef20","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.4.1","title":"transferAsset Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4691,"content":"- `maxAmount`: 50,000,000 USAT\n- `slope`: 250,000,000 USAT per day","contentHash":"e0e9a811172d09a00ce0676580c3cf5109fd4412093f9145202ecbbd6658da7e","addressRefs":[]},"069aa415-4d37-4567-b7da-bda62e4d0423":{"id":"069aa415-4d37-4567-b7da-bda62e4d0423","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4692,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"98759dcc-8bb4-459a-b020-d46a02b038ec":{"id":"98759dcc-8bb4-459a-b020-d46a02b038ec","doc_no":"A.6.1.1.1.2.6.1.3.1.13.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4693,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"4eee15e5-46e2-4438-8299-6c85c46bb85b":{"id":"4eee15e5-46e2-4438-8299-6c85c46bb85b","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2","title":"Ethereum Mainnet - Anchorage USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4694,"content":"The documents herein contain the Instance Configuration Document for the Anchorage USDT Instance.","contentHash":"dc0ed365c2b2064b7f662e7293911ac9197ea1b8ddcbc6873faaca6f40834a95","addressRefs":[]},"54ce1edc-9556-4103-bb4d-0b45efcdbb43":{"id":"54ce1edc-9556-4103-bb4d-0b45efcdbb43","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4695,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"7b07774c-4cda-4866-bc4e-7e469a685f5e":{"id":"7b07774c-4cda-4866-bc4e-7e469a685f5e","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4696,"content":"The documents herein define the parameters of the Anchorage USDT Instance of the Allocation System Primitive.","contentHash":"b082976191ae6c00dd306bd428fef8c3ebb7c29ee8897554a1ab6719f377b3d2","addressRefs":[]},"afa6a7e4-fbeb-4138-9220-91c023203ce5":{"id":"afa6a7e4-fbeb-4138-9220-91c023203ce5","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4697,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"e0febf90-ab83-4b7f-9bea-dc037c1b96c0":{"id":"e0febf90-ab83-4b7f-9bea-dc037c1b96c0","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4698,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"b8aed139-8a1a-467f-acf4-877d42516e87":{"id":"b8aed139-8a1a-467f-acf4-877d42516e87","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4699,"content":"Anchorage","contentHash":"081c70b9160626ec8bc2f6580f87c619f9a39a0ef58d13428686581b7d3677c7","addressRefs":[]},"f993b46b-291c-45a1-a369-27c37e7bfddd":{"id":"f993b46b-291c-45a1-a369-27c37e7bfddd","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4700,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"00f2dded-9e35-4af8-9ac4-c706737540ac":{"id":"00f2dded-9e35-4af8-9ac4-c706737540ac","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4701,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"30bc6650-5589-443b-ae3a-1b86d463e05b":{"id":"30bc6650-5589-443b-ae3a-1b86d463e05b","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4702,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"c9ef9947-ee35-416c-bb6d-30d1fea15d3f":{"id":"c9ef9947-ee35-416c-bb6d-30d1fea15d3f","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4703,"content":"`0xdAC17F958D2ee523a2206206994597C13D831ec7`","contentHash":"d674f514fb5256107f891afe7b796353b6535b08717e30bc071e1ccdf11a1fbf","addressRefs":["0xdac17f958d2ee523a2206206994597c13d831ec7"]},"f5b05cdd-1aef-4b02-beda-99a2e3a69015":{"id":"f5b05cdd-1aef-4b02-beda-99a2e3a69015","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.2.2","title":"Destination Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4704,"content":"`0x49506C3Aa028693458d6eE816b2EC28522946872`","contentHash":"012a7740dfe738485a88afc62514ae56190bcb718ff3120f90dab833c8b7851f","addressRefs":["0x49506c3aa028693458d6ee816b2ec28522946872"]},"435ca83e-fbd7-4ace-866d-8ffc9388118c":{"id":"435ca83e-fbd7-4ace-866d-8ffc9388118c","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4705,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"b494026e-d3bc-4122-bac3-98ea1d7436b0":{"id":"b494026e-d3bc-4122-bac3-98ea1d7436b0","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4706,"content":"The current `maxAmount` and `slope` for this conduit’s transferAssets operations are defined in the subdocuments herein.","contentHash":"8c6851ec335ffbbd6d83a4dacdb6531aaa1d537e31250ce3fd951645f555ed35","addressRefs":[]},"5a56203b-5c1b-42e8-9acb-8ab78eb4dc06":{"id":"5a56203b-5c1b-42e8-9acb-8ab78eb4dc06","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.4.1","title":"transferAsset Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4707,"content":"- `maxAmount`: 50,000,000 USDT\n- `slope`: 250,000,000 USDT per day","contentHash":"cf4710410f6300bab5c1b5a1d406fca66e0f6f9f389afc73f1c1cdc85c2ea329","addressRefs":[]},"1ec11acd-b8fe-4310-b1ba-6e57c9c27fd3":{"id":"1ec11acd-b8fe-4310-b1ba-6e57c9c27fd3","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4708,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"1c69d51a-f202-4e17-99cd-dd29a046e2a5":{"id":"1c69d51a-f202-4e17-99cd-dd29a046e2a5","doc_no":"A.6.1.1.1.2.6.1.3.1.13.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4709,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"9ddbfaed-ebb8-4dd4-9f08-d12cad450a00":{"id":"9ddbfaed-ebb8-4dd4-9f08-d12cad450a00","doc_no":"A.6.1.1.1.2.6.1.3.2","title":"Base","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4710,"content":"The Base Instances of the Spark Liquidity Layer with `Active` Status are stored herein.","contentHash":"d01a58c22887ffa4ada65a474beba6efc98bbb1af57b4602b6caddd88c04fafd","addressRefs":[]},"a5351a25-419c-437f-92c0-ff6f07c8677a":{"id":"a5351a25-419c-437f-92c0-ff6f07c8677a","doc_no":"A.6.1.1.1.2.6.1.3.2.1","title":"Morpho","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4711,"content":"The Base Instances of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"b1bfd808dca3f55aa7bc2b45a8e6f9ed3e46bc502232f81fc9d1f4ffb1dd19d6","addressRefs":[]},"97c54a67-ff3d-40c3-a702-f632f2b81f2d":{"id":"97c54a67-ff3d-40c3-a702-f632f2b81f2d","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1","title":"Base - Morpho Blue USDC ERC4626 Vault Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4712,"content":"The documents herein contain the Instance Configuration Document for the Morpho Blue USDC ERC4626 Vault Instance.","contentHash":"ef290ee37c0edf0557b95b65d7edb0099219b49834e584c639c74460b7b505f8","addressRefs":[]},"2bd39387-8ce1-4e3d-9c3b-5bbfb241f935":{"id":"2bd39387-8ce1-4e3d-9c3b-5bbfb241f935","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4713,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"c0b80ed0-dda1-4efd-9899-d35ecf5b2ab4":{"id":"c0b80ed0-dda1-4efd-9899-d35ecf5b2ab4","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4714,"content":"The documents herein define the parameters of the Morpho Blue USDC ERC4626 Vault Instance of the Allocation System Primitive.","contentHash":"14cb89e855edb09d1560de4eaee2b3e81c4e31d80f79350b880a73029052b033","addressRefs":[]},"49ab64df-ac5c-4595-82dc-0e984a8c97d9":{"id":"49ab64df-ac5c-4595-82dc-0e984a8c97d9","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4715,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"421aae3a-2ade-4dd3-accb-829a92b8fdf5":{"id":"421aae3a-2ade-4dd3-accb-829a92b8fdf5","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4716,"content":"Base","contentHash":"e5d5b6ffa6b5cd344e1d730f7910baa54b4ff67ba489d0f65414f99744fad304","addressRefs":[]},"8af68bad-a084-482d-bb17-746d2dc48a77":{"id":"8af68bad-a084-482d-bb17-746d2dc48a77","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4717,"content":"Morpho Blue (ERC4626 Vault)","contentHash":"56f031f8fbf3da3e8c5115875b5d2e605a87df1d1dd35d20a8629946ce76cf95","addressRefs":[]},"e40597fd-a25d-4865-a486-d1b6fd3141e7":{"id":"e40597fd-a25d-4865-a486-d1b6fd3141e7","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4718,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"6ed4c7e8-a0b2-4b61-aa55-9d5d43ba61b4":{"id":"6ed4c7e8-a0b2-4b61-aa55-9d5d43ba61b4","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4719,"content":"sparkUSDC","contentHash":"62756fd42eec238bfb1b1fee2318bb8acc958dc2fa9f47746ffa05b1e56d24f6","addressRefs":[]},"b29004e1-3967-4f92-93e5-152d6f96bac7":{"id":"b29004e1-3967-4f92-93e5-152d6f96bac7","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4720,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"89fc9a0a-0407-463e-8f45-2b2ca6e1d832":{"id":"89fc9a0a-0407-463e-8f45-2b2ca6e1d832","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.2.1","title":"Token Address (ERC4626 Vault)","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4721,"content":"`0x7BfA7C4f149E7415b73bdeDfe609237e29CBF34A`","contentHash":"fc6152fd922ca5b6f69d4f4040bc99b85fcf3c254b35118341467134722876af","addressRefs":["0x7bfa7c4f149e7415b73bdedfe609237e29cbf34a"]},"2efab1a6-9c66-4b61-af68-2740efd8d475":{"id":"2efab1a6-9c66-4b61-af68-2740efd8d475","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4722,"content":"`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`","contentHash":"1514606ff71954880aebca40f0d22ff3f4870e8ed77ca8c8f709e6a83f57efd6","addressRefs":["0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"]},"64f057b6-40cc-4ef9-b1c5-36c7430b543f":{"id":"64f057b6-40cc-4ef9-b1c5-36c7430b543f","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.2.3","title":"Allocator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4723,"content":"`0xCBA0C0a2a0B6Bb11233ec4EA85C5bFfea33e724d`","contentHash":"67fe37af7852bd0a9f2d38e18e822a26068d2db4270f41af6db7133ad45216e5","addressRefs":["0xcba0c0a2a0b6bb11233ec4ea85c5bffea33e724d"]},"c8ac360b-6c77-458f-a481-78b4554dd682":{"id":"c8ac360b-6c77-458f-a481-78b4554dd682","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4724,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"dbd9a2e2-74c7-47e5-abe4-d0940cb16f8e":{"id":"dbd9a2e2-74c7-47e5-abe4-d0940cb16f8e","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4725,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"97aa974e-5b7d-43fb-be88-947454d69a53":{"id":"97aa974e-5b7d-43fb-be88-947454d69a53","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4726,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,00 USDC\n- `slope`: 50,000,00 USDC per day","contentHash":"528c68a021880e4be9c3deffb5a0fcccbc12191261d96d83af1737b0f2425f7e","addressRefs":[]},"63e50c95-64fd-4266-86c0-096681fa54e6":{"id":"63e50c95-64fd-4266-86c0-096681fa54e6","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4727,"content":"The outflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"f86f9b8db49561115373b94ce3c5597ef57303406aa4653493a0f3808edf7859","addressRefs":[]},"1249bc92-d66d-4ffc-bc42-a0184cbef5cb":{"id":"1249bc92-d66d-4ffc-bc42-a0184cbef5cb","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4728,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"9b849363-5380-406f-888a-d533f6ec69de":{"id":"9b849363-5380-406f-888a-d533f6ec69de","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4729,"content":"The Instance follows the general ERC4626 procedures see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2 - ERC-4626 Functions](e386a0df-9e0b-4ffd-9879-49131f795b0b) and for emergency procedures see [A.6.1.1.1.2.6.1.2.2.3.4.1 - ERC-4626 Withdrawal Action](f92ddc3f-672a-4f52-931f-5263a9f709b9). For detailed example of the Spark Liquidity Layer interaction logic for depositing to, withdrawing from, and redeeming from this ERC4626 vault instance see [A.6.1.1.1.2.6.1.3.1.5.1.3.1 - Deposit ERC-4626 Tokens](e2ad525b-3f3f-4402-9e4d-3ae125b35b76) and [A.6.1.1.1.2.6.1.3.1.5.1.3.2 - Withdraw ERC-4626 Tokens](caa295f4-92f4-4ca9-9083-2a1b94c70d5f).","contentHash":"b89f6a6373effdd18fe878c76a39dd0a1275ab8b11159910da31ce93816f409d","addressRefs":[]},"71568640-f127-441d-bdbe-5761d685e505":{"id":"71568640-f127-441d-bdbe-5761d685e505","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4730,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"ab15055e-99ff-4699-82f9-6f1b9a6b4f58":{"id":"ab15055e-99ff-4699-82f9-6f1b9a6b4f58","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4.1","title":"Market Exposure","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4731,"content":"The documents herein contains exposure details for this Instance","contentHash":"dcb4517b68d8d2675d018958e9963b0b5a80b19db3c1d93ee12c6d3a842a0d1f","addressRefs":[]},"f826bb79-9903-49f0-a421-ff3e5a6b4efb":{"id":"f826bb79-9903-49f0-a421-ff3e5a6b4efb","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4.1.1","title":"ETH/USDC 86% LLTV Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4732,"content":"- Pool ID: 0x8793cf302b8ffd655ab97bd1c695dbd967807e8367a65cb2f4edaf1380ba1bda\n- Supply cap: 1,000,000,000","contentHash":"c3beac8c6da86a8c3b65e66e0ac9900e5ee7d52cef14b92dd19a3e0516a523d6","addressRefs":[]},"e9a7720b-27a4-4ec2-8c2c-ce46625369fd":{"id":"e9a7720b-27a4-4ec2-8c2c-ce46625369fd","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4.1.2","title":"cbETH/USDC 86% LLTV Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4733,"content":"- Pool ID: 0x1c21c59df9db44bf6f645d854ee710a8ca17b479451447e9f56758aee10a2fad\n- Supply cap: 50,000,000","contentHash":"6717ce6a8d603e92665c5a52b7d9360712cb11f699c3aeaf25b5fac1bff92200","addressRefs":[]},"38936f4a-42da-4d27-a7ef-65ae9b104a7a":{"id":"38936f4a-42da-4d27-a7ef-65ae9b104a7a","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4734,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"921d59d4-baaf-45a8-b6ff-93aa879e0e41":{"id":"921d59d4-baaf-45a8-b6ff-93aa879e0e41","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4.2.1","title":"Curator Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4735,"content":"`0x0f963A8A8c01042B69054e787E5763ABbB0646A3`","contentHash":"a57f654d13b483afeed9b6d9529e6c2c9210b95a6467dc5bbc34878b9cc20805","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3"]},"edee318a-59b1-4ff1-9790-8d4606f2f7bd":{"id":"edee318a-59b1-4ff1-9790-8d4606f2f7bd","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4.2.2","title":"Guardian Role Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4736,"content":"`0xf5748bBeFa17505b2F7222B23ae11584932C908B`","contentHash":"668a86bee4a9f2f78e24f2549b98c35e72d36e967e29827d12a4c7108e4269f6","addressRefs":["0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"63f24280-1724-4d2c-a0b8-aa8a2381afb8":{"id":"63f24280-1724-4d2c-a0b8-aa8a2381afb8","doc_no":"A.6.1.1.1.2.6.1.3.2.1.1.4.3","title":"Timelock","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4737,"content":"Timelock: 240 hours (10 days)","contentHash":"bd70db312c9585d38ff92e664b2ee51c62b5185a730a6bc4b8efaf617abbe565","addressRefs":[]},"6be8271c-9f42-4eef-a05e-96e73e5d18b4":{"id":"6be8271c-9f42-4eef-a05e-96e73e5d18b4","doc_no":"A.6.1.1.1.2.6.1.3.2.2","title":"Fluid","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4738,"content":"The Base Instances of the Fluid Protocol with `Active` Status are stored herein.","contentHash":"2eb18d019af7ef6f98a9ead644d3b931b3a25304a2fa39d1f8d315abc93b3364","addressRefs":[]},"b955e881-1ad7-479f-9858-efebe8e23bdc":{"id":"b955e881-1ad7-479f-9858-efebe8e23bdc","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1","title":"Base Mainnet - Fluid sUSDS ERC4626 Vault Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4739,"content":"The documents herein contain the Instance Configuration Document for the Fluid sUSDS ERC4626 Instance.","contentHash":"ff5d35a282ef42965ff1711b1bedfd7171972fdb4dace228be196ee7639537fb","addressRefs":[]},"79edb8fa-6801-43c0-9190-4dbb5e9865c8":{"id":"79edb8fa-6801-43c0-9190-4dbb5e9865c8","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4740,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"c090d021-d1a9-41c9-afcf-4edaa97150c0":{"id":"c090d021-d1a9-41c9-afcf-4edaa97150c0","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4741,"content":"The documents herein define the parameters of the Fluid sUSDS ERC4626 Vault Instance of the Allocation System Primitive.","contentHash":"c76335e444895dd188f1b3186a9ca3fa85c93663f1d3db4bab6da0e0b124254b","addressRefs":[]},"f8aeef37-1251-4871-b5c7-5d1e80d8f15c":{"id":"f8aeef37-1251-4871-b5c7-5d1e80d8f15c","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4742,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"f09051d1-3526-49cc-b09d-576a3705f4f8":{"id":"f09051d1-3526-49cc-b09d-576a3705f4f8","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4743,"content":"Base","contentHash":"e5d5b6ffa6b5cd344e1d730f7910baa54b4ff67ba489d0f65414f99744fad304","addressRefs":[]},"84fd28d3-1624-4a94-bff2-9c69cbaa2904":{"id":"84fd28d3-1624-4a94-bff2-9c69cbaa2904","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4744,"content":"Fluid Finance (ERC4626 Vault)","contentHash":"dce22b411372d756b541ceeeaf09ec6542de2afc444fa102196b8c77b1021acd","addressRefs":[]},"cb25347b-93dc-42cb-a691-1c130ec9c6a1":{"id":"cb25347b-93dc-42cb-a691-1c130ec9c6a1","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4745,"content":"sUSDS","contentHash":"fca5df225d787c8fd72534cf85993160140a59c4d215a8692340634c06d627c2","addressRefs":[]},"d638194b-7668-4ccd-bef0-1110c38fe6a3":{"id":"d638194b-7668-4ccd-bef0-1110c38fe6a3","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4746,"content":"fsUSDS","contentHash":"c16ee9508be095c21b7166a8e8bfa68feae03d80ccbdfa5f43d491397d359a80","addressRefs":[]},"18ae718a-6a68-41df-a5a0-b8f27d2b7665":{"id":"18ae718a-6a68-41df-a5a0-b8f27d2b7665","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4747,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"5ce2cf40-bc6f-48fe-894b-aca0c6a8ecec":{"id":"5ce2cf40-bc6f-48fe-894b-aca0c6a8ecec","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.2.1","title":"Token Address (ERC4626 Vault)","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4748,"content":"`0xf62e339f21d8018940f188F6987Bcdf02A849619`","contentHash":"f7bb127324202485496694bb1d943c0441593659372a0fa4fc758050ce2a277a","addressRefs":["0xf62e339f21d8018940f188f6987bcdf02a849619"]},"8b66880c-e943-46b2-8411-a1c84dc0a5f6":{"id":"8b66880c-e943-46b2-8411-a1c84dc0a5f6","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4749,"content":"`0x5875eEE11Cf8398102FdAd704C9E96607675467a`","contentHash":"309121c218a64bdda2eed1f40b90cdc1a13fe29a9dfc92f585fa27f088305d89","addressRefs":["0x5875eee11cf8398102fdad704c9e96607675467a"]},"4a6342b9-8f9f-48ae-82a2-8c1293bb8004":{"id":"4a6342b9-8f9f-48ae-82a2-8c1293bb8004","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4750,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"4f689c17-28f3-4217-984d-b71eb7b97b7a":{"id":"4f689c17-28f3-4217-984d-b71eb7b97b7a","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4751,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"29114e51-9590-4585-b494-b78417f35910":{"id":"29114e51-9590-4585-b494-b78417f35910","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4752,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 5,000,000 USDS per day","contentHash":"9083d2802963d50df8b99c4a2b8891ca4febbc20317c0b9c1cef030a1ddc77d8","addressRefs":[]},"f8a431bd-2d0b-4d60-886c-6e3dac42989e":{"id":"f8a431bd-2d0b-4d60-886c-6e3dac42989e","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4753,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 5,000,000 fsUSDS per day","contentHash":"76162056a3a1678fb0869e9341ba56033ab0a7a61199862dfebef86081c8e302","addressRefs":[]},"00f6c298-eb05-4c7a-b83c-5bc80a283104":{"id":"00f6c298-eb05-4c7a-b83c-5bc80a283104","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4754,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"7c196eb9-92b0-4c43-bd8a-d78a8743a589":{"id":"7c196eb9-92b0-4c43-bd8a-d78a8743a589","doc_no":"A.6.1.1.1.2.6.1.3.2.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4755,"content":"The Instance follows the general ERC4626 procedures see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2 - ERC-4626 Functions](e386a0df-9e0b-4ffd-9879-49131f795b0b) and for emergency procedures see [A.6.1.1.1.2.6.1.2.2.3.4.1 - ERC-4626 Withdrawal Action](f92ddc3f-672a-4f52-931f-5263a9f709b9). For detailed example of the Spark Liquidity Layer interaction logic for depositing to, withdrawing from, and redeeming from this ERC4626 vault instance see [A.6.1.1.1.2.6.1.3.1.5.1.3.1 - Deposit ERC-4626 Tokens](e2ad525b-3f3f-4402-9e4d-3ae125b35b76) and [A.6.1.1.1.2.6.1.3.1.5.1.3.2 - Withdraw ERC-4626 Tokens](caa295f4-92f4-4ca9-9083-2a1b94c70d5f).","contentHash":"b89f6a6373effdd18fe878c76a39dd0a1275ab8b11159910da31ce93816f409d","addressRefs":[]},"a74ec7ed-eb8a-4144-ae32-fa90f751538c":{"id":"a74ec7ed-eb8a-4144-ae32-fa90f751538c","doc_no":"A.6.1.1.1.2.6.1.3.2.3","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4756,"content":"The Base Instances of the Aave Protocol with `Active` Status are stored herein.","contentHash":"40c8efcf4195ebf027a625901e367a8d089944b55dcf4b8673758a17a3695880","addressRefs":[]},"adfe1844-38ae-4eac-9060-f79978751765":{"id":"adfe1844-38ae-4eac-9060-f79978751765","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1","title":"Base - Aave USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4757,"content":"The documents herein contain the Instance Configuration Document for the Aave USDC Instance.","contentHash":"c53d92914c7bde414efcfa56d67a653348c2e4f531417f18f5b567f6730380eb","addressRefs":[]},"5339627f-27f5-4c01-8d99-0b0bb0866f33":{"id":"5339627f-27f5-4c01-8d99-0b0bb0866f33","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4758,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"7b66655a-be93-49fa-b9d2-0ea76622930b":{"id":"7b66655a-be93-49fa-b9d2-0ea76622930b","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4759,"content":"The documents herein define the parameters of the Aave USDC Instance of the Allocation System Primitive.","contentHash":"d73e9b183c5bb40a8587be90595c166c098b81e638e4e3c6d6c223b0d74ca7d9","addressRefs":[]},"a2fae303-cde7-4e71-99ec-29fff49abb82":{"id":"a2fae303-cde7-4e71-99ec-29fff49abb82","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4760,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"25f23eac-7761-4b9e-9d10-19235d65d201":{"id":"25f23eac-7761-4b9e-9d10-19235d65d201","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4761,"content":"Base","contentHash":"e5d5b6ffa6b5cd344e1d730f7910baa54b4ff67ba489d0f65414f99744fad304","addressRefs":[]},"a33b4fb5-ee2b-49fc-bc99-4278f3ef281a":{"id":"a33b4fb5-ee2b-49fc-bc99-4278f3ef281a","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4762,"content":"Aave","contentHash":"65c4d784bc7c28c45f8106bfd470ca8b8c7c072efd28d90c06d56c790e8a1cfb","addressRefs":[]},"444562db-82e3-4e85-b1a0-eea3b5ed2162":{"id":"444562db-82e3-4e85-b1a0-eea3b5ed2162","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4763,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"a066bf00-a88d-486d-b288-76dcf6e74c15":{"id":"a066bf00-a88d-486d-b288-76dcf6e74c15","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4764,"content":"aBasUSDC","contentHash":"fc08d93415cc6eb6e40e857d822c7205c1c29c0bdee894ca75b25cce4341a455","addressRefs":[]},"4d455770-96aa-4ecd-93a0-00b54494ea9c":{"id":"4d455770-96aa-4ecd-93a0-00b54494ea9c","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4765,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"92d1ebed-51c8-4877-898e-e21c0cc85e6d":{"id":"92d1ebed-51c8-4877-898e-e21c0cc85e6d","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4766,"content":"`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`","contentHash":"1514606ff71954880aebca40f0d22ff3f4870e8ed77ca8c8f709e6a83f57efd6","addressRefs":["0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"]},"ce769e22-56cc-4ab1-91a7-ae8d12c2f9fd":{"id":"ce769e22-56cc-4ab1-91a7-ae8d12c2f9fd","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4767,"content":"`0x4e65fE4DbA92790696d040ac24Aa414708F5c0AB`","contentHash":"f61876a3c4240a2b2bbbccb42c33c494a3717e29cd87a8ebfe503ad8c51c8f52","addressRefs":["0x4e65fe4dba92790696d040ac24aa414708f5c0ab"]},"510aabe8-5660-4b5d-b647-cd4ff022a620":{"id":"510aabe8-5660-4b5d-b647-cd4ff022a620","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.2.3","title":"Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4768,"content":"This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"ea3c5d84119733fb3a2a429f279628dcce722f210f012ad0286de1cf9435e132","addressRefs":[]},"bdb8e938-6930-4307-8d26-1e6e0e29f5d5":{"id":"bdb8e938-6930-4307-8d26-1e6e0e29f5d5","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4769,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"9942de86-4cb3-4d55-a24c-7cf7cc42ea6d":{"id":"9942de86-4cb3-4d55-a24c-7cf7cc42ea6d","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4770,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"3ef9417d-39af-46ba-b26d-4fbe11ef153b":{"id":"3ef9417d-39af-46ba-b26d-4fbe11ef153b","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4771,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 25,000,000 USDC per day","contentHash":"7d84d9f4173122f32102d13ebffc575af717302b88c34986a1e928e96e92dfd2","addressRefs":[]},"89e0b1fb-f660-4cf2-8977-ccb872854ced":{"id":"89e0b1fb-f660-4cf2-8977-ccb872854ced","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4772,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: Unlimited","contentHash":"55f2afe4138f46e4ed73589852a0887ee907f02eb1fc355e4edab05a25597846","addressRefs":[]},"93b85c6b-8dff-420e-9f5a-c8c10390ef86":{"id":"93b85c6b-8dff-420e-9f5a-c8c10390ef86","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4773,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"bac5a103-a0fa-4d3b-8cd0-b9dfe024d4a9":{"id":"bac5a103-a0fa-4d3b-8cd0-b9dfe024d4a9","doc_no":"A.6.1.1.1.2.6.1.3.2.3.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4774,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes. For the general operational procedures applicable to all Aave-type instances. See [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3 - Aave Functions](9922dcf0-4562-445b-9a46-712f677cce64) and [A.6.1.1.1.2.6.1.2.2.3.2.3 - Aave AToken Withdrawal Action](2560adbb-4a5c-4c95-86cb-04647bb33836). For detailed example of the Spark Liquidity Layer interaction logic for depositing to and withdrawing from Aave see [A.6.1.1.1.2.6.1.3.1.2.1.3.1 - Process Definition For Depositing](fa2520ac-4779-4aeb-abe4-2c1b89e7ca51) and [A.6.1.1.1.2.6.1.3.1.2.1.3.2 - Process Definition For Withdrawing](35e32620-a28c-4101-a881-2b7c2b9e42f2).","contentHash":"d385452e47622b373128e6db9a2e709cf0a3646ef911db13d7e85bdf747760d5","addressRefs":[]},"52565140-229d-42b4-9284-905b858dee6c":{"id":"52565140-229d-42b4-9284-905b858dee6c","doc_no":"A.6.1.1.1.2.6.1.3.3","title":"Arbitrum","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4775,"content":"The Arbitrum Instances of the Spark Liquidity Layer with `Active` Status are stored herein.","contentHash":"14c661d9ee40fcc4228ea6a02e65c63c03c3e9584488794c2dca5d06b11aaed9","addressRefs":[]},"ede14170-01c6-4706-b17d-fb494b734a93":{"id":"ede14170-01c6-4706-b17d-fb494b734a93","doc_no":"A.6.1.1.1.2.6.1.3.3.1","title":"Fluid","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4776,"content":"The Arbitrum Instances of the Fluid Protocol with `Active` Status are stored herein.","contentHash":"18a2f5adf92f1392bf081866c522bedac394b9560b1f0c8928d423b9c76885ad","addressRefs":[]},"e6a55c76-91f7-4503-9349-b082c762ec76":{"id":"e6a55c76-91f7-4503-9349-b082c762ec76","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1","title":"Arbitrum - Fluid sUSDS ERC4626 Vault Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4777,"content":"The documents herein contain the Instance Configuration Document for the Fluid sUSDS ERC4626 Instance.","contentHash":"ff5d35a282ef42965ff1711b1bedfd7171972fdb4dace228be196ee7639537fb","addressRefs":[]},"910fe6e2-aeee-4d8a-8c98-dab4f9869a5c":{"id":"910fe6e2-aeee-4d8a-8c98-dab4f9869a5c","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4778,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"8ae596a4-1e54-430d-83ab-65e14c1b59a7":{"id":"8ae596a4-1e54-430d-83ab-65e14c1b59a7","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4779,"content":"The documents herein define the parameters of the Fluid sUSDS ERC4626 Vault Instance of the Allocation System Primitive.","contentHash":"c76335e444895dd188f1b3186a9ca3fa85c93663f1d3db4bab6da0e0b124254b","addressRefs":[]},"a3a5d44d-9ce3-40d0-af7d-dab76efd5d1e":{"id":"a3a5d44d-9ce3-40d0-af7d-dab76efd5d1e","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4780,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"b840b879-fcbe-4d18-ac3e-146693c67268":{"id":"b840b879-fcbe-4d18-ac3e-146693c67268","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4781,"content":"Arbitrum","contentHash":"547ba9625e474ab7c414601027c59310d85a306d87edac8e7b86b39772010668","addressRefs":[]},"ed8dfb3b-d69b-4238-a685-0ee37d4c047b":{"id":"ed8dfb3b-d69b-4238-a685-0ee37d4c047b","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4782,"content":"Fluid Finance (ERC4626 Vault)","contentHash":"dce22b411372d756b541ceeeaf09ec6542de2afc444fa102196b8c77b1021acd","addressRefs":[]},"d6a11516-1a75-4d97-a7de-402595d68dbc":{"id":"d6a11516-1a75-4d97-a7de-402595d68dbc","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4783,"content":"sUSDS","contentHash":"fca5df225d787c8fd72534cf85993160140a59c4d215a8692340634c06d627c2","addressRefs":[]},"f9882004-d6bf-4c5d-b85a-d9230e52a1a8":{"id":"f9882004-d6bf-4c5d-b85a-d9230e52a1a8","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4784,"content":"fsUSDS","contentHash":"c16ee9508be095c21b7166a8e8bfa68feae03d80ccbdfa5f43d491397d359a80","addressRefs":[]},"30cb7c3c-1133-4899-9850-d92a72e86446":{"id":"30cb7c3c-1133-4899-9850-d92a72e86446","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4785,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"d9b0d43b-3d65-453d-8099-f49e7959e6a4":{"id":"d9b0d43b-3d65-453d-8099-f49e7959e6a4","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.2.1","title":"Token Address (ERC4626 Vault)","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4786,"content":"`0x3459fcc94390C3372c0F7B4cD3F8795F0E5aFE96`","contentHash":"c0c08f7d2bc5c8b0368222a209330d6cff065ca3fe61911eb50a85a18707cc61","addressRefs":["0x3459fcc94390c3372c0f7b4cd3f8795f0e5afe96"]},"656e1bad-91a3-4360-9804-a04ac194b1c7":{"id":"656e1bad-91a3-4360-9804-a04ac194b1c7","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4787,"content":"`0xdDb46999F8891663a8F2828d25298f70416d7610`","contentHash":"aa9660bd4dfdee86473226669e7dbaecb0891817d0b6aaff78db2bc6acb50cf0","addressRefs":["0xddb46999f8891663a8f2828d25298f70416d7610"]},"f6ab4108-a374-4fa6-81b2-61ca5078691f":{"id":"f6ab4108-a374-4fa6-81b2-61ca5078691f","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4788,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"74318ab4-90e3-4dd0-a21f-138a856b0c76":{"id":"74318ab4-90e3-4dd0-a21f-138a856b0c76","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4789,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"6c0b965a-f912-454e-9214-1fb23974ad2c":{"id":"6c0b965a-f912-454e-9214-1fb23974ad2c","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4790,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 5,000,000 USDS per day","contentHash":"9083d2802963d50df8b99c4a2b8891ca4febbc20317c0b9c1cef030a1ddc77d8","addressRefs":[]},"4abd5303-6a27-42fa-8128-4c6e65f089ee":{"id":"4abd5303-6a27-42fa-8128-4c6e65f089ee","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4791,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 5,000,000 fsUSDS per day","contentHash":"76162056a3a1678fb0869e9341ba56033ab0a7a61199862dfebef86081c8e302","addressRefs":[]},"ac2eb45f-a059-4dcc-9af4-baa1bbd60e3c":{"id":"ac2eb45f-a059-4dcc-9af4-baa1bbd60e3c","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4792,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"9eb37215-612f-45cd-a975-00683437326c":{"id":"9eb37215-612f-45cd-a975-00683437326c","doc_no":"A.6.1.1.1.2.6.1.3.3.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4793,"content":"The Instance follows the general ERC4626 procedures see [A.6.1.1.1.2.6.1.2.2.1.2.1.2.2 - ERC-4626 Functions](e386a0df-9e0b-4ffd-9879-49131f795b0b) and for emergency procedures see [A.6.1.1.1.2.6.1.2.2.3.4.1 - ERC-4626 Withdrawal Action](f92ddc3f-672a-4f52-931f-5263a9f709b9). For detailed example of the Spark Liquidity Layer interaction logic for depositing to, withdrawing from, and redeeming from this ERC4626 vault instance see [A.6.1.1.1.2.6.1.3.1.5.1.3.1 - Deposit ERC-4626 Tokens](e2ad525b-3f3f-4402-9e4d-3ae125b35b76) and [A.6.1.1.1.2.6.1.3.1.5.1.3.2 - Withdraw ERC-4626 Tokens](caa295f4-92f4-4ca9-9083-2a1b94c70d5f).","contentHash":"b89f6a6373effdd18fe878c76a39dd0a1275ab8b11159910da31ce93816f409d","addressRefs":[]},"014fccbf-4720-43f5-8dff-e58518c06f8c":{"id":"014fccbf-4720-43f5-8dff-e58518c06f8c","doc_no":"A.6.1.1.1.2.6.1.3.3.2","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4794,"content":"The Arbitrum Instances of the Aave Protocol with `Active` Status are stored herein.","contentHash":"5ba7b72ed5e3e67f79c9e345153bfe72849d5d73b124e466157ddedb7ab759b2","addressRefs":[]},"e11091aa-e569-4ca9-9151-dc5e1a8e1062":{"id":"e11091aa-e569-4ca9-9151-dc5e1a8e1062","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1","title":"Arbitrum - Aave USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4795,"content":"The documents herein contain the Instance Configuration Document for the Aave USDC Instance.","contentHash":"c53d92914c7bde414efcfa56d67a653348c2e4f531417f18f5b567f6730380eb","addressRefs":[]},"25631831-853b-489f-b41a-2647ada595d6":{"id":"25631831-853b-489f-b41a-2647ada595d6","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4796,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"3aadca43-40a6-4647-81c6-912edc9ccd94":{"id":"3aadca43-40a6-4647-81c6-912edc9ccd94","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4797,"content":"The documents herein define the parameters of the Aave USDC Instance of the Allocation System Primitive.","contentHash":"d73e9b183c5bb40a8587be90595c166c098b81e638e4e3c6d6c223b0d74ca7d9","addressRefs":[]},"2583e4c8-26d6-496f-99d6-30e0ece95dfa":{"id":"2583e4c8-26d6-496f-99d6-30e0ece95dfa","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4798,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"f1e00fd6-c833-409f-9386-54787628d17b":{"id":"f1e00fd6-c833-409f-9386-54787628d17b","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4799,"content":"Arbitrum","contentHash":"547ba9625e474ab7c414601027c59310d85a306d87edac8e7b86b39772010668","addressRefs":[]},"598df96f-6205-4149-a359-97bba4acae1c":{"id":"598df96f-6205-4149-a359-97bba4acae1c","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4800,"content":"Aave","contentHash":"65c4d784bc7c28c45f8106bfd470ca8b8c7c072efd28d90c06d56c790e8a1cfb","addressRefs":[]},"698f28fd-3186-42b0-a0cb-0ef6a4cf71e3":{"id":"698f28fd-3186-42b0-a0cb-0ef6a4cf71e3","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4801,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"e836034b-a658-45ff-bcbd-bc2ee3bc24e7":{"id":"e836034b-a658-45ff-bcbd-bc2ee3bc24e7","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4802,"content":"aArbUSDCn","contentHash":"8dd1e9daf9876273ecdf544a3abdeef9276848d90fb950173aacdaca49817780","addressRefs":[]},"14933ea3-8469-4538-a37a-4963723a2fd3":{"id":"14933ea3-8469-4538-a37a-4963723a2fd3","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4803,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"8768aad5-79b2-4e6d-a92b-6e1c654681a7":{"id":"8768aad5-79b2-4e6d-a92b-6e1c654681a7","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4804,"content":"`0x724dc807b04555b71ed48a6896b6F41593b8C637`","contentHash":"fb04d711559b964552801cdd3ca8d8273a928a5d71f3c2877d59b2529436b89f","addressRefs":["0x724dc807b04555b71ed48a6896b6f41593b8c637"]},"3fe18ab3-8f90-494e-8c8b-0b4218dd77f6":{"id":"3fe18ab3-8f90-494e-8c8b-0b4218dd77f6","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4805,"content":"`0xaf88d065e77c8cC2239327C5EDb3A432268e5831`","contentHash":"d934868715379ae9146a36a1668b4e070f481a7c06537019068a4e30da932ff9","addressRefs":["0xaf88d065e77c8cc2239327c5edb3a432268e5831"]},"aaf8a23e-ca02-4a8a-a75e-9431119b25bb":{"id":"aaf8a23e-ca02-4a8a-a75e-9431119b25bb","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.2.3","title":"Pool","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4806,"content":"This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"ea3c5d84119733fb3a2a429f279628dcce722f210f012ad0286de1cf9435e132","addressRefs":[]},"b89d0921-1a1f-4b1e-a074-4027c7ab19ea":{"id":"b89d0921-1a1f-4b1e-a074-4027c7ab19ea","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4807,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"2f22951b-c30c-47f9-a102-25a854c9a002":{"id":"2f22951b-c30c-47f9-a102-25a854c9a002","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4808,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"be3d1475-4efe-4eee-99eb-3f9941b858fa":{"id":"be3d1475-4efe-4eee-99eb-3f9941b858fa","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4809,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: 50,000,000 USDC per day","contentHash":"44a783f8f147a6a47a45e14e07a7d104980e8bce9854ecf047fb8e6622885ad5","addressRefs":[]},"254af84a-fe4c-471f-bc8c-dde31c728141":{"id":"254af84a-fe4c-471f-bc8c-dde31c728141","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4810,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: Unlimited","contentHash":"55f2afe4138f46e4ed73589852a0887ee907f02eb1fc355e4edab05a25597846","addressRefs":[]},"4a10347b-02ab-47f4-8a13-b2b526fde198":{"id":"4a10347b-02ab-47f4-8a13-b2b526fde198","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4811,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"d30527ea-821f-4c63-9f2a-3f13ff8064f7":{"id":"d30527ea-821f-4c63-9f2a-3f13ff8064f7","doc_no":"A.6.1.1.1.2.6.1.3.3.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4812,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes. For the general operational procedures applicable to all Aave-type instances. See [A.6.1.1.1.2.6.1.2.2.1.2.1.2.3 - Aave Functions](9922dcf0-4562-445b-9a46-712f677cce64) and [A.6.1.1.1.2.6.1.2.2.3.2.3 - Aave AToken Withdrawal Action](2560adbb-4a5c-4c95-86cb-04647bb33836). For detailed example of the Spark Liquidity Layer interaction logic for depositing to and withdrawing from Aave see [A.6.1.1.1.2.6.1.3.1.2.1.3.1 - Process Definition For Depositing](fa2520ac-4779-4aeb-abe4-2c1b89e7ca51) and [A.6.1.1.1.2.6.1.3.1.2.1.3.2 - Process Definition For Withdrawing](35e32620-a28c-4101-a881-2b7c2b9e42f2).","contentHash":"d385452e47622b373128e6db9a2e709cf0a3646ef911db13d7e85bdf747760d5","addressRefs":[]},"c7b4d92f-9fdf-4f86-9ec5-84d7ac5373ac":{"id":"c7b4d92f-9fdf-4f86-9ec5-84d7ac5373ac","doc_no":"A.6.1.1.1.2.6.1.3.4","title":"Avalanche","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4813,"content":"The Avalanche Instances of the Spark Liquidity Layer with `Active` Status are stored herein.","contentHash":"fa2b2a647c5c7dbd9e03627948433704e6400303e796ef90da58c2c5ae7afaa0","addressRefs":[]},"0a406127-5dc8-4d96-bc2e-4ba017d610bc":{"id":"0a406127-5dc8-4d96-bc2e-4ba017d610bc","doc_no":"A.6.1.1.1.2.6.1.3.4.1","title":"Aave","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4814,"content":"The Avalanche Instances of the Aave Protocol with `Active` Status are stored herein.","contentHash":"4e1350ed0e1aea44873984201a85d25896c7e6dea50aa8f43a26190852230513","addressRefs":[]},"ae06054a-1ed8-410b-983d-1789b49f1f19":{"id":"ae06054a-1ed8-410b-983d-1789b49f1f19","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1","title":"Avalanche - Aave v3 USDC Vault Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4815,"content":"The documents herein contain the Instance Configuration Document for the Avalanche Aave v3 USDC Instance.","contentHash":"be3732480add760ea416ade45b4c3687072fb5625a5d2020caf8072c0fedc057","addressRefs":[]},"787a0db5-15a1-4220-97df-040647747a2f":{"id":"787a0db5-15a1-4220-97df-040647747a2f","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4816,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"bf0b9e14-f89d-45d8-83f7-09fd7fa596d4":{"id":"bf0b9e14-f89d-45d8-83f7-09fd7fa596d4","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4817,"content":"The documents herein define the parameters of the Avalanche Aave v3 USDC Vault Instance of the Allocation System Primitive.","contentHash":"7879909aae38ec3f5581d6b926b7000b2708e2c3f54deb2d2a5efebac786d882","addressRefs":[]},"6567b399-126a-4b42-8716-8d899809990e":{"id":"6567b399-126a-4b42-8716-8d899809990e","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4818,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"8abad2b7-1efd-4e48-b2fc-009dd299d4b4":{"id":"8abad2b7-1efd-4e48-b2fc-009dd299d4b4","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4819,"content":"Avalanche","contentHash":"40515202399d262e23ee7fca28b5d73627d96f30bb61c6d064100070976e4fa9","addressRefs":[]},"1cb748ac-2e03-4d8e-89f2-17b8c935a37a":{"id":"1cb748ac-2e03-4d8e-89f2-17b8c935a37a","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4820,"content":"Aave","contentHash":"65c4d784bc7c28c45f8106bfd470ca8b8c7c072efd28d90c06d56c790e8a1cfb","addressRefs":[]},"56593e5a-8e0b-42af-b8bd-a041e9a4999e":{"id":"56593e5a-8e0b-42af-b8bd-a041e9a4999e","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4821,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"f3579a1a-b94e-48ea-96ec-f44b2d706278":{"id":"f3579a1a-b94e-48ea-96ec-f44b2d706278","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4822,"content":"aAvaxUSDC","contentHash":"7f4c3c75fc721785a2d23e23698c4c0813c6bcbe01362d19381076e1c88b0f22","addressRefs":[]},"f0cd090b-7754-4436-8760-1491421fbee1":{"id":"f0cd090b-7754-4436-8760-1491421fbee1","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4823,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"ea787215-4911-47e3-a9dc-e6b3f16f6e47":{"id":"ea787215-4911-47e3-a9dc-e6b3f16f6e47","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4824,"content":"`0x625E7708f30cA75bfd92586e17077590C60eb4cD`","contentHash":"8bcfb47f43e5dc3554685d46dd0a9a2939dbbaa5ff39a5f05bf9fe5f45ddb5c6","addressRefs":["0x625e7708f30ca75bfd92586e17077590c60eb4cd"]},"494409b0-468f-4abb-b634-9f26d02f2bbe":{"id":"494409b0-468f-4abb-b634-9f26d02f2bbe","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4825,"content":"`0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E`","contentHash":"974d33f0ae152877034995c7f4480ca851dd613133d1a0abf5a2436c9029fc59","addressRefs":["0xb97ef9ef8734c71904d8002f8b6bc66dd9c48a6e"]},"6c79b029-bc6b-42b4-8689-c13c8105cad9":{"id":"6c79b029-bc6b-42b4-8689-c13c8105cad9","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4826,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"fef37e25ee6ae99b46a1e7920573dc23171ba7812ee156dde99b1069994255d3","addressRefs":[]},"8e6dc8bd-4276-400a-9525-1c4e057727cf":{"id":"8e6dc8bd-4276-400a-9525-1c4e057727cf","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4827,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"ae6e143b-db94-46c3-b42f-96d73a0e2c0a":{"id":"ae6e143b-db94-46c3-b42f-96d73a0e2c0a","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4828,"content":"The inflow rate limits are:\n\n- `maxAmount`: 20,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"cf80a0fd3d7fdba53afedd890f0d3941238500d22175edce5386542841387cf2","addressRefs":[]},"e3c0527d-368e-4c8c-bf7f-47ffb010f54c":{"id":"e3c0527d-368e-4c8c-bf7f-47ffb010f54c","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4829,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"569b0f886c9aedda81b4e87d26e1e21d96763dd2e909e2e9865edcf064b320e5","addressRefs":[]},"6f06f814-58ff-4978-b8e8-67848cae9290":{"id":"6f06f814-58ff-4978-b8e8-67848cae9290","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4830,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"8364da67-b040-4b71-9ef9-57c83f43cede":{"id":"8364da67-b040-4b71-9ef9-57c83f43cede","doc_no":"A.6.1.1.1.2.6.1.3.4.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4831,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes. For the general operational procedures applicable to all Aave-type instances. See Aave Functions and Aave AToken Withdrawal Action. For detailed example of the Spark Liquidity Layer interaction logic for depositing to and withdrawing from Aave see Process Definition For Depositing and Process Definition For Withdrawing.","contentHash":"82cab0ce6daa528f824bc1590fb91fd29f280be73e2ae4605ddbb6356ffc0906","addressRefs":[]},"3224ce80-1f48-48d9-b0d3-058aebb4723c":{"id":"3224ce80-1f48-48d9-b0d3-058aebb4723c","doc_no":"A.6.1.1.1.2.6.1.3.4.2","title":"Spark Savings V2","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4832,"content":"The Avalanche Instances of the Spark Savings v2 with `Active` Status are stored herein.","contentHash":"489c17b711499028568a1bb98b8500c3ed03cd10982b99cdb269f43961b0337a","addressRefs":[]},"afa35a43-18e2-4084-b36c-eb584f4749ac":{"id":"afa35a43-18e2-4084-b36c-eb584f4749ac","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1","title":"Avalanche - Spark Savings v2 USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4833,"content":"The documents herein contain the Instance Configuration Document for the Spark Savings v2 USDC Instance.","contentHash":"1f50d1c544708b0b1ae82c8cc72471a857f0919ef86431f59c6362204247be5e","addressRefs":[]},"6cdcf295-4999-4c30-8f72-1a840a40c10e":{"id":"6cdcf295-4999-4c30-8f72-1a840a40c10e","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4834,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"30cde382-587d-4cf2-b6a5-44918086131a":{"id":"30cde382-587d-4cf2-b6a5-44918086131a","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4835,"content":"The documents herein define the parameters of the Spark Savings v2 USDC Instance of the Allocation System Primitive.","contentHash":"90c485fb7dfe8776cf51d2ac32c359c0bf05de84ce7b0679074f0d26df3e460b","addressRefs":[]},"6487fdd4-c5a7-458e-8117-6cb0645674f7":{"id":"6487fdd4-c5a7-458e-8117-6cb0645674f7","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4836,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"ea9193c5-209b-464a-bfb5-5de47965f8c5":{"id":"ea9193c5-209b-464a-bfb5-5de47965f8c5","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4837,"content":"Avalanche","contentHash":"40515202399d262e23ee7fca28b5d73627d96f30bb61c6d064100070976e4fa9","addressRefs":[]},"dbee4fe8-546f-4e9f-bd11-a27c5309b148":{"id":"dbee4fe8-546f-4e9f-bd11-a27c5309b148","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4838,"content":"Spark Savings Protocol","contentHash":"ddf2cdda69c7d7d4d4ccba4cd3dd7f3deb1cca801180b93f57a14ca43a802f16","addressRefs":[]},"fc1b9adf-616f-413b-9aa8-1977f30cdaea":{"id":"fc1b9adf-616f-413b-9aa8-1977f30cdaea","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.1.3","title":"Asset Supplied By Users","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4839,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"eda065b2-4338-42b1-aafb-bd297ccc8645":{"id":"eda065b2-4338-42b1-aafb-bd297ccc8645","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4840,"content":"spUSDC","contentHash":"a61b2e3fb9c87e9d690350f9c017c4828dceaccb7d7f2c7e156a5139615620b3","addressRefs":[]},"e251ec36-6483-48f0-a78a-1d392c9f0c81":{"id":"e251ec36-6483-48f0-a78a-1d392c9f0c81","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4841,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"32e9d09c-1f8c-44b8-a281-f51a68351d41":{"id":"32e9d09c-1f8c-44b8-a281-f51a68351d41","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4842,"content":"`0x28B3a8fb53B741A8Fd78c0fb9A6B2393d896a43d`","contentHash":"20054e939006558c3e8dbbacda78e7884a9ef21d8dcd8d53dfedc749921f9093","addressRefs":["0x28b3a8fb53b741a8fd78c0fb9a6b2393d896a43d"]},"f6168c84-306f-4f20-afd6-fd24e84d405e":{"id":"f6168c84-306f-4f20-afd6-fd24e84d405e","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4843,"content":"`0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E`","contentHash":"974d33f0ae152877034995c7f4480ca851dd613133d1a0abf5a2436c9029fc59","addressRefs":["0xb97ef9ef8734c71904d8002f8b6bc66dd9c48a6e"]},"fb1032d9-61da-4bde-83b5-1410a53342d5":{"id":"fb1032d9-61da-4bde-83b5-1410a53342d5","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4844,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"fef37e25ee6ae99b46a1e7920573dc23171ba7812ee156dde99b1069994255d3","addressRefs":[]},"bc158ad0-debd-4f56-af7e-d0655772f693":{"id":"bc158ad0-debd-4f56-af7e-d0655772f693","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4845,"content":"The specific `maxAmount` and `slope` for this conduit's inflow/outflow are not defined for this Instance.","contentHash":"7a7beff7b4c6ecb868851425e1b215b313106005b011131a0944d74e97d2d9fe","addressRefs":[]},"382b30d4-e315-4622-b084-8b2ede0f37cd":{"id":"382b30d4-e315-4622-b084-8b2ede0f37cd","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4846,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"5bba533c-caff-47b4-8236-06421a44533e":{"id":"5bba533c-caff-47b4-8236-06421a44533e","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4847,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"4df29394-5d9c-41ab-be95-886ea4b6f488":{"id":"4df29394-5d9c-41ab-be95-886ea4b6f488","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4848,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer parameters.","contentHash":"954c398dca3897ac411e5ef7cec752742ba5c7ef64d821ab346a38d5c0bf4502","addressRefs":[]},"e6135b1d-16f8-4c3f-97fb-c811eae22ce2":{"id":"e6135b1d-16f8-4c3f-97fb-c811eae22ce2","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.1","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4849,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"ae89c0a6-c7a9-4c53-81b9-6cf980747ace":{"id":"ae89c0a6-c7a9-4c53-81b9-6cf980747ace","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.1.1","title":"Spark Vault v2 Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4850,"content":"`0xC2C0582D1cCe30449cF561C7b9C4D6d527547F12`","contentHash":"bc17f9e04ed5be5b70953604917c048d0469b96676dcb4f3f8b7239ae152685e","addressRefs":["0xc2c0582d1cce30449cf561c7b9c4d6d527547f12"]},"13349fb3-57ed-4ab8-b1e3-18be5874c43c":{"id":"13349fb3-57ed-4ab8-b1e3-18be5874c43c","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.1.2","title":"Default admin","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4851,"content":"`0x7566DEbC906C17338524A414343fA61BcA26A843`","contentHash":"9ac4cca86088b853dc699e8ae7f017bd47df59e5fba2e8e9cfd3731aa9aadd7f","addressRefs":["0x7566debc906c17338524a414343fa61bca26a843"]},"5e5e0b85-842f-46fa-8124-6e272dd95351":{"id":"5e5e0b85-842f-46fa-8124-6e272dd95351","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.1.3","title":"Setter","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4852,"content":"`0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC`","contentHash":"a4be1caa48d1c4c87ad16384d3686b46723fadc9e7ac5bd267c2413470eeb82f","addressRefs":["0x2e1b01adabb8d4981863394bea23a1263cbaedfc"]},"a0b65455-b90d-43a1-bedd-5eb9f9c1378f":{"id":"a0b65455-b90d-43a1-bedd-5eb9f9c1378f","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.1.4","title":"Taker","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4853,"content":"`0xecE6B0E8a54c2f44e066fBb9234e7157B15b7FeC`","contentHash":"65f25119c6e33f8d8fcf879d242c2161e42a9f51a15f5222aed8fb04ec078c8e","addressRefs":["0xece6b0e8a54c2f44e066fbb9234e7157b15b7fec"]},"668577c4-a21f-417f-aad0-95dddfc78fe2":{"id":"668577c4-a21f-417f-aad0-95dddfc78fe2","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.2","title":"Risk Parameters Current Configuration","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4854,"content":"The subdocuments herein define the current configuration of the risk parameters.","contentHash":"ae95706409030fd9a4186329c0ae2d52597b2b1e0c27b553b62ee8b3d7690a86","addressRefs":[]},"3d6a3fd3-4f36-45eb-9399-4eedfdc1c30d":{"id":"3d6a3fd3-4f36-45eb-9399-4eedfdc1c30d","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.2.1","title":"Spark Savings USDC Risk Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4855,"content":"The Risk parameters are:\n\n- Supply cap: 500,000,000 USDC\n- Max yield: 10%\n- Current yield (at launch): 0%","contentHash":"f5fc6fbe23c026bf1cd2bd97aa6ed95d365fd8f303bcc72dcb374c5b9b5d963b","addressRefs":[]},"2b911731-5f03-41b0-afbd-41af37e8646f":{"id":"2b911731-5f03-41b0-afbd-41af37e8646f","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.2.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4856,"content":"The current `maxAmount` for this conduit's take and transferAssets operations are defined in the subdocuments herein.","contentHash":"75b012e8bb8cfbabc557256dba223839a78a10ee18e841934ddae9f2475ba379","addressRefs":[]},"8507429b-f999-4990-825b-550ac91de996":{"id":"8507429b-f999-4990-825b-550ac91de996","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.2.3","title":"Take Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4857,"content":"The take rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"3426645201c930f3f055f6f9698d8cbca5aafe9562546059014160a4eef8e177","addressRefs":[]},"4c7311c4-a8fa-4bba-88f7-09abe67a8709":{"id":"4c7311c4-a8fa-4bba-88f7-09abe67a8709","doc_no":"A.6.1.1.1.2.6.1.3.4.2.1.4.2.4","title":"TransferAssets Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4858,"content":"The transferAssets rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"80a6f78822ec8b4de950e3d80005c47c2c7cdf94a6e9e18f343796d2d9f596a5","addressRefs":[]},"ed8c3394-ee05-496c-8dd6-4d5275d2ed1f":{"id":"ed8c3394-ee05-496c-8dd6-4d5275d2ed1f","doc_no":"A.6.1.1.1.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4859,"content":"The Instances of the Spark Liquidity Layer with `Completed` Status are stored herein.","contentHash":"d08096c00b9b6a884268f24ef2530d2f166cd59aecd1c9edee4da8ec1b70c1f7","addressRefs":[]},"ce83f39e-5efb-4a88-b27f-989083213239":{"id":"ce83f39e-5efb-4a88-b27f-989083213239","doc_no":"A.6.1.1.1.2.6.1.4.1","title":"Blackrock","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4860,"content":"The Ethereum Mainnet Instances of the Blackrock Protocol with `Completed` Status are stored herein.","contentHash":"dcd3371a2457ee9cb855490fdd1479c4bf523a75772bd14530f94f2f20130295","addressRefs":[]},"7a52fb87-96bf-4135-9a61-f2dc068af12c":{"id":"7a52fb87-96bf-4135-9a61-f2dc068af12c","doc_no":"A.6.1.1.1.2.6.1.4.1.1","title":"Ethereum Mainnet - Blackrock USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4861,"content":"The documents herein contain the Instance Configuration Document for the Blackrock USDC Instance.","contentHash":"4019665940a8aa159c6d2ed03986ecc093b967d4a4f6889977016cf69a14b813","addressRefs":[]},"704fd922-1700-4c0e-b182-e3ffe8741274":{"id":"704fd922-1700-4c0e-b182-e3ffe8741274","doc_no":"A.6.1.1.1.2.6.1.4.1.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4862,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"9f44d3eb-b1d4-490e-bab2-8f39b73dc6ad":{"id":"9f44d3eb-b1d4-490e-bab2-8f39b73dc6ad","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4863,"content":"The documents herein define the parameters of the Blackrock USDC Instance of the Allocation System Primitive","contentHash":"6c989ec06e22c0f509dcabbd8d4f76b8fc2df6563893291cc1244c1649d7cca3","addressRefs":[]},"fcee0621-3878-461c-8900-a55e62c90aeb":{"id":"fcee0621-3878-461c-8900-a55e62c90aeb","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4864,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"c667269d-b366-4a14-9861-e506d107a767":{"id":"c667269d-b366-4a14-9861-e506d107a767","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4865,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"10169c03-bbd8-40c2-990c-44ee2f5d436f":{"id":"10169c03-bbd8-40c2-990c-44ee2f5d436f","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4866,"content":"Blackrock","contentHash":"0cf18cf9e992f4e14fdde17d1cf0ce80b7b8535f82c25cb6b406256d899a407a","addressRefs":[]},"3215e3d7-850e-400a-adac-b57223c354c6":{"id":"3215e3d7-850e-400a-adac-b57223c354c6","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4867,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"892b7916-3ca3-4fd1-a8d2-732646ad7353":{"id":"892b7916-3ca3-4fd1-a8d2-732646ad7353","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4868,"content":"BUIDL-I","contentHash":"2317b6f4308e52f77b18de970c662272f0e32458f7f70f9754764426c2b99e12","addressRefs":[]},"1dd65da0-57e4-4cb4-bf6c-7885b0616ae2":{"id":"1dd65da0-57e4-4cb4-bf6c-7885b0616ae2","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4869,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"43930781-984c-4ba4-91e1-5e564fe448ad":{"id":"43930781-984c-4ba4-91e1-5e564fe448ad","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4870,"content":"`0x6a9DA2D710BB9B700acde7Cb81F10F1fF8C89041`","contentHash":"b5f6899da4b07597ae9060770e2d13c3651c65b004e625293235ac117c1bdfaf","addressRefs":["0x6a9da2d710bb9b700acde7cb81f10f1ff8c89041"]},"284c77f5-ea1b-4569-a4f4-9241cf338f9b":{"id":"284c77f5-ea1b-4569-a4f4-9241cf338f9b","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4871,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"43f9fa01-68a2-4c8f-b1f4-fe775927562e":{"id":"43f9fa01-68a2-4c8f-b1f4-fe775927562e","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4872,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow is:\n\n- `BUIDLI_DEPOSIT`: `0xD1917664bE3FdAea377f6E8D5BF043ab5C3b1312`\n- `BUIDL_REDEEM` (Circle redeem): `0x31D3F59Ad4aAC0eeE2247c65EBE8Bf6E9E470a53`\n- `BUIDLI_REDEEM` (Offchain redeem): `0x8780Dd016171B91E4Df47075dA0a947959C34200`","contentHash":"e6aa19dce3ecbe97e3677921632747bf3ec3276882fb9887083727c0aa6da40b","addressRefs":["0x31d3f59ad4aac0eee2247c65ebe8bf6e9e470a53","0x8780dd016171b91e4df47075da0a947959c34200","0xd1917664be3fdaea377f6e8d5bf043ab5c3b1312"]},"3a9acb95-b227-4473-aa26-95b7f25cfd8a":{"id":"3a9acb95-b227-4473-aa26-95b7f25cfd8a","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4873,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"4ec7ede8-416b-486e-ba56-160b02189a7b":{"id":"4ec7ede8-416b-486e-ba56-160b02189a7b","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4874,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"a21333a57e9e7bcbb8854ab9a6a741a8b9596662216cf1b25bb7ba48b23c3f4f","addressRefs":[]},"1fc9d6f3-3996-4245-a096-53dad4a624ea":{"id":"1fc9d6f3-3996-4245-a096-53dad4a624ea","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4875,"content":"The outflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"f86f9b8db49561115373b94ce3c5597ef57303406aa4653493a0f3808edf7859","addressRefs":[]},"dd3dffeb-7157-46dc-bf65-f5c8d5bf9fc8":{"id":"dd3dffeb-7157-46dc-bf65-f5c8d5bf9fc8","doc_no":"A.6.1.1.1.2.6.1.4.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4876,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"ddd37d10-75dd-4de4-a88b-b92745fd53bc":{"id":"ddd37d10-75dd-4de4-a88b-b92745fd53bc","doc_no":"A.6.1.1.1.2.6.1.4.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4877,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"8fb735f7-7d36-4b35-9e9a-19b645674517":{"id":"8fb735f7-7d36-4b35-9e9a-19b645674517","doc_no":"A.6.1.1.1.2.6.1.4.2","title":"Centrifuge","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4878,"content":"The Ethereum Mainnet Instances of the Centrifuge Protocol with `Completed` Status are stored herein.","contentHash":"df353ecd1163b379198b4bdb14971912f1eb134422d6e51e709ca6027e549a13","addressRefs":[]},"289555ee-996e-43a7-b05f-a0b06d1238f5":{"id":"289555ee-996e-43a7-b05f-a0b06d1238f5","doc_no":"A.6.1.1.1.2.6.1.4.2.1","title":"Ethereum Mainnet - Centrifuge USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4879,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge USDC Instance.","contentHash":"364646491b5395cc2b2ec18bab8b825ea5f081e688147606d2272b3848b5085a","addressRefs":[]},"c9a19386-f124-49bc-aca1-6860293395f3":{"id":"c9a19386-f124-49bc-aca1-6860293395f3","doc_no":"A.6.1.1.1.2.6.1.4.2.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4880,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"35533e6c-2d70-4cba-8192-95a150f93e9c":{"id":"35533e6c-2d70-4cba-8192-95a150f93e9c","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4881,"content":"The documents herein define the parameters of the Centrifuge USDC Instance of the Allocation System Primitive.","contentHash":"68f827aee9ff1bac53d88a78ff1fd22fbad75166493eb3e2d59c3924babd6850","addressRefs":[]},"1ba05a79-f768-45e8-ae14-bb04495e6f6c":{"id":"1ba05a79-f768-45e8-ae14-bb04495e6f6c","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4882,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"c10013b3-c688-4a97-8a5c-44c56d9ef481":{"id":"c10013b3-c688-4a97-8a5c-44c56d9ef481","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4883,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"1c386cce-adee-4f5a-aa88-7c84f0709a70":{"id":"1c386cce-adee-4f5a-aa88-7c84f0709a70","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4884,"content":"Centrifuge","contentHash":"15a808e2563fe8cc5805166b2619e590c1f1e9c1b0d43c0b85783ad6dc26b9dc","addressRefs":[]},"8eb1c7a9-18a7-46bf-841d-2db3476bf8ea":{"id":"8eb1c7a9-18a7-46bf-841d-2db3476bf8ea","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.1.3","title":"Asset Supplied By Spark Liquidity Layer","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4885,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"aaa19944-a11f-43e3-8ddf-25e8ab357d97":{"id":"aaa19944-a11f-43e3-8ddf-25e8ab357d97","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4886,"content":"JTRSY","contentHash":"a5435fae1627abed97fa9fff2bc126b9fa56b41fa129c9ce2c4e07c41c58f5aa","addressRefs":[]},"538be44e-fe35-4f33-83de-613713f0b674":{"id":"538be44e-fe35-4f33-83de-613713f0b674","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4887,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"75405fc4-d493-410d-b036-dc7f67242ca3":{"id":"75405fc4-d493-410d-b036-dc7f67242ca3","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4888,"content":"`0x8c213ee79581Ff4984583C6a801e5263418C4b86`","contentHash":"9c11681c4a39570279026209b5683b7d47ab2e2d4ef46f930949b046522f286c","addressRefs":["0x8c213ee79581ff4984583c6a801e5263418c4b86"]},"8e1a1625-29e0-46d0-ac50-d43b40c4c79d":{"id":"8e1a1625-29e0-46d0-ac50-d43b40c4c79d","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4889,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"3cd3c96e-b459-468f-a7be-f5c52c38666e":{"id":"3cd3c96e-b459-468f-a7be-f5c52c38666e","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4890,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Spark Artifact.","contentHash":"2861c03527d9eec86e8350164ef50d3f7fec6949e1e46e970c7c58f96b981f46","addressRefs":[]},"e5519b29-8100-4490-965b-a616729865e1":{"id":"e5519b29-8100-4490-965b-a616729865e1","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4891,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"81ab5665-f9b9-4363-9d05-0d7bf371394a":{"id":"81ab5665-f9b9-4363-9d05-0d7bf371394a","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4892,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"a21333a57e9e7bcbb8854ab9a6a741a8b9596662216cf1b25bb7ba48b23c3f4f","addressRefs":[]},"997c0581-022d-4fdd-8fde-cb43d58c8940":{"id":"997c0581-022d-4fdd-8fde-cb43d58c8940","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4893,"content":"The outflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Spark Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Spark Artifact.","contentHash":"f86f9b8db49561115373b94ce3c5597ef57303406aa4653493a0f3808edf7859","addressRefs":[]},"5ab63d35-c3d1-4ea6-924c-2d56bcd68295":{"id":"5ab63d35-c3d1-4ea6-924c-2d56bcd68295","doc_no":"A.6.1.1.1.2.6.1.4.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4894,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"d14420a3-4b36-4eac-bb1b-04f5598fe347":{"id":"d14420a3-4b36-4eac-bb1b-04f5598fe347","doc_no":"A.6.1.1.1.2.6.1.4.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4895,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Spark Liquidity Layer processes.","contentHash":"37cd43d9b3300d5d84a7b6552a34c2f0cbc87f21381e8e99823d85326d481c9c","addressRefs":[]},"5b1ce161-fc9e-4c90-ac14-75cfbba6a213":{"id":"5b1ce161-fc9e-4c90-ac14-75cfbba6a213","doc_no":"A.6.1.1.1.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4896,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.6.1.3 - Active Instances](f7c9fdda-3d42-4b9d-852d-610d7ae4f6c0).","contentHash":"be9554ee99fde5a1b44f3bdc54644acbea61696cdebac9d5da9479973d399281","addressRefs":[]},"0ffbf052-9a57-430a-a140-40666dc2548b":{"id":"0ffbf052-9a57-430a-a140-40666dc2548b","doc_no":"A.6.1.1.1.2.6.1.6","title":"Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4897,"content":"The documents herein contain data relevant to the Spark Liquidity Layer.","contentHash":"028f5690b719f4338926598add2c639c56fd3681200af002b35e5a16d22aa03a","addressRefs":[]},"bef153ea-bce0-4f87-aea1-be1ed219b0c1":{"id":"bef153ea-bce0-4f87-aea1-be1ed219b0c1","doc_no":"A.6.1.1.1.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4898,"content":"The documents herein contain all data and specifications for Spark’s Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"aadb052bd3111f2633ec289d5a4ca73154d5e4bac3e6e769d0eef5d5eaea0403","addressRefs":[]},"760db109-8209-4993-aa0f-a472cd09342f":{"id":"760db109-8209-4993-aa0f-a472cd09342f","doc_no":"A.6.1.1.1.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4899,"content":"The documents herein organize all base information relevant to Spark’s usage of the Junior Risk Capital Rental Primitive.","contentHash":"0561cd632fe26697ba7cb7ed21a3f5a09086165ad477d236b38f1e54bb67ef27","addressRefs":[]},"f677430e-d241-4697-afb7-3375ab33f901":{"id":"f677430e-d241-4697-afb7-3375ab33f901","doc_no":"A.6.1.1.1.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4900,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"cdd934f4-7607-4447-873a-2b08618d50b5":{"id":"cdd934f4-7607-4447-873a-2b08618d50b5","doc_no":"A.6.1.1.1.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4901,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"064dec5f-e008-450a-80b9-098dd49a06bc":{"id":"064dec5f-e008-450a-80b9-098dd49a06bc","doc_no":"A.6.1.1.1.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4902,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"0e18ffbc-b51b-4a25-a60a-b4b8ba61580b":{"id":"0e18ffbc-b51b-4a25-a60a-b4b8ba61580b","doc_no":"A.6.1.1.1.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4903,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.6.2.1.2 - Active Instances Directory](cdd934f4-7607-4447-873a-2b08618d50b5), whereas failed Invocations are Archived in [A.6.1.1.1.2.6.2.1.5 - Hub Data Repository](073af9bf-c7df-41ab-93cc-798f972134a3).","contentHash":"f03bd7b52cc2f8ae59ef88af8f1e02597c4e5ce9ca27cd08a55847f031ad692f","addressRefs":[]},"073af9bf-c7df-41ab-93cc-798f972134a3":{"id":"073af9bf-c7df-41ab-93cc-798f972134a3","doc_no":"A.6.1.1.1.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4904,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"93185aa4-1770-4649-b9b8-a570a3f6b2e8":{"id":"93185aa4-1770-4649-b9b8-a570a3f6b2e8","doc_no":"A.6.1.1.1.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4905,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"b9d396f1-e40c-4ec7-9855-852ae94e51ca":{"id":"b9d396f1-e40c-4ec7-9855-852ae94e51ca","doc_no":"A.6.1.1.1.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4906,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"505bd7a0-19e8-4b67-acb0-cf007114dd6c":{"id":"505bd7a0-19e8-4b67-acb0-cf007114dd6c","doc_no":"A.6.1.1.1.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4907,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"a9dfa35d-e51d-43ee-aa07-90c96a6acb86":{"id":"a9dfa35d-e51d-43ee-aa07-90c96a6acb86","doc_no":"A.6.1.1.1.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4908,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"6fab7906-d1dd-4291-9044-10eecd2c65d0":{"id":"6fab7906-d1dd-4291-9044-10eecd2c65d0","doc_no":"A.6.1.1.1.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4909,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"17e60d50-f521-4634-a732-ecface0953ca":{"id":"17e60d50-f521-4634-a732-ecface0953ca","doc_no":"A.6.1.1.1.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4910,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.6.2.2 - Active Instances](a9dfa35d-e51d-43ee-aa07-90c96a6acb86).","contentHash":"067c5ece9d231097d141c4f717769206f318063667bfb57dbaac2e016dd00071","addressRefs":[]},"9f627e5c-f56e-42a3-abf9-1bce25e7d1ba":{"id":"9f627e5c-f56e-42a3-abf9-1bce25e7d1ba","doc_no":"A.6.1.1.1.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4911,"content":"The documents herein contain all data and specifications for Spark’s Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"0cdcc2cfaf503023025812185ed5d00e9dda58d0ce4c731126bcdf6fd6582ed5","addressRefs":[]},"45974478-1591-4d54-9aae-e68a9b6f8793":{"id":"45974478-1591-4d54-9aae-e68a9b6f8793","doc_no":"A.6.1.1.1.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4912,"content":"The documents herein organize all base information relevant to Spark’s usage of the Asset Liability Management Rental Primitive.","contentHash":"50f48e01ee57bf02cc2c1dc3e1edbbe2f5ff38d70a05e90536246de2f7db26c4","addressRefs":[]},"8eece156-6d42-4cf3-88ec-0080b82be855":{"id":"8eece156-6d42-4cf3-88ec-0080b82be855","doc_no":"A.6.1.1.1.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4913,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"22456b6d-8106-48dd-ab8f-b6c5feec643a":{"id":"22456b6d-8106-48dd-ab8f-b6c5feec643a","doc_no":"A.6.1.1.1.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4914,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"197dc003-e809-49dd-85f3-8286f304e70f":{"id":"197dc003-e809-49dd-85f3-8286f304e70f","doc_no":"A.6.1.1.1.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4915,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"5e84e500-7b2b-42ae-b23e-34fad4d9aa57":{"id":"5e84e500-7b2b-42ae-b23e-34fad4d9aa57","doc_no":"A.6.1.1.1.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4916,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.6.3.1.2 - Active Instances Directory](22456b6d-8106-48dd-ab8f-b6c5feec643a), whereas failed Invocations are Archived in [A.6.1.1.1.2.6.3.1.5 - Hub Data Repository](ea4f687a-7c81-41bd-918a-7f4d56120f43).","contentHash":"dda10783630eec4abea56cca342b65aca1fc34c203fc63724e189153206d3018","addressRefs":[]},"ea4f687a-7c81-41bd-918a-7f4d56120f43":{"id":"ea4f687a-7c81-41bd-918a-7f4d56120f43","doc_no":"A.6.1.1.1.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4917,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e1c20a8c-f154-4680-95d4-5776281fd1d2":{"id":"e1c20a8c-f154-4680-95d4-5776281fd1d2","doc_no":"A.6.1.1.1.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4918,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"d4c34da2-6c80-461a-a156-7ca0ad76ef0c":{"id":"d4c34da2-6c80-461a-a156-7ca0ad76ef0c","doc_no":"A.6.1.1.1.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4919,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"06cc0973-28bf-48de-a5af-4438ea8a76fa":{"id":"06cc0973-28bf-48de-a5af-4438ea8a76fa","doc_no":"A.6.1.1.1.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4920,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"cdb5065b-0a14-4cf8-a0ac-d6b547ee0994":{"id":"cdb5065b-0a14-4cf8-a0ac-d6b547ee0994","doc_no":"A.6.1.1.1.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4921,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"25ce8d32-f425-4769-9de3-60c5517f1ab1":{"id":"25ce8d32-f425-4769-9de3-60c5517f1ab1","doc_no":"A.6.1.1.1.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4922,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"203386d2-3c59-4edd-aece-4d8034a2a08f":{"id":"203386d2-3c59-4edd-aece-4d8034a2a08f","doc_no":"A.6.1.1.1.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4923,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.6.3.2 - Active Instances](cdb5065b-0a14-4cf8-a0ac-d6b547ee0994).","contentHash":"96ee55c46ab15f472429db52570ae774c8f4ed5c6fd6a95205084e575686caa3","addressRefs":[]},"a0865261-677f-4cbf-a409-df6ac29d6e29":{"id":"a0865261-677f-4cbf-a409-df6ac29d6e29","doc_no":"A.6.1.1.1.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4924,"content":"The documents herein implement the Core Governance Primitives for Spark. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"e8b67610868cedc540b479104703a86114d47e1556435ca7f6299fa767cb7a44","addressRefs":[]},"5d111751-fac3-495e-8829-ce849c28aac8":{"id":"5d111751-fac3-495e-8829-ce849c28aac8","doc_no":"A.6.1.1.1.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4925,"content":"The documents herein contain all data and specifications for Spark’s Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"961983fb2b5579d55a31ed02ed3c848af88920718cc6d7f199a050d417d7450d","addressRefs":[]},"88a9d7aa-be82-4f4b-bb86-7eb9748c64ee":{"id":"88a9d7aa-be82-4f4b-bb86-7eb9748c64ee","doc_no":"A.6.1.1.1.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4926,"content":"The documents herein organize all base information relevant to Spark’s usage of the Core Governance Reward Primitive.","contentHash":"eb153e6c0a285ac3335d050a4b72bbb52fb6fd8bcf640e169ab80a167cf5e61b","addressRefs":[]},"85326b8b-a790-4b68-be43-2fff907bbf75":{"id":"85326b8b-a790-4b68-be43-2fff907bbf75","doc_no":"A.6.1.1.1.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4927,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"f4c484c7-e2e6-4d7c-ab60-6154e6c44fcd":{"id":"f4c484c7-e2e6-4d7c-ab60-6154e6c44fcd","doc_no":"A.6.1.1.1.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4928,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"46fcc70f-f3a8-4a6d-ba36-985b0adfda11":{"id":"46fcc70f-f3a8-4a6d-ba36-985b0adfda11","doc_no":"A.6.1.1.1.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4929,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"777f68a6-2248-44e5-9386-e6d4105498a4":{"id":"777f68a6-2248-44e5-9386-e6d4105498a4","doc_no":"A.6.1.1.1.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4930,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.1.2.7.1.1.2 - Active Instances Directory](f4c484c7-e2e6-4d7c-ab60-6154e6c44fcd), whereas failed Invocations are Archived in [A.6.1.1.1.2.7.1.1.5 - Hub Data Repository](b8e04127-ab44-4b58-b122-d85532138b13).","contentHash":"fdc0049c6c272ef0fc1b369c8242e9478e1e92997e88feb80de1a25a5ddc4708","addressRefs":[]},"b8e04127-ab44-4b58-b122-d85532138b13":{"id":"b8e04127-ab44-4b58-b122-d85532138b13","doc_no":"A.6.1.1.1.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4931,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"c214c982-d058-4cc5-b8f9-024d5ca5dea7":{"id":"c214c982-d058-4cc5-b8f9-024d5ca5dea7","doc_no":"A.6.1.1.1.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4932,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"e9d454c5-88b2-491e-bba0-206f2ca987a9":{"id":"e9d454c5-88b2-491e-bba0-206f2ca987a9","doc_no":"A.6.1.1.1.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4933,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"7f3c7c95-5759-4fd7-891b-60841b98df86":{"id":"7f3c7c95-5759-4fd7-891b-60841b98df86","doc_no":"A.6.1.1.1.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4934,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"1f638b59-eff7-4d69-870c-487f2728b188":{"id":"1f638b59-eff7-4d69-870c-487f2728b188","doc_no":"A.6.1.1.1.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4935,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"ffe6fa8d-4fb7-4cb3-8dda-328387613987":{"id":"ffe6fa8d-4fb7-4cb3-8dda-328387613987","doc_no":"A.6.1.1.1.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4936,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"7aae676b-55ba-4001-9a03-e9112f9bd94c":{"id":"7aae676b-55ba-4001-9a03-e9112f9bd94c","doc_no":"A.6.1.1.1.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"1bc21199-26d0-4cdd-8d66-454ac62204b9","order":4937,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.1.2.7.1.2 - Active Instances](1f638b59-eff7-4d69-870c-487f2728b188).","contentHash":"327475185408ad893415973625e22fb095f0b2bdf796c8ba0022a82fb25bc49e","addressRefs":[]},"f5ba2aec-ac1b-4da9-adc9-e1d370620e72":{"id":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","doc_no":"A.6.1.1.1.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"dee2f5a4-279a-488c-9a9d-9583e3216fbf","order":4938,"content":"The documents herein define Spark’s strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"524fb4415ff2f339e12541b68aa543888ea80d8b4815f4b59664e8fc7a9c554b","addressRefs":[]},"3dffc0f5-edbc-48e9-bf13-7d752a64de5a":{"id":"3dffc0f5-edbc-48e9-bf13-7d752a64de5a","doc_no":"A.6.1.1.1.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4939,"content":"The documents herein specify Spark governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Spark Artifact is specified in the Root Edit Primitive above at [A.6.1.1.1.2.2.2 - Root Edit Primitive](f60887de-a4eb-4e4b-8aa6-e22cf724772a).","contentHash":"5e103b8b4f1c4f63478c2f99bebe6e51314f2a4af8595ea019461885298f4b6c","addressRefs":[]},"978879a2-3f8b-4f3e-a938-07e8a5b4b4de":{"id":"978879a2-3f8b-4f3e-a938-07e8a5b4b4de","doc_no":"A.6.1.1.1.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4940,"content":"Spark uses the Sky Forum for governance-related discussion. Posts should use the \"Spark Prime\" category.","contentHash":"6a08576c8066d8fcc69281da116178e52b3e72184b03e713d12f6eec11cbe1fc","addressRefs":[]},"e7118615-bbaa-4a3d-b395-407244cc0969":{"id":"e7118615-bbaa-4a3d-b395-407244cc0969","doc_no":"A.6.1.1.1.3.1.2","title":"Discord","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4941,"content":"Spark also uses Discord for more immediate communication. The Spark Discord is located at [https://t.co/v6zG0MZtak](https://t.co/v6zG0MZtak).","contentHash":"2eecdaa3c816ddcdffc2439ead750ef0f42415d901933eb24e5ed59837ef2c05","addressRefs":[]},"afa6a37e-e7f1-4efb-bca7-f02bbbf5cf26":{"id":"afa6a37e-e7f1-4efb-bca7-f02bbbf5cf26","doc_no":"A.6.1.1.1.3.1.3","title":"Delegation Framework","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4942,"content":"The documents herein specify Spark’s governance delegation system, defining the rights and duties of Delegates and Delegators, as well as the processes for onboarding and offboarding Delegates.","contentHash":"c1a42fbbc807416e07fcffbf95d527c3e6ead1c74a4144f1db5ae89638be0f27","addressRefs":[]},"f667b5fa-0e31-4e59-9cfe-85c31c9f0b84":{"id":"f667b5fa-0e31-4e59-9cfe-85c31c9f0b84","doc_no":"A.6.1.1.1.3.1.3.1","title":"Delegate Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4943,"content":"A \"Delegate\" is a recognized actor empowered to exercise governance voting power on behalf of one or more SPK holders (\"Delegators\"). Delegates act as trusted representatives and are expected to vote in the long-term best interest of the Spark ecosystem.","contentHash":"4f6839c0d6d990dff98c13846c8c7fe987594469589cff92c393c2a15029bb85","addressRefs":[]},"7fcbb9da-7559-4a18-ab68-f0840a3fe921":{"id":"7fcbb9da-7559-4a18-ab68-f0840a3fe921","doc_no":"A.6.1.1.1.3.1.3.2","title":"How Delegation Works","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4944,"content":"SPK holders may assign (\"delegate\") the full voting power of their wallet to an Active Delegate at any time (see [A.6.1.1.1.3.1.3.8 - Registry of Delegates](f49a1e26-f774-4fbd-b7f8-156639e077f2)). The key features of delegation are specified in the subdocuments herein.","contentHash":"300d7b9b3841ae8a21fbae2185223cbc737175c0c859a6f84efd94aca128b772","addressRefs":[]},"e5ad866a-9d53-472e-bff5-077d06e8171f":{"id":"e5ad866a-9d53-472e-bff5-077d06e8171f","doc_no":"A.6.1.1.1.3.1.3.2.1","title":"Interfaces","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4945,"content":"Delegation can be executed through (i) the Spark App or (ii) directly on Spark’s Snapshot page.","contentHash":"451d2efb3b91e9da7623261391f18f9b119b36c77075850025acbf51675bb898","addressRefs":[]},"99c40e7d-2033-4ca2-bf8d-a2f4a8556b0d":{"id":"99c40e7d-2033-4ca2-bf8d-a2f4a8556b0d","doc_no":"A.6.1.1.1.3.1.3.2.2","title":"Snapshot Voting-Power Lock","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4946,"content":"A snapshot records voting power at each proposal snapshot-block height. Voting power (including delegations) cannot be altered for the duration of a specific active proposal. Changes in voting power are reflected in future votes.","contentHash":"fa28b7dd9ab07929eaf69016e9124d5dc7e95a7767801cbc1b1a17fc23e37e44","addressRefs":[]},"375d4774-24f8-4f19-9b00-1a9043891b70":{"id":"375d4774-24f8-4f19-9b00-1a9043891b70","doc_no":"A.6.1.1.1.3.1.3.2.3","title":"Undelegation & Re-delegation","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4947,"content":"Delegators may revoke or move their delegation whenever no proposal is live. All changes take effect at the next snapshot-block.","contentHash":"a5c87b75b2242856d85d58fc4a30d14d83eb012af4627945fb1f26d6690be87f","addressRefs":[]},"64fd2894-944b-41a3-bfaa-435035bfd257":{"id":"64fd2894-944b-41a3-bfaa-435035bfd257","doc_no":"A.6.1.1.1.3.1.3.2.4","title":"Restrictions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4948,"content":"SPK holders may only assign their voting power to Active Delegates. This also means Delegators cannot delegate to another wallet they themselves control, unless it is an Active Delegate wallet.","contentHash":"4dbfc2c8e3255f422c47c76769f43135ef1f84ec7c1b55754b117e5317c037a7","addressRefs":[]},"f230ba4e-eb5a-444e-b07a-13a0292338bd":{"id":"f230ba4e-eb5a-444e-b07a-13a0292338bd","doc_no":"A.6.1.1.1.3.1.3.3","title":"Delegate Responsibilities","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4949,"content":"The responsibilities for Delegates are defined in the subdocuments herein.","contentHash":"f57f75fcbff7370fc4004470a4d7f13e144701efe66d8db7549f413fd3ab61f9","addressRefs":[]},"3a662279-94d2-469e-b4c8-256b998a1b35":{"id":"3a662279-94d2-469e-b4c8-256b998a1b35","doc_no":"A.6.1.1.1.3.1.3.3.1","title":"Monitor Governance Channels","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4950,"content":"The Delegate must track the Sky Forum (\"Spark Prime\" category), Discord, and any other official communication venues for new proposals and discussions.","contentHash":"926f53c8e8fe1c714b3a1e52228e9075fd5c1106b38e7749657e632f7fbf0cb8","addressRefs":[]},"e494b7ff-22ae-40cf-8ce5-c285dd6a63ea":{"id":"e494b7ff-22ae-40cf-8ce5-c285dd6a63ea","doc_no":"A.6.1.1.1.3.1.3.3.2","title":"Review Proposals Thoroughly","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4951,"content":"The Delegate must evaluate technical, economic, and risk implications before voting.","contentHash":"7719faefd5bbc8184f84622db14a4b50f3e930e55f0486f2e0d8bb3137fdc4e9","addressRefs":[]},"46e9d0bb-e251-4f07-8327-804456f2e68a":{"id":"46e9d0bb-e251-4f07-8327-804456f2e68a","doc_no":"A.6.1.1.1.3.1.3.3.3","title":"Vote on Every Proposal","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4952,"content":"The Delegate must cast a vote (For / Against) on 100% of governance proposals within the designated voting window (see [A.6.1.1.1.2.2.2.2.1.2.1.4 - Root Edit Token Holder Vote](b60cfc4e-4cc5-4040-9610-f2113980831b)).","contentHash":"758437795b46af47de87928b34619ad4af20682ebc06be085d06e7a07f272819","addressRefs":[]},"16eb44b8-0a93-4138-a11a-99e654727b90":{"id":"16eb44b8-0a93-4138-a11a-99e654727b90","doc_no":"A.6.1.1.1.3.1.3.3.4","title":"Abstain Only for Disclosed Conflicts","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4953,"content":"The \"Abstain\" option may be used solely in cases where the Delegate has a documented conflict of interest for the specific proposal.","contentHash":"0f96967ed34f48ca134958d18c5b818a742e104b9ea87a8b4ec7f0fdbf8772fd","addressRefs":[]},"cfdf3c2d-6ede-49f0-8f2c-0cd91a5602bc":{"id":"cfdf3c2d-6ede-49f0-8f2c-0cd91a5602bc","doc_no":"A.6.1.1.1.3.1.3.3.4.1","title":"Disclosure Of Conflicts","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4954,"content":"Conflicts must be disclosed to both the Spark Foundation before the voting window (see [A.6.1.1.1.2.2.2.2.1.2.1.4 - Root Edit Token Holder Vote](b60cfc4e-4cc5-4040-9610-f2113980831b)) for the proposal begins.","contentHash":"638f80fc652b3ce8057276f223057e8b6bee37eaf49319a75834a142e98fc5c9","addressRefs":[]},"4d8ad5e6-937e-4916-ad8b-8d7e74a93542":{"id":"4d8ad5e6-937e-4916-ad8b-8d7e74a93542","doc_no":"A.6.1.1.1.3.1.3.3.4.2","title":"Abstaining For Non-Disclosed Conflicts","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4955,"content":"Abstaining for any reason other than a disclosed conflict is treated as non-performance under [A.6.1.1.1.3.1.3.5 - Delegate Offboarding](b49d9086-cb8a-43f7-a024-0d3320eae317).","contentHash":"1e79b28d61568c3de3a663a4a22f14eab12ff29db53981e98a611644620acb28","addressRefs":[]},"683bd4a6-b07a-4ed0-85dc-2f6d0f13bc6e":{"id":"683bd4a6-b07a-4ed0-85dc-2f6d0f13bc6e","doc_no":"A.6.1.1.1.3.1.3.3.5","title":"Report Rationale","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4956,"content":"The Delegate must post a concise rationale for each vote on the proposal thread.","contentHash":"b99a83dfeb26aa949d415d22f66fae584030bd04e6ee70a7a95770ee2b333025","addressRefs":[]},"6b2f76c8-3486-45f9-a79a-feae8b9117c0":{"id":"6b2f76c8-3486-45f9-a79a-feae8b9117c0","doc_no":"A.6.1.1.1.3.1.3.3.6","title":"Maintain Independence","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4957,"content":"The Delegate must disclose conflicts of interest and abstain where impartiality is compromised (see [A.6.1.1.1.3.1.3.3.4.1 - Disclosure Of Conflicts](cfdf3c2d-6ede-49f0-8f2c-0cd91a5602bc)). Failure to meet these obligations is grounds for offboarding (see [A.6.1.1.1.3.1.3.5 - Delegate Offboarding](b49d9086-cb8a-43f7-a024-0d3320eae317)).","contentHash":"dc6152899a1bf2f8deb3fb77c61e348bb8dd078b54529561f25991a546130494","addressRefs":[]},"fcf62ce5-910a-4357-a3d5-959b3be37021":{"id":"fcf62ce5-910a-4357-a3d5-959b3be37021","doc_no":"A.6.1.1.1.3.1.3.4","title":"Delegate Onboarding","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4958,"content":"The Delegate onboarding process is specified in the subdocuments herein.","contentHash":"537a151aa9c38463551a405b746aeff82f50ea7805053b6afdcd3489448beeb8","addressRefs":[]},"d08b9b32-bce9-45f4-b8db-9301556ac8db":{"id":"d08b9b32-bce9-45f4-b8db-9301556ac8db","doc_no":"A.6.1.1.1.3.1.3.4.1","title":"Delegate Onboarding Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4959,"content":"The Spark Foundation manages Delegate onboarding. The Spark Foundation may onboard a Delegate at its discretion. Minimum onboarding requirements are (1) identity and contact information, (2) Delegate wallet address, and (3) a signed acceptance of [A.6.1.1.1.3.1.3.3 - Delegate Responsibilities](f230ba4e-eb5a-444e-b07a-13a0292338bd). The Spark Foundation conducts identity verification, conflict-of-interest collection, and sanctions and undue-risk checks as it deems necessary. Upon acceptance, the Foundation notifies the Operational Facilitator, who updates [A.6.1.1.1.3.1.3.8 - Registry of Delegates](f49a1e26-f774-4fbd-b7f8-156639e077f2) and posts a notice on the Sky Forum.","contentHash":"6ddf136c3547ddcfebd967bd93ebf063493af661f87127d3a55b29c1457b5270","addressRefs":[]},"1bc894fc-f8d1-450b-9829-15a4a5b707c3":{"id":"1bc894fc-f8d1-450b-9829-15a4a5b707c3","doc_no":"A.6.1.1.1.3.1.3.4.2","title":"Application Requirements","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4960,"content":"Prospective Delegates must submit (i) identity & contact info, (ii) delegate wallet address, and (iii) a signed statement accepting the responsibilities in [A.6.1.1.1.3.1.3.3 - Delegate Responsibilities](f230ba4e-eb5a-444e-b07a-13a0292338bd). These requirements are further specified in the subdocuments herein.","contentHash":"9f601d5340fff4c2fdc7cc5b956bb0c00cf8c156acfce09b01c7f5d1983d64b4","addressRefs":[]},"2d7744d1-80ca-41b8-af6b-79d7ae3e89bd":{"id":"2d7744d1-80ca-41b8-af6b-79d7ae3e89bd","doc_no":"A.6.1.1.1.3.1.3.4.2.1","title":"Requirement To Verify Identity","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4961,"content":"Every prospective Delegate must complete an initial, confidential identity verification process with the Spark Foundation, subject to additional KYC verification as necessary in the future. Delegates may remain anonymous or pseudonymous to the public.","contentHash":"691112d863c8213b1357691062861743aa6210c383d55138207cefbb3aa5162d","addressRefs":[]},"d27d5d53-9ebc-45af-a755-f83e03dccdf7":{"id":"d27d5d53-9ebc-45af-a755-f83e03dccdf7","doc_no":"A.6.1.1.1.3.1.3.4.2.2","title":"Conflict-of-Interest Disclosure","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4962,"content":"At onboarding, prospective Delegates must provide any known conflicts of interest to the Spark Foundation. Disclosures must be updated as new conflicts arise.","contentHash":"14b5b607887956ecb46bd8d6e96ba1b59a86a6cc8109bd094ef56475f7eb8538","addressRefs":[]},"912f59c2-7aea-4ce6-b3ee-137102fc80b7":{"id":"912f59c2-7aea-4ce6-b3ee-137102fc80b7","doc_no":"A.6.1.1.1.3.1.3.4.2.3","title":"Eligibility","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4963,"content":"Individuals or entities listed on any international sanctions list are ineligible to serve as Delegates. In addition, a prospective Delegate may be deemed ineligible if, in the Spark Foundation’s sole discretion, their participation would be unlawful or would pose undue risk to Spark.","contentHash":"e93f8e0d10d23d621b884e6e65290f352ed14570d777ff5a5bc9e497891fcf2e","addressRefs":[]},"88f9aebd-8182-41be-ab0f-1003188bfad9":{"id":"88f9aebd-8182-41be-ab0f-1003188bfad9","doc_no":"A.6.1.1.1.3.1.3.4.2.4","title":"Ongoing Compliance","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4964,"content":"Delegates must promptly update the Spark Foundation on any material change in their legal status. Failure to do so results in automatic suspension until rectified.","contentHash":"b5e546244b71f393d255d292da1e75a2d2e19f8f76ef605ac271f03082226db6","addressRefs":[]},"1b98f386-689d-4935-a994-46c598415c23":{"id":"1b98f386-689d-4935-a994-46c598415c23","doc_no":"A.6.1.1.1.3.1.3.4.2.5","title":"Grounds for Disqualification","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4965,"content":"Submission of fraudulent information, criminal indictment for financial crime, or repeated governance negligence (see [A.6.1.1.1.3.1.3.5.2 - Non-Performance Removal](ca90a844-23e2-4741-aa76-97dd1092370d)) triggers an SRC-initiated Delegate Removal vote.","contentHash":"227fb5ad8770b0ba7f12536342333a6d26687c68f38f529c9961b1e9e91e2cdc","addressRefs":[]},"6dd2ed9e-7b1a-4b03-901f-51d29c19e8a4":{"id":"6dd2ed9e-7b1a-4b03-901f-51d29c19e8a4","doc_no":"A.6.1.1.1.3.1.3.4.2.6","title":"Application Does Not Guarantee Acceptance","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4966,"content":"Submission of a Delegate Application does not guarantee acceptance. Acceptance is at the Spark Foundation's sole discretion. The Spark Foundation may approve or deny any application at any time, for any reason or no stated reason including legal, sanctions, risk, operational, or capacity considerations even if the applicant satisfies the minimum requirements in [A.6.1.1.1.3.1.3.4.2 - Application Requirements](1bc894fc-f8d1-450b-9829-15a4a5b707c3). The Spark Foundation is not required to provide individualized rationale. Decisions are final unless otherwise provided in this Artifact.","contentHash":"7221e3d3c61e637b8ffbc0942e585a246092a3ef9195cf51d900275a612129f5","addressRefs":[]},"c612d4e4-96c4-4ccf-a830-7f742338cfd9":{"id":"c612d4e4-96c4-4ccf-a830-7f742338cfd9","doc_no":"A.6.1.1.1.3.1.3.4.3","title":"Minimum Term","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4967,"content":"Effective upon approval of this proposal, Delegates are appointed by the Spark Foundation to fixed six (6) month terms aligned to calendar half-years (January 1–June 30; July 1–December 31). To continue beyond a term, a Delegate must be re-approved by the Spark Foundation prior to term end; absent re-approval, the Delegate is automatically offboarded at term end pursuant to [A.6.1.1.1.3.1.3.5.5 - Term-End Automatic Offboarding](02deeacc-5305-4a08-a5aa-2aabeb5591be).\n\nTransition. Delegates serving prior to approval are automatically rolled over into this structure and deemed approved through June 30, 2026. For the avoidance of doubt, there will be no re-approval on January 1, 2026; the first re-approval checkpoint is July 1, 2026 for all such Delegates.","contentHash":"3c2f2ed474f516be0c196e32c6068e6cf20edb43b6ef4cec94c848c836b9486c","addressRefs":[]},"708a614c-115e-470c-b076-52834422ebc9":{"id":"708a614c-115e-470c-b076-52834422ebc9","doc_no":"A.6.1.1.1.3.1.3.4.4","title":"Delegate Record","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4968,"content":"Accepted Delegates are appended to [A.6.1.1.1.3.1.3.8 - Registry of Delegates](f49a1e26-f774-4fbd-b7f8-156639e077f2).","contentHash":"bc97fa109ff81ca54ff6fedb067a813785117eeaac440cdf880db561988034a7","addressRefs":[]},"b49d9086-cb8a-43f7-a024-0d3320eae317":{"id":"b49d9086-cb8a-43f7-a024-0d3320eae317","doc_no":"A.6.1.1.1.3.1.3.5","title":"Delegate Offboarding","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4969,"content":"The delegation offboarding process is specified in the subdocuments herein.","contentHash":"0d727cb9d3e3d196d555a157e492791cbeadb2265d3814396d4fd5166cd5fd4a","addressRefs":[]},"8606cdec-f7c2-44af-befb-c702d2ed4735":{"id":"8606cdec-f7c2-44af-befb-c702d2ed4735","doc_no":"A.6.1.1.1.3.1.3.5.1","title":"Voluntary Offboarding","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4970,"content":"A Delegate can voluntarily offboard by submitting a resignation message in the Spark Prime category of Sky Forum with a signed message from their Delegate wallet as proof. The offboarding takes effect immediately after all active proposals conclude.","contentHash":"2aaaf6fc3df067bf91c6d0993c3483fee8ded817dc7d1e971ac85bc8557e2d09","addressRefs":[]},"ca90a844-23e2-4741-aa76-97dd1092370d":{"id":"ca90a844-23e2-4741-aa76-97dd1092370d","doc_no":"A.6.1.1.1.3.1.3.5.2","title":"Non-Performance Removal","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4971,"content":"A Delegate is automatically offboarded if they:\n\n- Fail to vote on ≥ 3 proposals in a row; or\n- Maintain a voting percentage less than 85%.","contentHash":"ca9aa8934143e6af805907bff3a85bd832e6c7dd9506565e1bd72b273657957c","addressRefs":[]},"b016a208-3fce-4429-aea8-381fe6d4fb28":{"id":"b016a208-3fce-4429-aea8-381fe6d4fb28","doc_no":"A.6.1.1.1.3.1.3.5.3","title":"Emergency Removal","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4972,"content":"The Spark Risk Council can immediately offboard a delegate if they:\n\n- Breach disclosure / conflict-of-interest duties;\n- Engage in malicious or negligent conduct; or\n- Fail to provide acceptable KYC or updated KYC when requested.","contentHash":"6059350a1222cee4dbb42b209724504c0ac8f7a10645fbfd2cf4632330dfe1ba","addressRefs":[]},"a80aee08-2be5-419f-999c-44749fcf6a18":{"id":"a80aee08-2be5-419f-999c-44749fcf6a18","doc_no":"A.6.1.1.1.3.1.3.5.4","title":"Updating of Status","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4973,"content":"Upon offboarding, the Delegate’s status in [A.6.1.1.1.3.1.3.8 - Registry of Delegates](f49a1e26-f774-4fbd-b7f8-156639e077f2) is updated to Inactive. SPK delegators must manually revoke their delegations and redelegate if they wish to continue participating in Spark governance.","contentHash":"32ca86fdcfc7a40e25b0716c8af3e7bd3338b95c744dbb6a381115891c418317","addressRefs":[]},"02deeacc-5305-4a08-a5aa-2aabeb5591be":{"id":"02deeacc-5305-4a08-a5aa-2aabeb5591be","doc_no":"A.6.1.1.1.3.1.3.5.5","title":"Term-End Automatic Offboarding","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4974,"content":"At the end of a Delegate's six (6) month term (see [A.6.1.1.1.3.1.3.4.3 - Minimum Term](c612d4e4-96c4-4ccf-a830-7f742338cfd9)), if the Spark Foundation has not recorded a re-approval, the Delegate is automatically offboarded effective 00:00 UTC on the day after term end. The Operational Facilitator updates the Registry and posts a notice on the Sky Forum.","contentHash":"b65fd134bca88616f15a684a536bdd18b78ad5682c7f640e919c678985bbac11","addressRefs":[]},"5e38acbd-f010-4bd1-af6c-acdd17b3e9e9":{"id":"5e38acbd-f010-4bd1-af6c-acdd17b3e9e9","doc_no":"A.6.1.1.1.3.1.3.6","title":"Incentives & Compensation","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4975,"content":"Delegates are compensated for their service as follows:\n\n1. Compensation Amount. Active Delegates receive USD 4,000 per calendar month.\n2. Administration. The Spark Foundation administers compensation from its approved operating budget.\n3. Timing & Proration. The compensation structure goes into effect by December 1st 2025, with first payment being made January 2026. Payment is made monthly in arrears and prorated for partial months of service.\n4. Eligibility & Clawback. Payment requires the Delegate to be in good standing and to have met responsibilities in [A.6.1.1.1.3.1.3.3 - Delegate Responsibilities](f230ba4e-eb5a-444e-b07a-13a0292338bd) during the covered period; the Spark Foundation may withhold or claw back amounts for non-performance or breach.\n5. No Waiver of Oversight. Compensation does not limit or waive any onboarding, renewal, or offboarding requirements.","contentHash":"1df4ea53b8414ff98356a7bf984667d50b91d47d3a22504adaed5032c7fea923","addressRefs":[]},"8ab7950c-c347-41a1-bf53-ef4d77000af5":{"id":"8ab7950c-c347-41a1-bf53-ef4d77000af5","doc_no":"A.6.1.1.1.3.1.3.7","title":"Security Requirements & Compromise Procedure","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4976,"content":"The security requirements and procedure for a compromised key are specified in the subdocuments herein.","contentHash":"504d52b468c1cf4877a4b31a25888f156a41d7a92b3a592ac774147f196a79e7","addressRefs":[]},"b5d668cd-5f19-4660-8846-8293126c5a57":{"id":"b5d668cd-5f19-4660-8846-8293126c5a57","doc_no":"A.6.1.1.1.3.1.3.7.1","title":"Operational Security","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4977,"content":"Delegates must:\n\n- Sign votes from a hardware wallet or an equivalent secure device.\n- Use unique signing keys that are never reused for personal transactions.\n- Enable Multi-Factor Authentication on any platform accounts used for governance communication.","contentHash":"9bdcb3ed9ec2ae998abf17b601d9d4dcd3f695d85d7dd498f3e8781dd6a0bd45","addressRefs":[]},"05dbbbcc-7702-4d17-a222-9c93356be7cd":{"id":"05dbbbcc-7702-4d17-a222-9c93356be7cd","doc_no":"A.6.1.1.1.3.1.3.7.2","title":"Compromised Key Response","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4978,"content":"If a Delegate suspects key compromise, the following steps must be taken:\n\n- The Delegate must notify the SRC as soon as the breach is discovered.\n- SRC flags the Delegate in Registry of Delegates as \"Suspended - Security Review\" and notifies the governance community on the Sky Forum. All voting power to the suspended address is annulled.\n- The Delegate may submit a new verified address; upon SRC approval, suspensions are lifted and delegations migrate at the next snapshot-block.","contentHash":"b2602507a59621191c38fdfc3778d0edf002c8c20416250bb4d852f6909a4259","addressRefs":[]},"e66be018-f2f2-4294-9357-be8ee6484e6c":{"id":"e66be018-f2f2-4294-9357-be8ee6484e6c","doc_no":"A.6.1.1.1.3.1.3.7.3","title":"Non-Compliance","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4979,"content":"Failure to execute the steps in [A.6.1.1.1.3.1.3.7.2 - Compromised Key Response](05dbbbcc-7702-4d17-a222-9c93356be7cd) within 48 hours constitutes grounds for emergency removal.","contentHash":"789e822185239af9af15af094ee0d2ca35b3c1a40f57e7e8000617369d0c0cea","addressRefs":[]},"f49a1e26-f774-4fbd-b7f8-156639e077f2":{"id":"f49a1e26-f774-4fbd-b7f8-156639e077f2","doc_no":"A.6.1.1.1.3.1.3.8","title":"Registry of Delegates","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4980,"content":"The subdocuments herein list each active Delegate’s name, wallet address, effective date, and status. Entries are maintained via an Active Data document updated by the Operational Facilitator.","contentHash":"d25b4e2cb18d4a23ca3148f0813ecc8669324a8414b3cb1fa26a1ff707a6bdf9","addressRefs":[]},"6067e262-d4c3-40ee-af02-f3c69bf19b2f":{"id":"6067e262-d4c3-40ee-af02-f3c69bf19b2f","doc_no":"A.6.1.1.1.3.1.3.8.1","title":"Template Information For Each Delegate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4981,"content":"The list of Delegates must follow this template for each recorded Delegate:\n\n[Insert Delegate Handle]\n\n- Delegate Name: [Insert Handle]\n- Delegate Wallet Address:\n- Effective Date:\n- Status: Active/Inactive/Suspended","contentHash":"ba66c053ea2bc177ac696f2b3aad6667cf99e3fbd0f3eeefe4855d39e630f2e3","addressRefs":[]},"7802904e-51fd-4308-ae9f-5f4595eca3e5":{"id":"7802904e-51fd-4308-ae9f-5f4595eca3e5","doc_no":"A.6.1.1.1.3.1.3.8.2","title":"Updating List of Delegates","type":"Active Data Controller","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4982,"content":"The list of Delegates is defined as Active Data in [A.6.1.1.1.3.1.3.8.2.0.6.1 - List of Delegates](daa90217-00f4-4579-bc6d-cacb6afc70dc).\n\nThe Active Data is updated as follows:\n\n- Responsible Party: Operational Facilitator.\n- Trigger: Receipt of onboarding, renewal/re-approval, term-end automatic offboarding, or discretionary offboarding notice from the Spark Foundation.\n- Update Process: Direct Edit.\n- Publication: The Operational Facilitator posts a notice on the Sky Forum.","contentHash":"ff2d7305cf3b5d416615c7118f3341f2448b388e661c85003a54623d00d55ed2","addressRefs":[]},"daa90217-00f4-4579-bc6d-cacb6afc70dc":{"id":"daa90217-00f4-4579-bc6d-cacb6afc70dc","doc_no":"A.6.1.1.1.3.1.3.8.2.0.6.1","title":"List of Delegates","type":"Active Data","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4983,"content":"The information for each Delegate is listed below:\n\n- Remi\n    - Delegate Name: Remi\n    - Delegate Wallet Address: `0xDC5D4228a42880F5bbd577A184035503Bd55799a`\n    - Effective Date: 2025-08-21\n    - Status: Active\n- NeoNode\n    - Delegate Name: NeoNode\n    - Delegate Wallet Address: `0x71faa03C0cEbCbB53236763B6b118aD906d9F6d3`\n    - Effective Date: 2025-08-21\n    - Status: Active\n- TheMoon\n    - Delegate Name: TheMoon\n    - Delegate Wallet Address: `0xF80A26ee68Bdf0224c18F85876b20858ee5206A9`\n    - Effective Date: 2026-01-14\n    - Status: Active","contentHash":"13d0c19bc20c372936248fed7c36b7f51b9511bb4ebcc7f607f837101ee04c86","addressRefs":["0x71faa03c0cebcbb53236763b6b118ad906d9f6d3","0xdc5d4228a42880f5bbd577a184035503bd55799a","0xf80a26ee68bdf0224c18f85876b20858ee5206a9"]},"57f6f628-dfc3-4819-8265-c85a38c0fc9f":{"id":"57f6f628-dfc3-4819-8265-c85a38c0fc9f","doc_no":"A.6.1.1.1.3.1.3.9","title":"Subject to Change","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4984,"content":"Spark reserves the right to vary or amend these terms at its discretion, subject to established Spark Artifact governance procedures related to Artifact edits.","contentHash":"60bc5c03136ab99e691749c047ebc3a189d13f9b3f25a55998156a4e3f882978","addressRefs":[]},"cf019fb3-d792-4867-abf7-cfe4d0b73e5d":{"id":"cf019fb3-d792-4867-abf7-cfe4d0b73e5d","doc_no":"A.6.1.1.1.3.1.4","title":"Spark Risk Council","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4985,"content":"The documents herein define the Spark Risk Council (SRC). The SRC safeguards the integrity and security of the Spark Ecosystem by conducting pre-vote risk reviews and, where necessary, preventing proposals from proceeding to a vote in order to protect Spark.","contentHash":"bda4b2ade84c8b5e411865ecd19aee59ae9e03db3c7ebd37adc9b4029928c561","addressRefs":[]},"b2a23ffe-34db-4793-87fd-a9fec45a5a35":{"id":"b2a23ffe-34db-4793-87fd-a9fec45a5a35","doc_no":"A.6.1.1.1.3.1.4.1","title":"Purpose And Mandate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4986,"content":"The SRC identifies, assesses, and mitigates technical, economic, and governance-process risks posed by proposals subject to Spark Governance. The SRC’s mandate is to inform the community of potential risks inherent in proposals and, where necessary, prevent proposals from proceeding that are malicious or likely to expose Spark to substantial, unreasonable risk.","contentHash":"1c3213459c889e9fd59f685ccfd2f427c016a0e6611a5706b8aa0f41044d16a9","addressRefs":[]},"b269ffa9-8abc-4b02-ba54-ecfde4d30549":{"id":"b269ffa9-8abc-4b02-ba54-ecfde4d30549","doc_no":"A.6.1.1.1.3.1.4.2","title":"Scope Of Review","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4987,"content":"The SRC reviews proposals for (i) security vulnerabilities and operational attack surface, (ii) market and treasury risks, (iii) economic risk, and (iv) misalignment with the Sky Core Atlas or the Spark Artifact. The SRC’s authority is limited to reviewing proposals within this scope.","contentHash":"17f2fa6c05c495e106cf5b24e022fb66e3358ca2b1dd64e1bd0d18d2587f4136","addressRefs":[]},"c586a7cc-a4d0-4c9b-9578-cbfe1f99a20e":{"id":"c586a7cc-a4d0-4c9b-9578-cbfe1f99a20e","doc_no":"A.6.1.1.1.3.1.4.3","title":"SRC Risk Review Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4988,"content":"The subdocuments herein clarify the process of the SRC independent risk review in terms of new Root Edit proposals. See [A.6.1.1.1.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](c9f7cc6e-0548-4599-9f9d-bfa1d2bb7577).","contentHash":"4ca0c9798eed849c1dd65a9055097ce096085a2f4f066f4b33770d0941821d64","addressRefs":[]},"968b4807-8032-42a3-b09d-f787cdb4ef87":{"id":"968b4807-8032-42a3-b09d-f787cdb4ef87","doc_no":"A.6.1.1.1.3.1.4.3.1","title":"SRC Risk Review","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4989,"content":"Within seven (7) days (based on the start of the weekly cycle) of a new Atlas Root Edit proposal, the SRC must conduct an independent risk review and post (i) a conclusion (\"Passed SRC Review,\" or \"Failed SRC Review\") and (ii) a stand-alone risk analysis to the relevant forum thread. Details for each of these deliverables are set out in the subdocuments herein.","contentHash":"c8f2756353275577fa8379348f04f1f001b95e4bbbba034adb55a000675a4ba6","addressRefs":[]},"e468575b-bb18-475c-aa82-7f7e9e80a576":{"id":"e468575b-bb18-475c-aa82-7f7e9e80a576","doc_no":"A.6.1.1.1.3.1.4.3.1.1","title":"SRC Risk Review Conclusion","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4990,"content":"The SRC conclusion must reflect the majority opinion of SRC members. However, individual SRC members are free to post dissenting or concurring opinions at their discretion. See [A.6.1.1.1.3.1.4.9.1 - Concurring Or Dissenting Opinions](fef5a280-76c8-402b-bbeb-7c6ca4fab0d5).","contentHash":"2ae7886344c06bbeb9b6317997e7b05722c330ddf0b9320b3cf6ff0d75e1beb2","addressRefs":[]},"6c82172a-bd7d-4aa7-8ff9-771cf166707b":{"id":"6c82172a-bd7d-4aa7-8ff9-771cf166707b","doc_no":"A.6.1.1.1.3.1.4.3.1.2","title":"SRC Risk Analysis","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4991,"content":"The SRC risk analysis must summarize key findings, assumptions, mitigations, and any monitoring plan.","contentHash":"2fda57ba1738ca21cffcf24f0d0374dbcebd687b74d4f842548ab95b7f3e3193","addressRefs":[]},"b67605fd-a381-4299-aac9-4e6ef1d54386":{"id":"b67605fd-a381-4299-aac9-4e6ef1d54386","doc_no":"A.6.1.1.1.3.1.4.3.2","title":"SRC Risk Review Extension","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4992,"content":"The SRC can formally request, at the Operational Facilitator’s discretion, an extension of the deadline of seven (7) days by posting a public justification for an extension in the Sky Forum.","contentHash":"1523c58e96deb7d9a237436c2b04d45b28e15ce21117202e37a887831c7a52a3","addressRefs":[]},"f55b35ba-1013-4a86-a874-feda7d750e45":{"id":"f55b35ba-1013-4a86-a874-feda7d750e45","doc_no":"A.6.1.1.1.3.1.4.3.3","title":"Failure To Review","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4993,"content":"If no SRC conclusion or request for extension is posted within seven (7) days of submission, the Operational Facilitator will move the proposal to the Snapshot voting phase, provided the proposal is aligned with the Sky Core Atlas and the Spark Artifact.","contentHash":"5c12320aa66940c0be7db5084632263eca704a884119be551ddf6c10e956cdc0","addressRefs":[]},"ac9d89b5-7a07-4b95-8597-6644bc4029ab":{"id":"ac9d89b5-7a07-4b95-8597-6644bc4029ab","doc_no":"A.6.1.1.1.3.1.4.4","title":"“Failed SRC Review” Authority and Procedure","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4994,"content":"The subdocuments herein set out the threshold, process and implications of a \"Failed SRC Review\" determination by the SRC.","contentHash":"feab3a658d6ed68e78e6fd8615426ac6efd1f22c6da37b0830cd278a77abbdf4","addressRefs":[]},"85633365-939a-44c4-8a55-aa17fa4a7809":{"id":"85633365-939a-44c4-8a55-aa17fa4a7809","doc_no":"A.6.1.1.1.3.1.4.4.1","title":"Standard","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4995,"content":"A determination of \"Failed SRC Review\" may be exercised when a proposal is determined to be:\n\n- malicious or exploitative;\n- procedurally non-compliant with the Sky Core Atlas or Spark Artifact;\n- likely to expose Spark to substantial, unreasonable risk; or\n- in need of revisions in order for the SRC to evaluate the proposal.","contentHash":"a21cd769594304e37e0a51210b719e358bbda69c62f0e611bc6ce614fceb8dff","addressRefs":[]},"0d0a0212-4439-4fb3-a8b2-77e53a1d60db":{"id":"0d0a0212-4439-4fb3-a8b2-77e53a1d60db","doc_no":"A.6.1.1.1.3.1.4.4.2","title":"Threshold","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4996,"content":"A determination of \"Failed SRC Review\" must reflect the majority opinion of SRC members.","contentHash":"2c971d99fa2042ef1727b5152d9a53006e37c44eedaf5181c366ef411b64bdf2","addressRefs":[]},"8be65dbb-1cba-453b-a2cf-d37e8a1f0b42":{"id":"8be65dbb-1cba-453b-a2cf-d37e8a1f0b42","doc_no":"A.6.1.1.1.3.1.4.4.3","title":"Failed SRC Review Notice","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4997,"content":"A \"Failed SRC Review\" notice must be posted on the Sky Forum in the relevant thread prior to the Snapshot voting window opening (or, if already posted, prior to closure).","contentHash":"c1f5b5dbf1e9d556a9f2b235d66b1c3ea9cf0507994cf844e87da3759b604a6f","addressRefs":[]},"bca3632c-eb40-4256-a430-51252f00f0e0":{"id":"bca3632c-eb40-4256-a430-51252f00f0e0","doc_no":"A.6.1.1.1.3.1.4.4.4","title":"Operational Facilitator Designation","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4998,"content":"The Operational Facilitator marks the proposal \"Failed SRC Review.\"","contentHash":"89cf34815a7110f03a846379350965bc3d291f16d9eb525d5880b2292b34be3a","addressRefs":[]},"1a81ade4-dc44-4272-adda-b2c3bbfc8554":{"id":"1a81ade4-dc44-4272-adda-b2c3bbfc8554","doc_no":"A.6.1.1.1.3.1.4.4.5","title":"Effect","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":4999,"content":"The proposal does not proceed to Snapshot (or is withdrawn).","contentHash":"2229c307884e0b20f885c60f2070d3925cdbfc4947478c149c5166ee15908293","addressRefs":[]},"e8b3fdc4-8e46-47b8-b2d3-3775b4436d21":{"id":"e8b3fdc4-8e46-47b8-b2d3-3775b4436d21","doc_no":"A.6.1.1.1.3.1.4.5","title":"Composition, Tenure, And Due Diligence","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5000,"content":"The subdocuments herein set out key details about the SRC, including their composition and appointment.","contentHash":"596560695130eb886abde1e6b50e0f20a23c747280fdf5500c7abbab20656f9b","addressRefs":[]},"bb276783-cf71-46a8-84f5-f85e99a25c97":{"id":"bb276783-cf71-46a8-84f5-f85e99a25c97","doc_no":"A.6.1.1.1.3.1.4.5.1","title":"Expertise","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5001,"content":"SRC members shall be domain experts across security, risk/economics, and operations.","contentHash":"de266b1c668da72a0ea4d57eca05080b9240cb08eeaa0f856e76a8c391059877","addressRefs":[]},"f9b6eb2f-ae02-4870-9470-be8065f7d90f":{"id":"f9b6eb2f-ae02-4870-9470-be8065f7d90f","doc_no":"A.6.1.1.1.3.1.4.5.2","title":"Seat Count","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5002,"content":"The SRC will have a seat count of three (3).","contentHash":"be836a2f4ef3ed879f7c2eafc22d57d671867952f050a75721a59cd35b0c5d89","addressRefs":[]},"83e078f3-b7a3-443c-b3fe-694b6806a999":{"id":"83e078f3-b7a3-443c-b3fe-694b6806a999","doc_no":"A.6.1.1.1.3.1.4.5.3","title":"Bootstrapping Phase","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5003,"content":"During the bootstrapping phase, initial members are appointed directly by the Operational Facilitator in consultation with the Spark Foundation through a public announcement on the Sky Forum. The Operational Facilitator shall either reappoint current SRC members to their seats or appoint new members in consultation with and with the consent of the Spark Foundation on an as-needed basis to allow the Operational Facilitator and the Spark Foundation flexibility during the initial governance procedures.\n\nAdditional procedures on future elections governing the appointment of SRC members voted upon by the community will be specified in a future iteration of the Spark Artifact.","contentHash":"f2ca3e9e7b64a06cabf92e174dfd87108a38972d9d334997c035a580482ab3e0","addressRefs":[]},"5350be2f-636a-47a5-aad3-071275bcc473":{"id":"5350be2f-636a-47a5-aad3-071275bcc473","doc_no":"A.6.1.1.1.3.1.4.5.4","title":"Coordinator","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5004,"content":"The Nested Contributor Phoenix Labs has a seat on the SRC as a non-voting coordinating member. The role of the coordinator is to facilitate the work of the SRC being done in a timely manner.","contentHash":"ad054238fbd6297e6ebfe0d7814a4c0601c3e7497f79a05d304186d9ec10b80f","addressRefs":[]},"b97dbb58-676c-434f-8973-2080102660c2":{"id":"b97dbb58-676c-434f-8973-2080102660c2","doc_no":"A.6.1.1.1.3.1.4.5.5","title":"Due Diligence","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5005,"content":"Members may be required to complete a confidential due diligence process, if the Spark Foundation deems it necessary.","contentHash":"93dccf790cec1c051b97f5e7d97fc5ae5af051b3ef397e87145224e8f65d72fe","addressRefs":[]},"3dddde86-989d-44ea-a2f4-7a1c26f9c844":{"id":"3dddde86-989d-44ea-a2f4-7a1c26f9c844","doc_no":"A.6.1.1.1.3.1.4.6","title":"Compensation","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5006,"content":"SRC members will receive compensation for performing their role on terms approved by the Spark Foundation.","contentHash":"7e7a7f0cb1317e9a7c62667e22f01e49067354d9f185368ec34464969237d965","addressRefs":[]},"3c6ed2b0-8ae1-4e3f-8f64-04ce2ae64e57":{"id":"3c6ed2b0-8ae1-4e3f-8f64-04ce2ae64e57","doc_no":"A.6.1.1.1.3.1.4.7","title":"Council Meetings","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5007,"content":"The subdocuments herein set out details about SRC meetings, including cadence and external participation.","contentHash":"ca300e12fe8e2f494c28eecbe74656925cb35e4a4d686a3b43fdf4aa5d737c0f","addressRefs":[]},"ea7b0884-c4f8-4272-af38-cdda387bb65f":{"id":"ea7b0884-c4f8-4272-af38-cdda387bb65f","doc_no":"A.6.1.1.1.3.1.4.7.1","title":"Cadence","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5008,"content":"The SRC shall hold a monthly internal governance meeting.","contentHash":"a475d298ac644a72bea587c9eb82e2c0d29e18ab273bb090618be7d4dfe5225b","addressRefs":[]},"440d1f15-915b-45b8-9bec-1ca5e32ea036":{"id":"440d1f15-915b-45b8-9bec-1ca5e32ea036","doc_no":"A.6.1.1.1.3.1.4.7.2","title":"Participants","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5009,"content":"In addition to SRC members, representatives of the Spark Foundation, Nested Contributor Phoenix Labs, and the Operational Facilitator are each permitted to attend in a coordinating and facilitating capacity.","contentHash":"9c716d34a3cee4360c404e5aaec991ffcd6204b34c5f4665137822f10c5970df","addressRefs":[]},"c139606c-f594-4dba-9afe-a32e2a2c64a1":{"id":"c139606c-f594-4dba-9afe-a32e2a2c64a1","doc_no":"A.6.1.1.1.3.1.4.8","title":"Mid-Term Appointments And Member Changes","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5010,"content":"The subdocuments herein set out the process for mid-term appointments and other out-of-schedule replacement rules.","contentHash":"f597fb8caa38c99c93560dfcc859732498d1c5c474695a8d9db37900758d92cc","addressRefs":[]},"123b69dc-c3ef-4143-b66a-485a2d526b1c":{"id":"123b69dc-c3ef-4143-b66a-485a2d526b1c","doc_no":"A.6.1.1.1.3.1.4.8.1","title":"Vacancies Mid-Term (Out-Of-Schedule Replacement Appointment)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5011,"content":"If a seat becomes vacant (resignation, removal, ineligibility, or failure to complete due diligence), the Operational Facilitator shall make an out-of-schedule replacement appointment. This process is defined in the subdocuments herein.","contentHash":"7704e7dfbcaee8d0c273edc806d0c83d7f960d928053d1a3812715b8ae7269ca","addressRefs":[]},"b7390f2a-9d24-4f1a-ac04-0db841a1bcd5":{"id":"b7390f2a-9d24-4f1a-ac04-0db841a1bcd5","doc_no":"A.6.1.1.1.3.1.4.8.1.1","title":"Notice","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5012,"content":"Within seven (7) days of the vacancy, the Operational Facilitator publishes a vacancy notice and forum thread on the Sky Forum describing the circumstances of the vacancy.","contentHash":"b05b06eefc389da9eb6e657a999adbc0e2598c3fb49db4694f738b03591dac59","addressRefs":[]},"aa27264b-865b-47bd-8de5-0731c772dae1":{"id":"aa27264b-865b-47bd-8de5-0731c772dae1","doc_no":"A.6.1.1.1.3.1.4.8.1.2","title":"Appointment","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5013,"content":"The Operational Facilitator shall appoint a replacement member of the SRC to fill the vacant seat in consultation with the Spark Foundation and publish a new post in the relevant forum thread in order to announce the appointment.","contentHash":"767280c213cb57a103e330c6115261b4a7b690541bf5f7af5de602470a7881ef","addressRefs":[]},"c7e40d3d-5485-426c-944a-16291fb36674":{"id":"c7e40d3d-5485-426c-944a-16291fb36674","doc_no":"A.6.1.1.1.3.1.4.8.1.3","title":"Term","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5014,"content":"The appointee is seated upon due diligence completion to the Spark Foundation’s satisfaction and update to the SRC Membership Registry and serves the remainder of the current term.","contentHash":"104c027e9406fc9068e92361703bd1e8c6fbc27f57e128276c76caed31fb555c","addressRefs":[]},"27bb6f28-1021-4c68-b435-36f32ce72bfa":{"id":"27bb6f28-1021-4c68-b435-36f32ce72bfa","doc_no":"A.6.1.1.1.3.1.4.8.1.4","title":"Seating And Continuity","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5015,"content":"Incumbent SRC members remain in office until successors are seated to ensure continuity of SRC operations. Newly appointed members are seated upon completion of due diligence to the Spark Foundation’s satisfaction and publication to the SRC Membership Registry.","contentHash":"91dd2a8e9134ec7bb53140d62f1e0b9686fabd56e460a40fbafde8f5d1627e5e","addressRefs":[]},"c1304ded-6912-472a-b836-cd7092262434":{"id":"c1304ded-6912-472a-b836-cd7092262434","doc_no":"A.6.1.1.1.3.1.4.9","title":"Process Requirements","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5016,"content":"The subdocuments herein set out key deliverables for the SRC as well as rules around conflicts of interest.","contentHash":"6bbce6bd2b9aaa5b1bb0bdf09c17336a41c6be682bf31547e07e55a4b66e5309","addressRefs":[]},"fef5a280-76c8-402b-bbeb-7c6ca4fab0d5":{"id":"fef5a280-76c8-402b-bbeb-7c6ca4fab0d5","doc_no":"A.6.1.1.1.3.1.4.9.1","title":"Concurring Or Dissenting Opinions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5017,"content":"In addition to the determinative independent risk review posted by the SRC for each proposal, individual SRC members may post concurring or dissenting opinions in the Sky Forum at their discretion.","contentHash":"d6c785228c2866569813f46abe7dd1e0bc282bae85d039d488ca543554557ee6","addressRefs":[]},"20d7297d-b100-438d-a535-6b9968b2bb43":{"id":"20d7297d-b100-438d-a535-6b9968b2bb43","doc_no":"A.6.1.1.1.3.1.4.9.2","title":"Conflicts Of Interest","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5018,"content":"SRC members must disclose conflicts of interest to Spark Foundation and recuse themselves where impartiality is compromised.","contentHash":"f43a7da93e61aa4c3bfeb7f6bd6cacc9c539383367262435ec81c76d56966f9f","addressRefs":[]},"4a07187f-9fc2-4a70-ae4b-919a4f52467d":{"id":"4a07187f-9fc2-4a70-ae4b-919a4f52467d","doc_no":"A.6.1.1.1.3.1.4.10","title":"Non-Performance","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5019,"content":"Repeated failure to meet review timelines; failure to document decisions; blocking valid proposals due to malicious intent or evident poor due diligence; or any other failure to uphold the duties of the SRC set forth in the Spark Artifact may trigger removal and replacement of SRC members at the discretion of the Spark Foundation.","contentHash":"c66d94fcdc6f1addf6bb84f485d5785baacdefa62952fa4a7c6e33975eec8be3","addressRefs":[]},"dc208bb2-ffb4-4a2a-b561-d563bc52eb14":{"id":"dc208bb2-ffb4-4a2a-b561-d563bc52eb14","doc_no":"A.6.1.1.1.3.1.4.11","title":"SRC Membership Registry Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5020,"content":"The subdocuments herein contain the registry of SRC members, including name or alias, domain expertise, verified governance address, start date, term status, and standing (Active / Recused / Removed). The registry is maintained via an Active Data document updated by the Operational Facilitator per the subdocuments herein.","contentHash":"1ae23fbc4a710a56f788f6c9332c79f4d860814d608dc33f8d817c091d58e5ff","addressRefs":[]},"066783d5-c191-4db7-a38a-5370a75944ee":{"id":"066783d5-c191-4db7-a38a-5370a75944ee","doc_no":"A.6.1.1.1.3.1.4.11.1","title":"Updating SRC Membership Registry","type":"Active Data Controller","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5021,"content":"The SRC Membership Registry is defined as Active Data in [A.6.1.1.1.3.1.4.11.1.0.6.1 - SRC Membership Registry List](d9c6ed16-5b0d-4a6f-bb43-387398090afc).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is the Operational Facilitator.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"cd44138bbf511a42f26e05d1ee73fa91cc51ed99a435d2f7fe91e98ec3cc150a","addressRefs":[]},"d9c6ed16-5b0d-4a6f-bb43-387398090afc":{"id":"d9c6ed16-5b0d-4a6f-bb43-387398090afc","doc_no":"A.6.1.1.1.3.1.4.11.1.0.6.1","title":"SRC Membership Registry List","type":"Active Data","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5022,"content":"The information for each member of the SRC is listed below:\n\n| Name or Alias        | Domain Expertise | Verified Governance Address | Start Date  | Term Status  | Standing |\n|----------------------|------------------|-----------------------------|-------------|--------------|----------|\n| Blockworks Advisory  | Risk             | N/A                         | 2025-10-03  | Active Term  | Active   |\n| L2 Beat              | Risk             | N/A                         | 2025-10-03  | Active Term  | Active   |\n| Aragon               | Risk             | N/A                         | 2025-10-03  | Active Term  | Active   |","contentHash":"54eda7daabbbf505c170ca729151757d09d31578787f9f61bc13bb4a0ee5c360","addressRefs":[]},"0483b49d-b074-4a98-bb4b-bc5d222dabf1":{"id":"0483b49d-b074-4a98-bb4b-bc5d222dabf1","doc_no":"A.6.1.1.1.3.1.5","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5023,"content":"The documents herein specify Spark’s emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Spark Artifact.","contentHash":"a7c9426d9326cb78208ec5c61fd02472021959716e24d14a28459eba9ab9b779","addressRefs":[]},"2d540356-97e0-431b-a03b-c3ec360e139b":{"id":"2d540356-97e0-431b-a03b-c3ec360e139b","doc_no":"A.6.1.1.1.3.1.6","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5024,"content":"The documents herein specify Spark’s emergency response protocol in situations solely impacting Spark versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Spark Artifact.","contentHash":"a0715ce279a1c2d3d3c9047a5fee1f7f7a2522c6425e3eb00dc3c4cfb362be1d","addressRefs":[]},"fd2f8da1-616b-4c4f-9d6e-bdd14131eca4":{"id":"fd2f8da1-616b-4c4f-9d6e-bdd14131eca4","doc_no":"A.6.1.1.1.3.2","title":"Management Of Infrastructure Inherited From Sky Core","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5025,"content":"The documents herein specify Spark's strategy and operational processes for managing infrastructure inherited from Sky Core.","contentHash":"a86a1a8d4c7f6aabb3ce331409330d34d7f8580f3e6ade792bd55f98bc0559cb","addressRefs":[]},"d9ff0cd2-8999-4d3d-9670-2c7b49c1fe51":{"id":"d9ff0cd2-8999-4d3d-9670-2c7b49c1fe51","doc_no":"A.6.1.1.1.3.2.1","title":"SparkLend","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5026,"content":"The documents herein define the parameters and operational processes related to SparkLend. Control of SparkLend is being transitioned to Spark.","contentHash":"b22a68a91aeb26fd2dd08060fd5781de10193aa799e32e7e67b663fb51b57427","addressRefs":[]},"a15a6203-23b1-4921-8bdb-fe0ef6013bf6":{"id":"a15a6203-23b1-4921-8bdb-fe0ef6013bf6","doc_no":"A.6.1.1.1.3.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5027,"content":"The parameters of SparkLend are specified in the subdocuments herein.","contentHash":"21d9a8d973023a502afcec9be9f525d70a7f817bdde8e71726665740cfab023d","addressRefs":[]},"667abf8c-64a3-4029-b218-e7a6e7000bbd":{"id":"667abf8c-64a3-4029-b218-e7a6e7000bbd","doc_no":"A.6.1.1.1.3.2.1.1.1","title":"SparkLend Risk Parameters Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5028,"content":"The subdocuments herein provide definitions of the SparkLend risk parameters.","contentHash":"cba0dcf164e76282bf7ffc751d43a7390bf44690d1a178e5c563e09e38b567c4","addressRefs":[]},"b93bf576-6972-48b6-8847-5988b094e325":{"id":"b93bf576-6972-48b6-8847-5988b094e325","doc_no":"A.6.1.1.1.3.2.1.1.1.1","title":"Borrow Rate Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5029,"content":"The borrow rate is the annualized percentage yield for borrowing the asset, which is determined based on the market’s Interest Rate Model and actual utilization in the market.","contentHash":"b4a5c06b572c0ad7dddfef251503cd11895de958b7d3f1c9818469be46a7cdba","addressRefs":[]},"5c4963af-872c-45b9-ac39-fda5ac4f43a1":{"id":"5c4963af-872c-45b9-ac39-fda5ac4f43a1","doc_no":"A.6.1.1.1.3.2.1.1.1.2","title":"Supply Rate Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5030,"content":"The supply rate is the annualized percentage yield for supplying the asset, which is determined based on borrow rate as:\nsupply rate = market utilization * borrow rate * (1-reserve factor)","contentHash":"7504152aa01d2fd62e1bf7d4936584285224992dbda19b31a33abd024fc6d8c1","addressRefs":[]},"9006fd8d-bd13-48fc-bf2f-04f47579b3b0":{"id":"9006fd8d-bd13-48fc-bf2f-04f47579b3b0","doc_no":"A.6.1.1.1.3.2.1.1.1.3","title":"Interest Rate Model Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5031,"content":"The Interest Rate Model (\"IRM\") is defined by four main parameters:\n\n1. Base Rate - the starting rate at 0% utilization,\n2. Variable Slope 1 - the rate at optimal utilization,\n3. Variable Slope 2 - the rate at 100% utilization,\n4. Utilization - the utilization itself.\n\nThe Base Rate, Slope 1, and Slope 2 parameters are further defined in: [A.6.1.1.1.3.2.1.1.1.13 - Base Rate Definition](9372deb9-5115-4010-bf72-34023b846525); [A.6.1.1.1.3.2.1.1.1.15 - Slope 1 Definition](c16b2b24-d663-4877-8bb3-cbd32e977360); and [A.6.1.1.1.3.2.1.1.1.17 - Slope 2 Definition](56bc7808-5ef8-42af-ba17-708b995194cc).\n\nAll markets except Dai use this IRM. The IRM for Dai is independent of utilization and is defined as a spread over the Sky Savings Rate set forth in [A.3.1.2.2 - Sky Savings Rate](2674cccb-d779-4868-b83f-8cb86648c88a). The spread is determined by the Stability Facilitators, in consultation with the Core Council Risk Advisor.","contentHash":"f3d605602a7976c9d24499e81058e1ce20e4422dc7203c7c2eae71bd988888e1","addressRefs":[]},"586478a3-51cb-4a2e-8bb1-b96e6520fdcc":{"id":"586478a3-51cb-4a2e-8bb1-b96e6520fdcc","doc_no":"A.6.1.1.1.3.2.1.1.1.4","title":"LTV Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5032,"content":"The LTV is the maximum percentage of the value of collateral that borrowers can borrow against their collateral.","contentHash":"9d5275da7cb2721ad069e6b76dad4da098640ee2c29bd0fa7f51b82dcdb2c1d8","addressRefs":[]},"2dd2045c-6a33-4229-b6c8-e531d6ecd27a":{"id":"2dd2045c-6a33-4229-b6c8-e531d6ecd27a","doc_no":"A.6.1.1.1.3.2.1.1.1.5","title":"Liquidation Threshold Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5033,"content":"The liquidation threshold is the maximum debt a borrower can owe as a percentage of their collateral before their position is considered under-collateralized and thus at risk of being liquidated.","contentHash":"d61eade0f7dd929111772f244defb648c8be08340146f6769ca2058e7997fcd9","addressRefs":[]},"49159478-90c9-4200-ab33-277a70b924d6":{"id":"49159478-90c9-4200-ab33-277a70b924d6","doc_no":"A.6.1.1.1.3.2.1.1.1.6","title":"High Efficiency Mode Category Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5034,"content":"The High Efficiency Mode Category groups assets that are highly correlated with each other into buckets, for example Stablecoins or various forms of ETH. Borrowing against an asset to acquire another asset in the same category can support higher LTVs and liquidation thresholds as determined by the protocol.","contentHash":"a6abab9d9b2208e12e2ce8c21818487b1d964064b4fcb801671e76d24ba0d055","addressRefs":[]},"173ff961-bf1f-4c6c-992c-4a67b269e544":{"id":"173ff961-bf1f-4c6c-992c-4a67b269e544","doc_no":"A.6.1.1.1.3.2.1.1.1.7","title":"Liquidation Bonus Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5035,"content":"The liquidation bonus is the bonus for liquidating an unhealthy loan, or equivalently the penalty for having an unhealthy loan liquidated. The party paying off the unhealthy loan is entitled to collateral with an equivalent value as the debt paid off plus the liquidation bonus.","contentHash":"3c17e6331a5faa545cb6461fc1bdf8d22a3ca56ff5408c4f2587af98e280a102","addressRefs":[]},"a68d2ffe-e541-4754-b11e-6cafe7b4ae5c":{"id":"a68d2ffe-e541-4754-b11e-6cafe7b4ae5c","doc_no":"A.6.1.1.1.3.2.1.1.1.8","title":"Reserve Factor Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5036,"content":"The reserve factor is the percentage of interest payments paid to the protocol.","contentHash":"8880b363aae26c2b240a4006914d07daa89bd6067747ea601242eb6cb454697b","addressRefs":[]},"e222b8da-abda-42f5-8106-20c6f2881dc7":{"id":"e222b8da-abda-42f5-8106-20c6f2881dc7","doc_no":"A.6.1.1.1.3.2.1.1.1.9","title":"Supply Cap Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5037,"content":"The supply cap is the maximum amount of the asset that can be supplied.","contentHash":"f8105664a561dfd2cc2d464074abc09de8c7d57e8faf1248332821141281efac","addressRefs":[]},"a2d6a99e-c63a-4f30-87f3-a3d66b1eda92":{"id":"a2d6a99e-c63a-4f30-87f3-a3d66b1eda92","doc_no":"A.6.1.1.1.3.2.1.1.1.10","title":"Borrow Cap Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5038,"content":"The borrow cap is the maximum amount of the asset that can be borrowed.","contentHash":"1c2d0b2bbb7e7b2481b76365c9b5a50bd2935c5e0784e0c04e201dca5e6d857b","addressRefs":[]},"a6677e8a-7ef1-460b-a5cd-5411319bf2c0":{"id":"a6677e8a-7ef1-460b-a5cd-5411319bf2c0","doc_no":"A.6.1.1.1.3.2.1.1.1.11","title":"Optimal Utilization Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5039,"content":"The optimal utilization represents the desired target utilization of the borrowing capacity for the asset. It is an input used to determine the interest rate of borrowing. When the actual utilization is above the optimal utilization, borrowing rates will be higher; and when the actual utilization is below the optimal utilization, borrowing rates will be lower.","contentHash":"fada3b743e347fd4e0939397e9822ceaa637644fb58aeb4d06dcdea172bad20f","addressRefs":[]},"ccb5b20f-8fe0-487c-9d61-d038c87e04f0":{"id":"ccb5b20f-8fe0-487c-9d61-d038c87e04f0","doc_no":"A.6.1.1.1.3.2.1.1.1.12","title":"Isolated Debt Ceiling Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5040,"content":"The isolated debt ceiling represents the maximum amount that can be borrowed against designated isolated assets, as determined by the Stability Facilitators in consultation with the Core Council Risk Advisor. Only Stablecoins may be borrowed against isolated assets.","contentHash":"4977e944eca43d98456e186ef8445acc262d77f3a84718fec6a6653db4d2feb9","addressRefs":[]},"9372deb9-5115-4010-bf72-34023b846525":{"id":"9372deb9-5115-4010-bf72-34023b846525","doc_no":"A.6.1.1.1.3.2.1.1.1.13","title":"Base Rate Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5041,"content":"The base rate is an input used to determine the interest rate of borrowing. The base rate is adjusted based on actual borrowing utilization relative to optimal borrowing utilization to arrive at the actual borrowing rate.","contentHash":"42d7c69f8dddb8c0c51f06be44f222ebb868b70331d93a459b282982105c9e78","addressRefs":[]},"d6b75f49-ca6b-49ef-923f-1a8d452abaf2":{"id":"d6b75f49-ca6b-49ef-923f-1a8d452abaf2","doc_no":"A.6.1.1.1.3.2.1.1.1.14","title":"Reserve State Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5042,"content":"The reserve state represents the state of the market for a particular collateral type. The reserve state may be:\n\n- Active - all activities may occur\n- Frozen - all activities may occur except for supplying and borrowing\n- Paused - no activities may occur","contentHash":"9cf156a33bcf0bae514805b1a08a55bd47a51423f20030c463364afcfcd54e11","addressRefs":[]},"c16b2b24-d663-4877-8bb3-cbd32e977360":{"id":"c16b2b24-d663-4877-8bb3-cbd32e977360","doc_no":"A.6.1.1.1.3.2.1.1.1.15","title":"Slope 1 Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5043,"content":"Slope 1 is the interest rate at optimal utilization in the Interest Rate Model.","contentHash":"7242f72b2c12f4a01cd0f56c12406437ff5c80468372dcca5023a861e798ceef","addressRefs":[]},"a868bb67-36e5-44e5-b852-62f23c1c8ec4":{"id":"a868bb67-36e5-44e5-b852-62f23c1c8ec4","doc_no":"A.6.1.1.1.3.2.1.1.1.16","title":"Slope 1 Spread Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5044,"content":"The Slope 1 Spread is the difference between the WETH interest rate at optimal utilization in the Interest Rate Model and the staking yield on stETH. The Slope 1 Spread Parameter is only defined for WETH.","contentHash":"a285e0e3012bb01665798d5b53ef79068e3334406c240646184dc4933b222086","addressRefs":[]},"56bc7808-5ef8-42af-ba17-708b995194cc":{"id":"56bc7808-5ef8-42af-ba17-708b995194cc","doc_no":"A.6.1.1.1.3.2.1.1.1.17","title":"Slope 2 Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5045,"content":"Slope 2 is the interest rate at 100% utilization in the Interest Rate Model.","contentHash":"539c729b6af715d8a6e010a47763d1e85d4cab960fcd03f1fa41a7f292a7ff04","addressRefs":[]},"f0f7d864-7f68-4727-8c20-9d261dfd63eb":{"id":"f0f7d864-7f68-4727-8c20-9d261dfd63eb","doc_no":"A.6.1.1.1.3.2.1.1.1.18","title":"Collateral-Enabled Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5046,"content":"If Collateral is Enabled, then the asset may be used as collateral.","contentHash":"189b63050f35a70d34d97544c6e6f9ad49b3f3b643835d3134f545a09974c9cd","addressRefs":[]},"2ec70ad1-f979-4a4a-bce2-cd070e9e283f":{"id":"2ec70ad1-f979-4a4a-bce2-cd070e9e283f","doc_no":"A.6.1.1.1.3.2.1.1.1.19","title":"Borrowing-Enabled Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5047,"content":"If Borrowing is Enabled, then the asset may be borrowed.","contentHash":"3ccb4c8321541e190013c02d80c08c8bf0ff8b3b7db7ace0b1d02e193bae9a22","addressRefs":[]},"7dfd4e6f-7b62-42a5-9ff1-7326bdc979bb":{"id":"7dfd4e6f-7b62-42a5-9ff1-7326bdc979bb","doc_no":"A.6.1.1.1.3.2.1.1.1.20","title":"Isolated Collateral-Enabled Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5048,"content":"If Isolated Collateral is Enabled, only Stablecoins can be borrowed when using the asset as collateral.","contentHash":"3ba51392f02c6764305eb1da5dca93cd78a809d010afb9b0b4086077a6572a77","addressRefs":[]},"6e0c4a4d-c6b0-4c41-b6ac-747a90707fdb":{"id":"6e0c4a4d-c6b0-4c41-b6ac-747a90707fdb","doc_no":"A.6.1.1.1.3.2.1.1.1.21","title":"Isolation Mode Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5049,"content":"When a user is in Isolation Mode, only assets with Isolated Borrow enabled can be borrowed.","contentHash":"1a6d9e2af0fd3c680be473b04ff437f28e94e670d8f4230dddc9b500485b9b7f","addressRefs":[]},"eb779cd6-adeb-490e-b67d-d0854b7a844c":{"id":"eb779cd6-adeb-490e-b67d-d0854b7a844c","doc_no":"A.6.1.1.1.3.2.1.1.1.21.0.3.1","title":"Isolated Borrow - Element Annotation","type":"Annotation","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5050,"content":"\"Isolated Borrow\" specifies whether an asset can be borrowed when a user is in Isolation Mode on the SparkLend platform.","contentHash":"58e0e4a0a4db6511076519c40bc3bae53bf3b0d777931cb5fc7016d5430bed03","addressRefs":[]},"f6764325-46d2-4fe4-872e-6e89a1914a5d":{"id":"f6764325-46d2-4fe4-872e-6e89a1914a5d","doc_no":"A.6.1.1.1.3.2.1.1.1.22","title":"Siloed Borrowing-Enabled Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5051,"content":"If Siloed Borrowing is Enabled, then when borrowing the asset, no other asset may be borrowed.","contentHash":"416ef18ed701f9dd695c998c6b1ad7b5658dd28763e0b29b729e38a773662eba","addressRefs":[]},"17d352ee-a54b-43e5-92ee-224a1193c7ee":{"id":"17d352ee-a54b-43e5-92ee-224a1193c7ee","doc_no":"A.6.1.1.1.3.2.1.1.1.23","title":"Flash Loan Enabled Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5052,"content":"If the Flash Loan Enabled parameter is activated, then the asset may be borrowed using a flash loan.","contentHash":"58f28f6240e14b744a0bf149044668914a90ff44c93ed9bf1acd242ee234ca41","addressRefs":[]},"250bb1bd-128b-48d2-aa56-53006dab795e":{"id":"250bb1bd-128b-48d2-aa56-53006dab795e","doc_no":"A.6.1.1.1.3.2.1.1.1.24","title":"Total Flash Loan Fee Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5053,"content":"The Total Flash Loan Fee incorporates a fee paid to the protocol and a fee paid to liquidity providers. This total fee is calculated as a percentage of the flash loan amount. Of the Total Flash Loan Fee, the Protocol Flash Loan Fee is paid to the protocol, with the remainder paid to liquidity providers.\n\nThe Total Flash Loan Fee is set on a protocol level, regardless of what assets are being borrowed.","contentHash":"88c7437604ee52d594af2483d0f16750586f83f39b6f42da4659b698433d768d","addressRefs":[]},"638d0e6b-8d6a-48e9-9bf9-e8ee201e0e97":{"id":"638d0e6b-8d6a-48e9-9bf9-e8ee201e0e97","doc_no":"A.6.1.1.1.3.2.1.1.1.25","title":"Protocol Flash Loan Fee Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5054,"content":"The Protocol Flash Loan Fee is the fee for a flash loan paid to the protocol as a percentage of the flash loan amount.\n\nThe Protocol Flash Loan Fee is set on a protocol level, regardless of what assets are being borrowed.","contentHash":"1b33f2bf33da2ceac01971d962338230b135b432857b8b8afbccf9bff30a31aa","addressRefs":[]},"cb959917-c29c-4d2f-b151-ded03618357c":{"id":"cb959917-c29c-4d2f-b151-ded03618357c","doc_no":"A.6.1.1.1.3.2.1.1.2","title":"SparkLend Risk Parameters Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5055,"content":"The subdocuments herein define the current configuration of the SparkLend risk parameters.","contentHash":"f0aa53204e6a3ed24ec11bc225387739fa58b4c06301e44ea866c90b2a1555e5","addressRefs":[]},"b370fb72-57f8-4cf1-aab9-597d08afe403":{"id":"b370fb72-57f8-4cf1-aab9-597d08afe403","doc_no":"A.6.1.1.1.3.2.1.1.2.1","title":"SparkLend Ethereum Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5056,"content":"The subdocuments herein define the current configuration of the SparkLend Ethereum risk parameters.","contentHash":"4050a1161ef7a86ab1732ca20c6b226ea02c69d5753080de004a05b00c204fb2","addressRefs":[]},"acd9d2a2-ff4f-44fc-a544-f4cc02262a5b":{"id":"acd9d2a2-ff4f-44fc-a544-f4cc02262a5b","doc_no":"A.6.1.1.1.3.2.1.1.2.1.1","title":"GNO Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5057,"content":"The current GNO risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 25%\n- E-mode Category: N/A\n- Liquidation Bonus: 10%\n- Reserve Factor: 0%\n- Supply Cap: N/A\n- Borrow Cap: N/A\n- Optimal Utilization: 100%\n- Isolated Debt Ceiling: $5,000,000\n- Base Rate: 1%\n- Slope 1: 0%\n- Slope 2: 0%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: Yes\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"e8ffae1afb36d633a81583af79cc97c652ef1a1f7232ea7d5f789a308998d910","addressRefs":[]},"7d8ed55b-4aca-483b-af6d-24badb49d042":{"id":"7d8ed55b-4aca-483b-af6d-24badb49d042","doc_no":"A.6.1.1.1.3.2.1.1.2.1.2","title":"Dai Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5058,"content":"The current Dai risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0.01%\n- E-mode Category: N/A\n- Liquidation Bonus: 4.5%\n- Reserve Factor: 10%\n- Supply Cap: N/A\n- Borrow Cap: N/A\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: SSR + 1.25%\n- Slope 2: 15%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: Yes\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes\n\nThe Dai Borrow Rate is set through the Interest Rate Model as a spread over the Sky Savings Rate. The spread is set directly by the Stability Facilitators in consultation with the Core Council Risk Advisor.","contentHash":"274ca6d949bfa753c6c017629ce181e74855d8f576e1a402f95e80989b2abf13","addressRefs":[]},"d9a146b8-f101-4cd6-916c-85142bb8deec":{"id":"d9a146b8-f101-4cd6-916c-85142bb8deec","doc_no":"A.6.1.1.1.3.2.1.1.2.1.3","title":"USDS Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5059,"content":"The current USDS risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: N/A\n- Liquidation Bonus: 0%\n- Reserve Factor: 10%\n- Supply Cap: Unlimited\n- Borrow Cap: Unlimited\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: SSR + 1.25%\n- Slope 2: 15%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: Yes\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes.\n\nThe USDS Borrow Rate is set through the Interest Rate Model as a spread over the Sky Savings Rate. The spread is set directly by the Stability Facilitators in consultation with the Core Council Risk Advisor.","contentHash":"97170e30b7b1a59e912d32c2b81c8d831345c354ca3663604a747694ff148e7d","addressRefs":[]},"b1a1fb8a-29d7-4bbd-8204-25c74263c25d":{"id":"b1a1fb8a-29d7-4bbd-8204-25c74263c25d","doc_no":"A.6.1.1.1.3.2.1.1.2.1.4","title":"WETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5060,"content":"The current WETH risk parameters are:\n\n- LTV: 85%\n- Liquidation Threshold: 86%\n- E-mode Category: ETH\n- Liquidation Bonus: 5%\n- Reserve Factor: 5%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 90%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: N/A\n- Slope 1 Spread: -0.30%\n- Slope 2: 120%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes\n\nThe Slope 1 parameter for WETH is calculated based on the following formula:\n\nslope 1 = stETH yield + slope 1 spread - base rate","contentHash":"c82a92cc474ef135a27e6a6774d603679c17b98ece4738f1f481b2e2736357df","addressRefs":[]},"4999a374-380b-4694-a67c-0fa471b4cf43":{"id":"4999a374-380b-4694-a67c-0fa471b4cf43","doc_no":"A.6.1.1.1.3.2.1.1.2.1.5","title":"USDT Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5061,"content":"The current USDT risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: USD\n- Liquidation Bonus: 0%\n- Reserve Factor: 1%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 95%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: SSR value + 1.25%\n- Slope 2: 15%\n- Reserve State: Active\n- Collateral: No\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"c0d27d56ad38fb0952b8c7f61fdf4da8b2de01ac6f345378da10ab5f22c69813","addressRefs":[]},"c3c3830f-4829-48fc-aced-30dcdd2a5ba7":{"id":"c3c3830f-4829-48fc-aced-30dcdd2a5ba7","doc_no":"A.6.1.1.1.3.2.1.1.2.1.6","title":"WBTC Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5062,"content":"The current WBTC risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 35%\n- E-mode Category: N/A\n- Liquidation Bonus: 7%\n- Reserve Factor: 20%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 60%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 2%\n- Slope 2: 300%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"b7e79b1a32cb2210e729213f2ff13c9a45233342d120f1187d0ffed77d6070aa","addressRefs":[]},"61c21da3-22ff-4dba-8736-4a9a8556a32b":{"id":"61c21da3-22ff-4dba-8736-4a9a8556a32b","doc_no":"A.6.1.1.1.3.2.1.1.2.1.7","title":"sDai Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5063,"content":"The current sDai risk parameters are:\n\n- LTV: 79%\n- Liquidation Threshold: 80%\n- E-mode Category: USD\n- Liquidation Bonus: 5%\n- Reserve Factor: 10%\n- Supply Cap: Set by cap automator\n- Borrow Cap: N/A\n- Optimal Utilization: 100%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 1%\n- Slope 1: 0%\n- Slope 2: 0%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"cb4453ed7c0d2f9bea0f90865c05335800e78bf5d28f66369f9ab3ef1c505c5a","addressRefs":[]},"5d721ab3-be87-4989-b4a2-b32ff38b912f":{"id":"5d721ab3-be87-4989-b4a2-b32ff38b912f","doc_no":"A.6.1.1.1.3.2.1.1.2.1.8","title":"wstETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5064,"content":"The current wstETH risk parameters are:\n\n- LTV: 83%\n- Liquidation Threshold: 84%\n- E-mode Category: ETH\n- Liquidation Bonus: 7%\n- Reserve Factor: 30%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 70%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 2%\n- Slope 2: 200%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"a9e74cb29ddb26e333d5251dbcd84fef7d4d2758d3f9ed3154ffd08ee1da3626","addressRefs":[]},"d8242d1a-18f2-4000-a98b-0521486b0708":{"id":"d8242d1a-18f2-4000-a98b-0521486b0708","doc_no":"A.6.1.1.1.3.2.1.1.2.1.9","title":"USDC Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5065,"content":"The current USDC risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: USD\n- Liquidation Bonus: 0%\n- Reserve Factor: 1%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 95%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: SSR value + 1.25%\n- Slope 2: 15%\n- Reserve State: Active\n- Collateral: No\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"8384b24592f7533333e1fb3d5ab3cf71d038ea56f86373f6cc2eb3fcdf75c7ce","addressRefs":[]},"6ed18918-a695-44a6-82e7-547a3fbcafd3":{"id":"6ed18918-a695-44a6-82e7-547a3fbcafd3","doc_no":"A.6.1.1.1.3.2.1.1.2.1.10","title":"weETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5066,"content":"The current weETH risk parameters are:\n\n- LTV: 79%\n- Liquidation Threshold: 80%\n- E-mode Category: N/A\n- Liquidation Bonus: 10%\n- Reserve Factor: 15%\n- Supply Cap: Set by cap automator\n- Borrow Cap: N/A\n- Optimal Utilization: 45%\n- Isolated Debt Ceiling: $200,000,000\n- Base Rate: 5%\n- Slope 1: 15%\n- Slope 2: 300%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: Yes\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"7329684b159cb0550e29c3f569076a60f8ae3a97eb30be2bbe701ed4412b8ecf","addressRefs":[]},"9ef0bc64-db94-4d78-ac8b-cef71d28fedc":{"id":"9ef0bc64-db94-4d78-ac8b-cef71d28fedc","doc_no":"A.6.1.1.1.3.2.1.1.2.1.11","title":"rETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5067,"content":"The current rETH risk parameters are:\n\n- LTV: 79%\n- Liquidation Threshold: 80%\n- E-mode Category: ETH\n- Liquidation Bonus: 7%\n- Reserve Factor: 15%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 45%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0.25%\n- Slope 1: 7%\n- Slope 2: 300%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"b4676a374337492b7e611ddc89e531b91b965909aadf31598e6eb38690e29cfa","addressRefs":[]},"37ff9748-6f72-4adf-af97-0f90cb7154b4":{"id":"37ff9748-6f72-4adf-af97-0f90cb7154b4","doc_no":"A.6.1.1.1.3.2.1.1.2.1.12","title":"LBTC Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5068,"content":"The current LBTC risk parameters are:\n\n- LTV: 74%\n- Liquidation Threshold: 75%\n- E-mode Category: 3\n- Liquidation Bonus: 8%\n- Reserve Factor: 15%\n- Supply Cap: Set by cap automator\n- Borrow Cap: 0\n- Optimal Utilization: 45%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 5%\n- Slope 1: 15%\n- Slope 2: 300%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"9b3108a4b2ef127789c00c25fbc568061ee112a90b929ec89b9adf1279feddd7","addressRefs":[]},"17e2cc64-6172-48f8-a4f1-a2a7bc5edbbb":{"id":"17e2cc64-6172-48f8-a4f1-a2a7bc5edbbb","doc_no":"A.6.1.1.1.3.2.1.1.2.1.13","title":"tBTC Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5069,"content":"The current tBTC risk parameters are:\n\n- LTV: 74%\n- Liquidation Threshold: 75%\n- E-mode Category: 0\n- Liquidation Bonus: 8%\n- Reserve Factor: 99%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 1%\n- Slope 2: 300%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"78a7a8a30f7067028ca21799774490329be24c9665f859952a6c8b439144a376","addressRefs":[]},"51f3555b-57a3-4275-b462-a4ba85f3b8fe":{"id":"51f3555b-57a3-4275-b462-a4ba85f3b8fe","doc_no":"A.6.1.1.1.3.2.1.1.2.1.14","title":"ezETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5070,"content":"The current ezETH risk parameters are:\n\n- LTV: 75%\n- Liquidation Threshold: 76%\n- E-mode Category: 0\n- Liquidation Bonus: 10%\n- Reserve Factor: 15%\n- Supply Cap: Set by cap automator\n- Borrow Cap: 0\n- Optimal Utilization: 45%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 5%\n- Slope 1: 15%\n- Slope 2: 300%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"5fb2be139985023f890bbd960621e2a90182f35dab8cf587264121d357aae249","addressRefs":[]},"1da6ef90-fca2-4f72-9b8d-13a3786a3c1c":{"id":"1da6ef90-fca2-4f72-9b8d-13a3786a3c1c","doc_no":"A.6.1.1.1.3.2.1.1.2.1.15","title":"rsETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5071,"content":"The current rsETH risk parameters are:\n\n- LTV: 75%\n- Liquidation Threshold: 76%\n- E-mode Category: 0\n- Liquidation Bonus: 10%\n- Reserve Factor: 15%\n- Supply Cap: Set by cap automator\n- Borrow Cap: 0\n- Optimal Utilization: 45%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 5%\n- Slope 1: 15%\n- Slope 2: 300%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"54d90f0c8932d352843988e406679d4b53e120be5954074baa5d2931b81e2ec1","addressRefs":[]},"63038ac2-7666-40bb-ad9f-dba7c1a546b8":{"id":"63038ac2-7666-40bb-ad9f-dba7c1a546b8","doc_no":"A.6.1.1.1.3.2.1.1.2.1.16","title":"cbBTC Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5072,"content":"The current cbBTC risk parameters are:\n\n- LTV: 81%\n- Liquidation Threshold: 82%\n- E-mode Category: BTC\n- Liquidation Bonus: 8%\n- Reserve Factor: 20%\n- Supply Cap: 500 cbBTC\n- Borrow Cap: 50 cbBTC\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 1%\n- Slope 2: 300%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No","contentHash":"169bc061834a6a9453da7ec98b6c26cc7c6e4474abbf6707154fc51a8aabc729","addressRefs":[]},"1d7f757a-aabb-463d-9d3d-3f34f1c0656a":{"id":"1d7f757a-aabb-463d-9d3d-3f34f1c0656a","doc_no":"A.6.1.1.1.3.2.1.1.2.1.17","title":"sUSDS Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5073,"content":"The current sUSDS risk parameters are:\n\n- LTV: 79%\n- Liquidation Threshold: 80%\n- E-mode Category: USD\n- Liquidation Bonus: 5%\n- Reserve Factor: 10%\n- Supply Cap: 50,000,000 sUSDS\n- Borrow Cap: 0 sUSDS\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 2%\n- Slope 2: 300%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No","contentHash":"7dd23335f6b3376b44a3cad423321e381010a3afde6b09f196923fff133df337","addressRefs":[]},"5e05e5d8-8477-460f-a197-4b49bfa8652f":{"id":"5e05e5d8-8477-460f-a197-4b49bfa8652f","doc_no":"A.6.1.1.1.3.2.1.1.2.1.18","title":"pyUSD Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5074,"content":"The current pyUSD risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: USD\n- Liquidation Bonus: 10%\n- Reserve Factor: 10%\n- Supply Cap: Set by cap automator\n- Borrow Cap: Set by cap automator\n- Optimal Utilization: 95%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: SSR + 1.5%\n- Slope 2: 15%\n- Reserve State: Active\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No","contentHash":"17b4feb69c73b6ce9ec2922ea644c1abbe1bc2dd6b2aeeaee1c3432a04071d32","addressRefs":[]},"fdd544f0-fa59-42f5-afb8-290cd812eb35":{"id":"fdd544f0-fa59-42f5-afb8-290cd812eb35","doc_no":"A.6.1.1.1.3.2.1.1.2.1.19","title":"Total Flash Loan Fee Current Value","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5075,"content":"The Total Flash Loan Fee is 0.00%.","contentHash":"f81c5f3cae8642818151a31c74827f3539f500dd795eee0069e439a9d803c6a1","addressRefs":[]},"086d81f6-e8e2-4693-996f-6ccb62ee362b":{"id":"086d81f6-e8e2-4693-996f-6ccb62ee362b","doc_no":"A.6.1.1.1.3.2.1.1.2.1.20","title":"Protocol Flash Loan Fee Current Value","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5076,"content":"The Protocol Flash Loan Fee is 0.00%.","contentHash":"76903157c91ab394f0a5e88fceead3cf7aa7edddca15f6d949bc98789036caac","addressRefs":[]},"1ecdd683-0f6f-4bca-8f43-c2a458224404":{"id":"1ecdd683-0f6f-4bca-8f43-c2a458224404","doc_no":"A.6.1.1.1.3.2.1.1.2.2","title":"SparkLend Gnosis Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5077,"content":"The subdocuments herein define the current configuration of the SparkLend Gnosis risk parameters.","contentHash":"9b63c7d727263cc8194e439586bfb2da0950221ea8255c49c45e65b74950b22b","addressRefs":[]},"aacc4fa0-3fd8-44f4-af79-7ec3d4128328":{"id":"aacc4fa0-3fd8-44f4-af79-7ec3d4128328","doc_no":"A.6.1.1.1.3.2.1.1.2.2.1","title":"GNO Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5078,"content":"The current GNO risk parameters are:\n\n- LTV: 40%\n- Liquidation Threshold: 50%\n- E-mode Category: N/A\n- Liquidation Bonus: 12%\n- Reserve Factor: 50%\n- Supply Cap: 100,000 GNO\n- Borrow Cap: N/A\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: $1,000,000\n- Base Rate: 0%\n- Slope 1: 0%\n- Slope 2: 0%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: Yes\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"3b1fd9ce2503afcd3396dccd2e4c8540c218c3931c224bffe4954f9310eb8414","addressRefs":[]},"dc3b3c32-f891-49fa-bdb4-8944d14e3d56":{"id":"dc3b3c32-f891-49fa-bdb4-8944d14e3d56","doc_no":"A.6.1.1.1.3.2.1.1.2.2.2","title":"WETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5079,"content":"The current WETH risk parameters are:\n\n- LTV: 70%\n- Liquidation Threshold: 75%\n- E-mode Category: ETH\n- Liquidation Bonus: 5%\n- Reserve Factor: 50%\n- Supply Cap: 5,000 ETH\n- Borrow Cap: 3,000 ETH\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 2.5%\n- Slope 2: 120%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"45852b55ea492853a3234f617a17efd49945da76594dd2c67e0d7301b8cd13df","addressRefs":[]},"f5a396c7-dc2c-4d67-adff-89c5a8c62652":{"id":"f5a396c7-dc2c-4d67-adff-89c5a8c62652","doc_no":"A.6.1.1.1.3.2.1.1.2.2.3","title":"USDT Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5080,"content":"The current USDT risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: USD\n- Liquidation Bonus: 0%\n- Reserve Factor: 50%\n- Supply Cap: 10,000,000 USDT\n- Borrow Cap: 8,000,000 USDT\n- Optimal Utilization: 95%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 9%\n- Slope 2: 15%\n- Reserve State: Frozen\n- Collateral: No\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: Yes\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"a0ca663c4b4b34733ec3ac9182f017f1f734c7220c729a104941eccd639cd515","addressRefs":[]},"2c982dbd-dee3-45ce-9e45-48d7ebc33acb":{"id":"2c982dbd-dee3-45ce-9e45-48d7ebc33acb","doc_no":"A.6.1.1.1.3.2.1.1.2.2.4","title":"sDai Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5081,"content":"The current sDai risk parameters are:\n\n- LTV: 70%\n- Liquidation Threshold: 75%\n- E-mode Category: USD\n- Liquidation Bonus: 6%\n- Reserve Factor: 50%\n- Supply Cap: 40,000,000 sDai\n- Borrow Cap: N/A\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 0%\n- Slope 2: 0%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: No\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"0b22cdadf341b1d2990c648fd5259a1673d982ea1a2c72a0a633afb4023bbb47","addressRefs":[]},"a07d0682-9249-4a4f-b2a3-c0dfb163c683":{"id":"a07d0682-9249-4a4f-b2a3-c0dfb163c683","doc_no":"A.6.1.1.1.3.2.1.1.2.2.5","title":"wstETH Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5082,"content":"The current wstETH risk parameters are:\n\n- LTV: 65%\n- Liquidation Threshold: 72.5%\n- E-mode Category: ETH\n- Liquidation Bonus: 8%\n- Reserve Factor: 50%\n- Supply Cap: 15,000 wstETH\n- Borrow Cap: 100 wstETH\n- Optimal Utilization: 45%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 1%\n- Slope 1: 3%\n- Slope 2: 100%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"7c1e14b1c2e2d93eab78c25ec6a90fa6c0aff04e70d6050d436fd2149375ad12","addressRefs":[]},"f54fff22-1cad-4ccd-80ae-f05f0345c384":{"id":"f54fff22-1cad-4ccd-80ae-f05f0345c384","doc_no":"A.6.1.1.1.3.2.1.1.2.2.6","title":"USDC Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5083,"content":"The current USDC risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: USD\n- Liquidation Bonus: 0%\n- Reserve Factor: 50%\n- Supply Cap: 10,000,000 USDC\n- Borrow Cap: 1,000,000 USDC\n- Optimal Utilization: 80%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 9%\n- Slope 2: 50%\n- Reserve State: Frozen\n- Collateral: No\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: Yes\n- Siloed Borrowing: No\n- Flash Loan Enabled: Yes","contentHash":"5390cf43949189a3fff45e5302994f74329bb1bbebf589401f54603d3bdbdc8e","addressRefs":[]},"b54fc943-6d64-4c67-9aa2-150665be6493":{"id":"b54fc943-6d64-4c67-9aa2-150665be6493","doc_no":"A.6.1.1.1.3.2.1.1.2.2.7","title":"USDC.e Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5084,"content":"The current USDC.e risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: USD\n- Liquidation Bonus: 0%\n- Reserve Factor: 50%\n- Supply Cap: 10,000,000 USDC.e\n- Borrow Cap: 8,000,000 USDC.e\n- Optimal Utilization: 95%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 9%\n- Slope 2: 15%\n- Reserve State: Frozen\n- Collateral: No\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: Yes\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"5b50bca7e720a5640997e9baba6789cb3dbd42ccc9e06da201b14b569620e688","addressRefs":[]},"57bae006-ff07-4da7-adc3-ea3649ce7e38":{"id":"57bae006-ff07-4da7-adc3-ea3649ce7e38","doc_no":"A.6.1.1.1.3.2.1.1.2.2.8","title":"WXDAI Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5085,"content":"The current WXDAI risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 75%\n- E-mode Category: USD\n- Liquidation Bonus: 5%\n- Reserve Factor: 50%\n- Supply Cap: 20,000,000 WXDAI\n- Borrow Cap: 16,000,000 WXDAI\n- Optimal Utilization: 95%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 9%\n- Slope 2: 15%\n- Reserve State: Frozen\n- Collateral: Yes\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: Yes\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"a94a45ef6f0949191ac005594d463b67411b9857c29fda297a73dd7d859eb036","addressRefs":[]},"1a8186bd-c557-4a6d-80e3-a8140a215e06":{"id":"1a8186bd-c557-4a6d-80e3-a8140a215e06","doc_no":"A.6.1.1.1.3.2.1.1.2.2.9","title":"EURe Risk Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5086,"content":"The current EURe risk parameters are:\n\n- LTV: 0%\n- Liquidation Threshold: 0%\n- E-mode Category: N/A\n- Liquidation Bonus: 0%\n- Reserve Factor: 50%\n- Supply Cap: 5,000,000 EURe\n- Borrow Cap: 4,000,000 EURe\n- Optimal Utilization: 95%\n- Isolated Debt Ceiling: N/A\n- Base Rate: 0%\n- Slope 1: 5%\n- Slope 2: 15%\n- Reserve State: Frozen\n- Collateral: No\n- Borrowing: Yes\n- Isolated Collateral: No\n- Isolated Borrowing: No\n- Siloed Borrowing: No\n- Flash Loan Enabled: No","contentHash":"09b10575b878106466b833e96a7a25ec8e5790e0ca38a22d9ac6a2a1d8c6e9b6","addressRefs":[]},"6ffdb8ee-b083-40f5-b51b-1c91e954b68b":{"id":"6ffdb8ee-b083-40f5-b51b-1c91e954b68b","doc_no":"A.6.1.1.1.3.2.1.1.3","title":"SparkLend Risk Parameters Cap Automators","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5087,"content":"Cap Automators allow the Supply Cap defined in [A.6.1.1.1.3.2.1.1.1.9 - Supply Cap Definition](e222b8da-abda-42f5-8106-20c6f2881dc7) and the Borrow Cap defined in [A.6.1.1.1.3.2.1.1.1.10 - Borrow Cap Definition](a2d6a99e-c63a-4f30-87f3-a3d66b1eda92) to be dynamically adjusted.\n\nThe cap automator is defined in terms of three parameters:\n\n1. `gap` - the target available exposure\n2. `ttl` - the cooldown period for cap increases\n3. `max` - the absolute maximum exposure\n\nAuthorized parties can update a covered Supply Cap or Borrow Cap so the available exposure is equal to the target, as long as the resulting exposure does not exceed the specified maximum limit and the cooldown period has elapsed in the case of increases to the Supply Cap or Borrow Cap.","contentHash":"4255ae4bf1aea811bc6bfb619a6455d7be2dbb545f6ffaace93943f926892600","addressRefs":[]},"e6bc54e6-91df-4095-a032-0e1128c2cab7":{"id":"e6bc54e6-91df-4095-a032-0e1128c2cab7","doc_no":"A.6.1.1.1.3.2.1.1.3.1","title":"SparkLend Risk Parameters Cap Automator Parameter Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5088,"content":"The subdocuments herein define the parameters of the Cap Automators.","contentHash":"3cdd6d73ee84bd15b4ae0687e986d1d1b862ed1fc96105546cf5a95c9675d196","addressRefs":[]},"6d069b25-fb76-4fa6-93f2-7b9ff6aeaa4c":{"id":"6d069b25-fb76-4fa6-93f2-7b9ff6aeaa4c","doc_no":"A.6.1.1.1.3.2.1.1.3.1.1","title":"SparkLend Risk Parameters Cap Automator Target Available Exposure Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5089,"content":"The `gap` parameter is the target gap between the supply usage and the Supply Cap, in the case of the Supply Cap, or between the borrow usage and the Borrow Cap, in the case of the Borrow Cap.","contentHash":"ab0b4a138d88be9136b747c77b2c43b0bcb160df02c40f916f48be7dc6f395da","addressRefs":[]},"7807007b-c076-4c7a-bd90-10cd23d41189":{"id":"7807007b-c076-4c7a-bd90-10cd23d41189","doc_no":"A.6.1.1.1.3.2.1.1.3.1.2","title":"SparkLend Risk Parameters Cap Automator Cooldown Period Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5090,"content":"The `ttl` parameters is the minimum time requirement before it is possible to increase the Supply Cap or Borrow Cap, expressed in seconds.","contentHash":"7106d5f1839c6f220798f05e9235f040c11d64d3d01a205985eb9b436b32beb4","addressRefs":[]},"35323a90-f863-4fad-b6ca-9968a163a76d":{"id":"35323a90-f863-4fad-b6ca-9968a163a76d","doc_no":"A.6.1.1.1.3.2.1.1.3.1.3","title":"SparkLend Risk Parameters Cap Automator Absolute Maximum Exposure Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5091,"content":"The `max` parameter is the maximum the Supply Cap or Borrow Cap can be increased to.","contentHash":"19032ae55595494f697906729ce5563620a4350019e7715d16808053f0278286","addressRefs":[]},"44689f16-06e9-479b-9285-0bc897edca31":{"id":"44689f16-06e9-479b-9285-0bc897edca31","doc_no":"A.6.1.1.1.3.2.1.1.3.2","title":"SparkLend Cap Automator Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5092,"content":"The subdocuments herein define the current configuration of the cap automators for each covered market.","contentHash":"d8314e7add1a0bda51dfbcf7e4cdacca4e8e7c7c7942d483e93a37c71e91649e","addressRefs":[]},"89304383-83e5-48fe-aa1a-a34a5ded82e5":{"id":"89304383-83e5-48fe-aa1a-a34a5ded82e5","doc_no":"A.6.1.1.1.3.2.1.1.3.2.1","title":"SparkLend Cap Automator WETH Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5093,"content":"The current WETH cap automator parameters are:\n\n- Supply cap\n    - `gap`: 150,000 WETH\n    - `ttl`: 12 hours\n    - `max`: 2 million WETH\n- Borrow cap\n    - `gap`: 20,000 WETH\n    - `ttl`: 12 hours\n    - `max`: 1 million WETH","contentHash":"cfa0070f435b5e36d2081122ff1fd5bcb1f8f51213c9475d1821cccdd61afedb","addressRefs":[]},"93b851d7-9825-4022-a583-51a4bbdf4f9c":{"id":"93b851d7-9825-4022-a583-51a4bbdf4f9c","doc_no":"A.6.1.1.1.3.2.1.1.3.2.2","title":"SparkLend Cap Automator wstETH Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5094,"content":"The current wstETH cap automator parameters are:\n\n- Supply cap\n    - `gap`: 50,000 wstETH\n    - `ttl`: 12 hours\n    - `max`: 2 million wstETH\n- Borrow cap\n    - `gap`: 10,000 wstETH\n    - `ttl`: 12 hours\n    - `max`: 1 wstETH","contentHash":"70d009e14683ee7663c084b830988b6a8a943b7bfaed881b8072c48ef57548d6","addressRefs":[]},"4bec80b2-33d2-48a9-83e6-26bb2a00e303":{"id":"4bec80b2-33d2-48a9-83e6-26bb2a00e303","doc_no":"A.6.1.1.1.3.2.1.1.3.2.3","title":"SparkLend Cap Automator rETH Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5095,"content":"The current rETH cap automator parameters are:\n\n- Supply cap\n    - `gap`: 10,000 rETH\n    - `ttl`: 12 hours\n    - `max`: 80,000 rETH\n- Borrow cap\n    - `gap`: 100 rETH\n    - `ttl`: 12 hours\n    - `max`: 1 rETH","contentHash":"45e675d4cc29d2f0b55d7f92c923fffd0178a11079f8c929d0861ed72863d6e5","addressRefs":[]},"b67fb946-b21d-4173-b57b-e5505128f003":{"id":"b67fb946-b21d-4173-b57b-e5505128f003","doc_no":"A.6.1.1.1.3.2.1.1.3.2.4","title":"SparkLend Cap Automator WBTC Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5096,"content":"The current WBTC cap automator parameters are:\n\n- Supply cap\n    - `gap`: 200 WBTC\n    - `ttl`: 12 hours\n    - `max`: 5,000 WBTC\n- Borrow cap\n    - `gap`: 1 WBTC\n    - `ttl`: 12 hours\n    - `max`: 1 WBTC","contentHash":"8da95b53b306a9375efb42bb34adb6c2aa8468b5f9e3ff4c0b6d6ee00ebd6c5c","addressRefs":[]},"21bdfe50-0996-494d-8413-1d41966fb4f6":{"id":"21bdfe50-0996-494d-8413-1d41966fb4f6","doc_no":"A.6.1.1.1.3.2.1.1.3.2.5","title":"SparkLend Cap Automator sDai Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5097,"content":"The current sDai cap automator parameters are:\n\n- Supply cap\n    - `gap`: 50 million sDai\n    - `ttl`: 12 hours\n    - `max`: 1 billion sDai\n- Borrow cap: n/a - not a borrowable asset\n    - `gap`: n/a\n    - `ttl`: n/a\n    - `max`: 0 sDAI","contentHash":"24f54fd431b1a9f72d2e96c652785bc981bd318c0c4a88f71a4b05e02de9af44","addressRefs":[]},"07f1853e-ec34-44ae-b137-708a81cd3195":{"id":"07f1853e-ec34-44ae-b137-708a81cd3195","doc_no":"A.6.1.1.1.3.2.1.1.3.2.6","title":"SparkLend Cap Automator USDC Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5098,"content":"The current USDC cap automator parameters are:\n\n- Supply cap\n    - `gap`: 150 million USDC\n    - `ttl`: 12 hours\n    - `max`: 0 (no cap)\n- Borrow cap\n    - `gap`: 50 million USDC\n    - `ttl`: 12 hours\n    - `max`: 0 (no cap)","contentHash":"f3500236171dc285fbe83abf76b7056bd80776840bf3d607caa8424d9a1b05ca","addressRefs":[]},"7edd58f1-df79-4346-803b-4d01883e3f09":{"id":"7edd58f1-df79-4346-803b-4d01883e3f09","doc_no":"A.6.1.1.1.3.2.1.1.3.2.7","title":"SparkLend Cap Automator USDT Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5099,"content":"The current USDT cap automator parameters are:\n\n- Supply cap\n    - `gap`: 1 billion USDT\n    - `ttl`: 12 hours\n    - `max`: 0 (no cap)\n- Borrow cap\n    - `gap`: 200 million USDT\n    - `ttl`: 12 hours\n    - `max`: 0 (no cap)","contentHash":"da8c2cfc61a85ce9c49d2c0519924f144bb9ece1b7dd67f3ca29dc3c9c064d51","addressRefs":[]},"e2b2d7b0-56f9-408e-a49c-cfd211a20748":{"id":"e2b2d7b0-56f9-408e-a49c-cfd211a20748","doc_no":"A.6.1.1.1.3.2.1.1.3.2.8","title":"SparkLend Cap Automator cbBTC Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5100,"content":"The current cbBTC cap automator parameters are:\n\n- Supply cap\n    - `gap`: 500 cbBTC\n    - `ttl`: 12 hours\n    - `max`: 20,000 cbBTC\n- Borrow cap\n    - `gap`: 50 cbBTC\n    - `ttl`: 12 hours\n    - `max`: 10,000 cbBTC","contentHash":"76f0666872fe746985ea6e9d9cabb0eabdd6c9fad42fc3756b3e4166d7c1ee4e","addressRefs":[]},"061ca4e3-08a7-4262-aa22-9a79b988cf89":{"id":"061ca4e3-08a7-4262-aa22-9a79b988cf89","doc_no":"A.6.1.1.1.3.2.1.1.3.2.9","title":"SparkLend Cap Automator sUSDS Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5101,"content":"The current sUSDS cap automator parameters are:\n\n- Supply cap\n    - `gap`: 50 millions sUSDS\n    - `ttl`: 12 hours\n    - `max`: 500 million sUSDS\n- Borrow cap\n    - `gap`: N/A\n    - `ttl`: N/A\n    - `max`: N/A","contentHash":"c21742e4cedaff7ac09e6564468a3aa32426c3e176206491ba6649cc83bd73a7","addressRefs":[]},"cc049d6b-327f-4c85-aab0-97c976405e39":{"id":"cc049d6b-327f-4c85-aab0-97c976405e39","doc_no":"A.6.1.1.1.3.2.1.1.3.2.10","title":"SparkLend Cap Automator weETH Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5102,"content":"The current weETH cap automator parameters are:\n\n- Supply cap\n    - `gap`: 10,000 weETH\n    - `ttl`: 12 hours\n    - `max`: 500,000 weETH\n- Borrow cap\n    - `gap`: N/A\n    - `ttl`: N/A\n    - `max`: N/A","contentHash":"fa000979c6e1e279e717ac5c86bd2b1b16e5e3ecf74180409ecb468f987dd6ab","addressRefs":[]},"b0837675-5d32-43ee-84f9-076fe644c61e":{"id":"b0837675-5d32-43ee-84f9-076fe644c61e","doc_no":"A.6.1.1.1.3.2.1.1.3.2.11","title":"SparkLend Cap Automator LBTC Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5103,"content":"The current LBTC cap automator parameters are:\n\n- Supply cap\n    - `gap`: 500 LBTC\n    - `ttl`: 12 hours\n    - `max`: 10,000 LBTC\n- Borrow cap\n    - `gap`: N/A\n    - `ttl`: N/A\n    - `max`: N/A","contentHash":"0a4b84feb3ffd3c25aa4c05ca7a23bdf1f0e0c6f5397b02cb72866dc29998f39","addressRefs":[]},"33ee5bdf-e28d-4c9f-98a2-3e7b28bd9b50":{"id":"33ee5bdf-e28d-4c9f-98a2-3e7b28bd9b50","doc_no":"A.6.1.1.1.3.2.1.1.3.2.12","title":"SparkLend Cap Automator tBTC Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5104,"content":"The current tBTC cap automator parameters are:\n\n- Supply cap\n    - `gap`: 125 tBTC\n    - `ttl`: 12 hours\n    - `max`: 1,000 tBTC\n- Borrow cap\n    - `gap`: 25 tBTC\n    - `ttl`: 12 hours\n    - `max`: 900 tBTC","contentHash":"949921add60856ae659b3a99f7260db089a5dba6ae9c4d0913f6c81d72e66846","addressRefs":[]},"10f81b39-59d8-4f8c-837b-6f8eb00804b8":{"id":"10f81b39-59d8-4f8c-837b-6f8eb00804b8","doc_no":"A.6.1.1.1.3.2.1.1.3.2.13","title":"SparkLend Cap Automator ezETH Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5105,"content":"The current ezETH cap automator parameters are:\n\n- Supply cap\n    - `gap`: 5,000 ezETH\n    - `ttl`: 12 hours\n    - `max`: 40,000 ezETH\n- Borrow cap\n    - `gap`: N/A\n    - `ttl`: N/A\n    - `max`: N/A","contentHash":"be3a30e887e553970a5bc31b07b452bd1d9817b24e2db1844ec60029ea9abbaa","addressRefs":[]},"e8012cc7-5e8c-47e7-af44-d7e61bd16b3e":{"id":"e8012cc7-5e8c-47e7-af44-d7e61bd16b3e","doc_no":"A.6.1.1.1.3.2.1.1.3.2.14","title":"SparkLend Cap Automator rsETH Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5106,"content":"The current rsETH cap automator parameters are:\n\n- Supply cap\n    - `gap`: 5,000 rsETH\n    - `ttl`: 12 hours\n    - `max`: 40,000 rsETH\n- Borrow cap\n    - `gap`: N/A\n    - `ttl`: N/A\n    - `max`: N/A","contentHash":"77d254945e1ba67614c3174fe8a00d0295484c1bffcab82790191537180dc716","addressRefs":[]},"c06b8247-1397-4887-b1e6-0ea370d25dc9":{"id":"c06b8247-1397-4887-b1e6-0ea370d25dc9","doc_no":"A.6.1.1.1.3.2.1.1.3.2.15","title":"SparkLend Cap Automator pyUSD Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5107,"content":"The current pyUSD cap automator parameters are:\n\n- Supply cap\n    - `gap`: 50 million pyUSD\n    - `ttl`: 12 hours\n    - `max`: 0 (no cap)\n- Borrow cap\n    - `gap`: 25 million pyUSD\n    - `ttl`: 12 hours\n    - `max`: 0 (no cap)","contentHash":"f3db9ef7aa49d839058873c53ffe134253ab6d627cf6bbf84a35298e19345674","addressRefs":[]},"e58645fb-0085-4ea2-aba5-c4b5968038b8":{"id":"e58645fb-0085-4ea2-aba5-c4b5968038b8","doc_no":"A.6.1.1.1.3.2.1.1.3.3","title":"SparkLend Cap Automator Authorized Parties","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5108,"content":"The SparkLend Cap Automator can be triggered by any of the authorized parties below:\n\n- `0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178` (ALM Proxy Freezable)","contentHash":"2a7b6e4423d54e7eef02acda5fe3ccb63ca9614ec4c4e74a4e58299e7a11115c","addressRefs":["0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"2b17cf11-f0e3-4118-bbac-6a8458b4f70a":{"id":"2b17cf11-f0e3-4118-bbac-6a8458b4f70a","doc_no":"A.6.1.1.1.3.2.1.1.3.4","title":"SparkLend Cap Automator Version","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5109,"content":"The SparkLend Cap Automator Version is: 1.1","contentHash":"5950b620208f10380dee6e7423c88d90571fd2247132d4de642063f9aef98bee","addressRefs":[]},"38329b4f-7666-4f68-ba66-74ebb2e60e13":{"id":"38329b4f-7666-4f68-ba66-74ebb2e60e13","doc_no":"A.6.1.1.1.3.2.1.1.4","title":"SparkLend Risk Parameters Kill Switch","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5110,"content":"The kill switch disables all borrowing across SparkLend markets in the event of a depeg on key collateral assets.\n\nThe kill switch is defined in terms of a threshold for specified pegged assets. If the ratio of the price of a specified asset to its peg is equal to or less than the threshold, then any user can trigger the kill switch to disable borrowing across all SparkLend markets.\n\nAfter the kill switch is triggered, markets can be reactivated by Sky Governance after resetting the kill switch. Resetting the kill switch is subject to the Governance Security Delay specified in [A.1.10.3 - Governance Security Delay Requirements](c5f0e955-0441-42e0-a6fc-eab875bba568).","contentHash":"6adecc81c6a7f25ea4754f7c33b0bbd0f3e14197274ba19801ee0c10e03e87fe","addressRefs":[]},"d9e7ca3f-53f9-46aa-9e2c-c09f9d6392e1":{"id":"d9e7ca3f-53f9-46aa-9e2c-c09f9d6392e1","doc_no":"A.6.1.1.1.3.2.1.1.4.1","title":"SparkLend Risk Parameters Kill Switch Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5111,"content":"The kill switch currently covers the following assets with the specified thresholds:\n\n- wstETH/ETH - 0.95\n- LBTC/BTC - 0.95\n- weETH/ETH - 0.95\n- rETH/ETH - 0.95\n- cbBTC/BTC - 0.95\n- WBTC/BTC - 0.95","contentHash":"50deb26b9d09234d2598b7e816e6996973105ffe4c53a26cef9c93e1d9e492d5","addressRefs":[]},"e547484b-1388-4cc2-a03f-971b96c341bd":{"id":"e547484b-1388-4cc2-a03f-971b96c341bd","doc_no":"A.6.1.1.1.3.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5112,"content":"The documents herein define the process for the ongoing management of SparkLend. Future iterations of the Artifact will specify operational processes owned by Spark.","contentHash":"385c328c784fb0325f1e06636fcd5da81b1c02c5b9bdd999f0e0fac94016ba7e","addressRefs":[]},"6029a425-ad81-46c5-866d-94e2ff663873":{"id":"6029a425-ad81-46c5-866d-94e2ff663873","doc_no":"A.6.1.1.1.3.2.1.2.1","title":"SparkLend Risk Parameters Modification","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5113,"content":"The modification of SparkLend parameters is temporarily controlled by Sky Core, but will be transitioned to Spark in the future. Currently, the Core Council Risk Advisor, in consultation with Phoenix Labs, may recommend changes to any of the parameters specified in the subdocuments of [A.6.1.1.1.3.2.1.1.1 - SparkLend Risk Parameters Definitions](667abf8c-64a3-4029-b218-e7a6e7000bbd) or [A.6.1.1.1.3.2.1.1.3.1 - SparkLend Risk Parameters Cap Automator Parameter Definitions](e6bc54e6-91df-4095-a032-0e1128c2cab7).\n\nAs a general rule, the modification of said parameters is pursuant to the Operational Weekly Cycle and can be effected directly via an Executive Vote, without requiring a Governance Poll.","contentHash":"56c1ede7c947f73b665af625e2d6a40f3fa50c579e5ae588ea11d040fa03f736","addressRefs":[]},"1a1f4bef-d19d-42ff-8ac4-746498df9fbc":{"id":"1a1f4bef-d19d-42ff-8ac4-746498df9fbc","doc_no":"A.6.1.1.1.3.2.1.2.2","title":"Collateral Onboarding/Offboarding","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5114,"content":"The onboarding/offboarding of SparkLend collateral is temporarily controlled by Sky Core, but will be transitioned to Spark in the future. Currently, it is implemented by the Stability Facilitators, in consultation with the Core Council Risk Advisor and Phoenix Labs, through the Operational Weekly Cycle.","contentHash":"527cd648436a9b0615116218dabf1cb0fc81a192875d9b649051b4d72674dde6","addressRefs":[]},"a9529f7f-c2fa-4d56-a2b1-0a75e78fd135":{"id":"a9529f7f-c2fa-4d56-a2b1-0a75e78fd135","doc_no":"A.6.1.1.1.3.2.1.2.3","title":"Spark Protocol-Aave Revenue Share","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5115,"content":"Spark Protocol must pay out 10% of the income it generates from operating the borrowing and lending functionality of the protocol that is based on the Aave codebase. The documents herein define the Spark Protocol-Aave Revenue Share and its associated operational processes.","contentHash":"df6626b4d41f120c50684904c20551a4ceef48cfc9ea30c6a4d32350dc357982","addressRefs":[]},"f84a1cb6-7f77-4bd0-904f-8bf7b368d2d6":{"id":"f84a1cb6-7f77-4bd0-904f-8bf7b368d2d6","doc_no":"A.6.1.1.1.3.2.1.2.3.1","title":"Sky Core Governance Responsibility For Virtual Revenue Share Prior to Launch of SPK","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5116,"content":"Before the launch of Agent tokens, Sky Governance is temporarily responsible for paying out a \"virtual revenue share\" on behalf of Spark Protocol. It is calculated by taking the total amount of Dai borrowed from Spark Protocol, and then assuming a \"virtual income\" equivalent to 1% of this supply, and calculating a revenue share of 10% on that basis. The calculations and payments must be done manually by the Support Facilitators at the end of each quarter.\n\nAs an example: if, before the launch of Agent tokens, 200 million Dai is borrowed on Spark Protocol, then the virtual income is 1% of 200 million Dai, which gives 2 million Dai; and of that 2 million Dai the virtual revenue share is 200,000 Dai.\n\nThis 200,000 Dai must be paid out in incremental payments each quarter directly by Sky Governance from the Sky Surplus Buffer to a smart contract under the control of Aave Governance. If, before the launch of Agent tokens, less than 100 million Dai is borrowed from Spark Protocol by the Sky Protocol, accrual towards the virtual revenue share payments are paused (unpaid virtual revenue share that already accrued is still paid out at the end of the quarter), and the counting down of the revenue share duration is paused. The virtual revenue share payments and the counting down of the remaining revenue share duration is resumed when at least 100 million Dai is again borrowed from Spark Protocol by the Sky Protocol.\n\nOnce SPK tokens launch, the virtual revenue share system will be discontinued, and the standard rules of the Spark Protocol Aave Revenue Share Ecosystem Agreement shall take effect. See [A.6.1.1.1.3.2.1.2.3.2 - Standard Agreement Post SPK Launch](bb867551-5231-4a5b-ac37-09d545bf70ce).","contentHash":"7ed5404a665e544dbeb689a131d70122ac3f37c56616d23e1e182c1ec4ecf66f","addressRefs":[]},"bb867551-5231-4a5b-ac37-09d545bf70ce":{"id":"bb867551-5231-4a5b-ac37-09d545bf70ce","doc_no":"A.6.1.1.1.3.2.1.2.3.2","title":"Standard Agreement Post SPK Launch","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5117,"content":"Post SPK launch, the following revenue-share operational process takes effect. The revenue share payment must be calculated manually at the end of each quarter by the Spark and manually paid as Dai to a smart contract under the control of Aave Governance from Spark. The payments must occur for the revenue share duration of two (2) years, starting from September 25th, 2023.\n\nIf at any point in time after the launch of Agent tokens, Spark Protocol is generating less than 1 million Dai per year in income for Spark Agent, accrual towards the revenue share payments are paused (unpaid revenue share that already accrued is still paid out at the end of the quarter), and the counting down of the revenue share duration is paused. The revenue share payments and the counting down of the remaining revenue share duration is resumed when Spark Protocol is generating more than 1 million Dai per year in income again.","contentHash":"d2bacb0ca8f835c6d2a1e101e4317382062d1ac389c6596e47a36d998e665078","addressRefs":[]},"2301085e-3492-422b-8b75-c6dd6564ef29":{"id":"2301085e-3492-422b-8b75-c6dd6564ef29","doc_no":"A.6.1.1.1.3.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5118,"content":"The documents herein contain data relevant to SparkLend.","contentHash":"6e25b127d6abebddd46ae034bf2ed5357c189d8116963507a7c71fd8c2491554","addressRefs":[]},"b4172fc3-9566-4512-b058-75040e47e3bf":{"id":"b4172fc3-9566-4512-b058-75040e47e3bf","doc_no":"A.6.1.1.1.3.2.2","title":"Spark Pre-launch Token Rewards","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5119,"content":"The subdocuments herein define the parameters and operational processes related to Spark’s pre-launch token rewards program. These rewards will be paid exclusively out of the SPK tokens held by the Spark Foundation.","contentHash":"6cc3785526a0f0d5c46a2e96c8481926c7a8a6a583dd9f4b05ac16139cf260c1","addressRefs":[]},"666671f0-ce3b-4b3f-bf72-d163afa42f4e":{"id":"666671f0-ce3b-4b3f-bf72-d163afa42f4e","doc_no":"A.6.1.1.1.3.2.2.1","title":"Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5120,"content":"The parameters of the Spark Pre-launch Token Rewards are specified in the subdocuments herein.","contentHash":"8a1098265b3f722d00a287add94b2ef338fdb1ac4d46548065e989d22c618862","addressRefs":[]},"93dddb43-1d2e-4ea8-ab18-eb0518a193ba":{"id":"93dddb43-1d2e-4ea8-ab18-eb0518a193ba","doc_no":"A.6.1.1.1.3.2.2.1.1","title":"Conditions For The Pre-launch Token Rewards","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5121,"content":"Spark has a pre-launch token rewards program based on the usage of its lending platform. Users of the platform will receive an airdrop of SPK tokens, depending on how much and how long they have used the platform during the pre-launch token reward period. These rewards are only for users on Ethereum Mainnet.\n\nThere are two seasons of the Spark pre-launch token rewards: Season 1 and Season 2.\n\nSeason 1 of pre-launch token rewards was active from August 20 2023 and lasted for nine months, ending on May 20 2024. 130,434,783 SPK tokens were allocated in this period.\n\nIn Season 2 14,478,261 SPK will be rewarded per month to SparkLend users who qualify for the airdrop.\n\nSeason 2 is an additional pre-farming period, which runs until the Spark Agent launches as part of Sky Endgame launch season.\n\nThe monthly SPK rewards are allocated as follows:\n\n- 80 % is allocated to users borrowing DAI and/or USDS\n- 20 % is allocated to users supplying ETH\n\nThe proposed full anti-cheat SPK Airdrop for SparkLend is calculated using the following formula:\n\n`Airdrop = 80% * (DAI Borrows + USDS Borrows - sDAI Supplies * sDAI Liquidation Threshold - sUSDS Supplies * sUSDS Liquidation Threshold) + 20% * (ETH Supplies - ETH Borrows / ETH Liquidation Threshold)`\n\nAll supplies and borrows are denominated in USD based on the on-chain oracle price at that block to determine the conversion.","contentHash":"e1f9e487d935e83227fe53c3981246d0b1936fa656443b92fb9a3a74b70da476","addressRefs":[]},"ba833546-a8aa-4390-9c87-0204abd53e4b":{"id":"ba833546-a8aa-4390-9c87-0204abd53e4b","doc_no":"A.6.1.1.1.3.2.2.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5122,"content":"The documents herein define the process for the ongoing management of the Spark Pre-launch Token Rewards.","contentHash":"0dd0cba8e2299a6f755365e06d1086591357cf37b51c48dd055a5e95ae3d09f3","addressRefs":[]},"9906332c-bc2d-4864-97d4-589f206d6482":{"id":"9906332c-bc2d-4864-97d4-589f206d6482","doc_no":"A.6.1.1.1.3.2.2.2.1","title":"Special Pre-launch Token Reward Programs","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5123,"content":"Spark can activate a new SPK token pre-launch token reward airdrop program to capture other growth opportunities.\n\nThe program can last until the moment SPK launches, or a shorter duration. When activated, the exact details of the special pre-launch token reward airdrop program must be specified in [A.6.1.1.1.3.2.2.2.1.1.0.6.1 - Special Pre-launch Token Reward Program Details](51316a6c-fd6a-4507-b99d-731e80fc9f76).\n\nThe SPK tokens for the future Spark Airdrop are allocated between all borrowers based on a formula announced by Spark and specified in the above cited document. The rate of SPK tokens being earned is 7,239,130 SPK per month, distributed on a per block basis proportional to the formula specified in the above cited document.","contentHash":"b2cf28fbf05dd0afbb3ef2e3f6e0eaf256f101cf52a3d9a996fc91fe45980d5b","addressRefs":[]},"1e4ea33d-2d0d-4cfc-8ac2-febce5baf883":{"id":"1e4ea33d-2d0d-4cfc-8ac2-febce5baf883","doc_no":"A.6.1.1.1.3.2.2.2.1.1","title":"Special Pre-launch Token Reward Program Details","type":"Active Data Controller","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5124,"content":"The special pre-launch token reward airdrop program is defined as Active Data in [A.6.1.1.1.3.2.2.2.1.1.0.6.1 - Special Pre-launch Token Reward Program Details](51316a6c-fd6a-4507-b99d-731e80fc9f76).\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5dc9c5811d6266a7ccbc3401f37727fd1af91a098b74e18435166c209e139534","addressRefs":[]},"51316a6c-fd6a-4507-b99d-731e80fc9f76":{"id":"51316a6c-fd6a-4507-b99d-731e80fc9f76","doc_no":"A.6.1.1.1.3.2.2.2.1.1.0.6.1","title":"Special Pre-launch Token Reward Program Details","type":"Active Data","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5125,"content":"Active pre-launch token reward programs established by [A.6.1.1.1.3.2.2.2.1 - Special Pre-launch Token Reward Programs](9906332c-bc2d-4864-97d4-589f206d6482) are:\n\nAave V3 Main Market sUSDS (7,239,130 SPK per month, ending with SPK token launch):\n\nsUSDS supplies on Aave V3 Main Market are eligible to earn 7,239,130 SPK tokens per month. The SPK rewards program will start on the block during which the sUSDS market is onboarded onto the Aave V3 Main Market and lasts until the issuance of the SPK token, based on the following formula:\n\n`sUSDS Supplies - Sum_i(Stablecoin_i Borrow Amount (in USD) / Stablecoin_i Liquidation Threshold)`","contentHash":"a41b4e90e0418d7dfa59742256cd37e6c27c0cabd9de185fbbd8181d4ed2bf2e","addressRefs":[]},"4ffe4c6e-0dc0-4cb5-9365-8e5a62f0caa5":{"id":"4ffe4c6e-0dc0-4cb5-9365-8e5a62f0caa5","doc_no":"A.6.1.1.1.3.2.2.3","title":"Data Repository","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5126,"content":"The documents herein contain data relevant to the Spark Pre-launch Token Rewards.","contentHash":"71a3d3e36274b4b18d0ac35b83250d933a6c5f1700bdbf8433d0f639dd220816","addressRefs":[]},"599fad77-5117-44b2-83c6-3028b2a8a160":{"id":"599fad77-5117-44b2-83c6-3028b2a8a160","doc_no":"A.6.1.1.1.3.3","title":"Ecosystem Accords","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5127,"content":"Spark has formally agreed to the Ecosystem Accords herein.","contentHash":"1bacdda8e5ff0b6281b9fa454d8cf48fc451b50fdc7bf55ffc0a3b45a5183beb","addressRefs":[]},"7e68a753-88bc-4711-b709-3b5be9e286ad":{"id":"7e68a753-88bc-4711-b709-3b5be9e286ad","doc_no":"A.6.1.1.1.3.3.1","title":"Ecosystem Accord 1","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5128,"content":"Spark engaged in terms of agreement with the Grove Agent in Ecosystem Accord 1, located in [A.2.8.2.1 - Ecosystem Accord 1: Grove And Spark Agents](9ca40096-937e-431e-af50-9ecd50c0d0a8).","contentHash":"6e0d3c409e54e1b0d01043bf2ae4bb140bb393e10a3f152fef4d9f7d4669ee45","addressRefs":[]},"3b3961e9-9763-499e-bb75-0ea6a9af16b9":{"id":"3b3961e9-9763-499e-bb75-0ea6a9af16b9","doc_no":"A.6.1.1.1.3.3.1.1","title":"Right of First Refusal Activity","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5129,"content":"The subdocuments herein record the Right of First Refusal activity engaged in by Spark.","contentHash":"59387aaafb02d78bb95a7eb9decdbcfe5bdf6521cd720f41f8472265b198186f","addressRefs":[]},"c8fbcc0c-37c2-4ecc-84a6-a0e4607f9753":{"id":"c8fbcc0c-37c2-4ecc-84a6-a0e4607f9753","doc_no":"A.6.1.1.1.3.3.1.1.1","title":"Right of First Refusal Forgoing","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5130,"content":"Spark forwent exercising its Right of First Refusal in order to enable Grove to deploy in Aave Core RLUSD.","contentHash":"8e40c98b95d2cb800980ef8aebb6780ed8fa15400c91703f9a62626737288cc5","addressRefs":[]},"d8c5d4f5-5b32-4897-8174-90de0b3d9d84":{"id":"d8c5d4f5-5b32-4897-8174-90de0b3d9d84","doc_no":"A.6.1.1.1.3.3.2","title":"Ecosystem Accord 2","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5131,"content":"Spark engaged in terms of agreement with Sky, Moonbow and Grove in Ecosystem Accord 2, located in [A.2.8.2.2 - Prime Program](aa3b8e65-0ded-48c2-9c40-812debf99f32).","contentHash":"bfd5e44804e81acea17030b339befcd122f98bcce00134225787271193e468ec","addressRefs":[]},"2ad53f55-44cb-44fd-9e68-6c7ed128e360":{"id":"2ad53f55-44cb-44fd-9e68-6c7ed128e360","doc_no":"A.6.1.1.1.3.4","title":"SubDAO Proxy Management","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5132,"content":"The documents herein specify Spark's strategy and operational processes for managing assets held in the Spark SubDAO Proxy, and obligations relating to these assets.","contentHash":"65d9a6024c54278494082c03a126a8d7c0c4a5bbfa90c3fd19abc03e4fc9fc2f","addressRefs":[]},"bfdc08d5-42f5-4d49-9390-b6ad210c5c40":{"id":"bfdc08d5-42f5-4d49-9390-b6ad210c5c40","doc_no":"A.6.1.1.1.3.4.1","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5133,"content":"The documents herein define the process for updating Spark's SubDAO Proxy management policies.","contentHash":"69bebcc2ade9973c1c79560bb186738a2a128c8d028035e336f2203519cd8221","addressRefs":[]},"90240e75-6e5f-4a54-8999-ee430cfcf20d":{"id":"90240e75-6e5f-4a54-8999-ee430cfcf20d","doc_no":"A.6.1.1.1.3.4.1.1","title":"Spark SubDAO Proxy Policy Changes","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5134,"content":"Changes to Spark SubDAO Proxy management policies are implemented using the Root Edit Primitive.","contentHash":"03102138a1532ce6fbedd3f7440cd5b065a83fc5ab09fb312e0de8909102addc","addressRefs":[]},"8a421648-d732-44c1-8666-bbbb9b7bfff2":{"id":"8a421648-d732-44c1-8666-bbbb9b7bfff2","doc_no":"A.6.1.1.1.3.4.1.2","title":"Preapproved Subdao Proxy Activities","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5135,"content":"Dispositions of Spark SubDAO Proxy assets that have already been approved by governance and added to the Spark artifact, including periodic payments and disposal of non-core assets, can continue as planned until a superseding policy change is adopted via the Spark SubDAO Proxy Policy Changes process.","contentHash":"e8d0ee582b0f696ce976cf943409abb408b8c5be8c6ac2d70050609d82374beb","addressRefs":[]},"262ff1c9-9634-45a4-9f18-ed222352ddb4":{"id":"262ff1c9-9634-45a4-9f18-ed222352ddb4","doc_no":"A.6.1.1.1.3.4.2","title":"Policies and Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5136,"content":"The documents herein define the currently active policies for managing the Spark SubDAO Proxy, alongside relevant parameters for implementing the policies.","contentHash":"b1015f193c8680e6ca919587024fa356372f8ffd1e398216017ab0deed2ef4bb","addressRefs":[]},"9995ba51-1de7-4b32-8b76-a71462dc4c5b":{"id":"9995ba51-1de7-4b32-8b76-a71462dc4c5b","doc_no":"A.6.1.1.1.3.4.2.1","title":"Encumbrance Ratio","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5137,"content":"The documents herein define Spark's policy for managing the Encumbrance Ratio.","contentHash":"1369e15d620872d662ed7b539f0d82e5de4dc8e2b2434bfa342c47966b7edbfb","addressRefs":[]},"f426cc6e-336a-43bf-825d-1f0c08d1795e":{"id":"f426cc6e-336a-43bf-825d-1f0c08d1795e","doc_no":"A.6.1.1.1.3.4.2.1.1","title":"Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5138,"content":"The Encumbrance Ratio is defined as the ratio of Spark's Required Risk Capital (RRC) to Total Risk Capital (TRC), as these terms are defined in the Sky Atlas Stability Scope ([A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9)). Spark will seek to maintain a Encumbrance Ratio not greater than the Target Risk Tolerance Ratio specified in [A.6.1.1.1.3.4.2.1.3 - Parameters](d65a06a6-1426-4af2-978c-cd4f7bac79b7).","contentHash":"195ec0ecf0500ba809d420721080f8baa251a01677dfaf92e369cc1182b4c01f","addressRefs":[]},"7bc96051-ce11-4e29-aa30-b535183aeaa7":{"id":"7bc96051-ce11-4e29-aa30-b535183aeaa7","doc_no":"A.6.1.1.1.3.4.2.1.2","title":"Operational Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5139,"content":"Spark governance and contributors must take immediate action to reduce the Encumbrance Ratio when it exceeds the Target Encumbrance Ratio level. These actions may fall into two categories, risk capital actions or allocation system actions.\n\nRisk capital actions are actions Spark takes to increase Total Risk Capital, including increasing Internal Junior Risk Capital, sourcing External Junior Risk Capital from other Prime Agents or tokenized sources, or sourcing External Senior Risk Capital from Sky or tokenized sources.\n\nAllocation system actions involve adjusting the capital allocations within the Spark instance of the Allocation System to reduce Required Risk Capital, such as unwinding or disposing of assets requiring higher levels of risk capital as a percent of exposure.\n\nThe operational processes implemented at Spark will meet or exceed the requirements specified in the Sky Atlas at [A.2.2.9.1.1.3.2.1.2 - Primes’ Total Risk Capital (TRC) Management](3af8a3a2-25e5-44b3-87a4-7df1f2712685).","contentHash":"bac33656ebc4e66770f457d6cc07b8fc26a4cd2135c81d4bea902892d2047aaa","addressRefs":[]},"d65a06a6-1426-4af2-978c-cd4f7bac79b7":{"id":"d65a06a6-1426-4af2-978c-cd4f7bac79b7","doc_no":"A.6.1.1.1.3.4.2.1.3","title":"Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5140,"content":"The current Target Encumbrance Ratio is 90%.\n\nThis parameter will be maintained in parallel with the value specified in the Spark Artifact Allocation System Primitive section at [A.6.1.1.1.2.6.1.2.1.3.1 - Spark’s Operation Of Spark Liquidity Layer And Agreement Regarding Encumbrance Ratio](23f7ed09-99ca-45aa-8e12-dffcf55170af); any change to one section of the Spark Artifact will require a corresponding change in the other section.","contentHash":"5f5071ab73169de2a62315093a3d424666640d24a3a899aaff2597dbbae20423","addressRefs":[]},"2e676b28-14e8-4536-ab70-c49b896da8b8":{"id":"2e676b28-14e8-4536-ab70-c49b896da8b8","doc_no":"A.6.1.1.1.3.4.2.2","title":"Target SubDAO Proxy Value","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5141,"content":"The documents herein define Spark’s policy for maintaining a SubDAO Proxy balance sufficient to cover anticipated risk exposures and operational expenses.","contentHash":"00e496953daea0e00575b726094e2823521d420bc640179d608d15faebd07869","addressRefs":[]},"fd1df613-3038-4f60-9156-ecd4335addb0":{"id":"fd1df613-3038-4f60-9156-ecd4335addb0","doc_no":"A.6.1.1.1.3.4.2.2.1","title":"Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5142,"content":"The subdocuments herein provide definitions of target SubDAO Proxy value and relevant parameters.","contentHash":"083773d24d9faadd11f3acbdf409f040e6962e1e5531091a8c966eb20cc7ca43","addressRefs":[]},"3baabdcc-d715-419d-97b7-28936d4b0f95":{"id":"3baabdcc-d715-419d-97b7-28936d4b0f95","doc_no":"A.6.1.1.1.3.4.2.2.1.1","title":"Target SubDAO Proxy Value Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5143,"content":"Target SubDAO Proxy Value is the minimum target value of the Spark DAO SubDAO Proxy, below which Spark will not undertake any non-critical and non-strategic dispositions of SubDAO Proxy assets such as SPK token purchases.","contentHash":"c9255c711800216ce3aee731688c1f9dac915223ce6f800d78c11aae9e2ee24d","addressRefs":[]},"6e832698-c71b-441c-9132-4df8d0357351":{"id":"6e832698-c71b-441c-9132-4df8d0357351","doc_no":"A.6.1.1.1.3.4.2.2.1.2","title":"RRC Lookback Period Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5144,"content":"The Target SubDAO Proxy Value evaluation method ([A.6.1.1.1.3.4.2.2.2 - Evaluation Method](99d4b8da-fa5c-49ce-b93c-70d07334d7aa)) considers the higher of current Required Risk Capital (RRC) or highest RRC incurred within a trailing period. RRC Lookback Period defines the amount of time to review for the trailing period when evaluating the RRC component of Target SubDAO Proxy Value.","contentHash":"8938339407633edcaf8818c0c85da771fe3a3f724a2a2c9256d949075ce925cd","addressRefs":[]},"ac10196b-18b2-4bc4-8627-0cacac8a3524":{"id":"ac10196b-18b2-4bc4-8627-0cacac8a3524","doc_no":"A.6.1.1.1.3.4.2.2.1.3","title":"Spark Product Backstop Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5145,"content":"The Spark Product Backstop is a fixed value of USDS, updated from time to time by Spark governance via the Spark SubDAO Proxy Policy Changes process ([A.6.1.1.1.3.4.1.1 - Spark SubDAO Proxy Policy Changes](90240e75-6e5f-4a54-8999-ee430cfcf20d)), meant to cover the anticipated risk exposures to Spark products that are not covered under Sky’s Required Risk Capital framework.","contentHash":"1a0fde0498581ae2795f12cd777e9d3716b5233f356c6dcf0d0cdc4e38c9382b","addressRefs":[]},"0bd4cd1e-1a37-4209-8ac4-45c17facafd3":{"id":"0bd4cd1e-1a37-4209-8ac4-45c17facafd3","doc_no":"A.6.1.1.1.3.4.2.2.1.4","title":"Target Runway Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5146,"content":"Target Runway defines the amount of operational expenses Spark holds in reserve as part of the Target SubDAO Proxy Value. The operational expenses component of Target SubDAO Proxy Value counts the higher of past month’s operating expenses multiplied by Target Runway (in months), or total operating expenses incurred in trailing period equal to Target Runway.","contentHash":"97ffc914cb3f9f18896c405553ed7b791c43331a0d35c74025b938f5185a2df9","addressRefs":[]},"3ffad8de-515c-45e0-ac75-223d075cb9f8":{"id":"3ffad8de-515c-45e0-ac75-223d075cb9f8","doc_no":"A.6.1.1.1.3.4.2.2.1.5","title":"Operating Expense Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5147,"content":"Operating Expense is defined as the sum of governance-approved transfers to the Spark Foundation within a given period.","contentHash":"907d791d761dd1b822eeb8d2346b90bcae4e8575f76b4c707322d793f257db67","addressRefs":[]},"99d4b8da-fa5c-49ce-b93c-70d07334d7aa":{"id":"99d4b8da-fa5c-49ce-b93c-70d07334d7aa","doc_no":"A.6.1.1.1.3.4.2.2.2","title":"Evaluation Method","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5148,"content":"Target SubDAO Proxy Value is computed as the greater of Required Risk Capital (RRC) plus Spark Product Backstop, or Operational Expense Reserve.\n\nRRC is calculated as the higher of current RRC or highest RRC incurred within the RRC Lookback Period, divided by Risk Tolerance Ratio ([A.6.1.1.1.3.4.2.1 - Encumbrance Ratio](9995ba51-1de7-4b32-8b76-a71462dc4c5b)).\n\nSpark Product Backstop is set manually by Spark governance per [A.6.1.1.1.3.4.2.2.1.3 - Spark Product Backstop Definition](ac10196b-18b2-4bc4-8627-0cacac8a3524).\n\nOperational expense reserve is calculated as the higher of past month’s operating expenses multiplied by Target Runway (in months), or total operating expenses incurred in trailing period equal to Target Runway.","contentHash":"4b32422a70dc93869aeac1e67cf98f5e99447d303b53c831820a3c9b58dcaf43","addressRefs":[]},"7410ed94-db95-437a-a4d2-9120036ec7bd":{"id":"7410ed94-db95-437a-a4d2-9120036ec7bd","doc_no":"A.6.1.1.1.3.4.2.2.3","title":"Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5149,"content":"The current Target SubDAO Proxy Value parameters are:\n\n- RRC Lookback Period: 3 months\n- Spark Product Backstop: 1 million USDS\n- Target Runway: 12 months","contentHash":"e0b21539c4766a09fc0d27eb8f4b5428f22a998bdef233cc05ec48c91f5ae26d","addressRefs":[]},"6a4870fa-73f1-4d49-b7ee-d531fb59a971":{"id":"6a4870fa-73f1-4d49-b7ee-d531fb59a971","doc_no":"A.6.1.1.1.3.4.2.3","title":"Excess SubDAO Proxy Funds Disposition Policy","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5150,"content":"The documents herein define Spark’s policy for disposition of excess SubDAO Proxy funds above the target SubDAO Proxy value.","contentHash":"f1fd4fd6e29e0870f2943954d619e1711ee0b3a1c3da6c5ec8d512ac7025ac44","addressRefs":[]},"0da9928f-ae14-4869-b36b-761930422502":{"id":"0da9928f-ae14-4869-b36b-761930422502","doc_no":"A.6.1.1.1.3.4.2.3.1","title":"Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5151,"content":"The subdocuments herein provide definitions for relevant parameters and values.","contentHash":"afa192ac6d101d7d415f437eb7db360eb76cd4a44f04ed22d5bbb50867bf796c","addressRefs":[]},"9705a4be-e92f-4195-8e85-1cfe19ec1a0d":{"id":"9705a4be-e92f-4195-8e85-1cfe19ec1a0d","doc_no":"A.6.1.1.1.3.4.2.3.1.1","title":"Current SubDAO Proxy Value","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5152,"content":"The Current SubDAO Proxy Value is defined as the sum of all USDS tokens held in the Spark SubDAO on Ethereum at 0x3300f198988e4C9C63F75dF86De36421f06af8c4. Note that the operational process of excess SubDAO Proxy funds disposition as defined in [A.6.1.1.1.3.4.2.3.2 - Operational Process](dfa483c7-5adb-480e-9f82-c97cf4d0f74e) uses the most up-to-date onchain value for the Current SubDAO Proxy Value, and this does not need to be updated in the Spark Artifact as it is expected to fluctuate frequently based on monthly settlements and other operational processes.","contentHash":"712c8cc101d36ce0d988a43ea43d043750ea9ad4b59de7bead1971b75417e907","addressRefs":["0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"796dc640-03a7-4608-b676-a235a68174b1":{"id":"796dc640-03a7-4608-b676-a235a68174b1","doc_no":"A.6.1.1.1.3.4.2.3.1.2","title":"Standard Buyback Rate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5153,"content":"The Standard Buyback Rate defines the percentage of excess SubDAO Proxy value that is used for buybacks during each monthly cycle, up to the Enhanced Buyback Threshold.","contentHash":"61dc2e0e64e66a4977d0a7fa20adb262117a98741bd1b1a7129a9f57fe9c9147","addressRefs":[]},"0efbdfe8-3ccd-4e6a-8195-a52e7f63c1d9":{"id":"0efbdfe8-3ccd-4e6a-8195-a52e7f63c1d9","doc_no":"A.6.1.1.1.3.4.2.3.1.3","title":"Enhanced Buyback Rate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5154,"content":"The Enhanced Buyback Rate defines the percentage of SubDAO Proxy value in excess of the Enhanced Buyback Threshold that is used for buybacks during each monthly cycle.","contentHash":"1a71e593d1cd8d14d3de703eb10ada20439b127c83e135aa9040fbbb28fe6373","addressRefs":[]},"e150176c-1da5-4adb-ba5d-f344d0be03ae":{"id":"e150176c-1da5-4adb-ba5d-f344d0be03ae","doc_no":"A.6.1.1.1.3.4.2.3.1.4","title":"Enhanced Buyback Threshold","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5155,"content":"The Enhanced Buyback Threshold defines the threshold over which the Enhanced Buyback Rate is applied to calculate buyback amounts. This variable is specified as a percentage of the Target SubDAO Proxy Value; for example, a 200% Enhanced Buyback Threshold means that the Enhanced Buyback Rate will apply to any subDAO proxy value over 2x the Target SubDAO Proxy Value.","contentHash":"cfa169ebdd25ea124ced413a4256488cb32e3873ffbb5d80d58ae09aaaf16010","addressRefs":[]},"d6be588d-e76e-4413-8a3e-c1b59e5bd106":{"id":"d6be588d-e76e-4413-8a3e-c1b59e5bd106","doc_no":"A.6.1.1.1.3.4.2.3.1.5","title":"Buyback Executor","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5156,"content":"The Buyback Executor is the entity responsible for receiving excess SubDAO Proxy funds in USDS, purchasing SPK, and returning the SPK to the Spark SubDAO Proxy. Initially, this role will be performed by the Spark Operations Multisig.","contentHash":"51d0520a00505d03d414538d3ccd4282276157f5ac190cf6baa2b1ab3d4bcb56","addressRefs":[]},"dfa483c7-5adb-480e-9f82-c97cf4d0f74e":{"id":"dfa483c7-5adb-480e-9f82-c97cf4d0f74e","doc_no":"A.6.1.1.1.3.4.2.3.2","title":"Operational Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5157,"content":"Each month, immediately following Spark’s monthly settlement with Sky, the Current SubDAO Proxy Value with be calculated based on the definition in [A.6.1.1.1.3.4.2.3.1.1 - Current SubDAO Proxy Value](9705a4be-e92f-4195-8e85-1cfe19ec1a0d), and the Target SubDAO Proxy Value based on the evaluation method in [A.6.1.1.1.3.4.2.2.2 - Evaluation Method](99d4b8da-fa5c-49ce-b93c-70d07334d7aa). If the Current SubDAO Proxy Value is greater than the Target SubDAO Proxy Value, this excess SubDAO Proxy Value is multiplied by the Standard Buyback Rate parameter up to the Enhanced Buyback Threshold, and then by the Enhanced Buyback Rate for any amount in excess of the Enhanced Buyback Threshold. The buyback amount for the month is set as the sum of the two values of the standard and enhanced buybacks.\n\nThe next available Spark proxy Spell will include a transfer of this calculated buyback amount to the designated Buyback Executor. After using the transferred funds to purchase SPK, the Buyback Executor will transfer all accrued SPK to the Spark SubDAO Proxy.","contentHash":"08fc2d7d3038d7e30be139656f4f4ef2493402a3c6ed5fdb8db1b25b4b3b75bd","addressRefs":[]},"b52a4011-5346-4de7-9522-90ae66b81600":{"id":"b52a4011-5346-4de7-9522-90ae66b81600","doc_no":"A.6.1.1.1.3.4.2.3.3","title":"Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5158,"content":"The current buyback policy parameters are:\n\n- Standard Buyback rate: 25%\n- Enhanced Buyback rate: 100%\n- Enhanced Buyback threshold: 200%\n- Buyback executor: 0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC\n- Buyback recipient: 0x3300f198988e4C9C63F75dF86De36421f06af8c4","contentHash":"540307a81097a8e81b0805b593f3cb7d1eae7cd7830ee1cd4fc7720962429bc0","addressRefs":["0x2e1b01adabb8d4981863394bea23a1263cbaedfc","0x3300f198988e4c9c63f75df86de36421f06af8c4"]},"3b2d9368-7dd5-424a-b9da-b6218ffb5c55":{"id":"3b2d9368-7dd5-424a-b9da-b6218ffb5c55","doc_no":"A.6.1.1.1.3.4.2.4","title":"SPK Contributor Vesting","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5159,"content":"The documents herein define Spark’s policy for managing the SPK contributor vesting.","contentHash":"b2eb9b30f1a3295aeba17787d498d8e6eb9ac964c5ddb9a9423a960fbfc3dba7","addressRefs":[]},"318b9af4-5b49-41f1-b134-dd2133eafca8":{"id":"318b9af4-5b49-41f1-b134-dd2133eafca8","doc_no":"A.6.1.1.1.3.4.2.4.1","title":"Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5160,"content":"The SPK contributor vesting is a 4-year linear vesting schedule that compensates Spark contributors.","contentHash":"5bca9feeef9955c1d8564c71291705491ed7d3b768f7808e11c923c60a4d8cd5","addressRefs":[]},"0921d2d9-0270-40ab-bfad-726d3bcd345d":{"id":"0921d2d9-0270-40ab-bfad-726d3bcd345d","doc_no":"A.6.1.1.1.3.4.2.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5161,"content":"The current SPK contributor vesting parameters are:\n\n- DssVest\n    - Recipient address(es): `0xEFF097C5CC7F63e9537188FE381D1360158c1511`\n    - Start date: 17 June 2025\n    - Cliff date: 17 June 2026\n    - End date: 16 June 2029\n    - Vesting method: Linear per block with cliff\n    - Claim auth: Permissionless\n- SubDAO Proxy actions\n    - Approve SPK\n        - Address: `0x6Bad07722818Ceff1deAcc33280DbbFdA4939A09`\n        - Amount: 1.2 billion SPK (12% of total supply)","contentHash":"a5ec47618c66087358f86394b457a8febdd27ac095a17b9d8db4da3948d9cd7e","addressRefs":["0x6bad07722818ceff1deacc33280dbbfda4939a09","0xeff097c5cc7f63e9537188fe381d1360158c1511"]},"9b4ce799-3baa-42e8-a742-7e8deb377dfc":{"id":"9b4ce799-3baa-42e8-a742-7e8deb377dfc","doc_no":"A.6.1.1.1.3.5","title":"Spark Savings Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5162,"content":"The documents herein specify Spark's strategy and operational processes for managing parameters and liquidity for the Spark Savings protocol.","contentHash":"88b440d22fd644c97952f19a0f5507805c832d6bd41d054c7b93709539efcd8c","addressRefs":[]},"99f4c04b-e531-498a-aeaa-016c7811bf7a":{"id":"99f4c04b-e531-498a-aeaa-016c7811bf7a","doc_no":"A.6.1.1.1.3.5.1","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5163,"content":"The documents herein define the process for updating Spark Savings Configuration policies and parameters.","contentHash":"f60f84a111abe346cce24afd41325404f21ea3051d26a26e865280207a424ea9","addressRefs":[]},"d6405fa7-d02f-4c31-b191-ad1a2485cca3":{"id":"d6405fa7-d02f-4c31-b191-ad1a2485cca3","doc_no":"A.6.1.1.1.3.5.1.1","title":"Spark Savings Configuration Changes","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5164,"content":"Changes to Spark Savings Configuration policies and parameters are implemented using the Root Edit Primitive.","contentHash":"2337de23f9c26099028083230ba6baa35fc50b49ba52fc1904baae0ef10d20e6","addressRefs":[]},"32a8f019-86e2-47a0-a55d-c481ade62051":{"id":"32a8f019-86e2-47a0-a55d-c481ade62051","doc_no":"A.6.1.1.1.3.5.2","title":"Onchain Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5165,"content":"The documents herein define the onchain parameters that are implemented within Spark Savings.","contentHash":"7664e3f4f2c9bb006de984d39fa5533dbb5d0f16c9be2348f1afc6b49ecae86a","addressRefs":[]},"81198aca-06bd-44fa-90b0-16f8c2c4dd19":{"id":"81198aca-06bd-44fa-90b0-16f8c2c4dd19","doc_no":"A.6.1.1.1.3.5.2.1","title":"Spark Savings Parameters Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5166,"content":"The subdocuments herein provide definitions for Spark Savings onchain parameters.","contentHash":"7cc756b8e58c3b3c4bad05c5c6e4dde7d0a2bf301770c992e19cab56204a2bf6","addressRefs":[]},"a4d74779-a7d4-4f89-a1b0-8296227f9a9b":{"id":"a4d74779-a7d4-4f89-a1b0-8296227f9a9b","doc_no":"A.6.1.1.1.3.5.2.1.1","title":"Default Admin Role","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5167,"content":"The default admin role controls upgrades to Spark Savings vault contracts, and has overall admin control over the vault. This role will be assigned to Spark governance to ensure maximum possible security and decentralization.","contentHash":"0727a1a4d2185c0c6b40d084faf9980188dae139a4ebccabfe02c9355611d2ca","addressRefs":[]},"811c9931-3a70-4c64-a8fb-d1f162a46d62":{"id":"811c9931-3a70-4c64-a8fb-d1f162a46d62","doc_no":"A.6.1.1.1.3.5.2.1.2","title":"Setter Role","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5168,"content":"The setter role controls the current rewards rate for a Spark Savings vault, within the upper and lower bounds defined by the max yield and min yield onchain parameters.","contentHash":"f1da3e65c932be762151844751e7547e423365a64a9f7067dcde9be11f4d1ed1","addressRefs":[]},"a7fd125d-4017-48ba-a366-96253c6f3a16":{"id":"a7fd125d-4017-48ba-a366-96253c6f3a16","doc_no":"A.6.1.1.1.3.5.2.1.3","title":"Taker Role","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5169,"content":"The taker role has permission to withdraw a Spark Savings vault's underlying asset from the vault to the Spark Liquidity Layer ALM Proxy contract.","contentHash":"7b64c328255a5063d88643e170493e716c205cd6529cf07deb47b0359a24d0c1","addressRefs":[]},"e5dbc65a-45b9-41d5-ae13-56c3b3416b13":{"id":"e5dbc65a-45b9-41d5-ae13-56c3b3416b13","doc_no":"A.6.1.1.1.3.5.2.1.4","title":"Take Rate Limit","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5170,"content":"The take rate limit defines the maximum amount and pace of withdrawals from a Spark Savings vault permitted by the taker role.","contentHash":"6cbfe27ea4714bf73369bd438d5bb4b837aff24dbdd9565fa532296094e99b2e","addressRefs":[]},"739b7c5d-d1b5-48e6-a945-26db2a803854":{"id":"739b7c5d-d1b5-48e6-a945-26db2a803854","doc_no":"A.6.1.1.1.3.5.2.1.5","title":"Min Yield","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5171,"content":"The min yield parameter is the lowest Spark Savings vault rewards rate that can be implemented by the setter role. Typically this value will be 0.","contentHash":"2d645d26d4821b45459e5189fbc08ed3bbf4326757012b97247e3278441cab1f","addressRefs":[]},"ffc7bf31-df84-4c71-9da2-b4ebea95ae01":{"id":"ffc7bf31-df84-4c71-9da2-b4ebea95ae01","doc_no":"A.6.1.1.1.3.5.2.1.6","title":"Max Yield","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5172,"content":"The max yield parameter is the highest Spark Savings vault rewards rate that can be implemented by the setter role.","contentHash":"464272f66b41b905fd61cc6ab6235c57ef1cd13c8a9b9b85759c556b0081c37b","addressRefs":[]},"77918273-af7f-4c7e-80af-3f3d9d2097ec":{"id":"77918273-af7f-4c7e-80af-3f3d9d2097ec","doc_no":"A.6.1.1.1.3.5.2.1.7","title":"Supply Cap","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5173,"content":"The supply cap defines the maximum amount of underlying asset that can be deposited to a Spark Savings vault by users.","contentHash":"a593ea10e6f48008112dd79e1ed2062761524ad8c0202f17c16f0308a45dd32d","addressRefs":[]},"5cfe1941-3231-495c-a4c9-50745ec0a5a9":{"id":"5cfe1941-3231-495c-a4c9-50745ec0a5a9","doc_no":"A.6.1.1.1.3.5.2.2","title":"Spark Savings Parameters Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5174,"content":"The subdocuments herein provide the current configuration of Spark Savings onchain parameters.","contentHash":"320f4574806cb6d6dd86acc1a2cad3c7a6fe9bedd2cdad649aa596a58879ca16","addressRefs":[]},"e541391b-f470-480f-adea-5453f3f7da7a":{"id":"e541391b-f470-480f-adea-5453f3f7da7a","doc_no":"A.6.1.1.1.3.5.2.2.1","title":"Spark Savings USDC on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5175,"content":"The current parameters for Spark Savings USDC on Ethereum are:\n\n- Default admin role: 0x3300f198988e4C9C63F75dF86De36421f06af8c4\n- Setter role: 0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178\n- Taker role: 0x1601843c5E9bC251A3272907010AFa41Fa18347E\n- Take rate limit: unlimited\n- Min yield: 0%\n- Max yield: 10%\n- Supply cap: 10 billion","contentHash":"42001a78a884fdc259c9efd2fc9f84f81272e429f59171cc21a98d54f6581820","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e","0x3300f198988e4c9c63f75df86de36421f06af8c4","0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"39a398d7-600e-472a-ac85-c789866fddfc":{"id":"39a398d7-600e-472a-ac85-c789866fddfc","doc_no":"A.6.1.1.1.3.5.2.2.2","title":"Spark Savings USDT on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5176,"content":"The current parameters for Spark Savings USDT on Ethereum are:\n\n- Default admin role: 0x3300f198988e4C9C63F75dF86De36421f06af8c4\n- Setter role: 0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178\n- Taker role: 0x1601843c5E9bC251A3272907010AFa41Fa18347E\n- Take rate limit: unlimited\n- Min yield: 0%\n- Max yield: 10%\n- Supply cap: 10 billion","contentHash":"f85bb7250e1f2d80427dc56a679e8c15a7528000d531a277cc6e10f43a7ec673","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e","0x3300f198988e4c9c63f75df86de36421f06af8c4","0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"02c0847b-5608-4c12-a1f6-df889538722f":{"id":"02c0847b-5608-4c12-a1f6-df889538722f","doc_no":"A.6.1.1.1.3.5.2.2.3","title":"Spark Savings ETH on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5177,"content":"The current parameters for Spark Savings ETH on Ethereum are:\n\n- Default admin role: 0x3300f198988e4C9C63F75dF86De36421f06af8c4\n- Setter role: 0x9Ad87668d49ab69EEa0AF091de970EF52b0D5178\n- Taker role: 0x1601843c5E9bC251A3272907010AFa41Fa18347E\n- Take rate limit: unlimited\n- Min yield: 0%\n- Max yield: 5%\n- Supply cap: 1 million","contentHash":"c49bb70157b641d85b126d6abc528097492f789ac2b5c579d696775c8ab51171","addressRefs":["0x1601843c5e9bc251a3272907010afa41fa18347e","0x3300f198988e4c9c63f75df86de36421f06af8c4","0x9ad87668d49ab69eea0af091de970ef52b0d5178"]},"fc108236-9f07-45fb-9ff1-4c806975e049":{"id":"fc108236-9f07-45fb-9ff1-4c806975e049","doc_no":"A.6.1.1.1.3.5.2.2.4","title":"Spark Savings USDC on Avalanche","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5178,"content":"The current parameters for Spark Savings USDC on Avalanche are:\n\n- Default admin role: 0x7566DEbC906C17338524A414343fA61BcA26A843\n- Setter role: 0x45d91340B3B7B96985A72b5c678F7D9e8D664b62\n- Taker role: 0xecE6B0E8a54c2f44e066fBb9234e7157B15b7FeC\n- Take rate limit: unlimited\n- Min yield: 0%\n- Max yield: 10%\n- Supply cap: 150 million","contentHash":"bc7b7481a5bd622cd230c01306cbdb5890d4434a8a9acd09e9cf1c2a0bd5765a","addressRefs":["0x45d91340b3b7b96985a72b5c678f7d9e8d664b62","0x7566debc906c17338524a414343fa61bca26a843","0xece6b0e8a54c2f44e066fbb9234e7157b15b7fec"]},"c8fcae7c-01ea-48cf-9b8c-4de7d3c86d78":{"id":"c8fcae7c-01ea-48cf-9b8c-4de7d3c86d78","doc_no":"A.6.1.1.1.3.5.3","title":"Policies and Operational Parameters","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5179,"content":"The documents herein define the currently active policies for Spark Savings Configuration, alongside relevant operational parameters for implementing the policies.","contentHash":"cd8985fd1815fddd822a6686fc64b901d0fb6f8da85886a5a08e545ba6c46b5d","addressRefs":[]},"6f328a96-1275-46f7-a034-b40dcb69f708":{"id":"6f328a96-1275-46f7-a034-b40dcb69f708","doc_no":"A.6.1.1.1.3.5.3.1","title":"Target Liquidity","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5180,"content":"The documents herein define Spark's policy for managing the liquidity buffers available for user withdrawals from Spark Savings vaults.","contentHash":"6b6ad1e2dd0bee3d59ad6d3d6d0e04fdf76371dfdfc49bff05b045d772b6be2b","addressRefs":[]},"0289444b-b7fe-4003-b737-4e07230a4d9b":{"id":"0289444b-b7fe-4003-b737-4e07230a4d9b","doc_no":"A.6.1.1.1.3.5.3.1.1","title":"Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5181,"content":"Target Liquidity is the amount of deposited assets that should remain within each Spark Savings vault contract to support instant withdrawals. This value may be defined as a percent of total vault deposits, a fixed quantity of tokens, or a combination of both types of evaluation.","contentHash":"9edde70db7acff13aecac7e4b10a5d86eb4babcf6d78f56c9cf22e2225e9240b","addressRefs":[]},"33a7389c-c8a3-46ab-96a4-17d6b9ee2b4f":{"id":"33a7389c-c8a3-46ab-96a4-17d6b9ee2b4f","doc_no":"A.6.1.1.1.3.5.3.1.2","title":"Operational Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5182,"content":"The Spark Prime Relayer Multisig will execute transactions to ensure liquidity within Spark Savings vaults is aligned with the Target Liquidity configurations specified in Target Liquidity Current Configuration, up to the total amount of user deposits in a given Spark Savings vault. This will be implemented via control of the taker role in the vault and transferAsset rate limit from Spark Liquidity Layer ALM Proxy to the vault.\n\nIn normal conditions, this will be automated via the ALM Planner software. If the Prime Relayer Multisig fails to maintain Spark Savings vault liquidity in alignment with the Target Liquidity configurations, the Core Operator Relayer Multisig is empowered to effectuate transactions to achieve this.","contentHash":"b4f35f94ad6c80709302198bb5b378eef0cba342b4c57652bdb49699a3dbd54e","addressRefs":[]},"cae48a72-fa6d-439e-88fd-1dc37f499101":{"id":"cae48a72-fa6d-439e-88fd-1dc37f499101","doc_no":"A.6.1.1.1.3.5.3.1.2.1","title":"Savings Liquidity Intents","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5183,"content":"Spark Savings will enable users to withdraw amounts exceeding the standard Target Liquidity buffer via Savings Liquidity Intents. Users may submit signed withdrawal intents indicating their intent to redeem Spark Savings vault tokens in amounts exceeding the standard Target Liquidity buffer. Subject to available liquidity within the Spark Liquidity Layer and underlying asset allocations, the Spark Liquidity Layer planner may automatically trigger transactions through the Spark Prime Relayer infrastructure to fulfill such intents. Fulfillment of withdrawal intents is not guaranteed. Withdrawal intents may be replaced or cancelled by submitting a superseding signed intent with the same nonce. Intents that have passed their deadline timestamp may not be executed.","contentHash":"d01c77930d9e0825c93e5c8fa115cf4f0199f84f41babdf8fc4da02758f220de","addressRefs":[]},"98bf1329-ccd7-4a7e-bfaf-d30b5c29574c":{"id":"98bf1329-ccd7-4a7e-bfaf-d30b5c29574c","doc_no":"A.6.1.1.1.3.5.3.1.3","title":"Target Liquidity Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5184,"content":"The subdocuments herein specify the current values for Target Liquidity for each instance of Spark Savings.","contentHash":"f20a04ce5e8779651800f55262a97869854a0b8f4e5b50f9ee1ef932a7dc29d4","addressRefs":[]},"3b92fb2c-9944-4fa8-9300-5a53c16189dd":{"id":"3b92fb2c-9944-4fa8-9300-5a53c16189dd","doc_no":"A.6.1.1.1.3.5.3.1.3.1","title":"Spark Savings USDC on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5185,"content":"The current Target Liquidity for Spark Savings USDC on Ethereum is the greater of 10% of total deposits or 1 million USDC, up to a maximum amount of 10 million USDC.","contentHash":"5dbd2aacbd9ee1883aeb98e811c3c3be15f2e8f33935d88315e008ea1c15d829","addressRefs":[]},"5e8fdea7-ce4a-4185-9d18-995ff823eb94":{"id":"5e8fdea7-ce4a-4185-9d18-995ff823eb94","doc_no":"A.6.1.1.1.3.5.3.1.3.2","title":"Spark Savings USDT on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5186,"content":"The current Target Liquidity for Spark Savings USDT on Ethereum is the greater of 10% of total deposits or 1 million USDC, up to a maximum amount of 10 million USDT.","contentHash":"ea9680a9f10918effff8e06e2551a0a2bc994aae3a114d8570a13b43f9013d4a","addressRefs":[]},"944ebd8c-0562-4397-8a5a-6ebcea8167e7":{"id":"944ebd8c-0562-4397-8a5a-6ebcea8167e7","doc_no":"A.6.1.1.1.3.5.3.1.3.3","title":"Spark Savings ETH on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5187,"content":"The current Target Liquidity for Spark Savings ETH on Ethereum is the greater of 10% of total deposits or 250 ETH, up to a maximum amount of 2,500 ETH.","contentHash":"782d870c4e2e70aa789216742331975f4d3df03592b8be728596f0e39c71bb97","addressRefs":[]},"3a7b2e58-01ac-4b0c-a53e-6cce6f563168":{"id":"3a7b2e58-01ac-4b0c-a53e-6cce6f563168","doc_no":"A.6.1.1.1.3.5.3.1.3.4","title":"Spark Savings USDC on Avalanche","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5188,"content":"The current Target Liquidity for Spark Savings USDC on Avalanche is the greater of 10% of total deposits or 1 million USDC, up to a maximum amount of 10 million USDC.","contentHash":"ced2811728542a4195c6b505d6e61565402a47a9810cdbe686df601364b08368","addressRefs":[]},"5af03853-e89b-418a-a457-e8ecf34fc06e":{"id":"5af03853-e89b-418a-a457-e8ecf34fc06e","doc_no":"A.6.1.1.1.3.5.3.1.3.5","title":"Spark Savings PYUSD on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5189,"content":"The current Target Liquidity for Spark Savings PYUSD on Ethereum is the greater of 10% of total deposits or 1 million PYUSD, up to a maximum amount of 10 million PYUSD.","contentHash":"228525f7cbc3bf342c143c024d60a90fa56d247415df1716bf4f29c2ced69f77","addressRefs":[]},"22d359a5-3f83-409f-8396-595ac1ea0060":{"id":"22d359a5-3f83-409f-8396-595ac1ea0060","doc_no":"A.6.1.1.1.3.5.3.2","title":"Rewards Rate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5190,"content":"The documents herein define Spark's policy for managing the rewards rate for Spark Savings vaults.","contentHash":"08df4027843dbd05f836fa70f26c6c79ae710ddeafef978f3cc751afe874aa9b","addressRefs":[]},"3a143911-80c9-4eb0-9aa3-5b3d3a8ca843":{"id":"3a143911-80c9-4eb0-9aa3-5b3d3a8ca843","doc_no":"A.6.1.1.1.3.5.3.2.1","title":"Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5191,"content":"The Spark Savings Rewards Rate specifies the yield paid out to depositors on their supplied capital, expressed as an annual percentage rate. The Rewards Rate configuration for each vault may be set as a fixed value, or via reference to external benchmarks such as the Sky Savings Rate, Secured Overnight Funding Rate, SparkLend market supply rates, or other relevant measures.","contentHash":"a0383795aacf5ab32d7b6f98dafac82c1fa88f806997b33329f6a0062a6ff7ec","addressRefs":[]},"6c7a4964-485f-4edf-a05f-61fa65c9871c":{"id":"6c7a4964-485f-4edf-a05f-61fa65c9871c","doc_no":"A.6.1.1.1.3.5.3.2.2","title":"Operational Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5192,"content":"The Rewards Rate for each Spark Savings vault will be maintained in alignment with the configuration specified in Rewards Rate Current Configuration via the setter role for each vault. When the currently implemented Rewards Rate diverges from the target value, the setter is responsible for promptly updating the rate onchain.","contentHash":"a07fafc0cb4c274180e6cae0f0163d4a8fd97b4755c96e4c540caaf5a0c91ccb","addressRefs":[]},"89192471-7e48-43d8-b86e-fa4e70edcf8a":{"id":"89192471-7e48-43d8-b86e-fa4e70edcf8a","doc_no":"A.6.1.1.1.3.5.3.2.3","title":"Rewards Rate Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5193,"content":"The subdocuments herein specify the current configuration for determining Rewards Rate for each instance of Spark Savings.","contentHash":"408316c1f9faefbaf3e57b242a970302e9347d9942a4e378c954eaa3acb69174","addressRefs":[]},"8cba4337-8305-4b75-9fa2-79cee08a9739":{"id":"8cba4337-8305-4b75-9fa2-79cee08a9739","doc_no":"A.6.1.1.1.3.5.3.2.3.1","title":"Spark Savings USDC on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5194,"content":"The Rewards Rate for Spark Savings USDC on Ethereum will be maintained to be equal to the Sky Savings Rate.","contentHash":"652fb40e99e0ca1d73a6e5c814cbe9189b9be1668559b0a0961778799ca517b4","addressRefs":[]},"087dc001-1a44-4096-acd1-feeb109f7ec0":{"id":"087dc001-1a44-4096-acd1-feeb109f7ec0","doc_no":"A.6.1.1.1.3.5.3.2.3.2","title":"Spark Savings USDT on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5195,"content":"The Rewards Rate for Spark Savings USDT on Ethereum will be maintained to be equal to Aave Ethereum Core USDT supply rate plus the Spark Savings USDT Spread.\n\nThe Spark Savings USDT Spread will be defined as part of the ALM Planner configuration process, and will be set within a range of -0.5% to 2%.","contentHash":"90280e0f305dde5e27deab295a2c84e692aa3b4f4db99438ccf70e6a6dc485f2","addressRefs":[]},"a2a900aa-a3d6-42d6-b491-cd1fb9701fce":{"id":"a2a900aa-a3d6-42d6-b491-cd1fb9701fce","doc_no":"A.6.1.1.1.3.5.3.2.3.3","title":"Spark Savings ETH on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5196,"content":"The Rewards Rate for Spark Savings ETH on Ethereum will be maintained to be equal to the supply-weighted average yield of ETH-denominated assets held in the Spark Liquidity Layer, multiplied by one minus the percentage of spETH backing held in the spETH vault contract for instant redemptions, plus the Spark Savings ETH Spread.\n\nThe Spark Savings ETH Spread will be defined as part of the ALM Planner configuration process, and will be set within a range of -0.5% to 2%.","contentHash":"fe82f4ced1640e1fc7add2d8eefd353e19ef2f328992b611cbe77845691eefc9","addressRefs":[]},"afac32a3-7f73-4b24-8857-061eb5c6c264":{"id":"afac32a3-7f73-4b24-8857-061eb5c6c264","doc_no":"A.6.1.1.1.3.5.3.2.3.4","title":"Spark Savings USDC on Avalanche","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5197,"content":"The Rewards Rate for Spark Savings USDC on Avalanche will be maintained to be equal to the Sky Savings Rate.","contentHash":"0d590818025378f9dec4ab1598f6fc5b552f4f52c20e9d12688e350c9a5df89d","addressRefs":[]},"c54b370a-df10-4621-82a2-7fc4e5caf728":{"id":"c54b370a-df10-4621-82a2-7fc4e5caf728","doc_no":"A.6.1.1.1.3.5.3.2.3.5","title":"Spark Savings PYUSD on Ethereum","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5198,"content":"The Rewards Rate for Spark Savings PYUSD on Ethereum will be maintained to be equal to the Sky Savings Rate.","contentHash":"51f63125100b95c859be51a2fe47ec59c902d88ec639b6a86a54a26b6be9fd58","addressRefs":[]},"a05cc5db-64e5-4279-84ed-e93d4aa67c38":{"id":"a05cc5db-64e5-4279-84ed-e93d4aa67c38","doc_no":"A.6.1.1.1.3.6","title":"Strategic Investments","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5199,"content":"The documents herein specify Spark's operational processes for undertaking and managing strategic investments, alongside details of existing strategic investments.","contentHash":"5e963ba3f56f58f475ea69d1190a037e30244aed93c7665126a74229f35fcfea","addressRefs":[]},"b706d2e5-6f78-4c02-b3da-1ecc9d0a2397":{"id":"b706d2e5-6f78-4c02-b3da-1ecc9d0a2397","doc_no":"A.6.1.1.1.3.6.1","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5200,"content":"The documents herein define the process for updating Strategic Investment policies and procedures, and for actions related to proposed or current strategic investments.","contentHash":"d376985982bfb1e0029e70f07fcad5845b943f933a667314a8d4c4ae78540a29","addressRefs":[]},"4216b5c8-9038-4620-a4a9-17062e59863e":{"id":"4216b5c8-9038-4620-a4a9-17062e59863e","doc_no":"A.6.1.1.1.3.6.1.1","title":"Strategic Investment Policy Updates","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5201,"content":"Changes to Strategic Investment policies and procedures are implemented using the Root Edit Primitive.","contentHash":"445b61ba6b2ec8a0092846318aa9650253b8e874e67253f7700e7937f67c3c9d","addressRefs":[]},"66baa7af-73c7-493e-8fbb-66da8a2e8caf":{"id":"66baa7af-73c7-493e-8fbb-66da8a2e8caf","doc_no":"A.6.1.1.1.3.6.1.2","title":"Strategic Investment Approvals and Significant Decisions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5202,"content":"Approval of new Strategic Investments, as well as significant changes to existing strategic investments including assignment of rights, sales or disposal of interests, are subject to Spark governance approval and implemented via the Root Edit Primitive.","contentHash":"c9057395fd82908b532b0415d782b00537e8850e621c886a4a6c367e4d99ff01","addressRefs":[]},"daf295c4-78eb-463c-a7db-3a012deec873":{"id":"daf295c4-78eb-463c-a7db-3a012deec873","doc_no":"A.6.1.1.1.3.6.1.3","title":"Delegation of Authority","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5203,"content":"Certain rights and responsibilities related to strategic investments, including shareholder voting rights, conversion rights, and informational rights, may be held and exercised by Spark Foundation and/or Spark Asset Foundation. Additionally, legal ownership of and title to equity, tokens, or other interests in Spark's Strategic Investments may be held by Spark Foundation or Spark Asset Foundation. Details of delegated authority and rights management, where applicable, should be specified for each individual strategic investment.","contentHash":"4d744d36d05e989d85e5b29c9a487660376dc3bef66e231b0edbdb8a37e7bcdd","addressRefs":[]},"0eb2eb16-7306-4410-a596-8c2ff371598a":{"id":"0eb2eb16-7306-4410-a596-8c2ff371598a","doc_no":"A.6.1.1.1.3.6.2","title":"Current Strategic Investments","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5204,"content":"The documents herein provide details on each Strategic Investment undertaken by Spark.","contentHash":"d1a882d22e4e1a9e9ea2527bfb0ec1eba000e25c6a854a73e70565e78e416469","addressRefs":[]},"a4e71b17-18ca-4911-b9a6-3be65f919591":{"id":"a4e71b17-18ca-4911-b9a6-3be65f919591","doc_no":"A.6.1.1.1.3.6.2.1","title":"Arkis","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5205,"content":"Arkis is a protocol and technology infrastructure layer facilitating prime brokerage services across both defi protocols and assets, as well as centralized exchanges and custodial services.","contentHash":"a7437d9785fcdcb6926b8d35d84bf2978fbb19d4190ac098b0232fc415ab3f34","addressRefs":[]},"88040e43-50b4-4594-8b22-b2512259e8df":{"id":"88040e43-50b4-4594-8b22-b2512259e8df","doc_no":"A.6.1.1.1.3.6.2.1.1","title":"Investment Terms","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5206,"content":"Spark's strategic investment will be undertaken with the following terms:\n\n- Investing entity: Spark Foundation\n- Investment amount: $4 million paid in USDS\n- Recipient: PRM LBS LTD, at address 0xD5FF8bdeF23fc3C8Ff6815C6B4051F9809C877a5\n- Arkis post-money valuation: $45 million\n- Deal structure:\n    - Simple Agreement for Future Equity (SAFE) substantially mirroring the Ycombinator SAFE format\n    - Token warrant providing for token ownership share equal to at least 50% of Spark's share of equity ownership at the time of token launch\n    - Side letter providing for most favored nation rights, pro rata rights, information rights, major investor rights, and right to elect one director\n- Fee reduction: Spark will benefit from reduced fees for use of Arkis protocol for 5 years with Spark Foundation holding the option to extend by 2 additional years, assessed as a 50% reduction vs the lowest rate of fees paid by any other user","contentHash":"ee96b7d04a430ad28456443cf2d85285148596e16dba88262d8214329e83bf24","addressRefs":["0xd5ff8bdef23fc3c8ff6815c6b4051f9809c877a5"]},"483d37f0-0143-44cc-b470-63bbe7913f6d":{"id":"483d37f0-0143-44cc-b470-63bbe7913f6d","doc_no":"A.6.1.1.1.3.6.2.1.2","title":"Delegation of Authority","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5207,"content":"Spark Foundation, as legal owner of the interest in PRM LBS LTD, is empowered to exercise all rights and responsibilities related to the investment for the benefit of the Spark ecosystem, and according to generally accepted business practices as well as the Spark Foundation's own professional judgement.","contentHash":"dc80d5305654d507eb45f149b795b7e0a6cbaf2a7921f3c3d99071bc000c3b13","addressRefs":[]},"9a2d76b9-95c7-4e11-b3b8-ed74f2188e4f":{"id":"9a2d76b9-95c7-4e11-b3b8-ed74f2188e4f","doc_no":"A.6.1.1.1.3.7","title":"Spark Prime Brokerage","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5208,"content":"The documents herein specify Spark’s strategy and operational processes for allocating capital via Spark Prime Brokerage, powered by the Arkis protocol prime brokerage infrastructure.","contentHash":"29d7a193838c56f229ecc8bd5b4d7042239b81f13618c7881c8a3017d74363f5","addressRefs":[]},"cb7c2b0f-15e7-48b3-80fc-f2dc46341468":{"id":"cb7c2b0f-15e7-48b3-80fc-f2dc46341468","doc_no":"A.6.1.1.1.3.7.1","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5209,"content":"The documents herein define the process for updating Spark Prime Brokerage policies and procedures.","contentHash":"1307301e403ae9b18979f047f1668bc5ea523796ee0bf969edc7fceeafae5338","addressRefs":[]},"a9061ad0-9dbd-4188-94eb-3f1f6783f271":{"id":"a9061ad0-9dbd-4188-94eb-3f1f6783f271","doc_no":"A.6.1.1.1.3.7.1.1","title":"Spark Prime Brokerage Policy Changes","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5210,"content":"Changes to Spark Prime Brokerage policies are implemented using the Root Edit Primitive.","contentHash":"0b27d23d4bacbfd18c6a45fb19a070523db0ab7869b3315a7c5967778bcba1ed","addressRefs":[]},"3d254422-962c-405c-9c5c-dc72ff37bfec":{"id":"3d254422-962c-405c-9c5c-dc72ff37bfec","doc_no":"A.6.1.1.1.3.7.1.2","title":"Spark Prime Brokerage Policy Change Execution","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5211,"content":"Approved changes to Spark Prime Brokerage policies are executed by either Spark Governance (for onchain updates under Spark governance admin control), or via the Arkis team (for offchain components including the Arkis Margin engine or CEX subaccount management). Policy changes must be executed promptly after Root Edit Primitive approval. If policy changes are not executed as required, Spark must remove all funding allocated through the Arkis protocol infrastructure as soon as reasonably practicable.","contentHash":"c3415911df9229404b82aad2afa619f487f2ceb6d7ffb2a761ec0fbca7bac9ef","addressRefs":[]},"d126ed27-57ef-4bf0-ae49-aabbaec47ad4":{"id":"d126ed27-57ef-4bf0-ae49-aabbaec47ad4","doc_no":"A.6.1.1.1.3.7.2","title":"Policies and Mandate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5212,"content":"The documents herein define the currently active policies and mandate for allocation via Spark Prime Brokerage.","contentHash":"a3dcac89cd3dc052a8626a391152b3f56bd56041f0ffded0e222b9f6ff329242","addressRefs":[]},"15349ede-15d1-4cee-80d9-fd0b5e5f9f3a":{"id":"15349ede-15d1-4cee-80d9-fd0b5e5f9f3a","doc_no":"A.6.1.1.1.3.7.2.1","title":"Counterparty Requirements","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5213,"content":"Borrowers funded via Spark Prime Brokerage must be duly registered by competent authorities in their primary jurisdiction, and must not be subject to sanctions by the US, UK, EU, or UN. Responsibility for verifying KYC/KYB and meeting related compliance requirements is handled by Arkis during the borrower onboarding process.\n\nBorrowers must not be insolvent at the time of loan origination or renewal. Borrowers will self-certify their solvency as part of loan agreements. If a borrower becomes insolvent or enters administration while having an active loan, the entire loan amount becomes due and payable and Arkis may immediately liquidate collateral to recover the loan balance.","contentHash":"8226a9ac154aa1fe2a5354b9e9e6c63e406e0548e19944261624e15ee3b016ee","addressRefs":[]},"ef6decfd-b7ce-49a0-85aa-0885921c21f3":{"id":"ef6decfd-b7ce-49a0-85aa-0885921c21f3","doc_no":"A.6.1.1.1.3.7.2.2","title":"Marginable Assets","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5214,"content":"The documents herein define the assets or positions that are accepted as margin collateral within instances of the Arkis protocol funded by Spark.","contentHash":"87f979bfb4afdf97dd1e566f00fdd4d9592d3ed76578a8e4e8ea3a2642306096","addressRefs":[]},"a8a8220e-0380-411a-af53-8ba421bcdba4":{"id":"a8a8220e-0380-411a-af53-8ba421bcdba4","doc_no":"A.6.1.1.1.3.7.2.2.1","title":"Marginable Assets Parameters Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5215,"content":"The subdocuments herein define the specific risk parameters or limits applicable to each accepted margin collateral asset.","contentHash":"78c541501c5f3dd2560ee40d300541589b7e0e628230e56e0d152fbf6e8039aa","addressRefs":[]},"131e55ba-86f0-4249-93d1-6d7d40906ab0":{"id":"131e55ba-86f0-4249-93d1-6d7d40906ab0","doc_no":"A.6.1.1.1.3.7.2.2.1.1","title":"Collateral Haircut","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5216,"content":"The minimum discount applied to net exposure to an asset while calculating position health and stress tested portfolio value, expressed as a negative percentage for accounts net long an asset, or a positive percentage for accounts net short an asset. Spark and Arkis have discretion to implement more conservative collateral haircuts than those listed in the artifact on a case by case basis.","contentHash":"d1be6dc5b44c53f814cc8b929ed24e29061bf367de1e573de0104eda63c7d687","addressRefs":[]},"62b3310b-678a-4159-8a79-6d6433d0e8ab":{"id":"62b3310b-678a-4159-8a79-6d6433d0e8ab","doc_no":"A.6.1.1.1.3.7.2.2.1.2","title":"Exposure Limit","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5217,"content":"The maximum aggregate gross exposure to a given asset permitted within Spark funded instances of the Arkis protocol. When calculating gross exposure, we use the higher of the sum of long exposure across all positions or short exposure across all positions, without offsetting long and short exposure within each position.","contentHash":"8d76cc459168a9958458ae4714b70797460c8a98bb043dc90f530588fdd61afc","addressRefs":[]},"d24ea4df-6922-48f1-8b14-f62710c89575":{"id":"d24ea4df-6922-48f1-8b14-f62710c89575","doc_no":"A.6.1.1.1.3.7.2.2.1.3","title":"Staked and Wrapped Versions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5218,"content":"The acceptable staked or wrapped versions of a given marginable asset, including non native bridged versions of an asset.","contentHash":"913c4ce33f01e08065d7f23afb9290db4b73e9bc36f346bce4fca5fa051797d7","addressRefs":[]},"0dfe744f-7918-403b-85e3-520341769e71":{"id":"0dfe744f-7918-403b-85e3-520341769e71","doc_no":"A.6.1.1.1.3.7.2.2.2","title":"Marginable Assets Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5219,"content":"The subdocuments herein define the assets currently accepted as margin collateral within Spark funded instances of the Arkis protocol.","contentHash":"b73e3690e8f80504949f6bb6058665f8816c7e0b04ec55811f98dcace6e93ec0","addressRefs":[]},"60525756-fcea-4439-af53-e9c6eb1ef898":{"id":"60525756-fcea-4439-af53-e9c6eb1ef898","doc_no":"A.6.1.1.1.3.7.2.2.2.1","title":"Bitcoin (BTC)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5220,"content":"- Collateral Haircut: +20% / -20%\n- Exposure Limit: None (native BTC, cbBTC), $100 million (LBTC)\n- Staked and Wrapped Versions: Lombard LBTC, Coinbase cbBTC","contentHash":"b7dfa99b4631d0db197c5642b2b5de8a3df64b3bd47d506c5a166ac7a1303ccf","addressRefs":[]},"c015634f-20ec-4a86-a056-b0d9b8e46601":{"id":"c015634f-20ec-4a86-a056-b0d9b8e46601","doc_no":"A.6.1.1.1.3.7.2.2.2.2","title":"Ether (ETH)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5221,"content":"- Collateral Haircut: +20% / -20%\n- Exposure Limit: None (ETH/WETH, stETH), $250 million (weETH, native staking)\n- Staked and Wrapped Versions: WETH, Lido stETH/wstETH, Etherfi weETH, native staking with approved provider","contentHash":"571b32786bc83eb958c23d3fd71821006a09387712c7e2ac90192255b52e4ba9","addressRefs":[]},"4d25dda5-14c0-46cb-8a93-447445d3a154":{"id":"4d25dda5-14c0-46cb-8a93-447445d3a154","doc_no":"A.6.1.1.1.3.7.2.2.2.3","title":"Ripple (XRP)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5222,"content":"- Collateral Haircut: +20% / -20%\n- Exposure Limit: $50 million\n- Staked and Wrapped Versions: None","contentHash":"02c6ec779acd65bb0f1fbcdabf2d413aef30e9dfe8ae57a169da4bd7e4429b82","addressRefs":[]},"4e3841e8-b90e-476d-b0ab-da3786b15978":{"id":"4e3841e8-b90e-476d-b0ab-da3786b15978","doc_no":"A.6.1.1.1.3.7.2.2.2.4","title":"Solana (SOL)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5223,"content":"- Collateral Haircut: +20% / -20%\n- Exposure Limit: $100 million\n- Staked and Wrapped Versions: JitoSOL, Binance BNSOL, Bybit BBSOL, OKX OKSOL, native staking with approved provider","contentHash":"199106ce44eccc64b4d4573237172165627541b4a99cdf07d7b28fcd04d30c20","addressRefs":[]},"53bb9ea7-b86d-419d-836c-4b4edd21b297":{"id":"53bb9ea7-b86d-419d-836c-4b4edd21b297","doc_no":"A.6.1.1.1.3.7.2.2.2.5","title":"Dogecoin (DOGE)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5224,"content":"- Collateral Haircut: +25% / -25%\n- Exposure Limit: $25 million\n- Staked and Wrapped Versions: None","contentHash":"da618f231504bcf6463a40b5904fa07c6952ae5c31d0d946c4b79f77c2f48ec3","addressRefs":[]},"66b2fe30-3bf2-4488-a8e2-b26f39a2fad9":{"id":"66b2fe30-3bf2-4488-a8e2-b26f39a2fad9","doc_no":"A.6.1.1.1.3.7.2.2.2.6","title":"Cardano (ADA)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5225,"content":"- Collateral Haircut: +25% / -25%\n- Exposure Limit: $25 million\n- Staked and Wrapped Versions: None","contentHash":"da618f231504bcf6463a40b5904fa07c6952ae5c31d0d946c4b79f77c2f48ec3","addressRefs":[]},"6828399d-ea70-4044-a26d-b5c726e573b7":{"id":"6828399d-ea70-4044-a26d-b5c726e573b7","doc_no":"A.6.1.1.1.3.7.2.2.2.7","title":"Hyperliquid (HYPE)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5226,"content":"- Collateral Haircut: +25% / -25%\n- Exposure Limit: $50 million\n- Staked and Wrapped Versions: kHYPE, stHYPE, native staking with approved provider","contentHash":"99ce5792ecc649b693dc6482c1be0e37fad7c0848deaec62075dad62dafb2734","addressRefs":[]},"3847ad1c-a5cb-446d-af95-ad918b2798bf":{"id":"3847ad1c-a5cb-446d-af95-ad918b2798bf","doc_no":"A.6.1.1.1.3.7.2.2.2.8","title":"Zcash (ZEC)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5227,"content":"- Collateral Haircut: +30% / -30%\n- Exposure Limit: $20 million\n- Staked and Wrapped Versions: None","contentHash":"bfd86fab069a8acc0d4bcb463ad294cc95cdf747d0ea09d3f2bae90d7d174204","addressRefs":[]},"32d1cdc6-9d76-45b0-83a4-8ee228628987":{"id":"32d1cdc6-9d76-45b0-83a4-8ee228628987","doc_no":"A.6.1.1.1.3.7.2.2.2.9","title":"Avalanche (AVAX)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5228,"content":"- Collateral Haircut: +30% / -30%\n- Exposure Limit: $20 million\n- Staked and Wrapped Versions: Benqi sAVAX, native staking with approved provider","contentHash":"4f1218f39a1ff96cf3f54713c14f1c914330d1dff83a46122cd5d91e413fbd0a","addressRefs":[]},"b27f52fc-dee9-448e-bdf7-62453b559bd3":{"id":"b27f52fc-dee9-448e-bdf7-62453b559bd3","doc_no":"A.6.1.1.1.3.7.2.2.2.10","title":"Sui (SUI)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5229,"content":"- Collateral Haircut: +30% / -30%\n- Exposure Limit: $20 million\n- Staked and Wrapped Versions: native staking with approved provider","contentHash":"fdf7d5247c4489ed32be150853a4337e4fbd3aaae9d719400b3b8d9b0661ab41","addressRefs":[]},"a33a0224-1005-4875-b202-0935f48f9c82":{"id":"a33a0224-1005-4875-b202-0935f48f9c82","doc_no":"A.6.1.1.1.3.7.2.2.2.11","title":"Near (NEAR)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5230,"content":"- Collateral Haircut: +30% / -30%\n- Exposure Limit: $20 million\n- Staked and Wrapped Versions: native staking with approved provider","contentHash":"fdf7d5247c4489ed32be150853a4337e4fbd3aaae9d719400b3b8d9b0661ab41","addressRefs":[]},"862b3d39-6298-40ae-b1d7-909e24e87e07":{"id":"862b3d39-6298-40ae-b1d7-909e24e87e07","doc_no":"A.6.1.1.1.3.7.2.2.2.12","title":"Ethena (USDe)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5231,"content":"- Collateral Haircut: -10%\n- Exposure Limit: $500 million\n- Staked and Wrapped Versions: sUSDe","contentHash":"b7b2917ee7c8cc47b631873305afa1318885ccfb3c384cd12ddf0140e89e5088","addressRefs":[]},"224b6c35-7ec4-4dfb-8ec1-8efe4d88b942":{"id":"224b6c35-7ec4-4dfb-8ec1-8efe4d88b942","doc_no":"A.6.1.1.1.3.7.2.2.2.13","title":"Tether (USDT)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5232,"content":"- Collateral Haircut: 0%\n- Exposure Limit: None\n- Staked and Wrapped Versions: Spark Savings USDT (spUSDT)","contentHash":"d4f3c6533dd2edc41d8c335a44000f72672f8602f9af5e30d4d69bf8b38c09ec","addressRefs":[]},"839c1db9-48d7-45cf-b049-13e3edd0290d":{"id":"839c1db9-48d7-45cf-b049-13e3edd0290d","doc_no":"A.6.1.1.1.3.7.2.2.2.14","title":"Circle (USDC)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5233,"content":"- Collateral Haircut: 0%\n- Exposure Limit: None\n- Staked and Wrapped Versions: Spark Savings USDC v2 (spUSDC) and v1 (sUSDC)","contentHash":"b6b948961129bbc85ba46f75f676c40d697859d188192462e3e8dbb6eabb7cc2","addressRefs":[]},"d65ab4f5-a2cf-4817-95e7-f19c8b1a972f":{"id":"d65ab4f5-a2cf-4817-95e7-f19c8b1a972f","doc_no":"A.6.1.1.1.3.7.2.2.3","title":"Pendle PTs","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5234,"content":"Pendle PTs expiring within 120 days linked to approved assets may be accepted as margin collateral. Exposure to Pendle PTs shall not exceed 10 times the total liquidity within the Pendle AMM for the given PT.","contentHash":"993c76e7af142cc8f3d26b46cafa0a747ae96f6fc987a1f467c83cdcb076810a","addressRefs":[]},"904fd5ef-ac80-4171-8c29-27cc812a70bd":{"id":"904fd5ef-ac80-4171-8c29-27cc812a70bd","doc_no":"A.6.1.1.1.3.7.2.2.4","title":"Perpetual and Calendar Futures","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5235,"content":"Perpetual futures and calendar futures expiring within 120 days that reference an approved asset as underlying may be included in margin calculations.","contentHash":"73e53e16a0f332de6ea5cba42d976944579e5508ed38fc73f07917b0150c3d9d","addressRefs":[]},"5163ebb9-a425-4df6-aba9-b483e8a482c1":{"id":"5163ebb9-a425-4df6-aba9-b483e8a482c1","doc_no":"A.6.1.1.1.3.7.2.2.5","title":"Unapproved Assets and Products","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5236,"content":"Exposure to unapproved assets and/or futures products is not permitted, and incurs a collateral haircut rating of +100% / -100%. Long and short exposure to unapproved products will not be counted as offsetting each other. Frequent or significant exposure to unapproved assets or products may result in recall of the loan amount or liquidation of outstanding positions.","contentHash":"65b570a991f400f9ecb7298942cdd589d992672f82cbee43d5b06f16022509a5","addressRefs":[]},"c0a9aae3-661b-4124-9da7-1a85e01e4358":{"id":"c0a9aae3-661b-4124-9da7-1a85e01e4358","doc_no":"A.6.1.1.1.3.7.2.3","title":"Approved Venues","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5237,"content":"The documents herein define the venues where Spark Prime Brokerage users are permitted to trade and hold positions.","contentHash":"03e451c24ce79b29b641b130f323a912b636f2c055d3bf416ea0af03162d018c","addressRefs":[]},"06fcb0dd-3f54-420c-b518-34790d7a20ab":{"id":"06fcb0dd-3f54-420c-b518-34790d7a20ab","doc_no":"A.6.1.1.1.3.7.2.3.1","title":"Approved Venues Parameters Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5238,"content":"The subdocuments herein define the specific risk parameters or limits applicable to each approved venue.","contentHash":"e1412aa1dbc6ca505d84ac8806512a9e90379d7daf46493277b1228fd163dbee","addressRefs":[]},"5fbe9a91-0142-4d47-b89c-b46c911b313e":{"id":"5fbe9a91-0142-4d47-b89c-b46c911b313e","doc_no":"A.6.1.1.1.3.7.2.3.1.1","title":"Exposure Limit","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5239,"content":"The exposure limit is the maximum amount of account value, defined in USD based on current value of assets and positions, inclusive of spot assets, collateral for derivatives positions, and both settled and unrealized PNL within derivatives positions.","contentHash":"eca66397a04f41cb5cefcbc69aa88dcd972004b0d7f175322498faa179a1ebc3","addressRefs":[]},"0b290136-8726-49b5-92d4-fa3ac320af19":{"id":"0b290136-8726-49b5-92d4-fa3ac320af19","doc_no":"A.6.1.1.1.3.7.2.3.2","title":"Approved Venues Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5240,"content":"The subdocuments herein define the currently approved venues where positions and assets may be held in Spark funded instances of the Arkis Protocol.","contentHash":"7a13b5c87e1512ad9d188c39d20889cf1217101489d15bd2aa94dc2bc0b99066","addressRefs":[]},"5f029ce0-cb6e-4364-9cce-8dc7ad8fffbd":{"id":"5f029ce0-cb6e-4364-9cce-8dc7ad8fffbd","doc_no":"A.6.1.1.1.3.7.2.3.2.1","title":"Onchain","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5241,"content":"Users are permitted to hold assets and positions within their onchain Arkis margin account.\n\n- Exposure Limit: None","contentHash":"407bccc89a6148264e182bb367f5b7576897d9571b72566795c0283eabfcf46c","addressRefs":[]},"e9f0543a-ce6e-46b3-bdb7-c0fd60239c29":{"id":"e9f0543a-ce6e-46b3-bdb7-c0fd60239c29","doc_no":"A.6.1.1.1.3.7.2.3.2.2","title":"Binance","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5242,"content":"Users are permitted to hold assets and positions within Binance, in a subaccount controlled under the Arkis master account.\n\n- Exposure Limit: $100 million","contentHash":"f24f74b014a2c9808d65d6a418f38bbbf94a41ad347a9b6514425a67bd4b4006","addressRefs":[]},"35f40a50-fca5-4140-ab93-81e58c181b95":{"id":"35f40a50-fca5-4140-ab93-81e58c181b95","doc_no":"A.6.1.1.1.3.7.2.3.2.3","title":"OKX","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5243,"content":"Users are permitted to hold assets and positions within OKX, in a subaccount controlled under the Arkis master account.\n\n- Exposure Limit: $100 million","contentHash":"742b973f81f75ae5a56b6c7b5fddd383c5cf63a55d5156071984eec010959b98","addressRefs":[]},"ccb02230-7ade-4935-800d-8e038d104bcd":{"id":"ccb02230-7ade-4935-800d-8e038d104bcd","doc_no":"A.6.1.1.1.3.7.2.3.2.4","title":"Bybit","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5244,"content":"Users are permitted to hold assets and positions within Bybit, in a subaccount controlled under the Arkis master account.\n\n- Exposure Limit: $100 million","contentHash":"c4b6966893fb148ff447fe3f33a85926cc0974b6177fa95de884b254a6f629ba","addressRefs":[]},"790805e0-4798-4388-afd3-cfc977fa4fee":{"id":"790805e0-4798-4388-afd3-cfc977fa4fee","doc_no":"A.6.1.1.1.3.7.2.3.2.5","title":"Bitget","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5245,"content":"Users are permitted to hold assets and positions within Bitget, in a subaccount controlled under the Arkis master account.\n\n- Exposure Limit: $25 million","contentHash":"0ba3dd6289bcbcc22c48e97f91969986b365c2cc06b8379f53c9c0a6c68e88de","addressRefs":[]},"ce034c3a-89af-444b-bfad-bcf2e64e8b19":{"id":"ce034c3a-89af-444b-bfad-bcf2e64e8b19","doc_no":"A.6.1.1.1.3.7.2.3.2.6","title":"Hyperliquid (Hypercore)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5246,"content":"Users are permitted to hold assets and positions Hyperliquid perpetuals exchange (Hypercore), in a subaccount controlled under the Arkis master account.\n\n- Exposure Limit: $50 million","contentHash":"06441694562482c01bbab6002ff3527a157642c515680870ada0a369d38c30c6","addressRefs":[]},"f4bd5948-0d52-4fc9-9fa5-530b7768484c":{"id":"f4bd5948-0d52-4fc9-9fa5-530b7768484c","doc_no":"A.6.1.1.1.3.7.2.3.2.7","title":"Anchorage","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5247,"content":"Users are permitted to hold assets and positions within Anchorage, in a subaccount controlled under the Arkis master account, or via collateral management account where Arkis holds a secured interest.\n\n- Exposure Limit: $100 million","contentHash":"23b7516268cfb2e500b90c1aeb15a26a4414c963510bf2371db1b7e278528569","addressRefs":[]},"982d2ada-1f8f-422e-94d2-1027e9b0903c":{"id":"982d2ada-1f8f-422e-94d2-1027e9b0903c","doc_no":"A.6.1.1.1.3.7.2.3.2.8","title":"Bitgo","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5248,"content":"Users are permitted to hold assets and positions within Bitgo, in a subaccount controlled under the Arkis master account, or via collateral management account where Arkis holds a secured interest.\n\n- Exposure Limit: $100 million","contentHash":"b2365bfd2531c3d9c95c3b2e0dac51041428afa9d5ec7b9ccff6bad3464c2126","addressRefs":[]},"b3fed3ac-7b42-4dfd-b35e-c229598781f7":{"id":"b3fed3ac-7b42-4dfd-b35e-c229598781f7","doc_no":"A.6.1.1.1.3.7.2.4","title":"Loan Terms","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5249,"content":"The documents herein specify the policies and parameters for setting loan agreement terms.","contentHash":"b3474acb33415d73f88ddb7e399f900d417d7a4813ae970084be8e040146f62f","addressRefs":[]},"c62a0868-5713-4fec-b6b5-aea342bf149c":{"id":"c62a0868-5713-4fec-b6b5-aea342bf149c","doc_no":"A.6.1.1.1.3.7.2.4.1","title":"Loan Term Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5250,"content":"The subdocuments herein define parameters used to specify loan terms.","contentHash":"ade6cd8340f8ae16ae4a23b1e38b6c55f601bf28c173574e8a883977a2387de6","addressRefs":[]},"5e4d2a15-2ac1-4a59-b2e1-412c5b721c0c":{"id":"5e4d2a15-2ac1-4a59-b2e1-412c5b721c0c","doc_no":"A.6.1.1.1.3.7.2.4.1.1","title":"Duration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5251,"content":"The length of time that a loan is issued under specific terms. At the conclusion of the loan duration, the loan may either be payable in full, be rolled over upon mutual agreement with equivalent or different loan terms, or be set up as an “evergreen” loan where the loan is automatically extended at the current terms until recalled.","contentHash":"3f8d53f109f4224d40c74b1d7770fb3daa112ce6dd5ecf17d2d7332387da9152","addressRefs":[]},"ab65feec-36fd-4138-bf00-df715fb896e5":{"id":"ab65feec-36fd-4138-bf00-df715fb896e5","doc_no":"A.6.1.1.1.3.7.2.4.1.2","title":"Borrow Rate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5252,"content":"The minimum borrow rate that accrues on the outstanding loan balance, expressed as an annual percentage. Actual borrow rate charged may be structured in various ways including fixed rate, fixed spread vs a benchmark, performance fee or profit sharing based, or combination of the above. However, loans may not be issued with borrow cost structures below the values specified in this Loan Terms section.","contentHash":"fa84ada3992df1393f90e937d2db4608873a62b305a08a4d72d0da44e2af6bca","addressRefs":[]},"5f14d3d4-7def-4cbc-b6d8-3775c8262568":{"id":"5f14d3d4-7def-4cbc-b6d8-3775c8262568","doc_no":"A.6.1.1.1.3.7.2.4.2","title":"Loan Terms Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5253,"content":"The subdocuments herein specify the currently active parameters for loan terms that fall within Spark’s operational mandate.","contentHash":"fb68577da3e293051b0bbc9ea7ed99c9e7fcde536ef50ababda39648a3568a59","addressRefs":[]},"fa2dceca-3851-4844-8013-a399ddcba9b3":{"id":"fa2dceca-3851-4844-8013-a399ddcba9b3","doc_no":"A.6.1.1.1.3.7.2.4.2.1","title":"Duration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5254,"content":"Loans may be issued for the following durations:\n\n- Revolving / evergreen / demand\n- Fixed term up to 1 month","contentHash":"7a6e9694ac31bb2ca8fc3f3cc98d07c7104190ec1112bedba5c8f255f6686f6d","addressRefs":[]},"2bdfe55f-7788-480a-800c-09845c9dcd6b":{"id":"2bdfe55f-7788-480a-800c-09845c9dcd6b","doc_no":"A.6.1.1.1.3.7.2.4.2.2","title":"Borrow Rate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5255,"content":"The minimum borrow rate for loans via the Arkis infrastructure must be the greater of the following at the time of issuance or renewal:\n\n- Sky Savings Rate + 2%\n- SOFR + 2.5%","contentHash":"6aabac942f538a2ac2b0a9e03bec43311191b0d437904496e6646256a4dafe04","addressRefs":[]},"d234e0ca-af2f-4cab-8f84-6e5a39650b05":{"id":"d234e0ca-af2f-4cab-8f84-6e5a39650b05","doc_no":"A.6.1.1.1.3.7.2.5","title":"Recall and Acceleration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5256,"content":"The documents herein provide details of how and when loans should be recalled, accelerated, or liquidated in order to mitigate risk.","contentHash":"99baaecb233cd277c46f82e60bfa624e94d8a87dd980a1e3626d091b1df2ba94","addressRefs":[]},"8f7c70ad-b083-46fa-9550-3f2ae263c293":{"id":"8f7c70ad-b083-46fa-9550-3f2ae263c293","doc_no":"A.6.1.1.1.3.7.2.5.1","title":"Borrower Insolvency","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5257,"content":"If a borrower becomes insolvent or enters administration, any outstanding debts facilitated via the Arkis protocol become due and payable immediately. If the borrower does not repay the debt promptly, collateral may be liquidated to protect the interests of the lender.","contentHash":"b27c7412967b4b42c2778222bfc1220bbc9d531fa24d4c489025dfcb5b6010d9","addressRefs":[]},"a51aef25-bf7e-4467-9678-0b1ea59fb47e":{"id":"a51aef25-bf7e-4467-9678-0b1ea59fb47e","doc_no":"A.6.1.1.1.3.7.2.5.2","title":"Unapproved Products","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5258,"content":"If a borrower trades unapproved assets or products, this will be discounted or penalized via the margin calculation as noted in section [A.6.1.1.1.3.7.2.2.5 - Unapproved Assets and Products](5163ebb9-a425-4df6-aba9-b483e8a482c1). Repeated or serious instances of holding unapproved positions may result in the position being liquidated to protect the interests of the lender.","contentHash":"a4e05ceb42080f77e4a4ce4962c2ce34a87494428a1b00d2d6a089b56a52e4e1","addressRefs":[]},"a81f2f5d-796f-49e0-ac34-dbc5650ee2fe":{"id":"a81f2f5d-796f-49e0-ac34-dbc5650ee2fe","doc_no":"A.6.1.1.1.3.7.2.5.3","title":"Borrow Rate Shortfall","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5259,"content":"If the borrow rate charged on a loan falls below the borrow rate threshold specified in [A.6.1.1.1.3.7.2.4.2.2 - Borrow Rate](2bdfe55f-7788-480a-800c-09845c9dcd6b), either due to variation in the borrow rate itself (e.g., via profit sharing mechanisms) or because the benchmark rate(s) have increased, Spark must recall the debt or adjust the borrow rate at the earliest opportunity.","contentHash":"3eed2517eaa536f2c5facdbe9f95c97ad2ec7920c01b620283f9c1ee3764e150","addressRefs":[]},"50fa8061-8133-4765-a17c-4941634a6ff5":{"id":"50fa8061-8133-4765-a17c-4941634a6ff5","doc_no":"A.6.1.1.1.3.7.2.5.4","title":"Parameter Updates in Non Emergency Situations","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5260,"content":"Spark may update approved assets and products, risk parameters, and other details of the Spark Prime Brokerage product or allocation strategy into the Arkis protocol via governance. If a previously issued loan no longer conforms with Spark’s current operational mandate due to a non-emergency parameter update, Spark will recall the loan at the earliest possible opportunity, while respecting the agreed loan duration.","contentHash":"f952cbf59b9595e28ee108493720f4d01714b4f57446d3876ea337c0905f6d49","addressRefs":[]},"4d3f3e27-a0b6-430a-b9b4-ccf48bc49cbb":{"id":"4d3f3e27-a0b6-430a-b9b4-ccf48bc49cbb","doc_no":"A.6.1.1.1.3.7.2.5.5","title":"Emergency Parameter Updates","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5261,"content":"If market conditions or other factors create an immediate and severe risk of capital impairment, Spark and Arkis are empowered to implement immediate changes to risk parameters and configuration to mitigate risk. Actions taken may include preventing new loans or draws on existing loans, adjusting risk parameters of existing positions including increasing margin requirements or haircuts, demanding immediate repayment, up to and including liquidating high risk positions.","contentHash":"b09c6925c68cff83dda1b0d2c799fd57befb254118fdeff8724ebe37bf67bdc7","addressRefs":[]},"404a62a2-6918-44e3-9809-1fec0b7ca2a1":{"id":"404a62a2-6918-44e3-9809-1fec0b7ca2a1","doc_no":"A.6.1.1.1.3.7.2.6","title":"Delegation of Rights and Responsibilities","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5262,"content":"Spark Asset Foundation is the legal owner of funds allocated via the Spark Liquidity Layer and is the entity responsible for the Arkis onboarding and capital allocation relationship. Spark Asset Foundation will be empowered to exercise all rights and responsibilities with respect to the Spark Prime Brokerage capital allocation activities via the Arkis protocol, for the benefit of the Spark ecosystem and according to generally accepted business practices and Spark Asset Foundation’s professional judgement.","contentHash":"abafb846d920b92d584ac077c4ae2afc4f820fdfcac7aaf66faf34360707cd23","addressRefs":[]},"d55a80b7-f3e9-43b2-831c-0f41bbbb7b68":{"id":"d55a80b7-f3e9-43b2-831c-0f41bbbb7b68","doc_no":"A.6.1.1.1.3.7.2.7","title":"Account Management","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5263,"content":"The documents herein define the requirements for controlling and managing offchain accounts and permissions related to Spark Prime.","contentHash":"622bbdea9852c12480e0600c3dd4078ede71b9dcacaa370e525e8e20ee72c130","addressRefs":[]},"8b7e62e7-95f3-40a9-bc3e-22b6645e59cf":{"id":"8b7e62e7-95f3-40a9-bc3e-22b6645e59cf","doc_no":"A.6.1.1.1.3.7.2.7.1","title":"Critical Actions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5264,"content":"Critical actions are actions that could conceivably result in the loss of funds if they were executed maliciously or without authorization. The critical actions include:\n\n- Adding a withdrawal address to the whitelist\n- Adding or removing a signer from the account approvals policy\n- Changing the approval quorum\n- Transferring funds to an address under control of an external entity other than Spark Asset Foundation, Spark Foundation, or the Spark Liquidity Layer","contentHash":"ac42c1a71c179b5e1dac94e19e5e52cf9bbdacfd1284519f36847fc62f9102d2","addressRefs":[]},"2f4882cd-ddbf-4419-b69d-b5d6075d702c":{"id":"2f4882cd-ddbf-4419-b69d-b5d6075d702c","doc_no":"A.6.1.1.1.3.7.2.7.2","title":"Address Whitelist","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5265,"content":"Accounts shall only whitelist addresses for withdrawals to either an approved collateral agent (which will transfer received funds to borrowers as part of loan origination) or to the Spark Liquidity Layer.","contentHash":"878f7d5dff163a32c7d9b75e1c28b836a3b4818589ffe1e4d16c88f1b938fd1f","addressRefs":[]},"4c8b20c3-e723-4304-904f-7d7f8de5fc8b":{"id":"4c8b20c3-e723-4304-904f-7d7f8de5fc8b","doc_no":"A.6.1.1.1.3.7.2.7.3","title":"Quorum and Signers","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5266,"content":"Accounts must require a quorum of at least 3 signers for Critical Actions. It must not be possible for quorum to be met with signers from a single entity (no single entity will have enough signers to meet the quorum alone, and each critical action will therefore require approval from signers from at least 2 independent entities).\n\nSigners may be sourced from any of the following entities: Spark Asset Foundation (including legal council), Phoenix Labs, Spark Operational Facilitator.","contentHash":"8259f8e01b2f49fd279110165f0b9e3af523f360a6f1e2717286e7fdaa0acffe","addressRefs":[]},"cffebd02-baee-4b4c-809d-35d4b90246e6":{"id":"cffebd02-baee-4b4c-809d-35d4b90246e6","doc_no":"A.6.1.1.1.3.7.2.7.4","title":"Transfers","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5267,"content":"Funds may only be transferred to a collateral agent after confirmation that all necessary steps proceeding loan origination have been completed, including execution of final MLA and provision of configuration file for the loan to the custodian and/or collateral agent.\n\nFunds may be transferred to the designated address for Spark Liquidity Layer at any time without restriction.","contentHash":"f98936970f6ed35f1518973d7ae54c210a7e98b1419fe2439de7089c65fd9d27","addressRefs":[]},"7905b0d3-4269-4ba5-a3e2-fdb327b087f4":{"id":"7905b0d3-4269-4ba5-a3e2-fdb327b087f4","doc_no":"A.6.1.1.1.3.8","title":"Offchain Collateralized Lending","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5268,"content":"The documents herein specify Spark’s strategy and operational processes for allocating capital via offchain lending arrangements with collateral secured in qualified custodians.","contentHash":"ce1ec72009d776f98148c7da8c43df5f8173002b47645c01dce69bd384183f8a","addressRefs":[]},"8142b2db-e601-4222-a411-5a5caeb4009b":{"id":"8142b2db-e601-4222-a411-5a5caeb4009b","doc_no":"A.6.1.1.1.3.8.1","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5269,"content":"The documents herein define the process for updating Offchain Collateralized Lending policies and procedures.","contentHash":"43e092e8ed1eecffd0a278916f0f1f78c73dfa729a1686bffd1ad5c88972e108","addressRefs":[]},"c9ef7b0f-ed76-42d5-baa8-6afcd288fd58":{"id":"c9ef7b0f-ed76-42d5-baa8-6afcd288fd58","doc_no":"A.6.1.1.1.3.8.1.1","title":"Offchain Collateralized Lending Policy Changes","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5270,"content":"Changes to Offchain Collateralized Lending policies are implemented using the Root Edit Primitive.","contentHash":"04ab03ffce3bfbfc73b3e49678ce4d7d4d347a7bc9ed32c6e54232b8ab58ee49","addressRefs":[]},"c91355f0-4a54-4dd9-a13d-f40f8c515994":{"id":"c91355f0-4a54-4dd9-a13d-f40f8c515994","doc_no":"A.6.1.1.1.3.8.1.2","title":"Offchain Collateralized Lending Policy Change Execution","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5271,"content":"Approved changes to Offchain Collateralized Lending policies are executed by either Spark Governance (for onchain updates under Spark governance admin control), or via the Spark Asset Foundation account held at relevant custodian(s) and related admin panel(s) (for offchain components). Policy changes must be executed promptly after Root Edit Primitive approval. If policy changes are not executed as required, Spark must remove all funding allocated through the Offchain Collateralized Lending infrastructure as soon as reasonably practicable.","contentHash":"1d5c7e251f12d43e8c9509b6ccaf90f205ee54e12fb5cae4b59d9446a5065fc4","addressRefs":[]},"b3ebb481-d63f-45d7-9c9b-93a3a7be1f6d":{"id":"b3ebb481-d63f-45d7-9c9b-93a3a7be1f6d","doc_no":"A.6.1.1.1.3.8.2","title":"Policies and Mandate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5272,"content":"The documents herein define the currently active policies and mandate for allocation via Offchain Collateralized Lending arrangements.","contentHash":"065b8c731b01fed41edc6199c9f5da823f45e853ca5f9d55930ec76f3657eed4","addressRefs":[]},"5a57a6c6-f88d-439a-9e8b-f11068438bf6":{"id":"5a57a6c6-f88d-439a-9e8b-f11068438bf6","doc_no":"A.6.1.1.1.3.8.2.1","title":"Counterparty Requirements","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5273,"content":"Borrowers funded via Offchain Collateralized Lending must be duly registered by competent authorities in their primary jurisdiction, and must not be subject to sanctions by the US, UK, EU, or UN. Responsibility for verifying KYC/KYB and meeting related compliance requirements is handled by venues (custodians and/or collateral agents) during the borrower onboarding process.\n\nBorrowers must not be insolvent at the time of loan origination or renewal. Borrowers will self-certify their solvency as part of loan agreements. If a borrower becomes insolvent or enters administration while having an active loan, the entire loan amount becomes due and payable and the collateral agent or custodian may immediately liquidate collateral to recover the loan balance.","contentHash":"3e168ca520a4b75560f622bafc0a0b3e2a6077891899d7a494117157f63e5e10","addressRefs":[]},"137b6e3a-b6c7-4660-b135-8aff765a57a0":{"id":"137b6e3a-b6c7-4660-b135-8aff765a57a0","doc_no":"A.6.1.1.1.3.8.2.2","title":"Marginable Assets","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5274,"content":"The documents herein define the assets or positions that are accepted as margin collateral within Offchain Collateralized Lending arrangements funded by Spark.","contentHash":"916eed77b7116670c46d3019005a527eec7d18a09e3d1f2b52b55163c87350df","addressRefs":[]},"a8b82143-da87-47bb-8c68-5ce367ed629c":{"id":"a8b82143-da87-47bb-8c68-5ce367ed629c","doc_no":"A.6.1.1.1.3.8.2.2.1","title":"Marginable Assets Parameters Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5275,"content":"The subdocuments herein define the specific risk parameters or limits applicable to each accepted margin collateral asset.","contentHash":"78c541501c5f3dd2560ee40d300541589b7e0e628230e56e0d152fbf6e8039aa","addressRefs":[]},"5c35ebd7-da09-4f2e-b709-e081f654609e":{"id":"5c35ebd7-da09-4f2e-b709-e081f654609e","doc_no":"A.6.1.1.1.3.8.2.2.1.1","title":"Initial LTV","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5276,"content":"The maximum ratio of loan amount to collateral value permitted when a new loan is issued. Additionally, when a margin call is triggered, the borrower must return the position to an LTV ratio equal or less than the Initial LTV. Borrowers may only withdraw collateral from their position if their position LTV remains below the Initial LTV threshold after the withdrawal.","contentHash":"4535f093d56e6db2a9f810dbc33cceb9de3c7a0403014acdf19828855b4b0e47","addressRefs":[]},"7f7e0f99-83d7-45b4-b9ba-4ce80bdfe666":{"id":"7f7e0f99-83d7-45b4-b9ba-4ce80bdfe666","doc_no":"A.6.1.1.1.3.8.2.2.1.2","title":"Maintenance LTV","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5277,"content":"The maximum ratio of loan amount to collateral value above which a margin call is triggered. When triggered, the borrower is notified by the collateral agent to meet the margin call by reducing the position LTV to equal or less than the Initial LTV within the Cure Period.","contentHash":"e58f01a833db2fe825c958ae68548b18d7cc152bab82ec6337405dfb6fbbd5d1","addressRefs":[]},"5fdde1df-a2b7-4310-9d63-98392e1fdfcd":{"id":"5fdde1df-a2b7-4310-9d63-98392e1fdfcd","doc_no":"A.6.1.1.1.3.8.2.2.1.3","title":"Liquidation LTV","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5278,"content":"The maximum ratio of loan amount to collateral value above which a position may be liquidated immediately, regardless of whether there is an outstanding margin call in effect.","contentHash":"d701b2a0760bf328643b2e3ddb33098046868d4fb4e3f762ea7e3e8b5ad30fe8","addressRefs":[]},"ee8d2d3f-b5cf-4391-8081-81de0a5936c7":{"id":"ee8d2d3f-b5cf-4391-8081-81de0a5936c7","doc_no":"A.6.1.1.1.3.8.2.2.1.4","title":"Exposure Limit","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5279,"content":"The maximum aggregate exposure to a given asset permitted within Spark funded Offchain Collateralized Lending arrangements. Exposure is calculated based on total loan amounts secured by collateral backages.","contentHash":"cb2a35f8a14db80882301bd3d0f894bfe906c00ef664e410269f8e5d60b3e4c8","addressRefs":[]},"634e54de-0818-4307-aeb9-c9aae2d0a774":{"id":"634e54de-0818-4307-aeb9-c9aae2d0a774","doc_no":"A.6.1.1.1.3.8.2.2.1.5","title":"Staked and Wrapped Versions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5280,"content":"The acceptable staked or wrapped versions of a given marginable asset, including non native bridged versions of an asset.","contentHash":"913c4ce33f01e08065d7f23afb9290db4b73e9bc36f346bce4fca5fa051797d7","addressRefs":[]},"34d75d61-1df2-4921-890b-cb4ed68abe25":{"id":"34d75d61-1df2-4921-890b-cb4ed68abe25","doc_no":"A.6.1.1.1.3.8.2.2.2","title":"Marginable Assets Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5281,"content":"The subdocuments herein define the assets currently accepted as margin collateral within Spark funded Offchain Collateralized Lending arrangements.","contentHash":"b7cab2b39ef27f55a569f4979ae76ec67ade953e16cabe93a436629173e00eb6","addressRefs":[]},"8fd4dc40-59b1-47ae-ba5c-4782b9550245":{"id":"8fd4dc40-59b1-47ae-ba5c-4782b9550245","doc_no":"A.6.1.1.1.3.8.2.2.2.1","title":"Bitcoin (BTC)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5282,"content":"- Initial LTV: 80%\n- Maintenance LTV: 85%\n- Liquidation LTV: 90%\n- Exposure limit: Unlimited\n- Staked and wrapped versions: Coinbase cbBTC, Lombard LBTC, Bitgo/Bitglobal WBTC","contentHash":"1cf427775ee4b6a820c1c1bc4410651660c1690a1fe257e51a1f7732ff2e83ed","addressRefs":[]},"f6d82898-b431-43d5-8c0b-3b8e4aa9e236":{"id":"f6d82898-b431-43d5-8c0b-3b8e4aa9e236","doc_no":"A.6.1.1.1.3.8.2.2.2.2","title":"Ether (ETH)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5283,"content":"- Initial LTV: 70%\n- Maintenance LTV: 85%\n- Liquidation LTV: 90%\n- Exposure limit: Unlimited\n- Staked and wrapped versions: WETH, Lido stETH, Etherfi weETH, Alluvial lsETH, native staking with approved providers","contentHash":"e96488b15ef1e31a9e81201fd5490f426bb7b4cc896f1546cbc6f318e47f208b","addressRefs":[]},"ff7bf52c-e89d-4b2e-a55b-8c1b704a48f5":{"id":"ff7bf52c-e89d-4b2e-a55b-8c1b704a48f5","doc_no":"A.6.1.1.1.3.8.2.2.2.3","title":"Ripple (XRP)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5284,"content":"- Initial LTV: 60%\n- Maintenance LTV: 70%\n- Liquidation LTV: 80%\n- Exposure limit: $25 million\n- Staked and wrapped versions: None","contentHash":"3d4de7828999e9a7bced7f2d0886a444cb2ae339c89347e2dfe2baee0d483db4","addressRefs":[]},"b84f4195-c79d-477f-9361-3a9687ff5934":{"id":"b84f4195-c79d-477f-9361-3a9687ff5934","doc_no":"A.6.1.1.1.3.8.2.2.2.4","title":"Solana (SOL)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5285,"content":"- Initial LTV: 70%\n- Maintenance LTV: 80%\n- Liquidation LTV: 85%\n- Exposure limit: $100 million\n- Staked and wrapped versions: JitoSOL, native staking with approved providers","contentHash":"6b82f44a3cdee674132573da6376ac28bfce09fa406c1c22123c9b6e8d202d9f","addressRefs":[]},"e5d67f78-23cd-423c-80e4-2f9a4908a17c":{"id":"e5d67f78-23cd-423c-80e4-2f9a4908a17c","doc_no":"A.6.1.1.1.3.8.2.2.2.5","title":"Hyperliquid (HYPE)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5286,"content":"- Initial LTV: 60%\n- Maintenance LTV: 70%\n- Liquidation LTV: 80%\n- Exposure limit: $25 million\n- Staked and wrapped versions: Kinetiq kHYPE, native staking with approved providers","contentHash":"52e09de53d660b78ada8313b2c81261c9a81e984ed455f113cdf49708704bcc3","addressRefs":[]},"8db0e30b-c85c-4a92-8afd-84af4bfdfe92":{"id":"8db0e30b-c85c-4a92-8afd-84af4bfdfe92","doc_no":"A.6.1.1.1.3.8.2.2.2.6","title":"Gold (AU)","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5287,"content":"- Initial LTV: 80%\n- Maintenance LTV: 85%\n- Liquidation LTV: 90%\n- Exposure limit: $500 million (of which, not more than $50 million from XAUM)\n- Staked and wrapped versions: Tether XAUT, Paxos PAXG, Matrixdock XAUM","contentHash":"e781383db0c89a1f6f4517f4ea233600a850e455989723ae02d34d0d8c483f67","addressRefs":[]},"b03b3354-1290-41d6-89fe-d841c3a79d3c":{"id":"b03b3354-1290-41d6-89fe-d841c3a79d3c","doc_no":"A.6.1.1.1.3.8.2.3","title":"Approved Venues","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5288,"content":"The documents herein define the venues where liquidity and collateral related to Offchain Collateralized Lending arrangements may be held.","contentHash":"ac5c154e17afe9134525a2348e6a4a02a0efcf66a6c1af17b5963a322a5e5fdc","addressRefs":[]},"22fe93af-9188-4308-95ba-ac9917196290":{"id":"22fe93af-9188-4308-95ba-ac9917196290","doc_no":"A.6.1.1.1.3.8.2.3.1","title":"Approved Venues Parameters Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5289,"content":"The subdocuments herein define the specific risk parameters or limits applicable to each approved venue.","contentHash":"e1412aa1dbc6ca505d84ac8806512a9e90379d7daf46493277b1228fd163dbee","addressRefs":[]},"eeba9879-a5b3-4a85-b9ad-6df6c970f8d3":{"id":"eeba9879-a5b3-4a85-b9ad-6df6c970f8d3","doc_no":"A.6.1.1.1.3.8.2.3.1.1","title":"Exposure Limit","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5290,"content":"The exposure limit is the maximum amount of account value, defined in USD based on current value of assets and positions, inclusive of collateral, idle liquidity pending loan issuance, and repaid loan proceeds pending withdrawal or reinvestment, that may be held within each approved venue or under management of each collateral agent.","contentHash":"c78e2e7715f479e17e7ee66ff60ee6aeeb9a897a64a45b7b3614c6b61827008f","addressRefs":[]},"7552fd04-f619-4b13-ad86-50b00f6cdfc8":{"id":"7552fd04-f619-4b13-ad86-50b00f6cdfc8","doc_no":"A.6.1.1.1.3.8.2.3.1.2","title":"Collateral Agent","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5291,"content":"The collateral agent performs certain critical loan servicing functions on behalf of Spark Asset Foundation as lender, including issuing margin calls, performing liquidations, returning loan proceeds to the lender and excess collateral or liquidation proceeds to borrowers. This service may be provided by an affiliate of the venue/custodian, or by a third party. One venue may have multiple approved collateral agents, each with their own maximum exposure limit.","contentHash":"9cc8cee290805ac0c05d6bc16749ba4b4f84e79c1f81342f0eb8d27b1b1554c4","addressRefs":[]},"817e1360-ac36-4282-9604-1ab625755450":{"id":"817e1360-ac36-4282-9604-1ab625755450","doc_no":"A.6.1.1.1.3.8.2.3.2","title":"Approved Venues Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5292,"content":"The subdocuments herein define the currently approved venues where liquidity and collateral assets may be held for Spark’s Offchain Collateralized Lending activity.","contentHash":"db01f6581d39cdce889cc9e6783a40497676dd1cbd44ed25b57e60d4e7424807","addressRefs":[]},"fd82a25b-ef66-4fa4-b849-f2e34c9a575e":{"id":"fd82a25b-ef66-4fa4-b849-f2e34c9a575e","doc_no":"A.6.1.1.1.3.8.2.3.2.1","title":"Anchorage","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5293,"content":"Offchain Collateralized Lending may be facilitated via Anchorage, which is approved to hold collateral as well as lending liquidity related to such loans.\n\n- Venue exposure Limit: $1 billion\n- Collateral Agent(s):\n    - Anchorage Innovations: $1 billion","contentHash":"9cacce2362b7fe84382e85994e7aebb896b596055248ce5542685a038385ecc3","addressRefs":[]},"f80317f5-cf93-4610-b35a-2e60c94011d0":{"id":"f80317f5-cf93-4610-b35a-2e60c94011d0","doc_no":"A.6.1.1.1.3.8.2.4","title":"Loan Terms","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5294,"content":"The documents herein specify the policies and parameters for setting loan agreement terms.","contentHash":"b3474acb33415d73f88ddb7e399f900d417d7a4813ae970084be8e040146f62f","addressRefs":[]},"b28fabb2-4e1e-4140-92cf-b6190d5e0031":{"id":"b28fabb2-4e1e-4140-92cf-b6190d5e0031","doc_no":"A.6.1.1.1.3.8.2.4.1","title":"Loan Terms Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5295,"content":"The subdocuments herein define parameters used to specify loan terms.","contentHash":"ade6cd8340f8ae16ae4a23b1e38b6c55f601bf28c173574e8a883977a2387de6","addressRefs":[]},"d8c712e4-b71d-4e0a-812e-e86bb01af27f":{"id":"d8c712e4-b71d-4e0a-812e-e86bb01af27f","doc_no":"A.6.1.1.1.3.8.2.4.1.1","title":"Duration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5296,"content":"The length of time that a loan is issued under specific terms. At the conclusion of the loan duration, the loan may either be payable in full, be rolled over upon mutual agreement with equivalent or different loan terms, or be set up as an \"evergreen\" loan where the loan is automatically extended at the current terms until recalled.","contentHash":"1aa177c4474b0b9fee6b1858d18da6516ca85454770b9eb08718a8eea571c290","addressRefs":[]},"0ea26c9e-3dc5-43c0-8cc7-d9075afce8f3":{"id":"0ea26c9e-3dc5-43c0-8cc7-d9075afce8f3","doc_no":"A.6.1.1.1.3.8.2.4.1.2","title":"Borrow Rate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5297,"content":"The minimum borrow rate that accrues on the outstanding loan balance, expressed as an annual percentage. Actual borrow rate charged may be structured in various ways including fixed rate, fixed spread vs a benchmark, performance fee or profit sharing based, or combination of the above. However, loans may not be issued with borrow cost structures below the values specified in this Loan Terms section.","contentHash":"fa84ada3992df1393f90e937d2db4608873a62b305a08a4d72d0da44e2af6bca","addressRefs":[]},"0d3f2142-7069-41c6-8b79-e4972a3e4bdc":{"id":"0d3f2142-7069-41c6-8b79-e4972a3e4bdc","doc_no":"A.6.1.1.1.3.8.2.4.1.3","title":"Margin Call Cure Period","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5298,"content":"The maximum permitted amount of time for a borrower to meet a margin call before being liquidated.","contentHash":"57bf51259674d9d01737168e65e475b945f7555109edf8814e2f320aabac985e","addressRefs":[]},"df6eb53c-1cad-4fcc-97b8-d5bd3ca55ee8":{"id":"df6eb53c-1cad-4fcc-97b8-d5bd3ca55ee8","doc_no":"A.6.1.1.1.3.8.2.4.2","title":"Loan Terms Current Configuration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5299,"content":"The subdocuments herein specify the currently active parameters for loan terms that fall within Spark’s operational mandate.","contentHash":"fb68577da3e293051b0bbc9ea7ed99c9e7fcde536ef50ababda39648a3568a59","addressRefs":[]},"bc92d589-b079-41f8-a3fa-37300aef91b1":{"id":"bc92d589-b079-41f8-a3fa-37300aef91b1","doc_no":"A.6.1.1.1.3.8.2.4.2.1","title":"Duration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5300,"content":"Loans may be issued for the following durations:\n\n- Revolving / evergreen / payable on demand\n- Fixed rate, fixed term for up to 6 months","contentHash":"936e4ebcbb89114fe8e6d8bf1d88dc07ad6d0895324ed8c7b839230cc30eb426","addressRefs":[]},"67c9fae6-6911-4341-b94b-c03e9305c266":{"id":"67c9fae6-6911-4341-b94b-c03e9305c266","doc_no":"A.6.1.1.1.3.8.2.4.2.2","title":"Borrow Rate","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5301,"content":"The minimum borrow rate for loans via Offchain Collateralized Lending arrangements must be the greater of the following at the time of issuance or renewal:\n\n- Sky Savings Rate + 0.3%\n- SOFR + 0%","contentHash":"a615ab59b62b22ebd68bdf5bd74f0e9b0e52e0d9b91744976f19a814edbf391b","addressRefs":[]},"aedd10ee-5db1-4d38-b720-c451608c19e1":{"id":"aedd10ee-5db1-4d38-b720-c451608c19e1","doc_no":"A.6.1.1.1.3.8.2.4.2.3","title":"Margin Call Cure Period","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5302,"content":"The maximum permitted margin call cure period is 24 hours from the time the Maintenance LTV is breached.","contentHash":"830da9c40fd0935f18f5b3bd2e01175de3f5695b90a993e59525a3e6b947b214","addressRefs":[]},"19eeb757-6167-4aff-87f4-5f97331ab7e6":{"id":"19eeb757-6167-4aff-87f4-5f97331ab7e6","doc_no":"A.6.1.1.1.3.8.2.5","title":"Recall and Acceleration","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5303,"content":"The documents herein provide details of how and when loans should be recalled, accelerated, or liquidated in order to mitigate risk.","contentHash":"99baaecb233cd277c46f82e60bfa624e94d8a87dd980a1e3626d091b1df2ba94","addressRefs":[]},"86e1af9b-26e8-4170-a4a9-5b7285d861c2":{"id":"86e1af9b-26e8-4170-a4a9-5b7285d861c2","doc_no":"A.6.1.1.1.3.8.2.5.1","title":"Borrower Insolvency","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5304,"content":"If a borrower becomes insolvent or enters administration, any outstanding debts facilitated via Offchain Collateralized Lending arrangements become due and payable immediately. If the borrower does not repay the debt promptly, collateral may be liquidated to protect the interests of the lender.","contentHash":"9530898e128b84305ba005bf6c620e2872fd55eb2325209625d35bd2b5a6dada","addressRefs":[]},"a080d478-dcc8-4830-be67-136f810422d0":{"id":"a080d478-dcc8-4830-be67-136f810422d0","doc_no":"A.6.1.1.1.3.8.2.5.2","title":"Cross Default","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5305,"content":"If a borrower defaults on or is liquidated in one Offchain Collateralized Loan funded by Spark, Spark may accelerate any other outstanding loans from the same borrower.","contentHash":"70b83c62fbd6e8d71cc8b4062f7a095a334e1ac9fa67f52fe9baf5f5a76ce495","addressRefs":[]},"7953c6c6-337b-4d28-889c-e96fc44ab65d":{"id":"7953c6c6-337b-4d28-889c-e96fc44ab65d","doc_no":"A.6.1.1.1.3.8.2.5.3","title":"Borrow Rate Shortfall","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5306,"content":"If the borrow rate charged on a loan falls below the borrow rate threshold specified in [A.6.1.1.1.3.8.2.4.2.2 - Borrow Rate](67c9fae6-6911-4341-b94b-c03e9305c266), Spark must recall the debt or adjust the borrow rate at the earliest opportunity.","contentHash":"0d157ccfc586edb1c28ac915b7522cb6ddf1ce86031fd71e48081bd66ea5d089","addressRefs":[]},"936fa08a-3148-4c18-9aa2-420780ac884a":{"id":"936fa08a-3148-4c18-9aa2-420780ac884a","doc_no":"A.6.1.1.1.3.8.2.5.4","title":"Parameter Updates in Non Emergency Situations","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5307,"content":"Spark may update approved assets, risk parameters, and other details of the Offchain Collateralized Lending program via governance. If a previously issued loan no longer conforms with Spark’s current operational mandate due to a non-emergency parameter update, Spark will recall the loan at the earliest possible opportunity, while respecting the agreed loan duration.","contentHash":"5cb3edf4d3fbf2e3f329f79ac08904dbeafbf2138c336ef0c8f457fe884215ce","addressRefs":[]},"72ceaca8-788a-446b-90ac-c41ca65460c3":{"id":"72ceaca8-788a-446b-90ac-c41ca65460c3","doc_no":"A.6.1.1.1.3.8.2.5.5","title":"Emergency Parameter Updates","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5308,"content":"If market conditions or other factors create an immediate and severe risk of capital impairment, Spark is empowered to implement immediate changes to risk parameters and configuration to mitigate risk. Actions taken may include preventing new loans or draws on existing loans, adjusting configurable parameters, or requesting accelerated repayment and return of capital.","contentHash":"8381f85cfb6c03574c07f0de7e7ebaf78d8199a62cb86a716f7057f98fc5b345","addressRefs":[]},"4a181787-661e-4c97-9eec-0eaaa4d632c5":{"id":"4a181787-661e-4c97-9eec-0eaaa4d632c5","doc_no":"A.6.1.1.1.3.8.2.6","title":"Delegation of Rights and Responsibilities","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5309,"content":"Spark Asset Foundation is the legal owner of funds allocated via the Spark Liquidity Layer and onboarded entity for custodians and collateral agents. Spark Asset Foundation will be empowered to exercise all rights and responsibilities with respect to the Offchain Collateralized Lending allocation activities and account management, for the benefit of the Spark ecosystem and according to generally accepted business practices and Spark Asset Foundation’s professional judgement. Spark Asset Foundation may delegate certain operational functions to Phoenix Labs at its discretion, including risk underwriting, sourcing prospective borrowers, and deal negotiation.","contentHash":"85b57e90dca6548e97f885f84942e6dea2d4818578b72c9e11186a862040e99d","addressRefs":[]},"d6284e0b-441e-478b-b465-9053cd13ffaa":{"id":"d6284e0b-441e-478b-b465-9053cd13ffaa","doc_no":"A.6.1.1.1.3.8.2.7","title":"Account Management","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5310,"content":"The documents herein define the requirements for controlling and managing offchain custody accounts used within Offchain Collateralized Lending arrangements.","contentHash":"4c5ff3975fe5db29dca0ba408fea2ef225a452fec5b24aa1e46a0badd7232986","addressRefs":[]},"b501dc78-2452-40d9-acd7-7a89eef70e25":{"id":"b501dc78-2452-40d9-acd7-7a89eef70e25","doc_no":"A.6.1.1.1.3.8.2.7.1","title":"Critical Actions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5311,"content":"Critical actions are actions that could conceivably result in the loss of funds if they were executed maliciously or without authorization. The critical actions include:\n\n- Adding a withdrawal address to the whitelist\n- Adding or removing a signer from the account approvals policy\n- Changing the approval quorum\n- Transferring funds to an address outside of the preexisting withdrawal address whitelist","contentHash":"3526b42f20f9db2b464a443c9ab545c97af201773e3622fbc63804389f54b456","addressRefs":[]},"8787ecfc-d1f5-45fa-a261-c0ff12a20538":{"id":"8787ecfc-d1f5-45fa-a261-c0ff12a20538","doc_no":"A.6.1.1.1.3.8.2.7.2","title":"Address Whitelist","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5312,"content":"Accounts shall only whitelist addresses for withdrawals to either an approved collateral agent for the relevant custodian, to borrower addresses in connection with offchain collateralized lending agreements, or to the Spark Liquidity Layer.","contentHash":"ebeaf6094060b9dee9996fb4ac09f8b2f7817d150c93f590086dadda756f76e6","addressRefs":[]},"8f3822f2-8403-444f-9db7-2a9fa2da552f":{"id":"8f3822f2-8403-444f-9db7-2a9fa2da552f","doc_no":"A.6.1.1.1.3.8.2.7.3","title":"Quorum and Signers","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5313,"content":"Accounts must require a quorum of at least 3 signers for Critical Actions. It must not be possible for quorum to be met with signers from a single entity (no single entity will have enough signers to meet the quorum alone, and each critical action will therefore require approval from signers from at least 2 independent entities).\n\nSigners may be sourced from any of the following entities: Spark Asset Foundation (including legal council), Phoenix Labs, Spark Operational Executor Agent.","contentHash":"d26071981ae168177da7083ce33a4256a490d1a15c04691519e9540a82502d97","addressRefs":[]},"28517c27-b028-4b7a-9fea-6a70ae706468":{"id":"28517c27-b028-4b7a-9fea-6a70ae706468","doc_no":"A.6.1.1.1.3.8.2.7.4","title":"Transfers","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5314,"content":"Funds may be transferred to a collateral agent or whitelisted address only after Spark Asset Foundation confirmation that all required steps prior to loan disbursement have been completed.\n\nFunds may be transferred to the designated address(es) provided by the custodian or collateral manager for the payment of custody or collateral management service fees as permitted by governance-approved arrangements and upon receipt of a valid invoice.\n\nFunds may be transferred to the designated address for Spark Liquidity Layer at any time without restriction.","contentHash":"095bda588e1f61d168c9ad5699a999de7edbb6257d433e1b02a78a93b550af57","addressRefs":[]},"78018ebc-c69d-44f6-b602-190edca11483":{"id":"78018ebc-c69d-44f6-b602-190edca11483","doc_no":"A.6.1.1.1.3.9","title":"Risk Curation Framework","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5315,"content":"The documents herein specify Spark’s framework for delegating and executing certain on-chain activities through approved curator roles.","contentHash":"25fbd83554fc43ee1a23ca07fe91a2a0bdbe19b2deae0677ce44474df97495ac","addressRefs":[]},"d0c6aaa3-2d24-41f9-ac1b-51f56feff62f":{"id":"d0c6aaa3-2d24-41f9-ac1b-51f56feff62f","doc_no":"A.6.1.1.1.3.9.1","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5316,"content":"The documents herein define the process for updating Risk Curation Framework policies and procedures.","contentHash":"3d3f94caae0e4284c83e2a8caed97c5b047374918ecf45d2dda9135f6ef8940d","addressRefs":[]},"ca226501-8073-4830-b5e9-01fa960f17fe":{"id":"ca226501-8073-4830-b5e9-01fa960f17fe","doc_no":"A.6.1.1.1.3.9.1.1","title":"Risk Curation Framework Changes","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5317,"content":"Changes to Risk Curation Framework policies are implemented using the Root Edit Primitive.","contentHash":"6cb30771825ef0d4e0767c104118c40269e1eff5b17d479a6f47ede144dcc6ba","addressRefs":[]},"86925539-2db1-4a2e-930a-2ee6bc833ccd":{"id":"86925539-2db1-4a2e-930a-2ee6bc833ccd","doc_no":"A.6.1.1.1.3.9.2","title":"Purpose","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5318,"content":"The Risk Curation Framework defines the conditions under which Spark governance may authorize external contributors to execute approved changes onchain, while preserving governance oversight, timelock protections, and cancellation authorities.","contentHash":"6a83afc2cc6898acddf21db19fb7e90ac8ba058ed535ebcfc0fe405d84168578","addressRefs":[]},"6c3b277c-4acd-4692-939e-203855cff43e":{"id":"6c3b277c-4acd-4692-939e-203855cff43e","doc_no":"A.6.1.1.1.3.9.3","title":"Curator Roles","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5319,"content":"The documents herein define the meaning and scope of Curator roles within the Spark ecosystem.","contentHash":"d28e68bc6a67ef392767cedc5b7d5e7f6dc8cb9e32cc1b1511dcb206b214b426","addressRefs":[]},"3a796888-a39b-47c4-9cb9-6716d3e1c0db":{"id":"3a796888-a39b-47c4-9cb9-6716d3e1c0db","doc_no":"A.6.1.1.1.3.9.3.1","title":"Definition","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5320,"content":"A Curator is a specific admin role defined within the Morpho smart contract system.","contentHash":"15d7754c0637204ee146e81f0a4beef11eb53e8d5f56b1addcf5b401f4ed26c6","addressRefs":[]},"e4fb1a94-cfd8-40d3-ac79-966dd9f8db24":{"id":"e4fb1a94-cfd8-40d3-ac79-966dd9f8db24","doc_no":"A.6.1.1.1.3.9.3.2","title":"Scope of Authority","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5321,"content":"Curators may only execute actions that have been explicitly approved by Spark governance via polling.","contentHash":"79bfab3de01c580e1a613479fd6cd80bde6201b9bb6dfa1600d97088666c6a67","addressRefs":[]},"6f64ac9e-daf1-4339-8046-3894e57f4383":{"id":"6f64ac9e-daf1-4339-8046-3894e57f4383","doc_no":"A.6.1.1.1.3.9.3.3","title":"Reporting of Curator Actions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5322,"content":"All actions taken under a Curator role must be reported by the Curator in the Spark-Prime subsection of the Sky forum within 24 hours of submission. The report should include a transaction hash of the action, the UTC time at which the timelock period for the action elapses, a description of the action being implemented, and a link to the poll which provided governance approval for the action.","contentHash":"2f787bf716e9521cb31750430d18d3f6af3eea99e5d51bef9eba5ba38e540b4b","addressRefs":[]},"e3ddbd39-ee57-4b17-b66e-8bc823a03098":{"id":"e3ddbd39-ee57-4b17-b66e-8bc823a03098","doc_no":"A.6.1.1.1.3.9.4","title":"Governance Approval Process","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5323,"content":"The documents herein describe the requirements for all Curator actions to be approved by governance.","contentHash":"fd7b445df977ede5f65667135ab5e467c3b1f92705394da0041747087455322b","addressRefs":[]},"218f889f-6a5d-46a8-b8a3-cb0a075825c2":{"id":"218f889f-6a5d-46a8-b8a3-cb0a075825c2","doc_no":"A.6.1.1.1.3.9.4.1","title":"Polling Requirement","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5324,"content":"All curator-executed changes must be approved in advance by Spark governance through a polling process.","contentHash":"7e6dbdaa86cd74237f98f0227eb3661ecffe6670a20e378d7ac0370139eac9b3","addressRefs":[]},"48e6eeb9-86c0-4bfa-8be0-e9917d163118":{"id":"48e6eeb9-86c0-4bfa-8be0-e9917d163118","doc_no":"A.6.1.1.1.3.9.4.2","title":"Execution Authority","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5325,"content":"Following successful governance approval, the Curator is authorized to execute the approved change or changes by submitting the corresponding onchain transaction or transactions.","contentHash":"60f1f368c09449b0900a6894e8888f9fd8765d28f383f7871e5663ac5b53b8f1","addressRefs":[]},"a4f6132e-787f-445a-9290-bd810b9eb93f":{"id":"a4f6132e-787f-445a-9290-bd810b9eb93f","doc_no":"A.6.1.1.1.3.9.5","title":"Timelock Controls","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5326,"content":"The documents herein define the requirements for Timelock mechanisms to be used in conjunction with Curator roles.","contentHash":"5702beb473d851509ad4ef493e90703668f8c690b0ba9bfc69c5e39a15e7aba0","addressRefs":[]},"9cb30c4c-ecbb-4874-a931-b900b868b888":{"id":"9cb30c4c-ecbb-4874-a931-b900b868b888","doc_no":"A.6.1.1.1.3.9.5.1","title":"Timelock Requirement","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5327,"content":"All admin or privileged controls managed by curator roles must be subject to a minimum timelock delay of three (3) days between scheduling and execution.","contentHash":"fe2a2fa057ccb4fd2352bdd97d2855583a0c44f496148476cf6b77dd999562d1","addressRefs":[]},"4f45b29e-9f94-48d3-940c-1cd6b1f06f4b":{"id":"4f45b29e-9f94-48d3-940c-1cd6b1f06f4b","doc_no":"A.6.1.1.1.3.9.5.2","title":"Visibility","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5328,"content":"Pending changes subject to the timelock must be publicly visible onchain for the duration of the delay period.","contentHash":"e700a201e7149fe33f0b744d94c4ee7becf19de7c816fae36a6430d6daec47e3","addressRefs":[]},"86153ff2-e3f2-44af-b19b-678cbbac27f5":{"id":"86153ff2-e3f2-44af-b19b-678cbbac27f5","doc_no":"A.6.1.1.1.3.9.6","title":"Cancellation Authorities","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5329,"content":"The documents herein define the cancellation mechanisms and authorities for pending actions within the Timelock period.","contentHash":"6c2dc477a6b4ebedb2a460ca35c57c43236e8e9820e0df070dc1308c78e31f77","addressRefs":[]},"f87333c8-ec5e-4483-83a9-791e1f9f9634":{"id":"f87333c8-ec5e-4483-83a9-791e1f9f9634","doc_no":"A.6.1.1.1.3.9.6.1","title":"Authorized Cancellers","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5330,"content":"Pending changes within the timelock must be able to be cancelled by any of the following: the Spark subdao proxy, or a designated guardian role.","contentHash":"6e4e52aa84da4931f58a75292c53f9fa948831dacbdfb4ebf318dee160b612e4","addressRefs":[]},"0e572cad-bdf2-437f-b272-0cd634424b19":{"id":"0e572cad-bdf2-437f-b272-0cd634424b19","doc_no":"A.6.1.1.1.3.9.6.2","title":"Cancellation Reasons","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5331,"content":"Pending changes may be cancelled for the following reasons: misalignment or conflict with the Sky Atlas or Spark Artifact; excessive or unacceptable risk, as identified by the Sky Core Council or Spark Risk Council; emergency situations, as defined in the Sky Atlas in [A.1.9 - Emergency Response System](1d940c6d-02ce-4c17-8057-cef13c1cc7ad); or cancellation requested by the Curator.","contentHash":"9d1ffec6bd12051a1fe3e531757381052407021427d593e612c4606789414194","addressRefs":[]},"900c4a0d-ed93-41ad-b914-f84d50d6940e":{"id":"900c4a0d-ed93-41ad-b914-f84d50d6940e","doc_no":"A.6.1.1.1.3.9.6.3","title":"Guardian Role","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5332,"content":"A Guardian is a specific admin role defined within the Morpho smart contract system, also referred to as a Sentinel in some cases.","contentHash":"ef5933fcbb9dccdea0b6ae7ac90c208f9a8edd39e8e15984a0ebcb6906cd9f34","addressRefs":[]},"ea50c8da-008e-4f0f-b2df-ac666d5faf13":{"id":"ea50c8da-008e-4f0f-b2df-ac666d5faf13","doc_no":"A.6.1.1.1.3.9.6.3.1","title":"Guardian Independence","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5333,"content":"The Guardian must be independent from the Curator for each specific smart contract instance, meaning there must be no overlap between approvers, signers, contributors, role owners, or entities between the two roles. Compromise or misalignment of the Curator role should not in itself create risk of the Guardian role also becoming compromised.","contentHash":"2faf44d9ebe24530a867bed134b619aefd0baa1532f7bf289eaf8b2150d915c6","addressRefs":[]},"ac45b63b-3394-49d6-aab7-ff67b1d4fd0c":{"id":"ac45b63b-3394-49d6-aab7-ff67b1d4fd0c","doc_no":"A.6.1.1.1.3.9.6.3.2","title":"Guardian Reporting","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5334,"content":"All actions taken under a Guardian role must be reported by the Guardian in the Spark-Prime subsection of the Sky forum within 24 hours of submission. The report should include a transaction hash of the action, a description of the action, general reasoning for the action, and justification for the action being within the governance-approved mandate.","contentHash":"4711fa1a7b2ab97357173014a489729ad3488a01183b760691c4fb48acf94801","addressRefs":[]},"b3b590f9-0d3e-4c4a-a9e5-5b114d3c0ae4":{"id":"b3b590f9-0d3e-4c4a-a9e5-5b114d3c0ae4","doc_no":"A.6.1.1.1.3.9.7","title":"Delegated Risk Curation Instances","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5335,"content":"Spark governance approves the following instances of delegated risk curation authority. Each instance is governed independently and subject to the Risk Curation Framework.","contentHash":"bfbfb0953031fe41b27b0beecb355e18dc0c89e59c2db09412d0fc4648cd7f8d","addressRefs":[]},"3d1e7988-f513-4632-a653-69d420379998":{"id":"3d1e7988-f513-4632-a653-69d420379998","doc_no":"A.6.1.1.1.3.9.7.1","title":"Instance Parameter Definitions","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5336,"content":"The subdocuments herein describe the parameters which must be defined and maintained for each instance of delegated risk curation authority.","contentHash":"5ea5e75b9160b29c52a3dc8bbf358f447acd9997c01152f007c1bf09e7371ccf","addressRefs":[]},"e6fadf50-32a8-4c12-9b01-2ac1b9f8c1fb":{"id":"e6fadf50-32a8-4c12-9b01-2ac1b9f8c1fb","doc_no":"A.6.1.1.1.3.9.7.1.1","title":"Instance Name","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5337,"content":"The name of the product, vault, or protocol where authority is delegated.","contentHash":"a4f6fcebec1584facc297404cdfe9b195e169a860b868bce00c1c31365a804d0","addressRefs":[]},"6b237359-81f4-4089-a1cb-9674cc029fcd":{"id":"6b237359-81f4-4089-a1cb-9674cc029fcd","doc_no":"A.6.1.1.1.3.9.7.1.2","title":"Contract Address","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5338,"content":"The specific onchain contract address and the ownership or admin role over which curator authority is delegated.","contentHash":"03dc4aa4d7eae70c53c8e53573e4e8b44b18ab8b325fe4a1482eb04a92911a07","addressRefs":[]},"35326711-9bda-4880-a716-bbb0eb6a3762":{"id":"35326711-9bda-4880-a716-bbb0eb6a3762","doc_no":"A.6.1.1.1.3.9.7.1.3","title":"Curator","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5339,"content":"The entity or entities serving in the curator role, including how the role is controlled at the smart contract level, such as a multisig address and approval threshold or an alternative control mechanism.","contentHash":"93d8316628f4252600a52e46a2fa8fafed529c62cd143946f8b39408e113168b","addressRefs":[]},"0d5c17a2-a4a3-4f81-af4c-49839bc7b36f":{"id":"0d5c17a2-a4a3-4f81-af4c-49839bc7b36f","doc_no":"A.6.1.1.1.3.9.7.1.4","title":"Scope of Curator Authority","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5340,"content":"The specific execution actions the curator is permitted to take, subject to prior Spark governance approval via polling.","contentHash":"80a55c3bf307fb885b6e95597741c71c05a73f463f40c87b185550e917bce18c","addressRefs":[]},"817391bd-3748-479c-846e-f8d3e3ec56f4":{"id":"817391bd-3748-479c-846e-f8d3e3ec56f4","doc_no":"A.6.1.1.1.3.9.7.1.5","title":"Guardian","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5341,"content":"The entity or entities serving in the guardian role, including how the role is controlled at the smart contract level and how cancellation authority is exercised.","contentHash":"20d74831c2a0ef27566b6047c0960540696176afcb48379521a0b49d53075c54","addressRefs":[]},"5f30c335-8f12-4cc7-becd-f542a7546463":{"id":"5f30c335-8f12-4cc7-becd-f542a7546463","doc_no":"A.6.1.1.1.3.9.7.2","title":"Approved Instances","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5342,"content":"The documents herein enumerate the current approved instances of delegated risk curation authority.","contentHash":"1c479512f8e7ef48ff832805d5113fee43c473f950bb2d24de7de46f709159a8","addressRefs":[]},"3e8ed24b-da4a-4c3f-9a74-c3dd6a557abf":{"id":"3e8ed24b-da4a-4c3f-9a74-c3dd6a557abf","doc_no":"A.6.1.1.1.3.9.7.2.1","title":"Spark USDS Morpho Vault - Ethereum Mainnet","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5343,"content":"The Spark USDS Morpho Vault on Ethereum Mainnet is an approved instance with the following details:\n\n- Instance Name: Spark USDS Morpho Vault (Ethereum Mainnet)\n- Contract Address: `0xe41a0583334f0dc4E023Acd0bFef3667F6FE0597`\n- Curator: Soter Labs, implemented via a Gnosis Safe multisig at `0x0f963A8A8c01042B69054e787E5763ABbB0646A3`, requiring a 3 of 5 signer approval threshold\n- Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance polls\n- Guardian: Spark Foundation, implemented via a Gnosis Safe multisig at `0xf5748bBeFa17505b2F7222B23ae11584932C908B`, requiring a 3 of 5 signer approval threshold","contentHash":"c449e0073ef05b71f8a1cc67fef44c86d0b44dfe4e4c75c2ef3b908d2135ad24","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3","0xe41a0583334f0dc4e023acd0bfef3667f6fe0597","0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"603cf96e-5819-4e3d-942e-5290dd000847":{"id":"603cf96e-5819-4e3d-942e-5290dd000847","doc_no":"A.6.1.1.1.3.9.7.2.2","title":"Spark Blue Chip USDC Morpho Vault - Ethereum Mainnet","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5344,"content":"The Spark Blue Chip USDC Morpho Vault on Ethereum mainnet is an approved instance with the following details:\n\n- Instance Name: Spark Blue Chip USDC Morpho Vault (Ethereum Mainnet)\n- Contract Address: `0x56A76b428244a50513ec81e225a293d128fd581D`\n- Curator: Soter Labs, implemented via a Gnosis Safe multisig at `0x0f963A8A8c01042B69054e787E5763ABbB0646A3`, requiring a 3 of 5 signer approval threshold\n- Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance polls\n- Guardian: Spark Foundation, implemented via a Gnosis Safe multisig at `0xf5748bBeFa17505b2F7222B23ae11584932C908B`, requiring a 3 of 5 signer approval threshold","contentHash":"0ef3030283bbd8d96ea6293ab727d60e6b0f4c4226c1d843fda7d04b6d63960e","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3","0x56a76b428244a50513ec81e225a293d128fd581d","0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"5ef1e78f-e1d2-4b09-b00c-618e36ccb2d8":{"id":"5ef1e78f-e1d2-4b09-b00c-618e36ccb2d8","doc_no":"A.6.1.1.1.3.9.7.2.3","title":"Spark Blue Chip USDT Morpho Vault - Ethereum Mainnet","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5345,"content":"The Spark Blue Chip USDT Morpho Vault on Ethereum mainnet is an approved instance with the following details:\n\n- Instance Name: Spark Blue Chip USDT Morpho Vault (Ethereum Mainnet)\n- Contract Address: `0xc7CDcFDEfC64631ED6799C95e3b110cd42F2bD22`\n- Curator: Soter Labs, implemented via a Gnosis Safe multisig at `0x0f963A8A8c01042B69054e787E5763ABbB0646A3`, requiring a 3 of 5 signer approval threshold\n- Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance polls\n- Guardian: Spark Foundation, implemented via a Gnosis Safe multisig at `0xf5748bBeFa17505b2F7222B23ae11584932C908B`, requiring a 3 of 5 signer approval threshold","contentHash":"b08d817537da209a85052244383f78eb97069690973a2b6953f4ac2ac226179d","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3","0xc7cdcfdefc64631ed6799c95e3b110cd42f2bd22","0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"85722a93-ec30-4e7f-883c-adde12b0ac6b":{"id":"85722a93-ec30-4e7f-883c-adde12b0ac6b","doc_no":"A.6.1.1.1.3.9.7.2.4","title":"Spark USDC Morpho Vault - Base","type":"Core","depth":6,"parentId":"f5ba2aec-ac1b-4da9-adc9-e1d370620e72","order":5346,"content":"The Spark USDC Morpho Vault on Base is an approved instance with the following details:\n\n- Instance Name: Spark USDC Morpho Vault (Base)\n- Contract Address: `0x7BfA7C4f149E7415b73bdeDfe609237e29CBF34A`\n- Curator: Soter Labs, implemented via a Gnosis Safe multisig at `0x0f963A8A8c01042B69054e787E5763ABbB0646A3`, requiring a 3 of 5 signer approval threshold\n- Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance polls\n- Guardian: Spark Foundation, implemented via a Gnosis Safe multisig at `0xf5748bBeFa17505b2F7222B23ae11584932C908B`, requiring a 3 of 5 signer approval threshold","contentHash":"6784beb27c4cc78fcd603fbaf60856309f00d3c7523a6da7d9d25ec2a4d58dd8","addressRefs":["0x0f963a8a8c01042b69054e787e5763abbb0646a3","0x7bfa7c4f149e7415b73bdedfe609237e29cbf34a","0xf5748bbefa17505b2f7222b23ae11584932c908b"]},"727b0de6-095b-485e-bf9c-02108a364480":{"id":"727b0de6-095b-485e-bf9c-02108a364480","doc_no":"A.6.1.1.2","title":"Grove","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":5347,"content":"The documents herein specify all of the logic for Grove, including Grove’s strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"7bc225668f1a5bb92e9996165d9899742015b54cb240b4ad2f5a9d333dffb195","addressRefs":[]},"197ef51d-d785-491d-b929-cc659f3f3bb9":{"id":"197ef51d-d785-491d-b929-cc659f3f3bb9","doc_no":"A.6.1.1.2.1","title":"Introduction","type":"Core","depth":5,"parentId":"727b0de6-095b-485e-bf9c-02108a364480","order":5348,"content":"Grove is an Agent focused on unlocking the full potential of USDS through higher savings rates and new products and opportunities. Its main focus will be building an institutional-grade credit platform designed to facilitate credit creation and seamlessly move yield in and out of the onchain economy.","contentHash":"6f3777072bf7eb5989115682de5127ae508c129c5bfc5f8829f5989ca31e4e98","addressRefs":[]},"6b9bbf5e-0a76-4082-a042-811d4c426e6e":{"id":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","doc_no":"A.6.1.1.2.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"727b0de6-095b-485e-bf9c-02108a364480","order":5349,"content":"The documents herein implement the Sky Primitives for Grove. See [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"9eee5b83a01456242549b3f043d7c48c4beb638c4af75237e907d4415f59b469","addressRefs":[]},"96294c0f-de02-40e1-b2b3-4434116ccfd3":{"id":"96294c0f-de02-40e1-b2b3-4434116ccfd3","doc_no":"A.6.1.1.2.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5350,"content":"The documents herein implement the Genesis Primitives for Grove. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"33bb3c66e5a52e103987a3f5f09a92ce2f26e9a7ed913d9a20b3283984fbe2b6","addressRefs":[]},"f1d5f01a-3072-4c73-a039-7dcf19421640":{"id":"f1d5f01a-3072-4c73-a039-7dcf19421640","doc_no":"A.6.1.1.2.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5351,"content":"The documents herein contain all data and specifications for Grove’s Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"10de079d4f774bff227d53905eac88efba9616163aa7997ed305b5533fb0d22a","addressRefs":[]},"28443b6e-bf44-4a2b-9592-c1b55f2d4679":{"id":"28443b6e-bf44-4a2b-9592-c1b55f2d4679","doc_no":"A.6.1.1.2.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5352,"content":"The documents herein organize all base information relevant to Grove’s usage of the Agent Creation Primitive.","contentHash":"f82500f9bc10de379fee1e8040380a881cd40730f3ba1972d2ec69f1f463197e","addressRefs":[]},"7eee7726-9e35-4ed6-83a2-9b2b2ea8e84c":{"id":"7eee7726-9e35-4ed6-83a2-9b2b2ea8e84c","doc_no":"A.6.1.1.2.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5353,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"9e147616-5d78-4663-b474-eaa4b2b75b46":{"id":"9e147616-5d78-4663-b474-eaa4b2b75b46","doc_no":"A.6.1.1.2.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5354,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"8e823923-d5d6-4de9-b007-f9b112477cad":{"id":"8e823923-d5d6-4de9-b007-f9b112477cad","doc_no":"A.6.1.1.2.2.1.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5355,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"fc302db6-8265-4ec8-8139-9d3855411de6":{"id":"fc302db6-8265-4ec8-8139-9d3855411de6","doc_no":"A.6.1.1.2.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5356,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.1.1.3.1 - Single Instance Configuration Document](ce345522-2e73-4a7b-80f5-40eef6ad3ed1).","contentHash":"9a0417fc2f267f73ae02da647b0ae3642ca3d646d8f05cf674b93ac54f3bdbbf","addressRefs":[]},"ee1648c8-65e9-445e-9a1a-1fd3df03ea61":{"id":"ee1648c8-65e9-445e-9a1a-1fd3df03ea61","doc_no":"A.6.1.1.2.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5357,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"729bf0cf-8449-4fea-8510-f93da02ceb45":{"id":"729bf0cf-8449-4fea-8510-f93da02ceb45","doc_no":"A.6.1.1.2.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5358,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"33ee18a0-e672-469e-9d4f-3167346810f6":{"id":"33ee18a0-e672-469e-9d4f-3167346810f6","doc_no":"A.6.1.1.2.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5359,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"67170ab4-0ecf-46b4-beca-96668986ccbf":{"id":"67170ab4-0ecf-46b4-beca-96668986ccbf","doc_no":"A.6.1.1.2.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5360,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"81c5fa7b-856b-44fe-a361-2bbce3fbac56":{"id":"81c5fa7b-856b-44fe-a361-2bbce3fbac56","doc_no":"A.6.1.1.2.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5361,"content":"The subtrees for Instances of the Agent Creation Primitive with Suspended Status are stored here.","contentHash":"9d74d8318092fdddcd298b57e9de8af9fd8bc81c3b930a33d4680cf5cbf665a0","addressRefs":[]},"2549581e-c635-4389-bb57-0780bb24c37e":{"id":"2549581e-c635-4389-bb57-0780bb24c37e","doc_no":"A.6.1.1.2.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5362,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"994395c0-c61d-4fc9-8167-00ee3134bd5a":{"id":"994395c0-c61d-4fc9-8167-00ee3134bd5a","doc_no":"A.6.1.1.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5363,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"ce345522-2e73-4a7b-80f5-40eef6ad3ed1":{"id":"ce345522-2e73-4a7b-80f5-40eef6ad3ed1","doc_no":"A.6.1.1.2.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5364,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"9052b1a5-340b-4f19-a53f-357c4c690411":{"id":"9052b1a5-340b-4f19-a53f-357c4c690411","doc_no":"A.6.1.1.2.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5365,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"228cadd3-6dc4-4b08-8e57-4022c4f30cba":{"id":"228cadd3-6dc4-4b08-8e57-4022c4f30cba","doc_no":"A.6.1.1.2.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5366,"content":"The name of the Agent is Grove.","contentHash":"0d27dd305a91ee75105d084e7ace69c46f7061b17e817168fe75e33c71f7fbf3","addressRefs":[]},"d143241d-5819-432d-a6ba-892961502838":{"id":"d143241d-5819-432d-a6ba-892961502838","doc_no":"A.6.1.1.2.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5367,"content":"The address of Grove’s SubProxy Account on the Ethereum Mainnet is `0x1369f7b2b38c76B6478c0f0E66D94923421891Ba`.","contentHash":"e8f2e99126e4cdf7ca2dfe0853aeec9e5022b0c7a99671bdea652504161c237a","addressRefs":["0x1369f7b2b38c76b6478c0f0e66d94923421891ba"]},"9f6f0416-1efa-4986-aec9-0ee66cd13758":{"id":"9f6f0416-1efa-4986-aec9-0ee66cd13758","doc_no":"A.6.1.1.2.2.1.1.3.1.1.3","title":"Genesis Account","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5368,"content":"The address of Grove’s Genesis Account will be specified in a future iteration of the Grove Artifact.","contentHash":"8503cc6e1deb631605df2d774d56be6a22e32ace4eb4f74aaa14bcc54243b62b","addressRefs":[]},"e412a2af-5d3b-4901-b2a6-592b9695f07e":{"id":"e412a2af-5d3b-4901-b2a6-592b9695f07e","doc_no":"A.6.1.1.2.2.1.1.3.1.1.4","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5369,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"70d75e6f-009f-4ac0-b430-881b86d573ca":{"id":"70d75e6f-009f-4ac0-b430-881b86d573ca","doc_no":"A.6.1.1.2.2.1.1.3.1.1.4.1","title":"Grove Foundation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5370,"content":"The Grove Foundation is the Prime Foundation associated with Grove. Its mandate is to support the development, growth, and adoption of Grove.","contentHash":"1b957174d28dfa74a0095d02c6ed5ebaac5da96e28f49d2b15ee20fd8c15a12c","addressRefs":[]},"830f6fb5-1037-4516-9efa-d7101553a3d0":{"id":"830f6fb5-1037-4516-9efa-d7101553a3d0","doc_no":"A.6.1.1.2.2.1.1.3.1.1.4.2","title":"Grove Development Company","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5371,"content":"Grove Development Company is a development company that provides services to the Grove Foundation. Grove Development Company is a \"Nested Contributor\", i.e., a core contributor to both Grove and Sky.","contentHash":"c84a6d1ee613237fcc7cf5e74df157be1a2745cfcc2c058a2f5e28e94ea971e1","addressRefs":[]},"8ff8bfe6-5311-4f5f-9daf-c56219ac0a77":{"id":"8ff8bfe6-5311-4f5f-9daf-c56219ac0a77","doc_no":"A.6.1.1.2.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5372,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"db6a125d-1b36-460e-874e-539cfb4ef1a2":{"id":"db6a125d-1b36-460e-874e-539cfb4ef1a2","doc_no":"A.6.1.1.2.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5373,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"8d9cbbed-b242-4ed5-8d87-bd9e84c68bc4":{"id":"8d9cbbed-b242-4ed5-8d87-bd9e84c68bc4","doc_no":"A.6.1.1.2.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5374,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"36e78589-bf94-4abc-b656-0041afb5062a":{"id":"36e78589-bf94-4abc-b656-0041afb5062a","doc_no":"A.6.1.1.2.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5375,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"528d1e34-12b8-464f-bfbc-13daa1cd5047":{"id":"528d1e34-12b8-464f-bfbc-13daa1cd5047","doc_no":"A.6.1.1.2.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5376,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"a7a1d15b-4d7f-4224-adc2-645c9b8dfdcb":{"id":"a7a1d15b-4d7f-4224-adc2-645c9b8dfdcb","doc_no":"A.6.1.1.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5377,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"815b45f1-a157-482c-967b-472283a5ab29":{"id":"815b45f1-a157-482c-967b-472283a5ab29","doc_no":"A.6.1.1.2.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5378,"content":"The documents herein contain all data and specifications for Grove’s Instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"ee6bebf0e91d6b540a38695172fd70924f62499a939a3ed2bfcd03ed1908fa86","addressRefs":[]},"9062717c-fe70-4a96-b063-25fc05bf68da":{"id":"9062717c-fe70-4a96-b063-25fc05bf68da","doc_no":"A.6.1.1.2.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5379,"content":"The documents herein organize all base information relevant to Grove’s usage of the Prime Transformation Primitive.","contentHash":"e2715590d6f424b5be298deca0f94638981799497a2dd411d96682125811b1fd","addressRefs":[]},"fb90f38d-0222-4b27-a7f4-b05900306d70":{"id":"fb90f38d-0222-4b27-a7f4-b05900306d70","doc_no":"A.6.1.1.2.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5380,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"871ce4b9-27e9-40d7-aaad-293223ea2fa6":{"id":"871ce4b9-27e9-40d7-aaad-293223ea2fa6","doc_no":"A.6.1.1.2.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5381,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"d448f7ac-6bf5-42b5-94ac-2c1c822b4837":{"id":"d448f7ac-6bf5-42b5-94ac-2c1c822b4837","doc_no":"A.6.1.1.2.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5382,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"e191f839-2e50-46b0-8415-95258bc8c302":{"id":"e191f839-2e50-46b0-8415-95258bc8c302","doc_no":"A.6.1.1.2.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5383,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.1.2.3.1 - Single Instance Configuration Document](4661ec23-639b-4fab-b7ff-99a1f6b36aaa).","contentHash":"498b1531c1d2c1f9f96b0b4814bd3027f775d0cc8824b7e82bfa1cff19ab84f4","addressRefs":[]},"5ae3059b-9c39-4fe2-8ad9-2d2300dfd280":{"id":"5ae3059b-9c39-4fe2-8ad9-2d2300dfd280","doc_no":"A.6.1.1.2.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5384,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"b9a2b59e-866f-48ab-a34c-dc3368a5ab28":{"id":"b9a2b59e-866f-48ab-a34c-dc3368a5ab28","doc_no":"A.6.1.1.2.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5385,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e2c36640-249f-467c-82c3-a558c910acc1":{"id":"e2c36640-249f-467c-82c3-a558c910acc1","doc_no":"A.6.1.1.2.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5386,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"4db5063a-13c5-400d-9774-dca5147b7653":{"id":"4db5063a-13c5-400d-9774-dca5147b7653","doc_no":"A.6.1.1.2.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5387,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"04b81008-b4f3-4b5b-a59c-c075e2c12d10":{"id":"04b81008-b4f3-4b5b-a59c-c075e2c12d10","doc_no":"A.6.1.1.2.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5388,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"6131c7e6-63e8-40fc-91f7-a1d873ceeeff":{"id":"6131c7e6-63e8-40fc-91f7-a1d873ceeeff","doc_no":"A.6.1.1.2.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5389,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"442e6d79-7f69-48ae-8758-05347b5efb7c":{"id":"442e6d79-7f69-48ae-8758-05347b5efb7c","doc_no":"A.6.1.1.2.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5390,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"4661ec23-639b-4fab-b7ff-99a1f6b36aaa":{"id":"4661ec23-639b-4fab-b7ff-99a1f6b36aaa","doc_no":"A.6.1.1.2.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5391,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"8d62a853-c13b-4c10-93d7-ae10b20a8e9a":{"id":"8d62a853-c13b-4c10-93d7-ae10b20a8e9a","doc_no":"A.6.1.1.2.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5392,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"b6bd02e4-8e81-43ca-a2c7-2418304e9e6d":{"id":"b6bd02e4-8e81-43ca-a2c7-2418304e9e6d","doc_no":"A.6.1.1.2.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5393,"content":"Grove is a Prime Agent.","contentHash":"31816a1b7f4d6fcdb7cca222f99dea44d2ba433a7c9f87f0804b4bff8feb6c22","addressRefs":[]},"78d2887b-bc52-44e9-9ac1-335491058347":{"id":"78d2887b-bc52-44e9-9ac1-335491058347","doc_no":"A.6.1.1.2.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5394,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"3bbb10c7-56d8-46f0-b663-40fbf8764967":{"id":"3bbb10c7-56d8-46f0-b663-40fbf8764967","doc_no":"A.6.1.1.2.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5395,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"fd32256c-72b5-4435-8fa1-b9de99b14a48":{"id":"fd32256c-72b5-4435-8fa1-b9de99b14a48","doc_no":"A.6.1.1.2.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5396,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"51eb148f-c010-4e2a-a977-a6a2cb465e2d":{"id":"51eb148f-c010-4e2a-a977-a6a2cb465e2d","doc_no":"A.6.1.1.2.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5397,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"69cbf93f-2d99-4900-af0e-8e5d5609e2ca":{"id":"69cbf93f-2d99-4900-af0e-8e5d5609e2ca","doc_no":"A.6.1.1.2.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5398,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"4bb102d6-3cdf-41c2-a285-20f2db76902c":{"id":"4bb102d6-3cdf-41c2-a285-20f2db76902c","doc_no":"A.6.1.1.2.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5399,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"57c07fc2-51cc-442d-bf1b-326022ae71a2":{"id":"57c07fc2-51cc-442d-bf1b-326022ae71a2","doc_no":"A.6.1.1.2.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5400,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"999bd004-5dfa-40cd-89fe-1957515a0bb5":{"id":"999bd004-5dfa-40cd-89fe-1957515a0bb5","doc_no":"A.6.1.1.2.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5401,"content":"The documents herein contain all data and specifications for Grove’s Instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"16202c250ace21cf008dbf39156e3b985a30654d05d6c61e8a65e53ca76514d8","addressRefs":[]},"3d4fc87f-c02b-4e39-bbca-8cd90919479a":{"id":"3d4fc87f-c02b-4e39-bbca-8cd90919479a","doc_no":"A.6.1.1.2.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5402,"content":"The documents herein organize all base information relevant to Grove’s usage of the Executor Transformation Primitive.","contentHash":"00207574236c4cc0290dcf33e077300ab370f0bdfd7ec8007c811f6e32407bf0","addressRefs":[]},"1eac6dfe-960d-4625-925b-a4d074d36d4f":{"id":"1eac6dfe-960d-4625-925b-a4d074d36d4f","doc_no":"A.6.1.1.2.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5403,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"84d992af-ac27-49af-806b-2616736987ef":{"id":"84d992af-ac27-49af-806b-2616736987ef","doc_no":"A.6.1.1.2.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5404,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"40033336-9318-4a3d-a08e-9ce426ec302b":{"id":"40033336-9318-4a3d-a08e-9ce426ec302b","doc_no":"A.6.1.1.2.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5405,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"a653f42c-31ad-48c7-ac25-6ba2c54f8ff3":{"id":"a653f42c-31ad-48c7-ac25-6ba2c54f8ff3","doc_no":"A.6.1.1.2.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5406,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"07058335-a298-4542-aea3-09959c18746d":{"id":"07058335-a298-4542-aea3-09959c18746d","doc_no":"A.6.1.1.2.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5407,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"fabc93a3-02b4-44a8-9876-c23a5aaa9078":{"id":"fabc93a3-02b4-44a8-9876-c23a5aaa9078","doc_no":"A.6.1.1.2.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5408,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"adf7addb-1fe6-48a9-bb35-5d6bd6b1b2f0":{"id":"adf7addb-1fe6-48a9-bb35-5d6bd6b1b2f0","doc_no":"A.6.1.1.2.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5409,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"23572a29-d807-47f0-ab23-2e538a6d02aa":{"id":"23572a29-d807-47f0-ab23-2e538a6d02aa","doc_no":"A.6.1.1.2.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5410,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"9bceeba9-9bd7-4f23-91df-9424007e4373":{"id":"9bceeba9-9bd7-4f23-91df-9424007e4373","doc_no":"A.6.1.1.2.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5411,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"d26312b9-a479-476e-ad23-929ee4d7caf0":{"id":"d26312b9-a479-476e-ad23-929ee4d7caf0","doc_no":"A.6.1.1.2.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5412,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"9c98d05c-bf6a-49fe-9ac2-08c063df8a75":{"id":"9c98d05c-bf6a-49fe-9ac2-08c063df8a75","doc_no":"A.6.1.1.2.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5413,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"79d2d527-745b-4fad-88ae-fc9b0d04643d":{"id":"79d2d527-745b-4fad-88ae-fc9b0d04643d","doc_no":"A.6.1.1.2.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5414,"content":"The documents herein contain all data and specifications for Grove’s Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"d604b4532c92779d41c30ad9302e68fe5cf95c71553661c39f2205d74f88fe20","addressRefs":[]},"2bb3fe7a-046f-4109-bd32-2647fa919086":{"id":"2bb3fe7a-046f-4109-bd32-2647fa919086","doc_no":"A.6.1.1.2.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5415,"content":"The documents herein organize all base information relevant to Grove’s usage of the Agent Token Primitive.","contentHash":"20cf4b23c7d0ebb7fa61db57cdf4a80ef8ffa2b1dc625148bf4f36f156d8059b","addressRefs":[]},"5f7693e2-82d2-4838-9a7b-93cd2521c2b9":{"id":"5f7693e2-82d2-4838-9a7b-93cd2521c2b9","doc_no":"A.6.1.1.2.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5416,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"d64f369d-05fc-4f2e-9634-af68df978b19":{"id":"d64f369d-05fc-4f2e-9634-af68df978b19","doc_no":"A.6.1.1.2.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5417,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"8a2340d6-0526-45bf-99ac-068a51966ead":{"id":"8a2340d6-0526-45bf-99ac-068a51966ead","doc_no":"A.6.1.1.2.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5418,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.1.4.2.1 - Single Instance Configuration Document](6d4ca2d6-58be-40ee-84b6-b1983d30f38e).","contentHash":"09dedec7c0cd6a05a5af02487d38bc6db9ff237cd30fe24c8563ee438d2a58ad","addressRefs":[]},"216eaced-019f-4a04-bfc3-efc1be763af8":{"id":"216eaced-019f-4a04-bfc3-efc1be763af8","doc_no":"A.6.1.1.2.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5419,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"6b2832fe-aaaa-4034-bc3c-821d08cc9a58":{"id":"6b2832fe-aaaa-4034-bc3c-821d08cc9a58","doc_no":"A.6.1.1.2.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5420,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"12424c5a-1555-4e1e-9818-1c7eb4eaeec3":{"id":"12424c5a-1555-4e1e-9818-1c7eb4eaeec3","doc_no":"A.6.1.1.2.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5421,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"06eacd45-af50-4bbe-bdad-d44bf806613b":{"id":"06eacd45-af50-4bbe-bdad-d44bf806613b","doc_no":"A.6.1.1.2.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5422,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"f8b37bae-f093-41c1-aaa1-6fe2ee608ff0":{"id":"f8b37bae-f093-41c1-aaa1-6fe2ee608ff0","doc_no":"A.6.1.1.2.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5423,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"1b4e14d7-85b1-4465-825a-71919e6c32a1":{"id":"1b4e14d7-85b1-4465-825a-71919e6c32a1","doc_no":"A.6.1.1.2.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5424,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"8cde8c68-6f3a-467a-8fdb-42665dd322a9":{"id":"8cde8c68-6f3a-467a-8fdb-42665dd322a9","doc_no":"A.6.1.1.2.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5425,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"6d4ca2d6-58be-40ee-84b6-b1983d30f38e":{"id":"6d4ca2d6-58be-40ee-84b6-b1983d30f38e","doc_no":"A.6.1.1.2.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5426,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"f4e00e07-2243-4a78-a316-be6ec0ec7d73":{"id":"f4e00e07-2243-4a78-a316-be6ec0ec7d73","doc_no":"A.6.1.1.2.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5427,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"6d278d01-23ee-4be2-90aa-19a878f61ac8":{"id":"6d278d01-23ee-4be2-90aa-19a878f61ac8","doc_no":"A.6.1.1.2.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5428,"content":"The name of Grove’s token is Grove.","contentHash":"8a21434e0c86aff0dcffba4489b934d4f4a47c400db2d6b9540c5eebbec9684e","addressRefs":[]},"c4aa4ea7-8dfe-411e-9ab8-2c6ace976a78":{"id":"c4aa4ea7-8dfe-411e-9ab8-2c6ace976a78","doc_no":"A.6.1.1.2.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5429,"content":"The symbol of Grove’s token is GROVE.","contentHash":"a64c071895f694eebd6a6534bbd973442efd1b0609423b2ce4a88e4cea24954f","addressRefs":[]},"24ab5d8a-1587-460f-8fd2-19a5558ad7b2":{"id":"24ab5d8a-1587-460f-8fd2-19a5558ad7b2","doc_no":"A.6.1.1.2.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5430,"content":"The Genesis Supply of GROVE is 10 billion.","contentHash":"b8dc8e0bd7322580ff4742bd3c61c958f9e8c851a29a367b7c9d907765807198","addressRefs":[]},"1e92dae7-7e0a-4392-bcbe-3458082eb2ca":{"id":"1e92dae7-7e0a-4392-bcbe-3458082eb2ca","doc_no":"A.6.1.1.2.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5431,"content":"The address of GROVE on the Ethereum Mainnet is `0xB30FE1Cf884B48a22a50D22a9282004F2c5E9406`.","contentHash":"ed88c52e549f1415229241f0c44abaa0a173b4b037ff9727b243adfa35e14414","addressRefs":["0xb30fe1cf884b48a22a50d22a9282004f2c5e9406"]},"6664bb57-161a-4530-805d-38f5eb73751c":{"id":"6664bb57-161a-4530-805d-38f5eb73751c","doc_no":"A.6.1.1.2.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5432,"content":"The Token Admin is Grove’s SubProxy.","contentHash":"84ac41752ec6bd64134e252b3791324caecb6fc151e6df40ec9a913b8954bc56","addressRefs":[]},"a0325b38-1884-410e-9940-1dc5300cd65d":{"id":"a0325b38-1884-410e-9940-1dc5300cd65d","doc_no":"A.6.1.1.2.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5433,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Grove Governance. Sky Governance retains the ability to revert where Grove is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"d8d961809525da012a33fa12fee41bff8b5753274dfa20bc4918c1b543efebd9","addressRefs":[]},"13765437-eb17-450a-bbea-7bf1ec5bc9d3":{"id":"13765437-eb17-450a-bbea-7bf1ec5bc9d3","doc_no":"A.6.1.1.2.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5434,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"330deacc-c7f8-415f-a8cb-244c055b8a3c":{"id":"330deacc-c7f8-415f-a8cb-244c055b8a3c","doc_no":"A.6.1.1.2.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5435,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.","contentHash":"40152f8fe8f97c4c79218ed3bfd930929f789afccf070bc7cd80ffdbdea8fbaf","addressRefs":[]},"a9bae1cc-2a92-4465-b7cf-9f97121f7aa7":{"id":"a9bae1cc-2a92-4465-b7cf-9f97121f7aa7","doc_no":"A.6.1.1.2.2.1.4.2.1.2.1","title":"Minting Of Tokens To Grove Foundation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5436,"content":"The Genesis Supply was minted to an account owned by the Grove Foundation. The address of the account on the Ethereum Mainnet is `0x22F443740Aa13e9d9A1Fb3dadfbEAfd3d43099fF`.","contentHash":"3db98afc7c988ad3d1ea85236774a19e78aab4275d896b75416c7ee8f80502a0","addressRefs":["0x22f443740aa13e9d9a1fb3dadfbeafd3d43099ff"]},"57b9095b-6bea-4d99-ad42-d1a580f611e5":{"id":"57b9095b-6bea-4d99-ad42-d1a580f611e5","doc_no":"A.6.1.1.2.2.1.4.2.1.2.2","title":"Transfer Of Tokens To Sky","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5437,"content":"The Grove Foundation transferred 7 billion GROVE tokens from the Grove Foundation account, specified in [A.6.1.1.2.2.1.4.2.1.2.1 - Minting Of Tokens To Grove Foundation](a9bae1cc-2a92-4465-b7cf-9f97121f7aa7), to the Sky Pause Proxy.","contentHash":"2b5c2b11dfffa1aaf9f889d33bb0e2c6a73b8ad4dd28c1a07c16d56100b84ace","addressRefs":[]},"fa25a039-762a-4a94-a6dc-1651f7396e75":{"id":"fa25a039-762a-4a94-a6dc-1651f7396e75","doc_no":"A.6.1.1.2.2.1.4.2.1.2.3","title":"Transfer Of Tokens To Grove","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5438,"content":"The Grove Foundation transferred 3 billion GROVE tokens from the Grove Foundation account, specified in [A.6.1.1.2.2.1.4.2.1.2.1 - Minting Of Tokens To Grove Foundation](a9bae1cc-2a92-4465-b7cf-9f97121f7aa7), to the Grove SubProxy.","contentHash":"f720621bc6dedc6c99122718091785cc1ec1060e84745f24bc9eaa8ffe962545","addressRefs":[]},"ebca156f-a86a-4b40-ab1e-208e6d8f0f39":{"id":"ebca156f-a86a-4b40-ab1e-208e6d8f0f39","doc_no":"A.6.1.1.2.2.1.4.2.1.2.4","title":"Transfer Of Tokens To Grove Labs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5439,"content":"Grove will transfer 2.5 billion GROVE tokens from the Grove SubProxy to Grove Labs. The address of Grove Labs on the Ethereum Mainnet is `0x1EBC4425B16FD76F01f9260d8bfFE0c2C6ecCe70`.","contentHash":"12f4f31d213bb1653b8c0ff390aa5b9c444409da7a96201136ce0539aeda2821","addressRefs":["0x1ebc4425b16fd76f01f9260d8bffe0c2c6ecce70"]},"e582003e-4acc-4690-bff8-ddf66209a9cd":{"id":"e582003e-4acc-4690-bff8-ddf66209a9cd","doc_no":"A.6.1.1.2.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5440,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"7f6a1a86-3be4-450f-82fd-3c4b8ffa4c37":{"id":"7f6a1a86-3be4-450f-82fd-3c4b8ffa4c37","doc_no":"A.6.1.1.2.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5441,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"183d8611-6c51-4b92-ab69-d8cf00b68cb4":{"id":"183d8611-6c51-4b92-ab69-d8cf00b68cb4","doc_no":"A.6.1.1.2.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5442,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"aefe1e9e-8bcb-4dfd-aa58-05778d4d4326":{"id":"aefe1e9e-8bcb-4dfd-aa58-05778d4d4326","doc_no":"A.6.1.1.2.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5443,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"573d5df7-1147-4735-b3a5-f2fea1c569c7":{"id":"573d5df7-1147-4735-b3a5-f2fea1c569c7","doc_no":"A.6.1.1.2.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5444,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"4cba9d0d-52fd-4364-89f3-5425f89af772":{"id":"4cba9d0d-52fd-4364-89f3-5425f89af772","doc_no":"A.6.1.1.2.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5445,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"82f990e4-f44f-47ef-807c-e7a4d6c73a8c":{"id":"82f990e4-f44f-47ef-807c-e7a4d6c73a8c","doc_no":"A.6.1.1.2.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5446,"content":"The documents herein implement the Operational Primitives for Grove. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"694fa1b199140a27b678df70ded97e2d8bf89a4deaf403b84903a5055448dc70","addressRefs":[]},"e5a70b27-f322-48d8-9970-9d5e68566deb":{"id":"e5a70b27-f322-48d8-9970-9d5e68566deb","doc_no":"A.6.1.1.2.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5447,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"1f609347d3ffdb0cdc31782e74b33bd0bcddde9d39114411a6e57877d86cb2d3","addressRefs":[]},"456f2f2e-b578-499a-ae8e-52c2dee6651e":{"id":"456f2f2e-b578-499a-ae8e-52c2dee6651e","doc_no":"A.6.1.1.2.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5448,"content":"The documents herein organize all base information relevant to Grove’s usage of the Executor Accord Primitive.","contentHash":"2b64cbb754aa8314dae7cadd8577577f2bb4df03c5a51b051efaeb100e67ec6b","addressRefs":[]},"84cef275-a189-4413-bacc-c1c1c1c660b3":{"id":"84cef275-a189-4413-bacc-c1c1c1c660b3","doc_no":"A.6.1.1.2.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5449,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"22b27ed2-345c-4c6e-b20a-4da40e763745":{"id":"22b27ed2-345c-4c6e-b20a-4da40e763745","doc_no":"A.6.1.1.2.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5450,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"0fee90de-5460-4dea-a9c1-d451271d30e1":{"id":"0fee90de-5460-4dea-a9c1-d451271d30e1","doc_no":"A.6.1.1.2.2.2.1.1.2.1","title":"Amatsu Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5451,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.2.1.2.1 - Amatsu Instance Configuration Document](82aa705b-b3eb-42e1-9a81-e4dfe5d721ad).","contentHash":"dfae8b0eb39c71703c24df21ec29902a4f8ff7149db916f5803fd6a940c00c94","addressRefs":[]},"19bd168f-90bf-4a6f-859f-95c31bd53141":{"id":"19bd168f-90bf-4a6f-859f-95c31bd53141","doc_no":"A.6.1.1.2.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5452,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"163e4dcb-8614-434b-884e-3a20eef260f1":{"id":"163e4dcb-8614-434b-884e-3a20eef260f1","doc_no":"A.6.1.1.2.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5453,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.2.1.1.2 - Active Instances Directory](22b27ed2-345c-4c6e-b20a-4da40e763745) , whereas failed Invocations are Archived in [A.6.1.1.2.2.2.1.1.5 - Hub Data Repository](dd89d92c-6aef-4dc6-a218-fe498d4f1756).","contentHash":"6a68220c6bb7df26833aa3f852770de09904eb4603b0f33f379cba80687b6903","addressRefs":[]},"dd89d92c-6aef-4dc6-a218-fe498d4f1756":{"id":"dd89d92c-6aef-4dc6-a218-fe498d4f1756","doc_no":"A.6.1.1.2.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5454,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"2813b706-4058-41f3-bd01-ef27c66007fc":{"id":"2813b706-4058-41f3-bd01-ef27c66007fc","doc_no":"A.6.1.1.2.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5455,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"8e572907-768b-4d12-899a-8fcc3c2d600f":{"id":"8e572907-768b-4d12-899a-8fcc3c2d600f","doc_no":"A.6.1.1.2.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5456,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"eb6955b2-cf21-418f-86ed-153fa2faa02b":{"id":"eb6955b2-cf21-418f-86ed-153fa2faa02b","doc_no":"A.6.1.1.2.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5457,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"7da4fef1-0a6b-4ac6-b797-34095d491d04":{"id":"7da4fef1-0a6b-4ac6-b797-34095d491d04","doc_no":"A.6.1.1.2.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5458,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"82aa705b-b3eb-42e1-9a81-e4dfe5d721ad":{"id":"82aa705b-b3eb-42e1-9a81-e4dfe5d721ad","doc_no":"A.6.1.1.2.2.2.1.2.1","title":"Amatsu Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5459,"content":"The documents herein contain the Instance Configuration Document for the Amatsu Executor Accord Primitive Instance.","contentHash":"1c21c6e9bcc0a4917d31cb0e3687e2950886c0069d29ade1eaf0b26555b89dae","addressRefs":[]},"cae448f3-41f3-487c-afe7-981019f9c804":{"id":"cae448f3-41f3-487c-afe7-981019f9c804","doc_no":"A.6.1.1.2.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5460,"content":"The documents herein define the parameters of the Amatsu Instance of the Executor Accord Primitive.","contentHash":"4b845300c01bbf362ffc24169c2bf2ea87cf81f1f7ffe9edfdbf4d58ffe27828","addressRefs":[]},"cae67502-6f93-462f-82b6-0a6462e71e1c":{"id":"cae67502-6f93-462f-82b6-0a6462e71e1c","doc_no":"A.6.1.1.2.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5461,"content":"The Operational Facilitator and Operational GovOps for Amatsu are specified in [A.6.1.2.1 - Operational Executor Agent Amatsu](c57df14a-fde0-43f3-89ed-c2e4981d6bd5).","contentHash":"76d9fe55fd4705270171ce3e516634decfc626df9dfd732669b6336d1959d1fe","addressRefs":[]},"5821d38f-b791-47f1-9c96-9517cd61f848":{"id":"5821d38f-b791-47f1-9c96-9517cd61f848","doc_no":"A.6.1.1.2.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5462,"content":"The documents herein define the custom parameters of the Amatsu Instance of the Executor Accord Primitive, if any.","contentHash":"ad1cc46e684a82e8dbb992bc64497d98c2b32842daf0c18d9a1ea7a5e46c6686","addressRefs":[]},"a00c5047-11d3-432b-9f1d-0745b5321476":{"id":"a00c5047-11d3-432b-9f1d-0745b5321476","doc_no":"A.6.1.1.2.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5463,"content":"The documents herein define the process for the ongoing management of the Amatsu Instance of the Executor Accord Primitive.","contentHash":"66a5c505b65a5841595a3aa7d3e91ab5e833ac6f0bf82abcb7cbdd5062b75a6c","addressRefs":[]},"03f354c3-72b7-4ed5-95c8-0ae8181fd33f":{"id":"03f354c3-72b7-4ed5-95c8-0ae8181fd33f","doc_no":"A.6.1.1.2.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5464,"content":"The documents herein contain data relevant to the Amatsu Instance of the Executor Accord Primitive.","contentHash":"013ff159b352a95ad5edd2625d11e0b5f7e8d04a27f16c9d3de86248d6580acf","addressRefs":[]},"ccb322ea-75dd-4c19-a95e-fd9d43f92f7a":{"id":"ccb322ea-75dd-4c19-a95e-fd9d43f92f7a","doc_no":"A.6.1.1.2.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5465,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"977891ae-07b1-4330-9ce2-e2ea4a7e4f75":{"id":"977891ae-07b1-4330-9ce2-e2ea4a7e4f75","doc_no":"A.6.1.1.2.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5466,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"fb51f784-8c62-4bf9-92d1-f47e42c26439":{"id":"fb51f784-8c62-4bf9-92d1-f47e42c26439","doc_no":"A.6.1.1.2.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5467,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"bd479d49-6929-4eff-8809-2d440e541748":{"id":"bd479d49-6929-4eff-8809-2d440e541748","doc_no":"A.6.1.1.2.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5468,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"3e6ee2de-3801-49bd-884b-d0b758ea39ca":{"id":"3e6ee2de-3801-49bd-884b-d0b758ea39ca","doc_no":"A.6.1.1.2.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5469,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.2.1.2 - Active Instances](7da4fef1-0a6b-4ac6-b797-34095d491d04).","contentHash":"29cda03b16334d18e24160e245b1e0fac998f28367362ecd87f8534c7fc0e05a","addressRefs":[]},"da862b9f-ca77-443a-ac56-5a287c50b4db":{"id":"da862b9f-ca77-443a-ac56-5a287c50b4db","doc_no":"A.6.1.1.2.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5470,"content":"The documents herein contain all data and specifications for Grove’s Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"5c15ffe5dd0bdcf46b8f111eda63e5a05a843abd75e7f7dd4742231ffe48f651","addressRefs":[]},"f52af41f-b3a7-4218-bce6-11104e7d941b":{"id":"f52af41f-b3a7-4218-bce6-11104e7d941b","doc_no":"A.6.1.1.2.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5471,"content":"The documents herein organize all base information relevant to Grove’s usage of the Root Edit Primitive.","contentHash":"5607a9071a762d9372d4fe32bd1f840b67fb7ce713a13b978693fc942f9531e7","addressRefs":[]},"5e279bef-d668-4023-9096-89116ab51b89":{"id":"5e279bef-d668-4023-9096-89116ab51b89","doc_no":"A.6.1.1.2.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5472,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"cc85ca83-3d53-42d4-8cc3-2db2c31c20d7":{"id":"cc85ca83-3d53-42d4-8cc3-2db2c31c20d7","doc_no":"A.6.1.1.2.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5473,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"d67d1089-48c9-4dd5-ba29-48de446f5113":{"id":"d67d1089-48c9-4dd5-ba29-48de446f5113","doc_no":"A.6.1.1.2.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5474,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.2.2.2.1 - Single Instance Configuration Document](31babaee-9849-486f-8631-74a2ca9a7da8).","contentHash":"fa135c13ac2627d8d71c953bfd4a9a610c31a771539417eda62cad72c11cd443","addressRefs":[]},"7a112fc5-64c8-4cd9-81c4-9b3fba9eb6aa":{"id":"7a112fc5-64c8-4cd9-81c4-9b3fba9eb6aa","doc_no":"A.6.1.1.2.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5475,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"4c3bcaca-94f0-4682-a1ab-d61491c04214":{"id":"4c3bcaca-94f0-4682-a1ab-d61491c04214","doc_no":"A.6.1.1.2.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5476,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"be6770ee-2f7c-4845-ac49-8b996ed61d23":{"id":"be6770ee-2f7c-4845-ac49-8b996ed61d23","doc_no":"A.6.1.1.2.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5477,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"9d0c94c8-e109-4885-ab41-3d93f331642b":{"id":"9d0c94c8-e109-4885-ab41-3d93f331642b","doc_no":"A.6.1.1.2.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5478,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"c9217525-b93f-4188-b54c-dbf2430880ea":{"id":"c9217525-b93f-4188-b54c-dbf2430880ea","doc_no":"A.6.1.1.2.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5479,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"7210d615-787f-47a7-930e-0a70157dd891":{"id":"7210d615-787f-47a7-930e-0a70157dd891","doc_no":"A.6.1.1.2.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5480,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"a4332a72-d0a3-4540-9354-d4888100ad9e":{"id":"a4332a72-d0a3-4540-9354-d4888100ad9e","doc_no":"A.6.1.1.2.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5481,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"31babaee-9849-486f-8631-74a2ca9a7da8":{"id":"31babaee-9849-486f-8631-74a2ca9a7da8","doc_no":"A.6.1.1.2.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5482,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"741abe62-8d1c-4e07-949a-2f81295bc459":{"id":"741abe62-8d1c-4e07-949a-2f81295bc459","doc_no":"A.6.1.1.2.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5483,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.2.2.2.2.2.1.2 - Operational Process Definition](40826926-adb2-4de3-936d-702e2d8cb3b9).","contentHash":"a62c5d5edf85e461cc9da5a03866b75eb9cad8f726e418624c1cc621089ea73d","addressRefs":[]},"40826926-adb2-4de3-936d-702e2d8cb3b9":{"id":"40826926-adb2-4de3-936d-702e2d8cb3b9","doc_no":"A.6.1.1.2.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5484,"content":"The documents herein define the process for using the Root Edit Primitive to update the Grove Agent Artifact. Information on Grove governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.2.3.1 - Governance Information Unrelated To Root Edit Primitive](c1c86e47-a7db-4080-ab1f-99ed8e4892f7).","contentHash":"41a5860cde5a6cf4d5a3ef7360389446770b28890d65f3de4490be633067575f","addressRefs":[]},"d919ea0f-f819-45f3-b065-7f2cbdba5b08":{"id":"d919ea0f-f819-45f3-b065-7f2cbdba5b08","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5485,"content":"The documents herein define the process for using the Root Edit Primitive to update the Grove Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"b300f340c2539412d954196605f1612adbb80e8ced397e5eef090e3159c59f6c","addressRefs":[]},"e9ae4a8a-3e61-488c-8f8b-d0062f46644d":{"id":"e9ae4a8a-3e61-488c-8f8b-d0062f46644d","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5486,"content":"The Root Edit process begins with a GROVE token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. A GROVE token holder must hold at least 1% of the total token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Grove Prime\" category.","contentHash":"1f11534b6e3d33daa42d703eceb03c87a7e09b930eea45a505d6e4b15cf78133","addressRefs":[]},"6120ba4b-afcf-49db-9a9a-55e1fd00e933":{"id":"6120ba4b-afcf-49db-9a9a-55e1fd00e933","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.1.1","title":"Root Edit Proposal Submission Requirements Exception For Nested Contributors","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5487,"content":"Nested Contributors are always authorized to submit Artifact Edit Proposals and do not have to fulfill the token-holding requirements defined in [A.6.1.1.2.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](e9ae4a8a-3e61-488c-8f8b-d0062f46644d). However, all other procedural requirements within the Root Edit process continue to apply.\n\nTo see the Agent’s Nested Contributors, see [A.6.1.1.2.2.1.1.3.1.1.4.2 - Grove Development Company](830f6fb5-1037-4516-9efa-d7101553a3d0).","contentHash":"d1c269a9d047925b5752a68fa50a268d5a61fb8463ba395775a92730e5854890","addressRefs":[]},"a0b401ae-1ced-43af-ab0b-2eb16b797270":{"id":"a0b401ae-1ced-43af-ab0b-2eb16b797270","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.1.2","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5488,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, GROVE token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Grove Prime\" category. The title of the post must include the text \"Grove Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total GROVE token supply specified in [A.6.1.1.2.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](e9ae4a8a-3e61-488c-8f8b-d0062f46644d).","contentHash":"b84670ebf498b6cebd02cdcdf36f431ddc1ccca98603837a2656c2d69d9852c4","addressRefs":[]},"3cdc7302-7f68-4143-8243-685e0681991d":{"id":"3cdc7302-7f68-4143-8243-685e0681991d","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5489,"content":"A future iteration of the Grove Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis.","contentHash":"4d04ce66f1d5c75aedeaabcd5e731c7264318523c4d0b09ac637e2e8d6fce1cf","addressRefs":[]},"381ed4ee-5ec6-460e-b613-3a4610eb0aed":{"id":"381ed4ee-5ec6-460e-b613-3a4610eb0aed","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5490,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment.\n\nIf the proposal is aligned, the Operational Facilitator must respond to the Forum post to announce their finding. In this Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"3d695884c752507d7f445ad3a572c67b44863196d11108fb8a300dc2e71ce3e7","addressRefs":[]},"f6dd56ae-ee72-4109-be99-eaf69c92c3be":{"id":"f6dd56ae-ee72-4109-be99-eaf69c92c3be","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5491,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Grove Artifact, the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. The poll is open for three (3) days. A poll must have at least 10% of the circulating token supply participating and must have more than 50% of votes cast, excluding abstentions, in favor to be approved.","contentHash":"083d68fc9efec0472ed732235072054aec482f16ed819385a5c5532be2ca72ce","addressRefs":[]},"4cd4f590-6a01-4824-a6e7-bbf4a6f5225e":{"id":"4cd4f590-6a01-4824-a6e7-bbf4a6f5225e","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.4.1","title":"Circulating Supply Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5492,"content":"For purposes of [A.6.1.1.2.2.2.2.2.1.2.1.4 - Root Edit Token Holder Vote](f6dd56ae-ee72-4109-be99-eaf69c92c3be), the circulating supply of GROVE tokens is equal to the total supply of GROVE tokens minus the sum of:\n\n1. Tokens retained by Sky and not yet distributed as token rewards (see [A.2.8.2.2.2.1.2.2 - Sky Retained Tokens And Reward Pools](fb447af6-1581-4711-b73c-dc2e8d65e843)); and\n2. Tokens retained in vesting agreements for Grove contributors and not yet distributed; and\n3. Tokens in the Grove SubProxy Account (see [A.6.1.1.2.2.1.1.3.1.1.2 - SubProxy Account](d143241d-5819-432d-a6ba-892961502838)).","contentHash":"c4c9fb48896a3344c6936c65e38af80dc9583e3687ec70584fb55a8e98d27093","addressRefs":[]},"a3dcb3c9-7e5a-48b1-aac8-9af4b5dfcfc2":{"id":"a3dcb3c9-7e5a-48b1-aac8-9af4b5dfcfc2","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5493,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"c05f5877-d0e5-49dd-9608-86aa70d58cc0":{"id":"c05f5877-d0e5-49dd-9608-86aa70d58cc0","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.5.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5494,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"d3c68da3-81ff-4b73-a50c-1f9de5b6ff7f":{"id":"d3c68da3-81ff-4b73-a50c-1f9de5b6ff7f","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5495,"content":"The Grove Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"b93cf15a7c572f3c5221fa3eafcae721b41f7fe2861561741cc4c06db50a4839","addressRefs":[]},"2a438f59-854c-4281-8bca-2bef58163c9d":{"id":"2a438f59-854c-4281-8bca-2bef58163c9d","doc_no":"A.6.1.1.2.2.2.2.2.1.2.1.6.1","title":"Time-Limited Root Edit Restrictions On Removal Of Nested Contributors","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5496,"content":"For a period of three years after the Genesis Supply emissions of GROVE tokens take place, any Artifact Edit that would have the effect of removing a Nested Contributor must be approved by a vote of SKY holders in addition to a vote of GROVE holders to be effective.","contentHash":"1373eb2c25cdd9127688d0260eb92fcf75901bd15494ff2685f935a23154d91f","addressRefs":[]},"f96c5429-a5d5-40cd-b9eb-60fe06d59860":{"id":"f96c5429-a5d5-40cd-b9eb-60fe06d59860","doc_no":"A.6.1.1.2.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5497,"content":"The documents herein define the process for using the Root Edit Primitive to update the Grove Agent Artifact in non-routine conditions.","contentHash":"ab5f5d909de65b6ded34c4f5a309462196f4a85659f3f857f42ae3076a7796ba","addressRefs":[]},"e41f9cb5-5f2c-4a90-bbf0-c221cb37cdcb":{"id":"e41f9cb5-5f2c-4a90-bbf0-c221cb37cdcb","doc_no":"A.6.1.1.2.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5498,"content":"The documents herein define the process for using the Root Edit Primitive to update the Grove Agent Artifact in urgent or emergency situations.","contentHash":"dddecf0a97c41f3ab5402bf92e96ebcbcd7409b810d5228a1c8ad1325cbd12f9","addressRefs":[]},"09e744a5-cf02-4a56-8acb-d30ee74f8a3f":{"id":"09e744a5-cf02-4a56-8acb-d30ee74f8a3f","doc_no":"A.6.1.1.2.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process in Urgent and Emergency Situations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5499,"content":"In an Urgent or Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Grove Prime\" category), unless doing so would endanger Grove or its users.","contentHash":"d8a0cfc2dd9ff9c4c9de343f44a89e6081a001e936256ee4d2d09a0038d1edba","addressRefs":[]},"13875c96-2c30-4629-864e-8a94f9fa3779":{"id":"13875c96-2c30-4629-864e-8a94f9fa3779","doc_no":"A.6.1.1.2.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5500,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"07447068-8892-4154-b3d0-7a2b4f1412cc":{"id":"07447068-8892-4154-b3d0-7a2b4f1412cc","doc_no":"A.6.1.1.2.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5501,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"619ee46a-6a8c-4f13-9a04-e8cf4f8f4b86":{"id":"619ee46a-6a8c-4f13-9a04-e8cf4f8f4b86","doc_no":"A.6.1.1.2.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5502,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"e02ff5f7-7a4f-48f6-a28e-1e1fc362072e":{"id":"e02ff5f7-7a4f-48f6-a28e-1e1fc362072e","doc_no":"A.6.1.1.2.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5503,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"9784ad9e-ecb8-49f1-95a6-fd3987482733":{"id":"9784ad9e-ecb8-49f1-95a6-fd3987482733","doc_no":"A.6.1.1.2.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5504,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"398631e5-af29-49bf-9f9c-1d8fbd7a2dc2":{"id":"398631e5-af29-49bf-9f9c-1d8fbd7a2dc2","doc_no":"A.6.1.1.2.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5505,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"3a7273a8-da6b-4e1c-b59f-7b25003d1401":{"id":"3a7273a8-da6b-4e1c-b59f-7b25003d1401","doc_no":"A.6.1.1.2.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5506,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"7186bb3ceac0218d343858fb4785f245881ea341df0733df2ce0c75dfe71fa0f","addressRefs":[]},"659ba048-7352-449d-8d89-d4ba9c72c2df":{"id":"659ba048-7352-449d-8d89-d4ba9c72c2df","doc_no":"A.6.1.1.2.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5507,"content":"The documents herein organize all base information relevant to Grove’s usage of the Light Agent Primitive.","contentHash":"8beadd3f559a8da2245fb394211085f510986ee06bae341e36500067c1ac5289","addressRefs":[]},"b7d6cbd8-c8fe-41a6-a4f0-06e78017c1c5":{"id":"b7d6cbd8-c8fe-41a6-a4f0-06e78017c1c5","doc_no":"A.6.1.1.2.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5508,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"04eb437f-4664-487f-86e8-0454bb872081":{"id":"04eb437f-4664-487f-86e8-0454bb872081","doc_no":"A.6.1.1.2.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5509,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"c4b24078-dd71-4d9b-b71d-f7030d4fdd71":{"id":"c4b24078-dd71-4d9b-b71d-f7030d4fdd71","doc_no":"A.6.1.1.2.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5510,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"d0fd8e41-7f83-40ef-b0fd-fc32a3621f98":{"id":"d0fd8e41-7f83-40ef-b0fd-fc32a3621f98","doc_no":"A.6.1.1.2.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5511,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.2.3.1.2 - Active Instances Directory](04eb437f-4664-487f-86e8-0454bb872081), whereas failed Invocations are Archived in [A.6.1.1.2.2.2.3.1.5 - Hub Data Repository](9572d7c3-5472-4a06-9e59-4e0307bea775).","contentHash":"f9b8229ee737e747183b5805c06f4d24d1dc7efac0282a2d90c7cf2219684da6","addressRefs":[]},"9572d7c3-5472-4a06-9e59-4e0307bea775":{"id":"9572d7c3-5472-4a06-9e59-4e0307bea775","doc_no":"A.6.1.1.2.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5512,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"35399b0c-a972-4a77-83cd-1a86982441bb":{"id":"35399b0c-a972-4a77-83cd-1a86982441bb","doc_no":"A.6.1.1.2.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5513,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"1efd6936-c9d7-4f38-922c-b12b9de41801":{"id":"1efd6936-c9d7-4f38-922c-b12b9de41801","doc_no":"A.6.1.1.2.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5514,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"7770f51a-89af-42f9-bcd3-3ffebadaf840":{"id":"7770f51a-89af-42f9-bcd3-3ffebadaf840","doc_no":"A.6.1.1.2.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5515,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"25b9dd1a-045c-4ef6-8b3a-7d97622e4f3c":{"id":"25b9dd1a-045c-4ef6-8b3a-7d97622e4f3c","doc_no":"A.6.1.1.2.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5516,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"93909689-5956-495c-995b-f553ce7a4611":{"id":"93909689-5956-495c-995b-f553ce7a4611","doc_no":"A.6.1.1.2.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5517,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"c0c6f3ea-db96-493f-af49-9393c31ca800":{"id":"c0c6f3ea-db96-493f-af49-9393c31ca800","doc_no":"A.6.1.1.2.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5518,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.2.3.2 - Active Instances](25b9dd1a-045c-4ef6-8b3a-7d97622e4f3c).","contentHash":"d0b5b24bd8dfedd926fd4475f70eae757a8011e9b1d69f52e7dc9d90d38cc83c","addressRefs":[]},"4360c7ca-0f42-4ad8-8cad-ffe042e2f2b4":{"id":"4360c7ca-0f42-4ad8-8cad-ffe042e2f2b4","doc_no":"A.6.1.1.2.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5519,"content":"The documents herein implement the Ecosystem Upkeep Primitives for Grove. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"d1364636bc420ddb3b2aa65edb665e42bc296ff255a58f3c3f15c9ed4200957a","addressRefs":[]},"360c4fcc-fb40-482d-b3a7-4da11dce9da9":{"id":"360c4fcc-fb40-482d-b3a7-4da11dce9da9","doc_no":"A.6.1.1.2.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5520,"content":"The documents herein contain all data and specifications for Grove’s Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"be5d061e74b5cc95c1985ec34bc8bb5966ba0c39636fbf934c239397b932a82b","addressRefs":[]},"d8588e0b-0acd-4bed-989e-8da4016d0aa9":{"id":"d8588e0b-0acd-4bed-989e-8da4016d0aa9","doc_no":"A.6.1.1.2.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5521,"content":"The documents herein organize all base information relevant to Grove’s usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"bf23e702ef00294c6832894c81035422820f905158ef88930373a762d99b3105","addressRefs":[]},"f03feadf-740b-4a9f-95bd-d34c14476df4":{"id":"f03feadf-740b-4a9f-95bd-d34c14476df4","doc_no":"A.6.1.1.2.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5522,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"be81c9fd-51a3-41cb-9cd3-ae75dc5e4a1f":{"id":"be81c9fd-51a3-41cb-9cd3-ae75dc5e4a1f","doc_no":"A.6.1.1.2.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5523,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"d303d116-aaa4-4696-82f6-3e91134a7e65":{"id":"d303d116-aaa4-4696-82f6-3e91134a7e65","doc_no":"A.6.1.1.2.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5524,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.3.1.2.1 - Single Instance Configuration Document](f462656b-7c8a-4e2c-bbc8-24552dc6cfc8).","contentHash":"bc9189c8c0c0bf587430039e290e16730655a8e429f17d55a8aaa2570c3046f3","addressRefs":[]},"f89e1ba4-a944-4448-82cb-daecf0d56d97":{"id":"f89e1ba4-a944-4448-82cb-daecf0d56d97","doc_no":"A.6.1.1.2.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5525,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"b4657323-1dfc-4754-92a0-49fce826ed6e":{"id":"b4657323-1dfc-4754-92a0-49fce826ed6e","doc_no":"A.6.1.1.2.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5526,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"7eb4aec2-75b3-4f7a-a4b1-18833a110d49":{"id":"7eb4aec2-75b3-4f7a-a4b1-18833a110d49","doc_no":"A.6.1.1.2.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5527,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"4a56ae75-633e-4806-b226-831611e3f8f1":{"id":"4a56ae75-633e-4806-b226-831611e3f8f1","doc_no":"A.6.1.1.2.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5528,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"b84bdc68-c82e-4466-b1c8-b16cf8b3901e":{"id":"b84bdc68-c82e-4466-b1c8-b16cf8b3901e","doc_no":"A.6.1.1.2.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5529,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"5435ff31-2051-4863-9dc2-971fa12fb25e":{"id":"5435ff31-2051-4863-9dc2-971fa12fb25e","doc_no":"A.6.1.1.2.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5530,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"7e2eb143-8264-40e3-9151-9c6a9a44012b":{"id":"7e2eb143-8264-40e3-9151-9c6a9a44012b","doc_no":"A.6.1.1.2.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5531,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"f462656b-7c8a-4e2c-bbc8-24552dc6cfc8":{"id":"f462656b-7c8a-4e2c-bbc8-24552dc6cfc8","doc_no":"A.6.1.1.2.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5532,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"3b2cd856-880f-474d-a64e-dca106d7f1d3":{"id":"3b2cd856-880f-474d-a64e-dca106d7f1d3","doc_no":"A.6.1.1.2.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5533,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"46e8244b-d159-4884-b07f-e758424e4ec9":{"id":"46e8244b-d159-4884-b07f-e758424e4ec9","doc_no":"A.6.1.1.2.2.3.1.2.1.1.1","title":"Terms","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5534,"content":"Grove will pay 0.50% of its market capitalization per year in USDS.","contentHash":"d18208b8cae461984dea59c9335ad6b3ac1eeddc1c2190689d8d8d76fe33d487","addressRefs":[]},"2331102b-2095-4ff4-8755-1f7bde27a6ac":{"id":"2331102b-2095-4ff4-8755-1f7bde27a6ac","doc_no":"A.6.1.1.2.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5535,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"e267d1d2-d9e7-430b-b879-9d60ef8ad348":{"id":"e267d1d2-d9e7-430b-b879-9d60ef8ad348","doc_no":"A.6.1.1.2.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5536,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"d37c033b-2a45-46d4-b7dd-741c1e902d47":{"id":"d37c033b-2a45-46d4-b7dd-741c1e902d47","doc_no":"A.6.1.1.2.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5537,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"9a359283-1c1b-4755-aa52-995f278e688d":{"id":"9a359283-1c1b-4755-aa52-995f278e688d","doc_no":"A.6.1.1.2.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5538,"content":"The process to pay 0.50% of Grove’s market capitalization per year in USDS will be specified in future iterations of the Grove Artifact.","contentHash":"d71f867fc40bb40ab8f5cbfbc1c863142750b705fee829be12a89d5c36c7695e","addressRefs":[]},"bf4a3785-8570-46ae-94ca-ac00cf709f02":{"id":"bf4a3785-8570-46ae-94ca-ac00cf709f02","doc_no":"A.6.1.1.2.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5539,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"9036e0b9-a7d7-45a6-9800-3f97c47e86e9":{"id":"9036e0b9-a7d7-45a6-9800-3f97c47e86e9","doc_no":"A.6.1.1.2.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5540,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"95ee5c6a-4556-4d94-bda4-fc322ba4f112":{"id":"95ee5c6a-4556-4d94-bda4-fc322ba4f112","doc_no":"A.6.1.1.2.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5541,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"13c839b0-85fa-4582-a3e0-196627b68220":{"id":"13c839b0-85fa-4582-a3e0-196627b68220","doc_no":"A.6.1.1.2.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5542,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"644df4fe-8018-42cb-aa19-611b7a2f35b1":{"id":"644df4fe-8018-42cb-aa19-611b7a2f35b1","doc_no":"A.6.1.1.2.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5543,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"7b2e3d7a-c6ee-4d20-911a-2ca78b8eb12e":{"id":"7b2e3d7a-c6ee-4d20-911a-2ca78b8eb12e","doc_no":"A.6.1.1.2.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5544,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"370e4310-69e9-40e9-ae26-46518187cd47":{"id":"370e4310-69e9-40e9-ae26-46518187cd47","doc_no":"A.6.1.1.2.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5545,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"3c264e80-11c3-47a6-b496-852059d8826e":{"id":"3c264e80-11c3-47a6-b496-852059d8826e","doc_no":"A.6.1.1.2.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5546,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"ef8a7a1d-4e4d-474b-97fd-801c8285e9fc":{"id":"ef8a7a1d-4e4d-474b-97fd-801c8285e9fc","doc_no":"A.6.1.1.2.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5547,"content":"The documents herein contain all data and specifications for Groves Instance of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"f763dd04e64bb43741993cdc0c9532b7e6cabb9ede31b03a00b042c339881a76","addressRefs":[]},"52031d37-fadd-4112-b2e9-53cc04ac44b8":{"id":"52031d37-fadd-4112-b2e9-53cc04ac44b8","doc_no":"A.6.1.1.2.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5548,"content":"The documents herein organize all base information relevant to Grove’s usage of the Upkeep Rebate Primitive.","contentHash":"93979aa20e4860798c42c78efef1165f7bab6ce96de19ef1296998416cf12154","addressRefs":[]},"4466d3ec-d8a2-4ffd-b5bb-f5df7e58a7e3":{"id":"4466d3ec-d8a2-4ffd-b5bb-f5df7e58a7e3","doc_no":"A.6.1.1.2.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5549,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"c418d3f5-4a8b-4932-afe9-d0131c28aff1":{"id":"c418d3f5-4a8b-4932-afe9-d0131c28aff1","doc_no":"A.6.1.1.2.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5550,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"cca7ba1c-8ba0-42f6-8d32-0310e7dc4067":{"id":"cca7ba1c-8ba0-42f6-8d32-0310e7dc4067","doc_no":"A.6.1.1.2.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5551,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.3.2.2.1 - Single Instance Configuration Document](e09238d0-83f5-4163-b3d3-613e218014fa).","contentHash":"859c890ff8f49da0c22a7d4c4e4d37db8f8faa758735a2455ff92a61ea352489","addressRefs":[]},"2a87028d-9eea-47a9-9416-be32a71c94ed":{"id":"2a87028d-9eea-47a9-9416-be32a71c94ed","doc_no":"A.6.1.1.2.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5552,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"d95b16c0-0980-4401-ad83-9b4e4c8f947e":{"id":"d95b16c0-0980-4401-ad83-9b4e4c8f947e","doc_no":"A.6.1.1.2.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5553,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"d99c0146-440f-45f2-8363-fe30f270e191":{"id":"d99c0146-440f-45f2-8363-fe30f270e191","doc_no":"A.6.1.1.2.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5554,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"5d2ceb86-dc91-47ae-94d1-1664fb672d5a":{"id":"5d2ceb86-dc91-47ae-94d1-1664fb672d5a","doc_no":"A.6.1.1.2.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5555,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"0c01a5fa-f900-4642-9d63-32571651a5cf":{"id":"0c01a5fa-f900-4642-9d63-32571651a5cf","doc_no":"A.6.1.1.2.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5556,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"d4945245-9089-4464-ae63-2facab16a444":{"id":"d4945245-9089-4464-ae63-2facab16a444","doc_no":"A.6.1.1.2.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5557,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"0bc120ca-79b5-4998-a7d6-73d401e1a93c":{"id":"0bc120ca-79b5-4998-a7d6-73d401e1a93c","doc_no":"A.6.1.1.2.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5558,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"e09238d0-83f5-4163-b3d3-613e218014fa":{"id":"e09238d0-83f5-4163-b3d3-613e218014fa","doc_no":"A.6.1.1.2.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5559,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"437e2df9-8afe-48cd-af5c-6271c04ce4c0":{"id":"437e2df9-8afe-48cd-af5c-6271c04ce4c0","doc_no":"A.6.1.1.2.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5560,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"4e5243ed-13cd-4f24-abee-d3c11886d3cc":{"id":"4e5243ed-13cd-4f24-abee-d3c11886d3cc","doc_no":"A.6.1.1.2.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5561,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"f0f37117-6d8d-4c0f-94c9-8b0842bc1ce0":{"id":"f0f37117-6d8d-4c0f-94c9-8b0842bc1ce0","doc_no":"A.6.1.1.2.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5562,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"dca8ad49-39fe-4542-92ee-da36a1a96a31":{"id":"dca8ad49-39fe-4542-92ee-da36a1a96a31","doc_no":"A.6.1.1.2.2.3.2.2.1.2.1.1","title":"Grove Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5563,"content":"Grove keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"9f5e394bfe1c967d5524e497d2dd5cba7bdd14763655d1f6232bb6c7d5548ba9","addressRefs":[]},"de9ff4be-acd3-4d10-a66a-4f18d81d73c1":{"id":"de9ff4be-acd3-4d10-a66a-4f18d81d73c1","doc_no":"A.6.1.1.2.2.3.2.2.1.2.1.2","title":"Grove Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5564,"content":"When paying Ecosystem Upkeep fees, Grove deducts the rebate from the fees it pays.","contentHash":"1e359755588397f17aec5df9c94c267429a45ecd33602152011165b1985234e4","addressRefs":[]},"75305e17-8f4b-46cc-8bb5-39fd3680a8e0":{"id":"75305e17-8f4b-46cc-8bb5-39fd3680a8e0","doc_no":"A.6.1.1.2.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5565,"content":"Operational GovOps reviews Grove’s calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Grove Prime\" category and work with Grove to resolve the disagreement. If Operational GovOps and Grove cannot resolve the disagreement, it must be escalated to Core GovOps.","contentHash":"8311746266a376b20a77fad3d4a2e5a6de3e3a6aef4c75e8d93213ad087f9046","addressRefs":[]},"be43f527-f839-49c3-aea6-b2d592f7da6b":{"id":"be43f527-f839-49c3-aea6-b2d592f7da6b","doc_no":"A.6.1.1.2.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5566,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"9e2e5c70-3d46-4e82-ab1c-f7bd87427a07":{"id":"9e2e5c70-3d46-4e82-ab1c-f7bd87427a07","doc_no":"A.6.1.1.2.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5567,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"bad21323-3b52-4851-85be-bdf165f0b560":{"id":"bad21323-3b52-4851-85be-bdf165f0b560","doc_no":"A.6.1.1.2.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5568,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"0003325e-7d02-41af-b61b-110aba99540c":{"id":"0003325e-7d02-41af-b61b-110aba99540c","doc_no":"A.6.1.1.2.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5569,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"3753d344-3218-4171-be0e-9654f690439e":{"id":"3753d344-3218-4171-be0e-9654f690439e","doc_no":"A.6.1.1.2.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5570,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"7b87b8a2-5e30-46a3-b12b-5fe0053eafc4":{"id":"7b87b8a2-5e30-46a3-b12b-5fe0053eafc4","doc_no":"A.6.1.1.2.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5571,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"d659568c-ebea-462e-8d75-0fd3d848c884":{"id":"d659568c-ebea-462e-8d75-0fd3d848c884","doc_no":"A.6.1.1.2.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5572,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"742884ea-1851-4c44-8cbc-cc8cc69dd8da":{"id":"742884ea-1851-4c44-8cbc-cc8cc69dd8da","doc_no":"A.6.1.1.2.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5573,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"6ba46f75-fc23-4697-9c3d-e33b29d49bad":{"id":"6ba46f75-fc23-4697-9c3d-e33b29d49bad","doc_no":"A.6.1.1.2.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5574,"content":"The documents herein implement the SkyLink Primitives for Grove. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"b427e96e10002878ef207e527f759242592865f237b2d646825d5d7872956629","addressRefs":[]},"9f614096-200c-48cb-abba-9f2ea3a35073":{"id":"9f614096-200c-48cb-abba-9f2ea3a35073","doc_no":"A.6.1.1.2.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5575,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"6a5d42c9ec7cd206d19c73bb5f89b2bc4934a0f8e82335fa621809abde4a81c8","addressRefs":[]},"d6e99512-2f90-4c90-8d99-8b2dec137ace":{"id":"d6e99512-2f90-4c90-8d99-8b2dec137ace","doc_no":"A.6.1.1.2.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5576,"content":"The documents herein organize all base information relevant to Grove’s usage of the Token SkyLink Primitive.","contentHash":"04e61dc53feb73ff09978647d4455721817d6b4dcbff1dedabb69d1ee4dae2e4","addressRefs":[]},"8b7eb17f-1925-44c2-b6bb-e67130b9aea8":{"id":"8b7eb17f-1925-44c2-b6bb-e67130b9aea8","doc_no":"A.6.1.1.2.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5577,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"09e7789c-4644-4a12-aef9-72d86cc488f2":{"id":"09e7789c-4644-4a12-aef9-72d86cc488f2","doc_no":"A.6.1.1.2.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5578,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"54de0b4a-0e2a-40f0-84fe-2e71a65e5aac":{"id":"54de0b4a-0e2a-40f0-84fe-2e71a65e5aac","doc_no":"A.6.1.1.2.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5579,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"19184c86-0c06-4301-ae72-90969476ef71":{"id":"19184c86-0c06-4301-ae72-90969476ef71","doc_no":"A.6.1.1.2.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5580,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.4.1.1.2 - Active Instances Directory](09e7789c-4644-4a12-aef9-72d86cc488f2), whereas failed Invocations are Archived in [A.6.1.1.2.2.4.1.1.5 - Hub Data Repository](7afcf75e-ab7c-4e1e-b856-cab87541d1e3).","contentHash":"c22b569cf4bbfd6f6a77ca0ef7c3713dc48b323604e97fae2281a4dd328e7e50","addressRefs":[]},"7afcf75e-ab7c-4e1e-b856-cab87541d1e3":{"id":"7afcf75e-ab7c-4e1e-b856-cab87541d1e3","doc_no":"A.6.1.1.2.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5581,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"2fd0c2b3-7155-46c2-9b9b-e334a88ff9e3":{"id":"2fd0c2b3-7155-46c2-9b9b-e334a88ff9e3","doc_no":"A.6.1.1.2.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5582,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"376f3393-e5af-41ad-9247-31fbe63799ac":{"id":"376f3393-e5af-41ad-9247-31fbe63799ac","doc_no":"A.6.1.1.2.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5583,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"54893d32-c54c-4550-96a7-60dc45e9962e":{"id":"54893d32-c54c-4550-96a7-60dc45e9962e","doc_no":"A.6.1.1.2.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5584,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"da5c971b-7758-486d-bddb-fba2e1b5cdc5":{"id":"da5c971b-7758-486d-bddb-fba2e1b5cdc5","doc_no":"A.6.1.1.2.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5585,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"0a3bd259-7320-40d0-b98b-17a094fc2fcd":{"id":"0a3bd259-7320-40d0-b98b-17a094fc2fcd","doc_no":"A.6.1.1.2.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5586,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"9fcd2b86-f3a9-494e-936e-45614c466ccd":{"id":"9fcd2b86-f3a9-494e-936e-45614c466ccd","doc_no":"A.6.1.1.2.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5587,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.4.1.2 - Active Instances](da5c971b-7758-486d-bddb-fba2e1b5cdc5).","contentHash":"6e2a306f944a0e192adf12456e483d06934f49323d2f8051b061e5813ddac9c2","addressRefs":[]},"79933ed7-8378-437d-a546-b03f59668a38":{"id":"79933ed7-8378-437d-a546-b03f59668a38","doc_no":"A.6.1.1.2.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5588,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Grove. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"6ad8c4a45ab60afcb88f0a0c8e258245ab6415b882fda59e20cd67428ce34440","addressRefs":[]},"8c46d61f-9b02-4898-be15-f875692f3715":{"id":"8c46d61f-9b02-4898-be15-f875692f3715","doc_no":"A.6.1.1.2.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5589,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"d0ebe32b402a2d99a7cf5833d3c7a88cb5e1481b27cfe6ea03ce3f3a092da509","addressRefs":[]},"21b5e889-c9f9-45e7-becb-fde3e070e063":{"id":"21b5e889-c9f9-45e7-becb-fde3e070e063","doc_no":"A.6.1.1.2.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5590,"content":"The documents herein organize all base information relevant to Groves usage of the Distribution Reward Primitive.","contentHash":"61d20569a10bdac4eb213e4befaf7efdb9d2014d77eaeb722d5b690094c248b7","addressRefs":[]},"95daf547-3e90-48e2-93cf-1bb2b3240b3c":{"id":"95daf547-3e90-48e2-93cf-1bb2b3240b3c","doc_no":"A.6.1.1.2.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5591,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"c1d594d3-4303-451e-9efb-2baa8ffaa034":{"id":"c1d594d3-4303-451e-9efb-2baa8ffaa034","doc_no":"A.6.1.1.2.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5592,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"974d281c-9ad2-4531-9c39-fb44281b3ed0":{"id":"974d281c-9ad2-4531-9c39-fb44281b3ed0","doc_no":"A.6.1.1.2.2.5.1.1.2.1","title":"Grove Finance Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5593,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.5.1.2.1 - Grove Finance Instance Configuration Document](006f040b-63e1-4847-abd5-9dce1190706b).","contentHash":"2e4e8be64b9171287378ce98efffb0b126ed038f4ad8b24763722a5bafa72b7c","addressRefs":[]},"11f1f7ba-82ed-4d1e-a457-344406a158f3":{"id":"11f1f7ba-82ed-4d1e-a457-344406a158f3","doc_no":"A.6.1.1.2.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5594,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"1caf1f9a-040b-4687-ad2d-e4ad0c7709d5":{"id":"1caf1f9a-040b-4687-ad2d-e4ad0c7709d5","doc_no":"A.6.1.1.2.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5595,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.5.1.1.2 - Active Instances Directory](c1d594d3-4303-451e-9efb-2baa8ffaa034), whereas failed Invocations are Archived in [A.6.1.1.2.2.5.1.1.5 - Hub Data Repository](8ea4b4ad-e167-4772-b7d6-0c87357a10e8).","contentHash":"a99503eddf046f54ecacca66059b5de176bcb6ccc3dd2691327464d9a53a25eb","addressRefs":[]},"8ea4b4ad-e167-4772-b7d6-0c87357a10e8":{"id":"8ea4b4ad-e167-4772-b7d6-0c87357a10e8","doc_no":"A.6.1.1.2.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5596,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"6be994b9-97fa-4768-9e71-2f8c2c110cd4":{"id":"6be994b9-97fa-4768-9e71-2f8c2c110cd4","doc_no":"A.6.1.1.2.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5597,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"e20a22c1-1cac-4dc5-9194-8e474ac53f4c":{"id":"e20a22c1-1cac-4dc5-9194-8e474ac53f4c","doc_no":"A.6.1.1.2.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5598,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"50eb902b-79db-47c4-8927-94303313595d":{"id":"50eb902b-79db-47c4-8927-94303313595d","doc_no":"A.6.1.1.2.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5599,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"a4df61c2-514e-46e4-a84d-d2782f2f183f":{"id":"a4df61c2-514e-46e4-a84d-d2782f2f183f","doc_no":"A.6.1.1.2.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5600,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"006f040b-63e1-4847-abd5-9dce1190706b":{"id":"006f040b-63e1-4847-abd5-9dce1190706b","doc_no":"A.6.1.1.2.2.5.1.2.1","title":"Grove Finance Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5601,"content":"The documents herein contain the Instance Configuration Document for the Grove Finance Distribution Reward Primitive Instance.","contentHash":"3fb02e90c2bdba025347bc61f45c3db6c9c2d84c6752c829127c88ed2bed105f","addressRefs":[]},"e6847aa6-4668-4cf6-a757-0b292871a703":{"id":"e6847aa6-4668-4cf6-a757-0b292871a703","doc_no":"A.6.1.1.2.2.5.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5602,"content":"The documents herein define the parameters of the Grove Finance Instance of the Distribution Reward Primitive.","contentHash":"7e244344fc217c642a2c6b10e5cc2190e81449c0421d772214eefae9b8eb80e9","addressRefs":[]},"b5b1f4eb-10a3-472b-b675-008ef0cee259":{"id":"b5b1f4eb-10a3-472b-b675-008ef0cee259","doc_no":"A.6.1.1.2.2.5.1.2.1.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5603,"content":"`2002`.","contentHash":"d0d074e9b172e18d889deb30e001fb06e6c1a8305cf4b52a0a326a0804ac3573","addressRefs":[]},"78948530-a5e9-456f-bcaf-f74a70bdc0b8":{"id":"78948530-a5e9-456f-bcaf-f74a70bdc0b8","doc_no":"A.6.1.1.2.2.5.1.2.1.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5604,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"4b91017e-ee25-4cc3-a97a-25d234e50151":{"id":"4b91017e-ee25-4cc3-a97a-25d234e50151","doc_no":"A.6.1.1.2.2.5.1.2.1.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5605,"content":"The documents herein define the custom parameters of the Grove Finance Instance of the Distribution Reward Primitive, if any.","contentHash":"e2e9cdddefa9a7bf6f744218a2a80c7aebdd0c3c2a439532a862a4283e8b98eb","addressRefs":[]},"9237ad33-0759-4637-86a8-e7ad6317ebb1":{"id":"9237ad33-0759-4637-86a8-e7ad6317ebb1","doc_no":"A.6.1.1.2.2.5.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5606,"content":"The documents herein define the process for the ongoing management of the Grove Finance Instance of the Distribution Reward Primitive.","contentHash":"9b4d05369e74135aafffa0ffa31377a436a93e930c5d46fda128a5c0bda609c8","addressRefs":[]},"fe11d361-a9c7-460e-ae67-1b2e8a6142a1":{"id":"fe11d361-a9c7-460e-ae67-1b2e8a6142a1","doc_no":"A.6.1.1.2.2.5.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5607,"content":"This document defines the protocol for routine ongoing management of the Grove Finance Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Grove Artifact, a version of the full process definition customized to Grove will be included herein.","contentHash":"e8512ddfd851839bb298172e6069e77d0bb029ce69d0635340cf43dc86727fcd","addressRefs":[]},"3fecb22f-ccd8-4bb9-8221-d354b080bef6":{"id":"3fecb22f-ccd8-4bb9-8221-d354b080bef6","doc_no":"A.6.1.1.2.2.5.1.2.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5608,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"cf4777c8-e272-4b30-9027-b391191f6473":{"id":"cf4777c8-e272-4b30-9027-b391191f6473","doc_no":"A.6.1.1.2.2.5.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5609,"content":"The documents herein define the protocol for non-routine ongoing management of the Grove Finance Instance of this Distribution Reward Primitive.","contentHash":"b54cc7f941188f7b9866e0a7e7d7107128f66db2217a6bc27a0d523e70af9608","addressRefs":[]},"e3079d41-3785-4ee6-a5d0-90fd1c111093":{"id":"e3079d41-3785-4ee6-a5d0-90fd1c111093","doc_no":"A.6.1.1.2.2.5.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5610,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Grove Finance Instance of this Distribution Reward Primitive.","contentHash":"9a881e922453c26cf2fc10ced8ce9bbbafd47dcd8c02a58314e9ffe0dbbdaaa4","addressRefs":[]},"67d2e983-09c7-41da-8b4d-99a9fb00fb2d":{"id":"67d2e983-09c7-41da-8b4d-99a9fb00fb2d","doc_no":"A.6.1.1.2.2.5.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5611,"content":"The documents herein contain data relevant to the Grove Finance Instance of the Distribution Reward Primitive.","contentHash":"a62c41554abf887138e9f5f9b5557d46951f977b60c1c84702d4c85f7bf6854f","addressRefs":[]},"7259ff43-eaf7-484e-af71-8b6a0ecdde09":{"id":"7259ff43-eaf7-484e-af71-8b6a0ecdde09","doc_no":"A.6.1.1.2.2.5.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5612,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"06a7389f-65b0-48bb-a0ee-b7b9dcbeeaa6":{"id":"06a7389f-65b0-48bb-a0ee-b7b9dcbeeaa6","doc_no":"A.6.1.1.2.2.5.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5613,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"74019895-896c-4ab1-bb8c-f0e9741e69eb":{"id":"74019895-896c-4ab1-bb8c-f0e9741e69eb","doc_no":"A.6.1.1.2.2.5.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5614,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"698d68f4-8d3f-4ab4-bfd0-95dbd34b9099":{"id":"698d68f4-8d3f-4ab4-bfd0-95dbd34b9099","doc_no":"A.6.1.1.2.2.5.1.2.1.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5615,"content":"The Distribution Reward payments for the Grove Finance Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"cf01d925c981437206d00445ef614f2ee1f3a303774b7225b7a9c77c9478c4a9","addressRefs":[]},"bbd8de10-0899-4c16-ae48-a3d0afed9c6f":{"id":"bbd8de10-0899-4c16-ae48-a3d0afed9c6f","doc_no":"A.6.1.1.2.2.5.1.2.1.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5616,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"cca65b4d-5cf9-449e-9178-195b611ddc06":{"id":"cca65b4d-5cf9-449e-9178-195b611ddc06","doc_no":"A.6.1.1.2.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5617,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"1169df23-b14e-492d-9602-996c3aa0d577":{"id":"1169df23-b14e-492d-9602-996c3aa0d577","doc_no":"A.6.1.1.2.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5618,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.5.1.2 - Active Instances](a4df61c2-514e-46e4-a84d-d2782f2f183f).","contentHash":"844e5945d14f77d6d050cffd0416f27232d22d1162e56e7b61977bcc916405b5","addressRefs":[]},"634971ac-f579-4673-afbd-6a4366d26db9":{"id":"634971ac-f579-4673-afbd-6a4366d26db9","doc_no":"A.6.1.1.2.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5619,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"f378c07b621a52a97b98a3313eb3c07d34a83346c772118322817a1329d4b90b","addressRefs":[]},"c5a92bcd-69d3-41ee-a12a-33dce8af4686":{"id":"c5a92bcd-69d3-41ee-a12a-33dce8af4686","doc_no":"A.6.1.1.2.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5620,"content":"The documents herein organize all base information relevant to Grove’s usage of the Integration Boost Primitive.","contentHash":"a75abf469c46023ddf6091027287a16c0fa58c8daf5fe7911f5b1418507c7366","addressRefs":[]},"c6414cd5-4efa-446d-876e-3fcf2dbb816a":{"id":"c6414cd5-4efa-446d-876e-3fcf2dbb816a","doc_no":"A.6.1.1.2.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5621,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"8e0e2f27-cc60-419b-8533-8ae1cbaf427e":{"id":"8e0e2f27-cc60-419b-8533-8ae1cbaf427e","doc_no":"A.6.1.1.2.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5622,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"b400b223-0b70-462d-a69e-11eb6c91fa35":{"id":"b400b223-0b70-462d-a69e-11eb6c91fa35","doc_no":"A.6.1.1.2.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5623,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"83d45b11-4497-473b-b3c4-80c0543dd5dd":{"id":"83d45b11-4497-473b-b3c4-80c0543dd5dd","doc_no":"A.6.1.1.2.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5624,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.5.2.1.2 - Active Instances Directory](8e0e2f27-cc60-419b-8533-8ae1cbaf427e), whereas failed Invocations are Archived in [A.6.1.1.2.2.5.2.1.5 - Hub Data Repository](732e99b3-3a0c-4116-b3f6-5b9d2ad4d351) .","contentHash":"dac1a5400bf4e2e55572ac76a9f72e7e2284be85ac5bf69d0b25855eff330513","addressRefs":[]},"732e99b3-3a0c-4116-b3f6-5b9d2ad4d351":{"id":"732e99b3-3a0c-4116-b3f6-5b9d2ad4d351","doc_no":"A.6.1.1.2.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5625,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"1f22572f-5c05-4ef4-8fd7-a1a21c6ad050":{"id":"1f22572f-5c05-4ef4-8fd7-a1a21c6ad050","doc_no":"A.6.1.1.2.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5626,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"ac3d0e12-3328-43ac-9632-2cf1ac50e2a7":{"id":"ac3d0e12-3328-43ac-9632-2cf1ac50e2a7","doc_no":"A.6.1.1.2.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5627,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"da15a221-360f-4c7e-a324-6b5933eb8572":{"id":"da15a221-360f-4c7e-a324-6b5933eb8572","doc_no":"A.6.1.1.2.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5628,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"b1265577-1f7d-48be-941b-9a2b0f62818e":{"id":"b1265577-1f7d-48be-941b-9a2b0f62818e","doc_no":"A.6.1.1.2.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5629,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"90e4294a-089b-4f34-bb05-a5c10e469d0b":{"id":"90e4294a-089b-4f34-bb05-a5c10e469d0b","doc_no":"A.6.1.1.2.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5630,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"b7fe4d93-cd99-4223-853e-9eebe7bdaa91":{"id":"b7fe4d93-cd99-4223-853e-9eebe7bdaa91","doc_no":"A.6.1.1.2.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5631,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.5.2.2 - Active Instances](b1265577-1f7d-48be-941b-9a2b0f62818e).","contentHash":"f44e4c400207a3aec92cde67da77fc6de7dc677de77c61af658d635c9cd17aed","addressRefs":[]},"f8ffe054-1981-457e-abc6-412f3ee37927":{"id":"f8ffe054-1981-457e-abc6-412f3ee37927","doc_no":"A.6.1.1.2.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5632,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"d2727ac2451485215445047af3481a3d1e0d318db10f032158e6415f2197b835","addressRefs":[]},"63c25970-e1dd-475c-bb77-487ac7640aaa":{"id":"63c25970-e1dd-475c-bb77-487ac7640aaa","doc_no":"A.6.1.1.2.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5633,"content":"The documents herein organize all base information relevant to Grove’s usage of the Pioneer Chain Primitive.","contentHash":"959b60157afa93dc0f5d7817c124667baec3a765e97ac10e7084c53a9762dac0","addressRefs":[]},"180defb8-541e-4de9-a7a5-d117144af928":{"id":"180defb8-541e-4de9-a7a5-d117144af928","doc_no":"A.6.1.1.2.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5634,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"d9fca80a-1cbc-413b-83ca-3c19428732e7":{"id":"d9fca80a-1cbc-413b-83ca-3c19428732e7","doc_no":"A.6.1.1.2.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5635,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"796c25b9-f650-4321-962e-3f19414a2674":{"id":"796c25b9-f650-4321-962e-3f19414a2674","doc_no":"A.6.1.1.2.2.5.3.1.2.1","title":"Avalanche Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5636,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.5.3.2.1 - Avalanche Instance Configuration Document](1fecc114-523e-4a7f-aceb-a5805aea6356).","contentHash":"da4f6cb16ba6db05f21ecc18ca42f4bfb80747b14c2a50fbadcad0dfd71881df","addressRefs":[]},"f1007e17-0599-455f-8afb-f5e965a12683":{"id":"f1007e17-0599-455f-8afb-f5e965a12683","doc_no":"A.6.1.1.2.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5637,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"6ed7f41d-b5bb-49b8-9f4c-c0b37d6ea5f0":{"id":"6ed7f41d-b5bb-49b8-9f4c-c0b37d6ea5f0","doc_no":"A.6.1.1.2.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5638,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.5.3.1.2 - Active Instances Directory](d9fca80a-1cbc-413b-83ca-3c19428732e7), whereas failed Invocations are Archived in [A.6.1.1.2.2.5.3.1.5 - Hub Data Repository](495128f2-64bb-4192-bf4a-7df6259b4010).","contentHash":"5dc0a9622f9c4a1fd0a15c3af550e3413b81f08a2521213ed3bd0edfccf0d0ed","addressRefs":[]},"495128f2-64bb-4192-bf4a-7df6259b4010":{"id":"495128f2-64bb-4192-bf4a-7df6259b4010","doc_no":"A.6.1.1.2.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5639,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"5dd58057-07cd-4ccb-97b9-6bd85855d2c6":{"id":"5dd58057-07cd-4ccb-97b9-6bd85855d2c6","doc_no":"A.6.1.1.2.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5640,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"f6788dae-477c-4a19-9302-7f42f3c7023c":{"id":"f6788dae-477c-4a19-9302-7f42f3c7023c","doc_no":"A.6.1.1.2.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5641,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"82ab7549-0214-413e-9b14-493c15a9beca":{"id":"82ab7549-0214-413e-9b14-493c15a9beca","doc_no":"A.6.1.1.2.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5642,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"33a1baf4-9922-40a1-b121-558f620da186":{"id":"33a1baf4-9922-40a1-b121-558f620da186","doc_no":"A.6.1.1.2.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5643,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"1fecc114-523e-4a7f-aceb-a5805aea6356":{"id":"1fecc114-523e-4a7f-aceb-a5805aea6356","doc_no":"A.6.1.1.2.2.5.3.2.1","title":"Avalanche Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5644,"content":"The documents herein contain the Instance Configuration Document for the Avalanche Instance of the Pioneer Chain Primitive.","contentHash":"bd2b6bdc6039bf67266ad8f52f1cb307023f064062ae9c71b5750dc0123e7330","addressRefs":[]},"7870de5f-4051-4936-a73f-9b9903a83d3b":{"id":"7870de5f-4051-4936-a73f-9b9903a83d3b","doc_no":"A.6.1.1.2.2.5.3.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5645,"content":"The documents herein define the parameters of the Avalanche Instance of the Pioneer Chain Primitive.","contentHash":"891de1bc6f71f9384f41b593bdac888331225049bf897153c6483626af14bb10","addressRefs":[]},"cd8395d4-5466-44f5-b002-12646312942b":{"id":"cd8395d4-5466-44f5-b002-12646312942b","doc_no":"A.6.1.1.2.2.5.3.2.1.1.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5646,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"29ad76ea-72f5-42bc-910a-fa57a62d501a":{"id":"29ad76ea-72f5-42bc-910a-fa57a62d501a","doc_no":"A.6.1.1.2.2.5.3.2.1.1.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5647,"content":"Avalanche","contentHash":"40515202399d262e23ee7fca28b5d73627d96f30bb61c6d064100070976e4fa9","addressRefs":[]},"9b11e488-7c8f-4a6f-a5b6-0c4c526ad86a":{"id":"9b11e488-7c8f-4a6f-a5b6-0c4c526ad86a","doc_no":"A.6.1.1.2.2.5.3.2.1.1.2","title":"Pioneer Incentive Pool","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5648,"content":"The documents herein contain the terms that govern this Instance's Pioneer Incentive Pool and its address.","contentHash":"86b4489c5004a1a438ede266ddea17e1cee462ce29ad0e5a170e27f337fc0923","addressRefs":[]},"027429d2-2a2c-4735-8bea-8bdcdf42d45f":{"id":"027429d2-2a2c-4735-8bea-8bdcdf42d45f","doc_no":"A.6.1.1.2.2.5.3.2.1.1.2.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5649,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"ea4f2336-3f9f-49f6-af4e-00a8736e19d5":{"id":"ea4f2336-3f9f-49f6-af4e-00a8736e19d5","doc_no":"A.6.1.1.2.2.5.3.2.1.1.2.2","title":"Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5650,"content":"`0x1369f7b2b38c76B6478c0f0E66D94923421891Ba`","contentHash":"6090aa7c6b170378d1ffef006402a57cdd7b36b23372ef7d1bb909fdb3064a53","addressRefs":["0x1369f7b2b38c76b6478c0f0e66d94923421891ba"]},"1702148c-fdd5-4c87-af3e-8f99f2f90f05":{"id":"1702148c-fdd5-4c87-af3e-8f99f2f90f05","doc_no":"A.6.1.1.2.2.5.3.2.1.1.2.3","title":"Terms","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5651,"content":"The Pioneer Incentive Pool for this Instance is governed by the terms specified in [A.2.2.8.3.1.4 - Pioneer Incentive Pool](04edac33-19d5-4a87-a8ab-945a0cd57771).","contentHash":"398f45540512dcf7575840dc803f208433c4e3a0be43346a3f6eeb92e954d7d8","addressRefs":[]},"11351bed-db55-44e7-a316-9996446adca7":{"id":"11351bed-db55-44e7-a316-9996446adca7","doc_no":"A.6.1.1.2.2.5.3.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5652,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Pioneer Chain Primitive.","contentHash":"f539b85646adb15d17f60d7a5b49d0cddcf1a4e9fb3f366d650c543593c1e82d","addressRefs":[]},"5c3f4cab-ed95-4ac9-a717-c67b4a6754f8":{"id":"5c3f4cab-ed95-4ac9-a717-c67b4a6754f8","doc_no":"A.6.1.1.2.2.5.3.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5653,"content":"The documents herein contain data relevant to the Single Instance of the Pioneer Chain Primitive.","contentHash":"3ef47abf54c7d77c73253d1a8cea48175bafcf137874a62a4f54a6efa32c7d9b","addressRefs":[]},"ad66bcf7-bd92-4c71-be17-89310e6d0a83":{"id":"ad66bcf7-bd92-4c71-be17-89310e6d0a83","doc_no":"A.6.1.1.2.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5654,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"3299b4ea-60e5-4f46-9c4a-24c5da64a5fc":{"id":"3299b4ea-60e5-4f46-9c4a-24c5da64a5fc","doc_no":"A.6.1.1.2.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5655,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.5.3.2 - Active Instances](33a1baf4-9922-40a1-b121-558f620da186).","contentHash":"03284b5a4f62e77e6eddf589fb776cf2ca780b44af803581aab7ab38da280a83","addressRefs":[]},"fb59210b-5a2f-4be4-a4bb-5a908d9850e7":{"id":"fb59210b-5a2f-4be4-a4bb-5a908d9850e7","doc_no":"A.6.1.1.2.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5656,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Grove. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"ae45f71e5578ccca530f42b1d262ec15cda230e3dc71271462729a9516299a26","addressRefs":[]},"fecdf649-666c-4196-a046-b2eaf76574d3":{"id":"fecdf649-666c-4196-a046-b2eaf76574d3","doc_no":"A.6.1.1.2.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5657,"content":"The documents herein contain all data and specifications for Grove’s Allocation System Primitive Instances.","contentHash":"6399fa0c5401bb353af0392521b91205c9a8ebafbcdf14223b278e36a8f9151a","addressRefs":[]},"408b026b-09d3-4154-8fc2-e7270b76a053":{"id":"408b026b-09d3-4154-8fc2-e7270b76a053","doc_no":"A.6.1.1.2.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5658,"content":"The documents herein organize all base information relevant to Grove’s usage of the Grove Liquidity Layer.","contentHash":"6bb7c31912ec34c6708d9bfe9453be83b50d6aeeb28590e393fecc5d989ffd49","addressRefs":[]},"0ac08ba4-1b98-4d83-8abd-3efdcf966dcc":{"id":"0ac08ba4-1b98-4d83-8abd-3efdcf966dcc","doc_no":"A.6.1.1.2.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5659,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"1edfe612-6f19-4aa7-b0f9-1b3a2aae8a47":{"id":"1edfe612-6f19-4aa7-b0f9-1b3a2aae8a47","doc_no":"A.6.1.1.2.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5660,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"e6fe9576-9677-4bed-b779-cd2a52e4fdc0":{"id":"e6fe9576-9677-4bed-b779-cd2a52e4fdc0","doc_no":"A.6.1.1.2.2.6.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5661,"content":"The documents herein contain a Directory of all Instances on the Ethereum Mainnet of the Allocation System Primitive with Instance status of `Active`.","contentHash":"886bcf6fa542b5a20f09fe633a92b366fc593e9f17a10e8d06664ee1c2c5ec4a","addressRefs":[]},"2f175df9-3b8c-4c2c-a700-52f741abf501":{"id":"2f175df9-3b8c-4c2c-a700-52f741abf501","doc_no":"A.6.1.1.2.2.6.1.1.2.1.1","title":"Centrifuge","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5662,"content":"The Ethereum Mainnet Instances Directory of the Centrifuge Protocol with `Active` Status are stored herein.","contentHash":"887c9ec0f8872444c7e3ad6c6f7821985aeee4ca03d9289d4cd91897d3d80834","addressRefs":[]},"69e59a73-e7c8-4277-a804-0cc945497241":{"id":"69e59a73-e7c8-4277-a804-0cc945497241","doc_no":"A.6.1.1.2.2.6.1.1.2.1.1.1","title":"Ethereum Mainnet - Centrifuge JTRSY Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5663,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.1.1 - Ethereum Mainnet - Centrifuge JTRSY Instance Configuration Document](292d1098-9fe4-481f-a3e7-72e345bdca81).","contentHash":"916a750cdac8cf92f6adf43458cb9c05721fc067bb42d5b1900ac4826982757b","addressRefs":[]},"d1c474c6-9071-4110-90d6-36d81e73e98e":{"id":"d1c474c6-9071-4110-90d6-36d81e73e98e","doc_no":"A.6.1.1.2.2.6.1.1.2.1.1.2","title":"Ethereum Mainnet - Centrifuge JAAA Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5664,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.1.2 - Ethereum Mainnet - Centrifuge JAAA Instance Configuration Document](10f4641c-2ed1-4430-ae71-1e830e779269).","contentHash":"023a25f003b6eb98ce313b41d86f2fddaf53e9b98880a35a7388b1faf5454c6a","addressRefs":[]},"7db7e977-cf6d-4186-b20c-43715314cb2c":{"id":"7db7e977-cf6d-4186-b20c-43715314cb2c","doc_no":"A.6.1.1.2.2.6.1.1.2.1.1.3","title":"Ethereum Mainnet - Centrifuge ACRDX Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5665,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.1.3 - Ethereum Mainnet - Centrifuge ACRDX Instance Configuration Document](b0d889d1-8465-4229-ba69-ca4b5d866131).","contentHash":"e7b3ad51e20c9895858c5e3ae88aafeff8c6044c2744adff6107e8b17995a882","addressRefs":[]},"e50bfc41-5c93-4e29-87ef-dd1b0af9140c":{"id":"e50bfc41-5c93-4e29-87ef-dd1b0af9140c","doc_no":"A.6.1.1.2.2.6.1.1.2.1.1.4","title":"Ethereum Mainnet - Centrifuge JTRSY USDS Vault Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5666,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.1.4 - Ethereum Mainnet - Centrifuge JTRSY USDS Vault Instance Configuration Document](acbe1bed-7639-45a4-9a5d-73c7d434bd0a).","contentHash":"8f19fac3ca5167d52efc897a3ddf50982be1d5594b60cf725f518e5a2f49fa87","addressRefs":[]},"f1de44d8-9dc4-4513-ac06-295d5ccc427d":{"id":"f1de44d8-9dc4-4513-ac06-295d5ccc427d","doc_no":"A.6.1.1.2.2.6.1.1.2.1.2","title":"Blackrock","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5667,"content":"The Ethereum Mainnet Instances Directory of the Blackrock Protocol with `Active` Status are stored herein.","contentHash":"294d1d4dbdbac2023ec0a5abc1d22b39e2a3389da2179a787b4b55e6479f709d","addressRefs":[]},"44299e83-18ec-4bdd-990c-2f61f3d11276":{"id":"44299e83-18ec-4bdd-990c-2f61f3d11276","doc_no":"A.6.1.1.2.2.6.1.1.2.1.2.1","title":"Ethereum Mainnet - Blackrock BUIDL-I Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5668,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.2.1 - Ethereum Mainnet - Blackrock BUIDL-I Instance Configuration Document](8bc44388-0d97-4d5e-aa33-fdd1938f03ff).","contentHash":"93d4f8305ebe90e11ff60adb981d6aa8d95cd50aba1b86816cd13ee63d61b38e","addressRefs":[]},"a54ef112-49c1-456b-bee9-720b5683440c":{"id":"a54ef112-49c1-456b-bee9-720b5683440c","doc_no":"A.6.1.1.2.2.6.1.1.2.1.3","title":"Superstate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5669,"content":"The Ethereum Mainnet Instances Directory of the Superstate Protocol with `Active` Status are stored herein.","contentHash":"4df0121f1ea57d4f4b7f6e9b6f4c4775a8d8fd118866d84397b8912c1468c4b9","addressRefs":[]},"59096f55-3b2c-432c-bea1-e48f2277dec8":{"id":"59096f55-3b2c-432c-bea1-e48f2277dec8","doc_no":"A.6.1.1.2.2.6.1.1.2.1.3.1","title":"Ethereum Mainnet - Superstate USTB Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5670,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.3.1 - Ethereum Mainnet - Superstate USTB Instance Configuration Document](a49f5e48-6e00-434b-bd85-26539c7a9cfe).","contentHash":"58c64465b55c24f655a1fb30f52cb6c41cab92d578c004acaba4cd4f4d656af7","addressRefs":[]},"df36f5df-f45e-49a3-a6ee-508d1970740c":{"id":"df36f5df-f45e-49a3-a6ee-508d1970740c","doc_no":"A.6.1.1.2.2.6.1.1.2.1.4","title":"Ethena","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5671,"content":"The Ethereum Mainnet Instances Directory of the Ethena Protocol with `Active` Status are stored herein.","contentHash":"b0fd85f1061c67de4e42dd0262f4195e686077c304093d2e2eb077ff127143f8","addressRefs":[]},"0f7c80ec-f26a-4952-991c-c92cd9b902c1":{"id":"0f7c80ec-f26a-4952-991c-c92cd9b902c1","doc_no":"A.6.1.1.2.2.6.1.1.2.1.4.1","title":"Ethereum Mainnet - Ethena USDe Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5672,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.4.1 - Ethereum Mainnet - Ethena USDe Instance Configuration Document](dbe15588-fa00-4573-ae8a-f69e095532f5).","contentHash":"6360b534ffffd3b2d5195249e246c53a3b571668d12ea4a5a315e0cb2c557f45","addressRefs":[]},"bac8cfff-f26f-4cc2-aac4-a5ac7232e99c":{"id":"bac8cfff-f26f-4cc2-aac4-a5ac7232e99c","doc_no":"A.6.1.1.2.2.6.1.1.2.1.4.2","title":"Ethereum Mainnet - Ethena sUSDe Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5673,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.4.2 - Ethereum Mainnet - Ethena sUSDe Instance Configuration Document](5847fff3-ff82-4c01-ac24-7f06fac8c2a4).","contentHash":"f05488521df8cf1305e6400f0b745df61cc43546c6c2442182d30408fa03cfcb","addressRefs":[]},"39fdf5a1-92e9-40de-a1f4-23732d6bbb1a":{"id":"39fdf5a1-92e9-40de-a1f4-23732d6bbb1a","doc_no":"A.6.1.1.2.2.6.1.1.2.1.4.3","title":"Ethereum Mainnet - Ethena PT-USDe Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5674,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.4.3 - Ethereum Mainnet - Ethena PT-USDe Instance Configuration Document](e3f9abf3-0cd0-46cc-8295-175c1bc8afbd).","contentHash":"007ca0e86f7c8fec2f1bb919db1ebeba8ce80dcd1681de5c4113bacfd96ba097","addressRefs":[]},"46eb0e66-2594-4bb6-8e2b-0651a6ce39c8":{"id":"46eb0e66-2594-4bb6-8e2b-0651a6ce39c8","doc_no":"A.6.1.1.2.2.6.1.1.2.1.4.4","title":"Ethereum Mainnet - Ethena PT-sUSDe Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5675,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.4.4 - Ethereum Mainnet - Ethena PT-sUSDe Instance Configuration Document](ba45e20f-b6df-4836-94ea-b4f2f062e658).","contentHash":"426b3f87139193511b4aa56b60cbe943b828fcc826389118ae5b99f7ca90c8b2","addressRefs":[]},"23bbcb38-c473-4ccf-83c5-59fe292bb13c":{"id":"23bbcb38-c473-4ccf-83c5-59fe292bb13c","doc_no":"A.6.1.1.2.2.6.1.1.2.1.5","title":"Aave","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5676,"content":"The Ethereum Mainnet Instances Directory of the Aave Protocol with `Active` Status are stored herein.","contentHash":"b2ae795e6fd7562128444dde233fcdbc8a91447b067dd41d7d29e277e79228eb","addressRefs":[]},"7115f3e1-549f-458b-990a-756b679ce2b0":{"id":"7115f3e1-549f-458b-990a-756b679ce2b0","doc_no":"A.6.1.1.2.2.6.1.1.2.1.5.1","title":"Ethereum Mainnet - Aave Core v3 USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5677,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.5.1 - Ethereum Mainnet - Aave Core v3 USDC Instance Configuration Document](7f4eb111-6751-4308-88ce-efe2445e5455).","contentHash":"a2cc61161ef50c89cf8238519be1bbd887f65a38668305a31360ee4836964d17","addressRefs":[]},"6149518b-ccd9-48ad-85f2-3a57c8d2bb6d":{"id":"6149518b-ccd9-48ad-85f2-3a57c8d2bb6d","doc_no":"A.6.1.1.2.2.6.1.1.2.1.5.2","title":"Ethereum Mainnet - Aave Core v3 RLUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5678,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.5.2 - Ethereum Mainnet - Aave Core v3 RLUSD Instance Configuration Document](6b5a19f9-7810-4066-b2ca-df7eff376971).","contentHash":"6048722a1ae883fc1b12b3f525e9ab1dd13f81092598aed288b0537c4905452c","addressRefs":[]},"f7cb82e7-bb79-4e0a-9c92-652f8d24fcad":{"id":"f7cb82e7-bb79-4e0a-9c92-652f8d24fcad","doc_no":"A.6.1.1.2.2.6.1.1.2.1.5.3","title":"Ethereum Mainnet - Aave Horizon USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5679,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.5.3 - Ethereum Mainnet - Aave Horizon USDC Instance Configuration Document](3050edfd-dd88-4fa4-91b4-4870d4fed089).","contentHash":"0dd321c6fb391471db21bc8a3e4bc32ae964bc6341e5ddb22e42bebec070bca2","addressRefs":[]},"dbe0fa43-026b-467f-8108-879f4fe94e3b":{"id":"dbe0fa43-026b-467f-8108-879f4fe94e3b","doc_no":"A.6.1.1.2.2.6.1.1.2.1.5.4","title":"Ethereum Mainnet - Aave Horizon RLUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5680,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.5.4 - Ethereum Mainnet - Aave Horizon RLUSD Instance Configuration Document](15200deb-9894-4f54-95b6-7bab90a6f395).","contentHash":"504c4213819a70831e83382efee6db1006d92b528f832e9cf6a4285f93408829","addressRefs":[]},"74f2556f-fb78-45f3-95d7-f360b9982d09":{"id":"74f2556f-fb78-45f3-95d7-f360b9982d09","doc_no":"A.6.1.1.2.2.6.1.1.2.1.6","title":"Curve","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5681,"content":"The Ethereum Mainnet Instances Directory of the Curve Protocol with `Active` Status are stored herein.","contentHash":"e1a668176ab5e2b5a4874a9df8fbf4531edc87b29365354a999aaf4b76113b09","addressRefs":[]},"654eac37-dbe6-4bf1-a300-e04645c0652a":{"id":"654eac37-dbe6-4bf1-a300-e04645c0652a","doc_no":"A.6.1.1.2.2.6.1.1.2.1.6.1","title":"Ethereum Mainnet - Curve RLUSD/USDC Pool Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5682,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.6.1 - Ethereum Mainnet - Curve RLUSD/USDC Pool Instance Configuration Document](67b85f8a-3857-461d-a214-d3bf990f9111).","contentHash":"83b7b53b3aba8efba76b0d4f96ed4dd61a6db4ba38f0a8876e6409b55dac3439","addressRefs":[]},"e09057c5-3a44-4e92-a38c-5695a6ad08d9":{"id":"e09057c5-3a44-4e92-a38c-5695a6ad08d9","doc_no":"A.6.1.1.2.2.6.1.1.2.1.6.2","title":"Ethereum Mainnet - Curve RLUSD/USDC Pool LP Deposits Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5683,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.6.3 - Ethereum Mainnet - Curve RLUSD/USDC Pool LP Deposits Instance Configuration Document](ea9afb08-8f81-4ee9-b9a7-321862bad5d8).","contentHash":"e4b9109571843ad7293982e7f0dece4c1181869f1f6f8b5a5af56fb29ac2cdc3","addressRefs":[]},"b46fedbe-4c43-4924-970f-703e8e6d3876":{"id":"b46fedbe-4c43-4924-970f-703e8e6d3876","doc_no":"A.6.1.1.2.2.6.1.1.2.1.6.3","title":"Ethereum Mainnet - Curve AUSD/USDC Swaps Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5684,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.6.4 - Ethereum Mainnet - Curve AUSD/USDC Swaps Instance Configuration Document](207cc62c-29ee-4a03-afd9-37f279b2c25b).","contentHash":"69c6e45fb64836d212fea8403b612dd5111125744e459c46136c1dba257a436b","addressRefs":[]},"ad345081-935c-4fce-ba70-69992bc908c5":{"id":"ad345081-935c-4fce-ba70-69992bc908c5","doc_no":"A.6.1.1.2.2.6.1.1.2.1.6.4","title":"Ethereum Mainnet - Curve AUSD/USDC LP Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5685,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.6.5 - Ethereum Mainnet - Curve AUSD/USDC LP Instance Configuration Document](6d7f468e-e32c-4077-8dbc-66095e7b8f84).","contentHash":"a3e9aca086ac7e390d6b3ebe7e289cbc14b243636bd64ecdc7a34de3d891c01f","addressRefs":[]},"afeb8a74-9f57-4729-ba91-f87a63eaa6e5":{"id":"afeb8a74-9f57-4729-ba91-f87a63eaa6e5","doc_no":"A.6.1.1.2.2.6.1.1.2.1.6.5","title":"Ethereum Mainnet - Curve PYUSD/USDS Swaps Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5686,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.6.6 - Ethereum Mainnet - Curve PYUSD/USDS Swaps Instance Configuration Document](f168c4a8-f526-471e-8410-4f3f339e99d5).","contentHash":"a6e24bca2c1ec04f62f135e8b19f03141f1871a2648634f0f8298debf7e058dc","addressRefs":[]},"c7201d8e-ea9a-4283-ad53-8f1851bde413":{"id":"c7201d8e-ea9a-4283-ad53-8f1851bde413","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7","title":"Morpho","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5687,"content":"The Ethereum Mainnet Instances Directory of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"416cd4540aa798f84e3260980cd196fcbc9fcc59fb1cde760d6f95c03ba7fcc1","addressRefs":[]},"03708e1d-f0e9-41e6-a792-01ef1b2d969b":{"id":"03708e1d-f0e9-41e6-a792-01ef1b2d969b","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.1","title":"Ethereum Mainnet - Morpho Grove x Steakhouse High Yield Vault USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5688,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.1 - Ethereum Mainnet - Morpho Grove x Steakhouse High Yield Vault USDC Instance Configuration Document](29cb8322-96f5-4f18-b4fe-eb31826af580).","contentHash":"627ff1be5d44d1e8ebf3d62d1ac0d90f83334154b5a20e57c087872797fd8bd2","addressRefs":[]},"b75109cc-9cce-4831-ac8a-995d7d145383":{"id":"b75109cc-9cce-4831-ac8a-995d7d145383","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.2","title":"Ethereum Mainnet - Monad Morpho Grove x Steakhouse High Yield Vault AUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5689,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.2 - Ethereum Mainnet - Monad Morpho Grove x Steakhouse High Yield Vault AUSD Instance Configuration Document](27f06e65-8397-449a-b002-abaa0416badc).","contentHash":"4ba70ffdb5e70ba8c1643d8e91536ab4db9e8e2f733f4f21117144325abd8c43","addressRefs":[]},"c0daf824-060e-449e-be48-f86efd1447e2":{"id":"c0daf824-060e-449e-be48-f86efd1447e2","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.3","title":"Ethereum Mainnet - Grove x Steakhouse USDC Morpho Vault v2 Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5690,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.3 - Ethereum Mainnet - Grove x Steakhouse USDC Morpho Vault v2 Instance Configuration Document](6ec606f0-bc47-4f36-8591-75784bb78b00).","contentHash":"86ab2ac1a29a31df345eb693c3c10c57ee528c7fac41973dcec98f3f0e2b209c","addressRefs":[]},"d0a21cdb-ba69-4f0c-9b67-575996a01c4d":{"id":"d0a21cdb-ba69-4f0c-9b67-575996a01c4d","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.4","title":"Ethereum Mainnet - Steakhouse PYUSD Morpho Vault Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5691,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.4 - Ethereum Mainnet - Steakhouse PYUSD Morpho Vault Instance Configuration Document](0b7e1d3d-1f56-48a6-9729-88479aa5ff92).","contentHash":"1db75b47bbb1fe5ae0e245a57f7c044cc976c8ea5571fb6edfdb99ee0aea3eb3","addressRefs":[]},"1281f13b-4435-46c5-9e8a-b602aac42c7a":{"id":"1281f13b-4435-46c5-9e8a-b602aac42c7a","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.5","title":"Ethereum Mainnet - Grove x Steakhouse AUSD Morpho Vault V2 Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5692,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.5 - Ethereum Mainnet - Grove x Steakhouse AUSD Morpho Vault V2 Instance Configuration Document](2c21462b-2925-48d8-9578-5fc21aa96563).","contentHash":"8f25d853adc6664929e75f6c61b641d8fdbfc906cf4c4680c56a797fe203fed3","addressRefs":[]},"db6ff295-bf78-450f-a272-f4a5f01b0cdc":{"id":"db6ff295-bf78-450f-a272-f4a5f01b0cdc","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.6","title":"Ethereum Mainnet - Sentora PYUSD Morpho Vault V2 Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5693,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.6 - Ethereum Mainnet - Sentora PYUSD Morpho Vault V2 Instance Configuration Document](3e940e02-80eb-4e37-bce6-95939089da46).","contentHash":"2b02032b0af3297c017a9caad68809db51f76da870ddc49e42b17a37667af813","addressRefs":[]},"329dae6d-08a0-4628-b494-b533e69c26ce":{"id":"329dae6d-08a0-4628-b494-b533e69c26ce","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.7","title":"Ethereum Mainnet - Sentora RLUSD Morpho Vault V2 Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5694,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.7 - Ethereum Mainnet - Sentora RLUSD Morpho Vault V2 Instance Configuration Document](dff6df5f-f8ab-4df1-be1e-f71510c3534e).","contentHash":"3e9b065cddcaadcd5372e0490534e86dab88fa85cff124a825fe7ef35c79dc7e","addressRefs":[]},"d6cab49c-2cfd-4f70-a101-fbdb294c16db":{"id":"d6cab49c-2cfd-4f70-a101-fbdb294c16db","doc_no":"A.6.1.1.2.2.6.1.1.2.1.7.8","title":"Ethereum Mainnet - Grove x Steakhouse RLUSD Morpho Vault V2 Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5695,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.7.8 - Ethereum Mainnet - Grove x Steakhouse RLUSD Morpho Vault V2 Instance Configuration Document](cfb29474-ea48-4370-aad6-23af1cf4d11a).","contentHash":"780122c69225fd104b1893f08f4d823ce6c6f410736aed2b429d16083d9480dd","addressRefs":[]},"12a0d375-8f1e-4e62-83ba-d56bc6d3f2ab":{"id":"12a0d375-8f1e-4e62-83ba-d56bc6d3f2ab","doc_no":"A.6.1.1.2.2.6.1.1.2.1.8","title":"Securitize","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5696,"content":"The Ethereum Mainnet Instances Directory of the Securitize Protocol with `Active` Status are stored herein.","contentHash":"a79d085b8dc26fb81b1f39d9eb7cfd9f3d75b6d6b6a9cc74442dd4bd4493d6b6","addressRefs":[]},"f43479d2-2c76-4a18-8e9b-f59f1e1b493b":{"id":"f43479d2-2c76-4a18-8e9b-f59f1e1b493b","doc_no":"A.6.1.1.2.2.6.1.1.2.1.8.1","title":"Ethereum Mainnet - Securitize Tokenized AAA CLO Fund (STAC) Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5697,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.8.1 - Ethereum Mainnet - Securitize Tokenized AAA CLO Fund (STAC) Instance Configuration Document](a0c4fcd6-ebf9-4124-8767-cf14ab6ab397).","contentHash":"f2aa94af9c778b28309c7045e8a45014fd4b3041af726746ae8a52e53982383a","addressRefs":[]},"040d21e6-c423-45b6-81c0-fc05c1e45bae":{"id":"040d21e6-c423-45b6-81c0-fc05c1e45bae","doc_no":"A.6.1.1.2.2.6.1.1.2.1.9","title":"Galaxy","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5698,"content":"The Ethereum Mainnet Instances Directory of the Galaxy Protocol with `Active` Status are stored herein.","contentHash":"47c04a9ec925fc3a0f769b4109034527c4ff61d30698ae65a42eef2f08d000c2","addressRefs":[]},"af6212d3-fc1a-4c34-9352-ea18f8a2a294":{"id":"af6212d3-fc1a-4c34-9352-ea18f8a2a294","doc_no":"A.6.1.1.2.2.6.1.1.2.1.9.1","title":"Ethereum Mainnet - Galaxy Arch CLOs Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5699,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.9.1 - Ethereum Mainnet - Galaxy Arch CLOs Instance Configuration Document](61afae62-1210-4d80-aa6c-cdb26ef0a287).","contentHash":"6f623b4fb335079e5006036fe25c07dd0626c10e71920d3d7d3521c855e8661d","addressRefs":[]},"ad3557aa-ec4e-4cc5-8673-f3aa5818a288":{"id":"ad3557aa-ec4e-4cc5-8673-f3aa5818a288","doc_no":"A.6.1.1.2.2.6.1.1.2.1.9.2","title":"Ethereum Mainnet - Galaxy Warehouse Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5700,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.9.2 - Ethereum Mainnet - Galaxy Warehouse Instance Configuration Document](2e3e057e-0b48-4e3f-b03d-1ed84299ccfc).","contentHash":"68c1dcdddb5703c64ac2c76f2876a5d7f85e70c76fd1a18c7b7a3a0cfd158230","addressRefs":[]},"39843e09-154a-497a-8824-54393ea15915":{"id":"39843e09-154a-497a-8824-54393ea15915","doc_no":"A.6.1.1.2.2.6.1.1.2.1.10","title":"Ripple","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5701,"content":"The Ethereum Mainnet Instances Directory of the Ripple Protocol with `Active` Status are stored herein.","contentHash":"8aac8c079447778209b530d3ac458f3621b419b7b502d3eeab3af1e644d73011","addressRefs":[]},"6bf29031-456e-4f6e-bb43-1ceb4a2eb11e":{"id":"6bf29031-456e-4f6e-bb43-1ceb4a2eb11e","doc_no":"A.6.1.1.2.2.6.1.1.2.1.10.1","title":"Ethereum Mainnet - Ripple RLUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5702,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.10.1 - Ethereum Mainnet - Ripple RLUSD Instance Configuration Document](2e28c162-c608-452c-b796-4654ac1139d8).","contentHash":"c5b3f243fa11b90859045552a01df5202eaf2ae259db59cfce2d10dd934e1b3a","addressRefs":[]},"2417db38-50a7-4394-9cfb-7afcf01e8c85":{"id":"2417db38-50a7-4394-9cfb-7afcf01e8c85","doc_no":"A.6.1.1.2.2.6.1.1.2.1.11","title":"Agora","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5703,"content":"The Ethereum Mainnet Instances Directory of the Agora Protocol with `Active` Status are stored herein.","contentHash":"5583d3e60259c1899a35b3d190ede0e10b49b4e20c2319da4c7831124d8559e8","addressRefs":[]},"ec9d4393-2e68-40a7-b428-efc0452e35d8":{"id":"ec9d4393-2e68-40a7-b428-efc0452e35d8","doc_no":"A.6.1.1.2.2.6.1.1.2.1.11.1","title":"Ethereum Mainnet - Agora AUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5704,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.11.1 - Ethereum Mainnet - Agora AUSD Instance Configuration Document](0d71b879-0dd7-4c37-9a42-f16d868c4482).","contentHash":"37432665d23995c6f6154a86e3f7ebde7fd0b1d7d739dc80862e61b401e8a155","addressRefs":[]},"6285def0-e537-4d18-9776-7534196576e6":{"id":"6285def0-e537-4d18-9776-7534196576e6","doc_no":"A.6.1.1.2.2.6.1.1.2.1.12","title":"Uniswap","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5705,"content":"The Ethereum Mainnet Instances Directory of the Uniswap Protocol with `Active` Status are stored herein.","contentHash":"7d557aba567d865f3d0d1c8c73c8f812cd1b2e5a34026209dd3cdc1ff25c5de1","addressRefs":[]},"e033416b-635b-42c0-9757-4797614d6f7f":{"id":"e033416b-635b-42c0-9757-4797614d6f7f","doc_no":"A.6.1.1.2.2.6.1.1.2.1.12.1","title":"Ethereum Mainnet - Monad Uniswap AUSD/USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5706,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.12.1 - Ethereum Mainnet - Monad Uniswap AUSD/USDC Instance Configuration Document](c4d60460-2694-4d88-bf96-4f4141482cb5).","contentHash":"9fb57f21d3fb79daa89cf4f78c7b0228d07134fa549f1ae68690e249ae18f765","addressRefs":[]},"6fcc9608-b482-4d67-872f-828c0dad3a89":{"id":"6fcc9608-b482-4d67-872f-828c0dad3a89","doc_no":"A.6.1.1.2.2.6.1.1.2.1.12.2","title":"Ethereum Mainnet - Uniswap v3 AUSD/USDC Swaps Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5707,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.12.2 - Ethereum Mainnet - Uniswap v3 AUSD/USDC Swaps Instance Configuration Document](ffa0ca69-c416-4163-a1c6-b863f5d38c3f).","contentHash":"9e7e48dddf66997d3c175a69d42b0db695818674040d7a72a1f9853802387eeb","addressRefs":[]},"d8c0e975-1902-4fcf-b228-c3e75d3b6dee":{"id":"d8c0e975-1902-4fcf-b228-c3e75d3b6dee","doc_no":"A.6.1.1.2.2.6.1.1.2.1.12.3","title":"Ethereum Mainnet - Uniswap v3 AUSD/USDC LP Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5708,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.12.3 - Ethereum Mainnet - Uniswap v3 AUSD/USDC LP Instance Configuration Document](cca4236a-47f9-4b4f-81ef-c31a5ee624aa).","contentHash":"8c852514a5803fa15c3919ad3e08ceb62bbf5d434cbd900db568b3b039e70931","addressRefs":[]},"3fb5412d-23fd-4b1e-bddb-6e684e954050":{"id":"3fb5412d-23fd-4b1e-bddb-6e684e954050","doc_no":"A.6.1.1.2.2.6.1.1.2.1.13","title":"Maple","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5709,"content":"The Ethereum Mainnet Instances Directory of the Maple Protocol with `Active` Status are stored herein.","contentHash":"23d31010d23f63ecd6441f2d5871677626acdbf4cc73a664c3cb7e7130524d34","addressRefs":[]},"20b30bc3-c3e8-4098-bdf2-ca288e8bee1a":{"id":"20b30bc3-c3e8-4098-bdf2-ca288e8bee1a","doc_no":"A.6.1.1.2.2.6.1.1.2.1.13.1","title":"Ethereum Mainnet - Maple syrupUSDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5710,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.13.1 - Ethereum Mainnet - Maple syrupUSDC Instance Configuration Document](7502f64c-3276-478e-8f98-53a2377ca1a2).","contentHash":"60954a0c93d757d6f75d32e6628d17a1858f6caa135ea05ec586491da662b841","addressRefs":[]},"53a37417-5900-4b8d-a750-339782c838cb":{"id":"53a37417-5900-4b8d-a750-339782c838cb","doc_no":"A.6.1.1.2.2.6.1.1.2.1.14","title":"Tokenized Treasury","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5711,"content":"The Ethereum Mainnet Tokenized Treasury Instances Directory with `Active` Status are stored herein.","contentHash":"15be38b6b8324d1a39757e81e4842aa5196af769c29ccbcae1f276d439485d8d","addressRefs":[]},"e6582be2-cb08-4788-a011-32e3509a42e5":{"id":"e6582be2-cb08-4788-a011-32e3509a42e5","doc_no":"A.6.1.1.2.2.6.1.1.2.1.14.1","title":"Ethereum Mainnet - Tokenized Treasury JTRSY Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5712,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.1.14.1 - Ethereum Mainnet - Tokenized Treasury JTRSY Instance Configuration Document](5e38198e-1577-4ab0-900a-91b6d8284387).","contentHash":"6dc7c3dc74689036b8c2c25dc2f6243699eca7fd92f49f8705cc0fb701956b3f","addressRefs":[]},"7f10aaf2-b3e8-4dc8-b91f-ff27200a9ccf":{"id":"7f10aaf2-b3e8-4dc8-b91f-ff27200a9ccf","doc_no":"A.6.1.1.2.2.6.1.1.2.2","title":"Avalanche","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5713,"content":"The documents herein contain a Directory of all Instances on Avalanche of the Allocation System Primitive with Instance status of `Active`.","contentHash":"7068bc1569c6240c570089a214f3cc3ce5cb384415ba56112ccc77ee89e09198","addressRefs":[]},"bc3f2a84-6f20-448a-9f2a-9173cfe65204":{"id":"bc3f2a84-6f20-448a-9f2a-9173cfe65204","doc_no":"A.6.1.1.2.2.6.1.1.2.2.1","title":"Centrifuge","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5714,"content":"The Avalanche Instances Directory of the Centrifuge Protocol with `Active` Status are stored herein.","contentHash":"549bcb58b9c9f00905d8f25dccfb51d913c7a3b7f3f5e66379f7e510e95a70e2","addressRefs":[]},"af1d1da5-f77a-4d0e-9fa8-0fef4851eafc":{"id":"af1d1da5-f77a-4d0e-9fa8-0fef4851eafc","doc_no":"A.6.1.1.2.2.6.1.1.2.2.1.1","title":"Avalanche - Centrifuge JTRSY Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5715,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.2.1.1 - Avalanche - Centrifuge JTRSY Instance Configuration Document](3c731296-858a-4c27-a5cc-6b7ff208cc16).","contentHash":"4fba0a5a7a9261ef2a5b49c8511810a56949b849a4673e4a3db0c4f46f51e04a","addressRefs":[]},"975aa703-54ac-4593-a027-7cff0b5e25be":{"id":"975aa703-54ac-4593-a027-7cff0b5e25be","doc_no":"A.6.1.1.2.2.6.1.1.2.2.1.2","title":"Avalanche - Centrifuge JAAA Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5716,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.2.1.2 - Avalanche - Centrifuge JAAA Instance Configuration Document](bd37d6c9-2e05-4ce3-86dc-3a50d6887e6b).","contentHash":"2311996adbc24fafd678fe831d547b9ef0d3d2ed03206775827b1436c9ed8e5f","addressRefs":[]},"aad65f08-6a6f-4246-a356-ba74b83e142c":{"id":"aad65f08-6a6f-4246-a356-ba74b83e142c","doc_no":"A.6.1.1.2.2.6.1.1.2.2.2","title":"Curve","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5717,"content":"The Avalanche Instances Directory of the Curve Protocol with `Active` Status are stored herein.","contentHash":"29f05a5769ded13eaae9822b0ff335e01c6fcf7ec42596b82cc51c509d9c69a1","addressRefs":[]},"b92c6d2f-1b11-42e6-aa63-5a67c40dd487":{"id":"b92c6d2f-1b11-42e6-aa63-5a67c40dd487","doc_no":"A.6.1.1.2.2.6.1.1.2.2.2.1","title":"Avalanche - Curve USDS/USDC Swaps Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5718,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.2.2.1 - Avalanche - Curve USDS/USDC Swaps Instance Configuration Document](241a6ad1-ac18-496c-84f8-e2624497c7d9).","contentHash":"74ce9eb04134b1881f2282d9ab2f76feab27c82c82d1928fc5decc172c23fa34","addressRefs":[]},"2c8a48e0-00c4-41f7-a59a-a7ffc966a6db":{"id":"2c8a48e0-00c4-41f7-a59a-a7ffc966a6db","doc_no":"A.6.1.1.2.2.6.1.1.2.2.2.2","title":"Avalanche - Curve USDS/USDC LP Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5719,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.2.2.2 - Avalanche - Curve USDS/USDC LP Instance Configuration Document](72325c96-455c-4c19-aefc-541206494bd3).","contentHash":"8df401e64940412f893685b97b090b75576e8f78828760f95e547c7aae67d01a","addressRefs":[]},"a53e977f-7bc9-406e-9be1-1f52d9c51416":{"id":"a53e977f-7bc9-406e-9be1-1f52d9c51416","doc_no":"A.6.1.1.2.2.6.1.1.2.3","title":"Base","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5720,"content":"The documents herein contain a Directory of all Instances on Base of the Allocation System Primitive with Instance status of `Active`.","contentHash":"363e1e58ddee16c81293bb03988fcc80ea62b287ebe038b93144629bbd81d2c5","addressRefs":[]},"4953ca03-359c-46a0-b7f1-3625023492d5":{"id":"4953ca03-359c-46a0-b7f1-3625023492d5","doc_no":"A.6.1.1.2.2.6.1.1.2.3.1","title":"Morpho","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5721,"content":"The Base Instances Directory of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"d86ac0eac7329098e5d8c01763d9e21541ae13693e422c974e667216751d8a27","addressRefs":[]},"be020cd4-73d4-4fc3-ae39-d38b252defd0":{"id":"be020cd4-73d4-4fc3-ae39-d38b252defd0","doc_no":"A.6.1.1.2.2.6.1.1.2.3.1.1","title":"Base - Morpho Grove x Steakhouse High Yield Vault USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5722,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.3.1.1 - Base - Morpho Grove x Steakhouse High Yield Vault USDC Instance Configuration Document](43d78089-ba75-480c-a277-edaa6eaa6336).","contentHash":"b9062bde4217e5ddf2c1aa836526d96a3f6edf94e2afcd58a0b66bc0dff03d72","addressRefs":[]},"363c5d9f-9486-4091-8ed6-f909f66ead65":{"id":"363c5d9f-9486-4091-8ed6-f909f66ead65","doc_no":"A.6.1.1.2.2.6.1.1.2.3.1.2","title":"Base - Steakhouse Prime Instant USDC Morpho Vault V2 Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5723,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.3.2 - Base - Steakhouse Prime Instant USDC Morpho Vault V2 Instance Configuration Document](d47ec9c3-b308-453a-989a-7396504f6a99).","contentHash":"d989a87c63740727e3686346ccb5c0ef57c1dbec261dfb4a808ea81132d962c8","addressRefs":[]},"00ec8ca9-deee-45b2-9acc-f24560ad4a13":{"id":"00ec8ca9-deee-45b2-9acc-f24560ad4a13","doc_no":"A.6.1.1.2.2.6.1.1.2.4","title":"Plasma","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5724,"content":"The documents herein contain a Directory of all Instances on Plasma of the Allocation System Primitive with Instance status of `Active`.","contentHash":"24325cf7c324f2b7aa96e71286128114bc583887c8283cb38a4eb09fb0638509","addressRefs":[]},"8bf1db06-958b-4037-82f4-5b8463eb22a3":{"id":"8bf1db06-958b-4037-82f4-5b8463eb22a3","doc_no":"A.6.1.1.2.2.6.1.1.2.4.1","title":"Aave","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5725,"content":"The Plasma Instances Directory of the Aave Protocol with `Active` Status are stored herein.","contentHash":"ee9c663dbe6a73009f0b719570e2537acdfdb37846e3573ebb0c663fd88a7207","addressRefs":[]},"76b30e0f-543c-43e1-8f8b-2d1145a9cd4e":{"id":"76b30e0f-543c-43e1-8f8b-2d1145a9cd4e","doc_no":"A.6.1.1.2.2.6.1.1.2.4.1.1","title":"Plasma - Aave v3 USDT0 Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5726,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.4.1.1 - Plasma - Aave v3 USDT0 Instance Configuration Document](7a620ce6-c67a-4c15-b7fb-c8b869a28a0f).","contentHash":"bc3602d96e218d1f86d6b3a8d89abf8d8a771ab2c9d8cb810bcdc0282302ad3e","addressRefs":[]},"6caa7e89-332b-4f69-a128-7920ef97c4dd":{"id":"6caa7e89-332b-4f69-a128-7920ef97c4dd","doc_no":"A.6.1.1.2.2.6.1.1.2.5","title":"Plume","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5727,"content":"The documents herein contain a Directory of all Instances on Plume of the Allocation System Primitive with Instance status of `Active`.","contentHash":"26a0b4ebd4eaf7f76f9b76df02ade518a7e46c83f2f17b2afa0db1919828d606","addressRefs":[]},"6f8bcd5a-5fe1-46ad-b308-761822ac8110":{"id":"6f8bcd5a-5fe1-46ad-b308-761822ac8110","doc_no":"A.6.1.1.2.2.6.1.1.2.5.1","title":"Centrifuge","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5728,"content":"The Plume Instances of the Centrifuge Protocol with `Active` Status are stored herein.","contentHash":"785e6c60c14d2002c2e91a3789732d261c5154331c2748ce2855b21bbe6150cc","addressRefs":[]},"71a02530-2732-409f-b45f-486fc3c14387":{"id":"71a02530-2732-409f-b45f-486fc3c14387","doc_no":"A.6.1.1.2.2.6.1.1.2.5.1.1","title":"Plume - Centrifuge ACRDX Instance Configuration Document Location","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5729,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.2.2.6.1.3.5.1.1 - Plume - Centrifuge ACRDX Instance Configuration Document](a1a1fa83-6c86-49fe-9629-d5ce4b24ed8b).","contentHash":"24b66511a8044f96fb88e915e4984096f706fe1b1c36e1a5e4037e904c1358d5","addressRefs":[]},"70ddaca1-07ca-402f-bf3b-cfab52a8f360":{"id":"70ddaca1-07ca-402f-bf3b-cfab52a8f360","doc_no":"A.6.1.1.2.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5730,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"19280fed-ef24-4c95-843a-4abaec1d8bb6":{"id":"19280fed-ef24-4c95-843a-4abaec1d8bb6","doc_no":"A.6.1.1.2.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5731,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.6.1.1.2 - Active Instances Directory](1edfe612-6f19-4aa7-b0f9-1b3a2aae8a47), whereas failed Invocations are Archived in [A.6.1.1.2.2.6.1.1.5 - Hub Data Repository](20dc2ba0-0668-4975-b2d7-4f70af20d11b).","contentHash":"a168118886caa8f6128d9f8f7a7739e3bbcf3a0dbcbaf00b04505e89f41b6184","addressRefs":[]},"20dc2ba0-0668-4975-b2d7-4f70af20d11b":{"id":"20dc2ba0-0668-4975-b2d7-4f70af20d11b","doc_no":"A.6.1.1.2.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5732,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"adac5df0-d7b2-424e-a311-cccd58a65437":{"id":"adac5df0-d7b2-424e-a311-cccd58a65437","doc_no":"A.6.1.1.2.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5733,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"bd47fcfa-249b-4601-8112-39a8d66d57ad":{"id":"bd47fcfa-249b-4601-8112-39a8d66d57ad","doc_no":"A.6.1.1.2.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5734,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"230f8964-47e8-4422-905e-d120a06acab0":{"id":"230f8964-47e8-4422-905e-d120a06acab0","doc_no":"A.6.1.1.2.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5735,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"8dce92af-5b9c-48dd-b40b-d81aa9a0e41b":{"id":"8dce92af-5b9c-48dd-b40b-d81aa9a0e41b","doc_no":"A.6.1.1.2.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5736,"content":"The documents herein provide general specifications of the Grove Liquidity Layer and define Grove’s overarching strategy and operational framework for managing across all Instances.","contentHash":"fb8ea05682447d0d71ddf6bf7746489137c216d3d1264fb367a1d3826678e4c9","addressRefs":[]},"09be2207-cc0f-4456-b0bc-e9bd91462a47":{"id":"09be2207-cc0f-4456-b0bc-e9bd91462a47","doc_no":"A.6.1.1.2.2.6.1.2.1","title":"General Specifications","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5737,"content":"The documents herein contain general specifications for the Grove Liquidity Layer.","contentHash":"b38a1507638943c9a89380ef739586500f4de16e31ee9b544796746a98113833","addressRefs":[]},"8ceb8f78-6c83-4bdb-909f-2dec3875558e":{"id":"8ceb8f78-6c83-4bdb-909f-2dec3875558e","doc_no":"A.6.1.1.2.2.6.1.2.1.1","title":"Grove Liquidity Layer Architecture","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5738,"content":"The documents herein describe the high-level design of the Grove Liquidity Layer, including its key smart contracts and their functionality.","contentHash":"2a4a12c966bbbb77bbcbbddbcae5cced6c4866a172f02a4d002b8d55bae52664","addressRefs":[]},"338ff66d-d755-4364-a066-08d43c88c49c":{"id":"338ff66d-d755-4364-a066-08d43c88c49c","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1","title":"Grove Liquidity Layer Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5739,"content":"The subdocuments herein provide the addresses of the Grove Liquidity Layer’s constituent contracts.","contentHash":"f48c97d6844301bfdcc5b48c4970047f030bd26fb068b2808340ff155158d927","addressRefs":[]},"152e89bc-81a5-4bd9-affe-10d9e3e94fce":{"id":"152e89bc-81a5-4bd9-affe-10d9e3e94fce","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1","title":"Allocator Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5740,"content":"The documents herein contain global key addresses for the Allocator Contracts.","contentHash":"a99119eb26b8e6fbaae81a45fa911afc0af3344a9ea2bbcb90fc7cf9bd94fe9c","addressRefs":[]},"f8956105-115a-4873-abb8-68458cbacfcf":{"id":"f8956105-115a-4873-abb8-68458cbacfcf","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5741,"content":"The documents herein contain the Allocator Contract Addresses on the Ethereum Mainnet.","contentHash":"084c1a1c5fbe0a4abc17b09c0096038edfd2c77bdd298abb5411775b166695ef","addressRefs":[]},"599b6748-597f-4a9a-b35b-6638a2f8785f":{"id":"599b6748-597f-4a9a-b35b-6638a2f8785f","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.1.1","title":"Allocator Buffer Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5742,"content":"The address of the ALLOCATOR_BUFFER contract is: `0x629aD4D779F46B8A1491D3f76f7E97Cb04D8b1Cd`","contentHash":"1b51ed5e1a2f46cc041d4766fb8e6d6290dffd781a1fa4903cccdef7cb780fc9","addressRefs":["0x629ad4d779f46b8a1491d3f76f7e97cb04d8b1cd"]},"49c84e7b-8885-4107-9dd6-05de425c6217":{"id":"49c84e7b-8885-4107-9dd6-05de425c6217","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.1.2","title":"Allocator Oracle Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5743,"content":"The address of the ALLOCATOR_ORACLE contract is: `0xc7B91C401C02B73CBdF424dFaaa60950d5040dB7`","contentHash":"3915a8e9d83e0d12a43a164e763cda42d8b41817675dff88c98314a34152cb8e","addressRefs":["0xc7b91c401c02b73cbdf424dfaaa60950d5040db7"]},"d2fdbf24-f6bf-4f67-8c7c-4619e57411c8":{"id":"d2fdbf24-f6bf-4f67-8c7c-4619e57411c8","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.1.3","title":"Allocator Registry Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5744,"content":"The address of the ALLOCATOR_REGISTRY contract is: `0xCdCFA95343DA7821fdD01dc4d0AeDA958051bB3B`","contentHash":"b7d71c2ecb2f67f2fe2ddf5b5835dec050bd7652285c86dba07b3fb3e96f8275","addressRefs":["0xcdcfa95343da7821fdd01dc4d0aeda958051bb3b"]},"b5ab51c6-e66f-418b-9073-25728227847a":{"id":"b5ab51c6-e66f-418b-9073-25728227847a","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.1.4","title":"Allocator Roles Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5745,"content":"The address of the ALLOCATOR_ROLES contract is: `0x9A865A710399cea85dbD9144b7a09C889e94E803`","contentHash":"458d4bfa62334f282ee18ad433673de3de9a11f7e2c97fd190afc1bef481a49d","addressRefs":["0x9a865a710399cea85dbd9144b7a09c889e94e803"]},"a2060039-8764-412d-a55b-1f705a0612b3":{"id":"a2060039-8764-412d-a55b-1f705a0612b3","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.1.5","title":"Allocator Vault (Bloom-A) Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5746,"content":"The address of the ALLOCATOR_VAULT (ALLOCATOR-BLOOM-A) contract is: `0x26512A41C8406800f21094a7a7A0f980f6e25d43`","contentHash":"82047f9587b72633bc94b36c2c2b1e9eda05cde58a2b1df1583a1dd204e0fbaf","addressRefs":["0x26512a41c8406800f21094a7a7a0f980f6e25d43"]},"366a6ebc-a35d-42a2-ad9b-86932dd3aac4":{"id":"366a6ebc-a35d-42a2-ad9b-86932dd3aac4","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.2","title":"Base","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5747,"content":"The documents herein contain the Allocator Contract Addresses on Base.","contentHash":"9c3494c463abcb0a85340c8beb02bde70f8d74f92deb500f93dba6d8c1815463","addressRefs":[]},"ac9b04d0-cd27-45a8-9008-6799dbdb6038":{"id":"ac9b04d0-cd27-45a8-9008-6799dbdb6038","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.2.1","title":"Grove Executor","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5748,"content":"The address of the Grove executor on Base is: `0x491EDFB0B8b608044e227225C715981a30F3A44E`","contentHash":"693a6948cb46ff2468b1ec94f7fe74032ed9b9a5aaed1bdc17e085d219771c6a","addressRefs":["0x491edfb0b8b608044e227225c715981a30f3a44e"]},"52f4881b-134f-4eb1-bfe2-ae34abee1a72":{"id":"52f4881b-134f-4eb1-bfe2-ae34abee1a72","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.2.2","title":"Grove Receiver","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5749,"content":"The address of the Grove receiver on Base is: `0x5F5cfCB8a463868E37Ab27B5eFF3ba02112dF19a`","contentHash":"e0af531fdae2119d25135d0b2c3b6af542f375e7640925cb4e98e2d98aa7a0f9","addressRefs":["0x5f5cfcb8a463868e37ab27b5eff3ba02112df19a"]},"5fa11eb9-4399-4ac0-a6c0-ef03a5875254":{"id":"5fa11eb9-4399-4ac0-a6c0-ef03a5875254","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.2.3","title":"Circle CCTP v2 Mainnet To Base","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5750,"content":"The contract address of the Circle CCTP v2 Mainnet to Base is: `0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d`.","contentHash":"1ed8c2258e9c69e05d66f58776e6e8d834a637a36098612ce653207961657af5","addressRefs":["0x28b5a0e9c621a5badaa536219b3a228c8168cf5d"]},"16efc874-6658-48f0-a1fb-2babd3a90706":{"id":"16efc874-6658-48f0-a1fb-2babd3a90706","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.2.4","title":"Circle CCTP v2 Base To Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5751,"content":"The contract address of the Circle CCTP v2 Base to Mainnet is: `0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d`.","contentHash":"a690ea1b61dcc0ef2165943226e978f1d5c8d570a30b19f1ac00752bd0f46acd","addressRefs":["0x28b5a0e9c621a5badaa536219b3a228c8168cf5d"]},"b69eb9db-c986-4c19-a718-f0b747640c61":{"id":"b69eb9db-c986-4c19-a718-f0b747640c61","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.3","title":"Avalanche","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5752,"content":"The documents herein contain the Allocator Contract Addresses on Avalanche.","contentHash":"e8c30c94c2c48aeba2431996e93a0f9019915054ee3d2cd42ca909be16f038bf","addressRefs":[]},"4a1a3c1d-2291-4251-bbe5-8afdb1c9b725":{"id":"4a1a3c1d-2291-4251-bbe5-8afdb1c9b725","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.3.1","title":"Grove Executor","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5753,"content":"The address of the Grove executor on Avalanche is: `0x4b803781828b76EaBF21AaF02e5ce23596b4d60c`","contentHash":"879158296911f2188c63284d3a56a6077888aa2534ad72dc7b93c6b989380da8","addressRefs":["0x4b803781828b76eabf21aaf02e5ce23596b4d60c"]},"ae039fcd-37a2-4a47-843c-d079a2508941":{"id":"ae039fcd-37a2-4a47-843c-d079a2508941","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.1.3.2","title":"Grove Receiver","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5754,"content":"The address of the Grove receiver on Avalanche is: `0x380Be2b91B63BF75B194913b6e2C07Df09598c22`","contentHash":"f60c5cfcedc26cd8152d04106d73e842638ec09205233edc18a9d61372760758","addressRefs":["0x380be2b91b63bf75b194913b6e2c07df09598c22"]},"f233a46b-8dff-4335-8ccf-dc3f1c18a96f":{"id":"f233a46b-8dff-4335-8ccf-dc3f1c18a96f","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2","title":"ALM Contracts","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5755,"content":"The documents herein contain addresses for the ALM Contracts for the Grove Liquidity Layer.","contentHash":"c7fff4dd75abf094886b26cc2f8b11fc3f0d0345902fd4ba1ce2aa21c569c8a2","addressRefs":[]},"f6a76596-678a-45dd-900e-a7109102642e":{"id":"f6a76596-678a-45dd-900e-a7109102642e","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5756,"content":"The documents herein contain the ALM Contract Addresses for the Grove Liquidity Layer on the Ethereum Mainnet.","contentHash":"a42de3c988093300b6d12bf5d8b409a46a4efe9f37632f31e82324ea764155a3","addressRefs":[]},"53d016e8-dd83-42ca-a74b-7ed440d50bc5":{"id":"53d016e8-dd83-42ca-a74b-7ed440d50bc5","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.1.1","title":"ALM Controller (MainnetController) Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5757,"content":"The address of the ALM_CONTROLLER (MainnetController) contract is: `0xfd9dEA9a8D5B955649579Af482DB7198A392A9F5`.","contentHash":"a0642538672ae697cff892d640f275f7f87b282c3217d93fffe7838039223600","addressRefs":["0xfd9dea9a8d5b955649579af482db7198a392a9f5"]},"997b6fab-58d4-4d6d-a67f-f857585e829e":{"id":"997b6fab-58d4-4d6d-a67f-f857585e829e","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.1.2","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5758,"content":"The ALM_CONTROLLER contract version is: 1.8.0.","contentHash":"913cb8cffe97e8bd2b6878748f123a17a2c70e3ccc67474f707a42df32af1ae8","addressRefs":[]},"fb21540d-950c-4607-90a3-4736b1f0e517":{"id":"fb21540d-950c-4607-90a3-4736b1f0e517","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.1.3","title":"ALM Freezer Multisig (Mainnet) Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5759,"content":"The address of the Multisig that has the Freezer Role is: `0xB0113804960345fd0a245788b3423319c86940e5`","contentHash":"256b1cf9b38fcf22518aee358a7843aa22b374774709d7a2fb690835c93d8c42","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"51b50a8f-eb29-4424-bb0a-8247d2acce7d":{"id":"51b50a8f-eb29-4424-bb0a-8247d2acce7d","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.1.4","title":"ALM Relayer Multisig Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5760,"content":"The addresses of the multisigs that have the Relayer Role are specified in [A.6.1.1.2.2.6.1.2.1.2.2.1.1 - Address](2ecf77f4-13d5-40dd-a50f-d85aabdbf71b), [A.6.1.1.2.2.6.1.2.1.2.2.2.1 - Address](49588342-eebf-41e2-89eb-eb4f94ba5f36), and [A.6.1.1.2.2.6.1.2.1.2.2.3.1 - Address](712e0f02-b787-4812-8d67-60a81449b238).","contentHash":"763155ccfb6aee121d620b1f1603caada47d666ba0e58af3e92652b442b7a575","addressRefs":[]},"fda13ac2-b3ed-4b2a-9be6-9247632dafe3":{"id":"fda13ac2-b3ed-4b2a-9be6-9247632dafe3","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.1.5","title":"ALM Proxy (Mainnet) Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5761,"content":"The address of the ALM_PROXY contract is: `0x491EDFB0B8b608044e227225C715981a30F3A44E`","contentHash":"e667aed5e035506955049a35d46e13bc59c02aa79c2057d32ec702b6622ac953","addressRefs":["0x491edfb0b8b608044e227225c715981a30f3a44e"]},"d647b167-e936-4521-805e-f7851e48fe94":{"id":"d647b167-e936-4521-805e-f7851e48fe94","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.1.6","title":"ALM Rate Limits (Mainnet) Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5762,"content":"The address of the ALM_RATE_LIMITS contract is: `0x5F5cfCB8a463868E37Ab27B5eFF3ba02112dF19a`","contentHash":"6e63e796422854086a9bfe2ac7edf9536d0563106c99940a1e568ff10c658edb","addressRefs":["0x5f5cfcb8a463868e37ab27b5eff3ba02112df19a"]},"621734b8-dfaf-42f2-8ab1-9017e5e9c990":{"id":"621734b8-dfaf-42f2-8ab1-9017e5e9c990","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.2","title":"Avalanche","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5763,"content":"This document contains the ALM Contract Addresses for the Grove Liquidity Layer on Avalanche.","contentHash":"4307500124b4856cf45374406925f23fdded533beea49e703da72540f3054bb0","addressRefs":[]},"6445bdc4-6208-407f-820e-9d1e73213694":{"id":"6445bdc4-6208-407f-820e-9d1e73213694","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.2.1","title":"ALM Controller (ForeignController Avalanche) Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5764,"content":"The address of the ALM_CONTROLLER (ForeignController) contract is: `0x4236B772BEeEAFF57550Aa392A0f227C0b908Ce7`","contentHash":"c20fa8dfaa127534abc6e2717bc5b937d9b31d7b66ca47572139031370bfbbd5","addressRefs":["0x4236b772beeeaff57550aa392a0f227c0b908ce7"]},"6c937922-9c12-4d89-a987-8cca6bc27ebc":{"id":"6c937922-9c12-4d89-a987-8cca6bc27ebc","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.2.2","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5765,"content":"The ALM_CONTROLLER contract version is: 1.8.0.","contentHash":"913cb8cffe97e8bd2b6878748f123a17a2c70e3ccc67474f707a42df32af1ae8","addressRefs":[]},"228514c4-9a74-4324-b93a-4c10025d4bc7":{"id":"228514c4-9a74-4324-b93a-4c10025d4bc7","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.2.3","title":"ALM Freezer Multisig (Avalanche) Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5766,"content":"The address of the Multisig that has the Freezer Role is: `0xB0113804960345fd0a245788b3423319c86940e5`.","contentHash":"c9ddb936ffa6d0dfa41a5320e8598dedf550187757594279a8dfd9bedd33af28","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"79a7fa54-db2c-4850-b56b-55b1db8e7463":{"id":"79a7fa54-db2c-4850-b56b-55b1db8e7463","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.2.4","title":"ALM Relayer Multisig (Avalanche) Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5767,"content":"The address of the Multisig that has the Relayer Role is: `0x0eEC86649E756a23CBc68d9EFEd756f16aD5F85f`.","contentHash":"8448e57c5cc2a906673b3eb0512c474475c716c80734dedf0abc87dd378286b9","addressRefs":["0x0eec86649e756a23cbc68d9efed756f16ad5f85f"]},"0704f4b5-ee5c-455c-932f-94591b8a6594":{"id":"0704f4b5-ee5c-455c-932f-94591b8a6594","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.2.5","title":"ALM Proxy (Avalanche) Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5768,"content":"The address of the ALM_PROXY contract is: `0x7107DD8F56642327945294a18A4280C78e153644`","contentHash":"395aae28171c32d1cab9674a84f754f25b86101158ecb573a3cceb4190117778","addressRefs":["0x7107dd8f56642327945294a18a4280c78e153644"]},"fae298c2-f505-4d8f-904e-28220926b6d8":{"id":"fae298c2-f505-4d8f-904e-28220926b6d8","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.2.6","title":"ALM Rate Limits (Avalanche) Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5769,"content":"The address of the ALM_RATE_LIMITS contract is: `0x6ba2e6bCCe3d2A31F1e3e1d3e11CDffBaA002A21`","contentHash":"d80f4cc1d2904b86ad8cddc40d5e3fc8b1c793f62280215c7f19a4df54d7788d","addressRefs":["0x6ba2e6bcce3d2a31f1e3e1d3e11cdffbaa002a21"]},"50e8937a-ae76-49ac-8c50-e2ca21270303":{"id":"50e8937a-ae76-49ac-8c50-e2ca21270303","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.3","title":"Base","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5770,"content":"The documents herein contain the ALM Contract Addresses for the Grove Liquidity Layer on Base.","contentHash":"d269a9b8f9bc8cf0c5d27a696f75c674886168fda69cfdb13757bd65093950cd","addressRefs":[]},"c3c11dd2-3b15-4f6b-8771-ff1da05f1115":{"id":"c3c11dd2-3b15-4f6b-8771-ff1da05f1115","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.3.1","title":"ALM Controller Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5771,"content":"The address of the ALM_CONTROLLER contract is: `0x7f8408eBbBC3504F83eeDa52910dd75Eba92C955`.","contentHash":"bdfe5a1655038ff61c58f95d8c6354aaa3b766382b5dee25b488ba777f849366","addressRefs":["0x7f8408ebbbc3504f83eeda52910dd75eba92c955"]},"312c1860-7eec-4a60-9add-1b64204c2228":{"id":"312c1860-7eec-4a60-9add-1b64204c2228","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.3.2","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5772,"content":"The ALM_CONTROLLER contract version is: 1.8.0.","contentHash":"913cb8cffe97e8bd2b6878748f123a17a2c70e3ccc67474f707a42df32af1ae8","addressRefs":[]},"45278dad-c140-4671-9e33-59ba395d8d11":{"id":"45278dad-c140-4671-9e33-59ba395d8d11","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.3.3","title":"ALM Freezer Multisig Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5773,"content":"The address of the Multisig that has the Freezer Role is: `0xB0113804960345fd0a245788b3423319c86940e5`.","contentHash":"c9ddb936ffa6d0dfa41a5320e8598dedf550187757594279a8dfd9bedd33af28","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"b8053bf5-44d3-49b7-9eeb-9653df45abd1":{"id":"b8053bf5-44d3-49b7-9eeb-9653df45abd1","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.3.4","title":"ALM Relayer Multisig Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5774,"content":"The addresses of the Multisigs that have the Relayer Role are: `0x0eEC86649E756a23CBc68d9EFEd756f16aD5F85f` and `0x9187807e07112359C481870feB58f0c117a29179`.","contentHash":"daf2693c0ea169ad3dfc281a1a1d9f767a529c62ed896596b2bce543ff3c94ee","addressRefs":["0x0eec86649e756a23cbc68d9efed756f16ad5f85f","0x9187807e07112359c481870feb58f0c117a29179"]},"5c382a94-ce36-4ffa-862b-4718382450fe":{"id":"5c382a94-ce36-4ffa-862b-4718382450fe","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.3.5","title":"ALM Proxy Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5775,"content":"The address of the ALM_PROXY contract is: `0x9B746dBC5269e1DF6e4193Bcb441C0FbBF1CeCEe`","contentHash":"7d6b43bb30acbfcc498b8068c3778ec94c06baa518ded92f99fc9bc4d796d30a","addressRefs":["0x9b746dbc5269e1df6e4193bcb441c0fbbf1cecee"]},"a92d0054-8cc7-429b-91bb-dea4f0896e20":{"id":"a92d0054-8cc7-429b-91bb-dea4f0896e20","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.3.6","title":"ALM Rate Limits Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5776,"content":"The address of the ALM_RATE_LIMITS contract is: `0xAc8BF0669223197ac8B94Cbb53E725e40B3919E8`","contentHash":"0d962fd3311013d80f98a4f3c3b5e0ce08498b4600cabde89bcfbdbfeaa1ab82","addressRefs":["0xac8bf0669223197ac8b94cbb53e725e40b3919e8"]},"eae5ccc0-69e4-4210-8676-0f425e599f87":{"id":"eae5ccc0-69e4-4210-8676-0f425e599f87","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.4","title":"Plasma","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5777,"content":"The documents herein contain the ALM Contract Addresses for the Grove Liquidity Layer on Plasma.","contentHash":"d4b64718fdec06e24792d7ffc5d915827b038253430adc3068adf449c140c281","addressRefs":[]},"04952825-fe04-4459-ba45-01b44d21f606":{"id":"04952825-fe04-4459-ba45-01b44d21f606","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.4.1","title":"ALM Controller Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5778,"content":"The address of the ALM_CONTROLLER contract is: `0x85b0E7F3A7C1aB0E1aDea7dfAaD416D8A6e00f0e`","contentHash":"6b46c95eb08c38eeac61cd3a691ce98f961f45314e698e509dcf7240a642b005","addressRefs":["0x85b0e7f3a7c1ab0e1adea7dfaad416d8a6e00f0e"]},"ed9f98fd-bdaf-4779-a5d2-66b8194aa796":{"id":"ed9f98fd-bdaf-4779-a5d2-66b8194aa796","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.4.2","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5779,"content":"The ALM_CONTROLLER contract version will be specified in a future iteration of the Atlas.","contentHash":"56b42fb3ce4e240e2005c611b1064f6cbf70aa0fa7ee2c22f3f246efda7c4f3d","addressRefs":[]},"c7c722e6-f0d7-4182-afe1-ac260ce2482b":{"id":"c7c722e6-f0d7-4182-afe1-ac260ce2482b","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.4.3","title":"ALM Freezer Multisig Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5780,"content":"The address of the Multisig that has the Freezer Role is `0xB0113804960345fd0a245788b3423319c86940e5`","contentHash":"78fbd48f636d83396feade3a19135abc88af0c0164fb91f79d3829a5a5220a97","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"9a69f651-4e37-4c7e-8ecc-e93d0d36e358":{"id":"9a69f651-4e37-4c7e-8ecc-e93d0d36e358","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.4.4","title":"ALM Relayer Multisig Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5781,"content":"The address of the Multisig that has the Relayer Role is `0x0eEC86649E756a23CBc68d9EFEd756f16aD5F85f`","contentHash":"18cd1505a719529cab27aeb9031a76694b5015ea62350524a7c1b82c7e9f919f","addressRefs":["0x0eec86649e756a23cbc68d9efed756f16ad5f85f"]},"9d0bcc23-02d4-4389-9c85-707acf900dee":{"id":"9d0bcc23-02d4-4389-9c85-707acf900dee","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.4.5","title":"ALM Proxy Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5782,"content":"The address of the ALM_PROXY contract is: `0x0C462Fff7Cc975bC9F2B0aEB8270febA5FD71e1B`","contentHash":"0faaa609ead0a153d738aa6d9d76734a9179be3f469741d97b3dee8e35f76387","addressRefs":["0x0c462fff7cc975bc9f2b0aeb8270feba5fd71e1b"]},"59485651-9961-4382-8aa0-71b140a9105e":{"id":"59485651-9961-4382-8aa0-71b140a9105e","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.4.6","title":"ALM Rate Limits Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5783,"content":"The address of the ALM_RATE_LIMITS contract is: `0x1e993F992B90eE50115CD7bA2E7432a9c345d0c4`","contentHash":"963b370123cb10e93a3dc57aac8b90eb4b4d8a0f16b1d44409cd5094e54e51b8","addressRefs":["0x1e993f992b90ee50115cd7ba2e7432a9c345d0c4"]},"f2a1de37-0a71-45be-9dbb-8501c1a98252":{"id":"f2a1de37-0a71-45be-9dbb-8501c1a98252","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.5","title":"Plume","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5784,"content":"The documents herein contain the ALM Contract Addresses for the Grove Liquidity Layer on Plume.","contentHash":"de174ddb1fc30d3791e2f04bc7ca628bd85faa8a699d2e64b54a79f73aa6effe","addressRefs":[]},"15083990-2c69-45c1-93ab-8d48d140159c":{"id":"15083990-2c69-45c1-93ab-8d48d140159c","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.5.1","title":"ALM Controller Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5785,"content":"The address of the ALM_CONTROLLER contract is: `0x0C462Fff7Cc975bC9F2B0aEB8270febA5FD71e1B`","contentHash":"8c5d84e5325adcdea881af1caea3319f8a355c466601dfe8227e770d85310c80","addressRefs":["0x0c462fff7cc975bc9f2b0aeb8270feba5fd71e1b"]},"51739c12-4a4b-429c-a238-b1bdd554decf":{"id":"51739c12-4a4b-429c-a238-b1bdd554decf","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.5.2","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5786,"content":"The ALM_CONTROLLER contract version is: 1.6.0.","contentHash":"0d139bd8de2cb3e6af9cd02c0ab0753ccd8f7abb378925f406f46a609e6daa23","addressRefs":[]},"f655efd0-cbce-4c42-9c80-64f8358a339e":{"id":"f655efd0-cbce-4c42-9c80-64f8358a339e","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.5.3","title":"ALM Freezer Multisig Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5787,"content":"The address of the Multisig that has the Freezer Role is `0xB0113804960345fd0a245788b3423319c86940e5`","contentHash":"78fbd48f636d83396feade3a19135abc88af0c0164fb91f79d3829a5a5220a97","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"9e0a7a51-7cc1-4dce-9465-8b3961d14f1d":{"id":"9e0a7a51-7cc1-4dce-9465-8b3961d14f1d","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.5.4","title":"ALM Relayer Multisig Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5788,"content":"The address of the Multisig that has the Relayer Role is `0x0eEC86649E756a23CBc68d9EFEd756f16aD5F85f`","contentHash":"18cd1505a719529cab27aeb9031a76694b5015ea62350524a7c1b82c7e9f919f","addressRefs":["0x0eec86649e756a23cbc68d9efed756f16ad5f85f"]},"dcf0beac-b93e-41a7-b8b6-98c1d4cc819b":{"id":"dcf0beac-b93e-41a7-b8b6-98c1d4cc819b","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.5.5","title":"ALM Proxy Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5789,"content":"The address of the ALM_PROXY contract is: `0x1DB91ad50446a671e2231f77e00948E68876F812`","contentHash":"0219ccd058bdd08b9f847c5585246709a7ac1f128cf0b17a0a53c7d69d4a1966","addressRefs":["0x1db91ad50446a671e2231f77e00948e68876f812"]},"441a9fa5-4dcc-45f5-83a7-644128c23b05":{"id":"441a9fa5-4dcc-45f5-83a7-644128c23b05","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.2.5.6","title":"ALM Rate Limits Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5790,"content":"The address of the ALM_RATE_LIMITS contract is: `0x7f8408eBbBC3504F83eeDa52910dd75Eba92C955`","contentHash":"a7e5b4fe1b06bb63f29e230a9f13c19b8b40e96dd8d5993c6df685f14df3b424","addressRefs":["0x7f8408ebbbc3504f83eeda52910dd75eba92c955"]},"fc2fdc98-db17-4c10-91c1-50d05bd5bf9b":{"id":"fc2fdc98-db17-4c10-91c1-50d05bd5bf9b","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.3","title":"Tokenized Treasury Contracts","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5791,"content":"The documents herein define the addresses of shared Tokenized Treasury contracts used across Tokenized Treasury Instances of the Allocation System Primitive.","contentHash":"5fa4a652d55c00c40d7f059ae6b9840c916676a1a24144d4c4c2eb21578cf5f2","addressRefs":[]},"87773690-d9bc-4772-a39e-005552df0896":{"id":"87773690-d9bc-4772-a39e-005552df0896","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.3.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5792,"content":"This document contains the shared Tokenized Treasury contract addresses on Ethereum Mainnet.","contentHash":"69e28a6268a4033a4fc5ccc605d368993a041846d1d2ad8b6a47c372f388786b","addressRefs":[]},"11401b83-fc65-4c0a-8d57-503c1c2041ea":{"id":"11401b83-fc65-4c0a-8d57-503c1c2041ea","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.3.1.1","title":"RWA Instance Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5793,"content":"The address of the RWA Instance contract will be specified in a future iteration of the Atlas.","contentHash":"4420034524701455ba123354d6d744fe94eec217749334379a9eb9f7aa881279","addressRefs":[]},"21933aee-36b7-425f-8ad7-5ccd1c046c1a":{"id":"21933aee-36b7-425f-8ad7-5ccd1c046c1a","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.3.1.2","title":"Tokenized Treasury USDS And USDC Rate Provider Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5794,"content":"The address of the Chronicle Rate Provider contract pricing USDS and USDC, shared across Tokenized Treasury Instances that use USDS and USDC, is: `0xd79B9a9f5Fc240f2DCfcf260f004110B4713A7e7`.","contentHash":"c8ba329f9f48c3698433e5000ff426e0bd634038ce2317818ce5e8cc119c5aaa","addressRefs":["0xd79b9a9f5fc240f2dcfcf260f004110b4713a7e7"]},"75699288-150e-45e0-8c4a-19c40e4c1e94":{"id":"75699288-150e-45e0-8c4a-19c40e4c1e94","doc_no":"A.6.1.1.2.2.6.1.2.1.1.1.3.1.3","title":"Sky USDS And USDC PSM Wrapper Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5795,"content":"The address of the Sky USDS and USDC PSM Wrapper contract is: `0xA188EEC8F81263234dA3622A406892F3D630f98c`.","contentHash":"b30f19101921e0fb8b802b18ba0721ad8fa79551c3602508fef02622d6919e8f","addressRefs":["0xa188eec8f81263234da3622a406892f3d630f98c"]},"ec6cc8a0-3811-485a-9f9a-78f388659d46":{"id":"ec6cc8a0-3811-485a-9f9a-78f388659d46","doc_no":"A.6.1.1.2.2.6.1.2.1.1.2","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5796,"content":"The documents herein list the off-chain operational parameters for the Grove Liquidity Layer. These operational parameters are protocol settings managed outside of smart contracts (off-chain), used by operators and off-chain systems to guide the functioning of the Grove Liquidity Layer.","contentHash":"ed43b20b69ddc20d68c441a861528d6a8c51f522dc669f7d18b243b9e747e681","addressRefs":[]},"15554f42-3b63-4f11-a7e3-2e02c91d7171":{"id":"15554f42-3b63-4f11-a7e3-2e02c91d7171","doc_no":"A.6.1.1.2.2.6.1.2.1.1.2.1","title":"Off-chain Operational Parameters For Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5797,"content":"The document herein lists the current off-chain operational parameters for the Grove Liquidity Layer on Ethereum Mainnet.","contentHash":"09f49a0fa50f19a8b5187bb19a870cdb301936d0717da7bb483bbd1c80e68ea7","addressRefs":[]},"cad9056b-c097-4b3c-9958-e8962d8ef1ca":{"id":"cad9056b-c097-4b3c-9958-e8962d8ef1ca","doc_no":"A.6.1.1.2.2.6.1.2.1.1.2.1.1","title":"Minimum Operation Size Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5798,"content":"The minimum transaction size for operations on Ethereum Mainnet is (`MAINNET_MIN_OPERATION_SIZE`):\n\n- This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"ba4a0df3510f17a4adef915caa956812854958557949d47199de76d40bd4fb2f","addressRefs":[]},"1500fd24-2b7e-4a1c-8725-84e7a0b8adc5":{"id":"1500fd24-2b7e-4a1c-8725-84e7a0b8adc5","doc_no":"A.6.1.1.2.2.6.1.2.1.1.2.1.2","title":"Debt Ceiling Buffer Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5799,"content":"The buffer amount below the maximum debt ceiling is (`DEBT_CEILING_BUFFER`):\n\n- This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"b5584fb15085a8c48f3f66a3cd7b69b1cf374e82c988944fb90e8c5f6771eec1","addressRefs":[]},"ad3dbd7b-602b-4457-bc5e-25ed5708fbc2":{"id":"ad3dbd7b-602b-4457-bc5e-25ed5708fbc2","doc_no":"A.6.1.1.2.2.6.1.2.1.1.2.2","title":"Off-chain Operational Parameters For Avalanche","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5800,"content":"The document herein lists the current off-chain operational parameters for the Grove Liquidity Layer on Avalanche.","contentHash":"da32b1f1f326109c3e6688decccc7b872fc06bc172d86326a17e38bc384f41d0","addressRefs":[]},"29e17dd9-c575-496a-9c20-658aa92a260b":{"id":"29e17dd9-c575-496a-9c20-658aa92a260b","doc_no":"A.6.1.1.2.2.6.1.2.1.1.2.2.1","title":"Minimum Operation Size Avalanche","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5801,"content":"The minimum transaction size for operations on Avalanche is (`AVALANCHE_MIN_OPERATION_SIZE`):\n\n- This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"fbf6a93062e4483bf358e61e12d7d3f9ac514b8dc67193c40ccedc301fea0bf3","addressRefs":[]},"c485dc9b-e21b-4df9-8323-0d2856524a71":{"id":"c485dc9b-e21b-4df9-8323-0d2856524a71","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3","title":"RateLimits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5802,"content":"The documents herein list the Ratelimits for the Grove Liquidity Layer on each blockchain.","contentHash":"ccf3edbab3ad1a98802037b6dcecf1bd3c948d3397fcf7d2de94af1c11308715","addressRefs":[]},"7fe3ae46-d78e-428d-b41e-c2c49417fc3e":{"id":"7fe3ae46-d78e-428d-b41e-c2c49417fc3e","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5803,"content":"The documents herein list the current `RateLimits` for the Grove Liquidity Layer on Ethereum Mainnet.","contentHash":"75f7630a3e3021037375bd16839a78a9fc8c07c00ec21f5524dec649f045899b","addressRefs":[]},"104541de-f257-405a-8870-ab26d099f57b":{"id":"104541de-f257-405a-8870-ab26d099f57b","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.1.1","title":"USDS Mint Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5804,"content":"The maximum amount of USDS that can be minted within the Grove Liquidity Layer (`LIMIT_USDS_MINT`) is specified in the document herein.\n\n- `maxAmount` (USDS): 500,000,000\n- `slope` (USDS/ day): 500,000,000","contentHash":"14df0a502224288474bdf1ccaea5f5093555928565435d66bbdc1dc78650c6de","addressRefs":[]},"cf829503-02cf-4b84-8c04-7d05de1d82dd":{"id":"cf829503-02cf-4b84-8c04-7d05de1d82dd","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.1.2","title":"USDS Burn Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5805,"content":"The maximum amount of USDS that can be burned within the Grove Liquidity Layer (`LIMIT_USDS_BURN`) is specified in the document herein.\n\n- `maxAmount` (USDS): This parameter will be specified in a future iteration of the Grove Artifact.\n- `slope` (USDS/ day): This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"07bc15af5a2ce39362485aabad7e3dfbccd3de82c9e80c3e9f5316b8269ccad1","addressRefs":[]},"a591104c-5c45-480d-a156-46484440e163":{"id":"a591104c-5c45-480d-a156-46484440e163","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.1.3","title":"USDS For USDC Swap Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5806,"content":"The maximum amount of USDS that can be swapped for USDC by the Grove Liquidity Layer in the Mainnet PSM (`LIMIT_USDS_TO_USDC`) is specified in the document herein.\n\n- `maxAmount`: 500,000,000 USDC\n- `slope`: 500,000,000 USDC per day","contentHash":"1db59034c915c001abd750a8f9180ed6fafb2c48dd51d80a2f76a64f78d1f963","addressRefs":[]},"8a462b2a-68dc-4caf-ab26-855552f57d4f":{"id":"8a462b2a-68dc-4caf-ab26-855552f57d4f","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.1.4","title":"USDC Mainnet ALM Proxy Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5807,"content":"The maximum amount of USDC that can be sent to the Ethereum Mainnet ALM Proxy (`LIMIT_USDC_TO_DOMAIN`, hashed with Ethereum domain) is specified in the document herein.\n\n- `maxAmount` (USDC): This parameter will be specified in a future iteration of the Grove Artifact.\n- `slope` (USDC/ day): This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"a5be409f3843998a0fa83d15df335e2180cf842bbb2dad2a44254aea4b89ad10","addressRefs":[]},"b43ee2cd-06b9-4615-bcb4-ac44e2b8c693":{"id":"b43ee2cd-06b9-4615-bcb4-ac44e2b8c693","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.1.5","title":"USDC Mainnet ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5808,"content":"The maximum amount of USDC that can be bridged to Ethereum Mainnet ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_ETH`) is specified in the document herein.\n\n- `maxAmount` (USDC): max\n- `slope` (USDC/ day): 0","contentHash":"2038e8d1796e8a4462ced247f95034df3e0a4ac5824908ebadac38a855849a66","addressRefs":[]},"f6094634-372c-4235-beba-0862922809fb":{"id":"f6094634-372c-4235-beba-0862922809fb","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.1.6","title":"USDS To Avalanche Via SkyLink","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5809,"content":"The maximum amount of USDS that can be sent to the Avalanche ALM Controller via SkyLink (`LIMIT_LAYERZERO_TRANSFER`, hashed with Avalanche USDS OFT address and Avalanche destination domain) is specified in the document herein.\n\n- `maxAmount`: 50,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"313eb5a16e22f34841cf8b262f2dd925284f50a68e05f9a8c6ab13ce01a03cb8","addressRefs":[]},"b650c48d-435c-47e3-ac33-17ab6187492f":{"id":"b650c48d-435c-47e3-ac33-17ab6187492f","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.2","title":"Avalanche","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5810,"content":"The documents herein list the current `RateLimits` for the Grove Liquidity Layer on Avalanche.","contentHash":"165f50054ac877f67f9bb91ca1287e1527f0ec7c9c8c9c8bc740527f35d35f6f","addressRefs":[]},"00b438d4-d359-4e2f-a1fa-4c12aaf8c978":{"id":"00b438d4-d359-4e2f-a1fa-4c12aaf8c978","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.2.1","title":"USDC Avalanche ALM Proxy Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5811,"content":"The maximum amount of USDC that can be sent to the Avalanche ALM Proxy (`LIMIT_USDC_TO_DOMAIN`, hashed with Avalanche domain) is specified in the document herein.\n\n- `maxAmount` (USDC): This parameter will be specified in a future iteration of the Grove Artifact.\n- `slope` (USDC/ day): This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"7cb5665f431ff9cf4f3ea53c433ca4b85f844312ca5b05a2a282a181b8413ad6","addressRefs":[]},"d5b284c1-8cb7-4e49-8efc-6253b517f36e":{"id":"d5b284c1-8cb7-4e49-8efc-6253b517f36e","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.2.2","title":"USDC Avalanche ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5812,"content":"The maximum amount of USDC that can be bridged to Avalanche ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_Avalanche`) is specified in the document herein.\n\n- `maxAmount` (USDC): 50,000,000\n- `slope` (USDC/ day): 50,000,000","contentHash":"c2c3386ba83103e78909aff89818146721c84714b968422e1848ca6ea8f4d94d","addressRefs":[]},"a3b52620-db3f-40fa-80d5-a7eacf52090c":{"id":"a3b52620-db3f-40fa-80d5-a7eacf52090c","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.2.3","title":"USDC Ethereum Mainnet ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5813,"content":"The maximum amount of USDC that can be bridged to Ethereum Mainnet from the Avalanche ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_Ethereum`) is specified in the document herein.\n\n- `maxAmount` (USDC): Unlimited\n- `slope` (USDC/ day): Unlimited","contentHash":"f6e118a8d6e55d595946b7b88e7363f0dfe8daf79cc9dccd96c15049ccbea7c1","addressRefs":[]},"dec9ce16-90ba-48bd-b299-9462cb50de2c":{"id":"dec9ce16-90ba-48bd-b299-9462cb50de2c","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.2.4","title":"USDS To Ethereum Mainnet Via SkyLink","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5814,"content":"The maximum amount of USDS that can be sent to the Ethereum Mainnet ALM Controller from Avalanche via SkyLink (`LIMIT_LAYERZERO_TRANSFER`, hashed with Ethereum Mainnet USDS OFT address and Ethereum Mainnet destination domain) is specified in the document herein.\n\n- `maxAmount`: 20,000,000 USDS\n- `slope`: 20,000,000 USDS per day","contentHash":"03b6038f56933c1809205cc7853166fd8b7f0592981b83eb69442ee9693a424b","addressRefs":[]},"cedb7b47-c7e6-4948-8835-5862a65592cc":{"id":"cedb7b47-c7e6-4948-8835-5862a65592cc","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.3","title":"Base","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5815,"content":"The documents herein list the current `RateLimits` for the Grove Liquidity Layer on Base.","contentHash":"04afb30f21fc5eaca8c069acf2fbded5d30e014b9484ccd18714f00cf7247e6a","addressRefs":[]},"dba2c846-ecbe-4227-abfc-63dbd654af48":{"id":"dba2c846-ecbe-4227-abfc-63dbd654af48","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.3.1","title":"USDC Base ALM Proxy Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5816,"content":"The maximum amount of USDC that can be sent to the Base ALM Proxy (`LIMIT_USDC_TO_DOMAIN`, hashed with Base domain) is specified in the document herein.\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Grove Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"65c3b098cebd05e2ab701cd4721bb1b89ce0bbf3a0205871580a9570b66ef3b8","addressRefs":[]},"34e5a190-ec23-4449-8cf1-1125f78a6e44":{"id":"34e5a190-ec23-4449-8cf1-1125f78a6e44","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.3.2","title":"USDC Base ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5817,"content":"The maximum amount of USDC that can be bridged to Base ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_Base`) is specified in the document herein.\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"ae91dfe0f3586544d21064884522c5d8e9ed1b71c7b9f778894a00603a273e3d","addressRefs":[]},"9575357d-2778-4556-80d8-ca1e4ab293a6":{"id":"9575357d-2778-4556-80d8-ca1e4ab293a6","doc_no":"A.6.1.1.2.2.6.1.2.1.1.3.3.3","title":"USDC Ethereum Mainnet ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5818,"content":"The maximum amount of USDC that can be bridged to Ethereum Mainnet from the Base ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_Ethereum`) is specified in the document herein.\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"016373e8999afedeff92f934ca379f6814a53b95cd52934be1868f0ce5f779d9","addressRefs":[]},"21a390bd-ffc4-4f14-b8fd-e30aacdcee89":{"id":"21a390bd-ffc4-4f14-b8fd-e30aacdcee89","doc_no":"A.6.1.1.2.2.6.1.2.1.1.4","title":"On-chain Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5819,"content":"The documents herein list general on-chain parameters for the Grove Liquidity Layer.","contentHash":"bd3d0f63b514db524b671fb8808577f00b3617b4f592969e36d1f7e528f42061","addressRefs":[]},"4db4b613-f06c-4aae-a091-2a78521fb6de":{"id":"4db4b613-f06c-4aae-a091-2a78521fb6de","doc_no":"A.6.1.1.2.2.6.1.2.1.1.4.1","title":"Allocator Vault Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5820,"content":"The Allocator Vault parameters for ALLOCATOR-BLOOM-A are defined in [A.3.7.1.2.1.2 - ALLOCATOR-BLOOM-A Parameters](53cba245-68c6-4af9-a280-b200dabebec7).","contentHash":"5e89f140ade01b7e10fe1759550c8844096e1e08f5bda04fc0256e5927b1ee5c","addressRefs":[]},"6859900b-3d53-4a5c-8a00-ddb1cf0c07a4":{"id":"6859900b-3d53-4a5c-8a00-ddb1cf0c07a4","doc_no":"A.6.1.1.2.2.6.1.2.1.2","title":"Governance Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5821,"content":"The documents herein describe the specific governance processes for the Grove Liquidity Layer.","contentHash":"7ddbd1799e159a47b5786c28f69795844d38569268b6b2a46232cbf88768260e","addressRefs":[]},"edf44383-44e6-4aaa-972a-7dfdaee0998d":{"id":"edf44383-44e6-4aaa-972a-7dfdaee0998d","doc_no":"A.6.1.1.2.2.6.1.2.1.2.1","title":"Invoking New Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5822,"content":"The governance process to invoke a new Instance of the Allocation System Primitive follows the Root Edit process see [A.6.1.1.2.2.2.2.2.1.2 - Operational Process Definition](40826926-adb2-4de3-936d-702e2d8cb3b9).","contentHash":"3deff3bd7d3ce525d34a28a0cd0d981dd5fa3e3853d1c58d8acd0dea837b0ff5","addressRefs":[]},"355db9eb-fc32-4a27-819a-42e8c2f26b1b":{"id":"355db9eb-fc32-4a27-819a-42e8c2f26b1b","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2","title":"Multisigs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5823,"content":"The documents herein define multisigs that have privileged access to manage the Grove Liquidity Layer.","contentHash":"580b4c1afdfa3cac161eeb92c3a8c82f9c8e65e2f5759bad1877b29282160135","addressRefs":[]},"5e6f63a8-d0e5-441d-927b-13830f5f9b24":{"id":"5e6f63a8-d0e5-441d-927b-13830f5f9b24","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.1","title":"Prime Primary Relayer Multisig","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5824,"content":"The Prime Primary Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.2.2.6.1.2.2.1.1.2 - Relayer Role](4639e60c-111f-4018-bc8d-501b88c20edd) and is controlled by Grove.","contentHash":"c70091a24ae369e1a74b4f13158f2cdad25ce749a54ba976c2224973a72273d9","addressRefs":[]},"2ecf77f4-13d5-40dd-a50f-d85aabdbf71b":{"id":"2ecf77f4-13d5-40dd-a50f-d85aabdbf71b","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.1.1","title":"Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5825,"content":"The address of the Prime Primary Relayer Multisig is `0x0eEC86649E756a23CBc68d9EFEd756f16aD5F85f`.","contentHash":"ef283154fc15440f7ee76c67e89c0badac6e02048a9ce03aa73b7e8439692663","addressRefs":["0x0eec86649e756a23cbc68d9efed756f16ad5f85f"]},"7c9c4334-71c3-4e55-ad66-7970d244a1a0":{"id":"7c9c4334-71c3-4e55-ad66-7970d244a1a0","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.1.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5826,"content":"The Prime Primary Relayer Multisig currently has a 4/7 signing requirement.","contentHash":"96d5b8e13ba4ea12bc10693add0dc4c2aa7c6cddd4fe24108307fa770cf00a23","addressRefs":[]},"10b61bac-2e7a-4607-b464-75ac1635c102":{"id":"10b61bac-2e7a-4607-b464-75ac1635c102","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.1.3","title":"Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5827,"content":"The signers of the Prime Primary Relayer Multisig are seven (7) addresses controlled by Grove.","contentHash":"1a52446bd0e854a1cc3bef202797d473a2ca2fbe07ebed4dba9fa64a9276d93d","addressRefs":[]},"b3f2fd41-9682-46ff-b85e-4a0f0d0885b5":{"id":"b3f2fd41-9682-46ff-b85e-4a0f0d0885b5","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.1.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5828,"content":"The signers of the Prime Primary Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Grove Artifact.","contentHash":"9eeeb15951c15712d89c92b882f96a2d94545a22f78cc34f642f205ed072e503","addressRefs":[]},"8baba39e-0d83-4d64-b15a-cf9948583a5e":{"id":"8baba39e-0d83-4d64-b15a-cf9948583a5e","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.1.5","title":"Modification","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5829,"content":"Grove can change the signers of the Prime Primary Relayer Multisig at any time, so long as there are at least two (2) signers and at least a majority of signers are required to execute transactions.","contentHash":"b9d4c11c4497ce34e12340008c619d308355fe624fc18ecbc77341756214b1fa","addressRefs":[]},"bc712bee-9788-4f31-b671-fbc5aafaf42c":{"id":"bc712bee-9788-4f31-b671-fbc5aafaf42c","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.2","title":"Prime Secondary Relayer Multisig","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5830,"content":"The Prime Secondary Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.2.2.6.1.2.2.1.1.2 - Relayer Role](4639e60c-111f-4018-bc8d-501b88c20edd) and is controlled by Grove.","contentHash":"21d4ac634570f86969d7adf8e58b560b746e1fa5e077ae86c8823ceaac5f8cc6","addressRefs":[]},"49588342-eebf-41e2-89eb-eb4f94ba5f36":{"id":"49588342-eebf-41e2-89eb-eb4f94ba5f36","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.2.1","title":"Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5831,"content":"The address of the Prime Secondary Relayer Multisig is `0x9187807e07112359C481870feB58f0c117a29179`.","contentHash":"75e679f678313dc2f53efa796f0226bd35f890cb50cbb844bc85ac1828c6871d","addressRefs":["0x9187807e07112359c481870feb58f0c117a29179"]},"8f0b88bf-0fcd-4103-a4c2-e03b61a2e8a7":{"id":"8f0b88bf-0fcd-4103-a4c2-e03b61a2e8a7","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.2.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5832,"content":"The Prime Secondary Relayer Multisig currently has a 1/2 signing requirement.","contentHash":"4d5e5da727e7c91c1a8bf6d20f152c1bff46f8b985c5811d9a215c3346b69504","addressRefs":[]},"2ff0395a-f47a-478a-8621-28bae36bc2f7":{"id":"2ff0395a-f47a-478a-8621-28bae36bc2f7","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.2.3","title":"Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5833,"content":"The signers of the Prime Secondary Relayer Multisig are two (2) addresses controlled by Grove.","contentHash":"04243d73fac220aad14ba645790beaad1fe8344e3bf3f6738b454d674ac109de","addressRefs":[]},"d50351e8-6cca-4d49-abb8-0c7ce3b16b92":{"id":"d50351e8-6cca-4d49-abb8-0c7ce3b16b92","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.2.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5834,"content":"The signers of the Prime Secondary Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Grove Artifact.","contentHash":"657510a45a72e16e993e7f4f1f10472dbc2f1f0cdf760d64e22180be9f921adb","addressRefs":[]},"eecf9254-7939-492a-a4c8-938bbb19c7a0":{"id":"eecf9254-7939-492a-a4c8-938bbb19c7a0","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.2.5","title":"Modification","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5835,"content":"Grove can change the signers of the Prime Secondary Relayer Multisig at any time, so long as there are at least two (2) signers and at least a majority of signers are required to execute transactions.","contentHash":"3deaf9e557e875abfdf1ace3a752cd1ea13f077a2c2bc6c8abfad76a8aeae7a0","addressRefs":[]},"be75c381-80e1-4c95-8b8b-e990f00a178e":{"id":"be75c381-80e1-4c95-8b8b-e990f00a178e","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.3","title":"Core Operator Relayer Multisig","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5836,"content":"The Core Operator Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.2.2.6.1.2.2.1.1.2 - Relayer Role](4639e60c-111f-4018-bc8d-501b88c20edd), and is controlled by Operational GovOps Soter Labs.","contentHash":"c2cbaf4fd62dc64c8aa2a6e3d7316c96c8f8d571556deb6eaf5712241d27fd44","addressRefs":[]},"712e0f02-b787-4812-8d67-60a81449b238":{"id":"712e0f02-b787-4812-8d67-60a81449b238","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.3.1","title":"Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5837,"content":"The address of the Core Operator Relayer Multisig on the Ethereum Mainnet is `0x4364D17B578b0eD1c42Be9075D774D1d6AeAFe96`.","contentHash":"57c2a743bf21af7d39f9711d82fff5c80587f6a4a804dfd33c3a7fa4fc3a5809","addressRefs":["0x4364d17b578b0ed1c42be9075d774d1d6aeafe96"]},"9a1af2ad-da1b-460f-89f6-84c513c71418":{"id":"9a1af2ad-da1b-460f-89f6-84c513c71418","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.3.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5838,"content":"The Core Operator Relayer Multisig currently has a 2/3 signing requirement.","contentHash":"b95f8f292db28ccf8bfd3f9a26c34232a22a6849ead7951e92687e1b4cdfd849","addressRefs":[]},"7a7df887-8cdf-447e-8d8e-aad3360c7417":{"id":"7a7df887-8cdf-447e-8d8e-aad3360c7417","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.3.3","title":"Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5839,"content":"The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs.","contentHash":"3f47955b9c0fde92c5560c85814bf985ea86ba974f63c359990c046ae3388a94","addressRefs":[]},"2014eee2-c5e7-4da7-8925-04b5e4bfd6f5":{"id":"2014eee2-c5e7-4da7-8925-04b5e4bfd6f5","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.3.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5840,"content":"The signers of the Core Operator Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Grove Artifact.","contentHash":"08e8e429f08f93e8151b3bdc0acb29c19a01848209476132c21b5a8b96be4761","addressRefs":[]},"f789a1aa-ddfb-4ddd-85c4-76387ef6d516":{"id":"f789a1aa-ddfb-4ddd-85c4-76387ef6d516","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.3.5","title":"Modification","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5841,"content":"Operational GovOps Soter Labs can change the signers of the Core Operator Relayer Multisig at any time, so long as there are at least three (3) signers and at least two-thirds of signers are required to execute transactions.","contentHash":"050db4ce28c6bd1736123e3211a765079215503656f41e97eb06d3e0f0f22af0","addressRefs":[]},"99bc2dd5-5573-4bb9-9210-5af299d058d9":{"id":"99bc2dd5-5573-4bb9-9210-5af299d058d9","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.4","title":"Freezer Multisig","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5842,"content":"The Freezer Multisig has the `FREEZER_ROLE` as defined in [A.6.1.1.2.2.6.1.2.2.1.1.4 - Freezer Role](37871a80-dc8f-4804-bce1-5f082e9bca9f).","contentHash":"8cf5d9fb5ef201405a153ddc1a63c059b257e2009232f3d99dcc528af8c675b1","addressRefs":[]},"33cb22ad-7032-4eec-ab47-4c5f5d28e064":{"id":"33cb22ad-7032-4eec-ab47-4c5f5d28e064","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.4.1","title":"Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5843,"content":"The address of the Freezer Multisig on the Ethereum Mainnet is `0xB0113804960345fd0a245788b3423319c86940e5`.","contentHash":"4f4832701a70dc988f2633212487ddf4bbc5f69abd7c59e14d35e58ed7c182ee","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"939338a1-df49-47cb-9206-810059b6c16a":{"id":"939338a1-df49-47cb-9206-810059b6c16a","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.4.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5844,"content":"The Freezer Multisig currently has a 2/5 signing requirement.","contentHash":"5e26a52c6172c820a3edf55895c2df704dad7607cd26054763c73cd1b6fbdbc3","addressRefs":[]},"0a18da19-36e2-4948-93cc-ee86d20617b3":{"id":"0a18da19-36e2-4948-93cc-ee86d20617b3","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.4.3","title":"Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5845,"content":"The signers of the Freezer Multisig are two (2) addresses controlled by Operational GovOps Soter Labs, two (2) addresses controlled by Operational Facilitator Endgame Edge, and one (1) address controlled by Grove.","contentHash":"90f8b4aafa81abbe630f37e6c219c8a6059e3661dbfeb786c31e1d2fd5f92dd9","addressRefs":[]},"1bd5fe5c-6cb4-4a5a-a84a-03e59736c98a":{"id":"1bd5fe5c-6cb4-4a5a-a84a-03e59736c98a","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.4.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5846,"content":"The signers of the Freezer Multisig should exercise their authority to freeze the Grove Liquidity Layer in the event that Grove is not complying with rules regarding Risk Capital or Asset Liability Management, or in the event of another emergency.\n\nEach action executed by the Freezer Multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum.","contentHash":"b9b1784f9b9776e86ac6444f72e39348afb864630f945d456b7f9e1b01fd84de","addressRefs":[]},"827f87da-917e-4acf-af0a-9e220641b145":{"id":"827f87da-917e-4acf-af0a-9e220641b145","doc_no":"A.6.1.1.2.2.6.1.2.1.2.2.4.5","title":"Modification","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5847,"content":"Modification of the signers of the Freezer Multisig must be approved through an Atlas Edit Proposal.\n\nThe only exceptions to this are if: 1) a signer self-reports a loss of access to their private key due to any reason; or 2) a signer explicitly expresses their wish to be removed as a signer. In both cases, the signer is required to communicate the loss of access to their private key, or the wish to be removed as a signer, in the form of a public Sky Forum post. The specific signer should be replaced as soon as possible.\n\nAny changes to the Multisig signers that do not fall within the two exceptions listed above, or that have not been ratified by Sky Governance, should be questioned immediately and treated as malicious. Where malicious activity is suspected, the Core Facilitator must prepare an expedited Executive Vote so that Sky Governance can vote on removing external security access from the Multisig.","contentHash":"5a7d5809b6c81bb95db41542b9e9b65803e19629cf564e404811d45d7486f1e4","addressRefs":[]},"3567039f-c74a-4f4c-85c9-e68ac880009a":{"id":"3567039f-c74a-4f4c-85c9-e68ac880009a","doc_no":"A.6.1.1.2.2.6.1.2.1.3","title":"Total Risk Capital (TRC) Management","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5848,"content":"The documents herein specify requirements related to Grove’s Total Risk Capital (TRC) management.","contentHash":"ff76f80363e86228fe8b6dff2e711da9e079a2646c2d24d9aabbdb1c4fa513ec","addressRefs":[]},"b5120b66-7007-4f0c-977f-a441a7067f92":{"id":"b5120b66-7007-4f0c-977f-a441a7067f92","doc_no":"A.6.1.1.2.2.6.1.2.1.3.1","title":"Grove Development Company’s Operation Of Grove Liquidity Layer And Agreement Regarding Encumbrance Ratio","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5849,"content":"Grove Development Company will operate the Grove Liquidity Layer and agrees to stay at or below a 90% Encumbrance Ratio. See [A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9).","contentHash":"8b81c2bdaa33d83e3117a501bba4430cf8cf1f056500a92fa4200f3fd415525b","addressRefs":[]},"35b828fe-4bf3-49e3-a87b-95751562f2b5":{"id":"35b828fe-4bf3-49e3-a87b-95751562f2b5","doc_no":"A.6.1.1.2.2.6.1.2.1.3.2","title":"Grove Development Company’s Total Risk Capital (TRC) Management Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5850,"content":"As operators of the Grove Liquidity Layer, Grove Development Company automatically inherits, and is subject to, the base class of operational requirements related to Total Risk Capital management defined in [A.2.2.9.1.1.3.2.1.2 - Primes' Total Risk Capital (TRC) Management](3af8a3a2-25e5-44b3-87a4-7df1f2712685). Modifications to the base operational logic automatically propagate to the Grove Artifact.","contentHash":"8d8e98b280975780a0591e57eed0d231776aff3a6bf98206fc2a2617140974a6","addressRefs":[]},"e5d30bed-ae48-459e-92f1-2a97f21855b7":{"id":"e5d30bed-ae48-459e-92f1-2a97f21855b7","doc_no":"A.6.1.1.2.2.6.1.2.2","title":"Grove Liquidity Layer Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5851,"content":"The documents herein describe common operational procedures for the Grove Liquidity Layer applicable across multiple Instances.","contentHash":"6ee4e05e9d31e268e46a2c3369e428c8f2d29e184fd01cd4d8626b347facf789","addressRefs":[]},"eed08bf3-af5a-4cae-ae12-95ef5c6b6798":{"id":"eed08bf3-af5a-4cae-ae12-95ef5c6b6798","doc_no":"A.6.1.1.2.2.6.1.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5852,"content":"The documents herein define the protocol for routine ongoing management of the Grove Liquidity Layer and its active Instances.","contentHash":"b447e54c9825108e97f98161c68d57cbebd6b38c534e4188048ffe164a8378d0","addressRefs":[]},"dd9524c4-136c-4e52-a9af-0390517361d5":{"id":"dd9524c4-136c-4e52-a9af-0390517361d5","doc_no":"A.6.1.1.2.2.6.1.2.2.1.1","title":"Role Hierarchy And Permissions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5853,"content":"The documents herein defines roles (Admin, Relayer, Freezer) and their responsibilities/permissions for managing the Grove Liquidity Layer.","contentHash":"547f8dc6489cff8acbe2f2fbe63476f276a2e06f653fd48893f25f4ef0d23d5f","addressRefs":[]},"dc515367-2fa0-4f98-b3d1-1b82d7ce782f":{"id":"dc515367-2fa0-4f98-b3d1-1b82d7ce782f","doc_no":"A.6.1.1.2.2.6.1.2.2.1.1.1","title":"Default Admin Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5854,"content":"The admin role (`DEFAULT_ADMIN_ROLE`) is the role that can grant and revoke any role, including itself and all other roles defined in the contract. The admin role is also used for general admin functions in all contracts. This role is fully controlled by Sky Governance via the Grove Proxy.\n\n```\nconstructor(address admin) {\n        _grantRole(DEFAULT_ADMIN_ROLE, admin);\n```","contentHash":"4dd53d763717b5b99a003b9014f1abc99e930981d4345dfd48ced6fa10dfb31d","addressRefs":[]},"4639e60c-111f-4018-bc8d-501b88c20edd":{"id":"4639e60c-111f-4018-bc8d-501b88c20edd","doc_no":"A.6.1.1.2.2.6.1.2.2.1.1.2","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5855,"content":"The `RELAYER_ROLE` is the address for the Grove Liquidity Layer ALM Planner off-chain system that calls functions on `Controller` contracts to perform actions on behalf of the `ALMProxy` contract. The Relayer Role may be granted to an address by any address holding the `DEFAULT_ADMIN_ROLE`. The Relayer Role may be removed from an address by any address holding the `DEFAULT_ADMIN_ROLE` or the `FREEZER_ROLE`.","contentHash":"daa61aad264e13167dd903a7c12ae4a55e922f50d602d9932615411c9d6f4152","addressRefs":[]},"955c8db9-7bd7-4e49-b23c-7b482c84ca97":{"id":"955c8db9-7bd7-4e49-b23c-7b482c84ca97","doc_no":"A.6.1.1.2.2.6.1.2.2.1.1.3","title":"ALM Controller Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5856,"content":"The `ALM_CONTROLLER_ROLE` is the address of the role that can call the `call` functions on the `ALMProxy` contract and update `RateLimits` contract. It includes the `MainnetController` and `ForeignController` contracts. ALM Controller contracts are accessed and modified via the Relayer Role.","contentHash":"2338ec34a7da2944765e15ca9792b0c4ec0cffcbf72218d25d3c57bffdc821f2","addressRefs":[]},"37871a80-dc8f-4804-bce1-5f082e9bca9f":{"id":"37871a80-dc8f-4804-bce1-5f082e9bca9f","doc_no":"A.6.1.1.2.2.6.1.2.2.1.1.4","title":"Freezer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5857,"content":"The `FREEZER_ROLE` is the address of the emergency role that can remove a compromised Relayer.","contentHash":"5613adb996d95581a1f27d5ec22a32a62f59e9d8f62e6ff43f248f6bd75f410f","addressRefs":[]},"4d77a9ba-d186-48e8-a70d-53aa66e01c65":{"id":"4d77a9ba-d186-48e8-a70d-53aa66e01c65","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2","title":"Controller Functions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5858,"content":"The documents herein describe the purpose and operational use of key functions within the Grove Liquidity Layer `MainnetController` contracts: USDS management (mint/burn USDS), Asset Transfer Management (direct transfers, protocol deposits/withdrawals), Cross-chain Operations (CCTP bridging).","contentHash":"e99241c875a677ad0a6d5e844c2ac72247018af97968014d8b66d8d790af6825","addressRefs":[]},"1ee14921-5883-4533-aba0-b96d44e3cf6b":{"id":"1ee14921-5883-4533-aba0-b96d44e3cf6b","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1","title":"Mainnet Controller Contract Functions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5859,"content":"The documents herein define the functions controlled by the Controller contract for Grove Liquidity Layer operations on Ethereum Mainnet.","contentHash":"319702e3f760a1e5828f541e48af6aba72c5e396bb28bc3524d75b34ef2674f4","addressRefs":[]},"cdc104ee-6c78-404e-95bd-362dcec206bb":{"id":"cdc104ee-6c78-404e-95bd-362dcec206bb","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.1","title":"Admin Functions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5860,"content":"The documents herein define the operations performed by the `DEFAULT_ADMIN_ROLE` within the `MainnetController` contract.","contentHash":"ef2dd126343ef27e44dac91a9fa8ab84a7f77022ba19f45cde2dc73282dee02e","addressRefs":[]},"c4c09a75-ef25-4aa7-825a-73d386cbc87f":{"id":"c4c09a75-ef25-4aa7-825a-73d386cbc87f","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.1.1","title":"Set The Mint Recipient","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5861,"content":"The documents herein define the process to set the `mintRecipient` for a specific `destinationDomain`. This is used in cross-chain transfers to specify the address that will receive minted tokens on the target chain.","contentHash":"ac97c3006b959eb2702d4a42dcb6fb6a4184ae1b18c18f6c4faa299dfe270cca","addressRefs":[]},"310f2d02-371c-4fa1-b0bf-1e07d80464ee":{"id":"310f2d02-371c-4fa1-b0bf-1e07d80464ee","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.1.1.1","title":"Admin Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5862,"content":"The operator must ensure they are working as an Admin. Only the `DEFAULT_ADMIN_ROLE` is allowed to `setMintRecipient`.\n\n```\nfunction setMintRecipient(uint32 destinationDomain, bytes32 mintRecipient)\n        external\n        onlyRole(DEFAULT_ADMIN_ROLE)\n```","contentHash":"3f1c51fb46e2051ba3377fc73d9219df217b504bb94821996593aacc403ca1fa","addressRefs":[]},"c639083a-417f-45c8-ba94-c0713d1539ac":{"id":"c639083a-417f-45c8-ba94-c0713d1539ac","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.1.1.2","title":"Associate Mint Recipient With Domain","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5863,"content":"The operator must associate the `mintRecipient` with the `destinationDomain` such that any tokens minted on this domain will go to this recipient.\n\n```\n{\n        mintRecipients[destinationDomain] = mintRecipient;\n```","contentHash":"ddd587772be59ecbcba6eb93f151952b736aa8017d6598b7e0226d9e66d62f66","addressRefs":[]},"e3e6ca9d-7cd6-44f1-a688-80f1e744ed0f":{"id":"e3e6ca9d-7cd6-44f1-a688-80f1e744ed0f","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.1.1.3","title":"Emit Event To Logs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5864,"content":"The operator must emit the event to the blockchain logs.\n\n```\n        emit MintRecipientSet(destinationDomain, mintRecipient);\n    }\n```","contentHash":"415b45bf98a676ded63a74f18970eba4e7c85abcb498ac8d005e164fa3df3fa4","addressRefs":[]},"609939e3-81c4-4096-9f74-e4a410982b73":{"id":"609939e3-81c4-4096-9f74-e4a410982b73","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2","title":"Relayer Functions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5865,"content":"The documents herein define the operations performed by the `RELAYER_ROLE` within the `MainnetController` contract.","contentHash":"989229be02e35772e8a77e872cb3a4a77ae1b104064f991b448513ef70d3ee1f","addressRefs":[]},"a5229ab8-f310-4a83-97c7-555782b1f61b":{"id":"a5229ab8-f310-4a83-97c7-555782b1f61b","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1","title":"Core Vault Functions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5866,"content":"The documents herein define the operations that are performed to maintain the desired level of liquidity and debt balance of the Grove Liquidity Layer.","contentHash":"2e7f6c07435da67516c3edc09e7693fc0a6d486349f8608c667e759f5ba9c7e9","addressRefs":[]},"36126625-ab5d-4071-b805-5bd3ac4b246b":{"id":"36126625-ab5d-4071-b805-5bd3ac4b246b","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1","title":"Mint USDS","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5867,"content":"The documents herein define the steps for an operator to `mint` USDS from the Sky Allocation Vault to the Grove ALM Proxy.","contentHash":"665ff098f1cac567c3997137c4d292882f188ffdaabc34b620b61e8cdb248238","addressRefs":[]},"044fed6d-5a18-48d1-89df-777f86e4652a":{"id":"044fed6d-5a18-48d1-89df-777f86e4652a","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5868,"content":"The operator must ensure they are working as a `Relayer`. Only the `RELAYER` role is allowed to `mintUSDS`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction mintUSDS(uint256 usdsAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"0699ff9050f80c6ee37bd3244def5da428b2974d6781bcf0761bb8f3c7ebfe40","addressRefs":[]},"e3f04b74-9b6d-45e9-9363-e76bda9ba6dc":{"id":"e3f04b74-9b6d-45e9-9363-e76bda9ba6dc","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5869,"content":"The operator must ensure the `RateLimits` allow for minting the required amount.\n\n` rateLimited(LIMIT_USDS_MINT, usdsAmount)`","contentHash":"da490100c1b298300ed302bb31ffd2e60392211f985d89fc86e9fa10679e1de5","addressRefs":[]},"8230c4c2-71d4-4d1b-800b-0684e2de136e":{"id":"8230c4c2-71d4-4d1b-800b-0684e2de136e","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.3","title":"Mint USDS To Buffer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5870,"content":"The operator must call the `MainnetController` contract to `mint` USDS into the Buffer.","contentHash":"bcb64f3f855b3d4068265a5b4ea78963fb8d3b08148e6c758ff2e2da8968d3ac","addressRefs":[]},"137c1b88-c53c-42a2-95ed-6a4f42a41211":{"id":"137c1b88-c53c-42a2-95ed-6a4f42a41211","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.3.1","title":"Encode Mint Function Call","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5871,"content":"The operator must encode the `mint` function call, using `abi.encodeCall` with the address `vault` from which USDS will be `drawn`, and the `amount` of USDS to `mint`.","contentHash":"4c99b77c0615870f8869ac156e6e9d96d83b9338dd4da95ce353cbf79acc52ac","addressRefs":[]},"79ee81f3-b03f-4b60-8bbb-92d2e98ef1c6":{"id":"79ee81f3-b03f-4b60-8bbb-92d2e98ef1c6","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.3.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5872,"content":"The operator must send the encoded call using `proxy.doCall()` to the `draw` function of the vault contract.\n\n```\n    {\n        // Mint USDS into the buffer\n        proxy.doCall(\n            address(vault),\n            abi.encodeCall(vault.draw, (usdsAmount))\n        );\n```","contentHash":"3480937f177e06db1a50f4d8894bd5a83f2c4e58875f17c72868f7197b249374","addressRefs":[]},"b51fa176-1c34-4ad3-9154-46a6d1b6f60d":{"id":"b51fa176-1c34-4ad3-9154-46a6d1b6f60d","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.4","title":"Transfer USDS To ALM Proxy","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5873,"content":"The operator must call the `MainnetController` contract to `transfer` USDS from the Buffer to the ALM Proxy.","contentHash":"6b72d63683b9d08af48b249473750c262951b1f684a9d7556a750574b1964810","addressRefs":[]},"2a0d2948-5e23-4fc4-bad5-c692644f58c7":{"id":"2a0d2948-5e23-4fc4-bad5-c692644f58c7","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.4.1","title":"Encode Transfer Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5874,"content":"The operator must encode the `transfer` function call, using `abi.encodeCall` with the `buffer` address USDS will be transferred from, the `proxy` address that will receive USDS (i.e. ALM Proxy), and the `amount` of USDS to `transfer`.","contentHash":"588f50bd1c7e39dac696ec016acc75209ce80993fc3aa9bc0f3657fa1ea4df69","addressRefs":[]},"043d3c4c-7fa0-4bba-8393-ea762c109bce":{"id":"043d3c4c-7fa0-4bba-8393-ea762c109bce","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.1.4.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5875,"content":"The operator must send the encoded call using `proxy.doCall()` to the `transferFrom` function of the USDS contract.\n\n```\n        // Transfer USDS from the buffer to the proxy\n        proxy.doCall(\n            address(usds),\n            abi.encodeCall(usds.transferFrom, (buffer, address(proxy), usdsAmount))\n        );\n    }\n```","contentHash":"67f2acb5f4b95d74069aa58e6ab32c49407ade41afce41f0638ae6bc331b9cde","addressRefs":[]},"25706c25-2b74-486e-8234-c45f6630f379":{"id":"25706c25-2b74-486e-8234-c45f6630f379","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2","title":"Burn USDS","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5876,"content":"The documents herein define the steps for an operator to return and then `burn` Grove’s USDS debt in the Sky Allocation Vault.","contentHash":"d64337b41ce613fe3bec08bbc31111ee331a9ef4f37c3c6769d34507bf77cdfd","addressRefs":[]},"23d1b504-bd08-4759-b2d6-9067fdbcaedd":{"id":"23d1b504-bd08-4759-b2d6-9067fdbcaedd","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5877,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `burnUSDS`. They must also ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction burnUSDS(uint256 usdsAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"1d6c1d3f6bcf55c3bb899a25bc5960733f56aade04c445e94a4a2e6f6f796587","addressRefs":[]},"6449fd5a-ec8b-4d71-aa03-7cac23780c2c":{"id":"6449fd5a-ec8b-4d71-aa03-7cac23780c2c","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5878,"content":"The operator must ensure the `RateLimits` allow for minting the required amount.\n\n`cancelRateLimit(LIMIT_USDS_MINT, usdsAmount)`","contentHash":"95e303d09b876fff8c521a255f110a01372512b9fada00d5337744afcb016fc0","addressRefs":[]},"2e633940-12fd-4a3b-9b02-6fae976fd7e5":{"id":"2e633940-12fd-4a3b-9b02-6fae976fd7e5","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.3","title":"Transfer USDS To Buffer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5879,"content":"The operator must call the `MainnetController` to `transfer` USDS from the ALM Proxy to the Buffer.","contentHash":"401cc3785586d8544ed0df3293259456266e6e392b9c60870f982e1f2585438d","addressRefs":[]},"285f4224-5618-4be4-bb0e-900319d24c84":{"id":"285f4224-5618-4be4-bb0e-900319d24c84","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.3.1","title":"Encode Transfer Function Call","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5880,"content":"The operator must encode the `transfer` function call, using `abi.encodeCall` with the `buffer` address USDS will be transferred to, and the `amount` of USDS to `transfer`.","contentHash":"9d86e385ddb6e6cf057c06109ebb52031cbeae824027aea8dc353fc097116408","addressRefs":[]},"cdab9e7d-6a80-42a1-95fb-e4f72de7dbaf":{"id":"cdab9e7d-6a80-42a1-95fb-e4f72de7dbaf","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.3.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5881,"content":"The operator must send the encoded call using `proxy.doCall()` to the `transfer` function of the USDS contract.\n\n```\n     {\n        // Transfer USDS from the proxy to the buffer\n        proxy.doCall(\n            address(usds),\n            abi.encodeCall(usds.transfer, (buffer, usdsAmount))\n        );\n```","contentHash":"61da017b0e9ee747ab185acb44b9168cd5b506dcafa82c29fa2d544d9ee3f47d","addressRefs":[]},"df488122-2d82-4a54-8285-b24b86eb2e49":{"id":"df488122-2d82-4a54-8285-b24b86eb2e49","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.4","title":"Burn USDS","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5882,"content":"The operator must call the `MainnetController` contract to `burn` USDS.","contentHash":"dfe3eea25e20ed18f64619ce68bf982eda36d69d0bcb5c053c5da3b304b09708","addressRefs":[]},"f571c4cc-9172-4310-a863-9e94d1d5e953":{"id":"f571c4cc-9172-4310-a863-9e94d1d5e953","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.4.1","title":"Encode Wipe Function Call","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5883,"content":"The operator must encode the `wipe` function call, using `abi.encodeCall` with the address `vault` from which USDS will be `burned`, and the `amount` of USDS to `burn`.","contentHash":"c846ae13325433633f5f11f1013ca3576a039a683d6cb22288256ccb74b63212","addressRefs":[]},"d9ecb48d-6487-4c98-89c6-fabd4af60490":{"id":"d9ecb48d-6487-4c98-89c6-fabd4af60490","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2.4.2","title":"Send Encoded Call","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5884,"content":"The operator must send the encoded call using `proxy.doCall()` to the `wipe` function of the vault contract.\n\n```\n// Burn USDS from the buffer\n        proxy.doCall(\n            address(vault),\n            abi.encodeCall(vault.wipe, (usdsAmount))\n        );\n    }\n```","contentHash":"ad225ee32d721ae7b398858b289c8ab16409c0bf14d054985de370fd758cf722","addressRefs":[]},"2d92707b-e08a-49a5-8b31-a22cf6f458af":{"id":"2d92707b-e08a-49a5-8b31-a22cf6f458af","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.2","title":"ERC-4626 Functions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5885,"content":"The documents herein define the general Grove Liquidity Layer operational procedures for interacting with ERC4626-compliant tokenized vaults. ERC4626 is a standard interface for vaults representing shares of an underlying ERC20 token. The Grove Liquidity Layer can integrate with various ERC4626 vaults.","contentHash":"e667abc945b7fc39309d7a89aabe577754d8f27fc2777da6313b39ecae5a2ea4","addressRefs":[]},"4876005c-31a8-4be8-8133-e239bd0ac53b":{"id":"4876005c-31a8-4be8-8133-e239bd0ac53b","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.2.1","title":"General Deposit to ERC-4626 Tokens Procedure","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5886,"content":"This document defines the steps for an operator to deposit assets from the ALM Proxy to the ERC-4626 vault to receive yield-bearing shares.\n\n- The Grove Liquidity Layer Operator, acting as `RELAYER`, initiates a deposit.\n- Pre-conditions are checked: Grove Liquidity Layer contract `isActive`, ALM Proxy has sufficient underlying asset, and the deposit amount is within instance-specific `RateLimits` (defined in the relevant Instance Configuration Document).\n- The Grove Liquidity Layer Operator approves the target ERC4626 vault (identified by its `token` address in the Instance Configuration Document) to spend the underlying `asset` from the ALM Proxy.\n- The Grove Liquidity Layer Operator calls the `deposit(uint256 amount, address receiver)` function on the target ERC4626 vault, specifying the `amount` of underlying asset and the ALM `proxy` as the receiver of vault shares.\n- The number of shares received is recorded.\n- For detailed call structures, instance-specific parameters (vault address, asset address, rate limits), and operational examples, refer to the specific ERC4626 Instance Configuration Document (ICD).","contentHash":"00402ec4d8bec2dc9d947ee2e6dc42880fa7487f3ce300fa31135ff9d2716476","addressRefs":[]},"7b560160-e427-45a2-a3ac-3c23cf6fe943":{"id":"7b560160-e427-45a2-a3ac-3c23cf6fe943","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.2.2","title":"General Withdraw from ERC-4626 Tokens Procedure","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5887,"content":"This document defines the steps for an operator to withdraw a yield-earning balance from the ERC-4626 vault to the ALM Proxy.\n\n- The Grove Liquidity Layer Operator, acting as `RELAYER`, initiates a withdrawal.\n- Pre-conditions are checked: Grove Liquidity Layer contract `isActive`, ALM Proxy has sufficient shares of the ERC4626 vault token, and the withdrawal amount is within instance-specific `RateLimits` (defined in the relevant ICD).\n- Grove Liquidity Layer calls the `withdraw(uint256 assets, address receiver, address owner)` function on the target ERC4626 vault, specifying the `amount` of underlying assets to withdraw, with the ALM `proxy` as both `receiver` (of assets) and `owner` (of shares being burned).\n- The number of shares burned is recorded.\n- For detailed call structures, instance-specific parameters, and operational examples, refer to the specific ERC4626 Instance Configuration Document.","contentHash":"aa9fb4ab3f55962ed1aa433942a037a5469b7c8f810aff59563160a81109c4b1","addressRefs":[]},"7e90e505-42b9-474d-9cc5-9b4da6af7375":{"id":"7e90e505-42b9-474d-9cc5-9b4da6af7375","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.2.3","title":"General Redeem from ERC-4626 Tokens Procedure","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5888,"content":"This document defines the steps for an operator to redeem yield-bearing shares from the ERC-4626 vault, receiving the corresponding amount of underlying assets into the ALM Proxy.\n\n- The Grove Liquidity Layer Operator, acting as `RELAYER`, initiates a redemption of shares.\n- Pre-conditions are checked: Grove Liquidity Layer contract `isActive`, ALM Proxy has sufficient shares of the ERC4626 vault token.\n- Grove Liquidity Layer calls the `redeem(uint256 shares, address receiver, address owner)` function on the target ERC4626 vault, specifying the number of `shares` to redeem, with the ALM `proxy` as both `receiver` (of assets) and `owner` (of shares being redeemed).\n- The amount of underlying assets received is recorded, and relevant `RateLimits` (for withdrawal) are updated.\n- For detailed call structures, instance-specific parameters, and operational examples, refer to the specific ERC4626 Instance Configuration Document.","contentHash":"d8f3c59bbd6b2b1bf07242e8480e4ada34dd402661a4f780fcdd8a645675a259","addressRefs":[]},"2df8d8c7-17ee-4427-a75b-fc3ce08913d4":{"id":"2df8d8c7-17ee-4427-a75b-fc3ce08913d4","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3","title":"PSM Functions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5889,"content":"The documents herein define the swap operations performed by the Grove Liquidity Layer in the PSM.","contentHash":"960548c53fee731f175ebaaded341d7786f4282dd15db1286a11c6d38460c963","addressRefs":[]},"e159020b-6b20-4894-b001-ce13f389734a":{"id":"e159020b-6b20-4894-b001-ce13f389734a","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1","title":"Swap USDS to USDC","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5890,"content":"The documents herein define a series of operations for an operator to `swap` USDS to USDC through the PSM.","contentHash":"564fc251dbabe1de4723b87aa7179a9f9f901ef1b48e8c75549e98fefb798c1b","addressRefs":[]},"bd3ff49e-77af-4757-984d-f8e91346e702":{"id":"bd3ff49e-77af-4757-984d-f8e91346e702","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5891,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `swapUSDSToUSDC`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction swapUSDSToUSDC(uint256 usdcAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"c3b17d9e48f51665258702f1a188bc93d15edf34ac754e1de087b8b04a254d24","addressRefs":[]},"532d5769-4224-48c0-9282-9c19e9fe6455":{"id":"532d5769-4224-48c0-9282-9c19e9fe6455","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5892,"content":"The operator must ensure that `RateLimits` allows for swapping the required USDS amount to USDC.\n\n`rateLimited(LIMIT_USDS_TO_USDC, usdcAmount)`","contentHash":"517eec48e7b8c02b7d4828b7745f4edc49f59204a5fd66079cece35c481809ec","addressRefs":[]},"aa417e52-f42f-4653-a820-e0cdafac9aea":{"id":"aa417e52-f42f-4653-a820-e0cdafac9aea","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.3","title":"Convert To 18 Token Format","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5893,"content":"The operator must convert USDC amounts to an 18 token decimal format using `psmTo18ConversionFactor`.\n\n```\n{\n        uint256 usdsAmount = usdcAmount * psmTo18ConversionFactor;\n```","contentHash":"79d74874f2de3ba98c3736afa0d281d0e34dfc2023b2a2004ca7732eb0bfd435","addressRefs":[]},"c4b00dec-4cc9-49e8-97d1-a5c64560c8ce":{"id":"c4b00dec-4cc9-49e8-97d1-a5c64560c8ce","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.4","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5894,"content":"The operator must ensure that the ALM Proxy has enough USDS balance to `swap` for the required USDC amount.","contentHash":"46838f3aa1e3d6ddd36efe61d71f57682926a235ff432405904e66ec4d9e3371","addressRefs":[]},"348d05d6-74cb-484e-85dc-68bbce3e97df":{"id":"348d05d6-74cb-484e-85dc-68bbce3e97df","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.5","title":"Approve Contract Spend","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5895,"content":"The operator must approve the `daiUsds` contract to spend the `usdsAmount` on behalf of the `proxy`. `daiUsds` is a contract that facilitates a 1:1 swap between USDS and DAI.\n\n```\nproxy.doCall(\n            address(usds),\n            abi.encodeCall(usds.approve, (address(daiUsds), usdsAmount))\n        );\n```","contentHash":"aa75d340b6e82041989fde64dfe26f372f7689d2d0c8c5771b8c6c71b60fb425","addressRefs":[]},"97c2db26-16e7-4aee-a257-86bef4189fa7":{"id":"97c2db26-16e7-4aee-a257-86bef4189fa7","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.6","title":"Swap USDS To DAI","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5896,"content":"The operator must swap USDS to DAI. USDS is swapped to DAI in a 1:1 ratio through the `daiUsds` contract and sent back to the `proxy`.\n\n```\nproxy.doCall(\n    address(daiUsds),\n    abi.encodeCall(daiUsds.usdsToDai, (address(proxy), usdsAmount))\n);\n```","contentHash":"9d4dc459dc591e4721a2c68533fba01098ebff4de2f7d48c0eaf9c6a1dc15f81","addressRefs":[]},"0e02d0f4-a9b1-4f2f-8016-274c26db9fa2":{"id":"0e02d0f4-a9b1-4f2f-8016-274c26db9fa2","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.7","title":"Approve PSM Spend","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5897,"content":"The operator must approve the PSM to spend the newly acquired DAI. The approval is needed for the PSM to be able to `swap` DAI for USDC.\n\n```\nproxy.doCall(\n    address(dai),\n    abi.encodeCall(dai.approve, (address(psm), usdsAmount))\n);\n```","contentHash":"30a5e1ff278c71260ad2598dd8edc8646f1b17d9adfe06780b15b82b3421b4aa","addressRefs":[]},"fcf618b7-7708-4999-af08-c85b5b902ca5":{"id":"fcf618b7-7708-4999-af08-c85b5b902ca5","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.1.8","title":"Swap DAI To USDC","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5898,"content":"The operator must swap DAI to USDC. DAI is swapped to USDC in the PSM at a 1:1 ratio with no fee, using the `buyGemNoFee` function and return USDC to the `proxy`.\n\n```\n        proxy.doCall(\n            address(psm),\n            abi.encodeCall(psm.buyGemNoFee, (address(proxy), usdcAmount))\n        );\n    }\n```","contentHash":"7a7036d3a0062c6355098fa48214aea708091386738b0400901a36d15cf10924","addressRefs":[]},"1ec9a718-44f4-4ce9-97b3-bebeb207b280":{"id":"1ec9a718-44f4-4ce9-97b3-bebeb207b280","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2","title":"Swap USDC to USDS","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5899,"content":"The documents herein define a series of operations for an operator to `swap` USDC to USDS through the PSM.","contentHash":"f55bbceca04d743a7ae5c9c46fa9d3d34fd14dab41a5f282da781a788be9ba83","addressRefs":[]},"a3637c8d-ce3e-4cc8-ae15-2a8623a841db":{"id":"a3637c8d-ce3e-4cc8-ae15-2a8623a841db","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5900,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `swapUSDCToUSDS`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction swapUSDCToUSDS(uint256 usdcAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"f3ee36a72607de63195d31bc66fe14f5dcb34cee78f4d659008d3c4a90cb2306","addressRefs":[]},"462537ca-626a-4516-afd6-a3a344d1e241":{"id":"462537ca-626a-4516-afd6-a3a344d1e241","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.2","title":"Check RateLimits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5901,"content":"The operator must ensure that `RateLimits` allows for swapping the required USDC amount to USDS.\n\n`cancelRateLimit(LIMIT_USDS_TO_USDC, usdcAmount)`","contentHash":"4fe17333b51ce4e616f144d362e287fecaeba978eeb9b3f15c12be77f567ae95","addressRefs":[]},"f5d1b5d7-3968-4b49-99ff-21d7e3a5d2b7":{"id":"f5d1b5d7-3968-4b49-99ff-21d7e3a5d2b7","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.3","title":"Check ALM Proxy","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5902,"content":"The operator must ensure ALM Proxy has enough USDC balance to `swap` for the required USDS amount.","contentHash":"910b3439932669d61c78560e750ba1140bb6661d2fdce964872093d0c2907261","addressRefs":[]},"2c2b3e9a-5135-4379-bd4f-9f52884bd8da":{"id":"2c2b3e9a-5135-4379-bd4f-9f52884bd8da","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.4","title":"Approve Contract Spend","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5903,"content":"The operator must approve the PSM to spend USDC. The approval is needed for the PSM to be able to execute a `swap` of USDC.\n\n```\nproxy.doCall(\n    address(usdc),\n    abi.encodeCall(usdc.approve, (address(psm), usdcAmount))\n);\n```","contentHash":"109d7b51f311e7cbfb33a70c06703a4401618fb6de1d01a00ce0ab42e5ec0a64","addressRefs":[]},"0b3c6086-9e48-4587-a182-59ddf73000e2":{"id":"0b3c6086-9e48-4587-a182-59ddf73000e2","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.5","title":"Calculate Swap Limit","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5904,"content":"The operator must calculate the `swap` `limit` per transaction. The maximum amount of USDC that can be swapped to DAI in one transaction is calculated based on the DAI balance held by the PSM. `psmTo18ConversionFactor` converts DAI’s 18 token decimals to USDC’s 6 token decimals.\n\n`uint256 limit = dai.balanceOf(address(psm)) / psmTo18ConversionFactor;`","contentHash":"61d1c09ef3218a346d559a17127f79742ded36dde2c5ff55fd7dc96e0ef9270b","addressRefs":[]},"f060c012-dad4-4509-8ed8-1d68a88b7ca7":{"id":"f060c012-dad4-4509-8ed8-1d68a88b7ca7","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.6","title":"Swap USDC To DAI Directly If Possible","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5905,"content":"The operator must perform a `direct swap` feasibility check and `swap` USDC to DAI, if possible. If the `usdcAmount` is less than or equal to the `limit`, a direct swap should be performed. `_swapUSDCToDAI` is called to execute the swap from `USDC` to `DAI`.\n\n```\nif (usdcAmount <= limit) {\n    _swapUSDCToDAI(usdcAmount);\n}\n```","contentHash":"790bda381c653805cda375e135061e899ebaf7b715c38e41b548105814a4a9db","addressRefs":[]},"f64c4f1d-f7e3-4673-a43a-6891892a8d0d":{"id":"f64c4f1d-f7e3-4673-a43a-6891892a8d0d","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.7","title":"Swap USDC To DAI Iteratively If Needed","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5906,"content":"If `direct swap` is not possible, the operator must perform an `iterative swap` of USDC to DAI with DAI `refilling`.","contentHash":"ee5e385ba0724f63abf9216ac30cf03680fa63685c2787879e0010836a2889ef","addressRefs":[]},"20dba0ba-3dd2-47cb-8e7a-793de6a11c5d":{"id":"20dba0ba-3dd2-47cb-8e7a-793de6a11c5d","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.8","title":"Split Into Multiple Swaps If Limit Exceeded","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5907,"content":"If the `usdcAmount` exceeds the limit, the operator must split the swap into multiple smaller swaps as follows.\n\n1. The operator must refill the PSM with DAI by calling `psm.fill()`.\n2. The operator must recalculate the limit to see how much USDC can be swapped after the refill.\n3. The operator must swap the maximum possible USDC amount that doesn't exceed the limit.\n4. The operator must update `remainingUsdcToSwap` by subtracting the amount just swapped.\n5. The operator must repeat the process until the full `usdcAmount` is swapped.","contentHash":"1513220c29993c03fc315cd22d728231420a9102d181e899087c81148dc0d209","addressRefs":[]},"fcd50c06-9606-4a47-9bf8-fd28522535c1":{"id":"fcd50c06-9606-4a47-9bf8-fd28522535c1","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.9","title":"Split Into Multiple Swaps If Limit Exceeded","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5908,"content":"If the PSM can't be filled, the transaction reverts with `DssLitePsm/nothing-to-fill`.\n\n```\nelse {\n    uint256 remainingUsdcToSwap = usdcAmount;\n\n    while (remainingUsdcToSwap > 0) {\n        psm.fill();\n\n        limit = dai.balanceOf(address(psm)) / psmTo18ConversionFactor;\n\n        uint256 swapAmount = remainingUsdcToSwap < limit ? remainingUsdcToSwap : limit;\n\n        _swapUSDCToDAI(swapAmount);\n\n        remainingUsdcToSwap -= swapAmount;\n    }\n}\n```","contentHash":"b361b53607cb955315980849416124f17c767e98d8c50f0e441e685a7cff4054","addressRefs":[]},"810ef030-d702-4de4-9d56-0e2b3c9e4d5b":{"id":"810ef030-d702-4de4-9d56-0e2b3c9e4d5b","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.10","title":"Convert USDC Amount To DAI Amount","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5909,"content":"The operator must convert the USDC amount to the DAI amount, accounting for the token decimal difference.\n\n```\n{\n        uint256 daiAmount = usdcAmount * psmTo18ConversionFactor;\n```","contentHash":"bae4099a43fd4e11d306c82ef102857628a691166a482e1fe164d09d22bc5f31","addressRefs":[]},"fda81f79-1689-40f8-b971-95e314a0ec16":{"id":"fda81f79-1689-40f8-b971-95e314a0ec16","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.11","title":"Approve Contract Spend","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5910,"content":"The operator must approve the `daiUsds` contract to spend the `daiAmount` on behalf of the `proxy`.\n\n```\nproxy.doCall(\n    address(dai),\n    abi.encodeCall(dai.approve, (address(daiUsds), daiAmount))\n);\n```","contentHash":"8558eaa3103ec44c188810c3642f41b9f5c74c386af6e06abbc7f35df8b21072","addressRefs":[]},"77750a12-c615-4ffd-a05b-4c58f9d6277a":{"id":"77750a12-c615-4ffd-a05b-4c58f9d6277a","doc_no":"A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2.12","title":"Swap DAI to USDS","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5911,"content":"The operator must swap DAI to USDS. DAI is swapped to USDS at a 1:1 ratio through the `daiUsds` contract and sent back to the `proxy`.\n\n```\nproxy.doCall(\n            address(daiUsds),\n            abi.encodeCall(daiUsds.daiToUsds, (address(proxy), daiAmount))\n        );\n    }\n```","contentHash":"ed1825d2b0588ecb2bd768fca3b52c7c5fd1d7757e70adddf41745ae997b3949","addressRefs":[]},"873c16ce-2d4d-4d10-bb97-fb1634114311":{"id":"873c16ce-2d4d-4d10-bb97-fb1634114311","doc_no":"A.6.1.1.2.2.6.1.2.2.1.3","title":"Rate Limit Management","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5912,"content":"The documents herein define the protocol for querying, setting, and adjusting `RateLimits` for Instances using their `RateLimitID`s. The ratelimits must be maintained in line with Spark’s strategy, market conditions, and security considerations.","contentHash":"f596d4da6c7820597073dc6c69584dddc2394e41d0838a3ca29533ae6f581176","addressRefs":[]},"5aea6114-5e7e-4bb1-86fa-c54135015397":{"id":"5aea6114-5e7e-4bb1-86fa-c54135015397","doc_no":"A.6.1.1.2.2.6.1.2.2.1.3.1","title":"RateLimits Query","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5913,"content":"The following code sets out instructions for the operator to query the current `RateLimits` for a specific key:\n\n```\nFunction getRateLimitData(bytes32 key) external override view returns (RateLimitData memory) {\n        return _data[key];\n    }\n\n    function getCurrentRateLimit(bytes32 key) public override view returns (uint256) {\n        RateLimitData memory d = _data[key];\n\n        // Unlimited rate limit case\n        if (d.maxAmount == type(uint256).max) {\n            return type(uint256).max;\n        }\n\n        return _min(\n            d.slope * (block.timestamp - d.lastUpdated) + d.lastAmount,\n            d.maxAmount\n        );\n    }\n```","contentHash":"a3880073976bd68f69cc7f7c24a8996d997019336a9ab49625d5b63ff9486b99","addressRefs":[]},"aec1d10f-a5df-48d4-bbea-1b02c279c919":{"id":"aec1d10f-a5df-48d4-bbea-1b02c279c919","doc_no":"A.6.1.1.2.2.6.1.2.2.1.3.2","title":"Set RateLimit","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5914,"content":"The following code sets out instructions for the operator to set the `RateLimit` for a specific key:\n\n```\nfunction setRateLimitData(\n        bytes32 key,\n        uint256 maxAmount,\n        uint256 slope,\n        uint256 lastAmount,\n        uint256 lastUpdated\n    )\n        public override onlyRole(DEFAULT_ADMIN_ROLE)\n    {\n        require(lastAmount  <= maxAmount,       \"RateLimits/invalid-lastAmount\");\n        require(lastUpdated <= block.timestamp, \"RateLimits/invalid-lastUpdated\");\n\n        _data[key] = RateLimitData({\n            maxAmount:   maxAmount,\n            slope:       slope,\n            lastAmount:  lastAmount,\n            lastUpdated: lastUpdated\n        });\n\n        emit RateLimitDataSet(key, maxAmount, slope, lastAmount, lastUpdated);\n    }\n\n    function setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope) external override {\n        setRateLimitData(key, maxAmount, slope, maxAmount, block.timestamp);\n    }\n```","contentHash":"8ad154718350805bbb3472f1fbd4c9ac76bc609adc0564afa974a040128f272d","addressRefs":[]},"533d7220-75e3-43aa-8f1b-5512fdb9b828":{"id":"533d7220-75e3-43aa-8f1b-5512fdb9b828","doc_no":"A.6.1.1.2.2.6.1.2.2.1.3.3","title":"Set Unlimited RateLimit","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5915,"content":"The following code sets out instructions for the operator to set an unlimited `RateLimit` for a specific key:\n\n```\nfunction setUnlimitedRateLimitData(bytes32 key) external override {\n        setRateLimitData(key, type(uint256).max, 0, type(uint256).max, block.timestamp);\n```","contentHash":"a15f532e5596116bc6348a54ad1bc2f66083fa758ab7741f901daa0baefbb293","addressRefs":[]},"bc991d91-b79f-488c-b5d7-d632898c676e":{"id":"bc991d91-b79f-488c-b5d7-d632898c676e","doc_no":"A.6.1.1.2.2.6.1.2.2.1.3.4","title":"Set Trigger For RateLimit Decrease","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5916,"content":"The following code sets out instructions for the operator to trigger a decrease of a `RateLimit` for a specific key:\n\n```\nfunction triggerRateLimitDecrease(bytes32 key, uint256 amountToDecrease)\n        external override onlyRole(CONTROLLER) returns (uint256 newLimit)\n    {\n        RateLimitData storage d = _data[key];\n        uint256 maxAmount = d.maxAmount;\n\n        require(maxAmount > 0, \"RateLimits/zero-maxAmount\");\n        if (maxAmount == type(uint256).max) return type(uint256).max;  // Special case unlimited\n\n        uint256 currentRateLimit = getCurrentRateLimit(key);\n\n        require(amountToDecrease <= currentRateLimit, \"RateLimits/rate-limit-exceeded\");\n\n        d.lastAmount = newLimit = currentRateLimit - amountToDecrease;\n        d.lastUpdated = block.timestamp;\n\n        emit RateLimitDecreaseTriggered(key, amountToDecrease, currentRateLimit, newLimit);\n    }\n```","contentHash":"551f31c21344d606c3b5ffe10a2b607aecea098b75d113c9f791f1c147f35f82","addressRefs":[]},"d1dbab82-8be1-41f4-a4a3-ddc3cd0a917c":{"id":"d1dbab82-8be1-41f4-a4a3-ddc3cd0a917c","doc_no":"A.6.1.1.2.2.6.1.2.2.1.3.5","title":"Set Trigger For RateLimit Increase","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5917,"content":"The following code sets out instructions for the operator to trigger an increase of a `RateLimit` for a specific key:\n\n```\nfunction triggerRateLimitIncrease(bytes32 key, uint256 amountToIncrease)\n        external override onlyRole(CONTROLLER) returns (uint256 newLimit)\n    {\n        RateLimitData storage d = _data[key];\n        uint256 maxAmount = d.maxAmount;\n\n        require(maxAmount > 0, \"RateLimits/zero-maxAmount\");\n        if (maxAmount == type(uint256).max) return type(uint256).max;  // Special case unlimited\n\n        uint256 currentRateLimit = getCurrentRateLimit(key);\n\n        d.lastAmount = newLimit = _min(currentRateLimit + amountToIncrease, maxAmount);\n        d.lastUpdated = block.timestamp;\n\n        emit RateLimitIncreaseTriggered(key, amountToIncrease, currentRateLimit, newLimit);\n```","contentHash":"f2897f1ca340a3c532410b62a8e750acf1b70691e7576e4966ea6e320d5fb324","addressRefs":[]},"7402f24b-ee72-4b19-9690-fceec083c7e9":{"id":"7402f24b-ee72-4b19-9690-fceec083c7e9","doc_no":"A.6.1.1.2.2.6.1.2.2.1.4","title":"Instance Lifecycle Management","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5918,"content":"The documents herein define processes for invoking (onboarding) new Grove Liquidity Layer Instances and offboarding existing ones. This process will be specified in a future iteration of the Grove Artifact.","contentHash":"c728c884af21234b7fb4907be2d85a348935a303b7cd6e17694fcc85a6276882","addressRefs":[]},"3b49838e-423b-42b9-b3ca-2365e8e68725":{"id":"3b49838e-423b-42b9-b3ca-2365e8e68725","doc_no":"A.6.1.1.2.2.6.1.2.2.1.5","title":"Upgrading Controller","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5919,"content":"The documents herein define the process for deploying new Controller contracts. This process will be specified in a future iteration of the Grove Artifact.","contentHash":"06576f6353ad60cb85841255e91a53f7f0915932a92b00c517087fb9e036ec40","addressRefs":[]},"92908b02-e1eb-4c14-b44e-92968cccd881":{"id":"92908b02-e1eb-4c14-b44e-92968cccd881","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6","title":"Tokenized Treasury Role Hierarchy And Permissions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5920,"content":"The documents herein define the roles and permissions on Tokenized Treasury Instances of the Allocation System Primitive.","contentHash":"65c2521d55c4a26050143ca1ad3bf3c8c34dd3b0c6e43e31e4be16f8cc5890d4","addressRefs":[]},"41a7e6fb-59e1-40e8-a05a-68c1520fb361":{"id":"41a7e6fb-59e1-40e8-a05a-68c1520fb361","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.1","title":"Tokenized Treasury Owner Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5921,"content":"The `OWNER_ROLE` on a Tokenized Treasury Instance is authorized to set purchase and redemption fee rates within bounds established by the `MANAGER_ADMIN_ROLE`, and to grant or revoke any role in the contract. The `OWNER_ROLE` is held by an OpenZeppelin `TimelockController` operated by the credit token issuer. The Timelock address and the holders of its `PROPOSER_ROLE` are specified in each Instance Configuration Document. The holders of the Timelock's `EXECUTOR_ROLE` and `CANCELLER_ROLE` are specified in [A.6.1.1.2.2.6.1.2.2.1.6.7 - Tokenized Treasury Owner Timelock Executor Role](35e4cd97-0d88-4a47-8fbe-487c48ecc92e) and [A.6.1.1.2.2.6.1.2.2.1.6.8 - Tokenized Treasury Owner Timelock Canceller Role](0ff6a176-d3c5-45c6-a55a-5fec89d3c709).","contentHash":"f428223c74ac4b3c598d93d7ef227441b0d43494bd1f4e8e4461c22bf04fb212","addressRefs":[]},"4554fa6d-a03a-488d-a37e-a3be7b72323e":{"id":"4554fa6d-a03a-488d-a37e-a3be7b72323e","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.2","title":"Tokenized Treasury Manager Admin Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5922,"content":"The `MANAGER_ADMIN_ROLE` on a Tokenized Treasury Instance is authorized to configure rate providers, bounds for maximum swap size, oracle staleness, and fees, the Pocket contract, authorized redeemer contracts, and the fee claimer. The `MANAGER_ADMIN_ROLE` manages role assignments for the `MANAGER_ROLE`, `PAUSER_ROLE`, `REDEEMER_CONTRACT_ROLE`, and `REDEEMER_ROLE`. The `MANAGER_ADMIN_ROLE` is held by the Grove Proxy at `0x1369f7b2b38c76B6478c0f0E66D94923421891Ba` across all Tokenized Treasury Instances.","contentHash":"b3efa1e46bc00659de3290b72f3a49d98f07c7cf4191eeaf30eaff4d46f4a8cf","addressRefs":["0x1369f7b2b38c76b6478c0f0e66d94923421891ba"]},"191435aa-436b-4ef9-a95a-2357a314be01":{"id":"191435aa-436b-4ef9-a95a-2357a314be01","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.3","title":"Tokenized Treasury Manager Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5923,"content":"The `MANAGER_ROLE` on a Tokenized Treasury Instance is authorized to adjust the maximum swap size and oracle staleness threshold within bounds established by the `MANAGER_ADMIN_ROLE`. The `MANAGER_ROLE` is held by the Grove Relayer Multisig at `0x0eEC86649E756a23CBc68d9EFEd756f16aD5F85f` across all Tokenized Treasury Instances.","contentHash":"058803965940650109a6e09fcb85c338afb1fcab2dfeb04653aac0dce5ea9408","addressRefs":["0x0eec86649e756a23cbc68d9efed756f16ad5f85f"]},"abdc489a-6478-4e2a-9f22-423fd71d3700":{"id":"abdc489a-6478-4e2a-9f22-423fd71d3700","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.4","title":"Tokenized Treasury Pauser Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5924,"content":"The `PAUSER_ROLE` on a Tokenized Treasury Instance is authorized to pause or unpause individual swap directions, credit token deposits and withdrawals, or all contract operations. The `PAUSER_ROLE` is held by the Freezer Multisig at `0xB0113804960345fd0a245788b3423319c86940e5` across all Tokenized Treasury Instances.","contentHash":"09788a81763255e5e870ec00240bda4c8f43d3390d525eb7cec344df49009dd5","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"fbeb1921-37eb-465b-97fa-004c8e0925b1":{"id":"fbeb1921-37eb-465b-97fa-004c8e0925b1","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.5","title":"Tokenized Treasury Redeemer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5925,"content":"The `REDEEMER_ROLE` on a Tokenized Treasury Instance is authorized to initiate and complete the two-step redemption of credit tokens back into collateral tokens through an authorized redeemer contract. The `REDEEMER_ROLE` is controlled by the credit token issuer; the holder address is specified in each Instance Configuration Document.","contentHash":"4704ea2f79506869765355e5bd12b82733fb17e2609722b08356539b181788ae","addressRefs":[]},"493bc01d-1c2e-4ef1-8605-1183c77a8cf2":{"id":"493bc01d-1c2e-4ef1-8605-1183c77a8cf2","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.6","title":"Tokenized Treasury Redeemer Contract Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5926,"content":"The `REDEEMER_CONTRACT_ROLE` on a Tokenized Treasury Instance is granted to authorized redeemer contracts that execute the two-step redemption of credit tokens on behalf of holders of the `REDEEMER_ROLE`. `REDEEMER_CONTRACT_ROLE` holders are added and removed via the `addTokenRedeemer` and `removeTokenRedeemer` functions, which are authorized for the `MANAGER_ADMIN_ROLE`.","contentHash":"23259103edd6663236883c7f639c8e9c4d4d5064ec021a447e9602202e228da2","addressRefs":[]},"35e4cd97-0d88-4a47-8fbe-487c48ecc92e":{"id":"35e4cd97-0d88-4a47-8fbe-487c48ecc92e","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.7","title":"Tokenized Treasury Owner Timelock Executor Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5927,"content":"The `EXECUTOR_ROLE` on the OpenZeppelin `TimelockController` holding the `OWNER_ROLE` of a Tokenized Treasury Instance is authorized to execute queued operations once the Timelock delay period has elapsed. Across Tokenized Treasury Instances, this role is held by the Grove Proxy at `0x1369f7b2b38c76B6478c0f0E66D94923421891Ba`.","contentHash":"7d2d1183a992b354f6d9acd23dc8747fda22559c35aadf1724619414fc6e05cb","addressRefs":["0x1369f7b2b38c76b6478c0f0e66d94923421891ba"]},"0ff6a176-d3c5-45c6-a55a-5fec89d3c709":{"id":"0ff6a176-d3c5-45c6-a55a-5fec89d3c709","doc_no":"A.6.1.1.2.2.6.1.2.2.1.6.8","title":"Tokenized Treasury Owner Timelock Canceller Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5928,"content":"The `CANCELLER_ROLE` on the OpenZeppelin `TimelockController` holding the `OWNER_ROLE` of a Tokenized Treasury Instance is authorized to cancel queued Timelock operations before execution. Across Tokenized Treasury Instances, this role is held by the Freezer Multisig at `0xB0113804960345fd0a245788b3423319c86940e5`.","contentHash":"3506bde7a1b9d0dfe9dc63ddc7b093165d41da2a7f4186583ff463c650b04540","addressRefs":["0xb0113804960345fd0a245788b3423319c86940e5"]},"7a8f34ed-ae14-4c93-94d2-9d08c4d18e82":{"id":"7a8f34ed-ae14-4c93-94d2-9d08c4d18e82","doc_no":"A.6.1.1.2.2.6.1.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5929,"content":"The documents herein define the process for non-routine ongoing management of the Grove Liquidity Layer and its active Instances.","contentHash":"dfae7ab9cac1de78d45b18dd0dc5f6c1207178facb7814b523bfefdf323747ea","addressRefs":[]},"7ed2b9e8-1a29-421c-9186-d62ad6ffce50":{"id":"7ed2b9e8-1a29-421c-9186-d62ad6ffce50","doc_no":"A.6.1.1.2.2.6.1.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5930,"content":"The documents herein define all the possible actions that can be taken in case of an emergency within Grove Liquidity Layer operations.","contentHash":"5e654cf4c34ef17ef2f520e831ccc9dc89525c8c329ae7a2a758744556ebc494","addressRefs":[]},"53ff94d4-d7b5-4696-a66e-f6102deef3ac":{"id":"53ff94d4-d7b5-4696-a66e-f6102deef3ac","doc_no":"A.6.1.1.2.2.6.1.2.2.3.1","title":"Remove Compromised Relayer As Freezer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5931,"content":"In the event of a compromised Relayer, the `FREEZER_ROLE` can call the function to `removeRelayer` from the Controller contract. This function takes an address, and then the Freezer can remove the compromised Relayer, thereby preventing it from doing any harm to the system. The backstop relayer can then take over. This function should only be used if the keys to the relayer multisig have been leaked or compromised, and the relayer is now in the hands of an external bad actor.\n\n`mainnetController.removeRelayer(compromisedRelayer)`","contentHash":"8078ea8d196688f48ef19c5d259035c21615ce8ccd53856b0f87b469189f655d","addressRefs":[]},"550a6aa3-88b8-4b5a-a614-e06099d6898a":{"id":"550a6aa3-88b8-4b5a-a614-e06099d6898a","doc_no":"A.6.1.1.2.2.6.1.2.2.3.2","title":"Redeem All Mainnet Positions","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5932,"content":"The documents herein define the actions that should be performed by an operator if there is a need to recover the liquidity from Mainnet Protocols and centralize it in the Mainnet Grove ALM Proxy.","contentHash":"fa41538eb605cd847f94e6a76ce412b875a620dbd05aabd3f74ea2030305bc21","addressRefs":[]},"8991b422-bd6b-4ea1-b0b9-b787ee4b1000":{"id":"8991b422-bd6b-4ea1-b0b9-b787ee4b1000","doc_no":"A.6.1.1.2.2.6.1.2.2.3.2.1","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5933,"content":"In order to withdraw all ERC-4626 balances, the operator must execute the following action:\n\n```\nmainnetController.redeemERC4626(address(token), token.balanceOf(address(proxy)))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.2.2.6.1.2.2.1.2.1.2.2.2 - General Withdraw from ERC-4626 Tokens Procedure](7b560160-e427-45a2-a3ac-3c23cf6fe943) and [A.6.1.1.2.2.6.1.2.2.1.2.1.2.2.3 - General Redeem from ERC-4626 Tokens Procedure](7e90e505-42b9-474d-9cc5-9b4da6af7375).","contentHash":"69bd2a601d3c8edad8553b3b75515c526791887d52c55d6e744abb5576390231","addressRefs":[]},"03c4e450-6fbf-4194-9620-43e253379aa9":{"id":"03c4e450-6fbf-4194-9620-43e253379aa9","doc_no":"A.6.1.1.2.2.6.1.2.2.3.3","title":"USDC to USDS Swap Action","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5934,"content":"This document defines the action that should be performed by an operator if there is a need to centralize all recovered liquidity in USDS.\n\n```\nmainnetController.swapUSDCToUSDS(usdc.balanceOf(address(proxy))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.2.2.6.1.2.2.1.2.1.2.3.2 - Swap USDC to USDS](1ec9a718-44f4-4ce9-97b3-bebeb207b280).","contentHash":"0ae926bb07a76ceda03a06b7aa643f12531f33ae31f04fdce415effd67da7e1a","addressRefs":[]},"c0bc880f-818c-44cc-a02a-d66c01443a39":{"id":"c0bc880f-818c-44cc-a02a-d66c01443a39","doc_no":"A.6.1.1.2.2.6.1.2.2.3.4","title":"USDS Burn Action","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5935,"content":"This document defines the action that should be performed if there is a need to repay and then burn Grove’s USDS debt.\n\n```\nmainnetController.burnUSDS(usds.balanceOf(address(proxy))\n```\nMore detailed instructions on the code to execute this, see [A.6.1.1.2.2.6.1.2.2.1.2.1.2.1.2 - Burn USDS](25706c25-2b74-486e-8234-c45f6630f379).","contentHash":"bb9dc52824ba2a5b12a3013816652faa3c84e5444e546eedecf425a26fe102c4","addressRefs":[]},"0806984d-5799-4c19-8eda-d355bcc43524":{"id":"0806984d-5799-4c19-8eda-d355bcc43524","doc_no":"A.6.1.1.2.2.6.1.2.3","title":"Allocation Strategy","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5936,"content":"In the future, additional logic will be added herein regarding the strategy by which capital is allocated between different Instances of the Grove Liquidity Layer.","contentHash":"9a384f4229ddcaf5c87ad512d50848c2889c057bcefa980858c2ee60c2f3e595","addressRefs":[]},"1f16c7b1-eddf-4106-85f7-3425bf67ef1e":{"id":"1f16c7b1-eddf-4106-85f7-3425bf67ef1e","doc_no":"A.6.1.1.2.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5937,"content":"The Instances of the Grove Liquidity Layer with `Active` Status are stored herein. The `RRC Framework Full Implementation` status defines whether the Instance Financial RRC is calculated based on a fully implemented risk model (see [A.3.2.1.1.4.3.1 - Fully Implemented Risk Models](419a1d00-fbae-4d26-bd47-8f57677d8001)) or a pending risk model (see [A.3.2.1.1.4.3.2 - Pending Risk Models](81ca88bf-3f6a-4d10-a3e2-d47cf6636d7d)). If the Instance Financial RRC is calculated based on a fully implemented risk model the status is `Covered`. If the Instance Financial RRC is calculated based on a pending risk model the status is `Pending`.","contentHash":"4344ef8a7e7863e35ee3bdd2725992a4a494afcb42555f2c28cbd2dfe4b77721","addressRefs":[]},"25fe7f58-6025-4498-8847-5ac6330e8b2c":{"id":"25fe7f58-6025-4498-8847-5ac6330e8b2c","doc_no":"A.6.1.1.2.2.6.1.3.1","title":"Ethereum Mainnet Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5938,"content":"The Ethereum Mainnet Instances of the Grove Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"66d824a2e51875206cec9da77ff795bfcf422473939d2e21c187e27cd65d7afa","addressRefs":[]},"422e75c6-bb9e-4a2f-b58c-bfbd0ede789d":{"id":"422e75c6-bb9e-4a2f-b58c-bfbd0ede789d","doc_no":"A.6.1.1.2.2.6.1.3.1.1","title":"Centrifuge","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5939,"content":"The Ethereum Mainnet Instances of the Centrifuge Protocol with `Active` Status are stored herein.","contentHash":"f9cec93e190903ec4560d4e6e8fb4b10dfa1a82fc911b18748ffa06797caa904","addressRefs":[]},"292d1098-9fe4-481f-a3e7-72e345bdca81":{"id":"292d1098-9fe4-481f-a3e7-72e345bdca81","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1","title":"Ethereum Mainnet - Centrifuge JTRSY Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5940,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge JTRSY Instance.","contentHash":"ac20bee363ce023754729280d304dd89cdf76ddf5720dd72e0e02226d8d811bb","addressRefs":[]},"b2981f26-c563-4014-8460-36b74905a2a9":{"id":"b2981f26-c563-4014-8460-36b74905a2a9","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5941,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"3609697d-1d35-4dbf-ab8e-fcebfbc258f4":{"id":"3609697d-1d35-4dbf-ab8e-fcebfbc258f4","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5942,"content":"The documents herein define the parameters of the Centrifuge JTRSY Instance of the Allocation System Primitive.","contentHash":"7e5222005db9b113d00b229acfc5e6f1894d3676cfc4d1a6930b44c771130860","addressRefs":[]},"a43153dc-fe0a-49bc-84c7-1fd8fadf1c8e":{"id":"a43153dc-fe0a-49bc-84c7-1fd8fadf1c8e","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5943,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"2c0d8ede-45bc-4e75-8931-5ddfccf24a02":{"id":"2c0d8ede-45bc-4e75-8931-5ddfccf24a02","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5944,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"ec81f2d8-5050-4b1b-9acf-bb25574c71c7":{"id":"ec81f2d8-5050-4b1b-9acf-bb25574c71c7","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5945,"content":"Centrifuge","contentHash":"15a808e2563fe8cc5805166b2619e590c1f1e9c1b0d43c0b85783ad6dc26b9dc","addressRefs":[]},"6213ce59-e16a-41be-9f80-7ba335c0dd7b":{"id":"6213ce59-e16a-41be-9f80-7ba335c0dd7b","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5946,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"38e94216-daa1-4e05-bb5f-66c282c19d46":{"id":"38e94216-daa1-4e05-bb5f-66c282c19d46","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5947,"content":"JTRSY","contentHash":"a5435fae1627abed97fa9fff2bc126b9fa56b41fa129c9ce2c4e07c41c58f5aa","addressRefs":[]},"29fe2123-0565-4ba0-95d0-9de487877441":{"id":"29fe2123-0565-4ba0-95d0-9de487877441","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5948,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"39cf2050-ef55-49d4-b59d-fc1b0a11ac59":{"id":"39cf2050-ef55-49d4-b59d-fc1b0a11ac59","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5949,"content":"`0xFE6920eB6C421f1179cA8c8d4170530CDBdfd77A`","contentHash":"31a8cbaf6080390ffbff32697960927119a71d7a63ceefe697f351346a34ce9f","addressRefs":["0xfe6920eb6c421f1179ca8c8d4170530cdbdfd77a"]},"fbe40152-f7e6-4a4e-87ed-4e419687e40d":{"id":"fbe40152-f7e6-4a4e-87ed-4e419687e40d","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5950,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"2ecfcbd7-953a-44f8-b964-083f238b2da9":{"id":"2ecfcbd7-953a-44f8-b964-083f238b2da9","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5951,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"44eccfe2-b96a-4b76-bd9d-9a28aee10fb7":{"id":"44eccfe2-b96a-4b76-bd9d-9a28aee10fb7","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5952,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"9af18990-c582-46f9-a78e-0c4e4ce233fc":{"id":"9af18990-c582-46f9-a78e-0c4e4ce233fc","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5953,"content":"The inflow rate limits are:\n- `maxAmount`: 500,000,000 USDC\n- `slope`: 500,000,000 USDC per day","contentHash":"024265e01fe4cb6a1e95bf53913ea28ed6da321ca70b55390f14fd83daea756a","addressRefs":[]},"ad10bea9-b609-4be9-bce8-56aba87da4c9":{"id":"ad10bea9-b609-4be9-bce8-56aba87da4c9","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5954,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"7d0e7474-55c1-46b8-b283-917171b72081":{"id":"7d0e7474-55c1-46b8-b283-917171b72081","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5955,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"d5d38c79-1333-4772-9db9-6b3cf7d213b0":{"id":"d5d38c79-1333-4772-9db9-6b3cf7d213b0","doc_no":"A.6.1.1.2.2.6.1.3.1.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5956,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"10f4641c-2ed1-4430-ae71-1e830e779269":{"id":"10f4641c-2ed1-4430-ae71-1e830e779269","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2","title":"Ethereum Mainnet - Centrifuge JAAA Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5957,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge JAAA Instance.","contentHash":"9b4c70bbc51698cda24fa4e40823390d7f37438500ed2d0573e60041866c285b","addressRefs":[]},"05a8b7ae-7274-4ff7-a6f3-c7df85c2e591":{"id":"05a8b7ae-7274-4ff7-a6f3-c7df85c2e591","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5958,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"2318f007-26bf-463a-a275-535188ecb1b0":{"id":"2318f007-26bf-463a-a275-535188ecb1b0","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5959,"content":"The documents herein define the parameters of the Centrifuge JAAA Instance of the Allocation System Primitive.","contentHash":"194a5bc7c33c622c5cbbdd1abf1077ebcc1a09ac39958e616244b148049d090e","addressRefs":[]},"e1b41201-bf02-4c0b-a248-6f8e90f3e25f":{"id":"e1b41201-bf02-4c0b-a248-6f8e90f3e25f","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5960,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"c80c1dbe-6f51-4877-aea6-98ae4959fa80":{"id":"c80c1dbe-6f51-4877-aea6-98ae4959fa80","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5961,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"38eee5f5-3e8a-4519-9370-cfe95d807c69":{"id":"38eee5f5-3e8a-4519-9370-cfe95d807c69","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5962,"content":"Centrifuge","contentHash":"15a808e2563fe8cc5805166b2619e590c1f1e9c1b0d43c0b85783ad6dc26b9dc","addressRefs":[]},"a7002c17-f04c-4c77-9c36-0882c97b132f":{"id":"a7002c17-f04c-4c77-9c36-0882c97b132f","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5963,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"684afb30-ebb4-4928-829d-8f9f0001f3e6":{"id":"684afb30-ebb4-4928-829d-8f9f0001f3e6","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5964,"content":"JAAA","contentHash":"efcb18475852eaceb2beb8c102e6a4a0ea4c3b493859f247384dd7d3725815a6","addressRefs":[]},"12e79979-2299-4d8b-9aef-d7cd07868007":{"id":"12e79979-2299-4d8b-9aef-d7cd07868007","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5965,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"fe31ba7d-30cc-4fec-b74a-0dea0f633730":{"id":"fe31ba7d-30cc-4fec-b74a-0dea0f633730","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5966,"content":"`0x4880799eE5200fC58DA299e965df644fBf46780B`","contentHash":"2c8240690de0b222a5315a61ccfe888a273dd0df6399ac18221a3d9241480206","addressRefs":["0x4880799ee5200fc58da299e965df644fbf46780b"]},"14d69bb4-b7a8-4780-8563-4a798768d8b3":{"id":"14d69bb4-b7a8-4780-8563-4a798768d8b3","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5967,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"f5a93d42-0c5d-4065-9a36-d900d4798ee4":{"id":"f5a93d42-0c5d-4065-9a36-d900d4798ee4","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5968,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"d408bd88-f680-4696-912a-5918bb08cc83":{"id":"d408bd88-f680-4696-912a-5918bb08cc83","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5969,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"52d37b01-d8f2-4b9f-b251-c0f6e025c078":{"id":"52d37b01-d8f2-4b9f-b251-c0f6e025c078","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5970,"content":"The inflow rate limits are:\n\n- `maxAmount`: 100,000,000 USDC.\n- `slope`(per day): 50,000,000 USDC.","contentHash":"07824e43185900f4ec59f27d805df813b28d3912dba0162d109e704e02d5d3e9","addressRefs":[]},"f8705bd9-bc30-49c5-89fa-b529ebaee123":{"id":"f8705bd9-bc30-49c5-89fa-b529ebaee123","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5971,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"b600285512240f72e900c37ed9f60568499d3974a34f419964db51282cee8e36","addressRefs":[]},"6a41f1e9-8e61-4598-9a37-4f504fb50019":{"id":"6a41f1e9-8e61-4598-9a37-4f504fb50019","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5972,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"44c38f07-4f72-41fd-832c-ce06c2d514e0":{"id":"44c38f07-4f72-41fd-832c-ce06c2d514e0","doc_no":"A.6.1.1.2.2.6.1.3.1.1.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5973,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"b0d889d1-8465-4229-ba69-ca4b5d866131":{"id":"b0d889d1-8465-4229-ba69-ca4b5d866131","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3","title":"Ethereum Mainnet - Centrifuge ACRDX Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5974,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge ACRDX Instance.","contentHash":"cebf2e4556f73712f15fc95b450654b7501cb7a2b2b0179e5a0c9cf9af38c20d","addressRefs":[]},"7c02c1e6-c967-44cd-bebe-7b5adb071484":{"id":"7c02c1e6-c967-44cd-bebe-7b5adb071484","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5975,"content":"`Pending`","contentHash":"2986effe9fae335e819f546d8f69212a5a1e8bd5f01a449e4e295a5dee70536f","addressRefs":[]},"1c2f901d-4128-4bc6-b369-f31e568b3087":{"id":"1c2f901d-4128-4bc6-b369-f31e568b3087","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5976,"content":"The documents herein define the parameters of the Centrifuge ACRDX Instance of the Allocation System Primitive.","contentHash":"8629f541cfc64a25f28bf720a721ae40fa774c2c185a92fadf441b28917ffc53","addressRefs":[]},"b88a0c50-f937-40e1-85a4-293a0f11b534":{"id":"b88a0c50-f937-40e1-85a4-293a0f11b534","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5977,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"91a95c0d-32d2-404d-b4c8-9f02398080f2":{"id":"91a95c0d-32d2-404d-b4c8-9f02398080f2","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5978,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"71aa102a-e0cb-4c5b-a3cb-0a5200d83c2b":{"id":"71aa102a-e0cb-4c5b-a3cb-0a5200d83c2b","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5979,"content":"Centrifuge ACRDX","contentHash":"c9a585a7ef99fbf427d1c8c597dbf5cb50d5a468c469e5ddf02899e9725a6476","addressRefs":[]},"76fca48e-a4c4-4253-9c14-f3835d906d44":{"id":"76fca48e-a4c4-4253-9c14-f3835d906d44","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5980,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"a0fe0b4a-851e-4a3b-b040-309cb3ba23d2":{"id":"a0fe0b4a-851e-4a3b-b040-309cb3ba23d2","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5981,"content":"ACRDX","contentHash":"fcd923d00ef573039593aedb4cd2a4b39200665150cb21279b5c6de004a68870","addressRefs":[]},"c11a5f0f-11da-46e6-a08f-5e6722207bfe":{"id":"c11a5f0f-11da-46e6-a08f-5e6722207bfe","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5982,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"af5632c6-6a6f-4692-8cf4-3d4e8b617dc8":{"id":"af5632c6-6a6f-4692-8cf4-3d4e8b617dc8","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5983,"content":"`0x9477724Bb54AD5417de8Baff29e59DF3fB4DA74f`","contentHash":"093e4cc20577622cdd8634cac6d265c870e46cfb5ed47f1d4c5f86408c0629b5","addressRefs":["0x9477724bb54ad5417de8baff29e59df3fb4da74f"]},"a6946602-348a-408a-9cbf-d566efe96cbf":{"id":"a6946602-348a-408a-9cbf-d566efe96cbf","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.2.2","title":"Deposit Address (Mainnet)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5984,"content":"`0x74A739EA1Dc67c5a0179ebad665D1D3c4b80B712`","contentHash":"085b4041df19766a89531de579205dd7e3ebd91041f3a7cd17ccbedf55bed329","addressRefs":["0x74a739ea1dc67c5a0179ebad665d1d3c4b80b712"]},"904c9554-0fff-4d9d-9993-bf4c281e02c4":{"id":"904c9554-0fff-4d9d-9993-bf4c281e02c4","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.2.3","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5985,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"5b60c33b-7a48-43a7-bb78-0cd2e03f0079":{"id":"5b60c33b-7a48-43a7-bb78-0cd2e03f0079","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5986,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"bb056a14-2a9f-41ef-9226-3beb5867592c":{"id":"bb056a14-2a9f-41ef-9226-3beb5867592c","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5987,"content":"The inflow RateLimitID is: `0xb8139d1c2486c30929b3cb3a487a3d9c3885f49cff1f07e9393262b15ef1158a`","contentHash":"e19a197fd695d9c66f275d7e370816c9cae3cd5e2b48797c2e2abecea415b77c","addressRefs":[]},"6c04d78a-61d7-4e9a-b156-ef08168704f7":{"id":"6c04d78a-61d7-4e9a-b156-ef08168704f7","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5988,"content":"The outflow RateLimitID is: `0x58aa7b39a6c9894ea4a4cd6868d014c718d09913cdf5d793e21509f0ccd32495`","contentHash":"924ba917d465f8290c692fc224ba089dfa6e2b1ea947ef766302dc86b8aeebce","addressRefs":[]},"fb4b9380-ecef-4d3c-a2b0-6b2af6a960a9":{"id":"fb4b9380-ecef-4d3c-a2b0-6b2af6a960a9","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5989,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"2305ac7b-a8dc-4611-b242-0996d4d22a88":{"id":"2305ac7b-a8dc-4611-b242-0996d4d22a88","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5990,"content":"The deposit rate limits are:\n\n- `maxAmount`: 20,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"ffdc79e6800e455c82d3ce02c5697652fcbe21fc1d3fa74a4f01206f02d8fcf1","addressRefs":[]},"512819c7-6e39-4bdc-add6-0fc892f54ccb":{"id":"512819c7-6e39-4bdc-add6-0fc892f54ccb","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5991,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"2fad60e4-4c86-48b7-a7b9-0c0f0ef88459":{"id":"2fad60e4-4c86-48b7-a7b9-0c0f0ef88459","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5992,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"96e8ca2f-4e71-4ab0-ba0f-1958ea8e637b":{"id":"96e8ca2f-4e71-4ab0-ba0f-1958ea8e637b","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.2.5.1","title":"Maximum Exposure","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5993,"content":"Total ACRDX exposure may not exceed 50.97 million USDS and should be reduced to zero over time.","contentHash":"299a9ce816daad26668ffa93b3506acb6400262a9cfba61287b4050ac0f49bca","addressRefs":[]},"1faafb47-66b2-49a4-abf5-5cd6f1555361":{"id":"1faafb47-66b2-49a4-abf5-5cd6f1555361","doc_no":"A.6.1.1.2.2.6.1.3.1.1.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5994,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"acbe1bed-7639-45a4-9a5d-73c7d434bd0a":{"id":"acbe1bed-7639-45a4-9a5d-73c7d434bd0a","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4","title":"Ethereum Mainnet - Centrifuge JTRSY USDS Vault Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5995,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge JTRSY USDS Vault Instance.","contentHash":"6e97079ac44caf0580b13b6fd9412117cfac58be9521fae6b6a2015e9c2a99ac","addressRefs":[]},"72120c5a-c08c-40cf-935e-eb4c28649aff":{"id":"72120c5a-c08c-40cf-935e-eb4c28649aff","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5996,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"aa4c9779-aa53-47ad-9780-a9978fae5334":{"id":"aa4c9779-aa53-47ad-9780-a9978fae5334","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5997,"content":"The documents herein define the parameters of the Centrifuge JTRSY USDS Vault Instance of the Allocation System Primitive.","contentHash":"476ad8174da4a787227a859fc67a9d5d25fd9da07b0f03276d9e38a46a8f7664","addressRefs":[]},"e0b55a83-1e4c-4f6b-bd92-fe334bc220e5":{"id":"e0b55a83-1e4c-4f6b-bd92-fe334bc220e5","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5998,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"ebe72c81-05ca-4dda-9e91-177ebcd1d83e":{"id":"ebe72c81-05ca-4dda-9e91-177ebcd1d83e","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":5999,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"aed0cab3-1498-4bd1-8361-ef4be5c06ebc":{"id":"aed0cab3-1498-4bd1-8361-ef4be5c06ebc","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6000,"content":"Centrifuge","contentHash":"15a808e2563fe8cc5805166b2619e590c1f1e9c1b0d43c0b85783ad6dc26b9dc","addressRefs":[]},"80d0c003-7941-41ad-bc2b-ed2a27446ff5":{"id":"80d0c003-7941-41ad-bc2b-ed2a27446ff5","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6001,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"a6c0d662-dbd0-44e4-9e73-a1b455629f52":{"id":"a6c0d662-dbd0-44e4-9e73-a1b455629f52","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6002,"content":"JTRSY","contentHash":"a5435fae1627abed97fa9fff2bc126b9fa56b41fa129c9ce2c4e07c41c58f5aa","addressRefs":[]},"e155bd93-6ce4-497e-8e69-abc199b6e223":{"id":"e155bd93-6ce4-497e-8e69-abc199b6e223","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6003,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"baa2fd47-b45a-4d03-9393-0351d4fa70a8":{"id":"baa2fd47-b45a-4d03-9393-0351d4fa70a8","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6004,"content":"`0x381f4F3B43C30B78C1f7777553236e57bB8AE9ff`","contentHash":"05b08f8822f27a27afbb29e7f02648890b441629cd5e5a7e6c0ffd3bcd5b627b","addressRefs":["0x381f4f3b43c30b78c1f7777553236e57bb8ae9ff"]},"9a061684-5c54-4448-bdc7-cb21578db5cb":{"id":"9a061684-5c54-4448-bdc7-cb21578db5cb","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6005,"content":"`0xdC035D45d973E3EC169d2276DDab16f1e407384F`","contentHash":"70054b0ff65437cb32b35df32f8e11d1cc8ea540e9916e08d1cd96696d95e083","addressRefs":["0xdc035d45d973e3ec169d2276ddab16f1e407384f"]},"ae198061-322e-486c-b6a3-69c9f44a0092":{"id":"ae198061-322e-486c-b6a3-69c9f44a0092","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6006,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"cef889e791f2b83bcbb0a9c31a4ac27908ed8e42d81e0663f3596e7e35abb973","addressRefs":[]},"bbb15d43-e8e6-47a1-9f26-bbd0b9a34574":{"id":"bbb15d43-e8e6-47a1-9f26-bbd0b9a34574","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6007,"content":"The inflow RateLimitID is: `0x12a7aab841b7cc5a82aa3f431a00634d363fa012c2e247229a80509ab0426359`","contentHash":"397af26dbd64abdc79a6ad9e6b923b07ea4c4efecbc1f27266f7ee55006bdcef","addressRefs":[]},"d4f11693-8a00-44ec-bc44-07b3b9e13fe7":{"id":"d4f11693-8a00-44ec-bc44-07b3b9e13fe7","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6008,"content":"The outflow RateLimitID is: `0x90f60b9802ce2da6196f5558e32abf7b583c646525d836146bfa7938caaaa935`","contentHash":"f7397379d8d864b7715cff00251212a4fc68ecf34a59ea08e19013c9b176dd91","addressRefs":[]},"de12ee28-f435-43ce-beac-5b1ecff3b0d5":{"id":"de12ee28-f435-43ce-beac-5b1ecff3b0d5","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6009,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"aac8ee49-9414-4fe5-8594-7ecdecdaddd4":{"id":"aac8ee49-9414-4fe5-8594-7ecdecdaddd4","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6010,"content":"The inflow rate limits are:\n\n- `maxAmount`: 500,000,000 USDS\n- `slope`: 500,000,000 USDS per day","contentHash":"e1e1f6139501da2a9a4e1a0e47abbd24b0e85e0e5eae2ee94277a04e80297841","addressRefs":[]},"a1fa5391-2481-4e75-9070-4bb11d7598df":{"id":"a1fa5391-2481-4e75-9070-4bb11d7598df","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6011,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"019ca238-986e-4033-9d81-245845a0eadd":{"id":"019ca238-986e-4033-9d81-245845a0eadd","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6012,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"35ac515f-6832-4e41-88fe-7eb32e6f2702":{"id":"35ac515f-6832-4e41-88fe-7eb32e6f2702","doc_no":"A.6.1.1.2.2.6.1.3.1.1.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6013,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"61ab2f32-60b9-459e-99d5-0e59958c8561":{"id":"61ab2f32-60b9-459e-99d5-0e59958c8561","doc_no":"A.6.1.1.2.2.6.1.3.1.2","title":"Blackrock","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6014,"content":"The Ethereum Mainnet Instances of the Blackrock Protocol with `Active` Status are stored herein.","contentHash":"1c27f687504a67d2f1c676eb2f32e175fe06c952cc0fb8f997c0434fa29edb70","addressRefs":[]},"8bc44388-0d97-4d5e-aa33-fdd1938f03ff":{"id":"8bc44388-0d97-4d5e-aa33-fdd1938f03ff","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1","title":"Ethereum Mainnet - Blackrock BUIDL-I Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6015,"content":"The documents herein contain the Instance Configuration Document for the Blackrock BUIDL-I Instance.","contentHash":"d41264b592d984e6a017a2d27338437d778656d2a7168ef61da658e99aae4895","addressRefs":[]},"b565fc42-5f82-444c-95ae-bd560cb7e0e2":{"id":"b565fc42-5f82-444c-95ae-bd560cb7e0e2","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6016,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"b2eabff0-ab16-4840-8e75-79c2f8fd9bcf":{"id":"b2eabff0-ab16-4840-8e75-79c2f8fd9bcf","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6017,"content":"The documents herein define the parameters of the Blackrock BUIDL-I Instance of the Allocation System Primitive.","contentHash":"d87a0ee05109a998fe101cbe4f13e34b8344a53f6624a2bc1e312eb717473d14","addressRefs":[]},"7bc4d289-e05c-410f-b72f-e15ab6665119":{"id":"7bc4d289-e05c-410f-b72f-e15ab6665119","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6018,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"e9ae782a-3edc-4d11-acd3-4055dc6a836c":{"id":"e9ae782a-3edc-4d11-acd3-4055dc6a836c","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6019,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"c58fffd4-4905-4749-a7fa-55b69f0f44f3":{"id":"c58fffd4-4905-4749-a7fa-55b69f0f44f3","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6020,"content":"Blackrock","contentHash":"0cf18cf9e992f4e14fdde17d1cf0ce80b7b8535f82c25cb6b406256d899a407a","addressRefs":[]},"9e20f087-373b-439c-ba49-a697c2d5e089":{"id":"9e20f087-373b-439c-ba49-a697c2d5e089","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6021,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"bab41936-4c79-4821-9e78-fd1dd6511003":{"id":"bab41936-4c79-4821-9e78-fd1dd6511003","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6022,"content":"BUIDL-I","contentHash":"2317b6f4308e52f77b18de970c662272f0e32458f7f70f9754764426c2b99e12","addressRefs":[]},"bc0020b6-33fe-4297-bd2d-950583288718":{"id":"bc0020b6-33fe-4297-bd2d-950583288718","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6023,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"2c3d5162-5aac-4b5d-838d-8bc2952b7852":{"id":"2c3d5162-5aac-4b5d-838d-8bc2952b7852","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6024,"content":"`0x6a9DA2D710BB9B700acde7Cb81F10F1fF8C89041`","contentHash":"b5f6899da4b07597ae9060770e2d13c3651c65b004e625293235ac117c1bdfaf","addressRefs":["0x6a9da2d710bb9b700acde7cb81f10f1ff8c89041"]},"45250d99-f5d0-48f7-a8b6-a92bcbb95c05":{"id":"45250d99-f5d0-48f7-a8b6-a92bcbb95c05","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6025,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"e40c4ab5-15a9-4d56-a01e-609388d38bac":{"id":"e40c4ab5-15a9-4d56-a01e-609388d38bac","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6026,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"6aeaafb3-c78d-4a20-9da7-2d88adb2f7d9":{"id":"6aeaafb3-c78d-4a20-9da7-2d88adb2f7d9","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6027,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"5edb937d-c579-42e3-ae25-821150cddda2":{"id":"5edb937d-c579-42e3-ae25-821150cddda2","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6028,"content":"The inflow rate limits are:\n\n- `maxAmount`: 50,000,000\n- `slope`(per day): 50,000,000","contentHash":"c8af31540a309234651b4e04ac05af20eb4ce406d787de4fa984b67c513ef304","addressRefs":[]},"0b80d875-47a9-4863-8cf9-7a564e49d7ff":{"id":"0b80d875-47a9-4863-8cf9-7a564e49d7ff","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6029,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"b600285512240f72e900c37ed9f60568499d3974a34f419964db51282cee8e36","addressRefs":[]},"96d4e794-64f4-428d-a4e0-294576b64856":{"id":"96d4e794-64f4-428d-a4e0-294576b64856","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6030,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"123ded95-dc31-4f9b-9240-6180be9efa8c":{"id":"123ded95-dc31-4f9b-9240-6180be9efa8c","doc_no":"A.6.1.1.2.2.6.1.3.1.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6031,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"feb10c4e-f51f-4707-8794-df0e0c28069f":{"id":"feb10c4e-f51f-4707-8794-df0e0c28069f","doc_no":"A.6.1.1.2.2.6.1.3.1.3","title":"Superstate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6032,"content":"The Ethereum Mainnet Instances of the Superstate Protocol with `Active` Status are stored herein.","contentHash":"edf73d4fc02c65e81ad84fa8724da508b0d320efa5e71aa8b0eebf2a872db41d","addressRefs":[]},"a49f5e48-6e00-434b-bd85-26539c7a9cfe":{"id":"a49f5e48-6e00-434b-bd85-26539c7a9cfe","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1","title":"Ethereum Mainnet - Superstate USTB Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6033,"content":"The documents herein contain the Instance Configuration Document for the Superstate USTB Instance.","contentHash":"343f48a7d355e7f786ac2c284cfc981fe750f28205dbe782050ae277b3e68e7e","addressRefs":[]},"b3388919-4af4-4cd8-8d2e-76ba1e35a119":{"id":"b3388919-4af4-4cd8-8d2e-76ba1e35a119","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6034,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"2b146ad3-e8ba-4aa8-99e9-73b0b8d90f36":{"id":"2b146ad3-e8ba-4aa8-99e9-73b0b8d90f36","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6035,"content":"The documents herein define the parameters of the Superstate USTB Instance of the Allocation System Primitive.","contentHash":"e847a8f4bbb217b7b0039181b46aa2f41555c9522cd3e039d025a94397a2e36a","addressRefs":[]},"671f6c1e-5bba-4e80-93b3-91cc2547dd24":{"id":"671f6c1e-5bba-4e80-93b3-91cc2547dd24","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6036,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"74595227-8083-4620-a9c2-fc7b7ccb97bf":{"id":"74595227-8083-4620-a9c2-fc7b7ccb97bf","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6037,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"02307043-77c0-40d5-bec0-cc969dc2eb1e":{"id":"02307043-77c0-40d5-bec0-cc969dc2eb1e","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6038,"content":"Superstate","contentHash":"347a9de5e7347f5b0d15d5ffe54be23087536fbdcafc045e231c3309a787113c","addressRefs":[]},"6eb81d2f-e7c0-4306-a10f-fdf38e3eed5f":{"id":"6eb81d2f-e7c0-4306-a10f-fdf38e3eed5f","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6039,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"af5bb5fe-b41f-4e8d-ad1c-8015813ad323":{"id":"af5bb5fe-b41f-4e8d-ad1c-8015813ad323","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6040,"content":"USTB","contentHash":"9a2c6aa563c2ba0c8f132c3f1df378edfeaf658d25e7666c4645977536d06011","addressRefs":[]},"cdb0f02e-2fd4-48cb-a38c-17badb67f8da":{"id":"cdb0f02e-2fd4-48cb-a38c-17badb67f8da","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6041,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"c1b16951-4e99-45a3-a89f-259c5214f26d":{"id":"c1b16951-4e99-45a3-a89f-259c5214f26d","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6042,"content":"This address will be specified in a future iteration of the Grove Artifact.","contentHash":"9389f37cd4b415cd88a767840372a9c72e712fc5000dcd2f94301551a52dc201","addressRefs":[]},"10bd480c-d536-47ec-ba10-d09b053300c4":{"id":"10bd480c-d536-47ec-ba10-d09b053300c4","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6043,"content":"This address will be specified in a future iteration of the Grove Artifact.","contentHash":"9389f37cd4b415cd88a767840372a9c72e712fc5000dcd2f94301551a52dc201","addressRefs":[]},"24a76d96-4369-476d-baa8-82f0a0276fe2":{"id":"24a76d96-4369-476d-baa8-82f0a0276fe2","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6044,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"adc16c56-8f93-4598-ae41-e6e96f16936f":{"id":"adc16c56-8f93-4598-ae41-e6e96f16936f","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6045,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"bde14e56-5d3b-4797-9ab4-6cd689d74a8c":{"id":"bde14e56-5d3b-4797-9ab4-6cd689d74a8c","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6046,"content":"The inflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Grove Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"b1cf7d477103f529280f6c3749c0902e34dc861e625a89477894fcdc05523712","addressRefs":[]},"35aaf86f-8a8e-487a-8f1d-65f263223da1":{"id":"35aaf86f-8a8e-487a-8f1d-65f263223da1","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6047,"content":"The outflow rate limits are:\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Grove Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"388b3ccf4fb18d0c6a2116cbdf5746d5bb61164ff3725f77d6c3871f86f8c83f","addressRefs":[]},"a9787ff0-1082-4e6e-b77b-b86f9a3aeade":{"id":"a9787ff0-1082-4e6e-b77b-b86f9a3aeade","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6048,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"8488e826-76ee-47bd-aee1-4fea72109903":{"id":"8488e826-76ee-47bd-aee1-4fea72109903","doc_no":"A.6.1.1.2.2.6.1.3.1.3.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6049,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"39ed1591-d474-4ed1-a794-b178d64aa948":{"id":"39ed1591-d474-4ed1-a794-b178d64aa948","doc_no":"A.6.1.1.2.2.6.1.3.1.4","title":"Ethena","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6050,"content":"The Ethereum Mainnet Instances of the Ethena Protocol with `Active` Status are stored herein.","contentHash":"a46b12fc115b5c429a0867aaa62fc9f890e2b41454c14d2cedd6a98cd7aca7ee","addressRefs":[]},"dbe15588-fa00-4573-ae8a-f69e095532f5":{"id":"dbe15588-fa00-4573-ae8a-f69e095532f5","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1","title":"Ethereum Mainnet - Ethena USDe Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6051,"content":"The documents herein contain the Instance Configuration Document for the Ethena USDe Instance.","contentHash":"d01ab446023a57350389d71ef2933997d3c15887c6ef7ba7f71671ce744615b0","addressRefs":[]},"dfd44d17-c702-4e46-84e3-4361b95696cf":{"id":"dfd44d17-c702-4e46-84e3-4361b95696cf","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6052,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"14d7c28e-1ca0-4430-a9a2-a80625b292b8":{"id":"14d7c28e-1ca0-4430-a9a2-a80625b292b8","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6053,"content":"The documents herein define the parameters of the Ethena USDe Instance of the Allocation System Primitive.","contentHash":"9d4049ea143affeca92b38cad142ac72cfd010268acd973089ce91fdf1637ce9","addressRefs":[]},"53baf614-c4e3-41e1-ae1a-7002964bafcd":{"id":"53baf614-c4e3-41e1-ae1a-7002964bafcd","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6054,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"4b9deda5-4a2a-4da3-9e03-85a04f232110":{"id":"4b9deda5-4a2a-4da3-9e03-85a04f232110","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6055,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"6f33f060-c24e-4c24-b6f8-7882bb19f7c0":{"id":"6f33f060-c24e-4c24-b6f8-7882bb19f7c0","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6056,"content":"Ethena Protocol","contentHash":"28a2ae066b62e4f0fb21dea9515c881e910e33f91c217edd740a8db8d8e0dab2","addressRefs":[]},"45b293a2-10f7-4a5e-95c0-fc7375870e78":{"id":"45b293a2-10f7-4a5e-95c0-fc7375870e78","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6057,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"8f59e11f-8e45-4daa-b47e-9034c992b840":{"id":"8f59e11f-8e45-4daa-b47e-9034c992b840","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6058,"content":"USDe","contentHash":"9613d0cae557ec7702d9883e3926c60f107d41e7349456c05d3806dd74a255b9","addressRefs":[]},"0582245f-0b92-468a-868d-d7f83269b24a":{"id":"0582245f-0b92-468a-868d-d7f83269b24a","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6059,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"7dd0f228-265b-4411-87e9-5fff688a4bae":{"id":"7dd0f228-265b-4411-87e9-5fff688a4bae","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6060,"content":"`0x4c9EDD5852cd905f086C759E8383e09bff1E68B3`","contentHash":"af8f3aca379b74340581939474b84e3badef16e17802b2b71cfa3cb6f05cb267","addressRefs":["0x4c9edd5852cd905f086c759e8383e09bff1e68b3"]},"5f107bd7-9fcb-433a-a6a6-f6db9f2f018b":{"id":"5f107bd7-9fcb-433a-a6a6-f6db9f2f018b","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6061,"content":"This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"6982bdb150df3a0968a30dbd2bbda0d395399e22ed94ffe874865fb9befc6f4a","addressRefs":[]},"be1ccf23-f306-4c8e-a43c-26fb8d8d7d1a":{"id":"be1ccf23-f306-4c8e-a43c-26fb8d8d7d1a","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.2.3","title":"EthenaMinter","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6062,"content":"`0xe3490297a08d6fC8Da46Edb7B6142E4F461b62D3`","contentHash":"c6649b3505a142e742c11a8df260a1f7d33ae2c52bfc7a72be661f1a9e6dd085","addressRefs":["0xe3490297a08d6fc8da46edb7b6142e4f461b62d3"]},"d20a3198-86da-403b-8509-4cc374a5a1ed":{"id":"d20a3198-86da-403b-8509-4cc374a5a1ed","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6063,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"f1fa0280-9862-4e66-9e4f-4c410bbdf437":{"id":"f1fa0280-9862-4e66-9e4f-4c410bbdf437","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6064,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"cb1ffa0f-bdc8-4bd5-80ce-1592429758b8":{"id":"cb1ffa0f-bdc8-4bd5-80ce-1592429758b8","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6065,"content":"The inflow rate limits are:\n\n- `maxAmount`: 250,000,000\n- `slope`: 100,000,000 per day","contentHash":"7c4f2abebd8d2ae7b05749be62e061f49b97cacc8ee3d662651e8d90fe0f4577","addressRefs":[]},"6cf9b977-565d-44f3-9400-0ad1b05f57bd":{"id":"6cf9b977-565d-44f3-9400-0ad1b05f57bd","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6066,"content":"The outflow rate limits are:\n\n- `maxAmount`: 500,000,000\n- `slope`: 200,000,000 per day","contentHash":"4e532b527954d85315d33f0736283a77814828cbe7f3e3292fb12212c4bb8d9b","addressRefs":[]},"620c1687-bf39-4e90-a9dd-ab191a66f166":{"id":"620c1687-bf39-4e90-a9dd-ab191a66f166","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6067,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"80844016-8ae5-4ea3-b4b7-970a33158425":{"id":"80844016-8ae5-4ea3-b4b7-970a33158425","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6068,"content":"The documents herein defines the operations performed to manage the Ethena Instance, including rate limiting, role-based access control, and cooldown functionality.","contentHash":"58b2397eb062afb8152fdca76b752c92b3db3807113193ab146ecbe45f82095a","addressRefs":[]},"98191437-0437-496e-ad1a-ceeba3c3b9d6":{"id":"98191437-0437-496e-ad1a-ceeba3c3b9d6","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.1","title":"Delegated Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6069,"content":"The documents herein contain the addresses authorized as `delegatedSigners` in the `ethenaMinter` contract. `delegatedSigners` are set up and removed in the `MainnetController` contract by the `Relayer` role.","contentHash":"54d5367ab740bb3a103513d78aca5d0edc975b5263610287df45d7c8ea9d3697","addressRefs":[]},"ba1c514f-026a-4ecd-bb9a-c736cca59728":{"id":"ba1c514f-026a-4ecd-bb9a-c736cca59728","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.1.1","title":"Addresses Of Delegated Signers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6070,"content":"`delegatedSigner` addresses\n\n- These addesses will be specified in a future iteration of the Spark Artifact.","contentHash":"5b9338f144d807718f415afa955c9b71dab50de745415e5a112d00a9a13fc5c1","addressRefs":[]},"18b6c02a-45bc-419d-bcb6-acbbd44f75c0":{"id":"18b6c02a-45bc-419d-bcb6-acbbd44f75c0","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.2","title":"Set A Delegated Signer In The EthenaMinter Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6071,"content":"The documents herein define the process for an operator to set a delegated signer to the EthenaMinter contract.","contentHash":"536f22c9f9effac0e19649cb0a50d5f172ce836df588f208fe7e59cf08e341f5","addressRefs":[]},"be6df08e-d837-4ad8-bce4-69adbaec2213":{"id":"be6df08e-d837-4ad8-bce4-69adbaec2213","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6072,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `setDelegatedSigner`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction setDelegatedSigner(address delegatedSigner)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"8aba311385597beba3c6e88b0cd3956f3db2d9c2ed5c79f4e1986f70d31ed92d","addressRefs":[]},"0338eae8-0c00-4eb4-858f-50d66f2c65d7":{"id":"0338eae8-0c00-4eb4-858f-50d66f2c65d7","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.2.2","title":"Encode Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6073,"content":"The operator must use `proxy.doCall()` to forward the call to the `ethenaMinter` contract and call `setDelegatedSigner` function to set the address that will be authorized as a `delegatedSigner`. To call on `ethenaMinter` contract, the function must be encoded using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(ethenaMinter),\n        abi.encodeCall(ethenaMinter.setDelegatedSigner, (address(delegatedSigner)))\n    );\n}\n```","contentHash":"0c3c7f255361938c1e6338fd220081f53c7cf2a4f34062d8a83a6243bb5e36d9","addressRefs":[]},"a9007256-ac47-4807-a3c5-3686f8b688b7":{"id":"a9007256-ac47-4807-a3c5-3686f8b688b7","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.3","title":"Remove A Delegated Signer In The Ethena Minter Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6074,"content":"The documents herein define the process for an operator to remove a delegated signer from the Ethena Minter contract.","contentHash":"1a1164093641b73d7a09a9385e332b963fff1a1f238406778a51e64cda44b798","addressRefs":[]},"55d5ce02-6dc2-49c8-a482-8b10fa24f8b6":{"id":"55d5ce02-6dc2-49c8-a482-8b10fa24f8b6","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.3.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6075,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `removeDelegatedSigner`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction removeDelegatedSigner(address delegatedSigner)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"234716df620a9ea3c1d8f770436770d50a6d81b73f966313833b2efccdf03b00","addressRefs":[]},"e3f7d68f-d4af-4809-b6c9-2457b00ec991":{"id":"e3f7d68f-d4af-4809-b6c9-2457b00ec991","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.3.2","title":"Encode Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6076,"content":"The operator must use `proxy.doCall()` to forward the call to the `ethenaMinter` contract and call `removeDelegatedSigner` function to remove the authorization for the `address` to act as a `delegatedSigner`. To call on `ethenaMinter` contract, the function must be encoded using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(ethenaMinter),\n        abi.encodeCall(ethenaMinter.removeDelegatedSigner, (address(delegatedSigner)))\n    );\n}\n```","contentHash":"d02a53fd56f9a7b6d99dc1825d43566618d4f451f67f021981116cdf80c417d4","addressRefs":[]},"704d4083-3af2-491b-93c5-0dcaf19f0927":{"id":"704d4083-3af2-491b-93c5-0dcaf19f0927","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.4","title":"Approve Minting of USDe By Ethena Minter Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6077,"content":"The documents herein define the process for an operator to approve the minting of USDe by the EthenaMinter contract.","contentHash":"418de9614e562e8591d06c18d24f7da224a6dbfbad13c132f188944599719921","addressRefs":[]},"47f20c86-d122-4ab2-a9b0-5458e4b5797f":{"id":"47f20c86-d122-4ab2-a9b0-5458e4b5797f","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.4.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6078,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `prepareUSDeMint`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction prepareUSDeMint(uint256 usdcAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"71c17f77da2d4ac63e8ce39c65eb7d17c5984d96b0e63c65d731fa707b800105","addressRefs":[]},"3b26a2c4-fb16-4f72-8b46-ca96f0352681":{"id":"3b26a2c4-fb16-4f72-8b46-ca96f0352681","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.4.2","title":"Enforce Rate Limit","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6079,"content":"The operator must enforce a rate limit on how much USDC can be approved for minting USDe.\n\n`rateLimited(LIMIT_USDE_MINT, usdcAmount)`","contentHash":"7ca7f68376be8d5ab92d9877eea510aea8071346379d9140dc8bbc4fc8497965","addressRefs":[]},"5a33accd-3e23-4e64-be97-a0a981620a6f":{"id":"5a33accd-3e23-4e64-be97-a0a981620a6f","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.4.3","title":"Encode Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6080,"content":"The operator must use `proxy.doCall()` to send an approval call to the `usdc` contract, allowing the `ethenaMinter` contract to spend up to the specified `amount` of USDC. They must encode the function using `abi.encodeCall`.\n\n```\n {\n    proxy.doCall(\n        address(usdc),\n        abi.encodeCall(usdc.approve, (address(ethenaMinter), usdcAmount))\n    );\n}\n```","contentHash":"86e78931a13e473ea511aa636dcd83a0ad8bf7acef12cf17635448be5201f623","addressRefs":[]},"ffdc8734-a58e-4298-a98e-f379862e705e":{"id":"ffdc8734-a58e-4298-a98e-f379862e705e","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.5","title":"Approve Burning of USDe By EthenaMinter Contract","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6081,"content":"The documents herein define the process for an operator to approve the burning of USDe by the EthenaMinter contract.","contentHash":"b96a6e3b9e0dfe3cfac2c3b1012ef3f80a75206d7371e4e109f6ad4a360243cc","addressRefs":[]},"5d3210e1-2ad4-440f-9c61-6adcc22abc90":{"id":"5d3210e1-2ad4-440f-9c61-6adcc22abc90","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.5.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6082,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `prepareUSDeBurn`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction prepareUSDeBurn(uint256 usdeAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"28bd44137567aab7c0f230706822093dd7d7b334ee2244e4b379b334fcc2d723","addressRefs":[]},"e2f185ba-fcd6-4f46-8f7e-9b09c111a75d":{"id":"e2f185ba-fcd6-4f46-8f7e-9b09c111a75d","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.5.2","title":"Enforce Rate Limit","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6083,"content":"The operator must enforce a rate limit on how much USDe can be approved for burning.\n\n`rateLimited(LIMIT_USDE_BURN, usdeAmount)`","contentHash":"4384b668e75aed70fb58b96d7b40b659d53fd0fe945d3cd4533006ffe072f746","addressRefs":[]},"230f7b75-df50-417a-8d02-16089a5831c6":{"id":"230f7b75-df50-417a-8d02-16089a5831c6","doc_no":"A.6.1.1.2.2.6.1.3.1.4.1.3.5.3","title":"Encode Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6084,"content":"The operator must use `proxy.doCall()` to send an approval call to the `usde` contract, allowing the `ethenaMinter` contract to spend up to the specified `amount` of USDe. They must encode the function using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(usde),\n        abi.encodeCall(usde.approve, (address(ethenaMinter), usdeAmount))\n    );\n}\n```","contentHash":"e2f7b51f87aea6f0ff7c3c4f845d0bf658d68f685cf818ce3b9d22605e203b9b","addressRefs":[]},"5847fff3-ff82-4c01-ac24-7f06fac8c2a4":{"id":"5847fff3-ff82-4c01-ac24-7f06fac8c2a4","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2","title":"Ethereum Mainnet - Ethena sUSDe Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6085,"content":"The documents herein contain the Instance Configuration Document for the Ethena sUSDe Instance.","contentHash":"013709d56b596e1729075c5450c564b0cb0fdf3c05c3c6d985c16cf8a5eb0522","addressRefs":[]},"54635681-871e-4c36-8090-b55a760219ca":{"id":"54635681-871e-4c36-8090-b55a760219ca","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6086,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"b483ba5f-7570-4ab4-82e6-f8296553f3e4":{"id":"b483ba5f-7570-4ab4-82e6-f8296553f3e4","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6087,"content":"The documents herein define the parameters of the Ethena sUSDe Instance of the Allocation System Primitive.","contentHash":"bdafa68ac339ad6fcf55a243b9559fd7e3a9cd7bb8e935a99485437893c899c5","addressRefs":[]},"a544cec4-f067-477c-8cc5-f74e59d56d45":{"id":"a544cec4-f067-477c-8cc5-f74e59d56d45","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6088,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"f68d33ff-4092-46aa-92e2-e592b8f84c14":{"id":"f68d33ff-4092-46aa-92e2-e592b8f84c14","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6089,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"b31f534a-7268-4500-be69-abc662541b55":{"id":"b31f534a-7268-4500-be69-abc662541b55","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6090,"content":"Ethena Protocol","contentHash":"28a2ae066b62e4f0fb21dea9515c881e910e33f91c217edd740a8db8d8e0dab2","addressRefs":[]},"0f400550-8477-490d-bdd2-17cb3f808be1":{"id":"0f400550-8477-490d-bdd2-17cb3f808be1","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6091,"content":"USDe","contentHash":"9613d0cae557ec7702d9883e3926c60f107d41e7349456c05d3806dd74a255b9","addressRefs":[]},"c4f40f7e-84da-4cc1-8a45-9eeb27e92255":{"id":"c4f40f7e-84da-4cc1-8a45-9eeb27e92255","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6092,"content":"sUSDe","contentHash":"e401c6761be8363a66141080dd79aeb363bd7ae63a457335d764191f717f7a74","addressRefs":[]},"83e0f89d-08df-476a-bbb1-4566f69fafd4":{"id":"83e0f89d-08df-476a-bbb1-4566f69fafd4","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6093,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"002874e2-43a6-4daa-8e02-1b6f9291d02f":{"id":"002874e2-43a6-4daa-8e02-1b6f9291d02f","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6094,"content":"`0x9D39A5DE30e57443BfF2A8307A4256c8797A3497`","contentHash":"bfc04001766f78a641fffbae024f439d86f835031cab8f1bb23d43c4a6df7d80","addressRefs":["0x9d39a5de30e57443bff2a8307a4256c8797a3497"]},"be355bce-80b5-4e9d-a78f-ee5b87aa7117":{"id":"be355bce-80b5-4e9d-a78f-ee5b87aa7117","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6095,"content":"`0x4c9EDD5852cd905f086C759E8383e09bff1E68B3`","contentHash":"af8f3aca379b74340581939474b84e3badef16e17802b2b71cfa3cb6f05cb267","addressRefs":["0x4c9edd5852cd905f086c759e8383e09bff1e68b3"]},"368f88e3-5570-4a60-b15b-f4ee23519caa":{"id":"368f88e3-5570-4a60-b15b-f4ee23519caa","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.2.3","title":"EthenaMinter","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6096,"content":"`0xe3490297a08d6fC8Da46Edb7B6142E4F461b62D3`","contentHash":"c6649b3505a142e742c11a8df260a1f7d33ae2c52bfc7a72be661f1a9e6dd085","addressRefs":["0xe3490297a08d6fc8da46edb7b6142e4f461b62d3"]},"5ecd37de-d09e-438c-838a-9070c42c2802":{"id":"5ecd37de-d09e-438c-838a-9070c42c2802","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6097,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"cd0d2be7-92af-47e1-af84-efd52c36d4d9":{"id":"cd0d2be7-92af-47e1-af84-efd52c36d4d9","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6098,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"d25089f6-ed8a-4af9-adb1-9830e0daf0bc":{"id":"d25089f6-ed8a-4af9-adb1-9830e0daf0bc","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6099,"content":"The inflow rate limits are:\n\n- `maxAmount`: 250,000,000\n- `slope`: 100,000,000 per day","contentHash":"7c4f2abebd8d2ae7b05749be62e061f49b97cacc8ee3d662651e8d90fe0f4577","addressRefs":[]},"d33504c7-812f-43fb-b825-fc23aa177a3e":{"id":"d33504c7-812f-43fb-b825-fc23aa177a3e","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6100,"content":"The outflow rate limits are:\n\n- `maxAmount`: unlimited\n- `slope`: unlimited","contentHash":"d203bbdf6281d01b57bd47618604541e76fe7348908ab03b5a2ed8a8d7d37505","addressRefs":[]},"12935140-ad9b-42b4-a2e2-b84573e8ec0b":{"id":"12935140-ad9b-42b4-a2e2-b84573e8ec0b","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6101,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"e1e9bdd9-5301-4efb-80d8-ffc0b29a6ec1":{"id":"e1e9bdd9-5301-4efb-80d8-ffc0b29a6ec1","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6102,"content":"For operational processes defining the operations performed to manage the Ethena Instance, including rate limiting, role-based access control, and minting of USDe functionality see Instance-specific Operational Processes. For detailed logic specific for this instance see [A.6.1.1.2.2.6.1.3.1.4.2.3.1 - Initiate A sUSDe Cooldown Period](2e467f99-83b9-48a0-adf5-9cc5c538fb23), [A.6.1.1.2.2.6.1.3.1.4.2.3.2 - Cool Down sUSDe Shares](8f029eaf-a208-4f7c-8f00-d34b1e15ca08), [A.6.1.1.2.2.6.1.3.1.4.2.3.3 - Unstake sUSDe And Return It To ALM Proxy](bf0523c1-7c37-4073-b565-202c5497825c) and [A.6.1.1.2.2.6.1.3.1.4.2.3.4 - Emergency Procedure To Withdraw Ethena Balances](8d926497-9fe7-4189-83c8-10f649ff0b1d).","contentHash":"c22364a1759a8629c8943e1648888c2fc39587ad16708b5b02278a863c4cc0be","addressRefs":[]},"2e467f99-83b9-48a0-adf5-9cc5c538fb23":{"id":"2e467f99-83b9-48a0-adf5-9cc5c538fb23","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.1","title":"Initiate A sUSDe Cooldown Period","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6103,"content":"The documents herein define the process for an operator to initiate a sUSDe Cooldown period.","contentHash":"f80daecd5b1112e1c5a57b2fb9f8cf5f067b9f53cc6b7ffe9349d772b7737873","addressRefs":[]},"fc7b35c1-185a-41b1-83df-8d8e04349864":{"id":"fc7b35c1-185a-41b1-83df-8d8e04349864","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.1.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6104,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `cooldownAssetsSUSDe`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction cooldownAssetsSUSDe(uint256 usdeAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"4dcb2050bfb27b88451fbcc291480ca53895b1fdeb5d32d790d7c6ce4986d0d9","addressRefs":[]},"c9040dc5-3f47-4e47-861c-6ddac774ecb6":{"id":"c9040dc5-3f47-4e47-861c-6ddac774ecb6","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.1.2","title":"Enforce Rate Limit","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6105,"content":"The operator must enforce a rate limit on how much sUSDe can be cooled down.\n\n`rateLimited(LIMIT_SUSDE_COOLDOWN, usdeAmount)`","contentHash":"66229763b64764bbbde369b4676228796307a2f998650e73a86ac3b698b63c90","addressRefs":[]},"3c9e6628-3441-4d53-aed1-6dc973d8f8cc":{"id":"3c9e6628-3441-4d53-aed1-6dc973d8f8cc","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.1.3","title":"Encode Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6106,"content":"The operator must use `proxy.doCall()` to make a call to the `susde` contract, invoking the `cooldownAssets` function with the specified amount of sUSDe. They must encode the function using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(susde),\n        abi.encodeCall(susde.cooldownAssets, (usdeAmount))\n    );\n}\n```","contentHash":"67f25a96d2b15be438bda08ae22673ffd7a59ea12dd34038de512ce2263b33ef","addressRefs":[]},"8f029eaf-a208-4f7c-8f00-d34b1e15ca08":{"id":"8f029eaf-a208-4f7c-8f00-d34b1e15ca08","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.2","title":"Cool Down sUSDe Shares","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6107,"content":"The documents herein define the process for an operator to cool down sUSDe shares.","contentHash":"fdc6da6ff8a343a02c78b69ab29753353da7c356e1fef1749bd3731c30a93800","addressRefs":[]},"ba771f78-163f-4ec6-990d-ec8cc25e0393":{"id":"ba771f78-163f-4ec6-990d-ec8cc25e0393","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.2.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6108,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `cooldownSharesSUSDe`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction cooldownSharesSUSDe(uint256 susdeAmount)\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"574ebb22fd679cf3e289eca8ce6852fa04d586bf42942a214b87daec2ed21df1","addressRefs":[]},"038cb6fe-4040-4f3a-b1a8-9c6f2f3a4f72":{"id":"038cb6fe-4040-4f3a-b1a8-9c6f2f3a4f72","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.2.2","title":"Encode Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6109,"content":"The operator must use `proxy.doCall()` to make a call to the `susde` contract, initiating the `cooldown` on the specified amount of sUSDe shares. They must encode the function using `abi.encodeCall`.","contentHash":"67905094d5834ab89fe64850b0ebf027783b0920328b9cfd74544a4686a0f802","addressRefs":[]},"9e6e0eef-e29c-4e99-ad36-36c4eeac37ea":{"id":"9e6e0eef-e29c-4e99-ad36-36c4eeac37ea","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.2.2.1","title":"Decode For Underlying Shares","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6110,"content":"The operator must decode the result returned by the `cooldownShares` function into a `uint256` value, representing the amount of shares that were actually cooled down (`cooldownAmount`).\n\n```\n{\n    cooldownAmount = abi.decode(\n        proxy.doCall(\n            address(susde),\n            abi.encodeCall(susde.cooldownShares, (susdeAmount))\n        ),\n        (uint256)\n    );\n```","contentHash":"7201b6681d67856d70e64c7f3774a5e357610ac9ebd765240fe34951912b84b1","addressRefs":[]},"42943bad-504a-4b59-9164-d6cc2acf6a95":{"id":"42943bad-504a-4b59-9164-d6cc2acf6a95","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.2.3","title":"Decrease RateLimit","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6111,"content":"The operator must decrease the `RateLimit`, effectively reducing the available `cooldown` limit, based on the `cooldownAmount`.\n\n```\nrateLimits.triggerRateLimitDecrease(LIMIT_SUSDE_COOLDOWN, cooldownAmount);\n}\n```","contentHash":"662ae53a032957233ab23a23dd153da09b0486d4c297289270a97e2a1d211f65","addressRefs":[]},"bf0523c1-7c37-4073-b565-202c5497825c":{"id":"bf0523c1-7c37-4073-b565-202c5497825c","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.3","title":"Unstake sUSDe And Return It To ALM Proxy","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6112,"content":"The documents herein define the process for an operator to unstake sUSDe and return it to the ALM Proxy.","contentHash":"ab652ec461541aeda2c0abc68c9c4c47d0b270a281ff21515642c78a111a4d15","addressRefs":[]},"1f19cb45-1934-4e2e-8d07-0d4b78e7188c":{"id":"1f19cb45-1934-4e2e-8d07-0d4b78e7188c","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.3.1","title":"Relayer Role","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6113,"content":"The operator must ensure they are working as a `RELAYER`. Only the `RELAYER` role is allowed to `unstakeSUSDe`. Also, they must ensure the contract `isActive` i.e. can process the request.\n\n```\nfunction unstakeSUSDe()\n        external\n        onlyRole(RELAYER)\n        isActive\n```","contentHash":"4cdbdae9dd15bfb5cd57da2e604cdb39b95ea943e43e856c5f9c1e38eab8dc8f","addressRefs":[]},"516ca684-b183-4d57-9feb-97a7a9b58e42":{"id":"516ca684-b183-4d57-9feb-97a7a9b58e42","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.3.2","title":"Encode Function","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6114,"content":"The operator must use `proxy.doCall()` to make a call to the `susde` contract to invoke the `unstake` function, which unstakes sUSDe and sends the resulting tokens back to the `proxy` address (i.e. ALM Proxy). They must encode the function using `abi.encodeCall`.\n\n```\n{\n    proxy.doCall(\n        address(susde),\n        abi.encodeCall(susde.unstake, (address(proxy)))\n    );\n}\n```","contentHash":"67889e846ab9ad0e295de061ceb7c24d48a64a34a3f5bac1a12599e1357eb5f8","addressRefs":[]},"8d926497-9fe7-4189-83c8-10f649ff0b1d":{"id":"8d926497-9fe7-4189-83c8-10f649ff0b1d","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.4","title":"Emergency Procedure To Withdraw Ethena Balances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6115,"content":"In order to withdraw all Ethena balances, the operator must execute the following actions:","contentHash":"ea2b8b5def5df4f898a395262de817125b2816f5091161519d97f02eb76c6dcd","addressRefs":[]},"bc67845f-f3e8-45d3-b17b-93b669072f77":{"id":"bc67845f-f3e8-45d3-b17b-93b669072f77","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.4.1","title":"sUSDe Cooldown Action","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6116,"content":"The operator must start the cooldown for sUSDe using the following action:\n\n```\nmainnetController.cooldownSharesSUSDe(susde.balanceOf(address(proxy))\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.2.2.6.1.3.1.4.2.3.2 - Cool Down sUSDe Shares](8f029eaf-a208-4f7c-8f00-d34b1e15ca08).","contentHash":"4abc2c191b6dab0e7a763195127595a8b15df4c3e59ec3971d04073d3259d7ff","addressRefs":[]},"44ee472f-41a4-45c4-bce3-34615132e5d2":{"id":"44ee472f-41a4-45c4-bce3-34615132e5d2","doc_no":"A.6.1.1.2.2.6.1.3.1.4.2.3.4.2","title":"sUSDe Unstake Action","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6117,"content":"The operator must unstake sUSDe using the following action:\n\n```\nmainnetController.unstakeSUSDe()\n```\nFor more detailed instructions on the code to execute this, see [A.6.1.1.2.2.6.1.3.1.4.2.3.3 - Unstake sUSDe And Return It To ALM Proxy](bf0523c1-7c37-4073-b565-202c5497825c).","contentHash":"b395cfa28ab3cd08aec22d14444eefd012769b44bb5c0bd19c297bb32455ec04","addressRefs":[]},"e3f9abf3-0cd0-46cc-8295-175c1bc8afbd":{"id":"e3f9abf3-0cd0-46cc-8295-175c1bc8afbd","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3","title":"Ethereum Mainnet - Ethena PT-USDe Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6118,"content":"The documents herein contain the Instance Configuration Document for the Ethena PT-USDe Instance.","contentHash":"ed0bdc2288779a2afc182859bb4890ebc43e9b0cea8ea3be868538560c34ccd9","addressRefs":[]},"65922d1d-0866-480a-9e56-5c47f2ed24c0":{"id":"65922d1d-0866-480a-9e56-5c47f2ed24c0","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6119,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"f96e5493-ce45-496c-a9c0-833962329075":{"id":"f96e5493-ce45-496c-a9c0-833962329075","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6120,"content":"The documents herein define the parameters of the Ethena PT-USDe Instance of the Allocation System Primitive.","contentHash":"0c2c4d096a7b534a8ed4db8ab6458163b12666e74b3fc90a48d33a998d17ecd4","addressRefs":[]},"5882a708-164c-49c4-8348-1bc2f81066a4":{"id":"5882a708-164c-49c4-8348-1bc2f81066a4","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6121,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"7ff517b4-069c-4f73-adc8-028756a8e3f3":{"id":"7ff517b4-069c-4f73-adc8-028756a8e3f3","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6122,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"0d4e39d3-5b1a-44ad-aba5-4171bf22e370":{"id":"0d4e39d3-5b1a-44ad-aba5-4171bf22e370","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6123,"content":"Ethena","contentHash":"1cd6c88005c37da3facbdb981d3e3989d5d54e9c33d051fb861c394a1981c72f","addressRefs":[]},"f716ae3f-7c95-4ccc-8280-2e62a8a121d1":{"id":"f716ae3f-7c95-4ccc-8280-2e62a8a121d1","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6124,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"34447618-cb6c-4d05-874e-68e2d8c5ea95":{"id":"34447618-cb6c-4d05-874e-68e2d8c5ea95","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6125,"content":"PT-USDe","contentHash":"1edae53a0d6ad4cd5c9596b7aa6bc4be3a093dbf4afa1b1c32f80723f8bf9552","addressRefs":[]},"bb7c88fe-0f4f-4384-a9ca-a6a974e460c6":{"id":"bb7c88fe-0f4f-4384-a9ca-a6a974e460c6","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6126,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"9008b149-de3d-429d-824f-48524063d657":{"id":"9008b149-de3d-429d-824f-48524063d657","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6127,"content":"`0x4c9EDD5852cd905f086C759E8383e09bff1E68B3`","contentHash":"af8f3aca379b74340581939474b84e3badef16e17802b2b71cfa3cb6f05cb267","addressRefs":["0x4c9edd5852cd905f086c759e8383e09bff1e68b3"]},"dd7eaa92-d40a-4ffc-9359-ce7d8a9f01fe":{"id":"dd7eaa92-d40a-4ffc-9359-ce7d8a9f01fe","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6128,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"88303bee-82c3-4d78-8b31-e319c760ee31":{"id":"88303bee-82c3-4d78-8b31-e319c760ee31","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.2.3","title":"Broker Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6129,"content":"`0xD94F9ef3395BBE41C1f05ced3C9a7dc520D08036`","contentHash":"18dcdec6cd8885657e7f9c8af88d24f60ab090599e1ab3936fe0b2fb2741ed51","addressRefs":["0xd94f9ef3395bbe41c1f05ced3c9a7dc520d08036"]},"93e8e5e9-2e38-45ff-b325-7ff52f73017d":{"id":"93e8e5e9-2e38-45ff-b325-7ff52f73017d","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6130,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"7e3cf2f7-1371-426e-881a-99878625cd2e":{"id":"7e3cf2f7-1371-426e-881a-99878625cd2e","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6131,"content":"The inflow RateLimitID is: `0x098ad67dc41c1a5892ec3ef5fd411198dc11962475e9ef2e0362e6cb7f5a2174`.","contentHash":"d5831c000409652ebf8d301bc269e8a3d8122742ea4ee58b92f5995b66bdf4ce","addressRefs":[]},"49a086b0-0d77-4d9a-b899-9b1177181b4b":{"id":"49a086b0-0d77-4d9a-b899-9b1177181b4b","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6132,"content":"The outflow RateLimitID is: `0x6dd53d41cd67732ec6166a0927bd9c2da9e20940bd174778b44787531d32d42e`.","contentHash":"3069e90bffc134684ae0cf8468202d440b27a3f24510d849e583edd74cf0ab28","addressRefs":[]},"c13e1a1b-4104-4964-a901-4c7bcb19c868":{"id":"c13e1a1b-4104-4964-a901-4c7bcb19c868","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6133,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"7a93740b-d794-4ca9-aece-6c7db42bebf2":{"id":"7a93740b-d794-4ca9-aece-6c7db42bebf2","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.4.1","title":"Deposit Rate Limits (via FalconX)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6134,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50 million USDC\n- `slope`: 50 million USDC","contentHash":"a078eb6a0a3fbc39137a76f32eea55b575ef8b6aeaf9d30cf84fd357f5473ef3","addressRefs":[]},"e198f465-0b25-4f45-860f-66eacc575f9f":{"id":"e198f465-0b25-4f45-860f-66eacc575f9f","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.4.2","title":"Withdrawal Rate Limits (via FalconX)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6135,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: 50 million USDC\n- `slope`: 50 million USDC","contentHash":"dc5602066a2966eafb769f685fd5c5d0e6920b20e11efad386e72ad65ec6e333","addressRefs":[]},"9dce58c1-0c6d-44f4-8145-c4243e8c02a9":{"id":"9dce58c1-0c6d-44f4-8145-c4243e8c02a9","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.4.3","title":"Redemption Rate Limits (via Pendle Protocol)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6136,"content":"The redemption rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"76c960736fcba6f39e10ae8128253d4ea3718360211c59560bf70a0b2ce2a4b4","addressRefs":[]},"a0fbf90a-75dc-4ee7-a4a6-e9a39314f8b3":{"id":"a0fbf90a-75dc-4ee7-a4a6-e9a39314f8b3","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6137,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"64fc397b-a8e4-425a-814f-d22570dfadc7":{"id":"64fc397b-a8e4-425a-814f-d22570dfadc7","doc_no":"A.6.1.1.2.2.6.1.3.1.4.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6138,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"ba45e20f-b6df-4836-94ea-b4f2f062e658":{"id":"ba45e20f-b6df-4836-94ea-b4f2f062e658","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4","title":"Ethereum Mainnet - Ethena PT-sUSDe Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6139,"content":"The documents herein contain the Instance Configuration Document for the Ethena PT-sUSDe Instance.","contentHash":"00db76f8fd42c2740a56d58a8519cb6c3bed6524cc82b141f693639b7f9a233b","addressRefs":[]},"c0a78c43-bbd6-4735-b1b9-15772514223b":{"id":"c0a78c43-bbd6-4735-b1b9-15772514223b","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6140,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"5799c20d-bed8-4e81-bffb-5ec49e95d303":{"id":"5799c20d-bed8-4e81-bffb-5ec49e95d303","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6141,"content":"The documents herein define the parameters of the Ethena PT-sUSDe Instance of the Allocation System Primitive.","contentHash":"93df40d903d55fb9258328c22758c719f686e2c7ae9c471b97f8b1b94ea39d0c","addressRefs":[]},"6b772ff5-77a0-4f96-8ce7-896c4a221e31":{"id":"6b772ff5-77a0-4f96-8ce7-896c4a221e31","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6142,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"88cf47cb-a94e-475e-9fb8-1b9f2540ba9a":{"id":"88cf47cb-a94e-475e-9fb8-1b9f2540ba9a","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6143,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"6dbd0693-3ebd-4175-82ef-991f085b6942":{"id":"6dbd0693-3ebd-4175-82ef-991f085b6942","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6144,"content":"Ethena","contentHash":"1cd6c88005c37da3facbdb981d3e3989d5d54e9c33d051fb861c394a1981c72f","addressRefs":[]},"3246daa1-29ee-447e-ad83-b5b7f8f8a931":{"id":"3246daa1-29ee-447e-ad83-b5b7f8f8a931","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6145,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"dd3b11cd-ca9d-4c7b-9769-9624c3085954":{"id":"dd3b11cd-ca9d-4c7b-9769-9624c3085954","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6146,"content":"PT-sUSDe","contentHash":"d924ad69b3e734e86279582323e0b30d5f9d1dfe934dfe81be6a7003daf76e85","addressRefs":[]},"fc28e9fd-a4db-4963-8935-f2b05dd2a8bd":{"id":"fc28e9fd-a4db-4963-8935-f2b05dd2a8bd","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.1.5","title":"Broker","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6147,"content":"FalconX","contentHash":"a69f4e6cb49d78e822fe4c979ace61a7b9ab396071e0fd8e9e8be834fd478067","addressRefs":[]},"46e15661-6ee9-4ac6-88ad-d07d7f7fa6a4":{"id":"46e15661-6ee9-4ac6-88ad-d07d7f7fa6a4","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6148,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"3b108b97-6f88-4d96-a55a-38c39191281e":{"id":"3b108b97-6f88-4d96-a55a-38c39191281e","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6149,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"914e6bcf-a73b-4c80-bfa8-04dbd58a7805":{"id":"914e6bcf-a73b-4c80-bfa8-04dbd58a7805","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6150,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"4d4d42ae-76e3-4de8-87a0-14ce30a4ebe5":{"id":"4d4d42ae-76e3-4de8-87a0-14ce30a4ebe5","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.2.3","title":"Broker Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6151,"content":"`0xD94F9ef3395BBE41C1f05ced3C9a7dc520D08036`","contentHash":"18dcdec6cd8885657e7f9c8af88d24f60ab090599e1ab3936fe0b2fb2741ed51","addressRefs":["0xd94f9ef3395bbe41c1f05ced3c9a7dc520d08036"]},"3af5241e-5b72-4466-9e69-dccb8a8d203b":{"id":"3af5241e-5b72-4466-9e69-dccb8a8d203b","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6152,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"230f8de3-d642-460c-bbff-4e75f110e584":{"id":"230f8de3-d642-460c-bbff-4e75f110e584","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6153,"content":"The inflow RateLimitID is: `0x098ad67dc41c1a5892ec3ef5fd411198dc11962475e9ef2e0362e6cb7f5a2174`.","contentHash":"d5831c000409652ebf8d301bc269e8a3d8122742ea4ee58b92f5995b66bdf4ce","addressRefs":[]},"39d3f488-0d5a-4207-a010-64a5bc6cd8db":{"id":"39d3f488-0d5a-4207-a010-64a5bc6cd8db","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6154,"content":"The outflow RateLimitID is: `0x027191d7c552bd41037422747bcde7caca7d1f6afc5ea9b85f8a47432c70be67`.","contentHash":"1c73d14b7cf847837b91d5ae80425d836763a6b2adbc75f5ef9c4c1e3547b44e","addressRefs":[]},"df99c910-17a9-4374-989e-906bd81d621a":{"id":"df99c910-17a9-4374-989e-906bd81d621a","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6155,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"e66a0529-5419-46ef-8b9c-e6f6c255c3e3":{"id":"e66a0529-5419-46ef-8b9c-e6f6c255c3e3","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.4.1","title":"Deposit Rate Limits (via FalconX)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6156,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50 million USDC\n- `slope`: 50 million USDC","contentHash":"a078eb6a0a3fbc39137a76f32eea55b575ef8b6aeaf9d30cf84fd357f5473ef3","addressRefs":[]},"c3fa15e7-7193-4e4d-9463-9dc6001f3d75":{"id":"c3fa15e7-7193-4e4d-9463-9dc6001f3d75","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.4.2","title":"Withdrawal Rate Limits (via FalconX)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6157,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: 50 million USDC\n- `slope`: 50 million USDC","contentHash":"dc5602066a2966eafb769f685fd5c5d0e6920b20e11efad386e72ad65ec6e333","addressRefs":[]},"5d0649b9-c4ce-4a8a-bd2c-c6c0cc3de322":{"id":"5d0649b9-c4ce-4a8a-bd2c-c6c0cc3de322","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.4.3","title":"Redemption Rate Limits (via Pendle Protocol)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6158,"content":"The redemption rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"76c960736fcba6f39e10ae8128253d4ea3718360211c59560bf70a0b2ce2a4b4","addressRefs":[]},"917cd220-0d0e-4c34-82a5-acb1a0013bf6":{"id":"917cd220-0d0e-4c34-82a5-acb1a0013bf6","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6159,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"ab1c8923-2cf6-4825-b380-a17db876e3a9":{"id":"ab1c8923-2cf6-4825-b380-a17db876e3a9","doc_no":"A.6.1.1.2.2.6.1.3.1.4.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6160,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"2316e0fb-c6f0-43c9-b8d4-1fd1c966b9f0":{"id":"2316e0fb-c6f0-43c9-b8d4-1fd1c966b9f0","doc_no":"A.6.1.1.2.2.6.1.3.1.5","title":"Aave","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6161,"content":"The Ethereum Mainnet Instances of the Aave Protocol with `Active` Status are stored herein.","contentHash":"c1bc7a2945a5f116328c82aab498852617fa21ae00da6ad74a48e24a86f53ca8","addressRefs":[]},"7f4eb111-6751-4308-88ce-efe2445e5455":{"id":"7f4eb111-6751-4308-88ce-efe2445e5455","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1","title":"Ethereum Mainnet - Aave Core v3 USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6162,"content":"The documents herein contain the Instance Configuration Document for the Aave Core v3 USDC Instance.","contentHash":"f92e01d8fada283c6feab1c88b78af9dac7de2afc25533e656795707576e7040","addressRefs":[]},"ad0109ba-cdb8-40d8-8856-a1c21873af79":{"id":"ad0109ba-cdb8-40d8-8856-a1c21873af79","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6163,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"0283a372-0055-443f-aa39-2239180a65b1":{"id":"0283a372-0055-443f-aa39-2239180a65b1","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6164,"content":"The documents herein define the parameters of the Aave Core v3 USDC Instance of the Allocation System Primitive.","contentHash":"00401a19cfeb4cbf324f444becadf6f9c5aa170aafc20c40152d35b79642c1a7","addressRefs":[]},"9138c237-b95f-41fe-8189-8612f75deae5":{"id":"9138c237-b95f-41fe-8189-8612f75deae5","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6165,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"92f14d2c-140d-4d9b-841d-f869d46be687":{"id":"92f14d2c-140d-4d9b-841d-f869d46be687","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6166,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"56c581d0-5f0d-49cb-a149-42ff50a74ce3":{"id":"56c581d0-5f0d-49cb-a149-42ff50a74ce3","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6167,"content":"Aave Core v3","contentHash":"7e38c27f80c3f945557fc0be810afc3ecc50a4265c9b3a177bdc983ec6185bf9","addressRefs":[]},"b605f289-bf6a-40bd-89ce-4457be0767fd":{"id":"b605f289-bf6a-40bd-89ce-4457be0767fd","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6168,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"c9a9635e-70d4-4c45-9641-5d11a7b66815":{"id":"c9a9635e-70d4-4c45-9641-5d11a7b66815","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6169,"content":"aEthUSDC","contentHash":"d71f3701842f707489c99da586c42ac19abe79e7f02ab0d27aaa872e3606098c","addressRefs":[]},"78b79abf-d431-42c6-8fa0-6749768936f2":{"id":"78b79abf-d431-42c6-8fa0-6749768936f2","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6170,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"1899a80c-f660-488a-8ec1-7c9322bd602c":{"id":"1899a80c-f660-488a-8ec1-7c9322bd602c","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6171,"content":"`0x98C23E9d8f34FEFb1B7BD6a91B7FF122F4e16F5c`","contentHash":"b05fdf296174c1f48064da3b1bde6684a1902c132484896fd2d67d96807c529e","addressRefs":["0x98c23e9d8f34fefb1b7bd6a91b7ff122f4e16f5c"]},"39624e4c-91c2-4520-b353-b8c06b7bb4d8":{"id":"39624e4c-91c2-4520-b353-b8c06b7bb4d8","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6172,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"098e86e2-8f31-49a4-a6e3-00f60ed0ca43":{"id":"098e86e2-8f31-49a4-a6e3-00f60ed0ca43","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6173,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"8735fbad-b2a1-417d-87e8-097f6f883717":{"id":"8735fbad-b2a1-417d-87e8-097f6f883717","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6174,"content":"The inflow RateLimitID is: `0x5b6ed3b27d9aa6a9aaf68fc5c0980d9122ac4123093cce0241e4e047c154e214`.","contentHash":"931da52fd5e41f256cd0a99c65cf4094ca795e8bb4fd9949a523a3b0ad6c225d","addressRefs":[]},"74f07aa8-e24d-4e7d-a1f5-beb8d499666c":{"id":"74f07aa8-e24d-4e7d-a1f5-beb8d499666c","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6175,"content":"The outflow RateLimitID is: `0xc0a083c57c21570181e9781d750d04917923daac34e804bad63a5a241c92a850`.","contentHash":"550a198833ee926890c8803d2fee8210203b57f7f792c862780c2cfd3acc299c","addressRefs":[]},"bb488181-e690-4fe1-8be3-ceac0b5df9de":{"id":"bb488181-e690-4fe1-8be3-ceac0b5df9de","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6176,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"879f17bd-6d4a-48b4-8de7-cca31542ddfe":{"id":"879f17bd-6d4a-48b4-8de7-cca31542ddfe","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6177,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50 million USDC\n- `slope`: 25 million USDC per day","contentHash":"b9703247ea9b35cf75e8dce79cd2055e71e8ae051adcc8f860618804ef268d61","addressRefs":[]},"3c8495c0-5a34-48e6-9442-0c11420e2c79":{"id":"3c8495c0-5a34-48e6-9442-0c11420e2c79","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6178,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"dc4a21a8-0051-43a8-a43f-f2aefd6aa7d4":{"id":"dc4a21a8-0051-43a8-a43f-f2aefd6aa7d4","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6179,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"6428151d-e10c-49c1-b6df-2d4354c5a5cb":{"id":"6428151d-e10c-49c1-b6df-2d4354c5a5cb","doc_no":"A.6.1.1.2.2.6.1.3.1.5.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6180,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"6b5a19f9-7810-4066-b2ca-df7eff376971":{"id":"6b5a19f9-7810-4066-b2ca-df7eff376971","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2","title":"Ethereum Mainnet - Aave Core v3 RLUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6181,"content":"The documents herein contain the Instance Configuration Document for the Aave Core v3 RLUSD Instance.","contentHash":"763319419ce2fd26f5ec31b9b829f7a2e66337f1b79496c60de77d610f3a333e","addressRefs":[]},"0414a985-558c-4b0c-910a-8cdc6d16afd9":{"id":"0414a985-558c-4b0c-910a-8cdc6d16afd9","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6182,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"efb946ad-f34b-4794-a3a1-51359518ad8f":{"id":"efb946ad-f34b-4794-a3a1-51359518ad8f","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6183,"content":"The documents herein define the parameters of the Aave Core v3 RLUSD Instance of the Allocation System Primitive.","contentHash":"7d8fca7c6955c0924070dd0afc2015371c9f284aacc05b447ca5a1e31b2526ec","addressRefs":[]},"4f7e9f76-1d35-49d3-99c4-f909bedf1331":{"id":"4f7e9f76-1d35-49d3-99c4-f909bedf1331","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6184,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"6a167e9d-cd54-4be0-8cc3-cb3a44d39dd2":{"id":"6a167e9d-cd54-4be0-8cc3-cb3a44d39dd2","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6185,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"3a20c3e1-f1ac-4bb3-bf98-7207fa344390":{"id":"3a20c3e1-f1ac-4bb3-bf98-7207fa344390","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6186,"content":"Aave Core v3","contentHash":"7e38c27f80c3f945557fc0be810afc3ecc50a4265c9b3a177bdc983ec6185bf9","addressRefs":[]},"59252087-9578-4b5c-9dd8-a206f5397424":{"id":"59252087-9578-4b5c-9dd8-a206f5397424","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6187,"content":"RLUSD","contentHash":"ce52a67fc84336854744eab2516dc2e64b62d6ee5f1743be44f8fa57ae7ea42d","addressRefs":[]},"5ef9ba8f-d51a-45a3-b2a4-51419b479dc6":{"id":"5ef9ba8f-d51a-45a3-b2a4-51419b479dc6","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6188,"content":"aEthRLUSD","contentHash":"1839cc5ad0f785d68437873cac3b48ce437dceb1b5483b0062efbe55dc2b885c","addressRefs":[]},"79c4e91e-4f9a-4ea5-84d6-d92f76309e26":{"id":"79c4e91e-4f9a-4ea5-84d6-d92f76309e26","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6189,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"9e6c6c25-b323-4406-a327-2da9de622c3b":{"id":"9e6c6c25-b323-4406-a327-2da9de622c3b","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6190,"content":"`0xFa82580c16A31D0c1bC632A36F82e83EfEF3Eec0`","contentHash":"de15c23d9c8661c5ad69e7199b8be5767dad46480ed72beecdc66309dee183ba","addressRefs":["0xfa82580c16a31d0c1bc632a36f82e83efef3eec0"]},"02e46eb2-5c2e-4d28-861a-aba2b729fb7a":{"id":"02e46eb2-5c2e-4d28-861a-aba2b729fb7a","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6191,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"ed234f28-3636-44cc-9c48-62429f67a896":{"id":"ed234f28-3636-44cc-9c48-62429f67a896","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6192,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"6531616f-1a98-497e-aea9-674a577c3c57":{"id":"6531616f-1a98-497e-aea9-674a577c3c57","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6193,"content":"The inflow RateLimitID is: `0xd8ebadbd4eb7be4a44bcadbfa0d3e4ca014faa5e1973f993a4193ce396a61208`.","contentHash":"7ab9c2cea55c96f085291aaad2692d9a3e301ca52ed4ff5abd02fa8daad27cd8","addressRefs":[]},"1979d5a0-4a01-4ac9-b735-22d7c4f849d5":{"id":"1979d5a0-4a01-4ac9-b735-22d7c4f849d5","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6194,"content":"The outflow RateLimitID is: `0x574251b6fde351d987ce5235618a87bef48d50787414912b19ff8992cb2ae476`.","contentHash":"51c56df79d22af300e2fb0dc848fea876826524230195acfa25c79816ba07e7c","addressRefs":[]},"adeda437-130a-42d7-ae13-eba5f524fbc8":{"id":"adeda437-130a-42d7-ae13-eba5f524fbc8","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6195,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"2826e338-7b71-4c03-8f6a-2c17fa45863f":{"id":"2826e338-7b71-4c03-8f6a-2c17fa45863f","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6196,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50 million RLUSD\n- `slope`: 25 million RLUSD per day","contentHash":"3e87e7b57ced9cf47692e227b8c674b5d99f08f9c64dbaf69e69980974f3e693","addressRefs":[]},"2709008d-ca7f-45ab-a8c1-ef6bebedea30":{"id":"2709008d-ca7f-45ab-a8c1-ef6bebedea30","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6197,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"5e72ea64-b12f-4dc0-afaf-e3da966a947a":{"id":"5e72ea64-b12f-4dc0-afaf-e3da966a947a","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6198,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"6056f3fa-9fd0-4abc-8733-adb33cb4c725":{"id":"6056f3fa-9fd0-4abc-8733-adb33cb4c725","doc_no":"A.6.1.1.2.2.6.1.3.1.5.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6199,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"3050edfd-dd88-4fa4-91b4-4870d4fed089":{"id":"3050edfd-dd88-4fa4-91b4-4870d4fed089","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3","title":"Ethereum Mainnet - Aave Horizon USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6200,"content":"The documents herein contain the Instance Configuration Document for the Aave Horizon USDC Instance.","contentHash":"a8a6819e5b52c8aa61259705ae2ee5ecc375ffcbdd841c3678310a00dcaf93e8","addressRefs":[]},"87384721-3137-429e-aeda-53edac6e6b39":{"id":"87384721-3137-429e-aeda-53edac6e6b39","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6201,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"6df58738-91f6-412d-a06a-9d9448161903":{"id":"6df58738-91f6-412d-a06a-9d9448161903","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6202,"content":"The documents herein define the parameters of the Aave Horizon USDC Instance of the Allocation System Primitive.","contentHash":"bc807ab570e579beccb4566d8477920142fdfe1251bf55c7bd71c2e0035b16e5","addressRefs":[]},"0feddcb0-9621-4d77-be92-234469d95599":{"id":"0feddcb0-9621-4d77-be92-234469d95599","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6203,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"f519baad-ab33-453a-93f0-8c191f120ea7":{"id":"f519baad-ab33-453a-93f0-8c191f120ea7","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6204,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"5eb9bb64-1e7a-4160-a105-d23752979bf1":{"id":"5eb9bb64-1e7a-4160-a105-d23752979bf1","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6205,"content":"Aave Horizon","contentHash":"0e9c8a81c636d302fe4cd2f0889c0130b5eb9416cb4bf707883f503b9909e105","addressRefs":[]},"2ef8ee0b-a046-409a-9179-800d8deee24d":{"id":"2ef8ee0b-a046-409a-9179-800d8deee24d","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6206,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"349e2499-1e49-4382-b028-0296907de7eb":{"id":"349e2499-1e49-4382-b028-0296907de7eb","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6207,"content":"aHorRwaUSDC","contentHash":"f1f4913086ca40a0e31a1a2632dc97f4a99aa40b8e6d09dd016804ce9ae912b3","addressRefs":[]},"a0574f24-3165-48dd-98e4-bacdb83724ac":{"id":"a0574f24-3165-48dd-98e4-bacdb83724ac","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6208,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"6a88f6e1-07be-4994-b7c5-a9f7a9b0d2cc":{"id":"6a88f6e1-07be-4994-b7c5-a9f7a9b0d2cc","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6209,"content":"`0x68215B6533c47ff9f7125aC95adf00fE4a62f79e`","contentHash":"f3707e097b047ea0c5e47823cca0f537fddea2caaf4f76824c6736a604b7f7e6","addressRefs":["0x68215b6533c47ff9f7125ac95adf00fe4a62f79e"]},"8c65206c-cba3-4e4b-bb97-7ce46b5bcf91":{"id":"8c65206c-cba3-4e4b-bb97-7ce46b5bcf91","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6210,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"4fc579d0-f95b-4776-adcf-9773a3ee07ce":{"id":"4fc579d0-f95b-4776-adcf-9773a3ee07ce","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6211,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"69a9863f-cacc-4d15-bcc6-6cafbf70e1b5":{"id":"69a9863f-cacc-4d15-bcc6-6cafbf70e1b5","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6212,"content":"The inflow RateLimitID is: `0x3edeff8ad9d5510b3b4ff6dddd278ffc0f8ec084f9d49d9dd0d2936054dd27ca`.","contentHash":"66bcd13e6257a9212ba2cb96680d418819e2fc30cab0999ec6308bed22a4940a","addressRefs":[]},"b55b4606-d7ad-485d-80b5-55fccdb53af2":{"id":"b55b4606-d7ad-485d-80b5-55fccdb53af2","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6213,"content":"The outflow RateLimitID is: `0xb890cfc1ed93b136aef2cb34337fae5000d57dd88285b4fd6f886e5a06ede5bc`.","contentHash":"509bbd73dc02847e1abd9c7c91ecf2334176b5b37ce501cda1be1db4a0e9b4ba","addressRefs":[]},"b43cdb63-c017-4777-a184-bf255fd5ac97":{"id":"b43cdb63-c017-4777-a184-bf255fd5ac97","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6214,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"f8ef4e6d-aa05-4b8e-abcf-47afa908b1cc":{"id":"f8ef4e6d-aa05-4b8e-abcf-47afa908b1cc","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6215,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50 million USDC\n- `slope`: 25 million USDC per day","contentHash":"b9703247ea9b35cf75e8dce79cd2055e71e8ae051adcc8f860618804ef268d61","addressRefs":[]},"08e95e2d-2390-40ed-8a79-f312162f7640":{"id":"08e95e2d-2390-40ed-8a79-f312162f7640","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6216,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"9f7a4a5a-dcad-4fe4-9276-9352b7f8538c":{"id":"9f7a4a5a-dcad-4fe4-9276-9352b7f8538c","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6217,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"48413486-b0ac-4dc5-bbed-6a300a581872":{"id":"48413486-b0ac-4dc5-bbed-6a300a581872","doc_no":"A.6.1.1.2.2.6.1.3.1.5.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6218,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"15200deb-9894-4f54-95b6-7bab90a6f395":{"id":"15200deb-9894-4f54-95b6-7bab90a6f395","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4","title":"Ethereum Mainnet - Aave Horizon RLUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6219,"content":"The documents herein contain the Instance Configuration Document for the Aave Horizon RLUSD Instance.","contentHash":"8c9ab50f9bab0bbde696534410c940ea969d8bb024c52ad0cdc1ff3239730171","addressRefs":[]},"b78f0da7-001e-43d0-acd0-2704ad5f831c":{"id":"b78f0da7-001e-43d0-acd0-2704ad5f831c","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6220,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"9c98bbee-a499-48e8-9155-4b140d0f5cb6":{"id":"9c98bbee-a499-48e8-9155-4b140d0f5cb6","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6221,"content":"The documents herein define the parameters of the Aave Horizon RLUSD Instance of the Allocation System Primitive.","contentHash":"a5cbe7be223447440a2253741f940adb9dfe46d099e566f94723a2758ab1d368","addressRefs":[]},"2a8f42ef-f0f8-483e-b4be-74e530e860b1":{"id":"2a8f42ef-f0f8-483e-b4be-74e530e860b1","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6222,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"b80ce6f0-ca13-4ff9-88c9-e8996fc886ee":{"id":"b80ce6f0-ca13-4ff9-88c9-e8996fc886ee","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6223,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"3e19da9b-628e-4058-bf9a-0d9fcd9c1213":{"id":"3e19da9b-628e-4058-bf9a-0d9fcd9c1213","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6224,"content":"Aave Horizon","contentHash":"0e9c8a81c636d302fe4cd2f0889c0130b5eb9416cb4bf707883f503b9909e105","addressRefs":[]},"a77a3f3d-3ead-48b8-b774-693c698232aa":{"id":"a77a3f3d-3ead-48b8-b774-693c698232aa","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6225,"content":"RLUSD","contentHash":"ce52a67fc84336854744eab2516dc2e64b62d6ee5f1743be44f8fa57ae7ea42d","addressRefs":[]},"5bc6234b-f8ef-4c2c-8571-c751a1f35d8a":{"id":"5bc6234b-f8ef-4c2c-8571-c751a1f35d8a","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6226,"content":"aHorRwaRLUSD","contentHash":"d46855a0b84b2d47a8f0fc2483c05f62aba1d2e999a6528f55ae9c1d4316395f","addressRefs":[]},"ab136525-3878-4024-995d-eb28f4b412a9":{"id":"ab136525-3878-4024-995d-eb28f4b412a9","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6227,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"9d0c9c24-3982-44a7-b96f-c1bf25c41b10":{"id":"9d0c9c24-3982-44a7-b96f-c1bf25c41b10","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6228,"content":"`0xE3190143Eb552456F88464662f0c0C4aC67A77eB`","contentHash":"c8815f379ca08e9425e3e7c1c5520884822d53848d3711267be12e15dfd6a19a","addressRefs":["0xe3190143eb552456f88464662f0c0c4ac67a77eb"]},"80dd4ee6-eb44-4a56-8679-5d9df5a18fb2":{"id":"80dd4ee6-eb44-4a56-8679-5d9df5a18fb2","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6229,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"15c531fe-68c8-4fe6-8beb-d18fb7174da9":{"id":"15c531fe-68c8-4fe6-8beb-d18fb7174da9","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6230,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"92f01c9e-95a2-4364-b8ec-de494a7784b6":{"id":"92f01c9e-95a2-4364-b8ec-de494a7784b6","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6231,"content":"The inflow RateLimitID is: `0x5b8bd7b86efeb854063affedcbe0439d750ca9e5cf53217dd4c82b91be92524c`.","contentHash":"42ae7bf5e88d682beca7f313548c85f22f197abd2b1e9b6b25769a87c1f85f4b","addressRefs":[]},"808c067c-b464-4f1f-a35c-017e373a3a59":{"id":"808c067c-b464-4f1f-a35c-017e373a3a59","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6232,"content":"The outflow RateLimitID is: `0xa33f2f500dd7f4baa10d882fd974f197a507f7b61f245ae2689510311379df7a`.","contentHash":"45509f34de5ef5d20cc4d1289940d096924a3d2e9ae3ae0e80fd7da57b7e593f","addressRefs":[]},"220946bd-aa72-4690-a423-e728019bda4d":{"id":"220946bd-aa72-4690-a423-e728019bda4d","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6233,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"f2f286bd-6cea-4010-81b5-ab11edbbe6ad":{"id":"f2f286bd-6cea-4010-81b5-ab11edbbe6ad","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6234,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50 million RLUSD\n- `slope`: 25 million RLUSD per day","contentHash":"3e87e7b57ced9cf47692e227b8c674b5d99f08f9c64dbaf69e69980974f3e693","addressRefs":[]},"db19cefb-7b08-4d82-8a21-66e97b23d435":{"id":"db19cefb-7b08-4d82-8a21-66e97b23d435","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6235,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"f8a05090-7057-43b2-ab09-13acfadf118a":{"id":"f8a05090-7057-43b2-ab09-13acfadf118a","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6236,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"9e8aea1d-c1c1-4493-b1f2-383a07175591":{"id":"9e8aea1d-c1c1-4493-b1f2-383a07175591","doc_no":"A.6.1.1.2.2.6.1.3.1.5.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6237,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"6a6e239a-cc18-47ab-b1e0-8cf8cf2c2957":{"id":"6a6e239a-cc18-47ab-b1e0-8cf8cf2c2957","doc_no":"A.6.1.1.2.2.6.1.3.1.6","title":"Curve","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6238,"content":"The Ethereum Mainnet Instances of the Curve Protocol with `Active` Status are stored herein.","contentHash":"bbe4a4b6ba2956afcb9c28db209d5c1012eb0afbc525d654cf3eab0d447ca42b","addressRefs":[]},"67b85f8a-3857-461d-a214-d3bf990f9111":{"id":"67b85f8a-3857-461d-a214-d3bf990f9111","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1","title":"Ethereum Mainnet - Curve RLUSD/USDC Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6239,"content":"The documents herein contain the Instance Configuration Document for the Curve RLUSD/USDC Pool Instance.","contentHash":"81b6b70710ffa70f42c1053b5d4554e908c6735e184b23f6390afa2a23422bf0","addressRefs":[]},"f457fb43-c250-4111-b370-3e875e13db65":{"id":"f457fb43-c250-4111-b370-3e875e13db65","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6240,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"ef903d8d-08fe-4be2-b68f-adb87d7449e3":{"id":"ef903d8d-08fe-4be2-b68f-adb87d7449e3","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6241,"content":"The documents herein define the parameters of the Curve RLUSD/USDC Pool Instance of the Allocation System Primitive.","contentHash":"66d4fe99b9b390f73a05c2d9924712c3a7a28ef79c9cd731f1d844d603cd610a","addressRefs":[]},"49528c46-1220-46a7-b693-cf0433129077":{"id":"49528c46-1220-46a7-b693-cf0433129077","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6242,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"4b77a1d9-18bc-4144-ad5f-8b1bdf2974db":{"id":"4b77a1d9-18bc-4144-ad5f-8b1bdf2974db","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6243,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"d7ad7cbd-774d-4ef7-b35c-897e1d66b766":{"id":"d7ad7cbd-774d-4ef7-b35c-897e1d66b766","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6244,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"aadd33fa-45a8-4df8-963a-2ee40ea6075b":{"id":"aadd33fa-45a8-4df8-963a-2ee40ea6075b","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6245,"content":"RLUSD and USDC","contentHash":"4d865515186806f7e43e82f0076fc747aa64f8ce9926898f5f54db580171fa98","addressRefs":[]},"b787771e-42f4-4a11-b683-1be8d536546c":{"id":"b787771e-42f4-4a11-b683-1be8d536546c","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6246,"content":"RLUSD/USDC","contentHash":"6dd674aae9d9e7b98373d1525889ae9ac6f16d5724c80ebe054c82dc4f186e8b","addressRefs":[]},"3a2d436e-e498-46ae-aa93-5eaf2b1c3adf":{"id":"3a2d436e-e498-46ae-aa93-5eaf2b1c3adf","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6247,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"869f4a71-5a20-4e34-b718-cfe844630475":{"id":"869f4a71-5a20-4e34-b718-cfe844630475","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.2.1","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6248,"content":"`0xD001aE433f254283FeCE51d4ACcE8c53263aa186`","contentHash":"e02d076fe8c99eb214dc128d3fee05f1e082e9bdc79f20e7f6aba12a8629e00b","addressRefs":["0xd001ae433f254283fece51d4acce8c53263aa186"]},"29aee46d-b94b-4402-ba84-2029422965e6":{"id":"29aee46d-b94b-4402-ba84-2029422965e6","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6249,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"bcb5e6e4-1616-4e0f-96d5-a08d4c4dda84":{"id":"bcb5e6e4-1616-4e0f-96d5-a08d4c4dda84","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.2.3","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6250,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"5c5d80a6-c0cc-491c-9e4b-75480d2a7a30":{"id":"5c5d80a6-c0cc-491c-9e4b-75480d2a7a30","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6251,"content":"The specific `RateLimitID`(s) for this conduit’s inflow, outflow and swap are defined in the subdocuments herein.","contentHash":"1fee6a5441be3a55aea48130dcd72dca1fb2f38e7b197d873321adebd9668326","addressRefs":[]},"385325de-b8c3-4e9f-96ee-c8499fca7848":{"id":"385325de-b8c3-4e9f-96ee-c8499fca7848","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6252,"content":"The inflow RateLimitID is: N/A - swap only.","contentHash":"c046a8553700aa588b90022b604c7d1095a126f56ab28a96c81431cc48ed101c","addressRefs":[]},"4f630380-8ca6-4ce6-9482-9af88826ea07":{"id":"4f630380-8ca6-4ce6-9482-9af88826ea07","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6253,"content":"The outflow RateLimitID is: N/A - swap only.","contentHash":"35b5697c0529140a2aadd512fa301dfb0ecb47f6464ebc3cd70e33316b6a4b0c","addressRefs":[]},"3edab299-1530-48bb-9c89-0a2aee6902ce":{"id":"3edab299-1530-48bb-9c89-0a2aee6902ce","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.3.3","title":"Swap RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6254,"content":"The swap RateLimitID is: `0x8dcb7a359e6824ce9fd1c1f50ba67cd468764f690da2589aa3c262ac142c333a`.","contentHash":"718206ae547aa5fe684b1b28d8c8fde52e5f95412e5b4f73eedc73b816f13dbd","addressRefs":[]},"d9cb1721-0f26-41db-a929-4725ac227d3e":{"id":"d9cb1721-0f26-41db-a929-4725ac227d3e","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6255,"content":"The current `maxAmount`, `slope` and `maxSlippage` for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"1d003e9c0099921704dcd7ec6734c57a326c0bf191801b7f08ad4916db474c50","addressRefs":[]},"172836ec-2f76-4e64-96db-fb60c9885d12":{"id":"172836ec-2f76-4e64-96db-fb60c9885d12","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6256,"content":"The deposit rate limits are:\n\n- `maxAmount`: N/A - swap only\n- `slope`: N/A - swap only","contentHash":"745e557eac4fb01ee3e253bf4249ce12057792955e0258b6c7b001516b0e072a","addressRefs":[]},"a3a60b38-055f-42e4-b35d-bb04eb829b67":{"id":"a3a60b38-055f-42e4-b35d-bb04eb829b67","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6257,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A - swap only","contentHash":"5f37ebe61478902f63055055645edd58c39cefdf7a441623715e4733ca816fb1","addressRefs":[]},"511cec98-4c5b-488e-8b5b-c088d04cd46b":{"id":"511cec98-4c5b-488e-8b5b-c088d04cd46b","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6258,"content":"The swap rate limits are:\n\n- `maxAmount`: 20 million\n- `slope`: 100 million per day\n- `maxSlippage`: 0.1%","contentHash":"a78ba08d0f99b50bc2fa7df8a18c4307a3a96df2da0342d74c7d94de9e8aaaf1","addressRefs":[]},"8dbe4e53-e70b-4b52-b607-558e9b023b56":{"id":"8dbe4e53-e70b-4b52-b607-558e9b023b56","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6259,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"7a0d7698-5f64-47f8-b81e-c2e71e6e15dc":{"id":"7a0d7698-5f64-47f8-b81e-c2e71e6e15dc","doc_no":"A.6.1.1.2.2.6.1.3.1.6.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6260,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"f6501dc9-f8e9-4130-9390-a1d9f142fcc7":{"id":"f6501dc9-f8e9-4130-9390-a1d9f142fcc7","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2","title":"Ethereum Mainnet - Curve RLUSD/USDC Pool Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6261,"content":"The documents herein contain the Instance Configuration Document for the Curve RLUSD/USDC Pool Instance.","contentHash":"81b6b70710ffa70f42c1053b5d4554e908c6735e184b23f6390afa2a23422bf0","addressRefs":[]},"438f0f65-8e66-40c6-a17b-b861d57da301":{"id":"438f0f65-8e66-40c6-a17b-b861d57da301","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6262,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"23317c4d-a0ce-48c5-b2ac-7ce4cd93cf83":{"id":"23317c4d-a0ce-48c5-b2ac-7ce4cd93cf83","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6263,"content":"The documents herein define the parameters of the Curve RLUSD/USDC Pool Instance of the Allocation System Primitive.","contentHash":"66d4fe99b9b390f73a05c2d9924712c3a7a28ef79c9cd731f1d844d603cd610a","addressRefs":[]},"987eb2cc-420e-40d7-b5b2-31452ed7bcc7":{"id":"987eb2cc-420e-40d7-b5b2-31452ed7bcc7","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6264,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"a4fa782e-587c-46d5-b2d0-4a77d778ab07":{"id":"a4fa782e-587c-46d5-b2d0-4a77d778ab07","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6265,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"e727e42d-e275-4122-9ba0-fe98bb7eedcf":{"id":"e727e42d-e275-4122-9ba0-fe98bb7eedcf","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6266,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"7b685931-6f16-40b5-ae0e-86c46751da93":{"id":"7b685931-6f16-40b5-ae0e-86c46751da93","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6267,"content":"RLUSD and USDC","contentHash":"4d865515186806f7e43e82f0076fc747aa64f8ce9926898f5f54db580171fa98","addressRefs":[]},"8bc9fd15-00f7-44c5-b48d-1916ea567117":{"id":"8bc9fd15-00f7-44c5-b48d-1916ea567117","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6268,"content":"RLUSD/USDC","contentHash":"6dd674aae9d9e7b98373d1525889ae9ac6f16d5724c80ebe054c82dc4f186e8b","addressRefs":[]},"8aecdc5f-0f1a-4394-9306-a60c2f7daf69":{"id":"8aecdc5f-0f1a-4394-9306-a60c2f7daf69","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6269,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"ef88cdfb-f431-4897-b9e6-11a16c6b8188":{"id":"ef88cdfb-f431-4897-b9e6-11a16c6b8188","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.2.1","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6270,"content":"`0xD001aE433f254283FeCE51d4ACcE8c53263aa186`","contentHash":"e02d076fe8c99eb214dc128d3fee05f1e082e9bdc79f20e7f6aba12a8629e00b","addressRefs":["0xd001ae433f254283fece51d4acce8c53263aa186"]},"c3b33e2f-23b6-42f9-a6d7-abb5372217ae":{"id":"c3b33e2f-23b6-42f9-a6d7-abb5372217ae","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6271,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"f1c52fdb-5856-4fce-b99e-6cbcc13296b1":{"id":"f1c52fdb-5856-4fce-b99e-6cbcc13296b1","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.2.3","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6272,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"8b1cc07a-58fd-4657-99c7-e1feecc13ab3":{"id":"8b1cc07a-58fd-4657-99c7-e1feecc13ab3","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6273,"content":"The specific `RateLimitID`(s) for this conduit’s inflow, outflow and swap are defined in the subdocuments herein.","contentHash":"1fee6a5441be3a55aea48130dcd72dca1fb2f38e7b197d873321adebd9668326","addressRefs":[]},"6cff8544-7a7d-43a6-8db6-3f2b1939b656":{"id":"6cff8544-7a7d-43a6-8db6-3f2b1939b656","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6274,"content":"The inflow RateLimitID is: N/A - swap only.","contentHash":"c046a8553700aa588b90022b604c7d1095a126f56ab28a96c81431cc48ed101c","addressRefs":[]},"e5752190-a5a0-4d6f-9738-b07898e0dccb":{"id":"e5752190-a5a0-4d6f-9738-b07898e0dccb","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6275,"content":"The outflow RateLimitID is: N/A - swap only.","contentHash":"35b5697c0529140a2aadd512fa301dfb0ecb47f6464ebc3cd70e33316b6a4b0c","addressRefs":[]},"d2d15203-f105-401f-8d0b-19f67771fb1e":{"id":"d2d15203-f105-401f-8d0b-19f67771fb1e","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.3.3","title":"Swap RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6276,"content":"The swap RateLimitID is: `0x8dcb7a359e6824ce9fd1c1f50ba67cd468764f690da2589aa3c262ac142c333a`.","contentHash":"718206ae547aa5fe684b1b28d8c8fde52e5f95412e5b4f73eedc73b816f13dbd","addressRefs":[]},"c9ac1f48-8dbf-4c72-8a77-27c6e8863a83":{"id":"c9ac1f48-8dbf-4c72-8a77-27c6e8863a83","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6277,"content":"The current `maxAmount`, `slope` and `maxSlippage` for this conduit’s inflow/outflow/swap are defined in the subdocuments herein.","contentHash":"1d003e9c0099921704dcd7ec6734c57a326c0bf191801b7f08ad4916db474c50","addressRefs":[]},"84d948f0-8a23-4710-a6d4-8fc094befc91":{"id":"84d948f0-8a23-4710-a6d4-8fc094befc91","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6278,"content":"The deposit rate limits are:\n\n- `maxAmount`: N/A - swap only\n- `slope`: N/A - swap only","contentHash":"745e557eac4fb01ee3e253bf4249ce12057792955e0258b6c7b001516b0e072a","addressRefs":[]},"91eeb3a6-3b06-4e33-b835-51614136ce2e":{"id":"91eeb3a6-3b06-4e33-b835-51614136ce2e","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6279,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A - swap only","contentHash":"5f37ebe61478902f63055055645edd58c39cefdf7a441623715e4733ca816fb1","addressRefs":[]},"8885e8e3-1ab5-4b0a-998c-07e692db7054":{"id":"8885e8e3-1ab5-4b0a-998c-07e692db7054","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6280,"content":"The swap rate limits are:\n\n- `maxAmount`: 20 million\n- `slope`: 100 million per day\n- `maxSlippage`: 0.1%","contentHash":"a78ba08d0f99b50bc2fa7df8a18c4307a3a96df2da0342d74c7d94de9e8aaaf1","addressRefs":[]},"fb386f16-e7f8-4cba-b10f-346c0e19b8f1":{"id":"fb386f16-e7f8-4cba-b10f-346c0e19b8f1","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6281,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"502790de-8ab5-4359-86e0-d40b8ceda9ff":{"id":"502790de-8ab5-4359-86e0-d40b8ceda9ff","doc_no":"A.6.1.1.2.2.6.1.3.1.6.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6282,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"ea9afb08-8f81-4ee9-b9a7-321862bad5d8":{"id":"ea9afb08-8f81-4ee9-b9a7-321862bad5d8","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3","title":"Ethereum Mainnet - Curve RLUSD/USDC Pool LP Deposits Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6283,"content":"The documents herein contain the Instance Configuration Document for the Curve RLUSD/USDC Pool LP Deposits Instance.","contentHash":"c505803e2174aa5db7f0390742367cffd48d64202cc450a5b7182b7a15cae7de","addressRefs":[]},"d2362b8a-bbed-499c-9d76-9b646bc67024":{"id":"d2362b8a-bbed-499c-9d76-9b646bc67024","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6284,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"4d218b64-f137-43c1-a8b3-430e12677225":{"id":"4d218b64-f137-43c1-a8b3-430e12677225","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6285,"content":"The documents herein define the parameters of the Curve RLUSD/USDC Pool LP Deposits Instance of the Allocation System Primitive.","contentHash":"50746d7dc82cc332544df030b8c72931f8ddbf286bf8676d61a43d56270aa76a","addressRefs":[]},"5a429e97-4796-45f4-b79d-3bc370074a42":{"id":"5a429e97-4796-45f4-b79d-3bc370074a42","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6286,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"dfc15cd1-2c3f-4943-baa3-2c1a09c40c51":{"id":"dfc15cd1-2c3f-4943-baa3-2c1a09c40c51","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6287,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"5c60815c-de1b-4cde-86b4-4c70984c8ad7":{"id":"5c60815c-de1b-4cde-86b4-4c70984c8ad7","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6288,"content":"Curve","contentHash":"a5df3cf36e53f62232d5d78ff8901a71f42e9cee197070a6b23ad1c4d7fd7fb2","addressRefs":[]},"f52ce77b-6823-4afe-a841-f4a50eb8093c":{"id":"f52ce77b-6823-4afe-a841-f4a50eb8093c","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6289,"content":"RLUSD and USDC","contentHash":"4d865515186806f7e43e82f0076fc747aa64f8ce9926898f5f54db580171fa98","addressRefs":[]},"104bb526-03c2-4940-bf92-019fd6cf9c9a":{"id":"104bb526-03c2-4940-bf92-019fd6cf9c9a","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6290,"content":"RLUSD/USDC","contentHash":"6dd674aae9d9e7b98373d1525889ae9ac6f16d5724c80ebe054c82dc4f186e8b","addressRefs":[]},"60cfaf1e-cfab-4869-aa7b-403a81bd9864":{"id":"60cfaf1e-cfab-4869-aa7b-403a81bd9864","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6291,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"7e88794d-21d2-43ba-9e72-924dc4c23af5":{"id":"7e88794d-21d2-43ba-9e72-924dc4c23af5","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.2.1","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6292,"content":"`0xD001aE433f254283FeCE51d4ACcE8c53263aa186`","contentHash":"e02d076fe8c99eb214dc128d3fee05f1e082e9bdc79f20e7f6aba12a8629e00b","addressRefs":["0xd001ae433f254283fece51d4acce8c53263aa186"]},"b7168555-b5c9-4f72-871f-7ce226124cff":{"id":"b7168555-b5c9-4f72-871f-7ce226124cff","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.2.2","title":"Underlying Asset Address (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6293,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"99fde67c-857d-4ba1-89a5-3b237acdba6e":{"id":"99fde67c-857d-4ba1-89a5-3b237acdba6e","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.2.3","title":"Underlying Asset Address (RLUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6294,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"e63c5013-fbfc-40df-bfac-801f0ddb43d2":{"id":"e63c5013-fbfc-40df-bfac-801f0ddb43d2","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6295,"content":"The specific `RateLimitID`(s) for this conduit’s inflow, outflow and swap are defined in the subdocuments herein.","contentHash":"1fee6a5441be3a55aea48130dcd72dca1fb2f38e7b197d873321adebd9668326","addressRefs":[]},"710450c0-a5ee-4eb5-9011-0da07b39ae79":{"id":"710450c0-a5ee-4eb5-9011-0da07b39ae79","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6296,"content":"The inflow RateLimitID is: `0x450c909d837693f4f47c753eb316c7221dd923fff8e28ec3cfbf1cd548f544e7`.","contentHash":"787f0eadf5b0b40c5aead6416fe6500eb2713100f130361963824c37aab7fd28","addressRefs":[]},"8a956435-6a32-407d-bb1e-1af3db54bb7b":{"id":"8a956435-6a32-407d-bb1e-1af3db54bb7b","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6297,"content":"The outflow RateLimitID is: `0xca9b793f7b515f76fb88684bec4850e8c12afbb7f27a81eab232c966c9eb9e96`.","contentHash":"b5c7097f6af80e8f6e1f13f9537a644832e3fef19cab3de5800fb1b214f4b666","addressRefs":[]},"09b73b1b-969c-485a-822b-9b61840494bc":{"id":"09b73b1b-969c-485a-822b-9b61840494bc","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6298,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"15679304-3b86-43f4-be14-d02f33f72d2d":{"id":"15679304-3b86-43f4-be14-d02f33f72d2d","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6299,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 RLUSD or USDC\n- `slope`: 25,000,000 RLUSD or USDC per day","contentHash":"9e6b2c378f21e8b071d218e94ea5d192cd21a218a6546126584d34c809b286df","addressRefs":[]},"34276745-bc02-4e02-aaac-20284debe350":{"id":"34276745-bc02-4e02-aaac-20284debe350","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6300,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"ca62ee2b-3ced-4798-9c39-8687f3f11bef":{"id":"ca62ee2b-3ced-4798-9c39-8687f3f11bef","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6301,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"045a13d9-a6a4-4d50-8cf5-0a762252d9de":{"id":"045a13d9-a6a4-4d50-8cf5-0a762252d9de","doc_no":"A.6.1.1.2.2.6.1.3.1.6.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6302,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"207cc62c-29ee-4a03-afd9-37f279b2c25b":{"id":"207cc62c-29ee-4a03-afd9-37f279b2c25b","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4","title":"Ethereum Mainnet - Curve AUSD/USDC Swaps Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6303,"content":"The documents herein contain the Instance Configuration Document for the Curve AUSD/USDC Swaps Instance.","contentHash":"32993840750ef04c7219dcca5f8152f70b01677bf4a8f92c8900331204128dd9","addressRefs":[]},"4b0df25d-62db-4165-b225-0285a56838a1":{"id":"4b0df25d-62db-4165-b225-0285a56838a1","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6304,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"73dc573f-443e-4340-bfa5-a1773a839af8":{"id":"73dc573f-443e-4340-bfa5-a1773a839af8","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6305,"content":"The documents herein define the parameters of the Curve AUSD/USDC Swaps Instance of the Allocation System Primitive.","contentHash":"d503d82fd7bca5098d451919dd2179b01cb129d5d2a0d44b1985e91f96359d46","addressRefs":[]},"8df69912-f3f3-4225-bed8-e47865580a63":{"id":"8df69912-f3f3-4225-bed8-e47865580a63","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6306,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"f6ec618e-7eeb-4ca2-b702-9a9c978536c4":{"id":"f6ec618e-7eeb-4ca2-b702-9a9c978536c4","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6307,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"196f8840-a3f0-435b-90f6-f8e0d46235f9":{"id":"196f8840-a3f0-435b-90f6-f8e0d46235f9","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6308,"content":"Curve AUSD/USDC","contentHash":"f0b08d9b52c522f03a5d3cbd23dcccf7a7d02ddbac7f931af69a0ba1d924772b","addressRefs":[]},"5a3a318d-bba2-44f0-abe6-e413964e9b5d":{"id":"5a3a318d-bba2-44f0-abe6-e413964e9b5d","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6309,"content":"USDC and AUSD","contentHash":"999ebdd48dd35012dd2f3891ace89987092855bf0933638e151fd9998c49469c","addressRefs":[]},"7b862a65-b8d3-4034-a47b-649f18550393":{"id":"7b862a65-b8d3-4034-a47b-649f18550393","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6310,"content":"AUSDUSDC","contentHash":"49187a99be2280ccf1068410be6278c3ca419d72a2914144cb15be2e82e3d8d1","addressRefs":[]},"318ca1d7-f02c-4520-97b8-0b28762f5301":{"id":"318ca1d7-f02c-4520-97b8-0b28762f5301","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6311,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"ff266150-7da7-468a-b6cc-f8833c55d3b0":{"id":"ff266150-7da7-468a-b6cc-f8833c55d3b0","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.2.1","title":"Underlying Asset Address (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6312,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"f83f01f9-6963-4512-81ee-f632349a94d3":{"id":"f83f01f9-6963-4512-81ee-f632349a94d3","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.2.2","title":"Underlying Asset Address (AUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6313,"content":"`0x00000000eFE302BEAA2b3e6e1b18d08D69a9012a`","contentHash":"a46d00e1291e0e83786e8b6f0f1f1fcad4c00f15b21c1cf91487ee0535a472a6","addressRefs":["0x00000000efe302beaa2b3e6e1b18d08d69a9012a"]},"8e89d41b-075c-4a4b-bfa8-7129421fdf65":{"id":"8e89d41b-075c-4a4b-bfa8-7129421fdf65","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6314,"content":"`0xE79C1C7E24755574438A26D5e062Ad2626C04662`","contentHash":"37cbbff6291880be1f2b9ff3408d403a77c36318493f81173b2272069c117a5e","addressRefs":["0xe79c1c7e24755574438a26d5e062ad2626c04662"]},"4e47589f-4860-4d14-a74e-3b4536690f83":{"id":"4e47589f-4860-4d14-a74e-3b4536690f83","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6315,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"75afb0be-ec4f-49c2-9b86-0a4846ab1663":{"id":"75afb0be-ec4f-49c2-9b86-0a4846ab1663","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6316,"content":"The inflow RateLimitID is: `0x69758792004c0221462c6e75cf130926aea2203ca8540d22f2a5e570e341bc14`.","contentHash":"fa2b8004f72d63d1701931850f4ba727070f4d12d6ef92bd776964d46ef3f4e7","addressRefs":[]},"32bd5b6f-fa63-4919-8286-ecfcf962bee1":{"id":"32bd5b6f-fa63-4919-8286-ecfcf962bee1","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6317,"content":"The outflow RateLimitID is: N/A.","contentHash":"483affad475b6c78cfa6846cb48795ff6ea43b13d4079c9d25d0d4a65e2aa3d7","addressRefs":[]},"6022cee7-31ec-4356-acc7-537cda385855":{"id":"6022cee7-31ec-4356-acc7-537cda385855","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6318,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"33800c50-8d1e-4339-88a1-8c07e5c35496":{"id":"33800c50-8d1e-4339-88a1-8c07e5c35496","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6319,"content":"The deposit rate limits are:\n\n- `maxAmount`: N/A - swaps only\n- `slope`: N/A - swaps only","contentHash":"9aacd74b2f328e23b05a3a9de3aec35bb15339552aa40aa664957a794e1f6695","addressRefs":[]},"1a78fd44-9483-4063-bbd5-80fef10bf85a":{"id":"1a78fd44-9483-4063-bbd5-80fef10bf85a","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6320,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A - swaps only","contentHash":"be46260dae2beffad3058dbca73d719da91f7f5f4e4b688e1af7e4d9a2f05aea","addressRefs":[]},"5fdeea04-0bf6-475f-b7ed-1232040c6a32":{"id":"5fdeea04-0bf6-475f-b7ed-1232040c6a32","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6321,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000 USDC/AUSD\n- `slope`: 100,000,000 USDC/AUSD per day\n- `maxSlippage`: 0.1%","contentHash":"aacf875818c7f78c395d6a4c6ba1dbfeed0a8d1e71b940a7888bbb402b68c313","addressRefs":[]},"337c72cd-b626-458f-a4d3-a7e855a0c4fa":{"id":"337c72cd-b626-458f-a4d3-a7e855a0c4fa","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6322,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"77e3d9d0-7a70-4811-b60a-7bb91202e5df":{"id":"77e3d9d0-7a70-4811-b60a-7bb91202e5df","doc_no":"A.6.1.1.2.2.6.1.3.1.6.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6323,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"6d7f468e-e32c-4077-8dbc-66095e7b8f84":{"id":"6d7f468e-e32c-4077-8dbc-66095e7b8f84","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5","title":"Ethereum Mainnet - Curve AUSD/USDC LP Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6324,"content":"The documents herein contain the Instance Configuration Document for the Curve AUSD/USDC LP Instance.","contentHash":"a982241be4e5ed2d2b7f4865f214c8582746f9e1d856e887483da0d581e806d1","addressRefs":[]},"0ba7698b-d0ed-413e-8652-c2822c3ea7c3":{"id":"0ba7698b-d0ed-413e-8652-c2822c3ea7c3","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6325,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"5beb96b1-7975-42e2-90b6-67b92c01b60b":{"id":"5beb96b1-7975-42e2-90b6-67b92c01b60b","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6326,"content":"The documents herein define the parameters of the Curve AUSD/USDC LP Instance of the Allocation System Primitive.","contentHash":"76b77b2e4f8cb8af645945705d50d2620d340820aadf0a9ae156e0fbf2a9e356","addressRefs":[]},"1e8008c4-10c5-443e-85ae-36140449783f":{"id":"1e8008c4-10c5-443e-85ae-36140449783f","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6327,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"f16f6599-e1f2-482e-a1d0-7fac482abec3":{"id":"f16f6599-e1f2-482e-a1d0-7fac482abec3","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6328,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"79b0bed6-362b-4fb3-a3a1-0accb41ad704":{"id":"79b0bed6-362b-4fb3-a3a1-0accb41ad704","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6329,"content":"Curve AUSD/USDC","contentHash":"f0b08d9b52c522f03a5d3cbd23dcccf7a7d02ddbac7f931af69a0ba1d924772b","addressRefs":[]},"1c81fb59-4bfa-4635-ad2c-c3b0901128d6":{"id":"1c81fb59-4bfa-4635-ad2c-c3b0901128d6","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6330,"content":"USDC and AUSD","contentHash":"999ebdd48dd35012dd2f3891ace89987092855bf0933638e151fd9998c49469c","addressRefs":[]},"19bd5fb8-1f47-4be9-823c-8eea21bcab20":{"id":"19bd5fb8-1f47-4be9-823c-8eea21bcab20","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6331,"content":"AUSDUSDC","contentHash":"49187a99be2280ccf1068410be6278c3ca419d72a2914144cb15be2e82e3d8d1","addressRefs":[]},"37940251-3bd5-47f2-abe0-03aa036f2e51":{"id":"37940251-3bd5-47f2-abe0-03aa036f2e51","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6332,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"31b957ea-deb5-4143-a597-a5a094bd8c25":{"id":"31b957ea-deb5-4143-a597-a5a094bd8c25","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.2.1","title":"Underlying Asset Address (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6333,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"06c5e743-4d01-4325-a4c1-17680d1a79c1":{"id":"06c5e743-4d01-4325-a4c1-17680d1a79c1","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.2.2","title":"Underlying Asset Address (AUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6334,"content":"`0x00000000eFE302BEAA2b3e6e1b18d08D69a9012a`","contentHash":"a46d00e1291e0e83786e8b6f0f1f1fcad4c00f15b21c1cf91487ee0535a472a6","addressRefs":["0x00000000efe302beaa2b3e6e1b18d08d69a9012a"]},"63058463-a3d7-4a74-8a1b-a43e6cc20baa":{"id":"63058463-a3d7-4a74-8a1b-a43e6cc20baa","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6335,"content":"`0xE79C1C7E24755574438A26D5e062Ad2626C04662`","contentHash":"37cbbff6291880be1f2b9ff3408d403a77c36318493f81173b2272069c117a5e","addressRefs":["0xe79c1c7e24755574438a26d5e062ad2626c04662"]},"3c1c8cd1-ebaf-4138-a1c3-293af4849223":{"id":"3c1c8cd1-ebaf-4138-a1c3-293af4849223","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6336,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"e1565876-ecba-467b-9890-ebde7cf956d1":{"id":"e1565876-ecba-467b-9890-ebde7cf956d1","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6337,"content":"The inflow RateLimitID is: `0x67abf1af1d8f5f281e50b2b1f4587dacee38c7c1325bab70aa144056ba560538`.","contentHash":"02611049588af2e7a870f4853b20d6f27a1ada49ad02196d1e4cd49b341519f1","addressRefs":[]},"84b03f91-b152-4e24-a10c-4729908df9da":{"id":"84b03f91-b152-4e24-a10c-4729908df9da","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6338,"content":"The outflow RateLimitID is: `0x8b0ebe103264ec6caf8c9a6b03eeb13f101d3d1ece1fe8b70b17efb9153bb3fb`.","contentHash":"e9eaf61b7d0b938095ec0254d7a63337ba023ba9136f4b75f9636dc53390c943","addressRefs":[]},"6ce30263-7c13-4b45-ab75-e2b79e678272":{"id":"6ce30263-7c13-4b45-ab75-e2b79e678272","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6339,"content":"The current `maxAmount` and `slope` for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"e5eb411abadf20155e59acad4f3c0696c2b44cb3c8b38090d09489ca7a118f52","addressRefs":[]},"fe7ce511-f51b-4ed8-8ea1-30c4ae30e0bf":{"id":"fe7ce511-f51b-4ed8-8ea1-30c4ae30e0bf","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6340,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDC/AUSD\n- `slope`: 25,000,000 USDC/AUSD per day","contentHash":"58fefda5e7cb8b6e7f8273f5641a555650cee8257e40b4ebcf0d090da56dc738","addressRefs":[]},"5968dc38-0ac9-4c05-83b1-117fbe71c64c":{"id":"5968dc38-0ac9-4c05-83b1-117fbe71c64c","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6341,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"bff6b95b-dad1-4d5a-a8cf-26bd6944d93e":{"id":"bff6b95b-dad1-4d5a-a8cf-26bd6944d93e","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6342,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"ce053035-2796-4461-bbc8-b3c0ee0bcba3":{"id":"ce053035-2796-4461-bbc8-b3c0ee0bcba3","doc_no":"A.6.1.1.2.2.6.1.3.1.6.5.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6343,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"f168c4a8-f526-471e-8410-4f3f339e99d5":{"id":"f168c4a8-f526-471e-8410-4f3f339e99d5","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6","title":"Ethereum Mainnet - Curve PYUSD/USDS Swaps Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6344,"content":"The documents herein contain the Instance Configuration Document for the Curve PYUSD/USDS Swaps Instance.","contentHash":"e4346563aab73b5379f4c31cad2544ccb9fc48a4889a22b26bfc68ffb8207f80","addressRefs":[]},"a0f62040-5099-4e38-8db7-2fee0953ed21":{"id":"a0f62040-5099-4e38-8db7-2fee0953ed21","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6345,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"84afba1f-7050-4c57-94dc-f0d4ff5e976b":{"id":"84afba1f-7050-4c57-94dc-f0d4ff5e976b","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6346,"content":"The documents herein define the parameters of the Curve PYUSD/USDS Swaps Instance of the Allocation System Primitive.","contentHash":"ac0439a487319563c4189c51992aae4e3b15cc5eacbf6ab36e46dc7ccb819c89","addressRefs":[]},"83097786-002d-405f-966e-5502f4ef3d78":{"id":"83097786-002d-405f-966e-5502f4ef3d78","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6347,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"18b5144f-0fb4-4e58-ab17-ad5f4656a080":{"id":"18b5144f-0fb4-4e58-ab17-ad5f4656a080","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6348,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"2d7dbfa2-3dd3-43ee-9613-d9c4d6b8f830":{"id":"2d7dbfa2-3dd3-43ee-9613-d9c4d6b8f830","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6349,"content":"Curve PYUSD/USDS","contentHash":"643aa809c29fd8f22f2f3c96fffb2750930e8d1d2a40d61b6f763db5bab57611","addressRefs":[]},"78ade625-90af-4a60-a4da-d261f12cdca9":{"id":"78ade625-90af-4a60-a4da-d261f12cdca9","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6350,"content":"USDS and PYUSD","contentHash":"f15567c598355c9ed73c77fe5250a756a1eb38c9388b8497a2ed7fa8a42d0d09","addressRefs":[]},"61025ace-5e86-4671-88e9-5e6db1170890":{"id":"61025ace-5e86-4671-88e9-5e6db1170890","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6351,"content":"PYUSD/USDS","contentHash":"4f8fcdcdebb4012ab37455e9172c25de2a6a69e313187c30f9a2be92d86480f0","addressRefs":[]},"8bd50aee-8888-4a08-ac32-49ed69ef2b6f":{"id":"8bd50aee-8888-4a08-ac32-49ed69ef2b6f","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6352,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"77037711-fb38-435a-85e1-a177701710e9":{"id":"77037711-fb38-435a-85e1-a177701710e9","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.2.1","title":"Underlying Asset Address (USDS)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6353,"content":"`0xdC035D45d973E3EC169d2276DDab16f1e407384F`","contentHash":"70054b0ff65437cb32b35df32f8e11d1cc8ea540e9916e08d1cd96696d95e083","addressRefs":["0xdc035d45d973e3ec169d2276ddab16f1e407384f"]},"f02df9d0-e495-4896-ba88-806dca35d82c":{"id":"f02df9d0-e495-4896-ba88-806dca35d82c","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.2.2","title":"Underlying Asset Address (PYUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6354,"content":"`0x6c3ea9036406852006290770BEdFcAbA0e23A0e8`","contentHash":"cf0daac71d35ab865b50b412b6507da80922d98319a1d85cb7bbc731958009eb","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"dc239910-11ff-4b37-bffe-a98af705090b":{"id":"dc239910-11ff-4b37-bffe-a98af705090b","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6355,"content":"`0xA632D59b9B804a956BfaA9b48Af3A1b74808FC1f`","contentHash":"b80a642d598c5bc83f7cf2845d2d36212e8b59fe995ebf8660c32e4362e42258","addressRefs":["0xa632d59b9b804a956bfaa9b48af3a1b74808fc1f"]},"2a4bd826-18f2-4a58-b311-6fabb52b4f28":{"id":"2a4bd826-18f2-4a58-b311-6fabb52b4f28","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6356,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"2383066f-a8f7-4a7e-a953-5915ef366f60":{"id":"2383066f-a8f7-4a7e-a953-5915ef366f60","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6357,"content":"The inflow RateLimitID is: `0x495d2d5778d2cbf1ff13da2634eb38b1c7cfc08d120249eb740c796e40d80fb1`.","contentHash":"b627dd5cb4384218ba78121c0d13940f2ec6ed22eab10e4651e796f90ef72e00","addressRefs":[]},"72f0d0c1-4f88-4b4d-86ce-f7b558f05fd5":{"id":"72f0d0c1-4f88-4b4d-86ce-f7b558f05fd5","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6358,"content":"The outflow RateLimitID is: N/A.","contentHash":"483affad475b6c78cfa6846cb48795ff6ea43b13d4079c9d25d0d4a65e2aa3d7","addressRefs":[]},"4693cf03-c0fe-4ede-a83c-9af83d3cdcee":{"id":"4693cf03-c0fe-4ede-a83c-9af83d3cdcee","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6359,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"ad363791-a7e1-4a0c-8a8a-6102994c2876":{"id":"ad363791-a7e1-4a0c-8a8a-6102994c2876","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6360,"content":"The deposit rate limits are:\n\n- `maxAmount`: N/A - swaps only\n- `slope`: N/A - swaps only","contentHash":"9aacd74b2f328e23b05a3a9de3aec35bb15339552aa40aa664957a794e1f6695","addressRefs":[]},"b0b22bed-1cb0-43cd-bbdc-5f7fa48ebdab":{"id":"b0b22bed-1cb0-43cd-bbdc-5f7fa48ebdab","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6361,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A - swaps only","contentHash":"be46260dae2beffad3058dbca73d719da91f7f5f4e4b688e1af7e4d9a2f05aea","addressRefs":[]},"e3773f0c-33c5-4f55-93bf-69730b447deb":{"id":"e3773f0c-33c5-4f55-93bf-69730b447deb","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6362,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000 USDS/PYUSD\n- `slope`: 100,000,000 USDS/PYUSD per day\n- `maxSlippage`: 0.1%","contentHash":"b313c0f2dc00f07f3ff82a46539c0ae211ef2440e04d66c0c30be295b3cd575f","addressRefs":[]},"f484c818-9696-4cde-994d-d4218277a486":{"id":"f484c818-9696-4cde-994d-d4218277a486","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6363,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"fb16c677-3521-4250-8c9d-3e68155f9afd":{"id":"fb16c677-3521-4250-8c9d-3e68155f9afd","doc_no":"A.6.1.1.2.2.6.1.3.1.6.6.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6364,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"d03f121c-7853-4dc7-85d8-f231aaa64a68":{"id":"d03f121c-7853-4dc7-85d8-f231aaa64a68","doc_no":"A.6.1.1.2.2.6.1.3.1.7","title":"Morpho","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6365,"content":"The Ethereum Mainnet Instances of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"e9eca72d304ea5bab98e0c173553d3a6061edbb10327e17a038f36999f8a339a","addressRefs":[]},"29cb8322-96f5-4f18-b4fe-eb31826af580":{"id":"29cb8322-96f5-4f18-b4fe-eb31826af580","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1","title":"Ethereum Mainnet - Morpho Grove x Steakhouse High Yield Vault USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6366,"content":"The documents herein contain the Instance Configuration Document for the Morpho Grove x Steakhouse High Yield Vault USDC Instance.","contentHash":"ad0f4ed5721864ff8569bc626c4e60c46859735c9388743e7afcce605511c9af","addressRefs":[]},"6127e31a-798c-41eb-90d5-044d9b214d2a":{"id":"6127e31a-798c-41eb-90d5-044d9b214d2a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6367,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"7cdf8908-1adc-421d-9c71-37d138f99b20":{"id":"7cdf8908-1adc-421d-9c71-37d138f99b20","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6368,"content":"The documents herein define the parameters of the Morpho Grove x Steakhouse High Yield Vault USDC Instance of the Allocation System Primitive.","contentHash":"ff111421aa0cbdbf8a0489b19c327b7c8a1c045e900024a1dfeeec34d4787c52","addressRefs":[]},"260778ff-223a-4aca-a262-cd20aafe5f49":{"id":"260778ff-223a-4aca-a262-cd20aafe5f49","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6369,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"f4e45e27-3775-46e7-9f7f-ada5fb72bc27":{"id":"f4e45e27-3775-46e7-9f7f-ada5fb72bc27","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6370,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"a9e1a42f-d92b-4658-814a-2ad449de6eb5":{"id":"a9e1a42f-d92b-4658-814a-2ad449de6eb5","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6371,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"a810c912-a460-4a1f-ac0d-838eb6ff2f04":{"id":"a810c912-a460-4a1f-ac0d-838eb6ff2f04","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6372,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"4e19d59e-628e-4478-a986-6418879f03b2":{"id":"4e19d59e-628e-4478-a986-6418879f03b2","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6373,"content":"grove-bbqUSDC","contentHash":"3e56f375e1c8f3648d19469a73803751085410f59898449d39136725ab91e31b","addressRefs":[]},"94042273-29a0-4538-833b-1ea63b737db1":{"id":"94042273-29a0-4538-833b-1ea63b737db1","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6374,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"dcdff78c-809f-4ec8-80a2-36c124ca9ae8":{"id":"dcdff78c-809f-4ec8-80a2-36c124ca9ae8","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6375,"content":"`0xBEEf2B5FD3D94469b7782aeBe6364E6e6FB1B709`","contentHash":"80c14ee2dfa4db8f3a772ea52afdff77311a4deae72585470a6c74f9b4938614","addressRefs":["0xbeef2b5fd3d94469b7782aebe6364e6e6fb1b709"]},"ff7b0875-7f6d-4b18-b609-34eec3f725a0":{"id":"ff7b0875-7f6d-4b18-b609-34eec3f725a0","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6376,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"35269818-4f06-49a8-8675-f7da3f616976":{"id":"35269818-4f06-49a8-8675-f7da3f616976","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6377,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"e258f0cd-0b47-464a-bcdb-78fdfb3451a2":{"id":"e258f0cd-0b47-464a-bcdb-78fdfb3451a2","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6378,"content":"The inflow RateLimitID is: `0x82fb6a87781d1c18617960e9528d0633bfbc534f5ae8109347f10bb49a2f4f19`.","contentHash":"6a213c5f2998641b5672d40171bebba974b971cfc93821d10a994d1e97b6861e","addressRefs":[]},"a7ad7e2a-5c2e-4231-94d4-cdd14d526c1d":{"id":"a7ad7e2a-5c2e-4231-94d4-cdd14d526c1d","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6379,"content":"**Outflow RateLimitID** _(Core)_ - The outflow RateLimitID is: `0xe668276e49fbcb8fc24c716adf328ec4602ad894aaeabc608d172aadfd5cd485`.","contentHash":"a253d20f9e078ea0f9f04c275812ab4fdb68f5eee04c87ab789379606254c03e","addressRefs":[]},"a907ce48-a651-4cc9-a382-82e989f3ee50":{"id":"a907ce48-a651-4cc9-a382-82e989f3ee50","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6380,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"dbb8ef9e-c2ce-43b5-b320-bae57f6cb993":{"id":"dbb8ef9e-c2ce-43b5-b320-bae57f6cb993","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6381,"content":"The deposit rate limits are:\n\n- `maxAmount`: 20,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"ffdc79e6800e455c82d3ce02c5697652fcbe21fc1d3fa74a4f01206f02d8fcf1","addressRefs":[]},"b4ca4845-a846-479b-aaf8-e83e73bf25f7":{"id":"b4ca4845-a846-479b-aaf8-e83e73bf25f7","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6382,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"1ab38f81-28f4-4262-8529-37ef7d43e087":{"id":"1ab38f81-28f4-4262-8529-37ef7d43e087","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6383,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"9c79b4b9-8584-4414-bddf-36158d01dc20":{"id":"9c79b4b9-8584-4414-bddf-36158d01dc20","doc_no":"A.6.1.1.2.2.6.1.3.1.7.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6384,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"27f06e65-8397-449a-b002-abaa0416badc":{"id":"27f06e65-8397-449a-b002-abaa0416badc","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2","title":"Ethereum Mainnet - Monad Morpho Grove x Steakhouse High Yield Vault AUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6385,"content":"The documents herein contain the Instance Configuration Document for the Monad Morpho Grove x Steakhouse High Yield Vault AUSD Instance.","contentHash":"d2a456263f9d957856ed5ad1d4154b9c45d75baaf6439c516c0904478061199d","addressRefs":[]},"1487eca9-bca3-48ee-992b-cdd6f90cf2e1":{"id":"1487eca9-bca3-48ee-992b-cdd6f90cf2e1","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6386,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"4ed65dea-eefa-4cfc-93e8-99187aa14f7f":{"id":"4ed65dea-eefa-4cfc-93e8-99187aa14f7f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6387,"content":"The documents herein define the parameters of the Monad Morpho Grove x Steakhouse High Yield Vault AUSD Instance of the Allocation System Primitive.","contentHash":"0e99c513e481a71b69ced9e0f11ad5e906f8ee2e8858ffc5faadbd2b07779a9f","addressRefs":[]},"5852f668-1d79-4e62-8f8d-c1f77cec33e5":{"id":"5852f668-1d79-4e62-8f8d-c1f77cec33e5","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6388,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"be6bd732-a6d7-4a75-8d1c-b4d5103bc81c":{"id":"be6bd732-a6d7-4a75-8d1c-b4d5103bc81c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6389,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"0c9f30fb-8428-409d-9c76-a48426147bef":{"id":"0c9f30fb-8428-409d-9c76-a48426147bef","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6390,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"f6ba1cac-6a1c-4030-b490-307906cf4350":{"id":"f6ba1cac-6a1c-4030-b490-307906cf4350","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6391,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"db5c25d7-e55c-46cf-adcd-2f96c65eccb1":{"id":"db5c25d7-e55c-46cf-adcd-2f96c65eccb1","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6392,"content":"grove-bbqAUSD","contentHash":"a7996f501b8313332375803a38192562ea1f828f177b33f9fe9efb2372b00719","addressRefs":[]},"4b90512d-d7af-445c-884b-a57d0e86b5bd":{"id":"4b90512d-d7af-445c-884b-a57d0e86b5bd","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6393,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"fa192507-8cee-42fd-a88a-70d962f8e760":{"id":"fa192507-8cee-42fd-a88a-70d962f8e760","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.2.1","title":"Token Address (Monad)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6394,"content":"`0x32841A8511D5c2c5b253f45668780B99139e476D`","contentHash":"7f1445ac0e264a051697aebea5cc2c9d9ddd4bdef54600ff321af6ffc710fbf1","addressRefs":["0x32841a8511d5c2c5b253f45668780b99139e476d"]},"91bb8ea0-7ca5-4c22-8979-cf6b2262f020":{"id":"91bb8ea0-7ca5-4c22-8979-cf6b2262f020","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6395,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"19f94109-c950-40e8-949b-dfaf108b90f4":{"id":"19f94109-c950-40e8-949b-dfaf108b90f4","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6396,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"e94b8732-7022-4fca-a7ab-b1c92757aa55":{"id":"e94b8732-7022-4fca-a7ab-b1c92757aa55","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6397,"content":"The inflow RateLimitID is: `0x098ad67dc41c1a5892ec3ef5fd411198dc11962475e9ef2e0362e6cb7f5a2174`.","contentHash":"d5831c000409652ebf8d301bc269e8a3d8122742ea4ee58b92f5995b66bdf4ce","addressRefs":[]},"94c5adb4-8f74-4c8c-ba53-d06b79fd395a":{"id":"94c5adb4-8f74-4c8c-ba53-d06b79fd395a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6398,"content":"The outflow RateLimitID is: N/A.","contentHash":"483affad475b6c78cfa6846cb48795ff6ea43b13d4079c9d25d0d4a65e2aa3d7","addressRefs":[]},"56d33b3e-5c61-40bf-aaa1-d53cf78ac33c":{"id":"56d33b3e-5c61-40bf-aaa1-d53cf78ac33c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6399,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"f8a8a1ee-fb6c-4f4a-a7e8-c41f8dcccf1a":{"id":"f8a8a1ee-fb6c-4f4a-a7e8-c41f8dcccf1a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6400,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"d611f80cb40a432ea119c598c732961d7f492579e57452513915d7b2368d3fdd","addressRefs":[]},"99db86e0-e883-475e-a736-11aa5b3dab5e":{"id":"99db86e0-e883-475e-a736-11aa5b3dab5e","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6401,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A\n- `slope`: N/A","contentHash":"868ef21c91f22d83076d592b9bfad81c108b9a5c1eed56322abe0eafea2d3a7a","addressRefs":[]},"766eb787-b52c-47f0-bc07-3bcf51765c55":{"id":"766eb787-b52c-47f0-bc07-3bcf51765c55","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6402,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"3076a14b-eadb-4d3b-87d3-c8ff7e17c420":{"id":"3076a14b-eadb-4d3b-87d3-c8ff7e17c420","doc_no":"A.6.1.1.2.2.6.1.3.1.7.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6403,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"6ec606f0-bc47-4f36-8591-75784bb78b00":{"id":"6ec606f0-bc47-4f36-8591-75784bb78b00","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3","title":"Ethereum Mainnet - Grove x Steakhouse USDC Morpho Vault v2 Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6404,"content":"The documents herein contain the Instance Configuration Document for the Grove x Steakhouse USDC Morpho Vault v2 Instance.","contentHash":"83b4d0636ead8844d20dd037588a9f8e9e11b1a911da9fe33e4f5eda58292739","addressRefs":[]},"87d15c86-c604-465b-b920-050a1aabcb0c":{"id":"87d15c86-c604-465b-b920-050a1aabcb0c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6405,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"74f5efe4-582c-4b44-9235-71495f81ae51":{"id":"74f5efe4-582c-4b44-9235-71495f81ae51","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6406,"content":"The documents herein define the parameters of the Grove x Steakhouse USDC Morpho Vault v2 Instance of the Allocation System Primitive.","contentHash":"e2c7b4299a6bbf228a5c77ec8d2d185f434a2c8a4053ae8c927d0375ef7cd515","addressRefs":[]},"b9e733de-e621-42eb-b000-37195c47f395":{"id":"b9e733de-e621-42eb-b000-37195c47f395","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6407,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"7d5a86c8-1d10-49cc-9547-58bf93fb7eb0":{"id":"7d5a86c8-1d10-49cc-9547-58bf93fb7eb0","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6408,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"25ee9e5c-32d3-488a-82c2-495496964b23":{"id":"25ee9e5c-32d3-488a-82c2-495496964b23","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6409,"content":"Grove x Steakhouse USDC High Yield Vault V2","contentHash":"4607f35d4abdc2cc03cb8df7b1ef620f2629cbb0905ecf988769e4eea46b94a1","addressRefs":[]},"d1a9b070-f3c7-48e7-9bff-f2f0e17acc14":{"id":"d1a9b070-f3c7-48e7-9bff-f2f0e17acc14","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6410,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"45924aa7-76e2-4375-9b20-cd781f0a8e09":{"id":"45924aa7-76e2-4375-9b20-cd781f0a8e09","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6411,"content":"grove-bbqUSDC","contentHash":"3e56f375e1c8f3648d19469a73803751085410f59898449d39136725ab91e31b","addressRefs":[]},"a6b3dc78-d595-4224-ac9f-bc38d87f683b":{"id":"a6b3dc78-d595-4224-ac9f-bc38d87f683b","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6412,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"3c0cd2b5-035d-460d-92dd-b45c1e7a64a1":{"id":"3c0cd2b5-035d-460d-92dd-b45c1e7a64a1","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6413,"content":"`0xBeefF08dF54897e7544aB01d0e86f013DA354111`","contentHash":"1c68a84e9baf6b6dddb5e7c77332c8dae42bf3b93ef1ced835131cb5df9c7173","addressRefs":["0xbeeff08df54897e7544ab01d0e86f013da354111"]},"76adcd24-8473-4e8e-a42c-0c7583e13936":{"id":"76adcd24-8473-4e8e-a42c-0c7583e13936","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6414,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"23ecc971-d297-4a06-98da-1e7620f5a823":{"id":"23ecc971-d297-4a06-98da-1e7620f5a823","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6415,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"f6b59efd-b87c-4d35-b416-f582359c98ac":{"id":"f6b59efd-b87c-4d35-b416-f582359c98ac","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6416,"content":"The inflow RateLimitID is: `0xe9ff67ad8829919752eee93c75433e7e23f3460ca6b1d9576fae94f669fbc4d6`.","contentHash":"c5d202410edd4e26e27ce26ab1e2c893a5429199f807eba8604a1fb694434750","addressRefs":[]},"76749308-cb2d-4c39-ad38-90c3baebb6e8":{"id":"76749308-cb2d-4c39-ad38-90c3baebb6e8","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6417,"content":"The outflow RateLimitID is: `0xb6204f88cd26e1d2b5c27fe0beb10cc2c6a33aac17f228baffcb5cc3c8429a7b`.","contentHash":"b45c70a6c628920d3447e3f482cc0687ff413f24acf7bf143808e36711d49b5d","addressRefs":[]},"fdf5c673-201d-4866-8e95-d041f481f3cc":{"id":"fdf5c673-201d-4866-8e95-d041f481f3cc","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6418,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"506f5294-ad79-4ace-98b9-75d694072a3d":{"id":"506f5294-ad79-4ace-98b9-75d694072a3d","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6419,"content":"The deposit rate limits are:\n\n- `maxAmount`: 20,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"ffdc79e6800e455c82d3ce02c5697652fcbe21fc1d3fa74a4f01206f02d8fcf1","addressRefs":[]},"7e38063c-c6a7-4d45-9344-bd3b22047019":{"id":"7e38063c-c6a7-4d45-9344-bd3b22047019","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6420,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"6894aa1a-4e6d-4372-a989-34258aeddf00":{"id":"6894aa1a-4e6d-4372-a989-34258aeddf00","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.4.3","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6421,"content":"Controllers now have protections that require a `maxExchangeRate` to be set for deposits. The following ensures 1 share can represent at most 2 USDC.\n\n- `setMaxExchangeRate(GROVE_X_STEAKHOUSE_USDC_V2, 1e18, 2e6)`","contentHash":"4565ab1e089b5caf6854e5588b1b5b20ec986bed5e7575cd2e56073dd49c606a","addressRefs":[]},"0de4574b-adc6-4e83-9a8d-e6bcf97bf73e":{"id":"0de4574b-adc6-4e83-9a8d-e6bcf97bf73e","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6422,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"feabeb3e-73d4-4acc-acb9-33cd0cc5bf53":{"id":"feabeb3e-73d4-4acc-acb9-33cd0cc5bf53","doc_no":"A.6.1.1.2.2.6.1.3.1.7.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6423,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"0b7e1d3d-1f56-48a6-9729-88479aa5ff92":{"id":"0b7e1d3d-1f56-48a6-9729-88479aa5ff92","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4","title":"Ethereum Mainnet - Steakhouse PYUSD Morpho Vault Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6424,"content":"The documents herein contain the Instance Configuration Document for the Steakhouse PYUSD Morpho Vault Instance.","contentHash":"f863679243841a82890ea58b884f3c75e36b7c581d078f303ea0438d09a77ca7","addressRefs":[]},"b9d9d24c-2d3a-4eec-88fe-2b7a47ab369c":{"id":"b9d9d24c-2d3a-4eec-88fe-2b7a47ab369c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6425,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"f7048cf9-6517-48b9-8768-74a0160a8cea":{"id":"f7048cf9-6517-48b9-8768-74a0160a8cea","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6426,"content":"The documents herein define the parameters of the Steakhouse PYUSD Morpho Vault Instance of the Allocation System Primitive.","contentHash":"1f65de4917d9a8d59fc83788ac015ea1960690cf4cf7be138565b7bb423b7c8b","addressRefs":[]},"42f30ffc-3820-4965-a112-1ab3c303d51b":{"id":"42f30ffc-3820-4965-a112-1ab3c303d51b","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6427,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"99b185bd-c32d-4454-9c22-579f6ac4fd15":{"id":"99b185bd-c32d-4454-9c22-579f6ac4fd15","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6428,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"0963963e-de9c-4470-9d89-6932657f8283":{"id":"0963963e-de9c-4470-9d89-6932657f8283","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6429,"content":"Steakhouse PYUSD Morpho Vault","contentHash":"6ee1a3a31ef44389103cb5336f74e7d12ee513cb376c0c7dd9fd0613d4866137","addressRefs":[]},"f1b5c4b3-9d93-4c2e-b7fb-6e42f5987ea5":{"id":"f1b5c4b3-9d93-4c2e-b7fb-6e42f5987ea5","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6430,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"051f1879-4b97-41cb-90be-1ac54da4cab4":{"id":"051f1879-4b97-41cb-90be-1ac54da4cab4","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6431,"content":"grove-bbqPYUSD","contentHash":"fb4b3e3742b31a953baaa22d3d8f6e612fffef913aed37b070ec55046782e44d","addressRefs":[]},"958415c3-8983-4cd1-926e-5ec2029926b3":{"id":"958415c3-8983-4cd1-926e-5ec2029926b3","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6432,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"b7a5cbbf-15c4-4b0e-ba18-4dfa9994a212":{"id":"b7a5cbbf-15c4-4b0e-ba18-4dfa9994a212","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6433,"content":"`0xd8A6511979D9C5D387c819E9F8ED9F3a5C6c5379`","contentHash":"cbf6a8905a426028c2879260f12c4f49ef41c139d6aec3ce171a7d98df65dea5","addressRefs":["0xd8a6511979d9c5d387c819e9f8ed9f3a5c6c5379"]},"c9d27694-0ebd-4f06-b5b3-07c3879bf438":{"id":"c9d27694-0ebd-4f06-b5b3-07c3879bf438","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6434,"content":"`0x6c3ea9036406852006290770BEdFcAbA0e23A0e8`","contentHash":"cf0daac71d35ab865b50b412b6507da80922d98319a1d85cb7bbc731958009eb","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"d0a539f7-83a1-4aef-9a4a-050d4ba8596a":{"id":"d0a539f7-83a1-4aef-9a4a-050d4ba8596a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6435,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"288e9dc2-d8a6-40c9-b501-aec06f7c1e11":{"id":"288e9dc2-d8a6-40c9-b501-aec06f7c1e11","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6436,"content":"The inflow RateLimitID is: `0xfc4e1f8ba7b0389a287411c3f6b97cc0ec60fb2816bfaa31e12a21561486321a`.","contentHash":"32c62ed255a45d5f03f22d8500bfab5cfaca5a684ab3c08a0d7fc13ea1a4ece1","addressRefs":[]},"79ed24a8-d0ca-4da7-861a-66ae676eafcb":{"id":"79ed24a8-d0ca-4da7-861a-66ae676eafcb","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6437,"content":"The outflow RateLimitID is: `0xa0c827fea02219c83969babf0bd29df5bb5fe923e6b38491a5eea797984995e8`.","contentHash":"370ad1dcfe38bcd93164902459158c830cd8c281e3b557a59b29c61084ff6654","addressRefs":[]},"72af86dd-3a15-4245-8a90-5ae8100f49d9":{"id":"72af86dd-3a15-4245-8a90-5ae8100f49d9","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6438,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"aec6eb4d-103c-49e0-9d05-befc5dda716c":{"id":"aec6eb4d-103c-49e0-9d05-befc5dda716c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6439,"content":"The deposit rate limits are:\n\n- `maxAmount`: 20,000,000 PYUSD\n- `slope`: 20,000,000 PYUSD per day","contentHash":"bfb4214028e6835efbc3ca781c640fdd6e4de0b22b10a0eab8cc2341a14347d6","addressRefs":[]},"77112a8a-c39e-49da-b476-c97ebcb2d197":{"id":"77112a8a-c39e-49da-b476-c97ebcb2d197","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6440,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"c5fa2d90-df64-406e-a53d-9694d448b161":{"id":"c5fa2d90-df64-406e-a53d-9694d448b161","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.4.3","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6441,"content":"Controllers now have protections that require a `maxExchangeRate` to be set for deposits. The following ensures 1 share can represent at most 4 PYUSD (current share price is 2).\n\n- `setMaxExchangeRate(STEAKHOUSE_PYUSD_MAIN, 1e18, 4e6)`","contentHash":"83412cc388e93bdb179cd32951aca16083cfdaa8054bced0e133b3183d34c0c6","addressRefs":[]},"9f9f27c9-ad65-4afe-8ef7-de0eacfe3acc":{"id":"9f9f27c9-ad65-4afe-8ef7-de0eacfe3acc","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6442,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"fa6a6475-92d9-48b1-9033-6b1c196d9ead":{"id":"fa6a6475-92d9-48b1-9033-6b1c196d9ead","doc_no":"A.6.1.1.2.2.6.1.3.1.7.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6443,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"2c21462b-2925-48d8-9578-5fc21aa96563":{"id":"2c21462b-2925-48d8-9578-5fc21aa96563","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5","title":"Ethereum Mainnet - Grove x Steakhouse AUSD Morpho Vault V2 Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6444,"content":"The documents herein contain the Instance Configuration Document for the Grove x Steakhouse AUSD Morpho Vault V2 Instance.","contentHash":"842e9d0b21e1fa8e3c2de81ad584546d3d8845254430c5e67893def37109d41f","addressRefs":[]},"72d9d7fd-d236-43b7-9f02-77686a08be2b":{"id":"72d9d7fd-d236-43b7-9f02-77686a08be2b","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6445,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"284c435d-c60f-4d62-82e6-f70b9fd18170":{"id":"284c435d-c60f-4d62-82e6-f70b9fd18170","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6446,"content":"The documents herein define the parameters of the Grove x Steakhouse AUSD Morpho Vault V2 Instance of the Allocation System Primitive.","contentHash":"e0cea81510b766d3966a4a4506e838e23e6598f85d460bc303a3aa242b16ea23","addressRefs":[]},"0a6567d0-f433-4403-9bf0-e5f420e25759":{"id":"0a6567d0-f433-4403-9bf0-e5f420e25759","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6447,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"b2ce1772-2114-4042-873f-6434878c7b7e":{"id":"b2ce1772-2114-4042-873f-6434878c7b7e","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6448,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"70d6adc5-11a6-4058-887c-d277141bb1a8":{"id":"70d6adc5-11a6-4058-887c-d277141bb1a8","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6449,"content":"Grove x Steakhouse AUSD Morpho Vault","contentHash":"d21aed344de982889f05cead5a3a58981b9a6f2cf16516c2972b8d58432c92ba","addressRefs":[]},"9cba6bc2-2481-4fca-922c-160b02c59c70":{"id":"9cba6bc2-2481-4fca-922c-160b02c59c70","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6450,"content":"AUSD","contentHash":"d69492cb9237a4fe661cfb22b5603601d01ac18c772fdc7ebb10edd6fdf51f19","addressRefs":[]},"3ae27c28-7005-4b95-84e9-2eadfd88987a":{"id":"3ae27c28-7005-4b95-84e9-2eadfd88987a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6451,"content":"grove-bbqAUSD","contentHash":"a7996f501b8313332375803a38192562ea1f828f177b33f9fe9efb2372b00719","addressRefs":[]},"aee5af4c-bc06-4e40-a046-61c8fae70d5f":{"id":"aee5af4c-bc06-4e40-a046-61c8fae70d5f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6452,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"69648727-b4ab-45e7-85f9-c2846917d944":{"id":"69648727-b4ab-45e7-85f9-c2846917d944","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6453,"content":"`0xBEEfF0d672ab7F5018dFB614c93981045D4aA98a`","contentHash":"422a04c448e987dbceb5e3711dee50ef5597114f9e6c1afbe55c428dbe7d56fc","addressRefs":["0xbeeff0d672ab7f5018dfb614c93981045d4aa98a"]},"5ec16337-978a-4b21-bf47-326db289a2ef":{"id":"5ec16337-978a-4b21-bf47-326db289a2ef","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6454,"content":"`0x00000000eFE302BEAA2b3e6e1b18d08D69a9012a`","contentHash":"a46d00e1291e0e83786e8b6f0f1f1fcad4c00f15b21c1cf91487ee0535a472a6","addressRefs":["0x00000000efe302beaa2b3e6e1b18d08d69a9012a"]},"112d2a3d-0241-446e-96e8-36a25715c275":{"id":"112d2a3d-0241-446e-96e8-36a25715c275","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6455,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"e7301d05-fbbf-4786-bd6e-55bfc1d4247a":{"id":"e7301d05-fbbf-4786-bd6e-55bfc1d4247a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6456,"content":"The inflow RateLimitID is: `0x09b5f924263c1b33d619ff1c9c794ddf57bc2eb0f618e2cf5cfd838abecb541d`.","contentHash":"561c84f108a87b0b5be83f0911b366b57de6a6dac3fe2e2b83db22d924f98e64","addressRefs":[]},"0e535792-539f-42a5-b8a0-d309fd7ac3d0":{"id":"0e535792-539f-42a5-b8a0-d309fd7ac3d0","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6457,"content":"The outflow RateLimitID is: `0xdd975e5dc9904260242e80bbe7035784e9108c619e23f21b62342fae3226e0fe`.","contentHash":"8b360f4017f58d5246e21bfbe404c60f811638114edbae145bb6f2fe9fa58bb8","addressRefs":[]},"194a91d6-902b-4e2f-b416-cfd681addbde":{"id":"194a91d6-902b-4e2f-b416-cfd681addbde","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6458,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"c2b5471f-85af-4c3f-91af-3bf8d9492178":{"id":"c2b5471f-85af-4c3f-91af-3bf8d9492178","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6459,"content":"The deposit rate limits are:\n\n- `maxAmount`: 20,000,000 AUSD\n- `slope`: 20,000,000 AUSD per day","contentHash":"8a8cd6b6c7989c48bdc4d45dd878335aaa615880208cf0a18df195263abbebfe","addressRefs":[]},"ee2bb8e1-0e9d-4372-875c-22c8fbeafdf2":{"id":"ee2bb8e1-0e9d-4372-875c-22c8fbeafdf2","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6460,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"b8064e80-74cf-428e-9783-e03ed597a1f7":{"id":"b8064e80-74cf-428e-9783-e03ed597a1f7","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6461,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"ac75dba3-94e0-4bd9-8a4a-24eb93c488dd":{"id":"ac75dba3-94e0-4bd9-8a4a-24eb93c488dd","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6462,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"32ccb033-854c-45b2-b5f4-364e5eabc5f5":{"id":"32ccb033-854c-45b2-b5f4-364e5eabc5f5","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6463,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer parameters.","contentHash":"fb9cdee40bad95b4561c802450d9f2390b5c2ba57f0791739315c5e5ddbba48f","addressRefs":[]},"c7a016f1-0d8d-47ad-b91e-39d1a285b149":{"id":"c7a016f1-0d8d-47ad-b91e-39d1a285b149","doc_no":"A.6.1.1.2.2.6.1.3.1.7.5.4.1","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6464,"content":"Controllers now have protections that require a `maxExchangeRate` to be set for deposits. The following ensures 1 share can represent at most 2 AUSD:\n\n- `setMaxExchangeRate(GROVE_X_STEAKHOUSE_AUSD_V2, 1e18, 2e6)`","contentHash":"1b796bd811b4c40363b7070388563d98092a2e52a9cad81b04a4575a52d72064","addressRefs":[]},"3e940e02-80eb-4e37-bce6-95939089da46":{"id":"3e940e02-80eb-4e37-bce6-95939089da46","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6","title":"Ethereum Mainnet - Sentora PYUSD Morpho Vault V2 Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6465,"content":"The documents herein contain the Instance Configuration Document for the Sentora PYUSD Morpho Vault V2 Instance.","contentHash":"63c95a1b92a3941e10e4f80802e8a62cdee9aeb051dd469cc811ecd230c2def0","addressRefs":[]},"3fd05c9a-1d93-47f6-967d-6edb31f522fd":{"id":"3fd05c9a-1d93-47f6-967d-6edb31f522fd","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6466,"content":"`Pending`","contentHash":"2986effe9fae335e819f546d8f69212a5a1e8bd5f01a449e4e295a5dee70536f","addressRefs":[]},"7b251172-7a60-4240-af72-cacaca9fe3cc":{"id":"7b251172-7a60-4240-af72-cacaca9fe3cc","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6467,"content":"The documents herein define the parameters of the Sentora PYUSD Morpho Vault V2 Instance of the Allocation System Primitive.","contentHash":"82e7a46bd740e6b14b1b980b0063cf8d7154ce323ad6c9230e9e20c6ec26dffe","addressRefs":[]},"3d387fde-f4b9-47c0-8852-f4d9367c0369":{"id":"3d387fde-f4b9-47c0-8852-f4d9367c0369","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6468,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"0075ec52-7324-41b5-8849-e91bac55e742":{"id":"0075ec52-7324-41b5-8849-e91bac55e742","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6469,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"be9b2600-3021-4bb6-9eaf-ba92f17ccd61":{"id":"be9b2600-3021-4bb6-9eaf-ba92f17ccd61","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6470,"content":"Sentora PYUSD Morpho Vault V2","contentHash":"f6c4c7f2a230d56f5c38440728ec47fa7d88b7c5e79104817b58037d4767fd2d","addressRefs":[]},"8ba12c10-ec4f-4f37-a59c-4c34e14e1a8d":{"id":"8ba12c10-ec4f-4f37-a59c-4c34e14e1a8d","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6471,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"dbf0b180-07ad-4a4b-8cdb-b2c1ae7f2c7a":{"id":"dbf0b180-07ad-4a4b-8cdb-b2c1ae7f2c7a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6472,"content":"senPYUSDmain","contentHash":"c1cfbb22367f6acf5872225f0b709e6bad962b7881760ded7299b10af4448ec2","addressRefs":[]},"6a5becdf-2cb6-44c3-b93a-793072d5ff7b":{"id":"6a5becdf-2cb6-44c3-b93a-793072d5ff7b","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6473,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"9a0baa90-6aec-4be5-9ae5-4d3c790473a8":{"id":"9a0baa90-6aec-4be5-9ae5-4d3c790473a8","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6474,"content":"`0xb576765fB15505433aF24FEe2c0325895C559FB2`","contentHash":"0f84a07502d0f82234b5d4d20f974a8b1a834747f24dd2d2970ea154ae54bfb1","addressRefs":["0xb576765fb15505433af24fee2c0325895c559fb2"]},"412793f2-1e8e-490c-8604-3c457d54d6ed":{"id":"412793f2-1e8e-490c-8604-3c457d54d6ed","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6475,"content":"`0x6c3ea9036406852006290770BEdFcAbA0e23A0e8`","contentHash":"cf0daac71d35ab865b50b412b6507da80922d98319a1d85cb7bbc731958009eb","addressRefs":["0x6c3ea9036406852006290770bedfcaba0e23a0e8"]},"fce963cb-ade1-463e-a88f-898a30586e51":{"id":"fce963cb-ade1-463e-a88f-898a30586e51","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6476,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"31d24068-b9bf-43d7-8333-df129e00ee61":{"id":"31d24068-b9bf-43d7-8333-df129e00ee61","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6477,"content":"The inflow RateLimitID is: `0x4dc0c7cd471560aa12324cb36f720d7d301ef230d3ae772ae07b681725ae7b66`","contentHash":"b36db380a1525a4cbb3b9262c3eb4077fef675f378dc8c8489d8c382c7eaba04","addressRefs":[]},"cdd99b5b-34aa-42d5-b93a-0abda5ae7f0f":{"id":"cdd99b5b-34aa-42d5-b93a-0abda5ae7f0f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6478,"content":"The outflow RateLimitID is: `0x8edef92c8bf76460b6b832a88c63768022ac5aa2bd862fb858905a0f024bff8b`","contentHash":"6c1efff85ce1e808fed142e16402fcadf9d9608fca65962c4804a8222fc218e3","addressRefs":[]},"b94aa9b1-62c6-40dc-8b92-cc677ebac016":{"id":"b94aa9b1-62c6-40dc-8b92-cc677ebac016","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6479,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"0a4b26e1-5757-4ed9-bfc5-2614cc79500f":{"id":"0a4b26e1-5757-4ed9-bfc5-2614cc79500f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6480,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 PYUSD\n- `slope`: 50,000,000 PYUSD per day","contentHash":"5916fbeb91d58dbb5cb6245e42d5e97759babb64035b2ca3830c65d2d0b9eec6","addressRefs":[]},"3d7d307c-ffdc-4ca3-b9fa-951b02d46e3f":{"id":"3d7d307c-ffdc-4ca3-b9fa-951b02d46e3f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6481,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"143d4637-38b8-404c-ba4c-932796445fc8":{"id":"143d4637-38b8-404c-ba4c-932796445fc8","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6482,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"8c1e6098-3342-4d00-b314-d4e87f005dc2":{"id":"8c1e6098-3342-4d00-b314-d4e87f005dc2","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.2.5.1","title":"Maximum Exposure","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6483,"content":"The Maximum Exposure for this Instance is 0 USD.","contentHash":"000c2700aa2243b26617bab03c6cf2fc7bca87d60d9b2ebeb94ce3731f5af748","addressRefs":[]},"4eb5ab52-f412-4d4f-8d9e-5ac9b883eb77":{"id":"4eb5ab52-f412-4d4f-8d9e-5ac9b883eb77","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6484,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"8f2a06dd-60cb-4930-9f15-e8dae35444a9":{"id":"8f2a06dd-60cb-4930-9f15-e8dae35444a9","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6485,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer parameters.","contentHash":"fb9cdee40bad95b4561c802450d9f2390b5c2ba57f0791739315c5e5ddbba48f","addressRefs":[]},"1f14f407-9eeb-4e6b-bf6e-c837b5560f28":{"id":"1f14f407-9eeb-4e6b-bf6e-c837b5560f28","doc_no":"A.6.1.1.2.2.6.1.3.1.7.6.4.1","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6486,"content":"Controllers now have protections that require a `maxExchangeRate` to be set for deposits. The following ensures 1 share can represent at most 3 PYUSD:\n\n- `setMaxExchangeRate(SENTORA_PYUSD_MAIN_V2, 1e18, 3e6)`","contentHash":"46820cb0765da248edc1de275e39fd66e55d14c41c45b037b1e225d5312460e3","addressRefs":[]},"dff6df5f-f8ab-4df1-be1e-f71510c3534e":{"id":"dff6df5f-f8ab-4df1-be1e-f71510c3534e","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7","title":"Ethereum Mainnet - Sentora RLUSD Morpho Vault V2 Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6487,"content":"The documents herein contain the Instance Configuration Document for the Sentora RLUSD Morpho Vault V2 Instance.","contentHash":"60f505727b5207c3fbb5b2b5fbc69fa2dba1cfea777f9de78b7224883dde575b","addressRefs":[]},"35bdc1b6-604d-44ad-a577-ceb33bc20bd9":{"id":"35bdc1b6-604d-44ad-a577-ceb33bc20bd9","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6488,"content":"`Pending`","contentHash":"2986effe9fae335e819f546d8f69212a5a1e8bd5f01a449e4e295a5dee70536f","addressRefs":[]},"da718c05-b351-43dd-a12a-75fe5bc0b4cf":{"id":"da718c05-b351-43dd-a12a-75fe5bc0b4cf","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6489,"content":"The documents herein define the parameters of the Sentora RLUSD Morpho Vault V2 Instance of the Allocation System Primitive.","contentHash":"4dae0b7c497df5b3457888a85a715e1f6362ae3446ebbd8d1099812bcb4367de","addressRefs":[]},"958bd3b4-0650-44fc-8765-28392fe92df3":{"id":"958bd3b4-0650-44fc-8765-28392fe92df3","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6490,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"8baa615c-fc38-4bf7-8c44-47a6bb168ad8":{"id":"8baa615c-fc38-4bf7-8c44-47a6bb168ad8","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6491,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"bfc9f2f7-e69f-4685-b666-57bb2d55442f":{"id":"bfc9f2f7-e69f-4685-b666-57bb2d55442f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6492,"content":"Sentora RLUSD Morpho Vault V2","contentHash":"56435a72135a819edd203241ce4a4667d9f62f6c290aec3c1086f5c442cf15f6","addressRefs":[]},"0b1dbb71-5087-4db2-98e1-f4aafe4e46b5":{"id":"0b1dbb71-5087-4db2-98e1-f4aafe4e46b5","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6493,"content":"RLUSD","contentHash":"ce52a67fc84336854744eab2516dc2e64b62d6ee5f1743be44f8fa57ae7ea42d","addressRefs":[]},"e7b16e69-cfb2-4877-a0c2-9cbc7f4ff1ff":{"id":"e7b16e69-cfb2-4877-a0c2-9cbc7f4ff1ff","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6494,"content":"senRLUSDv2","contentHash":"81f7f78d34e23ae6c52a2cb00c3803002460d4716c06735feba32acfb15e3cf1","addressRefs":[]},"d2e8af21-8db9-43b3-8f52-7e080897d54e":{"id":"d2e8af21-8db9-43b3-8f52-7e080897d54e","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6495,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"dde53de4-3778-44b3-9f65-064eaab3bf93":{"id":"dde53de4-3778-44b3-9f65-064eaab3bf93","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6496,"content":"`0x6dC58a0FdfC8D694e571DC59B9A52EEEa780E6bf`","contentHash":"71b36adf702a205707ec970a93512b49b5030816d7d642f2516ad1114951865b","addressRefs":["0x6dc58a0fdfc8d694e571dc59b9a52eeea780e6bf"]},"b041fa2f-e7cd-4c64-98d0-a1b67f50d6a2":{"id":"b041fa2f-e7cd-4c64-98d0-a1b67f50d6a2","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6497,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"991d7839-4dfd-466f-aafd-8c397cd7af6b":{"id":"991d7839-4dfd-466f-aafd-8c397cd7af6b","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6498,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"a5775dc3-6444-4234-825d-7e0ae6b05f6b":{"id":"a5775dc3-6444-4234-825d-7e0ae6b05f6b","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6499,"content":"The inflow RateLimitID is: `0x944bbb34c3717aacc72419f43d62f5a01d2ebd7a9157ba9975fd7d971deb803f`","contentHash":"5e8dda50e0ff61c01d849bf7d283b391e9b1e8494194ebf7b18b12aada7106a7","addressRefs":[]},"2441cde7-6e2e-47d9-9fd3-62b1bfbb9c9c":{"id":"2441cde7-6e2e-47d9-9fd3-62b1bfbb9c9c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6500,"content":"The outflow RateLimitID is: `0xfc41a8cf89ec93b54bbf6960204c29c48a7ed98ec4a88dade68149dee919e788`","contentHash":"68bf66b9f5c62f44dda97291fc8ea548ac2edf49fdeb3b24e7c8fa2ef6447471","addressRefs":[]},"5ecbe8da-00f2-4d72-ab79-6276eae3bc0f":{"id":"5ecbe8da-00f2-4d72-ab79-6276eae3bc0f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6501,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"c7c4c3a1-ca25-4e9e-b4ab-cbcd01519535":{"id":"c7c4c3a1-ca25-4e9e-b4ab-cbcd01519535","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6502,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 RLUSD\n- `slope`: 50,000,000 RLUSD per day","contentHash":"adda796dbfae6a1e4aab4b1105176103ca333bc63cc4578cf6c49bc88a664b4e","addressRefs":[]},"3593ce57-8cf0-42c8-b0ce-0bfef547e4a6":{"id":"3593ce57-8cf0-42c8-b0ce-0bfef547e4a6","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6503,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"55c42f45-b94d-4e4d-959f-ae1cc1880fc5":{"id":"55c42f45-b94d-4e4d-959f-ae1cc1880fc5","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6504,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"4e3fae3f-b450-4f0b-bff4-4f4767c8f7a7":{"id":"4e3fae3f-b450-4f0b-bff4-4f4767c8f7a7","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.2.5.1","title":"Maximum Exposure","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6505,"content":"The Maximum Exposure for this Instance is 0 USD.","contentHash":"000c2700aa2243b26617bab03c6cf2fc7bca87d60d9b2ebeb94ce3731f5af748","addressRefs":[]},"e63662b0-149e-4e80-b7e0-6cf281f85ddd":{"id":"e63662b0-149e-4e80-b7e0-6cf281f85ddd","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6506,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"9aed2f2d-6a17-41a5-9104-bb622b3cb04e":{"id":"9aed2f2d-6a17-41a5-9104-bb622b3cb04e","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6507,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer parameters.","contentHash":"fb9cdee40bad95b4561c802450d9f2390b5c2ba57f0791739315c5e5ddbba48f","addressRefs":[]},"fd4778b5-78e7-49fc-a785-c2dfed2e5246":{"id":"fd4778b5-78e7-49fc-a785-c2dfed2e5246","doc_no":"A.6.1.1.2.2.6.1.3.1.7.7.4.1","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6508,"content":"Controllers now have protections that require a `maxExchangeRate` to be set for deposits. The following ensures 1 share can represent at most 3 RLUSD:\n\n- `setMaxExchangeRate(SENTORA_RLUSD_MAIN_V2, 1e18, 3e18)`","contentHash":"500aa06b786fb6003fee24b22cfd866716951ec72a401988c643826d1be53db7","addressRefs":[]},"cfb29474-ea48-4370-aad6-23af1cf4d11a":{"id":"cfb29474-ea48-4370-aad6-23af1cf4d11a","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8","title":"Ethereum Mainnet - Grove x Steakhouse RLUSD Morpho Vault V2 Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6509,"content":"The documents herein contain the Instance Configuration Document for the Grove x Steakhouse RLUSD Morpho Vault V2 Instance.","contentHash":"09051222ed7909a1113bcae0d82487f67c8c067d3904258ae592fd88fdb7ad9d","addressRefs":[]},"a1136418-1914-4543-aa3c-a77e7e8b60c7":{"id":"a1136418-1914-4543-aa3c-a77e7e8b60c7","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6510,"content":"`Pending`","contentHash":"2986effe9fae335e819f546d8f69212a5a1e8bd5f01a449e4e295a5dee70536f","addressRefs":[]},"d4091127-bd5c-4ff6-ba9c-de7bd8553e61":{"id":"d4091127-bd5c-4ff6-ba9c-de7bd8553e61","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6511,"content":"The documents herein define the parameters of the Grove x Steakhouse RLUSD Morpho Vault V2 Instance of the Allocation System Primitive.","contentHash":"8c05f104c5bbef08e83542a5ec415222b16a3110ab87b00cb99232b832ecfe9a","addressRefs":[]},"64527d65-8389-4d0c-859c-fe2da103f62d":{"id":"64527d65-8389-4d0c-859c-fe2da103f62d","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6512,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"74b876ee-2891-413b-bd1f-58b2c96b4585":{"id":"74b876ee-2891-413b-bd1f-58b2c96b4585","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6513,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"70e811cc-0a98-454a-b555-0f88a65187f1":{"id":"70e811cc-0a98-454a-b555-0f88a65187f1","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6514,"content":"Grove x Steakhouse RLUSD Morpho Vault V2","contentHash":"90f2751bcbfce66b82bd6796e9c9d15e26022f6f50ce6abcc2b6aa3a8db54f15","addressRefs":[]},"b3ad456b-d6de-4ed1-8576-01366e21bd5d":{"id":"b3ad456b-d6de-4ed1-8576-01366e21bd5d","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6515,"content":"RLUSD","contentHash":"ce52a67fc84336854744eab2516dc2e64b62d6ee5f1743be44f8fa57ae7ea42d","addressRefs":[]},"9325e9e9-4c9d-44ac-a732-64c8353bbff7":{"id":"9325e9e9-4c9d-44ac-a732-64c8353bbff7","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6516,"content":"grove-bbqRLUSD","contentHash":"dea8b228390bea7c7b9bcd239abb73f461ff93e3dfa03824dcf4de52d1c37f45","addressRefs":[]},"02fa5674-392e-4d0c-8e42-2adc3692881c":{"id":"02fa5674-392e-4d0c-8e42-2adc3692881c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6517,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"8ac9a401-96a6-4cbc-9d23-9374cb626d2b":{"id":"8ac9a401-96a6-4cbc-9d23-9374cb626d2b","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6518,"content":"`0xBeEff4fD39F8e48b6a6e475445D650cb11e9599F`","contentHash":"9d6b91f7d85854633dad9e5e3f77a998efa1e6ef2b47fe6017826c43de4e49bb","addressRefs":["0xbeeff4fd39f8e48b6a6e475445d650cb11e9599f"]},"de701477-61aa-4d32-81b7-9ab044bb2b74":{"id":"de701477-61aa-4d32-81b7-9ab044bb2b74","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6519,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"41f9c281-d313-47d4-af75-8df48c9e260c":{"id":"41f9c281-d313-47d4-af75-8df48c9e260c","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6520,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"cef889e791f2b83bcbb0a9c31a4ac27908ed8e42d81e0663f3596e7e35abb973","addressRefs":[]},"e868b5a4-e469-4e32-869d-2c904d31d221":{"id":"e868b5a4-e469-4e32-869d-2c904d31d221","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6521,"content":"The inflow RateLimitID is: `0xf655bc101a615fbcb591acce756dacae96cb119ff1beec548d9cc5d4558ea53a`","contentHash":"3efc356f3c3546c9d53fb068a0318e8bfc84753049d1475ee711843b149b878c","addressRefs":[]},"3944007b-9f6f-4c0a-a71b-dd3a1775cd94":{"id":"3944007b-9f6f-4c0a-a71b-dd3a1775cd94","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6522,"content":"The outflow RateLimitID is: `0xa6e68f8214d2fb32e0deb2888ef4644c36401d18605447843e4f936529f6a3cb`","contentHash":"4cfa1922ee2acc9540b9919de2f0db9b3351d4cb64ed62c13457f16a69aac96b","addressRefs":[]},"93fbe9e3-88b0-4160-b4cb-52b5333a0926":{"id":"93fbe9e3-88b0-4160-b4cb-52b5333a0926","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6523,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"adfeeede-027a-4b98-8636-c53975c4b7cf":{"id":"adfeeede-027a-4b98-8636-c53975c4b7cf","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6524,"content":"The deposit rate limits are:\n\n- `maxAmount`: 100,000,000 RLUSD\n- `slope`: 100,000,000 RLUSD per day","contentHash":"4f6f824fe479712e400c6c6dff0c8ca92dbb891900fc07b6e4c0c11e65cd1025","addressRefs":[]},"c455e62e-79a6-478e-aa06-f35d2ab6779f":{"id":"c455e62e-79a6-478e-aa06-f35d2ab6779f","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6525,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"f298feba-925d-4f87-99d8-855fc7adffe0":{"id":"f298feba-925d-4f87-99d8-855fc7adffe0","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6526,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"2952337f-8152-44ca-9d3e-0363c6f2b1c9":{"id":"2952337f-8152-44ca-9d3e-0363c6f2b1c9","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6527,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"8638d88f-8ac2-4deb-849e-6100eeea4b82":{"id":"8638d88f-8ac2-4deb-849e-6100eeea4b82","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6528,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer parameters.","contentHash":"fb9cdee40bad95b4561c802450d9f2390b5c2ba57f0791739315c5e5ddbba48f","addressRefs":[]},"ea2bbd07-134d-459d-bb20-2dbb756766b0":{"id":"ea2bbd07-134d-459d-bb20-2dbb756766b0","doc_no":"A.6.1.1.2.2.6.1.3.1.7.8.4.1","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6529,"content":"Controllers now have protections that require a `maxExchangeRate` to be set for deposits. The following ensures 1 share can represent at most 3 RLUSD:\n\n- `setMaxExchangeRate(GROVE_X_STEAKHOUSE_RLUSD_V2, 1e18, 3e18)`","contentHash":"f8f172fdc84608114ac7a0d9570e027819239b9791edf63174a3dc375c3c4ca7","addressRefs":[]},"b05d9fc2-9a93-4f3b-b0d8-b4f77bc294ce":{"id":"b05d9fc2-9a93-4f3b-b0d8-b4f77bc294ce","doc_no":"A.6.1.1.2.2.6.1.3.1.8","title":"Securitize","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6530,"content":"The Ethereum Mainnet Instances of the Securitize Protocol with `Active` Status are stored herein.","contentHash":"cd19b709d0984169fa55f33135c2e10216ac779005a0e17825fc7056e0e6ef4f","addressRefs":[]},"a0c4fcd6-ebf9-4124-8767-cf14ab6ab397":{"id":"a0c4fcd6-ebf9-4124-8767-cf14ab6ab397","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1","title":"Ethereum Mainnet - Securitize Tokenized AAA CLO Fund (STAC) Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6531,"content":"The documents herein contain the Instance Configuration Document for the Securitize Tokenized AAA CLO Fund (STAC) Instance.","contentHash":"5e6ba51bde08b743854e451872fbe6399e95091a1f2bc508b795bcdc5d38c636","addressRefs":[]},"96b8832b-b6b9-4550-b211-8df9adbf163c":{"id":"96b8832b-b6b9-4550-b211-8df9adbf163c","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6532,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"1258f424-862a-4e22-9281-658b7dcca2c5":{"id":"1258f424-862a-4e22-9281-658b7dcca2c5","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6533,"content":"The documents herein define the parameters of the Securitize Tokenized AAA CLO Fund (STAC) Instance of the Allocation System Primitive.","contentHash":"7d50de8a5f68eab981a0f0ec7e1f4cb20b38f9b57ddec6a8c806892982ad6f44","addressRefs":[]},"a5c55b02-742c-4172-a6d0-88155fd3b73f":{"id":"a5c55b02-742c-4172-a6d0-88155fd3b73f","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6534,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"ca21487e-43e1-4fd7-a67c-7389e59bf46d":{"id":"ca21487e-43e1-4fd7-a67c-7389e59bf46d","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6535,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"f29e4e19-73d2-4a9b-812f-0226be26687a":{"id":"f29e4e19-73d2-4a9b-812f-0226be26687a","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6536,"content":"Securitize","contentHash":"79ff390b92a3112b76cddc5251bb81780a7a9f01efc984c5c50419dde79c615e","addressRefs":[]},"5e3282b6-3920-43e8-9659-ad9d0a4f2efe":{"id":"5e3282b6-3920-43e8-9659-ad9d0a4f2efe","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6537,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"c448bf3a-b51d-40e9-ba3c-8bdeadad1dc2":{"id":"c448bf3a-b51d-40e9-ba3c-8bdeadad1dc2","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6538,"content":"STAC","contentHash":"20be6c5a68b25dec4da28468e783d31494dcef6ada4682c039be3f549d7087cc","addressRefs":[]},"9ab65d47-267a-4be6-b298-8a636b909e13":{"id":"9ab65d47-267a-4be6-b298-8a636b909e13","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6539,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"b6737216-3829-40ae-b033-846080f61d34":{"id":"b6737216-3829-40ae-b033-846080f61d34","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6540,"content":"`0x51C2d74017390CbBd30550179A16A1c28F7210fc`","contentHash":"fc6dd52cac8b72405d6356443dc956d98ed09277131499f6b0ef37b8f921dff1","addressRefs":["0x51c2d74017390cbbd30550179a16a1c28f7210fc"]},"19b23b6a-f8a5-4db8-8768-88b045bab3d2":{"id":"19b23b6a-f8a5-4db8-8768-88b045bab3d2","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6541,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"dd63b171-c94f-4082-8719-24870cb173c1":{"id":"dd63b171-c94f-4082-8719-24870cb173c1","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6542,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"ae0239af-eed4-40d6-8d21-c53bda72249d":{"id":"ae0239af-eed4-40d6-8d21-c53bda72249d","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6543,"content":"The inflow RateLimitID is: `0x01ccccb0233955b3de85eca4dcc78aaf2aa6da1cf048b496e85a91396c2feab6`.","contentHash":"30b8705f2188433c83545a35b7851c312b7add355bb45cbe95ad151fef8b035d","addressRefs":[]},"d451d2b1-70ea-458a-b2bb-dde38d29e9c0":{"id":"d451d2b1-70ea-458a-b2bb-dde38d29e9c0","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6544,"content":"The outflow RateLimitID is: `0xcbb4d6e874245392c78f0f249b7dc876e5462bb0dce135a6e5c4cc21d774390b`.","contentHash":"037f0c07baba78cbda3ecaf38ead859942b93169903962329bb0d2e0e0ace255","addressRefs":[]},"fd676948-7b31-4f11-b4b0-933226a193e7":{"id":"fd676948-7b31-4f11-b4b0-933226a193e7","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6545,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"ee33b709-1239-44c3-9c94-4211433877c4":{"id":"ee33b709-1239-44c3-9c94-4211433877c4","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6546,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"d611f80cb40a432ea119c598c732961d7f492579e57452513915d7b2368d3fdd","addressRefs":[]},"3cafebb2-cf4d-4830-9787-1c2d7d7da030":{"id":"3cafebb2-cf4d-4830-9787-1c2d7d7da030","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6547,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"174ba214-cfe9-4d35-83cb-3c0795e1936c":{"id":"174ba214-cfe9-4d35-83cb-3c0795e1936c","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6548,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"0f3ebd6c-2b7f-4125-aea8-68e84476da06":{"id":"0f3ebd6c-2b7f-4125-aea8-68e84476da06","doc_no":"A.6.1.1.2.2.6.1.3.1.8.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6549,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"e5507edb-8e06-48d2-a341-47de592d2a60":{"id":"e5507edb-8e06-48d2-a341-47de592d2a60","doc_no":"A.6.1.1.2.2.6.1.3.1.9","title":"Galaxy","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6550,"content":"The Ethereum Mainnet Instances of the Galaxy Protocol with `Active` Status are stored herein.","contentHash":"c4ec464e462286d604b52e3ce3a87efdcd6994fd794adc4bb1ee1faecb606251","addressRefs":[]},"61afae62-1210-4d80-aa6c-cdb26ef0a287":{"id":"61afae62-1210-4d80-aa6c-cdb26ef0a287","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1","title":"Ethereum Mainnet - Galaxy Arch CLOs Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6551,"content":"The documents herein contain the Instance Configuration Document for the Galaxy Arch CLOs Instance.","contentHash":"3a925c1ff586a10de204dba6d112a58208fdd78603f5bddc7d27a2dc3c1a0c5b","addressRefs":[]},"21f548d0-71cc-4a8a-8942-514e87cbd893":{"id":"21f548d0-71cc-4a8a-8942-514e87cbd893","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6552,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"da740e11-eb97-4647-9186-8cce66532f2a":{"id":"da740e11-eb97-4647-9186-8cce66532f2a","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6553,"content":"The documents herein define the parameters of the Galaxy Arch CLOs Instance of the Allocation System Primitive.","contentHash":"33c65f510f5b98c0d39b65967114b04642be179ab7a6a02139c28802b9617da2","addressRefs":[]},"b993eda4-2f51-470b-b0a9-e0213576a88d":{"id":"b993eda4-2f51-470b-b0a9-e0213576a88d","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6554,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"d8cf82e0-4c80-4378-844c-ce2dd0a5d04e":{"id":"d8cf82e0-4c80-4378-844c-ce2dd0a5d04e","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6555,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"357d0b0e-7db7-4c2c-9b06-e6e0134c4259":{"id":"357d0b0e-7db7-4c2c-9b06-e6e0134c4259","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6556,"content":"Galaxy","contentHash":"0898a6c7ed3a10bcbb271d47451a8d010c78d50d70d8a9fb6c3cc481cb2d1ab3","addressRefs":[]},"0d3d52df-eb9b-4df4-8023-295be72f1193":{"id":"0d3d52df-eb9b-4df4-8023-295be72f1193","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6557,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"72e3fb43-419f-437a-b7f4-59ebe16ccd20":{"id":"72e3fb43-419f-437a-b7f4-59ebe16ccd20","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6558,"content":"GACLO-1","contentHash":"8aa9e28eea1829d7dd8adc44fed206db816d9516637b50362fe243ee2fe33f41","addressRefs":[]},"221c015b-f830-48d0-9c0e-dbdfcf0865bf":{"id":"221c015b-f830-48d0-9c0e-dbdfcf0865bf","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6559,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"931d7521-9740-4913-8f36-52bbb856dca2":{"id":"931d7521-9740-4913-8f36-52bbb856dca2","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.2.1","title":"Token Address (Avalanche)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6560,"content":"`0x2C0aDFF8e114f3cA106051144353aC703D24B901`","contentHash":"7f985b34284c3d5951be918bda1a9897eebd117b0287ae1d9a68b13246573331","addressRefs":["0x2c0adff8e114f3ca106051144353ac703d24b901"]},"01affe4d-8bba-4783-a6b3-ff32193b63e3":{"id":"01affe4d-8bba-4783-a6b3-ff32193b63e3","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.2.2","title":"Deposit Address (Mainnet)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6561,"content":"`0x2E3A11807B94E689387f60CD4BF52A56857f2eDC`","contentHash":"1f566bf81bf81bb4de9e15074fca71cdd98ba39ec421deed585bf67ce6f96a3d","addressRefs":["0x2e3a11807b94e689387f60cd4bf52a56857f2edc"]},"44803afa-e8f9-4247-afda-a25fcedd8226":{"id":"44803afa-e8f9-4247-afda-a25fcedd8226","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.2.3","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6562,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"43ad16bf-2a53-492a-a9aa-187e5f3820ec":{"id":"43ad16bf-2a53-492a-a9aa-187e5f3820ec","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6563,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"df18f3e6-bde8-4241-86d3-aa98edf3179c":{"id":"df18f3e6-bde8-4241-86d3-aa98edf3179c","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6564,"content":"The inflow RateLimitID is: `0x0de7fd8a7d8060b09965787f4841cca8a448925e555aaf7ecb4894782ffa2e17`.","contentHash":"cb1718bb939eeec11ebf32dc3d2935cdf0c860a58af8091bf1376579e34f6a8a","addressRefs":[]},"be343d84-8e63-4e4e-99a3-77323db1f048":{"id":"be343d84-8e63-4e4e-99a3-77323db1f048","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6565,"content":"The outflow RateLimitID is: N/A.","contentHash":"483affad475b6c78cfa6846cb48795ff6ea43b13d4079c9d25d0d4a65e2aa3d7","addressRefs":[]},"23517c75-2462-4def-bab9-3a33c3c03e71":{"id":"23517c75-2462-4def-bab9-3a33c3c03e71","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6566,"content":"The current `maxAmount` and `slope` for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"e5eb411abadf20155e59acad4f3c0696c2b44cb3c8b38090d09489ca7a118f52","addressRefs":[]},"2e5f7349-fe4b-4c1b-8cc2-541d2ce86bf5":{"id":"2e5f7349-fe4b-4c1b-8cc2-541d2ce86bf5","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6567,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"d611f80cb40a432ea119c598c732961d7f492579e57452513915d7b2368d3fdd","addressRefs":[]},"c2f613ac-e271-4cbc-9ca7-f644082e5e8e":{"id":"c2f613ac-e271-4cbc-9ca7-f644082e5e8e","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6568,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A\n- `slope`: N/A","contentHash":"868ef21c91f22d83076d592b9bfad81c108b9a5c1eed56322abe0eafea2d3a7a","addressRefs":[]},"efac2756-89e0-4b0e-8313-3097c2660608":{"id":"efac2756-89e0-4b0e-8313-3097c2660608","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6569,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"65650ce9-1f1f-4e51-b60b-12f17efc2e67":{"id":"65650ce9-1f1f-4e51-b60b-12f17efc2e67","doc_no":"A.6.1.1.2.2.6.1.3.1.9.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6570,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"2e3e057e-0b48-4e3f-b03d-1ed84299ccfc":{"id":"2e3e057e-0b48-4e3f-b03d-1ed84299ccfc","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2","title":"Ethereum Mainnet - Galaxy Warehouse Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6571,"content":"The documents herein contain the Instance Configuration Document for the Galaxy Warehouse Instance.","contentHash":"e0632baa2d052e1262e88da09de98147b513bf04b36692ec31d5a0e5d6b085fc","addressRefs":[]},"91f2537e-d391-4e7a-9206-5f162cd6325a":{"id":"91f2537e-d391-4e7a-9206-5f162cd6325a","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6572,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"cdcd20ed-3cc9-457f-8f26-9a3770146089":{"id":"cdcd20ed-3cc9-457f-8f26-9a3770146089","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6573,"content":"The documents herein define the parameters of the Galaxy Warehouse Instance of the Allocation System Primitive.","contentHash":"a3941ba4e370112710a9d46487209c9e34a6994d69ce21f2b49c857b9f5b8060","addressRefs":[]},"02ee19aa-2e46-4d77-90ac-a37bb0163b83":{"id":"02ee19aa-2e46-4d77-90ac-a37bb0163b83","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6574,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"06807734-cc8c-4e05-a069-df86fe101a0a":{"id":"06807734-cc8c-4e05-a069-df86fe101a0a","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6575,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"39071e33-187b-46e3-b1dc-54c70e98e742":{"id":"39071e33-187b-46e3-b1dc-54c70e98e742","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6576,"content":"Galaxy","contentHash":"0898a6c7ed3a10bcbb271d47451a8d010c78d50d70d8a9fb6c3cc481cb2d1ab3","addressRefs":[]},"d8696c8d-94dc-4783-9da1-be62d2d7962c":{"id":"d8696c8d-94dc-4783-9da1-be62d2d7962c","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6577,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"40cf48fc-fa14-4853-91db-334f0d5e1c2b":{"id":"40cf48fc-fa14-4853-91db-334f0d5e1c2b","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6578,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"3874bdfc-77f3-4f2c-ae91-c4a4c0337c8e":{"id":"3874bdfc-77f3-4f2c-ae91-c4a4c0337c8e","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6579,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"51575781-6189-4bf3-9d6b-ae76fabbc2f7":{"id":"51575781-6189-4bf3-9d6b-ae76fabbc2f7","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.2.1","title":"Deposit Address (Mainnet)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6580,"content":"`0x3E23311f9FF660E3c3d87E4b7c207b3c3D7e04f0`","contentHash":"72a3c0f69111b6442595e0c0086bc4be6d25e705c6ad20450fd8782389692c31","addressRefs":["0x3e23311f9ff660e3c3d87e4b7c207b3c3d7e04f0"]},"39b83634-f5b2-4b7c-9e98-d5616fad62b2":{"id":"39b83634-f5b2-4b7c-9e98-d5616fad62b2","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6581,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"cc6e09bc-a2d0-4e4b-bf94-4fccebbd5995":{"id":"cc6e09bc-a2d0-4e4b-bf94-4fccebbd5995","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6582,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"8e16ecba-2c99-49f7-b979-a0108194873f":{"id":"8e16ecba-2c99-49f7-b979-a0108194873f","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6583,"content":"The inflow RateLimitID is: `0x110ff25f20e1f05ba3e82592752f6cd7e0ca645023d71d143b970e3689efc9f9`.","contentHash":"be76b52eef7e0492565f900c298a24c1f0a2dbd9021aaa414a02c41e637ec408","addressRefs":[]},"c2111eab-6850-46e1-9543-fe5d8966c9da":{"id":"c2111eab-6850-46e1-9543-fe5d8966c9da","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6584,"content":"The outflow RateLimitID is: N/A.","contentHash":"483affad475b6c78cfa6846cb48795ff6ea43b13d4079c9d25d0d4a65e2aa3d7","addressRefs":[]},"306c8538-fda8-4d3f-bf1d-ec249e4292e9":{"id":"306c8538-fda8-4d3f-bf1d-ec249e4292e9","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6585,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"282c02b2-9b9d-4934-be9d-5228d50a0918":{"id":"282c02b2-9b9d-4934-be9d-5228d50a0918","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6586,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"d611f80cb40a432ea119c598c732961d7f492579e57452513915d7b2368d3fdd","addressRefs":[]},"c38e4cd8-1be2-475d-8670-848d8eba3078":{"id":"c38e4cd8-1be2-475d-8670-848d8eba3078","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6587,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A","contentHash":"d88e89a289b425459f3757f6dcc010a026147315ded89e1cf253cbe5441d4deb","addressRefs":[]},"68cad9ca-620b-4aef-b47f-781d01640c87":{"id":"68cad9ca-620b-4aef-b47f-781d01640c87","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6588,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"09aa5dea-d9d1-4f8c-9ae4-c76aaa35d8a8":{"id":"09aa5dea-d9d1-4f8c-9ae4-c76aaa35d8a8","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.5.1","title":"Interim Deployment","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6589,"content":"This Instance is currently defined as an Interim Deployment (see [A.1.10.2.3.2.2.2 - Interim Deployments](9b3edbbf-89d1-42da-a9c3-18f858f8471f)) and as such has CRR of 100%. The testing parameters of this Interim Deployment are specified in the documents herein.","contentHash":"b6fff015c819db559725eb477c98d8d35d4139d7d683d8e68516302276b966fb","addressRefs":[]},"911d3d77-605c-4294-b61e-a6da21004b51":{"id":"911d3d77-605c-4294-b61e-a6da21004b51","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.5.1.1","title":"Maximum Allocation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6590,"content":"The maximum allocation for Interim Deployments in Galaxy Warehouse is $20 million.","contentHash":"f9157135849d95a3475216206ee93d34be1284144cd51ec31413414de2deda4e","addressRefs":[]},"202c9218-75c4-45df-ae0a-a23c6e949666":{"id":"202c9218-75c4-45df-ae0a-a23c6e949666","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.2.5.1.2","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6591,"content":"The Rate Limits for this Interim Deployment are defined in [A.6.1.1.2.2.6.1.3.1.9.2.2.4 - Rate Limits](306c8538-fda8-4d3f-bf1d-ec249e4292e9).","contentHash":"c00e01a1d309294a210edd18173bbd41172043a0679afb8bf4b04f0ecdf767c1","addressRefs":[]},"6a1719f2-bd99-4407-addc-dc9e7a84bf58":{"id":"6a1719f2-bd99-4407-addc-dc9e7a84bf58","doc_no":"A.6.1.1.2.2.6.1.3.1.9.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6592,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"9b416c43-4ed8-4c13-ba9f-5f12c9c3e7a0":{"id":"9b416c43-4ed8-4c13-ba9f-5f12c9c3e7a0","doc_no":"A.6.1.1.2.2.6.1.3.1.10","title":"Ripple","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6593,"content":"The Ethereum Mainnet Instances of the Ripple Protocol with `Active` Status are stored herein.","contentHash":"8807341b9efcae33019f03fd97f59ed15b6c2e1f4410d8f5a2e58afd85ce81c7","addressRefs":[]},"2e28c162-c608-452c-b796-4654ac1139d8":{"id":"2e28c162-c608-452c-b796-4654ac1139d8","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1","title":"Ethereum Mainnet - Ripple RLUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6594,"content":"The documents herein contain the Instance Configuration Document for the Ripple RLUSD Instance.","contentHash":"97f5d44f6124c6aaab7e52bc371bd46002b953f1492819c3192bc8866cf4a5d8","addressRefs":[]},"3860f545-4d08-45ff-b8b6-98bf78b78c3c":{"id":"3860f545-4d08-45ff-b8b6-98bf78b78c3c","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6595,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"060ff03e-4aa5-47ce-8d9c-ad6bcca8ac02":{"id":"060ff03e-4aa5-47ce-8d9c-ad6bcca8ac02","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6596,"content":"The documents herein define the parameters of the Ripple RLUSD Instance of the Allocation System Primitive.","contentHash":"112d2b9db235787794fbc7afaef703a341b440af62e4c41090760b57470c4503","addressRefs":[]},"fcccfc28-a6fe-4aaa-b0be-e34ffd36fba9":{"id":"fcccfc28-a6fe-4aaa-b0be-e34ffd36fba9","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6597,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"7bf6a865-5eb4-4693-b45e-e13dc2e45ef7":{"id":"7bf6a865-5eb4-4693-b45e-e13dc2e45ef7","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6598,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"8c0f9245-59c0-4119-b06e-461e043055f0":{"id":"8c0f9245-59c0-4119-b06e-461e043055f0","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6599,"content":"Ripple","contentHash":"a17e80a651e1ae915c04bc09b29e6597b0c29e2f706681a4bd99f759db48ddc9","addressRefs":[]},"ac03ab87-6983-4202-ab96-3b467887430c":{"id":"ac03ab87-6983-4202-ab96-3b467887430c","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6600,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"026d2917-1690-44ac-97e8-248ca299d1d3":{"id":"026d2917-1690-44ac-97e8-248ca299d1d3","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6601,"content":"RLUSD","contentHash":"ce52a67fc84336854744eab2516dc2e64b62d6ee5f1743be44f8fa57ae7ea42d","addressRefs":[]},"9a0b58c8-d674-4a3c-8a68-4856ad42484e":{"id":"9a0b58c8-d674-4a3c-8a68-4856ad42484e","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6602,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"a7a0518a-cc8a-460c-b9a4-58eae7130455":{"id":"a7a0518a-cc8a-460c-b9a4-58eae7130455","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6603,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"6f3ad27d-cb6d-4135-a0ad-444c3d3b2df6":{"id":"6f3ad27d-cb6d-4135-a0ad-444c3d3b2df6","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6604,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"84298bdc-2033-47d4-89f7-d8d244c1a3bc":{"id":"84298bdc-2033-47d4-89f7-d8d244c1a3bc","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6605,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"c52f70d9-7910-4f5b-8ffc-5e48a4d7ac39":{"id":"c52f70d9-7910-4f5b-8ffc-5e48a4d7ac39","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6606,"content":"The inflow RateLimitID is:\n\n`0x1fd0baaf4707a3525f15888ddf89e29b1a008d0f3cf7fb75171233c72003a588`.","contentHash":"179a1ada73c535d55758fa70cb8261110e59e6f858558910a06987298d1c8df7","addressRefs":[]},"de5079d5-deaa-4cac-abfa-f4032a0d29a2":{"id":"de5079d5-deaa-4cac-abfa-f4032a0d29a2","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6607,"content":"The outflow RateLimitID is:\n\n`0x786ff17c8a3c0f645317f91a3247bc843ba1ee4d248ab539acec8ba3bf4557ae`.","contentHash":"8532dfbc0da719bf7d7a75b23c989fee6507202f81f7964572d729d2b8a7e772","addressRefs":[]},"5cc1e823-b15a-4792-8b33-ce92a02fd0b0":{"id":"5cc1e823-b15a-4792-8b33-ce92a02fd0b0","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6608,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"1b66e040-0e9d-4fb7-a3a4-66068899c344":{"id":"1b66e040-0e9d-4fb7-a3a4-66068899c344","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6609,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"d611f80cb40a432ea119c598c732961d7f492579e57452513915d7b2368d3fdd","addressRefs":[]},"8cd46ad3-7589-4ac0-8cb6-a6dbe42bdc81":{"id":"8cd46ad3-7589-4ac0-8cb6-a6dbe42bdc81","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6610,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"9070789bb9d27284f5c83cf9ad801a1be88b39e8f6cc8fffa9cd2d7da42d3a9f","addressRefs":[]},"193f9b5d-a33e-44a0-ba8e-33e480d96243":{"id":"193f9b5d-a33e-44a0-ba8e-33e480d96243","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6611,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"8b96b7dc-9269-4d51-8b2f-a77d337736fc":{"id":"8b96b7dc-9269-4d51-8b2f-a77d337736fc","doc_no":"A.6.1.1.2.2.6.1.3.1.10.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6612,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"1e4049b8-cd1d-42ef-be21-7f365b6a5341":{"id":"1e4049b8-cd1d-42ef-be21-7f365b6a5341","doc_no":"A.6.1.1.2.2.6.1.3.1.11","title":"Agora","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6613,"content":"The Ethereum Mainnet Instances of the Agora Protocol with `Active` Status are stored herein.","contentHash":"f8e8255864907c2449cd634fb363e128bd18a006cdd2097b1d6b791e05274d4f","addressRefs":[]},"0d71b879-0dd7-4c37-9a42-f16d868c4482":{"id":"0d71b879-0dd7-4c37-9a42-f16d868c4482","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1","title":"Ethereum Mainnet - Agora AUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6614,"content":"The documents herein contain the Instance Configuration Document for the Agora AUSD Instance.","contentHash":"693f560d03ce74e58b575381874a541522a9ccca3135112fc2781814d029f3b5","addressRefs":[]},"fbfc3072-984e-4538-be7d-4a2dfc1b6057":{"id":"fbfc3072-984e-4538-be7d-4a2dfc1b6057","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6615,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"fbc9a192-1171-4a09-a223-a5ce4bfdf227":{"id":"fbc9a192-1171-4a09-a223-a5ce4bfdf227","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6616,"content":"The documents herein define the parameters of the Agora AUSD Instance of the Allocation System Primitive.","contentHash":"d4e2c40d2cbab34a1060cb6f3d9061df759bc76c60692c12a59fef0df9017439","addressRefs":[]},"386b5c26-965d-43c9-b6a7-6f2d9717f57c":{"id":"386b5c26-965d-43c9-b6a7-6f2d9717f57c","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6617,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"9c207b7e-5f87-490c-a209-44157b596745":{"id":"9c207b7e-5f87-490c-a209-44157b596745","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6618,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"7c6e311b-c4b6-498f-a9b1-7c1812d96006":{"id":"7c6e311b-c4b6-498f-a9b1-7c1812d96006","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6619,"content":"Agora AUSD","contentHash":"3c7829b416dfaa78acf34804ebc059333a4ba08a71317a9f77a1d71eb2aac9ed","addressRefs":[]},"2f2d0122-0b55-4c6a-be9b-05f0a1378ca9":{"id":"2f2d0122-0b55-4c6a-be9b-05f0a1378ca9","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6620,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"a4320ef3-98d4-4c6c-ba33-dd58fd40293c":{"id":"a4320ef3-98d4-4c6c-ba33-dd58fd40293c","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6621,"content":"AUSD","contentHash":"d69492cb9237a4fe661cfb22b5603601d01ac18c772fdc7ebb10edd6fdf51f19","addressRefs":[]},"33e1ff50-f11e-4a94-be47-ac2014ed172e":{"id":"33e1ff50-f11e-4a94-be47-ac2014ed172e","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6622,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"b4a55280-bf9d-477a-9d42-1b2a421f6028":{"id":"b4a55280-bf9d-477a-9d42-1b2a421f6028","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6623,"content":"`0x00000000eFE302BEAA2b3e6e1b18d08D69a9012a`","contentHash":"a46d00e1291e0e83786e8b6f0f1f1fcad4c00f15b21c1cf91487ee0535a472a6","addressRefs":["0x00000000efe302beaa2b3e6e1b18d08d69a9012a"]},"f8bcf8e0-e5a8-41c3-9963-2ba85697265f":{"id":"f8bcf8e0-e5a8-41c3-9963-2ba85697265f","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6624,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"978c5bd7-a3ad-42f2-a7d3-2166008e2e6b":{"id":"978c5bd7-a3ad-42f2-a7d3-2166008e2e6b","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.2.3","title":"Deposit Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6625,"content":"`0x748b66a6b3666311F370218Bc2819c0bEe13677e`","contentHash":"8308bcf8262c886e0ecca13ed088c238c4c9482e9fc3874d0dc11f6141c4b1d7","addressRefs":["0x748b66a6b3666311f370218bc2819c0bee13677e"]},"b811a795-e342-4578-9acb-447a7027c3f5":{"id":"b811a795-e342-4578-9acb-447a7027c3f5","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.2.4","title":"Withdrawal Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6626,"content":"`0xab8306d9FeFBE8183c3C59cA897A2E0Eb5beFE67`","contentHash":"9e660e15888e1a85603f524824aecf0c96af495d42236c9118c1738620ed5ec4","addressRefs":["0xab8306d9fefbe8183c3c59ca897a2e0eb5befe67"]},"c5462c4a-eb73-40c3-bc66-6224fb0d7359":{"id":"c5462c4a-eb73-40c3-bc66-6224fb0d7359","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6627,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"94e3de3e-d8b7-4d23-8b97-8fd6d4c56281":{"id":"94e3de3e-d8b7-4d23-8b97-8fd6d4c56281","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6628,"content":"The inflow RateLimitID is: `0xf49540d3618324319b2da1f511b10e85ace863c455904b9deb9348c495f6f0c5`.","contentHash":"cabcfacb674a5e1aeafb57bdbe18b55e5c99b5e557a3db78a82a1a5aa5f18bcc","addressRefs":[]},"d585ab62-9de7-4b98-88b3-c6b70428fd66":{"id":"d585ab62-9de7-4b98-88b3-c6b70428fd66","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6629,"content":"The outflow RateLimitID is: `0x42ad76bdc643205fd16f00e7e67f0d5e7ae13541010329da7677ea4ddc7e59e3`.","contentHash":"789f32ac34583a79bc23c8e4abc392d32599a4e560ac1e597d12e121a5aa85e4","addressRefs":[]},"d60717bb-c122-49b9-9617-d121c05f60cb":{"id":"d60717bb-c122-49b9-9617-d121c05f60cb","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6630,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"880c8154-4959-4875-b696-3133f795fe02":{"id":"880c8154-4959-4875-b696-3133f795fe02","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6631,"content":"The deposit rate limits are:\n\n- `maxAmount`: 10,000,000 USDC\n- `slope`: 100,000,000 USDC per day","contentHash":"e28a2d9a8c02c4af5ece9949cfa1a7c0eb92d11093d903d35876bac2c758400b","addressRefs":[]},"ce3f0a10-568d-4525-b69d-1669c3cb2e8c":{"id":"ce3f0a10-568d-4525-b69d-1669c3cb2e8c","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6632,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: 10,000,000 AUSD\n- `slope`: 100,000,000 AUSD per day","contentHash":"3e7838d6b8e57fbf27568152baba89575008c6c06f0c645c4367f68d4cf07958","addressRefs":[]},"b13534e8-3758-4255-8c2d-60520fa36ed5":{"id":"b13534e8-3758-4255-8c2d-60520fa36ed5","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6633,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"3b346059-5587-43d2-addd-92e12f26f83a":{"id":"3b346059-5587-43d2-addd-92e12f26f83a","doc_no":"A.6.1.1.2.2.6.1.3.1.11.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6634,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"e8924df2-b3af-4867-8eda-1aa41ebcb785":{"id":"e8924df2-b3af-4867-8eda-1aa41ebcb785","doc_no":"A.6.1.1.2.2.6.1.3.1.12","title":"Uniswap","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6635,"content":"The Ethereum Mainnet Instances of the Uniswap Protocol with `Active` Status are stored herein.","contentHash":"e50537daa44422dc3614d95410beb5b743ba7b8c6b7f4e1454bf01bf71ac0fb2","addressRefs":[]},"c4d60460-2694-4d88-bf96-4f4141482cb5":{"id":"c4d60460-2694-4d88-bf96-4f4141482cb5","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1","title":"Ethereum Mainnet - Monad Uniswap AUSD/USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6636,"content":"The documents herein contain the Instance Configuration Document for the Monad Uniswap AUSD/USDC Instance.","contentHash":"38dd4b0fd4c7f447a628d83fbc86b214995d9db0b96cce7b74cf5b6304626303","addressRefs":[]},"69723e54-7c6b-4ddc-854c-6477b1884e15":{"id":"69723e54-7c6b-4ddc-854c-6477b1884e15","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6637,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"f27e8a20-88f9-4f85-8e3f-28324751cd6d":{"id":"f27e8a20-88f9-4f85-8e3f-28324751cd6d","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6638,"content":"The documents herein define the parameters of the Monad Uniswap AUSD/USDC Instance of the Allocation System Primitive.","contentHash":"a7532a9e1083625708c99233e570c0961b7cd6d12f10a9a5075f6cafad0ad54e","addressRefs":[]},"09991d1f-ecd9-44c4-a15f-726494579136":{"id":"09991d1f-ecd9-44c4-a15f-726494579136","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6639,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"9b511ae4-773f-41e3-a170-070b05026fa9":{"id":"9b511ae4-773f-41e3-a170-070b05026fa9","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6640,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"fce86e17-2a7c-4ff2-ada6-6f3ec57b7cf9":{"id":"fce86e17-2a7c-4ff2-ada6-6f3ec57b7cf9","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6641,"content":"Uniswap AUSD/USDC","contentHash":"f5928d9591491546fe43070203e861edfd02abaf3573142b773ee01d96f54c28","addressRefs":[]},"ae4d43f2-e97f-4aa4-ab78-674a11cc246a":{"id":"ae4d43f2-e97f-4aa4-ab78-674a11cc246a","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6642,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"9ad52308-e46b-463b-ba6a-6bf541323206":{"id":"9ad52308-e46b-463b-ba6a-6bf541323206","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6643,"content":"Uniswap AUSD/USDC Pool","contentHash":"6f43c56eb8b96fc8bdd2411d18b03aa585ae555941c0a99bedfcc2abe55c28c0","addressRefs":[]},"22326048-1218-49b7-99bd-b71bf9f8212c":{"id":"22326048-1218-49b7-99bd-b71bf9f8212c","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6644,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"65f7e17e-61c6-452c-a352-abc2f9e92fb3":{"id":"65f7e17e-61c6-452c-a352-abc2f9e92fb3","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.2.1","title":"Token Address (Monad)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6645,"content":"`0x6B405DCA74897c9442d369DcF6c0EC230f7E1c7C`","contentHash":"f8f04c50e105e26788f99c154ac287ecdeac3e7436d9b0d61aee997cb31018b9","addressRefs":["0x6b405dca74897c9442d369dcf6c0ec230f7e1c7c"]},"4e680b6a-9f48-41d7-b7aa-655a36a5c068":{"id":"4e680b6a-9f48-41d7-b7aa-655a36a5c068","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6646,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"2e3e8ebe-335d-4a66-a466-ca87e4bf42ab":{"id":"2e3e8ebe-335d-4a66-a466-ca87e4bf42ab","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6647,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"5f26f655-a1e1-4e47-b0cb-a59fb7b40e19":{"id":"5f26f655-a1e1-4e47-b0cb-a59fb7b40e19","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6648,"content":"The inflow RateLimitID is:\n\n`0x098ad67dc41c1a5892ec3ef5fd411198dc11962475e9ef2e0362e6cb7f5a2174`.","contentHash":"7a8310e9095214f00f4de747757e93aacce808102f3a774440f2b04f3c42534b","addressRefs":[]},"6e491073-f15f-49bd-ab06-3d5277c75dbb":{"id":"6e491073-f15f-49bd-ab06-3d5277c75dbb","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6649,"content":"The outflow RateLimitID is: N/A","contentHash":"5a5ba1241f4f6a5a2d7a455843bd2463ea9d5481aa9f8f87b6fe675428a7bec8","addressRefs":[]},"d7fdb0e6-5763-4cf2-ba60-25b24e9ca655":{"id":"d7fdb0e6-5763-4cf2-ba60-25b24e9ca655","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6650,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"607a906a-da69-4105-a519-6e4cfa529c1d":{"id":"607a906a-da69-4105-a519-6e4cfa529c1d","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6651,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"d611f80cb40a432ea119c598c732961d7f492579e57452513915d7b2368d3fdd","addressRefs":[]},"a3862cd4-ff0e-4f7d-bcf9-cc1a207c74d6":{"id":"a3862cd4-ff0e-4f7d-bcf9-cc1a207c74d6","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6652,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A\n- `slope`: N/A","contentHash":"868ef21c91f22d83076d592b9bfad81c108b9a5c1eed56322abe0eafea2d3a7a","addressRefs":[]},"ad810569-b88a-4d10-9563-cc0e2cfb27f4":{"id":"ad810569-b88a-4d10-9563-cc0e2cfb27f4","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6653,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"53743f66-97ba-44ed-b386-b0ab75d9b8e4":{"id":"53743f66-97ba-44ed-b386-b0ab75d9b8e4","doc_no":"A.6.1.1.2.2.6.1.3.1.12.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6654,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"ffa0ca69-c416-4163-a1c6-b863f5d38c3f":{"id":"ffa0ca69-c416-4163-a1c6-b863f5d38c3f","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2","title":"Ethereum Mainnet - Uniswap v3 AUSD/USDC Swaps Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6655,"content":"The documents herein contain the Instance Configuration Document for the Uniswap v3 AUSD/USDC Swaps Instance.","contentHash":"f1cabcb627749c25c5923bddbca25396c10945dca2fe0caf6f98a08b7717396e","addressRefs":[]},"f13c08b4-db8a-4b52-9c99-55b2b2537153":{"id":"f13c08b4-db8a-4b52-9c99-55b2b2537153","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6656,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"e33ee131-43d9-472f-b8da-3a1a365cf884":{"id":"e33ee131-43d9-472f-b8da-3a1a365cf884","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6657,"content":"The documents herein define the parameters of the Uniswap v3 AUSD/USDC Swaps Instance of the Allocation System Primitive.","contentHash":"eba54ab7f4ea2afd7f0c3a78cc4cae5abbffa30488ee423201f7045f8d5ee281","addressRefs":[]},"575d774f-ca5c-4f77-a56a-a818c6313f0e":{"id":"575d774f-ca5c-4f77-a56a-a818c6313f0e","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6658,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"b797c786-724a-4355-905c-211c8eedbbcc":{"id":"b797c786-724a-4355-905c-211c8eedbbcc","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6659,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"c742ce08-484e-4f55-a422-00d6b4852ef8":{"id":"c742ce08-484e-4f55-a422-00d6b4852ef8","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6660,"content":"Uniswap v3 AUSD/USDC","contentHash":"133f246cb8ea2aac79de82e3eb2f35ccc5af88bcdaddf4754c1b07e23ca2c078","addressRefs":[]},"7156baa8-7cbf-4739-8b35-ae2dcf60601d":{"id":"7156baa8-7cbf-4739-8b35-ae2dcf60601d","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6661,"content":"USDC and AUSD","contentHash":"999ebdd48dd35012dd2f3891ace89987092855bf0933638e151fd9998c49469c","addressRefs":[]},"0f2e4756-a0ad-4d33-b17a-a2fa5148ce80":{"id":"0f2e4756-a0ad-4d33-b17a-a2fa5148ce80","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6662,"content":"Uniswap V3 AUSD/USDC Pool","contentHash":"046ca7339f125bdf701c783dd857f50e00e36f7fdb1941c6e6d01e0df43dd48b","addressRefs":[]},"fb504b91-0e11-405a-bfb4-3dce679857b6":{"id":"fb504b91-0e11-405a-bfb4-3dce679857b6","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6663,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"9dacb60c-fa1c-48cf-94c7-6b25cfbf9b28":{"id":"9dacb60c-fa1c-48cf-94c7-6b25cfbf9b28","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.2.1","title":"Underlying Asset Address (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6664,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"5adc9cd0-d960-45b9-9c35-23e5dc0d1ff9":{"id":"5adc9cd0-d960-45b9-9c35-23e5dc0d1ff9","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.2.2","title":"Underlying Asset Address (AUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6665,"content":"`0x00000000eFE302BEAA2b3e6e1b18d08D69a9012a`","contentHash":"a46d00e1291e0e83786e8b6f0f1f1fcad4c00f15b21c1cf91487ee0535a472a6","addressRefs":["0x00000000efe302beaa2b3e6e1b18d08d69a9012a"]},"75920dcb-2cbb-4be7-b0a8-4ed1b5eef507":{"id":"75920dcb-2cbb-4be7-b0a8-4ed1b5eef507","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6666,"content":"`0xbAFeAd7c60Ea473758ED6c6021505E8BBd7e8E5d`","contentHash":"03832588825f883e3fe6da5e7f5cf91039d0f8d4f4914ff37f917c1774c96548","addressRefs":["0xbafead7c60ea473758ed6c6021505e8bbd7e8e5d"]},"1de93819-97a2-450c-9a2f-5ad1d3c5ac9f":{"id":"1de93819-97a2-450c-9a2f-5ad1d3c5ac9f","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6667,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"5e3c790b-5e6f-472c-845e-017bc8023c52":{"id":"5e3c790b-5e6f-472c-845e-017bc8023c52","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.3.1","title":"Inflow RateLimitID (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6668,"content":"The inflow RateLimitID is: `0x6e850dcb18bea10055c82d1e3753f551b1228d04b81350ba117235de19f9a0da`.","contentHash":"00e8dd7e84d9b76253fc9620c879788786c5791d307365c73700b5811fcf8bad","addressRefs":[]},"5520059a-dca9-4212-8578-2fbefe501034":{"id":"5520059a-dca9-4212-8578-2fbefe501034","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.3.2","title":"Outflow RateLimitID (AUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6669,"content":"The outflow RateLimitID is: `0x7dd93dac252469b97c259284118454a6a09efd0e5f781dec59acc240f8f88402`.","contentHash":"81cadc9e1fd167257180cb2dfa7081b8ea0c8eb5b70335782861cfafd5d17eba","addressRefs":[]},"a4bfb5a5-7313-4d78-b9e9-eaa093dd510f":{"id":"a4bfb5a5-7313-4d78-b9e9-eaa093dd510f","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6670,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"37b74730-eeef-4f2a-89cc-699fa51b176b":{"id":"37b74730-eeef-4f2a-89cc-699fa51b176b","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6671,"content":"The deposit rate limits are:\n\n- `maxAmount`: N/A - swaps only\n- `slope`: N/A - swaps only","contentHash":"9aacd74b2f328e23b05a3a9de3aec35bb15339552aa40aa664957a794e1f6695","addressRefs":[]},"52f681eb-f0eb-4d36-95dd-4d239fef72b9":{"id":"52f681eb-f0eb-4d36-95dd-4d239fef72b9","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6672,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A - swaps only","contentHash":"be46260dae2beffad3058dbca73d719da91f7f5f4e4b688e1af7e4d9a2f05aea","addressRefs":[]},"e21c0b53-fc2a-46d1-b820-f9a5471c7efb":{"id":"e21c0b53-fc2a-46d1-b820-f9a5471c7efb","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6673,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000 AUSD/USDC\n- `slope`: 100,000,000 AUSD/USDC per day\n- `maxSlippage`: 0.1%","contentHash":"edc64eeeaad24626f9c1777edc1bbadd9c731004495e1040257eef8364802d53","addressRefs":[]},"9e2b3dee-8c09-4a75-888a-b1608201f1bc":{"id":"9e2b3dee-8c09-4a75-888a-b1608201f1bc","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6674,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"4bfb42c0-cb39-4d13-bf80-6d0a0a51c47d":{"id":"4bfb42c0-cb39-4d13-bf80-6d0a0a51c47d","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6675,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"960ce9e1-84f5-4798-81a6-6619ea153552":{"id":"960ce9e1-84f5-4798-81a6-6619ea153552","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6676,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer parameters.","contentHash":"fb9cdee40bad95b4561c802450d9f2390b5c2ba57f0791739315c5e5ddbba48f","addressRefs":[]},"dab70e48-7329-4bb4-87cc-3737c3c6336e":{"id":"dab70e48-7329-4bb4-87cc-3737c3c6336e","doc_no":"A.6.1.1.2.2.6.1.3.1.12.2.4.1","title":"Parameters For Stable Stable Pools","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6677,"content":"- `twapSecondsAgo`: 600\n- `maxTickDelta`: 200\n- `lowerTickBound`: -10\n- `upperTickBound`: +10","contentHash":"53c87d4be70430f2126769d1ff2e6e394b46cc8086770c06187e07d18baf391e","addressRefs":[]},"cca4236a-47f9-4b4f-81ef-c31a5ee624aa":{"id":"cca4236a-47f9-4b4f-81ef-c31a5ee624aa","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3","title":"Ethereum Mainnet - Uniswap v3 AUSD/USDC LP Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6678,"content":"The documents herein contain the Instance Configuration Document for the Uniswap v3 AUSD/USDC LP Instance.","contentHash":"834aab84bef9ada77be85b506cefcfe64ee4cee4cfbff72751d37a4b944e0b22","addressRefs":[]},"9e34658e-136a-4f6e-baf3-e2f31805dc61":{"id":"9e34658e-136a-4f6e-baf3-e2f31805dc61","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6679,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"2db140cc-9052-4ba6-bd8d-3662c4257d9e":{"id":"2db140cc-9052-4ba6-bd8d-3662c4257d9e","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6680,"content":"The documents herein define the parameters of the Uniswap v3 AUSD/USDC LP Instance of the Allocation System Primitive.","contentHash":"02996185ad283fd1382249ca1a4498146511e8225ff9376f74e5f34752cae18e","addressRefs":[]},"9aa5a907-0c1a-405c-8a8b-04f95b236c8c":{"id":"9aa5a907-0c1a-405c-8a8b-04f95b236c8c","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6681,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"68768ca1-ac88-4629-adbb-df3351dc14ef":{"id":"68768ca1-ac88-4629-adbb-df3351dc14ef","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6682,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"0311d64a-06f8-474e-bfcc-46a21e09aca7":{"id":"0311d64a-06f8-474e-bfcc-46a21e09aca7","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6683,"content":"Uniswap v3 AUSD/USDC","contentHash":"133f246cb8ea2aac79de82e3eb2f35ccc5af88bcdaddf4754c1b07e23ca2c078","addressRefs":[]},"8d7b7008-1e6f-4f9a-b786-637b33734ebc":{"id":"8d7b7008-1e6f-4f9a-b786-637b33734ebc","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6684,"content":"USDC and AUSD","contentHash":"999ebdd48dd35012dd2f3891ace89987092855bf0933638e151fd9998c49469c","addressRefs":[]},"8b10ab2e-d491-46de-994c-9c8fe4958b33":{"id":"8b10ab2e-d491-46de-994c-9c8fe4958b33","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6685,"content":"Uniswap V3 AUSD/USDC Pool","contentHash":"046ca7339f125bdf701c783dd857f50e00e36f7fdb1941c6e6d01e0df43dd48b","addressRefs":[]},"8bdcceab-3308-47b6-87f7-c137be46e2ba":{"id":"8bdcceab-3308-47b6-87f7-c137be46e2ba","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6686,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"a534cc96-a00b-41db-8120-156faddbdc56":{"id":"a534cc96-a00b-41db-8120-156faddbdc56","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.2.1","title":"Underlying Asset Address (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6687,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"d3d0525b-c3d0-42e6-bba4-519d22247856":{"id":"d3d0525b-c3d0-42e6-bba4-519d22247856","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.2.2","title":"Underlying Asset Address (AUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6688,"content":"`0x00000000eFE302BEAA2b3e6e1b18d08D69a9012a`","contentHash":"a46d00e1291e0e83786e8b6f0f1f1fcad4c00f15b21c1cf91487ee0535a472a6","addressRefs":["0x00000000efe302beaa2b3e6e1b18d08d69a9012a"]},"5ef626d9-9f44-4088-b874-5a06b0730f12":{"id":"5ef626d9-9f44-4088-b874-5a06b0730f12","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6689,"content":"`0xbAFeAd7c60Ea473758ED6c6021505E8BBd7e8E5d`","contentHash":"03832588825f883e3fe6da5e7f5cf91039d0f8d4f4914ff37f917c1774c96548","addressRefs":["0xbafead7c60ea473758ed6c6021505e8bbd7e8e5d"]},"a0cd0ff3-ffba-4b49-945b-06f0b402989a":{"id":"a0cd0ff3-ffba-4b49-945b-06f0b402989a","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6690,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"369980d8-10a0-4aa9-a3ef-b3ef5112ad5a":{"id":"369980d8-10a0-4aa9-a3ef-b3ef5112ad5a","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.3.1","title":"Inflow RateLimitID (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6691,"content":"The inflow RateLimitID is: `0x71efb11b03476e40dcc1ade629d360114fcbf838d70a3211270f69414ba9a187`.","contentHash":"6dcf9058a3b996bab804e2688f0d764b944b8e1f4e32a89d5f507730feb47213","addressRefs":[]},"fc8163c7-99af-416f-ad27-9a805c592778":{"id":"fc8163c7-99af-416f-ad27-9a805c592778","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.3.2","title":"Inflow RateLimitID (AUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6692,"content":"The inflow RateLimitID is: `0x89c0cb8c17898781d7c1776eafcf73fd0b570659ad5c3791ddcbefe66b001541`.","contentHash":"7df7073c759c4602a408a60dedc7c331d6f419d0d5878d1be9003fa2db53c64d","addressRefs":[]},"3377cf40-41df-4cb8-9b0b-e0fa0c89b20e":{"id":"3377cf40-41df-4cb8-9b0b-e0fa0c89b20e","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.3.3","title":"Outflow RateLimitID (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6693,"content":"The outflow RateLimitID is: `0x17c7a2da0785bd1ad67b8207080dbc243cfc4e573cbac18a68d0bd4b788a1dfc`.","contentHash":"7f81a21fbad0c5cb8b4beabd6ccfeec8df12ea34d981a92cb65a2c1322d6598d","addressRefs":[]},"7e8b0d83-300b-4127-a738-0c6c833b115b":{"id":"7e8b0d83-300b-4127-a738-0c6c833b115b","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.3.4","title":"Outflow RateLimitID (AUSD)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6694,"content":"The outflow RateLimitID is: `0xf353a8cb19089be9c21260f788c98069b2cef6a8a4bf9d061b3e5e7629a85671`.","contentHash":"8b1877592813d7ec266c46ea81a95b6c13672590c7a9c94e1a4fc99d5ef0fc72","addressRefs":[]},"fe6667c8-268e-4f3b-9d08-0538d47df313":{"id":"fe6667c8-268e-4f3b-9d08-0538d47df313","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6695,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"2a16ab46-2924-4c7d-8c47-26f8119fcf62":{"id":"2a16ab46-2924-4c7d-8c47-26f8119fcf62","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6696,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 AUSD/USDC\n- `slope`: 25,000,000 AUSD/USDC per day","contentHash":"f77b4022bfcd1449a1c18f8352441227306c913c72c54f527b15fc0435d91874","addressRefs":[]},"2f0a3fb8-6b7a-4c37-90c8-f2b277289969":{"id":"2f0a3fb8-6b7a-4c37-90c8-f2b277289969","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6697,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"5a987f26-765c-4464-9b18-9f2d88098304":{"id":"5a987f26-765c-4464-9b18-9f2d88098304","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6698,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"f33d7fc9-9654-4aa8-8ed5-13881c37ba24":{"id":"f33d7fc9-9654-4aa8-8ed5-13881c37ba24","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6699,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"6b6dd157-be7c-4170-a25d-f65f529e48b5":{"id":"6b6dd157-be7c-4170-a25d-f65f529e48b5","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6700,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer parameters.","contentHash":"fb9cdee40bad95b4561c802450d9f2390b5c2ba57f0791739315c5e5ddbba48f","addressRefs":[]},"cabd3b71-0346-4be4-9b5c-bf13dd7a0ab9":{"id":"cabd3b71-0346-4be4-9b5c-bf13dd7a0ab9","doc_no":"A.6.1.1.2.2.6.1.3.1.12.3.4.1","title":"Parameters For Stable Stable Pools","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6701,"content":"- `twapSecondsAgo`: 600\n- `maxTickDelta`: 200\n- `lowerTickBound`: -10\n- `upperTickBound`: +10","contentHash":"53c87d4be70430f2126769d1ff2e6e394b46cc8086770c06187e07d18baf391e","addressRefs":[]},"edcc1342-e0ca-4860-90bf-f5b4053d79df":{"id":"edcc1342-e0ca-4860-90bf-f5b4053d79df","doc_no":"A.6.1.1.2.2.6.1.3.1.13","title":"Maple","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6702,"content":"The Ethereum Mainnet Instances of the Maple Protocol with `Active` Status are stored herein.","contentHash":"8fc7c8ba100ab5d1abcce02e163a69acc6af84061a97d576f93c43fc63481e53","addressRefs":[]},"7502f64c-3276-478e-8f98-53a2377ca1a2":{"id":"7502f64c-3276-478e-8f98-53a2377ca1a2","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1","title":"Ethereum Mainnet - Maple syrupUSDC Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6703,"content":"The documents herein contain the Instance Configuration Document for the Maple syrupUSDC Instance.","contentHash":"109c8dccd61eb0389a104db923d775e3f0396d2aab678e9a035eddd8fa0f9726","addressRefs":[]},"5801de75-952f-4f5d-a0de-fd1643adb3f2":{"id":"5801de75-952f-4f5d-a0de-fd1643adb3f2","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6704,"content":"`Covered`","contentHash":"be251b9c103a237d7fd6952bfb2c1b349af1ac579ad9e75a852e4a05ff8b3ca2","addressRefs":[]},"9fda752d-6c8a-4bb2-bea9-da336d41586f":{"id":"9fda752d-6c8a-4bb2-bea9-da336d41586f","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6705,"content":"The documents herein define the parameters of the Maple syrupUSDC Instance of the Allocation System Primitive.","contentHash":"7a5995514fb41f4feb4c9a5d874d6bfdb677a4be8bd45e3ac0bd436f1cac467b","addressRefs":[]},"18cadbf1-8268-46a4-867c-5b8d3639f840":{"id":"18cadbf1-8268-46a4-867c-5b8d3639f840","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6706,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"933bb96c-0f5c-4ad1-a137-21442969b44c":{"id":"933bb96c-0f5c-4ad1-a137-21442969b44c","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6707,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"facc3c45-33a1-46f6-8e93-0474f87f40d6":{"id":"facc3c45-33a1-46f6-8e93-0474f87f40d6","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6708,"content":"Maple","contentHash":"187c93774dbd4c674ecaf745f0c304bb494ccfca31cd88c028251f97f09569c5","addressRefs":[]},"5da95711-2be7-4ff8-bbd1-245cd12f8b62":{"id":"5da95711-2be7-4ff8-bbd1-245cd12f8b62","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6709,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"b81399bc-f30a-4abb-a4f4-380517147462":{"id":"b81399bc-f30a-4abb-a4f4-380517147462","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6710,"content":"syrupUSDC","contentHash":"3b50b2203f4915b0b7b3098fc5d9205e27421a900c9bf60f5fe7d484e2a25003","addressRefs":[]},"68f4487a-c475-400f-9a24-0eaba47da45b":{"id":"68f4487a-c475-400f-9a24-0eaba47da45b","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6711,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"f4f3bc84-0544-47a0-ac5d-e605714c2354":{"id":"f4f3bc84-0544-47a0-ac5d-e605714c2354","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6712,"content":"`0x80ac24aA929eaF5013f6436cdA2a7ba190f5Cc0b`","contentHash":"c9da76a92fdbedaeaebc89f6ae1550989ebcbf6b96f68777626b48b5da9dfbce","addressRefs":["0x80ac24aa929eaf5013f6436cda2a7ba190f5cc0b"]},"166f7435-79ad-4e4c-be93-85ca69ec63ec":{"id":"166f7435-79ad-4e4c-be93-85ca69ec63ec","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6713,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"891be5d8-3a84-4d51-98d5-85f0e18dc791":{"id":"891be5d8-3a84-4d51-98d5-85f0e18dc791","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6714,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"cef889e791f2b83bcbb0a9c31a4ac27908ed8e42d81e0663f3596e7e35abb973","addressRefs":[]},"19362744-13c9-4f42-98af-18eae4946290":{"id":"19362744-13c9-4f42-98af-18eae4946290","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6715,"content":"The inflow RateLimitID is: `0x99a69e57b2f387f999d6adff6eb2e707b59fdb54f06ca6211b4f20956e9bfe10`","contentHash":"1fcebf3d37fbcb31666be37de75a10dc1905b221595feddede05658d789c9047","addressRefs":[]},"63e7a899-dfd5-489b-9ea0-6ccb527e64b7":{"id":"63e7a899-dfd5-489b-9ea0-6ccb527e64b7","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6716,"content":"The outflow RateLimitID will be specified in a future iteration of the Atlas.","contentHash":"7987b9701aaf5db6bea1d524cf8149e2b7abaecf224b235e16b07f6cc57d314a","addressRefs":[]},"f69051f4-25f1-4519-8776-30c753eb351e":{"id":"f69051f4-25f1-4519-8776-30c753eb351e","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6717,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"5ce46c5d-978e-4fe3-a109-8a11833b1b09":{"id":"5ce46c5d-978e-4fe3-a109-8a11833b1b09","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6718,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"d611f80cb40a432ea119c598c732961d7f492579e57452513915d7b2368d3fdd","addressRefs":[]},"2068313d-3791-4771-9e0d-f74dffa4d729":{"id":"2068313d-3791-4771-9e0d-f74dffa4d729","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6719,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: 0 USDC","contentHash":"e06981080c51686a971625d121bc68f7bf4a2daa8585dd2330857cc59e883d65","addressRefs":[]},"69ce0ff7-8847-43a1-93c8-47d143d86f69":{"id":"69ce0ff7-8847-43a1-93c8-47d143d86f69","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6720,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"38bc059a-09d1-4a86-bade-4b0da4bf8413":{"id":"38bc059a-09d1-4a86-bade-4b0da4bf8413","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.5.1","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6721,"content":"`setMaxExchangeRate(MAPLE_SYRUP_USDC, 1e6, 3e6)`","contentHash":"baef0a4df7d4ea3ab8b9bb25efa66efae7c7081af5484dd28885de2e1d7c93d7","addressRefs":[]},"d86392f8-071a-4167-9d44-64a8150c2b18":{"id":"d86392f8-071a-4167-9d44-64a8150c2b18","doc_no":"A.6.1.1.2.2.6.1.3.1.13.1.2.5.2","title":"Maximum Exposure","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6722,"content":"The Maximum Exposure for this Instance is 0 USD.","contentHash":"000c2700aa2243b26617bab03c6cf2fc7bca87d60d9b2ebeb94ce3731f5af748","addressRefs":[]},"be7157cb-9469-4f59-b1a0-d22a62e97242":{"id":"be7157cb-9469-4f59-b1a0-d22a62e97242","doc_no":"A.6.1.1.2.2.6.1.3.1.14","title":"Tokenized Treasury","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6723,"content":"The Ethereum Mainnet Tokenized Treasury Instances with `Active` Status are stored herein.","contentHash":"5c5500c3e19ee1cb3ba05358b6219d14100f42c77715a96e9d5147c2adc1b748","addressRefs":[]},"5e38198e-1577-4ab0-900a-91b6d8284387":{"id":"5e38198e-1577-4ab0-900a-91b6d8284387","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1","title":"Ethereum Mainnet - Tokenized Treasury JTRSY Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6724,"content":"The documents herein contain the Instance Configuration Document for the Tokenized Treasury JTRSY Instance.","contentHash":"ba1e25742d90a9bc08197bf6c90734550a0f11a1f68a8c856faa21c55c037676","addressRefs":[]},"fde7f4bb-0873-4d99-bef5-694a53300eae":{"id":"fde7f4bb-0873-4d99-bef5-694a53300eae","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6725,"content":"`Pending`","contentHash":"2986effe9fae335e819f546d8f69212a5a1e8bd5f01a449e4e295a5dee70536f","addressRefs":[]},"1834c864-183a-4835-bb17-b1107e41abbb":{"id":"1834c864-183a-4835-bb17-b1107e41abbb","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6726,"content":"The documents herein define the parameters of the Tokenized Treasury JTRSY Instance of the Allocation System Primitive.","contentHash":"71cf110ed77a5b7dae9370b6616dc4ea2cb2fefff2839f8a88f15061038764cf","addressRefs":[]},"3a505b8a-4ff1-40bf-aa03-ea7c4550422a":{"id":"3a505b8a-4ff1-40bf-aa03-ea7c4550422a","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6727,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"cdd4e8c9-b1be-4f96-9b65-d0ba9942202d":{"id":"cdd4e8c9-b1be-4f96-9b65-d0ba9942202d","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6728,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"6f3423c8-3aba-4852-9011-09dc0d90fa3b":{"id":"6f3423c8-3aba-4852-9011-09dc0d90fa3b","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6729,"content":"Tokenized Treasury","contentHash":"765956f16e1123dc79da97465d2e9e324bd1282a80e142b689727109d7601dfe","addressRefs":[]},"3f39032c-cc00-4ea9-be78-9e02e9fc4a25":{"id":"3f39032c-cc00-4ea9-be78-9e02e9fc4a25","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6730,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"6a11e241-9dba-423f-b9aa-31fa37c96ab3":{"id":"6a11e241-9dba-423f-b9aa-31fa37c96ab3","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6731,"content":"JTRSY","contentHash":"a5435fae1627abed97fa9fff2bc126b9fa56b41fa129c9ce2c4e07c41c58f5aa","addressRefs":[]},"75e8bf90-46f3-4e53-b6b9-f8b30dd80da7":{"id":"75e8bf90-46f3-4e53-b6b9-f8b30dd80da7","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6732,"content":"The documents herein define the Instance-specific contract addresses.","contentHash":"c63085404b6afeee0de5cf5f3ae8df3f1ddf997c4a9164629000855bea0f1a81","addressRefs":[]},"5c346c1b-a942-4ced-9267-7087d5c718a4":{"id":"5c346c1b-a942-4ced-9267-7087d5c718a4","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6733,"content":"`0x8c213ee79581Ff4984583C6a801e5263418C4b86`","contentHash":"9c11681c4a39570279026209b5683b7d47ab2e2d4ef46f930949b046522f286c","addressRefs":["0x8c213ee79581ff4984583c6a801e5263418c4b86"]},"c519baf9-b02c-4c07-a113-ac73738a217c":{"id":"c519baf9-b02c-4c07-a113-ac73738a217c","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2.2","title":"Centrifuge ERC-7540 Vault Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6734,"content":"`0xFE6920eB6C421f1179cA8c8d4170530CDBdfd77A`","contentHash":"31a8cbaf6080390ffbff32697960927119a71d7a63ceefe697f351346a34ce9f","addressRefs":["0xfe6920eb6c421f1179ca8c8d4170530cdbdfd77a"]},"e13f54bc-19d3-4a0f-a846-2c3c4154a19e":{"id":"e13f54bc-19d3-4a0f-a846-2c3c4154a19e","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2.3","title":"JTRSY Rate Provider Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6735,"content":"`0x7FB719Fc99A737bA15D676a09491805cD9623A8f`","contentHash":"254eb0b80c102fe70dfb03bb03eb8188edf7492d61141d65190670c63cdf6f19","addressRefs":["0x7fb719fc99a737ba15d676a09491805cd9623a8f"]},"fd19b075-d30d-4a8e-90f0-c7ab8a2cd48b":{"id":"fd19b075-d30d-4a8e-90f0-c7ab8a2cd48b","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2.4","title":"Pocket Contract Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6736,"content":"`0x30860b17f984D0f909B71Ab8D7b0C2e01C650479`","contentHash":"25d1e41e26026ac826a48f4ed974fca8c0858be40695bc3767831a0837eb5a37","addressRefs":["0x30860b17f984d0f909b71ab8d7b0c2e01c650479"]},"536e4413-c923-45e8-a126-8120fd9d2c72":{"id":"536e4413-c923-45e8-a126-8120fd9d2c72","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2.5","title":"Token Redeemer Contract Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6737,"content":"`0x471C4D7B1F38009061e7c545A08732d82Bd54B15`","contentHash":"96c99f9394465431cc21d4f03dfaab05e8b1644916d4b1fcf653506a5a6eaf1d","addressRefs":["0x471c4d7b1f38009061e7c545a08732d82bd54b15"]},"d2069cde-3b55-487a-9b1d-919bd3f76197":{"id":"d2069cde-3b55-487a-9b1d-919bd3f76197","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2.6","title":"Owner Timelock Contract Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6738,"content":"`0xfB805f2f88e862e687bEBdF120306ef39380F3bf`","contentHash":"1d7e0423e7e78b34ccef27120b271524171bd1eee29a180487ac265603d5badc","addressRefs":["0xfb805f2f88e862e687bebdf120306ef39380f3bf"]},"7f011dc2-7624-402e-86cb-c036d1cf9afc":{"id":"7f011dc2-7624-402e-86cb-c036d1cf9afc","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.2.7","title":"RWA Instance Contract Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6739,"content":"`0x34B7385D87793bAc8b94d95d8eF75200787A61F7`","contentHash":"f3f8964830364487977f6b59b951013099299c32d2f393c0301c11bb8ab483df","addressRefs":["0x34b7385d87793bac8b94d95d8ef75200787a61f7"]},"850f1210-d355-48ef-8ba9-dcc70bb90f0e":{"id":"850f1210-d355-48ef-8ba9-dcc70bb90f0e","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6740,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Atlas.","contentHash":"0182e25231e3f203ffa5e49ec3979a36e84de71ddc590ef42f49d41c0eec8b8d","addressRefs":[]},"abc0b1fc-4922-40f1-8ea9-60fba89f0e5f":{"id":"abc0b1fc-4922-40f1-8ea9-60fba89f0e5f","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6741,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"2e5234f6-0cae-4689-b8da-61ad99f20c31":{"id":"2e5234f6-0cae-4689-b8da-61ad99f20c31","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6742,"content":"The inflow rate limits are:\n\n- `maxAmount`: 0 USDS\n- `slope`: 0 USDS per day","contentHash":"83e00897449957af8d8bc5a2eaff07ca1ced2b5809c0ba1bc565093a30c8cb97","addressRefs":[]},"e460967c-baf1-4c39-89c8-38bb329e492e":{"id":"e460967c-baf1-4c39-89c8-38bb329e492e","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6743,"content":"The outflow rate limits are:\n\n- `maxAmount`: 0 USDS\n- `slope`: 0 USDS per day","contentHash":"f502091bfff833b7288284a029dd316fd0764df0af01f38fab2a787b31771abe","addressRefs":[]},"1daedcbc-29a1-4dbd-8442-21cefec40c3a":{"id":"1daedcbc-29a1-4dbd-8442-21cefec40c3a","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6744,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"a46f85c1-48be-4070-8848-74d392c3fed5":{"id":"a46f85c1-48be-4070-8848-74d392c3fed5","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6745,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"65ca009e-8d70-4dd5-80d3-e6e0b9beae2e":{"id":"65ca009e-8d70-4dd5-80d3-e6e0b9beae2e","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.4","title":"Instance-specific Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6746,"content":"The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer parameters.","contentHash":"fb9cdee40bad95b4561c802450d9f2390b5c2ba57f0791739315c5e5ddbba48f","addressRefs":[]},"16a4b87f-156e-407f-a882-d91b15a7909b":{"id":"16a4b87f-156e-407f-a882-d91b15a7909b","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.4.1","title":"Instance Configuration Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6747,"content":"The configuration parameters for this Instance are as follows:\n\n- Max Swap Size: 50,000,000 USD\n- Staleness Threshold: seven (7) days\n- Fees: 0\n- Credit Token Deposits: Disabled\n- Credit Token Withdrawals: Disabled\n- Stablecoin Swaps: Disabled","contentHash":"4f574f16e8bdb8f9707a992ed3c50fec4d78c1e4e643ea4cbe495c0e74e13cf0","addressRefs":[]},"7fbed34a-d69f-49eb-af6f-56a7522e6fda":{"id":"7fbed34a-d69f-49eb-af6f-56a7522e6fda","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.4.2","title":"Issuer-Specific Role Holders","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6748,"content":"The documents herein define the role holders that are specific to this Instance's credit token issuer.","contentHash":"90886582d6c09da6c3e6540a2d7b23a74b20f463b1627227e9160600e6ac3637","addressRefs":[]},"6c15b0a1-b9f1-40be-80b1-4c5565c30044":{"id":"6c15b0a1-b9f1-40be-80b1-4c5565c30044","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.4.2.1","title":"Owner Role Holder","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6749,"content":"The `OWNER_ROLE`, as defined in [A.6.1.1.2.2.6.1.2.2.1.6.1 - Tokenized Treasury Owner Role](41a7e6fb-59e1-40e8-a05a-68c1520fb361), is held by Anemoy via an OpenZeppelin `TimelockController` at the address specified in [A.6.1.1.2.2.6.1.3.1.14.1.2.2.6 - Owner Timelock Contract Address](d2069cde-3b55-487a-9b1d-919bd3f76197).","contentHash":"eea8b9ba6c090ec1ee2b27d14609eec681855f5f911f2df5eea41778a58758f6","addressRefs":[]},"dee0bbce-9f64-47e3-bbb5-3eb5204be9c5":{"id":"dee0bbce-9f64-47e3-bbb5-3eb5204be9c5","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.4.2.1.1","title":"Proposer Role Holder","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6750,"content":"The `PROPOSER_ROLE` of the Owner Timelock is held by Anemoy at `0x9184DdBCc4824B76CE2AEFA72534a1a87aA5037c`.","contentHash":"7ee3f1ae5c53b4fc3cbf14c5deaeee6393167f7d2b95bdb8b0001d9683af923c","addressRefs":["0x9184ddbcc4824b76ce2aefa72534a1a87aa5037c"]},"5ffebcfd-ba9b-401b-a35d-42b4426709de":{"id":"5ffebcfd-ba9b-401b-a35d-42b4426709de","doc_no":"A.6.1.1.2.2.6.1.3.1.14.1.4.2.2","title":"Redeemer Role Holder","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6751,"content":"The `REDEEMER_ROLE`, as defined in [A.6.1.1.2.2.6.1.2.2.1.6.5 - Tokenized Treasury Redeemer Role](fbeb1921-37eb-465b-97fa-004c8e0925b1), is controlled by Anemoy; the holder address will be specified in a future iteration of the Atlas.","contentHash":"a04e1f6d4290967bd703e64e0dcd500168a1cbc9c82b6a4513a4d810fa51f6ae","addressRefs":[]},"fbb34f07-a5c8-475e-9842-fc5c9b9bd359":{"id":"fbb34f07-a5c8-475e-9842-fc5c9b9bd359","doc_no":"A.6.1.1.2.2.6.1.3.2","title":"Avalanche Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6752,"content":"The Avalanche Instances of the Grove Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"25a74ec1e338060d50c355c71374daa3a5595009e976b67d7e03124d24f02ed8","addressRefs":[]},"87310712-edfa-4882-a22e-7b891f566026":{"id":"87310712-edfa-4882-a22e-7b891f566026","doc_no":"A.6.1.1.2.2.6.1.3.2.1","title":"Centrifuge","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6753,"content":"The Avalanche Instances of the Centrifuge Protocol with `Active` Status are stored herein.","contentHash":"6f4ec022d2ffc7a1e8a2b156babdefb2337a71e263206b302f143dbb6bf49e13","addressRefs":[]},"3c731296-858a-4c27-a5cc-6b7ff208cc16":{"id":"3c731296-858a-4c27-a5cc-6b7ff208cc16","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1","title":"Avalanche - Centrifuge JTRSY Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6754,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge JTRSY Instance.","contentHash":"ac20bee363ce023754729280d304dd89cdf76ddf5720dd72e0e02226d8d811bb","addressRefs":[]},"6b0ac1c6-dd10-4996-8924-2525d50abdbb":{"id":"6b0ac1c6-dd10-4996-8924-2525d50abdbb","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6755,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"5bc93313-446b-4dc2-a964-c565ee7718cf":{"id":"5bc93313-446b-4dc2-a964-c565ee7718cf","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6756,"content":"The documents herein define the parameters of the Centrifuge JTRSY Instance of the Allocation System Primitive.","contentHash":"7e5222005db9b113d00b229acfc5e6f1894d3676cfc4d1a6930b44c771130860","addressRefs":[]},"a8ac0ffa-f5f0-40e9-8b82-910ed3a00231":{"id":"a8ac0ffa-f5f0-40e9-8b82-910ed3a00231","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6757,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"0d7aa581-b3d4-4041-8be0-4bbf824dfe71":{"id":"0d7aa581-b3d4-4041-8be0-4bbf824dfe71","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6758,"content":"Avalanche","contentHash":"40515202399d262e23ee7fca28b5d73627d96f30bb61c6d064100070976e4fa9","addressRefs":[]},"e916d986-41b1-4f76-ab3f-3bd0f233adc1":{"id":"e916d986-41b1-4f76-ab3f-3bd0f233adc1","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6759,"content":"Centrifuge","contentHash":"15a808e2563fe8cc5805166b2619e590c1f1e9c1b0d43c0b85783ad6dc26b9dc","addressRefs":[]},"1c1e18f7-1202-4b9e-81d2-27736659ea42":{"id":"1c1e18f7-1202-4b9e-81d2-27736659ea42","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6760,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"3ea884e0-bb0e-4dcc-8644-2840b524c8b7":{"id":"3ea884e0-bb0e-4dcc-8644-2840b524c8b7","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6761,"content":"JTRSY","contentHash":"a5435fae1627abed97fa9fff2bc126b9fa56b41fa129c9ce2c4e07c41c58f5aa","addressRefs":[]},"bbcf802e-a2bd-4382-91e7-bc3e813683e9":{"id":"bbcf802e-a2bd-4382-91e7-bc3e813683e9","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6762,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"f9f790ea-f67a-4e6d-ac63-cd84faf208fe":{"id":"f9f790ea-f67a-4e6d-ac63-cd84faf208fe","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6763,"content":"`0xFE6920eB6C421f1179cA8c8d4170530CDBdfd77A`","contentHash":"31a8cbaf6080390ffbff32697960927119a71d7a63ceefe697f351346a34ce9f","addressRefs":["0xfe6920eb6c421f1179ca8c8d4170530cdbdfd77a"]},"fcf231c8-f8a5-4073-be59-cde9a5f86a29":{"id":"fcf231c8-f8a5-4073-be59-cde9a5f86a29","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6764,"content":"`0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E`","contentHash":"974d33f0ae152877034995c7f4480ca851dd613133d1a0abf5a2436c9029fc59","addressRefs":["0xb97ef9ef8734c71904d8002f8b6bc66dd9c48a6e"]},"d926a814-26d2-4f62-a92b-b05b3253ed89":{"id":"d926a814-26d2-4f62-a92b-b05b3253ed89","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6765,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"5a1eb061-1050-45e0-9b31-157440e84790":{"id":"5a1eb061-1050-45e0-9b31-157440e84790","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6766,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"0c432f68-5bbf-449e-b9fb-c089f3c750c7":{"id":"0c432f68-5bbf-449e-b9fb-c089f3c750c7","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6767,"content":"The inflow rate limits are:\n\n- `maxAmount`: 50,000,000 USDC\n- `slope`(per day): 50,000,000 USDC","contentHash":"ab370a16655972398dbbc8866e89c71b4e560ce02da475c4da5a4d98faf4048a","addressRefs":[]},"6e549221-bbf2-4c58-922d-649e7beee41c":{"id":"6e549221-bbf2-4c58-922d-649e7beee41c","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6768,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"b600285512240f72e900c37ed9f60568499d3974a34f419964db51282cee8e36","addressRefs":[]},"76b4c9cd-d637-40f1-a83d-b7f4a7c46d1b":{"id":"76b4c9cd-d637-40f1-a83d-b7f4a7c46d1b","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6769,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"905f3980-1d3c-4703-b7f4-6edd1d97ea9a":{"id":"905f3980-1d3c-4703-b7f4-6edd1d97ea9a","doc_no":"A.6.1.1.2.2.6.1.3.2.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6770,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"bd37d6c9-2e05-4ce3-86dc-3a50d6887e6b":{"id":"bd37d6c9-2e05-4ce3-86dc-3a50d6887e6b","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2","title":"Avalanche - Centrifuge JAAA Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6771,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge JAAA Instance.","contentHash":"9b4c70bbc51698cda24fa4e40823390d7f37438500ed2d0573e60041866c285b","addressRefs":[]},"d29cee92-1484-47ad-a253-42670e3f2839":{"id":"d29cee92-1484-47ad-a253-42670e3f2839","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.1","title":"RRC Framework Full Implementation","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6772,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"2428f891-6e70-4bc2-93b8-080af94a569c":{"id":"2428f891-6e70-4bc2-93b8-080af94a569c","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6773,"content":"The documents herein define the parameters of the Centrifuge JAAA Instance of the Allocation System Primitive.","contentHash":"194a5bc7c33c622c5cbbdd1abf1077ebcc1a09ac39958e616244b148049d090e","addressRefs":[]},"08fcf58b-bb1c-416e-a0e6-6c4177341d7f":{"id":"08fcf58b-bb1c-416e-a0e6-6c4177341d7f","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6774,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"787ada98-2320-476f-8abd-20ff2df52c91":{"id":"787ada98-2320-476f-8abd-20ff2df52c91","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6775,"content":"Avalanche","contentHash":"40515202399d262e23ee7fca28b5d73627d96f30bb61c6d064100070976e4fa9","addressRefs":[]},"9acb96f8-cdf9-42a3-97b0-7300353a5919":{"id":"9acb96f8-cdf9-42a3-97b0-7300353a5919","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6776,"content":"Centrifuge","contentHash":"15a808e2563fe8cc5805166b2619e590c1f1e9c1b0d43c0b85783ad6dc26b9dc","addressRefs":[]},"803ac88c-2a85-4e75-87a4-1484b47a8c07":{"id":"803ac88c-2a85-4e75-87a4-1484b47a8c07","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6777,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"3e847695-3ad3-4b39-b01e-44787c8dcc4c":{"id":"3e847695-3ad3-4b39-b01e-44787c8dcc4c","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6778,"content":"JAAA","contentHash":"efcb18475852eaceb2beb8c102e6a4a0ea4c3b493859f247384dd7d3725815a6","addressRefs":[]},"e240e244-f34c-41b2-a3a8-ef9c4293d97b":{"id":"e240e244-f34c-41b2-a3a8-ef9c4293d97b","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6779,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"c0f78cfe-30ca-4026-a8ad-a0391debe389":{"id":"c0f78cfe-30ca-4026-a8ad-a0391debe389","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6780,"content":"`0x1121F4e21eD8B9BC1BB9A2952cDD8639aC897784`","contentHash":"f13ee7e50f0aea3181cf0160e366aa05ec19b2bf185a409fcc73596bae5b0914","addressRefs":["0x1121f4e21ed8b9bc1bb9a2952cdd8639ac897784"]},"87989bfc-6d92-4d66-b26b-e007d0b7bbc0":{"id":"87989bfc-6d92-4d66-b26b-e007d0b7bbc0","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6781,"content":"`0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E`","contentHash":"974d33f0ae152877034995c7f4480ca851dd613133d1a0abf5a2436c9029fc59","addressRefs":["0xb97ef9ef8734c71904d8002f8b6bc66dd9c48a6e"]},"f1dd540e-feb7-44f2-a8f8-df4861f584de":{"id":"f1dd540e-feb7-44f2-a8f8-df4861f584de","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6782,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow will be specified in a future iteration of the Grove Artifact.","contentHash":"7a61adff9d82bc3ed4a7c260abba564a03a2a93227ca6179cf3676fe175a49c7","addressRefs":[]},"2e51243e-6f14-4c72-97c4-e873f449bdc9":{"id":"2e51243e-6f14-4c72-97c4-e873f449bdc9","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6783,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"338e8892-584c-4ca3-9a8c-8872e4105717":{"id":"338e8892-584c-4ca3-9a8c-8872e4105717","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6784,"content":"The inflow rate limits are:\n\n- `maxAmount`: 50,000,000 USDC.\n- `slope`(per day): 50,000,000 USDC.","contentHash":"109746bdb73c888cc141bb85442c691b223162013e9273871ee2cbc95eef768b","addressRefs":[]},"9c214444-96bf-4982-9c96-7ae79769262a":{"id":"9c214444-96bf-4982-9c96-7ae79769262a","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6785,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited\n- `slope`: This parameter will be specified in a future iteration of the Grove Artifact.","contentHash":"b600285512240f72e900c37ed9f60568499d3974a34f419964db51282cee8e36","addressRefs":[]},"c03dd770-73f8-4894-8e6d-314d22aec2df":{"id":"c03dd770-73f8-4894-8e6d-314d22aec2df","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6786,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"74e35297-1d5e-4c4a-be08-741c88329039":{"id":"74e35297-1d5e-4c4a-be08-741c88329039","doc_no":"A.6.1.1.2.2.6.1.3.2.1.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6787,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"c17ab278-4750-4e54-b6c9-f1fb31d36039":{"id":"c17ab278-4750-4e54-b6c9-f1fb31d36039","doc_no":"A.6.1.1.2.2.6.1.3.2.2","title":"Curve","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6788,"content":"The Avalanche Instances of the Curve Protocol with `Active` Status are stored herein.","contentHash":"44b41383a513a0f68cd34485853e9f25a91ab5239268258de014956b88da6374","addressRefs":[]},"241a6ad1-ac18-496c-84f8-e2624497c7d9":{"id":"241a6ad1-ac18-496c-84f8-e2624497c7d9","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1","title":"Avalanche - Curve USDS/USDC Swaps Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6789,"content":"The documents herein contain the Instance Configuration Document for the Curve USDS/USDC Swaps Instance.","contentHash":"5b0c945c1194347cc504e22a9f74267310c2ed09565151fa60b74d40d552baf7","addressRefs":[]},"b4ce834c-f831-432c-9b0d-114c7e69e386":{"id":"b4ce834c-f831-432c-9b0d-114c7e69e386","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6790,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"f770ab85-be68-40ed-b63d-bcd63b240485":{"id":"f770ab85-be68-40ed-b63d-bcd63b240485","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6791,"content":"The documents herein define the parameters of the Curve USDS/USDC Swaps Instance of the Allocation System Primitive.","contentHash":"45d23287a3788b81b8e1379be0aa7f7f3ce4533d65bc438e333c3aba03f73e7f","addressRefs":[]},"425a5441-4bfe-494e-b0fb-bb040ec92973":{"id":"425a5441-4bfe-494e-b0fb-bb040ec92973","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6792,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"24009c3a-58b6-4280-aa73-6a90ef36c706":{"id":"24009c3a-58b6-4280-aa73-6a90ef36c706","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6793,"content":"Avalanche","contentHash":"40515202399d262e23ee7fca28b5d73627d96f30bb61c6d064100070976e4fa9","addressRefs":[]},"47f6b57c-b563-47fd-a97f-e7f69a4d9ebf":{"id":"47f6b57c-b563-47fd-a97f-e7f69a4d9ebf","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6794,"content":"Curve USDS/USDC","contentHash":"f3ed3508a5899a574c9b3daa6a58d85b3ef336362ec578c38e3173b8e5cfd3b0","addressRefs":[]},"4a2677c5-9a63-4e04-80c3-a1bf57a7558c":{"id":"4a2677c5-9a63-4e04-80c3-a1bf57a7558c","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6795,"content":"USDS and USDC","contentHash":"6810e4cb977ae32d70836efc8dcf991af5f59e944498b31e0a591aee8b2f8666","addressRefs":[]},"47af1c25-51d3-46cb-87f3-9576568d0f62":{"id":"47af1c25-51d3-46cb-87f3-9576568d0f62","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6796,"content":"USDSUSDC","contentHash":"5322c2b22c0fb8015ebbdea806ae2d01017a54a2c50e08152ba72003a7aed830","addressRefs":[]},"43cebf0e-dc61-4206-8fad-32ae9a2c865d":{"id":"43cebf0e-dc61-4206-8fad-32ae9a2c865d","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6797,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"741efad1-425e-4290-a398-2923e4f88537":{"id":"741efad1-425e-4290-a398-2923e4f88537","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.2.1","title":"Underlying Asset Address (USDS)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6798,"content":"`0x86Ff09db814ac346a7C6FE2Cd648F27706D1D470`","contentHash":"67f85d5b2b063e9651060d8e8c0c8df29fcf305d804070b205e04123b538270f","addressRefs":["0x86ff09db814ac346a7c6fe2cd648f27706d1d470"]},"c079b224-7cbb-4959-b087-19fb0d9260fd":{"id":"c079b224-7cbb-4959-b087-19fb0d9260fd","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.2.2","title":"Underlying Asset Address (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6799,"content":"`0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E`","contentHash":"974d33f0ae152877034995c7f4480ca851dd613133d1a0abf5a2436c9029fc59","addressRefs":["0xb97ef9ef8734c71904d8002f8b6bc66dd9c48a6e"]},"33e4a492-5a15-4e59-be41-5e66d6cfb10c":{"id":"33e4a492-5a15-4e59-be41-5e66d6cfb10c","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6800,"content":"`0xA9d7d3D7e68a0cae89FB33c736199172f405C8D3`","contentHash":"03341edd3ff88d213d05294ba4818f16b55bffa5afc7682c8ae9beb9438f9434","addressRefs":["0xa9d7d3d7e68a0cae89fb33c736199172f405c8d3"]},"2e7ae859-1656-4267-b747-e062a44ca251":{"id":"2e7ae859-1656-4267-b747-e062a44ca251","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6801,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"cef889e791f2b83bcbb0a9c31a4ac27908ed8e42d81e0663f3596e7e35abb973","addressRefs":[]},"14ef09b9-2372-48cd-9749-3408c9fcb754":{"id":"14ef09b9-2372-48cd-9749-3408c9fcb754","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6802,"content":"The inflow RateLimitID is: `0x747102351e768926d4e5f06c0ea6ac35e4dcefa77fd901f2f8ff46e4710ab4cf`","contentHash":"dadff563a867f3796f98351dd062f9adedf1ebdc0807fb888dcbc60e32f1aca1","addressRefs":[]},"8b119935-a2e9-4c11-9a03-33cf025148cc":{"id":"8b119935-a2e9-4c11-9a03-33cf025148cc","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6803,"content":"The outflow RateLimitID is: N/A.","contentHash":"483affad475b6c78cfa6846cb48795ff6ea43b13d4079c9d25d0d4a65e2aa3d7","addressRefs":[]},"bfbca274-613d-43f8-92dd-45481bc53b8f":{"id":"bfbca274-613d-43f8-92dd-45481bc53b8f","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6804,"content":"The current `maxAmount` and `slope` for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"e5eb411abadf20155e59acad4f3c0696c2b44cb3c8b38090d09489ca7a118f52","addressRefs":[]},"3fc2060c-29d2-41fa-a9e6-1b47e4073cee":{"id":"3fc2060c-29d2-41fa-a9e6-1b47e4073cee","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6805,"content":"The deposit rate limits are:\n\n- `maxAmount`: N/A - swaps only\n- `slope`: N/A - swaps only","contentHash":"9aacd74b2f328e23b05a3a9de3aec35bb15339552aa40aa664957a794e1f6695","addressRefs":[]},"67213d51-ed52-4c6d-96b6-bf0718b935b1":{"id":"67213d51-ed52-4c6d-96b6-bf0718b935b1","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6806,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: N/A - swaps only","contentHash":"be46260dae2beffad3058dbca73d719da91f7f5f4e4b688e1af7e4d9a2f05aea","addressRefs":[]},"e23f36a6-c5f5-40d4-bdd0-77e862d7a8bb":{"id":"e23f36a6-c5f5-40d4-bdd0-77e862d7a8bb","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.4.3","title":"Swap Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6807,"content":"The swap rate limits are:\n\n- `maxAmount`: 5,000,000 USDS/USDC\n- `slope`: 100,000,000 USDS/USDC per day\n- `maxSlippage`: 0.1%","contentHash":"099da0613ff00aff2144d80fa8581c4f690b38e2b80bc1d965f9a614a7a7e70d","addressRefs":[]},"e1b88e2f-2890-4b09-a4c5-d3d76b411692":{"id":"e1b88e2f-2890-4b09-a4c5-d3d76b411692","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6808,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"a13b40ae-ba04-44f0-8b66-84fbed85a765":{"id":"a13b40ae-ba04-44f0-8b66-84fbed85a765","doc_no":"A.6.1.1.2.2.6.1.3.2.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6809,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"72325c96-455c-4c19-aefc-541206494bd3":{"id":"72325c96-455c-4c19-aefc-541206494bd3","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2","title":"Avalanche - Curve USDS/USDC LP Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6810,"content":"The documents herein contain the Instance Configuration Document for the Curve USDS/USDC LP Instance.","contentHash":"6b58d90ad31a9abc35df1233386771eca4dd2190a48e8b2c6dc6e4072c8b730a","addressRefs":[]},"cbbb4d16-1c71-4274-a0c3-3806101582d9":{"id":"cbbb4d16-1c71-4274-a0c3-3806101582d9","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6811,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"bb03ff8f-5dc3-4dcb-886c-09e94a526e6c":{"id":"bb03ff8f-5dc3-4dcb-886c-09e94a526e6c","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6812,"content":"The documents herein define the parameters of the Curve USDS/USDC LP Instance of the Allocation System Primitive.","contentHash":"4484d28aabf7caa3e782f2f7f7e1cd08ec22ac4e683f3d0868a426d39e1e027a","addressRefs":[]},"695932ec-127e-4661-a647-1ae96db7612c":{"id":"695932ec-127e-4661-a647-1ae96db7612c","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6813,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"832878c8-9d48-48eb-ab8e-88f53d3aa19c":{"id":"832878c8-9d48-48eb-ab8e-88f53d3aa19c","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6814,"content":"Avalanche","contentHash":"40515202399d262e23ee7fca28b5d73627d96f30bb61c6d064100070976e4fa9","addressRefs":[]},"93bda922-82d8-4d77-a4a2-c62583fc697f":{"id":"93bda922-82d8-4d77-a4a2-c62583fc697f","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6815,"content":"Curve USDS/USDC","contentHash":"f3ed3508a5899a574c9b3daa6a58d85b3ef336362ec578c38e3173b8e5cfd3b0","addressRefs":[]},"bb93289c-ef4a-4305-8f9b-d791186be836":{"id":"bb93289c-ef4a-4305-8f9b-d791186be836","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6816,"content":"USDS and USDC","contentHash":"6810e4cb977ae32d70836efc8dcf991af5f59e944498b31e0a591aee8b2f8666","addressRefs":[]},"681fba5c-0e27-4bbc-ba2a-6d8fec26aab1":{"id":"681fba5c-0e27-4bbc-ba2a-6d8fec26aab1","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6817,"content":"USDSUSDC","contentHash":"5322c2b22c0fb8015ebbdea806ae2d01017a54a2c50e08152ba72003a7aed830","addressRefs":[]},"8c668b50-96e3-44fc-9cf4-9b445b614608":{"id":"8c668b50-96e3-44fc-9cf4-9b445b614608","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6818,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"80d06fa8-f274-4cb2-a10c-d9899dd64687":{"id":"80d06fa8-f274-4cb2-a10c-d9899dd64687","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.2.1","title":"Underlying Asset Address (USDS)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6819,"content":"`0x86Ff09db814ac346a7C6FE2Cd648F27706D1D470`","contentHash":"67f85d5b2b063e9651060d8e8c0c8df29fcf305d804070b205e04123b538270f","addressRefs":["0x86ff09db814ac346a7c6fe2cd648f27706d1d470"]},"22c5c59d-0353-4b6e-95eb-eaa0a589b8d9":{"id":"22c5c59d-0353-4b6e-95eb-eaa0a589b8d9","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.2.2","title":"Underlying Asset Address (USDC)","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6820,"content":"`0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E`","contentHash":"974d33f0ae152877034995c7f4480ca851dd613133d1a0abf5a2436c9029fc59","addressRefs":["0xb97ef9ef8734c71904d8002f8b6bc66dd9c48a6e"]},"ce06313e-0cf1-4c24-9770-edf1aca08f3c":{"id":"ce06313e-0cf1-4c24-9770-edf1aca08f3c","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.2.3","title":"Pool Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6821,"content":"`0xA9d7d3D7e68a0cae89FB33c736199172f405C8D3`","contentHash":"03341edd3ff88d213d05294ba4818f16b55bffa5afc7682c8ae9beb9438f9434","addressRefs":["0xa9d7d3d7e68a0cae89fb33c736199172f405c8d3"]},"18189c82-4fa4-4013-8002-2e76aa8f29af":{"id":"18189c82-4fa4-4013-8002-2e76aa8f29af","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6822,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"cef889e791f2b83bcbb0a9c31a4ac27908ed8e42d81e0663f3596e7e35abb973","addressRefs":[]},"3c77c07a-6092-4a43-b26a-2a975cfaa6d1":{"id":"3c77c07a-6092-4a43-b26a-2a975cfaa6d1","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6823,"content":"The inflow RateLimitID is: `0xeff5bd77b02bef14ff90eb3c87a6ab879b3b894eed4fd904ab94e425137e9a36`","contentHash":"820827d3b93d8a7f33648b4c855cd50c318d9f77f2adba884cff032d57f072b4","addressRefs":[]},"0181c16f-79e5-4054-8d31-874674efb80e":{"id":"0181c16f-79e5-4054-8d31-874674efb80e","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6824,"content":"The outflow RateLimitID is: `0x3361a251fa0f068ec6ce72e830c34ff0f5839a56c13e17e4c569c7c9d75217cf`","contentHash":"4f3358d7c38125ce9cfbe450fb37a130ff0b659ae7c4805b250729654848ee44","addressRefs":[]},"196540fd-72be-4d7c-8c2c-ae7f48426034":{"id":"196540fd-72be-4d7c-8c2c-ae7f48426034","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6825,"content":"The current `maxAmount` and `slope` for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"e5eb411abadf20155e59acad4f3c0696c2b44cb3c8b38090d09489ca7a118f52","addressRefs":[]},"2bc7c072-65e9-4b06-821c-3cc378758de1":{"id":"2bc7c072-65e9-4b06-821c-3cc378758de1","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6826,"content":"The deposit rate limits are:\n\n- `maxAmount`: 50,000,000 USDS/USDC\n- `slope`: 50,000,000 USDS/USDC per day","contentHash":"ae6fa22a33bb46edbff82fd8f77d37d0573e639d56ebece6a60ef892de8eb6ad","addressRefs":[]},"7e5dd377-9028-4fa0-950f-d65f3364911a":{"id":"7e5dd377-9028-4fa0-950f-d65f3364911a","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6827,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"12c90f28-75d6-4560-987a-6428e8ec5a47":{"id":"12c90f28-75d6-4560-987a-6428e8ec5a47","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6828,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"6fe4c2f1-102e-4b71-b829-edff00a8be14":{"id":"6fe4c2f1-102e-4b71-b829-edff00a8be14","doc_no":"A.6.1.1.2.2.6.1.3.2.2.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6829,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"14c653d1-6667-47c3-bea4-8bb8553bf7b9":{"id":"14c653d1-6667-47c3-bea4-8bb8553bf7b9","doc_no":"A.6.1.1.2.2.6.1.3.3","title":"Base","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6830,"content":"The Base Instances of the Grove Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"2563b72f1a543749ae2ee1329b1c1f67c2f617aa868e0a4d0a61d3c0023dc971","addressRefs":[]},"469f2edf-0a5b-4d3a-a32f-e93c0a99b04b":{"id":"469f2edf-0a5b-4d3a-a32f-e93c0a99b04b","doc_no":"A.6.1.1.2.2.6.1.3.3.1","title":"Morpho","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6831,"content":"The Base Instances of the Morpho Protocol with `Active` Status are stored herein.","contentHash":"b1bfd808dca3f55aa7bc2b45a8e6f9ed3e46bc502232f81fc9d1f4ffb1dd19d6","addressRefs":[]},"43d78089-ba75-480c-a277-edaa6eaa6336":{"id":"43d78089-ba75-480c-a277-edaa6eaa6336","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1","title":"Base - Morpho Grove x Steakhouse High Yield Vault USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6832,"content":"The documents herein contain the Instance Configuration Document for the Morpho Grove x Steakhouse High Yield Vault USDC Instance.","contentHash":"ad0f4ed5721864ff8569bc626c4e60c46859735c9388743e7afcce605511c9af","addressRefs":[]},"766f35b4-24a6-4393-9a3f-c511a1bce0cc":{"id":"766f35b4-24a6-4393-9a3f-c511a1bce0cc","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6833,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"b72d1498-2f89-40ec-8c14-08ce2a84af8c":{"id":"b72d1498-2f89-40ec-8c14-08ce2a84af8c","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6834,"content":"The documents herein define the parameters of the Morpho Grove x Steakhouse High Yield Vault USDC Instance of the Allocation System Primitive.","contentHash":"ff111421aa0cbdbf8a0489b19c327b7c8a1c045e900024a1dfeeec34d4787c52","addressRefs":[]},"89b9b814-e433-4b20-bdb0-3c8189501f5f":{"id":"89b9b814-e433-4b20-bdb0-3c8189501f5f","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6835,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"9b88ee71-1097-431f-8fbe-a5be36ef6128":{"id":"9b88ee71-1097-431f-8fbe-a5be36ef6128","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6836,"content":"Base","contentHash":"e5d5b6ffa6b5cd344e1d730f7910baa54b4ff67ba489d0f65414f99744fad304","addressRefs":[]},"4e1857f5-a3c8-408d-96c1-913fd81c3848":{"id":"4e1857f5-a3c8-408d-96c1-913fd81c3848","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6837,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"b08511eb-0c49-4077-9676-da153fbf2797":{"id":"b08511eb-0c49-4077-9676-da153fbf2797","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6838,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"6ff4aa1b-d139-44af-baae-b8c10220b107":{"id":"6ff4aa1b-d139-44af-baae-b8c10220b107","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6839,"content":"grove-bbqUSDC","contentHash":"3e56f375e1c8f3648d19469a73803751085410f59898449d39136725ab91e31b","addressRefs":[]},"99a5b0c0-88a8-4f3a-9bf3-b87b6f0fdf39":{"id":"99a5b0c0-88a8-4f3a-9bf3-b87b6f0fdf39","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6840,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"1dc90986-481b-4e3a-a38c-7a9a636bb1da":{"id":"1dc90986-481b-4e3a-a38c-7a9a636bb1da","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6841,"content":"`0xBeEf2d50B428675a1921bC6bBF4bfb9D8cF1461A`","contentHash":"9f842905b00cf7f0d72d46009f2438b15afffc21c8efb089a69363b0f9e51358","addressRefs":["0xbeef2d50b428675a1921bc6bbf4bfb9d8cf1461a"]},"200c6217-d44c-4a1e-90b3-94735e35959a":{"id":"200c6217-d44c-4a1e-90b3-94735e35959a","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6842,"content":"`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`","contentHash":"1514606ff71954880aebca40f0d22ff3f4870e8ed77ca8c8f709e6a83f57efd6","addressRefs":["0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"]},"f8e73145-23c5-48f6-b48b-62e4f7b8af0d":{"id":"f8e73145-23c5-48f6-b48b-62e4f7b8af0d","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6843,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"9e4275e9-c6b0-43a3-a5ff-1e12dc215267":{"id":"9e4275e9-c6b0-43a3-a5ff-1e12dc215267","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6844,"content":"The inflow RateLimitID is: `0xb5c3e377398c99e28d39340657bbc979bef79e01e2af3d0ff742e30722cd0d5a`.","contentHash":"257f010928f588a75262817147c7ec88714a2d844dbc9f6b424f2d014ecbf634","addressRefs":[]},"24179f21-d109-4298-b0c8-b0a182d94bce":{"id":"24179f21-d109-4298-b0c8-b0a182d94bce","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6845,"content":"The outflow RateLimitID is: `0x13e37cfd8b7a0e3f59d4b4424894c2a3693ccf0c313905615ae9848a32e2db97`.","contentHash":"cc5f0a8dce29c321450f93f90e5d0c7678ca163233c2b866fc7cad175d29d070","addressRefs":[]},"d394483b-e739-4346-948b-488fb942a48f":{"id":"d394483b-e739-4346-948b-488fb942a48f","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6846,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"a1c1cca8-b6a3-440b-ae26-9393b95d328f":{"id":"a1c1cca8-b6a3-440b-ae26-9393b95d328f","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6847,"content":"The inflow rate limits are:\n\n- `maxAmount`: 20,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"58b609bca8ccb81fc987b770e861060c0fde0350b2b88b24afc963e91550f73d","addressRefs":[]},"b39a0a7f-3e17-4cf3-b96b-a1a16fc8ae13":{"id":"b39a0a7f-3e17-4cf3-b96b-a1a16fc8ae13","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6848,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"9a9ad1a3-ce48-4947-9da1-13dfcd450ee3":{"id":"9a9ad1a3-ce48-4947-9da1-13dfcd450ee3","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6849,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"a274fcdf-dc71-4b78-be4d-e41d1622e076":{"id":"a274fcdf-dc71-4b78-be4d-e41d1622e076","doc_no":"A.6.1.1.2.2.6.1.3.3.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6850,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"d47ec9c3-b308-453a-989a-7396504f6a99":{"id":"d47ec9c3-b308-453a-989a-7396504f6a99","doc_no":"A.6.1.1.2.2.6.1.3.3.2","title":"Base - Steakhouse Prime Instant USDC Morpho Vault V2 Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6851,"content":"The documents herein contain the Instance Configuration Document for the Steakhouse Prime Instant USDC Morpho Vault V2 Instance.","contentHash":"06f13e508d4a5f55e9efae6fa8c888116bc6c5faca2207fcbad6a684ae77a46c","addressRefs":[]},"7bc64313-cdc1-4877-947e-df6c7c22a28e":{"id":"7bc64313-cdc1-4877-947e-df6c7c22a28e","doc_no":"A.6.1.1.2.2.6.1.3.3.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6852,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"8a19e28f-444a-4603-8905-0c6b1bfa9155":{"id":"8a19e28f-444a-4603-8905-0c6b1bfa9155","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6853,"content":"The documents herein define the parameters of the Steakhouse Prime Instant USDC Morpho Vault V2 Instance of the Allocation System Primitive.","contentHash":"609ffc980af7bcb2b157d82fc019d7e845290908b1c39ab88f96a74006537822","addressRefs":[]},"8f4a9995-4963-4d49-8694-725617a2c074":{"id":"8f4a9995-4963-4d49-8694-725617a2c074","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6854,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"1dae9d3c-8010-48d5-9ee4-620f72b345cd":{"id":"1dae9d3c-8010-48d5-9ee4-620f72b345cd","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6855,"content":"Base","contentHash":"e5d5b6ffa6b5cd344e1d730f7910baa54b4ff67ba489d0f65414f99744fad304","addressRefs":[]},"c9751457-f617-4bc3-bf8a-0fe0ac7d086f":{"id":"c9751457-f617-4bc3-bf8a-0fe0ac7d086f","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6856,"content":"Morpho","contentHash":"3cea47d33ac9b20e74bb3e51a29b39b3965757ec25b49becc29fc7c2b6484803","addressRefs":[]},"3acf8d38-4eae-4ceb-b482-4754d2aafad2":{"id":"3acf8d38-4eae-4ceb-b482-4754d2aafad2","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6857,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"fb07802c-ae95-4214-9762-db19fae2b671":{"id":"fb07802c-ae95-4214-9762-db19fae2b671","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6858,"content":"steakUSDC","contentHash":"e75b5dd885e83ae6d7492638aef57de643cd1b43bdf08a1c383a935601648d9d","addressRefs":[]},"9a607af8-7f0a-4686-98c2-f62afc557f51":{"id":"9a607af8-7f0a-4686-98c2-f62afc557f51","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6859,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"e85ae1d4-c31d-4eae-a05c-6a1844918cfd":{"id":"e85ae1d4-c31d-4eae-a05c-6a1844918cfd","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6860,"content":"`0xbeef0e0834849aCC03f0089F01f4F1Eeb06873C9`","contentHash":"1f79ed49847938076f356d7ccee2705f0f885bf545486522486465d06b74beab","addressRefs":["0xbeef0e0834849acc03f0089f01f4f1eeb06873c9"]},"889f7585-dcca-4e87-a9ca-bb1308115252":{"id":"889f7585-dcca-4e87-a9ca-bb1308115252","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6861,"content":"`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`","contentHash":"1514606ff71954880aebca40f0d22ff3f4870e8ed77ca8c8f709e6a83f57efd6","addressRefs":["0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"]},"a4d71080-74e8-48dd-ba3f-1810b4ba08c4":{"id":"a4d71080-74e8-48dd-ba3f-1810b4ba08c4","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6862,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"3269cc14-28bd-405e-8d72-dd22528573cf":{"id":"3269cc14-28bd-405e-8d72-dd22528573cf","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6863,"content":"The inflow RateLimitID is: `0xcc33156879fb03deee37b5ff243fa9afa95b94d13a2ab710f8096c0b5f053f3b`.","contentHash":"99b370f427b66614b5a37a5981a7dd6e35cb46d8b7ed7704029ad18e9221dabf","addressRefs":[]},"35e4b715-6409-490c-b42d-c1a24611d452":{"id":"35e4b715-6409-490c-b42d-c1a24611d452","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6864,"content":"The outflow RateLimitID is: `0x6cbf2a3469ddd029ba9744291f720dfed49b9d475ef870978c70f12ee6831646`.","contentHash":"9e901fbfc60abb97193436220c28df0413712a878aa595c82a94869225ffa986","addressRefs":[]},"881815fb-a206-4e1a-9852-c701d5ba4e92":{"id":"881815fb-a206-4e1a-9852-c701d5ba4e92","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6865,"content":"The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"b0283547fb2fbc64407617ade147a35e5946c9687033ec741bc775c4ce7d42cc","addressRefs":[]},"0ebb71f7-71c7-4668-9e70-1771e58cec79":{"id":"0ebb71f7-71c7-4668-9e70-1771e58cec79","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6866,"content":"The deposit rate limits are:\n\n- `maxAmount`: 20,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"ffdc79e6800e455c82d3ce02c5697652fcbe21fc1d3fa74a4f01206f02d8fcf1","addressRefs":[]},"bec9a1fa-aace-47eb-a663-08d1abd70b60":{"id":"bec9a1fa-aace-47eb-a663-08d1abd70b60","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6867,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"3b96571e-bd04-44dd-b729-3c59288d80b1":{"id":"3b96571e-bd04-44dd-b729-3c59288d80b1","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.4.3","title":"Max Exchange Rate","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6868,"content":"Controllers now have protections that require a `maxExchangeRate` to be set for deposits. The following ensures 1 share can represent at most 2 USDC.\n\n- `setMaxExchangeRate(STEAKHOUSE_PRIME_INSTANT_USDC_V2, 1e18, 2e6)`","contentHash":"158bb49530ce033e36e09246dc46a7d93fb88d741be9ec61f2c1c887130b419f","addressRefs":[]},"9418d9ac-66d4-41c7-80cc-b0de328ac09c":{"id":"9418d9ac-66d4-41c7-80cc-b0de328ac09c","doc_no":"A.6.1.1.2.2.6.1.3.3.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6869,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"aac6839f-b2a7-40f6-9fe3-c2366a0aa957":{"id":"aac6839f-b2a7-40f6-9fe3-c2366a0aa957","doc_no":"A.6.1.1.2.2.6.1.3.3.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6870,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"348787e7-de5d-465c-9e19-3e8740f04efc":{"id":"348787e7-de5d-465c-9e19-3e8740f04efc","doc_no":"A.6.1.1.2.2.6.1.3.4","title":"Plasma","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6871,"content":"The Plasma Instances of the Grove Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"bbd4dd311a4650cd12f0c045eb09d10c49c0e0c9cb9b497e685b09c6695a2e43","addressRefs":[]},"9587d7aa-8ac3-41d1-ba77-ee5a086a2706":{"id":"9587d7aa-8ac3-41d1-ba77-ee5a086a2706","doc_no":"A.6.1.1.2.2.6.1.3.4.1","title":"Aave","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6872,"content":"The Plasma Instances of the Aave Protocol with `Active` Status are stored herein.","contentHash":"55a1b1c844a324e44f62ee9f37e1980948b746501742cb79e03d2a8ec680292e","addressRefs":[]},"7a620ce6-c67a-4c15-b7fb-c8b869a28a0f":{"id":"7a620ce6-c67a-4c15-b7fb-c8b869a28a0f","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1","title":"Plasma - Aave v3 USDT0 Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6873,"content":"The documents herein contain the Instance Configuration Document for the Aave v3 USDT0 Instance.","contentHash":"6674a2eeaf35966dc2de56d18360b5d91b8c2fc8b565839753b38b08fbc8396f","addressRefs":[]},"5e65df67-fa1e-414d-8f0c-7a9b99db4640":{"id":"5e65df67-fa1e-414d-8f0c-7a9b99db4640","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6874,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"d6f69e43-7f2a-4116-992c-526ef48c100e":{"id":"d6f69e43-7f2a-4116-992c-526ef48c100e","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6875,"content":"The documents herein define the parameters of the Aave v3 USDT0 Instance of the Allocation System Primitive.","contentHash":"b498898cf8b14e1d81bc76b880a3fa30bb6fee0ad93d0d719046058fa3d6f8c6","addressRefs":[]},"8b7a0db8-da51-43c2-8d0a-512a8d95e348":{"id":"8b7a0db8-da51-43c2-8d0a-512a8d95e348","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6876,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"2783ab68-e321-4635-886c-6cb3f84ee88f":{"id":"2783ab68-e321-4635-886c-6cb3f84ee88f","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6877,"content":"Plasma","contentHash":"303b32029c7f0a2560b1e12e8910bcbbff0d93a706a160bf7bf9353b13282b02","addressRefs":[]},"6ebe8640-bc0f-4637-a49f-645002785274":{"id":"6ebe8640-bc0f-4637-a49f-645002785274","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6878,"content":"Aave v3","contentHash":"e7fb5a3e345ddf7582b31a216a2788a7aeafe5559ff7d4171a1aed60ef9fa29a","addressRefs":[]},"c3aa0280-f998-4510-a1fd-45bb47c62f4b":{"id":"c3aa0280-f998-4510-a1fd-45bb47c62f4b","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6879,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"f8e5ff09-11a4-42da-b5f8-f3f2152be978":{"id":"f8e5ff09-11a4-42da-b5f8-f3f2152be978","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6880,"content":"USDT0","contentHash":"32a4ae46061b40764d549ec1f89eb897533301a709fe88dbda9d35f815b07cee","addressRefs":[]},"3c791810-2663-432b-9f8a-7276c721c3d2":{"id":"3c791810-2663-432b-9f8a-7276c721c3d2","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6881,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"c1b87980-9050-48ba-82ef-b5f65ba0840f":{"id":"c1b87980-9050-48ba-82ef-b5f65ba0840f","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6882,"content":"`0x5D72a9d9A9510Cd8cBdBA12aC62593A58930a948`","contentHash":"641c3b7d3744506d6035924461cf7007a606b7513b8f83e41eb02244ec7de314","addressRefs":["0x5d72a9d9a9510cd8cbdba12ac62593a58930a948"]},"bfacb6db-078c-49f1-9e68-0e8a1c9ddef8":{"id":"bfacb6db-078c-49f1-9e68-0e8a1c9ddef8","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6883,"content":"`0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD`","contentHash":"8195c922b1769ee1b8460bd64e16889418dd0c35e6df32993cf1d55c0cacf66f","addressRefs":["0x8292bb45bf1ee4d140127049757c2e0ff06317ed"]},"49ae5000-35bb-497f-a545-2369859b651a":{"id":"49ae5000-35bb-497f-a545-2369859b651a","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6884,"content":"The specific `RateLimitID`(s) for this conduit’s inflow and outflow are defined in the subdocuments herein.","contentHash":"6f613ff479dd31244b67dcc0250c1e1f3cdcfabf121c2d748dbb63642b010357","addressRefs":[]},"a54c1592-0be9-45f8-8a46-8dd2da0e0e24":{"id":"a54c1592-0be9-45f8-8a46-8dd2da0e0e24","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6885,"content":"The inflow RateLimitID is: `0xd97a9a164c3a3da9ba6f443e90f688c005720ace173ac2c6fbd10cc9c67a174e`.","contentHash":"b72fa75a3b06ce58156c1eb53351f9ba35bc8ba2d6474ddba3099c78b1284ccf","addressRefs":[]},"3895d9f5-bde8-4b8a-95f4-0fae627ee25e":{"id":"3895d9f5-bde8-4b8a-95f4-0fae627ee25e","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6886,"content":"The outflow RateLimitID is: `0xc170dc947a54b39bf03cfdfa8249447fdacf93d397502740f6703d80ed3d98e7`.","contentHash":"eeafd0faabe4ab8b3992b5efcab48a30ec612015ea54d7d086965fa6d24a90e5","addressRefs":[]},"9c8fc963-4a61-4157-a665-bd1ff47f0ae0":{"id":"9c8fc963-4a61-4157-a665-bd1ff47f0ae0","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6887,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the subdocuments herein.","contentHash":"5d7ed7b3cefae8358846bb5de10a3f2920f98a62fabd1cd198f2eae7b78f2b94","addressRefs":[]},"3035fcf7-9426-46a7-9223-3204d922ca14":{"id":"3035fcf7-9426-46a7-9223-3204d922ca14","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6888,"content":"The inflow rate limits are:\n\n- `maxAmount`: 20,000,000 USDT0\n- `slope`: 20,000,000 USDT0 per day","contentHash":"994cc6a7579d09ba98433609421ff6e6d74c15fb0d4e734c150358d318615a74","addressRefs":[]},"8eeb5709-8e90-44ed-a384-d99df2a89e85":{"id":"8eeb5709-8e90-44ed-a384-d99df2a89e85","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.4.2","title":"Outflow Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6889,"content":"The outflow rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"64ccfe5007290c0aedaa8944551319caae2c8f442212ef765c711035e1443fc0","addressRefs":[]},"dfc74dd9-8390-4428-96e4-9b09c1ce0955":{"id":"dfc74dd9-8390-4428-96e4-9b09c1ce0955","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6890,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"5ad3319c-8c5a-4ba3-8578-29ab5bd51830":{"id":"5ad3319c-8c5a-4ba3-8578-29ab5bd51830","doc_no":"A.6.1.1.2.2.6.1.3.4.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6891,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"0e282f82-8b41-4657-92c3-4939b112ec77":{"id":"0e282f82-8b41-4657-92c3-4939b112ec77","doc_no":"A.6.1.1.2.2.6.1.3.5","title":"Plume","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6892,"content":"The Plume Instances of the Grove Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"bc2c054b5efc23fd21bffffbde941c10d9051f65ad509a3afaca65a28ccf4a51","addressRefs":[]},"75f40bed-64ab-4240-b0fe-d38ba928e237":{"id":"75f40bed-64ab-4240-b0fe-d38ba928e237","doc_no":"A.6.1.1.2.2.6.1.3.5.1","title":"Centrifuge","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6893,"content":"The Plume Instances of the Centrifuge Protocol with `Active` Status are stored herein.","contentHash":"785e6c60c14d2002c2e91a3789732d261c5154331c2748ce2855b21bbe6150cc","addressRefs":[]},"a1a1fa83-6c86-49fe-9629-d5ce4b24ed8b":{"id":"a1a1fa83-6c86-49fe-9629-d5ce4b24ed8b","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1","title":"Plume - Centrifuge ACRDX Instance Configuration Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6894,"content":"The documents herein contain the Instance Configuration Document for the Centrifuge ACRDX Instance.","contentHash":"cebf2e4556f73712f15fc95b450654b7501cb7a2b2b0179e5a0c9cf9af38c20d","addressRefs":[]},"4392f549-4d6e-4b80-8618-29483d1b7c7e":{"id":"4392f549-4d6e-4b80-8618-29483d1b7c7e","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6895,"content":"`Pending`","contentHash":"2986effe9fae335e819f546d8f69212a5a1e8bd5f01a449e4e295a5dee70536f","addressRefs":[]},"415f9bbf-2f2d-439e-91e0-415b0e800555":{"id":"415f9bbf-2f2d-439e-91e0-415b0e800555","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6896,"content":"The documents herein define the parameters of the Centrifuge ACRDX Instance of the Allocation System Primitive.","contentHash":"8629f541cfc64a25f28bf720a721ae40fa774c2c185a92fadf441b28917ffc53","addressRefs":[]},"4a716487-e052-4f94-8515-b86a7800cbc9":{"id":"4a716487-e052-4f94-8515-b86a7800cbc9","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6897,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"8eb8159a-9148-4b56-a39b-57443c29f5fb":{"id":"8eb8159a-9148-4b56-a39b-57443c29f5fb","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6898,"content":"Plume","contentHash":"84e17f7633dcd9163eb8c9221543ab408c1c40b06bd901bd0cddc932e4b7f8e4","addressRefs":[]},"23d754de-f3fd-47f1-b5e9-6f4a78e7034d":{"id":"23d754de-f3fd-47f1-b5e9-6f4a78e7034d","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6899,"content":"Centrifuge ACRDX","contentHash":"c9a585a7ef99fbf427d1c8c597dbf5cb50d5a468c469e5ddf02899e9725a6476","addressRefs":[]},"ed660630-a95e-43d4-ac72-cfd514ec9067":{"id":"ed660630-a95e-43d4-ac72-cfd514ec9067","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.1.3","title":"Asset Supplied By Grove Liquidity Layer","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6900,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"9a69776f-e214-42aa-a249-1bc5835ff71a":{"id":"9a69776f-e214-42aa-a249-1bc5835ff71a","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6901,"content":"ACRDX","contentHash":"fcd923d00ef573039593aedb4cd2a4b39200665150cb21279b5c6de004a68870","addressRefs":[]},"170397f2-f92a-40c5-9560-8c5be6eaf9c0":{"id":"170397f2-f92a-40c5-9560-8c5be6eaf9c0","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6902,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"08beab86-27af-4c89-8d68-c8b1ad0c8476":{"id":"08beab86-27af-4c89-8d68-c8b1ad0c8476","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6903,"content":"`0x9477724Bb54AD5417de8Baff29e59DF3fB4DA74f`","contentHash":"093e4cc20577622cdd8634cac6d265c870e46cfb5ed47f1d4c5f86408c0629b5","addressRefs":["0x9477724bb54ad5417de8baff29e59df3fb4da74f"]},"e9d21b2c-cfec-4abd-a611-c7586d5acdb2":{"id":"e9d21b2c-cfec-4abd-a611-c7586d5acdb2","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6904,"content":"`0x222365EF19F7947e5484218551B56bb3965Aa7aF`","contentHash":"37924db09a3e69ac385bcd219b19c9141273689bb3e1d03da3f179a0363fc018","addressRefs":["0x222365ef19f7947e5484218551b56bb3965aa7af"]},"870debbb-51c3-4b1b-892e-aa434de29442":{"id":"870debbb-51c3-4b1b-892e-aa434de29442","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.3","title":"Rate Limit IDs","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6905,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are defined in the subdocuments herein.","contentHash":"cef889e791f2b83bcbb0a9c31a4ac27908ed8e42d81e0663f3596e7e35abb973","addressRefs":[]},"eb02a060-d1b3-4113-a484-8f497fbded01":{"id":"eb02a060-d1b3-4113-a484-8f497fbded01","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6906,"content":"The inflow RateLimitID is: `0xb8139d1c2486c30929b3cb3a487a3d9c3885f49cff1f07e9393262b15ef1158a`","contentHash":"e19a197fd695d9c66f275d7e370816c9cae3cd5e2b48797c2e2abecea415b77c","addressRefs":[]},"e0b46e30-c702-4c8c-a471-f0ece288a71b":{"id":"e0b46e30-c702-4c8c-a471-f0ece288a71b","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6907,"content":"The outflow RateLimitID is: `0x58aa7b39a6c9894ea4a4cd6868d014c718d09913cdf5d793e21509f0ccd32495`","contentHash":"924ba917d465f8290c692fc224ba089dfa6e2b1ea947ef766302dc86b8aeebce","addressRefs":[]},"b14eb131-1eea-423f-8ad2-71de61e00897":{"id":"b14eb131-1eea-423f-8ad2-71de61e00897","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6908,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the subdocuments herein.","contentHash":"8519af2b7b719a5266bf415940ae473b12d5daebb94bb70d9d8ea48a50866930","addressRefs":[]},"1a7f2fdf-1c26-4638-881d-02f5cc1ae1b5":{"id":"1a7f2fdf-1c26-4638-881d-02f5cc1ae1b5","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6909,"content":"The deposit rate limits are:\n\n- `maxAmount`: 20,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"ffdc79e6800e455c82d3ce02c5697652fcbe21fc1d3fa74a4f01206f02d8fcf1","addressRefs":[]},"7c1b8e7c-3004-4c98-a078-8ce0bbdf1141":{"id":"7c1b8e7c-3004-4c98-a078-8ce0bbdf1141","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6910,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"2b814864-8ffe-420e-a060-24224fccf1b9":{"id":"2b814864-8ffe-420e-a060-24224fccf1b9","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6911,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"efbb5106-cc25-4d93-9fa7-50f3b8f3ad29":{"id":"efbb5106-cc25-4d93-9fa7-50f3b8f3ad29","doc_no":"A.6.1.1.2.2.6.1.3.5.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6912,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes.","contentHash":"512a746f0b2dc72ca2184447107b1e6540b1b08cf4b8d533f7df9b68bc1a62a9","addressRefs":[]},"fd06fedd-819d-4e0a-a266-ecf5ede0343b":{"id":"fd06fedd-819d-4e0a-a266-ecf5ede0343b","doc_no":"A.6.1.1.2.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6913,"content":"The Instances of the Grove Liquidity Layer with `Completed` Status are stored herein.","contentHash":"e01f9de6dab31bab3d37fea3f6bb06131d1964d571cda80c23d752dbaa22deca","addressRefs":[]},"0bf496c2-5a2a-4ec3-8354-bc0dea0657c8":{"id":"0bf496c2-5a2a-4ec3-8354-bc0dea0657c8","doc_no":"A.6.1.1.2.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6914,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.6.1.3 - Active Instances](1f16c7b1-eddf-4106-85f7-3425bf67ef1e).","contentHash":"545395a0ecae453b8f753c60dfd031e1439c6756b8f67b6ae43ef39dad47e315","addressRefs":[]},"5c6804a0-df8c-4a47-82d4-cff1b44f680b":{"id":"5c6804a0-df8c-4a47-82d4-cff1b44f680b","doc_no":"A.6.1.1.2.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6915,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"309b93b22c1a0b9b33a1319a6b43e15aa267597c7485eac38de5daa3a4c8bcd1","addressRefs":[]},"6f06a403-ef8f-4623-ad1f-f136adf3a533":{"id":"6f06a403-ef8f-4623-ad1f-f136adf3a533","doc_no":"A.6.1.1.2.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6916,"content":"The documents herein organize all base information relevant to Grove’s usage of the Junior Risk Capital Rental Primitive.","contentHash":"f0582c8d2e6faf736bcc8367ce14b24669472d734d5ef70d47dd0b930b02308d","addressRefs":[]},"f6dac7a5-a35c-4ead-979a-b5dba1e89f0c":{"id":"f6dac7a5-a35c-4ead-979a-b5dba1e89f0c","doc_no":"A.6.1.1.2.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6917,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"75fef570-0632-4721-91c7-72b904dd7c78":{"id":"75fef570-0632-4721-91c7-72b904dd7c78","doc_no":"A.6.1.1.2.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6918,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"9b363d62-f785-48e8-bf4c-248262af6d9d":{"id":"9b363d62-f785-48e8-bf4c-248262af6d9d","doc_no":"A.6.1.1.2.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6919,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"5c973874-a0c1-4fa9-a5b5-3d5ae92ffe86":{"id":"5c973874-a0c1-4fa9-a5b5-3d5ae92ffe86","doc_no":"A.6.1.1.2.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6920,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.6.2.1.2 - Active Instances Directory](75fef570-0632-4721-91c7-72b904dd7c78), whereas failed Invocations are Archived in [A.6.1.1.2.2.6.2.1.5 - Hub Data Repository](b222a1c8-a369-45cb-8179-221c29179564).","contentHash":"c28727effaa9989299dfa8e0618eb4252faa9f77f016985e0fd65fc9c2d10be8","addressRefs":[]},"b222a1c8-a369-45cb-8179-221c29179564":{"id":"b222a1c8-a369-45cb-8179-221c29179564","doc_no":"A.6.1.1.2.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6921,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"b276c0f8-15f5-492b-b7b9-f3df603354c6":{"id":"b276c0f8-15f5-492b-b7b9-f3df603354c6","doc_no":"A.6.1.1.2.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6922,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"3d09f988-872e-46a4-871d-b176052fb3a7":{"id":"3d09f988-872e-46a4-871d-b176052fb3a7","doc_no":"A.6.1.1.2.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6923,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"5a3df9c1-35de-4fbc-8533-8fe93f111594":{"id":"5a3df9c1-35de-4fbc-8533-8fe93f111594","doc_no":"A.6.1.1.2.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6924,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"07287112-4dbb-4bfa-a73d-ea3f2845718e":{"id":"07287112-4dbb-4bfa-a73d-ea3f2845718e","doc_no":"A.6.1.1.2.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6925,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"3f553aac-54e2-40f5-8545-53a8065feaef":{"id":"3f553aac-54e2-40f5-8545-53a8065feaef","doc_no":"A.6.1.1.2.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6926,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"a08608f5-a6a7-43dc-ba2f-34c685af073a":{"id":"a08608f5-a6a7-43dc-ba2f-34c685af073a","doc_no":"A.6.1.1.2.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6927,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.6.2.2 - Active Instances](07287112-4dbb-4bfa-a73d-ea3f2845718e).","contentHash":"2092ac3916906ae61478b14d9548b14808332cd86179d436beb076797e03d92c","addressRefs":[]},"0ec0b58d-9332-49ba-bdf8-8e0201480d1d":{"id":"0ec0b58d-9332-49ba-bdf8-8e0201480d1d","doc_no":"A.6.1.1.2.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6928,"content":"The documents herein contain all data and specifications for Groves Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"bc45d47d2644e547ca7577e61ff78896dbe9d112e6f45c8c5e1ec46b2de79166","addressRefs":[]},"9ab7f0cb-ed9e-4fe5-9dfb-78b084563435":{"id":"9ab7f0cb-ed9e-4fe5-9dfb-78b084563435","doc_no":"A.6.1.1.2.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6929,"content":"The documents herein organize all base information relevant to Grove’s usage of the Asset Liability Management Rental Primitive.","contentHash":"6f9b191a786fb420addf945c2a97fe501ab44c81a3d0b461be05050136f64ec1","addressRefs":[]},"d57353cc-9987-44c3-8498-432704107e38":{"id":"d57353cc-9987-44c3-8498-432704107e38","doc_no":"A.6.1.1.2.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6930,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"c2d4d693-c42c-4607-a667-f081665b4a88":{"id":"c2d4d693-c42c-4607-a667-f081665b4a88","doc_no":"A.6.1.1.2.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6931,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"b6e794cb-06a3-4a97-897a-0da8b7592e6e":{"id":"b6e794cb-06a3-4a97-897a-0da8b7592e6e","doc_no":"A.6.1.1.2.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6932,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"07dd6a23-424a-4eda-b47c-92e84d46025c":{"id":"07dd6a23-424a-4eda-b47c-92e84d46025c","doc_no":"A.6.1.1.2.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6933,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.6.3.1.2 - Active Instances Directory](c2d4d693-c42c-4607-a667-f081665b4a88), whereas failed Invocations are Archived in [A.6.1.1.2.2.6.3.1.5 - Hub Data Repository](722a01cb-c72f-41eb-be97-0adb41096e33).","contentHash":"b4e9dd9f4b0e796cc13c8cf76a3d9a8d8268d8fa3b99eb7a8b5ca648c49abbbc","addressRefs":[]},"722a01cb-c72f-41eb-be97-0adb41096e33":{"id":"722a01cb-c72f-41eb-be97-0adb41096e33","doc_no":"A.6.1.1.2.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6934,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"22a8dc60-26f5-4a48-853d-ffab6f6275a3":{"id":"22a8dc60-26f5-4a48-853d-ffab6f6275a3","doc_no":"A.6.1.1.2.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6935,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"e64a0b04-1c8f-4092-bdb6-992876835617":{"id":"e64a0b04-1c8f-4092-bdb6-992876835617","doc_no":"A.6.1.1.2.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6936,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"898b5220-2c1e-4784-b241-21349c244930":{"id":"898b5220-2c1e-4784-b241-21349c244930","doc_no":"A.6.1.1.2.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6937,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"2b0e3614-6608-4a08-aced-531daf476b7d":{"id":"2b0e3614-6608-4a08-aced-531daf476b7d","doc_no":"A.6.1.1.2.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6938,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"95a17d1f-3aa5-4625-9eb3-f4dd8e391f79":{"id":"95a17d1f-3aa5-4625-9eb3-f4dd8e391f79","doc_no":"A.6.1.1.2.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6939,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"1051e006-9490-4eb5-b45c-bc644fec7ae0":{"id":"1051e006-9490-4eb5-b45c-bc644fec7ae0","doc_no":"A.6.1.1.2.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6940,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.6.3.2 - Active Instances](2b0e3614-6608-4a08-aced-531daf476b7d).","contentHash":"cd439036a0e45618ec3b93409f3abf586b37596508f67ae51759bcf444b2795f","addressRefs":[]},"a98aca77-3ecb-47f9-bb3c-dc80cecc7052":{"id":"a98aca77-3ecb-47f9-bb3c-dc80cecc7052","doc_no":"A.6.1.1.2.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6941,"content":"The documents herein implement the Core Governance Primitives for Grove. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"5d7de11288687ca8a42dec774207a9e81cbbd7bbf0f029c0ad261ad4e0d3f645","addressRefs":[]},"ae98d071-3e9e-4f8c-9573-f5d113596d15":{"id":"ae98d071-3e9e-4f8c-9573-f5d113596d15","doc_no":"A.6.1.1.2.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6942,"content":"The documents herein contain all data and specifications for Grove’s Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"e21707dab2b1ce7e1ec386e225ed01b983788b1fb307561fb64a1ba964f953a7","addressRefs":[]},"883eaf9b-ea56-4a24-ae1e-b207ca83c281":{"id":"883eaf9b-ea56-4a24-ae1e-b207ca83c281","doc_no":"A.6.1.1.2.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6943,"content":"The documents herein organize all base information relevant to Grove’s usage of the Core Governance Reward Primitive.","contentHash":"b8a329ebd7af9266316cdf9a95171936c5803d48de817e49953793b14c3e9f19","addressRefs":[]},"0ce2345e-7d51-4c14-8ce2-f1fc972a8f5b":{"id":"0ce2345e-7d51-4c14-8ce2-f1fc972a8f5b","doc_no":"A.6.1.1.2.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6944,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"d321600d-53e8-411e-b705-a7c6407e0343":{"id":"d321600d-53e8-411e-b705-a7c6407e0343","doc_no":"A.6.1.1.2.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6945,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"a2bdbb72-4b08-4a55-892c-be41750ffeb3":{"id":"a2bdbb72-4b08-4a55-892c-be41750ffeb3","doc_no":"A.6.1.1.2.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6946,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"ded59861-0c71-4466-b31f-c0e301f9deee":{"id":"ded59861-0c71-4466-b31f-c0e301f9deee","doc_no":"A.6.1.1.2.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6947,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.2.2.7.1.1.2 - Active Instances Directory](d321600d-53e8-411e-b705-a7c6407e0343), whereas failed Invocations are Archived in [A.6.1.1.2.2.7.1.1.5 - Hub Data Repository](b5892d1c-a837-468d-bedd-b92cc99a92cc).","contentHash":"0da1d9c6fb6ba39126051a90186f9e06215194bc7083b624c1badc6d3bf0a4c5","addressRefs":[]},"b5892d1c-a837-468d-bedd-b92cc99a92cc":{"id":"b5892d1c-a837-468d-bedd-b92cc99a92cc","doc_no":"A.6.1.1.2.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6948,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"bffe84e5-d5de-4ce7-bc4f-27e03ba26eb2":{"id":"bffe84e5-d5de-4ce7-bc4f-27e03ba26eb2","doc_no":"A.6.1.1.2.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6949,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"1263a14d-8a7f-4b66-8ec5-54600c9c6288":{"id":"1263a14d-8a7f-4b66-8ec5-54600c9c6288","doc_no":"A.6.1.1.2.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6950,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"0dd7d900-7ee6-428c-a637-0b072a3dd58d":{"id":"0dd7d900-7ee6-428c-a637-0b072a3dd58d","doc_no":"A.6.1.1.2.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6951,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"2e50776e-e2d8-4223-accb-67e72770e16e":{"id":"2e50776e-e2d8-4223-accb-67e72770e16e","doc_no":"A.6.1.1.2.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6952,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"869969a7-22d0-4f5a-8932-5b70fcf6b1b4":{"id":"869969a7-22d0-4f5a-8932-5b70fcf6b1b4","doc_no":"A.6.1.1.2.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6953,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"fff36d24-346a-4721-b11c-cb1a801d3dbc":{"id":"fff36d24-346a-4721-b11c-cb1a801d3dbc","doc_no":"A.6.1.1.2.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"6b9bbf5e-0a76-4082-a042-811d4c426e6e","order":6954,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.2.2.7.1.2 - Active Instances](2e50776e-e2d8-4223-accb-67e72770e16e).","contentHash":"b1ecd048b0914fe197f55937da5a7e8433737bb6d9a43f7c48a7e2f86476b55b","addressRefs":[]},"df257205-6b3a-4afc-bbfd-0a35c950bb87":{"id":"df257205-6b3a-4afc-bbfd-0a35c950bb87","doc_no":"A.6.1.1.2.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"727b0de6-095b-485e-bf9c-02108a364480","order":6955,"content":"The documents herein define Grove’s strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"cfc0fdbedf1365175ddef1b3d084434723eef8ba35168afc775c89ce121c031e","addressRefs":[]},"c1c86e47-a7db-4080-ab1f-99ed8e4892f7":{"id":"c1c86e47-a7db-4080-ab1f-99ed8e4892f7","doc_no":"A.6.1.1.2.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6956,"content":"The documents herein specify Grove governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Grove Artifact is specified in the Root Edit Primitive above at [A.6.1.1.2.2.2.2 - Root Edit Primitive](da862b9f-ca77-443a-ac56-5a287c50b4db).","contentHash":"7358c42bb140a81d0d205b664dc15f032a3ab0c1425d4b32f464bf119638bedb","addressRefs":[]},"2eaeb1d9-99ea-478d-9fba-d7410885b4e5":{"id":"2eaeb1d9-99ea-478d-9fba-d7410885b4e5","doc_no":"A.6.1.1.2.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6957,"content":"Grove uses the Sky Forum for governance-related discussion. Posts should use the \"Grove Prime\" category.","contentHash":"b1c144d2510979d6deaca1487272e680e9acf1f3a41dbf61d30bc48d41f3bd44","addressRefs":[]},"33bf516a-c9e1-4ee0-8a09-69b1f2bb5604":{"id":"33bf516a-c9e1-4ee0-8a09-69b1f2bb5604","doc_no":"A.6.1.1.2.3.1.2","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6958,"content":"The documents herein specify Grove’s emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Grove Artifact.","contentHash":"10085d3d91f9ed179f9e1161beb7663de1807f1ff788f5961367d24ba868afc4","addressRefs":[]},"98930f9c-13eb-433c-b485-2fb0e37d0029":{"id":"98930f9c-13eb-433c-b485-2fb0e37d0029","doc_no":"A.6.1.1.2.3.1.3","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6959,"content":"The documents herein specify Grove’s emergency response protocol in situations solely impacting Grove versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Grove Artifact.","contentHash":"176e0370e623ac4c0e79a6cf30918d6fc4d140e446f8a076f3027bd8893f1ed0","addressRefs":[]},"56fec44a-f8ca-4a03-a614-2c0eb0dde262":{"id":"56fec44a-f8ca-4a03-a614-2c0eb0dde262","doc_no":"A.6.1.1.2.3.2","title":"Strategic Intent","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6960,"content":"Grove will unlock the full potential of USDS by building an institutional-grade credit platform designed to facilitate credit creation and seamlessly move yield in and out of the onchain economy. Grove's priority is to make USDS more attractive through diversified stability fee streams, more efficient rates, and greater utility, with CLOs as the first step into accessing higher yielding investment-grade credit assets. To accomplish these goals, Grove will deploy a RWA Allocation Conduit focused on traditional credit opportunities, as well as crypto-native Conduits for Morpho and Curve.","contentHash":"5d6542b2f27b2538957d8c009467cf1725c72b5f3e6cdfb42200d716c96e42f0","addressRefs":[]},"2cd87922-d450-4cc2-bce5-81c26239a015":{"id":"2cd87922-d450-4cc2-bce5-81c26239a015","doc_no":"A.6.1.1.2.3.2.1","title":"Collateralized Loan Obligation Strategy","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6961,"content":"Grove will prioritize Collateralized Loan Obligations (CLOs) as the initial pathway to provide Sky ecosystem with rapid exposure to higher yielding investment-grade credit assets, establishing a scalable model for offchain credit with onchain governance.","contentHash":"1f50710ce8a5b4a9e0730e28a8c2627bfb54df7791583085ad18d844c711f9a2","addressRefs":[]},"0e6f2c26-31a2-4ce4-8ed3-2d235561e3d3":{"id":"0e6f2c26-31a2-4ce4-8ed3-2d235561e3d3","doc_no":"A.6.1.1.2.3.2.2","title":"RWA Conduit","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6962,"content":"Grove will begin with onboarding winners of the Grand Prix ([https://forum.skyeco.com/t/announcement-spark-tokenization-grand-prix-request-for-proposal/24631](https://forum.skyeco.com/t/announcement-spark-tokenization-grand-prix-request-for-proposal/24631)).","contentHash":"1c72ef59fb9b69a1c11e1efe4bebfdea827185ca417d7bb83cb792e6051ccbce","addressRefs":[]},"d89b9da2-caf7-423f-9305-efcd66df62d8":{"id":"d89b9da2-caf7-423f-9305-efcd66df62d8","doc_no":"A.6.1.1.2.3.2.3","title":"Institutional Credit Platform","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6963,"content":"Grove will build partnerships with leading financial institutions to scale credit opportunities. This will provide transparent insight into balance sheet allocations while delivering higher, more stable yields through diversified institutional-grade assets.","contentHash":"95c3c2f7cbe4c7212a76793a25162795a4f8ceef44e89d54dc0c89c2f0d58aa8","addressRefs":[]},"f1793c13-0022-4c27-a439-17ea98d2e1d1":{"id":"f1793c13-0022-4c27-a439-17ea98d2e1d1","doc_no":"A.6.1.1.2.3.2.4","title":"Crypto-Native Conduits","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6964,"content":"Grove will deploy Allocation Conduits for Morpho and Curve to capture high-yield, low-risk DeFi opportunities.","contentHash":"c27806bf32af75c74a3e73e49e9d4cd997422a188a3eab279a06525ee3fa9e1b","addressRefs":[]},"e834343d-e67a-4e8e-acde-34e0a85ea4cd":{"id":"e834343d-e67a-4e8e-acde-34e0a85ea4cd","doc_no":"A.6.1.1.2.3.2.4.1","title":"Morpho Allocation Conduit","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6965,"content":"Grove will allocate capital to low risk collateral to take advantage of opportunities for high rates in these markets.","contentHash":"3356a52754d7f3b43dc5f2fd4a300d04c324dede480f749ebdc2df20290fca09","addressRefs":[]},"9a76d9e7-b648-4a32-b097-1466902a4309":{"id":"9a76d9e7-b648-4a32-b097-1466902a4309","doc_no":"A.6.1.1.2.3.2.4.2","title":"Curve Allocation Conduit","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6966,"content":"Grove will partner with emerging stablecoins to deploy liquidity against fiat-backed stablecoins.","contentHash":"7054de131e12e53ab0fbb213f0211a6cd422cb8dc9afb986a7c28c07660ce7cb","addressRefs":[]},"e629ebcb-4588-4305-b6ef-9a568b35d554":{"id":"e629ebcb-4588-4305-b6ef-9a568b35d554","doc_no":"A.6.1.1.2.3.2.5","title":"Exploratory Allocation Opportunities","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6967,"content":"Grove will consider allocations to basis trades, Pendle PTs, and other delta-neutral crypto primitives.","contentHash":"0d9658c6911465db2174ee9a58f477db98eb748a96d20291b1fdb03e92ba3a6c","addressRefs":[]},"156c9c72-46c9-4668-81b6-7e524e7a4bac":{"id":"156c9c72-46c9-4668-81b6-7e524e7a4bac","doc_no":"A.6.1.1.2.3.3","title":"Projected Operational Roadmap","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6968,"content":"Grove’s phased plan to execute its strategy includes:\n\n1. Deploy infrastructure to enable initial allocation conduits;\n2. Establish manual reallocation processes; and\n3. Develop quantitative reallocation parameters and conditions to optimize and decentralize conduit management over time; and\n4. Develop transparent insights into the allocation of the balance sheet.","contentHash":"87b406fc4ebf937562c03e4e4bd63e6fef621d21199108d9b0c8922b52251eb8","addressRefs":[]},"55a72d83-1de3-401c-aef4-9bb330abb774":{"id":"55a72d83-1de3-401c-aef4-9bb330abb774","doc_no":"A.6.1.1.2.3.4","title":"Management Of Infrastructure Inherited From Sky Core","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6969,"content":"The documents herein specify Grove's strategy and operational processes for managing infrastructure inherited from Sky Core.","contentHash":"c427f6cde23ccae162426d5261b113cd79e35f9db65eb4af8c938f077d105b7a","addressRefs":[]},"631d1b05-9828-4b53-a8ab-80dccf549f05":{"id":"631d1b05-9828-4b53-a8ab-80dccf549f05","doc_no":"A.6.1.1.2.3.4.1","title":"Andromeda","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6970,"content":"Control of the Andromeda RWA Arranged Structure is currently being transitioned to Grove. Andromeda is the RWA Arranged Structure inherited from Sky Core that allocates capital into safe, short-term treasury strategies of less than one (1) year duration.","contentHash":"c7e02ce2084b54fc31c9882981d947735aae694f130d20846eecdbb12b34636b","addressRefs":[]},"73f483b4-f330-49a8-a6d8-59bccb985b5d":{"id":"73f483b4-f330-49a8-a6d8-59bccb985b5d","doc_no":"A.6.1.1.2.3.4.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6971,"content":"The parameters of Andromeda are defined in [A.3.3.2.7.2.1 - Andromeda](1b153f9f-7c70-4ae1-b76c-ef12f87532c6).","contentHash":"600307e30c3c6b02f4b7665bafa046098bddaf7450757fc3f87b93f30b3c67d2","addressRefs":[]},"62b93c99-8a06-4dad-a95e-96029cb5372a":{"id":"62b93c99-8a06-4dad-a95e-96029cb5372a","doc_no":"A.6.1.1.2.3.4.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6972,"content":"The documents herein define the process for the ongoing management of Andromeda. Future iterations of the Artifact will specify operational processes owned by Grove.","contentHash":"5f0ca9344465a8b014c21c86386fa64a4a76baad9dba732f45f9bb13df59a638","addressRefs":[]},"e16c9799-7be7-4482-a954-6b8fbf873fbb":{"id":"e16c9799-7be7-4482-a954-6b8fbf873fbb","doc_no":"A.6.1.1.2.3.4.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6973,"content":"The documents herein contain data relevant to Andromeda.","contentHash":"2c38fa6837f0936758efe51fcd46e45ea800d2220434b0929ddbc1cff74226f8","addressRefs":[]},"beb54246-6454-4716-a381-be605560cba5":{"id":"beb54246-6454-4716-a381-be605560cba5","doc_no":"A.6.1.1.2.3.4.2","title":"Lite Peg Stability Module","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6974,"content":"Control of the Lite PSM is currently being transitioned to Grove.","contentHash":"4300355c3cadbd6a7b97108525474f69db131bfb91845382d259aaf1fd81dbde","addressRefs":[]},"d83f190a-99d6-4f8c-8502-d3e7e917816d":{"id":"d83f190a-99d6-4f8c-8502-d3e7e917816d","doc_no":"A.6.1.1.2.3.4.2.1","title":"Parameters","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6975,"content":"The parameters of the Lite PSM are defined in the Sky Core Atlas.","contentHash":"f363a18216018af41535a3796c200099dd11a1efda33f31c48770cd7dc8718ee","addressRefs":[]},"b935a218-b921-41b3-aaac-3203c2ca3b84":{"id":"b935a218-b921-41b3-aaac-3203c2ca3b84","doc_no":"A.6.1.1.2.3.4.2.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6976,"content":"The transfer of ongoing management of the Lite PSM is specified in Ecosystem Accord 2, see [A.2.8.2.2 - Prime Program](aa3b8e65-0ded-48c2-9c40-812debf99f32).","contentHash":"840013fa98d1613387dbd31aee9856a0474dc935d82f8d5c9d081eea309b75a1","addressRefs":[]},"f22bc9ce-cd9c-4f20-957f-1591b50abad0":{"id":"f22bc9ce-cd9c-4f20-957f-1591b50abad0","doc_no":"A.6.1.1.2.3.4.2.2.1","title":"Parameter Modification","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6977,"content":"The Sky Core Facilitator currently owns the process for modifying the parameters of the Lite PSM, which process is defined in the Sky Core Atlas. This process is currently being transitioned over to Grove.","contentHash":"b061396f868ed22f5a2ac8caf5a73ed425d483bc7643bcbb417729ea0c420b05","addressRefs":[]},"165fc3f7-39cf-4f4e-ae94-6460263b8a71":{"id":"165fc3f7-39cf-4f4e-ae94-6460263b8a71","doc_no":"A.6.1.1.2.3.4.2.3","title":"Data Repository","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6978,"content":"The documents herein contain data relevant to the Lite PSM.","contentHash":"3875558f7dfd52ecb4ac0da6f47049a0ff4ba5c956a159a76a35593b6cbcfd56","addressRefs":[]},"8b3829dd-fb87-4b08-b1dc-224d7c993ee4":{"id":"8b3829dd-fb87-4b08-b1dc-224d7c993ee4","doc_no":"A.6.1.1.2.3.5","title":"Ecosystem Accords","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6979,"content":"Grove has formally agreed to the Ecosystem Accords herein.","contentHash":"bc591638f3bfa631fd8f652589b40123c95e3bc1097ee5423240799e9025974c","addressRefs":[]},"867b3512-2c21-41e2-81c2-3a442c441a14":{"id":"867b3512-2c21-41e2-81c2-3a442c441a14","doc_no":"A.6.1.1.2.3.5.1","title":"Ecosystem Accord 1","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6980,"content":"Grove engaged in terms of agreement with the Spark Agent in Ecosystem Accord 1, located in [A.2.8.2.1 - Ecosystem Accord 1: Grove And Spark Agents](9ca40096-937e-431e-af50-9ecd50c0d0a8).","contentHash":"fc1a801229d44639222d382c3e51cb7acad7937717572a8eac421759d8f071e8","addressRefs":[]},"dfa20b2f-e803-47f7-95fa-4e457816ae69":{"id":"dfa20b2f-e803-47f7-95fa-4e457816ae69","doc_no":"A.6.1.1.2.3.5.2","title":"Ecosystem Accord 2","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6981,"content":"Grove engaged in terms of agreement with Sky, Moonbow and the Spark Agent in Ecosystem Accord 2, located in [A.2.8.2.2 - Prime Program](aa3b8e65-0ded-48c2-9c40-812debf99f32).","contentHash":"c875b7832b35bcb92ca227ebeffe04b5cfe10fed0f35c48b2184a9212c1ddb4d","addressRefs":[]},"e7057828-ca35-4c1f-8da9-05f54b73e25a":{"id":"e7057828-ca35-4c1f-8da9-05f54b73e25a","doc_no":"A.6.1.1.2.3.5.3","title":"Ecosystem Accord 10","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6982,"content":"Grove engaged in terms of agreement with Sky in Ecosystem Accord 10, located in [A.2.8.2.10 - Ecosystem Accord 10: Sky And Grove](0cb00b28-12a8-4790-974a-a3d98fd4dc97).","contentHash":"8cfd97cdb62cd92538af452efa5163723a8d4d56502fb7ed72de19a787ba3b39","addressRefs":[]},"c9c04069-134f-4ab3-b99c-e922edb1cde8":{"id":"c9c04069-134f-4ab3-b99c-e922edb1cde8","doc_no":"A.6.1.1.2.3.6","title":"DAO Resolutions","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6983,"content":"Grove has formally agreed to the DAO Resolutions recorded herein.","contentHash":"36c88cef0e3b6dc3e3af6c565f7abd1ab2ba5e1e1cf84f76d3f86dd1474b9f19","addressRefs":[]},"287ca9e6-e807-4565-a48d-83805be94b92":{"id":"287ca9e6-e807-4565-a48d-83805be94b92","doc_no":"A.6.1.1.2.3.6.1","title":"Onboard To FalconX","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6984,"content":"On October 16, 2025, Grove agreed to a DAO Resolution authorizing Grove Foundation and Bamboo Grove Ltd to onboard to FalconX. See [https://gateway.pinata.cloud/ipfs/bafkreialsthk4uhtxfd7zbhy4xiwnxxowd2qwpletjefrvdmvmpkxpkola](https://gateway.pinata.cloud/ipfs/bafkreialsthk4uhtxfd7zbhy4xiwnxxowd2qwpletjefrvdmvmpkxpkola).","contentHash":"351f2b4e8c9b35815fa39997089365163213a2b9e3d3bd851c4e2830ce440f50","addressRefs":[]},"9629b16e-4f11-49bc-80be-6c85d711716c":{"id":"9629b16e-4f11-49bc-80be-6c85d711716c","doc_no":"A.6.1.1.2.3.6.2","title":"Onboard With Ethena","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6985,"content":"On October 23, 2025, Grove agreed to a DAO Resolution authorizing Bamboo Grove to onboard with Ethena. See [https://ipfs.io/ipfs/bafkreic5vspzukckcgnx5ykwj2inqidvbfcknafa56jqgo25cveqyi565q](https://ipfs.io/ipfs/bafkreic5vspzukckcgnx5ykwj2inqidvbfcknafa56jqgo25cveqyi565q). The DAO Resolution makes reference to a Deed Poll that is approved as part of the DAO Resolution. See [https://ipfs.io/ipfs/bafkreibvyodjaosdfdzsrqjtuohwte46pol4zzmchky4t5xejaltonzi24](https://ipfs.io/ipfs/bafkreibvyodjaosdfdzsrqjtuohwte46pol4zzmchky4t5xejaltonzi24).","contentHash":"4194a8ff7016fc31b593a40fd18391a84d4d411c2d95409a05d3ec5720a026d3","addressRefs":[]},"1890a855-9e68-4705-a20c-085ee8b5f463":{"id":"1890a855-9e68-4705-a20c-085ee8b5f463","doc_no":"A.6.1.1.2.3.6.3","title":"Onboard With Ripple, Agora And Paxos","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6986,"content":"On November 20, 2025, a DAO Resolution was passed authorizing the Grove Foundation and Bamboo Grove Ltd to onboard with Ripple, Agora, and Paxos. See [https://gateway.pinata.cloud/ipfs/bafkreia77ngaxn54wy33v3dgzqr3cm4bykulrjldvf4iyahbfy2yv3jebi](https://gateway.pinata.cloud/ipfs/bafkreia77ngaxn54wy33v3dgzqr3cm4bykulrjldvf4iyahbfy2yv3jebi).","contentHash":"2c402adcdad013341f076278d9cd1c2d5df58b3733fe68df98595aeea80b3e17","addressRefs":[]},"d2409e5a-a85b-4a51-8f4d-46a437660154":{"id":"d2409e5a-a85b-4a51-8f4d-46a437660154","doc_no":"A.6.1.1.2.3.6.4","title":"Onboard With Wintermute","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6987,"content":"On November 27, 2025, a DAO Resolution was passed authorizing the Grove Foundation and Bamboo Grove Ltd to onboard with Wintermute. See [https://ipfs.io/ipfs/bafkreia72u565ub3iazmbsqsf4jzrobveckb2dtrcspmwn52oenyic72xu](https://ipfs.io/ipfs/bafkreia72u565ub3iazmbsqsf4jzrobveckb2dtrcspmwn52oenyic72xu).","contentHash":"a5a109c641eff6ec47e2d8753dd1d7c668ee0590215643afbb438cf7258bdfe9","addressRefs":[]},"062461fe-fc60-4f7c-ac28-2238756a67ea":{"id":"062461fe-fc60-4f7c-ac28-2238756a67ea","doc_no":"A.6.1.1.2.3.6.5","title":"Authorization With Respect To FalconX","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6988,"content":"On December 4, 2025, a DAO Resolution was passed authorizing the Grove Foundation and Bamboo Grove Ltd with respect to FalconX. See [https://ipfs.io/ipfs/bafkreicfhmyziwispejbngiqhfrqjy3xwvxidqnyaaaacprlp4n6gzvw7u](https://ipfs.io/ipfs/bafkreicfhmyziwispejbngiqhfrqjy3xwvxidqnyaaaacprlp4n6gzvw7u).","contentHash":"57364bc443a2d233bf8e47b45cb716d36bd6774df93eb7000594242200be9770","addressRefs":[]},"806e65a3-9322-4ab6-8dcb-ecdc4be13c18":{"id":"806e65a3-9322-4ab6-8dcb-ecdc4be13c18","doc_no":"A.6.1.1.2.3.6.6","title":"Authorization Of Project Grove","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6989,"content":"On December 11, 2025, a DAO Resolution was passed authorizing Grove Foundation and Grove (BVI) Ltd to take actions related to Project Grove. See [https://ipfs.io/ipfs/bafkreiamufzul447ja3prczy7cfxccvsij73vmareedlqag2xxpcwtcgxu](https://ipfs.io/ipfs/bafkreiamufzul447ja3prczy7cfxccvsij73vmareedlqag2xxpcwtcgxu).","contentHash":"1a9e8df6b2df3aa30c6c5845c3bf1f9c1a77ce9fb1c0ea052e0edcbdb7b75424","addressRefs":[]},"db2e4893-d315-4a65-a5cc-133d7763c693":{"id":"db2e4893-d315-4a65-a5cc-133d7763c693","doc_no":"A.6.1.1.2.3.6.7","title":"Authorization To Subscribe And Purchase Notes Issued By Galaxy CLO","type":"Core","depth":6,"parentId":"df257205-6b3a-4afc-bbfd-0a35c950bb87","order":6990,"content":"On December 11, 2025, a DAO Resolution was passed authorizing Grove Foundation and Cedar Grove Ltd to subscribe for and purchase the Class B notes issued by Galaxy CLO 2025-1 LLC. See [https://gateway.pinata.cloud/ipfs/bafkreierc3rxu3d64xakeeibkqujkqbhlz3lcsnjymcckaacix55vhya6u](ttps://gateway.pinata.cloud/ipfs/bafkreierc3rxu3d64xakeeibkqujkqbhlz3lcsnjymcckaacix55vhya6u).","contentHash":"ac4be3af5f894a51f56df8610fa75ff238a8ae22e8d919b116ac7f3511122bf0","addressRefs":[]},"bc6aed17-2969-4d04-9af6-c7bf3e4497e6":{"id":"bc6aed17-2969-4d04-9af6-c7bf3e4497e6","doc_no":"A.6.1.1.3","title":"Keel","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":6991,"content":"The documents herein specify all of the logic for Keel, including Keel’s strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"ee0130c074f0c7a3c97afe6a1221546622eb9c1a6d16a547eb48758de6192e99","addressRefs":[]},"9cbee6c7-8bc4-4b0c-a3cd-0f7f4944114e":{"id":"9cbee6c7-8bc4-4b0c-a3cd-0f7f4944114e","doc_no":"A.6.1.1.3.1","title":"Introduction","type":"Core","depth":5,"parentId":"bc6aed17-2969-4d04-9af6-c7bf3e4497e6","order":6992,"content":"Keel is an Agent dedicated to expanding access to USDS, sUSDS, and other Sky benefits with an initial focus on the Solana ecosystem. Keel leverages strategic incentives and partnerships to foster adoption, deliver the Sky Savings Rate, and bring USDS liquidity to new markets. Keel also identifies and executes allocation opportunities to generate excess returns on assets in Sky’s collateral portfolio. Keel plans to develop a user-facing DeFi hub as well as other products that align naturally with Keel’s existing capabilities, including borrowing and lending solutions.","contentHash":"8406a6e9ace4426e9633bb0284d02e52c23bec3b85a2e9d4ca356d1e17a3c80f","addressRefs":[]},"0d415ab8-7a66-4d82-98a4-67696a120650":{"id":"0d415ab8-7a66-4d82-98a4-67696a120650","doc_no":"A.6.1.1.3.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"bc6aed17-2969-4d04-9af6-c7bf3e4497e6","order":6993,"content":"The documents herein implement the Sky Primitives for Keel. See [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"7345a49e2f5d2978592be1eb6451e4ebcc390ff1d64089cce074ed250a61966a","addressRefs":[]},"80c991f4-7714-4706-95ab-50b0edd2f181":{"id":"80c991f4-7714-4706-95ab-50b0edd2f181","doc_no":"A.6.1.1.3.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":6994,"content":"The documents herein implement the Genesis Primitives for Keel. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"0eae84043fa2e8465a71fc363a8a4985583bf4c3efff671a69fee1c1ef9050e6","addressRefs":[]},"b439ba28-c334-4211-bdc7-bb3f62158e49":{"id":"b439ba28-c334-4211-bdc7-bb3f62158e49","doc_no":"A.6.1.1.3.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":6995,"content":"The documents herein contain all data and specifications for Keel’s Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"2cef4a5808cb947f05659e45fc8ca840f70094efe0820aa3a617c25bfbc570b7","addressRefs":[]},"b001c1e5-89c6-4141-bc59-b4e7b86d5f47":{"id":"b001c1e5-89c6-4141-bc59-b4e7b86d5f47","doc_no":"A.6.1.1.3.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":6996,"content":"The documents herein organize all base information relevant to Keel’s usage of the Agent Creation Primitive.","contentHash":"9ed772ce9b923fee80e0fb5b850ced9a5da9844c96e96c56cfaac85e59d4450b","addressRefs":[]},"c6ee2c59-96cd-464c-9c38-7b177739ab25":{"id":"c6ee2c59-96cd-464c-9c38-7b177739ab25","doc_no":"A.6.1.1.3.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":6997,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"d25c9d88-d80f-4692-a8c4-23d5773c4db4":{"id":"d25c9d88-d80f-4692-a8c4-23d5773c4db4","doc_no":"A.6.1.1.3.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":6998,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"4498f995-ee6c-47ee-9ab2-5c268b44cfd9":{"id":"4498f995-ee6c-47ee-9ab2-5c268b44cfd9","doc_no":"A.6.1.1.3.2.1.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":6999,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"91d4bf72-2fa7-4fdc-9e7b-f7960e1406a4":{"id":"91d4bf72-2fa7-4fdc-9e7b-f7960e1406a4","doc_no":"A.6.1.1.3.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7000,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.1.1.3.1 - Single Instance Configuration Document](66669635-acd1-4c2d-b75e-b9f05dfdf9bf).","contentHash":"72263a348e79ebbe9ed308206565d6169101aefe459d3f3998a958b8b64a8a69","addressRefs":[]},"5dc11d90-b6cb-4e32-8e37-ec7ce4afc470":{"id":"5dc11d90-b6cb-4e32-8e37-ec7ce4afc470","doc_no":"A.6.1.1.3.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7001,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"6b3495db-ce51-4042-ab8b-6cf288bf7e21":{"id":"6b3495db-ce51-4042-ab8b-6cf288bf7e21","doc_no":"A.6.1.1.3.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7002,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"d397b88b-ddde-4e66-b58b-c4168157a539":{"id":"d397b88b-ddde-4e66-b58b-c4168157a539","doc_no":"A.6.1.1.3.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7003,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"77479534-34de-4154-be5c-7b6f9fab8bd9":{"id":"77479534-34de-4154-be5c-7b6f9fab8bd9","doc_no":"A.6.1.1.3.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7004,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"a8c87f52-ad5a-43ad-a9e8-7b087193d8d4":{"id":"a8c87f52-ad5a-43ad-a9e8-7b087193d8d4","doc_no":"A.6.1.1.3.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7005,"content":"The subtrees for Instances of the Agent Creation Primitive with Suspended Status are stored here.","contentHash":"9d74d8318092fdddcd298b57e9de8af9fd8bc81c3b930a33d4680cf5cbf665a0","addressRefs":[]},"e67cd345-759d-4bd3-b264-a81971bf1921":{"id":"e67cd345-759d-4bd3-b264-a81971bf1921","doc_no":"A.6.1.1.3.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7006,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"0b9ec93a-58c8-48cf-b88f-ebbbc3a4333b":{"id":"0b9ec93a-58c8-48cf-b88f-ebbbc3a4333b","doc_no":"A.6.1.1.3.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7007,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"66669635-acd1-4c2d-b75e-b9f05dfdf9bf":{"id":"66669635-acd1-4c2d-b75e-b9f05dfdf9bf","doc_no":"A.6.1.1.3.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7008,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"baa172cb-2f8d-4606-b988-1280a665f53b":{"id":"baa172cb-2f8d-4606-b988-1280a665f53b","doc_no":"A.6.1.1.3.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7009,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"678770b0-a7fd-4b38-beee-f985504bc5b0":{"id":"678770b0-a7fd-4b38-beee-f985504bc5b0","doc_no":"A.6.1.1.3.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7010,"content":"The name of the Agent is Keel.","contentHash":"7e426205e843516de0fef544bbc4b4499b01c3380b8f514e22ddb257818e0fc5","addressRefs":[]},"2d5f052a-e32a-472c-884f-4fd8746e0459":{"id":"2d5f052a-e32a-472c-884f-4fd8746e0459","doc_no":"A.6.1.1.3.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7011,"content":"The address of Keel's SubProxy Account on the Ethereum Mainnet is `0x355CD90Ecb1b409Fdf8b64c4473C3B858dA2c310`.","contentHash":"9f9f409955b3cdf09adb9d823835708cbc5f1261b462fd62eae0c4ecfefdee75","addressRefs":["0x355cd90ecb1b409fdf8b64c4473c3b858da2c310"]},"79ef290b-94c8-420b-9e05-dbfa4156c5b4":{"id":"79ef290b-94c8-420b-9e05-dbfa4156c5b4","doc_no":"A.6.1.1.3.2.1.1.3.1.1.3","title":"Genesis Account","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7012,"content":"The address of Keel’s Genesis Account will be specified in a future iteration of the Keel Artifact.","contentHash":"79a417d65570a3bc3ad8258cf048fd61b3d5cb6133983fb51dbea5c2c96c2323","addressRefs":[]},"7cd2fee6-4606-41e1-8566-fc5d1442a2cd":{"id":"7cd2fee6-4606-41e1-8566-fc5d1442a2cd","doc_no":"A.6.1.1.3.2.1.1.3.1.1.4","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7013,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"ad622a38-8b5f-4dca-991c-8d0fb79c965c":{"id":"ad622a38-8b5f-4dca-991c-8d0fb79c965c","doc_no":"A.6.1.1.3.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7014,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"89b627cc-8223-4faa-bb56-370731f1ee9f":{"id":"89b627cc-8223-4faa-bb56-370731f1ee9f","doc_no":"A.6.1.1.3.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7015,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"9bacd440-487f-49f7-b0ca-fbd8367e9298":{"id":"9bacd440-487f-49f7-b0ca-fbd8367e9298","doc_no":"A.6.1.1.3.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7016,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"d8938b72-36af-4dce-91bc-4a8b67d20493":{"id":"d8938b72-36af-4dce-91bc-4a8b67d20493","doc_no":"A.6.1.1.3.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7017,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"f79736e7-1c24-43fe-9645-605791e87942":{"id":"f79736e7-1c24-43fe-9645-605791e87942","doc_no":"A.6.1.1.3.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7018,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"e46ba795-34db-4fb0-ba67-3dc178a4b47e":{"id":"e46ba795-34db-4fb0-ba67-3dc178a4b47e","doc_no":"A.6.1.1.3.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7019,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"564fff56-3cd6-4929-b6d6-f2ea53c7dd7f":{"id":"564fff56-3cd6-4929-b6d6-f2ea53c7dd7f","doc_no":"A.6.1.1.3.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7020,"content":"The documents herein contain all data and specifications for Keel’s Instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"541ded43b45546b584eb653b06d4994b857d87b226f273286631116256fa9da4","addressRefs":[]},"ddfade4a-7dba-49ad-8feb-c19dfb56e378":{"id":"ddfade4a-7dba-49ad-8feb-c19dfb56e378","doc_no":"A.6.1.1.3.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7021,"content":"The documents herein organize all base information relevant to Keel’s usage of the Prime Transformation Primitive.","contentHash":"e1ce2181a3bce38335f0a3dd6486d8f3bcf17988481f3f8175ac7ef7988efeab","addressRefs":[]},"ce33e597-a6e9-45e6-800a-f83af4bfb8b6":{"id":"ce33e597-a6e9-45e6-800a-f83af4bfb8b6","doc_no":"A.6.1.1.3.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7022,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"77c9f65c-b1f6-48fa-abd2-49bf900473d7":{"id":"77c9f65c-b1f6-48fa-abd2-49bf900473d7","doc_no":"A.6.1.1.3.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7023,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"70d3ad1c-6625-4c99-87ce-c1044bd8d459":{"id":"70d3ad1c-6625-4c99-87ce-c1044bd8d459","doc_no":"A.6.1.1.3.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7024,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"655dca13-6e80-4267-8555-303053aa6956":{"id":"655dca13-6e80-4267-8555-303053aa6956","doc_no":"A.6.1.1.3.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7025,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.1.2.3.1 - Single Instance Configuration Document](c664d698-17af-4635-9e13-c0393f416b2d).","contentHash":"811f30cfb357ff479ecfcd0daf177642194ab16914e6bfb659d2ea8dcfb56987","addressRefs":[]},"120e7afd-9bfd-4532-9ded-fca199e41517":{"id":"120e7afd-9bfd-4532-9ded-fca199e41517","doc_no":"A.6.1.1.3.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7026,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"bd76b4e7-543b-458f-bd8c-c6a8d687f28a":{"id":"bd76b4e7-543b-458f-bd8c-c6a8d687f28a","doc_no":"A.6.1.1.3.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7027,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"3036b076-251d-4434-b195-b1ed7923767c":{"id":"3036b076-251d-4434-b195-b1ed7923767c","doc_no":"A.6.1.1.3.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7028,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"6c4e4296-f5ad-446b-a15f-51dc081f99be":{"id":"6c4e4296-f5ad-446b-a15f-51dc081f99be","doc_no":"A.6.1.1.3.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7029,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"b270e04d-49ba-43a2-a2c6-dd2d9bd053bc":{"id":"b270e04d-49ba-43a2-a2c6-dd2d9bd053bc","doc_no":"A.6.1.1.3.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7030,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"cd02e662-ac90-474e-93cd-4366cec2aa65":{"id":"cd02e662-ac90-474e-93cd-4366cec2aa65","doc_no":"A.6.1.1.3.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7031,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"63bcf409-d7f5-4e5a-9e65-970df317653f":{"id":"63bcf409-d7f5-4e5a-9e65-970df317653f","doc_no":"A.6.1.1.3.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7032,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"c664d698-17af-4635-9e13-c0393f416b2d":{"id":"c664d698-17af-4635-9e13-c0393f416b2d","doc_no":"A.6.1.1.3.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7033,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"83b76fe8-a186-4be4-8a8b-2929c9a99ac4":{"id":"83b76fe8-a186-4be4-8a8b-2929c9a99ac4","doc_no":"A.6.1.1.3.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7034,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"84a5adbb-10cc-4bda-9e94-8facfdb114e6":{"id":"84a5adbb-10cc-4bda-9e94-8facfdb114e6","doc_no":"A.6.1.1.3.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7035,"content":"Keel is a Prime Agent.","contentHash":"f1ccc66c44cdb01fcfe7bef0cc771dcd26ff1f0cf54e116f0851fb7ceb7130ca","addressRefs":[]},"ec58c072-add1-442f-abab-c5eefb8b19d5":{"id":"ec58c072-add1-442f-abab-c5eefb8b19d5","doc_no":"A.6.1.1.3.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7036,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"8c8258a2-768f-4da1-b400-66ed0e25ac0a":{"id":"8c8258a2-768f-4da1-b400-66ed0e25ac0a","doc_no":"A.6.1.1.3.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7037,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"af920dd4-90f5-41fa-9547-049c35ed84e8":{"id":"af920dd4-90f5-41fa-9547-049c35ed84e8","doc_no":"A.6.1.1.3.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7038,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"10d9a22e-22ff-4f1c-8ce9-4b907b3748f5":{"id":"10d9a22e-22ff-4f1c-8ce9-4b907b3748f5","doc_no":"A.6.1.1.3.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7039,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"7ab8edc0-14e5-40e1-8bf6-80ef2eb86549":{"id":"7ab8edc0-14e5-40e1-8bf6-80ef2eb86549","doc_no":"A.6.1.1.3.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7040,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"795f3788-68ae-48c0-8fe3-c33b9bb81dc7":{"id":"795f3788-68ae-48c0-8fe3-c33b9bb81dc7","doc_no":"A.6.1.1.3.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7041,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"83b6ac05-69c2-43a5-b7f4-c24e02671c0d":{"id":"83b6ac05-69c2-43a5-b7f4-c24e02671c0d","doc_no":"A.6.1.1.3.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7042,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"56a1e9a7-9754-4354-952d-a6fb2605c7b4":{"id":"56a1e9a7-9754-4354-952d-a6fb2605c7b4","doc_no":"A.6.1.1.3.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7043,"content":"The documents herein contain all data and specifications for Keel’s Instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"0884895c5b795a21d22353811655942d9ad6e1831b5661435e6b47acc0d80a07","addressRefs":[]},"14e5e6ce-f8ba-4a83-a013-27c821cae118":{"id":"14e5e6ce-f8ba-4a83-a013-27c821cae118","doc_no":"A.6.1.1.3.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7044,"content":"The documents herein organize all base information relevant to Keel’s usage of the Executor Transformation Primitive.","contentHash":"ee1cb72d7dce701a4f724bdfb62555110da070799d0a5547c0619a80ed18263a","addressRefs":[]},"0608173d-703f-47a1-b66e-0fde1faee269":{"id":"0608173d-703f-47a1-b66e-0fde1faee269","doc_no":"A.6.1.1.3.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7045,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"3a99c1c6-03a5-4136-8195-0fe20ac0a637":{"id":"3a99c1c6-03a5-4136-8195-0fe20ac0a637","doc_no":"A.6.1.1.3.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7046,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"773eee8d-8581-4dec-a917-d7238f9d5480":{"id":"773eee8d-8581-4dec-a917-d7238f9d5480","doc_no":"A.6.1.1.3.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7047,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"f3844b2e-d070-493f-acbd-7bb582314ed3":{"id":"f3844b2e-d070-493f-acbd-7bb582314ed3","doc_no":"A.6.1.1.3.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7048,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"4860f54a-803e-4cfb-a7cd-8af5a159af0e":{"id":"4860f54a-803e-4cfb-a7cd-8af5a159af0e","doc_no":"A.6.1.1.3.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7049,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"4015cc5b-9843-44f6-805f-9938c47ea372":{"id":"4015cc5b-9843-44f6-805f-9938c47ea372","doc_no":"A.6.1.1.3.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7050,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"b8060ecb-32c7-4a12-a439-158e6fe636ab":{"id":"b8060ecb-32c7-4a12-a439-158e6fe636ab","doc_no":"A.6.1.1.3.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7051,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"21078bf0-ff3a-42a7-9219-acd7ca8ad35e":{"id":"21078bf0-ff3a-42a7-9219-acd7ca8ad35e","doc_no":"A.6.1.1.3.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7052,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"9611f413-a11b-4c5b-bdf5-4c861c52cb59":{"id":"9611f413-a11b-4c5b-bdf5-4c861c52cb59","doc_no":"A.6.1.1.3.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7053,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"073a2259-36d6-473a-910a-0e0a8122254d":{"id":"073a2259-36d6-473a-910a-0e0a8122254d","doc_no":"A.6.1.1.3.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7054,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"8b270217-b3fb-4a6f-84f5-65e1073781cd":{"id":"8b270217-b3fb-4a6f-84f5-65e1073781cd","doc_no":"A.6.1.1.3.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7055,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"7c41668c-38c2-401b-8905-51d66b3574ff":{"id":"7c41668c-38c2-401b-8905-51d66b3574ff","doc_no":"A.6.1.1.3.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7056,"content":"The documents herein contain all data and specifications for Keel’s Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"6f7cbaec48d5f8bf8078b939e90f02ddff56fa7fbaeff8fbc18d3ce163e8bd14","addressRefs":[]},"e3469208-9d4f-4862-a82f-16222cb7235e":{"id":"e3469208-9d4f-4862-a82f-16222cb7235e","doc_no":"A.6.1.1.3.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7057,"content":"The documents herein organize all base information relevant to Keel’s usage of the Agent Token Primitive.","contentHash":"3150a9fde76eb355aff2f05bf2977d17ac4d28867c4cc7a9de3404545b0c01cd","addressRefs":[]},"c3443c18-3cf1-4b02-8675-e1e404b06f37":{"id":"c3443c18-3cf1-4b02-8675-e1e404b06f37","doc_no":"A.6.1.1.3.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7058,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"982226bb-b1d0-436f-ab86-9edd0880eb7c":{"id":"982226bb-b1d0-436f-ab86-9edd0880eb7c","doc_no":"A.6.1.1.3.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7059,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"b6ae5829-82aa-43a4-96e1-15ede7b76c07":{"id":"b6ae5829-82aa-43a4-96e1-15ede7b76c07","doc_no":"A.6.1.1.3.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7060,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.1.4.2.1 - Single Instance Configuration Document](d212a592-0f0f-401b-b358-17cd453fcab2).","contentHash":"72a31b3617b9863c5c56306abebb522b8544dc72cb358c1e0461e760a3a30b23","addressRefs":[]},"fe0883fb-4758-44c9-8aa2-591e68f814b2":{"id":"fe0883fb-4758-44c9-8aa2-591e68f814b2","doc_no":"A.6.1.1.3.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7061,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"53fa54ce-8d6a-4cc4-901b-80f87540e4a9":{"id":"53fa54ce-8d6a-4cc4-901b-80f87540e4a9","doc_no":"A.6.1.1.3.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7062,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"1e00fec2-9ad0-48e7-aab2-e941e3cc1862":{"id":"1e00fec2-9ad0-48e7-aab2-e941e3cc1862","doc_no":"A.6.1.1.3.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7063,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"7cfb3a25-424d-415f-be14-b68a6c2e94a4":{"id":"7cfb3a25-424d-415f-be14-b68a6c2e94a4","doc_no":"A.6.1.1.3.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7064,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"376ffc51-a5ee-43cc-b993-d045ee5588a1":{"id":"376ffc51-a5ee-43cc-b993-d045ee5588a1","doc_no":"A.6.1.1.3.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7065,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"0a97b894-190f-433a-ae34-76236acdd144":{"id":"0a97b894-190f-433a-ae34-76236acdd144","doc_no":"A.6.1.1.3.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7066,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"26f17849-a6a4-46c2-b128-d4eefa67db5b":{"id":"26f17849-a6a4-46c2-b128-d4eefa67db5b","doc_no":"A.6.1.1.3.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7067,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"d212a592-0f0f-401b-b358-17cd453fcab2":{"id":"d212a592-0f0f-401b-b358-17cd453fcab2","doc_no":"A.6.1.1.3.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7068,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"a391467e-c3ad-4e80-b1ce-f6d041001cdc":{"id":"a391467e-c3ad-4e80-b1ce-f6d041001cdc","doc_no":"A.6.1.1.3.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7069,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"60029c9c-4fcd-4bbe-b918-9e7bcb5dfdbb":{"id":"60029c9c-4fcd-4bbe-b918-9e7bcb5dfdbb","doc_no":"A.6.1.1.3.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7070,"content":"The name of Keel’s token is Keel.","contentHash":"b0fa567c7ff6b9445a7263ea9b8b2edc5a88f1780d1ab35c3e3a82685470ecb8","addressRefs":[]},"41c58fff-ec4b-4bd1-bcb7-7bec6c9141b5":{"id":"41c58fff-ec4b-4bd1-bcb7-7bec6c9141b5","doc_no":"A.6.1.1.3.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7071,"content":"The symbol of Keel’s token is KEEL.","contentHash":"f837c167050a5f2ec0270043130fee3af4509376ddbca219a42d058377adfcdd","addressRefs":[]},"ffb7392d-e4ab-40fd-a886-104140ef3a64":{"id":"ffb7392d-e4ab-40fd-a886-104140ef3a64","doc_no":"A.6.1.1.3.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7072,"content":"The Genesis Supply of KEEL will be specified in a future iteration of the Keel Artifact.","contentHash":"b69357fb471912f18a29a3c62e35f55f9bd43e2bdb0bcd7b593090729a6a6d8b","addressRefs":[]},"c3a2a1c7-7e09-49f6-9789-8fb62412b9ad":{"id":"c3a2a1c7-7e09-49f6-9789-8fb62412b9ad","doc_no":"A.6.1.1.3.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7073,"content":"The address of KEEL will be specified in a future iteration of the Keel Artifact.","contentHash":"0644b754201b528f900bad893a88ae4b41c1e720f0f864a425599bcd9fecfa8d","addressRefs":[]},"603c0bd3-547b-46e5-b96c-ea9d48b06e48":{"id":"603c0bd3-547b-46e5-b96c-ea9d48b06e48","doc_no":"A.6.1.1.3.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7074,"content":"The token Admin will be specified in a future iteration of the Keel Artifact.","contentHash":"00c10ff2ea3833e8af3a4620fdde187c635432775e85cdbc456e474690e9890d","addressRefs":[]},"1ba562b8-3d43-46f8-bc21-5021dc7b9fed":{"id":"1ba562b8-3d43-46f8-bc21-5021dc7b9fed","doc_no":"A.6.1.1.3.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7075,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Keel Governance. Sky Governance retains the ability to revert where Keel is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"ea665e53c8a1ad33c85e8bf91589dc620ba565ace7a4703e95a177e7a86ee0bc","addressRefs":[]},"cccb3c25-8862-412a-bad3-69b535cbfe5d":{"id":"cccb3c25-8862-412a-bad3-69b535cbfe5d","doc_no":"A.6.1.1.3.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7076,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"1eaa59a7-4c50-4ace-ba78-956b8a4d9219":{"id":"1eaa59a7-4c50-4ace-ba78-956b8a4d9219","doc_no":"A.6.1.1.3.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7077,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.\n\n- These processes will be defined in a future iteration of the Keel Artifact.","contentHash":"5d3ded960ddcb3a55b95f10321c9f245c7127776de10c5f5926d96d51a51bb21","addressRefs":[]},"50d5319f-6c7f-4318-83a2-2bc2eb87a134":{"id":"50d5319f-6c7f-4318-83a2-2bc2eb87a134","doc_no":"A.6.1.1.3.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7078,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"79139c7c-5234-4a41-a6f7-0112216a4a9c":{"id":"79139c7c-5234-4a41-a6f7-0112216a4a9c","doc_no":"A.6.1.1.3.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7079,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"b49a061d-1a47-4841-91d8-753e82488288":{"id":"b49a061d-1a47-4841-91d8-753e82488288","doc_no":"A.6.1.1.3.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7080,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"ae670617-6780-426c-b2ef-2037d12f4669":{"id":"ae670617-6780-426c-b2ef-2037d12f4669","doc_no":"A.6.1.1.3.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7081,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"9494bb11-ec12-4029-89bd-40228e6ea9de":{"id":"9494bb11-ec12-4029-89bd-40228e6ea9de","doc_no":"A.6.1.1.3.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7082,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"7a08825e-c44f-456e-9301-7f701e53d213":{"id":"7a08825e-c44f-456e-9301-7f701e53d213","doc_no":"A.6.1.1.3.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7083,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"bbd36575-5a71-4b3e-aec2-564edb0f0303":{"id":"bbd36575-5a71-4b3e-aec2-564edb0f0303","doc_no":"A.6.1.1.3.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7084,"content":"The documents herein implement the Operational Primitives for Keel. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"dce00639477f486a228250cc7b25616420b99ab5a3bdac3e51ff035d4871953f","addressRefs":[]},"c75806c5-436f-4fd6-9367-e0bc9c5a3ee6":{"id":"c75806c5-436f-4fd6-9367-e0bc9c5a3ee6","doc_no":"A.6.1.1.3.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7085,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"f18f847379f85de244deedd58ee7c35656e76fda58f953b4447c16c069f8c190","addressRefs":[]},"51000f60-cf06-4f87-8e86-45573952645e":{"id":"51000f60-cf06-4f87-8e86-45573952645e","doc_no":"A.6.1.1.3.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7086,"content":"The documents herein organize all base information relevant to Keel’s usage of the Executor Accord Primitive.","contentHash":"1764947bda0433f33c179d3fc3824fd4b187f81864dbb746790b4f2411caa68d","addressRefs":[]},"4fe13ac1-d80f-468d-87c9-fd766a9f5934":{"id":"4fe13ac1-d80f-468d-87c9-fd766a9f5934","doc_no":"A.6.1.1.3.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7087,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"67640351-2db1-4252-a1cb-5c28aa02a56e":{"id":"67640351-2db1-4252-a1cb-5c28aa02a56e","doc_no":"A.6.1.1.3.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7088,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"680f4740-3ddb-49ee-a12b-0eaf44a6d04f":{"id":"680f4740-3ddb-49ee-a12b-0eaf44a6d04f","doc_no":"A.6.1.1.3.2.2.1.1.2.1","title":"Amatsu Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7089,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.2.1.2.1 - Amatsu Instance Configuration Document](4e46f093-0dea-4d7f-9b61-52815cc65803).","contentHash":"873bfbc310fbfc55a278298bdfb1c0cd16c5abc997b7ce73f6015cd935a1f2f1","addressRefs":[]},"16cd554f-daae-476c-8938-aacf1dba4be6":{"id":"16cd554f-daae-476c-8938-aacf1dba4be6","doc_no":"A.6.1.1.3.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7090,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"66568c73-c92f-4bac-8b7d-bd653782b39e":{"id":"66568c73-c92f-4bac-8b7d-bd653782b39e","doc_no":"A.6.1.1.3.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7091,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.2.1.2 - Active Instances](e1eb3283-ac9c-490e-bd36-850dd8bd71bd), whereas failed Invocations are Archived in [A.6.1.1.3.2.2.1.1.5 - Hub Data Repository](55586d0c-04d0-47dc-8ea1-3296a877f3e0).","contentHash":"61fa9307adf5ec743bb72fe9131e3a0f64e3061a3983d79c80eb15a8426e6071","addressRefs":[]},"55586d0c-04d0-47dc-8ea1-3296a877f3e0":{"id":"55586d0c-04d0-47dc-8ea1-3296a877f3e0","doc_no":"A.6.1.1.3.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7092,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e79d1a63-abb5-4f3e-a41f-7c1c1bff68bc":{"id":"e79d1a63-abb5-4f3e-a41f-7c1c1bff68bc","doc_no":"A.6.1.1.3.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7093,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"92a64b7d-cef8-4b8f-a5fc-beca030d6fb5":{"id":"92a64b7d-cef8-4b8f-a5fc-beca030d6fb5","doc_no":"A.6.1.1.3.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7094,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"a370a8e3-5df9-4d17-9275-e16e9d7f35f8":{"id":"a370a8e3-5df9-4d17-9275-e16e9d7f35f8","doc_no":"A.6.1.1.3.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7095,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"e1eb3283-ac9c-490e-bd36-850dd8bd71bd":{"id":"e1eb3283-ac9c-490e-bd36-850dd8bd71bd","doc_no":"A.6.1.1.3.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7096,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"4e46f093-0dea-4d7f-9b61-52815cc65803":{"id":"4e46f093-0dea-4d7f-9b61-52815cc65803","doc_no":"A.6.1.1.3.2.2.1.2.1","title":"Amatsu Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7097,"content":"The documents herein contain the Instance Configuration Document for the Amatsu Executor Accord Primitive Instance.","contentHash":"1c21c6e9bcc0a4917d31cb0e3687e2950886c0069d29ade1eaf0b26555b89dae","addressRefs":[]},"90a3d4c7-b094-4a1f-85f4-3165deef201f":{"id":"90a3d4c7-b094-4a1f-85f4-3165deef201f","doc_no":"A.6.1.1.3.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7098,"content":"The documents herein define the parameters of the Amatsu Instance of the Executor Accord Primitive.","contentHash":"4b845300c01bbf362ffc24169c2bf2ea87cf81f1f7ffe9edfdbf4d58ffe27828","addressRefs":[]},"ceb1e104-908d-451c-bc18-b1df694b1caf":{"id":"ceb1e104-908d-451c-bc18-b1df694b1caf","doc_no":"A.6.1.1.3.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7099,"content":"The Operational Facilitator and Operational GovOps for Amatsu are specified in [A.6.1.2.1 - Operational Executor Agent Amatsu](c57df14a-fde0-43f3-89ed-c2e4981d6bd5).","contentHash":"76d9fe55fd4705270171ce3e516634decfc626df9dfd732669b6336d1959d1fe","addressRefs":[]},"9b6b68f4-be11-4c3e-b426-909ac66a2467":{"id":"9b6b68f4-be11-4c3e-b426-909ac66a2467","doc_no":"A.6.1.1.3.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7100,"content":"The documents herein define the custom parameters of the Amatsu Instance of the Executor Accord Primitive, if any.","contentHash":"ad1cc46e684a82e8dbb992bc64497d98c2b32842daf0c18d9a1ea7a5e46c6686","addressRefs":[]},"9f515d3f-fef3-47ea-82c5-e553e2ef313e":{"id":"9f515d3f-fef3-47ea-82c5-e553e2ef313e","doc_no":"A.6.1.1.3.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7101,"content":"The documents herein define the process for the ongoing management of the Amatsu Instance of the Executor Accord Primitive.","contentHash":"66a5c505b65a5841595a3aa7d3e91ab5e833ac6f0bf82abcb7cbdd5062b75a6c","addressRefs":[]},"9ecf7a1f-9059-4d5b-a61e-8eb659064054":{"id":"9ecf7a1f-9059-4d5b-a61e-8eb659064054","doc_no":"A.6.1.1.3.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7102,"content":"The documents herein contain data relevant to the Amatsu Instance of the Executor Accord Primitive.","contentHash":"013ff159b352a95ad5edd2625d11e0b5f7e8d04a27f16c9d3de86248d6580acf","addressRefs":[]},"6f47f192-3277-4e40-89d9-73edee5f465c":{"id":"6f47f192-3277-4e40-89d9-73edee5f465c","doc_no":"A.6.1.1.3.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7103,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"969849ad-170b-4fad-972a-e37880e91b86":{"id":"969849ad-170b-4fad-972a-e37880e91b86","doc_no":"A.6.1.1.3.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7104,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"66ac9ca7-833a-457a-8d2b-e8c3fb968412":{"id":"66ac9ca7-833a-457a-8d2b-e8c3fb968412","doc_no":"A.6.1.1.3.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7105,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"ecc18c15-e6f8-4a6f-9a6a-04fa32e3541c":{"id":"ecc18c15-e6f8-4a6f-9a6a-04fa32e3541c","doc_no":"A.6.1.1.3.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7106,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"ef14c4d5-3862-49f7-be15-a1dac7581dc3":{"id":"ef14c4d5-3862-49f7-be15-a1dac7581dc3","doc_no":"A.6.1.1.3.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7107,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.2.1.2 - Active Instances](e1eb3283-ac9c-490e-bd36-850dd8bd71bd).","contentHash":"9b946a25c956cd143ad5288824354e9b4e79e19be32533372d29bf60f536970b","addressRefs":[]},"3d02dcbc-6a31-4f63-b464-c8c3ecebb744":{"id":"3d02dcbc-6a31-4f63-b464-c8c3ecebb744","doc_no":"A.6.1.1.3.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7108,"content":"The documents herein contain all data and specifications for Keel’s Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"f85e3408dd918f7ecdc30db63c7e3fae99c66675b97b14b26e0123ee98eeafd7","addressRefs":[]},"d32ff849-fe1d-4a99-ac1d-18e58eeca32f":{"id":"d32ff849-fe1d-4a99-ac1d-18e58eeca32f","doc_no":"A.6.1.1.3.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7109,"content":"The documents herein organize all base information relevant to Keel’s usage of the Root Edit Primitive.","contentHash":"3211a79a4cd36b8bd8c3a5a4acaac1f53752c72622d7b10d51f2f6dd4672814e","addressRefs":[]},"20f48216-ac88-48df-818f-45656c0f499c":{"id":"20f48216-ac88-48df-818f-45656c0f499c","doc_no":"A.6.1.1.3.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7110,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"396dc450-748d-4047-9a8e-790dd6663f32":{"id":"396dc450-748d-4047-9a8e-790dd6663f32","doc_no":"A.6.1.1.3.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7111,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"750a46d2-14ce-4509-8386-66703aebedca":{"id":"750a46d2-14ce-4509-8386-66703aebedca","doc_no":"A.6.1.1.3.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7112,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.2.2.2.1 - Single Instance Configuration Document](58822854-8549-427b-9548-48388ab3be4e).","contentHash":"b3a7862fd9ea36618761c4127d04912d7abb4e5fce985043ca24532cc5d801d6","addressRefs":[]},"268ed732-c908-4cdc-93b4-0682643a8b44":{"id":"268ed732-c908-4cdc-93b4-0682643a8b44","doc_no":"A.6.1.1.3.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7113,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"6e444033-afe3-4d6e-9a2f-29d9cc503135":{"id":"6e444033-afe3-4d6e-9a2f-29d9cc503135","doc_no":"A.6.1.1.3.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7114,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"23116311-532d-45f7-a8b1-874d959d26fa":{"id":"23116311-532d-45f7-a8b1-874d959d26fa","doc_no":"A.6.1.1.3.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7115,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e8e41a2a-da41-4ddc-b2bd-15e7ce3f2b77":{"id":"e8e41a2a-da41-4ddc-b2bd-15e7ce3f2b77","doc_no":"A.6.1.1.3.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7116,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"161f3a43-e825-4200-a798-e6364a718ad2":{"id":"161f3a43-e825-4200-a798-e6364a718ad2","doc_no":"A.6.1.1.3.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7117,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"bcbe25d7-b9d4-41ab-b913-d90336dd6863":{"id":"bcbe25d7-b9d4-41ab-b913-d90336dd6863","doc_no":"A.6.1.1.3.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7118,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"9ae94a26-915d-4a99-b469-c3cea7f3c6c8":{"id":"9ae94a26-915d-4a99-b469-c3cea7f3c6c8","doc_no":"A.6.1.1.3.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7119,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"58822854-8549-427b-9548-48388ab3be4e":{"id":"58822854-8549-427b-9548-48388ab3be4e","doc_no":"A.6.1.1.3.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7120,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"008ab1e2-e2e6-488e-a9e8-1a66b8d55f85":{"id":"008ab1e2-e2e6-488e-a9e8-1a66b8d55f85","doc_no":"A.6.1.1.3.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7121,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.3.2.2.2.2.1.2 - Operational Process Definition](53987e91-b86c-42be-bb4b-20af084d622d).","contentHash":"288610ae45deceeb6ffa392eecf1be8375de7e9a44dbbbe6a04ec5599d063e18","addressRefs":[]},"53987e91-b86c-42be-bb4b-20af084d622d":{"id":"53987e91-b86c-42be-bb4b-20af084d622d","doc_no":"A.6.1.1.3.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7122,"content":"The documents herein define the process for using the Root Edit Primitive to update the Keel Agent Artifact. Information on Keel governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.3.3.1 - Governance Information Unrelated To Root Edit Primitive](1889a2a0-7378-487a-a278-aabe3177efff).","contentHash":"4c0038bb75e9ddf0f6342dd6131b2b6079fb9f24beccd3d2a4978c1ec43bf6e8","addressRefs":[]},"eaba3101-2ef6-441d-853e-909a920140fa":{"id":"eaba3101-2ef6-441d-853e-909a920140fa","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7123,"content":"The documents herein define the process for using the Root Edit Primitive to update the Keel Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"dda7549d2173fa2000f0ab88ca5178e2b958c50b36b48fa1f64ce46062c980be","addressRefs":[]},"98f59541-8896-4e64-8e99-2b25e7791bf0":{"id":"98f59541-8896-4e64-8e99-2b25e7791bf0","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7124,"content":"The Root Edit process begins with a KEEL token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. A KEEL token holder must hold at least 1% of the circulating token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Keel Prime\" category.","contentHash":"aa53001d4d46e449c0af47246fed2becdfccba2a7ed1546659526a3d9b01f1b4","addressRefs":[]},"b3c428c6-d73f-4ed3-a876-dcc130e23ab4":{"id":"b3c428c6-d73f-4ed3-a876-dcc130e23ab4","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.1.1","title":"Root Edit Proposal Submission Requirements Exception","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7125,"content":"For proposals that solely entail a buyback or a grant of KEEL tokens, the requirement that KEEL token holders must hold at least 1% of the circulating token supply to submit a proposal is waived. However, all other procedural requirements within the Root Edit process continue to apply.","contentHash":"5d0df7387cac146e39e78b2a3ee1959d30bb54ea19ba2afefedaf006ee04acaf","addressRefs":[]},"d4c3c15b-7cdc-4c57-9bf0-53bbfd95e52c":{"id":"d4c3c15b-7cdc-4c57-9bf0-53bbfd95e52c","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.1.2","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7126,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, KEEL token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Keel Prime\" category. The title of the post must include the text \"Keel Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total KEEL token supply specified in [A.6.1.1.3.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](98f59541-8896-4e64-8e99-2b25e7791bf0).","contentHash":"1471d6c7f8335b2d47ea6b26a7744269753bba2b746e579717d5dd517d436495","addressRefs":[]},"b9858413-c2da-4e8f-9945-b03acb0b64f6":{"id":"b9858413-c2da-4e8f-9945-b03acb0b64f6","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7127,"content":"A future iteration of the Keel Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis.","contentHash":"be3f400f31873ee53b38f61008b68c44082d2859c2e4fadb87a74b4ebdcecc52","addressRefs":[]},"5caf90a5-60dc-4698-9ef7-70aba1c38efe":{"id":"5caf90a5-60dc-4698-9ef7-70aba1c38efe","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7128,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment.\n\nIf the proposal is aligned, the Operational Facilitator must respond to the Forum post to announce their finding. In this Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"3d695884c752507d7f445ad3a572c67b44863196d11108fb8a300dc2e71ce3e7","addressRefs":[]},"45218edd-29a1-44a3-af7b-7f048a7d04f6":{"id":"45218edd-29a1-44a3-af7b-7f048a7d04f6","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7129,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Keel Artifact, the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. The poll is open for three (3) days. A poll must have at least 10% of the circulating token supply participating and must have more than 50% of votes cast, excluding abstentions, in favor to be approved.","contentHash":"c1ec2fee9178eb616edb1359749d1171cbe0e9d44e505cf0c40ca531d24096e2","addressRefs":[]},"293c49b9-48f4-433c-820f-4915696f742f":{"id":"293c49b9-48f4-433c-820f-4915696f742f","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7130,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"d76d266f-50b3-4100-b198-c9d403ad50fd":{"id":"d76d266f-50b3-4100-b198-c9d403ad50fd","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.5.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7131,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"e86acb47-775f-4f02-8cef-26eac82dd358":{"id":"e86acb47-775f-4f02-8cef-26eac82dd358","doc_no":"A.6.1.1.3.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7132,"content":"The Keel Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"62c29fd996ab22f03d00296931ec76693c15687bab79f5de6fda75d46501966c","addressRefs":[]},"58df0ed3-38f4-489b-8e3b-762731f598b2":{"id":"58df0ed3-38f4-489b-8e3b-762731f598b2","doc_no":"A.6.1.1.3.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7133,"content":"The documents herein define the process for using the Root Edit Primitive to update the Keel Agent Artifact in non-routine conditions.","contentHash":"f54d5b8adc7a33a7effbf5c7f1a3d0fe64950e938b74a4b30b7ce45dc5380159","addressRefs":[]},"28ae6634-9099-4971-8175-31a5bcd0bedb":{"id":"28ae6634-9099-4971-8175-31a5bcd0bedb","doc_no":"A.6.1.1.3.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7134,"content":"The documents herein define the process for using the Root Edit Primitive to update the Keel Agent Artifact in urgent or emergency situations.","contentHash":"b210035903b24da7fd6c69ee9a25d2a2026d94ef8babd19f88e240ecd5c88f73","addressRefs":[]},"a7d50d59-36a3-4301-a1c7-6ac5da584d06":{"id":"a7d50d59-36a3-4301-a1c7-6ac5da584d06","doc_no":"A.6.1.1.3.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process in Urgent and Emergency Situations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7135,"content":"In an Urgent or Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Keel Prime\" category), unless doing so would endanger Keel or its users.","contentHash":"592f440b91c5a746dd7733fd0d08c8a4e4d5653b0d973d8cd1bb746fff920125","addressRefs":[]},"9f496f47-3f57-443c-ac5e-a44e08d4aa4c":{"id":"9f496f47-3f57-443c-ac5e-a44e08d4aa4c","doc_no":"A.6.1.1.3.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7136,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"2e6ea01e-ec36-4150-a096-6ba0143dc800":{"id":"2e6ea01e-ec36-4150-a096-6ba0143dc800","doc_no":"A.6.1.1.3.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7137,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"360ae2a4-679c-4ee5-829a-6d01f0713602":{"id":"360ae2a4-679c-4ee5-829a-6d01f0713602","doc_no":"A.6.1.1.3.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7138,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"79fe6be0-e7ce-4349-8c63-4579d2f17295":{"id":"79fe6be0-e7ce-4349-8c63-4579d2f17295","doc_no":"A.6.1.1.3.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7139,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"a5a2c272-8442-4caa-9423-5eb4e0c9a97d":{"id":"a5a2c272-8442-4caa-9423-5eb4e0c9a97d","doc_no":"A.6.1.1.3.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7140,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"d76c3889-78be-451a-9dbd-438b22ad4e63":{"id":"d76c3889-78be-451a-9dbd-438b22ad4e63","doc_no":"A.6.1.1.3.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7141,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"1c45537d-f720-4462-8cc8-675d08618c2a":{"id":"1c45537d-f720-4462-8cc8-675d08618c2a","doc_no":"A.6.1.1.3.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7142,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"04be013cdedb08b11268fc8a047268ccbb844b1b6f1f92bb0afb5b85b74af5e2","addressRefs":[]},"34688a2f-3a17-404a-b985-8ff8479c13f8":{"id":"34688a2f-3a17-404a-b985-8ff8479c13f8","doc_no":"A.6.1.1.3.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7143,"content":"The documents herein organize all base information relevant to Keel’s usage of the Light Agent Primitive.","contentHash":"b9461db53aabe2f8cf959de1f5bd4e1cc2b6d6e1f0585f050d1c5fcd0a5b8482","addressRefs":[]},"39b36112-08f2-470f-ba9d-d32c94f2d2f1":{"id":"39b36112-08f2-470f-ba9d-d32c94f2d2f1","doc_no":"A.6.1.1.3.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7144,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"e196d802-de22-410a-963a-c9d8359e9644":{"id":"e196d802-de22-410a-963a-c9d8359e9644","doc_no":"A.6.1.1.3.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7145,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"00433aa2-6d23-4a5e-8e2e-06177e41d097":{"id":"00433aa2-6d23-4a5e-8e2e-06177e41d097","doc_no":"A.6.1.1.3.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7146,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"0f0a7685-546c-486c-bb70-3a6e70464428":{"id":"0f0a7685-546c-486c-bb70-3a6e70464428","doc_no":"A.6.1.1.3.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7147,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.2.3.2 - Active Instances](7acfe8a6-80a2-4074-a6d0-fad968c95d1c), whereas failed Invocations are Archived in [A.6.1.1.3.2.2.3.1.5 - Hub Data Repository](e62355b7-d4e4-4c7f-b877-acdfa2d81f29).","contentHash":"afafb7c0dc3bad3d03a2743a2468ab29b6acedae4b18548dccee379e5f09d717","addressRefs":[]},"e62355b7-d4e4-4c7f-b877-acdfa2d81f29":{"id":"e62355b7-d4e4-4c7f-b877-acdfa2d81f29","doc_no":"A.6.1.1.3.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7148,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"d966a7e3-5ba0-4f69-ba60-d62ed5f05883":{"id":"d966a7e3-5ba0-4f69-ba60-d62ed5f05883","doc_no":"A.6.1.1.3.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7149,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"5abb2a17-1eb4-4db4-8272-d4bb81bded88":{"id":"5abb2a17-1eb4-4db4-8272-d4bb81bded88","doc_no":"A.6.1.1.3.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7150,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"81c7ec71-da63-465e-a0fb-56b8a9be44a8":{"id":"81c7ec71-da63-465e-a0fb-56b8a9be44a8","doc_no":"A.6.1.1.3.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7151,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"7acfe8a6-80a2-4074-a6d0-fad968c95d1c":{"id":"7acfe8a6-80a2-4074-a6d0-fad968c95d1c","doc_no":"A.6.1.1.3.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7152,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"1cf924ff-7eab-4d1d-8287-f8158925dc19":{"id":"1cf924ff-7eab-4d1d-8287-f8158925dc19","doc_no":"A.6.1.1.3.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7153,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"a039d046-24d2-4857-a59a-081143d10d61":{"id":"a039d046-24d2-4857-a59a-081143d10d61","doc_no":"A.6.1.1.3.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7154,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.2.3.2 - Active Instances](7acfe8a6-80a2-4074-a6d0-fad968c95d1c).","contentHash":"854a3ce303dbf859443ea68ff252f83987c0101c2a12811b55aa380cc28931fa","addressRefs":[]},"ae5cc5d4-a105-4f67-9e38-fd9b947c57a2":{"id":"ae5cc5d4-a105-4f67-9e38-fd9b947c57a2","doc_no":"A.6.1.1.3.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7155,"content":"The documents herein implement the Ecosystem Upkeep Primitives for Keel. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"6fb8434d25e241f2bb545c4ec390306319e39e48533488c0aa7abbaaab229d7b","addressRefs":[]},"0300c5b6-3f31-411f-b64c-707a35a55205":{"id":"0300c5b6-3f31-411f-b64c-707a35a55205","doc_no":"A.6.1.1.3.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7156,"content":"The documents herein contain all data and specifications for Keel’s Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"484067163eb443bc9161d4e8e50f61b6badaa0e5e38b79c89155b6f54a3a99a9","addressRefs":[]},"16c06503-ed5a-4dbc-aa30-9417ca0840ad":{"id":"16c06503-ed5a-4dbc-aa30-9417ca0840ad","doc_no":"A.6.1.1.3.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7157,"content":"The documents herein organize all base information relevant to Keel’s usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"87d31b7ab1f8c614f246f86c66a8f0718985211b3cf7e63952d1919de757dbbc","addressRefs":[]},"067c779a-34c6-4843-96b9-17f868f062de":{"id":"067c779a-34c6-4843-96b9-17f868f062de","doc_no":"A.6.1.1.3.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7158,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"52fa55fc-0d16-4ace-a6f4-6bee82057a55":{"id":"52fa55fc-0d16-4ace-a6f4-6bee82057a55","doc_no":"A.6.1.1.3.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7159,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"94da1bd6-eafb-46ed-831f-33a764ac5fda":{"id":"94da1bd6-eafb-46ed-831f-33a764ac5fda","doc_no":"A.6.1.1.3.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7160,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.3.1.2.1 - Single Instance Configuration Document](4037530e-66ee-4672-871f-601aef420e3f).","contentHash":"27ecb64e624da207bb5c2f1337985f2090eb1529e8ea5a3d81baeea7c5c99a6f","addressRefs":[]},"9b2d0fed-1be9-478a-8c07-ef80b891b8d4":{"id":"9b2d0fed-1be9-478a-8c07-ef80b891b8d4","doc_no":"A.6.1.1.3.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7161,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"689500ec-52c9-4b49-90df-7e75cbfb820b":{"id":"689500ec-52c9-4b49-90df-7e75cbfb820b","doc_no":"A.6.1.1.3.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7162,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"97827d06-62bb-460d-838c-30a9140cf520":{"id":"97827d06-62bb-460d-838c-30a9140cf520","doc_no":"A.6.1.1.3.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7163,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"8e6b7896-76da-470d-b3b0-c3ca34e3cd96":{"id":"8e6b7896-76da-470d-b3b0-c3ca34e3cd96","doc_no":"A.6.1.1.3.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7164,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"6e4c12a1-1318-4d56-80c0-f82a658b0416":{"id":"6e4c12a1-1318-4d56-80c0-f82a658b0416","doc_no":"A.6.1.1.3.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7165,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"2787b09c-d682-4386-9cf7-12a84b7744dc":{"id":"2787b09c-d682-4386-9cf7-12a84b7744dc","doc_no":"A.6.1.1.3.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7166,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"c75d2427-3bfe-4e20-b33f-799f4af8e4b6":{"id":"c75d2427-3bfe-4e20-b33f-799f4af8e4b6","doc_no":"A.6.1.1.3.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7167,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"4037530e-66ee-4672-871f-601aef420e3f":{"id":"4037530e-66ee-4672-871f-601aef420e3f","doc_no":"A.6.1.1.3.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7168,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"d7c2fe73-d620-4953-8f25-708a3cc53111":{"id":"d7c2fe73-d620-4953-8f25-708a3cc53111","doc_no":"A.6.1.1.3.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7169,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"3ef3d779-a66e-44f3-9192-6c3a5a5ca971":{"id":"3ef3d779-a66e-44f3-9192-6c3a5a5ca971","doc_no":"A.6.1.1.3.2.3.1.2.1.1.1","title":"Terms","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7170,"content":"Keel will pay 0.50% of its market capitalization per year in USDS.","contentHash":"fca1794cf56e76995c3e903b4ec4d55c23acc9d5809028a0afc40563212d5506","addressRefs":[]},"f9ff9c94-1a3d-4bc6-b2a4-40f9af76b0ac":{"id":"f9ff9c94-1a3d-4bc6-b2a4-40f9af76b0ac","doc_no":"A.6.1.1.3.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7171,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"0461ccfd-4791-459f-b79d-c1377c0eaea9":{"id":"0461ccfd-4791-459f-b79d-c1377c0eaea9","doc_no":"A.6.1.1.3.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7172,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"770597e2-1c0d-4084-878f-045f7b90933a":{"id":"770597e2-1c0d-4084-878f-045f7b90933a","doc_no":"A.6.1.1.3.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7173,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"f8f8cbf6-75e0-4dbb-b617-f44bc8cc9d8d":{"id":"f8f8cbf6-75e0-4dbb-b617-f44bc8cc9d8d","doc_no":"A.6.1.1.3.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7174,"content":"The process to pay 0.50% of Keel’s market capitalization per year in USDS will be specified in future iterations of the Keel Artifact.","contentHash":"e8bd58c454515ee3606d2b06106dcb2ee0a6d01bf9ff42b992572ba18ce75f4f","addressRefs":[]},"7080e7d9-2c7e-4cf8-ad5a-4e3bf65b6d10":{"id":"7080e7d9-2c7e-4cf8-ad5a-4e3bf65b6d10","doc_no":"A.6.1.1.3.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7175,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"de07d443-13f5-4d86-8eea-bb218ee2b8e7":{"id":"de07d443-13f5-4d86-8eea-bb218ee2b8e7","doc_no":"A.6.1.1.3.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7176,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"1b71dd32-0f52-4f13-89ca-97d64932cd56":{"id":"1b71dd32-0f52-4f13-89ca-97d64932cd56","doc_no":"A.6.1.1.3.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7177,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"ea840f1f-dda7-42c5-80fe-f774657831e3":{"id":"ea840f1f-dda7-42c5-80fe-f774657831e3","doc_no":"A.6.1.1.3.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7178,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"86e71f93-690a-478c-9c87-000c3572b4df":{"id":"86e71f93-690a-478c-9c87-000c3572b4df","doc_no":"A.6.1.1.3.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7179,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"27bd4d7c-d6bb-43e8-96ef-7471798fa071":{"id":"27bd4d7c-d6bb-43e8-96ef-7471798fa071","doc_no":"A.6.1.1.3.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7180,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"5cbe0c56-1105-4ce8-a16a-499b409fbf6c":{"id":"5cbe0c56-1105-4ce8-a16a-499b409fbf6c","doc_no":"A.6.1.1.3.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7181,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"ff19abdc-12c9-45cf-aa80-04ed0a7d71d4":{"id":"ff19abdc-12c9-45cf-aa80-04ed0a7d71d4","doc_no":"A.6.1.1.3.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7182,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"354f14b7-2263-45f6-8f27-9897b25d65df":{"id":"354f14b7-2263-45f6-8f27-9897b25d65df","doc_no":"A.6.1.1.3.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7183,"content":"The documents herein contain all data and specifications for Keel’s Instance of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"3d225418ed2a0a7271a54dfbb947660d37f5cba520327e1727bc5e0795e7d0cc","addressRefs":[]},"b8dba4a4-069a-466a-843c-61f676c3be7e":{"id":"b8dba4a4-069a-466a-843c-61f676c3be7e","doc_no":"A.6.1.1.3.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7184,"content":"The documents herein organize all base information relevant to Keel’s usage of the Upkeep Rebate Primitive.","contentHash":"5491e2e003b831aa25b4eed469fdf228fa8ae6df48fd27d6c6e35cda727b3f1b","addressRefs":[]},"f3c3f998-4abc-4c15-95bd-905a9dcf1897":{"id":"f3c3f998-4abc-4c15-95bd-905a9dcf1897","doc_no":"A.6.1.1.3.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7185,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"a439f8d8-dab3-4e55-8f6c-a218c069d65a":{"id":"a439f8d8-dab3-4e55-8f6c-a218c069d65a","doc_no":"A.6.1.1.3.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7186,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"55f5e89c-6629-49c4-8ada-6ab8befc0467":{"id":"55f5e89c-6629-49c4-8ada-6ab8befc0467","doc_no":"A.6.1.1.3.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7187,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.3.2.2.1 - Single Instance Configuration Document](b55f18e1-1a73-455f-8990-640273d8faa4).","contentHash":"94a73a37df59d97b84a2c4416d99cf3304843b3bdd9569d76f668a8e8ad20e3e","addressRefs":[]},"3293ffde-7260-42ec-9685-b06a58e821d9":{"id":"3293ffde-7260-42ec-9685-b06a58e821d9","doc_no":"A.6.1.1.3.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7188,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"e2022311-1bd9-4ec4-9bd9-ee901f455ac4":{"id":"e2022311-1bd9-4ec4-9bd9-ee901f455ac4","doc_no":"A.6.1.1.3.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7189,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"4df83f84-5ebf-4495-b044-9c8d760a0236":{"id":"4df83f84-5ebf-4495-b044-9c8d760a0236","doc_no":"A.6.1.1.3.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7190,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"16fc76ed-7b13-4fb7-9720-8d616c170f05":{"id":"16fc76ed-7b13-4fb7-9720-8d616c170f05","doc_no":"A.6.1.1.3.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7191,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"3ffb7952-1a5d-40fe-b0fe-289ca1e93bca":{"id":"3ffb7952-1a5d-40fe-b0fe-289ca1e93bca","doc_no":"A.6.1.1.3.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7192,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"f5f81875-29fd-4120-8210-32a545ab938e":{"id":"f5f81875-29fd-4120-8210-32a545ab938e","doc_no":"A.6.1.1.3.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7193,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"81a59fe8-9a9c-4cc9-ae8f-2d9d70f39196":{"id":"81a59fe8-9a9c-4cc9-ae8f-2d9d70f39196","doc_no":"A.6.1.1.3.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7194,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"b55f18e1-1a73-455f-8990-640273d8faa4":{"id":"b55f18e1-1a73-455f-8990-640273d8faa4","doc_no":"A.6.1.1.3.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7195,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"0e875626-6f3b-49ae-a47f-2a7471a1da14":{"id":"0e875626-6f3b-49ae-a47f-2a7471a1da14","doc_no":"A.6.1.1.3.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7196,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"120312e3-ee20-4dc4-bdc2-b3fdfda415e8":{"id":"120312e3-ee20-4dc4-bdc2-b3fdfda415e8","doc_no":"A.6.1.1.3.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7197,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"f9d8a156-1a7f-4c8a-bb1b-f19b8070aafc":{"id":"f9d8a156-1a7f-4c8a-bb1b-f19b8070aafc","doc_no":"A.6.1.1.3.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7198,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"06cd14d5-0f55-4ac0-8d9d-f9060e0fcc1b":{"id":"06cd14d5-0f55-4ac0-8d9d-f9060e0fcc1b","doc_no":"A.6.1.1.3.2.3.2.2.1.2.1.1","title":"Keel Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7199,"content":"Keel keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"1de3b0cc15bfa32a49ad109d9424c3c50af8c576923066a4fc21f7f9dc726325","addressRefs":[]},"20ccbfff-9058-47e5-a2d5-893d5bf783b6":{"id":"20ccbfff-9058-47e5-a2d5-893d5bf783b6","doc_no":"A.6.1.1.3.2.3.2.2.1.2.1.2","title":"Keel Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7200,"content":"When paying Ecosystem Upkeep fees, Keel deducts the rebate from the fees it pays.","contentHash":"ac552f7e29988a696b74efd48e51229f206d98d86add646f9a442c4f5da92b85","addressRefs":[]},"77ad2a49-8fa6-499b-bd26-b9fdef57fded":{"id":"77ad2a49-8fa6-499b-bd26-b9fdef57fded","doc_no":"A.6.1.1.3.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7201,"content":"Operational GovOps reviews Keel’s calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Keel Prime\" category and work with Keel to resolve the disagreement. If Operational GovOps and Keel cannot resolve the disagreement, it must be escalated to Core GovOps","contentHash":"99d2fc03b3c9e3d39d40cca3ba4e516ebd4bd460a28f427cd76a6e4ce3e3bf79","addressRefs":[]},"4fb94d9f-fc15-4823-bab7-fb35f1247bb7":{"id":"4fb94d9f-fc15-4823-bab7-fb35f1247bb7","doc_no":"A.6.1.1.3.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7202,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"86a386f4-db23-4c09-b165-a0ae6d3168c9":{"id":"86a386f4-db23-4c09-b165-a0ae6d3168c9","doc_no":"A.6.1.1.3.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7203,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"68cfcc8f-3c24-4d02-a25b-a4a93857d9ca":{"id":"68cfcc8f-3c24-4d02-a25b-a4a93857d9ca","doc_no":"A.6.1.1.3.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7204,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"725ad94b-e5d5-4aad-a205-5a4508c9fe79":{"id":"725ad94b-e5d5-4aad-a205-5a4508c9fe79","doc_no":"A.6.1.1.3.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7205,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0c0ef0b1-2d54-49f2-9ba6-c47fd5e56af1":{"id":"0c0ef0b1-2d54-49f2-9ba6-c47fd5e56af1","doc_no":"A.6.1.1.3.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7206,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"ca265d73-1cc0-43d3-806f-dd03219c5dec":{"id":"ca265d73-1cc0-43d3-806f-dd03219c5dec","doc_no":"A.6.1.1.3.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7207,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"92404db0-53f0-4042-8daa-2950f01807be":{"id":"92404db0-53f0-4042-8daa-2950f01807be","doc_no":"A.6.1.1.3.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7208,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"21b6e826-f126-4234-9baa-3a1e8a822e99":{"id":"21b6e826-f126-4234-9baa-3a1e8a822e99","doc_no":"A.6.1.1.3.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7209,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"c81714a3-e1c6-423a-bf54-6456fcb88112":{"id":"c81714a3-e1c6-423a-bf54-6456fcb88112","doc_no":"A.6.1.1.3.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7210,"content":"The documents herein implement the SkyLink Primitives for Keel. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"b1d32b3abae9aa52810125fbbbddc8cfbc3853237c57c3179f289b787602257a","addressRefs":[]},"016fd32e-a2db-45d0-8893-739bdacf1c2f":{"id":"016fd32e-a2db-45d0-8893-739bdacf1c2f","doc_no":"A.6.1.1.3.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7211,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"56bef9533d8cf7b537f1fbce599d8dd81710919b4249ababa5c2d1833e65ce92","addressRefs":[]},"b9c869ff-73ed-4b30-bc1a-33c6875524aa":{"id":"b9c869ff-73ed-4b30-bc1a-33c6875524aa","doc_no":"A.6.1.1.3.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7212,"content":"The documents herein organize all base information relevant to Keel’s usage of the Token SkyLink Primitive.","contentHash":"32b1c74f6ada8e1d21453d934566b5a2b126f009929c51e24cfc53487601d425","addressRefs":[]},"4dc84081-55f8-4ab0-aecf-f02c90bfb969":{"id":"4dc84081-55f8-4ab0-aecf-f02c90bfb969","doc_no":"A.6.1.1.3.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7213,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"9e793e15-c1b3-41e9-a9ea-5cdd034aa27f":{"id":"9e793e15-c1b3-41e9-a9ea-5cdd034aa27f","doc_no":"A.6.1.1.3.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7214,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"58fe24db-b9bd-48d3-bd6e-c4663788cf0d":{"id":"58fe24db-b9bd-48d3-bd6e-c4663788cf0d","doc_no":"A.6.1.1.3.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7215,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"e5f55c8d-f3f6-4f59-b49c-18b4085df50e":{"id":"e5f55c8d-f3f6-4f59-b49c-18b4085df50e","doc_no":"A.6.1.1.3.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7216,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.4.1.2 - Active Instances](38756877-b767-4a71-9f38-630a96b50f5a), whereas failed Invocations are Archived in [A.6.1.1.3.2.4.1.1.5 - Hub Data Repository](99d73511-9bec-4479-a451-8196ce3ea877).","contentHash":"270be2ac8f6ed105215a5734e345fe660c95568202e2ec43f1317e612835e712","addressRefs":[]},"99d73511-9bec-4479-a451-8196ce3ea877":{"id":"99d73511-9bec-4479-a451-8196ce3ea877","doc_no":"A.6.1.1.3.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7217,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"9721d168-d3fd-429f-bc94-79fab9315753":{"id":"9721d168-d3fd-429f-bc94-79fab9315753","doc_no":"A.6.1.1.3.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7218,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"6a3fa465-3dd8-4c94-bf6c-c7ff94ed5fd7":{"id":"6a3fa465-3dd8-4c94-bf6c-c7ff94ed5fd7","doc_no":"A.6.1.1.3.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7219,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"b8e84189-0ccd-4a83-b726-915bb519b11c":{"id":"b8e84189-0ccd-4a83-b726-915bb519b11c","doc_no":"A.6.1.1.3.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7220,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"38756877-b767-4a71-9f38-630a96b50f5a":{"id":"38756877-b767-4a71-9f38-630a96b50f5a","doc_no":"A.6.1.1.3.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7221,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"90dac12f-9fa3-45d2-b444-a644ca747d0a":{"id":"90dac12f-9fa3-45d2-b444-a644ca747d0a","doc_no":"A.6.1.1.3.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7222,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"b42701f2-b0d5-4901-a458-fe0042558c64":{"id":"b42701f2-b0d5-4901-a458-fe0042558c64","doc_no":"A.6.1.1.3.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7223,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.4.1.2 - Active Instances](38756877-b767-4a71-9f38-630a96b50f5a).","contentHash":"f29191fe73fa0362d83abe47f7437ed202fb9434e9921d9ce5ee0306b9850e6d","addressRefs":[]},"e72378f0-3ee3-452b-8af3-a7ef31f619fe":{"id":"e72378f0-3ee3-452b-8af3-a7ef31f619fe","doc_no":"A.6.1.1.3.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7224,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Keel. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"5fbe29a2ff81e7e083fd9f676e4ceccb4fc36c7351cf11417b034f7a79cb7a55","addressRefs":[]},"9ec308ad-b010-4f2d-ac33-eb56f1236493":{"id":"9ec308ad-b010-4f2d-ac33-eb56f1236493","doc_no":"A.6.1.1.3.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7225,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"58be5461746edfa4c094d514659ec36265b61c6b6812020527cc75921a008c74","addressRefs":[]},"b6b85415-c331-41b9-847e-4c5173528ca8":{"id":"b6b85415-c331-41b9-847e-4c5173528ca8","doc_no":"A.6.1.1.3.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7226,"content":"The documents herein organize all base information relevant to Keel’s usage of the Distribution Reward Primitive.","contentHash":"2e56c418ec05eda8c7f961a6311cf87ac97bda44139b581b063d09d55581058a","addressRefs":[]},"9e1fc932-ba41-43fb-a63f-c3011020669f":{"id":"9e1fc932-ba41-43fb-a63f-c3011020669f","doc_no":"A.6.1.1.3.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7227,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"cc24f926-2163-46e6-a480-8d6365911553":{"id":"cc24f926-2163-46e6-a480-8d6365911553","doc_no":"A.6.1.1.3.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7228,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"cf007f6d-17a1-40fd-be3e-663b815dc8fc":{"id":"cf007f6d-17a1-40fd-be3e-663b815dc8fc","doc_no":"A.6.1.1.3.2.5.1.1.2.1","title":"Solana Bridge Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7229,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.3.2.5.1.2.1 - Solana Bridge Instance Configuration Document](97421aa5-eebe-49e4-8da8-dd5cfe2f49c4).","contentHash":"5c648546c0478a1269b276ed5825ab6206fa354039870ece105b36a5242f31ed","addressRefs":[]},"60982fac-8d7e-4b13-b779-f257238dd4a5":{"id":"60982fac-8d7e-4b13-b779-f257238dd4a5","doc_no":"A.6.1.1.3.2.5.1.1.2.2","title":"1inch Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7230,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.3.2.5.1.2.2 - 1inch Instance Configuration Document](eca1c14e-b112-4905-92d2-9165075ea1d2).","contentHash":"a709da0116ea3efd6b73ab762022414e6a0cbfd41c598520011967f20d590b81","addressRefs":[]},"7e800a1b-d86b-43f7-a227-a7ba94d264ef":{"id":"7e800a1b-d86b-43f7-a227-a7ba94d264ef","doc_no":"A.6.1.1.3.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7231,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"63d5ec68-45da-4146-b672-6b7bae2e9c21":{"id":"63d5ec68-45da-4146-b672-6b7bae2e9c21","doc_no":"A.6.1.1.3.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7232,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.5.1.2 - Active Instances](4da74767-8e45-420c-9477-89b810654ab4), whereas failed Invocations are Archived in [A.6.1.1.3.2.5.1.1.5 - Hub Data Repository](4cc7dd10-6321-4c82-a504-a5021c79fe5f).","contentHash":"53c0e7d98debb56d699d04c453d4f578048b69fb8a249630e7edbd5444944e0a","addressRefs":[]},"4cc7dd10-6321-4c82-a504-a5021c79fe5f":{"id":"4cc7dd10-6321-4c82-a504-a5021c79fe5f","doc_no":"A.6.1.1.3.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7233,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"785e9f1a-fa79-416e-b71f-27604fc0f63d":{"id":"785e9f1a-fa79-416e-b71f-27604fc0f63d","doc_no":"A.6.1.1.3.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7234,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"c3c58b55-7d46-4dfe-927b-e571311f61c7":{"id":"c3c58b55-7d46-4dfe-927b-e571311f61c7","doc_no":"A.6.1.1.3.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7235,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"72e1da1a-4b11-4920-b28a-2b1a8d070e79":{"id":"72e1da1a-4b11-4920-b28a-2b1a8d070e79","doc_no":"A.6.1.1.3.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7236,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"4da74767-8e45-420c-9477-89b810654ab4":{"id":"4da74767-8e45-420c-9477-89b810654ab4","doc_no":"A.6.1.1.3.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7237,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"97421aa5-eebe-49e4-8da8-dd5cfe2f49c4":{"id":"97421aa5-eebe-49e4-8da8-dd5cfe2f49c4","doc_no":"A.6.1.1.3.2.5.1.2.1","title":"Solana Bridge Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7238,"content":"The documents herein contain the Instance Configuration Document for the Solana Bridge Distribution Reward Primitive Instance.","contentHash":"35fba391548499365293f9ccaed686754343269e60d2023a13b81a72f9d9e5aa","addressRefs":[]},"70bdfca7-9103-47a8-91eb-47c5eb727933":{"id":"70bdfca7-9103-47a8-91eb-47c5eb727933","doc_no":"A.6.1.1.3.2.5.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7239,"content":"The documents herein define the parameters of the Solana Bridge Instance of the Distribution Reward Primitive.","contentHash":"b1bfc09dfc067a87d6757b1cb5606db77199e140df1bba88f0cf351e011cb254","addressRefs":[]},"e5261fd0-16b6-4c94-a101-e311e858ba92":{"id":"e5261fd0-16b6-4c94-a101-e311e858ba92","doc_no":"A.6.1.1.3.2.5.1.2.1.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7240,"content":"`4001`.","contentHash":"e985ea57d989b23294239584eab0ddb4010d90c4f8c6b681f83f899bf6aefd10","addressRefs":[]},"78ced90e-697d-408e-b301-e22740d650dc":{"id":"78ced90e-697d-408e-b301-e22740d650dc","doc_no":"A.6.1.1.3.2.5.1.2.1.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7241,"content":"Synthetic tagging of deposits and withdrawals from the LayerZero contract on Ethereum (`0x1e1D42781FC170EF9da004Fb735f56F0276d01B8`) minus the running balances already attributed to a Distribution Reward Instance.","contentHash":"6c6141b4d6bcd6f7714cc3534b2f7d3902465a014b5efa8429ef2d2efebfff6e","addressRefs":["0x1e1d42781fc170ef9da004fb735f56f0276d01b8"]},"0cea78ce-be5f-46f5-8a48-a5d313b60611":{"id":"0cea78ce-be5f-46f5-8a48-a5d313b60611","doc_no":"A.6.1.1.3.2.5.1.2.1.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7242,"content":"The documents herein define the custom parameters of the Solana Bridge Instance of the Distribution Reward Primitive, if any.","contentHash":"10c4187243d04d62aafdd9a41ded5db8169d9b8a33ad5801c3c44261fc2cdb63","addressRefs":[]},"d79a21fb-1b29-4d8b-ab0c-1b3e654970c9":{"id":"d79a21fb-1b29-4d8b-ab0c-1b3e654970c9","doc_no":"A.6.1.1.3.2.5.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7243,"content":"The documents herein define the process for the ongoing management of the Solana Bridge Instance of the Distribution Reward Primitive.","contentHash":"5db4103afb748df2cc0534d24ea4d80c43dfcc0992d99a4285b98c54ae1e53be","addressRefs":[]},"70a1df13-bfee-43ad-9e5f-cbf4db36868b":{"id":"70a1df13-bfee-43ad-9e5f-cbf4db36868b","doc_no":"A.6.1.1.3.2.5.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7244,"content":"This document defines the protocol for routine ongoing management of the Solana Bridge Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Keel Artifact, a version of the full process definition customized to Keel will be included herein.","contentHash":"1470c8e13c7d4cd83d35f6d4d48f6131b93be58a683c0f6a11d34762b100da60","addressRefs":[]},"f08a63d5-4157-4be4-9046-59005bac03c2":{"id":"f08a63d5-4157-4be4-9046-59005bac03c2","doc_no":"A.6.1.1.3.2.5.1.2.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7245,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"ece7350a-4588-4c4e-8bdc-d21f539582f5":{"id":"ece7350a-4588-4c4e-8bdc-d21f539582f5","doc_no":"A.6.1.1.3.2.5.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7246,"content":"The documents herein define the protocol for non-routine ongoing management of the Solana Bridge Instance of this Distribution Reward Primitive.","contentHash":"75f3ff37d43d0f0029f5b45e373cc6195005f0423e536687092c210414e50f05","addressRefs":[]},"4bb2e7f5-e9b8-4d0f-84c4-faef129b06a2":{"id":"4bb2e7f5-e9b8-4d0f-84c4-faef129b06a2","doc_no":"A.6.1.1.3.2.5.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7247,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Solana Bridge Instance of this Distribution Reward Primitive.","contentHash":"5a2734fadaf1c6274821669823c6e1d238cbef01e748413ffbed91472c3184bd","addressRefs":[]},"73afe8a4-db40-4310-ac84-be565a062d68":{"id":"73afe8a4-db40-4310-ac84-be565a062d68","doc_no":"A.6.1.1.3.2.5.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7248,"content":"The documents herein contain data relevant to the Solana Bridge Instance of the Distribution Reward Primitive.","contentHash":"b6a0df63da37273644e4ddd3f83ca704eabf205e9178c056f594628e3a2c518c","addressRefs":[]},"764fdbd7-a8a6-4da5-bd3e-c6f5471afd91":{"id":"764fdbd7-a8a6-4da5-bd3e-c6f5471afd91","doc_no":"A.6.1.1.3.2.5.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7249,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"634e03bc-fc80-4b2c-9182-0b3ae4386f0e":{"id":"634e03bc-fc80-4b2c-9182-0b3ae4386f0e","doc_no":"A.6.1.1.3.2.5.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7250,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"a2eeb79e-bb70-4f25-a106-18bacd69b5ab":{"id":"a2eeb79e-bb70-4f25-a106-18bacd69b5ab","doc_no":"A.6.1.1.3.2.5.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7251,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"394771d8-fa9c-4f5c-8b73-b8f996cb77c1":{"id":"394771d8-fa9c-4f5c-8b73-b8f996cb77c1","doc_no":"A.6.1.1.3.2.5.1.2.1.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7252,"content":"The Distribution Reward payments for the Solana Bridge Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"4790c2d29262fb3352beed01b7c55533397bdf82287b05d50be3840e5433342a","addressRefs":[]},"1d0e0165-719b-4899-af1c-8a0366a058af":{"id":"1d0e0165-719b-4899-af1c-8a0366a058af","doc_no":"A.6.1.1.3.2.5.1.2.1.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7253,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"eca1c14e-b112-4905-92d2-9165075ea1d2":{"id":"eca1c14e-b112-4905-92d2-9165075ea1d2","doc_no":"A.6.1.1.3.2.5.1.2.2","title":"1inch Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7254,"content":"The documents herein contain the Instance Configuration Document for the 1inch Distribution Reward Primitive Instance.","contentHash":"e6ce5fb4c91b01b932904a71de58cb2313dbafd5416d84d865773c8787881592","addressRefs":[]},"4fcd06bc-72fd-4cce-83fd-5b1a7dda3a4a":{"id":"4fcd06bc-72fd-4cce-83fd-5b1a7dda3a4a","doc_no":"A.6.1.1.3.2.5.1.2.2.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7255,"content":"The documents herein define the parameters of the 1inch Instance of the Distribution Reward Primitive.","contentHash":"8e8e8421c5623efb1aafb303bb7195878d128482b94a58e8f00d8d2636969014","addressRefs":[]},"adbef757-5f85-43ef-84d3-7ca3d5300d7a":{"id":"adbef757-5f85-43ef-84d3-7ca3d5300d7a","doc_no":"A.6.1.1.3.2.5.1.2.2.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7256,"content":"`4011`.","contentHash":"f606332244602d6fb5f1a6838919858f70fc44027ce6b2fea7c95e6e65df79cd","addressRefs":[]},"3642deee-6b05-45a8-ae8f-949997406709":{"id":"3642deee-6b05-45a8-ae8f-949997406709","doc_no":"A.6.1.1.3.2.5.1.2.2.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7257,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"988cd4e4-908a-4b5d-aa3c-251666e32a6d":{"id":"988cd4e4-908a-4b5d-aa3c-251666e32a6d","doc_no":"A.6.1.1.3.2.5.1.2.2.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7258,"content":"The documents herein define the custom parameters of the 1inch Instance of the Distribution Reward Primitive, if any.","contentHash":"197ae201b636e8586cf47a861c067f8bb99a53c2b61b4c040d81eef734466aae","addressRefs":[]},"5634a0c6-dfa2-490d-b3b5-0735407e345a":{"id":"5634a0c6-dfa2-490d-b3b5-0735407e345a","doc_no":"A.6.1.1.3.2.5.1.2.2.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7259,"content":"The documents herein define the process for the ongoing management of the 1inch Instance of the Distribution Reward Primitive.","contentHash":"157252cdf4f4edc6a1c2db0827d908e4e92a9e2a50d18a9304c3325d2da04edd","addressRefs":[]},"147799a6-7bc3-45c1-8e15-f9d6377d3b52":{"id":"147799a6-7bc3-45c1-8e15-f9d6377d3b52","doc_no":"A.6.1.1.3.2.5.1.2.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7260,"content":"This document defines the protocol for routine ongoing management of the 1inch Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Keel Artifact, a version of the full process definition customized to Keel will be included herein.","contentHash":"ec67e14232c610a472a1693f1d840c0229184ee6a47b678f06ead7d1d0e58d51","addressRefs":[]},"d8159db3-8fd7-4706-aab8-eeba1a831da0":{"id":"d8159db3-8fd7-4706-aab8-eeba1a831da0","doc_no":"A.6.1.1.3.2.5.1.2.2.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7261,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"72c61c6a-ef20-4e71-a3a2-5cbdfc8fc42f":{"id":"72c61c6a-ef20-4e71-a3a2-5cbdfc8fc42f","doc_no":"A.6.1.1.3.2.5.1.2.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7262,"content":"The documents herein define the protocol for non-routine ongoing management of the 1inch Instance of this Distribution Reward Primitive.","contentHash":"8054420c5631e67628969a7ac7edfdd4cd638c17189005ffb11bba59029393e1","addressRefs":[]},"f543af9e-d7db-4a0b-93f7-0108f789e7d0":{"id":"f543af9e-d7db-4a0b-93f7-0108f789e7d0","doc_no":"A.6.1.1.3.2.5.1.2.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7263,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the 1inch Instance of this Distribution Reward Primitive.","contentHash":"36d79335a73798aa55cfadc2a5ce548f9fd0433d4daee649b83da2a49c09a957","addressRefs":[]},"343708ad-a3ea-4044-b56a-055d3ffc388e":{"id":"343708ad-a3ea-4044-b56a-055d3ffc388e","doc_no":"A.6.1.1.3.2.5.1.2.2.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7264,"content":"The documents herein contain data relevant to the 1inch Instance of the Distribution Reward Primitive.","contentHash":"a9b1c71eb62f7a10145b55e8a4b2b834c1cf72a685fe138986aa0a1ac25c0d7f","addressRefs":[]},"90352ea8-67ed-4148-8594-bb66826b2ad9":{"id":"90352ea8-67ed-4148-8594-bb66826b2ad9","doc_no":"A.6.1.1.3.2.5.1.2.2.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7265,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"1f8b494d-a550-4fb7-adff-8afe9301b006":{"id":"1f8b494d-a550-4fb7-adff-8afe9301b006","doc_no":"A.6.1.1.3.2.5.1.2.2.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7266,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"4da0eb19-7721-4249-994e-91c86695b785":{"id":"4da0eb19-7721-4249-994e-91c86695b785","doc_no":"A.6.1.1.3.2.5.1.2.2.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7267,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"55f35766-6eb6-4f4d-be40-ce70af3bed55":{"id":"55f35766-6eb6-4f4d-be40-ce70af3bed55","doc_no":"A.6.1.1.3.2.5.1.2.2.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7268,"content":"The Distribution Reward payments for the 1inch Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"03a821faa6d0951db74f74da7bf6030cf964729fb5dc193b923c2be6f4b6c7da","addressRefs":[]},"f7274663-4447-4ed3-9fb5-30c72e23802b":{"id":"f7274663-4447-4ed3-9fb5-30c72e23802b","doc_no":"A.6.1.1.3.2.5.1.2.2.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7269,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"15a011c4-a0bb-4fd4-bf9d-ff8b5ebc74a6":{"id":"15a011c4-a0bb-4fd4-bf9d-ff8b5ebc74a6","doc_no":"A.6.1.1.3.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7270,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"8aa73f62-1589-4f34-a14b-c95a4701eebc":{"id":"8aa73f62-1589-4f34-a14b-c95a4701eebc","doc_no":"A.6.1.1.3.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7271,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.5.1.2 - Active Instances](4da74767-8e45-420c-9477-89b810654ab4).","contentHash":"5dcb8f7b82b3de6a5c914af917d8d544c428c1c3df1317062bd3b82c41b123c3","addressRefs":[]},"6319e8b0-577c-4d08-92af-8332fde7e553":{"id":"6319e8b0-577c-4d08-92af-8332fde7e553","doc_no":"A.6.1.1.3.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7272,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"e2fa731c77eb8717ed8e0d304489b63a713b46e35613f6eab018a27a7802a1c3","addressRefs":[]},"18b58761-8afa-44e0-824d-32d4c85b429e":{"id":"18b58761-8afa-44e0-824d-32d4c85b429e","doc_no":"A.6.1.1.3.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7273,"content":"The documents herein organize all base information relevant to Keel’s usage of the Integration Boost Primitive.","contentHash":"c19ef110113d1f34fa44605e79ba446af7cddaedc752a445597e1f09ee6fd750","addressRefs":[]},"8a49aa6e-8451-4773-82b9-17c59d3a8931":{"id":"8a49aa6e-8451-4773-82b9-17c59d3a8931","doc_no":"A.6.1.1.3.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7274,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"bc7296ae-4bfb-4318-87fb-44869a7932c1":{"id":"bc7296ae-4bfb-4318-87fb-44869a7932c1","doc_no":"A.6.1.1.3.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7275,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"538f7325-dcab-49e9-a369-add9f5930586":{"id":"538f7325-dcab-49e9-a369-add9f5930586","doc_no":"A.6.1.1.3.2.5.2.1.2.1","title":"Kamino Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7276,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.5.2.2.1 - Kamino Instance Configuration Document](bff45812-80f3-4e46-9428-74a374bef2fc).","contentHash":"4b574d7959ab9ba60cc8330c7bcf75b4991ceb17b49beea4a516470377dd48be","addressRefs":[]},"40262564-35e3-4637-a384-9d38658fd981":{"id":"40262564-35e3-4637-a384-9d38658fd981","doc_no":"A.6.1.1.3.2.5.2.1.2.2","title":"Drift Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7277,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.5.2.2.2 - Drift Instance Configuration Document](25114297-6807-418a-a8e2-1e08daeb711d).","contentHash":"e4ad19356dafcddf1a701915a3b03107f8fd506777d5ff0cf4e33efee960ac8a","addressRefs":[]},"4c4d2ef7-9aa4-4eb9-8339-0aa0865ee5ee":{"id":"4c4d2ef7-9aa4-4eb9-8339-0aa0865ee5ee","doc_no":"A.6.1.1.3.2.5.2.1.2.3","title":"Save Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7278,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.5.2.2.3 - Save Instance Configuration Document](1cdf853f-2d68-4ced-b143-1f3f2f7bbe70).","contentHash":"796fa8c4111e38ab8a935e5d0eb942844bb699145aeb19e1742ebc53e7d58366","addressRefs":[]},"cd0c2ad5-34ec-4a4e-8af3-55c656ccdfc9":{"id":"cd0c2ad5-34ec-4a4e-8af3-55c656ccdfc9","doc_no":"A.6.1.1.3.2.5.2.1.2.4","title":"Lifinity Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7279,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.5.2.2.4 - Lifinity Instance Configuration Document](fbaeaf7e-92a4-4dd3-b65c-5cac02f0e831).","contentHash":"b6387b1858189705c526c69a143752da6cf87811bc221b01bbec52a59a638725","addressRefs":[]},"18ae39d9-bf60-40de-ad6a-97d0b111e678":{"id":"18ae39d9-bf60-40de-ad6a-97d0b111e678","doc_no":"A.6.1.1.3.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7280,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"402d52cd-aa0b-4982-9672-743726b197d2":{"id":"402d52cd-aa0b-4982-9672-743726b197d2","doc_no":"A.6.1.1.3.2.5.2.1.3.1","title":"MarginFi Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7281,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.5.2.3.1 - MarginFi Instance Configuration Document](86236277-2125-46f3-82a8-737956898288).","contentHash":"c5e3330eb6cfa318d67d88ae7c26358f7982a2540c7e0c91e56764d4f648bccb","addressRefs":[]},"3d481afc-bf97-4354-9305-3c6948001f3b":{"id":"3d481afc-bf97-4354-9305-3c6948001f3b","doc_no":"A.6.1.1.3.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7282,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.5.2.2 - Active Instances](a53d1d40-f944-4cf2-9941-8e6f0ec77a72), whereas failed Invocations are Archived in [A.6.1.1.3.2.5.2.1.5 - Hub Data Repository](a26de8b6-230f-402f-8de0-3a6439161ffb).","contentHash":"b13ec419b3d52b72699db6272e4caea9700fd4597afbded726a53ff6c524c950","addressRefs":[]},"a26de8b6-230f-402f-8de0-3a6439161ffb":{"id":"a26de8b6-230f-402f-8de0-3a6439161ffb","doc_no":"A.6.1.1.3.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7283,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"d7f4e888-fe3b-412f-9623-163470390a37":{"id":"d7f4e888-fe3b-412f-9623-163470390a37","doc_no":"A.6.1.1.3.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7284,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"a4295b57-9276-4a82-b8cb-11e8e122d558":{"id":"a4295b57-9276-4a82-b8cb-11e8e122d558","doc_no":"A.6.1.1.3.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7285,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"b48fc045-1754-4a89-83cf-6d76fbe056bb":{"id":"b48fc045-1754-4a89-83cf-6d76fbe056bb","doc_no":"A.6.1.1.3.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7286,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"a53d1d40-f944-4cf2-9941-8e6f0ec77a72":{"id":"a53d1d40-f944-4cf2-9941-8e6f0ec77a72","doc_no":"A.6.1.1.3.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7287,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"bff45812-80f3-4e46-9428-74a374bef2fc":{"id":"bff45812-80f3-4e46-9428-74a374bef2fc","doc_no":"A.6.1.1.3.2.5.2.2.1","title":"Kamino Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7288,"content":"The documents herein contain the Instance Configuration Document for the Kamino Integration Boost Primitive Instance.","contentHash":"efd82356ca26b7eb2bde262cb898ce3686b062e1991c3ac24e5cc9bac6dbb218","addressRefs":[]},"6df9c015-0a57-48d2-9bdd-08fbf42b83c9":{"id":"6df9c015-0a57-48d2-9bdd-08fbf42b83c9","doc_no":"A.6.1.1.3.2.5.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7289,"content":"The documents herein define the parameters of the Kamino Instance of the Integration Boost Primitive.","contentHash":"123c9631541c4bb1a3fd1fc46df2c215806230156e7b382d11bd35a9e962d2f7","addressRefs":[]},"d86968f4-a54b-40e1-9e82-e513a7a69a58":{"id":"d86968f4-a54b-40e1-9e82-e513a7a69a58","doc_no":"A.6.1.1.3.2.5.2.2.1.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7290,"content":"The partner for the Kamino Integration Boost is Kamino.","contentHash":"8564ac8d831a9c1c17c7acc13a99cced248ea4c9274d40bac185457df99fee36","addressRefs":[]},"aa03c0ef-76b9-42b7-a8c0-c48b8392fab5":{"id":"aa03c0ef-76b9-42b7-a8c0-c48b8392fab5","doc_no":"A.6.1.1.3.2.5.2.2.1.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7291,"content":"The reward address for the Kamino Integration Boost is `AU4GkzA4G9rRX3hS8QCNTiVGAtt5MNUAfK5L5Q57BAC4` on Solana.","contentHash":"1e7a05b5fdecd3aebd98341a0d020bccb495f815b6eca1209890c1e62d06f151","addressRefs":["AU4GkzA4G9rRX3hS8QCNTiVGAtt5MNUAfK5L5Q57BAC4"]},"bfca608d-73b2-429d-a51c-d8adb412fef7":{"id":"bfca608d-73b2-429d-a51c-d8adb412fef7","doc_no":"A.6.1.1.3.2.5.2.2.1.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7292,"content":"The Kamino Integration Boost is on Solana blockchain.","contentHash":"0320cde1ef83965392a2184d108ab369449c097ef16bd5be5e1bb5241c98b349","addressRefs":[]},"f90e64f7-84c9-41b5-b5eb-ed9e890ccd5f":{"id":"f90e64f7-84c9-41b5-b5eb-ed9e890ccd5f","doc_no":"A.6.1.1.3.2.5.2.2.1.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7293,"content":"The payment cadence for the Kamino Integration Boost is weekly.","contentHash":"d681cf659e52ab03c501769837f269649cd9973e46b53700d5c757344b74d6ad","addressRefs":[]},"40834c20-539b-4295-8327-7f6b997f562f":{"id":"40834c20-539b-4295-8327-7f6b997f562f","doc_no":"A.6.1.1.3.2.5.2.2.1.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7294,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/solana-incentives/](https://info-sky.blockanalitica.com/api/v1/solana-incentives/).","contentHash":"bc1fde2224bbf01da05fd1bad203acf170c36df1a6eadf49f189fe959255d865","addressRefs":[]},"93b3b2a9-a105-4470-b827-96b56ae4e1d5":{"id":"93b3b2a9-a105-4470-b827-96b56ae4e1d5","doc_no":"A.6.1.1.3.2.5.2.2.1.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7295,"content":"The Data Submission Responsible Actor is the Core Council Risk Advisor.","contentHash":"2cbca921ff14149c82115c863b485464fa2f513275638558c3d7884fee9c26b1","addressRefs":[]},"ef715b84-a864-4e01-8615-0d7668c8155b":{"id":"ef715b84-a864-4e01-8615-0d7668c8155b","doc_no":"A.6.1.1.3.2.5.2.2.1.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7296,"content":"The Integration Boost is calculated based on per block values for USDS in Kamino and the Sky Savings Rate.","contentHash":"8522b7a9e0219fd6ee3285d97ba06b970b78d6374152c28b97cec7b4222aff04","addressRefs":[]},"8c2f1229-9472-4833-8e8b-9d686c5e1ec4":{"id":"8c2f1229-9472-4833-8e8b-9d686c5e1ec4","doc_no":"A.6.1.1.3.2.5.2.2.1.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7297,"content":"The documents herein define the custom parameters of the Kamino Instance of the Integration Boost Primitive, if any.","contentHash":"8a4cfaefd2381390a4c3bf070cb6d272231ee32cb9f34e62b4d68b1ec3d88389","addressRefs":[]},"ba61357d-b348-4bf0-907a-389fed4db441":{"id":"ba61357d-b348-4bf0-907a-389fed4db441","doc_no":"A.6.1.1.3.2.5.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7298,"content":"The documents herein define the process for the ongoing management of the Kamino Instance of the Integration Boost Primitive.","contentHash":"e01f5ea7ccfc2b7c30ab1f26d083283227ed4e208de92c5efc0083ed11fd415f","addressRefs":[]},"ee4adbeb-b6eb-42cc-8aca-4c0dfa34b7b0":{"id":"ee4adbeb-b6eb-42cc-8aca-4c0dfa34b7b0","doc_no":"A.6.1.1.3.2.5.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7299,"content":"This document defines the protocol for routine ongoing management of the Kamino Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.2.2.4 - Instance Ongoing Management Protocol](805381e5-89e7-4fb9-bda7-a97e84b531ba), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Keel Artifact, a version of the full process definition customized to Keel will be included herein.","contentHash":"da03a0c70aea52d284790468e28f03eb60b857573a8aa299f876d307eec1ae65","addressRefs":[]},"3872c2ee-5465-4ce1-8c34-3800e61fd674":{"id":"3872c2ee-5465-4ce1-8c34-3800e61fd674","doc_no":"A.6.1.1.3.2.5.2.2.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7300,"content":"The Keel Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"2a28d4e53f02ae87f70e2cc6a3b810cf47e9d191d1d52263739e4445c001390a","addressRefs":[]},"c30f58b3-2431-428f-92ff-2519457e2c4d":{"id":"c30f58b3-2431-428f-92ff-2519457e2c4d","doc_no":"A.6.1.1.3.2.5.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7301,"content":"The documents herein define the protocol for non-routine ongoing management of the Kamino Instance of this Integration Boost Primitive.","contentHash":"baa0f55fd6c45ddd113a95721e14a5193bae694e3a4b8890c4020307da32c184","addressRefs":[]},"c7fc42f8-ba5f-4d71-9dec-af1a54fd1438":{"id":"c7fc42f8-ba5f-4d71-9dec-af1a54fd1438","doc_no":"A.6.1.1.3.2.5.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7302,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Kamino Instance of this Integration Boost Primitive.","contentHash":"33dec5e1a7f54a7d0d2d7bcb5d4a8440cc4ddcde99e2faa72c07d65bbe58f2ae","addressRefs":[]},"bd0755f7-5787-4c4c-9d81-88e6b8573f6a":{"id":"bd0755f7-5787-4c4c-9d81-88e6b8573f6a","doc_no":"A.6.1.1.3.2.5.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7303,"content":"The documents herein contain data relevant to the Kamino Instance of the Integration Boost Primitive.","contentHash":"01e401f8a54c6119bda751ff37237b0a935e5c8e53725c3b3ed1378afd98bb40","addressRefs":[]},"0886e43d-3f0e-4fbc-bb39-b21934477638":{"id":"0886e43d-3f0e-4fbc-bb39-b21934477638","doc_no":"A.6.1.1.3.2.5.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7304,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"e00ea6ea-daab-4f81-a4c4-9e9c1a245495":{"id":"e00ea6ea-daab-4f81-a4c4-9e9c1a245495","doc_no":"A.6.1.1.3.2.5.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7305,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"0f24b8c3-c3ae-43e4-a649-9a7df4de6fde":{"id":"0f24b8c3-c3ae-43e4-a649-9a7df4de6fde","doc_no":"A.6.1.1.3.2.5.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7306,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"f02b9ea5-ceae-42dd-8ca0-9565f7148efb":{"id":"f02b9ea5-ceae-42dd-8ca0-9565f7148efb","doc_no":"A.6.1.1.3.2.5.2.2.1.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7307,"content":"The Integration Boost payments for the Kamino Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"af9aabe6feea8f09b947f76743c15a3df2a3240ea03e27e1c6de85f148327683","addressRefs":[]},"0abca082-24c3-425d-a02f-631766a438d1":{"id":"0abca082-24c3-425d-a02f-631766a438d1","doc_no":"A.6.1.1.3.2.5.2.2.1.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7308,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"25114297-6807-418a-a8e2-1e08daeb711d":{"id":"25114297-6807-418a-a8e2-1e08daeb711d","doc_no":"A.6.1.1.3.2.5.2.2.2","title":"Drift Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7309,"content":"The documents herein contain the Instance Configuration Document for the Drift Integration Boost Primitive Instance.","contentHash":"eae3c325a68cb0cbfaae447ec5206978ea186ad7212a076f66321429b0097f8a","addressRefs":[]},"aa1660a7-2153-4c19-b541-21e0c99da42c":{"id":"aa1660a7-2153-4c19-b541-21e0c99da42c","doc_no":"A.6.1.1.3.2.5.2.2.2.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7310,"content":"The documents herein define the parameters of the Drift Instance of the Integration Boost Primitive.","contentHash":"86d34dc39cd86f60ef58cb6d27122f60b15c4d138cb2ed8b78f8b1a1ff750602","addressRefs":[]},"ce435a87-211f-45df-ac38-66c816796fe9":{"id":"ce435a87-211f-45df-ac38-66c816796fe9","doc_no":"A.6.1.1.3.2.5.2.2.2.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7311,"content":"The partner for the Drift Integration Boost is Drift.","contentHash":"a2d49527b9809c83b08cde8bb23222b6e96baab4f7eb8b3f6f75299a5c05ade9","addressRefs":[]},"8eb58c56-1b4f-4deb-9a44-0578c876ec4a":{"id":"8eb58c56-1b4f-4deb-9a44-0578c876ec4a","doc_no":"A.6.1.1.3.2.5.2.2.2.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7312,"content":"The reward address for the Drift Integration Boost is `5hMjmxexWu954pX9gB9jkHxMqdjpxArQS2XdvkaevRax` on Solana.","contentHash":"7f30019188f993a3028e9a87158931f1cdbc74d555ee957ec84af53e0d365c37","addressRefs":["5hMjmxexWu954pX9gB9jkHxMqdjpxArQS2XdvkaevRax"]},"dcde5fe3-2b4d-463c-99c4-166a238b7cf2":{"id":"dcde5fe3-2b4d-463c-99c4-166a238b7cf2","doc_no":"A.6.1.1.3.2.5.2.2.2.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7313,"content":"The Drift Integration Boost is on Solana blockchain.","contentHash":"b7cd990c89261df0c28e4e464835fae860b90877b7a6182f15d5faa1a783de3c","addressRefs":[]},"35b1e1da-1e21-4f29-97c9-c7e99377b750":{"id":"35b1e1da-1e21-4f29-97c9-c7e99377b750","doc_no":"A.6.1.1.3.2.5.2.2.2.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7314,"content":"The payment cadence for the Drift Integration Boost is weekly.","contentHash":"9f8d960b9c1cbc9583f6b01b03d4bb6ea06cfcd8198772caa9ba705d55a62ae3","addressRefs":[]},"59d8afd5-abf0-4c59-be6e-cccbbe18da12":{"id":"59d8afd5-abf0-4c59-be6e-cccbbe18da12","doc_no":"A.6.1.1.3.2.5.2.2.2.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7315,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/solana-incentives/](https://info-sky.blockanalitica.com/api/v1/solana-incentives/).","contentHash":"bc1fde2224bbf01da05fd1bad203acf170c36df1a6eadf49f189fe959255d865","addressRefs":[]},"2bf87576-4df5-4d01-ba0b-6f132782813d":{"id":"2bf87576-4df5-4d01-ba0b-6f132782813d","doc_no":"A.6.1.1.3.2.5.2.2.2.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7316,"content":"The Data Submission Responsible Actor is the Core Council Risk Advisor.","contentHash":"2cbca921ff14149c82115c863b485464fa2f513275638558c3d7884fee9c26b1","addressRefs":[]},"71951f16-8f4e-49db-b98c-9d1799a1b869":{"id":"71951f16-8f4e-49db-b98c-9d1799a1b869","doc_no":"A.6.1.1.3.2.5.2.2.2.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7317,"content":"The Integration Boost is calculated based on per block values for USDS in Drift and the Sky Savings Rate.","contentHash":"7f67d2f517e7330c68415f485d3d54386f81ebab77588a04d257b0657fdcc0e7","addressRefs":[]},"e53ba12e-957c-48f8-b508-7190d07b4778":{"id":"e53ba12e-957c-48f8-b508-7190d07b4778","doc_no":"A.6.1.1.3.2.5.2.2.2.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7318,"content":"The documents herein define the custom parameters of the Drift Instance of the Integration Boost Primitive, if any.","contentHash":"9333da98652647aba034f94db62d076b90f846018ee2eecc9be925db284e1c31","addressRefs":[]},"313e0ae3-1981-4d0e-93d6-8a4719c3d8db":{"id":"313e0ae3-1981-4d0e-93d6-8a4719c3d8db","doc_no":"A.6.1.1.3.2.5.2.2.2.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7319,"content":"The documents herein define the process for the ongoing management of the Drift Instance of the Integration Boost Primitive.","contentHash":"e8f583c9f212b05632683fb14c78936fb6f5aac644badd71f846b136c835938a","addressRefs":[]},"e329ad9b-8788-4261-82e3-891cf51ca6f2":{"id":"e329ad9b-8788-4261-82e3-891cf51ca6f2","doc_no":"A.6.1.1.3.2.5.2.2.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7320,"content":"This document defines the protocol for routine ongoing management of the Drift Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.2.2.4 - Instance Ongoing Management Protocol](805381e5-89e7-4fb9-bda7-a97e84b531ba), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Keel Artifact, a version of the full process definition customized to Keel will be included herein.","contentHash":"24d2384e8c1d20498bb9ea3bcf9b1f7650ae900732fb1a456ac4ad3ae2582060","addressRefs":[]},"072498cd-35c7-4e12-a2f7-3c6462257ed3":{"id":"072498cd-35c7-4e12-a2f7-3c6462257ed3","doc_no":"A.6.1.1.3.2.5.2.2.2.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7321,"content":"The Keel Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"2a28d4e53f02ae87f70e2cc6a3b810cf47e9d191d1d52263739e4445c001390a","addressRefs":[]},"97aa301f-1b42-45fa-915a-3d3e0dcb55ee":{"id":"97aa301f-1b42-45fa-915a-3d3e0dcb55ee","doc_no":"A.6.1.1.3.2.5.2.2.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7322,"content":"The documents herein define the protocol for non-routine ongoing management of the Drift Instance of this Integration Boost Primitive.","contentHash":"ab4dead00ee49a2fb70d890383e38beb167cd8962b987c14320ef282ba9df592","addressRefs":[]},"e3d0dc30-cf9e-4101-8729-b0039cd03e1d":{"id":"e3d0dc30-cf9e-4101-8729-b0039cd03e1d","doc_no":"A.6.1.1.3.2.5.2.2.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7323,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Drift Instance of this Integration Boost Primitive.","contentHash":"93709b21404730161b705fc93194dae8d3db1e887ce4a5108af034d134ee021d","addressRefs":[]},"1cbe8086-9c91-4e07-9310-79591f81430a":{"id":"1cbe8086-9c91-4e07-9310-79591f81430a","doc_no":"A.6.1.1.3.2.5.2.2.2.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7324,"content":"The documents herein contain data relevant to the Drift Instance of the Integration Boost Primitive.","contentHash":"346663bb884e6d8961208d1503f9efb1dd0dc8270780497f4d4e133d542ad2f7","addressRefs":[]},"cb8de39f-11d4-462d-80e4-12bd793697f1":{"id":"cb8de39f-11d4-462d-80e4-12bd793697f1","doc_no":"A.6.1.1.3.2.5.2.2.2.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7325,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"fdac7f0f-b7b3-45cd-be4f-51ba5755e097":{"id":"fdac7f0f-b7b3-45cd-be4f-51ba5755e097","doc_no":"A.6.1.1.3.2.5.2.2.2.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7326,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"fd38b098-1cee-4b81-9128-49f319a85624":{"id":"fd38b098-1cee-4b81-9128-49f319a85624","doc_no":"A.6.1.1.3.2.5.2.2.2.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7327,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"de885def-4e9c-4116-9a16-899f0d45340f":{"id":"de885def-4e9c-4116-9a16-899f0d45340f","doc_no":"A.6.1.1.3.2.5.2.2.2.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7328,"content":"The Integration Boost payments for the Drift Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"9afb017e68698c1c8493eb53ad591f4755fd5e571c2928e08fb8404337e4af85","addressRefs":[]},"1016d28e-fab4-4893-8e8f-846bed7e207d":{"id":"1016d28e-fab4-4893-8e8f-846bed7e207d","doc_no":"A.6.1.1.3.2.5.2.2.2.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7329,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"1cdf853f-2d68-4ced-b143-1f3f2f7bbe70":{"id":"1cdf853f-2d68-4ced-b143-1f3f2f7bbe70","doc_no":"A.6.1.1.3.2.5.2.2.3","title":"Save Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7330,"content":"The documents herein contain the Instance Configuration Document for the Save Integration Boost Primitive Instance.","contentHash":"0c9c2e5339eb06d651a0443078dc7bf2d27e4bfc0ce2b1f686586eb9167c6d24","addressRefs":[]},"0666e496-d967-42f0-9ec6-465fce5cc6ea":{"id":"0666e496-d967-42f0-9ec6-465fce5cc6ea","doc_no":"A.6.1.1.3.2.5.2.2.3.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7331,"content":"The documents herein define the parameters of the Save Instance of the Integration Boost Primitive.","contentHash":"bf2cdd1007ee0167e2aff235479bee80e5b5d59c6f998a9db7068236f2f12bc7","addressRefs":[]},"e247f4cc-b5fb-4202-a2c7-2eeb4b6476a9":{"id":"e247f4cc-b5fb-4202-a2c7-2eeb4b6476a9","doc_no":"A.6.1.1.3.2.5.2.2.3.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7332,"content":"The partner for the Save Integration Boost is Save.","contentHash":"7fdc8867af49c35208e8edccda217cb353a16478556f60704660bf008e4267e4","addressRefs":[]},"9b3239d4-c331-45d2-ba53-2280ebaf7626":{"id":"9b3239d4-c331-45d2-ba53-2280ebaf7626","doc_no":"A.6.1.1.3.2.5.2.2.3.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7333,"content":"The reward address for the Save Integration Boost is `5QbRL9MU5QakL5Fx2He9YaiUzB3TQpVAUBR2ARKN1NrM` on Solana.","contentHash":"91b296598c1877e633effc5f36f8cec03424c20674de4ab6b4a48311e0d22564","addressRefs":["5QbRL9MU5QakL5Fx2He9YaiUzB3TQpVAUBR2ARKN1NrM"]},"c31ef8da-0d27-42f8-a6e7-cdd72fb89e15":{"id":"c31ef8da-0d27-42f8-a6e7-cdd72fb89e15","doc_no":"A.6.1.1.3.2.5.2.2.3.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7334,"content":"The Save Integration Boost is on Solana blockchain.","contentHash":"ac33bcb96b0cd8b5f06b1e5ecbf0ec76736f9dc7f8d8e74ad33c679ed29ad0c5","addressRefs":[]},"89cf27b7-ef63-4671-8a21-2a5c19064418":{"id":"89cf27b7-ef63-4671-8a21-2a5c19064418","doc_no":"A.6.1.1.3.2.5.2.2.3.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7335,"content":"The payment cadence for the Save Integration Boost is weekly.","contentHash":"b81ea1b4b735e0b3bf1b1ba87098cc1fe9c543d8eb7e9c50bbb9366dc94f7b00","addressRefs":[]},"e6dd6579-2a26-4e85-b1fd-7887a8a387e0":{"id":"e6dd6579-2a26-4e85-b1fd-7887a8a387e0","doc_no":"A.6.1.1.3.2.5.2.2.3.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7336,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/solana-incentives/](https://info-sky.blockanalitica.com/api/v1/solana-incentives/). The data for Save is available through the API endpoint under Solend, the previous name Save operated under.","contentHash":"9fc13288ffd7e0e06f921b085170297afb30c01236e7ce2da4ea60b6157a5f0d","addressRefs":[]},"5cf367ae-6302-488e-89d9-8d05fd447725":{"id":"5cf367ae-6302-488e-89d9-8d05fd447725","doc_no":"A.6.1.1.3.2.5.2.2.3.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7337,"content":"The Data Submission Responsible Actor is the Core Council Risk Advisor.","contentHash":"2cbca921ff14149c82115c863b485464fa2f513275638558c3d7884fee9c26b1","addressRefs":[]},"9c58cd0d-d637-4c26-8cec-bb5c8f4fcdbd":{"id":"9c58cd0d-d637-4c26-8cec-bb5c8f4fcdbd","doc_no":"A.6.1.1.3.2.5.2.2.3.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7338,"content":"The Integration Boost is calculated based on per block values for USDS in Save and the Sky Savings Rate.","contentHash":"62cc527733e6208b48afb5ed83c9f3dda83da9ce97ee5c51d7a6a7345c2c3f54","addressRefs":[]},"c5c5aa96-d72b-4ae9-b48b-f4068f9f772c":{"id":"c5c5aa96-d72b-4ae9-b48b-f4068f9f772c","doc_no":"A.6.1.1.3.2.5.2.2.3.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7339,"content":"The documents herein define the custom parameters of the Save Instance of the Integration Boost Primitive, if any.","contentHash":"a467376f7a1090169a9fecfe142fc1d04fcfb07eca45c50f2ffe6a215ce2ae2e","addressRefs":[]},"1f098ea0-1d9e-4207-bbb1-217e14308d87":{"id":"1f098ea0-1d9e-4207-bbb1-217e14308d87","doc_no":"A.6.1.1.3.2.5.2.2.3.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7340,"content":"The documents herein define the process for the ongoing management of the Save Instance of the Integration Boost Primitive.","contentHash":"9b62b2b5094963a599f5807ddfbf84777d3cc0b7c9b4ef6e1bba4089be32fdcd","addressRefs":[]},"0e669131-758f-4ab1-8835-4532cf22c29a":{"id":"0e669131-758f-4ab1-8835-4532cf22c29a","doc_no":"A.6.1.1.3.2.5.2.2.3.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7341,"content":"This document defines the protocol for routine ongoing management of the Save Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.2.2.4 - Instance Ongoing Management Protocol](805381e5-89e7-4fb9-bda7-a97e84b531ba), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Keel Artifact, a version of the full process definition customized to Keel will be included herein.","contentHash":"64d99dfeede1c3025e6abacd6818ffe93551b121d6cb9c7648e6aae327c71788","addressRefs":[]},"e5ffb0b8-fd9d-4932-b8fa-1ebcc2cbb0d2":{"id":"e5ffb0b8-fd9d-4932-b8fa-1ebcc2cbb0d2","doc_no":"A.6.1.1.3.2.5.2.2.3.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7342,"content":"The Keel Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"2a28d4e53f02ae87f70e2cc6a3b810cf47e9d191d1d52263739e4445c001390a","addressRefs":[]},"6e865551-6993-4193-9d2b-9aa3f7517e3e":{"id":"6e865551-6993-4193-9d2b-9aa3f7517e3e","doc_no":"A.6.1.1.3.2.5.2.2.3.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7343,"content":"The documents herein define the protocol for non-routine ongoing management of the Save Instance of this Integration Boost Primitive.","contentHash":"c152fcbb957a71c0c53566d6454678fd507e040cc128103fd67cab38f6480cd5","addressRefs":[]},"071ccf78-e331-4457-a6ef-25bf3ca3f75a":{"id":"071ccf78-e331-4457-a6ef-25bf3ca3f75a","doc_no":"A.6.1.1.3.2.5.2.2.3.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7344,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Save Instance of this Integration Boost Primitive.","contentHash":"17f86b7bc5a87ee73130c802ae40457e21a01ed376185bb7a8d5fab9468c52ea","addressRefs":[]},"6263e82f-b2f0-4d02-9e5e-d62bd615bce8":{"id":"6263e82f-b2f0-4d02-9e5e-d62bd615bce8","doc_no":"A.6.1.1.3.2.5.2.2.3.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7345,"content":"The documents herein contain data relevant to the Save Instance of the Integration Boost Primitive.","contentHash":"215185a751e90bded5f4a6e079a335650b80fdd4196c567bd42d232f9f79995f","addressRefs":[]},"d1d06d85-c679-4a6f-ab24-cd10e4de1361":{"id":"d1d06d85-c679-4a6f-ab24-cd10e4de1361","doc_no":"A.6.1.1.3.2.5.2.2.3.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7346,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0e3774ea-7b40-4188-a467-ba54faacfd59":{"id":"0e3774ea-7b40-4188-a467-ba54faacfd59","doc_no":"A.6.1.1.3.2.5.2.2.3.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7347,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"7e0fc33a-f01c-4bd1-bfae-96bfda6a7986":{"id":"7e0fc33a-f01c-4bd1-bfae-96bfda6a7986","doc_no":"A.6.1.1.3.2.5.2.2.3.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7348,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"5c116971-2a07-4074-9a41-422e18f5eaec":{"id":"5c116971-2a07-4074-9a41-422e18f5eaec","doc_no":"A.6.1.1.3.2.5.2.2.3.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7349,"content":"The Integration Boost payments for the Save Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"c38d717236acc65b39b4d31fa936d3ed9571c9d574591619d012fdbd6652d881","addressRefs":[]},"52237195-bbb7-4b4e-a13a-536f639bd0d0":{"id":"52237195-bbb7-4b4e-a13a-536f639bd0d0","doc_no":"A.6.1.1.3.2.5.2.2.3.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7350,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"fbaeaf7e-92a4-4dd3-b65c-5cac02f0e831":{"id":"fbaeaf7e-92a4-4dd3-b65c-5cac02f0e831","doc_no":"A.6.1.1.3.2.5.2.2.4","title":"Lifinity Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7351,"content":"The documents herein contain the Instance Configuration Document for the Lifinity Integration Boost Primitive Instance.","contentHash":"1778e4f8d2496b4de5b4bdb9900cad5ea5aedf21e13baf85958077dc2eb47526","addressRefs":[]},"02b34736-8bb3-4998-aad4-d059b6574313":{"id":"02b34736-8bb3-4998-aad4-d059b6574313","doc_no":"A.6.1.1.3.2.5.2.2.4.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7352,"content":"The documents herein define the parameters of the Lifinity Instance of the Integration Boost Primitive.","contentHash":"a308c18888c1fcd54fd18ef76874475f7ae17815a693f7d174d3214cd5e4c544","addressRefs":[]},"877e9999-2210-4d33-ae34-6f443b8a1e79":{"id":"877e9999-2210-4d33-ae34-6f443b8a1e79","doc_no":"A.6.1.1.3.2.5.2.2.4.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7353,"content":"The partner for the Lifinity Integration Boost is Lifinity.","contentHash":"83046504d749559e5c9b5ceabd6120f127a993b4402d864132b420a5e4b241a5","addressRefs":[]},"3a3bc406-cd62-4b77-b905-938cca0a6be0":{"id":"3a3bc406-cd62-4b77-b905-938cca0a6be0","doc_no":"A.6.1.1.3.2.5.2.2.4.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7354,"content":"The reward address for the Lifinity Integration Boost is `71hhezkHQ2dhmPySsHVCCkLggfWzPFEBdfEjbn4NCXMG` on Solana.","contentHash":"d9466b6379a8e5af5ddb952ac99c08037ad193357d84a63d24142b9d0035accf","addressRefs":["71hhezkHQ2dhmPySsHVCCkLggfWzPFEBdfEjbn4NCXMG"]},"8cbc89e4-5287-4fb1-88b4-3c5c09d9d345":{"id":"8cbc89e4-5287-4fb1-88b4-3c5c09d9d345","doc_no":"A.6.1.1.3.2.5.2.2.4.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7355,"content":"The Lifinity Integration Boost is on Solana blockchain.","contentHash":"1404eb7213eb8a26ef31bc634b79c0e2fbd10aa6476c87fcdb593ade47bc970f","addressRefs":[]},"16f59a39-f9d9-49d3-b7e6-7a77eb5c0a2c":{"id":"16f59a39-f9d9-49d3-b7e6-7a77eb5c0a2c","doc_no":"A.6.1.1.3.2.5.2.2.4.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7356,"content":"The payment cadence for the Lifinity Integration Boost is weekly.","contentHash":"70c34ea51976f66237a84fd4642974b7681148efa4acb11f3ab403ceb3c6b88a","addressRefs":[]},"faf426ea-f52c-4262-ac80-6e3ef4dc4c08":{"id":"faf426ea-f52c-4262-ac80-6e3ef4dc4c08","doc_no":"A.6.1.1.3.2.5.2.2.4.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7357,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/solana-incentives/](https://info-sky.blockanalitica.com/api/v1/solana-incentives/).","contentHash":"bc1fde2224bbf01da05fd1bad203acf170c36df1a6eadf49f189fe959255d865","addressRefs":[]},"94bc2f19-0cbd-4afe-8c5d-d909092fb31d":{"id":"94bc2f19-0cbd-4afe-8c5d-d909092fb31d","doc_no":"A.6.1.1.3.2.5.2.2.4.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7358,"content":"The Data Submission Responsible Actor is the Core Council Risk Advisor..","contentHash":"bd0e9d33d096ec2a2127c41dcfd8b3a6234efafc1553a1ef7bd6c1211c5cece7","addressRefs":[]},"492bb423-8995-4e93-9bba-d063410bed8e":{"id":"492bb423-8995-4e93-9bba-d063410bed8e","doc_no":"A.6.1.1.3.2.5.2.2.4.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7359,"content":"The Integration Boost is calculated based on per block values for USDS in Lifinity and the Sky Savings Rate.","contentHash":"a6a9f42e662093a70dc20736dfaaf0a385cca135a952b0bdda36e15ba76a4b45","addressRefs":[]},"25a5f4b3-ef5e-455a-8f3d-27ed798ce5a2":{"id":"25a5f4b3-ef5e-455a-8f3d-27ed798ce5a2","doc_no":"A.6.1.1.3.2.5.2.2.4.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7360,"content":"The documents herein define the custom parameters of the Lifinity Instance of the Integration Boost Primitive, if any.","contentHash":"4bcae7b595863549b55751ac72fadec0814a9c6474bfd44883e2697d1e579aac","addressRefs":[]},"b066ba5b-d067-42c6-bfa5-ab84c696e020":{"id":"b066ba5b-d067-42c6-bfa5-ab84c696e020","doc_no":"A.6.1.1.3.2.5.2.2.4.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7361,"content":"The documents herein define the process for the ongoing management of the Lifinity Instance of the Integration Boost Primitive.","contentHash":"7716fd2e1f86e936d08f8e73bcf1602ed05887e122778a63d747ffc75b9f39f4","addressRefs":[]},"e7eb4307-efd2-4112-9bed-e9f5e85f565b":{"id":"e7eb4307-efd2-4112-9bed-e9f5e85f565b","doc_no":"A.6.1.1.3.2.5.2.2.4.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7362,"content":"This document defines the protocol for routine ongoing management of the Lifinity Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.2.2.4 - Instance Ongoing Management Protocol](805381e5-89e7-4fb9-bda7-a97e84b531ba), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Keel Artifact, a version of the full process definition customized to Keel will be included herein.","contentHash":"546f5e8362e82c076d4b48c45370cf593c86e94146dcb12309f9568caf14a4b4","addressRefs":[]},"917307b6-ec3f-4b5f-b517-3f561c2cfe9a":{"id":"917307b6-ec3f-4b5f-b517-3f561c2cfe9a","doc_no":"A.6.1.1.3.2.5.2.2.4.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7363,"content":"The Keel Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"2a28d4e53f02ae87f70e2cc6a3b810cf47e9d191d1d52263739e4445c001390a","addressRefs":[]},"6bbaef28-382b-4c2c-8a9a-020de7727c86":{"id":"6bbaef28-382b-4c2c-8a9a-020de7727c86","doc_no":"A.6.1.1.3.2.5.2.2.4.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7364,"content":"The documents herein define the protocol for non-routine ongoing management of the Lifinity Instance of this Integration Boost Primitive.","contentHash":"a8c594f10940e94acec6047c959bbebafb2eb44e3d63d4221cbdff1bbfa6e311","addressRefs":[]},"2685b9a3-e827-44b0-82e9-d7750396fecc":{"id":"2685b9a3-e827-44b0-82e9-d7750396fecc","doc_no":"A.6.1.1.3.2.5.2.2.4.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7365,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Lifinity Instance of this Integration Boost Primitive.","contentHash":"d47751cc988664a2cb66a835dbe049e47f9470c14632cc729cee575acebc9dad","addressRefs":[]},"24b453d1-6f31-4ab2-bdca-a5493229b62f":{"id":"24b453d1-6f31-4ab2-bdca-a5493229b62f","doc_no":"A.6.1.1.3.2.5.2.2.4.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7366,"content":"The documents herein contain data relevant to the Lifinity Instance of the Integration Boost Primitive.","contentHash":"35f3a08f0bafd2a7a651a00f92092da4ce72f745e415990ea158e20d93070001","addressRefs":[]},"4de91f25-bb65-4bc4-94b2-e9d58fbf9733":{"id":"4de91f25-bb65-4bc4-94b2-e9d58fbf9733","doc_no":"A.6.1.1.3.2.5.2.2.4.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7367,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"2a2ac512-32ec-4ee1-85a5-5cae060bc2ca":{"id":"2a2ac512-32ec-4ee1-85a5-5cae060bc2ca","doc_no":"A.6.1.1.3.2.5.2.2.4.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7368,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"780b5dbf-5b27-4d12-940d-2b2d324fcf2c":{"id":"780b5dbf-5b27-4d12-940d-2b2d324fcf2c","doc_no":"A.6.1.1.3.2.5.2.2.4.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7369,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"b2077965-9350-4699-be85-847934f1d7b0":{"id":"b2077965-9350-4699-be85-847934f1d7b0","doc_no":"A.6.1.1.3.2.5.2.2.4.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7370,"content":"The Integration Boost payments for the Lifinity Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"63d5ed3b52086a5d8ee60c6e3a7effd303145ada1f93e54aba513e98ee6bb50d","addressRefs":[]},"4c94d227-1244-4926-be0b-d6cf87cd91b3":{"id":"4c94d227-1244-4926-be0b-d6cf87cd91b3","doc_no":"A.6.1.1.3.2.5.2.2.4.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7371,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"cb3d56e6-8284-4292-9cfe-df8c23c04bf0":{"id":"cb3d56e6-8284-4292-9cfe-df8c23c04bf0","doc_no":"A.6.1.1.3.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7372,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"86236277-2125-46f3-82a8-737956898288":{"id":"86236277-2125-46f3-82a8-737956898288","doc_no":"A.6.1.1.3.2.5.2.3.1","title":"MarginFi Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7373,"content":"The documents herein contain the Instance Configuration Document for the MarginFi Integration Boost Primitive Instance.","contentHash":"8229f4f7a12545bcb69ae34e274c2596073224aeb6d068161614a6309e469f9f","addressRefs":[]},"99f6f4f6-40c5-4b3d-bc80-8bf7361479a0":{"id":"99f6f4f6-40c5-4b3d-bc80-8bf7361479a0","doc_no":"A.6.1.1.3.2.5.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7374,"content":"The documents herein define the parameters of the MarginFi Instance of the Integration Boost Primitive.","contentHash":"24d8459343c97f236da1de2faed6fa37458d5aef848927abbff25fca8bfdf6d0","addressRefs":[]},"075a138e-889a-428a-bdd7-d1ccedecbfd7":{"id":"075a138e-889a-428a-bdd7-d1ccedecbfd7","doc_no":"A.6.1.1.3.2.5.2.3.1.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7375,"content":"The partner for the MarginFi Integration Boost is MarginFi.","contentHash":"1af39a14336077af16d370db7dd0c8388a9930975919115604e5cda5801bdd78","addressRefs":[]},"951107cb-8087-4a47-8b6c-5c50793b8796":{"id":"951107cb-8087-4a47-8b6c-5c50793b8796","doc_no":"A.6.1.1.3.2.5.2.3.1.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7376,"content":"The reward address for the MarginFi Integration Boost is `AZtUUe9GvTFq9kfseu9jxTioSgdSfjgmZfGQBmhVpTj1 `on Solana.","contentHash":"03fd86f5b28036ddf05e89dd627c374dec3ec51a730303060c96de6affac6113","addressRefs":["AZtUUe9GvTFq9kfseu9jxTioSgdSfjgmZfGQBmhVpTj1"]},"10f6ab13-0f78-4017-8ce2-b8443032b3be":{"id":"10f6ab13-0f78-4017-8ce2-b8443032b3be","doc_no":"A.6.1.1.3.2.5.2.3.1.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7377,"content":"The MarginFi Integration Boost is on Solana blockchain.","contentHash":"3e785d765f5a336f76645e07d230d9ab962ee39264aa6187b82fad77a0ad2647","addressRefs":[]},"17608de3-6224-4cc6-886d-ab5817178b6e":{"id":"17608de3-6224-4cc6-886d-ab5817178b6e","doc_no":"A.6.1.1.3.2.5.2.3.1.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7378,"content":"The payment cadence for the MarginFi Integration Boost is weekly.","contentHash":"3230fdff3deac8f1a05717b169971ce1247bf59c856a6f77c961fef1e6a59a3d","addressRefs":[]},"4164892e-41a3-4295-a35b-c0130859a378":{"id":"4164892e-41a3-4295-a35b-c0130859a378","doc_no":"A.6.1.1.3.2.5.2.3.1.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7379,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/solana-incentives/](https://info-sky.blockanalitica.com/api/v1/solana-incentives/).","contentHash":"bc1fde2224bbf01da05fd1bad203acf170c36df1a6eadf49f189fe959255d865","addressRefs":[]},"f9e0a68d-89a4-4c57-8da5-4912be9688fd":{"id":"f9e0a68d-89a4-4c57-8da5-4912be9688fd","doc_no":"A.6.1.1.3.2.5.2.3.1.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7380,"content":"The Data Submission Responsible Actor is the Core Council Risk Advisor.","contentHash":"2cbca921ff14149c82115c863b485464fa2f513275638558c3d7884fee9c26b1","addressRefs":[]},"8bc6de1d-c9ee-43a5-9e1f-9307b4de9ee1":{"id":"8bc6de1d-c9ee-43a5-9e1f-9307b4de9ee1","doc_no":"A.6.1.1.3.2.5.2.3.1.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7381,"content":"The Integration Boost is calculated based on per block values for USDS in MarginFi and the Sky Savings Rate.","contentHash":"a636b7da1f2a858a81128c0a4ebe2e6857cb65db9492424c6ba1abc8d4ed8117","addressRefs":[]},"3160b0a5-3822-49f9-b962-70b33baa0e2c":{"id":"3160b0a5-3822-49f9-b962-70b33baa0e2c","doc_no":"A.6.1.1.3.2.5.2.3.1.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7382,"content":"The documents herein define the custom parameters of the MarginFi Instance of the Integration Boost Primitive, if any.","contentHash":"f2451c9f3a858b8f46e8e2be65220c2c47f23e55cefe56c86564cf4918fedf5a","addressRefs":[]},"9ed9898f-a226-49f3-94d9-9279fa5eb143":{"id":"9ed9898f-a226-49f3-94d9-9279fa5eb143","doc_no":"A.6.1.1.3.2.5.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7383,"content":"The documents herein define the process for the ongoing management of the MarginFi Instance of the Integration Boost Primitive.","contentHash":"e8f6a8d3049a63534c71d7d928d28e2f9d9b7b9b2f0ea52e86b649cdbcbdb362","addressRefs":[]},"a367b919-e9bb-4a9e-9dbd-b3a0f520201b":{"id":"a367b919-e9bb-4a9e-9dbd-b3a0f520201b","doc_no":"A.6.1.1.3.2.5.2.3.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7384,"content":"This document defines the protocol for routine ongoing management of the MarginFi Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.2.2.4 - Instance Ongoing Management Protocol](805381e5-89e7-4fb9-bda7-a97e84b531ba), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Keel Artifact, a version of the full process definition customized to Keel will be included herein.","contentHash":"7948f6c5bee0f68d6e48161de7c844e5e973c35e758d7de663c6c6c9600ebe88","addressRefs":[]},"9e8e1663-b7cf-4492-8e6d-b66f80b28ab4":{"id":"9e8e1663-b7cf-4492-8e6d-b66f80b28ab4","doc_no":"A.6.1.1.3.2.5.2.3.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7385,"content":"The Keel Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"2a28d4e53f02ae87f70e2cc6a3b810cf47e9d191d1d52263739e4445c001390a","addressRefs":[]},"9a62f3b7-bef9-4002-865a-9d59dd19fb23":{"id":"9a62f3b7-bef9-4002-865a-9d59dd19fb23","doc_no":"A.6.1.1.3.2.5.2.3.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7386,"content":"The documents herein define the protocol for non-routine ongoing management of the MarginFi Instance of this Integration Boost Primitive.","contentHash":"231caa0e936609cf79658f191ba420992215f853debb887e1a399d163dceec94","addressRefs":[]},"d4c759f6-c8cc-4bc3-84b3-76a1a1a9492e":{"id":"d4c759f6-c8cc-4bc3-84b3-76a1a1a9492e","doc_no":"A.6.1.1.3.2.5.2.3.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7387,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the MarginFi Instance of this Integration Boost Primitive.","contentHash":"3c706ad597201ec6821f75bf0455e41a7085188daa8f9b86323cd8e330fdc759","addressRefs":[]},"a7f0ef1a-f643-4370-a2e6-d8d0c7db44d7":{"id":"a7f0ef1a-f643-4370-a2e6-d8d0c7db44d7","doc_no":"A.6.1.1.3.2.5.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7388,"content":"The documents herein contain data relevant to the MarginFi Instance of the Integration Boost Primitive.","contentHash":"444722acb1a3f75d80c5cad86d80c3d1d8071d0a68c2531d9f546b87b246ea02","addressRefs":[]},"5d022265-732d-471f-960c-ad352469f71e":{"id":"5d022265-732d-471f-960c-ad352469f71e","doc_no":"A.6.1.1.3.2.5.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7389,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"d7fe3f68-dc0b-4494-8563-44e2f8e684a3":{"id":"d7fe3f68-dc0b-4494-8563-44e2f8e684a3","doc_no":"A.6.1.1.3.2.5.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7390,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"3aaf2998-6729-4ccf-848d-5dbc8d8e68ae":{"id":"3aaf2998-6729-4ccf-848d-5dbc8d8e68ae","doc_no":"A.6.1.1.3.2.5.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7391,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"61c17003-e1b0-46a8-8b67-0b120a0cdd5b":{"id":"61c17003-e1b0-46a8-8b67-0b120a0cdd5b","doc_no":"A.6.1.1.3.2.5.2.3.1.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7392,"content":"The Integration Boost payments for the MarginFi Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"b848041646aee17d32c100741c990ea59d48252b5f41b7a1431746a3c735a31f","addressRefs":[]},"bc103251-76b5-4969-b17f-520474e01a14":{"id":"bc103251-76b5-4969-b17f-520474e01a14","doc_no":"A.6.1.1.3.2.5.2.3.1.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7393,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"4d86b12e-7abe-4707-afa6-3694fdb09e32":{"id":"4d86b12e-7abe-4707-afa6-3694fdb09e32","doc_no":"A.6.1.1.3.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7394,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.5.2.2 - Active Instances](a53d1d40-f944-4cf2-9941-8e6f0ec77a72).","contentHash":"8f6d1395aa410ea043d3ed42223537cdfd1d895b5667791d1edd7e5279328fd7","addressRefs":[]},"8744a0ac-6d59-407d-a192-7ce4ce257420":{"id":"8744a0ac-6d59-407d-a192-7ce4ce257420","doc_no":"A.6.1.1.3.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7395,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"5238ab208d7665058807eb999e72611f95365017972e1b5f24a5992315f9c88d","addressRefs":[]},"9502a517-1323-4f1a-9038-8314b4704ff1":{"id":"9502a517-1323-4f1a-9038-8314b4704ff1","doc_no":"A.6.1.1.3.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7396,"content":"The documents herein organize all base information relevant to Keel’s usage of the Pioneer Chain Primitive.","contentHash":"05e865931e8069cfe4faef1b2159ad2577880d5d009d8def2d8a5fcad30fcc1c","addressRefs":[]},"5bf76475-f22b-4929-ac3c-7792a567fa49":{"id":"5bf76475-f22b-4929-ac3c-7792a567fa49","doc_no":"A.6.1.1.3.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7397,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"0596e4e7-880f-42ce-96b8-00e8482837fb":{"id":"0596e4e7-880f-42ce-96b8-00e8482837fb","doc_no":"A.6.1.1.3.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7398,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"adab4387-3553-4134-bd3c-1f3d07f98415":{"id":"adab4387-3553-4134-bd3c-1f3d07f98415","doc_no":"A.6.1.1.3.2.5.3.1.2.1","title":"Solana Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7399,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.3.2.5.3.2.1 - Solana Instance Configuration Document](638b8dd4-6faa-47b8-9553-a8a4703b6545).","contentHash":"193727883300fc6c0828a13946da489806313c2936edcfdb11084f38cf2ae27e","addressRefs":[]},"e7dd62af-a742-4518-97a6-70b885ad67f6":{"id":"e7dd62af-a742-4518-97a6-70b885ad67f6","doc_no":"A.6.1.1.3.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7400,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"6b836e0a-37cd-4e54-9479-1cf54ee4088c":{"id":"6b836e0a-37cd-4e54-9479-1cf54ee4088c","doc_no":"A.6.1.1.3.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7401,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.5.3.2 - Active Instances](5d043c09-1d78-456d-b356-c72a13fe46c8), whereas failed Invocations are Archived in [A.6.1.1.3.2.5.3.1.5 - Hub Data Repository](e32e87d5-bbaf-4bde-9bbd-332e2465a44a).","contentHash":"ec1b9dc8e990f8c05a3a7cc23db915cba5af4b347e2509b1bb893bd4b2ab3a77","addressRefs":[]},"e32e87d5-bbaf-4bde-9bbd-332e2465a44a":{"id":"e32e87d5-bbaf-4bde-9bbd-332e2465a44a","doc_no":"A.6.1.1.3.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7402,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"6bd42489-8672-49d0-923b-57c6ea782fe2":{"id":"6bd42489-8672-49d0-923b-57c6ea782fe2","doc_no":"A.6.1.1.3.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7403,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"7cd4dd2e-693a-4879-ba88-158a95c6b428":{"id":"7cd4dd2e-693a-4879-ba88-158a95c6b428","doc_no":"A.6.1.1.3.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7404,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"4289b0d8-f587-4abf-8905-8c5df520c854":{"id":"4289b0d8-f587-4abf-8905-8c5df520c854","doc_no":"A.6.1.1.3.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7405,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"5d043c09-1d78-456d-b356-c72a13fe46c8":{"id":"5d043c09-1d78-456d-b356-c72a13fe46c8","doc_no":"A.6.1.1.3.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7406,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"638b8dd4-6faa-47b8-9553-a8a4703b6545":{"id":"638b8dd4-6faa-47b8-9553-a8a4703b6545","doc_no":"A.6.1.1.3.2.5.3.2.1","title":"Solana Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7407,"content":"The documents herein contain the Instance Configuration Document for the Solana Instance of the Pioneer Chain Primitive.","contentHash":"97475498887b2a4569279e297905eefb826327a1e745a9d63a60ecc0256a83aa","addressRefs":[]},"c4a101cc-2c82-4fba-8811-bf84829eead1":{"id":"c4a101cc-2c82-4fba-8811-bf84829eead1","doc_no":"A.6.1.1.3.2.5.3.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7408,"content":"The documents herein define the parameters of the Solana Instance of the Pioneer Chain Primitive.","contentHash":"fdf0ab5c6f353869e55ee9df290c617292ffb44baec03f09ff9875f1d602385a","addressRefs":[]},"86e50f38-bf79-43cb-854e-2421b6a3c812":{"id":"86e50f38-bf79-43cb-854e-2421b6a3c812","doc_no":"A.6.1.1.3.2.5.3.2.1.1.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7409,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"8c67dee5-c782-4cb9-bdcd-964eb662c28f":{"id":"8c67dee5-c782-4cb9-bdcd-964eb662c28f","doc_no":"A.6.1.1.3.2.5.3.2.1.1.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7410,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"1010660f-aa32-41bb-b85b-0986370b225f":{"id":"1010660f-aa32-41bb-b85b-0986370b225f","doc_no":"A.6.1.1.3.2.5.3.2.1.1.2","title":"Pioneer Incentive Pool","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7411,"content":"The documents herein contain the terms that govern this Instance's Pioneer Incentive Pool and its address.","contentHash":"86b4489c5004a1a438ede266ddea17e1cee462ce29ad0e5a170e27f337fc0923","addressRefs":[]},"f2648962-8b3a-45a1-a455-206f704535bb":{"id":"f2648962-8b3a-45a1-a455-206f704535bb","doc_no":"A.6.1.1.3.2.5.3.2.1.1.2.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7412,"content":"`8JmDPG5BFQ6gpUPJV9xBixYJLqTKCSNotkXksTmNsQfj`","contentHash":"03debbb9f1321b2de375a0a7068628f4c2fd8ce9c05dfaeaf90106bd44901839","addressRefs":["8JmDPG5BFQ6gpUPJV9xBixYJLqTKCSNotkXksTmNsQfj"]},"d8b93260-34fe-45b2-83a1-06e093813a7c":{"id":"d8b93260-34fe-45b2-83a1-06e093813a7c","doc_no":"A.6.1.1.3.2.5.3.2.1.1.2.2","title":"Terms","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7413,"content":"The Pioneer Incentive Pool for this Instance is governed by the terms specified in [A.2.2.8.3.1.4 - Pioneer Incentive Pool](04edac33-19d5-4a87-a8ab-945a0cd57771).","contentHash":"398f45540512dcf7575840dc803f208433c4e3a0be43346a3f6eeb92e954d7d8","addressRefs":[]},"1f4a087f-1f3a-4e6e-89c6-58a162674757":{"id":"1f4a087f-1f3a-4e6e-89c6-58a162674757","doc_no":"A.6.1.1.3.2.5.3.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7414,"content":"The documents herein define the process for the ongoing management of the Solana Instance of the Pioneer Chain Primitive.","contentHash":"a201251c397659eeb5f5cc4460702e261e61ac946c7e9f0cdbe41946b3bbb49a","addressRefs":[]},"dcdd2415-6ad3-4a02-a0a4-10acda9d185f":{"id":"dcdd2415-6ad3-4a02-a0a4-10acda9d185f","doc_no":"A.6.1.1.3.2.5.3.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7415,"content":"The documents herein contain data relevant to the Solana Instance of the Pioneer Chain Primitive.","contentHash":"f6c30156b756478c8de6672f8624db4a795052c6fce87a73d22f0e5974110e77","addressRefs":[]},"4ddfaa41-e902-4d6a-a915-6d999c502a34":{"id":"4ddfaa41-e902-4d6a-a915-6d999c502a34","doc_no":"A.6.1.1.3.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7416,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"079d3d3d-2549-4216-bc56-84af879ef929":{"id":"079d3d3d-2549-4216-bc56-84af879ef929","doc_no":"A.6.1.1.3.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7417,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.5.3.2 - Active Instances](5d043c09-1d78-456d-b356-c72a13fe46c8).","contentHash":"26f5f1eb61b7835136549bd52c94cf42299da8910b67f77e1048d2613c931e16","addressRefs":[]},"23e77e03-5726-4def-86a8-7ae41c7c9b51":{"id":"23e77e03-5726-4def-86a8-7ae41c7c9b51","doc_no":"A.6.1.1.3.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7418,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Keel. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"a2e1d4cea53cb9357eed55f149d0fb1a6b18ef9291b88f88a945c8d4702029fe","addressRefs":[]},"0f04cae2-326f-42f1-bc8a-74d01e6ad2af":{"id":"0f04cae2-326f-42f1-bc8a-74d01e6ad2af","doc_no":"A.6.1.1.3.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7419,"content":"The documents herein contain all data and specifications for Keel’s Allocation System Primitive Instances.","contentHash":"f908e5f675b84e229cd645b7020d5575bc7a7964c76631e63de84191ca7ee1b2","addressRefs":[]},"835a84a6-2167-4013-acce-281e164c5985":{"id":"835a84a6-2167-4013-acce-281e164c5985","doc_no":"A.6.1.1.3.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7420,"content":"The documents herein organize all base information relevant to Keel’s usage of the Keel Liquidity Layer.","contentHash":"d9241173365e0edda75c9ded0a1cffdd4ebb592ebbbda2ce083d6142aa060e26","addressRefs":[]},"08c6ac06-313b-47bc-b0af-bc93192c6a95":{"id":"08c6ac06-313b-47bc-b0af-bc93192c6a95","doc_no":"A.6.1.1.3.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7421,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"134c14e9-28ed-4e18-b15a-26899644dc0b":{"id":"134c14e9-28ed-4e18-b15a-26899644dc0b","doc_no":"A.6.1.1.3.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7422,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"421535cf-d79d-4e2f-92fa-020d53bd1aff":{"id":"421535cf-d79d-4e2f-92fa-020d53bd1aff","doc_no":"A.6.1.1.3.2.6.1.1.2.1","title":"Solana","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7423,"content":"The documents herein contain a Directory of all Instances on Solana of the Allocation System Primitive with Instance status of `Active`.","contentHash":"12b3a767fa1f8a23e643464aa552c0c7f869ed145cd18c59523070b64ae0710b","addressRefs":[]},"50b33f03-fdb8-4b5b-8b75-3768b17759a9":{"id":"50b33f03-fdb8-4b5b-8b75-3768b17759a9","doc_no":"A.6.1.1.3.2.6.1.1.2.1.1","title":"Kamino","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7424,"content":"The Solana Instances Directory of the Kamino Protocol with `Active` Status are stored herein.","contentHash":"f3377f69a7445cab2bf1953db20758a21b97949b50eae2189391986787a605b0","addressRefs":[]},"874acdaa-1c84-47a5-aa08-ec87718e3c0d":{"id":"874acdaa-1c84-47a5-aa08-ec87718e3c0d","doc_no":"A.6.1.1.3.2.6.1.1.2.1.1.1","title":"Solana - Kamino USDS Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7425,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.1.1 - Solana - Kamino USDS Instance Configuration Document](fa6f6aa7-410e-4515-8458-9f3efb30c942)","contentHash":"4ae8d3c616c884caf7de94047cac9347b3e0238016196e6b91ea4cf8b6401b84","addressRefs":[]},"202b96d7-36d0-4b5b-b885-dfe314464d3d":{"id":"202b96d7-36d0-4b5b-b885-dfe314464d3d","doc_no":"A.6.1.1.3.2.6.1.1.2.1.1.2","title":"Solana - Kamino USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7426,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.1.2 - Solana - Kamino USDC Instance Configuration Document](2510c2ba-c304-478f-84b1-a421e62de8b4)","contentHash":"732623009116fe1553f304b7e3d61417576675b7f901970cd6578da22831970c","addressRefs":[]},"4e40376a-59b3-4c2d-ab2b-9320b4f72e4e":{"id":"4e40376a-59b3-4c2d-ab2b-9320b4f72e4e","doc_no":"A.6.1.1.3.2.6.1.1.2.1.1.3","title":"Solana - Kamino USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7427,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.1.3 - Solana - Kamino USDT Instance Configuration Document](4adbf528-4a16-496c-974f-ce612af69162).","contentHash":"8e675bd3fb6d320c25b00c1274485ab5a9657e070ac8696f340fb79f31e426d5","addressRefs":[]},"09d70aa2-7082-42d0-b81b-2ec5065b49be":{"id":"09d70aa2-7082-42d0-b81b-2ec5065b49be","doc_no":"A.6.1.1.3.2.6.1.1.2.1.1.4","title":"Solana - Kamino USDG Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7428,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.1.4 - Solana - Kamino USDG Instance Configuration Document](8b972495-2f93-4d88-b1f4-d447e2d821a3).","contentHash":"d550f484f93839cec2d6522aa3b1d5c77e57390e7671d4ae4b5719e544d72e34","addressRefs":[]},"efde31d7-efae-463b-8c85-f104c284992d":{"id":"efde31d7-efae-463b-8c85-f104c284992d","doc_no":"A.6.1.1.3.2.6.1.1.2.1.1.5","title":"Solana - Kamino PYUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7429,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.1.5 - Solana - Kamino PYUSD Instance Configuration Document](dd6cf5ec-6ccd-46af-9c4e-0858f79948f7)","contentHash":"36a4c314819eb17176e3ea4326334152bf64e191b4efd37e794af2d8b6b29cde","addressRefs":[]},"e9748bec-bdee-440c-bde1-a2c7bb450a74":{"id":"e9748bec-bdee-440c-bde1-a2c7bb450a74","doc_no":"A.6.1.1.3.2.6.1.1.2.1.2","title":"Drift","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7430,"content":"The Solana Instances Directory of the Drift Protocol with `Active` Status are stored herein.","contentHash":"5550311115ae10a2730705bece75570598e3471952d59e445d8db9d9d27cc63d","addressRefs":[]},"32707a35-c0a8-47b8-abb3-03022a5df11d":{"id":"32707a35-c0a8-47b8-abb3-03022a5df11d","doc_no":"A.6.1.1.3.2.6.1.1.2.1.2.1","title":"Solana - Drift USDS Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7431,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.2.1 - Solana - Drift USDS Instance Configuration Document](5e934067-e691-4247-bfa1-7df9d4625f21).","contentHash":"c35cb481146bd67648bbd8b556acd8c64bf4898997f58f8b5e319702ffa8c80e","addressRefs":[]},"8b23bd05-aa9a-4298-be16-03a2f8165a84":{"id":"8b23bd05-aa9a-4298-be16-03a2f8165a84","doc_no":"A.6.1.1.3.2.6.1.1.2.1.2.2","title":"Solana - Drift USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7432,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.2.2 - Solana - Drift USDC Instance Configuration Document](ddf9f671-bf5c-4f21-af92-63cce7815af4).","contentHash":"2dd9e1081bcb0ec36f35823461817e7984d32cb957c91af029f6a4048ef34460","addressRefs":[]},"d720a25c-2e97-4b52-bdc4-3e1400789448":{"id":"d720a25c-2e97-4b52-bdc4-3e1400789448","doc_no":"A.6.1.1.3.2.6.1.1.2.1.2.3","title":"Solana - Drift USDT Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7433,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.2.3 - Solana - Drift USDT Instance Configuration Document](300e6f12-800f-4f55-900b-a0697acfb257).","contentHash":"1392ce924c080cdc801c9d837718888d62886598dc82320a2912906364b48ef9","addressRefs":[]},"04889d34-faf3-4619-ad82-bd12a8c0e28e":{"id":"04889d34-faf3-4619-ad82-bd12a8c0e28e","doc_no":"A.6.1.1.3.2.6.1.1.2.1.2.4","title":"Solana - Drift PYUSD Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7434,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.3.2.6.1.3.1.2.4 - Solana - Drift PYUSD Instance Configuration Document](ea272eb2-0ffd-4704-a02c-ee4f047cb8a3).","contentHash":"06d4d7f24c9c654f5d23c42c307c945bf59d45f8ae2eff8ffa6903aa74cea1ec","addressRefs":[]},"ca7557db-6f08-4352-a1b8-5d098ece70ec":{"id":"ca7557db-6f08-4352-a1b8-5d098ece70ec","doc_no":"A.6.1.1.3.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7435,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"c0753031-d528-4f41-affc-aed720bd018a":{"id":"c0753031-d528-4f41-affc-aed720bd018a","doc_no":"A.6.1.1.3.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7436,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to[A.6.1.1.3.2.6.1.1.2 - Active Instances Directory](134c14e9-28ed-4e18-b15a-26899644dc0b), whereas failed Invocations are Archived in [A.6.1.1.3.2.6.1.1.5 - Hub Data Repository](99be2bd2-c065-43b7-82f9-d51dfeeeaa58).","contentHash":"3d5860e0265bc7d8afa8363c46738b9509a929dc488a79e0e9a9a02ff38ad8d8","addressRefs":[]},"99be2bd2-c065-43b7-82f9-d51dfeeeaa58":{"id":"99be2bd2-c065-43b7-82f9-d51dfeeeaa58","doc_no":"A.6.1.1.3.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7437,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"3326fd03-88b1-4ab4-a0ab-24c8023d2c01":{"id":"3326fd03-88b1-4ab4-a0ab-24c8023d2c01","doc_no":"A.6.1.1.3.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7438,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"e080e3ed-c786-46bc-b68a-e46b6a752f17":{"id":"e080e3ed-c786-46bc-b68a-e46b6a752f17","doc_no":"A.6.1.1.3.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7439,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"7bf3b5c6-6cc5-46fe-b4a8-08b9a0108bec":{"id":"7bf3b5c6-6cc5-46fe-b4a8-08b9a0108bec","doc_no":"A.6.1.1.3.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7440,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"d4a7f9b4-7ee0-4f99-a9b9-eebe0219fa8c":{"id":"d4a7f9b4-7ee0-4f99-a9b9-eebe0219fa8c","doc_no":"A.6.1.1.3.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7441,"content":"The documents herein provide general specifications of the Keel Liquidity Layer and define Keel’s overarching strategy and operational framework for managing across all Instances.","contentHash":"28c0732543bbe3bc0f09e2c138a25ce85af6de0c8da5ef6041d729e17a53d493","addressRefs":[]},"5a1327e3-8c53-43d4-96b8-61483557e27d":{"id":"5a1327e3-8c53-43d4-96b8-61483557e27d","doc_no":"A.6.1.1.3.2.6.1.2.1","title":"General Specifications","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7442,"content":"The documents herein contain general specifications for the Keel Liquidity Layer.","contentHash":"7813923376cbf4169de758439c4c899d176e2ca4f212af530590117e048b22d0","addressRefs":[]},"0ab7adfb-1f39-479a-b8a0-546410401bba":{"id":"0ab7adfb-1f39-479a-b8a0-546410401bba","doc_no":"A.6.1.1.3.2.6.1.2.1.1","title":"Keel Liquidity Layer Architecture","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7443,"content":"The documents herein describe the high-level design of the Keel Liquidity Layer, including its key smart contracts and their functionality.","contentHash":"dd0b708a09a34c9d2f5815db57937210c9d96a2d29f775f8922df2c1c62b8021","addressRefs":[]},"c65bd264-cb23-4587-add5-d3091a16613d":{"id":"c65bd264-cb23-4587-add5-d3091a16613d","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1","title":"Keel Liquidity Layer Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7444,"content":"The subdocuments herein provide the addresses of the Keel Liquidity Layer’s constituent contracts.","contentHash":"2f3a321c0b28468fa7856dac6a98b47ed07e238d66d54647287c458b07c9b3ce","addressRefs":[]},"54f36966-b656-4f51-9272-ac60fd90e1cc":{"id":"54f36966-b656-4f51-9272-ac60fd90e1cc","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.1","title":"Allocator Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7445,"content":"The documents herein contain global key addresses for the Allocator Contracts.","contentHash":"a99119eb26b8e6fbaae81a45fa911afc0af3344a9ea2bbcb90fc7cf9bd94fe9c","addressRefs":[]},"14887966-f73a-4abd-bd5e-51df5a7fe061":{"id":"14887966-f73a-4abd-bd5e-51df5a7fe061","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.1.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7446,"content":"The documents herein contain the Allocator Contract Addresses on the Ethereum Mainnet.","contentHash":"084c1a1c5fbe0a4abc17b09c0096038edfd2c77bdd298abb5411775b166695ef","addressRefs":[]},"7aa8974f-04fe-4e51-9452-c01296250068":{"id":"7aa8974f-04fe-4e51-9452-c01296250068","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.1.1.1","title":"Allocator Buffer Contract","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7447,"content":"The address of the ALLOCATOR_BUFFER contract is: `0x065E5De3D3A08c9d14BF79Ce5A6d3D0E8794640c`","contentHash":"5c23a518653ce44476953ef8bf35dca26142ab9d207f8e147066b2c6d20320cf","addressRefs":["0x065e5de3d3a08c9d14bf79ce5a6d3d0e8794640c"]},"05259994-3a57-4249-82f4-f47eb881b5ee":{"id":"05259994-3a57-4249-82f4-f47eb881b5ee","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.1.1.2","title":"Allocator Oracle Contract","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7448,"content":"The address of the ALLOCATOR_ORACLE contract is: `0xc7B91C401C02B73CBdF424dFaaa60950d5040dB7`","contentHash":"3915a8e9d83e0d12a43a164e763cda42d8b41817675dff88c98314a34152cb8e","addressRefs":["0xc7b91c401c02b73cbdf424dfaaa60950d5040db7"]},"2052c0df-8888-48cf-990c-735899d60a47":{"id":"2052c0df-8888-48cf-990c-735899d60a47","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.1.1.3","title":"Allocator Registry Contract","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7449,"content":"The address of the ALLOCATOR_REGISTRY contract is: `0xCdCFA95343DA7821fdD01dc4d0AeDA958051bB3B`","contentHash":"b7d71c2ecb2f67f2fe2ddf5b5835dec050bd7652285c86dba07b3fb3e96f8275","addressRefs":["0xcdcfa95343da7821fdd01dc4d0aeda958051bb3b"]},"60f119c3-ba99-4370-8f77-f163374f73eb":{"id":"60f119c3-ba99-4370-8f77-f163374f73eb","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.1.1.4","title":"Allocator Roles Contract","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7450,"content":"The address of the ALLOCATOR_ROLES contract is: `0x9A865A710399cea85dbD9144b7a09C889e94E803`","contentHash":"458d4bfa62334f282ee18ad433673de3de9a11f7e2c97fd190afc1bef481a49d","addressRefs":["0x9a865a710399cea85dbd9144b7a09c889e94e803"]},"7fd991d5-e2f4-4f8e-b4a6-13ab01509894":{"id":"7fd991d5-e2f4-4f8e-b4a6-13ab01509894","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.1.1.5","title":"Allocator Vault (Nova) Contract","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7451,"content":"The address of the ALLOCATOR_VAULT (ALLOCATOR Nova) contract is: `0xe4470DD3158F7A905cDeA07260551F72d4bB0e77`","contentHash":"7f5a8caae90e45ea9da3730f182739d40860254901f2f8bfea26eddad5594c35","addressRefs":["0xe4470dd3158f7a905cdea07260551f72d4bb0e77"]},"d655a727-9a7c-4f7d-84e1-dc26395983fe":{"id":"d655a727-9a7c-4f7d-84e1-dc26395983fe","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2","title":"ALM Contracts","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7452,"content":"The documents herein contain addresses for the ALM Contracts for the Keel Liquidity Layer.","contentHash":"fc07ed3c481e5d3fe6cba1577dd937bebb64cc76921d719abbdc74d21b82b916","addressRefs":[]},"0a39fe78-c262-495a-96fa-cb50077a0d53":{"id":"0a39fe78-c262-495a-96fa-cb50077a0d53","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7453,"content":"The documents herein contain the ALM Contract Addresses for the Keel Liquidity Layer on the Ethereum Mainnet.","contentHash":"2ca8721751fcceb6ba2682fbd6b9a4fb7c6b96bcf61b0b6b2f5c8676595647ae","addressRefs":[]},"8ea07623-dc66-4e6b-8478-6fc3fadf049b":{"id":"8ea07623-dc66-4e6b-8478-6fc3fadf049b","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.1.1","title":"ALM Controller Contract Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7454,"content":"The address of the ALM_CONTROLLER (`MainnetController`) contract is: `0xEF26BDc34F35669C235345aeF24A251B1EE80EF3`","contentHash":"336c276584591aa4afef2851a93f19a494d32a91f4673c88c64f47804f083007","addressRefs":["0xef26bdc34f35669c235345aef24a251b1ee80ef3"]},"b0980c40-fd44-492b-8435-b71fa0217819":{"id":"b0980c40-fd44-492b-8435-b71fa0217819","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.1.2","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7455,"content":"The ALM_CONTROLLER contract version is: `1.7.0`","contentHash":"3be448bea3339d249a5e8805e22179924b29d28e5ed5f74f813e4f64c8b34939","addressRefs":[]},"bd6847f1-093d-44a7-8971-98628de6fa8d":{"id":"bd6847f1-093d-44a7-8971-98628de6fa8d","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.1.3","title":"ALM Freezer Multisig Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7456,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.3.2.6.1.2.1.2.2.3 - Freezer Multisig](50ef16ee-1309-4172-befa-186529eb91c3).","contentHash":"e87a7dfee48194b7228c1bb62845bce29dcbd7e918d9b84f353d44b95cc63dc6","addressRefs":[]},"9e280969-f099-4b67-8528-41f2248e634a":{"id":"9e280969-f099-4b67-8528-41f2248e634a","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.1.4","title":"ALM Relayer Multisig Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7457,"content":"The addresses of the Multisigs that have the Relayer Role are specified in [A.6.1.1.3.2.6.1.2.1.2.2.1 - Prime Relayer Multisig](0bdf0649-1446-4ea7-b8dd-e41dc26b9be7) and [A.6.1.1.3.2.6.1.2.1.2.2.2 - Core Operator Relayer Multisig](b17a4a11-7340-4113-972d-76362f816b8a).","contentHash":"3fd996722fafc2ced8bedcf21af5281ebc4d36ceb41825d76491f21834a663fe","addressRefs":[]},"796968ee-aa7b-40f2-acc8-a784eb41b21a":{"id":"796968ee-aa7b-40f2-acc8-a784eb41b21a","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.1.5","title":"ALM Proxy Contract","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7458,"content":"The address of the ALM_PROXY contract is: `0xa5139956eC99aE2e51eA39d0b57C42B6D8db0758`","contentHash":"f2f7118cc6be6cd0d474d1862c96bcf4dd7f2d61858e3af9ecb47928f3f21b8d","addressRefs":["0xa5139956ec99ae2e51ea39d0b57c42b6d8db0758"]},"0a1eaef9-84e5-4ebe-a6b7-328349b5f310":{"id":"0a1eaef9-84e5-4ebe-a6b7-328349b5f310","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.1.6","title":"ALM Rate Limits Contract","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7459,"content":"The address of the ALM_RATE_LIMITS contract is: `0x65E7B39e508944F7C4278d3e4580f84Eb20b26a7`","contentHash":"ddc1ba3f420e6c13f828e8777d9355d9903ff0ddb6a274eb79a1c387ca9d93df","addressRefs":["0x65e7b39e508944f7c4278d3e4580f84eb20b26a7"]},"63dcc42b-87ba-43db-a9f6-4eb2b47ecb79":{"id":"63dcc42b-87ba-43db-a9f6-4eb2b47ecb79","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2","title":"Solana","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7460,"content":"The documents herein contain the ALM Program Addresses for the Keel Liquidity Layer on Solana.","contentHash":"df06ff138e1007c60d183914efd1d7951c4d57126370764c40a78b75a4be7c44","addressRefs":[]},"286d26d1-4737-4c3a-9344-4a6d0cdefa93":{"id":"286d26d1-4737-4c3a-9344-4a6d0cdefa93","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2.1","title":"Solana ALM Controller Program","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7461,"content":"The address of the SOLANA_ALM_CONTROLLER (`SvmAlmController`) program is: `ALM1JSnEhc5PkNecbSZotgprBuJujL5objTbwGtpTgTd`.","contentHash":"0ca179e6e4905847578d9de2b7a118c0b9669a80fa48ec6a1d1684061843c21d","addressRefs":["ALM1JSnEhc5PkNecbSZotgprBuJujL5objTbwGtpTgTd"]},"725952f6-ed88-4869-8105-c43de12bb9a5":{"id":"725952f6-ed88-4869-8105-c43de12bb9a5","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2.2","title":"Solana ALM Controller State","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7462,"content":"The address of the state instance configured for Keel is: `EeobZr57FSmNvw8Hs719iULJNqv3XLrTB5uPezvC2ND3`.","contentHash":"c1fa489cb18e195416d417e089a95ea08b0ad17b4a43ba84e8615c4a3572b77c","addressRefs":["EeobZr57FSmNvw8Hs719iULJNqv3XLrTB5uPezvC2ND3"]},"844da5c2-cc3b-4bc2-8d2d-2ee9ee09f3a1":{"id":"844da5c2-cc3b-4bc2-8d2d-2ee9ee09f3a1","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2.3","title":"Solana ALM Controller’s PDA","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7463,"content":"The address of the instance’s PDA, configured for Keel is `EeWDutgcKNTdQGJkGRrWYmTXXuKnPUZNvXepbLkQrxW4`. This is the address that ‘owns’ any positions or tokens.","contentHash":"eadb316372a75ea221d402a598355d21aa10c1ace9b8a21ea1e12d1e949b1393","addressRefs":["EeWDutgcKNTdQGJkGRrWYmTXXuKnPUZNvXepbLkQrxW4"]},"aec3b22f-5d75-4c27-b6f8-68babb1211ed":{"id":"aec3b22f-5d75-4c27-b6f8-68babb1211ed","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2.4","title":"Solana ALM Controller Contract Version","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7464,"content":"The ALM_CONTROLLER contract version is: `1.0.0`","contentHash":"6af55bf718f2865171e0ad04ad470446dd0653bf182f13e01e8b7c3ae39ba14b","addressRefs":[]},"812bd84c-3826-4cda-9897-a6a50050494f":{"id":"812bd84c-3826-4cda-9897-a6a50050494f","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2.5","title":"Solana ALM Controller’s USDC TokenAccount Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7465,"content":"The Instance’s USDC TokenAccount Address is `4UA2CC9fQDTbX1SnJcanYn2QU5PtyB1MGfezDvGFPVwd`.","contentHash":"6da548e81336126a8dcd6c679014b3e34fada2f1aedfeab5832b5c4b32fac3c2","addressRefs":["4UA2CC9fQDTbX1SnJcanYn2QU5PtyB1MGfezDvGFPVwd"]},"d321eb55-3592-400a-970d-3ed194c57988":{"id":"d321eb55-3592-400a-970d-3ed194c57988","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2.6","title":"ALM Freezer Multisig Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7466,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.3.2.6.1.2.1.2.3.4 - Freezer Multisig](aeee4280-ab46-4269-9430-fef8c2ee6d43).","contentHash":"b41044fd24cb181a113fd775d62901c9641320c0e3337a85511dcd104bad95b7","addressRefs":[]},"21ec6877-82e9-4897-ac67-f23de2917a4b":{"id":"21ec6877-82e9-4897-ac67-f23de2917a4b","doc_no":"A.6.1.1.3.2.6.1.2.1.1.1.2.2.7","title":"ALM Relayer Multisig Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7467,"content":"The addresses of the Multisigs that have the Relayer Role are specified in [A.6.1.1.3.2.6.1.2.1.2.3.1 - Prime Primary Relayer Address](600dfd83-d3a1-4b26-a906-c412673855b9), [A.6.1.1.3.2.6.1.2.1.2.3.2 - Prime Secondary Relayer Address](3b538bc7-3d18-4091-908d-dc0c3a6e8a62) and [A.6.1.1.3.2.6.1.2.1.2.3.3 - Core Operator Relayer Multisig](ced26169-892b-4ec4-9a16-8fb90e94a9ef).","contentHash":"e4620ca364ef2e89a8ead40f1e6805506857394af000031beff7e785734e685a","addressRefs":[]},"6a9eed19-76e3-42c5-a3ac-2fda937600f4":{"id":"6a9eed19-76e3-42c5-a3ac-2fda937600f4","doc_no":"A.6.1.1.3.2.6.1.2.1.1.2","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7468,"content":"The documents herein list the off-chain operational parameters for the Keel Liquidity Layer. These operational parameters are protocol settings managed outside of smart contracts (off-chain), used by operators and off-chain systems to guide the functioning of the Keel Liquidity Layer.","contentHash":"0174ac10781d1515faf5e0518923e9b209029c1962c55b0008b8444fc28015f9","addressRefs":[]},"8477f75e-2800-4511-af34-dd25e590aa1f":{"id":"8477f75e-2800-4511-af34-dd25e590aa1f","doc_no":"A.6.1.1.3.2.6.1.2.1.1.2.1","title":"Off-chain Operational Parameters For Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7469,"content":"The document herein lists the current off-chain operational parameters for the Keel Liquidity Layer on Ethereum Mainnet.","contentHash":"947f02d15c3d9a5f77af37bfbef97c9bb5044b6e7f94e251d3d3411ddeb1dedb","addressRefs":[]},"387e28bf-7748-416c-9a62-6696e131f975":{"id":"387e28bf-7748-416c-9a62-6696e131f975","doc_no":"A.6.1.1.3.2.6.1.2.1.1.2.1.1","title":"Minimum Operation Size Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7470,"content":"The minimum transaction size for operations on Ethereum Mainnet is (`MAINNET_MIN_OPERATION_SIZE`)\n\n- This parameter will be specified in a future iteration of the Keel Artifact.","contentHash":"705ac3caa3e568b0a964d8b05787a3f4873b85ba267fd743b3f52ff770c2f21a","addressRefs":[]},"6d4807f2-c6d0-4731-a315-3eb64397e4b0":{"id":"6d4807f2-c6d0-4731-a315-3eb64397e4b0","doc_no":"A.6.1.1.3.2.6.1.2.1.1.2.1.2","title":"Debt Ceiling Buffer Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7471,"content":"The buffer amount below the maximum debt ceiling is (`DEBT_CEILING_BUFFER`)\n\n- This parameter will be specified in a future iteration of the Keel Artifact.","contentHash":"f085f789cc6e87e44c0fde41f045de4a4a647e7c0d0e0d3f7a330e99b8ebf290","addressRefs":[]},"297df822-cb2a-40ca-b42b-2f88f669122d":{"id":"297df822-cb2a-40ca-b42b-2f88f669122d","doc_no":"A.6.1.1.3.2.6.1.2.1.1.2.2","title":"Off-chain Operational Parameters For Solana","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7472,"content":"The document herein lists the current off-chain operational parameters for the Keel Liquidity Layer on Solana.","contentHash":"2a99f5e2906951358b5ace313311b2e79e84a224fef5a8855cf48a9fc7967498","addressRefs":[]},"68a562ac-e43d-4aa7-971e-b9c13d0465c7":{"id":"68a562ac-e43d-4aa7-971e-b9c13d0465c7","doc_no":"A.6.1.1.3.2.6.1.2.1.1.2.2.1","title":"Minimum Operation Size Solana","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7473,"content":"The minimum transaction size for operations on Solana is (`SOLANA_MIN_OPERATION_SIZE`)\n\n- This parameter will be specified in a future iteration of the Keel Artifact.","contentHash":"a58f7bee8794475971ab2139b57d106bb775b8451d3402474ba58784bce0df9c","addressRefs":[]},"bdbfe3ef-b848-4095-872d-66d189668fd3":{"id":"bdbfe3ef-b848-4095-872d-66d189668fd3","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7474,"content":"The documents herein list the Rate Limits for the Keel Liquidity Layer on each blockchain.","contentHash":"1b275b8d22ef8638fb9b513b052697e6111ae762dc70ee91209798ac56ca603b","addressRefs":[]},"f783b89a-c2c7-4b78-91d3-08794358bb5f":{"id":"f783b89a-c2c7-4b78-91d3-08794358bb5f","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7475,"content":"The documents herein list the current `RateLimits` for the Keel Liquidity Layer on Ethereum Mainnet.","contentHash":"66fa038980d741f237c19306b64298c364a286905e2fbbdb43ace1182955de70","addressRefs":[]},"8c2ffb6e-0f1b-458d-9066-ee65b6099e87":{"id":"8c2ffb6e-0f1b-458d-9066-ee65b6099e87","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.1","title":"Ethereum Mainnet USDS","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7476,"content":"The maximum mint, burn and swap for USDS on Ethereum Mainnet are located herein.","contentHash":"4323efef0315c0a5c2c9e4f553191f6dec03ed401554026f074f922f992b00db","addressRefs":[]},"568f6fae-4680-4090-8eee-fe0b8e920155":{"id":"568f6fae-4680-4090-8eee-fe0b8e920155","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.1.1","title":"USDS Mint Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7477,"content":"The maximum amount of USDS that can be minted within the Keel Liquidity Layer (`LIMIT_USDS_MINT`) is specified in the document herein.\n\n- `maxAmount`: 10,000 USDS\n- `slope`: 10,000 USDS per day","contentHash":"f101c0431db94c48d5c56914c5b29e5bb562113afaaf5f1e81f451a24a7b358f","addressRefs":[]},"308b6a69-7b8d-4631-a8c7-cfa2cd260ea4":{"id":"308b6a69-7b8d-4631-a8c7-cfa2cd260ea4","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.1.2","title":"USDS Burn Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7478,"content":"The maximum amount of USDS that can be burned within the Keel Liquidity Layer (`LIMIT_USDS_BURN`) is specified in the document herein.\n\n- `maxAmount`: Unlimited\n- `slope`: Unlimited","contentHash":"957471bb6f106ae72b28e93fcb4018c94a4fb4d8533d4ceed5ef33fecac9bb62","addressRefs":[]},"b5c9efe7-4240-4a29-bd4d-9dcb7bbe3840":{"id":"b5c9efe7-4240-4a29-bd4d-9dcb7bbe3840","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.1.3","title":"USDS For USDC Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7479,"content":"The maximum amount of USDS that can be swapped for USDC by the Keel Liquidity Layer in the Mainnet PSM (`LIMIT_USDS_TO_USDC`) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"631ff41e56139f8150d39882fc784a80d946bfd94b9c02c0c8106989aa4b6640","addressRefs":[]},"5ee088fb-53b0-46f9-bf40-b59101cc2f24":{"id":"5ee088fb-53b0-46f9-bf40-b59101cc2f24","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.1.4","title":"USDS to Solana via SkyBridge/OFT","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7480,"content":"The maximum amount of USDS that can be sent to Keel’s Solana ALM Controller (`LIMIT_LAYERZERO_TRANSFER`, hashed with Solana USDS OFT address and Solana destination domain) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"ba943954d8ae8f59c19670a0881611f9c1e6b357172842de63da8505f4a22efd","addressRefs":[]},"b593503f-ba6d-4f04-8fae-cf1971b55cbf":{"id":"b593503f-ba6d-4f04-8fae-cf1971b55cbf","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.2","title":"Ethereum Mainnet sUSDS","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7481,"content":"The maximum deposit and withdrawal amounts for sUSDS on Ethereum Mainnet are located herein.","contentHash":"a6395acb428651840437295161652e9cd4b8e2da00981e4ce5179750d42dc262","addressRefs":[]},"28831fcf-2e28-4760-a4cd-27ae538edd9a":{"id":"28831fcf-2e28-4760-a4cd-27ae538edd9a","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.2.1","title":"Ethereum Mainnet sUSDS Deposit Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7482,"content":"The maximum amount of sUSDS that can be deposited (`LIMIT_4626_DEPOSIT`) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"8a0bbc3009e8df10e723f667c1903c36f4e1da81aa269d41984e81b56ecbcb39","addressRefs":[]},"26dd35a7-0c0e-46e4-8717-84e974e27239":{"id":"26dd35a7-0c0e-46e4-8717-84e974e27239","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.2.2","title":"Ethereum Mainnet sUSDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7483,"content":"The maximum amount of sUSDS that can be withdrawn (`LIMIT_4626_WITHDRAW`) is specified in the document herein.\n\n- `maxAmount`: Unlimited\n- `slope`: 0","contentHash":"31703891c1d379df88277bd1b99735505440854c32803a5470b32654ab484433","addressRefs":[]},"6e47f3c2-1f5a-4d78-a74e-333e705a2257":{"id":"6e47f3c2-1f5a-4d78-a74e-333e705a2257","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.3","title":"Ethereum Mainnet USDC","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7484,"content":"The maximum amount that can be transferred and sent to Keel’s Solana ALM Controller for USDC are located herein.","contentHash":"e0622af5e96b35f6a2fd34e8d22532a161b030ec199e9a3998686b583880123e","addressRefs":[]},"cada0328-a57d-49c6-9d47-6e70400fc668":{"id":"cada0328-a57d-49c6-9d47-6e70400fc668","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.3.1","title":"USDC to Solana via CCTP","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7485,"content":"The maximum amount of USDC that can be sent to Keel’s Solana ALM Controller (`LIMIT_USDC_TO_DOMAIN`, hashed with Solana domain) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"11a9bce21df791ed9e1ca567af7be43378a245005b094881da414ff342fde953","addressRefs":[]},"4d8f22cb-194c-4a92-8c2e-ea258d52986a":{"id":"4d8f22cb-194c-4a92-8c2e-ea258d52986a","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.1.3.2","title":"USDC Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7486,"content":"The maximum amount of USDC that can be bridged to Ethereum Mainnet ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP`) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDC\n- `slope`: 50,000,000 USDC per day","contentHash":"6ffbfd96af3c01b0aa3d8021b1f76574c7e24901a896930a3ad5c8deff989cfd","addressRefs":[]},"2edb355c-541a-44e3-bcf0-87227fad560b":{"id":"2edb355c-541a-44e3-bcf0-87227fad560b","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2","title":"Solana","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7487,"content":"The documents herein list the current rate limits for the Keel Liquidity Layer on Solana.","contentHash":"1ec46348002e152bd9a1ddc02bb7a59a6cfbfc08159428978a3286e582275105","addressRefs":[]},"a9868620-43c5-419a-a1ff-691d7618ab8c":{"id":"a9868620-43c5-419a-a1ff-691d7618ab8c","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.1","title":"Solana USDS","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7488,"content":"The maximum mint, burn and swap for USDS on Solana are located herein","contentHash":"5208acf125f71711781d7509fdb59657434b5e24357c7e1c41e98ffa3857900a","addressRefs":[]},"d9e9085a-cc04-41b9-8708-fe41fc2ef0f3":{"id":"d9e9085a-cc04-41b9-8708-fe41fc2ef0f3","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.1.1","title":"USDS Reserve","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7489,"content":"The maximum amount of USDS that can leave the USDS `Reserve` in aggregate across any integrations is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDS\n- `slope`: 10,000,000 USDS per day","contentHash":"0ad8039c914c5adf8779d1880b25ca592cf4beefea58097c5298af97918c7b84","addressRefs":[]},"5f86844e-579b-425c-8f7b-e6521cfe55b9":{"id":"5f86844e-579b-425c-8f7b-e6521cfe55b9","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.1.2","title":"USDS For USDC Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7490,"content":"The maximum amount of USDS that can be swapped for USDC by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"b9cde2deb0be6206400e03dfc51222e700c835c7fc83b893342c7bd297698986","addressRefs":[]},"3e48b867-07ff-4af7-a0d8-66e95b935a8f":{"id":"3e48b867-07ff-4af7-a0d8-66e95b935a8f","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.1.3","title":"USDS to Ethereum Mainnet via SkyBridge/OFT","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7491,"content":"The maximum amount of USDS that can be sent to Keel’s Ethereum Mainnet ALM Controller is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDS\n- `slope`: 10,000,000 USDS per day","contentHash":"affd6b1ea1c6f4b33d96a9485b33390f44e473fb5414d5741d49e0b23cd2fea0","addressRefs":[]},"081d2895-b10a-44cf-871f-c2efc60d17ea":{"id":"081d2895-b10a-44cf-871f-c2efc60d17ea","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.2","title":"Solana USDC","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7492,"content":"The maximum mint, burn and swap for USDC on Solana are located herein","contentHash":"76b6a9ba6e8571d98fb7f90fac409902210504f4bc3acd268a43001a662d2a30","addressRefs":[]},"7f7a3441-7bf4-46e7-9e03-5144d47091f5":{"id":"7f7a3441-7bf4-46e7-9e03-5144d47091f5","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.2.1","title":"USDC Reserve","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7493,"content":"The maximum amount of USDC that can leave the USDC `Reserve` in aggregate across any integrations is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"63f726f025f670dbbfb67c8e32c2c623f9a4c4154ea4015d65e466c1f425352e","addressRefs":[]},"06081a43-075d-48c1-a26d-6578c1aa2fd3":{"id":"06081a43-075d-48c1-a26d-6578c1aa2fd3","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.2.2","title":"USDC For USDS Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7494,"content":"The maximum amount of USDC that can be swapped for USDC by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"1463310442304774454fad5b469ddf006d19277cb9b1bc9d22e172a26eee0c62","addressRefs":[]},"ed93fa5c-eb76-480d-9462-bd5d0af2bad2":{"id":"ed93fa5c-eb76-480d-9462-bd5d0af2bad2","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.2.3","title":"USDC For USDT Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7495,"content":"The maximum amount of USDC that can be swapped for USDT by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"5b1ac1a48b05cabc12d1ddae33fe22bad84cfcd4bc21c4c59962f76a76113dbf","addressRefs":[]},"bb63cc13-3e51-43fa-becb-6b4a8e2df939":{"id":"bb63cc13-3e51-43fa-becb-6b4a8e2df939","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.2.4","title":"USDC For USDG Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7496,"content":"The maximum amount of USDC that can be swapped for USDG by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"dd911a10de692726141a162e53f69e29d18d3a6f1eaa804d0e31e5f351fb90ec","addressRefs":[]},"58cf4236-d399-45b9-b650-b1cc8392459e":{"id":"58cf4236-d399-45b9-b650-b1cc8392459e","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.2.5","title":"USDC For PYUSD Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7497,"content":"The maximum amount of USDC that can be swapped for PYUSD by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"88551cfff68ee894b07a341e6eca829680c96d116d7d0a802424f10584d4cfdd","addressRefs":[]},"3aeb4993-17b2-4959-ae81-d1518bb7d333":{"id":"3aeb4993-17b2-4959-ae81-d1518bb7d333","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.2.6","title":"USDC to Ethereum Mainnet via CCTP","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7498,"content":"The maximum amount of USDC that can be sent to Keel’s Ethereum Mainnet ALM Controller is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"c3f5b3b10e2f9ae8d06da3dc1e22ee46249588d88b4860a626ff6e67defc79c7","addressRefs":[]},"492f7297-f350-45d7-baca-88f1fb9f6b5c":{"id":"492f7297-f350-45d7-baca-88f1fb9f6b5c","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.3","title":"Solana USDT","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7499,"content":"The maximum mint, burn and swap for USDT on Solana are located herein","contentHash":"69302fc46541dd0b83e199da4c36f0b9a614b79181745e43a1c033c9b8615474","addressRefs":[]},"ddfd7cfe-ebc0-413f-8060-f564a559b8fb":{"id":"ddfd7cfe-ebc0-413f-8060-f564a559b8fb","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.3.1","title":"USDT Reserve","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7500,"content":"The maximum amount of USDT that can leave the USDT `Reserve` in aggregate across any integrations is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDT\n- `slope`: 10,000,000 USDT per day","contentHash":"24f588eb0d466068a76b0b403917d33d4e38ea1a4a6803411c4e89f1d9ed7472","addressRefs":[]},"23c8500f-0866-4aa4-99a1-e9f513ad4fa8":{"id":"23c8500f-0866-4aa4-99a1-e9f513ad4fa8","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.3.2","title":"USDT For USDC Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7501,"content":"The maximum amount of USDT that can be swapped for USDC by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDT\n- `slope`: 10,000,000 USDT per day","contentHash":"a08fab8a7341f4eadd74f90a7bb777a652eb798eb5bebb55e8b3c6d7d1a0217d","addressRefs":[]},"d37a9ed4-8945-4076-8e05-dd2319bcb033":{"id":"d37a9ed4-8945-4076-8e05-dd2319bcb033","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.4","title":"Solana USDG","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7502,"content":"The maximum mint, burn and swap for USDG on Solana are located herein","contentHash":"caaf3cb7138bb5aa5629cad1d74b160a9d839a7d4bf411685b2931b6fc6d8007","addressRefs":[]},"dfd32464-7a3b-454d-99e4-c1652cb57c5d":{"id":"dfd32464-7a3b-454d-99e4-c1652cb57c5d","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.4.1","title":"USDG Reserve","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7503,"content":"The maximum amount of USDG that can leave the USDG `Reserve` in aggregate across any integrations is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDG\n- `slope`: 10,000,000 USDG per day","contentHash":"a4e76c152dec42c33d835d5e86c2dde4f6aea81d3dd2e9e2441fdbdf7b764080","addressRefs":[]},"e6ab3642-13a1-40bc-9f95-ba68b25a7b89":{"id":"e6ab3642-13a1-40bc-9f95-ba68b25a7b89","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.4.2","title":"USDG For USDC Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7504,"content":"The maximum amount of USDG that can be swapped for USDC by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 25,000,000 USDG\n- `slope`: 10,000,000 USDG per day","contentHash":"8677e39bfe456a0a7d6389eac636c4c165f83f372b4361fc9bb765a5680749ee","addressRefs":[]},"eff69ee3-46bb-44c5-b7e2-df7cc9848618":{"id":"eff69ee3-46bb-44c5-b7e2-df7cc9848618","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.5","title":"Solana PYUSD","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7505,"content":"The maximum mint, burn and swap for PYUSD on Solana are located herein","contentHash":"30381ef65043e91155d6d04bccc91672f2ff86167ef94be391057f2b5cb2afc7","addressRefs":[]},"2037a597-0dd7-4887-ab21-e4a6ff103af0":{"id":"2037a597-0dd7-4887-ab21-e4a6ff103af0","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.5.1","title":"PYUSD Reserve","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7506,"content":"The maximum amount of PYUSD that can leave the PYUSD `Reserve` in aggregate across any integrations is specified in the document herein.\n\n- `maxAmount`: 25,000,000 PYUSD\n- `slope`: 10,000,000 PYUSD per day","contentHash":"c5daae833016f894173adcb329ada9dfa334419302254796e29aa884981414e6","addressRefs":[]},"9e4ef1e5-95fd-4052-ab4d-778806a4e27a":{"id":"9e4ef1e5-95fd-4052-ab4d-778806a4e27a","doc_no":"A.6.1.1.3.2.6.1.2.1.1.3.2.5.2","title":"PYUSD For USDC Swap Maximum","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7507,"content":"The maximum amount of PYUSD that can be swapped for USDC by the Keel Liquidity Layer on Solana is specified in the document herein.\n\n- `maxAmount`: 25,000,000 PYUSD\n- `slope`: 10,000,000 PYUSD per day","contentHash":"5e564386840f7b2f1210ca0ee72680f634e3aa1307fcb590596c90084efbf34b","addressRefs":[]},"09f65586-bd5d-47fc-847b-3f3c087c6b62":{"id":"09f65586-bd5d-47fc-847b-3f3c087c6b62","doc_no":"A.6.1.1.3.2.6.1.2.1.1.4","title":"On-chain Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7508,"content":"The documents herein list general on-chain parameters for the Keel Liquidity Layer.","contentHash":"d17d3ece293ca434a8dc443c10e2e75f74f1cb810345551ad7c3f1e56ce9fd39","addressRefs":[]},"6952b3d2-7b66-46ba-90f7-700f244c5ee0":{"id":"6952b3d2-7b66-46ba-90f7-700f244c5ee0","doc_no":"A.6.1.1.3.2.6.1.2.1.1.4.1","title":"Allocator Vault Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7509,"content":"The Allocator Vault parameters for ALLOCATOR-NOVA-A are defined in [A.3.7.1.2.1.3 - ALLOCATOR-NOVA-A Parameters](08321783-f31a-4a80-8f0c-898afb4d8f9b).","contentHash":"6c1da12ded23d471d81afce82871243a6e94fc57096a005694e677f2456a2486","addressRefs":[]},"810671ff-8674-4178-a7ce-dd98c112688d":{"id":"810671ff-8674-4178-a7ce-dd98c112688d","doc_no":"A.6.1.1.3.2.6.1.2.1.1.4.2","title":"Whitelisting Of ALMProxy","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7510,"content":"The ALMProxy for Keel is whitelisted on the LitePSM. This allows Keel to call `buyGemNoFee` and `sellGemNoFee` on the `MCD_LITE_PSM_USDC_A` contract.","contentHash":"aedb22b036bf81fbb376b23611121036aa0cccf7fec9e3f21ed2cbd5af58f05c","addressRefs":[]},"b319a7e6-d484-44e7-b622-6df9754c5973":{"id":"b319a7e6-d484-44e7-b622-6df9754c5973","doc_no":"A.6.1.1.3.2.6.1.2.1.1.4.3","title":"Whitelisting of Keel SubProxy Cross‑Chain Messaging","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7511,"content":"Keel’s SubProxy must be authorized by the Pause Proxy contract to send cross‑chain messages on Solana.","contentHash":"680b4d4f253b4f2f610552328d1e4541cef926d1d7a41baa5c69fdf77c8e6e31","addressRefs":[]},"21742792-9418-4857-a143-664f9d7d44d9":{"id":"21742792-9418-4857-a143-664f9d7d44d9","doc_no":"A.6.1.1.3.2.6.1.2.1.2","title":"Governance Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7512,"content":"The documents herein describe the specific governance processes for the Keel Liquidity Layer.","contentHash":"73413b6f09627f1126b06ac4c26daff4469cee69118b7f0bc56e8d7b93534268","addressRefs":[]},"ca0026a1-a4d2-4ebd-a99a-0a089dea8c82":{"id":"ca0026a1-a4d2-4ebd-a99a-0a089dea8c82","doc_no":"A.6.1.1.3.2.6.1.2.1.2.1","title":"Invoking New Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7513,"content":"The governance process to invoke a new Instance of the Allocation System Primitive follows the Root Edit process see [A.6.1.1.3.2.2.2.2.1.2 - Operational Process Definition](53987e91-b86c-42be-bb4b-20af084d622d).","contentHash":"a9d5b8d45df55ab356dc8a9d126379d32657283991630cc53c154c3b91e1bda5","addressRefs":[]},"fcdf3c3c-fc8e-4bcc-af84-4aae709d5411":{"id":"fcdf3c3c-fc8e-4bcc-af84-4aae709d5411","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2","title":"Ethereum Multisigs","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7514,"content":"The documents herein define multisigs that have privileged access to manage the Keel Liquidity Layer on Ethereum.","contentHash":"bbd5d7b68fb7167ec7fb5cdd22777cb72b8cc24f9ef8475b5e2ad2c269903c9a","addressRefs":[]},"0bdf0649-1446-4ea7-b8dd-e41dc26b9be7":{"id":"0bdf0649-1446-4ea7-b8dd-e41dc26b9be7","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.1","title":"Prime Relayer Multisig","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7515,"content":"The Prime Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.3.2.6.1.2.2.1.1.1.2 - Relayer Role](1b64d5b8-ea7d-408e-a409-3e9e72989396) and is controlled by Keel.","contentHash":"73be13cd664bdeeff12ca83e9d98c8364b3ef0054e197fac2c4c150a2ddcb5ff","addressRefs":[]},"76265560-4bc8-42fd-b5d7-85be52e11648":{"id":"76265560-4bc8-42fd-b5d7-85be52e11648","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.1.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7516,"content":"The address of the Prime Relayer Multisig on the Ethereum Mainnet is `0xA4F39dAae4Dc86c27c46b9a0605AE2c911451F95`.","contentHash":"6d58d841c6fca82869daafe4002a7e27e8ac09994f74e829dafbe480ab8a7a14","addressRefs":["0xa4f39daae4dc86c27c46b9a0605ae2c911451f95"]},"90059aef-0d59-4174-9076-e894ce9cf730":{"id":"90059aef-0d59-4174-9076-e894ce9cf730","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.1.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7517,"content":"The Prime Relayer Multisig currently has a 1/2 signing requirement.","contentHash":"c72c182f9db5e595a36418e6949dad97a031f20153b4f1b95aa235e5a462bc27","addressRefs":[]},"10d25644-72b7-406e-ac02-97a6cc31322d":{"id":"10d25644-72b7-406e-ac02-97a6cc31322d","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.1.3","title":"Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7518,"content":"The signers of the Prime Relayer Multisig are two (2) addresses controlled by Keel.","contentHash":"0fafdb04b9e9e79fcabc26385bf20fe4b8d865258d6700914dd940336124d3e1","addressRefs":[]},"c0928c5e-9679-4e4c-929e-865a15007006":{"id":"c0928c5e-9679-4e4c-929e-865a15007006","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.1.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7519,"content":"The signers of the Prime Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Keel Artifact.","contentHash":"b622cf5fd1fc80090141b62e8d43c9e49457901f2ab163e149ae91f7d4aa3db4","addressRefs":[]},"8e1357dc-80a7-4716-becf-9a50ef7ae3a0":{"id":"8e1357dc-80a7-4716-becf-9a50ef7ae3a0","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.1.5","title":"Modification","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7520,"content":"Keel can change the signers of the Prime Relayer Multisig at any time, so long as there are at least two (2) signers and at least a majority of signers are required to execute transactions.","contentHash":"76ea64583074b252d9942a12eeaa45c73308eb6b40600188c14d4f053bd8629a","addressRefs":[]},"b17a4a11-7340-4113-972d-76362f816b8a":{"id":"b17a4a11-7340-4113-972d-76362f816b8a","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.2","title":"Core Operator Relayer Multisig","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7521,"content":"The Core Operator Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.3.2.6.1.2.2.1.1.1.2 - Relayer Role](1b64d5b8-ea7d-408e-a409-3e9e72989396) and is controlled by Operational GovOps Soter Labs.","contentHash":"43b666e307760477d83a12457cf0222aa107b55ebffea4c09a8035acb3968aee","addressRefs":[]},"8028f164-6410-4f0a-bbba-dc175fc77f58":{"id":"8028f164-6410-4f0a-bbba-dc175fc77f58","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.2.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7522,"content":"The address of the Core Operator Relayer Multisig on the Ethereum Mainnet is `0x0f72935f6de6C54Ce8056FD040d4Ddb012B7cd54`.","contentHash":"6644ec1dff7f2a537b4df70e70823926ae8f8ed504678e3cadb0160dc6720139","addressRefs":["0x0f72935f6de6c54ce8056fd040d4ddb012b7cd54"]},"e92ff3c5-581b-4d5e-bab4-e244348991e4":{"id":"e92ff3c5-581b-4d5e-bab4-e244348991e4","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.2.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7523,"content":"The Core Operator Relayer Multisig currently has a 2/3 signing requirement.","contentHash":"b95f8f292db28ccf8bfd3f9a26c34232a22a6849ead7951e92687e1b4cdfd849","addressRefs":[]},"17a98019-f677-471b-aebd-7885108c614b":{"id":"17a98019-f677-471b-aebd-7885108c614b","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.2.3","title":"Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7524,"content":"The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs.","contentHash":"3f47955b9c0fde92c5560c85814bf985ea86ba974f63c359990c046ae3388a94","addressRefs":[]},"6c744f15-9dc2-47a6-b1f5-33e534697baf":{"id":"6c744f15-9dc2-47a6-b1f5-33e534697baf","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.2.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7525,"content":"The signers of the Core Operator Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Keel Artifact.","contentHash":"5e2aeff5f0f66537b81a058b35a11e3bfe7ee15886b33c68bda43667e6c27391","addressRefs":[]},"f9bf39ea-a02f-4eac-bd81-7c0b4daeb970":{"id":"f9bf39ea-a02f-4eac-bd81-7c0b4daeb970","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.2.5","title":"Modification","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7526,"content":"Operational GovOps Soter Labs can change the signers of the Core Operator Relayer Multisig at any time, so long as there are at least three (3) signers and at least two-thirds of signers are required to execute transactions.","contentHash":"050db4ce28c6bd1736123e3211a765079215503656f41e97eb06d3e0f0f22af0","addressRefs":[]},"50ef16ee-1309-4172-befa-186529eb91c3":{"id":"50ef16ee-1309-4172-befa-186529eb91c3","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.3","title":"Freezer Multisig","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7527,"content":"The Freezer Multisig has the `FREEZER_ROLE` as defined in [A.6.1.1.3.2.6.1.2.2.1.1.1.4 - Freezer Role](45b602fb-9427-4555-a3f7-8ad5b17a1cf2).","contentHash":"8a5d38f9613d8a499326d26351f401e3e68be2d9d448e846e4f84ab293a61c65","addressRefs":[]},"5a0b849f-fbfc-4a4d-88f2-d639924548bf":{"id":"5a0b849f-fbfc-4a4d-88f2-d639924548bf","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.3.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7528,"content":"The address of the Freezer Multisig on the Ethereum Mainnet is `0xBCCB60cf518391d3315D63313F7bb764d02541fE`.","contentHash":"35ec2351b7d312eaaa3c6db32551d6158bb25acd35d8f9e3d445cd10af8d380b","addressRefs":["0xbccb60cf518391d3315d63313f7bb764d02541fe"]},"354e8b0c-4883-4ae9-9d18-b95fcfe56b3c":{"id":"354e8b0c-4883-4ae9-9d18-b95fcfe56b3c","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.3.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7529,"content":"The Freezer Multisig currently has a 2/5 signing requirement.","contentHash":"5e26a52c6172c820a3edf55895c2df704dad7607cd26054763c73cd1b6fbdbc3","addressRefs":[]},"81708b61-3321-42f2-af55-204c56b32eb3":{"id":"81708b61-3321-42f2-af55-204c56b32eb3","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.3.3","title":"Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7530,"content":"The signers of the Freezer Multisig are two (2) addresses controlled by Operational GovOps Soter Labs, two (2) addresses controlled by Operational Facilitator Endgame Edge, and one (1) address controlled by Keel.","contentHash":"a3df543aed8e133ebf7c9741c7d761dac7788a4595fd9ad1ed527281ee4ad50a","addressRefs":[]},"b375c2b6-b52d-42cf-bfd3-01e46af44248":{"id":"b375c2b6-b52d-42cf-bfd3-01e46af44248","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.3.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7531,"content":"The signers of the Freezer Multisig should exercise their authority to freeze the Keel Liquidity Layer in the event that Keel is not complying with rules regarding Risk Capital or Asset Liability Management, or in the event of another emergency.\n\nEach action executed by the Freezer Multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum.","contentHash":"da6ed63b6089b57930d9e49003f626055462fe702de1fec93bb2b8cf726bacc9","addressRefs":[]},"d9ec1326-2e1c-45a9-918e-bbedfa5235c8":{"id":"d9ec1326-2e1c-45a9-918e-bbedfa5235c8","doc_no":"A.6.1.1.3.2.6.1.2.1.2.2.3.5","title":"Modification","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7532,"content":"Modification of the signers of the Freezer Multisig must be approved through an Atlas Edit Proposal.\n\nThe only exceptions to this are if: 1) a signer self-reports a loss of access to their private key due to any reason; or 2) a signer explicitly expresses their wish to be removed as a signer. In both cases, the signer is required to communicate the loss of access to their private key, or the wish to be removed as a signer, in the form of a public Sky Forum post. The specific signer should be replaced as soon as possible.\n\nAny changes to the Multisig signers that do not fall within the two exceptions listed above, or that have not been ratified by Sky Governance, should be questioned immediately and treated as malicious. Where malicious activity is suspected, the Core Facilitator must prepare an expedited Executive Vote so that Sky Governance can vote on removing external security access from the Multisig.","contentHash":"5a7d5809b6c81bb95db41542b9e9b65803e19629cf564e404811d45d7486f1e4","addressRefs":[]},"5c25417a-8698-47f4-821c-06e51e6447b6":{"id":"5c25417a-8698-47f4-821c-06e51e6447b6","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3","title":"Solana Multisigs And Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7533,"content":"The documents herein define multisigs and addresses that have privileged access to manage the Keel Liquidity Layer on Solana.","contentHash":"fa1f6300d4064c303393a5c45420dfef849b7948714d41a334938690c8861b57","addressRefs":[]},"600dfd83-d3a1-4b26-a906-c412673855b9":{"id":"600dfd83-d3a1-4b26-a906-c412673855b9","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.1","title":"Prime Primary Relayer Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7534,"content":"The Prime Primary Relayer Address holds a [A.6.1.1.3.2.6.1.2.2.2.1.1.2 - Relayer Role](2b42015c-c76a-4364-b8b5-c9a2b9f6f484) and is controlled by Keel.","contentHash":"9467569eeff0f6d6fffba80797a4dbade0e8bc3bf4e781d7e6418b424a562ed9","addressRefs":[]},"e4c22be8-bae8-45a3-9fe6-84d007282786":{"id":"e4c22be8-bae8-45a3-9fe6-84d007282786","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.1.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7535,"content":"The address of the Prime Primary Relayer is `99J5Vcf3tav2dorWmB1qxdXtD4MKk6pyayQwS8RCXZKc`.","contentHash":"800589dc20aef143a8f356df32c0dbc4b55c2990c4c3109d5a85648e60e16e81","addressRefs":["99J5Vcf3tav2dorWmB1qxdXtD4MKk6pyayQwS8RCXZKc"]},"b9643943-7dac-4ba6-bd47-56d907ed802e":{"id":"b9643943-7dac-4ba6-bd47-56d907ed802e","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.1.2","title":"State Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7536,"content":"The address of the Prime Primary Relayer’s permission configurations is `2MeJkkKPfHs6qJgTKZJGnrpq8jBRsvty6zB5iA8SkoVU`.","contentHash":"9e3c1aef509f24393241b31766c86d2a5087c25b47945236f489e9cb14b57436","addressRefs":["2MeJkkKPfHs6qJgTKZJGnrpq8jBRsvty6zB5iA8SkoVU"]},"19f801cf-4014-4ebc-8512-5e0b7efc544d":{"id":"19f801cf-4014-4ebc-8512-5e0b7efc544d","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.1.3","title":"Signer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7537,"content":"The signer of the Prime Relayer Address is controlled by Keel.","contentHash":"57cccb1f820432b0ff8cfc5e1114a9b03fb91e70c84910c10f328bd5ce9d4877","addressRefs":[]},"d5bbbab6-ab49-4b45-90c8-31c2bbce5e65":{"id":"d5bbbab6-ab49-4b45-90c8-31c2bbce5e65","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.1.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7538,"content":"The signers of the Prime Relayer Address must use it to exercise the[A.6.1.1.3.2.6.1.2.2.2.1.1.2 - Relayer Role](2b42015c-c76a-4364-b8b5-c9a2b9f6f484) in accordance with the instructions specified in the Keel Artifact.","contentHash":"57178ba1507cdc39c63efeb0fa2eb3d9b6a2f2f7d5f81e451c3729af185ac0a2","addressRefs":[]},"e7492c8c-10b6-4ee1-9d62-fb3c292f1308":{"id":"e7492c8c-10b6-4ee1-9d62-fb3c292f1308","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.1.5","title":"Modification","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7539,"content":"Changes to the Prime Relayer Addresses is a controller action which must be invoked by a [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367).","contentHash":"836ce2c375dbe0709b02b49c8ff0c300b4605a615a09130d756a98fd47568356","addressRefs":[]},"3b538bc7-3d18-4091-908d-dc0c3a6e8a62":{"id":"3b538bc7-3d18-4091-908d-dc0c3a6e8a62","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.2","title":"Prime Secondary Relayer Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7540,"content":"The Prime Secondary Relayer Address holds a [A.6.1.1.3.2.6.1.2.2.2.1.1.2 - Relayer Role](2b42015c-c76a-4364-b8b5-c9a2b9f6f484) and is controlled by Keel.","contentHash":"fa19fb0b248d382e896f3e5c2416457cdbad256c3673e6c3add5776fab92498f","addressRefs":[]},"0cacb86a-aaaa-4857-b1d5-b4ac69bf5111":{"id":"0cacb86a-aaaa-4857-b1d5-b4ac69bf5111","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.2.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7541,"content":"The address of the Prime Secondary Relayer is `2gDBGyhU8M96JDMWzCfiGb3Pw2HvrEvdL5MkfwosBYnh`.","contentHash":"4bac5a73e32a3142715ba04ae410f1b68f8c2a49886c03e5d28c65dc90a180ae","addressRefs":["2gDBGyhU8M96JDMWzCfiGb3Pw2HvrEvdL5MkfwosBYnh"]},"03cabe40-5ddf-47ef-9cf2-d2f33e8c39a1":{"id":"03cabe40-5ddf-47ef-9cf2-d2f33e8c39a1","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.2.2","title":"State Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7542,"content":"The address of the Prime Secondary Relayer’s permission configurations is `6TdcW3qX25JcN9nMgSkFka5wXTXBFhb5J2tVRdG3pw3w`.","contentHash":"319f154353e580293ef6e198b8ff9a3c74b5c9ae825c591b4895533e5e7af1aa","addressRefs":["6TdcW3qX25JcN9nMgSkFka5wXTXBFhb5J2tVRdG3pw3w"]},"35c732d2-113a-4b05-bbd1-866938c01470":{"id":"35c732d2-113a-4b05-bbd1-866938c01470","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.2.3","title":"Signer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7543,"content":"The signer of the Prime Relayer Address is controlled by Keel.","contentHash":"57cccb1f820432b0ff8cfc5e1114a9b03fb91e70c84910c10f328bd5ce9d4877","addressRefs":[]},"3ca26d03-bb4d-4fe0-8f3f-3f9e6d92e2ed":{"id":"3ca26d03-bb4d-4fe0-8f3f-3f9e6d92e2ed","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.2.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7544,"content":"The signers of the Prime Relayer Address must use it to exercise the [A.6.1.1.3.2.6.1.2.2.2.1.1.2 - Relayer Role](2b42015c-c76a-4364-b8b5-c9a2b9f6f484) in accordance with the instructions specified in the Keel Artifact.","contentHash":"ebcd29accce6410b8d80a1434cf2551143fc9d53866c56dadb09b0df24715675","addressRefs":[]},"e471ce78-e775-4aff-a331-7e581a4606e6":{"id":"e471ce78-e775-4aff-a331-7e581a4606e6","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.2.5","title":"Modification","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7545,"content":"Changes to the Prime Relayer Addresses is a controller action which must be invoked by a [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367).","contentHash":"836ce2c375dbe0709b02b49c8ff0c300b4605a615a09130d756a98fd47568356","addressRefs":[]},"ced26169-892b-4ec4-9a16-8fb90e94a9ef":{"id":"ced26169-892b-4ec4-9a16-8fb90e94a9ef","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.3","title":"Core Operator Relayer Multisig","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7546,"content":"The Core Operator Relayer Multisig holds a [A.6.1.1.3.2.6.1.2.2.2.1.1.2 - Relayer Role](2b42015c-c76a-4364-b8b5-c9a2b9f6f484) and is controlled by Operational GovOps Soter Labs.","contentHash":"1841b3a94316923e7eb07c8831aa4803cfed78407885e70e1d7aef98fe733b99","addressRefs":[]},"f027ec03-4e5a-4262-9992-07fab72dc014":{"id":"f027ec03-4e5a-4262-9992-07fab72dc014","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.3.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7547,"content":"The address of the Core Operator Relayer Multisig on Solana is `7JvfSy4mWcw1EAy7vjvsHnKeC28UZeAURhVi4nQjUM6h`.","contentHash":"3f2a7000295e5138bbed747dcaaf7392633f9602ace039079a42c93d1ab96309","addressRefs":["7JvfSy4mWcw1EAy7vjvsHnKeC28UZeAURhVi4nQjUM6h"]},"310849fb-a67d-4e9a-aadb-8c39ff2a8b8e":{"id":"310849fb-a67d-4e9a-aadb-8c39ff2a8b8e","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.3.2","title":"State Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7548,"content":"The address of the Core Operator Relayer’s permission configurations is `2YLLgUuWHwf8hFnWXWUL9V5Vk68yBswVtJED1h4vnPjX`.","contentHash":"ab0a1d484d9ad79fc32887cf60b0f08f3135e296f9ab87d10747dc1e633362e8","addressRefs":["2YLLgUuWHwf8hFnWXWUL9V5Vk68yBswVtJED1h4vnPjX"]},"e8868f7c-3033-4355-9f87-81956961bedb":{"id":"e8868f7c-3033-4355-9f87-81956961bedb","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.3.3","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7549,"content":"The Core Operator Relayer Multisig currently has a 2/3 signing requirement.","contentHash":"b95f8f292db28ccf8bfd3f9a26c34232a22a6849ead7951e92687e1b4cdfd849","addressRefs":[]},"08036115-62a3-40c8-9b70-61f8dc38035c":{"id":"08036115-62a3-40c8-9b70-61f8dc38035c","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.3.4","title":"Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7550,"content":"The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs.","contentHash":"3f47955b9c0fde92c5560c85814bf985ea86ba974f63c359990c046ae3388a94","addressRefs":[]},"f2730835-93da-4616-989d-a38f1bd6416a":{"id":"f2730835-93da-4616-989d-a38f1bd6416a","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.3.5","title":"Usage Standards","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7551,"content":"The signers of the Core Operator Relayer Multisig must use the Multisig to exercise the Relayer Role in accordance with the instructions specified in the Keel Artifact.","contentHash":"c16955d6d8f69648d1ed2af9cd33d9bbdaa08859233e95f175d599b0d2772f63","addressRefs":[]},"2cf82458-eae4-4fad-9504-0fee8effd172":{"id":"2cf82458-eae4-4fad-9504-0fee8effd172","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.3.6","title":"Modification","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7552,"content":"Operational GovOps Soter Labs can change the signers of the Core Operator Relayer Multisig at any time, so long as there are at least three (3) signers and at least two thirds of signers are required to execute transactions.","contentHash":"000b84b3f38f0919060dc840a7e0f8e93a32658e543a2e8b1c596470ddf8341f","addressRefs":[]},"aeee4280-ab46-4269-9430-fef8c2ee6d43":{"id":"aeee4280-ab46-4269-9430-fef8c2ee6d43","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.4","title":"Freezer Multisig","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7553,"content":"The Freezer Multisig has the `FREEZER_ROLE` as defined in [A.6.1.1.3.2.6.1.2.2.2.1.1.3 - Freezer Role](6f7becc7-2e70-44e5-8662-25ba7dd1a5f8).","contentHash":"7f7bbad98e5931e3777d8536b34ad10d282689bcbc96632556db22244fe4cc93","addressRefs":[]},"b76dbc30-602e-4464-b797-8b6643d8e2b8":{"id":"b76dbc30-602e-4464-b797-8b6643d8e2b8","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.4.1","title":"Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7554,"content":"The address of the Freezer Multisig on Solana is `AUAJeXgLDNoDbBZ1uRguj9hWDZJSQkmoy4xk9U5zJF8h`.","contentHash":"f4d2c9e1fe34c0351933ac4c221977b0e73507f92bdc912636b089c0188d8246","addressRefs":["AUAJeXgLDNoDbBZ1uRguj9hWDZJSQkmoy4xk9U5zJF8h"]},"f9d1c2bc-5903-4581-9b0d-9c68f7c64ac8":{"id":"f9d1c2bc-5903-4581-9b0d-9c68f7c64ac8","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.4.2","title":"State Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7555,"content":"The address of the Freezer Multisig permission configurations is `B24DtbKAV25fcZ6e3buqfB8CSuuiFLRsHHojBGigntff`.","contentHash":"3f570c128df2e851abd1c63418d640d31d45ff65caad443abb5ee693b5637398","addressRefs":["B24DtbKAV25fcZ6e3buqfB8CSuuiFLRsHHojBGigntff"]},"c900500f-d44a-4c6f-9429-032a28262b68":{"id":"c900500f-d44a-4c6f-9429-032a28262b68","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.4.3","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7556,"content":"The Freezer Multisig currently has a 2/5 signing requirement.","contentHash":"5e26a52c6172c820a3edf55895c2df704dad7607cd26054763c73cd1b6fbdbc3","addressRefs":[]},"e6c86321-bef0-435c-a2db-2b82dc7f1c77":{"id":"e6c86321-bef0-435c-a2db-2b82dc7f1c77","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.4.4","title":"Signers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7557,"content":"The signers of the Freezer Multisig are two (2) addresses controlled by Operational GovOps Soter Labs, two (2) addresses controlled by Operational Facilitator Endgame Edge, and one (1) address controlled by Keel.","contentHash":"a3df543aed8e133ebf7c9741c7d761dac7788a4595fd9ad1ed527281ee4ad50a","addressRefs":[]},"9a900853-f703-4454-92bf-416fbb157aea":{"id":"9a900853-f703-4454-92bf-416fbb157aea","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.4.5","title":"Usage Standards","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7558,"content":"The signers of the Freezer Multisig should exercise their authority to freeze the Keel Liquidity Layer in the event that Keel is not complying with rules regarding Risk Capital or Asset Liability Management, or in the event of another emergency.\n\nEach action executed by the Freezer Multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum.","contentHash":"da6ed63b6089b57930d9e49003f626055462fe702de1fec93bb2b8cf726bacc9","addressRefs":[]},"6369ddc9-8898-40b3-b454-c324c75d7d39":{"id":"6369ddc9-8898-40b3-b454-c324c75d7d39","doc_no":"A.6.1.1.3.2.6.1.2.1.2.3.4.6","title":"Modification","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7559,"content":"Modification of the signers of the Freezer Multisig must be approved through an Atlas Edit Proposal.\n\nThe only exceptions to this are if: 1) a signer self-reports a loss of access to their private key due to any reason; or 2) a signer explicitly expresses their wish to be removed as a signer. In both cases, the signer is required to communicate the loss of access to their private key, or the wish to be removed as a signer, in the form of a public Sky Forum post. The specific signer should be replaced as soon as possible.\n\nAny changes to the Multisig signers that do not fall within the two exceptions listed above, or that have not been ratified by Sky Governance, should be questioned immediately and treated as malicious. Where malicious activity is suspected, the Core Facilitator must prepare an expedited Executive Vote so that Sky Governance can vote on removing external security access from the Multisig.","contentHash":"5a7d5809b6c81bb95db41542b9e9b65803e19629cf564e404811d45d7486f1e4","addressRefs":[]},"921ca242-451a-4013-90b4-611696fb1a41":{"id":"921ca242-451a-4013-90b4-611696fb1a41","doc_no":"A.6.1.1.3.2.6.1.2.1.3","title":"Total Risk Capital (TRC) Management","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7560,"content":"The documents herein specify requirements related to Keel’s Total Risk Capital (TRC) management.","contentHash":"8f2a6c0c95436db2dbdf6f0b1c921b900622369e1203763186782e012a75ce4d","addressRefs":[]},"e6b81e35-8a04-4d66-ac37-80b0a91d553b":{"id":"e6b81e35-8a04-4d66-ac37-80b0a91d553b","doc_no":"A.6.1.1.3.2.6.1.2.1.3.1","title":"Keel’s Operation Of Keel Liquidity Layer And Agreement Regarding Encumbrance Ratio","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7561,"content":"Keel will operate the Keel Liquidity Layer and agrees to stay at or below a 90% Encumbrance Ratio. See[A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9).","contentHash":"36fca3e88462a779b2a0f7fce7ba0c059e413d0b7f625a9587b1d183a30f03e8","addressRefs":[]},"afdffc09-3a0f-450f-beb8-e4a5107b434c":{"id":"afdffc09-3a0f-450f-beb8-e4a5107b434c","doc_no":"A.6.1.1.3.2.6.1.2.1.3.2","title":"Keel’s Total Risk Capital (TRC) Management Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7562,"content":"As operators of the Keel Liquidity Layer, Keel automatically inherits, and is subject to, the base class of operational requirements related to Total Risk Capital management defined in [A.2.2.9.1.1.3.2.1.2 - Primes' Total Risk Capital (TRC) Management](3af8a3a2-25e5-44b3-87a4-7df1f2712685). Modifications to the base operational logic automatically propagate to the Keel Artifact.","contentHash":"3bdd9f2b33f9fc42da0afdc7d4d03997be5f42f559b034d824ed8b655be5c3cc","addressRefs":[]},"44a6cfcc-26d3-414b-99a7-cf57d2b6c5d6":{"id":"44a6cfcc-26d3-414b-99a7-cf57d2b6c5d6","doc_no":"A.6.1.1.3.2.6.1.2.2","title":"Keel Liquidity Layer Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7563,"content":"The documents herein describe common operational procedures for the Keel Liquidity Layer applicable across multiple Instances.","contentHash":"3f4f7f1aa95d64249bdb0599e146f5f3dc71707d76a6ed5e9d9f7d1033df7b2c","addressRefs":[]},"d0dd4281-e342-43d9-9aa7-41d42ee6279d":{"id":"d0dd4281-e342-43d9-9aa7-41d42ee6279d","doc_no":"A.6.1.1.3.2.6.1.2.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7564,"content":"The documents herein describe common operational procedures for the Keel Liquidity Layer applicable across multiple Instances on Ethereum Mainnet.","contentHash":"7eb0dd948016359a8372b4814698ff9f4c84704cd71ccb621773f80c6ad56dc2","addressRefs":[]},"0a382c05-5a2b-43a5-83ac-94032e065094":{"id":"0a382c05-5a2b-43a5-83ac-94032e065094","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7565,"content":"The documents herein define the protocol for routine ongoing management of the Keel Liquidity Layer and its active Instances on Ethereum Mainnet.","contentHash":"c990d6b9ca23e68eec48e6c77f5ea333da829a923727816ed92b5866da211cef","addressRefs":[]},"70617021-ff70-4a9b-97aa-56be5ec2038d":{"id":"70617021-ff70-4a9b-97aa-56be5ec2038d","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.1","title":"Role Hierarchy And Permissions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7566,"content":"The documents herein define roles (Admin, Relayer, ALM Controller and Freezer) and their responsibilities/permissions for managing the Keel Liquidity Layer.","contentHash":"9392ab56e7fe0ebcfd7cf63e16946468a7dc2abd9d06e5ae866a527fe18d2fc2","addressRefs":[]},"26cac5a1-6313-4aff-952c-70eb84513815":{"id":"26cac5a1-6313-4aff-952c-70eb84513815","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.1.1","title":"Default Admin Role","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7567,"content":"The admin role (`DEFAULT_ADMIN_ROLE`) is the role that can grant and revoke any role, including itself and all other roles defined in the contract. The admin role is also used for general admin functions in all contracts. This role is fully controlled by Sky Governance via the Keel Proxy.\n\n```\nconstructor(address admin) {\n_grantRole(DEFAULT_ADMIN_ROLE, admin);\n```","contentHash":"54a0d753d9b68e11e625de4b75dfd035e4e214c4fc2d69126ae90796f2be0523","addressRefs":[]},"1b64d5b8-ea7d-408e-a409-3e9e72989396":{"id":"1b64d5b8-ea7d-408e-a409-3e9e72989396","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.1.2","title":"Relayer Role","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7568,"content":"The `RELAYER_ROLE` is the address for the Keel Liquidity Layer ALM Planner off-chain system that calls functions on `Controller` contracts to perform actions on behalf of the `ALMProxy` contract. The Relayer Role may be granted to an address by any address holding the `DEFAULT_ADMIN_ROLE`. The Relayer Role may be removed from an address by any address holding the `DEFAULT_ADMIN_ROLE` or the `FREEZER_ROLE`.","contentHash":"c8ca5899cdd16c21caeef2916cd983a88d4f258b9329376e46a09e0e23a62129","addressRefs":[]},"6ebd37e7-5234-4ac6-a48b-b75e86f29e82":{"id":"6ebd37e7-5234-4ac6-a48b-b75e86f29e82","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.1.3","title":"ALM Controller Role","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7569,"content":"The `ALM_CONTROLLER_ROLE` is the address of the role that can call the `call` functions on the `ALMProxy` contract and update `RateLimits` contract. It includes the `MainnetController` and `ForeignController` contracts. ALM Controller contracts are accessed and modified via the Relayer Role.","contentHash":"2338ec34a7da2944765e15ca9792b0c4ec0cffcbf72218d25d3c57bffdc821f2","addressRefs":[]},"45b602fb-9427-4555-a3f7-8ad5b17a1cf2":{"id":"45b602fb-9427-4555-a3f7-8ad5b17a1cf2","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.1.4","title":"Freezer Role","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7570,"content":"The `FREEZER_ROLE` is the address of the emergency role that can remove a compromised Relayer.","contentHash":"5613adb996d95581a1f27d5ec22a32a62f59e9d8f62e6ff43f248f6bd75f410f","addressRefs":[]},"777db288-7558-4e07-b649-fbf15c7ab202":{"id":"777db288-7558-4e07-b649-fbf15c7ab202","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2","title":"Controller Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7571,"content":"The documents herein describe the purpose and operational use of key functions within Keel Liquidity Layer `MainnetController` contracts: USDS management (mint/burn USDS), Asset Transfer Management (direct transfers, protocol deposits/withdrawals), Cross-chain Operations (CCTP bridging)","contentHash":"588aff15fdc5c99a400d02ab3b0c13228e4f7097be60a45f106d89ffc9c4c909","addressRefs":[]},"93b5cec4-1398-4adf-a14f-3c8fb5281cc9":{"id":"93b5cec4-1398-4adf-a14f-3c8fb5281cc9","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1","title":"Mainnet Controller Contract Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7572,"content":"The documents herein define the functions controlled by the Controller contract for Keel Liquidity Layer operations on Ethereum Mainnet.","contentHash":"ad4c1bf31a9a21d2fc4a4a7606233624fe33e1fab058b88aa7e5f91377991acd","addressRefs":[]},"91ed43a8-98d6-4954-8d4d-a79e49d17cbe":{"id":"91ed43a8-98d6-4954-8d4d-a79e49d17cbe","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.1","title":"Admin Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7573,"content":"The documents herein define the operations performed by the admin role (see [A.6.1.1.3.2.6.1.2.2.1.1.1.1 - Default Admin Role](26cac5a1-6313-4aff-952c-70eb84513815)) within the `MainnetController` contract.","contentHash":"330a42afc4b1623e506638ef34e0c77ef0fbfe012824e3ae13d2e472758aad26","addressRefs":[]},"d54329a6-eeaa-4741-9518-d7d24e2d418c":{"id":"d54329a6-eeaa-4741-9518-d7d24e2d418c","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.1.1","title":"Set Mint Recipient For Destination Domain","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7574,"content":"The documents herein define the steps for an admin to specify which address should receive newly minted tokens on a particular destination domain.","contentHash":"e18d032726334c884a3fef8347d5e82a077819f279c99e6388f0e0e6e6c17199","addressRefs":[]},"0d2d22cf-1ee4-44ee-8e10-95f516da51a9":{"id":"0d2d22cf-1ee4-44ee-8e10-95f516da51a9","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.1.1.1","title":"Call setMintRecipient Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7575,"content":"Only an operator with the admin role is able to set the mint recipient for a destination domain. To do so, they must call the `setMintRecipient` function on the Controller contract on mainnet providing the destination domain and the mint recipient address. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role the transaction will revert.\n- The contract will set the selected mint recipient for the specified destination domain.\n- The contract will emit a `MintRecipientSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setMintRecipient(uint32 destinationDomain, bytes32 mintRecipient) external`","contentHash":"62ff9aed370987d09554d45ed885419834c3a8d1ec5fb30268034f868b811e24","addressRefs":[]},"753bcc77-e4a6-438b-942c-bf2b4ef908be":{"id":"753bcc77-e4a6-438b-942c-bf2b4ef908be","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.1.2","title":"Set LayerZero Recipient","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7576,"content":"The documents herein define the steps for an admin to specify which address should receive LayerZero messages on a particular destination endpoint.","contentHash":"529b6a0e9f1b8e61a703349f93f307fde7ab7e28b97bc74b29a3dc4b391b9058","addressRefs":[]},"aceb66dc-7349-4d49-a893-7ed417e83797":{"id":"aceb66dc-7349-4d49-a893-7ed417e83797","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.1.2.1","title":"Call setLayerZeroRecipient Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7577,"content":"Only an operator with the admin role is able to set the LayerZero recipient for a destination endpoint. To do so, they must call the `setLayerZeroRecipient` function on the Controller contract on mainnet, providing the destination endpoint ID and the recipient address. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role, the transaction will revert.\n- The contract will set the selected LayerZero recipient for the specified destination endpoint.\n- The contract will emit a `LayerZeroRecipientSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setLayerZeroRecipient(uint32 destinationEndpointId, bytes32 layerZeroRecipient) external`","contentHash":"1a37c01cad0a4ff26a1f5c94db71a0ff3916acb7beca0e135db6a9505a0f1a63","addressRefs":[]},"323bb906-f37c-470d-8124-b133a050ffa6":{"id":"323bb906-f37c-470d-8124-b133a050ffa6","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.1.3","title":"Set Maximum Slippage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7578,"content":"The documents herein define the steps for an admin to set the maximum allowed slippage for a specific pool.","contentHash":"4c5e57348afcaa8e60130af9381c39d20bd2adbbc775d02aaedcfaa0fefeea09","addressRefs":[]},"8838da61-5edf-4ad5-b910-d4536aecd822":{"id":"8838da61-5edf-4ad5-b910-d4536aecd822","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.1.3.1","title":"Set The Maximum Slippage Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7579,"content":"Only an operator with the admin role is able to set the maximum slippage for a pool. To do so, they must call the `setMaxSlippage` function on the Controller contract on mainnet, providing the pool address and the maximum slippage value. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role, the transaction will revert.\n- The contract will set the maximum slippage for the specified pool.\n- The contract will emit a `MaxSlippageSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setMaxSlippage(address pool, uint256 maxSlippage) external`","contentHash":"9a27132420655c07a094df4efaba7ce834dd51c5e50556195377ccbbad5a46b6","addressRefs":[]},"0a7927fb-3301-423a-9b8f-6eff2c995dd0":{"id":"0a7927fb-3301-423a-9b8f-6eff2c995dd0","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2","title":"Relayer Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7580,"content":"The documents herein define the operations performed by the relayer role (see [A.6.1.1.3.2.6.1.2.2.1.1.1.2 - Relayer Role](1b64d5b8-ea7d-408e-a409-3e9e72989396)) within the `MainnetController` contract.","contentHash":"e02cdc1ec54e09e29d47b00c2c7cd1dd7ee27043ee4658ddccdb24938c1a832d","addressRefs":[]},"1a335368-4c05-49b1-b5fb-e0a9c572b28c":{"id":"1a335368-4c05-49b1-b5fb-e0a9c572b28c","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.1","title":"Relayer Vault Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7581,"content":"The documents herein define the operations that are performed to maintain the desired level of liquidity and debt balance of the Keel Liquidity Layer.","contentHash":"38e99c69c46c555d435cbb6a246dee214cda75f41c4d862dbc635eda1b78f3fe","addressRefs":[]},"6090ffba-788d-465c-b5d9-34e710745647":{"id":"6090ffba-788d-465c-b5d9-34e710745647","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.1.1","title":"Mint USDS","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7582,"content":"The documents herein define the steps for a relayer to mint USDS from the Sky Allocation Vault to the Keel ALM Proxy.","contentHash":"a329a889c3ba0afdd4d864ec0c65ee849ef1d751288d4439a02d8bd166814185","addressRefs":[]},"768ca90b-8432-456c-8f75-2469514d6969":{"id":"768ca90b-8432-456c-8f75-2469514d6969","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.1.1.1","title":"Call mintUSDS Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7583,"content":"Only an operator with the relayer role is able to mint USDS. To do so, they must call the mintUSDS function on the Controller contract on mainnet with the amount of USDS that is required for minting. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will ensure the `RateLimits` allow for minting the required amount. If the mint amount does not fall within the available Rate Limit the transaction will revert.\n- The contract will reduce the Rate Limit by the amount of USDS minted in this transaction.\n- The contract will mint the required USDS into the buffer contract.\n- The contract will transfer the newly minted USDS from the buffer to the Proxy.\n\nThe function call is as follows:\n\n`function mintUSDS(uint256 usdsAmount) external`","contentHash":"4a92d027ac25de66e3cad6a6e6f004a296bff56fc0060aae7ee62769d37ac12c","addressRefs":[]},"9c9536a8-bb2d-4d37-98cf-4c25a5699026":{"id":"9c9536a8-bb2d-4d37-98cf-4c25a5699026","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.1.2","title":"Burn USDS","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7584,"content":"The documents herein define the steps for a relayer to return and then burn Keel’s USDS debt in the Sky Allocation Vault.","contentHash":"62719a0deb1c904bb8d265190a0df5ad381a702e746bc3c58fb979f61fd85277","addressRefs":[]},"59b093a0-9025-4c60-ba6f-7a2e78a35ed4":{"id":"59b093a0-9025-4c60-ba6f-7a2e78a35ed4","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.1.2.1","title":"Call burnUSDS Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7585,"content":"Only an operator with the relayer role is able to repay vault debt and burn USDS. To do so, they must call the burnUSDS function of the Controller contract on mainnet with the amount of USDS that they wish to burn. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will increase the available Rate Limit for minting USDS by the amount of USDS being burned. This increase will be limited by the maxAmount parameter in the `Rate Limit` contract.\n- The contract will transfer USDS from the proxy to the buffer.\n- The contract will burn the USDS from the buffer and `wipe` an equivalent amount from the vault's debt.\n\nThe function call is as follows:\n\n`function burnUSDS(uint256 usdsAmount) external`","contentHash":"37e9ad1c273f11c34b2341776d2583d48e5f240aa11745e705eda0d509c506cd","addressRefs":[]},"7f8d8294-d5d6-437e-aae1-a1ee36c11e7e":{"id":"7f8d8294-d5d6-437e-aae1-a1ee36c11e7e","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.2","title":"ERC-20 Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7586,"content":"The documents herein define the operations that are performed to transfer ERC-20 assets to specified destinations.","contentHash":"d28c31b8ab0d83cf03cc2fc4bd3b795529ab9c078d5d41f64515b4e63120219b","addressRefs":[]},"0a409cf8-a66d-4fd4-beaf-ca518eaa77c1":{"id":"0a409cf8-a66d-4fd4-beaf-ca518eaa77c1","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.2.1","title":"Transfer Asset","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7587,"content":"The documents herein define the steps for a relayer to transfer ERC-20 tokens to a destination address.","contentHash":"88a951aa42193ef6d8f1c08721493c83b1b360651c00ac25507f0762fba7f268","addressRefs":[]},"fa55c1fb-83b5-4f73-a7a4-116d2c7814dd":{"id":"fa55c1fb-83b5-4f73-a7a4-116d2c7814dd","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.2.1.1","title":"Call transferAsset Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7588,"content":"Only an operator with the relayer role is able to transfer ERC-20 assets. To do so, they must call the `transferAsset` function on the Controller contract on mainnet, providing the ERC20 asset address, the destination address, and the amount to transfer. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will ensure the `RateLimits` allow for transferring the specified amount of the asset to the destination. If the transfer amount does not fall within the available Rate Limit, the transaction will revert.\n- The contract will execute the ERC-20 `transfer` function, sending the specified amount of the asset to the destination address.\n\nThe function call is as follows:\n\n`function transferAsset(address asset, address destination, uint256 amount) external`","contentHash":"a37fa4e3d9bcbef21e11a96c66528873e5067e6e764388d79dc367fc6a153b48","addressRefs":[]},"3de32801-e895-4a21-84da-aa5818d16349":{"id":"3de32801-e895-4a21-84da-aa5818d16349","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3","title":"ERC-4626 Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7589,"content":"The documents herein define the general Keel Liquidity Layer operational procedures for interacting with ERC-4626-compliant tokenized vaults. ERC-4626 is a standard interface for vaults representing shares of an underlying ERC-20 token. Keel Liquidity Layer can integrate with various ERC-4626 vaults. For instance-specific parameters (such as vault addresses, asset addresses, and rate limits), refer to the relevant ERC-4626 Instance Configuration Document.","contentHash":"22a78b96057c885d562bc39de9c7208298dd84f810c3699f2f87d57089655b84","addressRefs":[]},"a01273a3-0fc3-44ce-931a-cdc3d3983a73":{"id":"a01273a3-0fc3-44ce-931a-cdc3d3983a73","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3.1","title":"Deposit To ERC-4626 Vault","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7590,"content":"The documents herein define the steps for a relayer to deposit assets from the ALM Proxy to an ERC-4626 vault to receive yield-bearing shares.","contentHash":"b80f044c9242551c8ee6c4a30ae6071bbb378ef9d152494b757f8036bf9763bf","addressRefs":[]},"4e2c13af-7f66-4b87-9662-693e94212c28":{"id":"4e2c13af-7f66-4b87-9662-693e94212c28","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3.1.1","title":"Call depositERC4626 Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7591,"content":"Only an operator with the relayer role can deposit assets into an ERC-4626 vault. To do so, they must call the `depositERC4626` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to deposit. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for deposit; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the deposit amount is within the allowed rate limit for the specified vault.\n- The contract will approve the vault to spend the underlying asset from the ALM Proxy. The approval and deposit are both performed from the ALM Proxy address.\n- The contract will deposit the specified amount into the vault, and the ALM Proxy will receive the corresponding number of vault shares.\n\nThe function call is as follows:\n\n`function depositERC4626(address token, uint256 amount) external returns (uint256 shares)`","contentHash":"ce859456b41c25d101cea8acf861db4d9b2079df36be9ee6d72c46f6ae166e11","addressRefs":[]},"ad2c7a22-96aa-428d-a373-b92fec3b529f":{"id":"ad2c7a22-96aa-428d-a373-b92fec3b529f","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3.2","title":"Withdraw From ERC-4626 Vault","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7592,"content":"The documents herein define the steps for a relayer to withdraw a specified amount of the underlying asset from an ERC-4626 vault to the ALM Proxy.","contentHash":"b0fc494301a22c5aacd7e45e8742053e4e6ca1a382f8669ace79fb27c6907dee","addressRefs":[]},"37c09b7c-6aa0-4c3c-861e-984de4e3ba4d":{"id":"37c09b7c-6aa0-4c3c-861e-984de4e3ba4d","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3.2.1","title":"Call withdrawERC4626 Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7593,"content":"Only an operator with the relayer role can withdraw assets from an ERC-4626 vault. To do so, call the `withdrawERC4626` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to withdraw. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for withdrawal; otherwise, the transaction will revert. When this function is called:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the withdrawal amount is within the allowed rate limit for the specified vault.\n- The contract will withdraw the specified amount from the vault, burning the necessary number of vault shares held by the ALM Proxy as part of the withdrawal process.\n- The withdrawn assets will be sent to the ALM Proxy.\n\nThe function call is as follows:\n\n`function withdrawERC4626(address token, uint256 amount) external returns (uint256 shares)`","contentHash":"7d60d5666bf23f665a8546f1008c2a7bd850d383f8f4d55085337926096ac692","addressRefs":[]},"eec2b12a-6578-483a-824e-1442f3b0410c":{"id":"eec2b12a-6578-483a-824e-1442f3b0410c","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3.3","title":"Redeem ERC-4626 Shares","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7594,"content":"The documents herein define the steps for a relayer to redeem vault shares for the underlying asset from an ERC-4626 vault, with the assets sent to the ALM Proxy.","contentHash":"2c3c0a01bfb509b9b3c8f2081f53ed39ef0c035badaffa3c291d5974aed7638d","addressRefs":[]},"a6474ee7-317b-430b-abd7-bf81a50ca898":{"id":"a6474ee7-317b-430b-abd7-bf81a50ca898","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3.3.1","title":"Call redeemERC4626 Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7595,"content":"Only an operator with the relayer role can redeem vault shares for the underlying asset. To do so, they must call the `redeemERC4626` function on the Controller contract on mainnet, providing the number of shares to redeem. The address is the ALM Proxy acting as both the owner of the shares being redeemed and the receiver of the resulting assets. The operation will only succeed if the ALM Proxy holds at least the number of shares specified for redemption; otherwise, the transaction will revert. When this function is called:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will redeem the specified number of shares from the vault, sending the resulting assets to the ALM Proxy.\n- After redemption, the contract will update the withdrawal rate limit based on the amount of assets received.\n\nThe function call is as follows:\n\n`function redeemERC4626(address token, uint256 shares) external returns (uint256 assets)`","contentHash":"58a11a4ed299088cf7e8956cafcd462d18757b226cf24f29028b3be6686b9f4c","addressRefs":[]},"ff9638aa-a4d5-4a5e-a2bb-9b924b9987f9":{"id":"ff9638aa-a4d5-4a5e-a2bb-9b924b9987f9","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.4","title":"ERC-7540 Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7596,"content":"The documents herein define the general Keel Liquidity Layer operational procedures for interacting with ERC-7540-compliant tokenized vaults. ERC-7540 is a standard interface for vaults representing and managing multiple underlying assets within a single vault. Keel Liquidity Layer can integrate with various ERC-7540 vaults. For instance-specific parameters (such as vault addresses, asset addresses, and rate limits), refer to the relevant ERC-7540 Instance Configuration Document.","contentHash":"bc41b1f71a0d0d9801228053d3203d6a3b2c79ebddde5147531ea73fc5de42d3","addressRefs":[]},"0ab348c1-50f9-4215-a78b-2b9dcf22aa03":{"id":"0ab348c1-50f9-4215-a78b-2b9dcf22aa03","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.4.1","title":"Deposit To ERC-7540 Vault","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7597,"content":"The documents herein define the steps for a relayer to request and claim deposit of assets from the ALM Proxy to an ERC-7540 vault.","contentHash":"7774d3c7628aa70e17667f0cdf5e7bf69930a59961e22efb75639f71a1b01a91","addressRefs":[]},"e86cf2c1-31f6-4f83-8120-89b52611adae":{"id":"e86cf2c1-31f6-4f83-8120-89b52611adae","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.4.1.1","title":"Call requestDepositERC7540 Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7598,"content":"Only an operator with the relayer role can request a deposit into an ERC-7540 vault. To do so, they must call the `requestDepositERC7540` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to deposit. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for deposit; otherwise, the transaction will revert. The Rate Limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the deposit amount is within the allowed rate limit for the specified vault.\n- The contract will approve the vault to spend the underlying asset from the ALM Proxy. The approval and deposit request are both performed from the ALM Proxy address.\n- The contract will submit a deposit request to the vault. Shares will not be received immediately; they must be claimed in a separate step after the vault processes the deposit.\n\nThe function call is as follows:\n\n`function requestDepositERC7540(address token, uint256 amount) external`","contentHash":"7d94cd4feb63f0c6a54ba49c0bdf82e0dfde2f89e9c0299f7b1504423722b541","addressRefs":[]},"cb81a01a-74b8-4e35-a83d-0848dd1f9f14":{"id":"cb81a01a-74b8-4e35-a83d-0848dd1f9f14","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.4.1.2","title":"Call claimDepositERC7540 Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7599,"content":"Only an operator with the relayer role can claim shares from an ERC-7540 vault after a deposit request. To do so, they must call the `claimDepositERC7540` function on the Controller contract on mainnet, providing the vault token address. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will determine the maximum number of shares that can be claimed by the ALM Proxy.\n- The contract will claim the shares from the vault, and the ALM Proxy will receive the corresponding number of vault shares.\n\nThe function call is as follows:\n\n`function claimDepositERC7540(address token) external`","contentHash":"cf9133aff1f7250ddcc482b8ca1ac5626e3b1c19496455585148659e91593e03","addressRefs":[]},"7077efbf-91fb-402c-831f-8f15e13f0a6a":{"id":"7077efbf-91fb-402c-831f-8f15e13f0a6a","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.4.2","title":"Redeem From ERC-7540 Vault","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7600,"content":"The documents herein define the steps for a relayer to request and redeem vault shares for the underlying asset from an ERC-7540 vault, with the assets sent to the ALM Proxy.","contentHash":"0405683434d72ead3b6f43e52f1ee95b114f0b3fc58535114ce95cedd58d400f","addressRefs":[]},"19e6bba4-8d6f-4d1c-95d5-000b2dbf948c":{"id":"19e6bba4-8d6f-4d1c-95d5-000b2dbf948c","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.4.2.1","title":"Call requestRedeemERC7540 Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7601,"content":"Only an operator with the relayer role can request the redemption of shares from an ERC-7540 vault. To do so, they must call the `requestRedeemERC7540` function on the Controller contract on mainnet, providing the vault token address and the number of shares to redeem. The rate limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the redemption amount is within the allowed rate limit for the specified vault.\n- The contract will submit a redemption request to the vault. Assets will not be received immediately; they must be claimed in a separate step after the vault processes the redemption.\n\nThe function call is as follows:\n\n`function requestRedeemERC7540(address token, uint256 amount) external`","contentHash":"77cbcc6045b6a4abbab0211e3cbf383430e14fbda5a8d961e908aa886582ef4e","addressRefs":[]},"9b43cc7e-dfb9-4868-b9a6-8848c837691b":{"id":"9b43cc7e-dfb9-4868-b9a6-8848c837691b","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.4.2.2","title":"Call claimRedeemERC7540 Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7602,"content":"Only an operator with the relayer role can claim assets from an ERC-7540 vault after a redemption request. To do so, they must call the `claimRedeemERC7540` function on the Controller contract on mainnet, providing the vault token address. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will determine the maximum amount of assets that can be claimed by the ALM Proxy.\n- The contract will claim the assets from the vault, and the ALM Proxy will receive the corresponding amount of underlying assets.\n\nThe function call is as follows:\n\n`function claimRedeemERC7540(address token) external`","contentHash":"5e009dff8fc6a052984c70afd928dea021c7163bba2ae9249ad9d17a3b1a0b34","addressRefs":[]},"19d426c4-9846-4ea8-91f7-5b6d71055491":{"id":"19d426c4-9846-4ea8-91f7-5b6d71055491","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5","title":"PSM Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7603,"content":"The documents herein define the swap operations performed by the Keel Liquidity Layer in the PSM.","contentHash":"7f14b51e6966e83654fcf5e19c9f9b376adfb36d89559eef5420d3ebf676df44","addressRefs":[]},"cb52a3c2-6b2a-43a0-b2e0-728101c409bd":{"id":"cb52a3c2-6b2a-43a0-b2e0-728101c409bd","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.1","title":"Swap USDS To USDC","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7604,"content":"The documents herein define a series of operations for an operator to `swap` USDS to USDC through the PSM.","contentHash":"564fc251dbabe1de4723b87aa7179a9f9f901ef1b48e8c75549e98fefb798c1b","addressRefs":[]},"df09edaf-7a92-4d8e-ae86-a9666a0bf082":{"id":"df09edaf-7a92-4d8e-ae86-a9666a0bf082","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.1.1","title":"Call swapUSDSToUSDC Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7605,"content":"Only an operator with the relayer role can swap USDS to USDC via the PSM. To do so, they must call the swapUSDSToUSDC function on the Controller contract on mainnet, providing the usdcAmount (denominated in 1e6 precision to match PSM USDC handling). The operation will only succeed if the ALM Proxy holds at least the equivalent amount of USDS for the swap; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for swaps. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the swap amount is within the allowed rate limit (LIMIT_USDS_TO_USDC) for the PSM.\n- The contract will convert the USDC amount to an 18-decimal format using psmTo18ConversionFactor.\n- The contract will approve the daiUsds contract to spend the converted amount from the ALM Proxy.\n- The contract will swap USDS to DAI at a 1:1 ratio via daiUsds, sending DAI to the proxy.\n- The contract will approve the PSM to spend the DAI.\n- The contract will swap DAI to USDC at a 1:1 ratio with no fee via psm.buyGemNoFee, sending USDC to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDSToUSDC(uint256 usdcAmount) external`","contentHash":"7eb3eff7ccfadb9e15b1e53f6416a1529a1ce0afd50b48bf733b82eb49374957","addressRefs":[]},"da2164e3-03bc-447c-89c5-119d01feddaa":{"id":"da2164e3-03bc-447c-89c5-119d01feddaa","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.2","title":"Swap USDC To USDS","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7606,"content":"The documents herein define a series of operations for an operator to `swap` USDC to USDS through the PSM.","contentHash":"f55bbceca04d743a7ae5c9c46fa9d3d34fd14dab41a5f282da781a788be9ba83","addressRefs":[]},"1b18072b-c409-4d2f-a333-1e5c3ae8ab90":{"id":"1b18072b-c409-4d2f-a333-1e5c3ae8ab90","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.2.1","title":"Call swapUSDCToUSDS Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7607,"content":"Only an operator with the relayer role can swap USDC to USDS via the PSM. To do so, they must call the `swapUSDCToUSDS` function on the Controller contract on mainnet, providing the usdcAmount (denominated in 1e6 precision to match PSM USDC handling). The operation will only succeed if the ALM Proxy holds at least the amount of USDC specified for the swap; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for swaps. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the swap amount is within the allowed rate limit (LIMIT_USDC_TO_USDS) for the PSM.\n- The contract will approve the PSM to spend the USDC from the ALM Proxy.\n- The contract will calculate the swap limit per transaction based on the DAI balance held by the PSM, converting with psmTo18ConversionFactor.\n- If the usdcAmount is less than or equal to the limit, the contract will perform a direct swap of USDC to DAI.\n- If the usdcAmount exceeds the limit, the contract will split the swap into multiple smaller swaps: refill the PSM with DAI via psm.fill, recalculate the limit, swap the maximum allowed amount, update the remaining amount, and repeat until complete (reverting with \"DssLitePsm/nothing-to-fill\" if PSM cannot be filled).\n- The contract will convert the USDC amount to a DAI amount, accounting for token decimal differences.\n- The contract will approve the daiUsds contract to spend the DAI amount from the ALM Proxy.\n- The contract will swap DAI to USDS at a 1:1 ratio via daiUsds, sending USDS to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDCToUSDS(uint256 usdcAmount) external`","contentHash":"6746052f4df200a0360548ad38a669d5c4dacbed886fd5ca96376090711db7f4","addressRefs":[]},"030c5483-6126-40f7-b7ff-a99186ab105d":{"id":"030c5483-6126-40f7-b7ff-a99186ab105d","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.3","title":"Transfer Token Via LayerZero","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7608,"content":"The documents herein define the steps for a relayer to transfer a token via LayerZero to a destination endpoint, with the assets sent according to the configured recipient.","contentHash":"dbe9871d9bbde53a51e963b6846db15d606cc65522543ad28814be4f19f8d9e2","addressRefs":[]},"f88e14a0-fa64-44cc-a52c-cb35b7704ee8":{"id":"f88e14a0-fa64-44cc-a52c-cb35b7704ee8","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.3.1","title":"Call transferTokenLayerZero Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7609,"content":"Only an operator with the relayer role can transfer tokens via LayerZero. To do so, they must call the `transferTokenLayerZero` function on the Controller contract on mainnet, providing the oftAddress, amount, and destinationEndpointId (payable for native fees). The operation will only succeed if the ALM Proxy holds sufficient tokens and fees; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the transfer amount is within the allowed rate limit (built from LIMIT_LAYERZERO_TRANSFER, oftAddress, and destinationEndpointId).\n- If approval is required, the contract will approve the token for the oftAddress.\n- The contract will build LayerZero send options and a SendParam struct with destination details, amount, and recipient from layerZeroRecipients.\n- The contract will quote the OFT receipt to set the minimum amount received.\n- The contract will quote the messaging fee and execute the send via proxy.doCallWithValue, passing the fee value.\n\nThe function call is as follows:\n\n`function transferTokenLayerZero(address oftAddress, uint256 amount, uint32  destinationEndpointId) external payable`","contentHash":"a35fb0891772ab21f004a3c2d9997a1f57c3fe654845878902d240d60bc33274","addressRefs":[]},"66d40b48-7f80-46a2-8ee0-503580a42d4c":{"id":"66d40b48-7f80-46a2-8ee0-503580a42d4c","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.6","title":"Bridging Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7610,"content":"The documents herein define the operations performed by an operator to bridge liquidity between Ethereum Mainnet and the destination blockchains for the Keel Liquidity Layer.","contentHash":"c89a36d2c7e58d47881fe571a7275784db54a2516b90eb5a154f8757d99fd4cb","addressRefs":[]},"e4b91efa-ff29-4a8e-a28c-d54127ad2480":{"id":"e4b91efa-ff29-4a8e-a28c-d54127ad2480","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.6.1","title":"Bridge USDC Using Circle Cross-Chain Transfer Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7611,"content":"The documents herein define the process to bridge USDC using the Circle Cross-Chain Transfer Protocol.","contentHash":"4eacd6bae394ca7f266b3fe7b7be2efc53a5623ca734b8d34d428be16298fca7","addressRefs":[]},"46a74cd0-5e4e-4ea6-8fe6-ab38a8930f32":{"id":"46a74cd0-5e4e-4ea6-8fe6-ab38a8930f32","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.6.1.1","title":"Call transferUSDCToCCTP Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7612,"content":"Only an operator with the relayer role can initiate a USDC transfer to a specified destination domain using CCTP, handling rate limits, approvals, and splitting large amounts if needed. It requires parameters like proxy, Rate Limits, cctp, usdc, rate limit IDs, mintRecipient, destinationDomain, and usdcAmount. To do so, they must call the `transferUSDCToCCTP` function on the Controller contract on mainnet. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will trigger a rate limit decrease for the CCTP limit ID and amount.\n- The contract will trigger a rate limit decrease for a domain-specific key and amount.\n- The contract will require that mintRecipient is not zero, reverting if it is.\n- The contract will approve the CCTP contract to spend the USDC amount from the proxy, assuming that the proxy has enough USDC.\n- The contract will retrieve the burn limit per message for the USDC address (if the amount is larger than the limit it must be split into multiple calls).\n- If the usdcAmount exceeds the burn limit, the contract will initiate a CCTP transfer for the burn limit amount and subtract it from the remaining usdcAmount.\n- If any usdcAmount remains after the loop, the contract will initiate a final CCTP transfer for that amount.\n\nThe function call is as follows:\n\n`function transferUSDCToCCTP(uint256 usdcAmount, uint32 destinationDomain) external`","contentHash":"c3ccea98c7f1c749887534ce67f0e72764941f5d060a02905a4fefbd8b7b3807","addressRefs":[]},"d239ba22-9a09-49f1-9fdc-a1d306ffe697":{"id":"d239ba22-9a09-49f1-9fdc-a1d306ffe697","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.6.2","title":"Bridge USDS / sUSDS Using SkyBridge (LayerZero OFT) Token Bridge","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7613,"content":"This document defines the process for an operator to bridge USDS or sUSDS using the OP Token Bridge. This process will be specified in a future iteration of the Keel Artifact.","contentHash":"9946c1c65ea095df9cbc9544c2c7dddafd9665a4c2fb571bdce8e14b41319027","addressRefs":[]},"bf81a7dd-9483-48e4-b489-cb3cb2e61b37":{"id":"bf81a7dd-9483-48e4-b489-cb3cb2e61b37","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.3","title":"Rate Limit Management","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7614,"content":"The documents herein define the protocol for querying, setting, and adjusting `RateLimits` for Instances using their `RateLimitID`s. The Rate Limits must be maintained in line with Keel’s strategy, market conditions, and security considerations.","contentHash":"69f1ab22cfba00ac380a268472c6f97fa64b11b045bc0d012381cf59dc7281fe","addressRefs":[]},"921dd8b4-763e-4edf-9cb9-f2e0cb012109":{"id":"921dd8b4-763e-4edf-9cb9-f2e0cb012109","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.3.1","title":"Get Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7615,"content":"Anyone can query the full rate limit data for a specific key. Calling this function will carry out the following actions:\n\n- The contract will return the stored RateLimitData struct from the _data mapping for the key.\n\nThe function call is as follows:\n\n`function getRateLimitData(bytes32 key) external override view returns (RateLimitData memory)`","contentHash":"61aaead98caab9ae4da7ca412908ffa156e91b1a5fe8e1feca9babb5c82ac1fc","addressRefs":[]},"132f4de3-5b4c-462b-8f03-4cc15706baaf":{"id":"132f4de3-5b4c-462b-8f03-4cc15706baaf","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.3.2","title":"Set Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7616,"content":"Only an operator with the admin role is able to set or update rate limit data for a specific key, including maxAmount, slope, and historical values. There are two overloads for flexibility. Calling these functions will carry out the following actions:\n\n- The contract will require that lastAmount is less than or equal to maxAmount, reverting with \"RateLimits/invalid-lastAmount\" if not.\n- The contract will require that lastUpdated is less than or equal to the current block timestamp, reverting with \"RateLimits/invalid-lastUpdated\" if not.\n- The contract will store the provided data in the _data mapping as a RateLimitData struct.\n- The contract will emit a RateLimitDataSet event with the key and provided values.\n\nThe function calls are as follows:\n\n```\nfunction setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope, uint256 lastAmount, uint256 lastUpdated) public override onlyRole(DEFAULT_ADMIN_ROLE)\n\nfunction setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope) external override\n```","contentHash":"a9463875659a3ac6b66961118d94871545e79f20dea7a3671d7274e826248aa1","addressRefs":[]},"0a5ccc61-eaf4-4b49-80d7-770e29178c1a":{"id":"0a5ccc61-eaf4-4b49-80d7-770e29178c1a","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.3.3","title":"Set Unlimited Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7617,"content":"Only an operator with the admin role is able to set unlimited rate limit data for a specific key by configuring it with maximum values. Calling this function will carry out the following actions:\n\n- The contract will call setRateLimitData internally with type(uint256).max for maxAmount and lastAmount, 0 for slope, and the current block timestamp for lastUpdated.\n\nThe function call is as follows:\n\n`function setUnlimitedRateLimitData(bytes32 key) external override`","contentHash":"8d3f02b7a0c3f317c28a031cc58bcd6f8f28989b8f8fe5ce7d7e718bdfc42047","addressRefs":[]},"99f4fe4c-04af-4efe-b099-f5d92122de78":{"id":"99f4fe4c-04af-4efe-b099-f5d92122de78","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.3.4","title":"Get Current Rate Limit","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7618,"content":"Anyone can query the current rate limit value for a specific key, accounting for time-based slope accrual. Calling this function will carry out the following actions:\n\n- The contract will retrieve the RateLimitData for the key from the _data mapping.\n- If maxAmount is type(uint256).max (unlimited case), the contract will return type(uint256).max.\n- Otherwise, the contract will calculate and return the minimum of (slope * time elapsed since lastUpdated + lastAmount) and maxAmount.\n\nThe function call is as follows:\n\n`function getCurrentRateLimit(bytes32 key) public override view returns (uint256)`","contentHash":"4a41715aa485c085b94bc4050e85eaabdb529ba656d1185b8b57aa766ff36ad6","addressRefs":[]},"a710528f-e695-4262-bab1-e5ee57241315":{"id":"a710528f-e695-4262-bab1-e5ee57241315","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.3.5","title":"Trigger Rate Limit Decrease","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7619,"content":"Only an operator with the controller role can trigger a decrease in the rate limit for a specific key by a given amount. Calling this function will carry out the following actions:\n\n- The contract will retrieve the RateLimitData storage for the key from the data mapping.\n- The contract will require that maxAmount is greater than 0, reverting with \"RateLimits/zero-maxAmount\" if not.\n- If maxAmount is type(uint256).max (unlimited case), the contract will return type(uint256).max without changes.\n- The contract will calculate the currentRateLimit using getCurrentRateLimit.\n- The contract will require that amountToDecrease is less than or equal to currentRateLimit, reverting with \"RateLimits/rate-limit-exceeded\" if not.\n- The contract will update lastAmount to currentRateLimit minus amountToDecrease and set lastUpdated to the current block timestamp.\n- The contract will emit a RateLimitDecreaseTriggered event with the key, amountToDecrease, currentRateLimit, and newLimit.\n- The contract will return the newLimit.\n\nThe function call is as follows:\n\n`function triggerRateLimitDecrease(bytes32 key, uint256 amountToDecrease) external override onlyRole(CONTROLLER) returns (uint256 newLimit)`","contentHash":"90daece828f45dc63307a3e767f044524efeed8f45db7653932d890c4416f626","addressRefs":[]},"724970e4-e5e7-41ff-9448-d984c2c9a9e3":{"id":"724970e4-e5e7-41ff-9448-d984c2c9a9e3","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.4","title":"Instance Lifecycle Management","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7620,"content":"The documents herein define processes for invoking (onboarding) new Keel Liquidity Layer Instances and offboarding existing ones. This process will be specified in a future iteration of the Keel Artifact.","contentHash":"1d8ca6fb33b61ece2518f087e819afece5454d9a4d4c62246602028bfa67234d","addressRefs":[]},"f427c73d-fa0a-4183-89da-595ac1f5792e":{"id":"f427c73d-fa0a-4183-89da-595ac1f5792e","doc_no":"A.6.1.1.3.2.6.1.2.2.1.1.5","title":"Upgrading Controller","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7621,"content":"The documents herein define the process for deploying new Controller contracts. This process will be specified in a future iteration of the Keel Artifact.","contentHash":"447047bbe369ab2bbf0fc644df505823e7d4157fc4e95d9df3ccdda0cb038c43","addressRefs":[]},"0ca77e89-5598-46f6-a829-ff85c8c41e5e":{"id":"0ca77e89-5598-46f6-a829-ff85c8c41e5e","doc_no":"A.6.1.1.3.2.6.1.2.2.1.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7622,"content":"The documents herein define the process for non-routine ongoing management of the Keel Liquidity Layer and its active Instances on Ethereum Mainnet.","contentHash":"ee6ff0daa030a41d128f32206cd98d1f8929e7e38c4948d9f5bbb3ac96e9fe59","addressRefs":[]},"61b08883-4417-4f10-acb3-2cafdc5eda21":{"id":"61b08883-4417-4f10-acb3-2cafdc5eda21","doc_no":"A.6.1.1.3.2.6.1.2.2.1.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7623,"content":"The documents herein define all the possible actions that can be taken in case of an emergency within Keel Liquidity Layer operations on Ethereum Mainnet.","contentHash":"b0fd1f7bd74ba0c01b5406e769bd20d6e71e2ea5c965365d64ab5bb6c548cd58","addressRefs":[]},"00a56799-7803-460a-bda3-eab312fc296d":{"id":"00a56799-7803-460a-bda3-eab312fc296d","doc_no":"A.6.1.1.3.2.6.1.2.2.1.3.1","title":"Remove Compromised Relayer As Freezer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7624,"content":"In the event of a compromised Relayer, the `FREEZER_ROLE` can call the function to `removeRelayer` from the Controller contract. Only an operator with the freezer role can remove a relayer. To do so, they must call the `removeRelayer` function on the Controller contract on mainnet, providing the compromised relayer’s address. Calling this function will carry out the following actions:\n\n- The contract will confirm the caller holds the freezer role. If the caller does not have the freezer role, the transaction will revert.\n- The contract will revoke the relayer role from the specified address.\n- The contract will emit a `RelayerRemoved(relayer)` event.\n\nThe function call is as follows:\n\n`function removeRelayer(address relayer) external`","contentHash":"8ebeac10750fbcf9c40090f2a5d9a3266ffd6059753fd131ab44c8fe4b8aad1f","addressRefs":[]},"23a36776-11e0-4c65-a25d-500a44e14eb4":{"id":"23a36776-11e0-4c65-a25d-500a44e14eb4","doc_no":"A.6.1.1.3.2.6.1.2.2.1.3.2","title":"Redeem All Ethereum Mainnet Positions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7625,"content":"The documents herein define the actions that should be performed by an operator if there is a need to recover the liquidity from Mainnet Protocols and centralize it in the Mainnet Keel ALM Proxy.","contentHash":"072f888ab1538b4a2badbbae863275dca7313da6dc9cc86533cb02a4ede02d81","addressRefs":[]},"98208afa-5810-4591-b261-efe0c1b882e5":{"id":"98208afa-5810-4591-b261-efe0c1b882e5","doc_no":"A.6.1.1.3.2.6.1.2.2.1.3.2.1","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7626,"content":"In order to withdraw all ERC-4626 balances, the operator must call the `redeemERC4626` function.\n\nThe function call is as follows:\n\n`function redeemERC4626(address(token), token.balanceOf(address(proxy)))`\n\nFor more detailed instructions on the code to execute this, see [A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.3 - ERC-4626 Functions](3de32801-e895-4a21-84da-aa5818d16349).","contentHash":"d08d5aa195f5b6cd35fe95c1982b47b4fab0f40883dc42820b64309b6d3a0049","addressRefs":[]},"23770b76-5a1f-49d2-b970-dbf908c05817":{"id":"23770b76-5a1f-49d2-b970-dbf908c05817","doc_no":"A.6.1.1.3.2.6.1.2.2.1.3.3","title":"USDC to USDS Swap Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7627,"content":"This document defines the action that should be performed by an operator if there is a need to centralize all recovered liquidity in USDS. The operator must call the `swapUSDCToUSDS` function.\n\nThe function call is as follows:\n\n`function swapUSDCToUSDS(usdc.balanceOf(address(proxy))`\n\nFor more detailed instructions on the code to execute this see [A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.2 - Swap USDC To USDS](da2164e3-03bc-447c-89c5-119d01feddaa).","contentHash":"f405728c27fbe0a8ba6f5e76849dcfcca2304362a9ffa5f33f7cbbe71f403642","addressRefs":[]},"44ca2425-03dd-4913-919a-666a77854709":{"id":"44ca2425-03dd-4913-919a-666a77854709","doc_no":"A.6.1.1.3.2.6.1.2.2.1.3.4","title":"USDS Burn Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7628,"content":"This document defines the action that should be performed if there is a need to repay and then burn Keel’s USDS debt. The operator must call the `burnUSDS` function.\n\nThe function call is as follows:\n\n`function burnUSDS(usds.balanceOf(address(proxy))`\n\nMore detailed instructions on the code to execute this, see [A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.1.2 - Burn USDS](9c9536a8-bb2d-4d37-98cf-4c25a5699026).","contentHash":"81edb0516e3b888e0e44098765381641ee8f312c89ff3daabb3bb7862e83ec34","addressRefs":[]},"f70746e5-a879-4d13-bd48-74bf79478f4d":{"id":"f70746e5-a879-4d13-bd48-74bf79478f4d","doc_no":"A.6.1.1.3.2.6.1.2.2.2","title":"Solana","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7629,"content":"The documents herein describe common operational procedures for the Keel Liquidity Layer applicable across multiple Instances on Solana.","contentHash":"dd0b2509d298dac6718cee77b2069730aeec85ecbb8aeecd16ca4e5453ed8758","addressRefs":[]},"828e1609-88b5-4d6d-a31a-607183901ea1":{"id":"828e1609-88b5-4d6d-a31a-607183901ea1","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7630,"content":"The documents herein define the protocol for routine ongoing management of the Keel Liquidity Layer and its active Instances on Solana.","contentHash":"9ec2a12789cea1a2e003ae5647f6650936bb1737dad8459e7cfa4c43070900f3","addressRefs":[]},"6c7d3476-9e97-495d-a491-3194e7c061a3":{"id":"6c7d3476-9e97-495d-a491-3194e7c061a3","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.1","title":"Role Hierarchy And Permissions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7631,"content":"The documents herein define roles (Admin, Relayer, ALM Controller and Freezer) and their responsibilities/permissions for managing the Keel Liquidity Layer.","contentHash":"9392ab56e7fe0ebcfd7cf63e16946468a7dc2abd9d06e5ae866a527fe18d2fc2","addressRefs":[]},"0270b595-8957-4fb2-a9cd-2bc197dc3367":{"id":"0270b595-8957-4fb2-a9cd-2bc197dc3367","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.1.1","title":"Default Admin Role","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7632,"content":"The admin role is configured with the following permissions: `can_freeze_controller`, `can_unfreeze_controller`, `can_manage_permissions`, `can_suspend_permissions`, `can_manage_reserves_and_integrations`, `can_invoke_external_transfer`. This role can grant and revoke any role, including itself and all other roles defined in the contract. The admin role is also used for general admin functions in all contracts. This role is fully controlled by Sky Governance via the Keel Proxy.\n\n```\nconstructor(address admin) {\n_grantRole(DEFAULT_ADMIN_ROLE, admin);\n```","contentHash":"e7747a6c636a0c2a64ed1342fa45720192197b74ac0bc14e52a43534416d3056","addressRefs":[]},"2b42015c-c76a-4364-b8b5-c9a2b9f6f484":{"id":"2b42015c-c76a-4364-b8b5-c9a2b9f6f484","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.1.2","title":"Relayer Role","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7633,"content":"The Relayer role is the address(es) for the Keel Liquidity Layer ALM Planner off-chain system that calls functions on `SvmAlmController` program to perform actions on funds held by Keel's Solana Controller. The Relayer Role has `can_execute_swap` and `can_reallocate` permissions. The Relayer Role may be granted to an address by any address with `can_manage_permissions` privileges and can be revoked by one with `can_suspend_permissions` privileges.","contentHash":"160933743d333989b0a85afa36d2e8479e5748a285bec5571c67dc94339d4fdd","addressRefs":[]},"6f7becc7-2e70-44e5-8662-25ba7dd1a5f8":{"id":"6f7becc7-2e70-44e5-8662-25ba7dd1a5f8","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.1.3","title":"Freezer Role","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7634,"content":"The Freezer role is the address of the emergency role that can remove a compromised Relayer. The Freezer role has `can_freeze_controller` , `can_suspend_permissions` and `can_liquidate` permissions.","contentHash":"e9b8c34379d2ca5c3abdd29b85b50cb1e0b4b71f7f777d76314e77983b3a039d","addressRefs":[]},"78b48a5e-d4f8-46f3-bf32-c60cdc213be4":{"id":"78b48a5e-d4f8-46f3-bf32-c60cdc213be4","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2","title":"Controller Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7635,"content":"The documents herein describe the purpose and operational use of key functions within Keel Liquidity Layer `SvmAlmController` programs: Asset Transfer Management (direct transfers, protocol deposits/withdrawals) and Cross-chain Operations (CCTP bridging, SkyBridge bridging).","contentHash":"594d701b438dfd08a749f2a342a5fa150d901f869fc443e4b6019168e7084020","addressRefs":[]},"397928f4-0d80-4ed9-8a51-6e22f962ab94":{"id":"397928f4-0d80-4ed9-8a51-6e22f962ab94","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1","title":"Controller Contract Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7636,"content":"The documents herein define the functions controlled by the Controller contract for Keel Liquidity Layer operations on Solana.","contentHash":"5856e52ab8a2b9f2b0e7a78fbe5b1ee493c760b876603a814fb1ca52f761bbda","addressRefs":[]},"ab262163-ec0a-49c7-be21-578ed120ca56":{"id":"ab262163-ec0a-49c7-be21-578ed120ca56","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.1","title":"Admin Functions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7637,"content":"The documents herein define the operations performed by the admin role (see [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367)[)](https://www.notion.so/atlas-axis/SH-Add-Allocation-System-Primitive-Keel-294f2ff08d73802089c6e838cd85462c#2a2f2ff08d7381e7b822efcf1013e9f9) within the `SvmAlmController` contract.","contentHash":"2f853d34819335880d32c55b8b722cc634dbb61d1a3419dbece2c417011c04e7","addressRefs":[]},"10be5f11-b678-45b9-8ba2-f636ec3c83c7":{"id":"10be5f11-b678-45b9-8ba2-f636ec3c83c7","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.1.1","title":"Configure Integrations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7638,"content":"The admin can configure and update configurations on permitted integrations with third party protocols. For example, permitting bridge interfaces, setting slippage rules for permitted swap routes or permitting certain lending market interfaces.","contentHash":"0434e6409cdc713658f2355d95a12839f457a955fa1a8ea58f2ff1a515e12a54","addressRefs":[]},"85dbd095-10fd-46bf-9d6b-96a7b1a8c979":{"id":"85dbd095-10fd-46bf-9d6b-96a7b1a8c979","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.1.2","title":"Configure Reserves","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7639,"content":"The admin can configure and update configurations on permitted tokens which the `SvmAlmController` can hold or transact in.","contentHash":"1414317452b681652307b9d306080e65d2e233043e5a1f094d34b8d6bad89a78","addressRefs":[]},"7f7333d4-c1a8-4bb0-8dec-47ce46aac125":{"id":"7f7333d4-c1a8-4bb0-8dec-47ce46aac125","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.1.3","title":"Configure Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7640,"content":"The admin can configure and update the rate limits for `Integration`s and `Reserve`s.","contentHash":"94e172e867eef61b611bca07ebf354d7d3540b993a79dc7b7bc4ab624bee165a","addressRefs":[]},"ee2f8a2e-8225-4747-9f3a-cc1b4624987b":{"id":"ee2f8a2e-8225-4747-9f3a-cc1b4624987b","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2","title":"Relayer Function","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7641,"content":"The documents herein define the operations performed by the relayer role (see [A.6.1.1.3.2.6.1.2.2.2.1.1.2 - Relayer Role](2b42015c-c76a-4364-b8b5-c9a2b9f6f484)) within the `SvmAlmController` contract.","contentHash":"465610f078185b2cd41f56cc4f82e7d9cefa952a5551610d742185f6094aa637","addressRefs":[]},"619a94f1-05ac-4b47-80d5-cafd9515b7e5":{"id":"619a94f1-05ac-4b47-80d5-cafd9515b7e5","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2.1","title":"CctpBridge Actions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7642,"content":"The Relayer can perform CCTP Bridge actions which facilitates transferring of assets across networks using Circle’s CCTP Interoperability protocol.","contentHash":"0cf75068cd3fa97477bf2a474b7a4519d188d00f699eccb0940ae8f700c6c296","addressRefs":[]},"1294a5b5-316b-4a05-bdb3-87ed33067d39":{"id":"1294a5b5-316b-4a05-bdb3-87ed33067d39","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2.1.1","title":"Push Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7643,"content":"The Relayer can transfer tokens via a permitted bridging protocol, to a pre-configured destination chain and address, subject to rate limits.","contentHash":"8e64c14e927c653340057faa799feedefdc6d9eaf8955d9df77ac0c9c434c222","addressRefs":[]},"e408605b-d029-42ca-b9cb-8974d64f5be6":{"id":"e408605b-d029-42ca-b9cb-8974d64f5be6","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2.2","title":"LzBridge Actions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7644,"content":"The Relayer can perform OFT Bridge actions which facilitates transferring of assets across networks using LayerZero's OFT Interoperability protocol.","contentHash":"e4b3219502543206d740310c094cc555c0f8ce1cc444b3ff638eee2ca3e3ef15","addressRefs":[]},"5d174ad0-e955-40f9-b64e-e07a72b60216":{"id":"5d174ad0-e955-40f9-b64e-e07a72b60216","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2.2.1","title":"Push Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7645,"content":"The push action can transfer tokens via a permitted bridging protocol, to a pre-configured destination chain and address, subject to rate limits.","contentHash":"e0ab40bf8adac505959c4dfd3df19cf316f05c74e3c42954f1439d3f72052473","addressRefs":[]},"2f6f0f93-6a3b-4dec-a862-a78080b23736":{"id":"2f6f0f93-6a3b-4dec-a862-a78080b23736","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2.3","title":"AtomicSwap Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7646,"content":"The Relayer can perform swapping actions from one token to another. This action is split across two instructions which are applied as bookends to inner swap instructions.","contentHash":"d03a7476b4d650e4ca03a84e326dda8056e4c85c438732700df3c4b9ceb1a9fd","addressRefs":[]},"544c4bae-7d5c-494f-8bdc-4ee47203e1e7":{"id":"544c4bae-7d5c-494f-8bdc-4ee47203e1e7","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2.3.1","title":"Borrow Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7647,"content":"The borrow action temporarily funds the Relayers account with tokens to support an intended swap on a permitted swap route, subject to rate limits and validating that the corresponding `Repay` instruction is present at the end of the transaction.","contentHash":"7243b333c18b2e37471ff10dc76c096c1e6a908d8b4166c3f937fc424aedfd43","addressRefs":[]},"f19c7438-54ee-47ef-b92d-9313b581da29":{"id":"f19c7438-54ee-47ef-b92d-9313b581da29","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.2.1.2.3.2","title":"Repay Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7648,"content":"The repay action validates that the proceeds of the swap meet minimum slippage requirements, or fails the overall transaction.","contentHash":"8b044c4bad5d1f2bf14357009ecf2303f03617106e2e3a7fdd19ea5af8341614","addressRefs":[]},"7e6e8dea-5c3e-430f-a984-926bc726e992":{"id":"7e6e8dea-5c3e-430f-a984-926bc726e992","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3","title":"Rate Limit Management","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7649,"content":"The documents herein define the protocol for querying, setting, and adjusting Rate Limits. The Rate Limits must be maintained in line with Keel’s strategy, market conditions, and security considerations.","contentHash":"407becaa747633c75e95e5fc6d2d37e6fe2ea1bb6343facf9488ec432b0c07b4","addressRefs":[]},"f5b98691-5237-427b-8d8e-2b08262da8eb":{"id":"f5b98691-5237-427b-8d8e-2b08262da8eb","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.1","title":"Reserve Level Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7650,"content":"`Reserve` level rate limits constrain the outflow that can occur from a given token’s `Reserve` in aggregate across all Integrations.","contentHash":"2917a5852b800d630b4030c56bb41769c145659886a0a15f40f4a9ade17222a5","addressRefs":[]},"21590f17-8e03-4fc3-9a37-e8364bbee322":{"id":"21590f17-8e03-4fc3-9a37-e8364bbee322","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.1.1","title":"Get Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7651,"content":"The properties associated with a Reserve level rate limit can be read from the `Reserve` account corresponding to a particular token, as follows:\n\n```\npub struct Reserve {\n// ...\npub rate_limit_slope: u64,\npub rate_limit_max_outflow: u64,\npub rate_limit_outflow_amount_available: u64,\npub rate_limit_remainder: u64\n// ...\n}\n```","contentHash":"e6297ab0177f2e01d6d0308f293021a92ac07a038345f7adcb93448386b87f6f","addressRefs":[]},"aa43f1e6-6ee6-4596-a288-f79685cd8144":{"id":"aa43f1e6-6ee6-4596-a288-f79685cd8144","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.1.2","title":"Set Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7652,"content":"Only an operator with the [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367) is able to set or update rate limit data for a specific `Reserve`, including `rate_limit_slope` and `rate_limit_max_outflow`.\n\n```\nmanage_reserves(\nManageReserveArgs {\nstatus: None,\nrate_limit_slope: Some(rate_limit_slope),\nrate_limit_max_outflow: Some(rate_limit_max_outflow),\n}\n)\n```","contentHash":"f6ef10fd566da091e8d1a35d605c1960c396b88da1b99535b1d8379d71453227","addressRefs":[]},"76946aaf-70dc-43cf-a6e0-ce947f19b93b":{"id":"76946aaf-70dc-43cf-a6e0-ce947f19b93b","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.1.3","title":"Set Unlimited Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7653,"content":"Only an operator with the [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367) is able to set unlimited rate limit data for a specific key by configuring it with maximum values.\n\n```\nmanage_reserves(\nManageReserveArgs {\nstatus: None,\nrate_limit_slope: Some(0),\nrate_limit_max_outflow: Some(u64::MAX),\n}\n)\n```","contentHash":"7da45111ff4180de825b72d0d3551d087231d034e34fb7df2442e370d7030771","addressRefs":[]},"3bf06ac1-44d2-4901-92fb-7af3cebef5a0":{"id":"3bf06ac1-44d2-4901-92fb-7af3cebef5a0","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.2","title":"Integration Level Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7654,"content":"`Integration` level rate limits constrain the flow of assets into a particular `Integration`.","contentHash":"23f4476b70efdacc8f7c828bc280f2b2418b5e92422611e85f6919b736b88c51","addressRefs":[]},"c75e8c0d-0b16-4808-a14c-dac919ef9269":{"id":"c75e8c0d-0b16-4808-a14c-dac919ef9269","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.2.1","title":"Get Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7655,"content":"The properties associated with a Reserve level rate limit can be read from the `Integration` account corresponding to a particular token, as follows:\n\n```\npub struct Integration {\n// ...\npub rate_limit_slope: u64,\npub rate_limit_max_outflow: u64,\npub rate_limit_outflow_amount_available: u64,\npub rate_limit_remainder: u64\n// ...\n}\n```","contentHash":"14f3a4b5d1e6b90fee237112181b77ebad5f18ea627e1e4d455c9dac474889e4","addressRefs":[]},"62654961-cf70-4455-a7df-c81861944395":{"id":"62654961-cf70-4455-a7df-c81861944395","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.2.2","title":"Set Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7656,"content":"Only an operator with the [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367) is able to set or update rate limit data for a specific `Integration`, including `rate_limit_slope` and `rate_limit_max_outflow`.\n\n```\nmanage_integration(\nManageIntegrationArgs {\nstatus: None,\ndescription: None,\nrate_limit_slope: Some(rate_limit_slope),\nrate_limit_max_outflow: Some(rate_limit_max_outflow),\n}\n)\n```","contentHash":"645d1afb105af8c5102d9f7223e1820a77dbbe19e0441fad9c60c0b250a441b0","addressRefs":[]},"bd904ac0-32d2-4592-92cd-3eb01a3ce7de":{"id":"bd904ac0-32d2-4592-92cd-3eb01a3ce7de","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.3.2.3","title":"Set Unlimited Rate Limit Data","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7657,"content":"Only an operator with the [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367) is able to set unlimited rate limit data for a specific key by configuring it with maximum values.\n\n```\nmanage_integration(\nManageIntegrationArgs {\nstatus: None,\ndescription: None,\nrate_limit_slope: Some(0),\nrate_limit_max_outflow: Some(u64::MAX),\n}\n)\n```","contentHash":"187e85af47df52249b55573e5e21990a5580cc695faac36ae17d6afc470ffe97","addressRefs":[]},"5fcff9f8-7f6d-427d-a12d-02df83b4db6e":{"id":"5fcff9f8-7f6d-427d-a12d-02df83b4db6e","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.4","title":"Instance Lifecycle Management","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7658,"content":"The documents herein define processes for invoking (onboarding) new Keel Liquidity Layer Instances and off-boarding existing ones.","contentHash":"f68e74ad92cb10e4e811eb368037096b287087498881ef886d8983a1b3076a81","addressRefs":[]},"7675ad2a-f865-4756-8da9-49062e785074":{"id":"7675ad2a-f865-4756-8da9-49062e785074","doc_no":"A.6.1.1.3.2.6.1.2.2.2.1.5","title":"Upgrading Controller","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7659,"content":"The documents herein define the process for deploying new Controller contracts. This process will be specified in a future iteration of the Keel Artifact.","contentHash":"447047bbe369ab2bbf0fc644df505823e7d4157fc4e95d9df3ccdda0cb038c43","addressRefs":[]},"0aa16a2c-b0a0-427e-b822-1d9a399c65db":{"id":"0aa16a2c-b0a0-427e-b822-1d9a399c65db","doc_no":"A.6.1.1.3.2.6.1.2.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7660,"content":"The documents herein define the process for non-routine ongoing management of the Keel Liquidity Layer and its active Instances on Solana.","contentHash":"763afbbb5a41656464f4252bdd1b27ec8313fb71330620eaf7657d060981a7f7","addressRefs":[]},"6cc9260a-88f8-4bf2-8819-8897000c5e5d":{"id":"6cc9260a-88f8-4bf2-8819-8897000c5e5d","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7661,"content":"The documents herein define all the possible actions that can be taken in case of an emergency within Keel Liquidity Layer operations on Solana.","contentHash":"b11a27a656188c4f62a64d028a27ce5aff2c67caba6fe0c26dba74cd5e40f300","addressRefs":[]},"c4932ae7-0bf2-46fe-bbca-4bdd675368c9":{"id":"c4932ae7-0bf2-46fe-bbca-4bdd675368c9","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.1","title":"Remove Compromised Relayer As Freezer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7662,"content":"In the event of a compromised Relayer, the [A.6.1.1.3.2.6.1.2.2.2.1.1.3 - Freezer Role](6f7becc7-2e70-44e5-8662-25ba7dd1a5f8) and [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367) can call the instruction to suspend the compromised Relayer from the Controller program, thereby preventing it from doing any further harm to the system. The backstop Relayer can then take over. This function should only be used if the keys to the Relayer multisig have been leaked or compromised, and the Relayer is now in the hands of an external bad actor.\n\n```\nmanage_permission(\nManagePermissionArgs {\nstatus: PermissionStatus::Suspended,\ncan_manage_permissions: false,\ncan_invoke_external_transfer: false,\ncan_execute_swap: false,\ncan_reallocate: false,\ncan_freeze_controller: false,\ncan_unfreeze_controller: false,\ncan_manage_reserves_and_integrations: false,\ncan_suspend_permissions: false,\ncan_liquidate: false,\n}\n)\n```","contentHash":"43a48a282fa6ac6049bad83764687e3cd57f3459bebd630ae2a512903e21d426","addressRefs":[]},"de48d076-bad2-4edd-a740-0e5ee9173d0d":{"id":"de48d076-bad2-4edd-a740-0e5ee9173d0d","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.2","title":"Freeze the Controller","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7663,"content":"In the event of a more severe threat to the Controller, the [A.6.1.1.3.2.6.1.2.2.2.1.1.3 - Freezer Role](6f7becc7-2e70-44e5-8662-25ba7dd1a5f8) can call the instruction to suspend the entire Controller instance.","contentHash":"96240fc5361fc71c2a868a63c62174537583ccd7477a3c84dc856f3ddc27a0c9","addressRefs":[]},"4f8c8aa3-fffc-46dd-aeb7-b23e996619d7":{"id":"4f8c8aa3-fffc-46dd-aeb7-b23e996619d7","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.2.1","title":"Full Freeze","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7664,"content":"This action leads to a complete freeze and prevents any actions on the Controller until the [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367) subsequently lifts this status. Integrations, Reserves nor Permissions cannot be managed during this period, and funds cannot be moved.\n\n```\nmanage_controller(\nManageControllerArgs {\nstatus: ControllerStatus::PushPullFrozen,\n}\n)\n```","contentHash":"0026593886a016fbb2a41d7e9f4d0375ba125cb2875b9d43935d997d24ef6847","addressRefs":[]},"2ed41eef-989b-4253-8de7-5e368da0242a":{"id":"2ed41eef-989b-4253-8de7-5e368da0242a","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.2.2","title":"Reallocation Freeze","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7665,"content":"A complete freeze prevents any movement of funds within the Controller until the [A.6.1.1.3.2.6.1.2.2.2.1.1.1 - Default Admin Role](0270b595-8957-4fb2-a9cd-2bc197dc3367) subsequently lifts this status. Integrations, Reserves and Permissions cannot be configured during this period.\n\n```\nmanage_controller(\nManageControllerArgs {\nstatus: ControllerStatus::Frozen,\n}\n)\n```","contentHash":"ddbca8e243af44fe4d4099f39d18c1313d613ef5c1431461a50ea51bcf5accff","addressRefs":[]},"4f4a2911-a604-4203-8103-e9a05fe4cb80":{"id":"4f4a2911-a604-4203-8103-e9a05fe4cb80","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.3","title":"Redeem All Positions","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7666,"content":"The documents herein define the actions that should be performed by an operator if there is a need to recover the liquidity from Solana Protocols and centralize it in the Keel ALM Controller.","contentHash":"df92e4d006fdc5cf18870f68caaf09b0b1d3c68d4923544f5c5ee1a68d171c95","addressRefs":[]},"22943595-8338-47b6-b3d2-55bd131895e9":{"id":"22943595-8338-47b6-b3d2-55bd131895e9","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.3.1","title":"Integrations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7667,"content":"This will be specified in a future iteration of the Keel Artifact.","contentHash":"743402c4b2fb0f7eb8376642c293ab0a50d7f0f5008261c1758a027396963963","addressRefs":[]},"8d1232fa-d714-48e5-9cca-798543c02e65":{"id":"8d1232fa-d714-48e5-9cca-798543c02e65","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.3.2","title":"Reserves","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7668,"content":"This will be specified in a future iteration of the Keel Artifact.","contentHash":"743402c4b2fb0f7eb8376642c293ab0a50d7f0f5008261c1758a027396963963","addressRefs":[]},"1bc17a00-a5b7-4390-bec5-46674053222b":{"id":"1bc17a00-a5b7-4390-bec5-46674053222b","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.4","title":"AtomicSwap Action","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7669,"content":"This document defines the action that should be performed by an operator if there is a need to centralize all recovered liquidity in USDS.\n\n`mainnetController.swapUSDCToUSDS(usdc.balanceOf(address(proxy))`\n\nFor more detailed instructions on the code to execute this see [A.6.1.1.3.2.6.1.2.2.1.1.2.1.2.5.2 - Swap USDC To USDS](da2164e3-03bc-447c-89c5-119d01feddaa).","contentHash":"87610cbb2a1d3ab068867d0210f48c8b997aee699adc156ac07ec7b6e15852c4","addressRefs":[]},"c60fe936-a500-4366-bcf2-ae813e64584a":{"id":"c60fe936-a500-4366-bcf2-ae813e64584a","doc_no":"A.6.1.1.3.2.6.1.2.2.2.3.5","title":"Bridge to Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7670,"content":"This document defines the action that should be performed by an operator if there is a need to return recovered liquidity to Keel’s Ethereum Mainnet ALM Controller.","contentHash":"ba7280b6c7b2a533750af64374e1377e697da659217d3e94ae979be66f2a2b90","addressRefs":[]},"cebfc91d-1b4e-49ca-9e4d-4c9b7043db81":{"id":"cebfc91d-1b4e-49ca-9e4d-4c9b7043db81","doc_no":"A.6.1.1.3.2.6.1.2.3","title":"Allocation Strategy","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7671,"content":"In the future, additional logic will be added herein regarding the strategy by which capital is allocated between different Instances of the Keel Liquidity Layer.","contentHash":"dee982d75aac68004daf8e7e431818de6d7828a35f7c8c51d5c4dcd37322c33f","addressRefs":[]},"b9316097-ab93-4a8b-aa51-1e44ceb69c4d":{"id":"b9316097-ab93-4a8b-aa51-1e44ceb69c4d","doc_no":"A.6.1.1.3.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7672,"content":"The Instances of the Keel Liquidity Layer with `Active` Status are stored herein. The `RRC Framework Full Implementation Coverage` status defines whether the Instance Financial RRC is calculated based on a fully implemented risk model (see [A.3.2.1.1.4.3.1 - Fully Implemented Risk Models](419a1d00-fbae-4d26-bd47-8f57677d8001)) or a pending risk model (see [A.3.2.1.1.4.3.2 - Pending Risk Models](81ca88bf-3f6a-4d10-a3e2-d47cf6636d7d)). If the Instance Financial RRC is calculated based on a fully implemented risk model the status is `Covered`. If the Instance Financial RRC is calculated based on a pending risk model the status is `Pending`.","contentHash":"d2f3fe7251a3d7ef67f3e5ca4344db33a298ba9c7b651e311da3f5f564205913","addressRefs":[]},"77c4c83d-199b-412b-abf5-999b94e93531":{"id":"77c4c83d-199b-412b-abf5-999b94e93531","doc_no":"A.6.1.1.3.2.6.1.3.1","title":"Solana Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7673,"content":"The Solana Instances of the Keel Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"eb41e8e29a8ee2f83a61a7b85cefc39ae8800c304c41a5c0c1f689b0eae24879","addressRefs":[]},"39979f83-5da3-45c9-9ad4-bb17cca5513c":{"id":"39979f83-5da3-45c9-9ad4-bb17cca5513c","doc_no":"A.6.1.1.3.2.6.1.3.1.1","title":"Kamino","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7674,"content":"The Solana Instances of the Kamino Protocol with `Active` Status are stored herein.","contentHash":"3afd5fb5c7159795b1cf445d73a4615b073e7c732a1ae598af3d83c29502d45e","addressRefs":[]},"fa6f6aa7-410e-4515-8458-9f3efb30c942":{"id":"fa6f6aa7-410e-4515-8458-9f3efb30c942","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1","title":"Solana - Kamino USDS Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7675,"content":"The documents herein contain the Instance Configuration Document for the Kamino USDS Instance.","contentHash":"c611725b03e02bc0f8a5eee8f7ef8f32ce84038cc855cd34f03d25021da3bd0a","addressRefs":[]},"5a235b70-b3d0-4a33-a88d-32b0c3aec917":{"id":"5a235b70-b3d0-4a33-a88d-32b0c3aec917","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7676,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"3fc55a0d-c568-4b70-9771-ba125a89782e":{"id":"3fc55a0d-c568-4b70-9771-ba125a89782e","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7677,"content":"The documents herein define the parameters of the Kamino USDS Instance of the Allocation System Primitive.","contentHash":"f805f706d16296b4307f42e117e18173e2e5ffca4785ee9f3f9faded176849d4","addressRefs":[]},"77832cc0-aa05-4a84-952d-54efb83b6ec0":{"id":"77832cc0-aa05-4a84-952d-54efb83b6ec0","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7678,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"32e1e642-91bd-4f67-b271-771f32da87d9":{"id":"32e1e642-91bd-4f67-b271-771f32da87d9","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7679,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"3eba506a-6482-424d-8cc9-752c65e634c5":{"id":"3eba506a-6482-424d-8cc9-752c65e634c5","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7680,"content":"Kamino","contentHash":"b4c4574996552f964fff71d974229604d349dbaa253e182a50502aa5fa07dd97","addressRefs":[]},"7198e08b-080d-46c7-87fe-2387461b3473":{"id":"7198e08b-080d-46c7-87fe-2387461b3473","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.1.3","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7681,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"5569d20b-c7ac-4736-b5a1-c6017cff4520":{"id":"5569d20b-c7ac-4736-b5a1-c6017cff4520","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.1.4","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7682,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"d86162cd-defd-431c-8cac-5b0f6eecc1ac":{"id":"d86162cd-defd-431c-8cac-5b0f6eecc1ac","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7683,"content":"kUSDS","contentHash":"b457a66f1287a04c3a8f4bd6d123a62a250cbffa547a893694269197b368cd16","addressRefs":[]},"2bd4ac66-9878-42f1-9873-4708ed2a44c6":{"id":"2bd4ac66-9878-42f1-9873-4708ed2a44c6","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7684,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"e8d610ec-9514-46fb-9431-3c4260edc7be":{"id":"e8d610ec-9514-46fb-9431-3c4260edc7be","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7685,"content":"`6nnt6N4Ay9tBeMWnVWKS24hDtE6R3fshi5TteUcSKJcQ`","contentHash":"39ace901b9de1b207db37a0a0a3cd2d24a30356411a287e7e8a571745603ada4","addressRefs":["6nnt6N4Ay9tBeMWnVWKS24hDtE6R3fshi5TteUcSKJcQ"]},"1de01d57-847c-4b6d-afc9-d841d63228c0":{"id":"1de01d57-847c-4b6d-afc9-d841d63228c0","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7686,"content":"`USDSwr9ApdHk5bvJKMjzff41FfuX8bSxdKcR81vTwcA`","contentHash":"3be7c5cf0835df149bcfb9997c26373055af42734944d45edf0a3e178626db5f","addressRefs":["USDSwr9ApdHk5bvJKMjzff41FfuX8bSxdKcR81vTwcA"]},"d625d675-4667-4464-af41-95d35414fad4":{"id":"d625d675-4667-4464-af41-95d35414fad4","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7687,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Kamino USDS Instance of the Allocation System Primitive.","contentHash":"3d8cfc7103858687154d1c0e72bf3a2875ae0fbc85fd3d5b58be5e39ed147ca0","addressRefs":[]},"28537d8e-fe00-46db-b2ce-726fd718bd86":{"id":"28537d8e-fe00-46db-b2ce-726fd718bd86","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7688,"content":"`H5Vix4RGchYq1cemoe61y7J4j4v3XgWPGLBeqvPEgvzr`","contentHash":"34cd9c9b4d281517f80a3def223ca86e061e89cb9e76c153ad9e674d93501ec9","addressRefs":["H5Vix4RGchYq1cemoe61y7J4j4v3XgWPGLBeqvPEgvzr"]},"ecde5b24-7807-40ee-b352-f509d4e2daf7":{"id":"ecde5b24-7807-40ee-b352-f509d4e2daf7","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7689,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"9577670b-0f91-45e8-b7e9-faf072e2d7e9":{"id":"9577670b-0f91-45e8-b7e9-faf072e2d7e9","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7690,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDS\n- `slope`: 10,000,000 USDS per day","contentHash":"f6f5bd0dbd7f1aa291c7b4b8741f0eaa51b4f56811231c27f487cd9979340538","addressRefs":[]},"1d393362-1b05-4dc3-9531-233d748c2394":{"id":"1d393362-1b05-4dc3-9531-233d748c2394","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7691,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"3503046a-a936-46d1-93f6-dbce0b6b55d3":{"id":"3503046a-a936-46d1-93f6-dbce0b6b55d3","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7692,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"0a1e41de-51bb-4da5-972d-d1e7cfd13ace":{"id":"0a1e41de-51bb-4da5-972d-d1e7cfd13ace","doc_no":"A.6.1.1.3.2.6.1.3.1.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7693,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"2510c2ba-c304-478f-84b1-a421e62de8b4":{"id":"2510c2ba-c304-478f-84b1-a421e62de8b4","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2","title":"Solana - Kamino USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7694,"content":"The documents herein contain the Instance Configuration Document for the Kamino USDC Instance.","contentHash":"dbe602fb63eeb8d1f593806f3e0e5e71969d329b2779b9d83736d90e9c23fcef","addressRefs":[]},"f0715f96-8cc2-4bc9-88d4-11542aa9c288":{"id":"f0715f96-8cc2-4bc9-88d4-11542aa9c288","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7695,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"dae88d4b-670f-47e4-b9bb-11c5f8ce3833":{"id":"dae88d4b-670f-47e4-b9bb-11c5f8ce3833","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7696,"content":"The documents herein define the parameters of the Kamino USDC Instance of the Allocation System Primitive.","contentHash":"7f9a5bf4d9d4385396864de396eefa44ad7ec2dd4b1bb2ccf1521a4a1da65efc","addressRefs":[]},"2b1419e1-a279-4172-88dc-a897905ab17e":{"id":"2b1419e1-a279-4172-88dc-a897905ab17e","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7697,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"b9ca0b9a-e633-4902-9b56-39593690a455":{"id":"b9ca0b9a-e633-4902-9b56-39593690a455","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7698,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"11ebac06-18a7-4105-8523-0ae4020eb669":{"id":"11ebac06-18a7-4105-8523-0ae4020eb669","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7699,"content":"Kamino","contentHash":"b4c4574996552f964fff71d974229604d349dbaa253e182a50502aa5fa07dd97","addressRefs":[]},"6d5a7c41-5630-4df4-8995-f7f75df9a866":{"id":"6d5a7c41-5630-4df4-8995-f7f75df9a866","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.1.3","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7700,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"47b8761c-6f72-48dd-a014-05e29c8d6680":{"id":"47b8761c-6f72-48dd-a014-05e29c8d6680","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.1.4","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7701,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"8d7a5c83-d917-40ed-9fc7-f912fe9933f6":{"id":"8d7a5c83-d917-40ed-9fc7-f912fe9933f6","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7702,"content":"kUSDC","contentHash":"d78ad094b9e82186bee8626550409b2ceeef31413df39367c8f3380edd389776","addressRefs":[]},"76c37fb1-f74c-486f-8523-d485de5c278c":{"id":"76c37fb1-f74c-486f-8523-d485de5c278c","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7703,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"3f3deb3c-e023-4b37-94af-5e93a592ce3a":{"id":"3f3deb3c-e023-4b37-94af-5e93a592ce3a","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7704,"content":"`9DrvZvyWh1HuAoZxvYWMvkf2XCzryCpGgHqrMjyDWpmo`","contentHash":"9e09d23c853bef51e2a20fa8db46705459d059a1b072be6e66262091a0880977","addressRefs":["9DrvZvyWh1HuAoZxvYWMvkf2XCzryCpGgHqrMjyDWpmo"]},"537e73fd-f7d6-4776-af11-1cc83433dd43":{"id":"537e73fd-f7d6-4776-af11-1cc83433dd43","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7705,"content":"`EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`","contentHash":"4b8f042fe55c0df16c539b2e7f1e6ef76539f83b17d7ed0c7f3df8856822064d","addressRefs":["EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"]},"3740064f-912c-4ab0-8b79-8f2c5970ed0b":{"id":"3740064f-912c-4ab0-8b79-8f2c5970ed0b","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7706,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Kamino USDC Instance of the Allocation System Primitive.","contentHash":"71c02b7b9f9befc854da34bed8a78da9c3440468905e26585e249430f1fee9c7","addressRefs":[]},"9f0cdd10-d1fe-4da5-9b64-6757195ebf8b":{"id":"9f0cdd10-d1fe-4da5-9b64-6757195ebf8b","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7707,"content":"`GZ6vUcBZk4QiaBUhhn1TpX6S7FiXK71Pogke1RnBc3zA`","contentHash":"1654386fc04f40f32e3355b09f7675612719c797a3723ef7144c9c0bf33513ca","addressRefs":["GZ6vUcBZk4QiaBUhhn1TpX6S7FiXK71Pogke1RnBc3zA"]},"a1cf8da0-dc37-4abb-9205-aee0a825363a":{"id":"a1cf8da0-dc37-4abb-9205-aee0a825363a","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7708,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"564245a6-2191-4434-ba16-52a2f76d4acd":{"id":"564245a6-2191-4434-ba16-52a2f76d4acd","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7709,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"2f8505017d4178412d7ccd4f3aab09f3c5fbb3ea19e118551d5e215c32824991","addressRefs":[]},"f21f04b3-30d3-4b5e-81e0-2e83dda36b37":{"id":"f21f04b3-30d3-4b5e-81e0-2e83dda36b37","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7710,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"fe79db33-1328-4baa-867d-141173666215":{"id":"fe79db33-1328-4baa-867d-141173666215","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7711,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"44ed77d2-a81c-41d3-a77c-84b6e9293a3e":{"id":"44ed77d2-a81c-41d3-a77c-84b6e9293a3e","doc_no":"A.6.1.1.3.2.6.1.3.1.1.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7712,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"4adbf528-4a16-496c-974f-ce612af69162":{"id":"4adbf528-4a16-496c-974f-ce612af69162","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3","title":"Solana - Kamino USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7713,"content":"The documents herein contain the Instance Configuration Document for the Kamino USDT Instance.","contentHash":"5bba41a4ceb39a0dcfe8e85227800caeb3c50101b3981bb2d3e4daf1ddc7cb60","addressRefs":[]},"1c188d86-597d-414b-bb2f-8cc6250303d0":{"id":"1c188d86-597d-414b-bb2f-8cc6250303d0","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7714,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"d10c9266-b16b-4914-aba8-796acda503d0":{"id":"d10c9266-b16b-4914-aba8-796acda503d0","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7715,"content":"The documents herein define the parameters of the Kamino USDT Instance of the Allocation System Primitive.","contentHash":"55f1a53631382553f6ae643a6bf29753ca43543a932364d343cc67ac63bc9649","addressRefs":[]},"52324ef9-2f4b-4774-8b67-0cd4397c8194":{"id":"52324ef9-2f4b-4774-8b67-0cd4397c8194","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7716,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"3597fd3c-b4ed-4d7b-b4fa-74c816879966":{"id":"3597fd3c-b4ed-4d7b-b4fa-74c816879966","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7717,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"54e8166d-a2fd-42b6-a716-5a342c4f6f86":{"id":"54e8166d-a2fd-42b6-a716-5a342c4f6f86","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7718,"content":"Kamino","contentHash":"b4c4574996552f964fff71d974229604d349dbaa253e182a50502aa5fa07dd97","addressRefs":[]},"68d30595-356b-4ca3-a820-91a96fd7ac88":{"id":"68d30595-356b-4ca3-a820-91a96fd7ac88","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.1.3","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7719,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"704864d1-80d7-4e63-8389-ef58bac891f7":{"id":"704864d1-80d7-4e63-8389-ef58bac891f7","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.1.4","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7720,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"99b7437e-97a0-4788-828e-bfc3ed5a2d29":{"id":"99b7437e-97a0-4788-828e-bfc3ed5a2d29","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7721,"content":"kUSDT","contentHash":"f2aa4c2b6c5127ca13404234ef586e958f07dbecbea6e9888da328a72bbe5006","addressRefs":[]},"7c2ea693-828d-4c7a-9cfb-c6ae164622af":{"id":"7c2ea693-828d-4c7a-9cfb-c6ae164622af","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7722,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"916d9d97-14f4-4e03-b7ae-fe81a69b664b":{"id":"916d9d97-14f4-4e03-b7ae-fe81a69b664b","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7723,"content":"`B8zf4kojJbwgCRKA7rLaLhRCZBGhgAJp8wPBVZZHMhSv`","contentHash":"a170d55308d7a18b940f6cc00f83a11e929e6b63df58fcf472eb4fe66873b2a5","addressRefs":["B8zf4kojJbwgCRKA7rLaLhRCZBGhgAJp8wPBVZZHMhSv"]},"e14b47e9-9da0-475d-bfe7-001a7339f745":{"id":"e14b47e9-9da0-475d-bfe7-001a7339f745","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7724,"content":"`Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB`","contentHash":"d3b72b9e6472c2270195fa327c0a1d9480285acb3c772f30404d5d8b9397a633","addressRefs":["Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB"]},"4ce2bc6f-e280-4056-9d0c-d640a722fadb":{"id":"4ce2bc6f-e280-4056-9d0c-d640a722fadb","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7725,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Kamino USDT Instance of the Allocation System Primitive.","contentHash":"9f36c3318d9150678f0cd75c23c91300e13a8dcde7a3c2acebff0e32134f6b25","addressRefs":[]},"77b012a2-0e1f-4674-9984-86ac5eb2b53c":{"id":"77b012a2-0e1f-4674-9984-86ac5eb2b53c","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7726,"content":"`ArpjQUCqHvtDQZFR2tFbPPEKYiQHuaJkcFQBdW5NQC4U`","contentHash":"536f766eccf7fa1aee93a50f5dcbae75c1de452e80cae2ebf082fdd4a62ed2ab","addressRefs":["ArpjQUCqHvtDQZFR2tFbPPEKYiQHuaJkcFQBdW5NQC4U"]},"522805d9-5d8c-4147-ab77-f7472512852e":{"id":"522805d9-5d8c-4147-ab77-f7472512852e","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7727,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"7168f4a2-c928-41f5-a4c9-8a8da5fbd2d1":{"id":"7168f4a2-c928-41f5-a4c9-8a8da5fbd2d1","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7728,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDT\n- `slope`: 10,000,000 USDT per day","contentHash":"7e138aedd55ae8967af084fadef1bac129d790b4db936819328d9d9c6ab6f587","addressRefs":[]},"bdbed1a4-1957-442f-b6b6-f68ccb2c372a":{"id":"bdbed1a4-1957-442f-b6b6-f68ccb2c372a","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7729,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"d00abdfb-bc4b-476a-9962-06469889ace7":{"id":"d00abdfb-bc4b-476a-9962-06469889ace7","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7730,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"7c687440-6b84-40a7-8fa1-db0d15a33309":{"id":"7c687440-6b84-40a7-8fa1-db0d15a33309","doc_no":"A.6.1.1.3.2.6.1.3.1.1.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7731,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"8b972495-2f93-4d88-b1f4-d447e2d821a3":{"id":"8b972495-2f93-4d88-b1f4-d447e2d821a3","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4","title":"Solana - Kamino USDG Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7732,"content":"The documents herein contain the Instance Configuration Document for the Kamino USDG Instance.","contentHash":"666da6986908ce6bbee7131ec6e111e7c9fa3b90cc7d74a22f76cb9f61775127","addressRefs":[]},"65169498-1d46-4f29-8144-535eb26bd9b2":{"id":"65169498-1d46-4f29-8144-535eb26bd9b2","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7733,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"a37d7fbb-8326-4419-8d1d-7056ec48254a":{"id":"a37d7fbb-8326-4419-8d1d-7056ec48254a","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7734,"content":"The documents herein define the parameters of the Kamino USDG Instance of the Allocation System Primitive.","contentHash":"bfa1b3c9a62b2e01abb2833c8ff2fd992df5bd4c57de05a6e6cae6306b311ca9","addressRefs":[]},"db7a0534-1a4b-4a75-af13-5e1af34a5726":{"id":"db7a0534-1a4b-4a75-af13-5e1af34a5726","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7735,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"f2493a5e-7bd7-42f3-8f8a-9e8d2f526d71":{"id":"f2493a5e-7bd7-42f3-8f8a-9e8d2f526d71","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7736,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"71c5639c-26e8-4ea5-b99f-46208feca2b1":{"id":"71c5639c-26e8-4ea5-b99f-46208feca2b1","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7737,"content":"Kamino","contentHash":"b4c4574996552f964fff71d974229604d349dbaa253e182a50502aa5fa07dd97","addressRefs":[]},"4ec9542e-700c-4e1f-b25d-33823fa13f54":{"id":"4ec9542e-700c-4e1f-b25d-33823fa13f54","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.1.3","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7738,"content":"USDG","contentHash":"b02ff0d462b8abbde681bcb62ecc1f0e60664ff3775977f96fe17da501d80f65","addressRefs":[]},"de1bbb96-f280-4d42-9aa7-dacb6474d6a1":{"id":"de1bbb96-f280-4d42-9aa7-dacb6474d6a1","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.1.4","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7739,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"1416747d-d36c-48d8-ad9c-45c9c538788b":{"id":"1416747d-d36c-48d8-ad9c-45c9c538788b","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7740,"content":"kUSDG","contentHash":"71714c1c38efbc298a68421f94b07d63a6d776f06983a0ea2e59b37c5b21122e","addressRefs":[]},"1d1fc05b-ac3c-4991-a3c1-3b90f8eaad29":{"id":"1d1fc05b-ac3c-4991-a3c1-3b90f8eaad29","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7741,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"852f18fd-9ca0-4d7c-8f5b-4ce1adf6e447":{"id":"852f18fd-9ca0-4d7c-8f5b-4ce1adf6e447","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7742,"content":"`BG6gsv8goyoJguEbLquUZFNiZ8aGTXgo4DyH9h8z9qao`","contentHash":"0c333e72322cd9ffc6e373d044784a9138aa7fcb7a0cce038e53c2c6d4b4e3ea","addressRefs":["BG6gsv8goyoJguEbLquUZFNiZ8aGTXgo4DyH9h8z9qao"]},"96e864d5-57b9-44e7-9b9b-5de29477569d":{"id":"96e864d5-57b9-44e7-9b9b-5de29477569d","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7743,"content":"`2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH`","contentHash":"eb8559c3b6fb1e07de6e1db2a1163ec3908c0de7ae7b996118902cf35dd9b746","addressRefs":["2u1tszSeqZ3qBWF3uNGPFc8TzMk2tdiwknnRMWGWjGWH"]},"07f18f84-22d3-468d-8a2d-5874ec703a23":{"id":"07f18f84-22d3-468d-8a2d-5874ec703a23","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7744,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Kamino USDG Instance of the Allocation System Primitive.","contentHash":"2947146d46af80ea008105358d60f33509cdeb310f5c0e90c4996eed1102d37c","addressRefs":[]},"2857d96b-1196-48a5-9983-b629f708d75a":{"id":"2857d96b-1196-48a5-9983-b629f708d75a","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7745,"content":"`5JYk4vbZTFcBiHK5HzQTmYcT6kosEKJV62tYTCTpT6xy`","contentHash":"9bd1a57c89e9411df055ab919e384c731a33d9215d61ebaab7d4f48748c2a681","addressRefs":["5JYk4vbZTFcBiHK5HzQTmYcT6kosEKJV62tYTCTpT6xy"]},"1e88d799-a269-44e7-9ce4-2b3f871ece01":{"id":"1e88d799-a269-44e7-9ce4-2b3f871ece01","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7746,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"bbb53065-3606-45db-9c40-d49cfa6193e3":{"id":"bbb53065-3606-45db-9c40-d49cfa6193e3","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7747,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDG\n- `slope`: 10,000,000 USDG per day","contentHash":"b2689e9b340165f01c4c931b219b8bb2ac6844202f719e764423d5d0f76de62f","addressRefs":[]},"5af501f7-f554-4b02-9cf0-742fa8aeee82":{"id":"5af501f7-f554-4b02-9cf0-742fa8aeee82","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7748,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"1c475afa-a3ed-4b6f-99ee-ec1073880484":{"id":"1c475afa-a3ed-4b6f-99ee-ec1073880484","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7749,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"770281c7-e626-4f05-8c64-0f0af533a7ea":{"id":"770281c7-e626-4f05-8c64-0f0af533a7ea","doc_no":"A.6.1.1.3.2.6.1.3.1.1.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7750,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"dd6cf5ec-6ccd-46af-9c4e-0858f79948f7":{"id":"dd6cf5ec-6ccd-46af-9c4e-0858f79948f7","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5","title":"Solana - Kamino PYUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7751,"content":"The documents herein contain the Instance Configuration Document for the Kamino PYUSD Instance.","contentHash":"72fe6ca9ac834fd90b5898bcb6a255a4d8f32e34b5654b6228f5d8559d83d6db","addressRefs":[]},"951520fb-c20b-4962-82fa-b41a5a3ae4d3":{"id":"951520fb-c20b-4962-82fa-b41a5a3ae4d3","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7752,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"6f476ccf-09ce-4390-8ca0-8e92cd089fb3":{"id":"6f476ccf-09ce-4390-8ca0-8e92cd089fb3","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7753,"content":"The documents herein define the parameters of the Kamino PYUSD Instance of the Allocation System Primitive.","contentHash":"829f3170f38928343a95a8fb257a742aa08dde0288c6d01623e16c92ce1309bd","addressRefs":[]},"d9eb7260-03e4-4a82-9d7c-c3cd5c6e5bdb":{"id":"d9eb7260-03e4-4a82-9d7c-c3cd5c6e5bdb","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7754,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"ff242d99-5c3c-439c-a02a-751781177aef":{"id":"ff242d99-5c3c-439c-a02a-751781177aef","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7755,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"267fcf21-2917-45d3-a7fa-ee55bcfe78b9":{"id":"267fcf21-2917-45d3-a7fa-ee55bcfe78b9","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7756,"content":"Kamino","contentHash":"b4c4574996552f964fff71d974229604d349dbaa253e182a50502aa5fa07dd97","addressRefs":[]},"cb3adf9b-1ab7-40c4-b7d2-52a457af1048":{"id":"cb3adf9b-1ab7-40c4-b7d2-52a457af1048","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.1.3","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7757,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"7e4fe3c6-f252-4ee2-abb8-fbf2faa1b54c":{"id":"7e4fe3c6-f252-4ee2-abb8-fbf2faa1b54c","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.1.4","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7758,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"a54c7a30-48e2-4512-8541-4d87be565f13":{"id":"a54c7a30-48e2-4512-8541-4d87be565f13","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7759,"content":"kPYUSD","contentHash":"74b3aa1adb9fe92ab1375d99e0fe0ab2b0ac1d3938015f61971cbf8e29d52558","addressRefs":[]},"5309d275-c87d-47e0-9323-a1150b2d9453":{"id":"5309d275-c87d-47e0-9323-a1150b2d9453","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7760,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"b2442469-85ca-4458-a2b9-fa11ae1c9022":{"id":"b2442469-85ca-4458-a2b9-fa11ae1c9022","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7761,"content":"`2dQkXr1e9LBvT2QcfKrzZaWY6gGAAVoCjLgkWFk3Mhkj`","contentHash":"8a3483be8b56dbd049a18cd2810badd3df1d4dfd360c73ee957080c692de6b5f","addressRefs":["2dQkXr1e9LBvT2QcfKrzZaWY6gGAAVoCjLgkWFk3Mhkj"]},"6bca9d2a-c670-431c-b48d-3bfb3a6055e0":{"id":"6bca9d2a-c670-431c-b48d-3bfb3a6055e0","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7762,"content":"`2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo`","contentHash":"4a85459c0df09ffaff29c39ce66e5b5be18b6b0492659737e33b5a9c8eebea5a","addressRefs":["2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo"]},"2da72590-96a3-4ad7-a346-0a07034356d8":{"id":"2da72590-96a3-4ad7-a346-0a07034356d8","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7763,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Kamino PYUSD Instance of the Allocation System Primitive.","contentHash":"d162cd95956b3efc1bdf2c2b8b8af146ef3b2bf6e34637551c45107caea57ec4","addressRefs":[]},"627adb56-d243-42e7-8268-579c417db818":{"id":"627adb56-d243-42e7-8268-579c417db818","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7764,"content":"`9DULRsF4Cfj2BbYZp9n6deLf16yYnR5EcFicvzLNMC2s`","contentHash":"654b257e8b43689e0ec93e8e9882e129f3cef1c49b6d7c5529c840971a0dde2a","addressRefs":["9DULRsF4Cfj2BbYZp9n6deLf16yYnR5EcFicvzLNMC2s"]},"cb14e916-8015-46a0-812c-be780edec54f":{"id":"cb14e916-8015-46a0-812c-be780edec54f","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7765,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"e9130658-124d-4788-8c2d-6a4352276bd2":{"id":"e9130658-124d-4788-8c2d-6a4352276bd2","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7766,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 PYUSD\n- `slope`: 10,000,000 PYUSD per day","contentHash":"a6f9a6b597531d45e9ef226541d8533ba8b3785fd7853b2cc234428a1a8b36c1","addressRefs":[]},"86989052-581b-4b06-b906-f8b85e661b64":{"id":"86989052-581b-4b06-b906-f8b85e661b64","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7767,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"b8b3c21f-e712-46cf-b36a-79b0682f107f":{"id":"b8b3c21f-e712-46cf-b36a-79b0682f107f","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7768,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"54403309-9bbe-4cac-bc6c-22cfc7ea9748":{"id":"54403309-9bbe-4cac-bc6c-22cfc7ea9748","doc_no":"A.6.1.1.3.2.6.1.3.1.1.5.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7769,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"94351aff-0a88-4d30-a954-f710b136e32e":{"id":"94351aff-0a88-4d30-a954-f710b136e32e","doc_no":"A.6.1.1.3.2.6.1.3.1.2","title":"Drift","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7770,"content":"The Solana Instances of the Drift Protocol with `Active` Status are stored herein.","contentHash":"7131b73bef22a69414802cb9fdaf49ddc1ae42403c52bd45772e894a718b3f29","addressRefs":[]},"5e934067-e691-4247-bfa1-7df9d4625f21":{"id":"5e934067-e691-4247-bfa1-7df9d4625f21","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1","title":"Solana - Drift USDS Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7771,"content":"The documents herein contain the Instance Configuration Document for the Drift USDS Instance.","contentHash":"1d896e60034308f29747628334aca8ae313e7f583674871c87e4f79bfe042773","addressRefs":[]},"5a8a55c4-3e8a-4f08-9a28-4e125b4b5dc0":{"id":"5a8a55c4-3e8a-4f08-9a28-4e125b4b5dc0","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7772,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"60970f9a-c632-462f-b3c9-83c33899b48c":{"id":"60970f9a-c632-462f-b3c9-83c33899b48c","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7773,"content":"The documents herein define the parameters of the Drift USDS Instance of the Allocation System Primitive.","contentHash":"5bd0a5ccf521604042d0117548b527d25db575732a98247c393bdb96d687c04e","addressRefs":[]},"12d6850f-1d4c-4eb7-9bf6-a3686534930a":{"id":"12d6850f-1d4c-4eb7-9bf6-a3686534930a","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7774,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"2c80a41b-04ce-4dd9-9d9e-e02f4ed04222":{"id":"2c80a41b-04ce-4dd9-9d9e-e02f4ed04222","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7775,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"1db37f5c-f9f9-4ab3-b3b8-98095c22a145":{"id":"1db37f5c-f9f9-4ab3-b3b8-98095c22a145","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7776,"content":"Drift","contentHash":"ccc51f43e1fd58a3f83df5bbdfd04d20a4c9e04b045c709acb6f3a1797310068","addressRefs":[]},"68739838-07ae-49d6-9f9b-699a06478e31":{"id":"68739838-07ae-49d6-9f9b-699a06478e31","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.1.3","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7777,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"d44bb449-b540-4e7c-8e81-f5781ea9fb7c":{"id":"d44bb449-b540-4e7c-8e81-f5781ea9fb7c","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.1.4","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7778,"content":"USDS","contentHash":"7b9d4968544ef5b28c0f688e3e09c31f972b3ac30d2c08e5abeb52437e3bccc3","addressRefs":[]},"ef18b85f-9ba1-4877-b488-4f4c254f2ec7":{"id":"ef18b85f-9ba1-4877-b488-4f4c254f2ec7","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7779,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"89f44d6a-c066-47d7-9411-4d1b733ff69e":{"id":"89f44d6a-c066-47d7-9411-4d1b733ff69e","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7780,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"0c03ae38-d4cb-4d24-9e7a-74dcc077367a":{"id":"0c03ae38-d4cb-4d24-9e7a-74dcc077367a","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7781,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"1ef8c53e-e019-45ee-a91e-76e32c324a36":{"id":"1ef8c53e-e019-45ee-a91e-76e32c324a36","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7782,"content":"`USDSwr9ApdHk5bvJKMjzff41FfuX8bSxdKcR81vTwcA`","contentHash":"3be7c5cf0835df149bcfb9997c26373055af42734944d45edf0a3e178626db5f","addressRefs":["USDSwr9ApdHk5bvJKMjzff41FfuX8bSxdKcR81vTwcA"]},"1bd446ed-d9e7-41a0-89c2-40291f9c0e36":{"id":"1bd446ed-d9e7-41a0-89c2-40291f9c0e36","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7783,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Drift USDS Instance of the Allocation System Primitive.","contentHash":"c8de156af43cb6b709d78a020a1b8097ef71adedd255153b9d3d69a1a83e8d6e","addressRefs":[]},"19468eb6-4192-4db4-9289-b3110b296b29":{"id":"19468eb6-4192-4db4-9289-b3110b296b29","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7784,"content":"`DFrV1Nyfvoucz3nofVRGFmhWAxV1qz1xQxz5rQi4MNot`","contentHash":"3b514d94654d067627f4dd560582e8b46c591824b8b82c2d0021e8cac6e77b97","addressRefs":["DFrV1Nyfvoucz3nofVRGFmhWAxV1qz1xQxz5rQi4MNot"]},"e9d53583-526e-441e-87a6-79038aad553e":{"id":"e9d53583-526e-441e-87a6-79038aad553e","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7785,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"305929f9-e0f3-494e-9679-264ca1d6026c":{"id":"305929f9-e0f3-494e-9679-264ca1d6026c","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7786,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDS\n- `slope`: 10,000,000 USDS per day","contentHash":"f6f5bd0dbd7f1aa291c7b4b8741f0eaa51b4f56811231c27f487cd9979340538","addressRefs":[]},"09c83fd0-73ec-482b-8c87-bee7c0e5e57b":{"id":"09c83fd0-73ec-482b-8c87-bee7c0e5e57b","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7787,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"b03fa016-bec9-45b5-accb-b1edec40114a":{"id":"b03fa016-bec9-45b5-accb-b1edec40114a","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7788,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"c2bc44bc-1c9e-46d1-977f-abe117105d88":{"id":"c2bc44bc-1c9e-46d1-977f-abe117105d88","doc_no":"A.6.1.1.3.2.6.1.3.1.2.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7789,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"ddf9f671-bf5c-4f21-af92-63cce7815af4":{"id":"ddf9f671-bf5c-4f21-af92-63cce7815af4","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2","title":"Solana - Drift USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7790,"content":"The documents herein contain the Instance Configuration Document for the Drift USDC Instance.","contentHash":"0eedc550b3e5098bd0ce5bfb6851f51c413949c95f46aac56565d923ffd8a2d2","addressRefs":[]},"1cf7cf5e-c80f-43d6-bfa8-2b9088c5745d":{"id":"1cf7cf5e-c80f-43d6-bfa8-2b9088c5745d","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7791,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"4f7d5f5c-7d07-4aa6-a5c4-f3a25e67135d":{"id":"4f7d5f5c-7d07-4aa6-a5c4-f3a25e67135d","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7792,"content":"The documents herein define the parameters of the Drift USDC Instance of the Allocation System Primitive.","contentHash":"671fb9964f0837454c3f0e71d14de7f8c0ae86dec55e55b70be923813dad5bcf","addressRefs":[]},"154f31f7-6c8b-4948-b8f3-377e64b14bfb":{"id":"154f31f7-6c8b-4948-b8f3-377e64b14bfb","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7793,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"36b5102d-817e-4b01-8dcb-f0d1c31578a4":{"id":"36b5102d-817e-4b01-8dcb-f0d1c31578a4","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7794,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"d814206c-ecbb-4e0d-b404-a5946f76f429":{"id":"d814206c-ecbb-4e0d-b404-a5946f76f429","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7795,"content":"Drift","contentHash":"ccc51f43e1fd58a3f83df5bbdfd04d20a4c9e04b045c709acb6f3a1797310068","addressRefs":[]},"4fce1780-e418-4080-9e19-4b7cba7b7d9b":{"id":"4fce1780-e418-4080-9e19-4b7cba7b7d9b","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.1.3","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7796,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"2378b485-cdcf-4417-b283-a5ca2462ef27":{"id":"2378b485-cdcf-4417-b283-a5ca2462ef27","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.1.4","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7797,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"b486d70e-c793-41b8-a70b-e4b8e71276b0":{"id":"b486d70e-c793-41b8-a70b-e4b8e71276b0","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7798,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"5642e99a-b127-4e2c-8055-66cfdae46972":{"id":"5642e99a-b127-4e2c-8055-66cfdae46972","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7799,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"63026c1f-8a06-4cb4-9bcc-6509bda69cc6":{"id":"63026c1f-8a06-4cb4-9bcc-6509bda69cc6","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7800,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"f8f92260-eda4-484c-ae9e-ab74174f7572":{"id":"f8f92260-eda4-484c-ae9e-ab74174f7572","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7801,"content":"`EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`","contentHash":"4b8f042fe55c0df16c539b2e7f1e6ef76539f83b17d7ed0c7f3df8856822064d","addressRefs":["EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v"]},"963b3617-57ac-4ebb-a240-ed186225d16e":{"id":"963b3617-57ac-4ebb-a240-ed186225d16e","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7802,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Drift USDC Instance of the Allocation System Primitive.","contentHash":"fc7f6c5d1279d62e67a1bb7a2ccf32d5316aef42d24cf45b5aa5e2fae2bf4d20","addressRefs":[]},"69610d1d-df89-4169-966e-808d96b35044":{"id":"69610d1d-df89-4169-966e-808d96b35044","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7803,"content":"`ET3k7uBeXLmeVQW5Tm8xBnLte9FgUSRebgneT57wjuqL`","contentHash":"82985dd444ac066fb6e2f513e06d1d608b54c208d2e9826419c39d360fc9a056","addressRefs":["ET3k7uBeXLmeVQW5Tm8xBnLte9FgUSRebgneT57wjuqL"]},"b722ec68-1d66-49c7-a728-e64e3667059e":{"id":"b722ec68-1d66-49c7-a728-e64e3667059e","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7804,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"7268c2b8-b83b-480c-a51a-66e15e66d4f3":{"id":"7268c2b8-b83b-480c-a51a-66e15e66d4f3","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7805,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDC\n- `slope`: 10,000,000 USDC per day","contentHash":"2f8505017d4178412d7ccd4f3aab09f3c5fbb3ea19e118551d5e215c32824991","addressRefs":[]},"f2c12b28-6cea-400e-af47-f8c0acade37e":{"id":"f2c12b28-6cea-400e-af47-f8c0acade37e","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7806,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"72896ba0-86c9-4291-b8a7-95de8f76acc5":{"id":"72896ba0-86c9-4291-b8a7-95de8f76acc5","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7807,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"074a32ed-ca95-4dea-b9de-10dcc9e2b02c":{"id":"074a32ed-ca95-4dea-b9de-10dcc9e2b02c","doc_no":"A.6.1.1.3.2.6.1.3.1.2.2.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7808,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"300e6f12-800f-4f55-900b-a0697acfb257":{"id":"300e6f12-800f-4f55-900b-a0697acfb257","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3","title":"Solana - Drift USDT Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7809,"content":"The documents herein contain the Instance Configuration Document for the Drift USDT Instance.","contentHash":"464ae085e6d9124b37e148699480b97fd00e5551d1a00f17dc73ededb884b68d","addressRefs":[]},"f8408ed4-839d-481b-8099-8756d568c91c":{"id":"f8408ed4-839d-481b-8099-8756d568c91c","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7810,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"55df082a-1982-4880-8e45-d3c3309008fd":{"id":"55df082a-1982-4880-8e45-d3c3309008fd","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7811,"content":"The documents herein define the parameters of the Drift USDT Instance of the Allocation System Primitive.","contentHash":"e9f9aea649889e20167a4982fc17b3e534512405e8df8397a50a5f171e7cf023","addressRefs":[]},"f3c5a79b-f87f-4d5c-8df2-dad8d6ad6a50":{"id":"f3c5a79b-f87f-4d5c-8df2-dad8d6ad6a50","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7812,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"ce9ee0fb-2f77-4cc7-a1b7-accaf3426521":{"id":"ce9ee0fb-2f77-4cc7-a1b7-accaf3426521","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7813,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"782880a8-2b84-400c-91f3-2048004c74f2":{"id":"782880a8-2b84-400c-91f3-2048004c74f2","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7814,"content":"Drift","contentHash":"ccc51f43e1fd58a3f83df5bbdfd04d20a4c9e04b045c709acb6f3a1797310068","addressRefs":[]},"f5a6429e-f8c4-4606-8e41-c24efb324129":{"id":"f5a6429e-f8c4-4606-8e41-c24efb324129","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.1.3","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7815,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"1cfaeb94-1d8f-40ca-8e03-59684c39ce09":{"id":"1cfaeb94-1d8f-40ca-8e03-59684c39ce09","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.1.4","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7816,"content":"USDT","contentHash":"aecd4b21e5e28e3b4b382cd6a1833b949f0be99544e3344b615625439435b65e","addressRefs":[]},"932d4502-14fe-49d5-adfe-4a5835784e55":{"id":"932d4502-14fe-49d5-adfe-4a5835784e55","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7817,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"8862cc3f-cbfa-4781-989a-e7bc5914610a":{"id":"8862cc3f-cbfa-4781-989a-e7bc5914610a","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7818,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"04ab961e-8169-457c-887f-9427909910bc":{"id":"04ab961e-8169-457c-887f-9427909910bc","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7819,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"fb3ea256-b870-475a-82d9-5c1223154c87":{"id":"fb3ea256-b870-475a-82d9-5c1223154c87","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7820,"content":"`Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB`","contentHash":"d3b72b9e6472c2270195fa327c0a1d9480285acb3c772f30404d5d8b9397a633","addressRefs":["Es9vMFrzaCERmJfrF4H2FYD4KCoNkY11McCe8BenwNYB"]},"2537cc72-26f4-44d5-9b87-8cd6fa6c6f55":{"id":"2537cc72-26f4-44d5-9b87-8cd6fa6c6f55","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7821,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Drift USDT Instance of the Allocation System Primitive.","contentHash":"3f940bf6f051f6bf8db3acdf3441fbcbcf053ee505515ae1e6b8c8b471446b9a","addressRefs":[]},"5eb625d1-f3ea-4b5a-99ab-0fd668aeb19f":{"id":"5eb625d1-f3ea-4b5a-99ab-0fd668aeb19f","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7822,"content":"`Gb8TLtzWtUVVm5VaEXeZS7hdeXMc675PBvWimeep6aU1`","contentHash":"70d3aaca9970fbb46e83c0ebade0da46f06d21f63c4857497fd99bd1d552b78c","addressRefs":["Gb8TLtzWtUVVm5VaEXeZS7hdeXMc675PBvWimeep6aU1"]},"c9fcbc68-412f-4c62-a59d-a100ccb1e9f2":{"id":"c9fcbc68-412f-4c62-a59d-a100ccb1e9f2","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7823,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"7ad9224b-5ad1-4aa5-9249-11823d8fdd39":{"id":"7ad9224b-5ad1-4aa5-9249-11823d8fdd39","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7824,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 USDT\n- `slope`: 10,000,000 USDT per day","contentHash":"7e138aedd55ae8967af084fadef1bac129d790b4db936819328d9d9c6ab6f587","addressRefs":[]},"fdb802a9-5100-4951-b9d6-a7307e2c8cbe":{"id":"fdb802a9-5100-4951-b9d6-a7307e2c8cbe","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7825,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"d7c17775-2373-4214-b125-3f9ff3055b54":{"id":"d7c17775-2373-4214-b125-3f9ff3055b54","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7826,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"a276dc64-2505-43fa-a3d5-82cebeaeabff":{"id":"a276dc64-2505-43fa-a3d5-82cebeaeabff","doc_no":"A.6.1.1.3.2.6.1.3.1.2.3.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7827,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"ea272eb2-0ffd-4704-a02c-ee4f047cb8a3":{"id":"ea272eb2-0ffd-4704-a02c-ee4f047cb8a3","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4","title":"Solana - Drift PYUSD Instance Configuration Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7828,"content":"The documents herein contain the Instance Configuration Document for the Drift PYUSD Instance.","contentHash":"4f29e61b30076feaecc4b3f299b01cf397a511f266753c49fb6db25fe3be24c7","addressRefs":[]},"10cda4cd-9cdc-45f8-a63f-094abe5adc3b":{"id":"10cda4cd-9cdc-45f8-a63f-094abe5adc3b","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7829,"content":"**`Pending`**","contentHash":"a8dd20a28e1ec4173e652b8b9618dabd64197e5734dd2bec38da080989e5eb9e","addressRefs":[]},"8387df83-2229-4b49-bd90-142c370c550d":{"id":"8387df83-2229-4b49-bd90-142c370c550d","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7830,"content":"The documents herein define the parameters of the Drift PYUSD Instance of the Allocation System Primitive.","contentHash":"8cc75f805804a2ed4b35e8250b6dd43ccee1cd715ff175d6c30338755202b9b3","addressRefs":[]},"f332c28d-9fa7-4d29-bddf-c9367265fa0e":{"id":"f332c28d-9fa7-4d29-bddf-c9367265fa0e","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7831,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"cd79375b-5836-4661-8272-08c5a64403a8":{"id":"cd79375b-5836-4661-8272-08c5a64403a8","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7832,"content":"Solana","contentHash":"852885123b68825bd265ee97457dc8b3c786b4f07d1964587e00f69d96aca55e","addressRefs":[]},"a9ce9a01-ab10-49fa-915a-9045a9d175a1":{"id":"a9ce9a01-ab10-49fa-915a-9045a9d175a1","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7833,"content":"Drift","contentHash":"ccc51f43e1fd58a3f83df5bbdfd04d20a4c9e04b045c709acb6f3a1797310068","addressRefs":[]},"cefe0e20-f880-43d6-b447-31df98c89646":{"id":"cefe0e20-f880-43d6-b447-31df98c89646","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.1.3","title":"Market","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7834,"content":"Main","contentHash":"1f124cca3d86e30a18c4b27703a7a5cac0614c5ee91343033997f7184eecd2e2","addressRefs":[]},"dce9457e-6054-4230-a28b-ad9db2705cf9":{"id":"dce9457e-6054-4230-a28b-ad9db2705cf9","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.1.4","title":"Asset Supplied By Keel Liquidity Layer","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7835,"content":"PYUSD","contentHash":"a0df2a6f0a2e819e60224ba13dd09a8c6ccf621c34278c482fe262f4ef60fe10","addressRefs":[]},"6bff132c-66c9-43c9-a0fb-88f558b41829":{"id":"6bff132c-66c9-43c9-a0fb-88f558b41829","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.1.5","title":"Token","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7836,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"217ebbef-bf36-4636-b61c-3751b2d56065":{"id":"217ebbef-bf36-4636-b61c-3751b2d56065","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7837,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"67e955f5-75d9-4428-8f10-4ffe48fdc933":{"id":"67e955f5-75d9-4428-8f10-4ffe48fdc933","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7838,"content":"N/A","contentHash":"79225b8bba83bfc0371970ae577b5d113d90320892534ddb2b66512f983d3341","addressRefs":[]},"d4cbf289-dd54-43ad-b608-35eb7a71b49e":{"id":"d4cbf289-dd54-43ad-b608-35eb7a71b49e","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7839,"content":"`2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo`","contentHash":"4a85459c0df09ffaff29c39ce66e5b5be18b6b0492659737e33b5a9c8eebea5a","addressRefs":["2b1kV6DkPAnxd5ixfnxCpjxmKwqjjaYmCZfHsFu24GXo"]},"9f4549ed-69c5-4660-a8da-9648cecf5836":{"id":"9f4549ed-69c5-4660-a8da-9648cecf5836","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.3","title":"Rate Limit Information","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7840,"content":"The specific `Integration` account contains the rate limit information to control inflows into the Drift PYUSD Instance of the Allocation System Primitive.","contentHash":"b003b01aa2ddae1371fb693462f587ab990a02e14484906fcd99244dc7ef79ed","addressRefs":[]},"9d7cc1c8-9ad0-4cc2-84ad-9e54687eb60d":{"id":"9d7cc1c8-9ad0-4cc2-84ad-9e54687eb60d","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.3.1","title":"Integration Account Address","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7841,"content":"`5rqJu2NrbMBnW2B2mejSPUV589gb7pvHSGrWQyQqnQz5`","contentHash":"e69db7038cb31db08bcbf38ba232552ac5bc8d348fe0ff2a32e460275b88b26a","addressRefs":["5rqJu2NrbMBnW2B2mejSPUV589gb7pvHSGrWQyQqnQz5"]},"715c3865-bf52-41cd-84e3-d57508c27b5f":{"id":"715c3865-bf52-41cd-84e3-d57508c27b5f","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7842,"content":"The current `maxAmount` and `slope` for this conduit’s deposit and withdrawal are defined in the subdocuments herein.","contentHash":"5f166606100dba242878d39d234485541d02697480614ed52cf4e50ac8044a8d","addressRefs":[]},"f888618b-acc1-4ef8-9e02-d292448da6f0":{"id":"f888618b-acc1-4ef8-9e02-d292448da6f0","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.4.1","title":"Deposit Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7843,"content":"The deposit rate limits are:\n\n- `maxAmount`: 25,000,000 PYUSD\n- `slope`: 10,000,000 PYUSD per day","contentHash":"a6f9a6b597531d45e9ef226541d8533ba8b3785fd7853b2cc234428a1a8b36c1","addressRefs":[]},"074d5acf-8e9c-40bc-a1a0-f31bafb4f3b6":{"id":"074d5acf-8e9c-40bc-a1a0-f31bafb4f3b6","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7844,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"474e5b21-e27b-466d-b337-3a4b205d1f96":{"id":"474e5b21-e27b-466d-b337-3a4b205d1f96","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7845,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"d05923ef-0b89-4870-a080-920a6e81f417":{"id":"d05923ef-0b89-4870-a080-920a6e81f417","doc_no":"A.6.1.1.3.2.6.1.3.1.2.4.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7846,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Keel Liquidity Layer processes.","contentHash":"68bbef324b6048946aa0cced36c9399fb342e9c2bb99333fb6d83a445c0618ec","addressRefs":[]},"a1286844-4299-49fd-b744-51b8a0c84494":{"id":"a1286844-4299-49fd-b744-51b8a0c84494","doc_no":"A.6.1.1.3.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7847,"content":"The Instances of the Keel Liquidity Layer with `Completed` Status are stored herein.","contentHash":"9fd84b376ca4a8c815e096c71eaff4fafc2ba192ca0535ffbb864a870133f5d6","addressRefs":[]},"712b3441-b303-4296-8f07-dc298109308e":{"id":"712b3441-b303-4296-8f07-dc298109308e","doc_no":"A.6.1.1.3.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7848,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.6.1.3 - Active Instances](b9316097-ab93-4a8b-aa51-1e44ceb69c4d).","contentHash":"4cd5d9a2a30ea7ac66ef0da75bd50a73f615c59e738659b445fba6ce8a84a12f","addressRefs":[]},"af316389-e11d-4205-a14e-bb3c230ba2b5":{"id":"af316389-e11d-4205-a14e-bb3c230ba2b5","doc_no":"A.6.1.1.3.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7849,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"61b92e4ee881283ea85090aa3744f487b064821ffbe1ea8824ad4813dabaf12e","addressRefs":[]},"fcf3b78f-e91e-45f2-bd4d-14c1a3a97c1f":{"id":"fcf3b78f-e91e-45f2-bd4d-14c1a3a97c1f","doc_no":"A.6.1.1.3.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7850,"content":"The documents herein organize all base information relevant to Keel’s usage of the Junior Risk Capital Rental Primitive.","contentHash":"e02aecc0b57344d6c381b4262ed6058ac2854f8adf09437b413034ef26d155fd","addressRefs":[]},"45fe1729-7481-4215-8399-dd9718e37abf":{"id":"45fe1729-7481-4215-8399-dd9718e37abf","doc_no":"A.6.1.1.3.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7851,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"9264bed6-21a2-4e39-8546-0ab157380740":{"id":"9264bed6-21a2-4e39-8546-0ab157380740","doc_no":"A.6.1.1.3.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7852,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"7585f2d5-a12a-4526-9dbd-88fb210dd4aa":{"id":"7585f2d5-a12a-4526-9dbd-88fb210dd4aa","doc_no":"A.6.1.1.3.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7853,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"23138f00-8867-4b18-81fa-713007909f8f":{"id":"23138f00-8867-4b18-81fa-713007909f8f","doc_no":"A.6.1.1.3.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7854,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.6.2.2 - Active Instances](ee196317-63fc-4f69-a985-2a4f5a5be4e5), whereas failed Invocations are Archived in [A.6.1.1.3.2.6.2.1.5 - Hub Data Repository](74b8a03c-e123-4517-9c60-f445fc958174).","contentHash":"55fd378ed222b07dfc957f74c00e2058238256212101d2283a9a85c6fd900146","addressRefs":[]},"74b8a03c-e123-4517-9c60-f445fc958174":{"id":"74b8a03c-e123-4517-9c60-f445fc958174","doc_no":"A.6.1.1.3.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7855,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"67e1b1e7-eb74-4b14-a125-0e9245266878":{"id":"67e1b1e7-eb74-4b14-a125-0e9245266878","doc_no":"A.6.1.1.3.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7856,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"45ecc8cb-5ae7-4ea3-9edf-d1ac8ce2b860":{"id":"45ecc8cb-5ae7-4ea3-9edf-d1ac8ce2b860","doc_no":"A.6.1.1.3.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7857,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"50cf8700-8938-4dce-b7b5-4dfc3bd92836":{"id":"50cf8700-8938-4dce-b7b5-4dfc3bd92836","doc_no":"A.6.1.1.3.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7858,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"ee196317-63fc-4f69-a985-2a4f5a5be4e5":{"id":"ee196317-63fc-4f69-a985-2a4f5a5be4e5","doc_no":"A.6.1.1.3.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7859,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"14b1b9d8-c60a-4cb5-a06b-a059f354bcec":{"id":"14b1b9d8-c60a-4cb5-a06b-a059f354bcec","doc_no":"A.6.1.1.3.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7860,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"2b4b1b5a-e6a7-4743-9263-0fa8872d2f68":{"id":"2b4b1b5a-e6a7-4743-9263-0fa8872d2f68","doc_no":"A.6.1.1.3.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7861,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.6.2.2 - Active Instances](ee196317-63fc-4f69-a985-2a4f5a5be4e5).","contentHash":"d928dbad51126bc6672a4e1378e536669f6d65d203e0fd50f8173f1acb57a9fb","addressRefs":[]},"d12e1955-a592-4cf8-8b98-24ccfb431409":{"id":"d12e1955-a592-4cf8-8b98-24ccfb431409","doc_no":"A.6.1.1.3.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7862,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"6d8d5a5a5756749fa80e517cbf741d2114c50a4c97ca6ec520af006b26626d45","addressRefs":[]},"df75861d-ff07-4d63-9d39-f43bfb2b5b75":{"id":"df75861d-ff07-4d63-9d39-f43bfb2b5b75","doc_no":"A.6.1.1.3.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7863,"content":"The documents herein organize all base information relevant to Keel’s usage of the Asset Liability Management Rental Primitive.","contentHash":"9859aa407f52c8b5e2801eb32c8ff75b62bd05b9d34d36fbb4d28d332a293f1e","addressRefs":[]},"029950f2-bacc-4941-9ebe-b7c6770dbb1b":{"id":"029950f2-bacc-4941-9ebe-b7c6770dbb1b","doc_no":"A.6.1.1.3.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7864,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"7b21f5bd-68dd-4cf6-8048-cb5eef547b47":{"id":"7b21f5bd-68dd-4cf6-8048-cb5eef547b47","doc_no":"A.6.1.1.3.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7865,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"793d20ec-54b7-4f18-9da5-5ecc864eec06":{"id":"793d20ec-54b7-4f18-9da5-5ecc864eec06","doc_no":"A.6.1.1.3.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7866,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"d0c0850d-9f45-4d6c-bc22-b191a41d1e2a":{"id":"d0c0850d-9f45-4d6c-bc22-b191a41d1e2a","doc_no":"A.6.1.1.3.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7867,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.6.3.2 - Active Instances](537fef57-4e7f-49d7-ac58-b23ed98aff7c), whereas failed Invocations are Archived in [A.6.1.1.3.2.6.3.1.5 - Hub Data Repository](ce1d1572-7f0f-45d2-9f08-2eaae70c7b61).","contentHash":"2c71272114cede9f41c4c7b4429332741903a4058ccf356895494a224fabd8ea","addressRefs":[]},"ce1d1572-7f0f-45d2-9f08-2eaae70c7b61":{"id":"ce1d1572-7f0f-45d2-9f08-2eaae70c7b61","doc_no":"A.6.1.1.3.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7868,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"b315b2ed-16b0-4abd-ad83-693c3252fbdc":{"id":"b315b2ed-16b0-4abd-ad83-693c3252fbdc","doc_no":"A.6.1.1.3.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7869,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"8f99b878-ab18-44f3-aaeb-43fb443b7798":{"id":"8f99b878-ab18-44f3-aaeb-43fb443b7798","doc_no":"A.6.1.1.3.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7870,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"93503a72-77c3-4701-b545-3c0f3700ecd2":{"id":"93503a72-77c3-4701-b545-3c0f3700ecd2","doc_no":"A.6.1.1.3.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7871,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"537fef57-4e7f-49d7-ac58-b23ed98aff7c":{"id":"537fef57-4e7f-49d7-ac58-b23ed98aff7c","doc_no":"A.6.1.1.3.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7872,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"2b2af026-ff7e-476b-aa1a-e77eb1fc667a":{"id":"2b2af026-ff7e-476b-aa1a-e77eb1fc667a","doc_no":"A.6.1.1.3.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7873,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"9663607e-e54c-49fb-941f-a1fa5d91542b":{"id":"9663607e-e54c-49fb-941f-a1fa5d91542b","doc_no":"A.6.1.1.3.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7874,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.6.3.2 - Active Instances](537fef57-4e7f-49d7-ac58-b23ed98aff7c).","contentHash":"710b4da6e1456e728b8e210da0af7dad8400a446d9a4c9ef64df9ecad2ac2519","addressRefs":[]},"a99ec5d3-25e3-4391-8914-3ee55203218f":{"id":"a99ec5d3-25e3-4391-8914-3ee55203218f","doc_no":"A.6.1.1.3.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7875,"content":"The documents herein implement the Core Governance Primitives for Keel. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"3d140ba80b2d2bb7c6e77880b3cc3e134786e0a2cb2e867a7cb5e13fb01e7edc","addressRefs":[]},"a3d5bf7f-19fd-47d8-8815-6eb03b9bee1d":{"id":"a3d5bf7f-19fd-47d8-8815-6eb03b9bee1d","doc_no":"A.6.1.1.3.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7876,"content":"The documents herein contain all data and specifications for Keel’s Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"870605d05ee423795b821d2d8322bfb661d248ba09c7a816e690ff54405afa97","addressRefs":[]},"0841bc09-e502-4a45-a5fc-e30d793a423f":{"id":"0841bc09-e502-4a45-a5fc-e30d793a423f","doc_no":"A.6.1.1.3.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7877,"content":"The documents herein organize all base information relevant to Keel’s usage of the Core Governance Reward Primitive.","contentHash":"63c6693e2fbdbd032f1d9057f6acae95c85c35409e2b75da0ab99a07fe21707c","addressRefs":[]},"2aa1d719-9af8-47db-a190-d43677ef0e28":{"id":"2aa1d719-9af8-47db-a190-d43677ef0e28","doc_no":"A.6.1.1.3.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7878,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"11bc952d-781a-439b-9760-83a007fb9dd2":{"id":"11bc952d-781a-439b-9760-83a007fb9dd2","doc_no":"A.6.1.1.3.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7879,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"fc74cce7-ae3b-4ab8-8d4d-cc0f7636c523":{"id":"fc74cce7-ae3b-4ab8-8d4d-cc0f7636c523","doc_no":"A.6.1.1.3.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7880,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"66c63d9c-6bb6-44b7-a754-29a15475e4c0":{"id":"66c63d9c-6bb6-44b7-a754-29a15475e4c0","doc_no":"A.6.1.1.3.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7881,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.3.2.7.1.2 - Active Instances](0b4cc335-c2ed-4b7f-8cb5-eeb1bab394b8), whereas failed Invocations are Archived in [A.6.1.1.3.2.7.1.1.5 - Hub Data Repository](3ab2001f-f1eb-4249-852c-96604a85e987).","contentHash":"0d0fce47733185bbf49c6727cc6aa361dea9ba6bc742e9c2b54ab10cea7ceeea","addressRefs":[]},"3ab2001f-f1eb-4249-852c-96604a85e987":{"id":"3ab2001f-f1eb-4249-852c-96604a85e987","doc_no":"A.6.1.1.3.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7882,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"5e66b56a-fe9d-4d4c-94c6-2d919171e924":{"id":"5e66b56a-fe9d-4d4c-94c6-2d919171e924","doc_no":"A.6.1.1.3.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7883,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"6794a591-d126-42b6-ba59-c61c3c7e9486":{"id":"6794a591-d126-42b6-ba59-c61c3c7e9486","doc_no":"A.6.1.1.3.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7884,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"c84bc632-6972-443a-a02c-f2b45a3678ac":{"id":"c84bc632-6972-443a-a02c-f2b45a3678ac","doc_no":"A.6.1.1.3.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7885,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"0b4cc335-c2ed-4b7f-8cb5-eeb1bab394b8":{"id":"0b4cc335-c2ed-4b7f-8cb5-eeb1bab394b8","doc_no":"A.6.1.1.3.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7886,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"d4d144fb-eaf6-40ab-90c2-e86dc9494a42":{"id":"d4d144fb-eaf6-40ab-90c2-e86dc9494a42","doc_no":"A.6.1.1.3.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7887,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"6a200f7a-611d-4969-8046-6b5b88f6979a":{"id":"6a200f7a-611d-4969-8046-6b5b88f6979a","doc_no":"A.6.1.1.3.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d415ab8-7a66-4d82-98a4-67696a120650","order":7888,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.3.2.7.1.2 - Active Instances](0b4cc335-c2ed-4b7f-8cb5-eeb1bab394b8).","contentHash":"4d765326f686a2423fe81e551f8075474d550c1d6b5c032fb089c33b3dcf0042","addressRefs":[]},"bafbbf28-95dc-41a4-9c55-f3befde4e991":{"id":"bafbbf28-95dc-41a4-9c55-f3befde4e991","doc_no":"A.6.1.1.3.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"bc6aed17-2969-4d04-9af6-c7bf3e4497e6","order":7889,"content":"The documents herein define Keel’s strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"9ad5c52917b99225168e337264bfc7b10c61630dc39db6e6b486b2c18250ee0d","addressRefs":[]},"1889a2a0-7378-487a-a278-aabe3177efff":{"id":"1889a2a0-7378-487a-a278-aabe3177efff","doc_no":"A.6.1.1.3.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"bafbbf28-95dc-41a4-9c55-f3befde4e991","order":7890,"content":"The documents herein specify Keel governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Keel Artifact is specified in the Root Edit Primitive above at [A.6.1.1.3.2.2.2 - Root Edit Primitive](3d02dcbc-6a31-4f63-b464-c8c3ecebb744).","contentHash":"deb4604b116161861fd7d3a8dc843d2ac273e4def97ce9f44aa54c61d20c6673","addressRefs":[]},"63fec69d-a4df-42c3-bb5f-b959e711df56":{"id":"63fec69d-a4df-42c3-bb5f-b959e711df56","doc_no":"A.6.1.1.3.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"bafbbf28-95dc-41a4-9c55-f3befde4e991","order":7891,"content":"Keel uses the Sky Forum for governance-related discussion. Posts should use the \"Keel Prime\" category.","contentHash":"d7b1f2c529678810020db26942f41d4e77d60e182ba8655020d7fa59db2c114a","addressRefs":[]},"8613cc87-2809-4716-8c91-93ff0345f7a8":{"id":"8613cc87-2809-4716-8c91-93ff0345f7a8","doc_no":"A.6.1.1.3.3.1.2","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"bafbbf28-95dc-41a4-9c55-f3befde4e991","order":7892,"content":"The documents herein specify Keel’s emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Keel Artifact.","contentHash":"c32a11893c091a2819c1f9a52fe327c45e87910c18ab0e8c10cfae35e6e3c99b","addressRefs":[]},"ef98d5b6-3542-4b2f-a926-a0648713fa70":{"id":"ef98d5b6-3542-4b2f-a926-a0648713fa70","doc_no":"A.6.1.1.3.3.1.3","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"bafbbf28-95dc-41a4-9c55-f3befde4e991","order":7893,"content":"The documents herein specify Keel’s emergency response protocol in situations solely impacting Keel versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Keel Artifact.","contentHash":"38399872bf573e6708ed27487d4efd28c2671bc4cdad73523d848c81caa35cea","addressRefs":[]},"41ad175e-48c8-4caf-8cb7-638f90ff0ad6":{"id":"41ad175e-48c8-4caf-8cb7-638f90ff0ad6","doc_no":"A.6.1.1.3.3.2","title":"Use Of Idle Funds","type":"Core","depth":6,"parentId":"bafbbf28-95dc-41a4-9c55-f3befde4e991","order":7894,"content":"In the short term prior to Keel's implementation of the Allocation System Primitive, Keel may invest idle funds in low-risk decentralized finance opportunities, including providing liquidity to established lending protocols on Solana. These deployments will be subject to the approval of Operational GovOps.","contentHash":"6c6ef477b5a74108a41a1b786476bedc4259a6931ae862f90f00409dc0674e8e","addressRefs":[]},"e2db688f-a6f1-476a-b7da-dd67d94da35b":{"id":"e2db688f-a6f1-476a-b7da-dd67d94da35b","doc_no":"A.6.1.1.3.3.3","title":"Ecosystem Accords","type":"Core","depth":6,"parentId":"bafbbf28-95dc-41a4-9c55-f3befde4e991","order":7895,"content":"Keel has formally agreed to the Ecosystem Accords herein.","contentHash":"1c24d9ddf7db121cfd3415ac93e3102e949bd501c009eb2be13ab729c98199bb","addressRefs":[]},"962d4b79-2dea-4b86-a72f-8a460189327f":{"id":"962d4b79-2dea-4b86-a72f-8a460189327f","doc_no":"A.6.1.1.3.3.3.1","title":"Ecosystem Accord 3","type":"Core","depth":6,"parentId":"bafbbf28-95dc-41a4-9c55-f3befde4e991","order":7896,"content":"Keel engaged in terms of agreement with Sky in Ecosystem Accord 3, located in [A.2.8.2.3 - Ecosystem Accord 3: Sky And Keel](63a88b08-e6cd-48bf-9cec-64ce7e42ae0e).","contentHash":"b6bfa7ff23c74f1e60d679ee214588f992e0377b3cc3bc766ec83d71cf77d23a","addressRefs":[]},"c88439b5-f456-4e51-8825-42e0ba83546f":{"id":"c88439b5-f456-4e51-8825-42e0ba83546f","doc_no":"A.6.1.1.4","title":"Skybase","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":7897,"content":"The documents herein specify all of the logic for Skybase, including Skybase's strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"675f6e292cf241b404165bac566cc96f98fbf97c8cd649496b62917c17333eea","addressRefs":[]},"a09ca807-8649-45d0-8e80-62baeb042995":{"id":"a09ca807-8649-45d0-8e80-62baeb042995","doc_no":"A.6.1.1.4.1","title":"Introduction","type":"Core","depth":5,"parentId":"c88439b5-f456-4e51-8825-42e0ba83546f","order":7898,"content":"Skybase is an Agent specializing in creating accessible and user-friendly DeFi interfaces. It operates the Sky.money user interface. Sky.money is a non-custodial web application serving as a gateway to the Sky Protocol. Through its AI-powered interface, Sky.money makes digital asset interactions intuitive and accessible for users of all experience levels—all while ensuring users maintain complete control of their assets. Sky.money never takes custody of users' private keys or assets; users retain full responsibility for managing their private keys and digital wallet access. Skybase also operates select key Sky websites utilizing Sky.money subdomains, such as the Sky Governance Voting Portal (vote.sky.money).","contentHash":"292afda19523f0ca3742fef8f4eece3d4446bece9fc67df115e7c30d36761a05","addressRefs":[]},"614f046c-829b-4330-a462-adff2245b36d":{"id":"614f046c-829b-4330-a462-adff2245b36d","doc_no":"A.6.1.1.4.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"c88439b5-f456-4e51-8825-42e0ba83546f","order":7899,"content":"The documents herein implement the Sky Primitives for Skybase. See [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"fe1f0c75c780f8b830c2a1e118957076f4ce22be74bb6d83666b4b6fa19dbd68","addressRefs":[]},"f08231e6-caa9-490d-9d7f-4f65f9076084":{"id":"f08231e6-caa9-490d-9d7f-4f65f9076084","doc_no":"A.6.1.1.4.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7900,"content":"The documents herein implement the Genesis Primitives for Skybase. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"f839fc35c2c455f5feea5b63e84315e107ba22671de62cac4c72665c298e4a85","addressRefs":[]},"301c4673-0279-49e8-9c3b-e810e8223234":{"id":"301c4673-0279-49e8-9c3b-e810e8223234","doc_no":"A.6.1.1.4.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7901,"content":"The documents herein contain all data and specifications for Skybase's Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"804e88f8e631cf39e64128f87f8f3680c9944e098991f4c2fdc88c034815a038","addressRefs":[]},"df8efa45-85c4-4c66-b984-a5ddfc3f3522":{"id":"df8efa45-85c4-4c66-b984-a5ddfc3f3522","doc_no":"A.6.1.1.4.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7902,"content":"The documents herein organize all base information relevant to Skybase's usage of the Agent Creation Primitive.","contentHash":"e47543dc50b75d8e9b999798ef0d5fff637ecbd66fcca244a37f468860de8709","addressRefs":[]},"487d9253-c2ac-44be-a3b4-7474ba38fddd":{"id":"487d9253-c2ac-44be-a3b4-7474ba38fddd","doc_no":"A.6.1.1.4.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7903,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"0f377ebd-60bd-45ad-9996-a2adc324e2cf":{"id":"0f377ebd-60bd-45ad-9996-a2adc324e2cf","doc_no":"A.6.1.1.4.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7904,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"a36c4c17-6870-4458-8f38-7a966871b085":{"id":"a36c4c17-6870-4458-8f38-7a966871b085","doc_no":"A.6.1.1.4.2.1.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7905,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"385addb0-9ee7-4cc0-8fb1-22d6d229198b":{"id":"385addb0-9ee7-4cc0-8fb1-22d6d229198b","doc_no":"A.6.1.1.4.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7906,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.1.1.3.1 - Single Instance Configuration Document](b53a6744-c772-47bf-9bc3-26ffb933a6d6).","contentHash":"1ec1d4bc4185b287139ff78ecc013c3c8fb0071bdb4e4b8a40aa5564a18cc4df","addressRefs":[]},"462d376c-2f8d-497a-beb2-af3e96895733":{"id":"462d376c-2f8d-497a-beb2-af3e96895733","doc_no":"A.6.1.1.4.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7907,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"c2ab6cb7-f482-4993-b9ba-760cf06a7730":{"id":"c2ab6cb7-f482-4993-b9ba-760cf06a7730","doc_no":"A.6.1.1.4.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7908,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"90432b91-3439-4dee-8005-43af1cf2572a":{"id":"90432b91-3439-4dee-8005-43af1cf2572a","doc_no":"A.6.1.1.4.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7909,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"0d52617d-d303-4133-9523-0638d65be070":{"id":"0d52617d-d303-4133-9523-0638d65be070","doc_no":"A.6.1.1.4.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7910,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"aa957ab8-fa9a-4ce0-bb47-e34350f16027":{"id":"aa957ab8-fa9a-4ce0-bb47-e34350f16027","doc_no":"A.6.1.1.4.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7911,"content":"The subtrees for Instances of the Agent Creation Primitive with `Suspended` Status are stored here.","contentHash":"183d20b3c12bea99884c81ff611bff6d5be670766bb91a4f4ccf5339e0a26636","addressRefs":[]},"0334421f-a3a0-4016-94fd-5cb0fc026b25":{"id":"0334421f-a3a0-4016-94fd-5cb0fc026b25","doc_no":"A.6.1.1.4.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7912,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"87ad87f5-5441-4003-8029-b7ce10442119":{"id":"87ad87f5-5441-4003-8029-b7ce10442119","doc_no":"A.6.1.1.4.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7913,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"b53a6744-c772-47bf-9bc3-26ffb933a6d6":{"id":"b53a6744-c772-47bf-9bc3-26ffb933a6d6","doc_no":"A.6.1.1.4.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7914,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"b34cf681-4d8d-406d-997d-a805c2a9911c":{"id":"b34cf681-4d8d-406d-997d-a805c2a9911c","doc_no":"A.6.1.1.4.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7915,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"46d00c31-8877-4db8-981a-659276a86938":{"id":"46d00c31-8877-4db8-981a-659276a86938","doc_no":"A.6.1.1.4.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7916,"content":"The name of the Agent is Skybase.","contentHash":"ae9a8c8b962388ac2ebe2a39e839f405f0f0372e2d902b3a45f521b9fa2ce1d7","addressRefs":[]},"daed1676-6039-459e-9136-5e31617d756b":{"id":"daed1676-6039-459e-9136-5e31617d756b","doc_no":"A.6.1.1.4.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7917,"content":"The address of Skybase's SubProxy Account on the Ethereum Mainnet is `0x08978E3700859E476201c1D7438B3427e3C81140`.","contentHash":"cc2a8ae6ce0410d77163474db2353a2138e7b0fc6f60f867e0492f3093d72080","addressRefs":["0x08978e3700859e476201c1d7438b3427e3c81140"]},"9ae04b66-c6b3-492d-a37f-ae60b583ea62":{"id":"9ae04b66-c6b3-492d-a37f-ae60b583ea62","doc_no":"A.6.1.1.4.2.1.1.3.1.1.3","title":"StarGuard Contract","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7918,"content":"The address of Skybase's StarGuard contract on the Ethereum Mainnet is `0xA170086AeF9b3b81dD73897A0dF56B55e4C2a1F7`.","contentHash":"808aef10d54cdc0a94aa9c1b061725c816fbddec88f7c2edbf5e17cdeeccc596","addressRefs":["0xa170086aef9b3b81dd73897a0df56b55e4c2a1f7"]},"26e062c6-d49e-4f49-b14e-0884d899cbe1":{"id":"26e062c6-d49e-4f49-b14e-0884d899cbe1","doc_no":"A.6.1.1.4.2.1.1.3.1.1.3.1","title":"StarGuard Max Delay","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7919,"content":"The Skybase StarGuard `maxDelay` is seven (7) days.","contentHash":"5aefb8ca553febddc8d1ad3c06f6898c0cf75d38b6cac4c677790c7c28ff432e","addressRefs":[]},"082cb114-b47e-4371-afe5-d7bcba70704a":{"id":"082cb114-b47e-4371-afe5-d7bcba70704a","doc_no":"A.6.1.1.4.2.1.1.3.1.1.4","title":"Genesis Account","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7920,"content":"The address of Skybase's Genesis Account will be specified in a future iteration of the Skybase Artifact.","contentHash":"b323b086ace0955b465fd621ee8f2f6d617a6fdf9dc9d1c0bc5eedeb411825cf","addressRefs":[]},"7b71508d-de87-4c7b-a09a-7168d1d04f81":{"id":"7b71508d-de87-4c7b-a09a-7168d1d04f81","doc_no":"A.6.1.1.4.2.1.1.3.1.1.5","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7921,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"fe988ac4-6a04-46cd-89b0-c78ba8683f14":{"id":"fe988ac4-6a04-46cd-89b0-c78ba8683f14","doc_no":"A.6.1.1.4.2.1.1.3.1.1.5.1","title":"Skybase Foundation","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7922,"content":"The Skybase Foundation is the Prime Foundation associated with Skybase. Its mandate is to support the development, growth, and adoption of Skybase.","contentHash":"84584f6ee8226d3b4c87209ee8de4f5708bc7f0fe20e75103a7a10f3483a3925","addressRefs":[]},"095eabf8-26a4-484a-bdb7-b581799f4679":{"id":"095eabf8-26a4-484a-bdb7-b581799f4679","doc_no":"A.6.1.1.4.2.1.1.3.1.1.5.2","title":"Development Company","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7923,"content":"Skybase's Development Company will be updated in a future iteration of the Artifact.","contentHash":"696c35c939216343986b75c17885d0ca9844c147508dfa2f98f4a311cdbe1431","addressRefs":[]},"c38b8c86-828d-4d31-9ce6-0ba8d8694f1f":{"id":"c38b8c86-828d-4d31-9ce6-0ba8d8694f1f","doc_no":"A.6.1.1.4.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7924,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"638682f2-1973-4c77-afc2-b745b950fbf4":{"id":"638682f2-1973-4c77-afc2-b745b950fbf4","doc_no":"A.6.1.1.4.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7925,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"d6d7788a-4702-4e7f-8bd0-0e1bdb535e79":{"id":"d6d7788a-4702-4e7f-8bd0-0e1bdb535e79","doc_no":"A.6.1.1.4.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7926,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"efc466bf-6681-4c38-ac6a-281d4c1593be":{"id":"efc466bf-6681-4c38-ac6a-281d4c1593be","doc_no":"A.6.1.1.4.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7927,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"587c4557-6622-49af-b64b-9fd48dbc85b1":{"id":"587c4557-6622-49af-b64b-9fd48dbc85b1","doc_no":"A.6.1.1.4.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7928,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"58ddd7d7-28af-4ca3-ac6a-f5d2105f9e79":{"id":"58ddd7d7-28af-4ca3-ac6a-f5d2105f9e79","doc_no":"A.6.1.1.4.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7929,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"4da364d5-3b83-4858-a820-12d4980f6977":{"id":"4da364d5-3b83-4858-a820-12d4980f6977","doc_no":"A.6.1.1.4.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7930,"content":"The documents herein contain all data and specifications for Skybase's instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"a14456cc4b7300bfa72e60d63a600957b7327872fd35e82235921a03a391fe2e","addressRefs":[]},"f4d35d37-831f-4eee-b18f-d9a3d266655e":{"id":"f4d35d37-831f-4eee-b18f-d9a3d266655e","doc_no":"A.6.1.1.4.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7931,"content":"The documents herein organize all base information relevant to Skybase's usage of the Prime Transformation Primitive.","contentHash":"62b616e19169bc66ff6f36e1bda90a9cd9a4139eb5d5af4f4a7dd331e60cce11","addressRefs":[]},"8d69ca15-79c9-4351-b185-a7cd40c4ad71":{"id":"8d69ca15-79c9-4351-b185-a7cd40c4ad71","doc_no":"A.6.1.1.4.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7932,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"190a4493-15a5-4656-9151-b0b9407e03ff":{"id":"190a4493-15a5-4656-9151-b0b9407e03ff","doc_no":"A.6.1.1.4.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7933,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"67062ef3-c534-4ca3-a852-db5529f7e0f4":{"id":"67062ef3-c534-4ca3-a852-db5529f7e0f4","doc_no":"A.6.1.1.4.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7934,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"1f0cc3ff-862b-4a44-9603-1f7368e963dc":{"id":"1f0cc3ff-862b-4a44-9603-1f7368e963dc","doc_no":"A.6.1.1.4.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7935,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.1.2.3.1 - Single Instance Configuration Document](61e2585d-2ef1-43f5-af89-9f68a66dea12).","contentHash":"d794ebfd3767eff707e6b525469389456e32ae672871fa6c5d21efd097294921","addressRefs":[]},"78abc4a4-9a0f-4ee4-b716-db593325bd34":{"id":"78abc4a4-9a0f-4ee4-b716-db593325bd34","doc_no":"A.6.1.1.4.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7936,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"c67c2fad-a4d9-43ce-b6a0-94ab916b8ece":{"id":"c67c2fad-a4d9-43ce-b6a0-94ab916b8ece","doc_no":"A.6.1.1.4.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7937,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"f4a6295d-6cca-48b9-b692-03fc742e00be":{"id":"f4a6295d-6cca-48b9-b692-03fc742e00be","doc_no":"A.6.1.1.4.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7938,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"9ae8a7b5-d386-47e1-aa51-d80c8d781cfb":{"id":"9ae8a7b5-d386-47e1-aa51-d80c8d781cfb","doc_no":"A.6.1.1.4.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7939,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"0eb68a5c-3785-4085-8385-b052711f903c":{"id":"0eb68a5c-3785-4085-8385-b052711f903c","doc_no":"A.6.1.1.4.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7940,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"e8a80c86-33b0-4c9e-9331-5916e9355b28":{"id":"e8a80c86-33b0-4c9e-9331-5916e9355b28","doc_no":"A.6.1.1.4.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7941,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"2bd4f3c4-9d79-4acf-afa9-7fbb2160ef58":{"id":"2bd4f3c4-9d79-4acf-afa9-7fbb2160ef58","doc_no":"A.6.1.1.4.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7942,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"61e2585d-2ef1-43f5-af89-9f68a66dea12":{"id":"61e2585d-2ef1-43f5-af89-9f68a66dea12","doc_no":"A.6.1.1.4.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7943,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"2d442b0e-6f55-4a41-9599-e494a4da5cc1":{"id":"2d442b0e-6f55-4a41-9599-e494a4da5cc1","doc_no":"A.6.1.1.4.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7944,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"afa9a16f-e776-40f1-8e34-923ae661517a":{"id":"afa9a16f-e776-40f1-8e34-923ae661517a","doc_no":"A.6.1.1.4.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7945,"content":"Skybase is a Prime Agent.","contentHash":"21cb8bef146cf33eb20ea98e043bc7513c558d58acc4e9d84e39cc75126babbd","addressRefs":[]},"de857100-9b4b-4fcd-942c-a3b67a5f9a45":{"id":"de857100-9b4b-4fcd-942c-a3b67a5f9a45","doc_no":"A.6.1.1.4.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7946,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"d8eca741-b371-4e0a-b2f5-f10663683efa":{"id":"d8eca741-b371-4e0a-b2f5-f10663683efa","doc_no":"A.6.1.1.4.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7947,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"6f45d32b-f377-480c-b67f-a1d7b2d09ba8":{"id":"6f45d32b-f377-480c-b67f-a1d7b2d09ba8","doc_no":"A.6.1.1.4.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7948,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"70203ad1-71b6-4a80-97a4-d18227cd736e":{"id":"70203ad1-71b6-4a80-97a4-d18227cd736e","doc_no":"A.6.1.1.4.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7949,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"84e3ba93-7ba4-4f52-b54e-5ea6e73da623":{"id":"84e3ba93-7ba4-4f52-b54e-5ea6e73da623","doc_no":"A.6.1.1.4.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7950,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"102b2492-34f9-4f2f-8f42-593aa8871129":{"id":"102b2492-34f9-4f2f-8f42-593aa8871129","doc_no":"A.6.1.1.4.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7951,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"42f47668-ba50-430e-ac11-245eef79e712":{"id":"42f47668-ba50-430e-ac11-245eef79e712","doc_no":"A.6.1.1.4.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7952,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"4e2edd9e-61c2-4be1-8cb3-f2be5e1587f3":{"id":"4e2edd9e-61c2-4be1-8cb3-f2be5e1587f3","doc_no":"A.6.1.1.4.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7953,"content":"The documents herein contain all data and specifications for Skybase's instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"bb2ffc1fca4886489e90a01fa25eee011d3935689260c9a0313ed1de031b28cb","addressRefs":[]},"f60f5f5f-3aa8-49de-85fb-95841bb73bdb":{"id":"f60f5f5f-3aa8-49de-85fb-95841bb73bdb","doc_no":"A.6.1.1.4.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7954,"content":"The documents herein organize all base information relevant to Skybase's usage of the Executor Transformation Primitive.","contentHash":"85e285a6927b743ac3644364f4e452ff3a10498199199abbac652ff53456a33a","addressRefs":[]},"b1246162-614d-42b8-b648-474ba79b22aa":{"id":"b1246162-614d-42b8-b648-474ba79b22aa","doc_no":"A.6.1.1.4.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7955,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"33335844-6cd7-4135-9134-bc1ebbd06690":{"id":"33335844-6cd7-4135-9134-bc1ebbd06690","doc_no":"A.6.1.1.4.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7956,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"dddd885e-2600-4947-8c0a-8082e4121753":{"id":"dddd885e-2600-4947-8c0a-8082e4121753","doc_no":"A.6.1.1.4.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7957,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"09e544ef-8565-49d2-8dd6-e1b0aa53cb21":{"id":"09e544ef-8565-49d2-8dd6-e1b0aa53cb21","doc_no":"A.6.1.1.4.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7958,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"fecb494b-fbc2-467d-88df-df2a8a0e0786":{"id":"fecb494b-fbc2-467d-88df-df2a8a0e0786","doc_no":"A.6.1.1.4.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7959,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"838893af-76a9-4d49-94d4-51f7e82fa537":{"id":"838893af-76a9-4d49-94d4-51f7e82fa537","doc_no":"A.6.1.1.4.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7960,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"4f338613-eee5-40c7-bcb4-7dd32e81008d":{"id":"4f338613-eee5-40c7-bcb4-7dd32e81008d","doc_no":"A.6.1.1.4.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7961,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"e526b717-2105-41c5-9686-4387d7ef3b24":{"id":"e526b717-2105-41c5-9686-4387d7ef3b24","doc_no":"A.6.1.1.4.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7962,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"661072a0-b9cd-4ac9-b1d0-cc0f5626dd6d":{"id":"661072a0-b9cd-4ac9-b1d0-cc0f5626dd6d","doc_no":"A.6.1.1.4.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7963,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"08f562a1-4694-45a4-91b8-008876a413ff":{"id":"08f562a1-4694-45a4-91b8-008876a413ff","doc_no":"A.6.1.1.4.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7964,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"3218078d-249f-4d41-ae72-c53ac02ab033":{"id":"3218078d-249f-4d41-ae72-c53ac02ab033","doc_no":"A.6.1.1.4.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7965,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"a4708a14-1030-4935-a4a5-103826d9d4a5":{"id":"a4708a14-1030-4935-a4a5-103826d9d4a5","doc_no":"A.6.1.1.4.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7966,"content":"The documents herein contain all data and specifications for Skybase's Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"d78acf5ed95fc7289151196653ed2cdca03b8fb944fc31889563c0b32c8773e6","addressRefs":[]},"ffa68419-fc61-4b60-a4d5-7c1ca4aace6d":{"id":"ffa68419-fc61-4b60-a4d5-7c1ca4aace6d","doc_no":"A.6.1.1.4.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7967,"content":"The documents herein organize all base information relevant to Skybase's usage of the Agent Token Primitive.","contentHash":"9f2897056f1d6fd681893f5cebf452505d06c97571f2511547d8d315ca8602e3","addressRefs":[]},"3ac79f75-348c-4329-ba78-53b4882662cc":{"id":"3ac79f75-348c-4329-ba78-53b4882662cc","doc_no":"A.6.1.1.4.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7968,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"e1785e8c-71e2-4646-867d-bcca3e4704a7":{"id":"e1785e8c-71e2-4646-867d-bcca3e4704a7","doc_no":"A.6.1.1.4.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7969,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"5402a5c2-0b48-4ebd-9689-ab990578a72c":{"id":"5402a5c2-0b48-4ebd-9689-ab990578a72c","doc_no":"A.6.1.1.4.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7970,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.1.4.2.1 - Single Instance Configuration Document](6e4d6787-4bd7-485f-b378-6dc83dc860cc).","contentHash":"3b206413bfd4936cc49d44676fbf3a4240c2fe94141121b3aa76b79fe974cf8d","addressRefs":[]},"42ff09a3-7286-419f-a64c-fd69e480300b":{"id":"42ff09a3-7286-419f-a64c-fd69e480300b","doc_no":"A.6.1.1.4.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7971,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"f6b2bff2-c924-45f9-ae70-32e25fd621fc":{"id":"f6b2bff2-c924-45f9-ae70-32e25fd621fc","doc_no":"A.6.1.1.4.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7972,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"4e57c90f-df6f-41e6-ba60-129e515967b5":{"id":"4e57c90f-df6f-41e6-ba60-129e515967b5","doc_no":"A.6.1.1.4.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7973,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"feb8e6d3-298d-4f4f-ba31-1113cc2a9e24":{"id":"feb8e6d3-298d-4f4f-ba31-1113cc2a9e24","doc_no":"A.6.1.1.4.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7974,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"fa96fe93-4825-4d52-9050-05e922e44682":{"id":"fa96fe93-4825-4d52-9050-05e922e44682","doc_no":"A.6.1.1.4.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7975,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"4fa6c164-ab33-49c3-9a94-d044d6a9e551":{"id":"4fa6c164-ab33-49c3-9a94-d044d6a9e551","doc_no":"A.6.1.1.4.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7976,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"67fce1f3-961f-479c-b0f9-ccb03a260b83":{"id":"67fce1f3-961f-479c-b0f9-ccb03a260b83","doc_no":"A.6.1.1.4.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7977,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"6e4d6787-4bd7-485f-b378-6dc83dc860cc":{"id":"6e4d6787-4bd7-485f-b378-6dc83dc860cc","doc_no":"A.6.1.1.4.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7978,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"50b46486-6b4c-494a-90dc-e077e77564eb":{"id":"50b46486-6b4c-494a-90dc-e077e77564eb","doc_no":"A.6.1.1.4.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7979,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"1b5f18b6-ca5f-4c2a-be90-a8e270643e9b":{"id":"1b5f18b6-ca5f-4c2a-be90-a8e270643e9b","doc_no":"A.6.1.1.4.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7980,"content":"The name of Skybase's token is Skybase.","contentHash":"f176d5709026f435c152d53c5a924b8a7cafabdd6c636c440ebc4a448da3106d","addressRefs":[]},"8eb04812-6fe7-43dc-a461-afa09b992cc8":{"id":"8eb04812-6fe7-43dc-a461-afa09b992cc8","doc_no":"A.6.1.1.4.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7981,"content":"The symbol of Skybase's token is SKYBASE.","contentHash":"e0d4befa9a1822f2e6395b2f0079c721073f0e3ae8d1eb7e00f5c06ca3d2aa90","addressRefs":[]},"bc80a5e5-4ef7-4255-9e97-848c9cbbeb36":{"id":"bc80a5e5-4ef7-4255-9e97-848c9cbbeb36","doc_no":"A.6.1.1.4.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7982,"content":"The Genesis Supply of SKYBASE will be specified in a future iteration of the Skybase Artifact.","contentHash":"f996e424ce82ee7407d20f0283b1325aad5a233ad6b91bea75e7c547fedb8386","addressRefs":[]},"b2270863-75e9-42f6-8c25-749a0f83dcb5":{"id":"b2270863-75e9-42f6-8c25-749a0f83dcb5","doc_no":"A.6.1.1.4.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7983,"content":"The address of SKYBASE will be specified in a future iteration of the Skybase Artifact.","contentHash":"7a06c771f1cc92969e513309026557bd0fd188913cd86338d11802616dc13806","addressRefs":[]},"1f692794-fc64-4cf8-86a7-fabc865eb428":{"id":"1f692794-fc64-4cf8-86a7-fabc865eb428","doc_no":"A.6.1.1.4.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7984,"content":"The token Admin will be specified in a future iteration of the Skybase Artifact.","contentHash":"7010394e70635cf315a832ac47641e31eaee369e64e588650f702b5f09388c15","addressRefs":[]},"f56670f9-5a43-4b47-b94a-99026f8d87c0":{"id":"f56670f9-5a43-4b47-b94a-99026f8d87c0","doc_no":"A.6.1.1.4.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7985,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Skybase Governance. Sky Governance retains the ability to revert where Skybase is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"88795b25582d27967a862e35d52c123d87b4ff2e598e4923a463daf21f47d6ee","addressRefs":[]},"65437b13-60b3-4e22-ab0c-c6e5b29756a0":{"id":"65437b13-60b3-4e22-ab0c-c6e5b29756a0","doc_no":"A.6.1.1.4.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7986,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"652b94ef-66e3-40fe-ba80-4ce5c3d27f03":{"id":"652b94ef-66e3-40fe-ba80-4ce5c3d27f03","doc_no":"A.6.1.1.4.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7987,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.\n\n- These processes will be defined in a future iteration of the Skybase Artifact.","contentHash":"05624cbf7cdac736943f41da9e055802c166f6bef02f786a8e05a788784296cd","addressRefs":[]},"5f286327-f846-432a-98d5-31b8ecff7a8c":{"id":"5f286327-f846-432a-98d5-31b8ecff7a8c","doc_no":"A.6.1.1.4.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7988,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"05259bea-0f5e-4afc-8279-fbd98516d7ac":{"id":"05259bea-0f5e-4afc-8279-fbd98516d7ac","doc_no":"A.6.1.1.4.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7989,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"b146e772-2d00-456b-8ba7-536ea733c34a":{"id":"b146e772-2d00-456b-8ba7-536ea733c34a","doc_no":"A.6.1.1.4.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7990,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"a66316d6-e4be-4ff5-b894-4c8fa3d1285c":{"id":"a66316d6-e4be-4ff5-b894-4c8fa3d1285c","doc_no":"A.6.1.1.4.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7991,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"ba6be9cd-0812-4098-89f3-2e813948a3f8":{"id":"ba6be9cd-0812-4098-89f3-2e813948a3f8","doc_no":"A.6.1.1.4.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7992,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"24237950-dcfc-4ca7-932f-c808bc521a10":{"id":"24237950-dcfc-4ca7-932f-c808bc521a10","doc_no":"A.6.1.1.4.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7993,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"b0336f9e-09fd-415f-a86d-57220811dc80":{"id":"b0336f9e-09fd-415f-a86d-57220811dc80","doc_no":"A.6.1.1.4.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7994,"content":"The documents herein implement the Operational Primitives for Skybase. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"31cd28aa56bf80fe4089b635e56724c5ad628e8311e6f5e29634cad7c9b6a1e2","addressRefs":[]},"bb6c188b-ae69-4573-8104-44f9577427a1":{"id":"bb6c188b-ae69-4573-8104-44f9577427a1","doc_no":"A.6.1.1.4.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7995,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"73f8a6c0254f09bd50dae5435bf627e0b9ec26b46e44279de9da9a8dc0a51394","addressRefs":[]},"8f799c9e-618c-407f-a4a1-899f32d13d52":{"id":"8f799c9e-618c-407f-a4a1-899f32d13d52","doc_no":"A.6.1.1.4.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7996,"content":"The documents herein organize all base information relevant to Skybase's usage of the Executor Accord Primitive.","contentHash":"b6ea1b741f88b46354e62c84a82e11e7192f25a2eb5603ee9bf06bf4beb347b1","addressRefs":[]},"3018b2d6-65e3-41af-90ae-f4275e862e13":{"id":"3018b2d6-65e3-41af-90ae-f4275e862e13","doc_no":"A.6.1.1.4.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7997,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"d9493bdc-074e-4a87-af74-5e7826b541be":{"id":"d9493bdc-074e-4a87-af74-5e7826b541be","doc_no":"A.6.1.1.4.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7998,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"e396aca8-3823-452e-8bdd-21b0e0e54083":{"id":"e396aca8-3823-452e-8bdd-21b0e0e54083","doc_no":"A.6.1.1.4.2.2.1.1.2.1","title":"Ozone Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":7999,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.2.1.2.1 - Ozone Instance Configuration Document](ff142a80-adb5-49da-87d8-62aabdb36b10).","contentHash":"1129b8738c8bfa99fd7ca01987523d8bbebd204bf8afd39f4cb640cc79786804","addressRefs":[]},"f1f78b17-7c65-4d8c-9066-315c25ed8f2d":{"id":"f1f78b17-7c65-4d8c-9066-315c25ed8f2d","doc_no":"A.6.1.1.4.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8000,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"9b42623e-e6fb-4c18-a291-d5ed18634e39":{"id":"9b42623e-e6fb-4c18-a291-d5ed18634e39","doc_no":"A.6.1.1.4.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8001,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.2.1.1.2 - Active Instances Directory](d9493bdc-074e-4a87-af74-5e7826b541be), whereas failed Invocations are Archived in [A.6.1.1.4.2.2.1.1.5 - Hub Data Repository](c2daebbe-e96d-4201-a5df-725b9ef64780).","contentHash":"a4b7ac05f1506c09dd489b270ca3617063b0ed8f284ddb5165d159c5c1514267","addressRefs":[]},"c2daebbe-e96d-4201-a5df-725b9ef64780":{"id":"c2daebbe-e96d-4201-a5df-725b9ef64780","doc_no":"A.6.1.1.4.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8002,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"3d2a4d73-e717-4276-a608-13a92cd5b33c":{"id":"3d2a4d73-e717-4276-a608-13a92cd5b33c","doc_no":"A.6.1.1.4.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8003,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"85735314-b04b-48f5-b5cd-f1c9f8ff3614":{"id":"85735314-b04b-48f5-b5cd-f1c9f8ff3614","doc_no":"A.6.1.1.4.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8004,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"2250b3d8-6d7f-4454-80a7-3a2beba3cb37":{"id":"2250b3d8-6d7f-4454-80a7-3a2beba3cb37","doc_no":"A.6.1.1.4.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8005,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"830ba0df-d50e-4d8f-bef4-a8febf06d276":{"id":"830ba0df-d50e-4d8f-bef4-a8febf06d276","doc_no":"A.6.1.1.4.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8006,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"ff142a80-adb5-49da-87d8-62aabdb36b10":{"id":"ff142a80-adb5-49da-87d8-62aabdb36b10","doc_no":"A.6.1.1.4.2.2.1.2.1","title":"Ozone Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8007,"content":"The documents herein contain the Instance Configuration Document for the Ozone Executor Accord Primitive Instance.","contentHash":"ca0caee12f20439eb72be855f0a3c3853fe737be1313cfe253dad38c7f8d0623","addressRefs":[]},"cdcae493-a9b6-4b08-8b03-6f4c7c76eb25":{"id":"cdcae493-a9b6-4b08-8b03-6f4c7c76eb25","doc_no":"A.6.1.1.4.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8008,"content":"The documents herein define the parameters of the Ozone Instance of the Executor Accord Primitive.","contentHash":"638cf31df48e28f4a38e5155a81f9cd4b27bb221ff40cc010386b96be05691e5","addressRefs":[]},"82200234-6b7c-4299-a552-66ceac3be5e6":{"id":"82200234-6b7c-4299-a552-66ceac3be5e6","doc_no":"A.6.1.1.4.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8009,"content":"The Operational Facilitator and Operational GovOps for Ozone are specified in [A.6.1.2.2 - Operational Executor Agent Ozone](565660dd-7850-4c3a-8dba-554542bf103a).","contentHash":"8ed0f1fb66d463549e15caa041123f9031ac10ad2f25d039e4bc6b7777f702a7","addressRefs":[]},"822596a6-882f-416f-bc13-4986b1bf4052":{"id":"822596a6-882f-416f-bc13-4986b1bf4052","doc_no":"A.6.1.1.4.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8010,"content":"The documents herein define the custom parameters of the Ozone Instance of the Executor Accord Primitive, if any.","contentHash":"be003f7a447f9026ea8e107c73c8b00f811e9d616575d90ced4c5ffb41a29c34","addressRefs":[]},"27e3f4f9-6433-4cd5-b4db-7f67b3fb6cdf":{"id":"27e3f4f9-6433-4cd5-b4db-7f67b3fb6cdf","doc_no":"A.6.1.1.4.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8011,"content":"The documents herein define the process for the ongoing management of the Ozone Instance of the Executor Accord Primitive.","contentHash":"03daa9d3ebfb53ae8a57e22ffb990501ed356259a7b153b51d2b35cb6013c74b","addressRefs":[]},"5120e81d-c44f-47ec-a19a-dff5d4abf152":{"id":"5120e81d-c44f-47ec-a19a-dff5d4abf152","doc_no":"A.6.1.1.4.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8012,"content":"The documents herein contain data relevant to the Ozone Instance of the Executor Accord Primitive.","contentHash":"edd3e28207fedf752584ef2eb5e88f52b3ff82d2d0a5d7cfed80703bd5ad5d72","addressRefs":[]},"0f2d0ae7-1aa7-4692-9f36-dd00b119885e":{"id":"0f2d0ae7-1aa7-4692-9f36-dd00b119885e","doc_no":"A.6.1.1.4.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8013,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0bb80f80-c2c0-43f1-8783-b2a2bdbcc09b":{"id":"0bb80f80-c2c0-43f1-8783-b2a2bdbcc09b","doc_no":"A.6.1.1.4.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8014,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"659ad2e7-f1af-4bd4-b5c1-8624ba7f169e":{"id":"659ad2e7-f1af-4bd4-b5c1-8624ba7f169e","doc_no":"A.6.1.1.4.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8015,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"03bf33b4-f74d-4b40-a1a0-e34e19b30318":{"id":"03bf33b4-f74d-4b40-a1a0-e34e19b30318","doc_no":"A.6.1.1.4.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8016,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"a25a57e2-64b9-4e78-89d6-c2d68b388348":{"id":"a25a57e2-64b9-4e78-89d6-c2d68b388348","doc_no":"A.6.1.1.4.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8017,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.2.1.2 - Active Instances](830ba0df-d50e-4d8f-bef4-a8febf06d276).","contentHash":"fedfadd86f0bf636ee5304db1a235613ba7de987cda4537290a4083fb29ccd97","addressRefs":[]},"24517c43-dec9-44ec-bc03-e76671dc2e74":{"id":"24517c43-dec9-44ec-bc03-e76671dc2e74","doc_no":"A.6.1.1.4.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8018,"content":"The documents herein contain all data and specifications for Skybase's Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"abb56ca746437915b776e53d6b8c608a7130e429dd1f3b3658a079781b2ce2e9","addressRefs":[]},"787f01b6-0503-49aa-8dd1-f08ad222a5c9":{"id":"787f01b6-0503-49aa-8dd1-f08ad222a5c9","doc_no":"A.6.1.1.4.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8019,"content":"The documents herein organize all base information relevant to Skybase's usage of the Root Edit Primitive.","contentHash":"78dc4f268a085ac374ba8d404716138ab7b6557decc51cda8a8409e56edd620e","addressRefs":[]},"a70572a2-e643-49a1-afa2-3b25c5118c92":{"id":"a70572a2-e643-49a1-afa2-3b25c5118c92","doc_no":"A.6.1.1.4.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8020,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"0a03859b-466d-43bf-905d-fd6410fecc19":{"id":"0a03859b-466d-43bf-905d-fd6410fecc19","doc_no":"A.6.1.1.4.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8021,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"318fedce-fb39-450e-986a-4e0886b33dc5":{"id":"318fedce-fb39-450e-986a-4e0886b33dc5","doc_no":"A.6.1.1.4.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8022,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.2.2.2.1 - Single Instance Configuration Document](5c13949f-831a-4574-8942-ceaa4da11b9d).","contentHash":"0f200f92cd8cb7ec0d6c3bd45d1ad4909519a61bcf5376c63f8de9f76b64e643","addressRefs":[]},"e5d7b405-1839-472b-8b3d-fd30818e17fb":{"id":"e5d7b405-1839-472b-8b3d-fd30818e17fb","doc_no":"A.6.1.1.4.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8023,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"b754f376-5aef-4631-bf68-fb34dc02ac62":{"id":"b754f376-5aef-4631-bf68-fb34dc02ac62","doc_no":"A.6.1.1.4.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8024,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"e2d6993d-f8e2-4e39-9e30-6693eddb5643":{"id":"e2d6993d-f8e2-4e39-9e30-6693eddb5643","doc_no":"A.6.1.1.4.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8025,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"7af6212a-d0e0-4148-8d06-f825a97289ec":{"id":"7af6212a-d0e0-4148-8d06-f825a97289ec","doc_no":"A.6.1.1.4.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8026,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"9ac66a16-2aa3-4909-bf50-168e118bb5ba":{"id":"9ac66a16-2aa3-4909-bf50-168e118bb5ba","doc_no":"A.6.1.1.4.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8027,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"19493456-a088-49db-b65a-34ce5928b750":{"id":"19493456-a088-49db-b65a-34ce5928b750","doc_no":"A.6.1.1.4.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8028,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"ab9a8ca8-5bcf-4846-8740-12ea03ee8158":{"id":"ab9a8ca8-5bcf-4846-8740-12ea03ee8158","doc_no":"A.6.1.1.4.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8029,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"5c13949f-831a-4574-8942-ceaa4da11b9d":{"id":"5c13949f-831a-4574-8942-ceaa4da11b9d","doc_no":"A.6.1.1.4.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8030,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"9d5d586e-1840-49f3-9716-20d661f023ce":{"id":"9d5d586e-1840-49f3-9716-20d661f023ce","doc_no":"A.6.1.1.4.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8031,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.4.2.2.2.2.1.2 - Operational Process Definition](010ed495-c693-4d27-8c18-aa24b64e2715).","contentHash":"fab02b48955c011ab36469027f4d578bac3dad3b04890030268c7e44693dbb1c","addressRefs":[]},"010ed495-c693-4d27-8c18-aa24b64e2715":{"id":"010ed495-c693-4d27-8c18-aa24b64e2715","doc_no":"A.6.1.1.4.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8032,"content":"The documents herein define the process for using the Root Edit Primitive to update the Skybase Agent Artifact. Information on Skybase governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.4.3.1 - Governance Information Unrelated To Root Edit Primitive](70804058-8a1b-45ee-bf21-b09a5daefdb9).","contentHash":"129cc93483b2b2013a1ccffcb2ee897d7336bdb4ffd437fb08f82ea39e961b63","addressRefs":[]},"759db362-3e1b-4ee8-b07e-9c61f7818154":{"id":"759db362-3e1b-4ee8-b07e-9c61f7818154","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8033,"content":"The documents herein define the process for using the Root Edit Primitive to update the Skybase Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"da9a448ff23e5858b5e8f004351230084a6032784df48600d87d4f51bb06c5ef","addressRefs":[]},"f57f157c-c260-4671-8150-01acabcd286d":{"id":"f57f157c-c260-4671-8150-01acabcd286d","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8034,"content":"The Root Edit process begins with a SKYBASE token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. A SKYBASE token holder must hold at least 1% of the circulating token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Skybase Prime\" category.","contentHash":"757aad3b9a0f74ed5542be74bf3c4edbdce8f76d46d897b9264379371e935c19","addressRefs":[]},"502d08e5-d705-4443-bb71-f29580847d74":{"id":"502d08e5-d705-4443-bb71-f29580847d74","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.1.1","title":"Root Edit Proposal Submission Requirements Exception","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8035,"content":"For proposals that solely entail a buyback or a grant of SKYBASE tokens, the requirement that SKYBASE token holders must hold at least 1% of the circulating token supply to submit a proposal is waived. However, all other procedural requirements within the Root Edit process continue to apply.","contentHash":"016b34cf57e7881bb5bc309d2d3db00c360e503dd15267fdc4e2ff14a873b4f3","addressRefs":[]},"f88fc097-7e41-41d7-aac9-992a9a11919f":{"id":"f88fc097-7e41-41d7-aac9-992a9a11919f","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.1.2","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8036,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, SKYBASE token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Skybase Prime\" category. The title of the post must include the text \"Skybase Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total SKYBASE token supply specified in [A.6.1.1.4.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](f57f157c-c260-4671-8150-01acabcd286d).","contentHash":"18040067ab9fb3d88277b5a4d6e4630a5fe807e6b6c5b0c199911d1d1b777883","addressRefs":[]},"451079fe-fd11-4fef-ae51-6cb533a644c5":{"id":"451079fe-fd11-4fef-ae51-6cb533a644c5","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8037,"content":"A future iteration of the Skybase Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis.","contentHash":"5e37f6049e8eee94cb487e2df80848ab9bef59f3de44a07bb751baa88694e32a","addressRefs":[]},"76b51e97-ff82-4f52-8c24-7b75d629bb4a":{"id":"76b51e97-ff82-4f52-8c24-7b75d629bb4a","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8038,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment.\n\nIf the proposal is aligned, the Operational Facilitator must respond to the Forum post to announce their finding. In this Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"3d695884c752507d7f445ad3a572c67b44863196d11108fb8a300dc2e71ce3e7","addressRefs":[]},"836b9942-8fdf-46df-bf38-f5adf87eb390":{"id":"836b9942-8fdf-46df-bf38-f5adf87eb390","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8039,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Skybase Artifact, the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. The poll is open for three (3) days. A poll must have at least 10% of the circulating token supply participating and must have more than 50% of votes cast, excluding abstentions, in favor to be approved.","contentHash":"f145fd230f1bc1a2b5045896eceada5e39eafbd87bef383e8da16da990585945","addressRefs":[]},"b91f0f85-680d-4eeb-9a2e-7e0e245e4c6d":{"id":"b91f0f85-680d-4eeb-9a2e-7e0e245e4c6d","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8040,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"1adf5e90-53a8-4036-9964-11430891137e":{"id":"1adf5e90-53a8-4036-9964-11430891137e","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.5.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8041,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"f3e8ecec-cb08-4682-9218-d13f567fc00e":{"id":"f3e8ecec-cb08-4682-9218-d13f567fc00e","doc_no":"A.6.1.1.4.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8042,"content":"The Skybase Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"4c5b09668d63c471fa2f3c1006aad716fbde09cda5d864d631a36d51adbbfb09","addressRefs":[]},"e5477d87-ecc4-4eab-9e11-fe8d76791048":{"id":"e5477d87-ecc4-4eab-9e11-fe8d76791048","doc_no":"A.6.1.1.4.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8043,"content":"The documents herein define the process for using the Root Edit Primitive to update the Skybase Agent Artifact in non-routine conditions.","contentHash":"46dfb09b00f6c6e4bfd048b31f865c38656e979d6985fe0342b09937b4c57985","addressRefs":[]},"368ff139-9c2c-4b41-955e-e374996ad274":{"id":"368ff139-9c2c-4b41-955e-e374996ad274","doc_no":"A.6.1.1.4.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8044,"content":"The documents herein define the process for using the Root Edit Primitive to update the Skybase Agent Artifact in urgent or emergency situations.","contentHash":"a55eeccf925d127037246603fa3597236cc63d32f7ed555dcee932960d1da03f","addressRefs":[]},"5edc65d7-8023-4c03-b399-958c5f8869ff":{"id":"5edc65d7-8023-4c03-b399-958c5f8869ff","doc_no":"A.6.1.1.4.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process in Urgent and Emergency Situations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8045,"content":"In an Urgent or Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Skybase Prime\" category), unless doing so would endanger Skybase or its users.","contentHash":"448988e3ef4f8035afc855483aca56a383cc019b86775349f10399595878fe52","addressRefs":[]},"6f533a79-4263-4b1b-9d47-9ab9e670f0f0":{"id":"6f533a79-4263-4b1b-9d47-9ab9e670f0f0","doc_no":"A.6.1.1.4.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8046,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"112386b9-0c60-4224-8d39-a43b2805f351":{"id":"112386b9-0c60-4224-8d39-a43b2805f351","doc_no":"A.6.1.1.4.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8047,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"d9ebdf09-8d8e-4b14-a3f3-08a0d7579e92":{"id":"d9ebdf09-8d8e-4b14-a3f3-08a0d7579e92","doc_no":"A.6.1.1.4.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8048,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"91159367-dcf2-4c55-ae77-0ca91da4fb91":{"id":"91159367-dcf2-4c55-ae77-0ca91da4fb91","doc_no":"A.6.1.1.4.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8049,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"6840069f-a930-42ad-8fad-8224876da285":{"id":"6840069f-a930-42ad-8fad-8224876da285","doc_no":"A.6.1.1.4.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8050,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"492351ef-6e00-450c-8689-e7dd0c171a55":{"id":"492351ef-6e00-450c-8689-e7dd0c171a55","doc_no":"A.6.1.1.4.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8051,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"ceb79469-e43e-4640-9507-5d1d4eaea3cb":{"id":"ceb79469-e43e-4640-9507-5d1d4eaea3cb","doc_no":"A.6.1.1.4.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8052,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"17f5f5fe128d8b2db3152e692d7390eb595ec10b2443c851b561109b2a10a2f4","addressRefs":[]},"04e7dd63-49ab-42dd-b195-1e309d7295c9":{"id":"04e7dd63-49ab-42dd-b195-1e309d7295c9","doc_no":"A.6.1.1.4.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8053,"content":"The documents herein organize all base information relevant to Skybase's usage of the Light Agent Primitive.","contentHash":"5bf9fa50b73c66124529e377e6fc1102922d5f014d0a663a51fecb867f91bb67","addressRefs":[]},"1db03594-b529-4330-a4d9-536178be4303":{"id":"1db03594-b529-4330-a4d9-536178be4303","doc_no":"A.6.1.1.4.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8054,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"66f80060-6404-4cde-8059-ee8f220f952b":{"id":"66f80060-6404-4cde-8059-ee8f220f952b","doc_no":"A.6.1.1.4.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8055,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"7802509b-d232-4e04-b658-1f34621112a0":{"id":"7802509b-d232-4e04-b658-1f34621112a0","doc_no":"A.6.1.1.4.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8056,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"8f764154-a5d2-4cd6-ba54-537dbe785f6c":{"id":"8f764154-a5d2-4cd6-ba54-537dbe785f6c","doc_no":"A.6.1.1.4.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8057,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.2.3.1.2 - Active Instances Directory](66f80060-6404-4cde-8059-ee8f220f952b), whereas failed Invocations are Archived in [A.6.1.1.4.2.2.3.1.5 - Hub Data Repository](7561a59b-425a-405d-ba35-1892a282dd2b).","contentHash":"21997f05be9ef2d160dcb020eba68756eea81f3b48a0441686fba15cb4a5e133","addressRefs":[]},"7561a59b-425a-405d-ba35-1892a282dd2b":{"id":"7561a59b-425a-405d-ba35-1892a282dd2b","doc_no":"A.6.1.1.4.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8058,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"52ce096b-fba4-40ef-9164-a5ec944c59ad":{"id":"52ce096b-fba4-40ef-9164-a5ec944c59ad","doc_no":"A.6.1.1.4.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8059,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"4bfb3a1c-ac80-4a42-8760-0e83dd562fed":{"id":"4bfb3a1c-ac80-4a42-8760-0e83dd562fed","doc_no":"A.6.1.1.4.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8060,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"5c197fb1-5da3-414e-aa18-17eaf2f1701f":{"id":"5c197fb1-5da3-414e-aa18-17eaf2f1701f","doc_no":"A.6.1.1.4.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8061,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"1a09ba55-2b66-40e7-83d0-7ff144d2575b":{"id":"1a09ba55-2b66-40e7-83d0-7ff144d2575b","doc_no":"A.6.1.1.4.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8062,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"2546a8ae-ca91-4190-96e3-b06f160d073c":{"id":"2546a8ae-ca91-4190-96e3-b06f160d073c","doc_no":"A.6.1.1.4.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8063,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"fe73fbe5-570b-4388-8934-ab6605d89dd5":{"id":"fe73fbe5-570b-4388-8934-ab6605d89dd5","doc_no":"A.6.1.1.4.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8064,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.2.3.2 - Active Instances](1a09ba55-2b66-40e7-83d0-7ff144d2575b).","contentHash":"b9221c319a7d29a6f30e0aea35198408d28dd7beab1343ee4a4ec140ff33c389","addressRefs":[]},"833c1933-d81e-4653-af2c-aa03aac70883":{"id":"833c1933-d81e-4653-af2c-aa03aac70883","doc_no":"A.6.1.1.4.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8065,"content":"The documents herein implement the Ecosystem Upkeep Primitives for Skybase. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"ebda1bf6e586d0e59f93c0d8ed752351f11207dbf1c7792e436bdba20eba99c6","addressRefs":[]},"c6ef4a5c-d6f4-42d6-8800-6b7a40e64f50":{"id":"c6ef4a5c-d6f4-42d6-8800-6b7a40e64f50","doc_no":"A.6.1.1.4.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8066,"content":"The documents herein contain all data and specifications for Skybase's Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"38e5b6835f781db986a73830b856e60bb824ca3c8264235e6810a16692e7c6ee","addressRefs":[]},"9beebf8b-dfd4-40b4-8de1-f5a3f4a60824":{"id":"9beebf8b-dfd4-40b4-8de1-f5a3f4a60824","doc_no":"A.6.1.1.4.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8067,"content":"The documents herein organize all base information relevant to Skybase's usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"d19784ec128ceb70fc50aa3d80304189bae1a98037ae098f5d5d0ae7b4302d9e","addressRefs":[]},"dbb03eb2-d193-4193-93c7-1d874b9995f3":{"id":"dbb03eb2-d193-4193-93c7-1d874b9995f3","doc_no":"A.6.1.1.4.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8068,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"a5e68fe6-a420-4960-ac74-b02c01366315":{"id":"a5e68fe6-a420-4960-ac74-b02c01366315","doc_no":"A.6.1.1.4.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8069,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"c0ea44a4-98d9-427c-a570-6f94574bbf94":{"id":"c0ea44a4-98d9-427c-a570-6f94574bbf94","doc_no":"A.6.1.1.4.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8070,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.3.1.2.1 - Single Instance Configuration Document](2426a22f-8760-412f-bf21-e69c72787a9b).","contentHash":"0e3c1976817e8dd0965a4b101896a70628ef29b4e3780b9a005444f61f0c9172","addressRefs":[]},"f2c07b3e-d18d-4443-8b73-386a2d5c370b":{"id":"f2c07b3e-d18d-4443-8b73-386a2d5c370b","doc_no":"A.6.1.1.4.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8071,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"cf55b39f-204e-49b0-82fd-df87a22fd23f":{"id":"cf55b39f-204e-49b0-82fd-df87a22fd23f","doc_no":"A.6.1.1.4.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8072,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"cc9f3e40-bcec-49c9-a0ff-5d204c40b890":{"id":"cc9f3e40-bcec-49c9-a0ff-5d204c40b890","doc_no":"A.6.1.1.4.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8073,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"9bd4f238-f94c-4532-8001-c80d3f74febf":{"id":"9bd4f238-f94c-4532-8001-c80d3f74febf","doc_no":"A.6.1.1.4.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8074,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"250cba14-19c6-4211-af5b-33f0b78cc3f8":{"id":"250cba14-19c6-4211-af5b-33f0b78cc3f8","doc_no":"A.6.1.1.4.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8075,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"2118c398-b73f-401a-b71f-55d1fca06b29":{"id":"2118c398-b73f-401a-b71f-55d1fca06b29","doc_no":"A.6.1.1.4.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8076,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"4359d5d0-a404-4004-8cff-d552338df2f0":{"id":"4359d5d0-a404-4004-8cff-d552338df2f0","doc_no":"A.6.1.1.4.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8077,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"2426a22f-8760-412f-bf21-e69c72787a9b":{"id":"2426a22f-8760-412f-bf21-e69c72787a9b","doc_no":"A.6.1.1.4.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8078,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"734f47d3-adf3-46a0-972c-f8d37a8d009e":{"id":"734f47d3-adf3-46a0-972c-f8d37a8d009e","doc_no":"A.6.1.1.4.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8079,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"69b65ee6-746a-4d78-8d60-ec40ca2bb6b4":{"id":"69b65ee6-746a-4d78-8d60-ec40ca2bb6b4","doc_no":"A.6.1.1.4.2.3.1.2.1.1.1","title":"Terms","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8080,"content":"Skybase will pay 0.50% of its market capitalization per year in USDS.","contentHash":"2c50eda7cfba28fadbd9030eef1098ac44dafdb8bd61e3b2e10fdd48ec800564","addressRefs":[]},"61232bcd-4510-4ed1-8ede-14d744329c27":{"id":"61232bcd-4510-4ed1-8ede-14d744329c27","doc_no":"A.6.1.1.4.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8081,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"8c10d49d-6238-4cdb-b62e-32bb080b7b0b":{"id":"8c10d49d-6238-4cdb-b62e-32bb080b7b0b","doc_no":"A.6.1.1.4.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8082,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"6ca26507-85f1-4169-a2a2-156046847257":{"id":"6ca26507-85f1-4169-a2a2-156046847257","doc_no":"A.6.1.1.4.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8083,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"e2db4ada-d8af-4481-963b-8ed8adfbd18d":{"id":"e2db4ada-d8af-4481-963b-8ed8adfbd18d","doc_no":"A.6.1.1.4.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8084,"content":"The process to pay 0.50% of Skybase's market capitalization per year in USDS will be specified in future iterations of the Skybase Artifact.","contentHash":"c8f21954256b1d48aaafcf55740035d6c7e53640f3c5cabd1c870068bd7bcf20","addressRefs":[]},"df35e2e9-116d-4a1c-95d7-1e4b8acdd1c3":{"id":"df35e2e9-116d-4a1c-95d7-1e4b8acdd1c3","doc_no":"A.6.1.1.4.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8085,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"85815a3a-08b9-4917-b8a5-6c87f5dcd391":{"id":"85815a3a-08b9-4917-b8a5-6c87f5dcd391","doc_no":"A.6.1.1.4.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8086,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"26c81439-ed26-4d69-bd32-cc486058fb6f":{"id":"26c81439-ed26-4d69-bd32-cc486058fb6f","doc_no":"A.6.1.1.4.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8087,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"1285deb9-39ff-400c-a82c-2ec2e7b4d216":{"id":"1285deb9-39ff-400c-a82c-2ec2e7b4d216","doc_no":"A.6.1.1.4.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8088,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"db3e6b81-f383-4269-8cab-e94e47abc891":{"id":"db3e6b81-f383-4269-8cab-e94e47abc891","doc_no":"A.6.1.1.4.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8089,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"e877196c-33d9-48dd-b188-fe5c70c68d00":{"id":"e877196c-33d9-48dd-b188-fe5c70c68d00","doc_no":"A.6.1.1.4.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8090,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"ce66e2db-bbb6-4f33-9b3b-cc3b913f6459":{"id":"ce66e2db-bbb6-4f33-9b3b-cc3b913f6459","doc_no":"A.6.1.1.4.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8091,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"c67cbd36-a096-41fb-a210-8547a733a724":{"id":"c67cbd36-a096-41fb-a210-8547a733a724","doc_no":"A.6.1.1.4.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8092,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"dec47cc6-dce7-4256-bd23-6b659ae8bc25":{"id":"dec47cc6-dce7-4256-bd23-6b659ae8bc25","doc_no":"A.6.1.1.4.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8093,"content":"The documents herein contain all data and specifications for Skybase's instance of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"3f953c93dede9780967715a70dc11688da3963a2ba0eacd9050bc061c0569c0a","addressRefs":[]},"6952060d-f1dd-4d86-b2f8-f07090174d1d":{"id":"6952060d-f1dd-4d86-b2f8-f07090174d1d","doc_no":"A.6.1.1.4.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8094,"content":"The documents herein organize all base information relevant to Skybase's usage of the Upkeep Rebate Primitive.","contentHash":"df00922fd0bcc71417f90781d95b5b9cb63bcbc808e65bcd0d43467446cef0fb","addressRefs":[]},"aec5c887-c2d2-43ee-b00e-e77716b7bb30":{"id":"aec5c887-c2d2-43ee-b00e-e77716b7bb30","doc_no":"A.6.1.1.4.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8095,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"89236086-3786-47bb-8b97-6a0ee5013c46":{"id":"89236086-3786-47bb-8b97-6a0ee5013c46","doc_no":"A.6.1.1.4.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8096,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"1fe328fd-2a73-45ea-b80a-f5ce76728ae1":{"id":"1fe328fd-2a73-45ea-b80a-f5ce76728ae1","doc_no":"A.6.1.1.4.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8097,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.3.2.2.1 - Single Instance Configuration Document](f1ecc666-e14f-4828-977b-b24be78b1825).","contentHash":"f5ff75a343ecd3afb62415b7c00c2ac75706d8943aafd33a04501f6e8e15b3aa","addressRefs":[]},"883dcda6-bd15-4c39-9229-b0252e9556f8":{"id":"883dcda6-bd15-4c39-9229-b0252e9556f8","doc_no":"A.6.1.1.4.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8098,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"16c7d73e-df4d-401a-b8c7-aa5fe7df23f2":{"id":"16c7d73e-df4d-401a-b8c7-aa5fe7df23f2","doc_no":"A.6.1.1.4.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8099,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"dd6c0fe7-480e-492c-b24b-287ebde1fdfe":{"id":"dd6c0fe7-480e-492c-b24b-287ebde1fdfe","doc_no":"A.6.1.1.4.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8100,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"d9c92153-6411-4b40-9871-615e408cf738":{"id":"d9c92153-6411-4b40-9871-615e408cf738","doc_no":"A.6.1.1.4.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8101,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"ceb96633-4d3f-4818-bebb-e99243b7b061":{"id":"ceb96633-4d3f-4818-bebb-e99243b7b061","doc_no":"A.6.1.1.4.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8102,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"793bcfab-0f87-4c09-b4f5-0f131075604b":{"id":"793bcfab-0f87-4c09-b4f5-0f131075604b","doc_no":"A.6.1.1.4.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8103,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"6c2bb4eb-e052-4cb8-a249-d65201b4828e":{"id":"6c2bb4eb-e052-4cb8-a249-d65201b4828e","doc_no":"A.6.1.1.4.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8104,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"f1ecc666-e14f-4828-977b-b24be78b1825":{"id":"f1ecc666-e14f-4828-977b-b24be78b1825","doc_no":"A.6.1.1.4.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8105,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"0e8a5c2f-ef1b-4c4f-aa4a-ed1659d80663":{"id":"0e8a5c2f-ef1b-4c4f-aa4a-ed1659d80663","doc_no":"A.6.1.1.4.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8106,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"b7be1c16-a7e1-4d22-a697-d30cd1d2bb86":{"id":"b7be1c16-a7e1-4d22-a697-d30cd1d2bb86","doc_no":"A.6.1.1.4.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8107,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"717bb9de-7df5-4fec-8e59-d5d7fde0ac7d":{"id":"717bb9de-7df5-4fec-8e59-d5d7fde0ac7d","doc_no":"A.6.1.1.4.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8108,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"0d37e672-8a82-433c-a5c7-f88ff248cb6a":{"id":"0d37e672-8a82-433c-a5c7-f88ff248cb6a","doc_no":"A.6.1.1.4.2.3.2.2.1.2.1.1","title":"Skybase Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8109,"content":"Skybase keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"f481a7c973a4f0eb435646855529a98b37ad7594006645ae5b5c178ddef0bca7","addressRefs":[]},"d2a0b2dd-353f-46b1-ae2c-1791ce2a0b77":{"id":"d2a0b2dd-353f-46b1-ae2c-1791ce2a0b77","doc_no":"A.6.1.1.4.2.3.2.2.1.2.1.2","title":"Skybase Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8110,"content":"When paying Ecosystem Upkeep fees, Skybase deducts the rebate from the fees it pays.","contentHash":"cfc62185cc99cae9515f6c8eb70078addae8ebbf2a52a29ddabdd17fa7fbc5ff","addressRefs":[]},"911e4409-146c-49e6-9f5c-5abdc58d97d3":{"id":"911e4409-146c-49e6-9f5c-5abdc58d97d3","doc_no":"A.6.1.1.4.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8111,"content":"Operational GovOps reviews Skybase's calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Skybase Prime\" category and work with Skybase to resolve the disagreement. If Operational GovOps and Skybase cannot resolve the disagreement, it must be escalated to Core GovOps.","contentHash":"7496d591528fbc42e73e8560934ccd0cad073a97ee51e9375af6c25f8901c5cb","addressRefs":[]},"299fa3a2-ce38-4697-b876-faaa5e5ca3a9":{"id":"299fa3a2-ce38-4697-b876-faaa5e5ca3a9","doc_no":"A.6.1.1.4.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8112,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"c9eac99e-4444-478a-a0bf-cc5139413bf0":{"id":"c9eac99e-4444-478a-a0bf-cc5139413bf0","doc_no":"A.6.1.1.4.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8113,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"2bc4f7e9-e9a2-465e-b6da-1032ce4a6f42":{"id":"2bc4f7e9-e9a2-465e-b6da-1032ce4a6f42","doc_no":"A.6.1.1.4.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8114,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"a7718626-05e0-4c62-86ae-62ff9f2fc785":{"id":"a7718626-05e0-4c62-86ae-62ff9f2fc785","doc_no":"A.6.1.1.4.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8115,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0e9c8eb9-ab4e-4240-9ea9-a2c810ea3698":{"id":"0e9c8eb9-ab4e-4240-9ea9-a2c810ea3698","doc_no":"A.6.1.1.4.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8116,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"89f2904b-d250-4643-a84a-083b54a572e0":{"id":"89f2904b-d250-4643-a84a-083b54a572e0","doc_no":"A.6.1.1.4.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8117,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"aff0590c-e76d-4734-a139-ef7a67d9a619":{"id":"aff0590c-e76d-4734-a139-ef7a67d9a619","doc_no":"A.6.1.1.4.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8118,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"986814bc-13cc-4e9d-b1ba-f664863ad05e":{"id":"986814bc-13cc-4e9d-b1ba-f664863ad05e","doc_no":"A.6.1.1.4.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8119,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"23b316a2-8a07-4295-808f-f787fea871de":{"id":"23b316a2-8a07-4295-808f-f787fea871de","doc_no":"A.6.1.1.4.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8120,"content":"The documents herein implement the SkyLink Primitives for Skybase. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"c80ba0104da3d770569a38e78a91d3d11473baaec38852a9a73e3ebaf1ab180c","addressRefs":[]},"ddeb2ecf-ea5c-4087-a44d-0a69de3033f7":{"id":"ddeb2ecf-ea5c-4087-a44d-0a69de3033f7","doc_no":"A.6.1.1.4.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8121,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"d92786760fe1253c97151281110a9ddf9b84447ef59b7a1f78da98d654e0ca15","addressRefs":[]},"052c7deb-75d9-4be2-aa45-cb3a59d14bd5":{"id":"052c7deb-75d9-4be2-aa45-cb3a59d14bd5","doc_no":"A.6.1.1.4.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8122,"content":"The documents herein organize all base information relevant to Skybase's usage of the Token SkyLink Primitive.","contentHash":"e390dfe38908dd30c6d895d1bcf422815dc47425250c98ff0074fac6e91ab152","addressRefs":[]},"e8c65465-9db4-48a7-be8e-5e9616779056":{"id":"e8c65465-9db4-48a7-be8e-5e9616779056","doc_no":"A.6.1.1.4.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8123,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"a5aa1884-66a2-4fd0-b35d-f4291f0726f7":{"id":"a5aa1884-66a2-4fd0-b35d-f4291f0726f7","doc_no":"A.6.1.1.4.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8124,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"7f0e42ad-c54c-4023-9055-57288d0eeb3f":{"id":"7f0e42ad-c54c-4023-9055-57288d0eeb3f","doc_no":"A.6.1.1.4.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8125,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"75c0efb2-0428-4764-9bfd-fdccca850048":{"id":"75c0efb2-0428-4764-9bfd-fdccca850048","doc_no":"A.6.1.1.4.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8126,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.4.1.1.2 - Active Instances Directory](a5aa1884-66a2-4fd0-b35d-f4291f0726f7), whereas failed Invocations are Archived in [A.6.1.1.4.2.4.1.1.5 - Hub Data Repository](1707675b-308e-4ac1-8e29-129b76ed430d).","contentHash":"7a54ad94643a884d0866912118e2b4c32c82e1b26318ea5f6d4bd253a728fbb8","addressRefs":[]},"1707675b-308e-4ac1-8e29-129b76ed430d":{"id":"1707675b-308e-4ac1-8e29-129b76ed430d","doc_no":"A.6.1.1.4.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8127,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"18356d1b-545d-4819-a71e-b6d4e8c1ef81":{"id":"18356d1b-545d-4819-a71e-b6d4e8c1ef81","doc_no":"A.6.1.1.4.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8128,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"a168df08-8c61-4b31-a05b-2a36a3abf2ed":{"id":"a168df08-8c61-4b31-a05b-2a36a3abf2ed","doc_no":"A.6.1.1.4.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8129,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"cd2f777f-1c0b-4d1d-a603-ecc6ae1cd0e8":{"id":"cd2f777f-1c0b-4d1d-a603-ecc6ae1cd0e8","doc_no":"A.6.1.1.4.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8130,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"e9afe0ee-b765-49e0-9268-636b386c8733":{"id":"e9afe0ee-b765-49e0-9268-636b386c8733","doc_no":"A.6.1.1.4.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8131,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"a8e875d3-39f8-4040-a6f3-fe411e6d5d4e":{"id":"a8e875d3-39f8-4040-a6f3-fe411e6d5d4e","doc_no":"A.6.1.1.4.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8132,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"6947125b-804c-45a1-a730-9f1acc9daa13":{"id":"6947125b-804c-45a1-a730-9f1acc9daa13","doc_no":"A.6.1.1.4.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8133,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.4.1.2 - Active Instances](e9afe0ee-b765-49e0-9268-636b386c8733).","contentHash":"f6647c8434eb72e779b15b9379aa327037e8e534d756fa77aa2e4839780a1c79","addressRefs":[]},"6a390014-e5c9-4656-bdf8-587264a141cd":{"id":"6a390014-e5c9-4656-bdf8-587264a141cd","doc_no":"A.6.1.1.4.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8134,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Skybase. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"2c37ec71ca86dac49a81e563a1d45882b26058c1bf6894838275ef9c80accba2","addressRefs":[]},"d8e61fc3-18a2-4952-8e5b-43cfb94b0bab":{"id":"d8e61fc3-18a2-4952-8e5b-43cfb94b0bab","doc_no":"A.6.1.1.4.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8135,"content":"The documents herein contain all data and specifications for Skybase's instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"3458fb3a5994984a9aa998761441549f5a62e2ae226a61f0983693f52b1027a1","addressRefs":[]},"10b6c6e8-edee-4a77-a6c4-bbb05db8b364":{"id":"10b6c6e8-edee-4a77-a6c4-bbb05db8b364","doc_no":"A.6.1.1.4.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8136,"content":"The documents herein organize all base information relevant to Skybase's usage of the Distribution Reward Primitive.","contentHash":"f2b0097ee7c40e2121110074c323a6766ac2f883854267a94ebc51e1d7636e9b","addressRefs":[]},"03230dbb-8896-40b3-b5c3-d3c4ee729606":{"id":"03230dbb-8896-40b3-b5c3-d3c4ee729606","doc_no":"A.6.1.1.4.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8137,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"c6275b51-9ee0-49df-a4ea-33a24cd2c752":{"id":"c6275b51-9ee0-49df-a4ea-33a24cd2c752","doc_no":"A.6.1.1.4.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8138,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"ab7ff4b8-7e62-4a36-8573-581c86293e50":{"id":"ab7ff4b8-7e62-4a36-8573-581c86293e50","doc_no":"A.6.1.1.4.2.5.1.1.2.1","title":"Sky.money App Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8139,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.1 - Sky.money App Instance Configuration Document](b52f88c6-427b-45f6-8e1c-81fa27e522c8).","contentHash":"3d8d497f210b99d3903050ae66496a6f2196eff72e906a25f4046cfa2823e7a2","addressRefs":[]},"43fbf9b3-7cf6-46f3-a900-c3ef9d193d02":{"id":"43fbf9b3-7cf6-46f3-a900-c3ef9d193d02","doc_no":"A.6.1.1.4.2.5.1.1.2.2","title":"Sky.money Open Source Widgets Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8140,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.2 - Sky.money Open Source Widgets Instance Configuration Document](5aada153-29f6-4304-b56e-9d425dc978a4).","contentHash":"4eddad67fac0788c5b2656d57793c9a17af8245ce108973d7bcc50acfccd2027","addressRefs":[]},"a8442e7e-67ee-43a2-b0b6-6e18db4bbb41":{"id":"a8442e7e-67ee-43a2-b0b6-6e18db4bbb41","doc_no":"A.6.1.1.4.2.5.1.1.2.3","title":"DeFi Saver Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8141,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.3 - DeFi Saver Instance Configuration Document](9907bb75-f389-42bb-8fe4-e03ff3039c46).","contentHash":"c47f4034440672f3cb8866ef964b789038870a66d9016a1354fe3bd7df65e9c6","addressRefs":[]},"5341fdbc-78fc-4e15-8b06-d446a3dac8d8":{"id":"5341fdbc-78fc-4e15-8b06-d446a3dac8d8","doc_no":"A.6.1.1.4.2.5.1.1.2.4","title":"CoW Swap Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8142,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.4 - CoW Swap Instance Configuration Document](80f22d64-0ccf-4bb2-8da4-d170a95d2161).","contentHash":"0294f525398316b6903f386aee4f03cb5cbaa7a57c0d9d9e4216370c8751331f","addressRefs":[]},"ecc841f1-0bd8-4453-b97d-33a05fbbafba":{"id":"ecc841f1-0bd8-4453-b97d-33a05fbbafba","doc_no":"A.6.1.1.4.2.5.1.1.2.5","title":"ParaSwap Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8143,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.5 - ParaSwap Instance Configuration Document](d3f7f0e6-b912-4464-be3f-20b0c600bcfa).","contentHash":"b71f35bb8bf9b28768ecc77bd8bf7ea7cb482c37a08bde63c68594c2be9a3463","addressRefs":[]},"a1e42939-5c28-4e1c-8940-150f979b4e47":{"id":"a1e42939-5c28-4e1c-8940-150f979b4e47","doc_no":"A.6.1.1.4.2.5.1.1.2.6","title":"Yearn (Gimme) Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8144,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.6 - Yearn (Gimme) Instance Configuration Document](f36ce752-38d1-4dd4-8a51-dd18f2151756).","contentHash":"02ec70d05e87f8b046c39246e7c05af0edcefa0eb4361d541a16aaca2298c7af","addressRefs":[]},"c2fccf99-2f21-42df-bfea-e857110d386e":{"id":"c2fccf99-2f21-42df-bfea-e857110d386e","doc_no":"A.6.1.1.4.2.5.1.1.2.7","title":"MOM Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8145,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.7 - MOM Instance Configuration Document](ee4f9b64-aeb7-4813-b187-996e8172fea1).","contentHash":"97ca28d076d460a27cdcf0690cb747d31171aa1f09e77a917bb02413427be9c7","addressRefs":[]},"802c6126-3283-4311-b67f-a05003f7e6bf":{"id":"802c6126-3283-4311-b67f-a05003f7e6bf","doc_no":"A.6.1.1.4.2.5.1.1.2.8","title":"Lazy Summer Protocol Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8146,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.8 - Lazy Summer Protocol Instance Configuration Document](74db9986-5277-4c5f-8e27-f6a312ed591f).","contentHash":"f6839948602d10db2b2e7eb417e2c5709782483eb08c77a6b3d7c80f26a7e5fb","addressRefs":[]},"3c43db85-3995-4c95-a85c-e72786a28501":{"id":"3c43db85-3995-4c95-a85c-e72786a28501","doc_no":"A.6.1.1.4.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8147,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"0e6a80cb-041c-4dc1-a22b-91fda88ecd92":{"id":"0e6a80cb-041c-4dc1-a22b-91fda88ecd92","doc_no":"A.6.1.1.4.2.5.1.1.3.1","title":"Summer.fi Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8148,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.3.1 - Summer.fi Instance Configuration Document](fd9c7ace-e72c-4ffb-a74e-7106a0dde80b).","contentHash":"f5225b1d87a042a807063333ab019faa7cec05ef5625292d3d9fc09abcd00ee8","addressRefs":[]},"95beed80-4199-4c08-82bd-0ae7827c98b0":{"id":"95beed80-4199-4c08-82bd-0ae7827c98b0","doc_no":"A.6.1.1.4.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8149,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.5.1.1.2 - Active Instances Directory](c6275b51-9ee0-49df-a4ea-33a24cd2c752),; whereas failed Invocations are Archived in [A.6.1.1.4.2.5.1.1.5 - Hub Data Repository](86d7913a-b8d0-42a8-a6b7-02c190e74373).","contentHash":"b8e3a5a747fd2cda16d834177513369bd1ad7f7116cd901205b2c86ad5d11f83","addressRefs":[]},"91c685ab-75fb-4bd4-ad68-b9a26afc1962":{"id":"91c685ab-75fb-4bd4-ad68-b9a26afc1962","doc_no":"A.6.1.1.4.2.5.1.1.4.1","title":"MetaMask","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8150,"content":"The Invocation Status and Instance Configuration Document location of this prospective Instance are specified below:\n\nInvocation Status: `Planning`\n\nInstance Configuration Document Location: [A.6.1.1.4.2.5.1.4.1 - MetaMask Instance Configuration Document](d43ec3dd-96bf-419f-8387-f85615e6bcc5).","contentHash":"df95e0e30806705e38fe602965b9f0878f0092d80b0ab01617f023944af9780e","addressRefs":[]},"915e98d4-8cec-4598-8906-d9cff11ac5aa":{"id":"915e98d4-8cec-4598-8906-d9cff11ac5aa","doc_no":"A.6.1.1.4.2.5.1.1.4.2","title":"InstaDapp","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8151,"content":"The Invocation Status and Instance Configuration Document location of this prospective Instance are specified below:\n\nInvocation Status: `Planning`\nInstance Configuration Document Location: [A.6.1.1.4.2.5.1.4.2 - InstaDapp Instance Configuration Document](e870392a-2552-41ca-a148-4be47d34bac7).","contentHash":"69254928ce006139227f504a87f1992561938ea981917627ca3fdfa158909b24","addressRefs":[]},"d901f747-bd11-4359-b7d3-05752098586e":{"id":"d901f747-bd11-4359-b7d3-05752098586e","doc_no":"A.6.1.1.4.2.5.1.1.4.3","title":"Gnosis Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8152,"content":"The Invocation Status and Instance Configuration Document location of this prospective Instance are specified below:\n\nInvocation Status: `Planning`\nInstance Configuration Document Location: [A.6.1.1.4.2.5.1.4.3 - Gnosis Protocol Instance Configuration Document](34cde6e0-89a1-44a4-9ce1-58873b83c63b).","contentHash":"5c279a6d055baf67dca437d2c43f854350dfe8daa35fa7c4c78a7d249091c12c","addressRefs":[]},"befc9c75-0263-443d-b662-fe667a645d79":{"id":"befc9c75-0263-443d-b662-fe667a645d79","doc_no":"A.6.1.1.4.2.5.1.1.4.4","title":"Piku.co","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8153,"content":"The Invocation Status and Instance Configuration Document location of this prospective Instance are specified below:\n\nInvocation Status: `Planning`\nInstance Configuration Document Location: [A.6.1.1.4.2.5.1.4.4 - Piku.co Instance Configuration Document](bc145261-ff5d-4937-abbd-0719390ff124).","contentHash":"9cdc44d9c27fe770cbef03f3442c6f653053d4d61270b65844b224fbdaef199b","addressRefs":[]},"86d7913a-b8d0-42a8-a6b7-02c190e74373":{"id":"86d7913a-b8d0-42a8-a6b7-02c190e74373","doc_no":"A.6.1.1.4.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8154,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"d2f66b3d-7903-47e7-8f71-3aaa79407c20":{"id":"d2f66b3d-7903-47e7-8f71-3aaa79407c20","doc_no":"A.6.1.1.4.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8155,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"9e28ce11-cd68-4c1a-b872-eae49dc4887e":{"id":"9e28ce11-cd68-4c1a-b872-eae49dc4887e","doc_no":"A.6.1.1.4.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8156,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"6e3010db-596c-478b-9aed-8fb4222a53d1":{"id":"6e3010db-596c-478b-9aed-8fb4222a53d1","doc_no":"A.6.1.1.4.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8157,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"cb0709e4-c51d-45cc-b385-0c20a0bf4b25":{"id":"cb0709e4-c51d-45cc-b385-0c20a0bf4b25","doc_no":"A.6.1.1.4.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8158,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"b52f88c6-427b-45f6-8e1c-81fa27e522c8":{"id":"b52f88c6-427b-45f6-8e1c-81fa27e522c8","doc_no":"A.6.1.1.4.2.5.1.2.1","title":"Sky.money App Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8159,"content":"The documents herein contain the Instance Configuration Document for the Sky.money App Distribution Reward Primitive Instance.","contentHash":"010bbb1c459c9fa69d25655f105c8c55ec62149de3de43fed34a1f08f0aae9f0","addressRefs":[]},"5455497f-bfb3-49a0-a788-0b7db4da799b":{"id":"5455497f-bfb3-49a0-a788-0b7db4da799b","doc_no":"A.6.1.1.4.2.5.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8160,"content":"The documents herein define the parameters of the Sky.money App Instance of the Distribution Reward Primitive.","contentHash":"1952976ed40799d89524727278fae390b3eb2cd51e6f5feb1e2eb2588273de8c","addressRefs":[]},"fcff71ae-93ff-49f7-aa39-a97077a921c6":{"id":"fcff71ae-93ff-49f7-aa39-a97077a921c6","doc_no":"A.6.1.1.4.2.5.1.2.1.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8161,"content":"`1`.","contentHash":"c0e61d6e019a4af547bcb5cfe9498a230d228519d375eee6faca605446af7513","addressRefs":[]},"f79a1c05-b4f7-4b11-b9be-1e4f7d72f34f":{"id":"f79a1c05-b4f7-4b11-b9be-1e4f7d72f34f","doc_no":"A.6.1.1.4.2.5.1.2.1.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8162,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"e5ff6cc4-c1d2-4184-a266-010104a6a28f":{"id":"e5ff6cc4-c1d2-4184-a266-010104a6a28f","doc_no":"A.6.1.1.4.2.5.1.2.1.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8163,"content":"The documents herein define the custom parameters of the Sky.money App Instance of the Distribution Reward Primitive, if any.","contentHash":"284ce5d2bf2f9955f4419d8b4e23b7b9d2cb8c383179e82911f699b499ab7cad","addressRefs":[]},"cb266ef8-782b-4bef-af06-be12b727b280":{"id":"cb266ef8-782b-4bef-af06-be12b727b280","doc_no":"A.6.1.1.4.2.5.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8164,"content":"The documents herein define the process for the ongoing management of the Sky.money App Instance of the Distribution Reward Primitive.","contentHash":"31e75f09a5b6ccafde6b9a69ca0342a0773acd47d456f30d29ade14c2c59153e","addressRefs":[]},"bd3b25ac-90b8-49f0-ac29-bb51a2290820":{"id":"bd3b25ac-90b8-49f0-ac29-bb51a2290820","doc_no":"A.6.1.1.4.2.5.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8165,"content":"This document defines the protocol for routine ongoing management of the Sky.money App Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"211a1d0c46ca19c39adf89ebc1a6334e27e224f2c584c0f7e08b7112dd091dfe","addressRefs":[]},"b803a685-e88f-48d9-92e9-7e9e3c574b36":{"id":"b803a685-e88f-48d9-92e9-7e9e3c574b36","doc_no":"A.6.1.1.4.2.5.1.2.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8166,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"eff49ccd-5874-41d9-aff0-3e3e2a348336":{"id":"eff49ccd-5874-41d9-aff0-3e3e2a348336","doc_no":"A.6.1.1.4.2.5.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8167,"content":"The documents herein define the protocol for non-routine ongoing management of the Sky.money App Instance of this Distribution Reward Primitive.","contentHash":"1996dd2bd521f795685965d71ad8b1cbbe54835f86ef978cdbf3b88e470e1d07","addressRefs":[]},"d7296a92-3a38-42c3-938c-5327725b0fbb":{"id":"d7296a92-3a38-42c3-938c-5327725b0fbb","doc_no":"A.6.1.1.4.2.5.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8168,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Sky.money App Instance of this Distribution Reward Primitive.","contentHash":"84bbe0951efc3f4e360bc4520cb866926b093af82c0bf3f1e4256eba13415c6f","addressRefs":[]},"4ef496cf-201e-4a98-9f7e-e61ad7eebfd6":{"id":"4ef496cf-201e-4a98-9f7e-e61ad7eebfd6","doc_no":"A.6.1.1.4.2.5.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8169,"content":"The documents herein contain data relevant to the Sky.money App Instance of the Distribution Reward Primitive.","contentHash":"076caacc69ff8dfe970639e39c04cbacdfc37eabb248fef0c51dabee6ca7935a","addressRefs":[]},"c4fead38-31dc-4a6a-8d98-5f28b1a46f7a":{"id":"c4fead38-31dc-4a6a-8d98-5f28b1a46f7a","doc_no":"A.6.1.1.4.2.5.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8170,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"919d7b43-51e1-4d53-93c6-ff84a633542b":{"id":"919d7b43-51e1-4d53-93c6-ff84a633542b","doc_no":"A.6.1.1.4.2.5.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8171,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"8bb175ef-0165-417c-9222-f4ed8df23b3f":{"id":"8bb175ef-0165-417c-9222-f4ed8df23b3f","doc_no":"A.6.1.1.4.2.5.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8172,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"8ece0051-0eee-427f-b2ea-1abfd52b80cd":{"id":"8ece0051-0eee-427f-b2ea-1abfd52b80cd","doc_no":"A.6.1.1.4.2.5.1.2.1.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8173,"content":"The Distribution Reward payments for the Sky.money App Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"20be0ff9e5d31cba3207fc69adbbc487e61a3162034d6e9ac4ae1f7544fc1fb8","addressRefs":[]},"09282f1f-f4fa-40b6-9073-6adc42f31569":{"id":"09282f1f-f4fa-40b6-9073-6adc42f31569","doc_no":"A.6.1.1.4.2.5.1.2.1.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8174,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"5aada153-29f6-4304-b56e-9d425dc978a4":{"id":"5aada153-29f6-4304-b56e-9d425dc978a4","doc_no":"A.6.1.1.4.2.5.1.2.2","title":"Sky.money Open Source Widgets Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8175,"content":"The documents herein contain the Instance Configuration Document for the Sky.money Open Source Widgets Distribution Reward Primitive Instance.","contentHash":"9b422358a028b70779b6a5e51595075f4b9aa47db82c8465a7bfbcbdcf90f8ac","addressRefs":[]},"159c7e99-c884-4496-aa9b-b7721be4849a":{"id":"159c7e99-c884-4496-aa9b-b7721be4849a","doc_no":"A.6.1.1.4.2.5.1.2.2.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8176,"content":"The documents herein define the parameters of the Sky.money Open Source Widgets Instance of the Distribution Reward Primitive.","contentHash":"e9f4037628623ac84adf7570d28671909bde7606050b7ea3263d806822dcc172","addressRefs":[]},"9a774d02-8882-4363-87b9-2efebc8142f8":{"id":"9a774d02-8882-4363-87b9-2efebc8142f8","doc_no":"A.6.1.1.4.2.5.1.2.2.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8177,"content":"`0`.","contentHash":"2c4b3a20d6a9711596d747b836dda36919488cced535e5d020cec1a12a0f244c","addressRefs":[]},"31579503-9b6d-408e-ad44-28cf411c22f5":{"id":"31579503-9b6d-408e-ad44-28cf411c22f5","doc_no":"A.6.1.1.4.2.5.1.2.2.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8178,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"79e22741-ef2b-4b8e-b97c-acead4550deb":{"id":"79e22741-ef2b-4b8e-b97c-acead4550deb","doc_no":"A.6.1.1.4.2.5.1.2.2.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8179,"content":"The documents herein define the custom parameters of the Sky.money Open Source Widgets Instance of the Distribution Reward Primitive, if any.","contentHash":"d1946d89984cb5e43ce7f5dca3b31d26041f43cc08ee4f268b5844d266cb714a","addressRefs":[]},"4f94c1ee-d908-412a-b4c9-2f59e5bd4e67":{"id":"4f94c1ee-d908-412a-b4c9-2f59e5bd4e67","doc_no":"A.6.1.1.4.2.5.1.2.2.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8180,"content":"The documents herein define the process for the ongoing management of the Sky.money Open Source Widgets Instance of the Distribution Reward Primitive.","contentHash":"e7e39e1532a9c2c7de5c0d2deabb7b6043a4f3beb40547c31f7dd32f308dbf38","addressRefs":[]},"461e8506-cc90-4c8d-9927-153ee996c432":{"id":"461e8506-cc90-4c8d-9927-153ee996c432","doc_no":"A.6.1.1.4.2.5.1.2.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8181,"content":"This document defines the protocol for routine ongoing management of the Sky.money Frontend Open Source Widgets Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"0205923ec69a7a04235285704a74527cc9ccefa785fce11c2d5a61961009270c","addressRefs":[]},"5524ef1f-2b23-457a-b1fc-89773f56a7f3":{"id":"5524ef1f-2b23-457a-b1fc-89773f56a7f3","doc_no":"A.6.1.1.4.2.5.1.2.2.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8182,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"2ff3ed8b-6466-4a3d-87e0-040fb8940859":{"id":"2ff3ed8b-6466-4a3d-87e0-040fb8940859","doc_no":"A.6.1.1.4.2.5.1.2.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8183,"content":"The documents herein define the protocol for non-routine ongoing management of the Sky.money Open Source Widgets Instance of this Distribution Reward Primitive.","contentHash":"6ced0b667914cb5c18daf9eb20e226af345e727b0b7111ac6661fea4a7e1102b","addressRefs":[]},"45f2cc2c-e96d-455f-808e-e188e5aece34":{"id":"45f2cc2c-e96d-455f-808e-e188e5aece34","doc_no":"A.6.1.1.4.2.5.1.2.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8184,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Sky.money Open Source Widgets Instance of this Distribution Reward Primitive.","contentHash":"417875f1217209e0bd8292a077b29ef102fcb6c9c45e27a7f8729d1d8620ee14","addressRefs":[]},"b198cdd7-92c2-4ff5-9f10-b0d315ed5f00":{"id":"b198cdd7-92c2-4ff5-9f10-b0d315ed5f00","doc_no":"A.6.1.1.4.2.5.1.2.2.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8185,"content":"The documents herein contain data relevant to the Sky.money Open Source Widgets Instance of the Distribution Reward Primitive.","contentHash":"97e3e2c9f82068bd6c1d19184b77dae7f9b74cbafe582d676c5af8e2c1ba3450","addressRefs":[]},"8578558a-5bd3-4256-a8f6-0e14da879257":{"id":"8578558a-5bd3-4256-a8f6-0e14da879257","doc_no":"A.6.1.1.4.2.5.1.2.2.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8186,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"f3de12e6-9ca6-4969-95a4-50b6c6b928b3":{"id":"f3de12e6-9ca6-4969-95a4-50b6c6b928b3","doc_no":"A.6.1.1.4.2.5.1.2.2.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8187,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"09c5171b-5fe5-4a37-ad78-0e4be7b4c0f9":{"id":"09c5171b-5fe5-4a37-ad78-0e4be7b4c0f9","doc_no":"A.6.1.1.4.2.5.1.2.2.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8188,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"d96439a8-df0d-4ba9-973e-896fac953fad":{"id":"d96439a8-df0d-4ba9-973e-896fac953fad","doc_no":"A.6.1.1.4.2.5.1.2.2.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8189,"content":"The Distribution Reward payments for the Sky.money Open Source Widgets Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"26faa5bf3c1a79c109c38231e84cd89b3e9f428faf07fab4d87d6dea5e4171a2","addressRefs":[]},"ad573b24-befc-49f9-be30-6c65f8986c61":{"id":"ad573b24-befc-49f9-be30-6c65f8986c61","doc_no":"A.6.1.1.4.2.5.1.2.2.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8190,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"9907bb75-f389-42bb-8fe4-e03ff3039c46":{"id":"9907bb75-f389-42bb-8fe4-e03ff3039c46","doc_no":"A.6.1.1.4.2.5.1.2.3","title":"DeFi Saver Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8191,"content":"The documents herein contain the Instance Configuration Document for the DeFi Saver Distribution Reward Primitive Instance.","contentHash":"8a37202c9cb5b41cae04ef9b8955d4cda4597c4e064b93dd421c4f3302e1da4f","addressRefs":[]},"a7b36acb-01b2-42a3-8014-d567a82ab81e":{"id":"a7b36acb-01b2-42a3-8014-d567a82ab81e","doc_no":"A.6.1.1.4.2.5.1.2.3.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8192,"content":"The documents herein define the parameters of the DeFi Saver Instance of the Distribution Reward Primitive.","contentHash":"7ea057a8c83198197c6dd32edeb934b8facdb25b021c487fd3154edd4d6e49e0","addressRefs":[]},"b8b563d3-7b0c-4a35-adb7-4c6f120c7f26":{"id":"b8b563d3-7b0c-4a35-adb7-4c6f120c7f26","doc_no":"A.6.1.1.4.2.5.1.2.3.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8193,"content":"`1002`.","contentHash":"050ec3f524b13cbc560ac479fc362c8391ef5bf38f4d5f2bf6e6fc0a86b6cf94","addressRefs":[]},"be4e3d61-e28e-48d9-bc04-413ee57859ad":{"id":"be4e3d61-e28e-48d9-bc04-413ee57859ad","doc_no":"A.6.1.1.4.2.5.1.2.3.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8194,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"613151ab-cddd-426e-b4b4-4a7a659efd0c":{"id":"613151ab-cddd-426e-b4b4-4a7a659efd0c","doc_no":"A.6.1.1.4.2.5.1.2.3.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8195,"content":"The documents herein define the custom parameters of the DeFi Saver Instance of the Distribution Reward Primitive, if any.","contentHash":"5cff1c1890608cf626e278239216cb5a91b0d06beadcb5299ca796fe26847c41","addressRefs":[]},"352fd637-e23d-4598-998f-a1949f006002":{"id":"352fd637-e23d-4598-998f-a1949f006002","doc_no":"A.6.1.1.4.2.5.1.2.3.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8196,"content":"The documents herein define the process for the ongoing management of the DeFi Saver Instance of the Distribution Reward Primitive.","contentHash":"86f59ea43c5a307b1618608fff4d180b537cfceeb322c88d433db01c9b4a6c80","addressRefs":[]},"2e0cdaa7-5d3a-42c2-808d-220c4823c0e2":{"id":"2e0cdaa7-5d3a-42c2-808d-220c4823c0e2","doc_no":"A.6.1.1.4.2.5.1.2.3.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8197,"content":"This document defines the protocol for routine ongoing management of the DeFi Saver Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"36e10e4ee3485fef37629ffb0443bd44aa2e53d119e65f41710c72d7b13faf22","addressRefs":[]},"9cef88a9-952f-460b-92c3-d6bb90974972":{"id":"9cef88a9-952f-460b-92c3-d6bb90974972","doc_no":"A.6.1.1.4.2.5.1.2.3.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8198,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"a1f81f47-953d-4fde-8406-48ef1f4bf55a":{"id":"a1f81f47-953d-4fde-8406-48ef1f4bf55a","doc_no":"A.6.1.1.4.2.5.1.2.3.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8199,"content":"The documents herein define the protocol for non-routine ongoing management of the DeFi Saver Instance of this Distribution Reward Primitive.","contentHash":"7f3203504147fc3e8a1e3b7f503a66e6a2cf2bc1f04addf392a4163da3a764ac","addressRefs":[]},"8a8a1d60-594e-4042-8252-612d9603dab4":{"id":"8a8a1d60-594e-4042-8252-612d9603dab4","doc_no":"A.6.1.1.4.2.5.1.2.3.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8200,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the DeFi Saver Instance of this Distribution Reward Primitive.","contentHash":"04554169024b51fefb2a83808c1356e298751da28488c078bf9c78d1041c1773","addressRefs":[]},"7b55a0f5-cd48-4a95-a637-6cbf10a66ec5":{"id":"7b55a0f5-cd48-4a95-a637-6cbf10a66ec5","doc_no":"A.6.1.1.4.2.5.1.2.3.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8201,"content":"The documents herein contain data relevant to the DeFi Saver Instance of the Distribution Reward Primitive.","contentHash":"126587829e9ef40e41833b0cf12f3c703057b04a745884151b18d476ea176b6f","addressRefs":[]},"3117ffa8-81bb-4fc3-ab15-2e2a41de26fa":{"id":"3117ffa8-81bb-4fc3-ab15-2e2a41de26fa","doc_no":"A.6.1.1.4.2.5.1.2.3.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8202,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"e4cdcd58-9f16-4efe-9671-a0b667267004":{"id":"e4cdcd58-9f16-4efe-9671-a0b667267004","doc_no":"A.6.1.1.4.2.5.1.2.3.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8203,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"63a206b3-3bae-4c14-ac3c-e658b912b238":{"id":"63a206b3-3bae-4c14-ac3c-e658b912b238","doc_no":"A.6.1.1.4.2.5.1.2.3.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8204,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"0f9d7876-d376-4f85-840d-c3cbb96872d3":{"id":"0f9d7876-d376-4f85-840d-c3cbb96872d3","doc_no":"A.6.1.1.4.2.5.1.2.3.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8205,"content":"The Distribution Reward payments for the DeFi Saver Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"319ca20a034005ee7f6b9596bc4b15cf6eee91cece730d7628e25d380b062e83","addressRefs":[]},"731c96eb-57a2-434c-852c-2c7f461efb46":{"id":"731c96eb-57a2-434c-852c-2c7f461efb46","doc_no":"A.6.1.1.4.2.5.1.2.3.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8206,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"e2a262ce-e59a-421c-ab32-803fe41802c4":{"id":"e2a262ce-e59a-421c-ab32-803fe41802c4","doc_no":"A.6.1.1.4.2.5.1.2.3.3.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8207,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"8fc2657e-fb6b-4d43-988c-6f47b71052f1":{"id":"8fc2657e-fb6b-4d43-988c-6f47b71052f1","doc_no":"A.6.1.1.4.2.5.1.2.3.3.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8208,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"da35cd2c-4113-4656-a5f5-5b804b5f894f":{"id":"da35cd2c-4113-4656-a5f5-5b804b5f894f","doc_no":"A.6.1.1.4.2.5.1.2.3.3.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8209,"content":"DeFi Saver - `0x6467e807dB1E71B9Ef04E0E3aFb962E4B0900B2B`","contentHash":"0d5c7ae0b659b712616cfcf870fa241103c8fa0403b046f3e7a3ecb69fa851d6","addressRefs":["0x6467e807db1e71b9ef04e0e3afb962e4b0900b2b"]},"80f22d64-0ccf-4bb2-8da4-d170a95d2161":{"id":"80f22d64-0ccf-4bb2-8da4-d170a95d2161","doc_no":"A.6.1.1.4.2.5.1.2.4","title":"CoW Swap Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8210,"content":"The documents herein contain the Instance Configuration Document for the CoW Swap Distribution Reward Primitive Instance.","contentHash":"0b3f45c44d989d6b679085794c19b6688f4cb161ad00fda611181ec293eabdea","addressRefs":[]},"014a4af6-2df3-47fe-b0e4-c1238f3ce18b":{"id":"014a4af6-2df3-47fe-b0e4-c1238f3ce18b","doc_no":"A.6.1.1.4.2.5.1.2.4.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8211,"content":"The documents herein define the parameters of the CoW Swap Instance of the Distribution Reward Primitive.","contentHash":"75ecdcbc1e1eaa0ea316dc65d6d32c46c4e647d4906ae47bb75d66fe6d32a3d8","addressRefs":[]},"3df72746-229c-4b32-bafa-802df1b04401":{"id":"3df72746-229c-4b32-bafa-802df1b04401","doc_no":"A.6.1.1.4.2.5.1.2.4.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8212,"content":"`1003`.","contentHash":"bf3c3c7497c96b6a75d5c36d9672bd91f63656338d45e5aaecd82a069b644dcd","addressRefs":[]},"fc6cd905-6f53-4e3a-9ac8-14ca46fef6af":{"id":"fc6cd905-6f53-4e3a-9ac8-14ca46fef6af","doc_no":"A.6.1.1.4.2.5.1.2.4.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8213,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.2 - Ethereum Mainnet CoW Swap Tracking Methodology](1b5cc0ee-0ee8-467e-ab49-33c06ad417dc). Specifically, on-chain Settlement Events on the CoW Swap settlement contract ([https://etherscan.io/address/0x9008D19f58AAbD9eD0D60971565AA8510560ab41](https://etherscan.io/address/0x9008D19f58AAbD9eD0D60971565AA8510560ab41)) are checked for where they coincide perfectly with USDS deposit transactions into sUSDS.","contentHash":"457113ef60067ae1cefa188387dd1c2e348c1fec8537c49dbbe7847fda894b71","addressRefs":["0x9008d19f58aabd9ed0d60971565aa8510560ab41"]},"947cf303-80e9-4b9f-9403-a9634d876d76":{"id":"947cf303-80e9-4b9f-9403-a9634d876d76","doc_no":"A.6.1.1.4.2.5.1.2.4.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8214,"content":"The documents herein define the custom parameters of the CoW Swap Instance of the Distribution Reward Primitive, if any.","contentHash":"26bf94c51f219beeb300b6cd584f98b2aab910a7134542145727174633eabff4","addressRefs":[]},"6c37960a-a6e0-44af-b2fd-148853d0655f":{"id":"6c37960a-a6e0-44af-b2fd-148853d0655f","doc_no":"A.6.1.1.4.2.5.1.2.4.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8215,"content":"The documents herein define the process for the ongoing management of the CoW Swap Instance of the Distribution Reward Primitive.","contentHash":"4b4c223851347b172606de83329c8cbdfd2533e26561a994a5d1e5972d52cb44","addressRefs":[]},"c6e84f25-85fe-412e-808a-235e713d4ec2":{"id":"c6e84f25-85fe-412e-808a-235e713d4ec2","doc_no":"A.6.1.1.4.2.5.1.2.4.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8216,"content":"This document defines the protocol for routine ongoing management of the CoW Swap Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"095115eee02b6ddb400d2aa6e52ff88fa1f5837027c3eb3cafc890e5adec5cb8","addressRefs":[]},"1d1a2365-7cf2-409e-9637-5d7f9e6c0752":{"id":"1d1a2365-7cf2-409e-9637-5d7f9e6c0752","doc_no":"A.6.1.1.4.2.5.1.2.4.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8217,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"8f48dd88-d114-4c6f-9b01-a8c7468808b8":{"id":"8f48dd88-d114-4c6f-9b01-a8c7468808b8","doc_no":"A.6.1.1.4.2.5.1.2.4.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8218,"content":"The documents herein define the protocol for non-routine ongoing management of the CoW Swap Instance of this Distribution Reward Primitive.","contentHash":"37617676d68eeeeffb98257832c6b2b9292b916c5b6d1b5f7bab6a155fea2983","addressRefs":[]},"61d2a0ea-09d1-4ad3-a668-66ebd5593c2f":{"id":"61d2a0ea-09d1-4ad3-a668-66ebd5593c2f","doc_no":"A.6.1.1.4.2.5.1.2.4.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8219,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the CoW Swap Instance of this Distribution Reward Primitive.","contentHash":"7ad6c7c2d25fcd1c34b52389b09184c070b2679ba8358fc3ed71a24802092116","addressRefs":[]},"67188304-6a6e-421a-92b9-bf995cd49e49":{"id":"67188304-6a6e-421a-92b9-bf995cd49e49","doc_no":"A.6.1.1.4.2.5.1.2.4.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8220,"content":"The documents herein contain data relevant to the CoW Swap Instance of the Distribution Reward Primitive.","contentHash":"1dc03e607855a29b8e1f27f4347088905b70b0a8cc70ee484bf303482823e895","addressRefs":[]},"d0dcbfc1-826f-4f68-ac22-f356f2b3d3f4":{"id":"d0dcbfc1-826f-4f68-ac22-f356f2b3d3f4","doc_no":"A.6.1.1.4.2.5.1.2.4.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8221,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"7b5a94d3-1bdd-4b06-823e-c31199717e29":{"id":"7b5a94d3-1bdd-4b06-823e-c31199717e29","doc_no":"A.6.1.1.4.2.5.1.2.4.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8222,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"4a803925-4c83-44a8-9530-4b0f30b6d928":{"id":"4a803925-4c83-44a8-9530-4b0f30b6d928","doc_no":"A.6.1.1.4.2.5.1.2.4.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8223,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"dc323489-6f9b-4f0d-a5c6-3c74729cef7c":{"id":"dc323489-6f9b-4f0d-a5c6-3c74729cef7c","doc_no":"A.6.1.1.4.2.5.1.2.4.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8224,"content":"The Distribution Reward payments for the CoW Swap Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"b333aed7f17fe1ea99e78270e49f8955a2b25720b565b30c4ca4fc795407f1c8","addressRefs":[]},"655886dc-7ca2-45cd-be2c-7be8421961c7":{"id":"655886dc-7ca2-45cd-be2c-7be8421961c7","doc_no":"A.6.1.1.4.2.5.1.2.4.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8225,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"84df5c1e-86b7-431d-bb0e-8708f99a572e":{"id":"84df5c1e-86b7-431d-bb0e-8708f99a572e","doc_no":"A.6.1.1.4.2.5.1.2.4.3.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8226,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"88f6d49f-9473-46c2-a030-d3f74f2d1377":{"id":"88f6d49f-9473-46c2-a030-d3f74f2d1377","doc_no":"A.6.1.1.4.2.5.1.2.4.3.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8227,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"910f8a42-b56c-4617-890a-d135b196b168":{"id":"910f8a42-b56c-4617-890a-d135b196b168","doc_no":"A.6.1.1.4.2.5.1.2.4.3.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8228,"content":"CoW Swap - `0x616dE58c011F8736fa20c7Ae5352F7f6FB9F0669`","contentHash":"0dee9052af47b78f2249ceca28a760bb32c408be81ee1074d86a1889ddf03c27","addressRefs":["0x616de58c011f8736fa20c7ae5352f7f6fb9f0669"]},"d3f7f0e6-b912-4464-be3f-20b0c600bcfa":{"id":"d3f7f0e6-b912-4464-be3f-20b0c600bcfa","doc_no":"A.6.1.1.4.2.5.1.2.5","title":"ParaSwap Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8229,"content":"The documents herein contain the Instance Configuration Document for the ParaSwap Distribution Reward Primitive Instance.","contentHash":"69f7148f5aa1aa2039e16146a4b89bb6aa865ebc60e5b3558948b1ae130723dc","addressRefs":[]},"0dbc09fd-557b-4434-a3ac-2ac66da6acb4":{"id":"0dbc09fd-557b-4434-a3ac-2ac66da6acb4","doc_no":"A.6.1.1.4.2.5.1.2.5.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8230,"content":"The documents herein define the parameters of the ParaSwap Instance of the Distribution Reward Primitive.","contentHash":"3fab89bac7aae6b8c0036134d58925e5ce2af701cff23b93240c2d0ba630ae23","addressRefs":[]},"6940bdf3-78db-4565-8195-1c2fea444c8a":{"id":"6940bdf3-78db-4565-8195-1c2fea444c8a","doc_no":"A.6.1.1.4.2.5.1.2.5.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8231,"content":"`1004`.","contentHash":"47d4dc2e45b3c2e2e452949b200f6be55acc0c642a442adc733b2211393ddf9a","addressRefs":[]},"df5554b7-1b06-43bb-a112-4768192a73cf":{"id":"df5554b7-1b06-43bb-a112-4768192a73cf","doc_no":"A.6.1.1.4.2.5.1.2.5.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8232,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"78a7d271-f5d2-4692-8831-7bf98ea754ac":{"id":"78a7d271-f5d2-4692-8831-7bf98ea754ac","doc_no":"A.6.1.1.4.2.5.1.2.5.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8233,"content":"The documents herein define the custom parameters of the ParaSwap Instance of the Distribution Reward Primitive, if any.","contentHash":"f95f9621aefa8bf6db911d9d8e879fc3d44e287ae4cc660698d9d5aeaf842f4f","addressRefs":[]},"576943c0-8301-4372-bc8d-4620cf94bb05":{"id":"576943c0-8301-4372-bc8d-4620cf94bb05","doc_no":"A.6.1.1.4.2.5.1.2.5.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8234,"content":"The documents herein define the process for the ongoing management of the ParaSwap Instance of the Distribution Reward Primitive.","contentHash":"1cd45d5a32fd384e698985a7fd2d13f07087969ff13d3e2f5dca6d4da3d7e266","addressRefs":[]},"bf955649-4ac2-45e2-8376-052e884698e4":{"id":"bf955649-4ac2-45e2-8376-052e884698e4","doc_no":"A.6.1.1.4.2.5.1.2.5.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8235,"content":"This document defines the protocol for routine ongoing management of the ParaSwap Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"d65d6af2dc9ba614822ef35e2b86413e0994e3feb27fbb19fb82c0e44e6c66e6","addressRefs":[]},"200fb6db-3425-4bf5-adde-b9d3bcff412d":{"id":"200fb6db-3425-4bf5-adde-b9d3bcff412d","doc_no":"A.6.1.1.4.2.5.1.2.5.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8236,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"0d81e6c2-4586-4aa1-9a1b-c8ce66a05fd1":{"id":"0d81e6c2-4586-4aa1-9a1b-c8ce66a05fd1","doc_no":"A.6.1.1.4.2.5.1.2.5.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8237,"content":"The documents herein define the protocol for non-routine ongoing management of the ParaSwap Instance of this Distribution Reward Primitive.","contentHash":"bced7e74b6c09b3d5bf667f5a95d3663e8d110902ef26b28d454fddfa48a6d5b","addressRefs":[]},"b5583385-2432-40f3-a110-6790c7520754":{"id":"b5583385-2432-40f3-a110-6790c7520754","doc_no":"A.6.1.1.4.2.5.1.2.5.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8238,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the ParaSwap Instance of this Distribution Reward Primitive.","contentHash":"18f33e8424ae53047315f46e87b0f6361fd93be354e1099579427cdcfdf7a398","addressRefs":[]},"4a18e7da-c6b5-4850-825d-9e7aaf406795":{"id":"4a18e7da-c6b5-4850-825d-9e7aaf406795","doc_no":"A.6.1.1.4.2.5.1.2.5.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8239,"content":"The documents herein contain data relevant to the ParaSwap Instance of the Distribution Reward Primitive.","contentHash":"720dad0eeb26178e7380f8bca58ce61f66eefa886db9aa34c08bf444afd595c1","addressRefs":[]},"32dfe611-a223-40af-9100-70688fa0f162":{"id":"32dfe611-a223-40af-9100-70688fa0f162","doc_no":"A.6.1.1.4.2.5.1.2.5.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8240,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"20e0c61c-70c8-4d68-b90e-ce664ca5097a":{"id":"20e0c61c-70c8-4d68-b90e-ce664ca5097a","doc_no":"A.6.1.1.4.2.5.1.2.5.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8241,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"993a4e87-14d0-4d98-9477-446d4bbbfe12":{"id":"993a4e87-14d0-4d98-9477-446d4bbbfe12","doc_no":"A.6.1.1.4.2.5.1.2.5.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8242,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"3ea87681-b351-462c-b375-6fb60c817755":{"id":"3ea87681-b351-462c-b375-6fb60c817755","doc_no":"A.6.1.1.4.2.5.1.2.5.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8243,"content":"The Distribution Reward payments for the ParaSwap Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"68e2b6b7248ab289e4eb8adbf1b14cf6ad6b40cce64251f7be7fbb6708e3e550","addressRefs":[]},"4588c98b-1c51-4f8c-8cc5-baab631950ef":{"id":"4588c98b-1c51-4f8c-8cc5-baab631950ef","doc_no":"A.6.1.1.4.2.5.1.2.5.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8244,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"81bafe53-8c66-43ec-82fd-5848b9d64555":{"id":"81bafe53-8c66-43ec-82fd-5848b9d64555","doc_no":"A.6.1.1.4.2.5.1.2.5.3.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8245,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"3306dbf8-6c7c-4cfe-b98d-08105282272e":{"id":"3306dbf8-6c7c-4cfe-b98d-08105282272e","doc_no":"A.6.1.1.4.2.5.1.2.5.3.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8246,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"8088e4e4-a594-448c-a3cb-752b907b4f3c":{"id":"8088e4e4-a594-448c-a3cb-752b907b4f3c","doc_no":"A.6.1.1.4.2.5.1.2.5.3.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8247,"content":"The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact.","contentHash":"19f1d83f9602009a3889539a14d01432ce98b63d21824bf920a8a696a26ab4ee","addressRefs":[]},"f36ce752-38d1-4dd4-8a51-dd18f2151756":{"id":"f36ce752-38d1-4dd4-8a51-dd18f2151756","doc_no":"A.6.1.1.4.2.5.1.2.6","title":"Yearn (Gimme) Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8248,"content":"The documents herein contain the Instance Configuration Document for the Yearn (Gimme) Distribution Reward Primitive Instance.","contentHash":"71825707e0daab0780ac582e55b6996145de336ed5c1646595d8511901c54c61","addressRefs":[]},"49866e74-c131-4e4d-9165-325bba89cd48":{"id":"49866e74-c131-4e4d-9165-325bba89cd48","doc_no":"A.6.1.1.4.2.5.1.2.6.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8249,"content":"The documents herein define the parameters of the Yearn (Gimme) Instance of the Distribution Reward Primitive.","contentHash":"ea1da2780c0d68472f75b9debcb9e71132f4a2ab48cedaea39cd09db289542a3","addressRefs":[]},"30bcc1e7-0c26-4e67-b823-1fd1203c7370":{"id":"30bcc1e7-0c26-4e67-b823-1fd1203c7370","doc_no":"A.6.1.1.4.2.5.1.2.6.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8250,"content":"`1007`.","contentHash":"5a53ead11812694f7cd431fd8aef1fdd4d4c566e7a866ad051d77099d9757759","addressRefs":[]},"43ede046-4e45-4bf8-895b-d5823965eeae":{"id":"43ede046-4e45-4bf8-895b-d5823965eeae","doc_no":"A.6.1.1.4.2.5.1.2.6.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8251,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"f1a4510d-f38c-499c-bc07-405a8ca6816d":{"id":"f1a4510d-f38c-499c-bc07-405a8ca6816d","doc_no":"A.6.1.1.4.2.5.1.2.6.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8252,"content":"The documents herein define the custom parameters of the Yearn (Gimme) Instance of the Distribution Reward Primitive, if any.","contentHash":"ca128129d9990a4502520c4073e95a940bd81f65f561b8484433dbea834a6149","addressRefs":[]},"a3796610-b310-4dac-872b-21ce3bd835e7":{"id":"a3796610-b310-4dac-872b-21ce3bd835e7","doc_no":"A.6.1.1.4.2.5.1.2.6.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8253,"content":"The documents herein define the process for the ongoing management of the Yearn (Gimme) Instance of the Distribution Reward Primitive.","contentHash":"7ce7bbf52b9ccc3158730b6c2a5c8d3ac77d9b4237ec234044d4db574a001da9","addressRefs":[]},"1c93fd6d-5cff-46e7-86e5-0af4f6c83b4b":{"id":"1c93fd6d-5cff-46e7-86e5-0af4f6c83b4b","doc_no":"A.6.1.1.4.2.5.1.2.6.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8254,"content":"This document defines the protocol for routine ongoing management of the Yearn (Gimme) Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"89626b663a0246241a8265c000a6aa4ac2b629f55c4abbfb729ca6cdc15b62eb","addressRefs":[]},"d341791b-eec0-46a8-ada5-f6142ff49034":{"id":"d341791b-eec0-46a8-ada5-f6142ff49034","doc_no":"A.6.1.1.4.2.5.1.2.6.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8255,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"8998657a-ed5e-4610-b1bc-171f715a5d48":{"id":"8998657a-ed5e-4610-b1bc-171f715a5d48","doc_no":"A.6.1.1.4.2.5.1.2.6.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8256,"content":"The documents herein define the protocol for non-routine ongoing management of the Yearn (Gimme) Instance of this Distribution Reward Primitive.","contentHash":"3d538fe4af55e3b6d973f0614b7eecaf2863af71d047174e88b1b7e6d015ba80","addressRefs":[]},"8146f803-ddf9-4f85-81d3-84666b3f259c":{"id":"8146f803-ddf9-4f85-81d3-84666b3f259c","doc_no":"A.6.1.1.4.2.5.1.2.6.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8257,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Yearn (Gimme) Instance of this Distribution Reward Primitive.","contentHash":"cd60dd5fa1f65ad54d0550d94a7f2358dbc069623646b1761e94742160a24e5b","addressRefs":[]},"e2cf9382-81d0-4f38-a9bc-8b7c647805fb":{"id":"e2cf9382-81d0-4f38-a9bc-8b7c647805fb","doc_no":"A.6.1.1.4.2.5.1.2.6.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8258,"content":"The documents herein contain data relevant to the Yearn (Gimme) Instance of the Distribution Reward Primitive.","contentHash":"8d21ca439cb1123e76d15800278ea5f05e5e8c934e2d744df3457cad80f264be","addressRefs":[]},"2a400f84-7251-41ed-a8ce-c3d091c90ad6":{"id":"2a400f84-7251-41ed-a8ce-c3d091c90ad6","doc_no":"A.6.1.1.4.2.5.1.2.6.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8259,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"3bdf7ecb-accd-4b70-b956-a5e05cb60668":{"id":"3bdf7ecb-accd-4b70-b956-a5e05cb60668","doc_no":"A.6.1.1.4.2.5.1.2.6.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8260,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"1816152b-22ea-4a5a-822f-88da78afe8cf":{"id":"1816152b-22ea-4a5a-822f-88da78afe8cf","doc_no":"A.6.1.1.4.2.5.1.2.6.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8261,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"30be45d8-cd38-4c52-b4d0-ed7225c97b9a":{"id":"30be45d8-cd38-4c52-b4d0-ed7225c97b9a","doc_no":"A.6.1.1.4.2.5.1.2.6.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8262,"content":"The Distribution Reward payments for the Yearn (Gimme) Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"05387ec30f6b494527c982e5c1f4b10a73ba1ac1984439da73c9b07414a48d97","addressRefs":[]},"707956cc-62f8-4620-a95f-b45ebf263218":{"id":"707956cc-62f8-4620-a95f-b45ebf263218","doc_no":"A.6.1.1.4.2.5.1.2.6.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8263,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"690e54dd-c88a-422e-a06d-e6812035fc1c":{"id":"690e54dd-c88a-422e-a06d-e6812035fc1c","doc_no":"A.6.1.1.4.2.5.1.2.6.3.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8264,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"034c4a3d-46fc-46b4-afd0-1187bc29ea07":{"id":"034c4a3d-46fc-46b4-afd0-1187bc29ea07","doc_no":"A.6.1.1.4.2.5.1.2.6.3.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8265,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"be1b9146-9d66-4ab1-a47d-724d0220f5ef":{"id":"be1b9146-9d66-4ab1-a47d-724d0220f5ef","doc_no":"A.6.1.1.4.2.5.1.2.6.3.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8266,"content":"Yearn (Gimme) - `0xFEB4acf3df3cDEA7399794D0869ef76A6EfAff52`","contentHash":"751a3d5aa5ca5059d6705f7a6f740a257ee1a75e3427a5c9e8badc8a3fbd725c","addressRefs":["0xfeb4acf3df3cdea7399794d0869ef76a6efaff52"]},"ee4f9b64-aeb7-4813-b187-996e8172fea1":{"id":"ee4f9b64-aeb7-4813-b187-996e8172fea1","doc_no":"A.6.1.1.4.2.5.1.2.7","title":"MOM Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8267,"content":"The documents herein contain the Instance Configuration Document for the MOM Distribution Reward Primitive Instance.","contentHash":"7e61f007e11ad0aef2cb1b03c51830ac04569f5f743994b341281e18c3f68490","addressRefs":[]},"8adfffaf-011e-4762-9b44-3e35f0f6adaa":{"id":"8adfffaf-011e-4762-9b44-3e35f0f6adaa","doc_no":"A.6.1.1.4.2.5.1.2.7.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8268,"content":"The documents herein define the parameters of the MOM Instance of the Distribution Reward Primitive.","contentHash":"13c57e2271b30400e161af94729ac9296e060791975782207f8b4b30b7bec6ef","addressRefs":[]},"d87d51bb-8476-48b7-a8af-795917bb6f0d":{"id":"d87d51bb-8476-48b7-a8af-795917bb6f0d","doc_no":"A.6.1.1.4.2.5.1.2.7.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8269,"content":"`1015`.","contentHash":"cfac55415a903a8b52eb3fdb9b0aebea8380f6d917a8795d99b405bb313f9c07","addressRefs":[]},"0ed5b976-e929-4a38-9f45-6eda54d4cc6c":{"id":"0ed5b976-e929-4a38-9f45-6eda54d4cc6c","doc_no":"A.6.1.1.4.2.5.1.2.7.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8270,"content":"This Instance uses the Tracking Methodologies specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2) and [A.2.2.8.1.2.1.2.2.3 - Base Tracking Methodology](f710bddf-dc1d-483c-9503-483574cb6333).","contentHash":"1ddd237df371d795f044a9428378fb823213bc7c4aff1d685cdfad2363b0460b","addressRefs":[]},"4c40a025-6ff0-4ee7-9a33-d4c03b68f332":{"id":"4c40a025-6ff0-4ee7-9a33-d4c03b68f332","doc_no":"A.6.1.1.4.2.5.1.2.7.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8271,"content":"The documents herein define the custom parameters of the MOM Instance of the Distribution Reward Primitive, if any.","contentHash":"cd95133e587463a6372d1d0688b292667e0845b109045dce73f01f8774a821b9","addressRefs":[]},"3c170bd2-4a9e-4461-bf81-d33fd253dfc9":{"id":"3c170bd2-4a9e-4461-bf81-d33fd253dfc9","doc_no":"A.6.1.1.4.2.5.1.2.7.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8272,"content":"The documents herein define the process for the ongoing management of the MOM Instance of the Distribution Reward Primitive.","contentHash":"096290113bc139625b16ec680a6ab87e17b566d583936462057f62d91f8c5988","addressRefs":[]},"4b22e820-db7b-4f76-8b82-6f60b21ca1d9":{"id":"4b22e820-db7b-4f76-8b82-6f60b21ca1d9","doc_no":"A.6.1.1.4.2.5.1.2.7.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8273,"content":"This document defines the protocol for routine ongoing management of the MOM Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"2bbf81a81a22a5d076367a0725fa83a7b39b7e2f5500f7af533c6b5d617d3b32","addressRefs":[]},"9bbe0d8a-a65b-4da4-bdd0-8206c564f090":{"id":"9bbe0d8a-a65b-4da4-bdd0-8206c564f090","doc_no":"A.6.1.1.4.2.5.1.2.7.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8274,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"940153fc-b44e-4421-82de-2d196fe1b505":{"id":"940153fc-b44e-4421-82de-2d196fe1b505","doc_no":"A.6.1.1.4.2.5.1.2.7.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8275,"content":"The documents herein define the protocol for non-routine ongoing management of the MOM Instance of this Distribution Reward Primitive.","contentHash":"41e5da41676a26ce738d38a637eb21f78d602565edfe8f11f77a79c010d8f082","addressRefs":[]},"0d0e6b23-5f44-4f0f-98a1-a4c82780c3d7":{"id":"0d0e6b23-5f44-4f0f-98a1-a4c82780c3d7","doc_no":"A.6.1.1.4.2.5.1.2.7.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8276,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the MOM Instance of this Distribution Reward Primitive.","contentHash":"ac37a76959979a9953f273e9d91501053f6e2485ab0bdbc140056ac16a378063","addressRefs":[]},"6c8b1217-db6e-4952-bccf-a5635a3a0119":{"id":"6c8b1217-db6e-4952-bccf-a5635a3a0119","doc_no":"A.6.1.1.4.2.5.1.2.7.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8277,"content":"The documents herein contain data relevant to the MOM Instance of the Distribution Reward Primitive.","contentHash":"34d1f09933082b63deaf30c3ab0644633f4271e07d0035ba02bdf2a270619137","addressRefs":[]},"bea56b80-5d46-4a44-81a5-0df050a5255b":{"id":"bea56b80-5d46-4a44-81a5-0df050a5255b","doc_no":"A.6.1.1.4.2.5.1.2.7.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8278,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"16f6bff2-ed77-4e02-806d-5fe7941f94ce":{"id":"16f6bff2-ed77-4e02-806d-5fe7941f94ce","doc_no":"A.6.1.1.4.2.5.1.2.7.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8279,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"df961d91-acfd-45de-8fd6-f17237d34eb8":{"id":"df961d91-acfd-45de-8fd6-f17237d34eb8","doc_no":"A.6.1.1.4.2.5.1.2.7.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8280,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"e1961614-467f-40b0-9e7a-f67e2a70cc97":{"id":"e1961614-467f-40b0-9e7a-f67e2a70cc97","doc_no":"A.6.1.1.4.2.5.1.2.7.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8281,"content":"The Distribution Reward payments for the MOM Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"25a585837e4bbec13422015372667e87a7bd9255444b81285449a93e8543ee69","addressRefs":[]},"8520b41b-cf03-493b-a6ce-9314983f38b3":{"id":"8520b41b-cf03-493b-a6ce-9314983f38b3","doc_no":"A.6.1.1.4.2.5.1.2.7.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8282,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"74b0e9af-0a6d-4cfc-988a-5621713772fc":{"id":"74b0e9af-0a6d-4cfc-988a-5621713772fc","doc_no":"A.6.1.1.4.2.5.1.2.7.3.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8283,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"fc1a5e0b-0909-48d1-adc4-77e51a900050":{"id":"fc1a5e0b-0909-48d1-adc4-77e51a900050","doc_no":"A.6.1.1.4.2.5.1.2.7.3.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8284,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"4fc18aff-0fd6-41ea-a5e8-92ea54861c99":{"id":"4fc18aff-0fd6-41ea-a5e8-92ea54861c99","doc_no":"A.6.1.1.4.2.5.1.2.7.3.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8285,"content":"The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact.","contentHash":"19f1d83f9602009a3889539a14d01432ce98b63d21824bf920a8a696a26ab4ee","addressRefs":[]},"74db9986-5277-4c5f-8e27-f6a312ed591f":{"id":"74db9986-5277-4c5f-8e27-f6a312ed591f","doc_no":"A.6.1.1.4.2.5.1.2.8","title":"Lazy Summer Protocol Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8286,"content":"The documents herein contain the Instance Configuration Document for the Lazy Summer Protocol Distribution Reward Primitive Instance.","contentHash":"54caa2fd0c6a9d745d83959cc659be38e39442d1a45c6637cf292bffa315fecf","addressRefs":[]},"be044103-09bc-410d-872a-1dfefc9410aa":{"id":"be044103-09bc-410d-872a-1dfefc9410aa","doc_no":"A.6.1.1.4.2.5.1.2.8.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8287,"content":"The documents herein define the parameters of the Lazy Summer Protocol Instance of the Distribution Reward Primitive.","contentHash":"08c2272dcb94961f61944f0b3e27d2a77dc4579610f47518700fedcdd9747b56","addressRefs":[]},"a6caf2b3-a62d-495f-a580-1f962df1f994":{"id":"a6caf2b3-a62d-495f-a580-1f962df1f994","doc_no":"A.6.1.1.4.2.5.1.2.8.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8288,"content":"`1016`.","contentHash":"92c921c5b37e8cc2aad4598d6f2919eee8879137f41625a16587d3e3fdfd35e9","addressRefs":[]},"02b3a96e-2b37-4cd5-ace8-1849b1ce4840":{"id":"02b3a96e-2b37-4cd5-ace8-1849b1ce4840","doc_no":"A.6.1.1.4.2.5.1.2.8.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8289,"content":"This parameter will be defined in a future iteration of the Skybase Artifact.","contentHash":"d9808310fb2a313d41d447fbc6f4f6061ea3998ae9608d253da4787d07b61c22","addressRefs":[]},"73767654-3011-447b-9232-9e46cd6755aa":{"id":"73767654-3011-447b-9232-9e46cd6755aa","doc_no":"A.6.1.1.4.2.5.1.2.8.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8290,"content":"The documents herein define the custom parameters of the Lazy Summer Protocol Instance of the Distribution Reward Primitive, if any.","contentHash":"702a52ffe0921183399caa56442911469734b1daa3bd689fe82e71734b6514b4","addressRefs":[]},"d9308330-b4c2-4b7a-9416-3363dc334089":{"id":"d9308330-b4c2-4b7a-9416-3363dc334089","doc_no":"A.6.1.1.4.2.5.1.2.8.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8291,"content":"The documents herein define the process for the ongoing management of the Lazy Summer Protocol Instance of the Distribution Reward Primitive.","contentHash":"159696d1b83e16e5ae03612ca02bcb7e878422efb3d84de7a4eb12f14ed5b0fd","addressRefs":[]},"4a7215e4-f78e-4a44-9935-d5f18463cb3d":{"id":"4a7215e4-f78e-4a44-9935-d5f18463cb3d","doc_no":"A.6.1.1.4.2.5.1.2.8.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8292,"content":"This document defines the protocol for routine ongoing management of the Lazy Summer Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"b6e00d12d2636f410ca03c1cb9e71c4521c21b0c25eb9b248cdfdb8e4432da87","addressRefs":[]},"65d8cd24-5a71-40b7-8f37-8bd6f07de068":{"id":"65d8cd24-5a71-40b7-8f37-8bd6f07de068","doc_no":"A.6.1.1.4.2.5.1.2.8.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8293,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"f6a4b979-13e6-48da-a53c-aef0b06f657b":{"id":"f6a4b979-13e6-48da-a53c-aef0b06f657b","doc_no":"A.6.1.1.4.2.5.1.2.8.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8294,"content":"The documents herein define the protocol for non-routine ongoing management of the Lazy Summer Protocol Instance of this Distribution Reward Primitive.","contentHash":"27a80d942ed5946404b20f1118794c5d2a5806047b7b6685d66c0ef5d96f0e86","addressRefs":[]},"d607f30d-740a-4988-834a-e0d3522d1972":{"id":"d607f30d-740a-4988-834a-e0d3522d1972","doc_no":"A.6.1.1.4.2.5.1.2.8.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8295,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Lazy Summer Protocol Instance of this Distribution Reward Primitive.","contentHash":"90d789bf6bd59ea7d8a81e7594defb345740a8a7826023f44b6d605dc5f6135d","addressRefs":[]},"d6312bd7-c098-4fdd-99b8-a84cee98f64f":{"id":"d6312bd7-c098-4fdd-99b8-a84cee98f64f","doc_no":"A.6.1.1.4.2.5.1.2.8.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8296,"content":"The documents herein contain data relevant to the Lazy Summer Protocol Instance of the Distribution Reward Primitive.","contentHash":"e6414a59e5d161068ef142694bdfb976ffbb17fc17212fdaafde25a1379b97ac","addressRefs":[]},"85861627-db6d-4be3-8057-8aff18035130":{"id":"85861627-db6d-4be3-8057-8aff18035130","doc_no":"A.6.1.1.4.2.5.1.2.8.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8297,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"97a92e00-3f0e-481c-ab18-c3ceb1105d42":{"id":"97a92e00-3f0e-481c-ab18-c3ceb1105d42","doc_no":"A.6.1.1.4.2.5.1.2.8.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8298,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"cd44d715-d147-42b9-b84b-9a8d370ca6bf":{"id":"cd44d715-d147-42b9-b84b-9a8d370ca6bf","doc_no":"A.6.1.1.4.2.5.1.2.8.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8299,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"42349b55-1334-478b-bddd-d692e55e07b9":{"id":"42349b55-1334-478b-bddd-d692e55e07b9","doc_no":"A.6.1.1.4.2.5.1.2.8.3.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8300,"content":"The Distribution Reward payments for the Lazy Summer Protocol Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for `Direct Edit`.","contentHash":"9ef12afce9d3012be4f1639dee940ae99275fee0732f0b47c8e8d941789a3978","addressRefs":[]},"928ecae3-ee6f-4961-bae0-90dbf42b3b4d":{"id":"928ecae3-ee6f-4961-bae0-90dbf42b3b4d","doc_no":"A.6.1.1.4.2.5.1.2.8.3.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8301,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"04d4fea9-cc1e-4275-af1a-27f8c9b15d0b":{"id":"04d4fea9-cc1e-4275-af1a-27f8c9b15d0b","doc_no":"A.6.1.1.4.2.5.1.2.8.3.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8302,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for `Direct Edit`.","contentHash":"b7ca031f9ed094706c39db53ea8f37eecadf7ed998afb56a05e9cd0e9fdb76b6","addressRefs":[]},"0b55dd49-4787-4895-be75-091f9c2689f3":{"id":"0b55dd49-4787-4895-be75-091f9c2689f3","doc_no":"A.6.1.1.4.2.5.1.2.8.3.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8303,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"08771b54-8577-44ee-9edb-1915c0f6f050":{"id":"08771b54-8577-44ee-9edb-1915c0f6f050","doc_no":"A.6.1.1.4.2.5.1.2.8.3.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8304,"content":"The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact.","contentHash":"19f1d83f9602009a3889539a14d01432ce98b63d21824bf920a8a696a26ab4ee","addressRefs":[]},"44389e6f-b48e-4426-a6c8-110ec76ebea1":{"id":"44389e6f-b48e-4426-a6c8-110ec76ebea1","doc_no":"A.6.1.1.4.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8305,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"fd9c7ace-e72c-4ffb-a74e-7106a0dde80b":{"id":"fd9c7ace-e72c-4ffb-a74e-7106a0dde80b","doc_no":"A.6.1.1.4.2.5.1.3.1","title":"Summer.fi Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8306,"content":"The documents herein contain the Instance Configuration Document for the Summer.fi Distribution Reward Primitive Instance.","contentHash":"f4abf3a5108aabf332f9afc26a1cc5cb4d625031aaff5db52e86e0ed67971aa5","addressRefs":[]},"a2cbe867-bc51-4a3c-82b6-d921e2b0a4fc":{"id":"a2cbe867-bc51-4a3c-82b6-d921e2b0a4fc","doc_no":"A.6.1.1.4.2.5.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8307,"content":"The documents herein define the parameters of the Summer.fi Instance of the Distribution Reward Primitive.","contentHash":"11b7632049e4dfbe9797b8f0dfbefc7cf500d3f61a6662de66776dc03d4c71c9","addressRefs":[]},"1e8b16e7-b10e-4da7-936d-5cffbac57571":{"id":"1e8b16e7-b10e-4da7-936d-5cffbac57571","doc_no":"A.6.1.1.4.2.5.1.3.1.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8308,"content":"`1001`.","contentHash":"e44151c6fb3ffbaf2e5d54c22884e39fa878048256346e3da31f99614ef721de","addressRefs":[]},"8abb90c2-c62d-4dbd-96b5-d4e447a3bc4d":{"id":"8abb90c2-c62d-4dbd-96b5-d4e447a3bc4d","doc_no":"A.6.1.1.4.2.5.1.3.1.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8309,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - Ethereum Mainnet General Tracking Methodology](87fd6861-ba8a-4bde-945e-ee9ad37ae3e2).","contentHash":"35ba273303049ef15fe1c0802bd3ca06779aa5ddc22692a035084b9d92f8be97","addressRefs":[]},"80314c99-0e54-4449-88a0-828e86da92c5":{"id":"80314c99-0e54-4449-88a0-828e86da92c5","doc_no":"A.6.1.1.4.2.5.1.3.1.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8310,"content":"The documents herein define the custom parameters of the Summer.fi Instance of the Distribution Reward Primitive, if any.","contentHash":"0aafaefe68c42aed858165d16c6535c7d4a9f5531344eb4e1bd84837db9a6e22","addressRefs":[]},"7d73baad-0128-460d-b3b3-6b18ba86e755":{"id":"7d73baad-0128-460d-b3b3-6b18ba86e755","doc_no":"A.6.1.1.4.2.5.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8311,"content":"The documents herein define the process for the ongoing management of the Summer.fi Instance of the Distribution Reward Primitive.","contentHash":"ddae13921531c844d29b419655b126919cf04db69dd34086898732c23c0409b8","addressRefs":[]},"de64fb0f-e867-495f-9e43-c197072e1c3d":{"id":"de64fb0f-e867-495f-9e43-c197072e1c3d","doc_no":"A.6.1.1.4.2.5.1.3.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8312,"content":"This document defines the protocol for routine ongoing management of the Summer.fi Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"5008d17fc56cb74921ef4c5d9f97dca016fc0eb9141a80a5e64f621002a1209d","addressRefs":[]},"216473d9-6f63-45ff-aa7b-a6bec64dd6dc":{"id":"216473d9-6f63-45ff-aa7b-a6bec64dd6dc","doc_no":"A.6.1.1.4.2.5.1.3.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8313,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"47306338-2f28-4c95-b0d3-843744e04165":{"id":"47306338-2f28-4c95-b0d3-843744e04165","doc_no":"A.6.1.1.4.2.5.1.3.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8314,"content":"The documents herein define the protocol for non-routine ongoing management of the Summer.fi Instance of this Distribution Reward Primitive.","contentHash":"8b0b737b0a247894ec70e179ad6e6842f88c5ee7b2b77beb8de95ccfb3662eae","addressRefs":[]},"41233dc2-c7d4-4cd4-9e23-cebbbbfaa9ce":{"id":"41233dc2-c7d4-4cd4-9e23-cebbbbfaa9ce","doc_no":"A.6.1.1.4.2.5.1.3.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8315,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Summer.fi Instance of this Distribution Reward Primitive.","contentHash":"69a45832e64f4d17e5548d82abfbfe409d43a740bf621b27303292df674d5413","addressRefs":[]},"72bc2ff0-df12-4156-8300-5c6a09badccf":{"id":"72bc2ff0-df12-4156-8300-5c6a09badccf","doc_no":"A.6.1.1.4.2.5.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8316,"content":"The documents herein contain data relevant to the Summer.fi Instance of the Distribution Reward Primitive.","contentHash":"eab286bbaa1b39462a301cbc17e7c664f6e113c74700f2e334323611f53e0dc9","addressRefs":[]},"7cc02e97-e849-4f19-81bc-2fc85ccd2361":{"id":"7cc02e97-e849-4f19-81bc-2fc85ccd2361","doc_no":"A.6.1.1.4.2.5.1.3.1.3.1","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8317,"content":"The Distribution Reward payments for the Summer.fi Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"3703089415049517c39cf918066c9c5b3e568828b874a7790888ff32edab2584","addressRefs":[]},"289e8b48-d1ae-43d0-a9a5-b66672caacde":{"id":"289e8b48-d1ae-43d0-a9a5-b66672caacde","doc_no":"A.6.1.1.4.2.5.1.3.1.3.1.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8318,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"73fc6f80-ac05-423f-ac58-e22dbfa8de3f":{"id":"73fc6f80-ac05-423f-ac58-e22dbfa8de3f","doc_no":"A.6.1.1.4.2.5.1.3.1.3.2","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8319,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"1b25a9fd-1bb0-4425-b9a1-372f737d3a45":{"id":"1b25a9fd-1bb0-4425-b9a1-372f737d3a45","doc_no":"A.6.1.1.4.2.5.1.3.1.3.2.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8320,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"cc82491d-cabb-42dd-a63a-4b3c23ee55f0":{"id":"cc82491d-cabb-42dd-a63a-4b3c23ee55f0","doc_no":"A.6.1.1.4.2.5.1.3.1.3.2.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8321,"content":"Summer.fi - `0xC7b548AD9Cf38721810246C079b2d8083aba8909`","contentHash":"998c0494073e15091b665b9f650ddff6caa1625de5350e659645bd44c006981b","addressRefs":["0xc7b548ad9cf38721810246c079b2d8083aba8909"]},"dabb169a-e7d5-44c2-9ed8-f0936aa9c22a":{"id":"dabb169a-e7d5-44c2-9ed8-f0936aa9c22a","doc_no":"A.6.1.1.4.2.5.1.3.1.3.3","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8322,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"cc50de8e-ac63-4254-bb24-8a4247b8d2b5":{"id":"cc50de8e-ac63-4254-bb24-8a4247b8d2b5","doc_no":"A.6.1.1.4.2.5.1.3.1.3.4","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8323,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"bff7bad8-b9c9-4fb7-ae9c-08137f427f36":{"id":"bff7bad8-b9c9-4fb7-ae9c-08137f427f36","doc_no":"A.6.1.1.4.2.5.1.3.1.3.5","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8324,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"05362fab-8fc5-487c-af2e-b6ebf6f4445e":{"id":"05362fab-8fc5-487c-af2e-b6ebf6f4445e","doc_no":"A.6.1.1.4.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8325,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.5.1.2 - Active Instances](cb0709e4-c51d-45cc-b385-0c20a0bf4b25).","contentHash":"8c488a3e57ed6671890b24efe5c8841bc5f9f9745e4aaf502fc269b1696ce85c","addressRefs":[]},"d43ec3dd-96bf-419f-8387-f85615e6bcc5":{"id":"d43ec3dd-96bf-419f-8387-f85615e6bcc5","doc_no":"A.6.1.1.4.2.5.1.4.1","title":"MetaMask Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8326,"content":"The documents herein contain the Instance Configuration Document for the MetaMask Distribution Reward Primitive Instance.","contentHash":"b9ac9cb36b8be7e3ddcaccd1aa7438174043a17428b785efbe3954e9b13ee931","addressRefs":[]},"650a20a0-362c-431b-bd56-ef13386c3aec":{"id":"650a20a0-362c-431b-bd56-ef13386c3aec","doc_no":"A.6.1.1.4.2.5.1.4.1.1","title":"Invocation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8327,"content":"`Planning`","contentHash":"186f9387deb4df9ad5dbf51656fbfea1a174909388c146bc0ccababda06922ac","addressRefs":[]},"f46ff617-d495-402f-a3dc-f4822a018b19":{"id":"f46ff617-d495-402f-a3dc-f4822a018b19","doc_no":"A.6.1.1.4.2.5.1.4.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8328,"content":"The documents herein define the parameters of the MetaMask Instance of the Distribution Reward Primitive.","contentHash":"d30ab3df8dffad7c397e5432253cdf742eff79b3133ce13fd67e1f8ce6d4415d","addressRefs":[]},"c3f4fb9f-9af6-495d-8261-04bd19c8c552":{"id":"c3f4fb9f-9af6-495d-8261-04bd19c8c552","doc_no":"A.6.1.1.4.2.5.1.4.1.2.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8329,"content":"`1005`.","contentHash":"10aab1a8fe9a006ed174aa0deb51703ece26c666cfdfd91e75c3ec62044e9e75","addressRefs":[]},"98906b92-72db-4f7e-ac79-053a92728025":{"id":"98906b92-72db-4f7e-ac79-053a92728025","doc_no":"A.6.1.1.4.2.5.1.4.1.2.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8330,"content":"This parameter will be defined in a future iteration of the Skybase Artifact.","contentHash":"d9808310fb2a313d41d447fbc6f4f6061ea3998ae9608d253da4787d07b61c22","addressRefs":[]},"fc5ec9c3-fad3-455d-8cb8-8be082ea388e":{"id":"fc5ec9c3-fad3-455d-8cb8-8be082ea388e","doc_no":"A.6.1.1.4.2.5.1.4.1.2.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8331,"content":"The documents herein define the custom parameters of the MetaMask Instance of the Distribution Reward Primitive, if any.","contentHash":"0ad436bb0520685cf0b8801fbef62d1940b47b8fad49ed7dcf0a2d1cc8fd40ba","addressRefs":[]},"81e97a1c-9bf1-4038-be0e-4eece0a2f88b":{"id":"81e97a1c-9bf1-4038-be0e-4eece0a2f88b","doc_no":"A.6.1.1.4.2.5.1.4.1.3","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8332,"content":"The documents herein define the process for the ongoing management of the MetaMask Instance of the Distribution Reward Primitive.","contentHash":"02ea1d4a6fa27469bcde53b9fae695504d72c823d3f46c701326ab0c1eacf222","addressRefs":[]},"02c6ffc8-5fdc-4a1f-8037-a6a1aeb5e51c":{"id":"02c6ffc8-5fdc-4a1f-8037-a6a1aeb5e51c","doc_no":"A.6.1.1.4.2.5.1.4.1.3.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8333,"content":"This document defines the protocol for routine ongoing management of the MetaMask Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"0c70ba3acbdc6e943b2e0e2a8da9f01516de5f23b3077e0b17cd52cffc7d2837","addressRefs":[]},"e739cfa7-90c6-49f2-9b03-ea4744e7f2e9":{"id":"e739cfa7-90c6-49f2-9b03-ea4744e7f2e9","doc_no":"A.6.1.1.4.2.5.1.4.1.3.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8334,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"167f2753-e45f-4d55-b182-2c17c4f1e2c5":{"id":"167f2753-e45f-4d55-b182-2c17c4f1e2c5","doc_no":"A.6.1.1.4.2.5.1.4.1.3.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8335,"content":"The documents herein define the protocol for non-routine ongoing management of the MetaMask Instance of this Distribution Reward Primitive.","contentHash":"a9a32e455dd2141366a736bf830a8aa29e2fcb2b62d83b6acbe25514312f9076","addressRefs":[]},"6c02ae31-2313-46ff-9232-2875186e0255":{"id":"6c02ae31-2313-46ff-9232-2875186e0255","doc_no":"A.6.1.1.4.2.5.1.4.1.3.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8336,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the MetaMask Instance of this Distribution Reward Primitive.","contentHash":"0572049eb450f45e67df3752380f0837fa6eab8240a2bb83b2a0a7bd4ab498c3","addressRefs":[]},"a4a10d71-42f8-49f3-9eeb-dda2ceb1332a":{"id":"a4a10d71-42f8-49f3-9eeb-dda2ceb1332a","doc_no":"A.6.1.1.4.2.5.1.4.1.4","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8337,"content":"The documents herein contain data relevant to the MetaMask Instance of the Distribution Reward Primitive.","contentHash":"5a4f752238b7d248436da2d2a02121c5e25730a825415c9726ec93262d938c97","addressRefs":[]},"177f02ea-cde5-4d68-b7de-c3cef1a47f32":{"id":"177f02ea-cde5-4d68-b7de-c3cef1a47f32","doc_no":"A.6.1.1.4.2.5.1.4.1.4.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8338,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"2cc897a5-eb49-4766-9489-3cdca7c74196":{"id":"2cc897a5-eb49-4766-9489-3cdca7c74196","doc_no":"A.6.1.1.4.2.5.1.4.1.4.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8339,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"a7582742-03a8-4095-b394-6fe1b62f912a":{"id":"a7582742-03a8-4095-b394-6fe1b62f912a","doc_no":"A.6.1.1.4.2.5.1.4.1.4.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8340,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"6296fedf-c2f4-4cdc-a16f-a2b0e8bd19bc":{"id":"6296fedf-c2f4-4cdc-a16f-a2b0e8bd19bc","doc_no":"A.6.1.1.4.2.5.1.4.1.4.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8341,"content":"The Distribution Reward payments for the MetaMask Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"6c9c5e48d619164643ad6509d78f830cd017ed45513811fb27389853d287ac04","addressRefs":[]},"20376e25-f067-400e-be73-dc2552766c47":{"id":"20376e25-f067-400e-be73-dc2552766c47","doc_no":"A.6.1.1.4.2.5.1.4.1.4.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8342,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"ded05ed5-e470-4cbc-b3f0-c7d8cd928584":{"id":"ded05ed5-e470-4cbc-b3f0-c7d8cd928584","doc_no":"A.6.1.1.4.2.5.1.4.1.4.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8343,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"aa0ea344-4e89-4b6e-8c32-afc5c19cf8d0":{"id":"aa0ea344-4e89-4b6e-8c32-afc5c19cf8d0","doc_no":"A.6.1.1.4.2.5.1.4.1.4.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8344,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"b537c8e2-92b6-4d2f-88ff-337acb1e8357":{"id":"b537c8e2-92b6-4d2f-88ff-337acb1e8357","doc_no":"A.6.1.1.4.2.5.1.4.1.4.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8345,"content":"The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact.","contentHash":"19f1d83f9602009a3889539a14d01432ce98b63d21824bf920a8a696a26ab4ee","addressRefs":[]},"e870392a-2552-41ca-a148-4be47d34bac7":{"id":"e870392a-2552-41ca-a148-4be47d34bac7","doc_no":"A.6.1.1.4.2.5.1.4.2","title":"InstaDapp Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8346,"content":"The documents herein contain the Instance Configuration Document for the InstaDapp Distribution Reward Primitive Instance.","contentHash":"cb13040a46d91b8f3a9f7f07cf455addf9092f53779df8ba40627a99e9ed2dde","addressRefs":[]},"2f8dec26-fa98-454d-b035-284359de4fe3":{"id":"2f8dec26-fa98-454d-b035-284359de4fe3","doc_no":"A.6.1.1.4.2.5.1.4.2.1","title":"Invocation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8347,"content":"`Planning`","contentHash":"186f9387deb4df9ad5dbf51656fbfea1a174909388c146bc0ccababda06922ac","addressRefs":[]},"58b69a0b-a8f3-40cd-bc36-154aa61d8f0c":{"id":"58b69a0b-a8f3-40cd-bc36-154aa61d8f0c","doc_no":"A.6.1.1.4.2.5.1.4.2.2","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8348,"content":"The documents herein define the parameters of the InstaDapp Instance of the Distribution Reward Primitive.","contentHash":"1b312749c8e69867baed2afe18abfae43bb8da69b7c33efd4c2a0eeb06dbaefd","addressRefs":[]},"d57c7da4-c5dd-4e11-b5a3-d08aafdaa65f":{"id":"d57c7da4-c5dd-4e11-b5a3-d08aafdaa65f","doc_no":"A.6.1.1.4.2.5.1.4.2.2.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8349,"content":"`1006`.","contentHash":"9621c7d40e8e35b73743726cd23d28665dea44b1f57380367432a0126ce8c514","addressRefs":[]},"1dcac5c2-21ec-4714-bf77-f861a851aec4":{"id":"1dcac5c2-21ec-4714-bf77-f861a851aec4","doc_no":"A.6.1.1.4.2.5.1.4.2.2.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8350,"content":"This parameter will be defined in a future iteration of the Skybase Artifact.","contentHash":"d9808310fb2a313d41d447fbc6f4f6061ea3998ae9608d253da4787d07b61c22","addressRefs":[]},"5c7380f4-bb98-4dcc-81de-0f02d4e71bbc":{"id":"5c7380f4-bb98-4dcc-81de-0f02d4e71bbc","doc_no":"A.6.1.1.4.2.5.1.4.2.2.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8351,"content":"The documents herein define the custom parameters of the InstaDapp Instance of the Distribution Reward Primitive, if any.","contentHash":"06e86d5fb71b6cf58121602dee165b456fdf824a21a06c558ff42a747745b26a","addressRefs":[]},"64113652-22f2-487b-b170-675ed1e25741":{"id":"64113652-22f2-487b-b170-675ed1e25741","doc_no":"A.6.1.1.4.2.5.1.4.2.3","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8352,"content":"The documents herein define the process for the ongoing management of the InstaDapp Instance of the Distribution Reward Primitive.","contentHash":"f174d69dc24e7d871d2c730cec15c48d86a26fc3ea694fa6ea7449318e0cb38b","addressRefs":[]},"c458078b-ffba-428e-950a-9c20a64967d4":{"id":"c458078b-ffba-428e-950a-9c20a64967d4","doc_no":"A.6.1.1.4.2.5.1.4.2.3.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8353,"content":"This document defines the protocol for routine ongoing management of the InstaDapp Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"37f8b2279970c7895785988652c725d01d0cad70bb9d2e433e98d11656426b4f","addressRefs":[]},"ae59d85f-0a27-461d-a2ef-4b10dd597fee":{"id":"ae59d85f-0a27-461d-a2ef-4b10dd597fee","doc_no":"A.6.1.1.4.2.5.1.4.2.3.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8354,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"7a34becd-4afd-405c-bfb2-a367568c516f":{"id":"7a34becd-4afd-405c-bfb2-a367568c516f","doc_no":"A.6.1.1.4.2.5.1.4.2.3.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8355,"content":"The documents herein define the protocol for non-routine ongoing management of the InstaDapp Instance of this Distribution Reward Primitive.","contentHash":"60f238fc0a36c5e95b6d5b7e64c2a9657aef4fa965891516363abf170c956b15","addressRefs":[]},"060f50d5-e37f-430a-a103-a06c6b880c63":{"id":"060f50d5-e37f-430a-a103-a06c6b880c63","doc_no":"A.6.1.1.4.2.5.1.4.2.3.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8356,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the InstaDapp Instance of this Distribution Reward Primitive.","contentHash":"0d9bf04b61a0b141ec5162ba69bd3b607570b72d10a92a66f1810bed3e309e07","addressRefs":[]},"0d530623-4cf8-4046-ac19-5a2095a805d2":{"id":"0d530623-4cf8-4046-ac19-5a2095a805d2","doc_no":"A.6.1.1.4.2.5.1.4.2.4","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8357,"content":"The documents herein contain data relevant to the InstaDapp Instance of the Distribution Reward Primitive.","contentHash":"dbd2e23e412f32e58a8786529842013bb8c90dc0f0209513eeab5eafee0f3cd7","addressRefs":[]},"f51aa574-e8c8-4e15-bfba-76082d40ac91":{"id":"f51aa574-e8c8-4e15-bfba-76082d40ac91","doc_no":"A.6.1.1.4.2.5.1.4.2.4.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8358,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"d35d512a-2c81-4491-b966-6803b68f9834":{"id":"d35d512a-2c81-4491-b966-6803b68f9834","doc_no":"A.6.1.1.4.2.5.1.4.2.4.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8359,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"57a3bfd7-83e2-4033-9dc0-d64274973784":{"id":"57a3bfd7-83e2-4033-9dc0-d64274973784","doc_no":"A.6.1.1.4.2.5.1.4.2.4.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8360,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"38f84680-46ff-400b-baeb-62a0684d2aa7":{"id":"38f84680-46ff-400b-baeb-62a0684d2aa7","doc_no":"A.6.1.1.4.2.5.1.4.2.4.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8361,"content":"The Distribution Reward payments for the InstaDapp Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"2c72ba37765b82c5fa38ba70adfa99e2f3c138b336a3798bdfadbed4691a77ef","addressRefs":[]},"a75fa6c5-8d93-43fe-acad-dfb07e226668":{"id":"a75fa6c5-8d93-43fe-acad-dfb07e226668","doc_no":"A.6.1.1.4.2.5.1.4.2.4.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8362,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"28b69d1f-44d3-4b97-8aff-809513145245":{"id":"28b69d1f-44d3-4b97-8aff-809513145245","doc_no":"A.6.1.1.4.2.5.1.4.2.4.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8363,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"1d995038-ec86-4f39-a02c-21ee651dd3cc":{"id":"1d995038-ec86-4f39-a02c-21ee651dd3cc","doc_no":"A.6.1.1.4.2.5.1.4.2.4.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8364,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"1438c4e7-e15b-443c-b9c6-dcdde63920c6":{"id":"1438c4e7-e15b-443c-b9c6-dcdde63920c6","doc_no":"A.6.1.1.4.2.5.1.4.2.4.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8365,"content":"The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact.","contentHash":"19f1d83f9602009a3889539a14d01432ce98b63d21824bf920a8a696a26ab4ee","addressRefs":[]},"34cde6e0-89a1-44a4-9ce1-58873b83c63b":{"id":"34cde6e0-89a1-44a4-9ce1-58873b83c63b","doc_no":"A.6.1.1.4.2.5.1.4.3","title":"Gnosis Protocol Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8366,"content":"The documents herein contain the Instance Configuration Document for the Gnosis Protocol Distribution Reward Primitive Instance.","contentHash":"955861758f00b9132e2f42393d72bf414551f19cf8b6c590d6740464f58c8996","addressRefs":[]},"ec6a6561-a5e3-4ec6-8ecf-b8053c98149b":{"id":"ec6a6561-a5e3-4ec6-8ecf-b8053c98149b","doc_no":"A.6.1.1.4.2.5.1.4.3.1","title":"Invocation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8367,"content":"`Planning`","contentHash":"186f9387deb4df9ad5dbf51656fbfea1a174909388c146bc0ccababda06922ac","addressRefs":[]},"a8cf666e-2fb6-4830-bc53-5005e0111408":{"id":"a8cf666e-2fb6-4830-bc53-5005e0111408","doc_no":"A.6.1.1.4.2.5.1.4.3.2","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8368,"content":"The documents herein define the parameters of the Gnosis Protocol Instance of the Distribution Reward Primitive.","contentHash":"f5d61d5be0124fcfd73b0e459323e7144b7b35858721cd19859c9e018735b4fc","addressRefs":[]},"96af997a-cd62-41f4-9e32-c5a9dd243f37":{"id":"96af997a-cd62-41f4-9e32-c5a9dd243f37","doc_no":"A.6.1.1.4.2.5.1.4.3.2.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8369,"content":"`1050`.","contentHash":"8b3ceeccf782cc319c86e7d486880cac30618145c90db7fe7f9bb8bad18dae52","addressRefs":[]},"07ec38da-a0ca-468e-83b7-2059ad5e4016":{"id":"07ec38da-a0ca-468e-83b7-2059ad5e4016","doc_no":"A.6.1.1.4.2.5.1.4.3.2.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8370,"content":"This parameter will be defined in a future iteration of the Skybase Artifact.","contentHash":"d9808310fb2a313d41d447fbc6f4f6061ea3998ae9608d253da4787d07b61c22","addressRefs":[]},"6fc01270-3033-45b4-8e88-79751b36448c":{"id":"6fc01270-3033-45b4-8e88-79751b36448c","doc_no":"A.6.1.1.4.2.5.1.4.3.2.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8371,"content":"The documents herein define the custom parameters of the Gnosis Instance of the Distribution Reward Primitive, if any.","contentHash":"f9b4b442b7d371e11ca8899ad2564ba2b6e25401b13e88a396b7724d5e7e5ec9","addressRefs":[]},"fac720c6-f7d2-410c-80bb-8b68c77cdd7c":{"id":"fac720c6-f7d2-410c-80bb-8b68c77cdd7c","doc_no":"A.6.1.1.4.2.5.1.4.3.3","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8372,"content":"The documents herein define the process for the ongoing management of the Gnosis Protocol Instance of the Distribution Reward Primitive.","contentHash":"cba36c41f0a07bb772977f4668b321a9bd4b4e5bb6fd3a30f7d354649bc9adbe","addressRefs":[]},"34d65ab5-5a03-42a6-848d-ace67c5e9ab0":{"id":"34d65ab5-5a03-42a6-848d-ace67c5e9ab0","doc_no":"A.6.1.1.4.2.5.1.4.3.3.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8373,"content":"This document defines the protocol for routine ongoing management of the Gnosis Protocol Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"86cdd7b9d58e8f782aa9f5f763643d8ca186410061fa010a1f2c2116259352a3","addressRefs":[]},"423d68eb-6fdd-44f4-9bd0-885b44abdd6d":{"id":"423d68eb-6fdd-44f4-9bd0-885b44abdd6d","doc_no":"A.6.1.1.4.2.5.1.4.3.3.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8374,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"9b770474-14bd-4846-8813-4df2bfa77a8f":{"id":"9b770474-14bd-4846-8813-4df2bfa77a8f","doc_no":"A.6.1.1.4.2.5.1.4.3.3.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8375,"content":"The documents herein define the protocol for non-routine ongoing management of the Gnosis Protocol Instance of this Distribution Reward Primitive.","contentHash":"e3b23ade25d08d9525db8171be2a9c08ad27ff1270545f6c5ed0f9090699b9e5","addressRefs":[]},"06e37d7d-f130-4b78-b207-32769d75c9db":{"id":"06e37d7d-f130-4b78-b207-32769d75c9db","doc_no":"A.6.1.1.4.2.5.1.4.3.3.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8376,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Gnosis Protocol Instance of this Distribution Reward Primitive.","contentHash":"069949d5e63e9903a021b837373df1d95ca692965c17d0295311d45293d7f090","addressRefs":[]},"1bd8546a-db64-46e5-9271-efc314b0a374":{"id":"1bd8546a-db64-46e5-9271-efc314b0a374","doc_no":"A.6.1.1.4.2.5.1.4.3.4","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8377,"content":"The documents herein contain data relevant to the Gnosis Protocol Instance of the Distribution Reward Primitive.","contentHash":"f9131aca3a10b498108b43572278a3661a54bdd6a9d092400a5d774fa463cb68","addressRefs":[]},"c2db568d-6c90-4a62-8fb9-33cfb504fc1d":{"id":"c2db568d-6c90-4a62-8fb9-33cfb504fc1d","doc_no":"A.6.1.1.4.2.5.1.4.3.4.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8378,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"446804db-4495-4621-a504-e3575e5be34b":{"id":"446804db-4495-4621-a504-e3575e5be34b","doc_no":"A.6.1.1.4.2.5.1.4.3.4.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8379,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"711781c6-57a9-4813-9e4d-263f9a70384a":{"id":"711781c6-57a9-4813-9e4d-263f9a70384a","doc_no":"A.6.1.1.4.2.5.1.4.3.4.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8380,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"32c6b23b-8c5f-4798-97e2-84248365365d":{"id":"32c6b23b-8c5f-4798-97e2-84248365365d","doc_no":"A.6.1.1.4.2.5.1.4.3.4.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8381,"content":"The Distribution Reward payments for the Gnosis Protocol Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"33e979e62fd8c34f53a5447b145659c8022326c6529092aab6e9487234d70da7","addressRefs":[]},"3dd71633-a629-47af-b806-f7930f1332da":{"id":"3dd71633-a629-47af-b806-f7930f1332da","doc_no":"A.6.1.1.4.2.5.1.4.3.4.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8382,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"efbea98b-9063-4706-a467-050eb2594339":{"id":"efbea98b-9063-4706-a467-050eb2594339","doc_no":"A.6.1.1.4.2.5.1.4.3.4.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8383,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"985b10b4-837a-48c6-884b-80de88e2462a":{"id":"985b10b4-837a-48c6-884b-80de88e2462a","doc_no":"A.6.1.1.4.2.5.1.4.3.4.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8384,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"802462c0-d9d1-42fa-8729-54135634f7f5":{"id":"802462c0-d9d1-42fa-8729-54135634f7f5","doc_no":"A.6.1.1.4.2.5.1.4.3.4.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8385,"content":"The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact.","contentHash":"19f1d83f9602009a3889539a14d01432ce98b63d21824bf920a8a696a26ab4ee","addressRefs":[]},"bc145261-ff5d-4937-abbd-0719390ff124":{"id":"bc145261-ff5d-4937-abbd-0719390ff124","doc_no":"A.6.1.1.4.2.5.1.4.4","title":"Piku.co Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8386,"content":"The documents herein contain the Instance Configuration Document for the Piku.co Distribution Reward Primitive Instance.","contentHash":"2720c16727d67f2b803b888d4df567637ca00e5906a908e710e0d1a4ab55a98b","addressRefs":[]},"76e70fba-b3a1-40dc-8625-6ba5c6447444":{"id":"76e70fba-b3a1-40dc-8625-6ba5c6447444","doc_no":"A.6.1.1.4.2.5.1.4.4.1","title":"Invocation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8387,"content":"`Planning`","contentHash":"186f9387deb4df9ad5dbf51656fbfea1a174909388c146bc0ccababda06922ac","addressRefs":[]},"79da10fb-e6c0-491f-8e18-80edc9e642ad":{"id":"79da10fb-e6c0-491f-8e18-80edc9e642ad","doc_no":"A.6.1.1.4.2.5.1.4.4.2","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8388,"content":"The documents herein define the parameters of the Piku.co Instance of the Distribution Reward Primitive.","contentHash":"ca7184e6e23a7242e446b7746bac747c84846a22efcc3a930b08dfa05996d992","addressRefs":[]},"e2a11959-ddcf-4b85-b093-92e2924f2d85":{"id":"e2a11959-ddcf-4b85-b093-92e2924f2d85","doc_no":"A.6.1.1.4.2.5.1.4.4.2.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8389,"content":"`1010`.","contentHash":"33e07422ede0291b1877409a1fd47a1ef637d84de682164c6848b13124c5abac","addressRefs":[]},"2785cf23-1be4-4c83-b50e-be57a30c1a79":{"id":"2785cf23-1be4-4c83-b50e-be57a30c1a79","doc_no":"A.6.1.1.4.2.5.1.4.4.2.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8390,"content":"This parameter will be defined in a future iteration of the Skybase Artifact.","contentHash":"d9808310fb2a313d41d447fbc6f4f6061ea3998ae9608d253da4787d07b61c22","addressRefs":[]},"0f252ad2-ea66-49a4-9ff5-10d9bb222532":{"id":"0f252ad2-ea66-49a4-9ff5-10d9bb222532","doc_no":"A.6.1.1.4.2.5.1.4.4.2.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8391,"content":"The documents herein define the custom parameters of the Piku.co Instance of the Distribution Reward Primitive, if any.","contentHash":"2efab0093bba995401342fdfd560ef15462865bc782ccb11ef3aa024e3234ac5","addressRefs":[]},"78aaaa71-7843-4910-aefe-6ba166cbbb0d":{"id":"78aaaa71-7843-4910-aefe-6ba166cbbb0d","doc_no":"A.6.1.1.4.2.5.1.4.4.3","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8392,"content":"The documents herein define the process for the ongoing management of the Piku.co Instance of the Distribution Reward Primitive.","contentHash":"b17b46ec5c251643b49b7bc869aa7b1fa44e0c1a8cdbcac2c33eb973e42e1165","addressRefs":[]},"a08670ae-0bc5-4424-9b65-38db64441e8d":{"id":"a08670ae-0bc5-4424-9b65-38db64441e8d","doc_no":"A.6.1.1.4.2.5.1.4.4.3.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8393,"content":"This document defines the protocol for routine ongoing management of the [Piku.co](http://Piku.co) Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"2528ce69556cc2f059cbfd80de3062cb6106516aeb81313bef7d6e2d119d6b3d","addressRefs":[]},"af262fdb-d5ac-4a53-9ca5-47e0448f7ff4":{"id":"af262fdb-d5ac-4a53-9ca5-47e0448f7ff4","doc_no":"A.6.1.1.4.2.5.1.4.4.3.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8394,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"4eee5be9-976e-4899-8444-a73c41a952e7":{"id":"4eee5be9-976e-4899-8444-a73c41a952e7","doc_no":"A.6.1.1.4.2.5.1.4.4.3.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8395,"content":"The documents herein define the protocol for non-routine ongoing management of the Piku.co Instance of this Distribution Reward Primitive.","contentHash":"bc463d05c8a6ff88e81eec6e4abd8d9b44d5b6e90ca70892a5ec95d221fd2b55","addressRefs":[]},"316c7704-f588-430a-bc71-6a0730810e54":{"id":"316c7704-f588-430a-bc71-6a0730810e54","doc_no":"A.6.1.1.4.2.5.1.4.4.3.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8396,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Piku.co Instance of this Distribution Reward Primitive.","contentHash":"06ea8baaebcf9602e032c8c7bef91c779c29e0fbeb9920ffc66d88d7e903af49","addressRefs":[]},"07bcf5db-08bd-4091-9416-38e2561e992b":{"id":"07bcf5db-08bd-4091-9416-38e2561e992b","doc_no":"A.6.1.1.4.2.5.1.4.4.4","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8397,"content":"The documents herein contain data relevant to the Piku.co Instance of the Distribution Reward Primitive.","contentHash":"2b9c29ec2be31982122f16644a222904820fa183cfcda0a2318e21dcbb7e2aba","addressRefs":[]},"3fa947ef-d8e4-4315-bccb-b4a1b6e760ca":{"id":"3fa947ef-d8e4-4315-bccb-b4a1b6e760ca","doc_no":"A.6.1.1.4.2.5.1.4.4.4.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8398,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"8dd619da-bb48-4efc-8a68-c21754a11372":{"id":"8dd619da-bb48-4efc-8a68-c21754a11372","doc_no":"A.6.1.1.4.2.5.1.4.4.4.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8399,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"7ccfd0ad-4d2c-441f-afbf-dd6f7b5d4293":{"id":"7ccfd0ad-4d2c-441f-afbf-dd6f7b5d4293","doc_no":"A.6.1.1.4.2.5.1.4.4.4.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8400,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"a1f69b33-8bd2-4c68-b4d5-6b8d34ed763e":{"id":"a1f69b33-8bd2-4c68-b4d5-6b8d34ed763e","doc_no":"A.6.1.1.4.2.5.1.4.4.4.4","title":"Distribution Reward Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8401,"content":"The Distribution Reward payments for the Piku.co Instance of the Distribution Reward Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"3c27eebc4403f2c16f564f39b36aba51e3e746f89d46fd23d49760b1f57a7e40","addressRefs":[]},"e05bf544-6a9c-42f5-9135-01a41887a75f":{"id":"e05bf544-6a9c-42f5-9135-01a41887a75f","doc_no":"A.6.1.1.4.2.5.1.4.4.4.4.0.6.1","title":"List Of Distribution Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8402,"content":"The Distribution Reward Payments are:","contentHash":"40025d715ec61de440d461cf5507125e9f533fda357a704d46b56203006c98f3","addressRefs":[]},"55ab7dfa-57e5-49d2-9dc3-05b0bfe14d04":{"id":"55ab7dfa-57e5-49d2-9dc3-05b0bfe14d04","doc_no":"A.6.1.1.4.2.5.1.4.4.4.5","title":"Third Party Partner Payment Addresses And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8403,"content":"This Document records information pertaining to Skybase's payments to the Third Party Partner associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5742222919fd5bfc6d755fdd495cd3c6e19e2b02557948c3583301c95fb8920d","addressRefs":[]},"e0517981-c05e-4f31-b8e0-51a690853132":{"id":"e0517981-c05e-4f31-b8e0-51a690853132","doc_no":"A.6.1.1.4.2.5.1.4.4.4.5.0.6.1","title":"Payment Details Per Reward Period","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8404,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"63b04949cca4b480ddde6a7b548a701868fda7e9712a6241685cf852b47870a7","addressRefs":[]},"49aa9d18-aa7e-464d-a965-f56fd014c02f":{"id":"49aa9d18-aa7e-464d-a965-f56fd014c02f","doc_no":"A.6.1.1.4.2.5.1.4.4.4.5.0.6.2","title":"Third Party Partner Payment Addresses","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8405,"content":"The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact.","contentHash":"19f1d83f9602009a3889539a14d01432ce98b63d21824bf920a8a696a26ab4ee","addressRefs":[]},"460cd7ec-5947-4f16-bc6e-de5db7c7a139":{"id":"460cd7ec-5947-4f16-bc6e-de5db7c7a139","doc_no":"A.6.1.1.4.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8406,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"510e1d086d8b26b127014faff646f6bd0dce80a13018e34938ff3c817e95f734","addressRefs":[]},"4d0912c0-d103-43b2-a6bd-c764b83436ec":{"id":"4d0912c0-d103-43b2-a6bd-c764b83436ec","doc_no":"A.6.1.1.4.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8407,"content":"The documents herein organize all base information relevant to Skybase's usage of the Integration Boost Primitive.","contentHash":"db456b2b4e88d260120224e3a60aceaacab7f37708dd2f0db7ff8b751b6babdf","addressRefs":[]},"e5199f4b-1c36-45c6-b555-51221ea2d09d":{"id":"e5199f4b-1c36-45c6-b555-51221ea2d09d","doc_no":"A.6.1.1.4.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8408,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"5c4c9ad3-b437-463c-8a2d-c87be9da1a0b":{"id":"5c4c9ad3-b437-463c-8a2d-c87be9da1a0b","doc_no":"A.6.1.1.4.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8409,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"3a05c10f-9e73-4599-91ae-ed0d48fa9fc6":{"id":"3a05c10f-9e73-4599-91ae-ed0d48fa9fc6","doc_no":"A.6.1.1.4.2.5.2.1.2.1","title":"Euler Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8410,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.2.2.1 - Euler Instance Configuration Document](af548686-1935-4f20-b099-0d5238f388a6).","contentHash":"a02760780fa74c74a9c78b0cdf188fda24a673bec0a7a7016cbe5cb1ec4e8201","addressRefs":[]},"46aa3d84-5bf6-4cfd-8b5c-ecbddd086984":{"id":"46aa3d84-5bf6-4cfd-8b5c-ecbddd086984","doc_no":"A.6.1.1.4.2.5.2.1.2.2","title":"Curve Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8411,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.2.2.2 - Curve Instance Configuration Document](f628b743-4df7-4814-9684-4707250a7284).","contentHash":"cd8d22a531bf5cb17521560c2b6221b12749f04785f4c1548d12b2dfd57f328d","addressRefs":[]},"a050d87d-8918-4bf7-a0ae-0314d7e85b42":{"id":"a050d87d-8918-4bf7-a0ae-0314d7e85b42","doc_no":"A.6.1.1.4.2.5.2.1.2.3","title":"Morpho Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8412,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.2.2.3 Morpho Instance Configuration Document](c18c7746-de43-492b-82f6-6735effa6508).","contentHash":"05471a19ef5a95cb2b93b994fc7e459ab5d8b22969f4db52e6ed37a12bbe68b1","addressRefs":[]},"d9541cd3-07a3-41c7-99ee-c486d4271567":{"id":"d9541cd3-07a3-41c7-99ee-c486d4271567","doc_no":"A.6.1.1.4.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8413,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"2a9c16c1-c8e4-40eb-96a0-f908ee506a8c":{"id":"2a9c16c1-c8e4-40eb-96a0-f908ee506a8c","doc_no":"A.6.1.1.4.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8414,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.5.2.1.2 - Active Instances Directory](5c4c9ad3-b437-463c-8a2d-c87be9da1a0b), whereas failed Invocations are Archived in [A.6.1.1.4.2.5.2.1.5 - Hub Data Repository](eea53dfc-ac8a-456b-8775-c9a80052670b).","contentHash":"677a067b34cf850c3e74b996ecd8bb624a1efe9c636aca7ea01fd35167be8dda","addressRefs":[]},"a0d67712-7f2e-4b40-9b07-d3e8173dbb9b":{"id":"a0d67712-7f2e-4b40-9b07-d3e8173dbb9b","doc_no":"A.6.1.1.4.2.5.2.1.4.1","title":"Compound","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8415,"content":"The Invocation Status and Instance Configuration Document location of this prospective Instance are specified below:\n\nInvocation Status: `Planning`\n\nInstance Configuration Document Location: [A.6.1.1.4.2.5.2.4.1 - Compound Instance Configuration Document](0f02f958-70e7-477c-9ad4-386ad01cb2f4).","contentHash":"73bdc46564522885dce8950dc2c452be36ef0874c863b63599c41147ab4c0a55","addressRefs":[]},"eea53dfc-ac8a-456b-8775-c9a80052670b":{"id":"eea53dfc-ac8a-456b-8775-c9a80052670b","doc_no":"A.6.1.1.4.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8416,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"38990d57-558c-4efd-95c8-846190693dce":{"id":"38990d57-558c-4efd-95c8-846190693dce","doc_no":"A.6.1.1.4.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8417,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"df61a722-0030-4edd-9bec-5be8af796083":{"id":"df61a722-0030-4edd-9bec-5be8af796083","doc_no":"A.6.1.1.4.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8418,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"24c1bfcf-3525-4ba8-86d8-266435c603f0":{"id":"24c1bfcf-3525-4ba8-86d8-266435c603f0","doc_no":"A.6.1.1.4.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8419,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"29a952d3-7b87-4aa1-b30f-aed5ed3ff3bd":{"id":"29a952d3-7b87-4aa1-b30f-aed5ed3ff3bd","doc_no":"A.6.1.1.4.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8420,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"af548686-1935-4f20-b099-0d5238f388a6":{"id":"af548686-1935-4f20-b099-0d5238f388a6","doc_no":"A.6.1.1.4.2.5.2.2.1","title":"Euler Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8421,"content":"The documents herein contain the Instance Configuration Document for the Euler Integration Boost Primitive Instance.","contentHash":"2befe2e2a0cd45a6f9bf5941c1e1cc068507d615ce3a000b1911823d609dcbb3","addressRefs":[]},"a0d70867-be02-4ef6-89c2-40cf796b6696":{"id":"a0d70867-be02-4ef6-89c2-40cf796b6696","doc_no":"A.6.1.1.4.2.5.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8422,"content":"The documents herein define the parameters of the Euler Instance of the Integration Boost Primitive.","contentHash":"f7a927b4eeab84fb71dfef97c1ad63f6354a885cdd3edbf11548e668c383dab9","addressRefs":[]},"fc909b71-8944-425f-aba8-6a5c05eb84cd":{"id":"fc909b71-8944-425f-aba8-6a5c05eb84cd","doc_no":"A.6.1.1.4.2.5.2.2.1.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8423,"content":"The partner for the Euler Integration Boost is Euler.","contentHash":"d2e120501ce54f386af6533c4aea09efcf6a26f7b7faf54bc98e8308389ed64d","addressRefs":[]},"f052604f-63f5-46ce-8fab-606122e66122":{"id":"f052604f-63f5-46ce-8fab-606122e66122","doc_no":"A.6.1.1.4.2.5.2.2.1.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8424,"content":"The reward address for the Euler Integration Boost is `0x33C71422B3E20ef2472Bc9aa9252220CAeAF207e` on Base.","contentHash":"8eac9bcca90aeb4b06dd058d0557337ad7e96fd5324e7df9d089470033d6cc18","addressRefs":["0x33c71422b3e20ef2472bc9aa9252220caeaf207e"]},"6f530a97-134f-498f-a662-dd54baef5376":{"id":"6f530a97-134f-498f-a662-dd54baef5376","doc_no":"A.6.1.1.4.2.5.2.2.1.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8425,"content":"The Euler Integration Boost is on Base blockchain.","contentHash":"a1636a9e646d6bf642c0c7bffdcb13b8166dafb69914508e4a4906c015763421","addressRefs":[]},"05c3cbb8-2f47-4dac-9b42-307d0313ad58":{"id":"05c3cbb8-2f47-4dac-9b42-307d0313ad58","doc_no":"A.6.1.1.4.2.5.2.2.1.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8426,"content":"The payment cadence for the Euler Integration Boost is weekly.","contentHash":"33f28dbf4539cae77f78306065ab60ebdc7af00783fda6c13abfcfe89496fe12","addressRefs":[]},"f82e8ec9-565c-4d5e-9121-c66086d4bb73":{"id":"f82e8ec9-565c-4d5e-9121-c66086d4bb73","doc_no":"A.6.1.1.4.2.5.2.2.1.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8427,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/incentivized-pools/](https://info-sky.blockanalitica.com/api/v1/incentivized-pools/).","contentHash":"339305c044beccbd3105f2f5089bc68091a1c763a69acbdd943bfe1ddeee6fa4","addressRefs":[]},"ff5a96bc-61f4-4be7-bacd-9a34dd59cbe8":{"id":"ff5a96bc-61f4-4be7-bacd-9a34dd59cbe8","doc_no":"A.6.1.1.4.2.5.2.2.1.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8428,"content":"The Data Submission Responsible Actor is Core Council Risk Advisor.","contentHash":"aa5f707481ca9ff5cb651a8a81dbbbfcf2574677d1b8b861c61a1d3944006e5f","addressRefs":[]},"cc7b38a2-0465-461b-a10d-484a5ad192b3":{"id":"cc7b38a2-0465-461b-a10d-484a5ad192b3","doc_no":"A.6.1.1.4.2.5.2.2.1.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8429,"content":"The Integration Boost is calculated based on per block values for USDS in Euler and the Sky Savings Rate.","contentHash":"480422d0b174dfb8fe84b2bd0557919b687d30cdb315078edb19d047f58a9039","addressRefs":[]},"0aee1540-84c6-415e-b297-bfa085b65188":{"id":"0aee1540-84c6-415e-b297-bfa085b65188","doc_no":"A.6.1.1.4.2.5.2.2.1.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8430,"content":"The documents herein define the custom parameters of the Euler Instance of the Integration Boost Primitive, if any.","contentHash":"3025561297161f60156003e4d1841da012c93b7abed2bb05ed042fa1b867f6e4","addressRefs":[]},"568b6e28-10dc-42aa-81cd-9bc7a6e17a57":{"id":"568b6e28-10dc-42aa-81cd-9bc7a6e17a57","doc_no":"A.6.1.1.4.2.5.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8431,"content":"The documents herein define the process for the ongoing management of the Euler Instance of the Integration Boost Primitive.","contentHash":"ff7fb10a4c0bbf1cd7efe494fad5a59ea01663b5bf51e1feaea51c192b57957e","addressRefs":[]},"6fe71ca8-3c28-408e-8b11-3c2fcfcc5778":{"id":"6fe71ca8-3c28-408e-8b11-3c2fcfcc5778","doc_no":"A.6.1.1.4.2.5.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8432,"content":"This document defines the protocol for routine ongoing management of the Euler Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"4b46654e4564f0c038835af7d277a42b88305c3ee510a9e807ff2fd9f077fe69","addressRefs":[]},"4f83666c-ef2e-4527-aeb7-79576b60b221":{"id":"4f83666c-ef2e-4527-aeb7-79576b60b221","doc_no":"A.6.1.1.4.2.5.2.2.1.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8433,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"fa57673c-3d0f-426a-b7c2-3954db4e3b8a":{"id":"fa57673c-3d0f-426a-b7c2-3954db4e3b8a","doc_no":"A.6.1.1.4.2.5.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8434,"content":"The documents herein define the protocol for non-routine ongoing management of the Euler Instance of this Integration Boost Primitive.","contentHash":"bbf5e1cdc984f8dff7c15b781b02623de968af72a330ead34bab06169764e899","addressRefs":[]},"07b055a7-cf21-4789-9890-bc3d937de558":{"id":"07b055a7-cf21-4789-9890-bc3d937de558","doc_no":"A.6.1.1.4.2.5.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8435,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Euler Instance of this Integration Boost Primitive.","contentHash":"cb80eb37acecd3292133b5ec7cc504f4a55b0381e3d90494cc75c8fc09ccd5ed","addressRefs":[]},"cb71b9fa-f990-41b1-8650-a37c16e0ef74":{"id":"cb71b9fa-f990-41b1-8650-a37c16e0ef74","doc_no":"A.6.1.1.4.2.5.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8436,"content":"The documents herein contain data relevant to the Euler Instance of the Integration Boost Primitive.","contentHash":"21a9a09ab31bcf57961b5a83c4a691f517c390143a829c26d5e4b0ab3db4b334","addressRefs":[]},"abc0866d-8e3f-4bad-879d-6f82cee2b028":{"id":"abc0866d-8e3f-4bad-879d-6f82cee2b028","doc_no":"A.6.1.1.4.2.5.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8437,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"ec81388d-8320-47c6-8e13-2dbd5ad95dbe":{"id":"ec81388d-8320-47c6-8e13-2dbd5ad95dbe","doc_no":"A.6.1.1.4.2.5.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8438,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"81cff123-b17c-4208-9348-fcf2aaf99c4b":{"id":"81cff123-b17c-4208-9348-fcf2aaf99c4b","doc_no":"A.6.1.1.4.2.5.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8439,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"1f3904b0-28b7-48e2-8cc7-ed67f4b90b68":{"id":"1f3904b0-28b7-48e2-8cc7-ed67f4b90b68","doc_no":"A.6.1.1.4.2.5.2.2.1.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8440,"content":"The Integration Boost payments for the Euler Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"ff0230336bbb0aea6ee2857461c8c37a5613779292ee9b6403ad8e9bc7ad0bed","addressRefs":[]},"358530ef-9012-4e7f-8dc4-192930c180d0":{"id":"358530ef-9012-4e7f-8dc4-192930c180d0","doc_no":"A.6.1.1.4.2.5.2.2.1.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8441,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"f628b743-4df7-4814-9684-4707250a7284":{"id":"f628b743-4df7-4814-9684-4707250a7284","doc_no":"A.6.1.1.4.2.5.2.2.2","title":"Curve Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8442,"content":"The documents herein contain the Instance Configuration Document for the Curve Integration Boost Primitive Instance.","contentHash":"ab0e02746d53d30f6dad07da5f868a8f9071cbfa39361d12b5df1f4c3c27f8fe","addressRefs":[]},"358e8a04-fb48-4597-abe6-58b955cd9f00":{"id":"358e8a04-fb48-4597-abe6-58b955cd9f00","doc_no":"A.6.1.1.4.2.5.2.2.2.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8443,"content":"The documents herein define the parameters of the Curve Instance of the Integration Boost Primitive.","contentHash":"0653f23eb31a6785b68cf00acb5c465c3018e945190b8dd6428f86d70985ec67","addressRefs":[]},"48ae657d-86c0-4254-8202-da1564cb347a":{"id":"48ae657d-86c0-4254-8202-da1564cb347a","doc_no":"A.6.1.1.4.2.5.2.2.2.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8444,"content":"The partner for the Curve Integration Boost is Curve.","contentHash":"2a7b512606acdd23de6a358eb31bdfa1a54e69941a24bc2723a796905d221c16","addressRefs":[]},"fa241343-8f00-454b-9b95-726cbcbb7b9d":{"id":"fa241343-8f00-454b-9b95-726cbcbb7b9d","doc_no":"A.6.1.1.4.2.5.2.2.2.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8445,"content":"The reward address for the Curve Integration Boost is `0xa7843f843d29ca33ba48d9d1335b774eecc328dc`.","contentHash":"e7f3507386600477a8d7d9325de6acdd0fde7b578eb2129c1bd6008f17be0a0e","addressRefs":["0xa7843f843d29ca33ba48d9d1335b774eecc328dc"]},"dd776d9a-7a0c-4b87-a5a5-6ae9e7ac829b":{"id":"dd776d9a-7a0c-4b87-a5a5-6ae9e7ac829b","doc_no":"A.6.1.1.4.2.5.2.2.2.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8446,"content":"The Curve Integration Boost is on Ethereum Mainnet blockchain.","contentHash":"13bc6ff96f21207eb608ddf05a34b2b1543f65c265b359f8f1e473f61e688981","addressRefs":[]},"4bbd6ba9-0f20-460b-968b-6b795c20ab4f":{"id":"4bbd6ba9-0f20-460b-968b-6b795c20ab4f","doc_no":"A.6.1.1.4.2.5.2.2.2.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8447,"content":"The payment cadence for the Curve Integration Boost is weekly.","contentHash":"eba89a78b5fd36ee9038b7ed7d1402c95b4bbcf79a08841a28bf46be10f95268","addressRefs":[]},"930022db-e936-4e10-8918-9badced679c0":{"id":"930022db-e936-4e10-8918-9badced679c0","doc_no":"A.6.1.1.4.2.5.2.2.2.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8448,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/incentivized-pools/](https://info-sky.blockanalitica.com/api/v1/incentivized-pools/).","contentHash":"339305c044beccbd3105f2f5089bc68091a1c763a69acbdd943bfe1ddeee6fa4","addressRefs":[]},"1371ca2e-38bc-4c5a-9983-06b2b960f2c9":{"id":"1371ca2e-38bc-4c5a-9983-06b2b960f2c9","doc_no":"A.6.1.1.4.2.5.2.2.2.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8449,"content":"The Data Submission Responsible Actor is Core Council Risk Advisor.","contentHash":"aa5f707481ca9ff5cb651a8a81dbbbfcf2574677d1b8b861c61a1d3944006e5f","addressRefs":[]},"ddc79c0b-b022-4696-88e4-e2b5d482193d":{"id":"ddc79c0b-b022-4696-88e4-e2b5d482193d","doc_no":"A.6.1.1.4.2.5.2.2.2.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8450,"content":"The Integration Boost is calculated based on per block values for USDS in Curve and the Sky Savings Rate.","contentHash":"a8f720a3f06675f16c609a39ec49a5b49f8821d116b5c301238f5eee672c5adc","addressRefs":[]},"eec6574a-8c01-4de9-8766-8185d6814a79":{"id":"eec6574a-8c01-4de9-8766-8185d6814a79","doc_no":"A.6.1.1.4.2.5.2.2.2.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8451,"content":"The documents herein define the custom parameters of the Curve Instance of the Integration Boost Primitive, if any.","contentHash":"11f21cef1d75bb18fe10af8cbbadde23e218e7954742749bf7f30f33575c46bc","addressRefs":[]},"73b0331d-ac57-4d24-9593-c579d64069f6":{"id":"73b0331d-ac57-4d24-9593-c579d64069f6","doc_no":"A.6.1.1.4.2.5.2.2.2.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8452,"content":"The documents herein define the process for the ongoing management of the Curve Instance of the Integration Boost Primitive.","contentHash":"40ad34f127d2323b927e3d8b7d57c15d4e47d61c62dadb1d262b67ad8a01fdfc","addressRefs":[]},"62d7f115-e6ed-4bce-8c84-abbbdcb8cb76":{"id":"62d7f115-e6ed-4bce-8c84-abbbdcb8cb76","doc_no":"A.6.1.1.4.2.5.2.2.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8453,"content":"This document defines the protocol for routine ongoing management of the Curve Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"194be7f795a9627f68cad2dc38274bfc0a0f504a8a7cc6e2c88614ce61c84431","addressRefs":[]},"c62e6889-1704-4258-aa32-69ef911dba25":{"id":"c62e6889-1704-4258-aa32-69ef911dba25","doc_no":"A.6.1.1.4.2.5.2.2.2.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8454,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"15a02312-d93d-4b6c-bf08-e23c6d7c36d9":{"id":"15a02312-d93d-4b6c-bf08-e23c6d7c36d9","doc_no":"A.6.1.1.4.2.5.2.2.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8455,"content":"The documents herein define the protocol for non-routine ongoing management of the Curve Instance of this Integration Boost Primitive.","contentHash":"1f7c57ab7367f4304318329e03d5f9e7a2fc926548982f65773b9f5f624b9d07","addressRefs":[]},"080d6d53-1fa3-41f2-a479-b2fab290c45e":{"id":"080d6d53-1fa3-41f2-a479-b2fab290c45e","doc_no":"A.6.1.1.4.2.5.2.2.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8456,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Curve Instance of this Integration Boost Primitive.","contentHash":"007228d615d64a78b93fbf311768fdd402bb4cc176291636c631ec6dc0e6c9de","addressRefs":[]},"cf22699e-1dc0-4526-9c07-fc5165ab3f75":{"id":"cf22699e-1dc0-4526-9c07-fc5165ab3f75","doc_no":"A.6.1.1.4.2.5.2.2.2.3","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8457,"content":"The documents herein contain data relevant to the Curve Instance of the Integration Boost Primitive.","contentHash":"8687ecde58577553b00e660173140dfe552f35aca43150c66fec93d9f9ec5807","addressRefs":[]},"00b3c481-bf1d-40a7-9fe8-aea7a99c0524":{"id":"00b3c481-bf1d-40a7-9fe8-aea7a99c0524","doc_no":"A.6.1.1.4.2.5.2.2.2.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8458,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"4cdcce5d-a4f5-4474-8818-72d13f6c6174":{"id":"4cdcce5d-a4f5-4474-8818-72d13f6c6174","doc_no":"A.6.1.1.4.2.5.2.2.2.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8459,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"4c26b560-c84a-4e2b-882f-8ea4b821886f":{"id":"4c26b560-c84a-4e2b-882f-8ea4b821886f","doc_no":"A.6.1.1.4.2.5.2.2.2.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8460,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"d2f2c0be-765d-4f3b-9dac-e39ab0244a85":{"id":"d2f2c0be-765d-4f3b-9dac-e39ab0244a85","doc_no":"A.6.1.1.4.2.5.2.2.2.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8461,"content":"The Integration Boost payments for the Curve Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"3e47eb78b46d155bfc7c65777e190db1a584678d8c146573e32c874a9dfc2edd","addressRefs":[]},"af376688-bb97-4fe1-bda9-58a59f735a69":{"id":"af376688-bb97-4fe1-bda9-58a59f735a69","doc_no":"A.6.1.1.4.2.5.2.2.2.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8462,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"c18c7746-de43-492b-82f6-6735effa6508":{"id":"c18c7746-de43-492b-82f6-6735effa6508","doc_no":"A.6.1.1.4.2.5.2.2.3","title":"Morpho Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8463,"content":"The documents herein contain the Instance Configuration Document for the Morpho Integration Boost Primitive Instance.","contentHash":"8ffd3c88c4d85df4816de8ca0f98a402ba771d2746c76127dfeda7cba29072ff","addressRefs":[]},"fda57199-87e2-4e4a-975a-35780fd324f3":{"id":"fda57199-87e2-4e4a-975a-35780fd324f3","doc_no":"A.6.1.1.4.2.5.2.2.3.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8464,"content":"The documents herein define the parameters of the Morpho Instance of the Integration Boost Primitive.","contentHash":"df648a3a9680e46a0be3afdfea59f3b7ecc6671060d0bba8340a404dadc80edc","addressRefs":[]},"460f1773-d543-4aad-81a3-ca4de567095b":{"id":"460f1773-d543-4aad-81a3-ca4de567095b","doc_no":"A.6.1.1.4.2.5.2.2.3.1.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8465,"content":"The partner for the Morpho Integration Boost is Morpho.","contentHash":"dda623f1bd5c68e6711da64e436c8edf00a0980793c2d0b376b4a15f1ee6c226","addressRefs":[]},"b70f1003-1159-4d5b-b362-c37aa11403d3":{"id":"b70f1003-1159-4d5b-b362-c37aa11403d3","doc_no":"A.6.1.1.4.2.5.2.2.3.1.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8466,"content":"The reward address for the Morpho Integration Boost is `0xa7843f843d29ca33ba48d9d1335b774eecc328dc`.","contentHash":"108055c6bb7bdb546079de3494f244d1dfc0c8e9a8300ec57c3d8aa190e42d06","addressRefs":["0xa7843f843d29ca33ba48d9d1335b774eecc328dc"]},"fbbbda2e-2eca-4b1f-90b1-9cd2f41015a0":{"id":"fbbbda2e-2eca-4b1f-90b1-9cd2f41015a0","doc_no":"A.6.1.1.4.2.5.2.2.3.1.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8467,"content":"The Morpho Integration Boost is on Ethereum Mainnet blockchain.","contentHash":"d3c3bd49eb144d0d01237e9cdeeabbb596b94f992ad2f92ec453b46cff928bc9","addressRefs":[]},"39dcdc06-4969-4bc3-a9f5-d3196ab1546f":{"id":"39dcdc06-4969-4bc3-a9f5-d3196ab1546f","doc_no":"A.6.1.1.4.2.5.2.2.3.1.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8468,"content":"The payment cadence for the Morpho Integration Boost is weekly.","contentHash":"e9e3eb51b73b1a4d71f4e563ec32e6c4ae241e6b443879ed7487a1f330c15d9f","addressRefs":[]},"a92af254-9677-4ae2-ab31-4785180ba959":{"id":"a92af254-9677-4ae2-ab31-4785180ba959","doc_no":"A.6.1.1.4.2.5.2.2.3.1.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8469,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/incentivized-pools/](https://info-sky.blockanalitica.com/api/v1/incentivized-pools/).","contentHash":"339305c044beccbd3105f2f5089bc68091a1c763a69acbdd943bfe1ddeee6fa4","addressRefs":[]},"d6f989ca-e897-499c-8ccf-1db864470ad0":{"id":"d6f989ca-e897-499c-8ccf-1db864470ad0","doc_no":"A.6.1.1.4.2.5.2.2.3.1.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8470,"content":"The Data Submission Responsible Actor is Core Council Risk Advisor.","contentHash":"aa5f707481ca9ff5cb651a8a81dbbbfcf2574677d1b8b861c61a1d3944006e5f","addressRefs":[]},"398179cc-7315-45ff-bfe3-e26cd761ef93":{"id":"398179cc-7315-45ff-bfe3-e26cd761ef93","doc_no":"A.6.1.1.4.2.5.2.2.3.1.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8471,"content":"The Integration Boost is calculated based on per block values for USDS in Morpho and the Sky Savings Rate.","contentHash":"0d44f7caf6460a4bffe7269702844e39cdee137e6fb4c9349ac31ce66b9a20a6","addressRefs":[]},"dec45734-5da8-4834-acd9-d905b7fb8934":{"id":"dec45734-5da8-4834-acd9-d905b7fb8934","doc_no":"A.6.1.1.4.2.5.2.2.3.1.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8472,"content":"The documents herein define the custom parameters of the Morpho Instance of the Integration Boost Primitive, if any.","contentHash":"5138f5ad7c096c2dd9326af0b1d897f7b4962febb4e3df813658e9da579398a9","addressRefs":[]},"6e1c68cd-4b68-40df-a9a1-2e729b3af35a":{"id":"6e1c68cd-4b68-40df-a9a1-2e729b3af35a","doc_no":"A.6.1.1.4.2.5.2.2.3.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8473,"content":"The documents herein define the process for the ongoing management of the Morpho Instance of the Integration Boost Primitive.","contentHash":"ebcb723ed0b3cf8540dca96929973d5154f2d5a15a368ef7a52297c9415b7465","addressRefs":[]},"c90ad783-129a-416d-a316-a56938a74147":{"id":"c90ad783-129a-416d-a316-a56938a74147","doc_no":"A.6.1.1.4.2.5.2.2.3.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8474,"content":"This document defines the protocol for routine ongoing management of the Morpho Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.2.2.1.3.2.1 - Near Term Process](4ab621b4-ef8e-4b01-a6aa-9296601033c5).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"a5d8830ad24b737b5cd9c386898dc20cdda4e1d62e74de50f69990f15c704d64","addressRefs":[]},"b16396c1-b9af-4840-ba2d-75761b39c7da":{"id":"b16396c1-b9af-4840-ba2d-75761b39c7da","doc_no":"A.6.1.1.4.2.5.2.2.3.2.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8475,"content":"The Prime Agent may define Instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"cfd91aa0c3222f95c38aaf5dbdb5b567c1bb892cf36616f645a83a6b8f3adcc9","addressRefs":[]},"20c4a428-1129-42c9-b03f-349418cc0767":{"id":"20c4a428-1129-42c9-b03f-349418cc0767","doc_no":"A.6.1.1.4.2.5.2.2.3.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8476,"content":"The documents herein define the protocol for non-routine ongoing management of the Morpho Instance of this Integration Boost Primitive.","contentHash":"7efcfd067520237b91d0ba7d7d439de229e5a27f4f3ea8a5517d07ad37c2b532","addressRefs":[]},"36da0ac3-eb57-43e9-a56c-832e2bd73b06":{"id":"36da0ac3-eb57-43e9-a56c-832e2bd73b06","doc_no":"A.6.1.1.4.2.5.2.2.3.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8477,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Morpho Instance of this Integration Boost Primitive.","contentHash":"82160780a339e0743e772aeb70f4d6020ec098be3d431ae74379bc9cf4ebac7a","addressRefs":[]},"88095904-1a04-449c-b421-3a3c7e4fa437":{"id":"88095904-1a04-449c-b421-3a3c7e4fa437","doc_no":"A.6.1.1.4.2.5.2.2.3.3","title":"Date Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8478,"content":"The documents herein contain data relevant to the Morpho Instance of the Integration Boost Primitive.","contentHash":"c8cbdd5a1ed591eed7ddaadc5e42f2b363276641bb72f6103d8c49c8a3bbd42f","addressRefs":[]},"ef86b5b0-48ce-471e-8a26-dd59dfa09449":{"id":"ef86b5b0-48ce-471e-8a26-dd59dfa09449","doc_no":"A.6.1.1.4.2.5.2.2.3.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8479,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"c1e28481-d41d-40b8-96d9-cd372e46b45d":{"id":"c1e28481-d41d-40b8-96d9-cd372e46b45d","doc_no":"A.6.1.1.4.2.5.2.2.3.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8480,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"1024c532-ea70-4d0f-b178-b99529950f25":{"id":"1024c532-ea70-4d0f-b178-b99529950f25","doc_no":"A.6.1.1.4.2.5.2.2.3.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8481,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"81ee6226-9067-4e72-bd0b-77773b581701":{"id":"81ee6226-9067-4e72-bd0b-77773b581701","doc_no":"A.6.1.1.4.2.5.2.2.3.3.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8482,"content":"The Integration Boost payments for the Morpho Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"3c674a10c75ccfd25d51fcf0e412743bd1e61ca6e65ca8dbc2afa269d30bd294","addressRefs":[]},"71d49eb8-0224-4fe7-831e-e49467e2f90d":{"id":"71d49eb8-0224-4fe7-831e-e49467e2f90d","doc_no":"A.6.1.1.4.2.5.2.2.3.3.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8483,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"1f90bc85-18f4-46d1-b13c-e49682361c3e":{"id":"1f90bc85-18f4-46d1-b13c-e49682361c3e","doc_no":"A.6.1.1.4.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8484,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"77018376-b8b2-4a4f-b9c9-e3fc6838be62":{"id":"77018376-b8b2-4a4f-b9c9-e3fc6838be62","doc_no":"A.6.1.1.4.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8485,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.5.2.2 - Active Instances](29a952d3-7b87-4aa1-b30f-aed5ed3ff3bd).","contentHash":"db9fcbd851b36178cb29879d244a187ef07ce8fccc52ad5b312d4b0ef71c6e5b","addressRefs":[]},"0f02f958-70e7-477c-9ad4-386ad01cb2f4":{"id":"0f02f958-70e7-477c-9ad4-386ad01cb2f4","doc_no":"A.6.1.1.4.2.5.2.4.1","title":"Compound Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8486,"content":"The documents herein contain the Instance Configuration Document for the Compound Integration Boost Primitive Instance.","contentHash":"4e744ea7f7cb9c52b9726c4fb9c3a6ed00be85ec9de9d3d17701b939979ebcef","addressRefs":[]},"12313a2b-f15e-47ef-84c1-a170dcb777db":{"id":"12313a2b-f15e-47ef-84c1-a170dcb777db","doc_no":"A.6.1.1.4.2.5.2.4.1.1","title":"Invocation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8487,"content":"`Planning`","contentHash":"186f9387deb4df9ad5dbf51656fbfea1a174909388c146bc0ccababda06922ac","addressRefs":[]},"8976aeab-15f0-44a3-8e94-145cc998be81":{"id":"8976aeab-15f0-44a3-8e94-145cc998be81","doc_no":"A.6.1.1.4.2.5.2.4.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8488,"content":"The documents herein define the parameters of the Compound Instance of the Integration Boost Primitive.","contentHash":"71906657b220642d5de9fae5f8cfaaf04caa1c13c4fcd4e09039cc59f8d1dc9a","addressRefs":[]},"31dc4b4c-075d-49ce-bb6a-dfccc5a4fceb":{"id":"31dc4b4c-075d-49ce-bb6a-dfccc5a4fceb","doc_no":"A.6.1.1.4.2.5.2.4.1.2.1","title":"Integration Partner Name","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8489,"content":"The partner for the Compound Integration Boost is Compound.","contentHash":"04125d1ee7d0feb239516bb0157220835ec8bebf59c535a83f7bf0da8a20ff65","addressRefs":[]},"8fa189a2-6b3f-4af7-9cb5-c24353732ebc":{"id":"8fa189a2-6b3f-4af7-9cb5-c24353732ebc","doc_no":"A.6.1.1.4.2.5.2.4.1.2.2","title":"Integration Partner Reward Address","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8490,"content":"The reward address for the Compound Integration Boost is `0xD66241b84dC4d6ccD4aA072A9da22b4B218FC1b0` on Base.","contentHash":"73db9bf54a5a97c642195ac92996055b324aae2941d2e9146a419d6c5f8f4af6","addressRefs":["0xd66241b84dc4d6ccd4aa072a9da22b4b218fc1b0"]},"4251b3fc-52fa-4c98-9c27-e596406efdfd":{"id":"4251b3fc-52fa-4c98-9c27-e596406efdfd","doc_no":"A.6.1.1.4.2.5.2.4.1.2.3","title":"Integration Partner Chain","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8491,"content":"The Compound Integration Boost is on Base blockchain.","contentHash":"7e851f3290dfbd54ab04f26681824eda10d691d9ea68644954f088a0d2f7469c","addressRefs":[]},"779345d7-e6fe-4363-afde-0b42384294be":{"id":"779345d7-e6fe-4363-afde-0b42384294be","doc_no":"A.6.1.1.4.2.5.2.4.1.2.4","title":"Integration Boost Cadence","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8492,"content":"The payment cadence for the Compound Integration Boost is weekly.","contentHash":"d84eeaced3c102f886e96757a8016a779536fbee4b7a97f93e4901c0144b0d91","addressRefs":[]},"1174bee1-fca4-403e-bfee-36704e00b3c2":{"id":"1174bee1-fca4-403e-bfee-36704e00b3c2","doc_no":"A.6.1.1.4.2.5.2.4.1.2.5","title":"Integration Boost Data Submission Format","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8493,"content":"The Data Submission Responsible Actor calculates the net deposits based on on-chain events and makes the data available through an API endpoint located at [https://info-sky.blockanalitica.com/api/v1/incentivized-pools/](https://info-sky.blockanalitica.com/api/v1/incentivized-pools/).","contentHash":"339305c044beccbd3105f2f5089bc68091a1c763a69acbdd943bfe1ddeee6fa4","addressRefs":[]},"45a70053-e0a3-4188-a40b-f6b64ffde9e6":{"id":"45a70053-e0a3-4188-a40b-f6b64ffde9e6","doc_no":"A.6.1.1.4.2.5.2.4.1.2.6","title":"Integration Boost Data Submission Responsible Actor","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8494,"content":"The Data Submission Responsible Actor is The Data Submission Responsible Actor is.","contentHash":"640fc81bcbee3b6d35c08597a9a703e61d6f17ffe6e42c4fa1119da1b92257ef","addressRefs":[]},"7f1d30e9-7eaf-45e1-89a5-603f239a11ff":{"id":"7f1d30e9-7eaf-45e1-89a5-603f239a11ff","doc_no":"A.6.1.1.4.2.5.2.4.1.2.7","title":"Integration Boost Savings Rate Adjustment Strategy","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8495,"content":"The Integration Boost is calculated based on per block values for USDS in Compound and the Sky Savings Rate.","contentHash":"b4bd13d6aeb18b2573aaf39eaa6bd9dc9c54636d4fea499d9776a88658306038","addressRefs":[]},"8b64b909-3db0-4c6e-afea-f822433509a7":{"id":"8b64b909-3db0-4c6e-afea-f822433509a7","doc_no":"A.6.1.1.4.2.5.2.4.1.2.8","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8496,"content":"The documents herein define the custom parameters of the Compound Instance of the Integration Boost Primitive, if any.","contentHash":"83563c858b3d54a220faa206dd19a90afc38d985c7518b166b1038eadf48f216","addressRefs":[]},"d6e0908f-7b85-4a0f-acac-233489f70164":{"id":"d6e0908f-7b85-4a0f-acac-233489f70164","doc_no":"A.6.1.1.4.2.5.2.4.1.3","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8497,"content":"The documents herein define the process for the ongoing management of the Compound Instance of the Integration Boost Primitive.","contentHash":"4654981e75c0de480333d66facf0066b7a03d1748173eb35a0b5b093d56e33d2","addressRefs":[]},"9ad35e12-7bd0-46c8-a753-4a341ab880a2":{"id":"9ad35e12-7bd0-46c8-a753-4a341ab880a2","doc_no":"A.6.1.1.4.2.5.2.4.1.3.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8498,"content":"This document defines the protocol for routine ongoing management of the Compound Instance. This Instance inherits the base class of operational logic defined in [A.2.2.8.1.2.4.1 - Routine Protocol](c2abdd22-fe0f-489e-b281-450e066db701), subject to the qualifications specified in [A.2.2.8.1.2.1.5.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2).\n\nModifications to the base operational logic automatically propagate to this Instance. In future iterations of the Skybase Artifact, a version of the full process definition customized to Skybase will be included herein.","contentHash":"781f38e760ba42b5343fe9fed81e4673e4bf268decf56ba3860a940f412badc5","addressRefs":[]},"f1e42734-b704-4067-bedb-684bca8a1773":{"id":"f1e42734-b704-4067-bedb-684bca8a1773","doc_no":"A.6.1.1.4.2.5.2.4.1.3.1.1","title":"Agent Customizations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8499,"content":"The Prime Agent may define instance-specific customization of the routine protocol to extend the baseline functionality defined in the Sky Core Atlas. This can include custom routines or processes layered on top of the inherited Sky Core logic. Any extensions must remain fully aligned with the requirements specified in the Sky Core Atlas. This document defines those customizations, if any.\n\n[No customization presently.]","contentHash":"127c13bed8d333aa7cbfe6c08163309727c0eccbe9cb8a9920c0f539d4e83414","addressRefs":[]},"3aab09cc-2cdb-4afa-82db-230aae80437d":{"id":"3aab09cc-2cdb-4afa-82db-230aae80437d","doc_no":"A.6.1.1.4.2.5.2.4.1.3.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8500,"content":"The documents herein define the protocol for non-routine ongoing management of the Compound Instance of this Integration Boost Primitive.","contentHash":"815e62cf478a5346fc6555f7180796407953819875c8744d501ad73a12a87046","addressRefs":[]},"22f14eff-37fd-4bc0-92c5-6d079ee8724b":{"id":"22f14eff-37fd-4bc0-92c5-6d079ee8724b","doc_no":"A.6.1.1.4.2.5.2.4.1.3.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8501,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Compound Instance of this Integration Boost Primitive.","contentHash":"5e8be81d6c345ad9407a0639416379f33d633269d004a3d2a0012464f5e90ade","addressRefs":[]},"ab31a239-9f46-491f-ab8c-b1954bbdb20f":{"id":"ab31a239-9f46-491f-ab8c-b1954bbdb20f","doc_no":"A.6.1.1.4.2.5.2.4.1.4","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8502,"content":"The documents herein contain data relevant to the Compound Instance of the Integration Boost Primitive.","contentHash":"09f90e9f8cdff578435241179f72b99710e7ccc5739f1818b0af8da139dd25d4","addressRefs":[]},"eecefb67-7692-48f7-9f5b-b4bfde253fac":{"id":"eecefb67-7692-48f7-9f5b-b4bfde253fac","doc_no":"A.6.1.1.4.2.5.2.4.1.4.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8503,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"28bf469c-af5c-4014-8947-035def7c4077":{"id":"28bf469c-af5c-4014-8947-035def7c4077","doc_no":"A.6.1.1.4.2.5.2.4.1.4.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8504,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"6543a665-e415-4b54-9c0b-5af10c14f5ce":{"id":"6543a665-e415-4b54-9c0b-5af10c14f5ce","doc_no":"A.6.1.1.4.2.5.2.4.1.4.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8505,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"55b46793-6543-4002-a1d7-9cc33ef46ab6":{"id":"55b46793-6543-4002-a1d7-9cc33ef46ab6","doc_no":"A.6.1.1.4.2.5.2.4.1.4.4","title":"Integration Boost Payments","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8506,"content":"The Integration Boost payments for the Compound Instance of the Integration Boost Primitive are defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for ‘Direct Edit’.","contentHash":"5b127b6a7c661fbe7c948e2495ea3c96004c573b1dfa0f54d875cd26a95dba5b","addressRefs":[]},"afe3fba8-14b9-47b7-bd71-20be58c47f29":{"id":"afe3fba8-14b9-47b7-bd71-20be58c47f29","doc_no":"A.6.1.1.4.2.5.2.4.1.4.4.0.6.1","title":"List Of Integration Boost Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8507,"content":"The Integration Boost Payments are:","contentHash":"6a154932cc183b96e951a4ce301c62bc4f51844406a9e848087cd8a39d4c80bd","addressRefs":[]},"d096b01c-84a2-44a5-9af6-8888a825e0d4":{"id":"d096b01c-84a2-44a5-9af6-8888a825e0d4","doc_no":"A.6.1.1.4.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8508,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"248e784f2f310e2c794b5e87cf1137d9c20fcf1fc4930c4f7cd52bc42f45dee9","addressRefs":[]},"a5890268-5a4c-4b8c-890a-6db09c71aced":{"id":"a5890268-5a4c-4b8c-890a-6db09c71aced","doc_no":"A.6.1.1.4.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8509,"content":"The documents herein organize all base information relevant to Skybase's usage of the Pioneer Chain Primitive.","contentHash":"9afdbd55d8813e7cb2a1aee0129e08f919d25e150a6585ec25f423ca85551592","addressRefs":[]},"91ae0bcc-bd80-4de1-bbd7-e875d150563a":{"id":"91ae0bcc-bd80-4de1-bbd7-e875d150563a","doc_no":"A.6.1.1.4.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8510,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"5aa36020-011e-457b-8605-95988a244606":{"id":"5aa36020-011e-457b-8605-95988a244606","doc_no":"A.6.1.1.4.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8511,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"f7c6c056-bbb0-4dae-9457-4bb4592966a7":{"id":"f7c6c056-bbb0-4dae-9457-4bb4592966a7","doc_no":"A.6.1.1.4.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8512,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"5dde47de-0f14-4cba-aae8-89c5f16a2303":{"id":"5dde47de-0f14-4cba-aae8-89c5f16a2303","doc_no":"A.6.1.1.4.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8513,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.5.3.1.2 - Active Instances Directory](5aa36020-011e-457b-8605-95988a244606), whereas failed Invocations are Archived in [A.6.1.1.4.2.5.3.1.5 - Hub Data Repository](352eb7b1-b4bf-405d-970c-d937ffb65ae3).","contentHash":"d3e97f2022a91b4b0bbd140b35d2436ce373c875cb00c615b0c2cd5e1ec0c5f2","addressRefs":[]},"352eb7b1-b4bf-405d-970c-d937ffb65ae3":{"id":"352eb7b1-b4bf-405d-970c-d937ffb65ae3","doc_no":"A.6.1.1.4.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8514,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"6808eba8-aea7-497f-9ca1-3fa360a6ad46":{"id":"6808eba8-aea7-497f-9ca1-3fa360a6ad46","doc_no":"A.6.1.1.4.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8515,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"c5a4fb59-8b70-42ef-a43d-c78d6bdb70b6":{"id":"c5a4fb59-8b70-42ef-a43d-c78d6bdb70b6","doc_no":"A.6.1.1.4.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8516,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"55bf90c4-007c-4cd8-8a37-60659a0404bb":{"id":"55bf90c4-007c-4cd8-8a37-60659a0404bb","doc_no":"A.6.1.1.4.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8517,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"204539dc-c8b2-46d2-a6c1-14552870b6e3":{"id":"204539dc-c8b2-46d2-a6c1-14552870b6e3","doc_no":"A.6.1.1.4.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8518,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"0e546189-6559-4d2b-b4d1-bdd86e2ab499":{"id":"0e546189-6559-4d2b-b4d1-bdd86e2ab499","doc_no":"A.6.1.1.4.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8519,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"6787cd76-9666-4fb4-9b2c-120ad771afb8":{"id":"6787cd76-9666-4fb4-9b2c-120ad771afb8","doc_no":"A.6.1.1.4.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8520,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.5.3.2 - Active Instances](204539dc-c8b2-46d2-a6c1-14552870b6e3).","contentHash":"2678b1c96d7bf2ef9017967b987c480f3981c483627de6064e54d414b2d4d525","addressRefs":[]},"b58a8d96-b6df-416e-b81f-2898d82924b4":{"id":"b58a8d96-b6df-416e-b81f-2898d82924b4","doc_no":"A.6.1.1.4.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8521,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Skybase. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"15d85e9edd62f60fe7013ef6e5c8f2bea7aff78ae869200c060d9e3af2c26d6a","addressRefs":[]},"24b63123-f30f-4dc3-aefa-74b4351c4baa":{"id":"24b63123-f30f-4dc3-aefa-74b4351c4baa","doc_no":"A.6.1.1.4.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8522,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Allocation System Primitive. See [A.2.2.9.1 - Allocation System Primitive](9db14ab7-bb4b-4751-8084-843bd4359f2a).","contentHash":"170c1f6e4f00129b8b68360b6fe25be93c22f2b3fcad8502f7feabc0e37168da","addressRefs":[]},"72950044-a7ba-44bf-9910-1e655bfbbb76":{"id":"72950044-a7ba-44bf-9910-1e655bfbbb76","doc_no":"A.6.1.1.4.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8523,"content":"The documents herein organize all base information relevant to Skybase's usage of the Allocation System Primitive.","contentHash":"41c0a36ea1af2d59863c1b02e2631e11687fd2b1dad886940a344c05476398cd","addressRefs":[]},"757a827f-c736-4ac5-8eaf-993567dee621":{"id":"757a827f-c736-4ac5-8eaf-993567dee621","doc_no":"A.6.1.1.4.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8524,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"05bc1cbc-57a1-462e-8618-b401636ac835":{"id":"05bc1cbc-57a1-462e-8618-b401636ac835","doc_no":"A.6.1.1.4.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8525,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"04c05a8f-cb70-4cb3-85e7-ceaa94c75c34":{"id":"04c05a8f-cb70-4cb3-85e7-ceaa94c75c34","doc_no":"A.6.1.1.4.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8526,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"b74ad51a-a372-4706-9084-d22c00318955":{"id":"b74ad51a-a372-4706-9084-d22c00318955","doc_no":"A.6.1.1.4.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8527,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.6.1.1.2 - Active Instances Directory](05bc1cbc-57a1-462e-8618-b401636ac835), whereas failed Invocations are Archived in [A.6.1.1.4.2.6.1.1.5 - Hub Data Repository](b5d982d8-9d61-480b-a6c0-a90b7bbc8221).","contentHash":"36f13e0d5dbde391109b1bc934e19d2ee44076d4a22bebfe5c4e1942de546972","addressRefs":[]},"b5d982d8-9d61-480b-a6c0-a90b7bbc8221":{"id":"b5d982d8-9d61-480b-a6c0-a90b7bbc8221","doc_no":"A.6.1.1.4.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8528,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"a8aa5d01-48ae-4ade-8a3c-ed42fb40a2b2":{"id":"a8aa5d01-48ae-4ade-8a3c-ed42fb40a2b2","doc_no":"A.6.1.1.4.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8529,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"21cab16e-58b3-4111-bdff-188d4cf8095e":{"id":"21cab16e-58b3-4111-bdff-188d4cf8095e","doc_no":"A.6.1.1.4.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8530,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"560787c2-e593-4d69-aba0-d1708fb92a1a":{"id":"560787c2-e593-4d69-aba0-d1708fb92a1a","doc_no":"A.6.1.1.4.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8531,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"fcfbc136-69fe-48aa-986e-b0cc5eea9590":{"id":"fcfbc136-69fe-48aa-986e-b0cc5eea9590","doc_no":"A.6.1.1.4.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8532,"content":"The documents herein specify the logic for coordinating multiple Instances of the Allocation System Primitive. In the future, additional logic will be added herein regarding how capital is allocated between different Instances of the Allocation System Primitive.","contentHash":"6324c508c5238b69764bd46d3e8ddef89e70ddd868d59807f87ac3230f72a081","addressRefs":[]},"d9c177ad-b1c8-4af7-a537-b6a36bf29dc4":{"id":"d9c177ad-b1c8-4af7-a537-b6a36bf29dc4","doc_no":"A.6.1.1.4.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8533,"content":"The Instances of the Allocation System Primitive with `Active` Status are stored herein.","contentHash":"1ec0e728a9f82ad97fb8eeaf6a1959350595219b9f7cf894e7fe0704248213a2","addressRefs":[]},"953249d4-609a-4e03-b069-bbbcd2d1c88e":{"id":"953249d4-609a-4e03-b069-bbbcd2d1c88e","doc_no":"A.6.1.1.4.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8534,"content":"The Instances of the Allocation System Primitive with `Completed` Status are stored herein.","contentHash":"5e8b303421b8ddbbe094a65ed1a012a162ef23442d0be75ad055b30f78fb3af7","addressRefs":[]},"c95c1adc-dd0a-4ddb-b992-3948f1e000c2":{"id":"c95c1adc-dd0a-4ddb-b992-3948f1e000c2","doc_no":"A.6.1.1.4.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8535,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.6.1.3 - Active Instances](d9c177ad-b1c8-4af7-a537-b6a36bf29dc4).","contentHash":"3098a6e2564ef39caad8182c057f4c6ffdef23fd48cee76a2e2857b9f20112d0","addressRefs":[]},"09144d1a-2cda-4805-b50d-b3da4f09d48b":{"id":"09144d1a-2cda-4805-b50d-b3da4f09d48b","doc_no":"A.6.1.1.4.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8536,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"978fd673dfb7be58a995b10d840c98ce1d9ca45c5abe3e4da5575515a611e9b0","addressRefs":[]},"16bf9c06-af9f-4853-bf8b-5246ada6e580":{"id":"16bf9c06-af9f-4853-bf8b-5246ada6e580","doc_no":"A.6.1.1.4.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8537,"content":"The documents herein organize all base information relevant to Skybase's usage of the Junior Risk Capital Rental Primitive.","contentHash":"ec514cdfc7ce0f62332fb7561ad17f5977832978e9579d773a6da1ad9dd4c9aa","addressRefs":[]},"84c95412-5704-480d-bf68-7dcffb78cf21":{"id":"84c95412-5704-480d-bf68-7dcffb78cf21","doc_no":"A.6.1.1.4.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8538,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"1c446878-ac5e-46a5-956c-346dfb288381":{"id":"1c446878-ac5e-46a5-956c-346dfb288381","doc_no":"A.6.1.1.4.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8539,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"30d04fa4-801d-468a-b7ea-2b0ffb54c18b":{"id":"30d04fa4-801d-468a-b7ea-2b0ffb54c18b","doc_no":"A.6.1.1.4.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8540,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"f0296ab8-bf0c-465a-955e-2566580cc810":{"id":"f0296ab8-bf0c-465a-955e-2566580cc810","doc_no":"A.6.1.1.4.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8541,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.6.2.1.2 - Active Instances Directory](1c446878-ac5e-46a5-956c-346dfb288381), whereas failed Invocations are Archived in [A.6.1.1.4.2.6.2.1.5 - Hub Data Repository](f3e94987-31d6-47c9-8809-fc90d1f401cd).","contentHash":"135038b0fb20da20bf9889cb4e1fb0c8f5c8adefcef5d8fc698671d21cbaf0e5","addressRefs":[]},"f3e94987-31d6-47c9-8809-fc90d1f401cd":{"id":"f3e94987-31d6-47c9-8809-fc90d1f401cd","doc_no":"A.6.1.1.4.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8542,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ebbef9e3-ab93-4a98-90d3-57663fac9134":{"id":"ebbef9e3-ab93-4a98-90d3-57663fac9134","doc_no":"A.6.1.1.4.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8543,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"7b34c64e-fda4-40d0-84cd-891c86e8de1c":{"id":"7b34c64e-fda4-40d0-84cd-891c86e8de1c","doc_no":"A.6.1.1.4.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8544,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"90c24d4a-39b0-40a3-af07-7cd353440b7e":{"id":"90c24d4a-39b0-40a3-af07-7cd353440b7e","doc_no":"A.6.1.1.4.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8545,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"44cbe0d7-fb84-4958-9bd7-29f931e09629":{"id":"44cbe0d7-fb84-4958-9bd7-29f931e09629","doc_no":"A.6.1.1.4.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8546,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"759df9b0-3bac-426e-b08d-3a5fb98d1cb9":{"id":"759df9b0-3bac-426e-b08d-3a5fb98d1cb9","doc_no":"A.6.1.1.4.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8547,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"08ab0db0-8a0f-45b5-8579-8c4984a69fd1":{"id":"08ab0db0-8a0f-45b5-8579-8c4984a69fd1","doc_no":"A.6.1.1.4.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8548,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.6.2.2 - Active Instances](44cbe0d7-fb84-4958-9bd7-29f931e09629).","contentHash":"e3b4f15b1575d608568fa8d459ecb02f58ee1b112acefcad73be87824061725d","addressRefs":[]},"c2f8c143-52a9-41a5-be4a-05c07ca64f6b":{"id":"c2f8c143-52a9-41a5-be4a-05c07ca64f6b","doc_no":"A.6.1.1.4.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8549,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"9ea7463bfee19efe39a13ad304437f8b14de3547a07bb427bc509549f7e16dd9","addressRefs":[]},"23300804-de11-4f5d-a28f-bc7995b36165":{"id":"23300804-de11-4f5d-a28f-bc7995b36165","doc_no":"A.6.1.1.4.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8550,"content":"The documents herein organize all base information relevant to Skybase's usage of the Asset Liability Management Rental Primitive.","contentHash":"a4a66813afa14251e3472107d0d0b732a6e652330dca5b49ecb41222f09005e9","addressRefs":[]},"d57f7f80-a04b-45be-a9e1-3ce55fdf7b03":{"id":"d57f7f80-a04b-45be-a9e1-3ce55fdf7b03","doc_no":"A.6.1.1.4.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8551,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"5a9f343e-4513-4ded-ab34-6f76690943d1":{"id":"5a9f343e-4513-4ded-ab34-6f76690943d1","doc_no":"A.6.1.1.4.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8552,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"b537b35c-d9a5-4c64-88ab-d2bc54793ecb":{"id":"b537b35c-d9a5-4c64-88ab-d2bc54793ecb","doc_no":"A.6.1.1.4.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8553,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"92a1b7cd-9f42-4238-b388-d09d2eab1b61":{"id":"92a1b7cd-9f42-4238-b388-d09d2eab1b61","doc_no":"A.6.1.1.4.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8554,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.6.3.1.2 - Active Instances Directory](5a9f343e-4513-4ded-ab34-6f76690943d1), whereas failed Invocations are Archived in [A.6.1.1.4.2.6.3.1.5 - Hub Data Repository](ca4d7aa2-daae-4806-aeb8-fa2ff48d5a1c).","contentHash":"fe9cafff1c918579fce6f3061e2962682f49e28356cb513d2736c0e1c8e44e55","addressRefs":[]},"ca4d7aa2-daae-4806-aeb8-fa2ff48d5a1c":{"id":"ca4d7aa2-daae-4806-aeb8-fa2ff48d5a1c","doc_no":"A.6.1.1.4.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8555,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"9916eb6a-e91a-4fcd-b7fe-09728e5d9229":{"id":"9916eb6a-e91a-4fcd-b7fe-09728e5d9229","doc_no":"A.6.1.1.4.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8556,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"402c4b86-0fdc-4234-b3c9-81436bdfb5ac":{"id":"402c4b86-0fdc-4234-b3c9-81436bdfb5ac","doc_no":"A.6.1.1.4.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8557,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"df448d70-9b59-41e9-b4a7-475c2ad37b8c":{"id":"df448d70-9b59-41e9-b4a7-475c2ad37b8c","doc_no":"A.6.1.1.4.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8558,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"afc7b951-c066-4a6e-8b54-cf706a75c09f":{"id":"afc7b951-c066-4a6e-8b54-cf706a75c09f","doc_no":"A.6.1.1.4.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8559,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"662e5da6-5275-4649-991a-1121f4f9773e":{"id":"662e5da6-5275-4649-991a-1121f4f9773e","doc_no":"A.6.1.1.4.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8560,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"2827ce37-f144-4111-8fd4-2908beeade5a":{"id":"2827ce37-f144-4111-8fd4-2908beeade5a","doc_no":"A.6.1.1.4.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8561,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.6.3.2 - Active Instances](afc7b951-c066-4a6e-8b54-cf706a75c09f).","contentHash":"5a2e456afc4254f1d98b0fecca1efaaee1f5fd65b09816ce7ab63c34b12ecb1f","addressRefs":[]},"095cc4f1-a097-4157-8e81-06031208c39f":{"id":"095cc4f1-a097-4157-8e81-06031208c39f","doc_no":"A.6.1.1.4.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8562,"content":"The documents herein implement the Core Governance Primitives for Skybase. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"dbfdc26ee4d59bb57a012cbe01fed745ee7c69ded82c90ab3231a7589d17ae7b","addressRefs":[]},"79b5a43d-1abe-4945-9f7d-7fa8a5ac182e":{"id":"79b5a43d-1abe-4945-9f7d-7fa8a5ac182e","doc_no":"A.6.1.1.4.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8563,"content":"The documents herein contain all data and specifications for Skybase's Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"c9c43b59ed221f0055f0d39a90f7518d459b09d87931eecba4681789042ae517","addressRefs":[]},"58a4cf93-5c1c-4fec-8c5b-2c1c6f167c72":{"id":"58a4cf93-5c1c-4fec-8c5b-2c1c6f167c72","doc_no":"A.6.1.1.4.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8564,"content":"The documents herein organize all base information relevant to Skybase's usage of the Core Governance Reward Primitive.","contentHash":"c8268976ea926f47ca6e55680256a286f4ddb2c1ec4fd8261f193c01a883daf8","addressRefs":[]},"3c76baaa-df7f-464e-80ed-6b48eefbea7f":{"id":"3c76baaa-df7f-464e-80ed-6b48eefbea7f","doc_no":"A.6.1.1.4.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8565,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"93f4f2d8-68ae-4b33-98a6-e9d9fa764cd0":{"id":"93f4f2d8-68ae-4b33-98a6-e9d9fa764cd0","doc_no":"A.6.1.1.4.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8566,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"07f7da42-c12c-4ee1-a45a-7cc342ef5ff2":{"id":"07f7da42-c12c-4ee1-a45a-7cc342ef5ff2","doc_no":"A.6.1.1.4.2.7.1.1.2.1","title":"Sky.money Frontend Instance Configuration Document Location","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8567,"content":"This Instance's associated Instance Configuration Document is located at [Sky.money Frontend Instance Configuration Document](33a977ad-77eb-45f6-850e-4d00eed8d049).","contentHash":"0f15439fffa2eecf55f48d0ecd91184f92cbe2fa09429ac9b79f7767b18f7ea6","addressRefs":[]},"ed1c95ef-c156-473d-9c9e-b78c84bc2feb":{"id":"ed1c95ef-c156-473d-9c9e-b78c84bc2feb","doc_no":"A.6.1.1.4.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8568,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"30c32b90-6471-49f7-ab7b-956ece318a8e":{"id":"30c32b90-6471-49f7-ab7b-956ece318a8e","doc_no":"A.6.1.1.4.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8569,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.4.2.7.1.1.2 - Active Instances Directory](93f4f2d8-68ae-4b33-98a6-e9d9fa764cd0), whereas failed Invocations are Archived in [A.6.1.1.4.2.7.1.1.5 - Hub Data Repository](766df1ab-660b-4066-982a-7e99c21c93ec).","contentHash":"c2de685adeb3ddc0d32d8f85660a97fa73e681e69058bae8c55a7985f747a973","addressRefs":[]},"766df1ab-660b-4066-982a-7e99c21c93ec":{"id":"766df1ab-660b-4066-982a-7e99c21c93ec","doc_no":"A.6.1.1.4.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8570,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"1afa6e50-af3a-4014-bd38-c53b4b1287e7":{"id":"1afa6e50-af3a-4014-bd38-c53b4b1287e7","doc_no":"A.6.1.1.4.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8571,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"3b9b1819-7645-4d38-9766-05d21d6403ad":{"id":"3b9b1819-7645-4d38-9766-05d21d6403ad","doc_no":"A.6.1.1.4.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8572,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"8cea9dc7-d1b5-4a26-89fb-675dc896bdb0":{"id":"8cea9dc7-d1b5-4a26-89fb-675dc896bdb0","doc_no":"A.6.1.1.4.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8573,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"2e2b5ba1-329c-4654-9628-5e5bc50da4d7":{"id":"2e2b5ba1-329c-4654-9628-5e5bc50da4d7","doc_no":"A.6.1.1.4.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8574,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"33a977ad-77eb-45f6-850e-4d00eed8d049":{"id":"33a977ad-77eb-45f6-850e-4d00eed8d049","doc_no":"A.6.1.1.4.2.7.1.2.1","title":"Sky.money Frontend Instance Configuration Document","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8575,"content":"The documents herein contain the Instance Configuration Document for the Sky.money Frontend Core Governance Reward Primitive Instance.","contentHash":"e3534d2b758ef00b180e296103a5883ba11c4b49cc08b2c37a428646413815cf","addressRefs":[]},"715c34a9-79fa-42ab-9e6b-f0f045544cc6":{"id":"715c34a9-79fa-42ab-9e6b-f0f045544cc6","doc_no":"A.6.1.1.4.2.7.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8576,"content":"The documents herein define the parameters of the Sky.money Frontend Instance of the Core Governance Reward Primitive.","contentHash":"3900cd4076bcb05c7909d69b2e6b64ab9f5fc896d6e1d66570ac696c7eaca02f","addressRefs":[]},"ecd6843d-d1a3-43d8-af2c-af5fc8d9045f":{"id":"ecd6843d-d1a3-43d8-af2c-af5fc8d9045f","doc_no":"A.6.1.1.4.2.7.1.2.1.1.1","title":"Reward Code","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8577,"content":"`1`.","contentHash":"c0e61d6e019a4af547bcb5cfe9498a230d228519d375eee6faca605446af7513","addressRefs":[]},"e7a6dd83-4b9f-41db-8506-dede902828ce":{"id":"e7a6dd83-4b9f-41db-8506-dede902828ce","doc_no":"A.6.1.1.4.2.7.1.2.1.1.2","title":"Tracking Methodology","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8578,"content":"This Instance uses the Tracking Methodology specified in [A.2.2.10.1.4.2.1 - Tracking Via Reward Codes](b16cb8a3-aea3-4fda-b904-eb782ea7a8e1).","contentHash":"d983b1216adcded84e18390cb3df7f22bbbb8de3d08b46b73b2ee39bd26a0000","addressRefs":[]},"228f89fd-a51e-413a-b42b-e117414891be":{"id":"228f89fd-a51e-413a-b42b-e117414891be","doc_no":"A.6.1.1.4.2.7.1.2.1.1.3","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8579,"content":"The documents herein define the custom parameters of the Sky.money Frontend Instance of the Core Governance Reward Primitive, if any.","contentHash":"f7a348a733eda9709d0b0d69c3014c2d8b5c58b2c340fcb3c9420500bad3132f","addressRefs":[]},"56de7bd0-062d-46f5-acca-6b4466d15777":{"id":"56de7bd0-062d-46f5-acca-6b4466d15777","doc_no":"A.6.1.1.4.2.7.1.2.1.1.3.1","title":"Integrator Recipient","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8580,"content":"The Integrator is Sky.money Frontend, which is controlled by Skybase. As such, no additional Integrator payment will be made.","contentHash":"e2a2ab076257f68baa5ea3b8da5bcc964ecd2d10facfac6e1470ceb53ce4aca5","addressRefs":[]},"3f0387c9-2a45-47f1-8f5e-1cdfa273f237":{"id":"3f0387c9-2a45-47f1-8f5e-1cdfa273f237","doc_no":"A.6.1.1.4.2.7.1.2.1.2","title":"Data Repository","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8581,"content":"The documents herein contain data relevant to the Sky.money Frontend Instance of the Core Governance Reward Primitive.","contentHash":"2d35b278a30879073505809f091764a035b39dff2887763a33c29ac05e65900d","addressRefs":[]},"3dc7cce4-1e15-43e4-907c-d4a074a3531a":{"id":"3dc7cce4-1e15-43e4-907c-d4a074a3531a","doc_no":"A.6.1.1.4.2.7.1.2.1.2.1","title":"Core Governance Reward Payments And Transaction Records","type":"Active Data Controller","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8582,"content":"This Document records information pertaining to payments received by Skybase for Governance Rewards associated with this Instance. This information is defined as Active Data.\n\nThe Active Data is updated as follows:\n\n- The Responsible Party is Operational GovOps.\n- The Update Process must follow the protocol for 'Direct Edit'.","contentHash":"9abc4950fc1874b4fab53f4e34a1bf85aa9f743d87c4a8175ab662ec5aacdcc0","addressRefs":[]},"adcc7123-ee48-48ae-be34-f6c94b5a973c":{"id":"adcc7123-ee48-48ae-be34-f6c94b5a973c","doc_no":"A.6.1.1.4.2.7.1.2.1.2.1.0.6.1","title":"List Of Core Governance Reward Payments","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8583,"content":"The payment details consist of a table where each entry represents a single payment. Each entry has the following fields:\n\n- Reward Period\n- Payee (Skybase)\n- Payment Address\n- Amount Paid\n- Transaction Hash\n- Transaction Date","contentHash":"a266954de4c7f2f554495e2471f5f91d39c1c68e7231cee65c4db40274ed0780","addressRefs":[]},"7d57bc04-a81b-4007-aa2e-8d78ba4ecc52":{"id":"7d57bc04-a81b-4007-aa2e-8d78ba4ecc52","doc_no":"A.6.1.1.4.2.7.1.2.1.2.1.0.6.2","title":"Governance Reward Payment Address","type":"Active Data","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8584,"content":"The Sky.money Frontend Governance Reward payment address is Skybase's SubProxy Account on Ethereum Mainnet: `0x08978E3700859E476201c1D7438B3427e3C81140`.","contentHash":"6bd605bb4a68ec3d28e72213335dd046fbb3986e8c3ffab3bef02f2fd6e89ebe","addressRefs":["0x08978e3700859e476201c1d7438b3427e3c81140"]},"81228652-c70b-42db-bed4-8fbe4c35695f":{"id":"81228652-c70b-42db-bed4-8fbe4c35695f","doc_no":"A.6.1.1.4.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8585,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"cd5aeba6-3ba5-4f8e-9246-18319f6986b3":{"id":"cd5aeba6-3ba5-4f8e-9246-18319f6986b3","doc_no":"A.6.1.1.4.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"614f046c-829b-4330-a462-adff2245b36d","order":8586,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.4.2.7.1.2 - Active Instances](2e2b5ba1-329c-4654-9628-5e5bc50da4d7).","contentHash":"67429f245f83a3ffdd5eadec11c823f37b7dd283e9eaf9392b5b910c5240218a","addressRefs":[]},"12153a95-5be4-4f5e-8d04-d3046ad9b7bc":{"id":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","doc_no":"A.6.1.1.4.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"c88439b5-f456-4e51-8825-42e0ba83546f","order":8587,"content":"The documents herein define Skybase's strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"dc2c89547de5e9d7b40de3ab1997c48cdf0240f29a86d40a16de3cd4e2300cdb","addressRefs":[]},"70804058-8a1b-45ee-bf21-b09a5daefdb9":{"id":"70804058-8a1b-45ee-bf21-b09a5daefdb9","doc_no":"A.6.1.1.4.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8588,"content":"The documents herein specify Skybase governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Skybase Artifact is specified in the Root Edit Primitive above at [A.6.1.1.4.2.2.2 - Root Edit Primitive](24517c43-dec9-44ec-bc03-e76671dc2e74).","contentHash":"e9de9a00366a98c69a1fd1f94c99a47bc7c683fe2b89911639e16a2e95c8e3ac","addressRefs":[]},"0d482d6a-f140-4798-bf9c-a0c6cb5a2aa5":{"id":"0d482d6a-f140-4798-bf9c-a0c6cb5a2aa5","doc_no":"A.6.1.1.4.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8589,"content":"Skybase uses the Sky Forum for governance-related discussion. Posts should use the \"Skybase Prime\" category.","contentHash":"511b1db075fedcf6fa9043a3ebc27bd629d4f1afa6d3a3eb9fbda49aae24319d","addressRefs":[]},"31f5b013-30a1-4135-8e04-4e9b7ee6a794":{"id":"31f5b013-30a1-4135-8e04-4e9b7ee6a794","doc_no":"A.6.1.1.4.3.1.2","title":"Discord","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8590,"content":"Skybase also uses Discord for more immediate communication. The Sky Discord is located at [https://t.co/v6zG0MZtak](https://t.co/v6zG0MZtak).","contentHash":"489bca6306029e5e5baefc44b788ca544634d6b467d9a791592fc6c77c38017a","addressRefs":[]},"dedeb7e0-af9d-41ef-aec2-cdfb8b3fc437":{"id":"dedeb7e0-af9d-41ef-aec2-cdfb8b3fc437","doc_no":"A.6.1.1.4.3.1.3","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8591,"content":"The documents herein specify Skybase's emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Skybase Artifact.","contentHash":"192eb91dbc536a54c1c19ae4dca363ec0f77261cb43fd95a3a0f1baf2b9b14ed","addressRefs":[]},"8a9aef44-d044-40e6-91f6-c810d27e9d5c":{"id":"8a9aef44-d044-40e6-91f6-c810d27e9d5c","doc_no":"A.6.1.1.4.3.1.4","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8592,"content":"The documents herein specify Skybase's emergency response protocol in situations solely impacting Skybase versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Skybase Artifact.","contentHash":"9a52d4ca9da632aebf7c2d0a10f2ce3a2617e89c03ad18e1aa02c3cf7e65ae14","addressRefs":[]},"8bc018e0-e343-424e-9089-6a813d168dff":{"id":"8bc018e0-e343-424e-9089-6a813d168dff","doc_no":"A.6.1.1.4.3.2","title":"Sky Primitives Strategy","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8593,"content":"The documents herein define Skybase's strategic intent with respect to certain Sky Primitives.","contentHash":"428fa47e57ba3631fd5d25a31bceafc50563ae9d72616db91ccb09246987c033","addressRefs":[]},"825f23f7-739b-4a76-8e23-540b11f1854c":{"id":"825f23f7-739b-4a76-8e23-540b11f1854c","doc_no":"A.6.1.1.4.3.2.1","title":"Distribution Reward Strategy","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8594,"content":"Skybase's strategy with respect to the Distribution Reward Primitive is to encourage the broad adoption of USDS by bridging into new communities and DeFi platforms, thereby earning and distributing Distribution Rewards for USDS balances facilitated through its frontend. Prospective partners should demonstrate strong alignment with Skybase's mission, and offer clear pathways to engage new user bases and support the sustainable growth of USDS across diverse ecosystems.\n\nThe guiding criteria are as follows:\n\n- **Shared Mission Alignment:** Partners must demonstrate a commitment to promoting user-friendly stablecoin usage and responsible financial empowerment.\n- **Clear Synergy:** The collaboration should enhance USDS accessibility, by offering either a unique distribution channel or a robust incentive model.\n- **Community Benefit**: Proposed partnerships should deliver tangible rewards or advantages that resonate with Sky’s user base.\n- **Scalability & Compliance:** Potential integrations should have the capacity to handle increased demand and adhere to the risk management guidelines described in the Atlas.","contentHash":"60088ab61cd05e71fb3dccda34931d776f501d23e46ab89c305c01b63c38c33c","addressRefs":[]},"8b587f01-c678-4f6d-ba37-a0765f5657b0":{"id":"8b587f01-c678-4f6d-ba37-a0765f5657b0","doc_no":"A.6.1.1.4.3.2.2","title":"Integration Boost Strategy","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8595,"content":"Skybase's strategy with respect to the Integration Boost Primitive is to deliver a \"Sky Savings Rate\" (or similar program) to USDS users across selected DeFi platforms. This approach aims to extend the reach of USDS by tapping into fresh communities and expanding its overall market presence. New collaborations should exhibit compatibility with Skybase's accessibility ethos, showcase steady on-chain activity, and present clear opportunities to onboard broader user segments into the Skybase ecosystem.\n\nThe guiding criteria are as follows:\n\n- **Long-Term Viability:** Target platforms must exhibit strong on-chain activity and a track record of stability.\n- **Aligned Incentives:** Collaborations should offer meaningful yield enhancements that support the broader Sky mission.\n- **Growth Potential:** Partners must show clear prospects for sustainable scaling, ensuring that users can benefit from ongoing improvements.","contentHash":"7c736e037a8e4cdc30d503a53fe22d08bd721f164b39ccb914527a7e6f90febb","addressRefs":[]},"276d8421-4f07-4ac5-812d-88909b5a9ecd":{"id":"276d8421-4f07-4ac5-812d-88909b5a9ecd","doc_no":"A.6.1.1.4.3.2.3","title":"Core Governance Reward Strategy","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8596,"content":"Skybase's strategy with respect to the Core Governance Reward Primitive is to provide continuous, secure, and user-friendly governance frontend hosting for SKY holders, ensuring critical decision-making processes remain accessible and reliable over time.\n\nThe guiding criteria are as follows:\n\n- **Security & Reliability:** The Prime Agent will uphold robust security measures and maintain high availability to prevent disruptions or unauthorized access.\n- **Governance Framework Alignment:** Any updates to the frontend should integrate smoothly with Skybase's existing governance mechanisms, preserving uninterrupted voting and proposal workflows.","contentHash":"c102d9aa63ed4c5d83685628fd8533f85dc4b0f525fac0f5a39751ec70e790d6","addressRefs":[]},"64dd4885-6d75-45c0-86a9-507bc9a55194":{"id":"64dd4885-6d75-45c0-86a9-507bc9a55194","doc_no":"A.6.1.1.4.3.3","title":"Ecosystem Accords","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8597,"content":"Skybase has formally agreed to the Ecosystem Accords herein.","contentHash":"c961dd9396e88c8df2e8475f768e62986310dc31ff7e2a596cf77cd2d302fafb","addressRefs":[]},"b6196792-be39-47cb-9742-620159bf09c2":{"id":"b6196792-be39-47cb-9742-620159bf09c2","doc_no":"A.6.1.1.4.3.3.1","title":"Ecosystem Accord 7","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8598,"content":"Skybase engaged in terms of agreement with Sky in Ecosystem Accord 7, located in [A.2.8.2.7 - Ecosystem Accord 7: Sky And Skybase](8a74919c-d9c1-4d9a-9499-302201f96f9c).","contentHash":"14cbd889fdaf6a984af4bb695b49f141d1fbb577219d906ceff3509117b47a53","addressRefs":[]},"5e276fe6-1449-47ba-9a7d-cddd1d1a236f":{"id":"5e276fe6-1449-47ba-9a7d-cddd1d1a236f","doc_no":"A.6.1.1.4.3.4","title":"USDS Demand Subsidies","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8599,"content":"Skybase uses capital to provide Subsidies to incentivize strategic markets to promote USDS demand.","contentHash":"c76dae6dbbced0de780a421b39e5bc46a38c69b8155dcacd53dd9987b3313a4f","addressRefs":[]},"1d8d603f-33f8-47bb-8562-8eb5701a3aff":{"id":"1d8d603f-33f8-47bb-8562-8eb5701a3aff","doc_no":"A.6.1.1.4.3.4.1","title":"USDS Demand Subsidies Capital","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8600,"content":"The source of capital for Skybase's USDS Demand Subsidies is the Skybase Treasury. Skybase Treasury capital is transferred to the USDS Demand Subsidies Multisig for utilization.","contentHash":"50f8bd7f7ec5194e606c553a4d6fafbda2623a343771a2f0f456c271270d52e8","addressRefs":[]},"20ee784c-115a-40bb-ae74-d4b3726b0c1b":{"id":"20ee784c-115a-40bb-ae74-d4b3726b0c1b","doc_no":"A.6.1.1.4.3.4.2","title":"USDS Demand Subsidies Multisig","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8601,"content":"The USDS Demand Subsidies Multisig is controlled by two (2) signers from Operational GovOps Soter Labs and one (1) signer from Skybase Foundation.","contentHash":"e394ea1a45fd8a4fb138c2d147cf7d6cf8b5dfe5cb4ab7d0d0adc1b88190a406","addressRefs":[]},"615835d8-475b-48f6-9e0f-bcaf041a63ff":{"id":"615835d8-475b-48f6-9e0f-bcaf041a63ff","doc_no":"A.6.1.1.4.3.4.2.1","title":"Address","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8602,"content":"The USDS Demand Subsidies Multisig address on Ethereum Mainnet is `0x3f32bc09d41ee699844f8296e806417d6bf61bba`.","contentHash":"1c372dacd97457de099d3e715413e5fa636535b6cfedc2168294353ef2e0547c","addressRefs":["0x3f32bc09d41ee699844f8296e806417d6bf61bba"]},"740a4a39-f560-437a-962c-4255384298a1":{"id":"740a4a39-f560-437a-962c-4255384298a1","doc_no":"A.6.1.1.4.3.4.2.2","title":"Required Number of Signers","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8603,"content":"The USDS Demand Subsidies Multisig currently has a 2/3 signing requirement.","contentHash":"10aa2eaa025f682fe04858905dbe923b3c033a9a0b59035e062f0ab5caae6e3f","addressRefs":[]},"dbb22ec2-97fc-47c1-85d3-9b1cc94d3ce0":{"id":"dbb22ec2-97fc-47c1-85d3-9b1cc94d3ce0","doc_no":"A.6.1.1.4.3.4.2.3","title":"Signers","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8604,"content":"The USDS Demand Subsidies Multisig has the following signers:\n\n- Soter Labs: 2 signers\n- Skybase Foundation: 1 signer","contentHash":"0338fc6b47dd504aa1ee968977ba47d03f1504f8380708920f45673e577e86f3","addressRefs":[]},"0d896655-0d03-4c73-b164-3f59668256dd":{"id":"0d896655-0d03-4c73-b164-3f59668256dd","doc_no":"A.6.1.1.4.3.4.2.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8605,"content":"The signers must use the USDS Demand Subsidies Multisig to disburse funds on behalf of Skybase to fund strategic USDS demand incentive opportunities.","contentHash":"b607f75e4eaec6dd168d373c9bb42b550bd5c8815e07b53f70cd27e713838a9d","addressRefs":[]},"665ca5c5-ca1b-471a-9a10-16c46ee10cfd":{"id":"665ca5c5-ca1b-471a-9a10-16c46ee10cfd","doc_no":"A.6.1.1.4.3.4.2.5","title":"Modification","type":"Core","depth":6,"parentId":"12153a95-5be4-4f5e-8d04-d3046ad9b7bc","order":8606,"content":"Operational GovOps Soter Labs can change the signers of the USDS Demand Subsidies Multisig at any time, so long as there are at least two (2) signers from Soter Labs and one (1) signer from Skybase Foundation, and at least two-thirds of signers are required to execute transactions.","contentHash":"57c1094c3402eb06bbb0eb6333a87ce213d97eb7db00d6012b70e47f429ec318","addressRefs":[]},"f558e673-cbab-4696-8ca1-3af9b90fe5d4":{"id":"f558e673-cbab-4696-8ca1-3af9b90fe5d4","doc_no":"A.6.1.1.5","title":"Obex","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":8607,"content":"The documents herein specify all of the logic for Obex, including Obex’s strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"6949a8af190939cac50706e373d52f360c234dd55f72bb2e3e8e06b2c8ce48bd","addressRefs":[]},"e395a323-3c53-4154-a7e6-d54c363f56f2":{"id":"e395a323-3c53-4154-a7e6-d54c363f56f2","doc_no":"A.6.1.1.5.1","title":"Introduction","type":"Core","depth":5,"parentId":"f558e673-cbab-4696-8ca1-3af9b90fe5d4","order":8608,"content":"Obex is an 'incubator' Agent operationalizing a turnkey solution for the Sky Ecosystem's development and deployment of Prime and Halo Agents. This will give Agent founders a streamlined pathway to establish, build, operationalize, fundraise, and launch new Agents. The overall goal of the Obex Agent is to produce Agents for the Sky Ecosystem at scale, supporting cohorts of new Agent founders through leveraging rich content, workstreams and turnkey services for legal, risk, tech, and operational requirements.","contentHash":"e196a7a8d263a4f9fffc707c9fc351610df57335382087cfa0d0e65b74564691","addressRefs":[]},"de2892b7-087c-49ee-8b85-e3753987d38e":{"id":"de2892b7-087c-49ee-8b85-e3753987d38e","doc_no":"A.6.1.1.5.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"f558e673-cbab-4696-8ca1-3af9b90fe5d4","order":8609,"content":"The documents herein implement the Sky Primitives for Obex. See [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"f542856369b21ab5afa8df33dfc3089de43495c1d00fe0baa63eef3d887f34b2","addressRefs":[]},"d5354d3f-8281-49e2-9ff6-c36091afa18a":{"id":"d5354d3f-8281-49e2-9ff6-c36091afa18a","doc_no":"A.6.1.1.5.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8610,"content":"The documents herein implement the Genesis Primitives for Obex. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"7bab9a8520e96ba2f3f1bf0cef0eb1d06a9e1a7ae1e622116fc3ffff1ce557e6","addressRefs":[]},"de89dc5f-7351-4ea0-bc7b-4a6eb25d6a4d":{"id":"de89dc5f-7351-4ea0-bc7b-4a6eb25d6a4d","doc_no":"A.6.1.1.5.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8611,"content":"The documents herein contain all data and specifications for Obex's Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"d044e92ed8b5bd79485c181fc540882cf5435c7d26ad505f83c1f20fe229548c","addressRefs":[]},"38ef6c16-11fb-400f-ba72-88e7f50fc1e8":{"id":"38ef6c16-11fb-400f-ba72-88e7f50fc1e8","doc_no":"A.6.1.1.5.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8612,"content":"The documents herein organize all base information relevant to Obex's usage of the Agent Creation Primitive.","contentHash":"034e3f91023e382c888f4df16138b2086c15f29591a9b9c2cbd5b413048422df","addressRefs":[]},"d812fe0d-1128-4824-b0df-ea61ba23a624":{"id":"d812fe0d-1128-4824-b0df-ea61ba23a624","doc_no":"A.6.1.1.5.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8613,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"6229b346-ecd5-474a-bfd4-e22066a365f0":{"id":"6229b346-ecd5-474a-bfd4-e22066a365f0","doc_no":"A.6.1.1.5.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8614,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"7c3e364b-84e7-4b47-9b5a-54978a127f97":{"id":"7c3e364b-84e7-4b47-9b5a-54978a127f97","doc_no":"A.6.1.1.5.2.1.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8615,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"a1b0f1ed-1e3e-47ff-9690-afb6bfd22192":{"id":"a1b0f1ed-1e3e-47ff-9690-afb6bfd22192","doc_no":"A.6.1.1.5.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8616,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.1.1.3.1 - Single Instance Configuration Document](9d67690d-87df-4fcf-bac0-0b2bcf75bf12).","contentHash":"538fb7a0efe7d06a4766387890cf803dec2f49a2a44d2bd9b509cd7467e76854","addressRefs":[]},"c9952aea-58df-4a2e-a706-8f342a6d525c":{"id":"c9952aea-58df-4a2e-a706-8f342a6d525c","doc_no":"A.6.1.1.5.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8617,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"d8bb6ab7-07b3-4224-9612-5c10b1a4cab2":{"id":"d8bb6ab7-07b3-4224-9612-5c10b1a4cab2","doc_no":"A.6.1.1.5.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8618,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"2d301483-65e6-4501-828f-67012966cbae":{"id":"2d301483-65e6-4501-828f-67012966cbae","doc_no":"A.6.1.1.5.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8619,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"7c5074c6-0cf3-4f96-bd35-ecd14d4a8cf5":{"id":"7c5074c6-0cf3-4f96-bd35-ecd14d4a8cf5","doc_no":"A.6.1.1.5.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8620,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"637cb4d7-f5d1-4181-bd60-d54f8893a4bd":{"id":"637cb4d7-f5d1-4181-bd60-d54f8893a4bd","doc_no":"A.6.1.1.5.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8621,"content":"The subtrees for Instances of the Agent Creation Primitive with `Suspended` Status are stored here.","contentHash":"183d20b3c12bea99884c81ff611bff6d5be670766bb91a4f4ccf5339e0a26636","addressRefs":[]},"5f6b104e-2310-45d4-ba62-92d3a9a5ed0b":{"id":"5f6b104e-2310-45d4-ba62-92d3a9a5ed0b","doc_no":"A.6.1.1.5.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8622,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"31bafd0d-b417-4759-88af-7589f9a32518":{"id":"31bafd0d-b417-4759-88af-7589f9a32518","doc_no":"A.6.1.1.5.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8623,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"9d67690d-87df-4fcf-bac0-0b2bcf75bf12":{"id":"9d67690d-87df-4fcf-bac0-0b2bcf75bf12","doc_no":"A.6.1.1.5.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8624,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"151d3bb0-77bb-4aeb-8bcb-be120968400b":{"id":"151d3bb0-77bb-4aeb-8bcb-be120968400b","doc_no":"A.6.1.1.5.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8625,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"05cdc5d1-c73e-4ccd-abe0-dd0a58d0c65c":{"id":"05cdc5d1-c73e-4ccd-abe0-dd0a58d0c65c","doc_no":"A.6.1.1.5.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8626,"content":"The name of the Agent is Obex.","contentHash":"ba35b30d37492d5beb1a0063420893215c52a207f67ca6bf5313746fde8d839e","addressRefs":[]},"510817f8-7ce6-4b32-b598-186610760525":{"id":"510817f8-7ce6-4b32-b598-186610760525","doc_no":"A.6.1.1.5.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8627,"content":"The address of Obex’s SubProxy Account on the Ethereum Mainnet is `0x8be042581f581E3620e29F213EA8b94afA1C8071`.","contentHash":"dece9491c00486b89b79fa399de2886a477fa21b47fa0cbad7b69f3c752ad93f","addressRefs":["0x8be042581f581e3620e29f213ea8b94afa1c8071"]},"d77522ec-0987-474d-87b3-9377f107c9b6":{"id":"d77522ec-0987-474d-87b3-9377f107c9b6","doc_no":"A.6.1.1.5.2.1.1.3.1.1.3","title":"Genesis Account","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8628,"content":"The address of Obex’s Genesis Account will be specified in a future iteration of the Obex Artifact.","contentHash":"4319426c8b6738bb3eb1846479df5d94527f38e954a34d695adb47b9b6b29c9c","addressRefs":[]},"6b501d73-1151-46a1-9994-1e51d25729da":{"id":"6b501d73-1151-46a1-9994-1e51d25729da","doc_no":"A.6.1.1.5.2.1.1.3.1.1.4","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8629,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"57b0ac97-ddd8-424c-a407-6f6ab91a3806":{"id":"57b0ac97-ddd8-424c-a407-6f6ab91a3806","doc_no":"A.6.1.1.5.2.1.1.3.1.1.4.1","title":"Rubicon","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8630,"content":"Rubicon is the Prime Foundation associated with Obex. Its mandate is to support the development, growth, and adoption of Obex.","contentHash":"5b9cd08520073c2e3f889a726ab72dea06af1e9b7c03784183efdfe4a7f8842b","addressRefs":[]},"44a4e626-eb16-44cb-8502-9133c97c0773":{"id":"44a4e626-eb16-44cb-8502-9133c97c0773","doc_no":"A.6.1.1.5.2.1.1.3.1.1.4.2","title":"Treadstone","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8631,"content":"Treadstone is the development company that provides services to Rubicon.","contentHash":"3981d69ef4940fb38e6c191ababa917ac60b2dc0466566ac54be50c85e092847","addressRefs":[]},"8171b404-5ea7-47ed-869d-8bd94f6e9e86":{"id":"8171b404-5ea7-47ed-869d-8bd94f6e9e86","doc_no":"A.6.1.1.5.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8632,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"fab9e798-14f5-4105-8dec-1e49eacc2b36":{"id":"fab9e798-14f5-4105-8dec-1e49eacc2b36","doc_no":"A.6.1.1.5.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8633,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"a5498802-b2d9-46d2-9a2e-30e546ba6110":{"id":"a5498802-b2d9-46d2-9a2e-30e546ba6110","doc_no":"A.6.1.1.5.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8634,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"a09fca08-e196-49b1-99e2-21e5c01a59cb":{"id":"a09fca08-e196-49b1-99e2-21e5c01a59cb","doc_no":"A.6.1.1.5.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8635,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"2e5c5930-3805-47c2-8c11-b05b8c5bdddc":{"id":"2e5c5930-3805-47c2-8c11-b05b8c5bdddc","doc_no":"A.6.1.1.5.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8636,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"3731f5d8-ff05-4c80-9f3f-2b056b6b9b38":{"id":"3731f5d8-ff05-4c80-9f3f-2b056b6b9b38","doc_no":"A.6.1.1.5.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8637,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"5c7d376d-ebb0-4477-8d96-129d362e7799":{"id":"5c7d376d-ebb0-4477-8d96-129d362e7799","doc_no":"A.6.1.1.5.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8638,"content":"The documents herein contain all data and specifications for Obex's instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"17bcb84190e8e99868181f3f50482b530eb6db720a82b231ac4771a03c7aea7f","addressRefs":[]},"b9e7cf68-feff-4a8b-9126-bc44bf3e7283":{"id":"b9e7cf68-feff-4a8b-9126-bc44bf3e7283","doc_no":"A.6.1.1.5.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8639,"content":"The documents herein organize all base information relevant to Obex's usage of the Prime Transformation Primitive.","contentHash":"5550b75ce7b1217dd3c96c5f5e67f3782f9cf3fdc25081753f8e0b8209e64eb7","addressRefs":[]},"32f5e8a7-fdce-4e77-b032-4c1670ecb9da":{"id":"32f5e8a7-fdce-4e77-b032-4c1670ecb9da","doc_no":"A.6.1.1.5.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8640,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"e4e7adc0-7c85-464c-a60c-87dafb800e48":{"id":"e4e7adc0-7c85-464c-a60c-87dafb800e48","doc_no":"A.6.1.1.5.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8641,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"1ad29165-0b55-4b7d-a908-c8e097a9d053":{"id":"1ad29165-0b55-4b7d-a908-c8e097a9d053","doc_no":"A.6.1.1.5.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8642,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"b404798f-056d-4c57-b252-4b30d960b8e3":{"id":"b404798f-056d-4c57-b252-4b30d960b8e3","doc_no":"A.6.1.1.5.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8643,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.1.2.3.1 - Single Instance Configuration Document](2fd59b03-9278-4371-a3f1-fe9514ab322b).","contentHash":"a3670ba7b99b20d114f23e2177860b9dcd384506d8c835c1cdf2f6020b5a5453","addressRefs":[]},"79851842-32b3-4e42-bbbc-2e4240a7b875":{"id":"79851842-32b3-4e42-bbbc-2e4240a7b875","doc_no":"A.6.1.1.5.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8644,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"3e55f8cd-3aff-4f45-a213-bb59f869ab84":{"id":"3e55f8cd-3aff-4f45-a213-bb59f869ab84","doc_no":"A.6.1.1.5.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8645,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"175640b2-a33d-4a0a-af98-8aa895344eca":{"id":"175640b2-a33d-4a0a-af98-8aa895344eca","doc_no":"A.6.1.1.5.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8646,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"8a61c3ea-fe8d-41a5-ade2-e338754f0666":{"id":"8a61c3ea-fe8d-41a5-ade2-e338754f0666","doc_no":"A.6.1.1.5.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8647,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"6b3b64ef-26b1-45ee-8596-7c78c243f1ae":{"id":"6b3b64ef-26b1-45ee-8596-7c78c243f1ae","doc_no":"A.6.1.1.5.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8648,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"e54ec47c-4526-4cc2-9722-43ed3cee7768":{"id":"e54ec47c-4526-4cc2-9722-43ed3cee7768","doc_no":"A.6.1.1.5.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8649,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"1a8ffef1-7997-452c-9f58-6b8d9af23c04":{"id":"1a8ffef1-7997-452c-9f58-6b8d9af23c04","doc_no":"A.6.1.1.5.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8650,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"2fd59b03-9278-4371-a3f1-fe9514ab322b":{"id":"2fd59b03-9278-4371-a3f1-fe9514ab322b","doc_no":"A.6.1.1.5.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8651,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"ff8bd343-f602-4a9c-a5b6-2048496d4ec8":{"id":"ff8bd343-f602-4a9c-a5b6-2048496d4ec8","doc_no":"A.6.1.1.5.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8652,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"3275f4de-18d6-4fca-8023-d6f2e3fb4f01":{"id":"3275f4de-18d6-4fca-8023-d6f2e3fb4f01","doc_no":"A.6.1.1.5.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8653,"content":"Obex is a Prime Agent.","contentHash":"dee97d211420aaa189e75b5588363beadadf247e717b776e1ee8aebe586f1108","addressRefs":[]},"65c00572-3f2f-41fa-892d-e568ef1cf7ba":{"id":"65c00572-3f2f-41fa-892d-e568ef1cf7ba","doc_no":"A.6.1.1.5.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8654,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"91999490-cd47-4523-aa5b-f71216472a3c":{"id":"91999490-cd47-4523-aa5b-f71216472a3c","doc_no":"A.6.1.1.5.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8655,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"e70d36bc-8e5e-44b4-ab3b-492308ab7196":{"id":"e70d36bc-8e5e-44b4-ab3b-492308ab7196","doc_no":"A.6.1.1.5.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8656,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"c0cc5f1c-0cc5-44c8-bf92-d28b371e05b0":{"id":"c0cc5f1c-0cc5-44c8-bf92-d28b371e05b0","doc_no":"A.6.1.1.5.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8657,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"aa23e483-3205-4843-92c9-5906b244e662":{"id":"aa23e483-3205-4843-92c9-5906b244e662","doc_no":"A.6.1.1.5.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8658,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"9e54e190-a5f0-466e-945b-a9075fbc20b1":{"id":"9e54e190-a5f0-466e-945b-a9075fbc20b1","doc_no":"A.6.1.1.5.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8659,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"685248fb-8b9c-44d0-8ba3-ada4ada84e06":{"id":"685248fb-8b9c-44d0-8ba3-ada4ada84e06","doc_no":"A.6.1.1.5.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8660,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"ad55a2b2-7b47-401f-967e-f89e601e567c":{"id":"ad55a2b2-7b47-401f-967e-f89e601e567c","doc_no":"A.6.1.1.5.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8661,"content":"The documents herein contain all data and specifications for Obex's instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"6187219575a014af55e0109572f133054b9c34d5a960bfdd824de558c7dc50e1","addressRefs":[]},"7b3f85c4-e618-4071-b07f-5c771a3bc873":{"id":"7b3f85c4-e618-4071-b07f-5c771a3bc873","doc_no":"A.6.1.1.5.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8662,"content":"The documents herein organize all base information relevant to Obex's usage of the Executor Transformation Primitive.","contentHash":"5db73e5cf5a37d56eec44143144eb23565cf1b6f138dbcfeda78321579a845f3","addressRefs":[]},"7e92d813-a224-495a-b2c7-ad83304b977c":{"id":"7e92d813-a224-495a-b2c7-ad83304b977c","doc_no":"A.6.1.1.5.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8663,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"5f9f5d64-6e5b-466e-a4c0-a194ec24161f":{"id":"5f9f5d64-6e5b-466e-a4c0-a194ec24161f","doc_no":"A.6.1.1.5.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8664,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"8f2c269a-20d6-4d3c-82e8-1a98123d663b":{"id":"8f2c269a-20d6-4d3c-82e8-1a98123d663b","doc_no":"A.6.1.1.5.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8665,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"1a4b9edf-b153-4f7f-be3a-27a87ef58185":{"id":"1a4b9edf-b153-4f7f-be3a-27a87ef58185","doc_no":"A.6.1.1.5.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8666,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"15635343-8607-45d0-a675-e5486ca08c7b":{"id":"15635343-8607-45d0-a675-e5486ca08c7b","doc_no":"A.6.1.1.5.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8667,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"84461fee-fe8d-4008-8bb1-0e72f22e0921":{"id":"84461fee-fe8d-4008-8bb1-0e72f22e0921","doc_no":"A.6.1.1.5.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8668,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"5b36399c-c01b-445a-ad21-f4f057575621":{"id":"5b36399c-c01b-445a-ad21-f4f057575621","doc_no":"A.6.1.1.5.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8669,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"87d42440-89ee-4d33-8f3e-8a9cf56b0fc6":{"id":"87d42440-89ee-4d33-8f3e-8a9cf56b0fc6","doc_no":"A.6.1.1.5.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8670,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"697d6019-9769-49cb-8394-c74c9c2240f3":{"id":"697d6019-9769-49cb-8394-c74c9c2240f3","doc_no":"A.6.1.1.5.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8671,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"0dfb0a6f-af53-45d5-badb-0383c76f2515":{"id":"0dfb0a6f-af53-45d5-badb-0383c76f2515","doc_no":"A.6.1.1.5.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8672,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"7ee33331-fa25-4c43-b3e8-de3362118dea":{"id":"7ee33331-fa25-4c43-b3e8-de3362118dea","doc_no":"A.6.1.1.5.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8673,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"29c1a185-926e-42e0-a15c-1aad1dbe9068":{"id":"29c1a185-926e-42e0-a15c-1aad1dbe9068","doc_no":"A.6.1.1.5.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8674,"content":"The documents herein contain all data and specifications for Obex's Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"66b080011f2d7b2425d5f8e2a0f1e1102c713633ad84eb899e9eeb58745c0da7","addressRefs":[]},"ea5efaa6-992d-4e59-9ebb-4c027ee7aa87":{"id":"ea5efaa6-992d-4e59-9ebb-4c027ee7aa87","doc_no":"A.6.1.1.5.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8675,"content":"The documents herein organize all base information relevant to Obex's usage of the Agent Token Primitive.","contentHash":"c0bbe79e8ffccdb975ac39f7710757aa28b817c81d828ab699f8d7f39e0fe13b","addressRefs":[]},"0dbea81d-1a7b-4c83-8817-20ee5aa3e90b":{"id":"0dbea81d-1a7b-4c83-8817-20ee5aa3e90b","doc_no":"A.6.1.1.5.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8676,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"6a9df4c5-fe51-4bfa-b661-69e313df475c":{"id":"6a9df4c5-fe51-4bfa-b661-69e313df475c","doc_no":"A.6.1.1.5.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8677,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"ccaebb1f-f68d-4f07-89a0-a18afea052d4":{"id":"ccaebb1f-f68d-4f07-89a0-a18afea052d4","doc_no":"A.6.1.1.5.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8678,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.1.4.2.1 - Single Instance Configuration Document](81d78b70-e460-4588-8e37-d2cf7ec87d32).","contentHash":"4bf303fcc27f866f6f07c179b8e74c7160795dc7ae3fa0f699114b1f746caf27","addressRefs":[]},"7e49543e-ee1f-4a60-9b80-e290e961931d":{"id":"7e49543e-ee1f-4a60-9b80-e290e961931d","doc_no":"A.6.1.1.5.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8679,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"5d1fa3e0-cafc-4667-951e-0ea439d13a95":{"id":"5d1fa3e0-cafc-4667-951e-0ea439d13a95","doc_no":"A.6.1.1.5.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8680,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"70cf9e11-7eed-4eba-8ef1-47bd21974a5f":{"id":"70cf9e11-7eed-4eba-8ef1-47bd21974a5f","doc_no":"A.6.1.1.5.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8681,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"38877b86-ed6e-49fb-ae28-4c0b7f0df215":{"id":"38877b86-ed6e-49fb-ae28-4c0b7f0df215","doc_no":"A.6.1.1.5.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8682,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"c87625a9-a7f2-4302-8104-739664173433":{"id":"c87625a9-a7f2-4302-8104-739664173433","doc_no":"A.6.1.1.5.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8683,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"7b49d757-66c0-4a34-b715-729a64801fca":{"id":"7b49d757-66c0-4a34-b715-729a64801fca","doc_no":"A.6.1.1.5.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8684,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"df170b7f-303a-4029-8f10-7548dab07f8a":{"id":"df170b7f-303a-4029-8f10-7548dab07f8a","doc_no":"A.6.1.1.5.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8685,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"81d78b70-e460-4588-8e37-d2cf7ec87d32":{"id":"81d78b70-e460-4588-8e37-d2cf7ec87d32","doc_no":"A.6.1.1.5.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8686,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"dcca537a-8364-4306-8f54-0113652e187c":{"id":"dcca537a-8364-4306-8f54-0113652e187c","doc_no":"A.6.1.1.5.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8687,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"86cff886-c2dd-447b-b300-7f3ac0334624":{"id":"86cff886-c2dd-447b-b300-7f3ac0334624","doc_no":"A.6.1.1.5.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8688,"content":"The name of Obex's token is Obex.","contentHash":"2cee9f143d4826e9be1447595b3c485c48f7ab9f6a7ac2c42da5e8d9945aa952","addressRefs":[]},"65767abc-766f-43e0-88c1-12b9a1855868":{"id":"65767abc-766f-43e0-88c1-12b9a1855868","doc_no":"A.6.1.1.5.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8689,"content":"The symbol of Obex's token is OBEX.","contentHash":"27803e6597b8ce3c5621d05afc123a025b81e7df0045ec13d5d47bd9f0554f03","addressRefs":[]},"19ad3fe9-9161-4ddd-af93-d3fc854d51ed":{"id":"19ad3fe9-9161-4ddd-af93-d3fc854d51ed","doc_no":"A.6.1.1.5.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8690,"content":"The Genesis Supply of OBEX is 10 billion.","contentHash":"c02669a6e343fdaa2e9f4ea9a000e0828c96601c7df94743caec1f6cef3ee615","addressRefs":[]},"a954b3b9-4230-448e-b926-e7daaad542c5":{"id":"a954b3b9-4230-448e-b926-e7daaad542c5","doc_no":"A.6.1.1.5.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8691,"content":"The address of OBEX will be specified in a future iteration of the Obex Artifact.","contentHash":"5ff966f98759ef9118ef6646e41e2118b0ff36d54a266cfe1b13da18e93afb80","addressRefs":[]},"2646a808-056e-4907-88bb-b504afe61946":{"id":"2646a808-056e-4907-88bb-b504afe61946","doc_no":"A.6.1.1.5.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8692,"content":"The token Admin will be specified in a future iteration of the Obex Artifact.","contentHash":"bb17644e778572a1daa267f50e62e5854db72564bd1bf894acc90e96528509a4","addressRefs":[]},"e687b86c-f6b8-4f2e-aabf-b7922b2d3f6d":{"id":"e687b86c-f6b8-4f2e-aabf-b7922b2d3f6d","doc_no":"A.6.1.1.5.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8693,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Obex Governance. Sky Governance retains the ability to revert where Obex is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"4057de7882f1b199cd6c8081e1db724c63a5de325752f3b79f8537e488a535ab","addressRefs":[]},"c40b84ff-e133-434a-bef9-e12aba5ac87c":{"id":"c40b84ff-e133-434a-bef9-e12aba5ac87c","doc_no":"A.6.1.1.5.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8694,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"1cd77356-66a5-449c-a573-71a44a628044":{"id":"1cd77356-66a5-449c-a573-71a44a628044","doc_no":"A.6.1.1.5.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8695,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.\n\n- These processes will be defined in a future iteration of the Obex Artifact.","contentHash":"e6b241efe99a2d07550addc08f1f56c6f22b4a8129c887674c9f8faa6b0e791b","addressRefs":[]},"596d5aa9-8116-44a0-aca7-e53b5181e62e":{"id":"596d5aa9-8116-44a0-aca7-e53b5181e62e","doc_no":"A.6.1.1.5.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8696,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"6fe2485a-225f-41e3-b791-0b98363df1e8":{"id":"6fe2485a-225f-41e3-b791-0b98363df1e8","doc_no":"A.6.1.1.5.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8697,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"44b64f9f-aa20-4aeb-b2e3-6abda1cfa77d":{"id":"44b64f9f-aa20-4aeb-b2e3-6abda1cfa77d","doc_no":"A.6.1.1.5.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8698,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"c6ec5fe6-691b-4ac7-a863-2be65a28ea3f":{"id":"c6ec5fe6-691b-4ac7-a863-2be65a28ea3f","doc_no":"A.6.1.1.5.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8699,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"c0ee9726-7ae8-4176-a3f3-01152a53f0d1":{"id":"c0ee9726-7ae8-4176-a3f3-01152a53f0d1","doc_no":"A.6.1.1.5.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8700,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"ec1f15fa-3059-4fd3-9467-7a796d7050a5":{"id":"ec1f15fa-3059-4fd3-9467-7a796d7050a5","doc_no":"A.6.1.1.5.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8701,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"91762197-a7e2-4e0c-bce5-4490f23f9667":{"id":"91762197-a7e2-4e0c-bce5-4490f23f9667","doc_no":"A.6.1.1.5.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8702,"content":"The documents herein implement the Operational Primitives for Obex. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"20ff99ace0f0e41aa99b4ea2585bb6fa49c1bbacd250d7564e1faf6d86b92080","addressRefs":[]},"e0baddbe-f261-4439-8fc0-e03b521c10ad":{"id":"e0baddbe-f261-4439-8fc0-e03b521c10ad","doc_no":"A.6.1.1.5.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8703,"content":"The documents herein contain all data and specifications for Obex's Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"032b3e321d2b7ba6e5a2f7318f1a96731fe33d1064fa5b4f1ac39e6eac1b9d0d","addressRefs":[]},"4f398e78-1f12-447d-bb28-71cfc4e9ce4c":{"id":"4f398e78-1f12-447d-bb28-71cfc4e9ce4c","doc_no":"A.6.1.1.5.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8704,"content":"The documents herein organize all base information relevant to Obex's usage of the Executor Accord Primitive.","contentHash":"839fc5784360159c39caa8ecb5eb613982d7aee98d3b9d14fde19e953e1aedaa","addressRefs":[]},"4bb8c2f6-b020-4f18-aa1e-9ac5962c6fac":{"id":"4bb8c2f6-b020-4f18-aa1e-9ac5962c6fac","doc_no":"A.6.1.1.5.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8705,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"5db0baf4-141b-4eb9-8d5b-bd5386e6786c":{"id":"5db0baf4-141b-4eb9-8d5b-bd5386e6786c","doc_no":"A.6.1.1.5.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8706,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"e08db2e2-b978-473f-be58-cf4a304bf15c":{"id":"e08db2e2-b978-473f-be58-cf4a304bf15c","doc_no":"A.6.1.1.5.2.2.1.1.2.1","title":"Ozone Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8707,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.2.1.2.1 - Ozone Instance Configuration Document](7634c378-486d-4d5b-823a-aee5c1c8b3a6).","contentHash":"26dabe5d3f97df7f7b2fd48bc4ed331321582a1c82a4d0d6b4eb1520b553b33e","addressRefs":[]},"0a0ddb4d-d708-4b2d-b9f2-1c7524fa2038":{"id":"0a0ddb4d-d708-4b2d-b9f2-1c7524fa2038","doc_no":"A.6.1.1.5.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8708,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"1310aa75-5080-4291-9de9-e4ce0cd7adcc":{"id":"1310aa75-5080-4291-9de9-e4ce0cd7adcc","doc_no":"A.6.1.1.5.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8709,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.2.1.1.2 - Active Instances Directory](5db0baf4-141b-4eb9-8d5b-bd5386e6786c), whereas failed Invocations are Archived in [A.6.1.1.5.2.2.1.1.5 - Hub Data Repository](6c78d193-aa70-45a1-b807-77dcba6b6543).","contentHash":"804cef7cc1202da4f8e6ebdcc801cb6569a39af83712a6a6b35d8e6a6c6c9e21","addressRefs":[]},"6c78d193-aa70-45a1-b807-77dcba6b6543":{"id":"6c78d193-aa70-45a1-b807-77dcba6b6543","doc_no":"A.6.1.1.5.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8710,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"8eb2aa7f-71ca-4c91-a0f9-5d433dcf22f3":{"id":"8eb2aa7f-71ca-4c91-a0f9-5d433dcf22f3","doc_no":"A.6.1.1.5.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8711,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"8e1fddae-22a6-4dc9-9e1b-78861747d2ca":{"id":"8e1fddae-22a6-4dc9-9e1b-78861747d2ca","doc_no":"A.6.1.1.5.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8712,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"4a6fc07c-c28c-499d-93c4-bd469e8b2012":{"id":"4a6fc07c-c28c-499d-93c4-bd469e8b2012","doc_no":"A.6.1.1.5.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8713,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"2fd90ea2-b604-4a06-8c73-888c08365dba":{"id":"2fd90ea2-b604-4a06-8c73-888c08365dba","doc_no":"A.6.1.1.5.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8714,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"7634c378-486d-4d5b-823a-aee5c1c8b3a6":{"id":"7634c378-486d-4d5b-823a-aee5c1c8b3a6","doc_no":"A.6.1.1.5.2.2.1.2.1","title":"Ozone Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8715,"content":"The documents herein contain the Instance Configuration Document for the Ozone Executor Accord Primitive Instance.","contentHash":"ca0caee12f20439eb72be855f0a3c3853fe737be1313cfe253dad38c7f8d0623","addressRefs":[]},"182988e8-96c8-4c3c-ab19-6b9b88b9532b":{"id":"182988e8-96c8-4c3c-ab19-6b9b88b9532b","doc_no":"A.6.1.1.5.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8716,"content":"The documents herein define the parameters of the Ozone Instance of the Executor Accord Primitive.","contentHash":"638cf31df48e28f4a38e5155a81f9cd4b27bb221ff40cc010386b96be05691e5","addressRefs":[]},"e3e97ee0-1ef7-48dd-acf0-3e1e6a6de47e":{"id":"e3e97ee0-1ef7-48dd-acf0-3e1e6a6de47e","doc_no":"A.6.1.1.5.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8717,"content":"The Operational Facilitator and Operational GovOps for Ozone are specified in [A.6.1.2.2 - Operational Executor Agent Ozone](565660dd-7850-4c3a-8dba-554542bf103a).","contentHash":"8ed0f1fb66d463549e15caa041123f9031ac10ad2f25d039e4bc6b7777f702a7","addressRefs":[]},"4b5e6287-583b-40c0-8ec4-87675a15f802":{"id":"4b5e6287-583b-40c0-8ec4-87675a15f802","doc_no":"A.6.1.1.5.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8718,"content":"The documents herein define the custom parameters of the Ozone Instance of the Executor Accord Primitive, if any.","contentHash":"be003f7a447f9026ea8e107c73c8b00f811e9d616575d90ced4c5ffb41a29c34","addressRefs":[]},"520a274c-6b18-4fb7-953a-8f562c5ca111":{"id":"520a274c-6b18-4fb7-953a-8f562c5ca111","doc_no":"A.6.1.1.5.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8719,"content":"The documents herein define the process for the ongoing management of the Ozone Instance of the Executor Accord Primitive.","contentHash":"03daa9d3ebfb53ae8a57e22ffb990501ed356259a7b153b51d2b35cb6013c74b","addressRefs":[]},"2a655bfa-fbcb-4888-b4df-0d0ec8398a14":{"id":"2a655bfa-fbcb-4888-b4df-0d0ec8398a14","doc_no":"A.6.1.1.5.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8720,"content":"The documents herein contain data relevant to the Ozone Instance of the Executor Accord Primitive.","contentHash":"edd3e28207fedf752584ef2eb5e88f52b3ff82d2d0a5d7cfed80703bd5ad5d72","addressRefs":[]},"b7eb3de8-9b56-4e2a-b0c0-5d3f8dddccb7":{"id":"b7eb3de8-9b56-4e2a-b0c0-5d3f8dddccb7","doc_no":"A.6.1.1.5.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8721,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0ab58c7d-7bb4-4d33-bd7a-2eca8e80b62a":{"id":"0ab58c7d-7bb4-4d33-bd7a-2eca8e80b62a","doc_no":"A.6.1.1.5.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8722,"content":"The materials associated with Operational GovOps review during the Invocation of this Instance are contained herein.","contentHash":"4d9cf82f10b4116dc01ad201efd474911d68cc99e9ef9477435cf5f1402ce280","addressRefs":[]},"248099c5-af01-490c-b248-4441accf889f":{"id":"248099c5-af01-490c-b248-4441accf889f","doc_no":"A.6.1.1.5.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8723,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"33eff493-0a21-4bb0-899e-f3fab9ef6f27":{"id":"33eff493-0a21-4bb0-899e-f3fab9ef6f27","doc_no":"A.6.1.1.5.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8724,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"dfca9a54-ab85-476a-ab49-345ec43a1294":{"id":"dfca9a54-ab85-476a-ab49-345ec43a1294","doc_no":"A.6.1.1.5.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8725,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.2.1.2 - Active Instances](2fd90ea2-b604-4a06-8c73-888c08365dba).","contentHash":"ace09fe8e13e7e151762e48c8cabcce6c7f4715fc2c6907f918c5ff82233060b","addressRefs":[]},"b69559bf-1acb-4f9c-8638-19fb8ef20fc2":{"id":"b69559bf-1acb-4f9c-8638-19fb8ef20fc2","doc_no":"A.6.1.1.5.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8726,"content":"The documents herein contain all data and specifications for Obex's Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"8070f14abdc7694c6bf90ccd02836d53c627c1aa04640805683da4ea4b627973","addressRefs":[]},"f6e6bc46-aa12-4a74-8433-85ffcfad4917":{"id":"f6e6bc46-aa12-4a74-8433-85ffcfad4917","doc_no":"A.6.1.1.5.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8727,"content":"The documents herein organize all base information relevant to Obex's usage of the Root Edit Primitive.","contentHash":"5b58b5d7df52633f4c860b028c5c194b9513efa61ae91639f86be2a79eaa5a67","addressRefs":[]},"363d6ab5-1065-4cb5-8326-506a7dc62db6":{"id":"363d6ab5-1065-4cb5-8326-506a7dc62db6","doc_no":"A.6.1.1.5.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8728,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"0a66c55d-66c6-4fae-819b-c1bce486a03e":{"id":"0a66c55d-66c6-4fae-819b-c1bce486a03e","doc_no":"A.6.1.1.5.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8729,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"48d674cd-633b-40b7-ab4f-9ff4028ea1e6":{"id":"48d674cd-633b-40b7-ab4f-9ff4028ea1e6","doc_no":"A.6.1.1.5.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8730,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.2.2.2.1 - Single Instance Configuration Document](f5cb7958-d3a3-4179-9541-8a603745a5f1).","contentHash":"8fed283b0de9b4c127f62b776aaa8de0735ee7e93a6d71c7bd33e004a387ee10","addressRefs":[]},"67ec15f0-3610-42e3-bbd4-1d35c5944aa6":{"id":"67ec15f0-3610-42e3-bbd4-1d35c5944aa6","doc_no":"A.6.1.1.5.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8731,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"155d502c-8c81-47dc-aaa5-0944a565cd8c":{"id":"155d502c-8c81-47dc-aaa5-0944a565cd8c","doc_no":"A.6.1.1.5.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8732,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"f5bcf120-3af4-4b17-b63c-1adcf745ce75":{"id":"f5bcf120-3af4-4b17-b63c-1adcf745ce75","doc_no":"A.6.1.1.5.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8733,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"988302bd-3993-4833-9611-456285591f89":{"id":"988302bd-3993-4833-9611-456285591f89","doc_no":"A.6.1.1.5.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8734,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"64ae8942-a1ac-4904-ba13-43ee7334551e":{"id":"64ae8942-a1ac-4904-ba13-43ee7334551e","doc_no":"A.6.1.1.5.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8735,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"75008710-7942-45ef-87ee-f342f0a571f4":{"id":"75008710-7942-45ef-87ee-f342f0a571f4","doc_no":"A.6.1.1.5.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8736,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"2bc00f12-93cd-4431-8d6c-6a1170ca474c":{"id":"2bc00f12-93cd-4431-8d6c-6a1170ca474c","doc_no":"A.6.1.1.5.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8737,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"f5cb7958-d3a3-4179-9541-8a603745a5f1":{"id":"f5cb7958-d3a3-4179-9541-8a603745a5f1","doc_no":"A.6.1.1.5.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8738,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"5034d53f-d21f-471b-a796-e62893aeab03":{"id":"5034d53f-d21f-471b-a796-e62893aeab03","doc_no":"A.6.1.1.5.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8739,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.5.2.2.2.2.1.2 - Operational Process Definition](ef3c8fc4-d958-492b-bee6-d96b5f972720).","contentHash":"4983d923b8587d0659c33ad3558d87f79a970d546e78e6a9b6e6682d1e9b5cbc","addressRefs":[]},"ef3c8fc4-d958-492b-bee6-d96b5f972720":{"id":"ef3c8fc4-d958-492b-bee6-d96b5f972720","doc_no":"A.6.1.1.5.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8740,"content":"The documents herein define the process for using the Root Edit Primitive to update the Obex Agent Artifact. Information on Obex governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.5.3.1 - Governance Information Unrelated To Root Edit Primitive](bdad4ea3-7cf2-40fb-a8ab-4bb8b320e4c9).","contentHash":"f4455bc25fbff8462b70933c80c1e2752aa1f748c03602f7fb3a15979442126c","addressRefs":[]},"da6d3815-d49e-47a4-8e62-81b66dbab51f":{"id":"da6d3815-d49e-47a4-8e62-81b66dbab51f","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8741,"content":"The documents herein define the process for using the Root Edit Primitive to update the Obex Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"bdc8b9e8eb88abbdc86304935a524e22bc8d003778ca858ce3c32b7a1d724248","addressRefs":[]},"fcb1b51e-8bb3-4a55-8cc0-9bec637086c8":{"id":"fcb1b51e-8bb3-4a55-8cc0-9bec637086c8","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8742,"content":"The Root Edit process begins with a OBEX token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. A OBEX token holder must hold at least 1% of the circulating token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Obex Prime\" category.","contentHash":"37ff517f092d4731ec06c66c33d9def54971fb5f09ed4a962d3ae62a311fe09d","addressRefs":[]},"e0020160-9ee8-4f35-90f1-ba375d625689":{"id":"e0020160-9ee8-4f35-90f1-ba375d625689","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.1.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8743,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, OBEX token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Obex Prime\" category. The title of the post must include the text \"Obex Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total OBEX token supply specified in [A.6.1.1.5.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](fcb1b51e-8bb3-4a55-8cc0-9bec637086c8).","contentHash":"a7c38f6b0cfcb72f4b6b088a7a3497bf6022c8485b86a979b6f49e1858ee7f10","addressRefs":[]},"432c532c-3e3a-41e9-b9dc-88c20d944541":{"id":"432c532c-3e3a-41e9-b9dc-88c20d944541","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8744,"content":"A future iteration of the Obex Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis.","contentHash":"93ef0a9ba529cf84e9ccacb1d7861f9af87cc2022ff577c2982e70117cf8aa7c","addressRefs":[]},"d21854da-165b-455d-893c-147db514d31c":{"id":"d21854da-165b-455d-893c-147db514d31c","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8745,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment.\n\nIf the proposal is aligned, the Operational Facilitator must respond to the Forum post to announce their finding. In this Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"3d695884c752507d7f445ad3a572c67b44863196d11108fb8a300dc2e71ce3e7","addressRefs":[]},"b60fe2f0-2aa6-4f36-9d87-e81c2294abc9":{"id":"b60fe2f0-2aa6-4f36-9d87-e81c2294abc9","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8746,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Obex Artifact, the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. The poll is open for three (3) days. A poll must have at least 10% of the circulating token supply participating and must have 50% of votes in favor to be approved.","contentHash":"446ca045586efc0ec30293ec95b9768e7835ede49eca1668564149cf26105efb","addressRefs":[]},"e0a6abf0-6191-4605-afa3-cc0de7b72a05":{"id":"e0a6abf0-6191-4605-afa3-cc0de7b72a05","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8747,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"a418eef2-bbfc-43eb-8d79-62c7bb940c3d":{"id":"a418eef2-bbfc-43eb-8d79-62c7bb940c3d","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.5.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8748,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"c14e9e4d-2819-46cb-b267-a9b13600192a":{"id":"c14e9e4d-2819-46cb-b267-a9b13600192a","doc_no":"A.6.1.1.5.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8749,"content":"The Obex Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"d8dc0d8b70b634ee774373cb85588388a710ca983b1e61322d7e8cc92178921d","addressRefs":[]},"2dcc5cd2-5936-4779-8ff6-072ad863756f":{"id":"2dcc5cd2-5936-4779-8ff6-072ad863756f","doc_no":"A.6.1.1.5.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8750,"content":"The documents herein define the process for using the Root Edit Primitive to update the Obex Agent Artifact in non-routine conditions.","contentHash":"23a3d6944bb2b54d13638bfe6435a909d1948323017d653a5317c43e7afc25c1","addressRefs":[]},"d12b8cf2-2668-4466-ac2e-7404fce6c718":{"id":"d12b8cf2-2668-4466-ac2e-7404fce6c718","doc_no":"A.6.1.1.5.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8751,"content":"The documents herein define the process for using the Root Edit Primitive to update the Obex Agent Artifact in emergency situations.","contentHash":"5be28a66091bdd1d073eeee71ffebadc24ff1e332d292fad99a2d9acba9ebb9b","addressRefs":[]},"f8b1cf73-d16d-4ca0-aeea-3f95d25245a8":{"id":"f8b1cf73-d16d-4ca0-aeea-3f95d25245a8","doc_no":"A.6.1.1.5.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process in Emergency Situations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8752,"content":"In an Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Obex Prime\" category), unless doing so would endanger Obex or its users.","contentHash":"826556551abbd560500f845f9632af82bfc7d0e7f49f4d6e6c9003ffc0f7967a","addressRefs":[]},"8f8ef2ba-1071-40df-98bc-384d1f6782b5":{"id":"8f8ef2ba-1071-40df-98bc-384d1f6782b5","doc_no":"A.6.1.1.5.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8753,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"b2f9aa29-8e29-4123-8996-12dad34b51e5":{"id":"b2f9aa29-8e29-4123-8996-12dad34b51e5","doc_no":"A.6.1.1.5.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8754,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"91cbbea6-33e4-49a4-ab2a-1c01d2b3eed8":{"id":"91cbbea6-33e4-49a4-ab2a-1c01d2b3eed8","doc_no":"A.6.1.1.5.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8755,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"efce80bb-4637-4bdf-8ddb-ad412154a521":{"id":"efce80bb-4637-4bdf-8ddb-ad412154a521","doc_no":"A.6.1.1.5.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8756,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"4d6ec316-b444-4550-a591-006a6b8080cd":{"id":"4d6ec316-b444-4550-a591-006a6b8080cd","doc_no":"A.6.1.1.5.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8757,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"77be1f27-3cd0-4e3f-a05d-8ce0880f37a7":{"id":"77be1f27-3cd0-4e3f-a05d-8ce0880f37a7","doc_no":"A.6.1.1.5.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8758,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"32cf649f-13f7-41e2-bbe4-347a14532114":{"id":"32cf649f-13f7-41e2-bbe4-347a14532114","doc_no":"A.6.1.1.5.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8759,"content":"The documents herein contain all data and specifications for Obex's Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"d938fb3973f8cc2dc36d026218192af0fb39562fd061bc7045ef5661408d87c5","addressRefs":[]},"c4b311b3-3f2c-483f-b24a-845ef5c6a6df":{"id":"c4b311b3-3f2c-483f-b24a-845ef5c6a6df","doc_no":"A.6.1.1.5.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8760,"content":"The documents herein organize all base information relevant to Obex's usage of the Light Agent Primitive.","contentHash":"3273c80bcef0166b2eba99c82696064ca563d6dba41f311d252c98aad262bc5b","addressRefs":[]},"afc008c0-e6d3-4973-b501-0f9f2db1cfa4":{"id":"afc008c0-e6d3-4973-b501-0f9f2db1cfa4","doc_no":"A.6.1.1.5.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8761,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"848c213e-5478-448c-9c7b-a8ea119823e5":{"id":"848c213e-5478-448c-9c7b-a8ea119823e5","doc_no":"A.6.1.1.5.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8762,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"88717821-a8d4-480e-91c6-ba996685746c":{"id":"88717821-a8d4-480e-91c6-ba996685746c","doc_no":"A.6.1.1.5.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8763,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"c38da3e3-0dbc-4deb-833f-0a124d55f0f7":{"id":"c38da3e3-0dbc-4deb-833f-0a124d55f0f7","doc_no":"A.6.1.1.5.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8764,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.2.3.1.2 - Active Instances Directory](848c213e-5478-448c-9c7b-a8ea119823e5), whereas failed Invocations are Archived in [A.6.1.1.5.2.2.3.1.5 - Hub Data Repository](19e005fe-f719-407f-b788-5bc13f3ffb11).","contentHash":"fe0602b582ad2bc24eb7498c06ce367162c19883a4fa3099ff64afd3f5f93d46","addressRefs":[]},"19e005fe-f719-407f-b788-5bc13f3ffb11":{"id":"19e005fe-f719-407f-b788-5bc13f3ffb11","doc_no":"A.6.1.1.5.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8765,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"8dfdbffe-91f9-44c5-8e28-45cbda1cbdfb":{"id":"8dfdbffe-91f9-44c5-8e28-45cbda1cbdfb","doc_no":"A.6.1.1.5.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8766,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"a7910404-5064-4d72-946d-2b9cb2f7d944":{"id":"a7910404-5064-4d72-946d-2b9cb2f7d944","doc_no":"A.6.1.1.5.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8767,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"d9955aca-f64d-41a3-9c5c-16ad98f98956":{"id":"d9955aca-f64d-41a3-9c5c-16ad98f98956","doc_no":"A.6.1.1.5.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8768,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"d7b02050-890e-4b86-9bbf-2d4183a97f44":{"id":"d7b02050-890e-4b86-9bbf-2d4183a97f44","doc_no":"A.6.1.1.5.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8769,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"5ef59d24-d4c8-445c-8385-08801b24be3a":{"id":"5ef59d24-d4c8-445c-8385-08801b24be3a","doc_no":"A.6.1.1.5.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8770,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"041daa3a-41b4-47fd-8e2b-bb288fd8342b":{"id":"041daa3a-41b4-47fd-8e2b-bb288fd8342b","doc_no":"A.6.1.1.5.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8771,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.2.3.2 - Active Instances](d7b02050-890e-4b86-9bbf-2d4183a97f44).","contentHash":"8507d2f6a8ba4de1692b93e05e8de131004fffc43db32cfb349da23ddedf693d","addressRefs":[]},"ea7388bc-3689-4b90-80d8-920eb7f25411":{"id":"ea7388bc-3689-4b90-80d8-920eb7f25411","doc_no":"A.6.1.1.5.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8772,"content":"The documents herein implement the Ecosystem Upkeep Primitives for Obex. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"4e51abcbf859dc7a469a348ee6db2116f25bcfd51badd3e2d5ed404ae5ea9753","addressRefs":[]},"518b0729-7d39-4e94-96ae-4e1dce577b3a":{"id":"518b0729-7d39-4e94-96ae-4e1dce577b3a","doc_no":"A.6.1.1.5.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8773,"content":"The documents herein contain all data and specifications for Obex's Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"1ab0f1be60b24305c7f0892eda5f3a77190fef501393c6efb2e8f5493b4ee8ae","addressRefs":[]},"367db765-3d90-449f-88d7-356eb2e5df6b":{"id":"367db765-3d90-449f-88d7-356eb2e5df6b","doc_no":"A.6.1.1.5.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8774,"content":"The documents herein organize all base information relevant to Obex's usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"2e3216538ec3e91e1bafc2bd9f4ff6c9e2fb1b7f3f93bafc4f361e436a0623ec","addressRefs":[]},"6a8a9da7-4c67-4553-84fd-5ad743f50847":{"id":"6a8a9da7-4c67-4553-84fd-5ad743f50847","doc_no":"A.6.1.1.5.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8775,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"590456d2-baea-411e-bd00-dccbd12387c0":{"id":"590456d2-baea-411e-bd00-dccbd12387c0","doc_no":"A.6.1.1.5.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8776,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"347ce0a4-ad9c-4a54-975b-939c932edbba":{"id":"347ce0a4-ad9c-4a54-975b-939c932edbba","doc_no":"A.6.1.1.5.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8777,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.3.1.2.1 - Single Instance Configuration Document](7ef7b4b1-d8c1-4f9d-bf00-c1cf292b0c02).","contentHash":"61f37747f5aa12ccbb595917b1fb4b7ff66ba79f16c5ff4c3f65be3d460a0cab","addressRefs":[]},"1d7ff736-dd46-4b6f-b5c1-c52e50f34846":{"id":"1d7ff736-dd46-4b6f-b5c1-c52e50f34846","doc_no":"A.6.1.1.5.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8778,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"14a2006a-764a-4526-8d9f-ff3dfc4591fe":{"id":"14a2006a-764a-4526-8d9f-ff3dfc4591fe","doc_no":"A.6.1.1.5.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8779,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"2087141c-ab9c-404e-bba8-1a1843350bb5":{"id":"2087141c-ab9c-404e-bba8-1a1843350bb5","doc_no":"A.6.1.1.5.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8780,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"8898ed9a-e7fc-403e-a061-8399a6b132b8":{"id":"8898ed9a-e7fc-403e-a061-8399a6b132b8","doc_no":"A.6.1.1.5.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8781,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"2ef60c48-9590-4e1f-b00a-48cb9edbcd20":{"id":"2ef60c48-9590-4e1f-b00a-48cb9edbcd20","doc_no":"A.6.1.1.5.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8782,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"a300b6cf-1826-4b4a-b49a-b9fe4f75ccda":{"id":"a300b6cf-1826-4b4a-b49a-b9fe4f75ccda","doc_no":"A.6.1.1.5.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8783,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"a27eeee1-ce9a-4b26-9bef-57199b921eda":{"id":"a27eeee1-ce9a-4b26-9bef-57199b921eda","doc_no":"A.6.1.1.5.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8784,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"7ef7b4b1-d8c1-4f9d-bf00-c1cf292b0c02":{"id":"7ef7b4b1-d8c1-4f9d-bf00-c1cf292b0c02","doc_no":"A.6.1.1.5.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8785,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"c3c06c49-ce92-4eac-b7e9-00783b4c6902":{"id":"c3c06c49-ce92-4eac-b7e9-00783b4c6902","doc_no":"A.6.1.1.5.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8786,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"49fe9982-412f-4da4-b81d-92786d3a7709":{"id":"49fe9982-412f-4da4-b81d-92786d3a7709","doc_no":"A.6.1.1.5.2.3.1.2.1.1.1","title":"Term","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8787,"content":"Obex will pay 0.50% of its market capitalization per year in USDS.","contentHash":"244a85edb21aa3e01a067c60d6d6c3ca0e95698d56566cc96218f05adf08afca","addressRefs":[]},"d58f7727-d553-43b9-b513-d4d490abc16f":{"id":"d58f7727-d553-43b9-b513-d4d490abc16f","doc_no":"A.6.1.1.5.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8788,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"dfafe9f2-4bc7-450a-b227-008d37b88249":{"id":"dfafe9f2-4bc7-450a-b227-008d37b88249","doc_no":"A.6.1.1.5.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8789,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"0fa4e4f4-a123-42d4-9353-997480ee8d14":{"id":"0fa4e4f4-a123-42d4-9353-997480ee8d14","doc_no":"A.6.1.1.5.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8790,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"ec192467-881e-4af6-9378-1fa4e36a6c18":{"id":"ec192467-881e-4af6-9378-1fa4e36a6c18","doc_no":"A.6.1.1.5.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8791,"content":"The process to pay 0.50% of Obex's market capitalization per year in USDS will be specified in future iterations of the Obex Artifact.","contentHash":"c687d0387bfccc8b9fd1a70c663d7ce06107d38878145b909cfb6b52a5589f10","addressRefs":[]},"fc2e23dd-7ca5-4487-b7ba-283156adab6f":{"id":"fc2e23dd-7ca5-4487-b7ba-283156adab6f","doc_no":"A.6.1.1.5.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8792,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"e68b9b15-fd96-4e9b-93d6-8feab64f8d7b":{"id":"e68b9b15-fd96-4e9b-93d6-8feab64f8d7b","doc_no":"A.6.1.1.5.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8793,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"4ba98afe-bd9c-49bb-938e-1475ceddd30b":{"id":"4ba98afe-bd9c-49bb-938e-1475ceddd30b","doc_no":"A.6.1.1.5.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8794,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"1f1e7bb2-dfa7-4189-84bd-9a6759aec3e7":{"id":"1f1e7bb2-dfa7-4189-84bd-9a6759aec3e7","doc_no":"A.6.1.1.5.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8795,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"8f8f951d-8768-457d-9c56-3a81b92c395a":{"id":"8f8f951d-8768-457d-9c56-3a81b92c395a","doc_no":"A.6.1.1.5.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8796,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"2e866803-811d-4220-b336-ebe239402921":{"id":"2e866803-811d-4220-b336-ebe239402921","doc_no":"A.6.1.1.5.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8797,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"beeba9d9-39bb-4f36-9447-9456966975eb":{"id":"beeba9d9-39bb-4f36-9447-9456966975eb","doc_no":"A.6.1.1.5.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8798,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"3c7049bc-3c9f-4088-94bc-0fc242dca76a":{"id":"3c7049bc-3c9f-4088-94bc-0fc242dca76a","doc_no":"A.6.1.1.5.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8799,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"1cec73ac-6b70-48ff-a7ff-1d0f689d602f":{"id":"1cec73ac-6b70-48ff-a7ff-1d0f689d602f","doc_no":"A.6.1.1.5.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8800,"content":"The documents herein contain all data and specifications for Obex's instance of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"5a11c26e24457f491346a795483f3a3a81e0772efa09a720c6bc4406e2dd5a63","addressRefs":[]},"36f57327-abff-4ac1-890b-c5097c449b02":{"id":"36f57327-abff-4ac1-890b-c5097c449b02","doc_no":"A.6.1.1.5.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8801,"content":"The documents herein organize all base information relevant to Obex's usage of the Upkeep Rebate Primitive.","contentHash":"6c99a358a5201b31d411eafa5a257e82cbb55473bfe123dff84327ae6fd9671d","addressRefs":[]},"28f93080-7f1f-45f1-a9c6-a78cea11cbbd":{"id":"28f93080-7f1f-45f1-a9c6-a78cea11cbbd","doc_no":"A.6.1.1.5.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8802,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"47f2fe76-ba5f-437e-8110-799c1e3fe7f5":{"id":"47f2fe76-ba5f-437e-8110-799c1e3fe7f5","doc_no":"A.6.1.1.5.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8803,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"4800d116-8fa3-40b4-ac3b-dce8629d2984":{"id":"4800d116-8fa3-40b4-ac3b-dce8629d2984","doc_no":"A.6.1.1.5.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8804,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.3.2.2.1 - Single Instance Configuration Document](8a327b83-b508-480b-8e97-038c6e35c64f).","contentHash":"6ee4467c616539bb025b0da42ba376eab8d04bc83de90cc2c1be9c04ebd8be01","addressRefs":[]},"41b96ba1-f506-498a-803f-d4067053b6ed":{"id":"41b96ba1-f506-498a-803f-d4067053b6ed","doc_no":"A.6.1.1.5.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8805,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"8850b00e-dd0a-44d7-b64a-7e4ef5cf7d37":{"id":"8850b00e-dd0a-44d7-b64a-7e4ef5cf7d37","doc_no":"A.6.1.1.5.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8806,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"0daa3c8b-dbce-4c8c-bfd6-30a3d5ae7486":{"id":"0daa3c8b-dbce-4c8c-bfd6-30a3d5ae7486","doc_no":"A.6.1.1.5.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8807,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"a8cd1289-22f9-4e01-878b-01a7b0e90a80":{"id":"a8cd1289-22f9-4e01-878b-01a7b0e90a80","doc_no":"A.6.1.1.5.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8808,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"49d6d2d2-1052-44d5-a9a9-0935d26f99ff":{"id":"49d6d2d2-1052-44d5-a9a9-0935d26f99ff","doc_no":"A.6.1.1.5.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8809,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"28085731-4ac7-4016-807c-652fe1447bb8":{"id":"28085731-4ac7-4016-807c-652fe1447bb8","doc_no":"A.6.1.1.5.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8810,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"c4e5deff-2cf9-492c-af8c-cfbd33327686":{"id":"c4e5deff-2cf9-492c-af8c-cfbd33327686","doc_no":"A.6.1.1.5.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8811,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"8a327b83-b508-480b-8e97-038c6e35c64f":{"id":"8a327b83-b508-480b-8e97-038c6e35c64f","doc_no":"A.6.1.1.5.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8812,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"439a27ef-945c-43dc-ab3b-836e5ab6372b":{"id":"439a27ef-945c-43dc-ab3b-836e5ab6372b","doc_no":"A.6.1.1.5.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8813,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"1d3eb5ff-4a71-4eff-a1f0-935f434644c1":{"id":"1d3eb5ff-4a71-4eff-a1f0-935f434644c1","doc_no":"A.6.1.1.5.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8814,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"144cfca6-e760-4f34-8ba3-effb1a1b9681":{"id":"144cfca6-e760-4f34-8ba3-effb1a1b9681","doc_no":"A.6.1.1.5.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8815,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"93599af2-bf73-4598-8b78-dfb74549f90d":{"id":"93599af2-bf73-4598-8b78-dfb74549f90d","doc_no":"A.6.1.1.5.2.3.2.2.1.2.1.1","title":"Obex Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8816,"content":"Obex keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"efe2dadcb2047a7ccb797526b9c0d10e37864536a0897d200e6c1c1b2d71fc51","addressRefs":[]},"eb954d3d-94d9-46d8-a118-a74e0d9da8c0":{"id":"eb954d3d-94d9-46d8-a118-a74e0d9da8c0","doc_no":"A.6.1.1.5.2.3.2.2.1.2.1.2","title":"Obex Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8817,"content":"When paying Ecosystem Upkeep fees, Obex deducts the rebate from the fees it pays.","contentHash":"f556cabfad228aefa37b871169bf34960ea91437c37593c045ed69f60adce58f","addressRefs":[]},"a8afed5e-3721-40a3-847c-3589a5dfce95":{"id":"a8afed5e-3721-40a3-847c-3589a5dfce95","doc_no":"A.6.1.1.5.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8818,"content":"Operational GovOps reviews Obex's calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Obex Prime\" category and work with Obex to resolve the disagreement. If Operational GovOps and Obex cannot resolve the disagreement, it must be escalated to Core GovOps.","contentHash":"565c913314754d008d0904a56c6ab0c57a3f03c9346038ff1323a56481336198","addressRefs":[]},"025b8abf-69a3-4749-95f3-60a7268983ff":{"id":"025b8abf-69a3-4749-95f3-60a7268983ff","doc_no":"A.6.1.1.5.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8819,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"e68e712a-cf58-45c0-8065-f81a5f259b18":{"id":"e68e712a-cf58-45c0-8065-f81a5f259b18","doc_no":"A.6.1.1.5.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8820,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"dd6c0d05-79f9-4663-85bb-916d12a29ce1":{"id":"dd6c0d05-79f9-4663-85bb-916d12a29ce1","doc_no":"A.6.1.1.5.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8821,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"df002eaa-d6d5-4b27-9ccb-26193cc65ec5":{"id":"df002eaa-d6d5-4b27-9ccb-26193cc65ec5","doc_no":"A.6.1.1.5.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8822,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"5bf870c7-57bc-40f8-82d4-f6094b484a5b":{"id":"5bf870c7-57bc-40f8-82d4-f6094b484a5b","doc_no":"A.6.1.1.5.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8823,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"d94ae414-18e8-432b-9f17-f58e8cc0cce3":{"id":"d94ae414-18e8-432b-9f17-f58e8cc0cce3","doc_no":"A.6.1.1.5.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8824,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"0723c247-7b2d-48aa-a1f1-1166aad05319":{"id":"0723c247-7b2d-48aa-a1f1-1166aad05319","doc_no":"A.6.1.1.5.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8825,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"4e8268eb-b8f4-4d45-bf11-a6c03f262275":{"id":"4e8268eb-b8f4-4d45-bf11-a6c03f262275","doc_no":"A.6.1.1.5.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8826,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"e66cbbd1-df57-418d-9699-73d050388fd6":{"id":"e66cbbd1-df57-418d-9699-73d050388fd6","doc_no":"A.6.1.1.5.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8827,"content":"The documents herein implement the SkyLink Primitives for Obex. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"e9ce9a58da5386e8897556217fca8c40b777601d9d20a7d157868a07b6e55c7e","addressRefs":[]},"5642de19-bfb3-4d54-9bc9-19b11b60a3c2":{"id":"5642de19-bfb3-4d54-9bc9-19b11b60a3c2","doc_no":"A.6.1.1.5.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8828,"content":"The documents herein contain all data and specifications for Obex's Instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"32250e57aefb7402e00e87bf457f4887330031dea4e069164107ded3c8e3b6d1","addressRefs":[]},"3ce6f8aa-7a27-4701-83cb-d1fc4c41bb28":{"id":"3ce6f8aa-7a27-4701-83cb-d1fc4c41bb28","doc_no":"A.6.1.1.5.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8829,"content":"The documents herein organize all base information relevant to Obex's usage of the Token SkyLink Primitive.","contentHash":"f081665b0e32e76501ed7b3255ce0665050376f30e9aa206101a33ae88e7f08b","addressRefs":[]},"9d778551-1fd4-4206-a0e0-cb555f6d1e34":{"id":"9d778551-1fd4-4206-a0e0-cb555f6d1e34","doc_no":"A.6.1.1.5.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8830,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"5c2fbcb7-e90b-44a5-854b-1616d9ad45a9":{"id":"5c2fbcb7-e90b-44a5-854b-1616d9ad45a9","doc_no":"A.6.1.1.5.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8831,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"a4ca44ca-4663-4d7d-8640-f173dfad1054":{"id":"a4ca44ca-4663-4d7d-8640-f173dfad1054","doc_no":"A.6.1.1.5.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8832,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"3fd9d534-7c71-411b-84ed-afbe997589d0":{"id":"3fd9d534-7c71-411b-84ed-afbe997589d0","doc_no":"A.6.1.1.5.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8833,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.4.1.1.2 - Active Instances Directory](5c2fbcb7-e90b-44a5-854b-1616d9ad45a9), whereas failed Invocations are Archived in [A.6.1.1.5.2.4.1.1.5 - Hub Data Repository](930899b8-232d-4015-a594-317b682ca460).","contentHash":"0a1333083c15d6e71f3dd74513daf3a5bd083a1f6eb67f5329b9541cbb9cd3b0","addressRefs":[]},"930899b8-232d-4015-a594-317b682ca460":{"id":"930899b8-232d-4015-a594-317b682ca460","doc_no":"A.6.1.1.5.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8834,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"f11e195b-b8ad-43fd-93a1-001b297d0dcf":{"id":"f11e195b-b8ad-43fd-93a1-001b297d0dcf","doc_no":"A.6.1.1.5.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8835,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"13a369a4-5eb1-4301-98a1-eff12149501a":{"id":"13a369a4-5eb1-4301-98a1-eff12149501a","doc_no":"A.6.1.1.5.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8836,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"aea6d389-e1d1-4cd1-bd96-24a29c1b3ecc":{"id":"aea6d389-e1d1-4cd1-bd96-24a29c1b3ecc","doc_no":"A.6.1.1.5.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8837,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"e8a2afff-b4b0-4b47-8b7a-32119eca9091":{"id":"e8a2afff-b4b0-4b47-8b7a-32119eca9091","doc_no":"A.6.1.1.5.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8838,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"b08f8e0b-5cc8-4b0a-b148-4ef44fa7ae03":{"id":"b08f8e0b-5cc8-4b0a-b148-4ef44fa7ae03","doc_no":"A.6.1.1.5.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8839,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"01dcfdbb-70a4-4986-bf38-28db96dba4c4":{"id":"01dcfdbb-70a4-4986-bf38-28db96dba4c4","doc_no":"A.6.1.1.5.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8840,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.4.1.2 - Active Instances](e8a2afff-b4b0-4b47-8b7a-32119eca9091).","contentHash":"2ccc66e7b5bdefbcf5a35be07b6c2bc50f394514c41f7b7d37a7dee1b05075a9","addressRefs":[]},"66ca6538-89c2-442e-87c2-9fe2d586b516":{"id":"66ca6538-89c2-442e-87c2-9fe2d586b516","doc_no":"A.6.1.1.5.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8841,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Obex. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"d0b6eb5c0f1d155be1afd5cdb313e65176c53ec2a54e078015e9b9c3262933f3","addressRefs":[]},"f055e990-51e6-44c2-8d14-4e8694e62c1d":{"id":"f055e990-51e6-44c2-8d14-4e8694e62c1d","doc_no":"A.6.1.1.5.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8842,"content":"The documents herein contain all data and specifications for Obex's instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"4fc65a5edc13be59141810daa8242167ab7e15ecbc92d32786ac461fb980d594","addressRefs":[]},"f11e8f01-a17f-44e7-aac1-56dbd5e9272e":{"id":"f11e8f01-a17f-44e7-aac1-56dbd5e9272e","doc_no":"A.6.1.1.5.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8843,"content":"The documents herein organize all base information relevant to Obex's usage of the Distribution Reward Primitive.","contentHash":"6adef18b8f603f9914966f7a8c2bc1a3d3fba1113b032915a826889befaf9cfe","addressRefs":[]},"94bbd7ec-e724-41e7-b74a-0e567768f219":{"id":"94bbd7ec-e724-41e7-b74a-0e567768f219","doc_no":"A.6.1.1.5.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8844,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"6d07d8e0-e37e-47f0-8534-e0c67effd267":{"id":"6d07d8e0-e37e-47f0-8534-e0c67effd267","doc_no":"A.6.1.1.5.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8845,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"f3d16b8f-4ac2-41b8-8744-13beb396588e":{"id":"f3d16b8f-4ac2-41b8-8744-13beb396588e","doc_no":"A.6.1.1.5.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8846,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"e1234baf-b923-4837-a279-96a76208f78d":{"id":"e1234baf-b923-4837-a279-96a76208f78d","doc_no":"A.6.1.1.5.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8847,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.5.1.1.2 - Active Instances Directory](6d07d8e0-e37e-47f0-8534-e0c67effd267), whereas failed Invocations are Archived in [A.6.1.1.5.2.5.1.1.5 - Hub Data Repository](27d2b846-1278-4cf6-9a2f-09114d659813).","contentHash":"cad6953ae487fc1db3e395b0fec6bac57d01b39ee483348123ee22c2d67aed9b","addressRefs":[]},"27d2b846-1278-4cf6-9a2f-09114d659813":{"id":"27d2b846-1278-4cf6-9a2f-09114d659813","doc_no":"A.6.1.1.5.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8848,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"d345b6e5-cf01-4c2c-a177-6d4f5549dcff":{"id":"d345b6e5-cf01-4c2c-a177-6d4f5549dcff","doc_no":"A.6.1.1.5.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8849,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"1cb40bb8-ab91-4fb8-82ba-84e71bd84504":{"id":"1cb40bb8-ab91-4fb8-82ba-84e71bd84504","doc_no":"A.6.1.1.5.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8850,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"ce59ab47-8c7a-4893-a3f2-c9eeafac5168":{"id":"ce59ab47-8c7a-4893-a3f2-c9eeafac5168","doc_no":"A.6.1.1.5.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8851,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"bbe5be33-f895-48a4-a8de-7d65d83d4321":{"id":"bbe5be33-f895-48a4-a8de-7d65d83d4321","doc_no":"A.6.1.1.5.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8852,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"51861e24-08e4-4828-a5ea-0f0ac08f67db":{"id":"51861e24-08e4-4828-a5ea-0f0ac08f67db","doc_no":"A.6.1.1.5.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8853,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"12cf9640-3b5b-4255-b7d9-e84baa973d9f":{"id":"12cf9640-3b5b-4255-b7d9-e84baa973d9f","doc_no":"A.6.1.1.5.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8854,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.5.1.2 - Active Instances](bbe5be33-f895-48a4-a8de-7d65d83d4321).","contentHash":"a9dacedb354b29bdd087f43c5dbdcd779612f3503fe6b9ab85068661996bb1da","addressRefs":[]},"edc5cd33-99a9-4687-b3fe-8c3e07da92e8":{"id":"edc5cd33-99a9-4687-b3fe-8c3e07da92e8","doc_no":"A.6.1.1.5.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8855,"content":"The documents herein contain all data and specifications for Obex's Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"52f6c3640784456c7e99a31c4ba1a1897764b47e25df00c1160c558392ad974c","addressRefs":[]},"f9d5c302-4695-436f-9a06-595c06da2fc9":{"id":"f9d5c302-4695-436f-9a06-595c06da2fc9","doc_no":"A.6.1.1.5.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8856,"content":"The documents herein organize all base information relevant to Obex's usage of the Integration Boost Primitive.","contentHash":"8db452605f5e5efc926f24aa70c09e445e4c2bae91eeeb094e922e2360b0cd73","addressRefs":[]},"f6c8017d-81cc-4ad5-ac3c-c68a354f2a61":{"id":"f6c8017d-81cc-4ad5-ac3c-c68a354f2a61","doc_no":"A.6.1.1.5.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8857,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"bf82c8f9-c7d4-42ac-b590-f28982863ef5":{"id":"bf82c8f9-c7d4-42ac-b590-f28982863ef5","doc_no":"A.6.1.1.5.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8858,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"c206ac89-c13e-4fae-886e-3014d0640b05":{"id":"c206ac89-c13e-4fae-886e-3014d0640b05","doc_no":"A.6.1.1.5.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8859,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"daad121e-7835-4c61-90fb-eb15f987329e":{"id":"daad121e-7835-4c61-90fb-eb15f987329e","doc_no":"A.6.1.1.5.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8860,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.5.2.1.2 - Active Instances Directory](bf82c8f9-c7d4-42ac-b590-f28982863ef5), whereas failed Invocations are Archived in [A.6.1.1.5.2.5.2.1.5 - Hub Data Repository](7b523fb3-f463-4f10-90d6-6dd1211dbc24).","contentHash":"41967ea484fde469450e02af2abd9196f61634ad9cbb0633a1df5520e847fe90","addressRefs":[]},"7b523fb3-f463-4f10-90d6-6dd1211dbc24":{"id":"7b523fb3-f463-4f10-90d6-6dd1211dbc24","doc_no":"A.6.1.1.5.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8861,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"3aa560cf-c7bd-47f8-b156-e3422c5dfc9b":{"id":"3aa560cf-c7bd-47f8-b156-e3422c5dfc9b","doc_no":"A.6.1.1.5.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8862,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"64cbff91-cacc-492e-97de-d412bb860190":{"id":"64cbff91-cacc-492e-97de-d412bb860190","doc_no":"A.6.1.1.5.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8863,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"d229d7d4-efdf-413c-9d9d-d4af3b43164b":{"id":"d229d7d4-efdf-413c-9d9d-d4af3b43164b","doc_no":"A.6.1.1.5.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8864,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"0607bde3-cffa-4597-8ad9-fdb38272a843":{"id":"0607bde3-cffa-4597-8ad9-fdb38272a843","doc_no":"A.6.1.1.5.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8865,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"4dca2418-b9ea-4bdb-ae27-f34a09c7e761":{"id":"4dca2418-b9ea-4bdb-ae27-f34a09c7e761","doc_no":"A.6.1.1.5.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8866,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"7fdf50ff-7d49-4ffc-9e2d-c1db6ce4a33a":{"id":"7fdf50ff-7d49-4ffc-9e2d-c1db6ce4a33a","doc_no":"A.6.1.1.5.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8867,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.5.2.2 - Active Instances](0607bde3-cffa-4597-8ad9-fdb38272a843).","contentHash":"45c705e63809652bd1baeebfda42cc5083c848a1aeb16e3860946f23b9818c64","addressRefs":[]},"2f0a0b71-759e-4f14-b63d-0286450855fe":{"id":"2f0a0b71-759e-4f14-b63d-0286450855fe","doc_no":"A.6.1.1.5.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8868,"content":"The documents herein contain all data and specifications for Obex's Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"acf2de1f9754b9e71eb99a97412508d289d26c922e7b8a102840b8a42a8e6ade","addressRefs":[]},"7e7dc6f6-bfe1-460e-9fb1-35a906f75259":{"id":"7e7dc6f6-bfe1-460e-9fb1-35a906f75259","doc_no":"A.6.1.1.5.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8869,"content":"The documents herein organize all base information relevant to Obex's usage of the Pioneer Chain Primitive.","contentHash":"0d95037f0779b792f0c19d58f3f81de77cd9f9899a53d2661fd14e793579cdb8","addressRefs":[]},"c13df592-a35a-4d72-b33e-65c3ee9ba799":{"id":"c13df592-a35a-4d72-b33e-65c3ee9ba799","doc_no":"A.6.1.1.5.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8870,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"b0507c60-c43a-4ba2-b2d1-e0dbc4694720":{"id":"b0507c60-c43a-4ba2-b2d1-e0dbc4694720","doc_no":"A.6.1.1.5.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8871,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"18bcb4c7-6147-4231-a7fc-0d0c43cec037":{"id":"18bcb4c7-6147-4231-a7fc-0d0c43cec037","doc_no":"A.6.1.1.5.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8872,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"e9e9cbf4-87cb-4e48-bf7c-f1a4caa934fa":{"id":"e9e9cbf4-87cb-4e48-bf7c-f1a4caa934fa","doc_no":"A.6.1.1.5.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8873,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.5.3.1.2 - Active Instances Directory](b0507c60-c43a-4ba2-b2d1-e0dbc4694720), whereas failed Invocations are Archived in [A.6.1.1.5.2.5.3.1.5 - Hub Data Repository](be430718-d9f5-4104-bdd0-26e333bd0a13).","contentHash":"52a4e10a03d0e8abf1ef3c827b97cfb30114cd8492e22120bc6a518d0493878e","addressRefs":[]},"be430718-d9f5-4104-bdd0-26e333bd0a13":{"id":"be430718-d9f5-4104-bdd0-26e333bd0a13","doc_no":"A.6.1.1.5.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8874,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"cd28b1ad-9837-4db4-bcb5-7b35ee89d7a0":{"id":"cd28b1ad-9837-4db4-bcb5-7b35ee89d7a0","doc_no":"A.6.1.1.5.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8875,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"fd0b30aa-9a67-428f-8414-ed99818c58b0":{"id":"fd0b30aa-9a67-428f-8414-ed99818c58b0","doc_no":"A.6.1.1.5.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8876,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"20face9e-9216-44e9-b195-7d5fcb4c8465":{"id":"20face9e-9216-44e9-b195-7d5fcb4c8465","doc_no":"A.6.1.1.5.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8877,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"4fd3fe8d-e5d8-49ce-95b5-15e14e165abf":{"id":"4fd3fe8d-e5d8-49ce-95b5-15e14e165abf","doc_no":"A.6.1.1.5.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8878,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"504497a1-14b9-4119-b520-bdcf4bedc4f9":{"id":"504497a1-14b9-4119-b520-bdcf4bedc4f9","doc_no":"A.6.1.1.5.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8879,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"cafab30a-9a0e-46ba-8eb9-889d85a57bb0":{"id":"cafab30a-9a0e-46ba-8eb9-889d85a57bb0","doc_no":"A.6.1.1.5.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8880,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.5.3.2 - Active Instances](4fd3fe8d-e5d8-49ce-95b5-15e14e165abf).","contentHash":"2cfc5e0063b99a0813bf29a22476917ec97ff2147596e6fbfaa4b9711bc9665e","addressRefs":[]},"c63a813f-b434-4c81-8826-df78171f61f0":{"id":"c63a813f-b434-4c81-8826-df78171f61f0","doc_no":"A.6.1.1.5.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8881,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Obex. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"0091b18c45c6d357d539eaa120501a23039dd6bb1e47cc1bf745be8bbb071c91","addressRefs":[]},"fe98c7e7-b7f8-4f2c-800a-bca5192576ac":{"id":"fe98c7e7-b7f8-4f2c-800a-bca5192576ac","doc_no":"A.6.1.1.5.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8882,"content":"The documents herein contain all data and specifications for Obex's Allocation System Primitive Instances.","contentHash":"8a0fe23d4a10701392aded068f95372c2bbe7a4558934ba78edb8f958d6c63ba","addressRefs":[]},"cbf426ee-7754-49c5-9040-b29a5126da39":{"id":"cbf426ee-7754-49c5-9040-b29a5126da39","doc_no":"A.6.1.1.5.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8883,"content":"The documents herein organize all base information relevant to Obex's usage of the Obex Liquidity Layer.","contentHash":"d5a84dc13fafc14bce5308e8395ff9bab03e879b372fd96fc0daf49e6c12fcfa","addressRefs":[]},"02a794ce-0d32-4044-80c2-1ba5bf0b1ca0":{"id":"02a794ce-0d32-4044-80c2-1ba5bf0b1ca0","doc_no":"A.6.1.1.5.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8884,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"b8d74925-677a-48e8-be42-b9e2614c9e0f":{"id":"b8d74925-677a-48e8-be42-b9e2614c9e0f","doc_no":"A.6.1.1.5.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8885,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"7b8f5dc5-643d-4eb8-be6f-1663cc0856ac":{"id":"7b8f5dc5-643d-4eb8-be6f-1663cc0856ac","doc_no":"A.6.1.1.5.2.6.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8886,"content":"The documents herein contain a Directory of all Instances on Ethereum Mainnet of the Allocation System Primitive with Instance status of `Active`.","contentHash":"cfd1cdbfaa1c46010dde8c6a850409b0b5d25ece87b06d03d1df44b1b8420b32","addressRefs":[]},"59ef3080-82eb-4c0f-96cf-5d973128e4ef":{"id":"59ef3080-82eb-4c0f-96cf-5d973128e4ef","doc_no":"A.6.1.1.5.2.6.1.1.2.1.1","title":"Maple","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8887,"content":"The Ethereum Mainnet Instances Directory of the Maple Protocol with `Active` Status are stored herein.","contentHash":"23d31010d23f63ecd6441f2d5871677626acdbf4cc73a664c3cb7e7130524d34","addressRefs":[]},"7188ea33-de7a-4d97-a52e-4a6acbcb608c":{"id":"7188ea33-de7a-4d97-a52e-4a6acbcb608c","doc_no":"A.6.1.1.5.2.6.1.1.2.1.1.1","title":"Ethereum Mainnet - Maple USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8888,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.5.2.6.1.3.1.1.1 - Ethereum Mainnet - Maple USDC Instance Configuration Document](7488a14c-2464-4649-b476-48ee93bb438f).","contentHash":"c12c6d4e9026aaeedfff0d799fd27a3fa3fb1f966d4513b98e75266b3abd951d","addressRefs":[]},"f98d5f67-2cf0-4691-b13b-23e11caad05b":{"id":"f98d5f67-2cf0-4691-b13b-23e11caad05b","doc_no":"A.6.1.1.5.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8889,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"492c60d5-d5eb-4fab-b8eb-a4858c7b6033":{"id":"492c60d5-d5eb-4fab-b8eb-a4858c7b6033","doc_no":"A.6.1.1.5.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8890,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.6.1.1.2 - Active Instances Directory](b8d74925-677a-48e8-be42-b9e2614c9e0f), whereas failed Invocations are Archived in [A.6.1.1.5.2.6.1.1.5 - Hub Data Repository](1a4ddf66-20ba-42e8-b7a9-6a71106f891a).","contentHash":"3a6164b43c09dfd914ef1f6e16766b0467273850b5e579fce412fe8febe7d7bf","addressRefs":[]},"1a4ddf66-20ba-42e8-b7a9-6a71106f891a":{"id":"1a4ddf66-20ba-42e8-b7a9-6a71106f891a","doc_no":"A.6.1.1.5.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8891,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"1b2334f1-f766-4b58-94b2-8cfbceb90ac6":{"id":"1b2334f1-f766-4b58-94b2-8cfbceb90ac6","doc_no":"A.6.1.1.5.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8892,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"224c6cc9-f120-4a4c-b708-3df8b9c50faf":{"id":"224c6cc9-f120-4a4c-b708-3df8b9c50faf","doc_no":"A.6.1.1.5.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8893,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"a685b24a-59a8-49e4-94d5-20db465f316e":{"id":"a685b24a-59a8-49e4-94d5-20db465f316e","doc_no":"A.6.1.1.5.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8894,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"aa59c9ff-7347-407f-9d55-59fa499a58c9":{"id":"aa59c9ff-7347-407f-9d55-59fa499a58c9","doc_no":"A.6.1.1.5.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8895,"content":"The documents herein provide general specifications of the Obex Liquidity Layer and define Obex's overarching strategy and operational framework for managing across all Instances.","contentHash":"5e9d9b1a3ec04170efaf7701f4a21e9bbeaf8f0fc8bd90971d7fef3eb23d8d1c","addressRefs":[]},"1fa01b00-08d6-4344-ab6c-7a0cbea5e06c":{"id":"1fa01b00-08d6-4344-ab6c-7a0cbea5e06c","doc_no":"A.6.1.1.5.2.6.1.2.1","title":"General Specifications","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8896,"content":"The documents herein contain general specifications for the Obex Liquidity Layer.","contentHash":"10d112fd64df7748abaa68d1d7639181033e04a9204baa588beeedae7e732572","addressRefs":[]},"c29faa6d-d657-47a0-9379-21b8cd831d02":{"id":"c29faa6d-d657-47a0-9379-21b8cd831d02","doc_no":"A.6.1.1.5.2.6.1.2.1.1","title":"Obex Liquidity Layer Architecture","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8897,"content":"The documents herein describe the high-level design of the Obex Liquidity Layer, including its key smart contracts and their functionality.","contentHash":"f124da9c00896edc2bafff8871a79d3a2867bfed68e66509b7c5f1fe9266c75b","addressRefs":[]},"ef875c4e-2303-4b94-8c92-6831ec96fac9":{"id":"ef875c4e-2303-4b94-8c92-6831ec96fac9","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1","title":"Obex Liquidity Layer Addresses","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8898,"content":"The documents herein provide the addresses of the Obex Liquidity Layer's constituent contracts.","contentHash":"5842466ab288d8b344c4356f4df6ff9286b1cdd86c36b01dd3627bdb66f7fedb","addressRefs":[]},"4cd1c7c9-f246-40b1-a31c-4512638f7fd3":{"id":"4cd1c7c9-f246-40b1-a31c-4512638f7fd3","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.1","title":"Allocator Contract Addresses","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8899,"content":"The documents herein contain global key addresses for the Allocator Contracts.","contentHash":"a99119eb26b8e6fbaae81a45fa911afc0af3344a9ea2bbcb90fc7cf9bd94fe9c","addressRefs":[]},"3dbd11b0-2713-40e1-b0ca-66f5ebdf213c":{"id":"3dbd11b0-2713-40e1-b0ca-66f5ebdf213c","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.1.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8900,"content":"The documents herein contain the Allocator Contract Addresses on the Ethereum Mainnet.","contentHash":"084c1a1c5fbe0a4abc17b09c0096038edfd2c77bdd298abb5411775b166695ef","addressRefs":[]},"0d4e4822-8b33-4306-9f32-c08cd4014484":{"id":"0d4e4822-8b33-4306-9f32-c08cd4014484","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.1.1.1","title":"Allocator Buffer Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8901,"content":"The address of the ALLOCATOR_BUFFER contract is: `0x51E9681D7a05abFD33EfaFd43e5dd3Afc0093F1D`","contentHash":"62c779f0d152e2001f90a7fa4657e3f22ddfb2b6f8200ed40574fa46cf3abb80","addressRefs":["0x51e9681d7a05abfd33efafd43e5dd3afc0093f1d"]},"87e95c06-0f81-4908-8282-8067346b3200":{"id":"87e95c06-0f81-4908-8282-8067346b3200","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.1.1.2","title":"Allocator Oracle Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8902,"content":"The address of the ALLOCATOR_ORACLE contract is: `0xc7B91C401C02B73CBdF424dFaaa60950d5040dB7`","contentHash":"3915a8e9d83e0d12a43a164e763cda42d8b41817675dff88c98314a34152cb8e","addressRefs":["0xc7b91c401c02b73cbdf424dfaaa60950d5040db7"]},"850fc16c-496e-4148-a86a-d2d2e5f03685":{"id":"850fc16c-496e-4148-a86a-d2d2e5f03685","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.1.1.3","title":"Allocator Registry Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8903,"content":"The address of the ALLOCATOR_REGISTRY contract is: `0xCdCFA95343DA7821fdD01dc4d0AeDA958051bB3B`","contentHash":"b7d71c2ecb2f67f2fe2ddf5b5835dec050bd7652285c86dba07b3fb3e96f8275","addressRefs":["0xcdcfa95343da7821fdd01dc4d0aeda958051bb3b"]},"0b889cc8-0fa2-476e-ae62-77bc09ca556e":{"id":"0b889cc8-0fa2-476e-ae62-77bc09ca556e","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.1.1.4","title":"Allocator Roles Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8904,"content":"The address of the ALLOCATOR_ROLES contract is: `0x9A865A710399cea85dbD9144b7a09C889e94E803`","contentHash":"458d4bfa62334f282ee18ad433673de3de9a11f7e2c97fd190afc1bef481a49d","addressRefs":["0x9a865a710399cea85dbd9144b7a09c889e94e803"]},"a4310d54-9535-43ec-8d6a-c92c854f8a98":{"id":"a4310d54-9535-43ec-8d6a-c92c854f8a98","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.1.1.5","title":"Allocator Vault Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8905,"content":"The address of the ALLOCATOR_VAULT contract is: `0xF275110dFE7B80df66a762f968f59B70BABE2b29`","contentHash":"a345f5bc6d1dde5c406f020afaa256dc8f770f9bb787adef86ffc9edc3bd0fad","addressRefs":["0xf275110dfe7b80df66a762f968f59b70babe2b29"]},"656c09f6-93a7-4b0b-a268-a495adeffaf0":{"id":"656c09f6-93a7-4b0b-a268-a495adeffaf0","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2","title":"ALM Contracts","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8906,"content":"The documents herein contain addresses for the ALM Contracts for the Obex Liquidity Layer.","contentHash":"3ca07e1b285efaae31ec081a68e59ef88c7a078efe2c17c14a9db1f50c0e355b","addressRefs":[]},"5d99d731-c3ed-461c-a6ea-50ebd741b3d2":{"id":"5d99d731-c3ed-461c-a6ea-50ebd741b3d2","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8907,"content":"The documents herein contain the ALM Contract Addresses for the Obex Liquidity Layer on the Ethereum Mainnet.","contentHash":"3d3bfe69e139a6b998fa0d32e549e0dc7a42bae86a28751e1b6589882814a9bc","addressRefs":[]},"cdb42b2b-e506-4e5e-a088-651b10880cde":{"id":"cdb42b2b-e506-4e5e-a088-651b10880cde","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2.2","title":"ALM Controller Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8908,"content":"The address of the ALM_CONTROLLER (MainnetController) contract is: `0xF2bB664f16E2df4b0c71F9d2cFc386504E795b7A`","contentHash":"ba991a9b538d6283ed49b66d0bc866749850bcc546455142a5e9058c2fab5d0e","addressRefs":["0xf2bb664f16e2df4b0c71f9d2cfc386504e795b7a"]},"4f345770-ead0-41ce-a821-96ab1291d033":{"id":"4f345770-ead0-41ce-a821-96ab1291d033","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2.3","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8909,"content":"The ALM_CONTROLLER contract version is: V.1.6.0","contentHash":"72517f77084344a284929e31fa4bb127f6bf891590d3200870aea1c5c39fe908","addressRefs":[]},"855a0165-ff72-4d0f-bddf-62bae68be333":{"id":"855a0165-ff72-4d0f-bddf-62bae68be333","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2.4","title":"ALM Freezer Multisig Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8910,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.5.2.6.1.2.1.2.2.3 - Freezer Multisig](49e6c234-7102-43e0-80a6-fb14e259e1f7).","contentHash":"10b340d0f184a9e38f0bc6accd2d557ed58d71ea989ff00f43e56cc4c21289cf","addressRefs":[]},"86586cb8-ccbb-4ab7-8244-add51cca65fe":{"id":"86586cb8-ccbb-4ab7-8244-add51cca65fe","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2.5","title":"ALM Relayer Multisig Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8911,"content":"The address of the Multisigs that has the Relayer Role is specified in [A.6.1.1.5.2.6.1.2.1.2.2.1 - Prime Relayer Multisig](3b53c3b4-1d13-4197-8078-54523949784f) and [A.6.1.1.5.2.6.1.2.1.2.2.2 - Core Operator Relayer Multisig](b32dec2f-51e1-44b0-a81b-679b648ed659).","contentHash":"0e5752f67800a80091769dbc6359a907a9d46fb8442be192c8808221ecc452a5","addressRefs":[]},"53aa9c70-f2c8-4c0b-a30c-9c541d7dbbd4":{"id":"53aa9c70-f2c8-4c0b-a30c-9c541d7dbbd4","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2.6","title":"ALM Proxy Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8912,"content":"The address of the ALM_PROXY contract is: `0xb6dD7ae22C9922AFEe0642f9Ac13e58633f715A2`","contentHash":"8a42a881c034bd749784cfb7921b9f10c5381f7eaa1c33ae65d5da8947e585cc","addressRefs":["0xb6dd7ae22c9922afee0642f9ac13e58633f715a2"]},"837cd549-5b8f-4d00-974b-f53af0f53f82":{"id":"837cd549-5b8f-4d00-974b-f53af0f53f82","doc_no":"A.6.1.1.5.2.6.1.2.1.1.1.2.7","title":"ALM Rate Limits Contract","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8913,"content":"The address of the ALM_RATE_LIMITS contract is: `0x81f8f5306cF80655Edff78f89860a8D89118E150`","contentHash":"a249e7060bcefcc0e583a954a3fa9729d0e799d04be89b432e0e79d716994b66","addressRefs":["0x81f8f5306cf80655edff78f89860a8d89118e150"]},"3f4a771a-ed2f-43ae-b8ad-a4d27e206779":{"id":"3f4a771a-ed2f-43ae-b8ad-a4d27e206779","doc_no":"A.6.1.1.5.2.6.1.2.1.1.2","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8914,"content":"The documents herein list the off-chain operational parameters for the Obex Liquidity Layer. These operational parameters are protocol settings managed outside of smart contracts (off-chain), used by operators and off-chain systems to guide the functioning of the Obex Liquidity Layer.","contentHash":"c281272011d221e202d43a1614a6105d7a33c8f2af19be2aa4088913c7ad357c","addressRefs":[]},"5915e763-fa01-4202-95c9-b446b94bc92a":{"id":"5915e763-fa01-4202-95c9-b446b94bc92a","doc_no":"A.6.1.1.5.2.6.1.2.1.1.2.1","title":"Off-chain Operational Parameters For Ethereum Mainnet","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8915,"content":"The document herein lists the current off-chain operational parameters for the Obex Liquidity Layer on Ethereum Mainnet.","contentHash":"214df12654756ff802b892bf9b2eaa6ff31e3000eb6f664482171c75f3af2568","addressRefs":[]},"319b996c-7563-4d56-a7b2-4302cebc91f5":{"id":"319b996c-7563-4d56-a7b2-4302cebc91f5","doc_no":"A.6.1.1.5.2.6.1.2.1.1.2.1.1","title":"Minimum Operation Size Ethereum Mainnet","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8916,"content":"The minimum transaction size for operations on Ethereum Mainnet is (`MAINNET_MIN_OPERATION_SIZE`):\n\n- This parameter will be specified in a future iteration of the Obex Artifact.","contentHash":"f9434c984ab77ba3c054793cdcd4dc148c6a094d3b25e84d4fb717b5ac809826","addressRefs":[]},"ff5d0ea1-bfb0-4e18-8768-603230a3dea6":{"id":"ff5d0ea1-bfb0-4e18-8768-603230a3dea6","doc_no":"A.6.1.1.5.2.6.1.2.1.1.2.1.2","title":"Debt Ceiling Buffer Ethereum Mainnet","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8917,"content":"The buffer amount below the maximum debt ceiling is (`DEBT_CEILING_BUFFER`):\n\n- This parameter will be specified in a future iteration of the Obex Artifact.","contentHash":"b3f3069142ce0abc0e3e7b95aa687a46ad4a4db3c26309e00d68b12fd168ac96","addressRefs":[]},"3dea2074-9594-44af-80b9-f67d831bde1a":{"id":"3dea2074-9594-44af-80b9-f67d831bde1a","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3","title":"Rate Limits","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8918,"content":"The documents herein list the Rate Limits for the Obex Liquidity Layer on each blockchain.","contentHash":"86f9468cf2e3d344ffdb4600c46cfa73fc2f88e1409592f91bda7522b6a4cadf","addressRefs":[]},"cecaa353-2826-4e19-a641-ee24989d42b6":{"id":"cecaa353-2826-4e19-a641-ee24989d42b6","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8919,"content":"The documents herein list the current `RateLimits` for the Obex Liquidity Layer on Ethereum Mainnet.","contentHash":"852df5b31d3a92bda1bd38ba155ee9f9e8ed702172229ded1f3b34b8c5576daa","addressRefs":[]},"a97961ff-de69-4a13-b2a4-830a2458e3b9":{"id":"a97961ff-de69-4a13-b2a4-830a2458e3b9","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.1","title":"Ethereum Mainnet USDS","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8920,"content":"The maximum mint, burn and swap for USDS on Ethereum Mainnet are located herein","contentHash":"6df9387dbe2719b407f2d90596e3ca32bcc117a9b2328444ad098fdf3b58bad0","addressRefs":[]},"1b4f0be7-31d8-4217-9961-08789613fbb1":{"id":"1b4f0be7-31d8-4217-9961-08789613fbb1","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.1.1","title":"USDS Mint Maximum","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8921,"content":"The maximum amount of USDS that can be minted within the Obex Liquidity Layer (`LIMIT_USDS_MINT`) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"d30f5a6de48cd25e871cddc7c36e4782d2e85a267cf733cb90c2ee96277b5b40","addressRefs":[]},"312ab6a0-55b8-4974-b918-bbd0f69085b3":{"id":"312ab6a0-55b8-4974-b918-bbd0f69085b3","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.1.2","title":"USDS Burn Maximum","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8922,"content":"The maximum amount of USDS that can be burned within the Obex Liquidity Layer (`LIMIT_USDS_BURN`) is specified in the document herein.\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Obex Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Obex Artifact.","contentHash":"bd5d09c448ea2f2a5f91c6669d13dd891e5328095dee72df09a2fa6ed175a040","addressRefs":[]},"1bae9188-f480-49d7-91c5-c3f271260e60":{"id":"1bae9188-f480-49d7-91c5-c3f271260e60","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.1.3","title":"USDS For USDC Swap Maximum","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8923,"content":"The maximum amount of USDS that can be swapped for USDC by the Obex Liquidity Layer in the Mainnet PSM (`LIMIT_USDS_TO_USDC`) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"dfa8525fa47c447f2306c228e460c06e5686a011d29c7c669b0db65ea529bf8b","addressRefs":[]},"d6cbd2a4-e0cb-4339-8354-5c11f6a72c93":{"id":"d6cbd2a4-e0cb-4339-8354-5c11f6a72c93","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.2","title":"Ethereum Mainnet sUSDS","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8924,"content":"The maximum deposit and withdraw amounts for sUSDS on Ethereum Mainnet are located herein.","contentHash":"1e726f4384f0cc88789de9e0c752ada6c43c7410006c62f95842dea9436b16f8","addressRefs":[]},"a5d4f47c-615d-4bc7-bd7d-7cf694b7b02c":{"id":"a5d4f47c-615d-4bc7-bd7d-7cf694b7b02c","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.2.1","title":"Ethereum Mainnet sUSDS Deposit Maximum","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8925,"content":"The maximum amount of sUSDS that can be deposited (`LIMIT_4626_DEPOSIT`) is specified in the document herein.\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Obex Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Obex Artifact.","contentHash":"fbb72caa0b562a6db19af1b8a4d1aecb18404cdb0c12565fbef1681eb4bb94ce","addressRefs":[]},"40959dc7-e554-4611-b615-25d3ff557bdf":{"id":"40959dc7-e554-4611-b615-25d3ff557bdf","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.2.2","title":"Ethereum Mainnet sUSDS Withdrawal Maximum","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8926,"content":"The maximum amount of sUSDS that can be withdrawn (`LIMIT_4626_WITHDRAW`) is specified in the document herein.\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Obex Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Obex Artifact.","contentHash":"449034c89817965309f209539eacc3b0f195993ace679ba67661dbb0fff4b6a8","addressRefs":[]},"8505febf-f853-4de9-89dc-d483d5439cbc":{"id":"8505febf-f853-4de9-89dc-d483d5439cbc","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.3","title":"Ethereum Mainnet USDC ALM Proxy","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8927,"content":"The maximum amount that can be transferred and sent to the Ethereum Mainnet ALM Proxy for USDC are located herein.","contentHash":"68830d060981b0780a06abcb64f5b336d432d02fd53d921f4a62c56d50eb943a","addressRefs":[]},"212d5d8b-7d1c-4e25-864b-f9e072d9d345":{"id":"212d5d8b-7d1c-4e25-864b-f9e072d9d345","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.3.1","title":"USDC ALM Proxy Maximum","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8928,"content":"The maximum amount of USDC that can be sent to the Ethereum Mainnet ALM Proxy (`LIMIT_USDC_TO_DOMAIN`, hashed with Ethereum domain) is specified in the document herein.\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Obex Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Obex Artifact.","contentHash":"18d2c61375927b0f4184e4e2d8ea7cd6e0f6f759d78e45539eac8d0eca21c4f1","addressRefs":[]},"17827367-6342-4e4e-bc1f-652c0f5b079e":{"id":"17827367-6342-4e4e-bc1f-652c0f5b079e","doc_no":"A.6.1.1.5.2.6.1.2.1.1.3.1.3.1.1","title":"USDC ALM Proxy Circle Cross-Chain Transfer Protocol Maximum","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8929,"content":"The maximum amount of USDC that can be bridged to Ethereum Mainnet ALM Proxy using the Circle Cross-Chain Transfer Protocol (`LIMIT_USDC_TO_CCTP_ETH`) is specified in the document herein.\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Obex Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Obex Artifact.","contentHash":"4f07c04c4832ce834bd167d1d5930b973acacaf6f8c3fae4d91f7f8ff6e4cee8","addressRefs":[]},"97d35c04-2b5b-430d-b297-b2b4703d71c0":{"id":"97d35c04-2b5b-430d-b297-b2b4703d71c0","doc_no":"A.6.1.1.5.2.6.1.2.1.1.4","title":"On-chain Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8930,"content":"The documents herein list general on-chain parameters for the Obex Liquidity Layer","contentHash":"5881cacbe777d0fca4441449506eabe5b405d658e6af0a36cfd3cc7452069ebd","addressRefs":[]},"c30d6144-4cbd-4ef4-90d5-312d24c9858e":{"id":"c30d6144-4cbd-4ef4-90d5-312d24c9858e","doc_no":"A.6.1.1.5.2.6.1.2.1.1.4.1","title":"Allocator Vault Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8931,"content":"The Allocator Vault parameters for ALLOCATOR-OBEX-A are defined in [A.3.7.1.2.1.4 - ALLOCATOR-OBEX-A Parameters](1ee3efd3-fe75-4766-bc6a-ec204f6a3bca).","contentHash":"bdf07a860f119b54dcf0132742003a47640ea7b2b296a835b6340a8486da9d69","addressRefs":[]},"5c795414-020c-432d-91b6-a7d72495452e":{"id":"5c795414-020c-432d-91b6-a7d72495452e","doc_no":"A.6.1.1.5.2.6.1.2.1.1.4.2","title":"Whitelisting Of ALMProxy","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8932,"content":"The ALMProxy for Obex must be whitelisted on the LitePSM. This will effectively allow Obex to call `buyGemNoFee` and `sellGemNoFee` on the `MCD_LITE_PSM_USDC_A` contract.","contentHash":"03a596cda18cbbfffe18e8cdfa12b73c811b5425f7f259f89f9d88491a5832db","addressRefs":[]},"94015de1-4d83-43d3-998b-093c1a2099fa":{"id":"94015de1-4d83-43d3-998b-093c1a2099fa","doc_no":"A.6.1.1.5.2.6.1.2.1.2","title":"Governance Processes","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8933,"content":"The documents herein describe the specific governance processes for the Obex Liquidity Layer.","contentHash":"fda8987aa0c93c1e0f2c0b5e7a45796170d1c9b59e89e060a264b03db361ca9c","addressRefs":[]},"f6be405d-fae7-474e-882d-5c98985324b6":{"id":"f6be405d-fae7-474e-882d-5c98985324b6","doc_no":"A.6.1.1.5.2.6.1.2.1.2.1","title":"Invoking New Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8934,"content":"The governance process to invoke a new Instance of the Allocation System Primitive follows the Root Edit process see Operational Process Definition.","contentHash":"7c9b275563145851d7c7a8cf17c821a9f507a5ecffd68b48ae96e2e9706975bc","addressRefs":[]},"7b3aa284-2872-4ffe-9938-2bbfa7d4525d":{"id":"7b3aa284-2872-4ffe-9938-2bbfa7d4525d","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2","title":"Multisigs","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8935,"content":"The documents herein define multisigs that have privileged access to manage the Obex Liquidity Layer.","contentHash":"ea53873f13d01c65442b5fbfedf2982c73787aab4000dc6feedf240b055f5d78","addressRefs":[]},"3b53c3b4-1d13-4197-8078-54523949784f":{"id":"3b53c3b4-1d13-4197-8078-54523949784f","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.1","title":"Prime Relayer Multisig","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8936,"content":"The Prime Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.5.2.6.1.2.2.1.1.2 - Relayer Role](0a8458ff-499e-4ac6-85a3-6ce200df18ae) and is controlled by Obex.","contentHash":"e2526ce2858f3d39152ca0ef85cdfa2ddf5c92b5f792e94f2b21cba806d40371","addressRefs":[]},"5d2d1cef-96c5-4881-a7b7-d70e75541fac":{"id":"5d2d1cef-96c5-4881-a7b7-d70e75541fac","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.1.1","title":"Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8937,"content":"The address of the Prime Relayer Multisig on the Ethereum Mainnet is `0x5d36918C8F4726a62257AA79a50E53D553465663`.","contentHash":"0735a3fb1a66ff8059a383f855f6e515f0d4bd8c40729cc23d52923a21b86eee","addressRefs":["0x5d36918c8f4726a62257aa79a50e53d553465663"]},"2f7dbfea-075e-4208-bb37-abf05599b1d1":{"id":"2f7dbfea-075e-4208-bb37-abf05599b1d1","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.1.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8938,"content":"The Prime Relayer Multisig currently has a 4/7 signing requirement.","contentHash":"52a09c5df511d4b5d8f1e446e2d2e958d1f9cde1d82bb10e69f965b6223ae8eb","addressRefs":[]},"b14ad946-9e1c-494a-8849-45c30d625e3d":{"id":"b14ad946-9e1c-494a-8849-45c30d625e3d","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.1.3","title":"Signers","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8939,"content":"The signers of the Prime Relayer Multisig are seven (7) addresses controlled by Obex.","contentHash":"c43bac5df73b0925002c5b9a25fb4c8b5b8319a7f9ac139f7896ec0fd04ef063","addressRefs":[]},"c96f7c83-92e7-4874-9c03-4a450cc904ff":{"id":"c96f7c83-92e7-4874-9c03-4a450cc904ff","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.1.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8940,"content":"The signers of the Prime Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Obex Artifact.","contentHash":"54ba09d768f310f09228c2e50f4ed2fd7e45e0998b650195a84461fd709bb7dd","addressRefs":[]},"3212cf2f-ec75-4418-9fe2-f4b751bd19d8":{"id":"3212cf2f-ec75-4418-9fe2-f4b751bd19d8","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.1.5","title":"Modification","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8941,"content":"Obex can change the signers of the Prime Relayer Multisig at any time, so long as there are at least seven (7) signers and at least a majority of signers are required to execute transactions.","contentHash":"3d5d79b2a69946b503a6ab7f25c466f3db9d233cb477684bcbb7179c7b7bf292","addressRefs":[]},"b32dec2f-51e1-44b0-a81b-679b648ed659":{"id":"b32dec2f-51e1-44b0-a81b-679b648ed659","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.2","title":"Core Operator Relayer Multisig","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8942,"content":"The Core Operator Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.5.2.6.1.2.2.1.1.2 - Relayer Role](0a8458ff-499e-4ac6-85a3-6ce200df18ae) and is controlled by Operational GovOps Soter Labs.","contentHash":"ed91c0e475b7e6542a3d290488c9cc1d0bd16bab0315fa995840ac65513862e4","addressRefs":[]},"17c29741-7ed5-4a6e-96ff-55514df2a8f5":{"id":"17c29741-7ed5-4a6e-96ff-55514df2a8f5","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.2.1","title":"Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8943,"content":"The address of the Core Operator Relayer Multisig on the Ethereum Mainnet is `0x2b1D60B11B7015fB83361a219BE01B7564436054`.","contentHash":"962113b63923eb45f8c23cc58129f9fcdbd138cbaedc47962a3c8181ecd705a0","addressRefs":["0x2b1d60b11b7015fb83361a219be01b7564436054"]},"ecc50ea6-d4f0-41be-b0f4-af11a34bd60e":{"id":"ecc50ea6-d4f0-41be-b0f4-af11a34bd60e","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.2.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8944,"content":"The Core Operator Relayer Multisig currently has a 2/3 signing requirement.","contentHash":"b95f8f292db28ccf8bfd3f9a26c34232a22a6849ead7951e92687e1b4cdfd849","addressRefs":[]},"2c9c02a4-86a1-4862-90aa-e314d9177f37":{"id":"2c9c02a4-86a1-4862-90aa-e314d9177f37","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.2.3","title":"Signers","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8945,"content":"The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs.","contentHash":"3f47955b9c0fde92c5560c85814bf985ea86ba974f63c359990c046ae3388a94","addressRefs":[]},"476f94f2-3e35-4d99-9664-c91984104b6b":{"id":"476f94f2-3e35-4d99-9664-c91984104b6b","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.2.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8946,"content":"The signers of the Core Operator Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Obex Artifact.","contentHash":"6c7dc619e7edbbff7927bef095e3d0bd60cd85f60c8a6e89cb660f2cc2f10385","addressRefs":[]},"a342e39a-ba3e-4871-ad17-17ce3323e6f2":{"id":"a342e39a-ba3e-4871-ad17-17ce3323e6f2","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.2.5","title":"Modification","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8947,"content":"Operational GovOps Soter Labs can change the signers of the Core Operator Relayer Multisig at any time, so long as there are at least three (3) signers and at least two thirds of signers are required to execute transactions.","contentHash":"000b84b3f38f0919060dc840a7e0f8e93a32658e543a2e8b1c596470ddf8341f","addressRefs":[]},"49e6c234-7102-43e0-80a6-fb14e259e1f7":{"id":"49e6c234-7102-43e0-80a6-fb14e259e1f7","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.3","title":"Freezer Multisig","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8948,"content":"The Freezer Multisig has the `FREEZER_ROLE` as defined in [A.6.1.1.5.2.6.1.2.2.1.1.4 - Freezer Role](afcfa58a-fc3d-4f5d-9bc8-bf40e7fa3ec7).","contentHash":"646a59b12abebf0bb77bcdf1a805ab1d7857837b03735b4c12f29cb733c67324","addressRefs":[]},"6624912c-1cf6-443c-925f-ba1451a1644f":{"id":"6624912c-1cf6-443c-925f-ba1451a1644f","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.3.1","title":"Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8949,"content":"The address of the Freezer Multisig on the Ethereum Mainnet is `0x1924b6990B63c5f820b81a23CD40383808D416D8`.","contentHash":"3bc67829a673a5bdde63bf7166e6d796a0bcb32e482fc7ea757a8a6dad957a11","addressRefs":["0x1924b6990b63c5f820b81a23cd40383808d416d8"]},"b1b34a90-ead4-4e45-8a88-72c1149f716b":{"id":"b1b34a90-ead4-4e45-8a88-72c1149f716b","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.3.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8950,"content":"The Freezer Multisig currently has a 2/5 signing requirement.","contentHash":"5e26a52c6172c820a3edf55895c2df704dad7607cd26054763c73cd1b6fbdbc3","addressRefs":[]},"cac6b239-3d5f-4014-98a2-df082c1c6cdb":{"id":"cac6b239-3d5f-4014-98a2-df082c1c6cdb","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.3.3","title":"Signers","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8951,"content":"The signers of the Freezer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs, one (1) address controlled by Operational Facilitator Redline Facilitation Group, and one (1) address controlled by Obex.","contentHash":"81bcf23243db9bd856996237288292fc78dd8043c3a17f09523f7d2e1142ff16","addressRefs":[]},"0535c9cd-dd37-4a76-815d-836ad1dd1974":{"id":"0535c9cd-dd37-4a76-815d-836ad1dd1974","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.3.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8952,"content":"The signers of the Freezer Multisig should exercise their authority to freeze the Obex Liquidity Layer in the event that Obex is not complying with rules regarding Risk Capital or Asset Liability Management, or in the event of another emergency.\n\nEach action executed by the Freezer Multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum.","contentHash":"74c24a4c67354e69ed31d8f5fa7fd15b9f87f1de1d92cfe56105e7d5f554c598","addressRefs":[]},"247ea87b-5649-4c92-aebe-5a5fc45c2c75":{"id":"247ea87b-5649-4c92-aebe-5a5fc45c2c75","doc_no":"A.6.1.1.5.2.6.1.2.1.2.2.3.5","title":"Modification","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8953,"content":"Modification of the signers of the Freezer Multisig must be approved through an Atlas Edit Proposal.\n\nThe only exceptions to this are if: 1) a signer self-reports a loss of access to their private key due to any reason; or 2) a signer explicitly expresses their wish to be removed as a signer. In both cases, the signer is required to communicate the loss of access to their private key, or the wish to be removed as a signer, in the form of a public Sky Forum post. The specific signer should be replaced as soon as possible.\n\nAny changes to the Multisig signers that do not fall within the two exceptions listed above, or that have not been ratified by Sky Governance, should be questioned immediately and treated as malicious. Where malicious activity is suspected, the Core Facilitator must prepare an expedited Executive Vote so that Sky Governance can vote on removing external security access from the Multisig.","contentHash":"5a7d5809b6c81bb95db41542b9e9b65803e19629cf564e404811d45d7486f1e4","addressRefs":[]},"f65883db-3b01-4c25-be16-d05c8b95494a":{"id":"f65883db-3b01-4c25-be16-d05c8b95494a","doc_no":"A.6.1.1.5.2.6.1.2.1.3","title":"Total Risk Capital (TRC) Management","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8954,"content":"The documents herein specify requirements related to Obex’s Total Risk Capital (TRC) management.","contentHash":"aa0ffc6597da033b790a04794c82e21271feee167451f4a6c85d8b5317a00f46","addressRefs":[]},"d915471b-230e-41ab-bc86-68bc9453e417":{"id":"d915471b-230e-41ab-bc86-68bc9453e417","doc_no":"A.6.1.1.5.2.6.1.2.1.3.1","title":"Treadstone's Operation Of Obex Liquidity Layer And Agreement Regarding Encumbrance Ratio","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8955,"content":"Treadstone will operate the Obex Liquidity Layer and agrees to stay at or below a 90% Encumbrance Ratio. See [A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9).","contentHash":"09ed2d3b0f77e7f7229010486337ba866644e2e26baa1948286c59d0491c61c2","addressRefs":[]},"8248b6dc-0dd9-4019-98e6-83c8d5892317":{"id":"8248b6dc-0dd9-4019-98e6-83c8d5892317","doc_no":"A.6.1.1.5.2.6.1.2.1.3.2","title":"Treadstone's Total Risk Capital (TRC) Management Processes","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8956,"content":"As operators of the Obex Liquidity Layer, Treadstone automatically inherits, and is subject to, the base class of operational requirements related to Total Risk Capital management defined in [A.2.2.9.1.1.3.2.1.2 - Primes' Total Risk Capital (TRC) Management](3af8a3a2-25e5-44b3-87a4-7df1f2712685). Modifications to the base operational logic automatically propagate to the Obex Artifact.","contentHash":"b7493e1a247f7cbaae190fa8a722e0b11a0c7dfe6d6aa2fbd7caa1af619e94e6","addressRefs":[]},"f0393207-2bae-42a2-9ca0-df8ffd4d2a39":{"id":"f0393207-2bae-42a2-9ca0-df8ffd4d2a39","doc_no":"A.6.1.1.5.2.6.1.2.2","title":"Obex Liquidity Layer Operational Processes","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8957,"content":"The documents herein describe common operational procedures for the Obex Liquidity Layer applicable across multiple Instances.","contentHash":"25e979d450cc0d2e6e644cb7c68579b1e86995ea8341d506e3c73b490da7fbf8","addressRefs":[]},"cea1c91e-e940-41ab-99bb-254b821b24ff":{"id":"cea1c91e-e940-41ab-99bb-254b821b24ff","doc_no":"A.6.1.1.5.2.6.1.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8958,"content":"The documents herein define the protocol for routine ongoing management of the Obex Liquidity Layer and its active Instances.","contentHash":"8699a968922b03007ec9e7c842eea9587be378f1b9f019035f4679a01dd76766","addressRefs":[]},"4eb0b4dc-9ffe-4201-b0cf-31e1cde8fcdb":{"id":"4eb0b4dc-9ffe-4201-b0cf-31e1cde8fcdb","doc_no":"A.6.1.1.5.2.6.1.2.2.1.1","title":"Role Hierarchy And Permissions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8959,"content":"The documents herein defines roles (Admin, Relayer, ALM Controller and Freezer) and their responsibilities/permissions for managing the Obex Liquidity Layer.","contentHash":"482c4574f2fe3f34bc33c80d0037e585a363dc59d5b1b20db76fc6ba3458ce79","addressRefs":[]},"d0dfc54e-e06e-434b-9194-9b1ad5b6be8a":{"id":"d0dfc54e-e06e-434b-9194-9b1ad5b6be8a","doc_no":"A.6.1.1.5.2.6.1.2.2.1.1.1","title":"Default Admin Role","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8960,"content":"The admin role (DEFAULT_ADMIN_ROLE) is the role that can grant and revoke any role, including itself and all other roles defined in the contract. The admin role is also used for general admin functions in all contracts. This role is fully controlled by Sky Governance via the Obex Proxy.\n\n```\nconstructor(address admin) {\n_grantRole(DEFAULT_ADMIN_ROLE, admin);\n```","contentHash":"03e3682549eafd75b45f0e9db5fd873a65d0b23893de0e4324ebb657893ad576","addressRefs":[]},"0a8458ff-499e-4ac6-85a3-6ce200df18ae":{"id":"0a8458ff-499e-4ac6-85a3-6ce200df18ae","doc_no":"A.6.1.1.5.2.6.1.2.2.1.1.2","title":"Relayer Role","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8961,"content":"The `RELAYER_ROLE` is the address for the Obex Liquidity Layer ALM Planner off-chain system that calls functions on `Controller` contracts to perform actions on behalf of the `ALMProxy` contract. The Relayer Role may be granted to an address by any address holding the `DEFAULT_ADMIN_ROLE`. The Relayer Role may be removed from an address by any address holding the `DEFAULT_ADMIN_ROLE` or the `FREEZER_ROLE`.","contentHash":"e2a3c06e77838d98f7bc404a817d2e22c8d2223f45c3ce304771a8803c62c665","addressRefs":[]},"9a8f34e4-1e38-48da-8fc7-e97d8b6dc64f":{"id":"9a8f34e4-1e38-48da-8fc7-e97d8b6dc64f","doc_no":"A.6.1.1.5.2.6.1.2.2.1.1.3","title":"ALM Controller Role","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8962,"content":"The `ALM_CONTROLLER_ROLE` is the address of the role that can call the `call` functions on the `ALMProxy` contract and update `RateLimits` contract. It includes the `MainnetController` and `ForeignController` contracts. ALM Controller contracts are accessed and modified via the Relayer Role.","contentHash":"2338ec34a7da2944765e15ca9792b0c4ec0cffcbf72218d25d3c57bffdc821f2","addressRefs":[]},"afcfa58a-fc3d-4f5d-9bc8-bf40e7fa3ec7":{"id":"afcfa58a-fc3d-4f5d-9bc8-bf40e7fa3ec7","doc_no":"A.6.1.1.5.2.6.1.2.2.1.1.4","title":"Freezer Role","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8963,"content":"The `FREEZER_ROLE` is the address of the emergency role that can remove a compromised Relayer.","contentHash":"5613adb996d95581a1f27d5ec22a32a62f59e9d8f62e6ff43f248f6bd75f410f","addressRefs":[]},"b64040c5-b290-478a-b69f-08cd8b5e7003":{"id":"b64040c5-b290-478a-b69f-08cd8b5e7003","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2","title":"Controller Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8964,"content":"The documents herein describe the purpose and operational use of key functions within the Obex Liquidity Layer `MainnetController` contracts: USDS management (mint/burn USDS), Asset Transfer Management (direct transfers, protocol deposits/withdrawals), Cross-chain Operations (CCTP bridging).","contentHash":"dd5b4f2256b69e3630e88b437126757c4a46f18b55449bf8f54c02c9ae0a44de","addressRefs":[]},"39a5aa5c-19b0-4012-9f8d-2cef298bdd4b":{"id":"39a5aa5c-19b0-4012-9f8d-2cef298bdd4b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1","title":"Mainnet Controller Contract Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8965,"content":"The documents herein define the functions controlled by the Controller contract for Obex Liquidity Layer operations on Ethereum Mainnet.","contentHash":"253fc19f6d11ac414dcf09e04471e21a0f100a2e7cf89d84312f4d4612ae5f2f","addressRefs":[]},"abb49068-d94b-4569-9014-bb767ceec6cb":{"id":"abb49068-d94b-4569-9014-bb767ceec6cb","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.1","title":"Admin Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8966,"content":"The documents herein define the operations performed by the admin role (see [A.6.1.1.5.2.6.1.2.2.1.1.1 - Default Admin Role](d0dfc54e-e06e-434b-9194-9b1ad5b6be8a)) within the `MainnetController` contract.","contentHash":"046289e8592ccc06557f6f4dddaf6ff6a4f25194fbdcff24d1bd2eb60b2fe495","addressRefs":[]},"1a834a8b-d87b-4eed-8f17-8276a2ae2dee":{"id":"1a834a8b-d87b-4eed-8f17-8276a2ae2dee","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.1.1","title":"Set Mint Recipient For Destination Domain","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8967,"content":"The documents herein define the steps for an admin to specify which address should receive newly minted tokens on a particular destination domain.","contentHash":"e18d032726334c884a3fef8347d5e82a077819f279c99e6388f0e0e6e6c17199","addressRefs":[]},"05134536-1b5a-488f-8c82-a9a1aa6ea836":{"id":"05134536-1b5a-488f-8c82-a9a1aa6ea836","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.1.1.1","title":"Call setMintRecipient Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8968,"content":"Only an operator with the admin role is able to set the mint recipient for a destination domain. To do so, they must call the `setMintRecipient` function on the Controller contract on mainnet providing the destination domain and the mint recipient address. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role the transaction will revert.\n- The contract will set the selected mint recipient for the specified destination domain.\n- The contract will emit a `MintRecipientSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setMintRecipient(uint32 destinationDomain, bytes32 mintRecipient) external`","contentHash":"62ff9aed370987d09554d45ed885419834c3a8d1ec5fb30268034f868b811e24","addressRefs":[]},"27f7da97-2cf4-4d32-81e9-c1ef7b8f0199":{"id":"27f7da97-2cf4-4d32-81e9-c1ef7b8f0199","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.1.2","title":"Set LayerZero Recipient","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8969,"content":"The documents herein define the steps for an admin to specify which address should receive LayerZero messages on a particular destination endpoint.","contentHash":"529b6a0e9f1b8e61a703349f93f307fde7ab7e28b97bc74b29a3dc4b391b9058","addressRefs":[]},"54c019d8-ae0a-4c1c-9f05-1192d7b1cefb":{"id":"54c019d8-ae0a-4c1c-9f05-1192d7b1cefb","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.1.2.1","title":"Call setLayerZeroRecipient Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8970,"content":"Only an operator with the admin role is able to set the LayerZero recipient for a destination endpoint. To do so, they must call the `setLayerZeroRecipient` function on the Controller contract on mainnet, providing the destination endpoint ID and the recipient address. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role, the transaction will revert.\n- The contract will set the selected LayerZero recipient for the specified destination endpoint.\n- The contract will emit a `LayerZeroRecipientSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setLayerZeroRecipient(uint32 destinationEndpointId, bytes32 layerZeroRecipient) external`","contentHash":"1a37c01cad0a4ff26a1f5c94db71a0ff3916acb7beca0e135db6a9505a0f1a63","addressRefs":[]},"c25f736d-c806-4287-a5ee-9ef81f8e0ab7":{"id":"c25f736d-c806-4287-a5ee-9ef81f8e0ab7","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.1.3","title":"Set Maximum Slippage","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8971,"content":"The documents herein define the steps for an admin to set the maximum allowed slippage for a specific pool.","contentHash":"4c5e57348afcaa8e60130af9381c39d20bd2adbbc775d02aaedcfaa0fefeea09","addressRefs":[]},"9926982e-5571-4108-9caa-88b4d8708d45":{"id":"9926982e-5571-4108-9caa-88b4d8708d45","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.1.3.1","title":"Call setMaximumSlippage Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8972,"content":"Only an operator with the admin role is able to set the maximum slippage for a pool. To do so, they must call the `setMaxSlippage` function on the Controller contract on mainnet, providing the pool address and the maximum slippage value. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role, the transaction will revert.\n- The contract will set the maximum slippage for the specified pool.\n- The contract will emit a `MaxSlippageSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setMaxSlippage(address pool, uint256 maxSlippage) external`","contentHash":"9a27132420655c07a094df4efaba7ce834dd51c5e50556195377ccbbad5a46b6","addressRefs":[]},"04da1a02-47fb-4ecd-9b50-27daf99b6d6f":{"id":"04da1a02-47fb-4ecd-9b50-27daf99b6d6f","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2","title":"Relayer Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8973,"content":"The documents herein define the operations performed by the relayer role (see [A.6.1.1.5.2.6.1.2.2.1.1.2 - Relayer Role](0a8458ff-499e-4ac6-85a3-6ce200df18ae)) within the `MainnetController` contract.","contentHash":"d1eeb7a269c90c63bb5d152058f94359ffed67be524d935988d4e328143f9711","addressRefs":[]},"dad796ae-ec65-4aec-b0d4-c47e87f3d148":{"id":"dad796ae-ec65-4aec-b0d4-c47e87f3d148","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.1","title":"Relayer Vault Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8974,"content":"The documents herein define the operations that are performed to maintain the desired level of liquidity and debt balance of the Obex Liquidity Layer.","contentHash":"16f9a5f33ac538d69fc1d8defb5af59ace3dc769e097d501715054fb10615280","addressRefs":[]},"d56d12e9-b513-4e8c-8e3c-cf9e49d59f2b":{"id":"d56d12e9-b513-4e8c-8e3c-cf9e49d59f2b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.1.1","title":"Mint USDS","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8975,"content":"The documents herein define the steps for a relayer to mint USDS from the Sky Allocation Vault to the Obex ALM Proxy.","contentHash":"9012f280c9ffd90f08d19e67b880df3602c309cf55d79c4dcc7e8feca663ea60","addressRefs":[]},"e6313c89-b401-468d-882b-bf5e57d0182c":{"id":"e6313c89-b401-468d-882b-bf5e57d0182c","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.1.1.1","title":"Call mintUSDS Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8976,"content":"Only an operator with the relayer role is able to mint USDS. To do so, they must call the `mintUSDS` function on the Controller contract on mainnet with the amount of USDS that is required for minting. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will ensure the `RateLimits` allow for minting the required amount. If the mint amount does not fall within the available Rate Limit the transaction will revert.\n- The contract will reduce the Rate Limit by the amount of USDS minted in this transaction.\n- The contract will mint the required USDS into the buffer contract.\n- The contract will transfer the newly minted USDS from the buffer to the Proxy.\n\nThe function call is as follows:\n\n`function mintUSDS(uint256 usdsAmount) external`","contentHash":"e7409520ec60f2ff611d39df14d23e10c54062d4ded68a08ae6c2dded8120050","addressRefs":[]},"1e27b007-ed34-4c15-9116-d62145572dce":{"id":"1e27b007-ed34-4c15-9116-d62145572dce","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.1.2","title":"Burn USDS","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8977,"content":"The documents herein define the steps for a relayer to return and then burn Obex’s USDS debt in the Sky Allocation Vault.","contentHash":"ceb70baf78fa9176641efd99b4378d6f5f64d8b178aa951980474f58e76a61d4","addressRefs":[]},"9faf62a8-812c-4986-8133-5b3493634b9f":{"id":"9faf62a8-812c-4986-8133-5b3493634b9f","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.1.2.1","title":"Call burnUSDS Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8978,"content":"Only an operator with the relayer role is able to repay vault debt and burn USDS. To do so, they must call the `burnUSDS` function of the Controller contract on mainnet with the amount of USDS that they wish to burn. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will increase the available Rate Limit for minting USDS by the amount of USDS being burned. This increase will be limited by the `maxAmount` parameter in the `Rate Limit` contract.\n- The contract will transfer USDS from the proxy to the buffer.\n- The contract will burn the USDS from the buffer and `wipe` an equivalent amount from the vault's debt.\n\nThe function call is as follows:\n\n`function burnUSDS(uint256 usdsAmount) external`","contentHash":"92b3508ecc9977345338f28c9c2cd842eb213fe799124831e454251715f09f8c","addressRefs":[]},"4d4dd524-bad6-424b-9d39-0e35f8f889b4":{"id":"4d4dd524-bad6-424b-9d39-0e35f8f889b4","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.2","title":"ERC-20 Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8979,"content":"The documents herein define the operations that are performed to transfer ERC-20 assets to specified destinations.","contentHash":"d28c31b8ab0d83cf03cc2fc4bd3b795529ab9c078d5d41f64515b4e63120219b","addressRefs":[]},"81128daf-2709-465d-bfd3-ff29e5566072":{"id":"81128daf-2709-465d-bfd3-ff29e5566072","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.2.1","title":"Transfer Asset","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8980,"content":"The documents herein define the steps for a relayer to transfer ERC-20 tokens to a destination address.","contentHash":"88a951aa42193ef6d8f1c08721493c83b1b360651c00ac25507f0762fba7f268","addressRefs":[]},"77447d4a-137b-4b1c-b266-02ca8c678f61":{"id":"77447d4a-137b-4b1c-b266-02ca8c678f61","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.2.1.1","title":"Call transferAsset Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8981,"content":"Only an operator with the relayer role is able to transfer ERC-20 assets. To do so, they must call the `transferAsset` function on the Controller contract on mainnet, providing the ERC20 asset address, the destination address, and the amount to transfer. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will ensure the `RateLimits` allow for transferring the specified amount of the asset to the destination. If the transfer amount does not fall within the available Rate Limit, the transaction will revert.\n- The contract will execute the ERC-20 `transfer` function, sending the specified amount of the asset to the destination address.\n\nThe function call is as follows:\n\n`function transferAsset(address asset, address destination, uint256 amount) external`","contentHash":"a37fa4e3d9bcbef21e11a96c66528873e5067e6e764388d79dc367fc6a153b48","addressRefs":[]},"08d30ec2-c343-4176-aded-dce33e76d69c":{"id":"08d30ec2-c343-4176-aded-dce33e76d69c","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.3","title":"ERC-4626 Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8982,"content":"The documents herein define the general Obex Liquidity Layer operational procedures for interacting with ERC-4626-compliant tokenized vaults. ERC-4626 is a standard interface for vaults representing shares of an underlying ERC-20 token. Obex Liquidity Layer can integrate with various ERC-4626 vaults. For instance-specific parameters (such as vault addresses, asset addresses, and rate limits), refer to the relevant ERC-4626 Instance Configuration Document.","contentHash":"cb342f14d60addc6f0aaabb04a458f468309443a2372bab81f51d32ec4a9ef8c","addressRefs":[]},"bab638ed-79fb-4163-aeb2-c569fc79c8e1":{"id":"bab638ed-79fb-4163-aeb2-c569fc79c8e1","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.3.1","title":"Deposit To ERC-4626 Vault","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8983,"content":"The documents herein define the steps for a relayer to deposit assets from the ALM Proxy to an ERC-4626 vault to receive yield-bearing shares.","contentHash":"b80f044c9242551c8ee6c4a30ae6071bbb378ef9d152494b757f8036bf9763bf","addressRefs":[]},"58edaa80-7dc0-4591-93fb-3552a2bb6a0b":{"id":"58edaa80-7dc0-4591-93fb-3552a2bb6a0b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.3.1.1","title":"Call depositERC4626 Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8984,"content":"Only an operator with the relayer role can deposit assets into an ERC-4626 vault. To do so, they must call the `depositERC4626` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to deposit. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for deposit; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the deposit amount is within the allowed rate limit for the specified vault.\n- The contract will approve the vault to spend the underlying asset from the ALM Proxy. The approval and deposit are both performed from the ALM Proxy address.\n- The contract will deposit the specified amount into the vault, and the ALM Proxy will receive the corresponding number of vault shares.\n\nThe function call is as follows:\n\n`function depositERC4626(address token, uint256 amount) external returns (uint256 shares)`","contentHash":"ce859456b41c25d101cea8acf861db4d9b2079df36be9ee6d72c46f6ae166e11","addressRefs":[]},"3ea615ce-f2a9-4451-aed4-dd52c0703f5b":{"id":"3ea615ce-f2a9-4451-aed4-dd52c0703f5b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.3.2","title":"Withdraw From ERC-4626 Vault","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8985,"content":"The documents herein define the steps for a relayer to withdraw a specified amount of the underlying asset from an ERC-4626 vault to the ALM Proxy.","contentHash":"b0fc494301a22c5aacd7e45e8742053e4e6ca1a382f8669ace79fb27c6907dee","addressRefs":[]},"d545d2f1-5973-4a93-889c-9d558ff79be7":{"id":"d545d2f1-5973-4a93-889c-9d558ff79be7","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.3.2.1","title":"Call withdrawERC4626 Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8986,"content":"Only an operator with the relayer role can withdraw assets from an ERC-4626 vault. To do so, they must call the `withdrawERC4626` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to withdraw. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for withdrawal; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the withdrawal amount is within the allowed rate limit for the specified vault.\n- The contract will withdraw the specified amount from the vault, burning the necessary number of vault shares held by the ALM Proxy as part of the withdrawal process.\n- The withdrawn assets will be sent to the ALM Proxy.\n\nThe function call is as follows:\n\n`function withdrawERC4626(address token, uint256 amount) external returns (uint256 shares)`","contentHash":"318aaa8d8238d93540150141605208e2d512228ca44ab72973f9702d31068bd5","addressRefs":[]},"8e6a7981-7658-4c4e-ab87-aad8db8e215e":{"id":"8e6a7981-7658-4c4e-ab87-aad8db8e215e","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.3.3","title":"Redeem ERC-4626 Shares","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8987,"content":"The documents herein define the steps for a relayer to redeem vault shares for the underlying asset from an ERC-4626 vault, with the assets sent to the ALM Proxy.","contentHash":"2c3c0a01bfb509b9b3c8f2081f53ed39ef0c035badaffa3c291d5974aed7638d","addressRefs":[]},"5e9546bb-fbb9-4f4f-92f6-5ba41dffb41f":{"id":"5e9546bb-fbb9-4f4f-92f6-5ba41dffb41f","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.3.3.1","title":"Call redeemERC4626 Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8988,"content":"Only an operator with the relayer role can redeem vault shares for the underlying asset. To do so, they must call the `redeemERC4626` function on the Controller contract on mainnet, providing the number of shares to redeem. The address is the ALM Proxy acting as both the owner of the shares being redeemed and the receiver of the resulting assets. The operation will only succeed if the ALM Proxy holds at least the number of shares specified for redemption; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will redeem the specified number of shares from the vault, sending the resulting assets to the ALM Proxy.\n- After redemption, the contract will update the withdrawal rate limit based on the amount of assets received.\n\nThe function call is as follows:\n\n`function redeemERC4626(address token, uint256 shares) external returns (uint256 assets)`","contentHash":"32623311f5eae5fc43cd31d0d2958331ca741307cf36739b05af881688102150","addressRefs":[]},"e1a57a43-7bac-4f32-b4cc-4de7c050a89b":{"id":"e1a57a43-7bac-4f32-b4cc-4de7c050a89b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.4","title":"ERC-7540 Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8989,"content":"The documents herein define the general Obex Liquidity Layer operational procedures for interacting with ERC-7540-compliant tokenized vaults. ERC-7540 is a standard interface for vaults representing and managing multiple underlying assets within a single vault. Obex Liquidity Layer can integrate with various ERC-7540 vaults. For instance-specific parameters (such as vault addresses, asset addresses, and rate limits), refer to the relevant ERC-7540 Instance Configuration Document.","contentHash":"efcdf889a9d5a80e1449d066640901a12c1d46519ef998c3409082a5258aa4c6","addressRefs":[]},"63200ccb-fb66-4ce8-a9b9-d056f72ec60b":{"id":"63200ccb-fb66-4ce8-a9b9-d056f72ec60b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.4.1","title":"Deposit To ERC-7540 Vault","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8990,"content":"The documents herein define the steps for a relayer to request and claim deposit of assets from the ALM Proxy to an ERC-7540 vault.","contentHash":"7774d3c7628aa70e17667f0cdf5e7bf69930a59961e22efb75639f71a1b01a91","addressRefs":[]},"134e3124-3ba1-43dc-a3e6-9347416f006b":{"id":"134e3124-3ba1-43dc-a3e6-9347416f006b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.4.1.1","title":"Call requestDepositERC7540 Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8991,"content":"Only an operator with the relayer role can request a deposit into an ERC-7540 vault. To do so, they must call the `requestDepositERC7540` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to deposit. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for deposit; otherwise, the transaction will revert. The Rate Limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the deposit amount is within the allowed rate limit for the specified vault.\n- The contract will approve the vault to spend the underlying asset from the ALM Proxy. The approval and deposit are both performed from the ALM Proxy address.\n- The contract will submit a deposit request to the vault. Shares will not be received immediately; they must be claimed in a separate step after the vault processes the deposit.\n\nThe function call is as follows:\n\n`function requestDepositERC7540(address token, uint256 amount) external`","contentHash":"d17bb232619cd4c715d0bcf131e6bc8d1a9715d9e667494479645ccd38394999","addressRefs":[]},"41f68822-0f26-4fb2-a805-587fc08abb3f":{"id":"41f68822-0f26-4fb2-a805-587fc08abb3f","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.4.1.2","title":"Call claimDepositERC7540 Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8992,"content":"Only an operator with the relayer role can claim shares from an ERC-7540 vault after a deposit request. To do so, they must call the `claimDepositERC7540` function on the Controller contract on mainnet, providing the vault token address. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will determine the maximum number of shares that can be claimed by the ALM Proxy.\n- The contract will claim the shares from the vault, and the ALM Proxy will receive the corresponding number of vault shares.\n\nThe function call is as follows:\n\n`function claimDepositERC7540(address token) external`","contentHash":"cf9133aff1f7250ddcc482b8ca1ac5626e3b1c19496455585148659e91593e03","addressRefs":[]},"6765a298-8ea7-4b1d-8d37-b3ccb069e12b":{"id":"6765a298-8ea7-4b1d-8d37-b3ccb069e12b","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.4.2","title":"Redeem From ERC-7540 Vault","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8993,"content":"The documents herein define the steps for a relayer to request and redeem vault shares for the underlying asset from an ERC-7540 vault, with the assets sent to the ALM Proxy.","contentHash":"0405683434d72ead3b6f43e52f1ee95b114f0b3fc58535114ce95cedd58d400f","addressRefs":[]},"bd723808-6f03-41ed-9b19-72672d38dc36":{"id":"bd723808-6f03-41ed-9b19-72672d38dc36","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.4.2.1","title":"Call requestRedeemERC7540 Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8994,"content":"Only an operator with the relayer role can request the redemption of shares from an ERC-7540 vault. To do so, they must call the `requestRedeemERC7540` function on the Controller contract on mainnet, providing the vault token address and the number of shares to redeem. The rate limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the redemption amount is within the allowed rate limit for the specified vault.\n- The contract will submit a redemption request to the vault. Assets will not be received immediately; they must be claimed in a separate step after the vault processes the redemption.\n\nThe function call is as follows:\n\n`function requestRedeemERC7540(address token, uint256 amount) external`","contentHash":"77cbcc6045b6a4abbab0211e3cbf383430e14fbda5a8d961e908aa886582ef4e","addressRefs":[]},"08474241-fee8-4ca3-95e8-564bd6676ea1":{"id":"08474241-fee8-4ca3-95e8-564bd6676ea1","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.4.2.2","title":"Call claimRedeemERC7540 Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8995,"content":"Only an operator with the relayer role can claim assets from an ERC-7540 vault after a redemption request. To do so, they must call the `claimRedeemERC7540` function on the Controller contract on mainnet, providing the vault token address. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will determine the maximum amount of assets that can be claimed by the ALM Proxy.\n- The contract will claim the assets from the vault, and the ALM Proxy will receive the corresponding amount of underlying assets.\n\nThe function call is as follows:\n\n`function claimRedeemERC7540(address token) external`","contentHash":"5e009dff8fc6a052984c70afd928dea021c7163bba2ae9249ad9d17a3b1a0b34","addressRefs":[]},"df1e38f3-5954-44d6-8500-6d26f03cc8da":{"id":"df1e38f3-5954-44d6-8500-6d26f03cc8da","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.5","title":"Dai / USDS Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8996,"content":"The documents herein define the swap operations between Dai and USDS.","contentHash":"f36ef24d14bc80de5bc10143703d7ecf159839ce3772551c0fa1e39d475d5a72","addressRefs":[]},"22b124dd-3e9d-4439-bc4e-2993f2c267dd":{"id":"22b124dd-3e9d-4439-bc4e-2993f2c267dd","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.5.1","title":"Swap USDS to Dai","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8997,"content":"The documents herein define a series of operations for an operator to `swap` USDS to Dai.","contentHash":"fb2a18a3c900f2b88037f665dc833575360840e94dd7a655e1c5cd7b4c9e186e","addressRefs":[]},"ed445f2b-9211-46fe-b79a-6e70cac7fec7":{"id":"ed445f2b-9211-46fe-b79a-6e70cac7fec7","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.5.1.1","title":"Call swapUSDSToDAI Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8998,"content":"Only an operator with the relayer role can swap USDS to Dai. To do so, they must call the `swapUSDSToDAI` function on the Controller contract on mainnet, providing the usdsAmount. The operation will only succeed if the Proxy holds enough USDS for the swap; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will approve the DaiUsds migrator to spend the specified USDS amount from the Proxy.\n- The contract will swap USDS to Dai at a 1:1 ratio by calling the `usdsToDai` function on the migrator, sending the resulting DAI to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDSToDAI(uint256 usdsAmount) external`","contentHash":"58fd4d26eca7cc4ff164cfd9ac0f85e0bb19968d20c147bbf84e68018627682a","addressRefs":[]},"d536a9fd-fa93-4909-ab75-17f3c4ccce3a":{"id":"d536a9fd-fa93-4909-ab75-17f3c4ccce3a","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.5.2","title":"Swap Dai to USDS","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":8999,"content":"The documents herein define a series of operations for an operator to `swap` Dai to USDS.","contentHash":"72782112e31cf3bf9ac4c1820cf0b6beee560bd08bc8e2011301e59217763bb5","addressRefs":[]},"3941f682-b9ae-483e-93a5-4c756388434e":{"id":"3941f682-b9ae-483e-93a5-4c756388434e","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.5.2.1","title":"Call swapDAIToUSDS Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9000,"content":"Only an operator with the relayer role can swap Dai to USDS. To do so, they must call the `swapDAIToUSDS` function on the Controller contract on mainnet, providing the daiAmount. The operation will only succeed if the Proxy holds enough Dai for the swap; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will approve the DaiUsds migrator to spend the specified Dai amount from the Proxy.\n- The contract will swap Dai to USDS at a 1:1 ratio by calling the `daiToUsds` function on the migrator, sending the resulting USDS to the proxy.\n\nThe function call is as follows:\n\n`function swapDAIToUSDS(uint256 daiAmount) external`","contentHash":"221a10f1dacee5cda6eb6b272622a64a781fe5f341cd0ad5d1d549ef8208fc38","addressRefs":[]},"8666d408-4c3a-4646-8cbf-d0752167dcd6":{"id":"8666d408-4c3a-4646-8cbf-d0752167dcd6","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.6","title":"PSM Functions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9001,"content":"The documents herein define the swap operations performed by the Obex Liquidity Layer in the PSM.","contentHash":"34ec863f90ec94bc33f05ea1d84767059fac70defe7806858a1ae28ffb6c4de3","addressRefs":[]},"43917647-67dc-4981-8048-522c19b4caf0":{"id":"43917647-67dc-4981-8048-522c19b4caf0","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.6.1","title":"Swap USDS to USDC","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9002,"content":"The documents herein define a series of operations for an operator to `swap` USDS to USDC through the PSM.","contentHash":"564fc251dbabe1de4723b87aa7179a9f9f901ef1b48e8c75549e98fefb798c1b","addressRefs":[]},"0ec7c5be-32a2-4d3b-b856-71face6612a9":{"id":"0ec7c5be-32a2-4d3b-b856-71face6612a9","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.6.1.1","title":"Call swapUSDSToUSDC Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9003,"content":"Only an operator with the relayer role can swap USDS to USDC via the PSM. To do so, they must call the `swapUSDSToUSDC` function on the Controller contract on mainnet, providing the usdcAmount (denominated in 1e6 precision to match PSM USDC handling). The operation will only succeed if the ALM Proxy holds at least the equivalent amount of USDS for the swap; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for swaps. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the swap amount is within the allowed rate limit (LIMIT_USDS_TO_USDC) for the PSM.\n- The contract will convert the USDC amount to an 18-decimal format using psmTo18ConversionFactor.\n- The contract will approve the daiUsds contract to spend the converted amount from the ALM Proxy.\n- The contract will swap USDS to Dai at a 1:1 ratio via daiUsds, sending Dai to the proxy.\n- The contract will approve the PSM to spend the Dai.\n- The contract will swap Dai to USDC at a 1:1 ratio with no fee via psm.buyGemNoFee, sending USDC to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDSToUSDC(uint256 usdcAmount) external`","contentHash":"cc3728b1904efa771e6576a8833a6096a44aa7d0b21a635e7cf570db93ff37ff","addressRefs":[]},"17675b49-5767-47de-9ccf-e324b7bebec5":{"id":"17675b49-5767-47de-9ccf-e324b7bebec5","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.6.2","title":"Swap USDC To USDS","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9004,"content":"The documents herein define a series of operations for an operator to `swap` USDC to USDS through the PSM.","contentHash":"f55bbceca04d743a7ae5c9c46fa9d3d34fd14dab41a5f282da781a788be9ba83","addressRefs":[]},"f0117433-4568-4b4b-bed6-fce75f85939a":{"id":"f0117433-4568-4b4b-bed6-fce75f85939a","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.6.2.1","title":"Call swapUSDCToUSDS Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9005,"content":"Only an operator with the relayer role can swap USDC to USDS via the PSM. To do so, they must call the `swapUSDCToUSDS` function on the Controller contract on mainnet, providing the usdcAmount (denominated in 1e6 precision to match PSM USDC handling). The operation will only succeed if the ALM Proxy holds at least the amount of USDC specified for the swap; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for swaps. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the swap amount is within the allowed rate limit (LIMIT_USDC_TO_USDS) for the PSM.\n- The contract will approve the PSM to spend the USDC from the ALM Proxy.\n- The contract will calculate the swap limit per transaction based on the Dai balance held by the PSM, converting with psmTo18ConversionFactor.\n- If the usdcAmount is less than or equal to the limit, the contract will perform a direct swap of USDC to Dai.\n- If the usdcAmount exceeds the limit, the contract will split the swap into multiple smaller swaps: refill the PSM with Dai via psm.fill, recalculate the limit, swap the maximum allowed amount, update the remaining amount, and repeat until complete (reverting with \"DssLitePsm/nothing-to-fill\" if PSM cannot be filled).\n- The contract will convert the USDC amount to a Dai amount, accounting for token decimal differences.\n- The contract will approve the daiUsds contract to spend the Dai amount from the ALM Proxy.\n- The contract will swap Dai to USDS at a 1:1 ratio via daiUsds, sending USDS to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDCToUSDS(uint256 usdcAmount) external`","contentHash":"373dca92f7fe2552f8fbbda1918df1e55c1556dfb36f61eb8b30f06df23aa0bc","addressRefs":[]},"7f1746e3-9bc8-467f-97b8-72e4ee51ebfc":{"id":"7f1746e3-9bc8-467f-97b8-72e4ee51ebfc","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.6.3","title":"Transfer Token Via LayerZero","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9006,"content":"The documents herein define the steps for a relayer to `transfer` a token via LayerZero to a destination endpoint, with the assets sent according to the configured recipient.","contentHash":"209ac1740bb885c01bcf8b9c84111d5989e7232964c2eb7017bd745b6976136c","addressRefs":[]},"04a8ecfb-e8b5-4994-b4f1-1fe99efd8dcd":{"id":"04a8ecfb-e8b5-4994-b4f1-1fe99efd8dcd","doc_no":"A.6.1.1.5.2.6.1.2.2.1.2.1.2.6.3.1","title":"Call transferTokenLayerZero Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9007,"content":"Only an operator with the relayer role can transfer tokens via LayerZero. To do so, they must call the `transferTokenLayerZero` function on the Controller contract on mainnet, providing the oftAddress, amount, and destinationEndpointId (payable for native fees). The operation will only succeed if the ALM Proxy holds sufficient tokens and fees; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the transfer amount is within the allowed rate limit (built from LIMIT_LAYERZERO_TRANSFER, oftAddress, and destinationEndpointId).\n- If approval is required, the contract will approve the token for the oftAddress.\n- The contract will build LayerZero send options and a SendParam struct with destination details, amount, and recipient from layerZeroRecipients.\n- The contract will quote the OFT receipt to set the minimum amount received.\n- The contract will quote the messaging fee and execute the send via proxy.doCallWithValue, passing the fee value.\n\nThe function call is as follows:\n\n`function transferTokenLayerZero(address oftAddress, uint256 amount, uint32  destinationEndpointId) external payable`","contentHash":"a35fb0891772ab21f004a3c2d9997a1f57c3fe654845878902d240d60bc33274","addressRefs":[]},"73da45c9-78eb-49f3-a1d5-593780e9d362":{"id":"73da45c9-78eb-49f3-a1d5-593780e9d362","doc_no":"A.6.1.1.5.2.6.1.2.2.1.3","title":"Rate Limit Management","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9008,"content":"The documents herein define the protocol for querying, setting, and adjusting `RateLimits` for Instances using their `RateLimitID`s. The Rate Limits must be maintained in line with Obex's strategy, market conditions, and security considerations.","contentHash":"c45bc6ce9ce699dffe531eb1185e5b3729a26c7a11c1efe5645b4fce2b2914d4","addressRefs":[]},"716b493e-d102-47c8-8f87-bcb1c809c8ee":{"id":"716b493e-d102-47c8-8f87-bcb1c809c8ee","doc_no":"A.6.1.1.5.2.6.1.2.2.1.3.1","title":"Get Rate Limit Data","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9009,"content":"Anyone can query the full rate limit data for a specific key. Calling this function will carry out the following actions:\n\n- The contract will return the stored RateLimitData struct from the _data mapping for the key.\n\nThe function call is as follows:\n\n`function getRateLimitData(bytes32 key) external override view returns (RateLimitData memory)`","contentHash":"61aaead98caab9ae4da7ca412908ffa156e91b1a5fe8e1feca9babb5c82ac1fc","addressRefs":[]},"993bbc35-1692-4c1b-87b2-de5997e90bf5":{"id":"993bbc35-1692-4c1b-87b2-de5997e90bf5","doc_no":"A.6.1.1.5.2.6.1.2.2.1.3.2","title":"Set Rate Limit Data","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9010,"content":"Only an operator with the admin role is able to set or update rate limit data for a specific key, including maxAmount, slope, and historical values. There are two overloads for flexibility. Calling these functions will carry out the following actions:\n\n- The contract will require that lastAmount is less than or equal to maxAmount, reverting with \"RateLimits/invalid-lastAmount\" if not.\n- The contract will require that lastUpdated is less than or equal to the current block timestamp, reverting with \"RateLimits/invalid-lastUpdated\" if not.\n- The contract will store the provided data in the _data mapping as a RateLimitData struct.\n- The contract will emit a RateLimitDataSet event with the key and provided values.\n\nThe function calls are as follows:\n\n```\nfunction setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope, uint256 lastAmount, uint256 lastUpdated) public override onlyRole(DEFAULT_ADMIN_ROLE)\n\nfunction setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope) external override\n```","contentHash":"a9463875659a3ac6b66961118d94871545e79f20dea7a3671d7274e826248aa1","addressRefs":[]},"37aed332-50c8-4392-91be-095bd13139d1":{"id":"37aed332-50c8-4392-91be-095bd13139d1","doc_no":"A.6.1.1.5.2.6.1.2.2.1.3.3","title":"Set Unlimited Rate Limit Data","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9011,"content":"Only an operator with the admin role is able to set unlimited rate limit data for a specific key by configuring it with maximum values. Calling this function will carry out the following actions:\n\n- The contract will call setRateLimitData internally with type(uint256).max for maxAmount and lastAmount, 0 for slope, and the current block timestamp for lastUpdated.\n\nThe function call is as follows:\n\n`function setUnlimitedRateLimitData(bytes32 key) external override`","contentHash":"8d3f02b7a0c3f317c28a031cc58bcd6f8f28989b8f8fe5ce7d7e718bdfc42047","addressRefs":[]},"f629bb8f-afb2-4bfc-b7fa-3f5fbaa2c2f9":{"id":"f629bb8f-afb2-4bfc-b7fa-3f5fbaa2c2f9","doc_no":"A.6.1.1.5.2.6.1.2.2.1.3.4","title":"Get Current Rate Limit","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9012,"content":"Anyone can query the current rate limit value for a specific key, accounting for time-based slope accrual. Calling this function will carry out the following actions:\n\n- The contract will retrieve the RateLimitData for the key from the _data mapping.\n- If maxAmount is type(uint256).max (unlimited case), the contract will return type(uint256).max.\n- Otherwise, the contract will calculate and return the minimum of (slope * time elapsed since lastUpdated + lastAmount) and maxAmount.\n\nThe function call is as follows:\n\n`function getCurrentRateLimit(bytes32 key) public override view returns (uint256)`","contentHash":"4a41715aa485c085b94bc4050e85eaabdb529ba656d1185b8b57aa766ff36ad6","addressRefs":[]},"2fc640dc-1f48-4167-a700-cb54f2cb1097":{"id":"2fc640dc-1f48-4167-a700-cb54f2cb1097","doc_no":"A.6.1.1.5.2.6.1.2.2.1.3.5","title":"Trigger Rate Limit Decrease","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9013,"content":"Only an operator with the controller role can trigger a decrease in the rate limit for a specific key by a given amount. Calling this function will carry out the following actions:\n\n- The contract will retrieve the RateLimitData storage for the key from the data mapping.\n- The contract will require that maxAmount is greater than 0, reverting with \"RateLimits/zero-maxAmount\" if not.\n- If maxAmount is type(uint256).max (unlimited case), the contract will return type(uint256).max without changes.\n- The contract will calculate the currentRateLimit using getCurrentRateLimit.\n- The contract will require that amountToDecrease is less than or equal to currentRateLimit, reverting with \"RateLimits/rate-limit-exceeded\" if not.\n- The contract will update lastAmount to currentRateLimit minus amountToDecrease and set lastUpdated to the current block timestamp.\n- The contract will emit a RateLimitDecreaseTriggered event with the key, amountToDecrease, currentRateLimit, and newLimit.\n- The contract will return the newLimit.\n\nThe function call is as follows:\n\n`function triggerRateLimitDecrease(bytes32 key, uint256 amountToDecrease) external override onlyRole(CONTROLLER) returns (uint256 newLimit)`","contentHash":"90daece828f45dc63307a3e767f044524efeed8f45db7653932d890c4416f626","addressRefs":[]},"2dde3f2b-925d-42a4-9fe1-0cb5bfd86855":{"id":"2dde3f2b-925d-42a4-9fe1-0cb5bfd86855","doc_no":"A.6.1.1.5.2.6.1.2.2.1.4","title":"Instance Lifecycle Management","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9014,"content":"The documents herein define processes for invoking (onboarding) new Obex Liquidity Layer Instances and offboarding existing ones. This process will be specified in a future iteration of the Obex Artifact.","contentHash":"856be0bf6b8a813559cf97d07e4c1b2f172dffc1b04f6931409243e2c2b32f59","addressRefs":[]},"4e238661-718b-44ec-8473-bad60d76074d":{"id":"4e238661-718b-44ec-8473-bad60d76074d","doc_no":"A.6.1.1.5.2.6.1.2.2.1.5","title":"Upgrading Controller","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9015,"content":"The documents herein define the process for deploying new Controller contracts. This process will be specified in a future iteration of the Obex Artifact.","contentHash":"5868e143ecf1d9d69786d240ac7150da493d0dfc16a40f40e1b6946590d7633a","addressRefs":[]},"7fc9e39e-4f3d-435a-84af-7fc74c449ce0":{"id":"7fc9e39e-4f3d-435a-84af-7fc74c449ce0","doc_no":"A.6.1.1.5.2.6.1.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9016,"content":"The documents herein define the process for non-routine ongoing management of the Obex Liquidity Layer and its active Instances.","contentHash":"45fa0ecb33cd2eba86f664ac1aa73e9769047047e03ad5ff52c0c6dee141f1a0","addressRefs":[]},"d99e4cb6-1c6c-4562-948b-c2ac4ea66253":{"id":"d99e4cb6-1c6c-4562-948b-c2ac4ea66253","doc_no":"A.6.1.1.5.2.6.1.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9017,"content":"The documents herein define all the possible actions that can be taken in case of an emergency within Obex Liquidity Layer operations.","contentHash":"141100506c17e8d46326971004642723141699ad9943ac57217c6f3c4b9e62e3","addressRefs":[]},"15c966fc-e579-4277-abb0-6f0b9ad5cbce":{"id":"15c966fc-e579-4277-abb0-6f0b9ad5cbce","doc_no":"A.6.1.1.5.2.6.1.2.2.3.1","title":"Remove Compromised Relayer As Freezer","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9018,"content":"In the event of a compromised Relayer, the `FREEZER_ROLE` can call the function to `removeRelayer` from the Controller contract. Only an operator with the freezer role can remove a relayer. To do so, they must call the `removeRelayer` function on the Controller contract on mainnet, providing the compromised relayer’s address. Calling this function will carry out the following actions:\n\n- The contract will confirm the caller holds the freezer role. If the caller does not have the freezer role, the transaction will revert.\n- The contract will revoke the relayer role from the specified address.\n- The contract will emit a `RelayerRemoved(relayer)` event.\n\nThe function call is as follows:\n\n`function removeRelayer(address relayer) external`","contentHash":"8ebeac10750fbcf9c40090f2a5d9a3266ffd6059753fd131ab44c8fe4b8aad1f","addressRefs":[]},"10597c85-6ce2-4364-a83b-e2d3c93c45c7":{"id":"10597c85-6ce2-4364-a83b-e2d3c93c45c7","doc_no":"A.6.1.1.5.2.6.1.2.2.3.2","title":"Redeem All Mainnet Positions","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9019,"content":"The documents herein define the actions that should be performed by an operator if there is a need to recover the liquidity from Mainnet Protocols and centralize it in the Mainnet Obex ALM Proxy.","contentHash":"8649ced6c676e140312c3af733701a0161c3c71455800e4b9383f51c5e4018d4","addressRefs":[]},"6078cd75-f853-49ca-b7c1-eaab4ef85c72":{"id":"6078cd75-f853-49ca-b7c1-eaab4ef85c72","doc_no":"A.6.1.1.5.2.6.1.2.2.3.2.1","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9020,"content":"In order to withdraw all ERC-4626 balances, the operator must call the `redeemERC4626` function.\n\nThe function call is as follows:\n\n`function redeemERC4626(address(token), token.balanceOf(address(proxy)))`\n\nFor more detailed instructions on the code to execute this, see [A.6.1.1.5.2.6.1.2.2.1.2.1.2.3 - ERC-4626 Functions](08d30ec2-c343-4176-aded-dce33e76d69c).","contentHash":"57bb6d17185b1ba1c1b0ba69e1be5af4fffba40cb831d165ec6702a84d456c3f","addressRefs":[]},"b93c5c32-642e-4448-9ebd-c908dee78d46":{"id":"b93c5c32-642e-4448-9ebd-c908dee78d46","doc_no":"A.6.1.1.5.2.6.1.2.2.3.3","title":"USDC To USDS Swap Action","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9021,"content":"This document defines the action that should be performed by an operator if there is a need to centralize all recovered liquidity in USDS. The operator must call the `swapUSDCToUSDS` function.\n\nThe function call is as follows:\n\n`function swapUSDCToUSDS(usdc.balanceOf(address(proxy))`\n\nFor more detailed instructions on the code to execute this see [A.6.1.1.5.2.6.1.2.2.1.2.1.2.6.2 - Swap USDC To USDS](17675b49-5767-47de-9ccf-e324b7bebec5).","contentHash":"54713ce90b80ff2e70d7ea1ab7213cf9583799de4485ed0c11141e199ac61703","addressRefs":[]},"3304ecba-6dad-45af-886e-878648d2abb8":{"id":"3304ecba-6dad-45af-886e-878648d2abb8","doc_no":"A.6.1.1.5.2.6.1.2.2.3.4","title":"USDS Burn Action","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9022,"content":"This document defines the action that should be performed if there is a need to repay and then burn Obex's USDS debt. The operator must call the `burnUSDS` function.\n\nThe function call is as follows:\n\n`function burnUSDS(usds.balanceOf(address(proxy))`\n\nMore detailed instructions on the code to execute this, see [A.6.1.1.5.2.6.1.2.2.1.2.1.2.1.2 - Burn USDS](1e27b007-ed34-4c15-9116-d62145572dce).","contentHash":"04ec127c55316592f2b285d4dd573dcf18b0e25e0b65d7fdd594e9adfc282dff","addressRefs":[]},"5611a719-923b-4d95-b246-5bc788d55307":{"id":"5611a719-923b-4d95-b246-5bc788d55307","doc_no":"A.6.1.1.5.2.6.1.2.3","title":"Allocation Strategy","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9023,"content":"In the future, additional logic will be added herein regarding the strategy by which capital is allocated between different Instances of the Obex Liquidity Layer.","contentHash":"d9994ef835a1cd6cafe8f09feb0354080324e90151411c827bec00e8262a2a70","addressRefs":[]},"ccde7679-912d-403f-aad1-f9a56c8e3387":{"id":"ccde7679-912d-403f-aad1-f9a56c8e3387","doc_no":"A.6.1.1.5.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9024,"content":"The Instances of the Obex Liquidity Layer with `Active` Status are stored herein. The `RRC Framework Full Implementation Coverage` status defines whether the Instance Financial RRC is calculated based on a fully implemented risk model (see [A.3.2.1.1.4.3.1 - Fully Implemented Risk Models](419a1d00-fbae-4d26-bd47-8f57677d8001)) or a pending risk model (see [A.3.2.1.1.4.3.2 - Pending Risk Models](81ca88bf-3f6a-4d10-a3e2-d47cf6636d7d)). If the Instance Financial RRC is calculated based on a fully implemented risk model the status is `Covered`. If the Instance Financial RRC is calculated based on a pending risk model the status is `Pending`.","contentHash":"eaed7377178b1ae28bafe9b6734dbfd3f16af68e13dbc46671b2a69b7723cc1d","addressRefs":[]},"a10f4c25-6281-42e5-8247-6ac5cac9f850":{"id":"a10f4c25-6281-42e5-8247-6ac5cac9f850","doc_no":"A.6.1.1.5.2.6.1.3.1","title":"Ethereum Mainnet Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9025,"content":"The Ethereum Mainnet Instances of the Obex Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"cef2e18a652ab41e119e2a5b9d0c459284c089ab9f0044be547d74de094c4fb6","addressRefs":[]},"a03f7eb7-4f1f-441c-98ba-41c87f482186":{"id":"a03f7eb7-4f1f-441c-98ba-41c87f482186","doc_no":"A.6.1.1.5.2.6.1.3.1.1","title":"Maple","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9026,"content":"The Ethereum Mainnet Instances of the Maple Protocol with `Active` Status are stored herein.","contentHash":"8fc7c8ba100ab5d1abcce02e163a69acc6af84061a97d576f93c43fc63481e53","addressRefs":[]},"7488a14c-2464-4649-b476-48ee93bb438f":{"id":"7488a14c-2464-4649-b476-48ee93bb438f","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1","title":"Ethereum Mainnet - Maple USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9027,"content":"The documents herein contain the Instance Configuration Document for the Maple USDC Instance.","contentHash":"1f0b8dcfe605b4906709f0bad210660334f119702f681e347f3f6e7d7567a5ed","addressRefs":[]},"28fa701f-7d0a-45e6-9977-e28bfd32fe0e":{"id":"28fa701f-7d0a-45e6-9977-e28bfd32fe0e","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9028,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"82cb8c2b-c551-4ea0-bec2-6afa0d41ab8d":{"id":"82cb8c2b-c551-4ea0-bec2-6afa0d41ab8d","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9029,"content":"The documents herein define the parameters of the Maple USDC Instance of the Allocation System Primitive.","contentHash":"bc52815c6a6edbb05f61c0586baf40df733aaa345107b7fcd1ac535777faefd7","addressRefs":[]},"87ea484a-cb48-46dc-b97b-ab79e59420bf":{"id":"87ea484a-cb48-46dc-b97b-ab79e59420bf","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9030,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"8b3a0a62-f92e-43cd-9791-8eab8c36ffe4":{"id":"8b3a0a62-f92e-43cd-9791-8eab8c36ffe4","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9031,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"c953c251-42d5-4dcd-9952-6329ed7179f2":{"id":"c953c251-42d5-4dcd-9952-6329ed7179f2","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9032,"content":"Maple","contentHash":"187c93774dbd4c674ecaf745f0c304bb494ccfca31cd88c028251f97f09569c5","addressRefs":[]},"7d83e07d-c05f-4917-97ef-7bca6a6cf184":{"id":"7d83e07d-c05f-4917-97ef-7bca6a6cf184","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.1.3","title":"Asset Supplied By Obex Liquidity Layer","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9033,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"0c1296a7-a091-4753-8851-3eb2df18cc33":{"id":"0c1296a7-a091-4753-8851-3eb2df18cc33","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9034,"content":"syrupUSDC","contentHash":"3b50b2203f4915b0b7b3098fc5d9205e27421a900c9bf60f5fe7d484e2a25003","addressRefs":[]},"81a36b20-bf42-40eb-b47f-c5859529a77c":{"id":"81a36b20-bf42-40eb-b47f-c5859529a77c","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9035,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"85a64942-705d-4079-a265-2510ae4310f7":{"id":"85a64942-705d-4079-a265-2510ae4310f7","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9036,"content":"`0x80ac24aA929eaF5013f6436cdA2a7ba190f5Cc0b`","contentHash":"c9da76a92fdbedaeaebc89f6ae1550989ebcbf6b96f68777626b48b5da9dfbce","addressRefs":["0x80ac24aa929eaf5013f6436cda2a7ba190f5cc0b"]},"e9a1b7f7-df7c-4b9c-83d1-96fc3b109089":{"id":"e9a1b7f7-df7c-4b9c-83d1-96fc3b109089","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9037,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"d2d46842-e9dd-4f88-bfa5-5e947381f70b":{"id":"d2d46842-e9dd-4f88-bfa5-5e947381f70b","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.3","title":"RateLimitIDs","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9038,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow will be specified in a future iteration of the Obex Artifact.","contentHash":"ee255c18d74608844b684042b1b67ee3fc199d5855d74279591ad5c1f2226cc7","addressRefs":[]},"97344456-e215-42e5-a149-89f0276e1b4c":{"id":"97344456-e215-42e5-a149-89f0276e1b4c","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9039,"content":"The inflow RateLimitID is: `0x99a69e57b2f387f999d6adff6eb2e707b59fdb54f06ca6211b4f20956e9bfe10`","contentHash":"1fcebf3d37fbcb31666be37de75a10dc1905b221595feddede05658d789c9047","addressRefs":[]},"c4e18b43-5009-4c77-8781-bfc053d2c606":{"id":"c4e18b43-5009-4c77-8781-bfc053d2c606","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9040,"content":"The outflow RateLimitID is: `0x64e6fd9d694640eebeeefc7b5abe32ef09bbabaa3d4e60221461d05a9577dc57`","contentHash":"4871287b6111e508f3c17951524f850991555573c78bf6dd8176dbbd81015769","addressRefs":[]},"db184982-3dca-493b-b2a9-640196443cd8":{"id":"db184982-3dca-493b-b2a9-640196443cd8","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9041,"content":"The current `maxAmount` and `slope` for this conduit’s inflow/outflow are defined in the documents herein.","contentHash":"e257ac0d69a758b486e39d6f2af16b5828cc7723f21348f1e24b02a88a2084b7","addressRefs":[]},"3776ec7d-668c-496d-aaa7-094ba92e496f":{"id":"3776ec7d-668c-496d-aaa7-094ba92e496f","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9042,"content":"The deposit rate limits are:\n\n- `maxAmount`: 100,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"bc10c92bd20563afabf4f1812c0d9078b5b3ae1f853a816d199d2e0e9b359d71","addressRefs":[]},"b29ac1d6-4cbd-46db-b77c-2f02d9705936":{"id":"b29ac1d6-4cbd-46db-b77c-2f02d9705936","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9043,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"b7dff5a9-125e-4ee1-9977-4698b5442b26":{"id":"b7dff5a9-125e-4ee1-9977-4698b5442b26","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9044,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"12bfd1a4-fe27-4a7d-8c1e-d0541c690066":{"id":"12bfd1a4-fe27-4a7d-8c1e-d0541c690066","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9045,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Obex Liquidity Layer processes.","contentHash":"998cb659c3cea9c93c5dee9aa39c39931bf1071372652e560d7248cf82e95d10","addressRefs":[]},"6fb19cf7-516c-4de4-89b9-02288053f905":{"id":"6fb19cf7-516c-4de4-89b9-02288053f905","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.3.1","title":"Redeem Maple Shares","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9046,"content":"The documents herein define the steps for a relayer to redeem vault shares from Maple.","contentHash":"33f07984a7023381083285874a35539725587f30cbc80fc5ee5304df3bb57949","addressRefs":[]},"fd047e05-3239-434b-a5d8-81cd72ada783":{"id":"fd047e05-3239-434b-a5d8-81cd72ada783","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.3.1.1","title":"Call RequestMapleRedemption Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9047,"content":"Only an operator with the relayer role can request the redemption of shares from Maple. To do so, they must call the `requestMapleRedemption` function on the Controller contract on mainnet, providing the Maple token address and the number of shares to request. All Maple redemption operations are performed on behalf of the ALM Proxy and the destination address is always set to the proxy by the contract. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the redemption amount is within the allowed rate limit for the specified vault and decrease the rate limit for the redemption amount.\n- The contract will submit a redemption request to the vault. Assets will not be received immediately; they must be claimed in a separate step after the vault processes the redemption.\n\nThe function call is as follows:\n\n`function requestMapleRedemption(address mapleToken, uint256 shares) external`","contentHash":"2ef622847b78f9352bbf084a0e712d677237271d1e5c603dfd0bdeca1697eae1","addressRefs":[]},"7378e3fb-3c6a-4ea4-8e01-c6b84658944d":{"id":"7378e3fb-3c6a-4ea4-8e01-c6b84658944d","doc_no":"A.6.1.1.5.2.6.1.3.1.1.1.3.1.2","title":"Call CancelMapleRedemption Function","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9048,"content":"Only an operator with the relayer role can cancel a previously requested redemption of shares from Maple. To do so, they must call the `cancelMapleRedemption` function on the Controller contract on mainnet, providing the Maple token address and the number of shares to cancel. All Maple cancellations of redemption operations are performed on behalf of the ALM Proxy. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will check that a rate limit exists for the asset. If no rate limit exists the transaction will revert.\n- The contract will submit a cancellation request to the vault, removing the specified number of shares from the pending redemption.\n\nThe function call is as follows:\n\n`function cancelMapleRedemption(address mapleToken, uint256 shares) external`","contentHash":"b78ad2e77a36fcde5dd0e9ec8080438f123f68e3fd8211161871a918703db8e7","addressRefs":[]},"6b16b0d6-a5a1-44da-a95d-e62d38a35ade":{"id":"6b16b0d6-a5a1-44da-a95d-e62d38a35ade","doc_no":"A.6.1.1.5.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9049,"content":"The Instances of the Obex Liquidity Layer with `Completed` Status are stored herein.","contentHash":"a35c283b203804a4a0a68fdb1aba7f9dcd5fc2eeebf437be04ed4818a3dcc332","addressRefs":[]},"ca2c0cd1-73e3-49f1-b415-65e5f200b097":{"id":"ca2c0cd1-73e3-49f1-b415-65e5f200b097","doc_no":"A.6.1.1.5.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9050,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.6.1.3 - Active Instances](ccde7679-912d-403f-aad1-f9a56c8e3387).","contentHash":"ceaa340c5ec48baf6c95c993174c57b31cd35b7d8a103da385fdcdf029efe8cf","addressRefs":[]},"473d0f9e-a5dc-48ee-84b9-a48cd2b6f215":{"id":"473d0f9e-a5dc-48ee-84b9-a48cd2b6f215","doc_no":"A.6.1.1.5.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9051,"content":"The documents herein contain all data and specifications for Obex's Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"aaef5199be47171d4a8512fd32e3604325031f8a19288b71fc27075e33ef2595","addressRefs":[]},"7c5c39de-a531-42a7-8b74-e8e6ffeb2bc3":{"id":"7c5c39de-a531-42a7-8b74-e8e6ffeb2bc3","doc_no":"A.6.1.1.5.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9052,"content":"The documents herein organize all base information relevant to Obex's usage of the Junior Risk Capital Rental Primitive.","contentHash":"493a450467210c3588dfbccf153f4398ca96cc8035c2488d3f208c60b057a574","addressRefs":[]},"c3a0f75a-d418-411a-bc8e-ccde6aa938b1":{"id":"c3a0f75a-d418-411a-bc8e-ccde6aa938b1","doc_no":"A.6.1.1.5.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9053,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"5f9e7e17-d7c4-4c72-9d0f-a2b58de3bbe6":{"id":"5f9e7e17-d7c4-4c72-9d0f-a2b58de3bbe6","doc_no":"A.6.1.1.5.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9054,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"51f16355-24cf-463f-9603-154da3fcb1b3":{"id":"51f16355-24cf-463f-9603-154da3fcb1b3","doc_no":"A.6.1.1.5.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9055,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"b60d8075-b908-4086-9bb0-0d8a609b1dd6":{"id":"b60d8075-b908-4086-9bb0-0d8a609b1dd6","doc_no":"A.6.1.1.5.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9056,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.6.2.1.2 - Active Instances Directory](5f9e7e17-d7c4-4c72-9d0f-a2b58de3bbe6), whereas failed Invocations are Archived in [A.6.1.1.5.2.6.2.1.5 - Hub Data Repository](a5fea5f5-f6b2-47e4-9ef5-bb23ba08921d).","contentHash":"5e966f8466ca69006bc4f230bb9c208274c3fde29e8145f1d2a4eaf7dc46f2b7","addressRefs":[]},"a5fea5f5-f6b2-47e4-9ef5-bb23ba08921d":{"id":"a5fea5f5-f6b2-47e4-9ef5-bb23ba08921d","doc_no":"A.6.1.1.5.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9057,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ecd92a2e-9c67-4fb0-b3cf-3ad63cebf8a5":{"id":"ecd92a2e-9c67-4fb0-b3cf-3ad63cebf8a5","doc_no":"A.6.1.1.5.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9058,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"6e6d714e-4700-4aa8-bd61-6e8f012df6d4":{"id":"6e6d714e-4700-4aa8-bd61-6e8f012df6d4","doc_no":"A.6.1.1.5.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9059,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"fd2cdc13-4035-4c91-b17c-7d1d1d5c5b7b":{"id":"fd2cdc13-4035-4c91-b17c-7d1d1d5c5b7b","doc_no":"A.6.1.1.5.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9060,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"b894cf0e-5a3d-4fe2-bb43-668a1f973857":{"id":"b894cf0e-5a3d-4fe2-bb43-668a1f973857","doc_no":"A.6.1.1.5.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9061,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"4b2e42f3-064c-4cb8-87a8-96512a581841":{"id":"4b2e42f3-064c-4cb8-87a8-96512a581841","doc_no":"A.6.1.1.5.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9062,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"b83be319-7f7e-4cf5-ad70-ac59302422e4":{"id":"b83be319-7f7e-4cf5-ad70-ac59302422e4","doc_no":"A.6.1.1.5.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9063,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.6.2.2 - Active Instances](b894cf0e-5a3d-4fe2-bb43-668a1f973857).","contentHash":"5721f1a09122ec9a52b098cc6901822a7b5e174ba9816b25048be644169d5796","addressRefs":[]},"fab6088e-5b4c-4ab4-af33-051920120273":{"id":"fab6088e-5b4c-4ab4-af33-051920120273","doc_no":"A.6.1.1.5.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9064,"content":"The documents herein contain all data and specifications for Obex's Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"6b5b8713e01b33f81ccd3565ee490085911860454c0486a32259925a2815ed9e","addressRefs":[]},"804821a4-0344-4642-9575-8bde38f8edef":{"id":"804821a4-0344-4642-9575-8bde38f8edef","doc_no":"A.6.1.1.5.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9065,"content":"The documents herein organize all base information relevant to Obex's usage of the Asset Liability Management Rental Primitive.","contentHash":"28da39323769ea44ed99d6ff33722cc23483ecd9cbb60ca6566ba05d066dc1bd","addressRefs":[]},"80b90a60-c898-4700-8c19-c168709b2bb0":{"id":"80b90a60-c898-4700-8c19-c168709b2bb0","doc_no":"A.6.1.1.5.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9066,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"10f33907-8a83-41ea-8e9c-c4a73882ce79":{"id":"10f33907-8a83-41ea-8e9c-c4a73882ce79","doc_no":"A.6.1.1.5.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9067,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"6759bef4-337e-4e21-8dfe-4152b5618f0d":{"id":"6759bef4-337e-4e21-8dfe-4152b5618f0d","doc_no":"A.6.1.1.5.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9068,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"70f39980-940c-4f32-9365-a196fcca7858":{"id":"70f39980-940c-4f32-9365-a196fcca7858","doc_no":"A.6.1.1.5.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9069,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.6.3.1.2 - Active Instances Directory](10f33907-8a83-41ea-8e9c-c4a73882ce79), whereas failed Invocations are Archived in [A.6.1.1.5.2.6.3.1.5 - Hub Data Repository](c4856110-03a4-4f52-b13b-f3e99b8aba4f).","contentHash":"fab57602dd5ef4fdc94c8ab39b3ecd0577546f4ea954bfd3ac8d1abf2096b07f","addressRefs":[]},"c4856110-03a4-4f52-b13b-f3e99b8aba4f":{"id":"c4856110-03a4-4f52-b13b-f3e99b8aba4f","doc_no":"A.6.1.1.5.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9070,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"b79f57c2-8d27-4147-8b02-9a2794ab9986":{"id":"b79f57c2-8d27-4147-8b02-9a2794ab9986","doc_no":"A.6.1.1.5.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9071,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"9ee5b528-4d53-46fb-b2ed-711c99fca801":{"id":"9ee5b528-4d53-46fb-b2ed-711c99fca801","doc_no":"A.6.1.1.5.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9072,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"06e80d6f-d630-4fab-99db-cb71211c8f56":{"id":"06e80d6f-d630-4fab-99db-cb71211c8f56","doc_no":"A.6.1.1.5.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9073,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"b1667bfc-be11-4b02-ab99-d39b3f5e510d":{"id":"b1667bfc-be11-4b02-ab99-d39b3f5e510d","doc_no":"A.6.1.1.5.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9074,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"9ce2e9b8-8033-4fae-bd6f-9f7b7590ba1b":{"id":"9ce2e9b8-8033-4fae-bd6f-9f7b7590ba1b","doc_no":"A.6.1.1.5.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9075,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"3c1a4517-7097-4964-a687-5dc1de1b00ee":{"id":"3c1a4517-7097-4964-a687-5dc1de1b00ee","doc_no":"A.6.1.1.5.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9076,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.6.3.2 - Active Instances](b1667bfc-be11-4b02-ab99-d39b3f5e510d).","contentHash":"f22089021e0a21eb4871b2a515fb6bcaf385096cc9c43d8bb85c5b5769b9e241","addressRefs":[]},"901fba8d-ac5f-4809-a3d4-e510fc9b74ca":{"id":"901fba8d-ac5f-4809-a3d4-e510fc9b74ca","doc_no":"A.6.1.1.5.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9077,"content":"The documents herein implement the Core Governance Primitives for Obex. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"891ca9a88e6dad6dc24af2e632a3d153ae6e228388c263efe5426167920f9839","addressRefs":[]},"871764eb-5ccb-47fc-8852-0523e989bef6":{"id":"871764eb-5ccb-47fc-8852-0523e989bef6","doc_no":"A.6.1.1.5.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9078,"content":"The documents herein contain all data and specifications for Obex's Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"8d0d07ab7cf21fe8828b568d3b29bffb87b29a3521f86392361a0fed28eb7a77","addressRefs":[]},"e0e1769f-ecbe-4598-a236-318d7b00c929":{"id":"e0e1769f-ecbe-4598-a236-318d7b00c929","doc_no":"A.6.1.1.5.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9079,"content":"The documents herein organize all base information relevant to Obex's usage of the Core Governance Reward Primitive.","contentHash":"8da66c88f41ee37028757be4114068613168a6ddf9e46a7658ff5f57d5b67eae","addressRefs":[]},"a5f4abc0-9d2f-4356-9977-919fcf8ca427":{"id":"a5f4abc0-9d2f-4356-9977-919fcf8ca427","doc_no":"A.6.1.1.5.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9080,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"03941fc1-96ff-454d-aa4d-0658057f7b4c":{"id":"03941fc1-96ff-454d-aa4d-0658057f7b4c","doc_no":"A.6.1.1.5.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9081,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"05d4383b-1140-49f9-857b-00eec596f248":{"id":"05d4383b-1140-49f9-857b-00eec596f248","doc_no":"A.6.1.1.5.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9082,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"77ff1220-f6e0-4b35-ad1c-0224aa5098df":{"id":"77ff1220-f6e0-4b35-ad1c-0224aa5098df","doc_no":"A.6.1.1.5.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9083,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.5.2.7.1.1.2 - Active Instances Directory](03941fc1-96ff-454d-aa4d-0658057f7b4c), whereas failed Invocations are Archived in [A.6.1.1.5.2.7.1.1.5 - Hub Data Repository](6f24ea77-43d3-4c4f-84a0-9341114569c9).","contentHash":"1aa939611523f5e96e30575c931b67b5baae74d7c8b9b31dbc568133f5078872","addressRefs":[]},"6f24ea77-43d3-4c4f-84a0-9341114569c9":{"id":"6f24ea77-43d3-4c4f-84a0-9341114569c9","doc_no":"A.6.1.1.5.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9084,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"38d8dad5-0503-4d43-9826-a2895e9484cc":{"id":"38d8dad5-0503-4d43-9826-a2895e9484cc","doc_no":"A.6.1.1.5.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9085,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"aa94bd40-29d7-4bec-88e6-e54a658947f3":{"id":"aa94bd40-29d7-4bec-88e6-e54a658947f3","doc_no":"A.6.1.1.5.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9086,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"8cf31f6c-e9cc-4d01-97a3-afd2dae271c8":{"id":"8cf31f6c-e9cc-4d01-97a3-afd2dae271c8","doc_no":"A.6.1.1.5.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9087,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"1627c920-e582-446c-b6a0-39f7a528f28a":{"id":"1627c920-e582-446c-b6a0-39f7a528f28a","doc_no":"A.6.1.1.5.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9088,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"e14a0186-9557-4b1f-b4c1-eddeb88e7e34":{"id":"e14a0186-9557-4b1f-b4c1-eddeb88e7e34","doc_no":"A.6.1.1.5.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9089,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"18f93603-5951-4d2e-9527-f88d81c408a3":{"id":"18f93603-5951-4d2e-9527-f88d81c408a3","doc_no":"A.6.1.1.5.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"de2892b7-087c-49ee-8b85-e3753987d38e","order":9090,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.5.2.7.1.2 - Active Instances](1627c920-e582-446c-b6a0-39f7a528f28a).","contentHash":"325c03aee75a7353e5eefb5ada2952d074ad200b1835de843bea230ed4db0da8","addressRefs":[]},"239c5dd4-46a1-4936-8e31-f37ea2aa802c":{"id":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","doc_no":"A.6.1.1.5.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"f558e673-cbab-4696-8ca1-3af9b90fe5d4","order":9091,"content":"The documents herein define Obex's strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"532b294e6d480eaf81f98a6fdb8bb2b50042cab80c4fcfb4928044e9a4218d18","addressRefs":[]},"bdad4ea3-7cf2-40fb-a8ab-4bb8b320e4c9":{"id":"bdad4ea3-7cf2-40fb-a8ab-4bb8b320e4c9","doc_no":"A.6.1.1.5.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9092,"content":"The documents herein specify Obex governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Obex Artifact is specified in the Root Edit Primitive above at [A.6.1.1.5.2.2.2 - Root Edit Primitive](b69559bf-1acb-4f9c-8638-19fb8ef20fc2).","contentHash":"1b1623940f486a32cfb57d80c43207a16c4d8f0d0181dcc5ae08eefde49b74de","addressRefs":[]},"fb92df01-4e93-45ec-8e81-b59d5767ebb7":{"id":"fb92df01-4e93-45ec-8e81-b59d5767ebb7","doc_no":"A.6.1.1.5.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9093,"content":"Obex uses the Sky Forum for governance-related discussion. Posts should use the \"Obex Prime\" category.","contentHash":"98746a54386eb0f87eaece1bf238048869a506fde42a25cb5bad6bfe2dbe81c9","addressRefs":[]},"ec6dc53f-7398-4242-afc4-81e436541da2":{"id":"ec6dc53f-7398-4242-afc4-81e436541da2","doc_no":"A.6.1.1.5.3.1.2","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9094,"content":"The documents herein specify Obex's emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Obex Artifact.","contentHash":"07879ac0f3f5af9a1399680c6967ce43983b81bd32b4aadfdac549fa350d9fb1","addressRefs":[]},"e5ac06b5-0f4a-4506-bfa4-a4d18901e1cc":{"id":"e5ac06b5-0f4a-4506-bfa4-a4d18901e1cc","doc_no":"A.6.1.1.5.3.1.3","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9095,"content":"The documents herein specify Obex's emergency response protocol in situations solely impacting Obex versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Obex Artifact.","contentHash":"4a2e55f0ece2b8e3f29a5d187e8b904c6b0696660d93543a161a80a0c52cc7ce","addressRefs":[]},"b380c021-e579-47a2-ae01-c85340caa135":{"id":"b380c021-e579-47a2-ae01-c85340caa135","doc_no":"A.6.1.1.5.3.2","title":"Strategic Intent And Operating Model","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9096,"content":"Obex is an incubation-focused Prime within the Sky Ecosystem. It provides capital, infrastructure, and technical support to early-stage teams building on Sky Primitives. Obex's purpose is to accelerate aligned builders through structured incubation and funding. The subdocuments herein define the operating model, structure, mandate, and operational standards of Obex.","contentHash":"ebac221e97b90e980a636e073e2dddb2a1d298a85edcd7d6196645a0f02fd4df","addressRefs":[]},"7d7658f6-31a9-4d73-8d3f-19b87d0e89ec":{"id":"7d7658f6-31a9-4d73-8d3f-19b87d0e89ec","doc_no":"A.6.1.1.5.3.2.1","title":"Operating Model","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9097,"content":"Obex follows a direct-execution model rather than a multi-layered governance system. Key processes include:\n\n- **Incubation Selection:** Projects are sourced, evaluated, and onboarded based on strategic fit, feasibility, and alignment with Sky objectives.\n- **Capital Allocation:** All allocations occur through the Obex Incubator Prime, which deploys first-loss or operational capital under predefined parameters.","contentHash":"73f8d5748ae8eb29def46f9d3e2be82f93d6cc51908e2d9335f1b9c116f1265c","addressRefs":[]},"d3466d20-01c9-453a-aee0-e7b8f9e17cf0":{"id":"d3466d20-01c9-453a-aee0-e7b8f9e17cf0","doc_no":"A.6.1.1.5.3.2.2","title":"Risk and Compliance","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9098,"content":"Obex adheres to the Sky Ecosystem's standards for risk, transparency, and recourse.","contentHash":"f83c68c1c05071e5fec9bc9a8528b6cfaf3214b7e95a7d0821e84b4ee18ce0f0","addressRefs":[]},"7f550ce1-dbd5-43dc-8c03-741eb6b9df4a":{"id":"7f550ce1-dbd5-43dc-8c03-741eb6b9df4a","doc_no":"A.6.1.1.5.3.2.3","title":"Ecosystem Accord Alignment","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9099,"content":"Obex operates in full alignment with the Sky Atlas. All operations, reporting, and capital flows must comply with the standards established by Sky Governance and any applicable Ecosystem Accords.","contentHash":"e131551bb48bbea2f8dd8546c41055ea1aa72ab45699cafec026122c21630310","addressRefs":[]},"909f6c00-369e-4fd1-b052-1e933a17b669":{"id":"909f6c00-369e-4fd1-b052-1e933a17b669","doc_no":"A.6.1.1.5.3.2.4","title":"First-Loss and Recourse Principles","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9100,"content":"Capital deployed through Obex carries explicit first-loss protection defined by the Incubator Prime. Each funded project must maintain verifiable recourse through token, equity, or revenue participation agreements enforceable by the Prime's legal wrapper.","contentHash":"a88c81052b44597044762c10826d59939aca41589bce2d826f5e83016f629acb","addressRefs":[]},"c861f5fb-e99b-40ca-b535-291b94b69811":{"id":"c861f5fb-e99b-40ca-b535-291b94b69811","doc_no":"A.6.1.1.5.3.2.5","title":"Data and Transparency Standards","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9101,"content":"Obex maintains an active dashboard reporting total allocations, active projects, utilization, default rates, and realized yields.","contentHash":"448471487e346793094efe88084e57dd09ffaeda533d5417a1ac6a2f309f8423","addressRefs":[]},"dba03405-43a8-4ce1-8a16-dfdeb75cda14":{"id":"dba03405-43a8-4ce1-8a16-dfdeb75cda14","doc_no":"A.6.1.1.5.3.3","title":"Ecosystem Accords","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9102,"content":"Obex has formally agreed to the Ecosystem Accords herein.","contentHash":"a92a93698af74246b553344b779d546c1e8b781af04a4d1a06bcfc18299c73d3","addressRefs":[]},"eab0145b-3b7b-4793-92ff-56717d2e5544":{"id":"eab0145b-3b7b-4793-92ff-56717d2e5544","doc_no":"A.6.1.1.5.3.3.1","title":"Ecosystem Accord 4","type":"Core","depth":6,"parentId":"239c5dd4-46a1-4936-8e31-f37ea2aa802c","order":9103,"content":"Obex engaged in terms of agreement with Sky in Ecosystem Accord 4, located in [A.2.8.2.4 - Ecosystem Accord 4: Sky And Obex](6bddc5aa-ac80-43d8-b8c8-8cde14e896df).","contentHash":"dfc7a6e53e62c5a82b0fc7b60d2ceaf205ae013d3bf2d801ea3cb569f5b8edc4","addressRefs":[]},"dc083d10-74bc-43b6-ab2f-c91efce76e84":{"id":"dc083d10-74bc-43b6-ab2f-c91efce76e84","doc_no":"A.6.1.1.6","title":"Pattern","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":9104,"content":"The documents herein specify all of the logic for Pattern, including Pattern's strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"1c1703797c56be91357a0f1978e97bc2f29b464db0664c80ab6418fbaff2701a","addressRefs":[]},"b137d591-a3a2-482a-a18e-d4ff447964cf":{"id":"b137d591-a3a2-482a-a18e-d4ff447964cf","doc_no":"A.6.1.1.6.1","title":"Introduction","type":"Core","depth":5,"parentId":"dc083d10-74bc-43b6-ab2f-c91efce76e84","order":9105,"content":"Pattern is an Agent providing on-chain liquidity to on-chain and off-chain credit opportunities. Pattern will support new Halo projects focused on both traditional credit and decentralized lending.","contentHash":"1c11a21b6dfaaaaf95ea4e21b6357382bbf8825471cf400ed8d3797649a691ac","addressRefs":[]},"42740824-41c4-49f1-9b59-177aa36ecc9d":{"id":"42740824-41c4-49f1-9b59-177aa36ecc9d","doc_no":"A.6.1.1.6.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"dc083d10-74bc-43b6-ab2f-c91efce76e84","order":9106,"content":"The documents herein implement the Sky Primitives for Pattern. See [A.2.2 - Sky Primitives](cde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"48442587f3bdb011ee14fc3bbf3a2ad23e741f3538f501435bb66a7cc8f7b8bf","addressRefs":[]},"6f66d930-9023-420e-b696-4cb59bc11066":{"id":"6f66d930-9023-420e-b696-4cb59bc11066","doc_no":"A.6.1.1.6.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9107,"content":"The documents herein implement the Genesis Primitives for Pattern. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"4a3f1029243f5829db36f13f5e2459115f2aaa4a8765f6dd8073cef96d0d237d","addressRefs":[]},"b6a417d7-f308-4544-a4d7-eabd4d971556":{"id":"b6a417d7-f308-4544-a4d7-eabd4d971556","doc_no":"A.6.1.1.6.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9108,"content":"The documents herein contain all data and specifications for Pattern's Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"dd105e8c0adc3ae1f34761ea65d0c0b24c1cf1fc92b36c9685b3f5f4d9892cd1","addressRefs":[]},"a5f738ba-82b4-4a9a-a434-393f7a1da00d":{"id":"a5f738ba-82b4-4a9a-a434-393f7a1da00d","doc_no":"A.6.1.1.6.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9109,"content":"The documents herein organize all base information relevant to Pattern's usage of the Agent Creation Primitive.","contentHash":"c989405a91919a8f94cf163effca96ec32217a5ec9940729e053bc974fe8bd3a","addressRefs":[]},"ca2897ab-b88e-46bd-9703-955d007f186a":{"id":"ca2897ab-b88e-46bd-9703-955d007f186a","doc_no":"A.6.1.1.6.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9110,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"ecc0bff3-aa5f-4d3f-9804-35646eaedc4a":{"id":"ecc0bff3-aa5f-4d3f-9804-35646eaedc4a","doc_no":"A.6.1.1.6.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9111,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"cfdd7b8f-b40d-4249-9a1f-1e79af084d6d":{"id":"cfdd7b8f-b40d-4249-9a1f-1e79af084d6d","doc_no":"A.6.1.1.6.2.1.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9112,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"73b79367-bc9c-4df4-a50b-968d5fce2ea0":{"id":"73b79367-bc9c-4df4-a50b-968d5fce2ea0","doc_no":"A.6.1.1.6.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9113,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.1.1.3.1 - Single Instance Configuration Document](0587ddd2-1a45-439c-ab47-400ef6f1fc14).","contentHash":"acb382917b05f86f6f1ad5f65dc9eb9cf1cc38f092c625224bcc04f3bda53ca5","addressRefs":[]},"ec6be13b-0544-471e-88f8-77c567e9c8d0":{"id":"ec6be13b-0544-471e-88f8-77c567e9c8d0","doc_no":"A.6.1.1.6.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9114,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"511e162f-148d-4869-8f6f-d7bfd32f9247":{"id":"511e162f-148d-4869-8f6f-d7bfd32f9247","doc_no":"A.6.1.1.6.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9115,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"79863165-2324-4824-8a58-bf4ee9b3bd0c":{"id":"79863165-2324-4824-8a58-bf4ee9b3bd0c","doc_no":"A.6.1.1.6.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9116,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"42f975c1-b9c5-41d6-8f5c-83979b4518e0":{"id":"42f975c1-b9c5-41d6-8f5c-83979b4518e0","doc_no":"A.6.1.1.6.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9117,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"a087ab7b-998c-4bbc-a10a-5e1281569e28":{"id":"a087ab7b-998c-4bbc-a10a-5e1281569e28","doc_no":"A.6.1.1.6.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9118,"content":"The subtrees for Instances of the Agent Creation Primitive with `Suspended` Status are stored here.","contentHash":"183d20b3c12bea99884c81ff611bff6d5be670766bb91a4f4ccf5339e0a26636","addressRefs":[]},"8fa0177e-3454-4d44-94e2-ca20873e98d2":{"id":"8fa0177e-3454-4d44-94e2-ca20873e98d2","doc_no":"A.6.1.1.6.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9119,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"b57af67d-e709-41a7-986b-afdd90fd18d1":{"id":"b57af67d-e709-41a7-986b-afdd90fd18d1","doc_no":"A.6.1.1.6.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9120,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"0587ddd2-1a45-439c-ab47-400ef6f1fc14":{"id":"0587ddd2-1a45-439c-ab47-400ef6f1fc14","doc_no":"A.6.1.1.6.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9121,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"68bc9006-f5bd-4f8e-9608-28a138b0d29c":{"id":"68bc9006-f5bd-4f8e-9608-28a138b0d29c","doc_no":"A.6.1.1.6.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9122,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"3d765fcc-06a8-47ba-b510-60b3e306cb04":{"id":"3d765fcc-06a8-47ba-b510-60b3e306cb04","doc_no":"A.6.1.1.6.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9123,"content":"The name of the Agent is Pattern.","contentHash":"27b12be16cd1eed35d83aba9acaba8a53df3df3e1a29d38537373b3ac735749c","addressRefs":[]},"9703d0ef-84c9-445b-a2b4-bfe9d24363f0":{"id":"9703d0ef-84c9-445b-a2b4-bfe9d24363f0","doc_no":"A.6.1.1.6.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9124,"content":"The address of Pattern's SubProxy Account on the Ethereum Mainnet is `0xbC8959Ae2d4E9B385Fe620BEF48C2FD7f4A84736`.","contentHash":"aa6d00744b408e5d88d91df396fae98c89462f25fb012e82d614b45de22761ce","addressRefs":["0xbc8959ae2d4e9b385fe620bef48c2fd7f4a84736"]},"16b680a4-27f8-457a-acb5-f6c6e8d29d4d":{"id":"16b680a4-27f8-457a-acb5-f6c6e8d29d4d","doc_no":"A.6.1.1.6.2.1.1.3.1.1.3","title":"StarGuard Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9125,"content":"The address of Pattern's StarGuard contract on the Ethereum Mainnet is `0x2fb18b28fB39Ec3b26C3B5AF5222e2ca3B8B2269`.","contentHash":"eebe0fcc5b7f1ebe9aa719fa8c9e5b85aca53f82bef6e253313044c3ac1edfe5","addressRefs":["0x2fb18b28fb39ec3b26c3b5af5222e2ca3b8b2269"]},"5a466516-e901-4490-8d7c-22a31c82902c":{"id":"5a466516-e901-4490-8d7c-22a31c82902c","doc_no":"A.6.1.1.6.2.1.1.3.1.1.3.1","title":"StarGuard Max Delay","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9126,"content":"The Pattern StarGuard `maxDelay` is seven (7) days.","contentHash":"8ce5dd690c2708c3db4564bd356da9fdfe380f2ec93495c3a62e714bd246776d","addressRefs":[]},"f2c22b75-0ad5-4a7c-be15-d7f0a2d0af89":{"id":"f2c22b75-0ad5-4a7c-be15-d7f0a2d0af89","doc_no":"A.6.1.1.6.2.1.1.3.1.1.4","title":"Genesis Account","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9127,"content":"The address of Pattern's Genesis Account will be specified in a future iteration of the Pattern Artifact.","contentHash":"55bd501679f4a897288483bb1ed11f4a5de082df278975b7fe78d25ac9b40e6e","addressRefs":[]},"3eaa6b51-8d31-4ac9-b171-ee234a67efcd":{"id":"3eaa6b51-8d31-4ac9-b171-ee234a67efcd","doc_no":"A.6.1.1.6.2.1.1.3.1.1.5","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9128,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"07037190-1bad-41df-9fa3-012c8cd18bdf":{"id":"07037190-1bad-41df-9fa3-012c8cd18bdf","doc_no":"A.6.1.1.6.2.1.1.3.1.1.5.1","title":"Pattern Dev Co.","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9129,"content":"Pattern Dev Co. is the development company that provides services to Pattern.","contentHash":"27cca2b9267d7badc03450a54edb18c5f6bd26d77f82c83caa8dcf0f4e0a5033","addressRefs":[]},"e1ea6ef1-5a19-4c09-bbf4-ba67cbc832c8":{"id":"e1ea6ef1-5a19-4c09-bbf4-ba67cbc832c8","doc_no":"A.6.1.1.6.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9130,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"69ab5e3e-0505-485d-8b3e-225681b7565c":{"id":"69ab5e3e-0505-485d-8b3e-225681b7565c","doc_no":"A.6.1.1.6.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9131,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"23b86592-2145-4b96-b74f-7ce8e976b47d":{"id":"23b86592-2145-4b96-b74f-7ce8e976b47d","doc_no":"A.6.1.1.6.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9132,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"79928bec-a87b-427b-9221-2bc19f92fc8d":{"id":"79928bec-a87b-427b-9221-2bc19f92fc8d","doc_no":"A.6.1.1.6.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9133,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"63ba43df-c030-47a1-9563-75ee436969d9":{"id":"63ba43df-c030-47a1-9563-75ee436969d9","doc_no":"A.6.1.1.6.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9134,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"38aff44f-e8ef-4734-8e11-fb7894d024a5":{"id":"38aff44f-e8ef-4734-8e11-fb7894d024a5","doc_no":"A.6.1.1.6.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9135,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"ddd10617-caa7-4d4c-b088-cee2f888cef9":{"id":"ddd10617-caa7-4d4c-b088-cee2f888cef9","doc_no":"A.6.1.1.6.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9136,"content":"The documents herein contain all data and specifications for Pattern's instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"539a22bc614c74edb03792f3da68d066d541bddca941d81b5ec6599ee6a2dfbb","addressRefs":[]},"73321a03-f62c-4aaf-84de-ee79bfd55662":{"id":"73321a03-f62c-4aaf-84de-ee79bfd55662","doc_no":"A.6.1.1.6.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9137,"content":"The documents herein organize all base information relevant to Pattern's usage of the Prime Transformation Primitive.","contentHash":"6e8fe715b04be620b0251db507315a9ca4eff1018df281fd9cd11a6b7855c82d","addressRefs":[]},"4f8cc1c3-7aa4-4d55-a3c7-c3b90365f52a":{"id":"4f8cc1c3-7aa4-4d55-a3c7-c3b90365f52a","doc_no":"A.6.1.1.6.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9138,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"afe290aa-60a5-4e27-869e-b25fc1ed7a9d":{"id":"afe290aa-60a5-4e27-869e-b25fc1ed7a9d","doc_no":"A.6.1.1.6.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9139,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"85dd2116-5311-4379-b89d-1216a59883e7":{"id":"85dd2116-5311-4379-b89d-1216a59883e7","doc_no":"A.6.1.1.6.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9140,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"42771b54-c551-42e2-89ca-b592ccd41eaa":{"id":"42771b54-c551-42e2-89ca-b592ccd41eaa","doc_no":"A.6.1.1.6.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9141,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.1.2.3.1 - Single Instance Configuration Document](2fcbd692-29c5-4788-8f4e-83b415eca7cd).","contentHash":"e7001e177d33b7bfb402d1a69e44ba842919c345f6f95ee69f2f5da3f5b93ab5","addressRefs":[]},"99a274fe-7da8-4b22-bdf6-8b8645f7c617":{"id":"99a274fe-7da8-4b22-bdf6-8b8645f7c617","doc_no":"A.6.1.1.6.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9142,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"3ed71aa1-06fc-4e9d-a8ab-2746506a9562":{"id":"3ed71aa1-06fc-4e9d-a8ab-2746506a9562","doc_no":"A.6.1.1.6.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9143,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e2da8527-9f1e-46d8-beae-9580c3703fcf":{"id":"e2da8527-9f1e-46d8-beae-9580c3703fcf","doc_no":"A.6.1.1.6.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9144,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"2783e2db-322c-4866-9b58-ce7e20c43d24":{"id":"2783e2db-322c-4866-9b58-ce7e20c43d24","doc_no":"A.6.1.1.6.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9145,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"7df624c0-7e91-43de-bd55-eaf0b6b54ddf":{"id":"7df624c0-7e91-43de-bd55-eaf0b6b54ddf","doc_no":"A.6.1.1.6.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9146,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"879bb696-688c-4c77-acde-3936b2c48e7f":{"id":"879bb696-688c-4c77-acde-3936b2c48e7f","doc_no":"A.6.1.1.6.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9147,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"09d97b62-fc72-4695-a780-34899e670f9e":{"id":"09d97b62-fc72-4695-a780-34899e670f9e","doc_no":"A.6.1.1.6.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9148,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"2fcbd692-29c5-4788-8f4e-83b415eca7cd":{"id":"2fcbd692-29c5-4788-8f4e-83b415eca7cd","doc_no":"A.6.1.1.6.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9149,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"39a9fe33-c0ed-4001-8e00-4877e651f820":{"id":"39a9fe33-c0ed-4001-8e00-4877e651f820","doc_no":"A.6.1.1.6.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9150,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"cc457437-4f65-45d6-9c1a-b3e96806de60":{"id":"cc457437-4f65-45d6-9c1a-b3e96806de60","doc_no":"A.6.1.1.6.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9151,"content":"Pattern is a Prime Agent.","contentHash":"fbe39f882363eb465dd78b0c146d75bff2b8c947327e16927914ef4b8f16ada0","addressRefs":[]},"1b7f692d-75a1-4946-9edc-18287204df0f":{"id":"1b7f692d-75a1-4946-9edc-18287204df0f","doc_no":"A.6.1.1.6.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9152,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"b6ac0688-a46a-4a93-9465-7f1481e757f9":{"id":"b6ac0688-a46a-4a93-9465-7f1481e757f9","doc_no":"A.6.1.1.6.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9153,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"e88a0572-4a34-43f2-87df-397f568c1a6a":{"id":"e88a0572-4a34-43f2-87df-397f568c1a6a","doc_no":"A.6.1.1.6.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9154,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"f1d6c189-e998-4bfc-b7a0-322dffdf818e":{"id":"f1d6c189-e998-4bfc-b7a0-322dffdf818e","doc_no":"A.6.1.1.6.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9155,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"f2188696-f28a-41ca-b1d9-7dba408089e7":{"id":"f2188696-f28a-41ca-b1d9-7dba408089e7","doc_no":"A.6.1.1.6.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9156,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"f68d7dad-91a6-41df-8a4f-f0a51d1edcaa":{"id":"f68d7dad-91a6-41df-8a4f-f0a51d1edcaa","doc_no":"A.6.1.1.6.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9157,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"92101482-3d95-4596-8caa-331a7b32362f":{"id":"92101482-3d95-4596-8caa-331a7b32362f","doc_no":"A.6.1.1.6.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9158,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"dbba1a29-c226-4da3-8609-36aea2ecf564":{"id":"dbba1a29-c226-4da3-8609-36aea2ecf564","doc_no":"A.6.1.1.6.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9159,"content":"The documents herein contain all data and specifications for Pattern's instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"b69ea912b7d15573dc56b8fd7678cbd7eff8b30bcb32431c05e374301787d8ef","addressRefs":[]},"4053d47c-8495-470c-8363-763f6c9ea5e8":{"id":"4053d47c-8495-470c-8363-763f6c9ea5e8","doc_no":"A.6.1.1.6.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9160,"content":"The documents herein organize all base information relevant to Pattern's usage of the Executor Transformation Primitive.","contentHash":"5791cd993ec77f68a01801311178ade3f8b49e958a2de03bd0d467ee09e746fe","addressRefs":[]},"9ceac949-3ea5-4c4e-9d14-a14c6af2e28b":{"id":"9ceac949-3ea5-4c4e-9d14-a14c6af2e28b","doc_no":"A.6.1.1.6.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9161,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"0136e45f-2150-4eee-ac7f-024c55df76e9":{"id":"0136e45f-2150-4eee-ac7f-024c55df76e9","doc_no":"A.6.1.1.6.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9162,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"96d03759-39c1-47f1-b4df-3fb6f17c53d6":{"id":"96d03759-39c1-47f1-b4df-3fb6f17c53d6","doc_no":"A.6.1.1.6.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9163,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"fe4c3186-e657-4503-866c-1c5951d36865":{"id":"fe4c3186-e657-4503-866c-1c5951d36865","doc_no":"A.6.1.1.6.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9164,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"9b578e58-0b39-4c8f-85cf-d620e7b26aaa":{"id":"9b578e58-0b39-4c8f-85cf-d620e7b26aaa","doc_no":"A.6.1.1.6.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9165,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ec65edb3-27bc-4417-899e-7bf79a15bb89":{"id":"ec65edb3-27bc-4417-899e-7bf79a15bb89","doc_no":"A.6.1.1.6.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9166,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"da208691-821a-449f-91c8-12feebfa309e":{"id":"da208691-821a-449f-91c8-12feebfa309e","doc_no":"A.6.1.1.6.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9167,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"29a6a43c-10a4-4b9d-ac2d-ba8392d32848":{"id":"29a6a43c-10a4-4b9d-ac2d-ba8392d32848","doc_no":"A.6.1.1.6.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9168,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"b663556e-0602-4afa-a333-c4bddb7cf763":{"id":"b663556e-0602-4afa-a333-c4bddb7cf763","doc_no":"A.6.1.1.6.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9169,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"e6c0d4a8-24ef-4e0f-a0f3-439dd4cdf326":{"id":"e6c0d4a8-24ef-4e0f-a0f3-439dd4cdf326","doc_no":"A.6.1.1.6.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9170,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"f4b8bb12-b5ba-4bef-ae6d-0985bb9c0a90":{"id":"f4b8bb12-b5ba-4bef-ae6d-0985bb9c0a90","doc_no":"A.6.1.1.6.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9171,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"b16a82ab-c18b-474d-91f5-97dba7e73bf9":{"id":"b16a82ab-c18b-474d-91f5-97dba7e73bf9","doc_no":"A.6.1.1.6.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9172,"content":"The documents herein contain all data and specifications for Pattern's Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"52a7729dcd839d0a178608c436fc2c3b2481d76b92d4cb1169bbf22a55357131","addressRefs":[]},"9d78656b-5f03-4644-b6bb-c37ed7bdfe58":{"id":"9d78656b-5f03-4644-b6bb-c37ed7bdfe58","doc_no":"A.6.1.1.6.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9173,"content":"The documents herein organize all base information relevant to Pattern's usage of the Agent Token Primitive.","contentHash":"c2237ee4946cb0eed7ebc5b7088c456202e9055b8ca1f65b2a9bbf69278413ee","addressRefs":[]},"548f4e01-9e6b-4031-af13-4db16657fe3c":{"id":"548f4e01-9e6b-4031-af13-4db16657fe3c","doc_no":"A.6.1.1.6.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9174,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"840388d9-fee4-4ed5-ba4d-f66c86756a59":{"id":"840388d9-fee4-4ed5-ba4d-f66c86756a59","doc_no":"A.6.1.1.6.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9175,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"2e06bfa4-06ab-4d99-98de-1aad9e96ae07":{"id":"2e06bfa4-06ab-4d99-98de-1aad9e96ae07","doc_no":"A.6.1.1.6.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9176,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.1.4.2.1 - Single Instance Configuration Document](0667a9c2-6fe1-456e-bd0a-3cf367fac480).","contentHash":"25c279b3dde35ecdb882e312de65fdcaec0c3fab3feb0d48c490837721332937","addressRefs":[]},"e1fada1e-777d-4591-8c33-17fcd67a7e12":{"id":"e1fada1e-777d-4591-8c33-17fcd67a7e12","doc_no":"A.6.1.1.6.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9177,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"e51a3ed3-3ddc-4148-af56-e5b9a43b20cb":{"id":"e51a3ed3-3ddc-4148-af56-e5b9a43b20cb","doc_no":"A.6.1.1.6.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9178,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent's token, no further Instances of the Primitive can be Invoked.","contentHash":"074cf01e7e3e0ae54374fe52a096387e2d56f0d44ce5ffbe535b303308949c9a","addressRefs":[]},"9957f9c5-7770-4bb8-a883-2e2adbc57578":{"id":"9957f9c5-7770-4bb8-a883-2e2adbc57578","doc_no":"A.6.1.1.6.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9179,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"d2dd644c-787d-411b-8838-cb64863e08c0":{"id":"d2dd644c-787d-411b-8838-cb64863e08c0","doc_no":"A.6.1.1.6.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9180,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"b832b536-0c59-461d-b347-8f829b51a21d":{"id":"b832b536-0c59-461d-b347-8f829b51a21d","doc_no":"A.6.1.1.6.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9181,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"17139c9f-911a-412d-b8d9-b233212969fe":{"id":"17139c9f-911a-412d-b8d9-b233212969fe","doc_no":"A.6.1.1.6.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9182,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"2e096f4a-35ad-4a3a-a21a-2319bd5e45d7":{"id":"2e096f4a-35ad-4a3a-a21a-2319bd5e45d7","doc_no":"A.6.1.1.6.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9183,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"0667a9c2-6fe1-456e-bd0a-3cf367fac480":{"id":"0667a9c2-6fe1-456e-bd0a-3cf367fac480","doc_no":"A.6.1.1.6.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9184,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"c562edbd-5dd4-44c7-a6c4-ab8a2169df55":{"id":"c562edbd-5dd4-44c7-a6c4-ab8a2169df55","doc_no":"A.6.1.1.6.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9185,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"49243902-54b4-49e4-8bed-caa61cca4fa1":{"id":"49243902-54b4-49e4-8bed-caa61cca4fa1","doc_no":"A.6.1.1.6.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9186,"content":"The name of Pattern's token is Pattern.","contentHash":"3d6e346695809a15d97e2fa6de0a0e0f32310670b7dbd2a8183dba1cd6d3e20c","addressRefs":[]},"b840db04-00cb-4f16-9f43-f967963807a4":{"id":"b840db04-00cb-4f16-9f43-f967963807a4","doc_no":"A.6.1.1.6.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9187,"content":"The symbol of Pattern's token is PATTERN.","contentHash":"dc0f328c07d0fdc07627e1aaff388f132ae5aea26cfd26d254ab5cf71155eb83","addressRefs":[]},"f699e4e0-6c47-41b2-ab52-9e0169fa7ffe":{"id":"f699e4e0-6c47-41b2-ab52-9e0169fa7ffe","doc_no":"A.6.1.1.6.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9188,"content":"The Genesis Supply of PATTERN is 10 billion.","contentHash":"f6c0d787d821ef7d1154653712753da5ceaa26153623345c543c0f4d7e34552a","addressRefs":[]},"1108297e-9d69-4468-859e-2d26a42c27af":{"id":"1108297e-9d69-4468-859e-2d26a42c27af","doc_no":"A.6.1.1.6.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9189,"content":"The address of PATTERN will be specified in a future iteration of the Pattern Artifact.","contentHash":"cf20e106bee6fc575f24f145a03699683ae9d2cd8608d2d88df7f58a94069a74","addressRefs":[]},"82d9f120-27e1-4b0c-a575-d26b537df45e":{"id":"82d9f120-27e1-4b0c-a575-d26b537df45e","doc_no":"A.6.1.1.6.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9190,"content":"The token Admin will be specified in a future iteration of the Pattern Artifact.","contentHash":"4a74a4d06121c8a1c41281e7e54e72aa96919f128cf6fc32a48498156088513e","addressRefs":[]},"ddb9f10e-8452-482a-b102-656dc8b23eea":{"id":"ddb9f10e-8452-482a-b102-656dc8b23eea","doc_no":"A.6.1.1.6.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9191,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Pattern Governance. Sky Governance retains the ability to revert where Pattern is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"10cf31a8551e9d7745db1eb0061c5612687659a3cebe2fcc5d2085eaf95e56b8","addressRefs":[]},"488f6950-fecd-4f82-ab43-62c4fab0f9ae":{"id":"488f6950-fecd-4f82-ab43-62c4fab0f9ae","doc_no":"A.6.1.1.6.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9192,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"7f6bce4b-af7e-4810-aea8-890ee4b5f6ad":{"id":"7f6bce4b-af7e-4810-aea8-890ee4b5f6ad","doc_no":"A.6.1.1.6.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9193,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.\n\n- These processes will be defined in a future iteration of the Pattern Artifact.","contentHash":"db9a91a502d3cf70e590cc753ff72c66b546087357dd406c940760350c7257ad","addressRefs":[]},"16fc704d-3db3-4701-b3e3-cddadd99f125":{"id":"16fc704d-3db3-4701-b3e3-cddadd99f125","doc_no":"A.6.1.1.6.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9194,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"c900576f-7e31-40cc-8c2d-994b6b06bb5a":{"id":"c900576f-7e31-40cc-8c2d-994b6b06bb5a","doc_no":"A.6.1.1.6.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9195,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"34f38616-01ff-4516-8ede-b553d2305fb8":{"id":"34f38616-01ff-4516-8ede-b553d2305fb8","doc_no":"A.6.1.1.6.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9196,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"bc407d25-c3f5-412e-bf72-4cab3189f9e4":{"id":"bc407d25-c3f5-412e-bf72-4cab3189f9e4","doc_no":"A.6.1.1.6.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9197,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"abfc5286-88ee-4cb1-9610-ef45082019d6":{"id":"abfc5286-88ee-4cb1-9610-ef45082019d6","doc_no":"A.6.1.1.6.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9198,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"2c50493d-aa00-4aaa-95a7-fd43a5625500":{"id":"2c50493d-aa00-4aaa-95a7-fd43a5625500","doc_no":"A.6.1.1.6.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9199,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent's token, no further Instances of the Primitive can be Invoked.","contentHash":"074cf01e7e3e0ae54374fe52a096387e2d56f0d44ce5ffbe535b303308949c9a","addressRefs":[]},"74b5123e-1557-4323-851b-96ada6249e50":{"id":"74b5123e-1557-4323-851b-96ada6249e50","doc_no":"A.6.1.1.6.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9200,"content":"The documents herein implement the Operational Primitives for Pattern. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"b27c1412c6c65867222eea5aa76a1334e8582b2412230d00e96e75255d7bb253","addressRefs":[]},"5675fbe0-03fc-4571-9bf6-0eed37f06b8c":{"id":"5675fbe0-03fc-4571-9bf6-0eed37f06b8c","doc_no":"A.6.1.1.6.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9201,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"06cf421676546a7b58301681e048c174cff43be6d8741bfb92e38a8f7492feed","addressRefs":[]},"4604fb19-254c-455e-93c6-e2aba0b7261d":{"id":"4604fb19-254c-455e-93c6-e2aba0b7261d","doc_no":"A.6.1.1.6.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9202,"content":"The documents herein organize all base information relevant to Pattern's usage of the Executor Accord Primitive.","contentHash":"eb714c0d7af736f0fc0a1628a89ab7c0a234f6fc617c43ad5ea1a6e8d40ffd10","addressRefs":[]},"3d671fa2-ff8c-4a09-aac6-579b23e43d9a":{"id":"3d671fa2-ff8c-4a09-aac6-579b23e43d9a","doc_no":"A.6.1.1.6.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9203,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"8466094a-9e2a-4dad-bac9-88e0bb8987aa":{"id":"8466094a-9e2a-4dad-bac9-88e0bb8987aa","doc_no":"A.6.1.1.6.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9204,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"d00595bb-b9c6-4663-8055-18332fa01647":{"id":"d00595bb-b9c6-4663-8055-18332fa01647","doc_no":"A.6.1.1.6.2.2.1.1.2.1","title":"Ozone Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9205,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.2.1.2.1 - Ozone Instance Configuration Document](960445d5-4b1c-406e-b05a-470e0cca6e71).","contentHash":"908cdccc93f6aa10a795f896cf7d468bfddc991d85fa2e82c58fc82cf475ff6e","addressRefs":[]},"061c10bc-d108-4610-abc3-fb017304d711":{"id":"061c10bc-d108-4610-abc3-fb017304d711","doc_no":"A.6.1.1.6.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9206,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"2d253ba6-4610-4478-b844-d5288368e94a":{"id":"2d253ba6-4610-4478-b844-d5288368e94a","doc_no":"A.6.1.1.6.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9207,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.2.1.1.2 - Active Instances Directory(8466094a-9e2a-4dad-bac9-88e0bb8987aa)], whereas failed Invocations are Archived in [A.6.1.1.6.2.2.1.1.5 - Hub Data Repository](f5ddf7f3-add9-4599-ae6e-108d56abcb5b).","contentHash":"53347a7bc3586b7617eaddf91678ffe63f72eb0dabf64ab12912c82f4633acfe","addressRefs":[]},"f5ddf7f3-add9-4599-ae6e-108d56abcb5b":{"id":"f5ddf7f3-add9-4599-ae6e-108d56abcb5b","doc_no":"A.6.1.1.6.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9208,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"087712fc-59c2-4a4a-90fa-a5644451d476":{"id":"087712fc-59c2-4a4a-90fa-a5644451d476","doc_no":"A.6.1.1.6.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9209,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"9bbb61da-85ae-4926-868e-69fe3935284e":{"id":"9bbb61da-85ae-4926-868e-69fe3935284e","doc_no":"A.6.1.1.6.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9210,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"2f4c6bfd-ef22-481e-996f-8d443c446aad":{"id":"2f4c6bfd-ef22-481e-996f-8d443c446aad","doc_no":"A.6.1.1.6.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9211,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"b50f2b43-50b8-43e4-bb4b-393434d8d935":{"id":"b50f2b43-50b8-43e4-bb4b-393434d8d935","doc_no":"A.6.1.1.6.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9212,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"960445d5-4b1c-406e-b05a-470e0cca6e71":{"id":"960445d5-4b1c-406e-b05a-470e0cca6e71","doc_no":"A.6.1.1.6.2.2.1.2.1","title":"Ozone Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9213,"content":"The documents herein contain the Instance Configuration Document for the Ozone Executor Accord Primitive Instance.","contentHash":"ca0caee12f20439eb72be855f0a3c3853fe737be1313cfe253dad38c7f8d0623","addressRefs":[]},"8cee1084-ac2b-4608-bbfd-adbc021b290b":{"id":"8cee1084-ac2b-4608-bbfd-adbc021b290b","doc_no":"A.6.1.1.6.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9214,"content":"The documents herein define the parameters of the Ozone Instance of the Executor Accord Primitive.","contentHash":"638cf31df48e28f4a38e5155a81f9cd4b27bb221ff40cc010386b96be05691e5","addressRefs":[]},"9eb31932-9fe5-49fb-9f7c-4d44db589295":{"id":"9eb31932-9fe5-49fb-9f7c-4d44db589295","doc_no":"A.6.1.1.6.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9215,"content":"The Operational Facilitator and Operational GovOps for Ozone are specified in [A.6.1.2.2 - Operational Executor Agent Ozone](565660dd-7850-4c3a-8dba-554542bf103a).","contentHash":"8ed0f1fb66d463549e15caa041123f9031ac10ad2f25d039e4bc6b7777f702a7","addressRefs":[]},"62d6ce9b-d6b3-4ccf-9739-7fa4aee3c5fa":{"id":"62d6ce9b-d6b3-4ccf-9739-7fa4aee3c5fa","doc_no":"A.6.1.1.6.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9216,"content":"The documents herein define the custom parameters of the Ozone Instance of the Executor Accord Primitive, if any.","contentHash":"be003f7a447f9026ea8e107c73c8b00f811e9d616575d90ced4c5ffb41a29c34","addressRefs":[]},"5f9cf743-c9f6-4a7b-a543-45cc5b950d13":{"id":"5f9cf743-c9f6-4a7b-a543-45cc5b950d13","doc_no":"A.6.1.1.6.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9217,"content":"The documents herein define the process for the ongoing management of the Ozone Instance of the Executor Accord Primitive.","contentHash":"03daa9d3ebfb53ae8a57e22ffb990501ed356259a7b153b51d2b35cb6013c74b","addressRefs":[]},"aa2c1044-4832-4e97-a2c9-36f4b872bd88":{"id":"aa2c1044-4832-4e97-a2c9-36f4b872bd88","doc_no":"A.6.1.1.6.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9218,"content":"The documents herein contain data relevant to the Ozone Instance of the Executor Accord Primitive.","contentHash":"edd3e28207fedf752584ef2eb5e88f52b3ff82d2d0a5d7cfed80703bd5ad5d72","addressRefs":[]},"5ac885aa-64f6-4400-82b9-d11a33470b28":{"id":"5ac885aa-64f6-4400-82b9-d11a33470b28","doc_no":"A.6.1.1.6.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9219,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"b3a60a21-7f43-403f-9cfa-aa8bd29f0140":{"id":"b3a60a21-7f43-403f-9cfa-aa8bd29f0140","doc_no":"A.6.1.1.6.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9220,"content":"The materials associated with Operational GovOps review during the Invocation of this Instance are contained herein.","contentHash":"4d9cf82f10b4116dc01ad201efd474911d68cc99e9ef9477435cf5f1402ce280","addressRefs":[]},"eb0aaebd-16e4-4955-b7c9-c1a778b4cf9e":{"id":"eb0aaebd-16e4-4955-b7c9-c1a778b4cf9e","doc_no":"A.6.1.1.6.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9221,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"20a2abf2-ca4d-407e-8c23-2950271ffa19":{"id":"20a2abf2-ca4d-407e-8c23-2950271ffa19","doc_no":"A.6.1.1.6.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9222,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"475e7d64-fa87-480a-bb50-adf16acd4af8":{"id":"475e7d64-fa87-480a-bb50-adf16acd4af8","doc_no":"A.6.1.1.6.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9223,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.2.1.2 - Active Instances](b50f2b43-50b8-43e4-bb4b-393434d8d935).","contentHash":"f13e01c319d2779fffcfc7a2b023de48b3c7c195cdb2513080ef953776dd9f73","addressRefs":[]},"e30f2e01-78c1-4286-a80a-0df31923303f":{"id":"e30f2e01-78c1-4286-a80a-0df31923303f","doc_no":"A.6.1.1.6.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9224,"content":"The documents herein contain all data and specifications for Pattern's Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"0299427f0883b07fbf657d2d3f376120a5cf4744a571c479f3b6e8c64ef7c0ff","addressRefs":[]},"f987a5d2-2fe4-450e-a57b-32c44ba2eb99":{"id":"f987a5d2-2fe4-450e-a57b-32c44ba2eb99","doc_no":"A.6.1.1.6.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9225,"content":"The documents herein organize all base information relevant to Pattern's usage of the Root Edit Primitive.","contentHash":"14e81203fa33e31d962fd93add7e285e91708fe13d5ee6ade612aecc6b8dc3b7","addressRefs":[]},"0f9cb02c-8c9b-459a-b326-86a81cfcca9c":{"id":"0f9cb02c-8c9b-459a-b326-86a81cfcca9c","doc_no":"A.6.1.1.6.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9226,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"8653a85e-f6dc-44b9-8192-5f998c9f5369":{"id":"8653a85e-f6dc-44b9-8192-5f998c9f5369","doc_no":"A.6.1.1.6.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9227,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"e36d3e60-d222-4ae4-a02f-6994bd6b252c":{"id":"e36d3e60-d222-4ae4-a02f-6994bd6b252c","doc_no":"A.6.1.1.6.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9228,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.2.2.2.1 - Single Instance Configuration Document](a53a7f47-1c80-4ab8-bf86-d32dc0e21ccc).","contentHash":"ef28863728f807583113c4177d8e228e74400a643451b74ee9985cab00ab49ce","addressRefs":[]},"8fa24145-e0d4-4d70-ae7c-b830ad966e8f":{"id":"8fa24145-e0d4-4d70-ae7c-b830ad966e8f","doc_no":"A.6.1.1.6.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9229,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"47690711-4a0d-4f50-9aa8-47c3cada5afc":{"id":"47690711-4a0d-4f50-9aa8-47c3cada5afc","doc_no":"A.6.1.1.6.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9230,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"fe138146-b5f3-4790-a027-366281bee9d4":{"id":"fe138146-b5f3-4790-a027-366281bee9d4","doc_no":"A.6.1.1.6.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9231,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"f6241c15-1f4e-44a1-9e32-9b0593ff09c9":{"id":"f6241c15-1f4e-44a1-9e32-9b0593ff09c9","doc_no":"A.6.1.1.6.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9232,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"ec7cb8c6-c1a9-470c-8f3a-4a8bae47f28c":{"id":"ec7cb8c6-c1a9-470c-8f3a-4a8bae47f28c","doc_no":"A.6.1.1.6.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9233,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"6443e0c7-2ec7-431f-a4d7-a93453e742ef":{"id":"6443e0c7-2ec7-431f-a4d7-a93453e742ef","doc_no":"A.6.1.1.6.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9234,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"4bfaf43d-8cde-4359-9581-cff3c9363337":{"id":"4bfaf43d-8cde-4359-9581-cff3c9363337","doc_no":"A.6.1.1.6.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9235,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"a53a7f47-1c80-4ab8-bf86-d32dc0e21ccc":{"id":"a53a7f47-1c80-4ab8-bf86-d32dc0e21ccc","doc_no":"A.6.1.1.6.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9236,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"cdf80bb3-4e22-4e51-b0fd-4325c331b7e2":{"id":"cdf80bb3-4e22-4e51-b0fd-4325c331b7e2","doc_no":"A.6.1.1.6.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9237,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.6.2.2.2.2.1.2 - Operational Process Definition](0a6525e3-429d-4955-8dac-9fc61f6643f8).","contentHash":"99dffb48a20f4b53c048ab343449727708dd6ca8630486e1e2dd75bc4cf6dbbf","addressRefs":[]},"0a6525e3-429d-4955-8dac-9fc61f6643f8":{"id":"0a6525e3-429d-4955-8dac-9fc61f6643f8","doc_no":"A.6.1.1.6.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9238,"content":"The documents herein define the process for using the Root Edit Primitive to update the Pattern Agent Artifact. Information on Pattern governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.6.3.1 - Governance Information Unrelated To Root Edit Primitive](df8e7155-ba1f-4606-8a4a-0619c06da12b).","contentHash":"761939bdc7784869362dc6c5a7565e613207934e43923b908f1412344f97289b","addressRefs":[]},"531cdc0a-091f-4c06-9d4e-e2421853a4c6":{"id":"531cdc0a-091f-4c06-9d4e-e2421853a4c6","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9239,"content":"The documents herein define the process for using the Root Edit Primitive to update the Pattern Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"8e14731022748935cb9beaac226adf8c5e47f0a32d7f482729b452655146d1b7","addressRefs":[]},"a6261165-8c88-432f-a3c1-79465599d706":{"id":"a6261165-8c88-432f-a3c1-79465599d706","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9240,"content":"The Root Edit process begins with a PATTERN token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. A PATTERN token holder must hold at least 1% of the circulating token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Pattern Prime\" category.","contentHash":"eac8b1811b08e426c1d1d6e49fed7878c1f67429a192beffe614ac280269424e","addressRefs":[]},"351f7eac-691a-4bcb-868e-5ca56787d53a":{"id":"351f7eac-691a-4bcb-868e-5ca56787d53a","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.1.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9241,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, PATTERN token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Pattern Prime\" category. The title of the post must include the text \"Pattern Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total PATTERN token supply specified in [A.6.1.1.6.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](a6261165-8c88-432f-a3c1-79465599d706).","contentHash":"edd7ec1356a395ed8b55204f3a0bcfa35c36e58acba336763f29c6a5daf07463","addressRefs":[]},"17be5231-4b3e-44ab-92ea-c7e259e633e1":{"id":"17be5231-4b3e-44ab-92ea-c7e259e633e1","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9242,"content":"A future iteration of the Pattern Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis.","contentHash":"3f5b93d50cd4063caee566171d9505ac79290d99ac97b375fb2fbe366ad07dcf","addressRefs":[]},"af30f942-9746-4576-ab61-df3dd9697fbe":{"id":"af30f942-9746-4576-ab61-df3dd9697fbe","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9243,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment.\n\nIf the proposal is aligned, the Operational Facilitator must respond to the Forum post to announce their finding. In this Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"3d695884c752507d7f445ad3a572c67b44863196d11108fb8a300dc2e71ce3e7","addressRefs":[]},"8704e66e-872f-4bca-b63c-8361aa694496":{"id":"8704e66e-872f-4bca-b63c-8361aa694496","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9244,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Pattern Artifact, the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. The poll is open for three (3) days. A poll must have at least 10% of the circulating token supply participating and must have 50% of votes in favor to be approved.","contentHash":"e4f31e44633a767326cf67a8eee92fa03f999e46a2f7b70ff2c8e1b5e39ff2db","addressRefs":[]},"d2543813-8897-48a1-968d-1cfd3a2d3068":{"id":"d2543813-8897-48a1-968d-1cfd3a2d3068","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9245,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"058a9110-5c05-4b0d-9602-1d0429ab6fbb":{"id":"058a9110-5c05-4b0d-9602-1d0429ab6fbb","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.5.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9246,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"4137d6f6-d330-4953-99e7-b17f2fb8ac55":{"id":"4137d6f6-d330-4953-99e7-b17f2fb8ac55","doc_no":"A.6.1.1.6.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9247,"content":"The Pattern Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"9e5ff2d6eb1764866b118c60f8dc4b99fc0f1c509e1e3e3a350d9bf982194a4e","addressRefs":[]},"3474027e-8a10-4972-b929-90f9c2894c70":{"id":"3474027e-8a10-4972-b929-90f9c2894c70","doc_no":"A.6.1.1.6.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9248,"content":"The documents herein define the process for using the Root Edit Primitive to update the Pattern Agent Artifact in non-routine conditions.","contentHash":"15fe38d670ea7c14e8b96f9bd3d44017a407504591f279299b0baa72bcc157ae","addressRefs":[]},"fbd6606d-dfe5-4816-bb90-f555c13323b1":{"id":"fbd6606d-dfe5-4816-bb90-f555c13323b1","doc_no":"A.6.1.1.6.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9249,"content":"The documents herein define the process for using the Root Edit Primitive to update the Pattern Agent Artifact in emergency situations.","contentHash":"d2d88c7932514548d82bf713a493f29cdbec7c727352449dc24a15102d4b6381","addressRefs":[]},"7d31d593-75bb-41ef-86f4-a10ecf83e19f":{"id":"7d31d593-75bb-41ef-86f4-a10ecf83e19f","doc_no":"A.6.1.1.6.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process In Emergency Situations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9250,"content":"In an Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Pattern Prime\" category), unless doing so would endanger Pattern or its users.","contentHash":"fccb88d91e2b624d771860e90290d7d14cfb9219f12d288f50935016855316b2","addressRefs":[]},"ffdbcc14-282a-47ae-81c6-7773b2cc09bf":{"id":"ffdbcc14-282a-47ae-81c6-7773b2cc09bf","doc_no":"A.6.1.1.6.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9251,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"f4b2bc56-63d1-4b5b-8c84-8eccc1fa3218":{"id":"f4b2bc56-63d1-4b5b-8c84-8eccc1fa3218","doc_no":"A.6.1.1.6.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9252,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"10680aaa-0b55-4c66-b40d-9741bcd4dc6e":{"id":"10680aaa-0b55-4c66-b40d-9741bcd4dc6e","doc_no":"A.6.1.1.6.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9253,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"17aa4887-fc5d-4b66-8f3e-60a3490250a5":{"id":"17aa4887-fc5d-4b66-8f3e-60a3490250a5","doc_no":"A.6.1.1.6.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9254,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"261adee1-2841-4c6b-937e-c5c86cf6cbac":{"id":"261adee1-2841-4c6b-937e-c5c86cf6cbac","doc_no":"A.6.1.1.6.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9255,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"2f12e03a-7561-4b7c-ae2f-baec03f1b18f":{"id":"2f12e03a-7561-4b7c-ae2f-baec03f1b18f","doc_no":"A.6.1.1.6.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9256,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"ecf594f7-ccc6-45f0-8ed0-e7a0f0b5182d":{"id":"ecf594f7-ccc6-45f0-8ed0-e7a0f0b5182d","doc_no":"A.6.1.1.6.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9257,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"c766a48e7ba1e421825d5b64f76bba019b30ff0cf3b7edb79fe7319f061d3410","addressRefs":[]},"2abd678a-fea3-4968-87c5-a81302f3c387":{"id":"2abd678a-fea3-4968-87c5-a81302f3c387","doc_no":"A.6.1.1.6.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9258,"content":"The documents herein organize all base information relevant to Pattern's usage of the Light Agent Primitive.","contentHash":"5340d47afd71c8e6f50fcfd77ff2287dcb1f49713075c40a340355dd2f036653","addressRefs":[]},"c1a3ea5f-5cd9-46f3-9d0a-a7ad7648c3c4":{"id":"c1a3ea5f-5cd9-46f3-9d0a-a7ad7648c3c4","doc_no":"A.6.1.1.6.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9259,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"d59c68f3-1755-457d-b16e-3ca9eda708bf":{"id":"d59c68f3-1755-457d-b16e-3ca9eda708bf","doc_no":"A.6.1.1.6.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9260,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"2c5faabf-cbe8-47f4-b710-d431ae46ac2d":{"id":"2c5faabf-cbe8-47f4-b710-d431ae46ac2d","doc_no":"A.6.1.1.6.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9261,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"d90aac90-120d-4ed3-83bc-cf2d2fd91250":{"id":"d90aac90-120d-4ed3-83bc-cf2d2fd91250","doc_no":"A.6.1.1.6.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9262,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.2.3.1.2 - Active Instances Directory](d59c68f3-1755-457d-b16e-3ca9eda708bf), whereas failed Invocations are Archived in [A.6.1.1.6.2.2.3.1.5 - Hub Data Repository](cdf9a214-d0a4-482d-8218-8bfe3f783524).","contentHash":"059a26b6bf7eb89a094411fdc7650810d65f569fecc592561ba0333292422dd8","addressRefs":[]},"cdf9a214-d0a4-482d-8218-8bfe3f783524":{"id":"cdf9a214-d0a4-482d-8218-8bfe3f783524","doc_no":"A.6.1.1.6.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9263,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"6b266aa2-92ea-4072-af2a-b7bbf05366ed":{"id":"6b266aa2-92ea-4072-af2a-b7bbf05366ed","doc_no":"A.6.1.1.6.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9264,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"61056f64-f4ec-45bd-996c-677745cb4d18":{"id":"61056f64-f4ec-45bd-996c-677745cb4d18","doc_no":"A.6.1.1.6.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9265,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"06b30e73-6a92-4e83-acd0-f09a3dca5b37":{"id":"06b30e73-6a92-4e83-acd0-f09a3dca5b37","doc_no":"A.6.1.1.6.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9266,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"1f384209-da9a-4792-a244-2effa8187f50":{"id":"1f384209-da9a-4792-a244-2effa8187f50","doc_no":"A.6.1.1.6.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9267,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"978cd88e-53a9-403b-9186-9462d572cee4":{"id":"978cd88e-53a9-403b-9186-9462d572cee4","doc_no":"A.6.1.1.6.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9268,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"b1642b58-8b1f-4a05-9ff2-6dccbcc217ee":{"id":"b1642b58-8b1f-4a05-9ff2-6dccbcc217ee","doc_no":"A.6.1.1.6.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9269,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.2.3.2 - Active Instances](1f384209-da9a-4792-a244-2effa8187f50).","contentHash":"229c202ea1ccc0ad6ee314749fccdbcdda699a4ab02de481d1076382ed3a6aef","addressRefs":[]},"49eaa780-25f5-4732-8a47-fc18e06f320c":{"id":"49eaa780-25f5-4732-8a47-fc18e06f320c","doc_no":"A.6.1.1.6.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9270,"content":"The documents herein implement the Ecosystem Upkeep Primitives for Pattern. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"105caa3a7d5d5b2b3155f7132e6b0925c91806a93e2cfe143bafcb6bf9c9fe36","addressRefs":[]},"0d6ea791-8496-4fe5-8430-b636482ed967":{"id":"0d6ea791-8496-4fe5-8430-b636482ed967","doc_no":"A.6.1.1.6.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9271,"content":"The documents herein contain all data and specifications for Pattern's Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"d0c3bc2b0ce9ffdf2e32133d65973f0d8cf3cccc9262d7289ad92b2467027d9a","addressRefs":[]},"494d6e55-e1c1-4d0f-a51d-8f87d2a95ad5":{"id":"494d6e55-e1c1-4d0f-a51d-8f87d2a95ad5","doc_no":"A.6.1.1.6.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9272,"content":"The documents herein organize all base information relevant to Pattern's usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"3842124af0c13b7561b40f1f303189d9de4ba5ed54712678c7126a9234e2e170","addressRefs":[]},"280c32bc-e40e-4187-be61-0f2fd26ab167":{"id":"280c32bc-e40e-4187-be61-0f2fd26ab167","doc_no":"A.6.1.1.6.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9273,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"09267410-31c0-42be-a8d2-dfb0768b72b0":{"id":"09267410-31c0-42be-a8d2-dfb0768b72b0","doc_no":"A.6.1.1.6.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9274,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"b23ab610-19e1-44a7-b23a-2b44c2d18720":{"id":"b23ab610-19e1-44a7-b23a-2b44c2d18720","doc_no":"A.6.1.1.6.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9275,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.3.1.2.1 - Single Instance Configuration Document](d8b7f338-3318-462c-a65d-4e49a29398b2).","contentHash":"b906dd90b180e798dc94f9148b0c878679a2de4cbfa519429ed3461ebe24e5c1","addressRefs":[]},"e7a3cf2c-258e-4709-8a0c-db71bccc487f":{"id":"e7a3cf2c-258e-4709-8a0c-db71bccc487f","doc_no":"A.6.1.1.6.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9276,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"c58a4af2-fdf4-4b79-8720-5836734d028a":{"id":"c58a4af2-fdf4-4b79-8720-5836734d028a","doc_no":"A.6.1.1.6.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9277,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"033c7842-34e2-4043-b7fa-238c52e21709":{"id":"033c7842-34e2-4043-b7fa-238c52e21709","doc_no":"A.6.1.1.6.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9278,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"f33304eb-bd49-4f6b-ad0f-6bd869f51c81":{"id":"f33304eb-bd49-4f6b-ad0f-6bd869f51c81","doc_no":"A.6.1.1.6.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9279,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"15afa4dd-86cb-4080-8c57-7c0e9083871d":{"id":"15afa4dd-86cb-4080-8c57-7c0e9083871d","doc_no":"A.6.1.1.6.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9280,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"21ab98ce-6e98-43e1-907b-f9851d19114e":{"id":"21ab98ce-6e98-43e1-907b-f9851d19114e","doc_no":"A.6.1.1.6.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9281,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"dc3af461-324a-44d3-8971-6ed3ed93d34b":{"id":"dc3af461-324a-44d3-8971-6ed3ed93d34b","doc_no":"A.6.1.1.6.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9282,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"d8b7f338-3318-462c-a65d-4e49a29398b2":{"id":"d8b7f338-3318-462c-a65d-4e49a29398b2","doc_no":"A.6.1.1.6.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9283,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"27bfc7f9-d9da-42bc-8fde-7c3aacb0b2c7":{"id":"27bfc7f9-d9da-42bc-8fde-7c3aacb0b2c7","doc_no":"A.6.1.1.6.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9284,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"14a3b7fc-37f3-4407-a59b-061df4b7fc73":{"id":"14a3b7fc-37f3-4407-a59b-061df4b7fc73","doc_no":"A.6.1.1.6.2.3.1.2.1.1.1","title":"Terms","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9285,"content":"Pattern will pay 0.50% of its market capitalization per year in USDS.","contentHash":"9fa3de128eb9715afd3c700b3caa37ed040fcf87655dd82d72ca9790c4cd81e4","addressRefs":[]},"5147797a-7219-4f30-ab4e-38b6306bcc3b":{"id":"5147797a-7219-4f30-ab4e-38b6306bcc3b","doc_no":"A.6.1.1.6.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9286,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"a1718608-c793-4521-a2ae-df2a685f2070":{"id":"a1718608-c793-4521-a2ae-df2a685f2070","doc_no":"A.6.1.1.6.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9287,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"46b382ec-7179-44ce-b07c-f53a33b8bf23":{"id":"46b382ec-7179-44ce-b07c-f53a33b8bf23","doc_no":"A.6.1.1.6.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9288,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"8d0b0487-8d3d-4663-8096-04b32c52b073":{"id":"8d0b0487-8d3d-4663-8096-04b32c52b073","doc_no":"A.6.1.1.6.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9289,"content":"The process to pay 0.50% of Pattern's market capitalization per year in USDS will be specified in future iterations of the Pattern Artifact.","contentHash":"ccbbdb75a4f5ec40dfb46b262f4e14acd64194db4e0470336df36d81e82c99c9","addressRefs":[]},"8508d44e-41ca-41ed-a491-3d5135ce490a":{"id":"8508d44e-41ca-41ed-a491-3d5135ce490a","doc_no":"A.6.1.1.6.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9290,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"3564cdbb-e173-413c-b21d-1fa25259470e":{"id":"3564cdbb-e173-413c-b21d-1fa25259470e","doc_no":"A.6.1.1.6.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9291,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"899424bc-a0b7-4766-aa19-2b17e6b37991":{"id":"899424bc-a0b7-4766-aa19-2b17e6b37991","doc_no":"A.6.1.1.6.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9292,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"87094d8d-a42a-4665-8215-615124a8e123":{"id":"87094d8d-a42a-4665-8215-615124a8e123","doc_no":"A.6.1.1.6.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9293,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0b1d35c9-7ae9-4b23-a5c8-360c5af2d58c":{"id":"0b1d35c9-7ae9-4b23-a5c8-360c5af2d58c","doc_no":"A.6.1.1.6.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9294,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"cf3abeef-7836-457a-a659-e432d1eb7c20":{"id":"cf3abeef-7836-457a-a659-e432d1eb7c20","doc_no":"A.6.1.1.6.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9295,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"88e57951-b13f-4c14-8af1-c0b6f757df42":{"id":"88e57951-b13f-4c14-8af1-c0b6f757df42","doc_no":"A.6.1.1.6.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9296,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"7493f2d6-1910-43fd-b7db-40f435529fe3":{"id":"7493f2d6-1910-43fd-b7db-40f435529fe3","doc_no":"A.6.1.1.6.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9297,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"33b2f3db-d757-472e-be6e-c03b376f4ec3":{"id":"33b2f3db-d757-472e-be6e-c03b376f4ec3","doc_no":"A.6.1.1.6.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9298,"content":"The documents herein contain all data and specifications for Pattern's instances of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"95422f408523171a829254ad89a53a0cae141db2449d911a51e728246c648b66","addressRefs":[]},"c1ba86c9-f638-4ebe-9346-e22377841c2c":{"id":"c1ba86c9-f638-4ebe-9346-e22377841c2c","doc_no":"A.6.1.1.6.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9299,"content":"The documents herein organize all base information relevant to Pattern's usage of the Upkeep Rebate Primitive.","contentHash":"9dc2efd1a81b71a1dcba693145a28c1e292804bd80b466669424d0982d1111c1","addressRefs":[]},"91965eb0-adbe-44fb-90eb-b4b898579c02":{"id":"91965eb0-adbe-44fb-90eb-b4b898579c02","doc_no":"A.6.1.1.6.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9300,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"c3368a88-6bd8-4111-8e9a-e22d9afe1bfe":{"id":"c3368a88-6bd8-4111-8e9a-e22d9afe1bfe","doc_no":"A.6.1.1.6.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9301,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"04802fe1-3d1b-4499-8006-22048d3e8b6c":{"id":"04802fe1-3d1b-4499-8006-22048d3e8b6c","doc_no":"A.6.1.1.6.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9302,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.3.2.2.1 - Single Instance Configuration Document](77bd8e6f-aad2-4830-8822-1abc3281bfa8).","contentHash":"e568915e0bcc5da97dd35d912857159135769e3a117c947021ba26535a7edc83","addressRefs":[]},"85c523fe-a6be-4695-ac8c-1d584f285324":{"id":"85c523fe-a6be-4695-ac8c-1d584f285324","doc_no":"A.6.1.1.6.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9303,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"9da85689-3fae-4814-8e7e-3c817f1c09f8":{"id":"9da85689-3fae-4814-8e7e-3c817f1c09f8","doc_no":"A.6.1.1.6.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9304,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"d3c8ecd1-8a0f-4ffe-a181-3906b7daae8d":{"id":"d3c8ecd1-8a0f-4ffe-a181-3906b7daae8d","doc_no":"A.6.1.1.6.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9305,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"f58354db-e99a-426a-a5b6-0517e65d0cf3":{"id":"f58354db-e99a-426a-a5b6-0517e65d0cf3","doc_no":"A.6.1.1.6.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9306,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"b00aa59c-d001-4043-ac29-6f4ea207183e":{"id":"b00aa59c-d001-4043-ac29-6f4ea207183e","doc_no":"A.6.1.1.6.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9307,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"17d4ef14-d08a-4c23-b4b6-629adf08ef80":{"id":"17d4ef14-d08a-4c23-b4b6-629adf08ef80","doc_no":"A.6.1.1.6.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9308,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"805a832a-10ef-49d8-b1de-9e5d28f29f95":{"id":"805a832a-10ef-49d8-b1de-9e5d28f29f95","doc_no":"A.6.1.1.6.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9309,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"77bd8e6f-aad2-4830-8822-1abc3281bfa8":{"id":"77bd8e6f-aad2-4830-8822-1abc3281bfa8","doc_no":"A.6.1.1.6.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9310,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"8ecbe4ce-28f0-48d0-844f-7d236c242264":{"id":"8ecbe4ce-28f0-48d0-844f-7d236c242264","doc_no":"A.6.1.1.6.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9311,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"79728f8b-64c3-49d1-9477-990073c87c94":{"id":"79728f8b-64c3-49d1-9477-990073c87c94","doc_no":"A.6.1.1.6.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9312,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"377b7042-5cee-4baf-a77f-39acd0f99854":{"id":"377b7042-5cee-4baf-a77f-39acd0f99854","doc_no":"A.6.1.1.6.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9313,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"106faf37-f072-4cac-aa1d-50982c04acea":{"id":"106faf37-f072-4cac-aa1d-50982c04acea","doc_no":"A.6.1.1.6.2.3.2.2.1.2.1.1","title":"Pattern Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9314,"content":"Pattern keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"9b84c929604e93d99aefce4a5048495f96155685fa9374b1496ecfabba630f2c","addressRefs":[]},"5abf2834-3f70-4ca9-9bf8-14df17e1f1bd":{"id":"5abf2834-3f70-4ca9-9bf8-14df17e1f1bd","doc_no":"A.6.1.1.6.2.3.2.2.1.2.1.2","title":"Pattern Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9315,"content":"When paying Ecosystem Upkeep fees, Pattern deducts the rebate from the fees it pays.","contentHash":"217786828df1b6d697a067de00f93bdf78f6768bbc754f5f00a249e4afff9417","addressRefs":[]},"3e913724-ce5a-41a5-b9db-27ba25c35c06":{"id":"3e913724-ce5a-41a5-b9db-27ba25c35c06","doc_no":"A.6.1.1.6.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9316,"content":"Operational GovOps reviews Pattern's calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Pattern Prime\" category and work with Pattern to resolve the disagreement. If Operational GovOps and Pattern cannot resolve the disagreement, it must be escalated to Core GovOps.","contentHash":"667a903923dae351af12c6b2e0323fbf04ec01e04f8183b71b4967e39db1df41","addressRefs":[]},"e5897490-739e-4778-9eb3-15a57309bf7b":{"id":"e5897490-739e-4778-9eb3-15a57309bf7b","doc_no":"A.6.1.1.6.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9317,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"a506aba7-1c37-46eb-954c-bb99b83d59c6":{"id":"a506aba7-1c37-46eb-954c-bb99b83d59c6","doc_no":"A.6.1.1.6.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9318,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"c1002f65-de06-45e0-ab0b-99d44279ffb3":{"id":"c1002f65-de06-45e0-ab0b-99d44279ffb3","doc_no":"A.6.1.1.6.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9319,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"136d9a42-5b8f-4e7c-835a-bbcdff8e3d9a":{"id":"136d9a42-5b8f-4e7c-835a-bbcdff8e3d9a","doc_no":"A.6.1.1.6.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9320,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"e432bb7e-0054-4306-a573-494655454d35":{"id":"e432bb7e-0054-4306-a573-494655454d35","doc_no":"A.6.1.1.6.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9321,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"1e486b02-fcb5-4c95-b832-153f592b5f13":{"id":"1e486b02-fcb5-4c95-b832-153f592b5f13","doc_no":"A.6.1.1.6.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9322,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"3aa8f9e7-67ca-4411-9938-d3e7472f3cfe":{"id":"3aa8f9e7-67ca-4411-9938-d3e7472f3cfe","doc_no":"A.6.1.1.6.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9323,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"31495a53-3a81-466f-bb02-ac7ba4180851":{"id":"31495a53-3a81-466f-bb02-ac7ba4180851","doc_no":"A.6.1.1.6.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9324,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"fcc2d538-6b23-45bc-b153-53d2e25ab056":{"id":"fcc2d538-6b23-45bc-b153-53d2e25ab056","doc_no":"A.6.1.1.6.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9325,"content":"The documents herein implement the SkyLink Primitives for Pattern. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"7ae83d324fb59f144de8cdddd820410e20822580725127c107a26299edf3e9b1","addressRefs":[]},"f2056d2f-e669-41a8-b402-184c8f12092c":{"id":"f2056d2f-e669-41a8-b402-184c8f12092c","doc_no":"A.6.1.1.6.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9326,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"ea322fca1dab1d58c8a0145e53ecdaa88f1a7f64e31a42e1803bd0027892559b","addressRefs":[]},"028c364c-6ac4-42b1-86a7-afb6b255d3f7":{"id":"028c364c-6ac4-42b1-86a7-afb6b255d3f7","doc_no":"A.6.1.1.6.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9327,"content":"The documents herein organize all base information relevant to Pattern's usage of the Token SkyLink Primitive.","contentHash":"b650948ed0fd2f53265b2cce4ec909dfc2368eac7f15a673e25bca7aa8730976","addressRefs":[]},"6239f922-626f-4d62-aa0d-4404f3728578":{"id":"6239f922-626f-4d62-aa0d-4404f3728578","doc_no":"A.6.1.1.6.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9328,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"584acc45-1d1c-4133-8c6a-e37ffeba25a7":{"id":"584acc45-1d1c-4133-8c6a-e37ffeba25a7","doc_no":"A.6.1.1.6.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9329,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"36da00c5-3634-43f9-882f-f8ccfb5220ae":{"id":"36da00c5-3634-43f9-882f-f8ccfb5220ae","doc_no":"A.6.1.1.6.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9330,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"7c196ec5-654e-4f5c-91ea-6e8fc3701edd":{"id":"7c196ec5-654e-4f5c-91ea-6e8fc3701edd","doc_no":"A.6.1.1.6.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9331,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.4.1.1.2 - Active Instances Directory](584acc45-1d1c-4133-8c6a-e37ffeba25a7), whereas failed Invocations are Archived in [A.6.1.1.6.2.4.1.1.5 - Hub Data Repository](598e9e9c-1e55-41df-916e-d7df282a60a1).","contentHash":"6bba0f78732a241c87278e2e311f8b396a915608a576fec74191f6a1246f31e2","addressRefs":[]},"598e9e9c-1e55-41df-916e-d7df282a60a1":{"id":"598e9e9c-1e55-41df-916e-d7df282a60a1","doc_no":"A.6.1.1.6.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9332,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"43ac33bd-cc48-4c9b-bad2-1b5502e8b66e":{"id":"43ac33bd-cc48-4c9b-bad2-1b5502e8b66e","doc_no":"A.6.1.1.6.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9333,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"55532dd8-2c51-449d-83e5-ff3fbed3db1b":{"id":"55532dd8-2c51-449d-83e5-ff3fbed3db1b","doc_no":"A.6.1.1.6.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9334,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"6b8ee6b3-5a83-4c1e-822d-bad42feed529":{"id":"6b8ee6b3-5a83-4c1e-822d-bad42feed529","doc_no":"A.6.1.1.6.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9335,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"0767e0df-03e9-49ba-b47f-12502213732e":{"id":"0767e0df-03e9-49ba-b47f-12502213732e","doc_no":"A.6.1.1.6.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9336,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"19165634-385c-4bba-a279-685f6bd91492":{"id":"19165634-385c-4bba-a279-685f6bd91492","doc_no":"A.6.1.1.6.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9337,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"688eb991-5d06-4f3a-b847-e258d96857ab":{"id":"688eb991-5d06-4f3a-b847-e258d96857ab","doc_no":"A.6.1.1.6.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9338,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.4.1.2 - Active Instances](0767e0df-03e9-49ba-b47f-12502213732e).","contentHash":"7f9a22b3b0fa174c27a9148b141d9f50166004460887cfaf00ee76238daa1907","addressRefs":[]},"0545c0f9-eab5-4b9e-93f9-cb59a8267312":{"id":"0545c0f9-eab5-4b9e-93f9-cb59a8267312","doc_no":"A.6.1.1.6.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9339,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Pattern. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"2f2ca61eb2e0dee34a070bb059507d770e53fd61cbc5f64c717d7feb4c4386a7","addressRefs":[]},"6cfff1d4-93e9-41cb-9e40-6051a43975c1":{"id":"6cfff1d4-93e9-41cb-9e40-6051a43975c1","doc_no":"A.6.1.1.6.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9340,"content":"The documents herein contain all data and specifications for Pattern's instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"1a420206bef6b21448ab3f55a924c4f55bebb308d996f9350347168ce7df5698","addressRefs":[]},"076aeee9-3225-4b3e-8d2c-da278c0cb334":{"id":"076aeee9-3225-4b3e-8d2c-da278c0cb334","doc_no":"A.6.1.1.6.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9341,"content":"The documents herein organize all base information relevant to Pattern's usage of the Distribution Reward Primitive.","contentHash":"171eaf8873f7c154f4b322c05b5d5bc58e1f7e5f957c9ca0b99e218a3fc6b726","addressRefs":[]},"0fb59894-f344-4fbf-8918-7a8cb271c3b8":{"id":"0fb59894-f344-4fbf-8918-7a8cb271c3b8","doc_no":"A.6.1.1.6.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9342,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"082222ab-1802-4eb6-91ee-22986f27a43c":{"id":"082222ab-1802-4eb6-91ee-22986f27a43c","doc_no":"A.6.1.1.6.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9343,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"d2443507-e41f-401a-9953-feb3b683c66d":{"id":"d2443507-e41f-401a-9953-feb3b683c66d","doc_no":"A.6.1.1.6.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9344,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"7c88dfbb-08eb-40ac-92e9-8b934a630d2d":{"id":"7c88dfbb-08eb-40ac-92e9-8b934a630d2d","doc_no":"A.6.1.1.6.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9345,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.5.1.1.2 - Active Instances Directory](082222ab-1802-4eb6-91ee-22986f27a43c), whereas failed Invocations are Archived in [A.6.1.1.6.2.5.1.1.5 - Hub Data Repository](f10a7cf3-932b-4123-9a7d-c8813c50063f).","contentHash":"4f89d234d9f20ea060ffffa2bb20d46ff0298b53c2ec75f9a5865bcb2e6e5312","addressRefs":[]},"f10a7cf3-932b-4123-9a7d-c8813c50063f":{"id":"f10a7cf3-932b-4123-9a7d-c8813c50063f","doc_no":"A.6.1.1.6.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9346,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ee7ee835-4894-489b-a0cc-08b649e1ecf5":{"id":"ee7ee835-4894-489b-a0cc-08b649e1ecf5","doc_no":"A.6.1.1.6.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9347,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"e8a949ae-d26b-4a59-a0e0-8657d99c0f59":{"id":"e8a949ae-d26b-4a59-a0e0-8657d99c0f59","doc_no":"A.6.1.1.6.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9348,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"6785c95f-4712-4760-8d56-29717402f654":{"id":"6785c95f-4712-4760-8d56-29717402f654","doc_no":"A.6.1.1.6.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9349,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"c1b876c3-5328-4313-b957-e5b0c3eb7d42":{"id":"c1b876c3-5328-4313-b957-e5b0c3eb7d42","doc_no":"A.6.1.1.6.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9350,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"2759639a-3ed8-4f82-9cea-c9beeb927318":{"id":"2759639a-3ed8-4f82-9cea-c9beeb927318","doc_no":"A.6.1.1.6.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9351,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"e3a7fb2e-9621-4066-a73d-96340caec41e":{"id":"e3a7fb2e-9621-4066-a73d-96340caec41e","doc_no":"A.6.1.1.6.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9352,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.5.1.2 - Active Instances](c1b876c3-5328-4313-b957-e5b0c3eb7d42).","contentHash":"ad1052d20befc6bba02358a569f4f026b7e96e80e7cdaf2f0fed21fc37222941","addressRefs":[]},"1fb482e6-cb6d-4311-9f2a-be481b65c9c2":{"id":"1fb482e6-cb6d-4311-9f2a-be481b65c9c2","doc_no":"A.6.1.1.6.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9353,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"5b94774d95e1ae72acf5ee3576910b24f1b5f2fe92318505949bcb730e246978","addressRefs":[]},"64832811-c6d5-4269-8bae-f95a7f334cc4":{"id":"64832811-c6d5-4269-8bae-f95a7f334cc4","doc_no":"A.6.1.1.6.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9354,"content":"The documents herein organize all base information relevant to Pattern's usage of the Integration Boost Primitive.","contentHash":"dcd4925c8904219cf2aff352d8d190722faf6da242d02e3550515c033739b9d9","addressRefs":[]},"a8713d41-40eb-48f8-82ee-020948616d59":{"id":"a8713d41-40eb-48f8-82ee-020948616d59","doc_no":"A.6.1.1.6.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9355,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"7c44f1ca-0d6a-481a-82e0-a9aab01badd9":{"id":"7c44f1ca-0d6a-481a-82e0-a9aab01badd9","doc_no":"A.6.1.1.6.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9356,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"e8117148-0c90-4960-baea-bd26800db9ef":{"id":"e8117148-0c90-4960-baea-bd26800db9ef","doc_no":"A.6.1.1.6.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9357,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"571dbaf2-afaf-4e94-ae56-c9fd9f2a7462":{"id":"571dbaf2-afaf-4e94-ae56-c9fd9f2a7462","doc_no":"A.6.1.1.6.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9358,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.5.2.1.2 - Active Instances Directory](7c44f1ca-0d6a-481a-82e0-a9aab01badd9), whereas failed Invocations are Archived in [A.6.1.1.6.2.5.2.1.5 - Hub Data Repository](b70f4e2b-678b-4b71-a3eb-3e8e62e09fe8).","contentHash":"142360889f6a097f8d34b40f7f495070cfcef82ba1a425332ba6068ddabcd29e","addressRefs":[]},"b70f4e2b-678b-4b71-a3eb-3e8e62e09fe8":{"id":"b70f4e2b-678b-4b71-a3eb-3e8e62e09fe8","doc_no":"A.6.1.1.6.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9359,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"b0c2c079-6855-44ca-8e7e-dbfca4da7106":{"id":"b0c2c079-6855-44ca-8e7e-dbfca4da7106","doc_no":"A.6.1.1.6.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9360,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"7d6e06d9-f858-4c77-ab31-16878e06f2b6":{"id":"7d6e06d9-f858-4c77-ab31-16878e06f2b6","doc_no":"A.6.1.1.6.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9361,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"ce1a95be-d2cf-416e-89e0-e61c7a959e04":{"id":"ce1a95be-d2cf-416e-89e0-e61c7a959e04","doc_no":"A.6.1.1.6.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9362,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"15973e56-ba8b-41b9-b7b5-a08879226b1c":{"id":"15973e56-ba8b-41b9-b7b5-a08879226b1c","doc_no":"A.6.1.1.6.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9363,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"27f4e5af-96a6-490f-8f1c-5f745548a4af":{"id":"27f4e5af-96a6-490f-8f1c-5f745548a4af","doc_no":"A.6.1.1.6.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9364,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"f4323304-2a2b-41e2-9be1-adb41d3f1f8e":{"id":"f4323304-2a2b-41e2-9be1-adb41d3f1f8e","doc_no":"A.6.1.1.6.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9365,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.5.2.2 - Active Instances](15973e56-ba8b-41b9-b7b5-a08879226b1c).","contentHash":"e5809d8d09df12831e2e95fd63b0659aa794a4b2445a875c0a52275ba838a4dc","addressRefs":[]},"a6c0ce30-cd60-49ca-875f-b96ffb72273a":{"id":"a6c0ce30-cd60-49ca-875f-b96ffb72273a","doc_no":"A.6.1.1.6.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9366,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"124cba106e639fc66d2b1407f8ccb30631057b0ebb2af1d42545f6ece0b11e67","addressRefs":[]},"d3d4d0b2-e491-4fd5-9c2f-8f2545f0130b":{"id":"d3d4d0b2-e491-4fd5-9c2f-8f2545f0130b","doc_no":"A.6.1.1.6.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9367,"content":"The documents herein organize all base information relevant to Pattern's usage of the Pioneer Chain Primitive.","contentHash":"63fa88df42d31d988884068c0f288875bc6d123a24616086d8064bcac1c6cb6c","addressRefs":[]},"1271c05e-f761-49ae-b26f-650f643e6480":{"id":"1271c05e-f761-49ae-b26f-650f643e6480","doc_no":"A.6.1.1.6.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9368,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"899d30b8-2bc5-4ec9-b888-285fca7e37c1":{"id":"899d30b8-2bc5-4ec9-b888-285fca7e37c1","doc_no":"A.6.1.1.6.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9369,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"0f1efcda-3b38-4255-9c69-16e96d62db42":{"id":"0f1efcda-3b38-4255-9c69-16e96d62db42","doc_no":"A.6.1.1.6.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9370,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"3102c70c-dca5-4211-a978-18319e17524b":{"id":"3102c70c-dca5-4211-a978-18319e17524b","doc_no":"A.6.1.1.6.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9371,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.5.3.1.2 - Active Instances Directory](899d30b8-2bc5-4ec9-b888-285fca7e37c1), whereas failed Invocations are Archived in [A.6.1.1.6.2.5.3.1.5 - Hub Data Repository](53fc4aba-c522-4876-83e6-492c2ee95ca2).","contentHash":"1ec56df641525ec3a552ff84094de448a3d09b7e06e7db9c6bc6878e25ab8d7b","addressRefs":[]},"53fc4aba-c522-4876-83e6-492c2ee95ca2":{"id":"53fc4aba-c522-4876-83e6-492c2ee95ca2","doc_no":"A.6.1.1.6.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9372,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"601ec019-c79f-4142-9ef1-9116c59153a8":{"id":"601ec019-c79f-4142-9ef1-9116c59153a8","doc_no":"A.6.1.1.6.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9373,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"cfd5b108-3fe8-4228-b983-b098a6a3cd08":{"id":"cfd5b108-3fe8-4228-b983-b098a6a3cd08","doc_no":"A.6.1.1.6.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9374,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"076af992-fa03-4e82-80b7-80095ddc96bd":{"id":"076af992-fa03-4e82-80b7-80095ddc96bd","doc_no":"A.6.1.1.6.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9375,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"55104448-6e24-4557-bfb9-5cb4b217b636":{"id":"55104448-6e24-4557-bfb9-5cb4b217b636","doc_no":"A.6.1.1.6.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9376,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"f9ef6582-b22c-4065-bd1f-0f959e2aba53":{"id":"f9ef6582-b22c-4065-bd1f-0f959e2aba53","doc_no":"A.6.1.1.6.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9377,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"0f4adb4b-97d5-40b3-ab09-697eeb1e128c":{"id":"0f4adb4b-97d5-40b3-ab09-697eeb1e128c","doc_no":"A.6.1.1.6.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9378,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.5.3.2 - Active Instances](55104448-6e24-4557-bfb9-5cb4b217b636).","contentHash":"d92000734d6b5d075748462ebd73396785732fa2fee86b4aa783d5306dca77ab","addressRefs":[]},"5994da99-c086-4877-8777-3be6e5e63562":{"id":"5994da99-c086-4877-8777-3be6e5e63562","doc_no":"A.6.1.1.6.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9379,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Pattern. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"5b4ffba71aa7fa8b6d08f5a344e90abe21683e8f1e11a8a918bbda98702c7636","addressRefs":[]},"62ce0e4a-e6fb-4617-8bb6-46e89a83d5bc":{"id":"62ce0e4a-e6fb-4617-8bb6-46e89a83d5bc","doc_no":"A.6.1.1.6.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9380,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Allocation System Primitive. See [A.2.2.9.1 - Allocation System Primitive](9db14ab7-bb4b-4751-8084-843bd4359f2a).","contentHash":"11f6a9ce23aa064c3e2fee094439a223608ca72e51c36aac48e6dc75b5c7e1af","addressRefs":[]},"ac8bef79-4452-44b6-8947-2dff84da918e":{"id":"ac8bef79-4452-44b6-8947-2dff84da918e","doc_no":"A.6.1.1.6.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9381,"content":"The documents herein organize all base information relevant to Pattern's usage of the Allocation System Primitive.","contentHash":"1d1ac369abdc7585a656793bf6692135bedeb7088e44da947d2cffe179cdb1d3","addressRefs":[]},"7e0762bd-f890-481f-b26c-f737985054e6":{"id":"7e0762bd-f890-481f-b26c-f737985054e6","doc_no":"A.6.1.1.6.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9382,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"9fa776cb-2485-4c4d-92f2-02789b1c914b":{"id":"9fa776cb-2485-4c4d-92f2-02789b1c914b","doc_no":"A.6.1.1.6.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9383,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"d2ae0f64-bb95-4c50-961e-52c82dd52586":{"id":"d2ae0f64-bb95-4c50-961e-52c82dd52586","doc_no":"A.6.1.1.6.2.6.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9384,"content":"The documents herein contain a Directory of all Instances on Ethereum Mainnet of the Allocation System Primitive with Instance status of `Active`.","contentHash":"cfd1cdbfaa1c46010dde8c6a850409b0b5d25ece87b06d03d1df44b1b8420b32","addressRefs":[]},"5572abc6-902d-4c4d-8eee-0823a3616c36":{"id":"5572abc6-902d-4c4d-8eee-0823a3616c36","doc_no":"A.6.1.1.6.2.6.1.1.2.1.1","title":"Maple","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9385,"content":"The Ethereum Mainnet Instances Directory of the Maple Protocol with `Active` Status are stored herein.","contentHash":"23d31010d23f63ecd6441f2d5871677626acdbf4cc73a664c3cb7e7130524d34","addressRefs":[]},"5755702e-4107-4d81-a986-39b970dce859":{"id":"5755702e-4107-4d81-a986-39b970dce859","doc_no":"A.6.1.1.6.2.6.1.1.2.1.1.1","title":"Ethereum Mainnet - Maple USDC Instance Configuration Document Location","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9386,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.6.1.3.1.1.1 - Ethereum Mainnet - Maple USDC Instance Configuration Document](50d86fb7-cacd-4f9b-adf4-7056cfe8cd97).","contentHash":"74c029749f0bcc26b854ce3d095d2fabdeac55e30f6e39d40bcc8a95a7d6f1fe","addressRefs":[]},"d447c96a-dec9-4ce7-87fa-44291e6a4c32":{"id":"d447c96a-dec9-4ce7-87fa-44291e6a4c32","doc_no":"A.6.1.1.6.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9387,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"c9a77c32-b63a-4d9a-8dd3-f09b05e20eda":{"id":"c9a77c32-b63a-4d9a-8dd3-f09b05e20eda","doc_no":"A.6.1.1.6.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9388,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.6.1.1.2 - Active Instances Directory](9fa776cb-2485-4c4d-92f2-02789b1c914b), whereas failed Invocations are Archived in [A.6.1.1.6.2.6.1.1.5 - Hub Data Repository](8a6d2cf2-ca58-48a3-b5fc-0cf932257e9e).","contentHash":"d3a47c632d415dc11946201681801c987eb3a114a522e6540d426e28e8022baa","addressRefs":[]},"8a6d2cf2-ca58-48a3-b5fc-0cf932257e9e":{"id":"8a6d2cf2-ca58-48a3-b5fc-0cf932257e9e","doc_no":"A.6.1.1.6.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9389,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"36721bb0-2049-4660-b8fe-20408586d8a9":{"id":"36721bb0-2049-4660-b8fe-20408586d8a9","doc_no":"A.6.1.1.6.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9390,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"30befb6f-af6f-451d-88e2-5df33fb8e7f4":{"id":"30befb6f-af6f-451d-88e2-5df33fb8e7f4","doc_no":"A.6.1.1.6.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9391,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"d137860e-b7f0-4601-a6ce-c98dbfc1d90c":{"id":"d137860e-b7f0-4601-a6ce-c98dbfc1d90c","doc_no":"A.6.1.1.6.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9392,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"d02fc174-54ea-4336-8f61-99f530ea533b":{"id":"d02fc174-54ea-4336-8f61-99f530ea533b","doc_no":"A.6.1.1.6.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9393,"content":"The documents herein provide general specifications of the Pattern Liquidity Layer and define Pattern's overarching strategy and operational framework for managing across all Instances.","contentHash":"29293628f5357495e3681312681d071995dce72b04770b734d439baab0c4262d","addressRefs":[]},"45faacc7-d61e-4446-9900-d1aa2bb2280e":{"id":"45faacc7-d61e-4446-9900-d1aa2bb2280e","doc_no":"A.6.1.1.6.2.6.1.2.1","title":"General Specifications","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9394,"content":"The documents herein contain general specifications for the Pattern Liquidity Layer.","contentHash":"cde3c77a4781722a783553d9258a2eb3d1c47d927d9f5879b02ef5a9448f16d7","addressRefs":[]},"73d09dec-c8d4-425c-9d54-2ef73a82d6b9":{"id":"73d09dec-c8d4-425c-9d54-2ef73a82d6b9","doc_no":"A.6.1.1.6.2.6.1.2.1.1","title":"Pattern Liquidity Layer Architecture","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9395,"content":"The documents herein describe the high-level design of the Pattern Liquidity Layer, including its key smart contracts and their functionality.","contentHash":"d382ee0238a78e5b39c26d9dd9a701381e9c210e1b496ae4b24f1542b69eebc7","addressRefs":[]},"440cb15b-0421-444a-aa3b-fc14a3f11026":{"id":"440cb15b-0421-444a-aa3b-fc14a3f11026","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1","title":"Pattern Liquidity Layer Addresses","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9396,"content":"The subdocuments herein provide the addresses of the Pattern Liquidity Layer’s constituent contracts.","contentHash":"f840308492274221289c529104bf0945b61e1954f9b8d0aa83e75c8ceb431a27","addressRefs":[]},"b64940f7-ae82-49c7-84ae-0019aff1d7f7":{"id":"b64940f7-ae82-49c7-84ae-0019aff1d7f7","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.1","title":"Allocator Contract Addresses","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9397,"content":"The documents herein contain global key addresses for the Allocator Contracts.","contentHash":"a99119eb26b8e6fbaae81a45fa911afc0af3344a9ea2bbcb90fc7cf9bd94fe9c","addressRefs":[]},"54c9cfe2-b5d7-425b-a9ee-bf6901066437":{"id":"54c9cfe2-b5d7-425b-a9ee-bf6901066437","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.1.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9398,"content":"The documents herein contain the Allocator Contract Addresses on the Ethereum Mainnet.","contentHash":"084c1a1c5fbe0a4abc17b09c0096038edfd2c77bdd298abb5411775b166695ef","addressRefs":[]},"deb0a2c0-4a6c-403b-b9b4-79803de4fea8":{"id":"deb0a2c0-4a6c-403b-b9b4-79803de4fea8","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.1.1.1","title":"Allocator Buffer Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9399,"content":"The address of the ALLOCATOR_BUFFER contract is: `0x823459b55D79F0421f24a4828237F7ecb8D7F1ef`.","contentHash":"818df0100305e17cbccffd5ee6054013d03fbe9ce7b8c4dfa21ba7c5a47852d6","addressRefs":["0x823459b55d79f0421f24a4828237f7ecb8d7f1ef"]},"a808de67-ebcb-4b57-83be-eaf1c536bc9b":{"id":"a808de67-ebcb-4b57-83be-eaf1c536bc9b","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.1.1.2","title":"Allocator Oracle Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9400,"content":"The address of the ALLOCATOR_ORACLE contract is: `0xc7B91C401C02B73CBdF424dFaaa60950d5040dB7`","contentHash":"3915a8e9d83e0d12a43a164e763cda42d8b41817675dff88c98314a34152cb8e","addressRefs":["0xc7b91c401c02b73cbdf424dfaaa60950d5040db7"]},"91f97de8-17f8-44e8-a0ec-e140d2ecab30":{"id":"91f97de8-17f8-44e8-a0ec-e140d2ecab30","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.1.1.3","title":"Allocator Registry Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9401,"content":"The address of the ALLOCATOR_REGISTRY contract is: `0xCdCFA95343DA7821fdD01dc4d0AeDA958051bB3B`","contentHash":"b7d71c2ecb2f67f2fe2ddf5b5835dec050bd7652285c86dba07b3fb3e96f8275","addressRefs":["0xcdcfa95343da7821fdd01dc4d0aeda958051bb3b"]},"e2c792e9-abf1-475f-a657-987bc2736a5e":{"id":"e2c792e9-abf1-475f-a657-987bc2736a5e","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.1.1.4","title":"Allocator Roles Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9402,"content":"The address of the ALLOCATOR_ROLES contract is: `0x9A865A710399cea85dbD9144b7a09C889e94E803`","contentHash":"458d4bfa62334f282ee18ad433673de3de9a11f7e2c97fd190afc1bef481a49d","addressRefs":["0x9a865a710399cea85dbd9144b7a09c889e94e803"]},"5ee30a61-2280-4744-8f8f-eb5c5fd56682":{"id":"5ee30a61-2280-4744-8f8f-eb5c5fd56682","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.1.1.5","title":"Allocator Vault Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9403,"content":"The address of the ALLOCATOR_VAULT (ALLOCATOR-PATTERN-A) contract is: `0xbd34fc6AAa1d3F52B314CB9D78023dd23eAc3B0E`.","contentHash":"a742b08023c7158a636cde73ac350bf06c84d55f359a171476641e58730f68cd","addressRefs":["0xbd34fc6aaa1d3f52b314cb9d78023dd23eac3b0e"]},"e21f8717-c764-42c0-a544-d9991345515a":{"id":"e21f8717-c764-42c0-a544-d9991345515a","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2","title":"ALM Contracts","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9404,"content":"The documents herein contain addresses for the ALM Contracts for the Pattern Liquidity Layer.","contentHash":"35d4bfe686bcdcecf7550bf09344b7b096aef327eec3c4cb83c65a8890694d90","addressRefs":[]},"9cad03ef-0226-44b6-b424-c18669e71b00":{"id":"9cad03ef-0226-44b6-b424-c18669e71b00","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9405,"content":"The documents herein contain the ALM Contract Addresses for the Pattern Liquidity Layer on the Ethereum Mainnet.","contentHash":"1d45c4c489cf33a1ec6edb3f73a9976c42185f7054e5ac8ad1718f2e3514c31e","addressRefs":[]},"6d579a04-dc47-47a7-b504-8047782bb4e3":{"id":"6d579a04-dc47-47a7-b504-8047782bb4e3","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2.1.1","title":"ALM Controller Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9406,"content":"The address of the ALM_CONTROLLER (MainnetController) contract is: `0x8739a869E41e828c83EA45575fBDf9FfcC0962b1`","contentHash":"cbfeacef941d750e2c4b4fb20d70d79574ea173ae1697f14b06ce8a22613379d","addressRefs":["0x8739a869e41e828c83ea45575fbdf9ffcc0962b1"]},"2a2092ee-243a-43c8-8e1a-11264b0373db":{"id":"2a2092ee-243a-43c8-8e1a-11264b0373db","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2.1.2","title":"ALM Controller Contract Version","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9407,"content":"The ALM_CONTROLLER contract version is: V.1.6.0","contentHash":"72517f77084344a284929e31fa4bb127f6bf891590d3200870aea1c5c39fe908","addressRefs":[]},"4a56a0a4-2046-4eb8-ab4f-1afb2ee91a66":{"id":"4a56a0a4-2046-4eb8-ab4f-1afb2ee91a66","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2.1.3","title":"ALM Freezer Multisig Address","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9408,"content":"The address of the Multisig that has the Freezer Role is specified in [A.6.1.1.6.2.6.1.2.1.2.2.2 - Freezer Multisig](841e629e-c887-48ec-8219-e0b1c86145d6).","contentHash":"f79f803059114a71ea21af921f03531d78d139487103a6e9cf01d8ab200e6c89","addressRefs":[]},"d55d14f5-d749-4e5c-8931-1c931a4f8ef7":{"id":"d55d14f5-d749-4e5c-8931-1c931a4f8ef7","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2.1.4","title":"ALM Relayer Multisig Address","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9409,"content":"The address of the Multisig that has the Relayer Role is specified in [A.6.1.1.6.2.6.1.2.1.2.2.1 - Relayer Multisig](42f3ceba-f9bc-48bb-aa89-dde3feb21479).","contentHash":"5cf5ca06c577c3c23f2cce4de31c1752e3174d2911c79de02c7cb7acb9ec45f0","addressRefs":[]},"65c5dd3b-9ef8-4ace-9dd8-491431b86242":{"id":"65c5dd3b-9ef8-4ace-9dd8-491431b86242","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2.1.5","title":"ALM Proxy Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9410,"content":"The address of the ALM_PROXY contract is: `0xbA43325E91C79E500486a23E953ab3d8C46f169F`","contentHash":"2355fca6f543cba1fa1f7b4e203665d18dcefcb3c1f1cfb1131d4212d24d3ac9","addressRefs":["0xba43325e91c79e500486a23e953ab3d8c46f169f"]},"5afd1a4a-8803-479c-82e1-21a9b94c047f":{"id":"5afd1a4a-8803-479c-82e1-21a9b94c047f","doc_no":"A.6.1.1.6.2.6.1.2.1.1.1.2.1.6","title":"ALM Rate Limits Contract","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9411,"content":"The address of the ALM_RATE_LIMITS contract is: `0xa77f69f90646A4c0e44cEe1D44Fab08bEb4EA204`","contentHash":"974b332f3f60be631ebaf70a8193ef40e84a77848edfbf84698c7ebc5d8e46ea","addressRefs":["0xa77f69f90646a4c0e44cee1d44fab08beb4ea204"]},"d92dedda-2021-4279-888e-f49fda05a32e":{"id":"d92dedda-2021-4279-888e-f49fda05a32e","doc_no":"A.6.1.1.6.2.6.1.2.1.1.2","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9412,"content":"The documents herein list the off-chain operational parameters for the Pattern Liquidity Layer. These operational parameters are protocol settings managed outside of smart contracts (off-chain), used by operators and off-chain systems to guide the functioning of the Pattern Liquidity Layer.","contentHash":"35f2d04d9f7e0bebfe565de1e41ba7562f6ff32abd4809c78eb2399e4d884570","addressRefs":[]},"83b318cc-a2de-4f00-a340-04699481af4e":{"id":"83b318cc-a2de-4f00-a340-04699481af4e","doc_no":"A.6.1.1.6.2.6.1.2.1.1.2.1","title":"Off-chain Operational Parameters For Ethereum Mainnet","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9413,"content":"The document herein lists the current off-chain operational parameters for the Pattern Liquidity Layer on Ethereum Mainnet.","contentHash":"de1a25d30009dc4f5d7a7603880cd71e5a50dfa4550d67b5f5bdffe39cb22b06","addressRefs":[]},"0d3a94a6-7e10-426a-8542-585120e4a77d":{"id":"0d3a94a6-7e10-426a-8542-585120e4a77d","doc_no":"A.6.1.1.6.2.6.1.2.1.1.2.1.1","title":"Minimum Operation Size Ethereum Mainnet","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9414,"content":"The minimum transaction size for operations on Ethereum Mainnet is (`MAINNET_MIN_OPERATION_SIZE`):\n\n- This parameter will be specified in a future iteration of the Pattern Artifact.","contentHash":"9158f9d088257fec7e3145ae4fec46453ffbd577516e8f8e47c0af81d3f18836","addressRefs":[]},"e8c9203a-0241-4be1-9efa-b72e9ae7aa89":{"id":"e8c9203a-0241-4be1-9efa-b72e9ae7aa89","doc_no":"A.6.1.1.6.2.6.1.2.1.1.2.1.2","title":"Debt Ceiling Buffer Ethereum Mainnet","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9415,"content":"The buffer amount below the maximum debt ceiling is (`DEBT_CEILING_BUFFER`):\n\n- This parameter will be specified in a future iteration of the Pattern Artifact.","contentHash":"e7eb08140971957233e9f66771eff570226cd7b7e2cd6b384129572d98ab5c5d","addressRefs":[]},"cdda3be6-f632-44a7-aaae-b5ee01442bd6":{"id":"cdda3be6-f632-44a7-aaae-b5ee01442bd6","doc_no":"A.6.1.1.6.2.6.1.2.1.1.3","title":"Rate Limits","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9416,"content":"The documents herein list the Rate Limits for the Pattern Liquidity Layer on each blockchain.","contentHash":"31dfc2b5f07ca70e7ccc34f72dc5e4cfe737a7a9debcd09ded552bc1583b7398","addressRefs":[]},"08ac5921-06ce-4b7d-9dfa-7a466ed9e7de":{"id":"08ac5921-06ce-4b7d-9dfa-7a466ed9e7de","doc_no":"A.6.1.1.6.2.6.1.2.1.1.3.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9417,"content":"The documents herein list the current `RateLimits` for the Pattern Liquidity Layer on Ethereum Mainnet.","contentHash":"d00957a2953922dcb50586379b02f5e67f5ab7668cdfe7aa1f8389352d94aeb9","addressRefs":[]},"bda93796-f235-4b48-a131-b84fdd5bc920":{"id":"bda93796-f235-4b48-a131-b84fdd5bc920","doc_no":"A.6.1.1.6.2.6.1.2.1.1.3.1.1","title":"Ethereum Mainnet USDS","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9418,"content":"The maximum mint, burn, and swap for USDS on Ethereum Mainnet are located herein.","contentHash":"2f3fcaa53a0aa5e0f2d7caa806ec666aeabba91e6f9a55f775df03062ef7208d","addressRefs":[]},"c71c498c-1529-4bf1-9520-b0a580ce1ffb":{"id":"c71c498c-1529-4bf1-9520-b0a580ce1ffb","doc_no":"A.6.1.1.6.2.6.1.2.1.1.3.1.1.1","title":"USDS Mint Maximum","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9419,"content":"The maximum amount of USDS that can be minted within the Pattern Liquidity Layer (`LIMIT_USDS_MINT`) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"0978de18d6e9563a1a14b196cdc90a91e44e9bfb6163c085e828030b0a4cb73b","addressRefs":[]},"55c46a1a-5a5a-44b6-a184-c7dbe4a4f68d":{"id":"55c46a1a-5a5a-44b6-a184-c7dbe4a4f68d","doc_no":"A.6.1.1.6.2.6.1.2.1.1.3.1.1.2","title":"USDS Burn Maximum","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9420,"content":"The maximum amount of USDS that can be burned within the Pattern Liquidity Layer (`LIMIT_USDS_BURN`) is specified in the document herein.\n\n- `maxAmount`: This parameter will be specified in a future iteration of the Pattern Artifact.\n- `slope`: This parameter will be specified in a future iteration of the Pattern Artifact.","contentHash":"26cf8cc02a3bb01d7fff875d1a4d3174ad8285a57537011cfca12f28c6b79534","addressRefs":[]},"c73a58b7-0931-44ab-8599-eca4dc70194a":{"id":"c73a58b7-0931-44ab-8599-eca4dc70194a","doc_no":"A.6.1.1.6.2.6.1.2.1.1.3.1.1.3","title":"USDS For USDC Swap Maximum","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9421,"content":"The maximum amount of USDS that can be swapped for USDC by the Pattern Liquidity Layer in the Mainnet PSM (`LIMIT_USDS_TO_USDC`) is specified in the document herein.\n\n- `maxAmount`: 100,000,000 USDS\n- `slope`: 50,000,000 USDS per day","contentHash":"1452e75a6a6f9cbee1a73a5520cb5ad08b9158c580525382202d6bae1f423016","addressRefs":[]},"d3dc636f-e81d-4889-a84c-d7818ef48b6b":{"id":"d3dc636f-e81d-4889-a84c-d7818ef48b6b","doc_no":"A.6.1.1.6.2.6.1.2.1.1.4","title":"On-chain Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9422,"content":"The documents herein list general on-chain parameters for the Pattern Liquidity Layer.","contentHash":"d7e94bb0d4fcdb5148f3c90ac35ba29b016566b21a28b5d04e7e45d09afe5eb7","addressRefs":[]},"e8c676bb-a818-47dc-bd1c-05199588ba4f":{"id":"e8c676bb-a818-47dc-bd1c-05199588ba4f","doc_no":"A.6.1.1.6.2.6.1.2.1.1.4.1","title":"Allocator Vault Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9423,"content":"The Allocator Vault parameters for ALLOCATOR-PATTERN-A are defined in [A.3.7.1.2.1.5 - ALLOCATOR-PATTERN-A Parameters](322e7ccc-6dcb-4f83-96e5-d8f2fa87cd00).","contentHash":"74b326f6093684eee92fe62fa5e3d178eac37cf34caacbedcfb77a22a3e1dbf8","addressRefs":[]},"a8094362-4ca8-4bf0-a1d8-bbed3c80d61c":{"id":"a8094362-4ca8-4bf0-a1d8-bbed3c80d61c","doc_no":"A.6.1.1.6.2.6.1.2.1.1.4.2","title":"Whitelisting Of ALMProxy","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9424,"content":"The ALMProxy for Pattern must be whitelisted on the LitePSM. This will effectively allow Pattern to call `buyGemNoFee` and `sellGemNoFee` on the `MCD_LITE_PSM_USDC_A` contract.","contentHash":"17a2b08e3bb366d764e6b1f0dc53063b23f7396a2a2906e9c325ad1c66f1bca9","addressRefs":[]},"7c432de2-411e-497b-82b3-17c6853cb0b9":{"id":"7c432de2-411e-497b-82b3-17c6853cb0b9","doc_no":"A.6.1.1.6.2.6.1.2.1.2","title":"Governance Processes","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9425,"content":"The documents herein describe the specific governance processes for the Pattern Liquidity Layer.","contentHash":"d2e5d4818a9409bcac1dd43fe29f261f18a540acfed54e7fb3cd422356665e31","addressRefs":[]},"3d4aba3f-a9d8-41c6-a132-c292cabab25e":{"id":"3d4aba3f-a9d8-41c6-a132-c292cabab25e","doc_no":"A.6.1.1.6.2.6.1.2.1.2.1","title":"Invoking New Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9426,"content":"The governance process to invoke a new Instance of the Allocation System Primitive follows the Root Edit process see [A.6.1.1.6.2.2.2.2.1.2 - Operational Process Definition](0a6525e3-429d-4955-8dac-9fc61f6643f8).","contentHash":"f31637365b2fed7aa1d2c9305af2a20f70722f9790b443f3095b9ee4d10bf77e","addressRefs":[]},"cf32471f-42ca-4299-a84c-ccf437ec6950":{"id":"cf32471f-42ca-4299-a84c-ccf437ec6950","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2","title":"Multisigs","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9427,"content":"The documents herein define multisigs that have privileged access to manage the Pattern Liquidity Layer.","contentHash":"e6160c2f3f0c9f8ac30a666a529f373533e5494193158deb6fd07cb661f8b645","addressRefs":[]},"42f3ceba-f9bc-48bb-aa89-dde3feb21479":{"id":"42f3ceba-f9bc-48bb-aa89-dde3feb21479","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.1","title":"Relayer Multisig","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9428,"content":"The Relayer Multisig has the `RELAYER_ROLE` as defined in [A.6.1.1.6.2.6.1.2.2.1.1.2 - Relayer Role](905e342b-8dca-4fbc-8673-f6fabb6b29fd) and is controlled by Operational GovOps Soter Labs.","contentHash":"e749711bd60fd29f5b5c7cf067ddc75168e05f080009cb8568463ec7d6c00386","addressRefs":[]},"77969281-5739-4eba-a856-6b89259b26e1":{"id":"77969281-5739-4eba-a856-6b89259b26e1","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.1.1","title":"Address","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9429,"content":"The address of the Relayer Multisig on the Ethereum Mainnet is `0xd00665Df77E0b1294Ae2bdC3662F870092f6737B`.","contentHash":"5aa2fdead6904a8f063aacddbaa5eb2b1669be120acdc1f340f357d392db5410","addressRefs":["0xd00665df77e0b1294ae2bdc3662f870092f6737b"]},"15f7cf5c-7e06-4a26-8f2f-2adacf21ec32":{"id":"15f7cf5c-7e06-4a26-8f2f-2adacf21ec32","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.1.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9430,"content":"The Relayer Multisig currently has a 2/3 signing requirement.","contentHash":"c9d37bc9fe315e47bffe1afab92453fa966772fbb8272820cc7d823609f165ef","addressRefs":[]},"5660ebf4-dc55-4f91-b5f7-d735195c62a3":{"id":"5660ebf4-dc55-4f91-b5f7-d735195c62a3","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.1.3","title":"Signers","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9431,"content":"The signers of the Relayer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs.","contentHash":"0177bca87529d524d73741f329bbc934b2c26b74c2f10fc3d9c67fe381beaad9","addressRefs":[]},"9fd84c4e-5160-4b87-857d-8dde97d08ff2":{"id":"9fd84c4e-5160-4b87-857d-8dde97d08ff2","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.1.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9432,"content":"The signers of the Relayer Multisig must use the Multisig to exercise the `RELAYER_ROLE` in accordance with the instructions specified in the Pattern Artifact.","contentHash":"dc91346cda8f7b2cf81439171ca3fe2d714f3152b7924e4afb246b053e5d9495","addressRefs":[]},"066ac9dc-3020-4d14-bafe-43e62bacdb90":{"id":"066ac9dc-3020-4d14-bafe-43e62bacdb90","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.1.5","title":"Modification","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9433,"content":"Operational GovOps Soter Labs can change the signers of the Relayer Multisig at any time, so long as there are at least three (3) signers and at least two-thirds of signers are required to execute transactions.","contentHash":"c6504f2d61fe7c505c77b69b767ce09b066852624c244aedcf143f711ffb72d7","addressRefs":[]},"841e629e-c887-48ec-8219-e0b1c86145d6":{"id":"841e629e-c887-48ec-8219-e0b1c86145d6","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.2","title":"Freezer Multisig","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9434,"content":"The Freezer Multisig has the `FREEZER_ROLE` as defined in [A.6.1.1.6.2.6.1.2.2.1.1.4 - Freezer Role](62db1fa2-9958-4692-a2af-907feb5d2c72).","contentHash":"dd5911893abf75556f1867915f5ba389c712fbf0d9397588c86bbde1613e01ef","addressRefs":[]},"008e670d-d877-475a-96f2-950aa0d6c072":{"id":"008e670d-d877-475a-96f2-950aa0d6c072","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.2.1","title":"Address","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9435,"content":"The address of the Freezer Multisig on the Ethereum Mainnet is `0xe728D67bca6cb18dE249325792b6379Eef4618bB`.","contentHash":"9f1a34c29603a16caf00482f1cf3da72105e705367e19d4cbf79a85c7b0df800","addressRefs":["0xe728d67bca6cb18de249325792b6379eef4618bb"]},"f5140241-938a-4775-a873-8ddbb21d6758":{"id":"f5140241-938a-4775-a873-8ddbb21d6758","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.2.2","title":"Required Number Of Signers","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9436,"content":"The Freezer Multisig currently has a 2/5 signing requirement.","contentHash":"5e26a52c6172c820a3edf55895c2df704dad7607cd26054763c73cd1b6fbdbc3","addressRefs":[]},"4525e369-401f-4d39-869f-5b121444ff69":{"id":"4525e369-401f-4d39-869f-5b121444ff69","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.2.3","title":"Signers","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9437,"content":"The signers of the Freezer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs, one (1) address controlled by Operational Facilitator Redline Facilitation Group, and one (1) address controlled by Pattern.","contentHash":"c9e6032290cb9770421ef8402ec14199003ec22834cd1da3ce1c6126dbd5c164","addressRefs":[]},"db641bf1-41f3-4035-9d0c-9328f79c7b4a":{"id":"db641bf1-41f3-4035-9d0c-9328f79c7b4a","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.2.4","title":"Usage Standards","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9438,"content":"The signers of the Freezer Multisig should exercise their authority to freeze the Pattern Liquidity Layer in the event that Pattern is not complying with rules regarding Risk Capital or Asset Liability Management, or in the event of another emergency.\n\nEach action executed by the Freezer Multisig, including any function calls and their parameters, must be reported to the Sky community within a reasonable time frame through a post on the Sky Forum.","contentHash":"38274b8c1bb6a9499d59b7e69e1fef6ff5cbf1869cc5c2e825617d89ecff6993","addressRefs":[]},"601869a5-973d-46da-b601-7fef88a9e07a":{"id":"601869a5-973d-46da-b601-7fef88a9e07a","doc_no":"A.6.1.1.6.2.6.1.2.1.2.2.2.5","title":"Modification","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9439,"content":"Modification of the signers of the Freezer Multisig must be approved through an Atlas Edit Proposal.\n\nThe only exceptions to this are if: 1) a signer self-reports a loss of access to their private key due to any reason; or 2) a signer explicitly expresses their wish to be removed as a signer. In both cases, the signer is required to communicate the loss of access to their private key, or the wish to be removed as a signer, in the form of a public Sky Forum post. The specific signer should be replaced as soon as possible.\n\nAny changes to the Multisig signers that do not fall within the two exceptions listed above, or that have not been ratified by Sky Governance, should be questioned immediately and treated as malicious. Where malicious activity is suspected, the Core Facilitator must prepare an expedited Executive Vote so that Sky Governance can vote on removing external security access from the Multisig.","contentHash":"5a7d5809b6c81bb95db41542b9e9b65803e19629cf564e404811d45d7486f1e4","addressRefs":[]},"d8fa58f9-8f77-43be-a2d4-6a5b55bc9b67":{"id":"d8fa58f9-8f77-43be-a2d4-6a5b55bc9b67","doc_no":"A.6.1.1.6.2.6.1.2.1.3","title":"Total Risk Capital (TRC) Management","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9440,"content":"The documents herein specify requirements related to Pattern's Total Risk Capital (TRC) management.","contentHash":"3eda7ed4590f76318096371da61147f2bf34c51621f49facdb18feb674c10812","addressRefs":[]},"4a799475-64ce-45e7-8ecd-d63af574dfca":{"id":"4a799475-64ce-45e7-8ecd-d63af574dfca","doc_no":"A.6.1.1.6.2.6.1.2.1.3.1","title":"Pattern Dev Co.'s Operation Of Pattern Liquidity Layer And Agreement Regarding Encumbrance Ratio","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9441,"content":"Pattern Dev Co. will operate the Pattern Liquidity Layer and agrees to stay at or below a 90% Encumbrance Ratio. See [A.3.2.2.7.2.1.1.1 - Encumbrance Ratio](5435f680-aaaa-461a-bcae-4056bb8964d9).","contentHash":"c6870d435404a2273b16da76e27247a590175051b132feaaea3b32b8323666f3","addressRefs":[]},"52c89daa-256c-4779-b644-71615bb092d7":{"id":"52c89daa-256c-4779-b644-71615bb092d7","doc_no":"A.6.1.1.6.2.6.1.2.1.3.2","title":"Pattern Dev Co.'s Total Risk Capital (TRC) Management Processes","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9442,"content":"As operators of the Pattern Liquidity Layer, Pattern Dev Co. automatically inherits, and is subject to, the base class of operational requirements related to Total Risk Capital management defined in [A.2.2.9.1.1.3.2.1.2 - Primes' Total Risk Capital (TRC) Management](3af8a3a2-25e5-44b3-87a4-7df1f2712685). Modifications to the base operational logic automatically propagate to the Pattern Artifact.","contentHash":"0803bc68d3048ce01f775c7b0489e486cefa61935b32aecdb3e3787078e15ab4","addressRefs":[]},"a7ce0d4c-c47d-4976-a40c-d8005d35cd5c":{"id":"a7ce0d4c-c47d-4976-a40c-d8005d35cd5c","doc_no":"A.6.1.1.6.2.6.1.2.2","title":"Pattern Liquidity Layer Operational Processes","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9443,"content":"The documents herein describe common operational procedures for the Pattern Liquidity Layer applicable across multiple Instances.","contentHash":"f77bf39e1af9f0f3be72d9fdc6f0c322f2205e78ed4e85d89cea2a92dfbef4bd","addressRefs":[]},"d15c12da-9ef3-4b47-bcaa-d5832ee57ddf":{"id":"d15c12da-9ef3-4b47-bcaa-d5832ee57ddf","doc_no":"A.6.1.1.6.2.6.1.2.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9444,"content":"The documents herein define the protocol for routine ongoing management of the Pattern Liquidity Layer and its active Instances.","contentHash":"1722a9b7c9d4b0d7d43bf65c204235d23dabbff6326c1f40f7bb5eb7c33eca67","addressRefs":[]},"a7d02d42-69b7-4b55-924f-8513163d23e8":{"id":"a7d02d42-69b7-4b55-924f-8513163d23e8","doc_no":"A.6.1.1.6.2.6.1.2.2.1.1","title":"Role Hierarchy And Permissions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9445,"content":"The documents herein define roles (Admin, Relayer, ALM Controller, and Freezer) and their responsibilities/permissions for managing the Pattern Liquidity Layer.","contentHash":"ca3bb6cfd6417d10006047bfcc15a9ef48b9b7f540e32ed8605f967f674183cd","addressRefs":[]},"6434ee18-27d9-4dcc-9895-0bbf316b8144":{"id":"6434ee18-27d9-4dcc-9895-0bbf316b8144","doc_no":"A.6.1.1.6.2.6.1.2.2.1.1.1","title":"Default Admin Role","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9446,"content":"The admin role (DEFAULT_ADMIN_ROLE) is the role that can grant and revoke any role, including itself and all other roles defined in the contract. The admin role is also used for general admin functions in all contracts. This role is fully controlled by Sky Governance via the Pattern Proxy.\n\n```\nconstructor(address admin) {\n_grantRole(DEFAULT_ADMIN_ROLE, admin);\n```","contentHash":"75083bb03b7e68857ec53936b7fd2cfff3353474183f784b023f4bd364d28375","addressRefs":[]},"905e342b-8dca-4fbc-8673-f6fabb6b29fd":{"id":"905e342b-8dca-4fbc-8673-f6fabb6b29fd","doc_no":"A.6.1.1.6.2.6.1.2.2.1.1.2","title":"Relayer Role","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9447,"content":"The `RELAYER_ROLE` is the address for the Pattern Liquidity Layer ALM Planner off-chain system that calls functions on `Controller` contracts to perform actions on behalf of the `ALMProxy` contract. The Relayer Role may be granted to an address by any address holding the `DEFAULT_ADMIN_ROLE`. The Relayer Role may be removed from an address by any address holding the `DEFAULT_ADMIN_ROLE` or the `FREEZER_ROLE`.","contentHash":"ca6b30f7d22b64e03971baf1ff0a6917f7766f06f147657fa72ee4b5e18d942d","addressRefs":[]},"090b5728-5338-4ab7-83bf-15b213758616":{"id":"090b5728-5338-4ab7-83bf-15b213758616","doc_no":"A.6.1.1.6.2.6.1.2.2.1.1.3","title":"ALM Controller Role","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9448,"content":"The `ALM_CONTROLLER_ROLE` is the address of the role that can call the `call` functions on the `ALMProxy` contract and update `RateLimits` contract. It includes the `MainnetController` and `ForeignController` contracts. ALM Controller contracts are accessed and modified via the Relayer Role.","contentHash":"2338ec34a7da2944765e15ca9792b0c4ec0cffcbf72218d25d3c57bffdc821f2","addressRefs":[]},"62db1fa2-9958-4692-a2af-907feb5d2c72":{"id":"62db1fa2-9958-4692-a2af-907feb5d2c72","doc_no":"A.6.1.1.6.2.6.1.2.2.1.1.4","title":"Freezer Role","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9449,"content":"The `FREEZER_ROLE` is the address of the emergency role that can remove a compromised Relayer.","contentHash":"5613adb996d95581a1f27d5ec22a32a62f59e9d8f62e6ff43f248f6bd75f410f","addressRefs":[]},"a4dba2f1-0f11-4a04-9982-ba41674bcec9":{"id":"a4dba2f1-0f11-4a04-9982-ba41674bcec9","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2","title":"Controller Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9450,"content":"The documents herein describe the purpose and operational use of key functions within the Pattern Liquidity Layer `MainnetController` contracts: USDS management (mint/burn USDS), Asset Transfer Management (direct transfers, protocol deposits/withdrawals), Cross-chain Operations (CCTP bridging).","contentHash":"c17648e464c108b4e588e3bc0a4566229c85fcf5805f332b56e72b55a7570141","addressRefs":[]},"b48c9008-3166-4240-a54d-732463cd28b1":{"id":"b48c9008-3166-4240-a54d-732463cd28b1","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1","title":"Mainnet Controller Contract Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9451,"content":"The documents herein define the functions controlled by the Controller contract for Pattern Liquidity Layer operations on Ethereum Mainnet.","contentHash":"361e5bd6197452cfb17d698ea39b0bbbac31590dd843e4a070139a0870dc3b04","addressRefs":[]},"886081b4-f379-4dba-bf28-038559138713":{"id":"886081b4-f379-4dba-bf28-038559138713","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.1","title":"Admin Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9452,"content":"The documents herein define the operations performed by the admin role (see [A.6.1.1.6.2.6.1.2.2.1.1.1 - Default Admin Role](6434ee18-27d9-4dcc-9895-0bbf316b8144)) within the `MainnetController` contract.","contentHash":"9d9513c87d5508f50e43c91a9a212735427f58d4504ce8a95c7f814d47b88187","addressRefs":[]},"f849be24-c82e-4b13-9a34-027dcaf03fb2":{"id":"f849be24-c82e-4b13-9a34-027dcaf03fb2","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.1.1","title":"Set Mint Recipient For Destination Domain","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9453,"content":"The documents herein define the steps for an admin to specify which address should receive newly minted tokens on a particular destination domain.","contentHash":"e18d032726334c884a3fef8347d5e82a077819f279c99e6388f0e0e6e6c17199","addressRefs":[]},"929818fb-10b0-4520-ba00-5bc2f46815ed":{"id":"929818fb-10b0-4520-ba00-5bc2f46815ed","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.1.1.1","title":"Call setMintRecipient Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9454,"content":"Only an operator with the admin role is able to set the mint recipient for a destination domain. To do so, they must call the `setMintRecipient` function on the Controller contract on mainnet providing the destination domain and the mint recipient address. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role the transaction will revert.\n- The contract will set the selected mint recipient for the specified destination domain.\n- The contract will emit a `MintRecipientSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setMintRecipient(uint32 destinationDomain, bytes32 mintRecipient) external`","contentHash":"62ff9aed370987d09554d45ed885419834c3a8d1ec5fb30268034f868b811e24","addressRefs":[]},"8666edaa-5bd6-4c13-9d3b-5854e90583cb":{"id":"8666edaa-5bd6-4c13-9d3b-5854e90583cb","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.1.2","title":"Set LayerZero Recipient","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9455,"content":"The documents herein define the steps for an admin to specify which address should receive LayerZero messages on a particular destination endpoint.","contentHash":"529b6a0e9f1b8e61a703349f93f307fde7ab7e28b97bc74b29a3dc4b391b9058","addressRefs":[]},"0bc584c7-53da-47ee-9e7f-7514076e5fb0":{"id":"0bc584c7-53da-47ee-9e7f-7514076e5fb0","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.1.2.1","title":"Call setLayerZeroRecipient Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9456,"content":"Only an operator with the admin role is able to set the LayerZero recipient for a destination endpoint. To do so, they must call the `setLayerZeroRecipient` function on the Controller contract on mainnet, providing the destination endpoint ID and the recipient address. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role, the transaction will revert.\n- The contract will set the selected LayerZero recipient for the specified destination endpoint.\n- The contract will emit a `LayerZeroRecipientSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setLayerZeroRecipient(uint32 destinationEndpointId, bytes32 layerZeroRecipient) external`","contentHash":"1a37c01cad0a4ff26a1f5c94db71a0ff3916acb7beca0e135db6a9505a0f1a63","addressRefs":[]},"829d2426-0bd7-44cb-b1c3-b9958706e1b6":{"id":"829d2426-0bd7-44cb-b1c3-b9958706e1b6","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.1.3","title":"Set Maximum Slippage","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9457,"content":"The documents herein define the steps for an admin to set the maximum allowed slippage for a specific pool.","contentHash":"4c5e57348afcaa8e60130af9381c39d20bd2adbbc775d02aaedcfaa0fefeea09","addressRefs":[]},"1d54c38f-02a3-4f15-b101-d23861967337":{"id":"1d54c38f-02a3-4f15-b101-d23861967337","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.1.3.1","title":"Call setMaximumSlippage Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9458,"content":"Only an operator with the admin role is able to set the maximum slippage for a pool. To do so, they must call the `setMaxSlippage` function on the Controller contract on mainnet, providing the pool address and the maximum slippage value. Calling this function will carry out the following actions:\n\n- The contract will confirm the admin status of the operator. If the caller does not have the admin role, the transaction will revert.\n- The contract will set the maximum slippage for the specified pool.\n- The contract will emit a `MaxSlippageSet` event to the blockchain logs.\n\nThe function call is as follows:\n\n`function setMaxSlippage(address pool, uint256 maxSlippage) external`","contentHash":"9a27132420655c07a094df4efaba7ce834dd51c5e50556195377ccbbad5a46b6","addressRefs":[]},"6607a910-567f-4331-9edc-e8f5013f93fb":{"id":"6607a910-567f-4331-9edc-e8f5013f93fb","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2","title":"Relayer Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9459,"content":"The documents herein define the operations performed by the relayer role (see [A.6.1.1.6.2.6.1.2.2.1.1.2 - Relayer Role](905e342b-8dca-4fbc-8673-f6fabb6b29fd)) within the `MainnetController` contract.","contentHash":"4237c68a88000e8f27a0e1f7f8197668f3c0cbbcba8d6a7a6489f55e850ee40b","addressRefs":[]},"ada3451f-65ff-4c36-9706-4ebad61564dc":{"id":"ada3451f-65ff-4c36-9706-4ebad61564dc","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.1","title":"Relayer Vault Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9460,"content":"The documents herein define the operations that are performed to maintain the desired level of liquidity and debt balance of the Pattern Liquidity Layer.","contentHash":"73335298095fc423681cbd581aeebae65b28c4ab1c2c989aa7ec4a987ae6fc13","addressRefs":[]},"52901348-0e9a-4809-94c3-09ceeda40e91":{"id":"52901348-0e9a-4809-94c3-09ceeda40e91","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.1.1","title":"Mint USDS","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9461,"content":"The documents herein define the steps for a relayer to mint USDS from the Sky Allocation Vault to the Pattern ALM Proxy.","contentHash":"82c4e4f4056c001a779f5ac6a905ddf8ca2ff35712cb8a48dcb8693775e2210a","addressRefs":[]},"e58f4b54-eae5-4b7c-a6b5-68406b5b50b7":{"id":"e58f4b54-eae5-4b7c-a6b5-68406b5b50b7","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.1.1.1","title":"Call mintUSDS Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9462,"content":"Only an operator with the relayer role is able to mint USDS. To do so, they must call the `mintUSDS` function on the Controller contract on mainnet with the amount of USDS that is required for minting. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will ensure the `RateLimits` allow for minting the required amount. If the mint amount does not fall within the available Rate Limit the transaction will revert.\n- The contract will reduce the Rate Limit by the amount of USDS minted in this transaction.\n- The contract will mint the required USDS into the buffer contract.\n- The contract will transfer the newly minted USDS from the buffer to the Proxy.\n\nThe function call is as follows:\n\n`function mintUSDS(uint256 usdsAmount) external`","contentHash":"e7409520ec60f2ff611d39df14d23e10c54062d4ded68a08ae6c2dded8120050","addressRefs":[]},"886d04ba-23c3-45fb-ac5d-044288a621e1":{"id":"886d04ba-23c3-45fb-ac5d-044288a621e1","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.1.2","title":"Burn USDS","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9463,"content":"The documents herein define the steps for a relayer to return and then burn Pattern's USDS debt in the Sky Allocation Vault.","contentHash":"9085ae9c52b3e3c1ced2ce5a95d2eb807311359320bdb25a6aa1cc94be489db5","addressRefs":[]},"b974ebda-d402-456a-8b4d-1ea805ac7be0":{"id":"b974ebda-d402-456a-8b4d-1ea805ac7be0","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.1.2.1","title":"Call burnUSDS Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9464,"content":"Only an operator with the relayer role is able to repay vault debt and burn USDS. To do so, they must call the `burnUSDS` function of the Controller contract on mainnet with the amount of USDS that they wish to burn. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will increase the available Rate Limit for minting USDS by the amount of USDS being burned. This increase will be limited by the `maxAmount` parameter in the `Rate Limit` contract.\n- The contract will transfer USDS from the proxy to the buffer.\n- The contract will burn the USDS from the buffer and `wipe` an equivalent amount from the vault's debt.\n\nThe function call is as follows:\n\n`function burnUSDS(uint256 usdsAmount) external`","contentHash":"92b3508ecc9977345338f28c9c2cd842eb213fe799124831e454251715f09f8c","addressRefs":[]},"dfc76ebc-2a7e-453f-8d9f-e2c380af3083":{"id":"dfc76ebc-2a7e-453f-8d9f-e2c380af3083","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.2","title":"ERC-20 Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9465,"content":"The documents herein define the operations that are performed to transfer ERC-20 assets to specified destinations.","contentHash":"d28c31b8ab0d83cf03cc2fc4bd3b795529ab9c078d5d41f64515b4e63120219b","addressRefs":[]},"32b22532-f92b-4544-b1a5-41acead7982e":{"id":"32b22532-f92b-4544-b1a5-41acead7982e","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.2.1","title":"Transfer Asset","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9466,"content":"The documents herein define the steps for a relayer to transfer ERC-20 tokens to a destination address.","contentHash":"88a951aa42193ef6d8f1c08721493c83b1b360651c00ac25507f0762fba7f268","addressRefs":[]},"530a40e2-8322-44ff-b2ce-4ea0821a8b80":{"id":"530a40e2-8322-44ff-b2ce-4ea0821a8b80","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.2.1.1","title":"Call transferAsset Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9467,"content":"Only an operator with the relayer role is able to transfer ERC-20 assets. To do so, they must call the `transferAsset` function on the Controller contract on mainnet, providing the ERC20 asset address, the destination address, and the amount to transfer. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role the transaction will revert.\n- The contract will ensure the `RateLimits` allow for transferring the specified amount of the asset to the destination. If the transfer amount does not fall within the available Rate Limit, the transaction will revert.\n- The contract will execute the ERC-20 `transfer` function, sending the specified amount of the asset to the destination address.\n\nThe function call is as follows:\n\n`function transferAsset(address asset, address destination, uint256 amount) external`","contentHash":"a37fa4e3d9bcbef21e11a96c66528873e5067e6e764388d79dc367fc6a153b48","addressRefs":[]},"c6dcf1ab-9861-4a41-9edc-ea79b705db2d":{"id":"c6dcf1ab-9861-4a41-9edc-ea79b705db2d","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.3","title":"ERC-4626 Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9468,"content":"The documents herein define the general Pattern Liquidity Layer operational procedures for interacting with ERC-4626-compliant tokenized vaults. ERC-4626 is a standard interface for vaults representing shares of an underlying ERC-20 token. Pattern Liquidity Layer can integrate with various ERC-4626 vaults. For instance-specific parameters (such as vault addresses, asset addresses, and rate limits), refer to the relevant ERC-4626 Instance Configuration Document.","contentHash":"01138014fda65f18d4683f9f68fd3c0132288fe4e0d65dccb43019678ce10660","addressRefs":[]},"2dd9a377-0fc7-483a-8942-9eb668b8e334":{"id":"2dd9a377-0fc7-483a-8942-9eb668b8e334","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.3.1","title":"Deposit To ERC-4626 Vault","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9469,"content":"The documents herein define the steps for a relayer to deposit assets from the ALM Proxy to an ERC-4626 vault to receive yield-bearing shares.","contentHash":"b80f044c9242551c8ee6c4a30ae6071bbb378ef9d152494b757f8036bf9763bf","addressRefs":[]},"04ac423a-ef3a-42a2-87de-745da9afded3":{"id":"04ac423a-ef3a-42a2-87de-745da9afded3","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.3.1.1","title":"Call depositERC4626 Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9470,"content":"Only an operator with the relayer role can deposit assets into an ERC-4626 vault. To do so, they must call the `depositERC4626` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to deposit. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for deposit; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the deposit amount is within the allowed rate limit for the specified vault.\n- The contract will approve the vault to spend the underlying asset from the ALM Proxy. The approval and deposit are both performed from the ALM Proxy address.\n- The contract will deposit the specified amount into the vault, and the ALM Proxy will receive the corresponding number of vault shares.\n\nThe function call is as follows:\n\n`function depositERC4626(address token, uint256 amount) external returns (uint256 shares)`","contentHash":"ce859456b41c25d101cea8acf861db4d9b2079df36be9ee6d72c46f6ae166e11","addressRefs":[]},"788ff656-5797-41f3-ac17-38c88e690cc5":{"id":"788ff656-5797-41f3-ac17-38c88e690cc5","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.3.2","title":"Withdraw From ERC-4626 Vault","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9471,"content":"The documents herein define the steps for a relayer to withdraw a specified amount of the underlying asset from an ERC-4626 vault to the ALM Proxy.","contentHash":"b0fc494301a22c5aacd7e45e8742053e4e6ca1a382f8669ace79fb27c6907dee","addressRefs":[]},"40875283-48ec-48f0-8b61-e45d33f976ab":{"id":"40875283-48ec-48f0-8b61-e45d33f976ab","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.3.2.1","title":"Call withdrawERC4626 Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9472,"content":"Only an operator with the relayer role can withdraw assets from an ERC-4626 vault. To do so, they must call the `withdrawERC4626` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to withdraw. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for withdrawal; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the withdrawal amount is within the allowed rate limit for the specified vault.\n- The contract will withdraw the specified amount from the vault, burning the necessary number of vault shares held by the ALM Proxy as part of the withdrawal process.\n- The withdrawn assets will be sent to the ALM Proxy.\n\nThe function call is as follows:\n\n`function withdrawERC4626(address token, uint256 amount) external returns (uint256 shares)`","contentHash":"318aaa8d8238d93540150141605208e2d512228ca44ab72973f9702d31068bd5","addressRefs":[]},"7582c5d2-205c-4ae0-8190-ae583a3db138":{"id":"7582c5d2-205c-4ae0-8190-ae583a3db138","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.3.3","title":"Redeem ERC-4626 Shares","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9473,"content":"The documents herein define the steps for a relayer to redeem vault shares for the underlying asset from an ERC-4626 vault, with the assets sent to the ALM Proxy.","contentHash":"2c3c0a01bfb509b9b3c8f2081f53ed39ef0c035badaffa3c291d5974aed7638d","addressRefs":[]},"037d3def-39bc-4aaf-9c3d-69fb86245f35":{"id":"037d3def-39bc-4aaf-9c3d-69fb86245f35","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.3.3.1","title":"Call redeemERC4626 Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9474,"content":"Only an operator with the relayer role can redeem vault shares for the underlying asset. To do so, they must call the `redeemERC4626` function on the Controller contract on mainnet, providing the number of shares to redeem. The address is the ALM Proxy acting as both the owner of the shares being redeemed and the receiver of the resulting assets. The operation will only succeed if the ALM Proxy holds at least the number of shares specified for redemption; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will redeem the specified number of shares from the vault, sending the resulting assets to the ALM Proxy.\n- After redemption, the contract will update the withdrawal rate limit based on the amount of assets received.\n\nThe function call is as follows:\n\n`function redeemERC4626(address token, uint256 shares) external returns (uint256 assets)`","contentHash":"32623311f5eae5fc43cd31d0d2958331ca741307cf36739b05af881688102150","addressRefs":[]},"f11f72f7-5f70-43e0-ad48-1b3285211284":{"id":"f11f72f7-5f70-43e0-ad48-1b3285211284","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.4","title":"ERC-7540 Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9475,"content":"The documents herein define the general Pattern Liquidity Layer operational procedures for interacting with ERC-7540-compliant tokenized vaults. ERC-7540 is a standard interface for vaults representing and managing multiple underlying assets within a single vault. Pattern Liquidity Layer can integrate with various ERC-7540 vaults. For instance-specific parameters (such as vault addresses, asset addresses, and rate limits), refer to the relevant ERC-7540 Instance Configuration Document.","contentHash":"952791f2b86202d389de89feabc05b0f9cd72b6864e09643d4835a7863178392","addressRefs":[]},"9cb65647-4f82-44a6-9b55-25384e7a6cf6":{"id":"9cb65647-4f82-44a6-9b55-25384e7a6cf6","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.4.1","title":"Deposit To ERC-7540 Vault","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9476,"content":"The documents herein define the steps for a relayer to request and claim deposit of assets from the ALM Proxy to an ERC-7540 vault.","contentHash":"7774d3c7628aa70e17667f0cdf5e7bf69930a59961e22efb75639f71a1b01a91","addressRefs":[]},"138b2674-60c1-4a5c-925a-e30956299119":{"id":"138b2674-60c1-4a5c-925a-e30956299119","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.4.1.1","title":"Call requestDepositERC7540 Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9477,"content":"Only an operator with the relayer role can request a deposit into an ERC-7540 vault. To do so, they must call the `requestDepositERC7540` function on the Controller contract on mainnet, providing the vault token address and the amount of the underlying asset to deposit. The operation will only succeed if the ALM Proxy holds at least the amount of the underlying asset specified for deposit; otherwise, the transaction will revert. The Rate Limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the deposit amount is within the allowed rate limit for the specified vault.\n- The contract will approve the vault to spend the underlying asset from the ALM Proxy. The approval and deposit are both performed from the ALM Proxy address.\n- The contract will submit a deposit request to the vault. Shares will not be received immediately; they must be claimed in a separate step after the vault processes the deposit.\n\nThe function call is as follows:\n\n`function requestDepositERC7540(address token, uint256 amount) external`","contentHash":"d17bb232619cd4c715d0bcf131e6bc8d1a9715d9e667494479645ccd38394999","addressRefs":[]},"fccd0af9-6156-400e-bb4b-27a9d4fca711":{"id":"fccd0af9-6156-400e-bb4b-27a9d4fca711","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.4.1.2","title":"Call claimDepositERC7540 Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9478,"content":"Only an operator with the relayer role can claim shares from an ERC-7540 vault after a deposit request. To do so, they must call the `claimDepositERC7540` function on the Controller contract on mainnet, providing the vault token address. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will determine the maximum number of shares that can be claimed by the ALM Proxy.\n- The contract will claim the shares from the vault, and the ALM Proxy will receive the corresponding number of vault shares.\n\nThe function call is as follows:\n\n`function claimDepositERC7540(address token) external`","contentHash":"cf9133aff1f7250ddcc482b8ca1ac5626e3b1c19496455585148659e91593e03","addressRefs":[]},"b46a85df-ba8e-482a-bcde-b61f2b520190":{"id":"b46a85df-ba8e-482a-bcde-b61f2b520190","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.4.2","title":"Redeem From ERC-7540 Vault","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9479,"content":"The documents herein define the steps for a relayer to request and redeem vault shares for the underlying asset from an ERC-7540 vault, with the assets sent to the ALM Proxy.","contentHash":"0405683434d72ead3b6f43e52f1ee95b114f0b3fc58535114ce95cedd58d400f","addressRefs":[]},"e637cc53-2243-483f-afa2-d3e92a3365fd":{"id":"e637cc53-2243-483f-afa2-d3e92a3365fd","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.4.2.1","title":"Call requestRedeemERC7540 Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9480,"content":"Only an operator with the relayer role can request the redemption of shares from an ERC-7540 vault. To do so, they must call the `requestRedeemERC7540` function on the Controller contract on mainnet, providing the vault token address and the number of shares to redeem. The rate limit configuration serves as whitelisting for vaults. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the redemption amount is within the allowed rate limit for the specified vault.\n- The contract will submit a redemption request to the vault. Assets will not be received immediately; they must be claimed in a separate step after the vault processes the redemption.\n\nThe function call is as follows:\n\n`function requestRedeemERC7540(address token, uint256 shares) external`","contentHash":"4a348f874c820a14a3a6c15b91275ccd9bcc808ff6def9fa092cea981805a88f","addressRefs":[]},"0c3a819b-f93f-4565-948f-7d9147cfe9d8":{"id":"0c3a819b-f93f-4565-948f-7d9147cfe9d8","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.4.2.2","title":"Call claimRedeemERC7540 Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9481,"content":"Only an operator with the relayer role can claim assets from an ERC-7540 vault after a redemption request. To do so, they must call the `claimRedeemERC7540` function on the Controller contract on mainnet, providing the vault token address. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will determine the maximum amount of assets that can be claimed by the ALM Proxy.\n- The contract will claim the assets from the vault, and the ALM Proxy will receive the corresponding amount of underlying assets.\n\nThe function call is as follows:\n\n`function claimRedeemERC7540(address token) external`","contentHash":"5e009dff8fc6a052984c70afd928dea021c7163bba2ae9249ad9d17a3b1a0b34","addressRefs":[]},"918d2721-5fea-4b89-a134-56de5146aa5c":{"id":"918d2721-5fea-4b89-a134-56de5146aa5c","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.5","title":"Dai / USDS Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9482,"content":"The documents herein define the swap operations between Dai and USDS.","contentHash":"f36ef24d14bc80de5bc10143703d7ecf159839ce3772551c0fa1e39d475d5a72","addressRefs":[]},"3107138f-1944-40da-9e60-7b9fed97b984":{"id":"3107138f-1944-40da-9e60-7b9fed97b984","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.5.1","title":"Swap USDS to Dai","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9483,"content":"The documents herein define a series of operations for an operator to `swap` USDS to Dai.","contentHash":"fb2a18a3c900f2b88037f665dc833575360840e94dd7a655e1c5cd7b4c9e186e","addressRefs":[]},"b28a88b4-bb7f-4f7b-a538-cb394ce6ce23":{"id":"b28a88b4-bb7f-4f7b-a538-cb394ce6ce23","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.5.1.1","title":"Call swapUSDSToDAI Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9484,"content":"Only an operator with the relayer role can swap USDS to Dai. To do so, they must call the `swapUSDSToDAI` function on the Controller contract on mainnet, providing the usdsAmount. The operation will only succeed if the Proxy holds enough USDS for the swap; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will approve the DaiUsds migrator to spend the specified USDS amount from the Proxy.\n- The contract will swap USDS to Dai at a 1:1 ratio by calling the `usdsToDai` function on the migrator, sending the resulting DAI to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDSToDAI(uint256 usdsAmount) external`","contentHash":"58fd4d26eca7cc4ff164cfd9ac0f85e0bb19968d20c147bbf84e68018627682a","addressRefs":[]},"76a9ada0-0697-4201-8b3b-621063b3554b":{"id":"76a9ada0-0697-4201-8b3b-621063b3554b","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.5.2","title":"Swap Dai to USDS","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9485,"content":"The documents herein define a series of operations for an operator to `swap` Dai to USDS.","contentHash":"72782112e31cf3bf9ac4c1820cf0b6beee560bd08bc8e2011301e59217763bb5","addressRefs":[]},"06ba856a-91a7-43b5-b4d7-9f392df360d4":{"id":"06ba856a-91a7-43b5-b4d7-9f392df360d4","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.5.2.1","title":"Call swapDAIToUSDS Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9486,"content":"Only an operator with the relayer role can swap Dai to USDS. To do so, they must call the `swapDAIToUSDS` function on the Controller contract on mainnet, providing the daiAmount. The operation will only succeed if the Proxy holds enough Dai for the swap; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will approve the DaiUsds migrator to spend the specified Dai amount from the Proxy.\n- The contract will swap Dai to USDS at a 1:1 ratio by calling the `daiToUsds` function on the migrator, sending the resulting USDS to the proxy.\n\nThe function call is as follows:\n\n`function swapDAIToUSDS(uint256 daiAmount) external`","contentHash":"221a10f1dacee5cda6eb6b272622a64a781fe5f341cd0ad5d1d549ef8208fc38","addressRefs":[]},"4ee9a639-8b91-4bd9-8993-9efe3117524a":{"id":"4ee9a639-8b91-4bd9-8993-9efe3117524a","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.6","title":"PSM Functions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9487,"content":"The documents herein define the swap operations performed by the Pattern Liquidity Layer in the PSM.","contentHash":"a2ddce8cf98739aaf564807d191b596865460b4848e0bb4bb9480c22d1042522","addressRefs":[]},"ef9a88a1-cf2b-47a9-9664-685880558489":{"id":"ef9a88a1-cf2b-47a9-9664-685880558489","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.6.1","title":"Swap USDS to USDC","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9488,"content":"The documents herein define a series of operations for an operator to `swap` USDS to USDC through the PSM.","contentHash":"564fc251dbabe1de4723b87aa7179a9f9f901ef1b48e8c75549e98fefb798c1b","addressRefs":[]},"b08f57de-599d-46e4-aabe-64b1db5a38ad":{"id":"b08f57de-599d-46e4-aabe-64b1db5a38ad","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.6.1.1","title":"Call swapUSDSToUSDC Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9489,"content":"Only an operator with the relayer role can swap USDS to USDC via the PSM. To do so, they must call the `swapUSDSToUSDC` function on the Controller contract on mainnet, providing the usdcAmount (denominated in 1e6 precision to match PSM USDC handling). The operation will only succeed if the ALM Proxy holds at least the equivalent amount of USDS for the swap; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for swaps. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the swap amount is within the allowed rate limit (LIMIT_USDS_TO_USDC) for the PSM.\n- The contract will convert the USDC amount to an 18-decimal format using psmTo18ConversionFactor.\n- The contract will approve the daiUsds contract to spend the converted amount from the ALM Proxy.\n- The contract will swap USDS to Dai at a 1:1 ratio via daiUsds, sending Dai to the proxy.\n- The contract will approve the PSM to spend the Dai.\n- The contract will swap Dai to USDC at a 1:1 ratio with no fee via psm.buyGemNoFee, sending USDC to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDSToUSDC(uint256 usdcAmount) external`","contentHash":"cc3728b1904efa771e6576a8833a6096a44aa7d0b21a635e7cf570db93ff37ff","addressRefs":[]},"9d828ddb-7423-41cb-9adb-43d4cbfc9d38":{"id":"9d828ddb-7423-41cb-9adb-43d4cbfc9d38","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.6.2","title":"Swap USDC To USDS","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9490,"content":"The documents herein define a series of operations for an operator to `swap` USDC to USDS through the PSM.","contentHash":"f55bbceca04d743a7ae5c9c46fa9d3d34fd14dab41a5f282da781a788be9ba83","addressRefs":[]},"355f4606-5346-41d5-8ea7-2c4490d761e1":{"id":"355f4606-5346-41d5-8ea7-2c4490d761e1","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.6.2.1","title":"Call swapUSDCToUSDS Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9491,"content":"Only an operator with the relayer role can swap USDC to USDS via the PSM. To do so, they must call the `swapUSDCToUSDS` function on the Controller contract on mainnet, providing the usdcAmount (denominated in 1e6 precision to match PSM USDC handling). The operation will only succeed if the ALM Proxy holds at least the amount of USDC specified for the swap; otherwise, the transaction will revert. The rate limit configuration serves as whitelisting for swaps. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the swap amount is within the allowed rate limit (LIMIT_USDC_TO_USDS) for the PSM.\n- The contract will approve the PSM to spend the USDC from the ALM Proxy.\n- The contract will calculate the swap limit per transaction based on the Dai balance held by the PSM, converting with psmTo18ConversionFactor.\n- If the usdcAmount is less than or equal to the limit, the contract will perform a direct swap of USDC to Dai.\n- If the usdcAmount exceeds the limit, the contract will split the swap into multiple smaller swaps: refill the PSM with Dai via psm.fill, recalculate the limit, swap the maximum allowed amount, update the remaining amount, and repeat until complete (reverting with \"DssLitePsm/nothing-to-fill\" if PSM cannot be filled).\n- The contract will convert the USDC amount to a Dai amount, accounting for token decimal differences.\n- The contract will approve the daiUsds contract to spend the Dai amount from the ALM Proxy.\n- The contract will swap Dai to USDS at a 1:1 ratio via daiUsds, sending USDS to the proxy.\n\nThe function call is as follows:\n\n`function swapUSDCToUSDS(uint256 usdcAmount) external`","contentHash":"373dca92f7fe2552f8fbbda1918df1e55c1556dfb36f61eb8b30f06df23aa0bc","addressRefs":[]},"901bf629-cee3-4296-afd6-d1e7779d15bb":{"id":"901bf629-cee3-4296-afd6-d1e7779d15bb","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.6.3","title":"Transfer Token Via LayerZero","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9492,"content":"The documents herein define the steps for a relayer to `transfer` a token via LayerZero to a destination endpoint, with the assets sent according to the configured recipient.","contentHash":"209ac1740bb885c01bcf8b9c84111d5989e7232964c2eb7017bd745b6976136c","addressRefs":[]},"24c70856-ba73-4b1e-86db-1d7829220c49":{"id":"24c70856-ba73-4b1e-86db-1d7829220c49","doc_no":"A.6.1.1.6.2.6.1.2.2.1.2.1.2.6.3.1","title":"Call transferTokenLayerZero Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9493,"content":"Only an operator with the relayer role can transfer tokens via LayerZero. To do so, they must call the `transferTokenLayerZero` function on the Controller contract on mainnet, providing the oftAddress, amount, and destinationEndpointId (payable for native fees). The operation will only succeed if the ALM Proxy holds sufficient tokens and fees; otherwise, the transaction will revert. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the transfer amount is within the allowed rate limit (built from LIMIT_LAYERZERO_TRANSFER, oftAddress, and destinationEndpointId).\n- If approval is required, the contract will approve the token for the oftAddress.\n- The contract will build LayerZero send options and a SendParam struct with destination details, amount, and recipient from layerZeroRecipients.\n- The contract will quote the OFT receipt to set the minimum amount received.\n- The contract will quote the messaging fee and execute the send via proxy.doCallWithValue, passing the fee value.\n\nThe function call is as follows:\n\n`function transferTokenLayerZero(address oftAddress, uint256 amount, uint32  destinationEndpointId) external payable`","contentHash":"a35fb0891772ab21f004a3c2d9997a1f57c3fe654845878902d240d60bc33274","addressRefs":[]},"2b03d21b-d03a-4c0e-8d90-d5a2f5dd9140":{"id":"2b03d21b-d03a-4c0e-8d90-d5a2f5dd9140","doc_no":"A.6.1.1.6.2.6.1.2.2.1.3","title":"Rate Limit Management","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9494,"content":"The documents herein define the protocol for querying, setting, and adjusting `RateLimits` for Instances using their `RateLimitID`s. The Rate Limits must be maintained in line with Pattern's strategy, market conditions, and security considerations.","contentHash":"e368176f63ccf1d13f0f8257e265be59e4f34e5637a279ad0e21939461cd6f27","addressRefs":[]},"f46cbe06-e7df-4a92-8972-cd21bf9be2c5":{"id":"f46cbe06-e7df-4a92-8972-cd21bf9be2c5","doc_no":"A.6.1.1.6.2.6.1.2.2.1.3.1","title":"Get Rate Limit Data","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9495,"content":"Anyone can query the full rate limit data for a specific key. Calling this function will carry out the following actions:\n\n- The contract will return the stored RateLimitData struct from the _data mapping for the key.\n\nThe function call is as follows:\n\n`function getRateLimitData(bytes32 key) external override view returns (RateLimitData memory)`","contentHash":"61aaead98caab9ae4da7ca412908ffa156e91b1a5fe8e1feca9babb5c82ac1fc","addressRefs":[]},"89b060bd-1026-46ec-ab32-d032edb58f83":{"id":"89b060bd-1026-46ec-ab32-d032edb58f83","doc_no":"A.6.1.1.6.2.6.1.2.2.1.3.2","title":"Set Rate Limit Data","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9496,"content":"Only an operator with the admin role is able to set or update rate limit data for a specific key, including maxAmount, slope, and historical values. There are two overloads for flexibility. Calling these functions will carry out the following actions:\n\n- The contract will require that lastAmount is less than or equal to maxAmount, reverting with \"RateLimits/invalid-lastAmount\" if not.\n- The contract will require that lastUpdated is less than or equal to the current block timestamp, reverting with \"RateLimits/invalid-lastUpdated\" if not.\n- The contract will store the provided data in the _data mapping as a RateLimitData struct.\n- The contract will emit a RateLimitDataSet event with the key and provided values.\n\nThe function calls are as follows:\n\n```\nfunction setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope, uint256 lastAmount, uint256 lastUpdated) public override onlyRole(DEFAULT_ADMIN_ROLE)\n\nfunction setRateLimitData(bytes32 key, uint256 maxAmount, uint256 slope) external override\n```","contentHash":"a9463875659a3ac6b66961118d94871545e79f20dea7a3671d7274e826248aa1","addressRefs":[]},"7c4bdc16-13e0-47b4-8988-18e9720eb292":{"id":"7c4bdc16-13e0-47b4-8988-18e9720eb292","doc_no":"A.6.1.1.6.2.6.1.2.2.1.3.3","title":"Set Unlimited Rate Limit Data","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9497,"content":"Only an operator with the admin role is able to set unlimited rate limit data for a specific key by configuring it with maximum values. Calling this function will carry out the following actions:\n\n- The contract will call setRateLimitData internally with type(uint256).max for maxAmount and lastAmount, 0 for slope, and the current block timestamp for lastUpdated.\n\nThe function call is as follows:\n\n`function setUnlimitedRateLimitData(bytes32 key) external override`","contentHash":"8d3f02b7a0c3f317c28a031cc58bcd6f8f28989b8f8fe5ce7d7e718bdfc42047","addressRefs":[]},"b0afea3f-9ff2-4462-a771-522b1256a343":{"id":"b0afea3f-9ff2-4462-a771-522b1256a343","doc_no":"A.6.1.1.6.2.6.1.2.2.1.3.4","title":"Get Current Rate Limit","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9498,"content":"Anyone can query the current rate limit value for a specific key, accounting for time-based slope accrual. Calling this function will carry out the following actions:\n\n- The contract will retrieve the RateLimitData for the key from the _data mapping.\n- If maxAmount is type(uint256).max (unlimited case), the contract will return type(uint256).max.\n- Otherwise, the contract will calculate and return the minimum of (slope * time elapsed since lastUpdated + lastAmount) and maxAmount.\n\nThe function call is as follows:\n\n`function getCurrentRateLimit(bytes32 key) public override view returns (uint256)`","contentHash":"4a41715aa485c085b94bc4050e85eaabdb529ba656d1185b8b57aa766ff36ad6","addressRefs":[]},"9f76a9bc-5451-4ff7-8dcd-153e4c47fe72":{"id":"9f76a9bc-5451-4ff7-8dcd-153e4c47fe72","doc_no":"A.6.1.1.6.2.6.1.2.2.1.3.5","title":"Trigger Rate Limit Decrease","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9499,"content":"Only an operator with the controller role can trigger a decrease in the rate limit for a specific key by a given amount. Calling this function will carry out the following actions:\n\n- The contract will retrieve the RateLimitData storage for the key from the data mapping.\n- The contract will require that maxAmount is greater than 0, reverting with \"RateLimits/zero-maxAmount\" if not.\n- If maxAmount is type(uint256).max (unlimited case), the contract will return type(uint256).max without changes.\n- The contract will calculate the currentRateLimit using getCurrentRateLimit.\n- The contract will require that amountToDecrease is less than or equal to currentRateLimit, reverting with \"RateLimits/rate-limit-exceeded\" if not.\n- The contract will update lastAmount to currentRateLimit minus amountToDecrease and set lastUpdated to the current block timestamp.\n- The contract will emit a RateLimitDecreaseTriggered event with the key, amountToDecrease, currentRateLimit, and newLimit.\n- The contract will return the newLimit.\n\nThe function call is as follows:\n\n`function triggerRateLimitDecrease(bytes32 key, uint256 amountToDecrease) external override onlyRole(CONTROLLER) returns (uint256 newLimit)`","contentHash":"90daece828f45dc63307a3e767f044524efeed8f45db7653932d890c4416f626","addressRefs":[]},"568f470e-adce-49ee-8cbe-756757814dc5":{"id":"568f470e-adce-49ee-8cbe-756757814dc5","doc_no":"A.6.1.1.6.2.6.1.2.2.1.4","title":"Instance Lifecycle Management","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9500,"content":"The documents herein define processes for invoking (onboarding) new Pattern Liquidity Layer Instances and offboarding existing ones. This process will be specified in a future iteration of the Pattern Artifact.","contentHash":"9464b6e6fb5165702408b491bf785bb13ee898ef5d34a4cf8b2d7e02f4ef049a","addressRefs":[]},"2858c1d6-bc8d-4896-a5d7-8647a1010e46":{"id":"2858c1d6-bc8d-4896-a5d7-8647a1010e46","doc_no":"A.6.1.1.6.2.6.1.2.2.1.5","title":"Upgrading Controller","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9501,"content":"The documents herein define the process for deploying new Controller contracts. This process will be specified in a future iteration of the Pattern Artifact.","contentHash":"fd1f684857fc519710dbdc554fb4441012d6b7f2435b45dd705a2a0e2f14518b","addressRefs":[]},"ae7cab85-07da-4c66-ab60-f7837dd268fd":{"id":"ae7cab85-07da-4c66-ab60-f7837dd268fd","doc_no":"A.6.1.1.6.2.6.1.2.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9502,"content":"The documents herein define the process for non-routine ongoing management of the Pattern Liquidity Layer and its active Instances.","contentHash":"ae2054f3eb9dfe04e3e48f7b4c00fdded779f371cfcd3d24563c86e0d09fb184","addressRefs":[]},"9eb7f00e-dfdb-48da-92cd-ac6793496290":{"id":"9eb7f00e-dfdb-48da-92cd-ac6793496290","doc_no":"A.6.1.1.6.2.6.1.2.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9503,"content":"The documents herein define all the possible actions that can be taken in case of an emergency within Pattern Liquidity Layer operations.","contentHash":"cc7789c0d41588f8884355aa95bfc58f39e6a46f0b48dca46990d0b78db83b0e","addressRefs":[]},"a7054e75-b492-4e49-bae6-41c786153fb2":{"id":"a7054e75-b492-4e49-bae6-41c786153fb2","doc_no":"A.6.1.1.6.2.6.1.2.2.3.1","title":"Remove Compromised Relayer As Freezer","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9504,"content":"In the event of a compromised Relayer, the `FREEZER_ROLE` can call the function to `removeRelayer` from the Controller contract. Only an operator with the freezer role can remove a relayer. To do so, they must call the `removeRelayer` function on the Controller contract on mainnet, providing the compromised relayer's address. Calling this function will carry out the following actions:\n\n- The contract will confirm the caller holds the freezer role. If the caller does not have the freezer role, the transaction will revert.\n- The contract will revoke the relayer role from the specified address.\n- The contract will emit a `RelayerRemoved(relayer)` event.\n\nThe function call is as follows:\n\n`function removeRelayer(address relayer) external`","contentHash":"267a4fe6db302e420652371cb15d001193346f2f8a1b683b6857827d8275230e","addressRefs":[]},"d1885385-a7d8-4d1c-b345-a843a5001052":{"id":"d1885385-a7d8-4d1c-b345-a843a5001052","doc_no":"A.6.1.1.6.2.6.1.2.2.3.2","title":"Redeem All Mainnet Positions","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9505,"content":"The documents herein define the actions that should be performed by an operator if there is a need to recover the liquidity from Mainnet Protocols and centralize it in the Mainnet Pattern ALM Proxy.","contentHash":"9fe2418c73621817c39ce7e2291ac1fe76369df2011bbe5f4e8ff088ee2f4583","addressRefs":[]},"872a4857-504e-4795-9cbd-2a6f159c1ea0":{"id":"872a4857-504e-4795-9cbd-2a6f159c1ea0","doc_no":"A.6.1.1.6.2.6.1.2.2.3.2.1","title":"ERC-4626 Withdrawal Action","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9506,"content":"In order to withdraw all ERC-4626 balances, the operator must call the `redeemERC4626` function.\n\nThe function call is as follows:\n\n`function redeemERC4626(address(token), token.balanceOf(address(proxy)))`\n\nFor more detailed instructions on the code to execute this, see [A.6.1.1.6.2.6.1.2.2.1.2.1.2.3 - ERC-4626 Functions](c6dcf1ab-9861-4a41-9edc-ea79b705db2d).","contentHash":"3562c7f52c5a5840964c8d64baced8742b0fa92b2c7dfa16014a0dd05db1145a","addressRefs":[]},"c30c1496-0eff-4199-9c18-eb72fb486aac":{"id":"c30c1496-0eff-4199-9c18-eb72fb486aac","doc_no":"A.6.1.1.6.2.6.1.2.2.3.3","title":"USDC To USDS Swap Action","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9507,"content":"This document defines the action that should be performed by an operator if there is a need to centralize all recovered liquidity in USDS. The operator must call the `swapUSDCToUSDS` function.\n\nThe function call is as follows:\n\n`function swapUSDCToUSDS(usdc.balanceOf(address(proxy))`\n\nFor more detailed instructions on the code to execute this see [A.6.1.1.6.2.6.1.2.2.1.2.1.2.6.2 - Swap USDC To USDS](9d828ddb-7423-41cb-9adb-43d4cbfc9d38).","contentHash":"3557402105f14658c6db07e3e788155d28e4ea344e5b5f7b6a839c6733d3a364","addressRefs":[]},"451ccaa5-640c-423d-b816-de953edbf115":{"id":"451ccaa5-640c-423d-b816-de953edbf115","doc_no":"A.6.1.1.6.2.6.1.2.2.3.4","title":"USDS Burn Action","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9508,"content":"This document defines the action that should be performed if there is a need to repay and then burn Pattern's USDS debt. The operator must call the `burnUSDS` function.\n\nThe function call is as follows:\n\n`function burnUSDS(usds.balanceOf(address(proxy))`\n\nMore detailed instructions on the code to execute this, see [A.6.1.1.6.2.6.1.2.2.1.2.1.2.1.2 - Burn USDS](886d04ba-23c3-45fb-ac5d-044288a621e1).","contentHash":"cff7c302d6295ead72f97a46559f9ee85ed8ca9ade8e5637259f981f5ef6b361","addressRefs":[]},"e4bc88c1-a8b6-428a-aafd-2b03e7cb85ae":{"id":"e4bc88c1-a8b6-428a-aafd-2b03e7cb85ae","doc_no":"A.6.1.1.6.2.6.1.2.3","title":"Allocation Strategy","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9509,"content":"In the future, additional logic will be added herein regarding the strategy by which capital is allocated between different Instances of the Pattern Liquidity Layer.","contentHash":"bb6128306f36e3a610d0493cdf5d2a9dc75fcf4463ab38eb15498e9056f972e3","addressRefs":[]},"5050f24e-45b1-4032-adf7-319235cdb6b9":{"id":"5050f24e-45b1-4032-adf7-319235cdb6b9","doc_no":"A.6.1.1.6.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9510,"content":"The Instances of the Pattern Liquidity Layer with `Active` Status are stored herein. The `RRC Framework Full Implementation Coverage` status defines whether the Instance Financial RRC is calculated based on a fully implemented risk model (see [A.3.2.1.1.4.3.1 - Fully Implemented Risk Models](419a1d00-fbae-4d26-bd47-8f57677d8001)) or a pending risk model (see [A.3.2.1.1.4.3.2 - Pending Risk Models](81ca88bf-3f6a-4d10-a3e2-d47cf6636d7d)). If the Instance Financial RRC is calculated based on a fully implemented risk model the status is `Covered`. If the Instance Financial RRC is calculated based on a pending risk model the status is `Pending`.","contentHash":"1eac1896b2d7ab45b028a3dd03f32d2659da54ea68c6401de32c9914c2fa7afa","addressRefs":[]},"5eb721ed-289b-42f8-bed4-1e62debcc31c":{"id":"5eb721ed-289b-42f8-bed4-1e62debcc31c","doc_no":"A.6.1.1.6.2.6.1.3.1","title":"Ethereum Mainnet Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9511,"content":"The Ethereum Mainnet Instances of the Pattern Liquidity Layer with `Active` Status are stored herein and are organized by target protocol.","contentHash":"ea0f3e9abc8dbde3642046836dc80b5b9246b7e14cae01020aea1033872a6d86","addressRefs":[]},"ffd9916b-8088-47bb-854f-2fd3f31b67eb":{"id":"ffd9916b-8088-47bb-854f-2fd3f31b67eb","doc_no":"A.6.1.1.6.2.6.1.3.1.1","title":"Maple","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9512,"content":"The Ethereum Mainnet Instances of the Maple Protocol with `Active` Status are stored herein.","contentHash":"8fc7c8ba100ab5d1abcce02e163a69acc6af84061a97d576f93c43fc63481e53","addressRefs":[]},"50d86fb7-cacd-4f9b-adf4-7056cfe8cd97":{"id":"50d86fb7-cacd-4f9b-adf4-7056cfe8cd97","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1","title":"Ethereum Mainnet - Maple USDC Instance Configuration Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9513,"content":"The documents herein contain the Instance Configuration Document for the Maple USDC Instance.","contentHash":"1f0b8dcfe605b4906709f0bad210660334f119702f681e347f3f6e7d7567a5ed","addressRefs":[]},"1b922f8d-dc0e-4788-bb42-a01319b3e272":{"id":"1b922f8d-dc0e-4788-bb42-a01319b3e272","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.1","title":"RRC Framework Full Implementation Coverage","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9514,"content":"**`Covered`**","contentHash":"44413f87a5dc2bb17083b98a95fa85377414f57aa2f10a9d8998e680a9b42c2d","addressRefs":[]},"91e09aad-6287-44a1-a113-07adb46045d8":{"id":"91e09aad-6287-44a1-a113-07adb46045d8","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2","title":"Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9515,"content":"The documents herein define the parameters of the Maple USDC Instance of the Allocation System Primitive.","contentHash":"bc52815c6a6edbb05f61c0586baf40df733aaa345107b7fcd1ac535777faefd7","addressRefs":[]},"3bb453cb-4ae2-466f-9008-b50079d27767":{"id":"3bb453cb-4ae2-466f-9008-b50079d27767","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9516,"content":"The documents herein define the Instance identifiers","contentHash":"cf4786e81b8efd306139d361868f52281b69c9d635810d8459b598ad580de105","addressRefs":[]},"b20300e4-a1e9-4461-a62f-7d28dd3ba411":{"id":"b20300e4-a1e9-4461-a62f-7d28dd3ba411","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.1.1","title":"Network","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9517,"content":"Ethereum Mainnet","contentHash":"5eb7a442abd7e24a288e7199e98325cd5df5eb62125a8b9a6fa4e48826f8bf90","addressRefs":[]},"68c3772f-bb79-4518-94b4-f62a5f9976cd":{"id":"68c3772f-bb79-4518-94b4-f62a5f9976cd","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.1.2","title":"Target Protocol","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9518,"content":"Maple","contentHash":"187c93774dbd4c674ecaf745f0c304bb494ccfca31cd88c028251f97f09569c5","addressRefs":[]},"3374585c-f518-4f40-ae7e-ef6adf934d30":{"id":"3374585c-f518-4f40-ae7e-ef6adf934d30","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.1.3","title":"Asset Supplied By Pattern Liquidity Layer","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9519,"content":"USDC","contentHash":"22c7a95ef940d32490e7fd7ec68281ccaaf563f1f7cebc3bc2196fece98b12ac","addressRefs":[]},"91b6aca1-10f0-4353-b392-33c28777ced3":{"id":"91b6aca1-10f0-4353-b392-33c28777ced3","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.1.4","title":"Token","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9520,"content":"syrupUSDC","contentHash":"3b50b2203f4915b0b7b3098fc5d9205e27421a900c9bf60f5fe7d484e2a25003","addressRefs":[]},"29098a46-4273-4375-8ae1-4c2f869c12bc":{"id":"29098a46-4273-4375-8ae1-4c2f869c12bc","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.2","title":"Contract Addresses","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9521,"content":"The documents herein define the Instance contract addresses.","contentHash":"864bdafb9b200906d6d0e99c6f057f95cc25a3f56f5f169fdd59b8ed0a7f437f","addressRefs":[]},"f62da26d-7c08-4c6c-8ed2-732bd756fa18":{"id":"f62da26d-7c08-4c6c-8ed2-732bd756fa18","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.2.1","title":"Token Address","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9522,"content":"`0x80ac24aA929eaF5013f6436cdA2a7ba190f5Cc0b`","contentHash":"c9da76a92fdbedaeaebc89f6ae1550989ebcbf6b96f68777626b48b5da9dfbce","addressRefs":["0x80ac24aa929eaf5013f6436cda2a7ba190f5cc0b"]},"2b47ae9c-85f4-41ac-97f9-63737a95aab3":{"id":"2b47ae9c-85f4-41ac-97f9-63737a95aab3","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.2.2","title":"Underlying Asset Address","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9523,"content":"`0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48`","contentHash":"23916335f3e6f27eb2b746178ef1392c7de72b9bbf5948e3ffe59448c4d8fc56","addressRefs":["0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"]},"b909a2b6-4fea-42f1-a883-6c4be70abd3c":{"id":"b909a2b6-4fea-42f1-a883-6c4be70abd3c","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.3","title":"RateLimitIDs","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9524,"content":"The specific `RateLimitID`(s) for this conduit's inflow and outflow are specified in the documents herein.","contentHash":"dcb85223cd5bc656424dab0b36280843954d9fc0970480de5ad614ad75dd2f8e","addressRefs":[]},"36faf4e4-dbef-488e-b1f3-a145c2058289":{"id":"36faf4e4-dbef-488e-b1f3-a145c2058289","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.3.1","title":"Inflow RateLimitID","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9525,"content":"The inflow RateLimitID is: `0x99a69e57b2f387f999d6adff6eb2e707b59fdb54f06ca6211b4f20956e9bfe10`","contentHash":"1fcebf3d37fbcb31666be37de75a10dc1905b221595feddede05658d789c9047","addressRefs":[]},"8b64e6db-f656-47cc-939d-34d92e10048e":{"id":"8b64e6db-f656-47cc-939d-34d92e10048e","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.3.2","title":"Outflow RateLimitID","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9526,"content":"The outflow RateLimitID is: `0x64e6fd9d694640eebeeefc7b5abe32ef09bbabaa3d4e60221461d05a9577dc57`","contentHash":"4871287b6111e508f3c17951524f850991555573c78bf6dd8176dbbd81015769","addressRefs":[]},"93912f1a-3f33-4584-9d4c-dd0a57571c4e":{"id":"93912f1a-3f33-4584-9d4c-dd0a57571c4e","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.4","title":"Rate Limits","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9527,"content":"The current `maxAmount` and `slope` for this conduit's inflow/outflow are defined in the documents herein.","contentHash":"b3d533df61cd69c85387e29090a8ce81f097ff1e8f0631318826757dc8c011e9","addressRefs":[]},"baf5e2d2-8d4f-4248-90ff-c3bb21972b62":{"id":"baf5e2d2-8d4f-4248-90ff-c3bb21972b62","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.4.1","title":"Inflow Rate Limits","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9528,"content":"The deposit rate limits are:\n\n- `maxAmount`: 100,000,000 USDC\n- `slope`: 20,000,000 USDC per day","contentHash":"bc10c92bd20563afabf4f1812c0d9078b5b3ae1f853a816d199d2e0e9b359d71","addressRefs":[]},"49a40f8d-e564-4cb3-bd6d-44d51bcba9c2":{"id":"49a40f8d-e564-4cb3-bd6d-44d51bcba9c2","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.4.2","title":"Withdrawal Rate Limits","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9529,"content":"The withdrawal rate limits are:\n\n- `maxAmount`: Unlimited","contentHash":"4f9a4eb0b0bbaf2c431d7ed35ccf335d5276bd576e9ef7fc568e9a2cf6f77628","addressRefs":[]},"eb78d31a-7540-4851-815a-8d1200050dee":{"id":"eb78d31a-7540-4851-815a-8d1200050dee","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.2.5","title":"Off-chain Operational Parameters","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9530,"content":"The documents herein contain specific off-chain parameters for this Instance.","contentHash":"2a68e14c13bf61a702c1959b8a27c6ed4115ee27d6b7cff9f437a749bac5d9d7","addressRefs":[]},"d19f3ee9-95d8-42fc-971d-1fe20aeea6ba":{"id":"d19f3ee9-95d8-42fc-971d-1fe20aeea6ba","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.3","title":"Instance-specific Operational Processes","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9531,"content":"The documents herein contain operational procedures or monitoring requirements unique to this Instance that deviate from or otherwise supplement the general Pattern Liquidity Layer processes.","contentHash":"8bcaf2ec8fecd2e51219f64bb108defa0fc7a1085d46e8ef141245fd377ae7d1","addressRefs":[]},"e1bc16e0-7239-49fe-bc15-c51867bb1b5a":{"id":"e1bc16e0-7239-49fe-bc15-c51867bb1b5a","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.3.1","title":"Redeem Maple Shares","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9532,"content":"The documents herein define the steps for a relayer to redeem vault shares from Maple.","contentHash":"33f07984a7023381083285874a35539725587f30cbc80fc5ee5304df3bb57949","addressRefs":[]},"d080330d-912e-4c6d-9c81-714ce4b544a1":{"id":"d080330d-912e-4c6d-9c81-714ce4b544a1","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.3.1.1","title":"Call RequestMapleRedemption Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9533,"content":"Only an operator with the relayer role can request the redemption of shares from Maple. To do so, they must call the `requestMapleRedemption` function on the Controller contract on mainnet, providing the Maple token address and the number of shares to request. All Maple redemption operations are performed on behalf of the ALM Proxy and the destination address is always set to the proxy by the contract. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will ensure the redemption amount is within the allowed rate limit for the specified vault and decrease the rate limit for the redemption amount.\n- The contract will submit a redemption request to the vault. Assets will not be received immediately; they must be claimed in a separate step after the vault processes the redemption.\n\nThe function call is as follows:\n\n`function requestMapleRedemption(address mapleToken, uint256 shares) external`","contentHash":"2ef622847b78f9352bbf084a0e712d677237271d1e5c603dfd0bdeca1697eae1","addressRefs":[]},"85d7a1f5-3361-49cf-b087-b027183cb640":{"id":"85d7a1f5-3361-49cf-b087-b027183cb640","doc_no":"A.6.1.1.6.2.6.1.3.1.1.1.3.1.2","title":"Call CancelMapleRedemption Function","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9534,"content":"Only an operator with the relayer role can cancel a previously requested redemption of shares from Maple. To do so, they must call the `cancelMapleRedemption` function on the Controller contract on mainnet, providing the Maple token address and the number of shares to cancel. All Maple cancellations of redemption operations are performed on behalf of the ALM Proxy. Calling this function will carry out the following actions:\n\n- The contract will confirm the relayer status of the operator. If the caller does not have the relayer role, the transaction will revert.\n- The contract will check that a rate limit exists for the asset. If no rate limit exists the transaction will revert.\n- The contract will submit a cancellation request to the vault, removing the specified number of shares from the pending redemption.\n\nThe function call is as follows:\n\n`function cancelMapleRedemption(address mapleToken, uint256 shares) external`","contentHash":"b78ad2e77a36fcde5dd0e9ec8080438f123f68e3fd8211161871a918703db8e7","addressRefs":[]},"f7a6d433-9be9-4140-89b4-eacf579522e4":{"id":"f7a6d433-9be9-4140-89b4-eacf579522e4","doc_no":"A.6.1.1.6.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9535,"content":"The Instances of the Allocation System Primitive with `Completed` Status are stored herein.","contentHash":"5e8b303421b8ddbbe094a65ed1a012a162ef23442d0be75ad055b30f78fb3af7","addressRefs":[]},"1899ca65-7192-4881-b75d-21712af70e3c":{"id":"1899ca65-7192-4881-b75d-21712af70e3c","doc_no":"A.6.1.1.6.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9536,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.6.1.3 - Active Instances](5050f24e-45b1-4032-adf7-319235cdb6b9).","contentHash":"8a1bf53bc5ea96d80505d8ba230283c995fa9776a1c2f0ea7d38e0187500c65b","addressRefs":[]},"5345e5c5-d791-48ab-835c-413af9665327":{"id":"5345e5c5-d791-48ab-835c-413af9665327","doc_no":"A.6.1.1.6.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9537,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"60ed0ab418a08dba542d42d8f2f677b3eed0756c06c32e8a0dad95958c383cd5","addressRefs":[]},"f4572c7d-15e0-44e6-842e-80b93f4a3357":{"id":"f4572c7d-15e0-44e6-842e-80b93f4a3357","doc_no":"A.6.1.1.6.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9538,"content":"The documents herein organize all base information relevant to Pattern's usage of the Junior Risk Capital Rental Primitive.","contentHash":"8ae45f3a4eacd15947c4460a24d9e34a2b92e74c442eb0558732bdf03f564f23","addressRefs":[]},"a865a886-0961-46d5-9ba9-079c49971538":{"id":"a865a886-0961-46d5-9ba9-079c49971538","doc_no":"A.6.1.1.6.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9539,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"edf76ec6-4b5b-4d06-be3a-21a97096754a":{"id":"edf76ec6-4b5b-4d06-be3a-21a97096754a","doc_no":"A.6.1.1.6.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9540,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"b73aa2a6-aa69-4bf1-91aa-cad8c95f1cce":{"id":"b73aa2a6-aa69-4bf1-91aa-cad8c95f1cce","doc_no":"A.6.1.1.6.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9541,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"b6ff1423-0299-4688-bfa4-f900fd940698":{"id":"b6ff1423-0299-4688-bfa4-f900fd940698","doc_no":"A.6.1.1.6.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9542,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.6.2.1.2 - Active Instances Directory](edf76ec6-4b5b-4d06-be3a-21a97096754a), whereas failed Invocations are Archived in [A.6.1.1.6.2.6.2.1.5 - Hub Data Repository](ea2a247c-3564-4bdb-a1a7-2a2559e51f03).","contentHash":"d63e1da6eb3fc0922e69797cf3f58b5562c0b78847be3a03afd63cbbea3a844a","addressRefs":[]},"ea2a247c-3564-4bdb-a1a7-2a2559e51f03":{"id":"ea2a247c-3564-4bdb-a1a7-2a2559e51f03","doc_no":"A.6.1.1.6.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9543,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"c47c1559-736e-43af-b8d3-55d0a7b60e8c":{"id":"c47c1559-736e-43af-b8d3-55d0a7b60e8c","doc_no":"A.6.1.1.6.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9544,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"9edcdbb1-02ab-48aa-bd6d-b363bb34559a":{"id":"9edcdbb1-02ab-48aa-bd6d-b363bb34559a","doc_no":"A.6.1.1.6.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9545,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"8f7140b0-0f4c-46a7-9ce0-4dac030e12f6":{"id":"8f7140b0-0f4c-46a7-9ce0-4dac030e12f6","doc_no":"A.6.1.1.6.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9546,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"8bc496da-9dbc-49ea-9539-bc0c68eae4e1":{"id":"8bc496da-9dbc-49ea-9539-bc0c68eae4e1","doc_no":"A.6.1.1.6.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9547,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"39aefad1-cd44-4526-86ed-3f2e1b76d658":{"id":"39aefad1-cd44-4526-86ed-3f2e1b76d658","doc_no":"A.6.1.1.6.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9548,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"f443ef76-7111-479f-ba69-1f0d5e1342fe":{"id":"f443ef76-7111-479f-ba69-1f0d5e1342fe","doc_no":"A.6.1.1.6.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9549,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.6.2.2 - Active Instances](8bc496da-9dbc-49ea-9539-bc0c68eae4e1).","contentHash":"a85c8bd9565215f22d97bbb3b8f768ab1b185f9bd93f3e7e8b939ac552af8bfb","addressRefs":[]},"6e435727-a8e1-492e-a004-31526d042d39":{"id":"6e435727-a8e1-492e-a004-31526d042d39","doc_no":"A.6.1.1.6.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9550,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"03ab595f13dabac7adcd24c62a5ab9287347e7cf99fd6cc43ea1ca46974338d8","addressRefs":[]},"b971db81-6c85-4e95-9fb1-4556cd05e988":{"id":"b971db81-6c85-4e95-9fb1-4556cd05e988","doc_no":"A.6.1.1.6.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9551,"content":"The documents herein organize all base information relevant to Pattern's usage of the Asset Liability Management Rental Primitive.","contentHash":"01733445ac56c3c23c82372c07b760fb26fbbaf443b9f5275b492ec0887310bc","addressRefs":[]},"d00700e6-033b-4cd8-a986-7129adae5859":{"id":"d00700e6-033b-4cd8-a986-7129adae5859","doc_no":"A.6.1.1.6.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9552,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"5095bf55-801b-43b9-9346-addbd20d6380":{"id":"5095bf55-801b-43b9-9346-addbd20d6380","doc_no":"A.6.1.1.6.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9553,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"a633ddea-66b1-4391-874f-ffdd2034380b":{"id":"a633ddea-66b1-4391-874f-ffdd2034380b","doc_no":"A.6.1.1.6.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9554,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"c1ac8c62-bd2f-4108-a297-6e0bea3e5244":{"id":"c1ac8c62-bd2f-4108-a297-6e0bea3e5244","doc_no":"A.6.1.1.6.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9555,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.6.3.1.2 - Active Instances Directory](5095bf55-801b-43b9-9346-addbd20d6380), whereas failed Invocations are Archived in [A.6.1.1.6.2.6.3.1.5 - Hub Data Repository](d7ec5f26-18a6-4453-bb73-fc40cfb6f8d1).","contentHash":"68cabc51436cac56a51e5613ccc475e8443d463a42d15b4536d1357c51444564","addressRefs":[]},"d7ec5f26-18a6-4453-bb73-fc40cfb6f8d1":{"id":"d7ec5f26-18a6-4453-bb73-fc40cfb6f8d1","doc_no":"A.6.1.1.6.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9556,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ce88b10b-8ff5-470b-bbc4-14ad92752989":{"id":"ce88b10b-8ff5-470b-bbc4-14ad92752989","doc_no":"A.6.1.1.6.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9557,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"a14c1182-eaec-4c43-adc6-4b3f6809adb9":{"id":"a14c1182-eaec-4c43-adc6-4b3f6809adb9","doc_no":"A.6.1.1.6.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9558,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"be53be24-2aab-4b26-815d-23b776016bb9":{"id":"be53be24-2aab-4b26-815d-23b776016bb9","doc_no":"A.6.1.1.6.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9559,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"64838888-348c-4209-925a-f5bb3be8c5e8":{"id":"64838888-348c-4209-925a-f5bb3be8c5e8","doc_no":"A.6.1.1.6.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9560,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"8c9e34d9-05c5-4885-af09-83de803f9417":{"id":"8c9e34d9-05c5-4885-af09-83de803f9417","doc_no":"A.6.1.1.6.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9561,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"ae5f669d-b19f-4ddb-ad13-9e9012a1bef3":{"id":"ae5f669d-b19f-4ddb-ad13-9e9012a1bef3","doc_no":"A.6.1.1.6.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9562,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.6.3.2 - Active Instances](64838888-348c-4209-925a-f5bb3be8c5e8).","contentHash":"8558768883374737d06d2931d5e9cc5ad5d6b58527a80606f3574e82c71dce7d","addressRefs":[]},"99858314-0f00-4b3b-b249-a0b236f52f0a":{"id":"99858314-0f00-4b3b-b249-a0b236f52f0a","doc_no":"A.6.1.1.6.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9563,"content":"The documents herein implement the Core Governance Primitives for Pattern. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"58c88a3eca15b2f1459abbae50613aaa8cc5cf42cf18b87a27e523c6ef8d1c76","addressRefs":[]},"a63ed032-155a-42c3-9791-571a01d5f2fb":{"id":"a63ed032-155a-42c3-9791-571a01d5f2fb","doc_no":"A.6.1.1.6.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9564,"content":"The documents herein contain all data and specifications for Pattern's Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"7e151030ecd0283e1824c154573fe3a7ae9caecd8fc19473d043070c5bbcf110","addressRefs":[]},"4ca55a86-e89b-43d7-8291-297c3ecf5586":{"id":"4ca55a86-e89b-43d7-8291-297c3ecf5586","doc_no":"A.6.1.1.6.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9565,"content":"The documents herein organize all base information relevant to Pattern's usage of the Core Governance Reward Primitive.","contentHash":"b8399664061d02af9823986c56669c61e0046cdb1e4702f6b7ef6d4413c57459","addressRefs":[]},"cf6ee47e-4796-44a7-9689-5ac2189be470":{"id":"cf6ee47e-4796-44a7-9689-5ac2189be470","doc_no":"A.6.1.1.6.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9566,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"757d7404-e9c0-4320-9db0-841a5b703d12":{"id":"757d7404-e9c0-4320-9db0-841a5b703d12","doc_no":"A.6.1.1.6.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9567,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"9bef7242-a809-4cf3-a2db-787974915c1e":{"id":"9bef7242-a809-4cf3-a2db-787974915c1e","doc_no":"A.6.1.1.6.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9568,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"374de01d-c42b-4322-89cf-aa613a136a3f":{"id":"374de01d-c42b-4322-89cf-aa613a136a3f","doc_no":"A.6.1.1.6.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9569,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.7.1.1.2 - Active Instances Directory](757d7404-e9c0-4320-9db0-841a5b703d12), whereas failed Invocations are Archived in [A.6.1.1.6.2.7.1.1.5 - Hub Data Repository](3bcc019b-a28c-4532-9b1a-0b563eaa7cc2).","contentHash":"1be9661d79397ac2fe219e9b2741da85ca87ce02a62d91923c3b22c47a05a5b1","addressRefs":[]},"3bcc019b-a28c-4532-9b1a-0b563eaa7cc2":{"id":"3bcc019b-a28c-4532-9b1a-0b563eaa7cc2","doc_no":"A.6.1.1.6.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9570,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"91e8f0e7-55f0-4fcb-a46a-97086e69696b":{"id":"91e8f0e7-55f0-4fcb-a46a-97086e69696b","doc_no":"A.6.1.1.6.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9571,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"dc26dbaf-0c48-4b40-90bf-46543efc6050":{"id":"dc26dbaf-0c48-4b40-90bf-46543efc6050","doc_no":"A.6.1.1.6.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9572,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"5a6d6aae-19ed-4474-b8f4-de09a5dc8344":{"id":"5a6d6aae-19ed-4474-b8f4-de09a5dc8344","doc_no":"A.6.1.1.6.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9573,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"c7489972-e440-4693-b8e4-0e0c2ead4850":{"id":"c7489972-e440-4693-b8e4-0e0c2ead4850","doc_no":"A.6.1.1.6.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9574,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"fe4128c5-e0a0-4e25-8b47-5ee583e00e33":{"id":"fe4128c5-e0a0-4e25-8b47-5ee583e00e33","doc_no":"A.6.1.1.6.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9575,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"4da34ab2-143e-4a89-8b40-e4c1bafa7951":{"id":"4da34ab2-143e-4a89-8b40-e4c1bafa7951","doc_no":"A.6.1.1.6.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"42740824-41c4-49f1-9b59-177aa36ecc9d","order":9576,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.7.1.2 - Active Instances](c7489972-e440-4693-b8e4-0e0c2ead4850).","contentHash":"33fa9656a45447b8d6a629206f9dc88d4095260a8e8b583213da634e487f6c48","addressRefs":[]},"42652f00-4299-41db-9124-10be8b030ee3":{"id":"42652f00-4299-41db-9124-10be8b030ee3","doc_no":"A.6.1.1.6.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"dc083d10-74bc-43b6-ab2f-c91efce76e84","order":9577,"content":"The documents herein define Pattern's strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"364a9154dc225ca04d39cc482048ae6cf0f9f236a55e03ed803a783250d58fbc","addressRefs":[]},"df8e7155-ba1f-4606-8a4a-0619c06da12b":{"id":"df8e7155-ba1f-4606-8a4a-0619c06da12b","doc_no":"A.6.1.1.6.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"42652f00-4299-41db-9124-10be8b030ee3","order":9578,"content":"The documents herein specify Pattern governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Pattern Artifact is specified in the Root Edit Primitive above at [A.6.1.1.6.2.2.2 - Root Edit Primitive](e30f2e01-78c1-4286-a80a-0df31923303f).","contentHash":"ed027f249f1011a9134c34e81203f17182dfef0fcfd7032d3e6795d67d0fc539","addressRefs":[]},"1382be77-1dc3-40e0-811d-cce8052282ee":{"id":"1382be77-1dc3-40e0-811d-cce8052282ee","doc_no":"A.6.1.1.6.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"42652f00-4299-41db-9124-10be8b030ee3","order":9579,"content":"Pattern uses the Sky Forum for governance-related discussion. Posts should use the \"Pattern Prime\" category.","contentHash":"598edd64c7544cdb6fadb13b169a7457455e277c81a00a4b9c3cef9bfd96ac0a","addressRefs":[]},"721cb164-5c20-425d-a479-43e426066909":{"id":"721cb164-5c20-425d-a479-43e426066909","doc_no":"A.6.1.1.6.3.1.2","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"42652f00-4299-41db-9124-10be8b030ee3","order":9580,"content":"The documents herein specify Pattern's emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Pattern Artifact.","contentHash":"0ed17a6d3e7085719dbc0bf5ccc8c6d78b5af34e1a882b6aa70f2eda8963896d","addressRefs":[]},"5c2318bb-f6ce-4804-83b1-cb5efa914a23":{"id":"5c2318bb-f6ce-4804-83b1-cb5efa914a23","doc_no":"A.6.1.1.6.3.1.3","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"42652f00-4299-41db-9124-10be8b030ee3","order":9581,"content":"The documents herein specify Pattern's emergency response protocol in situations solely impacting Pattern versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Pattern Artifact.","contentHash":"4b1f59ea1e50bfd3207ae6194e86a9a3e157ea4474ec1c11a80a5b44e5015c89","addressRefs":[]},"eba0dcc7-e135-496f-b866-342deeb91dc4":{"id":"eba0dcc7-e135-496f-b866-342deeb91dc4","doc_no":"A.6.1.1.7","title":"Launch Agent 6","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":9582,"content":"The documents herein specify all of the logic for Launch Agent 6, including Launch Agent 6's strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"283602dec9ac955204841dac7cca02254ba3198a396c59caad611ad5d07df1b1","addressRefs":[]},"963a72da-503f-4150-922e-94155924be8d":{"id":"963a72da-503f-4150-922e-94155924be8d","doc_no":"A.6.1.1.7.1","title":"Introduction","type":"Core","depth":5,"parentId":"eba0dcc7-e135-496f-b866-342deeb91dc4","order":9583,"content":"Launch Agent 6 is an Agent focused on building credit infrastructure for onchain and traditional finance, with a focus on USD₮ liquidity. In addition to allocating capital to scale Sky's collateral portfolio, Launch Agent 6 serves as a platform enabling stablecoin distribution hubs—including exchanges, wallets, and neobanks—to access institutional grade lending infrastructure underpinning USDS through a suite of products.","contentHash":"679ca5cf250ab076bd3969f8d05b061fcc2697d8bb51749b407b50bc6cf6f6a9","addressRefs":[]},"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0":{"id":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","doc_no":"A.6.1.1.7.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"eba0dcc7-e135-496f-b866-342deeb91dc4","order":9584,"content":"The documents herein implement the Sky Primitives for Launch Agent 6. See [A.2.2.1.5 - Primitives](947a5b27-d2dc-41e4-b6fd-696e35e2929d).","contentHash":"d8261d7ec2bd754aa15dfaf099a05650a52bbe2c39c19bccb92265b23c4b526e","addressRefs":[]},"7594cfaf-c101-4379-976e-aba279add723":{"id":"7594cfaf-c101-4379-976e-aba279add723","doc_no":"A.6.1.1.7.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9585,"content":"The documents herein implement the Genesis Primitives for Launch Agent 6. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"b1388a08218ebd1d4a185814a6e5082ee38e66e9df0039c95a940b4f98fd882d","addressRefs":[]},"1049c46a-0222-4101-ad86-b8c75c73ffd6":{"id":"1049c46a-0222-4101-ad86-b8c75c73ffd6","doc_no":"A.6.1.1.7.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9586,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"de893edd1b7e524dd1fb664003a153b0a442c28e3d229b4fc71ff0d5bd93e93a","addressRefs":[]},"e8203aca-ee78-41c6-ad35-8f7324d9a277":{"id":"e8203aca-ee78-41c6-ad35-8f7324d9a277","doc_no":"A.6.1.1.7.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9587,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Agent Creation Primitive.","contentHash":"6d8fde945d4c86936530fb67c8aacc8409120168b3b1639fc9cb38f77f850633","addressRefs":[]},"7e7f3004-1886-4783-8360-561ef927ff35":{"id":"7e7f3004-1886-4783-8360-561ef927ff35","doc_no":"A.6.1.1.7.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9588,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"77c294b2-2d74-4a90-8c43-982abcc64afb":{"id":"77c294b2-2d74-4a90-8c43-982abcc64afb","doc_no":"A.6.1.1.7.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9589,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"ef331af9-dfd3-4b0c-abd2-75ce104bf1ca":{"id":"ef331af9-dfd3-4b0c-abd2-75ce104bf1ca","doc_no":"A.6.1.1.7.2.1.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9590,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"211ee879-956d-4e04-aa8a-2599c9872e86":{"id":"211ee879-956d-4e04-aa8a-2599c9872e86","doc_no":"A.6.1.1.7.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9591,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.1.1.3.1 - Single Instance Configuration Document](a4cd3e49-84c9-44e6-86f2-6a1b34162d50).","contentHash":"d4460885a2cf10386e91008be940f985b52edae8068095567a449ecdbbc4b992","addressRefs":[]},"383eb03a-1eba-4266-880f-58571f78b719":{"id":"383eb03a-1eba-4266-880f-58571f78b719","doc_no":"A.6.1.1.7.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9592,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"bdf94e77-b137-4a01-aefb-314b92d49b24":{"id":"bdf94e77-b137-4a01-aefb-314b92d49b24","doc_no":"A.6.1.1.7.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9593,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"6a2b403a-772e-47a0-8873-47749729512f":{"id":"6a2b403a-772e-47a0-8873-47749729512f","doc_no":"A.6.1.1.7.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9594,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"038042c1-bec7-43e5-9a76-81a4a836aa7d":{"id":"038042c1-bec7-43e5-9a76-81a4a836aa7d","doc_no":"A.6.1.1.7.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9595,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"31c1d31a-91fb-4487-b65d-8e682044276f":{"id":"31c1d31a-91fb-4487-b65d-8e682044276f","doc_no":"A.6.1.1.7.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9596,"content":"The subtrees for Instances of the Agent Creation Primitive with `Suspended` Status are stored here.","contentHash":"183d20b3c12bea99884c81ff611bff6d5be670766bb91a4f4ccf5339e0a26636","addressRefs":[]},"99e0c315-2f2a-4d61-b653-70b75c03be0d":{"id":"99e0c315-2f2a-4d61-b653-70b75c03be0d","doc_no":"A.6.1.1.7.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9597,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"6ff08b90-e51c-4ab7-abee-ab864131cced":{"id":"6ff08b90-e51c-4ab7-abee-ab864131cced","doc_no":"A.6.1.1.7.2.1.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9598,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"a4cd3e49-84c9-44e6-86f2-6a1b34162d50":{"id":"a4cd3e49-84c9-44e6-86f2-6a1b34162d50","doc_no":"A.6.1.1.7.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9599,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"c5df1f14-67f1-4be4-b4c2-be6ddf68e9cd":{"id":"c5df1f14-67f1-4be4-b4c2-be6ddf68e9cd","doc_no":"A.6.1.1.7.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9600,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"e225427b-cf79-4922-a423-b12a23a659c3":{"id":"e225427b-cf79-4922-a423-b12a23a659c3","doc_no":"A.6.1.1.7.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9601,"content":"The name of the Agent is Launch Agent 6.","contentHash":"88f1cbc68b7def740379b5a6c56610564e94aa108d3b4b524d12c6ce6dac1cae","addressRefs":[]},"bb7586a5-8e85-4d8c-aedc-2b0f76fb826f":{"id":"bb7586a5-8e85-4d8c-aedc-2b0f76fb826f","doc_no":"A.6.1.1.7.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9602,"content":"The address of Launch Agent 6's SubProxy Account on the Ethereum Mainnet is `0x24fdcd3bFA5C2553e05B2f9AD0365EBC296278D3`.","contentHash":"aa2a4923c0947818d057176190b0c1f557b4ea62c9d41a41d759a63a575243e8","addressRefs":["0x24fdcd3bfa5c2553e05b2f9ad0365ebc296278d3"]},"d3499ce6-c517-49f7-a07e-b321c390470d":{"id":"d3499ce6-c517-49f7-a07e-b321c390470d","doc_no":"A.6.1.1.7.2.1.1.3.1.1.3","title":"StarGuard Contract","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9603,"content":"The address of Launch Agent 6's StarGuard contract on the Ethereum Mainnet is `0xBfA2D1dA838E55A74c61699e164cDFF8cF0cF0e2`.","contentHash":"b5a16d5f23591929eb38800e4d9b2cde2b1bd3a0c82bef1c8b672e1109145ece","addressRefs":["0xbfa2d1da838e55a74c61699e164cdff8cf0cf0e2"]},"96060edd-a089-499c-9e96-b90a89bc2c0c":{"id":"96060edd-a089-499c-9e96-b90a89bc2c0c","doc_no":"A.6.1.1.7.2.1.1.3.1.1.3.1","title":"StarGuard Max Delay","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9604,"content":"The Launch Agent 6 StarGuard `maxDelay` is seven (7) days.","contentHash":"dd6e1af4b5ddffd2eab0b4924aed4f466238f9b843aead108125ad4b58af01f2","addressRefs":[]},"a5674a63-9d57-4fd9-9b66-ec653f49afab":{"id":"a5674a63-9d57-4fd9-9b66-ec653f49afab","doc_no":"A.6.1.1.7.2.1.1.3.1.1.4","title":"Genesis Account","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9605,"content":"The address of Launch Agent 6's Genesis Account will be specified in a future iteration of the Launch Agent 6 Artifact.","contentHash":"1c36ca156be635d430f4876b608b983f7028595fa002a848d1df6eaae09344a3","addressRefs":[]},"433f5f95-3a16-4f07-b389-b4ead64f21f2":{"id":"433f5f95-3a16-4f07-b389-b4ead64f21f2","doc_no":"A.6.1.1.7.2.1.1.3.1.1.5","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9606,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"62d84951-7f77-423e-b5df-960faf6b2fd0":{"id":"62d84951-7f77-423e-b5df-960faf6b2fd0","doc_no":"A.6.1.1.7.2.1.1.3.1.1.5.1","title":"Launch Agent 6 Foundation","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9607,"content":"The Launch Agent 6 Foundation is the Prime Foundation associated with Launch Agent 6. Its mandate is to support the development, growth, and adoption of Launch Agent 6.","contentHash":"389e4f4c2aa76b20f81feaa2813b1305b87ca6337e48fb2304f581e141e0b435","addressRefs":[]},"0eb2722b-c3e2-4c9a-83c1-986b0b0587cb":{"id":"0eb2722b-c3e2-4c9a-83c1-986b0b0587cb","doc_no":"A.6.1.1.7.2.1.1.3.1.1.5.2","title":"Stablewatch","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9608,"content":"Stablewatch is a development company that provides services to the Launch Agent 6 Foundation.","contentHash":"6e24022fda77559fd5ecaf4f69ce43fbf43f96db6513dccd2c4296692efe4556","addressRefs":[]},"cf57e4ff-d96b-486d-a37e-93c711308d4c":{"id":"cf57e4ff-d96b-486d-a37e-93c711308d4c","doc_no":"A.6.1.1.7.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9609,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"61c2470d-9699-48c1-8d0b-93bf452fe8b8":{"id":"61c2470d-9699-48c1-8d0b-93bf452fe8b8","doc_no":"A.6.1.1.7.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9610,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"d58b413f-6fce-4b0d-80a8-aba5d74117b0":{"id":"d58b413f-6fce-4b0d-80a8-aba5d74117b0","doc_no":"A.6.1.1.7.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9611,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"0d4f2b2d-305b-4a23-9764-64fdf5a7bcc8":{"id":"0d4f2b2d-305b-4a23-9764-64fdf5a7bcc8","doc_no":"A.6.1.1.7.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9612,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"dc435918-f881-4d35-af7d-1640979cc9cd":{"id":"dc435918-f881-4d35-af7d-1640979cc9cd","doc_no":"A.6.1.1.7.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9613,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"ff4e7a8d-3832-40a3-b2b0-fec3831ed689":{"id":"ff4e7a8d-3832-40a3-b2b0-fec3831ed689","doc_no":"A.6.1.1.7.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9614,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"ff1ff3b0-3505-475a-9b04-92e0fbb16978":{"id":"ff1ff3b0-3505-475a-9b04-92e0fbb16978","doc_no":"A.6.1.1.7.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9615,"content":"The documents herein contain all data and specifications for Launch Agent 6's instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"04ce41d0677fd9204579e64c9dcd617459055b10a03820f9915c988f347b82d5","addressRefs":[]},"ccbf1b06-7d52-4355-8780-2618c68f1bfe":{"id":"ccbf1b06-7d52-4355-8780-2618c68f1bfe","doc_no":"A.6.1.1.7.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9616,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Prime Transformation Primitive.","contentHash":"8bfba5f28396e88ff3c5057a1989aba4af31f7155b14ecd5021261cd42030365","addressRefs":[]},"f8278414-f667-4d1d-a2bd-8ada95c5311a":{"id":"f8278414-f667-4d1d-a2bd-8ada95c5311a","doc_no":"A.6.1.1.7.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9617,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"ea4d3442-8d1a-4948-b199-d4d3831a58ce":{"id":"ea4d3442-8d1a-4948-b199-d4d3831a58ce","doc_no":"A.6.1.1.7.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9618,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"8a699a06-4d30-4815-a2c5-a77c6effe229":{"id":"8a699a06-4d30-4815-a2c5-a77c6effe229","doc_no":"A.6.1.1.7.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9619,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"337fa7c7-9727-4257-a4cb-6205afc2b687":{"id":"337fa7c7-9727-4257-a4cb-6205afc2b687","doc_no":"A.6.1.1.7.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9620,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.1.2.3.1 - Single Instance Configuration Document](9bfd222e-7d6f-4ad3-a248-bf87900f4993).","contentHash":"3f75c06f583a9ab985697dc5b4cd7ee39144b003ce03f11dac4400d812d50e8f","addressRefs":[]},"0fcf82ab-6ae3-41c7-b8e4-424dd5f3850d":{"id":"0fcf82ab-6ae3-41c7-b8e4-424dd5f3850d","doc_no":"A.6.1.1.7.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9621,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"7cc6435b-939d-4695-882b-2e2cde5dd9b5":{"id":"7cc6435b-939d-4695-882b-2e2cde5dd9b5","doc_no":"A.6.1.1.7.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9622,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"378a3dc3-181d-48f1-bd16-6ab43905bbf7":{"id":"378a3dc3-181d-48f1-bd16-6ab43905bbf7","doc_no":"A.6.1.1.7.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9623,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"f0c60a20-750b-4f1f-a17e-871d4f1c76c4":{"id":"f0c60a20-750b-4f1f-a17e-871d4f1c76c4","doc_no":"A.6.1.1.7.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9624,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"5ca98f18-9440-4717-a940-2c663121dbc7":{"id":"5ca98f18-9440-4717-a940-2c663121dbc7","doc_no":"A.6.1.1.7.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9625,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"adb5289b-af36-42b8-8ca4-6bd4cfbc7ac7":{"id":"adb5289b-af36-42b8-8ca4-6bd4cfbc7ac7","doc_no":"A.6.1.1.7.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9626,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"ab6b47e6-8f17-4caa-a2f4-4f1a87f95545":{"id":"ab6b47e6-8f17-4caa-a2f4-4f1a87f95545","doc_no":"A.6.1.1.7.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9627,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"9bfd222e-7d6f-4ad3-a248-bf87900f4993":{"id":"9bfd222e-7d6f-4ad3-a248-bf87900f4993","doc_no":"A.6.1.1.7.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9628,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"38a57bee-dfc8-462c-888c-3a2963e3539d":{"id":"38a57bee-dfc8-462c-888c-3a2963e3539d","doc_no":"A.6.1.1.7.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9629,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"69d7e31c-36a7-4500-9e78-25167e2f38ab":{"id":"69d7e31c-36a7-4500-9e78-25167e2f38ab","doc_no":"A.6.1.1.7.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9630,"content":"Launch Agent 6 is a Prime Agent.","contentHash":"c790de6138fd57c30ff0a47926cffa34f302c683e92a11063481da723a36cf7e","addressRefs":[]},"967efec7-0378-4491-94b1-918ea79de538":{"id":"967efec7-0378-4491-94b1-918ea79de538","doc_no":"A.6.1.1.7.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9631,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"70018dbb-8b14-41d5-aef0-529e6104ea36":{"id":"70018dbb-8b14-41d5-aef0-529e6104ea36","doc_no":"A.6.1.1.7.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9632,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"fa03dbed-b41c-41db-8adb-826c991d64b8":{"id":"fa03dbed-b41c-41db-8adb-826c991d64b8","doc_no":"A.6.1.1.7.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9633,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"36e23c65-220f-43b9-ab14-6f0fe4a25524":{"id":"36e23c65-220f-43b9-ab14-6f0fe4a25524","doc_no":"A.6.1.1.7.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9634,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"d5c113e8-b4d2-40c4-80d8-5797f8833cd3":{"id":"d5c113e8-b4d2-40c4-80d8-5797f8833cd3","doc_no":"A.6.1.1.7.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9635,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"1b8cb6c6-0906-4c56-935f-ad8e43bb9a11":{"id":"1b8cb6c6-0906-4c56-935f-ad8e43bb9a11","doc_no":"A.6.1.1.7.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9636,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"33beb09c-af1f-4d75-8307-d4546192acf8":{"id":"33beb09c-af1f-4d75-8307-d4546192acf8","doc_no":"A.6.1.1.7.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9637,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"0e769f4f-510c-49a4-aaa8-03a822ed75f3":{"id":"0e769f4f-510c-49a4-aaa8-03a822ed75f3","doc_no":"A.6.1.1.7.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9638,"content":"The documents herein contain all data and specifications for Launch Agent 6's instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"eb4d334e0f8f6e42f4e9690b3656ad295d1b5c02a427f14612e3734c0120461a","addressRefs":[]},"d46b399b-0432-4350-9e3c-d5cf3487764f":{"id":"d46b399b-0432-4350-9e3c-d5cf3487764f","doc_no":"A.6.1.1.7.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9639,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Executor Transformation Primitive.","contentHash":"18842375903e093bbbf8cd12b3e6cb0a82d260950727cc97d595ade9bcb8a17b","addressRefs":[]},"24501122-1780-4f2c-b23c-d9608e8d3475":{"id":"24501122-1780-4f2c-b23c-d9608e8d3475","doc_no":"A.6.1.1.7.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9640,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"b967e4a6-4911-4dd5-a8e4-b54047a589c0":{"id":"b967e4a6-4911-4dd5-a8e4-b54047a589c0","doc_no":"A.6.1.1.7.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9641,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"9744681d-c677-4153-8d70-32fd72a7554c":{"id":"9744681d-c677-4153-8d70-32fd72a7554c","doc_no":"A.6.1.1.7.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9642,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"1344eb03-7880-49c9-bed0-c2a954c93069":{"id":"1344eb03-7880-49c9-bed0-c2a954c93069","doc_no":"A.6.1.1.7.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9643,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"061f9187-78ca-4966-a1dc-e53b7f11faa1":{"id":"061f9187-78ca-4966-a1dc-e53b7f11faa1","doc_no":"A.6.1.1.7.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9644,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ffd96894-fd24-4644-b9ed-ab03ba5b72ce":{"id":"ffd96894-fd24-4644-b9ed-ab03ba5b72ce","doc_no":"A.6.1.1.7.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9645,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"800dbefc-e953-40fa-b84a-6b199c9f46ee":{"id":"800dbefc-e953-40fa-b84a-6b199c9f46ee","doc_no":"A.6.1.1.7.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9646,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"866b3ee2-2a07-4bfa-81cc-d5a664bb78d0":{"id":"866b3ee2-2a07-4bfa-81cc-d5a664bb78d0","doc_no":"A.6.1.1.7.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9647,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"00ccdc84-b88e-4e2c-ac6a-2e5b6e882c62":{"id":"00ccdc84-b88e-4e2c-ac6a-2e5b6e882c62","doc_no":"A.6.1.1.7.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9648,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"f3fb394f-c38b-41f8-a215-db199329bfee":{"id":"f3fb394f-c38b-41f8-a215-db199329bfee","doc_no":"A.6.1.1.7.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9649,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"a5cbb162-5a2b-44db-857b-1af33c13b1e6":{"id":"a5cbb162-5a2b-44db-857b-1af33c13b1e6","doc_no":"A.6.1.1.7.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9650,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"b9ef6634-cc3a-487f-8588-a1f2d3b8346c":{"id":"b9ef6634-cc3a-487f-8588-a1f2d3b8346c","doc_no":"A.6.1.1.7.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9651,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"2800fbf1a7c176e716ac12ffb2da7b6b511b68a429ad425aaf09cccfe7d630cf","addressRefs":[]},"1885d903-2eff-43cf-9ed4-c7bd586c0af0":{"id":"1885d903-2eff-43cf-9ed4-c7bd586c0af0","doc_no":"A.6.1.1.7.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9652,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Agent Token Primitive.","contentHash":"09311fefa73dee62b5fc50299f34ebacc7a2b83d4d21c47008adb5468235ccf0","addressRefs":[]},"b1f02877-3e82-4c5d-b99c-b422e5cad652":{"id":"b1f02877-3e82-4c5d-b99c-b422e5cad652","doc_no":"A.6.1.1.7.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9653,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"0e0755ba-fbc4-417b-bb74-8c8c81aa20af":{"id":"0e0755ba-fbc4-417b-bb74-8c8c81aa20af","doc_no":"A.6.1.1.7.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9654,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"38b3be19-4fb6-4af7-9d6a-f46cd006d7b8":{"id":"38b3be19-4fb6-4af7-9d6a-f46cd006d7b8","doc_no":"A.6.1.1.7.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9655,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.1.4.2.1 - Single Instance Configuration Document](80dc8fe6-5c4e-44aa-b9fb-89350ac4e5bf).","contentHash":"377642e4521ffdd7cc74eacdaee9a5a02a1f0ef67dc48eccf5f7b3592dc689f2","addressRefs":[]},"481bb1cf-1a60-4ceb-9502-ffdd1a19b50e":{"id":"481bb1cf-1a60-4ceb-9502-ffdd1a19b50e","doc_no":"A.6.1.1.7.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9656,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"4163c78f-f018-47cd-8efc-f407119283c2":{"id":"4163c78f-f018-47cd-8efc-f407119283c2","doc_no":"A.6.1.1.7.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9657,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent's token, no further Instances of the Primitive can be Invoked.","contentHash":"074cf01e7e3e0ae54374fe52a096387e2d56f0d44ce5ffbe535b303308949c9a","addressRefs":[]},"54bd28cb-95e9-432a-8107-751ef59b9fc4":{"id":"54bd28cb-95e9-432a-8107-751ef59b9fc4","doc_no":"A.6.1.1.7.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9658,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"090c9945-ad81-47e3-925a-3c364c38a6df":{"id":"090c9945-ad81-47e3-925a-3c364c38a6df","doc_no":"A.6.1.1.7.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9659,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"f3ecfdce-f3d1-44b0-900b-5d1aca5e3edc":{"id":"f3ecfdce-f3d1-44b0-900b-5d1aca5e3edc","doc_no":"A.6.1.1.7.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9660,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"72dbc2a7-c097-4385-94d5-8f71833b1360":{"id":"72dbc2a7-c097-4385-94d5-8f71833b1360","doc_no":"A.6.1.1.7.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9661,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"ca56cc56-4afb-46a8-b754-5956e73075f1":{"id":"ca56cc56-4afb-46a8-b754-5956e73075f1","doc_no":"A.6.1.1.7.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9662,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"80dc8fe6-5c4e-44aa-b9fb-89350ac4e5bf":{"id":"80dc8fe6-5c4e-44aa-b9fb-89350ac4e5bf","doc_no":"A.6.1.1.7.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9663,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"44fa192b-1ac1-4ef3-923e-8529a433c83f":{"id":"44fa192b-1ac1-4ef3-923e-8529a433c83f","doc_no":"A.6.1.1.7.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9664,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"ccd245e9-50d4-4083-9f9c-c77a204f9ecc":{"id":"ccd245e9-50d4-4083-9f9c-c77a204f9ecc","doc_no":"A.6.1.1.7.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9665,"content":"The name of Launch Agent 6's token is Launch Agent 6.","contentHash":"506b38bd0cb94361cdc2f8c1cdc28c8c4e4f9876a3631907564364bc636972dd","addressRefs":[]},"841b8960-e62f-4602-b213-9474157b0684":{"id":"841b8960-e62f-4602-b213-9474157b0684","doc_no":"A.6.1.1.7.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9666,"content":"The symbol of Launch Agent 6's token is AGENT6.","contentHash":"afa9a200ac679f167f77d556ea60b4d32da69b4accdea2963bf29b78148774fa","addressRefs":[]},"a1b32961-6aa2-4385-b515-b1bc334960df":{"id":"a1b32961-6aa2-4385-b515-b1bc334960df","doc_no":"A.6.1.1.7.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9667,"content":"The Genesis Supply of AGENT6 is 1 billion.","contentHash":"bf8784423e8dc5fb86cf6d374e0590d285cee69931e584fbacaab1000aef0ebf","addressRefs":[]},"bd33da7e-609b-4866-89f7-637987cff659":{"id":"bd33da7e-609b-4866-89f7-637987cff659","doc_no":"A.6.1.1.7.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9668,"content":"The address of AGENT6 will be specified in a future iteration of the Launch Agent 6 Artifact.","contentHash":"ff422ef271b2aca7677624fe1c5247e8157ac0619b9539712e32861f298f2e9a","addressRefs":[]},"1863bfd0-8b9f-4c76-8748-c9262f6245a9":{"id":"1863bfd0-8b9f-4c76-8748-c9262f6245a9","doc_no":"A.6.1.1.7.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9669,"content":"The token Admin will be specified in a future iteration of the Launch Agent 6 Artifact.","contentHash":"04b221f0587fe5d48fa617081bfa78b16ca9148c839d7aaf17e7121fd6687d4f","addressRefs":[]},"8ce3d244-b7d4-4cc4-b35e-5deaccc9c52f":{"id":"8ce3d244-b7d4-4cc4-b35e-5deaccc9c52f","doc_no":"A.6.1.1.7.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9670,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Launch Agent 6 Governance. Sky Governance retains the ability to revert where Launch Agent 6 is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"8f11d3b3e4767c0d19f22696300d768200397ae493a41295b01e52a7541fa526","addressRefs":[]},"bac7bdc2-4060-4ae7-8273-4420d96c53dd":{"id":"bac7bdc2-4060-4ae7-8273-4420d96c53dd","doc_no":"A.6.1.1.7.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9671,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"5179fc59-1ed8-45be-9516-58c59083d6c1":{"id":"5179fc59-1ed8-45be-9516-58c59083d6c1","doc_no":"A.6.1.1.7.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9672,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.\n\n- These processes will be defined in a future iteration of the Launch Agent 6 Artifact.","contentHash":"c4c47c222afed1a490567be1a385b1961785965b23f84df820fa6b1f50da7dc9","addressRefs":[]},"b4574752-f657-4d44-8be0-0387a26b2f0a":{"id":"b4574752-f657-4d44-8be0-0387a26b2f0a","doc_no":"A.6.1.1.7.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9673,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"1d7df1bf-116c-451f-ad56-3fb899db577b":{"id":"1d7df1bf-116c-451f-ad56-3fb899db577b","doc_no":"A.6.1.1.7.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9674,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"a56b88fe-398f-4384-ac87-4cd45c0290cf":{"id":"a56b88fe-398f-4384-ac87-4cd45c0290cf","doc_no":"A.6.1.1.7.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9675,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"cc30ee14-2850-45fa-bdf0-84d4789b7d3d":{"id":"cc30ee14-2850-45fa-bdf0-84d4789b7d3d","doc_no":"A.6.1.1.7.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9676,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"dc44ad54-7a03-43b0-8a1b-232353c163c3":{"id":"dc44ad54-7a03-43b0-8a1b-232353c163c3","doc_no":"A.6.1.1.7.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9677,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"cdd39473-4eaf-4a3b-9d6a-2cd0ac46859b":{"id":"cdd39473-4eaf-4a3b-9d6a-2cd0ac46859b","doc_no":"A.6.1.1.7.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9678,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent's token, no further Instances of the Primitive can be Invoked.","contentHash":"074cf01e7e3e0ae54374fe52a096387e2d56f0d44ce5ffbe535b303308949c9a","addressRefs":[]},"6b98a6ae-9f12-4503-9096-9e548d68451d":{"id":"6b98a6ae-9f12-4503-9096-9e548d68451d","doc_no":"A.6.1.1.7.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9679,"content":"The documents herein implement the Operational Primitives for Launch Agent 6. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"435f499a5de9c9fe30e6b5cf5e1993d2ed62858218de8c2e2d09459f9fdaff43","addressRefs":[]},"77a105f5-98e7-41b8-acac-47a4d5473c81":{"id":"77a105f5-98e7-41b8-acac-47a4d5473c81","doc_no":"A.6.1.1.7.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9680,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"b385048b5a6a20499f0f71ed647790f21ec2c4ae5847c1d1ebaef7e09dda3642","addressRefs":[]},"6adf71d4-03f8-43ed-83ad-3011dfebe17d":{"id":"6adf71d4-03f8-43ed-83ad-3011dfebe17d","doc_no":"A.6.1.1.7.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9681,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Executor Accord Primitive.","contentHash":"08751e8e3c530743f06decee6ac514ac510aca4ec9127f3451bdfd11c5a84a6e","addressRefs":[]},"64d43bdf-ecd5-41bf-8023-64bf78ad70d4":{"id":"64d43bdf-ecd5-41bf-8023-64bf78ad70d4","doc_no":"A.6.1.1.7.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9682,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"a1260e19-86fc-4ebe-a53a-501e4baf9752":{"id":"a1260e19-86fc-4ebe-a53a-501e4baf9752","doc_no":"A.6.1.1.7.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9683,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"c0aff461-b4c5-4392-bf92-3db9ebe7a476":{"id":"c0aff461-b4c5-4392-bf92-3db9ebe7a476","doc_no":"A.6.1.1.7.2.2.1.1.2.1","title":"Ozone Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9684,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.2.1.2.1 - Ozone Instance Configuration Document](c41fe115-5145-438e-bcaf-9924996b4fcd).","contentHash":"7f86d883599d1172a53755ed51879d4d7e98362814da5b3888a2082b789f80ee","addressRefs":[]},"a3222e92-22ee-49a6-a7ae-20e7bd2a6ca5":{"id":"a3222e92-22ee-49a6-a7ae-20e7bd2a6ca5","doc_no":"A.6.1.1.7.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9685,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"c5af5be5-2612-4e3b-aad4-f06603235bd7":{"id":"c5af5be5-2612-4e3b-aad4-f06603235bd7","doc_no":"A.6.1.1.7.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9686,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.2.1.1.2 - Active Instances Directory](a1260e19-86fc-4ebe-a53a-501e4baf9752), whereas failed Invocations are Archived in [A.6.1.1.7.2.2.1.1.5 - Hub Data Repository](10c951e0-3200-4359-a76e-c1ff9ccb9105).","contentHash":"5e93844c8cdded2592bcfe5098c29d722f10e1c65ab11c8232da1144ea9ad6fc","addressRefs":[]},"10c951e0-3200-4359-a76e-c1ff9ccb9105":{"id":"10c951e0-3200-4359-a76e-c1ff9ccb9105","doc_no":"A.6.1.1.7.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9687,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"5621fd19-1f72-47d1-823e-762399ef7eae":{"id":"5621fd19-1f72-47d1-823e-762399ef7eae","doc_no":"A.6.1.1.7.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9688,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"593f7150-b5b6-48c6-8e39-30d084ac31ee":{"id":"593f7150-b5b6-48c6-8e39-30d084ac31ee","doc_no":"A.6.1.1.7.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9689,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"b2f1f9df-2812-4aa7-a066-dfb67ebdb288":{"id":"b2f1f9df-2812-4aa7-a066-dfb67ebdb288","doc_no":"A.6.1.1.7.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9690,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"d5f4610a-9cd1-4a6e-96de-5ea617463152":{"id":"d5f4610a-9cd1-4a6e-96de-5ea617463152","doc_no":"A.6.1.1.7.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9691,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"c41fe115-5145-438e-bcaf-9924996b4fcd":{"id":"c41fe115-5145-438e-bcaf-9924996b4fcd","doc_no":"A.6.1.1.7.2.2.1.2.1","title":"Ozone Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9692,"content":"The documents herein contain the Instance Configuration Document for the Ozone Executor Accord Primitive Instance.","contentHash":"ca0caee12f20439eb72be855f0a3c3853fe737be1313cfe253dad38c7f8d0623","addressRefs":[]},"f5dfa719-a44c-4a4f-bf28-9204a976dfcb":{"id":"f5dfa719-a44c-4a4f-bf28-9204a976dfcb","doc_no":"A.6.1.1.7.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9693,"content":"The documents herein define the parameters of the Ozone Instance of the Executor Accord Primitive.","contentHash":"638cf31df48e28f4a38e5155a81f9cd4b27bb221ff40cc010386b96be05691e5","addressRefs":[]},"1ab18042-345c-40b2-9ed3-06cfdb3b7d4b":{"id":"1ab18042-345c-40b2-9ed3-06cfdb3b7d4b","doc_no":"A.6.1.1.7.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9694,"content":"The Operational Facilitator and Operational GovOps for Ozone are specified in [A.6.1.2.2 - Operational Executor Agent Ozone](565660dd-7850-4c3a-8dba-554542bf103a)","contentHash":"b605e4e22016de812b8a12b273b1b84aa4cd0120376996255f9310ff6e3365e0","addressRefs":[]},"3b306de0-b8d7-4eda-b23b-0173c24e742e":{"id":"3b306de0-b8d7-4eda-b23b-0173c24e742e","doc_no":"A.6.1.1.7.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9695,"content":"The documents herein define the custom parameters of the Ozone Instance of the Executor Accord Primitive, if any.","contentHash":"be003f7a447f9026ea8e107c73c8b00f811e9d616575d90ced4c5ffb41a29c34","addressRefs":[]},"68badec0-cfad-49de-b15a-51f12e90275a":{"id":"68badec0-cfad-49de-b15a-51f12e90275a","doc_no":"A.6.1.1.7.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9696,"content":"The documents herein define the process for the ongoing management of the Ozone Instance of the Executor Accord Primitive.","contentHash":"03daa9d3ebfb53ae8a57e22ffb990501ed356259a7b153b51d2b35cb6013c74b","addressRefs":[]},"af743a8c-0d39-41ac-9898-0cdfac8e2c56":{"id":"af743a8c-0d39-41ac-9898-0cdfac8e2c56","doc_no":"A.6.1.1.7.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9697,"content":"The documents herein contain data relevant to the Ozone Instance of the Executor Accord Primitive.","contentHash":"edd3e28207fedf752584ef2eb5e88f52b3ff82d2d0a5d7cfed80703bd5ad5d72","addressRefs":[]},"23aab69c-d555-46d7-88ab-cb06303dc9af":{"id":"23aab69c-d555-46d7-88ab-cb06303dc9af","doc_no":"A.6.1.1.7.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9698,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"d283179e-7527-4522-8935-5fe4d2442ed5":{"id":"d283179e-7527-4522-8935-5fe4d2442ed5","doc_no":"A.6.1.1.7.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9699,"content":"The materials associated with Operational GovOps review during the Invocation of this Instance are contained herein.","contentHash":"4d9cf82f10b4116dc01ad201efd474911d68cc99e9ef9477435cf5f1402ce280","addressRefs":[]},"83075590-9293-4ae7-bdb0-701fd0689570":{"id":"83075590-9293-4ae7-bdb0-701fd0689570","doc_no":"A.6.1.1.7.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9700,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"a1204555-a3db-4b2d-a965-5a8300d66b3e":{"id":"a1204555-a3db-4b2d-a965-5a8300d66b3e","doc_no":"A.6.1.1.7.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9701,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"aa2527c7-a809-4552-8557-3d093bd80e53":{"id":"aa2527c7-a809-4552-8557-3d093bd80e53","doc_no":"A.6.1.1.7.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9702,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.2.1.2 - Active Instances](d5f4610a-9cd1-4a6e-96de-5ea617463152).","contentHash":"c5feeb46609fea30326abeea0b767bd25a6c8b20427ef16f0ecb99cd4fb5b2b6","addressRefs":[]},"6c61b3d8-6cc8-4250-8173-eee8396a4ef4":{"id":"6c61b3d8-6cc8-4250-8173-eee8396a4ef4","doc_no":"A.6.1.1.7.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9703,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"9f158e1a93b9b2bcb14b9860e42717ec3ecde92429b3b25ecd76125bcc837de3","addressRefs":[]},"30a4ea54-3083-4a3b-add0-0d3c41f5fcd2":{"id":"30a4ea54-3083-4a3b-add0-0d3c41f5fcd2","doc_no":"A.6.1.1.7.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9704,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Root Edit Primitive.","contentHash":"191e31b75ace823f75890e2ce8fc2b8d863f97214efc9c366050832e84cc5153","addressRefs":[]},"c2d33537-86aa-4953-9549-f8a298280ef2":{"id":"c2d33537-86aa-4953-9549-f8a298280ef2","doc_no":"A.6.1.1.7.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9705,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"3a35c81d-b624-4f61-9fad-6bb18aaf196b":{"id":"3a35c81d-b624-4f61-9fad-6bb18aaf196b","doc_no":"A.6.1.1.7.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9706,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"2bc5a631-5c2d-4d88-82ff-64883968bc22":{"id":"2bc5a631-5c2d-4d88-82ff-64883968bc22","doc_no":"A.6.1.1.7.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9707,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.2.2.2.1 - Single Instance Configuration Document](db6cb28a-c001-404d-b630-6ea755499ed3).","contentHash":"bd53a94288a749ee6042b2dba4a3058273899368efe2ce08d46c8a855aabb01a","addressRefs":[]},"4050328d-f2b9-4a46-baf7-563489ea7ebc":{"id":"4050328d-f2b9-4a46-baf7-563489ea7ebc","doc_no":"A.6.1.1.7.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9708,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"4bbc8ebb-94be-4625-8dd6-67961a03574e":{"id":"4bbc8ebb-94be-4625-8dd6-67961a03574e","doc_no":"A.6.1.1.7.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9709,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"151cb222-ad08-45c5-a884-55efd3d050d2":{"id":"151cb222-ad08-45c5-a884-55efd3d050d2","doc_no":"A.6.1.1.7.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9710,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"5dabf55e-66a0-4662-a3cd-5f522593f254":{"id":"5dabf55e-66a0-4662-a3cd-5f522593f254","doc_no":"A.6.1.1.7.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9711,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"c0cd8734-a01b-4e2b-b42c-622880a5e120":{"id":"c0cd8734-a01b-4e2b-b42c-622880a5e120","doc_no":"A.6.1.1.7.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9712,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"024712ec-d260-4464-86f2-10cad410a114":{"id":"024712ec-d260-4464-86f2-10cad410a114","doc_no":"A.6.1.1.7.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9713,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"c5c7c09a-2b33-465e-bc01-dc90415872d5":{"id":"c5c7c09a-2b33-465e-bc01-dc90415872d5","doc_no":"A.6.1.1.7.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9714,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"db6cb28a-c001-404d-b630-6ea755499ed3":{"id":"db6cb28a-c001-404d-b630-6ea755499ed3","doc_no":"A.6.1.1.7.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9715,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"dfaa57ba-36fa-45be-9f89-0bf77fbcff59":{"id":"dfaa57ba-36fa-45be-9f89-0bf77fbcff59","doc_no":"A.6.1.1.7.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9716,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.7.2.2.2.2.1.2 - Operational Process Definition](cfd923fb-0a53-4dd2-bb4f-5e840bda69c6).","contentHash":"14123d2ef88888b49473886686dfed158b48184563a23921541358d21290140b","addressRefs":[]},"cfd923fb-0a53-4dd2-bb4f-5e840bda69c6":{"id":"cfd923fb-0a53-4dd2-bb4f-5e840bda69c6","doc_no":"A.6.1.1.7.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9717,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 6 Agent Artifact. Information on Launch Agent 6 governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.7.3.1 - Governance Information Unrelated To Root Edit Primitive](a472d201-3dfd-4939-9789-5cedce9ea37a).","contentHash":"51c09b4170511fa9076272e2e5f79973cfa6ea7bee6c782f0cbebbf3178f67d1","addressRefs":[]},"ff28b8ca-2279-4ec4-96d9-e0b4d2340c64":{"id":"ff28b8ca-2279-4ec4-96d9-e0b4d2340c64","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9718,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 6 Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"32484375fef98cf4cec81cf3ff3d60feceb30c7ac10b38439c239ac2e6aefb04","addressRefs":[]},"70c91853-b74b-4c6b-befb-8446f00c9691":{"id":"70c91853-b74b-4c6b-befb-8446f00c9691","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9719,"content":"The Root Edit process begins with an AGENT6 token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. An AGENT6 token holder must hold at least 1% of the circulating token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Launch Agent 6 Prime\" category.","contentHash":"ac151a2982e40c99ab2b8939f3dad3cad53f036478f4967004ba3c48740e9561","addressRefs":[]},"caafe932-8fa7-4ee6-ba0b-dd49bcef1ee1":{"id":"caafe932-8fa7-4ee6-ba0b-dd49bcef1ee1","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.1.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9720,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, AGENT6 token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Launch Agent 6 Prime\" category. The title of the post must include the text \"Launch Agent 6 Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total AGENT6 token supply specified in [A.6.1.1.7.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](70c91853-b74b-4c6b-befb-8446f00c9691).","contentHash":"4ca59a445d30d302669d5e9e4882d57d1b049593aac2d6b52f85cc10473a654b","addressRefs":[]},"baaa8a79-a8a9-4a90-b350-83e845b52895":{"id":"baaa8a79-a8a9-4a90-b350-83e845b52895","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9721,"content":"A future iteration of the Launch Agent 6 Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis.","contentHash":"3cfc77c4bc01822eacfb4a2012b4f5763d79a98f9fbe3f3f1d9b31dbd26c3c56","addressRefs":[]},"8f6ab3a5-f915-4faf-8d3b-4cc48cd03824":{"id":"8f6ab3a5-f915-4faf-8d3b-4cc48cd03824","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9722,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment.\n\nIf the proposal is aligned, the Operational Facilitator must respond to the Forum post to announce their finding. In this Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"3d695884c752507d7f445ad3a572c67b44863196d11108fb8a300dc2e71ce3e7","addressRefs":[]},"a015eb36-9095-4112-9fe6-a75dd8a6040a":{"id":"a015eb36-9095-4112-9fe6-a75dd8a6040a","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9723,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Launch Agent 6 Artifact, the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. The poll is open for three (3) days. A poll must have at least 10% of the circulating token supply participating and must have 50% of votes in favor to be approved.","contentHash":"ce79d96ba35da26da9c4a929aa6a1aaf3143ac08af01a4acb24ef702b4cb820f","addressRefs":[]},"4328ddab-d71b-47bf-8ff7-d6f0a2e37c2f":{"id":"4328ddab-d71b-47bf-8ff7-d6f0a2e37c2f","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9724,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"6de8c6b8-2e65-4a0b-940f-c509eb0661cd":{"id":"6de8c6b8-2e65-4a0b-940f-c509eb0661cd","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.5.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9725,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"ad3c8df7-2df3-4bb3-8192-f97ba459de7b":{"id":"ad3c8df7-2df3-4bb3-8192-f97ba459de7b","doc_no":"A.6.1.1.7.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9726,"content":"The Launch Agent 6 Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"51a702f42aab7a2b3247be6e1246534bc255a3090f4168ebfc8deee80bbe6241","addressRefs":[]},"08bc46ae-a50a-499a-99be-6f3449f13bc1":{"id":"08bc46ae-a50a-499a-99be-6f3449f13bc1","doc_no":"A.6.1.1.7.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9727,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 6 Agent Artifact in non-routine conditions.","contentHash":"d9fd6b5a45e165707091d49f6b082414d1ff66d37c135962f0bb0f35ac99ac32","addressRefs":[]},"dd51cdeb-242b-4d26-8841-754079074e41":{"id":"dd51cdeb-242b-4d26-8841-754079074e41","doc_no":"A.6.1.1.7.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9728,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 6 Agent Artifact in emergency situations.","contentHash":"8d50b03444a93bf2b847165881f8a23e6d6c0fd68bf640ca3103f2a91bc862f9","addressRefs":[]},"8d2ba042-109c-4819-89c3-023e8f1c3de2":{"id":"8d2ba042-109c-4819-89c3-023e8f1c3de2","doc_no":"A.6.1.1.7.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process In Emergency Situations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9729,"content":"In an Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Launch Agent 6 Prime\" category), unless doing so would endanger Launch Agent 6 or its users.","contentHash":"c45b3596f92da2c283c6b472d54e7c44808457e794d7549cfa2109062b13c3e6","addressRefs":[]},"08286cf1-8c6f-4cd2-9898-92e4147c60e8":{"id":"08286cf1-8c6f-4cd2-9898-92e4147c60e8","doc_no":"A.6.1.1.7.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9730,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"9dbfdcc1-4908-489a-8887-a36628d0e2d6":{"id":"9dbfdcc1-4908-489a-8887-a36628d0e2d6","doc_no":"A.6.1.1.7.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9731,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"7cfd996c-2a02-412b-8d65-0efbc88a6cdf":{"id":"7cfd996c-2a02-412b-8d65-0efbc88a6cdf","doc_no":"A.6.1.1.7.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9732,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"ade379d8-2b49-49d8-8425-8060c5bba942":{"id":"ade379d8-2b49-49d8-8425-8060c5bba942","doc_no":"A.6.1.1.7.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9733,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"e8c23769-6920-4fba-aebf-3051851be0fc":{"id":"e8c23769-6920-4fba-aebf-3051851be0fc","doc_no":"A.6.1.1.7.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9734,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"9f9665de-c252-4376-91aa-103482f41152":{"id":"9f9665de-c252-4376-91aa-103482f41152","doc_no":"A.6.1.1.7.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9735,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"5b3ff28a-27e7-414c-87c7-b2d4f239ac2a":{"id":"5b3ff28a-27e7-414c-87c7-b2d4f239ac2a","doc_no":"A.6.1.1.7.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9736,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"e06d0618b6d9d95508414adce52c4cbfacfa3da5df208218e9cf54f1e0be27a0","addressRefs":[]},"40fd0acb-dd7c-4b72-a842-9024d1250f3e":{"id":"40fd0acb-dd7c-4b72-a842-9024d1250f3e","doc_no":"A.6.1.1.7.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9737,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Light Agent Primitive.","contentHash":"c393e4416e4a5cb46b1553b714a7878bc319e65257c3f54f077574337b0e6601","addressRefs":[]},"963ebcfe-f66b-4598-90fb-c8d61eb87520":{"id":"963ebcfe-f66b-4598-90fb-c8d61eb87520","doc_no":"A.6.1.1.7.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9738,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"e04cf30c-cb79-4b5c-902a-c75e6387dadb":{"id":"e04cf30c-cb79-4b5c-902a-c75e6387dadb","doc_no":"A.6.1.1.7.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9739,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"db97fdbc-5163-4b23-a6ed-e05ac62167ea":{"id":"db97fdbc-5163-4b23-a6ed-e05ac62167ea","doc_no":"A.6.1.1.7.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9740,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"0bb0c992-f0b6-463b-abff-e50d8e3689ca":{"id":"0bb0c992-f0b6-463b-abff-e50d8e3689ca","doc_no":"A.6.1.1.7.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9741,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.2.3.1.2 - Active Instances Directory](e04cf30c-cb79-4b5c-902a-c75e6387dadb), whereas failed Invocations are Archived in [A.6.1.1.7.2.2.3.1.5 - Hub Data Repository](29a0cd95-500c-45ce-b5a5-66ea10493545).","contentHash":"bae560f7f8eb9c5a925bc610cd0cb96157ead29cc8eee02a8317d5c1572285ae","addressRefs":[]},"29a0cd95-500c-45ce-b5a5-66ea10493545":{"id":"29a0cd95-500c-45ce-b5a5-66ea10493545","doc_no":"A.6.1.1.7.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9742,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"89a1c42e-611a-4239-8330-0a9003955634":{"id":"89a1c42e-611a-4239-8330-0a9003955634","doc_no":"A.6.1.1.7.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9743,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"71e93307-834d-485b-a576-cdd0490af3f5":{"id":"71e93307-834d-485b-a576-cdd0490af3f5","doc_no":"A.6.1.1.7.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9744,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"cece35ac-24aa-44e6-87fe-d9f2e0d1e68c":{"id":"cece35ac-24aa-44e6-87fe-d9f2e0d1e68c","doc_no":"A.6.1.1.7.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9745,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"a2e69b89-5ac1-43bf-8841-ecfe17ad8d84":{"id":"a2e69b89-5ac1-43bf-8841-ecfe17ad8d84","doc_no":"A.6.1.1.7.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9746,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"7f7e5c17-b539-4fff-8620-6630ef8c1285":{"id":"7f7e5c17-b539-4fff-8620-6630ef8c1285","doc_no":"A.6.1.1.7.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9747,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"328eff05-96c8-46e8-9e15-95add9638abb":{"id":"328eff05-96c8-46e8-9e15-95add9638abb","doc_no":"A.6.1.1.7.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9748,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.2.3.2 - Active Instances](a2e69b89-5ac1-43bf-8841-ecfe17ad8d84).","contentHash":"9bd490ef97350362b2c5e2633d32429d2245232936551080fab49d515f6051ed","addressRefs":[]},"539eca6a-be95-47ee-bd9d-22a031abbd86":{"id":"539eca6a-be95-47ee-bd9d-22a031abbd86","doc_no":"A.6.1.1.7.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9749,"content":"The documents herein implement the Ecosystem Upkeep Primitives for Launch Agent 6. See [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"e6623020362bb0aad2d44ff4170185ef85b6303cd8caf2bf1c6f2952947278d2","addressRefs":[]},"e30013e8-4d99-40fa-9708-ede560312786":{"id":"e30013e8-4d99-40fa-9708-ede560312786","doc_no":"A.6.1.1.7.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9750,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"6d513c3c3a0ed6ce9551585c78e4ded3ea9bf1b1c2c5591dea79df7641905336","addressRefs":[]},"1a65a542-00ef-4bb6-85ec-67c7b3127f43":{"id":"1a65a542-00ef-4bb6-85ec-67c7b3127f43","doc_no":"A.6.1.1.7.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9751,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"5f25a0c8f27504a3edb4a00870d8fa3483e1c910527f93b29cf84c598e359fcc","addressRefs":[]},"b2ddd73c-530b-4dcc-b821-371a4bb49eda":{"id":"b2ddd73c-530b-4dcc-b821-371a4bb49eda","doc_no":"A.6.1.1.7.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9752,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"a254f828-3f7c-4810-b084-13ded96a3727":{"id":"a254f828-3f7c-4810-b084-13ded96a3727","doc_no":"A.6.1.1.7.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9753,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"31065251-c40d-4298-9d8a-d9b4ef0d23f7":{"id":"31065251-c40d-4298-9d8a-d9b4ef0d23f7","doc_no":"A.6.1.1.7.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9754,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.3.1.2.1 - Single Instance Configuration Document](8cd599cd-d6f1-4ef4-86cd-94aaf842d62e).","contentHash":"2df1305c2130191c753fa36620eb278ebc3096c161c2b12ef4014bb168ed23c8","addressRefs":[]},"bade3eef-dde0-4103-814c-17b428fb7a68":{"id":"bade3eef-dde0-4103-814c-17b428fb7a68","doc_no":"A.6.1.1.7.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9755,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"7efb6642-5543-4a7a-9d4a-3dcf4b9f8a50":{"id":"7efb6642-5543-4a7a-9d4a-3dcf4b9f8a50","doc_no":"A.6.1.1.7.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9756,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"a978e8ea-067b-45f7-915a-2189a47fb035":{"id":"a978e8ea-067b-45f7-915a-2189a47fb035","doc_no":"A.6.1.1.7.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9757,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"1fe40ee6-efd4-4cdb-a5ab-cbb8ccef8bad":{"id":"1fe40ee6-efd4-4cdb-a5ab-cbb8ccef8bad","doc_no":"A.6.1.1.7.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9758,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"f92f755a-d487-4871-b126-a92c049bfdcb":{"id":"f92f755a-d487-4871-b126-a92c049bfdcb","doc_no":"A.6.1.1.7.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9759,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"bc7d3904-3cf6-4b38-9d33-46b734891bfb":{"id":"bc7d3904-3cf6-4b38-9d33-46b734891bfb","doc_no":"A.6.1.1.7.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9760,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"cd0de0c7-7970-49b0-b05a-def3e1bcab9a":{"id":"cd0de0c7-7970-49b0-b05a-def3e1bcab9a","doc_no":"A.6.1.1.7.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9761,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"8cd599cd-d6f1-4ef4-86cd-94aaf842d62e":{"id":"8cd599cd-d6f1-4ef4-86cd-94aaf842d62e","doc_no":"A.6.1.1.7.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9762,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"0b3112c5-3632-4e98-971c-8737f657ec80":{"id":"0b3112c5-3632-4e98-971c-8737f657ec80","doc_no":"A.6.1.1.7.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9763,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"0545120b-a962-479c-a35d-9e208e6fff17":{"id":"0545120b-a962-479c-a35d-9e208e6fff17","doc_no":"A.6.1.1.7.2.3.1.2.1.1.1","title":"Terms","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9764,"content":"Launch Agent 6 will pay 0.50% of its market capitalization per year in USDS.","contentHash":"90aa635e9497f56b13d2af2cd19b77b4d037bf78a722f093b87c609382cc47bb","addressRefs":[]},"65782992-194b-4f7a-af35-23dc1db7287f":{"id":"65782992-194b-4f7a-af35-23dc1db7287f","doc_no":"A.6.1.1.7.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9765,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"bea02c9f-ea6a-4d22-ab23-04f5ca6a37d0":{"id":"bea02c9f-ea6a-4d22-ab23-04f5ca6a37d0","doc_no":"A.6.1.1.7.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9766,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"9a0c543e-1846-4baf-9245-7a218bd45d3f":{"id":"9a0c543e-1846-4baf-9245-7a218bd45d3f","doc_no":"A.6.1.1.7.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9767,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"82841628-ddd7-4ccc-90c3-a45bf961d678":{"id":"82841628-ddd7-4ccc-90c3-a45bf961d678","doc_no":"A.6.1.1.7.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9768,"content":"The process to pay 0.50% of Launch Agent 6's market capitalization per year in USDS will be specified in future iterations of the Launch Agent 6 Artifact.","contentHash":"49791a40d05f128689f3b94bd52d16be60d273863c3b8d52b92a62dc189c3356","addressRefs":[]},"2b131681-dfba-4f69-b185-d512fbdf8a26":{"id":"2b131681-dfba-4f69-b185-d512fbdf8a26","doc_no":"A.6.1.1.7.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9769,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"ac8f7954-3348-4cb7-bdea-76b1dd4a294f":{"id":"ac8f7954-3348-4cb7-bdea-76b1dd4a294f","doc_no":"A.6.1.1.7.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9770,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"5909f14c-6248-4a31-b8b5-c699e1f51897":{"id":"5909f14c-6248-4a31-b8b5-c699e1f51897","doc_no":"A.6.1.1.7.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9771,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"1d31b5fd-d55c-4d8e-b554-d2d9f1e95a05":{"id":"1d31b5fd-d55c-4d8e-b554-d2d9f1e95a05","doc_no":"A.6.1.1.7.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9772,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"9e648afc-d5c5-4f2e-8026-71fede7b270b":{"id":"9e648afc-d5c5-4f2e-8026-71fede7b270b","doc_no":"A.6.1.1.7.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9773,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"e5150ceb-77a8-468c-b202-19fefcb1f95d":{"id":"e5150ceb-77a8-468c-b202-19fefcb1f95d","doc_no":"A.6.1.1.7.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9774,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"bdcaed32-e33f-4426-b059-93dfe4fc1956":{"id":"bdcaed32-e33f-4426-b059-93dfe4fc1956","doc_no":"A.6.1.1.7.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9775,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"6ef3b9a9-b6a7-45ef-aaf4-3788389d7bf3":{"id":"6ef3b9a9-b6a7-45ef-aaf4-3788389d7bf3","doc_no":"A.6.1.1.7.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9776,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"8389ea55-0cd8-4471-b940-50b9882f0924":{"id":"8389ea55-0cd8-4471-b940-50b9882f0924","doc_no":"A.6.1.1.7.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9777,"content":"The documents herein contain all data and specifications for Launch Agent 6's instance of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"31b841e0f8f0dd42a68d98a399e738bace6f4d38779fad806c7665fc3809f04b","addressRefs":[]},"9693a23e-9116-43d3-87ae-5036fa0fb4d1":{"id":"9693a23e-9116-43d3-87ae-5036fa0fb4d1","doc_no":"A.6.1.1.7.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9778,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Upkeep Rebate Primitive.","contentHash":"c8e601d05a94088ff3f75cb32f4c9c4e1c119499f13b08a5dc784f5cf16f8e1e","addressRefs":[]},"bbec58f6-cf9f-4bb9-a760-3cde09c6c153":{"id":"bbec58f6-cf9f-4bb9-a760-3cde09c6c153","doc_no":"A.6.1.1.7.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9779,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"17114b33-3010-4053-aa42-bcf3bf3ae73b":{"id":"17114b33-3010-4053-aa42-bcf3bf3ae73b","doc_no":"A.6.1.1.7.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9780,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"7c31bd54-47e2-4b66-8a6a-bca28cb4c5f9":{"id":"7c31bd54-47e2-4b66-8a6a-bca28cb4c5f9","doc_no":"A.6.1.1.7.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9781,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.3.2.2.1 - Single Instance Configuration Document](6e734cc1-a07e-42d7-afac-31ffa3cfd5dc).","contentHash":"eafb3b9b992be65ea8c9fb129c90e874f61eb9ab5ed8a5aa85760e81e5299d08","addressRefs":[]},"7882085c-54c7-468d-9693-7c03ab8c847f":{"id":"7882085c-54c7-468d-9693-7c03ab8c847f","doc_no":"A.6.1.1.7.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9782,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"6f4901f6-2170-481c-8fd9-7d7c9ef2ab6d":{"id":"6f4901f6-2170-481c-8fd9-7d7c9ef2ab6d","doc_no":"A.6.1.1.7.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9783,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"d1a41004-f2c2-4a95-9872-ba3f09778366":{"id":"d1a41004-f2c2-4a95-9872-ba3f09778366","doc_no":"A.6.1.1.7.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9784,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"02c01711-c3ca-4fdd-b8a1-660ee2c1cf23":{"id":"02c01711-c3ca-4fdd-b8a1-660ee2c1cf23","doc_no":"A.6.1.1.7.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9785,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"9f0f82e8-a49b-4ed4-ac3a-27c427a327f5":{"id":"9f0f82e8-a49b-4ed4-ac3a-27c427a327f5","doc_no":"A.6.1.1.7.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9786,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"b548b647-8c48-41cc-8d60-ad34075226bf":{"id":"b548b647-8c48-41cc-8d60-ad34075226bf","doc_no":"A.6.1.1.7.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9787,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"288c1b34-5986-4a83-abc1-56efa6af6500":{"id":"288c1b34-5986-4a83-abc1-56efa6af6500","doc_no":"A.6.1.1.7.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9788,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"6e734cc1-a07e-42d7-afac-31ffa3cfd5dc":{"id":"6e734cc1-a07e-42d7-afac-31ffa3cfd5dc","doc_no":"A.6.1.1.7.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9789,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"1c3dc285-97c5-4732-b763-2525038de133":{"id":"1c3dc285-97c5-4732-b763-2525038de133","doc_no":"A.6.1.1.7.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9790,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"2330f1de-6a7c-469e-9a2a-8706c6930d25":{"id":"2330f1de-6a7c-469e-9a2a-8706c6930d25","doc_no":"A.6.1.1.7.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9791,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"5126a10e-9036-42fc-a0f7-236df746295c":{"id":"5126a10e-9036-42fc-a0f7-236df746295c","doc_no":"A.6.1.1.7.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9792,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"a0347944-1dea-473f-acfe-a66f582d27a9":{"id":"a0347944-1dea-473f-acfe-a66f582d27a9","doc_no":"A.6.1.1.7.2.3.2.2.1.2.1.1","title":"Launch Agent 6 Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9793,"content":"Launch Agent 6 keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"b71801c8f1a2de15ada2cd593784aaf1a7ae2add9a3ed96e860b9ba40e813026","addressRefs":[]},"eac62395-4c6c-40d5-bc37-e2acf3301072":{"id":"eac62395-4c6c-40d5-bc37-e2acf3301072","doc_no":"A.6.1.1.7.2.3.2.2.1.2.1.2","title":"Launch Agent 6 Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9794,"content":"When paying Ecosystem Upkeep fees, Launch Agent 6 deducts the rebate from the fees it pays.","contentHash":"5ac1471172caeafb0cdc4b3c2f3f127feb2a7b180d7fb0dcd45896384cc7ecfd","addressRefs":[]},"e7058972-4fa4-4a85-967b-965afede3a23":{"id":"e7058972-4fa4-4a85-967b-965afede3a23","doc_no":"A.6.1.1.7.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9795,"content":"Operational GovOps reviews Launch Agent 6's calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Launch Agent 6 Prime\" category and work with Launch Agent 6 to resolve the disagreement. If Operational GovOps and Launch Agent 6 cannot resolve the disagreement, it must be escalated to Core GovOps.","contentHash":"6dc3314c00f59107b3c3bfdcd7244ba7babee0be18c9a107c1f39241ab25e1f4","addressRefs":[]},"7a5f2fbb-e524-4ca0-95bd-2f7c76fd3c3f":{"id":"7a5f2fbb-e524-4ca0-95bd-2f7c76fd3c3f","doc_no":"A.6.1.1.7.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9796,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"1192301e-a2ff-4016-b650-90e1436af97d":{"id":"1192301e-a2ff-4016-b650-90e1436af97d","doc_no":"A.6.1.1.7.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9797,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"3a02223c-f21e-4fee-8bc8-36a4cf36366a":{"id":"3a02223c-f21e-4fee-8bc8-36a4cf36366a","doc_no":"A.6.1.1.7.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9798,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"e6be574b-1a20-4fbb-8ee9-43d649be4c0d":{"id":"e6be574b-1a20-4fbb-8ee9-43d649be4c0d","doc_no":"A.6.1.1.7.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9799,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"86a4e532-848d-4363-a87d-944176a3707f":{"id":"86a4e532-848d-4363-a87d-944176a3707f","doc_no":"A.6.1.1.7.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9800,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"54f739a5-7170-4bed-aa9b-67e6b4591786":{"id":"54f739a5-7170-4bed-aa9b-67e6b4591786","doc_no":"A.6.1.1.7.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9801,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"6187f71c-8d4f-4a95-9aff-a87395f3f6b1":{"id":"6187f71c-8d4f-4a95-9aff-a87395f3f6b1","doc_no":"A.6.1.1.7.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9802,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"5ceee64b-59df-42e1-9da4-71b9f91dcb1c":{"id":"5ceee64b-59df-42e1-9da4-71b9f91dcb1c","doc_no":"A.6.1.1.7.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9803,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"58d0ebb7-7b3d-46bb-9976-de6a7fa76e2d":{"id":"58d0ebb7-7b3d-46bb-9976-de6a7fa76e2d","doc_no":"A.6.1.1.7.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9804,"content":"The documents herein implement the SkyLink Primitives for Launch Agent 6. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"4f22cdd4f64c5f166993eb88c93bf93a394a5496d47e6f970026355f9917fc24","addressRefs":[]},"f599a2d4-2527-4747-abe8-3418ca46d0de":{"id":"f599a2d4-2527-4747-abe8-3418ca46d0de","doc_no":"A.6.1.1.7.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9805,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"3b87e95726657e5bea3ba601863d2ff0ab441721c59c40aa951d4c2b547a9db7","addressRefs":[]},"3244d08e-fcb7-4685-afda-41d6b82460da":{"id":"3244d08e-fcb7-4685-afda-41d6b82460da","doc_no":"A.6.1.1.7.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9806,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Token SkyLink Primitive.","contentHash":"6d54808c5d5399bef8b9e43559687b9945b512242afa72821e35fe3d82ac512d","addressRefs":[]},"1bce4eaa-2b7e-466c-8e2c-abf9680af8ac":{"id":"1bce4eaa-2b7e-466c-8e2c-abf9680af8ac","doc_no":"A.6.1.1.7.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9807,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"5697d516-fc74-40a8-a2c7-7f00c534f3a6":{"id":"5697d516-fc74-40a8-a2c7-7f00c534f3a6","doc_no":"A.6.1.1.7.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9808,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"4df0c5d3-3273-47da-b144-de84b87600dc":{"id":"4df0c5d3-3273-47da-b144-de84b87600dc","doc_no":"A.6.1.1.7.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9809,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"7ae00ad7-11bd-428a-99c9-a787ba7d6c97":{"id":"7ae00ad7-11bd-428a-99c9-a787ba7d6c97","doc_no":"A.6.1.1.7.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9810,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.4.1.1.2 - Active Instances Directory](5697d516-fc74-40a8-a2c7-7f00c534f3a6), whereas failed Invocations are Archived in [A.6.1.1.7.2.4.1.1.5 - Hub Data Repository](dff4750a-bf17-475d-8741-049e00083d5f).","contentHash":"3918c94705788dac71b25e6bb774905aa579eca6a2166de491f95d5b8481a64e","addressRefs":[]},"dff4750a-bf17-475d-8741-049e00083d5f":{"id":"dff4750a-bf17-475d-8741-049e00083d5f","doc_no":"A.6.1.1.7.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9811,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"690d210b-0a09-448e-a691-448551f029c8":{"id":"690d210b-0a09-448e-a691-448551f029c8","doc_no":"A.6.1.1.7.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9812,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"71081f64-8e4b-46e1-9c58-b45cdceeb362":{"id":"71081f64-8e4b-46e1-9c58-b45cdceeb362","doc_no":"A.6.1.1.7.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9813,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"da4c1103-d221-4f8a-a51a-2c5601aa70cf":{"id":"da4c1103-d221-4f8a-a51a-2c5601aa70cf","doc_no":"A.6.1.1.7.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9814,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"9e0bbf6f-a71c-4db1-80a2-b3a5991a072b":{"id":"9e0bbf6f-a71c-4db1-80a2-b3a5991a072b","doc_no":"A.6.1.1.7.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9815,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"1488c64d-f8a7-4f11-8e81-b0096e50ed97":{"id":"1488c64d-f8a7-4f11-8e81-b0096e50ed97","doc_no":"A.6.1.1.7.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9816,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"5883e7cb-4e0a-4ed0-a0c9-6e3ce7564a9d":{"id":"5883e7cb-4e0a-4ed0-a0c9-6e3ce7564a9d","doc_no":"A.6.1.1.7.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9817,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.4.1.2 - Active Instances](9e0bbf6f-a71c-4db1-80a2-b3a5991a072b).","contentHash":"c79f2f3271a765c8d386750db3ef66b52975c832791f38f72692eee5af0bbae4","addressRefs":[]},"a0f8bc2e-4ac4-4335-8fd1-37132c875baf":{"id":"a0f8bc2e-4ac4-4335-8fd1-37132c875baf","doc_no":"A.6.1.1.7.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9818,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Launch Agent 6. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"decae57d9ee5422a62a97bdfa1169069e8f27056b62ac219b8766f2fdac9c42a","addressRefs":[]},"10fdd41c-61e5-42fa-96b9-97f268f46902":{"id":"10fdd41c-61e5-42fa-96b9-97f268f46902","doc_no":"A.6.1.1.7.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9819,"content":"The documents herein contain all data and specifications for Launch Agent 6's instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"ba4951b2c6212c5848b6e0a8887724be24a6b4bc1a9e215dbaecd66b9f04eb09","addressRefs":[]},"f3db2774-0ec3-4efd-9da8-0fa6d0fe609b":{"id":"f3db2774-0ec3-4efd-9da8-0fa6d0fe609b","doc_no":"A.6.1.1.7.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9820,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Distribution Reward Primitive.","contentHash":"1731db1f180aa79bf497b186968344795213724cc2f44b0daf912cbac899c6fd","addressRefs":[]},"d4cef458-3331-464c-9352-f36704aaecff":{"id":"d4cef458-3331-464c-9352-f36704aaecff","doc_no":"A.6.1.1.7.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9821,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"ef465153-3408-49f2-8b39-761c445e7a8a":{"id":"ef465153-3408-49f2-8b39-761c445e7a8a","doc_no":"A.6.1.1.7.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9822,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"d495c6cf-095e-4257-b54a-59139110bd3e":{"id":"d495c6cf-095e-4257-b54a-59139110bd3e","doc_no":"A.6.1.1.7.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9823,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"ab0d6db3-879d-4bc3-b099-89810a10877c":{"id":"ab0d6db3-879d-4bc3-b099-89810a10877c","doc_no":"A.6.1.1.7.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9824,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.5.1.1.2 - Active Instances Directory](ef465153-3408-49f2-8b39-761c445e7a8a), whereas failed Invocations are Archived in [A.6.1.1.7.2.5.1.1.5 - Hub Data Repository](aad36c3f-431d-4a1d-942b-a583805618c1).","contentHash":"e7be356c351bc28aa70ba338667a2f1278704f08e8737ff209457d36ffeeab3c","addressRefs":[]},"aad36c3f-431d-4a1d-942b-a583805618c1":{"id":"aad36c3f-431d-4a1d-942b-a583805618c1","doc_no":"A.6.1.1.7.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9825,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"18514778-d22b-43bc-ad19-ebb7403e02a5":{"id":"18514778-d22b-43bc-ad19-ebb7403e02a5","doc_no":"A.6.1.1.7.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9826,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"fdfc3679-50ad-4c3e-bcae-e69df4c6d6b2":{"id":"fdfc3679-50ad-4c3e-bcae-e69df4c6d6b2","doc_no":"A.6.1.1.7.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9827,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"ecb8493a-5c44-4619-8f5a-e36327c797e8":{"id":"ecb8493a-5c44-4619-8f5a-e36327c797e8","doc_no":"A.6.1.1.7.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9828,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"464695e4-744c-48fd-a023-565096dc9144":{"id":"464695e4-744c-48fd-a023-565096dc9144","doc_no":"A.6.1.1.7.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9829,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"4e7b84d1-356c-437a-9aa2-3a569c0c29ab":{"id":"4e7b84d1-356c-437a-9aa2-3a569c0c29ab","doc_no":"A.6.1.1.7.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9830,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"ef23d204-14e2-4576-bca3-8bceca7b1c63":{"id":"ef23d204-14e2-4576-bca3-8bceca7b1c63","doc_no":"A.6.1.1.7.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9831,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.5.1.2 - Active Instances](464695e4-744c-48fd-a023-565096dc9144).","contentHash":"748799713c6a17fd94de6a429afe4529429e164bd9d9d8d6e04542e09f3125d0","addressRefs":[]},"937c895e-2569-46d3-8de0-8ed716e11b09":{"id":"937c895e-2569-46d3-8de0-8ed716e11b09","doc_no":"A.6.1.1.7.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9832,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"c132d5d35c9ecccc68d0465b40c050ead626dcba62bf7a464039f1edd6b73484","addressRefs":[]},"60d8973d-b5e0-4dc3-ae21-edfda998bc42":{"id":"60d8973d-b5e0-4dc3-ae21-edfda998bc42","doc_no":"A.6.1.1.7.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9833,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Integration Boost Primitive.","contentHash":"b7072a7dd8be3d6681452428675c1e8cd60500ca32900402f682c0df3bd5bca0","addressRefs":[]},"bafcd161-a5d8-4498-8502-cf71deffd0ee":{"id":"bafcd161-a5d8-4498-8502-cf71deffd0ee","doc_no":"A.6.1.1.7.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9834,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"cdbc02f2-7ec8-4ae4-b027-8938f0824864":{"id":"cdbc02f2-7ec8-4ae4-b027-8938f0824864","doc_no":"A.6.1.1.7.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9835,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"c915735d-8347-433e-bc47-6f94a41e8689":{"id":"c915735d-8347-433e-bc47-6f94a41e8689","doc_no":"A.6.1.1.7.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9836,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"bd14164c-8c4f-4d7d-99f4-da281221288a":{"id":"bd14164c-8c4f-4d7d-99f4-da281221288a","doc_no":"A.6.1.1.7.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9837,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.5.2.1.2 - Active Instances Directory](cdbc02f2-7ec8-4ae4-b027-8938f0824864), whereas failed Invocations are Archived in [A.6.1.1.7.2.5.2.1.5 - Hub Data Repository](ed0542a2-e910-4caa-9d1a-e96381aed48d).","contentHash":"a9a9a0418ceb615556be46a045c239401dc2899142e6c833a8eb41228b19c895","addressRefs":[]},"ed0542a2-e910-4caa-9d1a-e96381aed48d":{"id":"ed0542a2-e910-4caa-9d1a-e96381aed48d","doc_no":"A.6.1.1.7.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9838,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"0af68d0c-c6fc-43cd-aed5-5b889110d25a":{"id":"0af68d0c-c6fc-43cd-aed5-5b889110d25a","doc_no":"A.6.1.1.7.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9839,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"9ad5e114-dd9f-4caf-a255-d830011c784d":{"id":"9ad5e114-dd9f-4caf-a255-d830011c784d","doc_no":"A.6.1.1.7.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9840,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"101f1885-e1ba-49f8-93f8-2c7d45288d2c":{"id":"101f1885-e1ba-49f8-93f8-2c7d45288d2c","doc_no":"A.6.1.1.7.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9841,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"2628525c-6956-49dd-9a48-e3de403a0597":{"id":"2628525c-6956-49dd-9a48-e3de403a0597","doc_no":"A.6.1.1.7.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9842,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"0d520de1-d730-427f-95bd-2ed92b80512d":{"id":"0d520de1-d730-427f-95bd-2ed92b80512d","doc_no":"A.6.1.1.7.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9843,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"b86632f7-9311-4313-956f-dd502be7480c":{"id":"b86632f7-9311-4313-956f-dd502be7480c","doc_no":"A.6.1.1.7.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9844,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.5.2.2 - Active Instances](2628525c-6956-49dd-9a48-e3de403a0597).","contentHash":"82b3f208ffeb581a97fd2dac7b39c9a419d70d6b49da94f91b13fb9f3432367a","addressRefs":[]},"ad535f1f-c7f0-4cd8-aca0-5a447dc2622b":{"id":"ad535f1f-c7f0-4cd8-aca0-5a447dc2622b","doc_no":"A.6.1.1.7.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9845,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"541a45cdb952d250a796f9bac635275dac66e5a4abb192f61d5610a487f11e4b","addressRefs":[]},"92023efc-2ee6-4f98-9750-574f90e21184":{"id":"92023efc-2ee6-4f98-9750-574f90e21184","doc_no":"A.6.1.1.7.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9846,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Pioneer Chain Primitive.","contentHash":"4adf49d67dc6f469fe968f39f8175746cf7adfd759c3bc9cf64ade4720d25e4d","addressRefs":[]},"e33acbf0-cf13-4e74-acb0-23319b551d42":{"id":"e33acbf0-cf13-4e74-acb0-23319b551d42","doc_no":"A.6.1.1.7.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9847,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"04a6899a-8b0c-4b3d-873a-69325cc5bf50":{"id":"04a6899a-8b0c-4b3d-873a-69325cc5bf50","doc_no":"A.6.1.1.7.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9848,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"04ba9c33-02e3-44e1-a003-9b9ca96bcdb2":{"id":"04ba9c33-02e3-44e1-a003-9b9ca96bcdb2","doc_no":"A.6.1.1.7.2.5.3.1.2.1","title":"Plasma Instance Configuration Document Location","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9849,"content":"This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.5.3.2.1 - Plasma Instance Configuration Document](eb40fb85-194c-4bae-a0c4-24c66df4735e).","contentHash":"a83786e516f77978ceaf5a0246ed710c86e8464efe8d20744cf0db66e88c87ce","addressRefs":[]},"0e7ab6cf-3e07-4f0d-9294-802072d07a4e":{"id":"0e7ab6cf-3e07-4f0d-9294-802072d07a4e","doc_no":"A.6.1.1.7.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9850,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"ce54fef7-9758-4c98-8e3f-bed68ff82f73":{"id":"ce54fef7-9758-4c98-8e3f-bed68ff82f73","doc_no":"A.6.1.1.7.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9851,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.5.3.1.2 - Active Instances Directory](04a6899a-8b0c-4b3d-873a-69325cc5bf50), whereas failed Invocations are Archived in [A.6.1.1.7.2.5.3.1.5 - Hub Data Repository](5cd1f6cd-7349-429d-9f3d-42aaca039b69).","contentHash":"d6e8da094ba33a77c1ac08fc08f6cefcdf162190d7c9286d629df072bafd0008","addressRefs":[]},"5cd1f6cd-7349-429d-9f3d-42aaca039b69":{"id":"5cd1f6cd-7349-429d-9f3d-42aaca039b69","doc_no":"A.6.1.1.7.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9852,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"2c6db399-c525-49bd-b020-4761a50ce837":{"id":"2c6db399-c525-49bd-b020-4761a50ce837","doc_no":"A.6.1.1.7.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9853,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"c31b6835-60e8-445d-94f6-924b1d81d5ed":{"id":"c31b6835-60e8-445d-94f6-924b1d81d5ed","doc_no":"A.6.1.1.7.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9854,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"7415359b-8d19-4607-9054-30258781eb51":{"id":"7415359b-8d19-4607-9054-30258781eb51","doc_no":"A.6.1.1.7.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9855,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"1cf22b6c-83d7-4ddf-8b4c-13059f4ec555":{"id":"1cf22b6c-83d7-4ddf-8b4c-13059f4ec555","doc_no":"A.6.1.1.7.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9856,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"eb40fb85-194c-4bae-a0c4-24c66df4735e":{"id":"eb40fb85-194c-4bae-a0c4-24c66df4735e","doc_no":"A.6.1.1.7.2.5.3.2.1","title":"Plasma Instance Configuration Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9857,"content":"The documents herein contain the Instance Configuration Document for the Plasma Instance of the Pioneer Chain Primitive.","contentHash":"ecd15d68c9c1f5c399119519ec3dd4dadd0a56b625ef72c84a26ba11b7e25e09","addressRefs":[]},"3f22028a-59e5-470c-b5bf-80226706d085":{"id":"3f22028a-59e5-470c-b5bf-80226706d085","doc_no":"A.6.1.1.7.2.5.3.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9858,"content":"The documents herein define the parameters of the Plasma Instance of the Pioneer Chain Primitive.","contentHash":"b8ff75cde268a7ef260559d53178e011467f9a35ee1e2834f6e900a70dfda91a","addressRefs":[]},"96f5ca50-30db-43ca-aa03-ba7b88835db5":{"id":"96f5ca50-30db-43ca-aa03-ba7b88835db5","doc_no":"A.6.1.1.7.2.5.3.2.1.1.1","title":"Instance Identifiers","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9859,"content":"The documents herein define the Instance identifiers.","contentHash":"f1e512a5a5ade51b88cb0f3fa9f4a0875fde27530e9bd6c0b8dca572b1e7ca20","addressRefs":[]},"774ad565-8ee2-4abc-87d6-390ee470b18b":{"id":"774ad565-8ee2-4abc-87d6-390ee470b18b","doc_no":"A.6.1.1.7.2.5.3.2.1.1.1.1","title":"Network","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9860,"content":"Plasma","contentHash":"303b32029c7f0a2560b1e12e8910bcbbff0d93a706a160bf7bf9353b13282b02","addressRefs":[]},"3e96125b-ce79-4639-86a7-d22db2ee801e":{"id":"3e96125b-ce79-4639-86a7-d22db2ee801e","doc_no":"A.6.1.1.7.2.5.3.2.1.1.2","title":"Pioneer Incentive Pool","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9861,"content":"The documents herein contain the terms that govern this Instance's Pioneer Incentive Pool and its address.","contentHash":"86b4489c5004a1a438ede266ddea17e1cee462ce29ad0e5a170e27f337fc0923","addressRefs":[]},"dd6dfbb0-c7fc-45be-ad2c-aeca560eb644":{"id":"dd6dfbb0-c7fc-45be-ad2c-aeca560eb644","doc_no":"A.6.1.1.7.2.5.3.2.1.1.2.1","title":"Address","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9862,"content":"The address of Launch Agent 6's Pioneer Incentive Pool is Launch Agent 6's SubProxy Account on the Ethereum Mainnet: `0x24fdcd3bFA5C2553e05B2f9AD0365EBC296278D3`.","contentHash":"38ba50a3b28adcc31a5fd9c2bd082fe9aafa7e139de0587acbb912ca91fb7f23","addressRefs":["0x24fdcd3bfa5c2553e05b2f9ad0365ebc296278d3"]},"60702f4c-cbfe-416f-aab9-f8097fbca47a":{"id":"60702f4c-cbfe-416f-aab9-f8097fbca47a","doc_no":"A.6.1.1.7.2.5.3.2.1.1.2.2","title":"Terms","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9863,"content":"The Pioneer Incentive Pool for this Instance is governed by the terms specified in [A.2.2.8.3.1.4 - Pioneer Incentive Pool](04edac33-19d5-4a87-a8ab-945a0cd57771).","contentHash":"398f45540512dcf7575840dc803f208433c4e3a0be43346a3f6eeb92e954d7d8","addressRefs":[]},"5127e898-68b8-4ae5-8a7f-92202a9d2553":{"id":"5127e898-68b8-4ae5-8a7f-92202a9d2553","doc_no":"A.6.1.1.7.2.5.3.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9864,"content":"The documents herein define the process for the ongoing management of the Plasma Instance of the Pioneer Chain Primitive.","contentHash":"55b74e87994090e0e561b1dcd9c923b9082cb642dc85a7f6e690fc3b37fd3b61","addressRefs":[]},"652f040b-29ed-4578-a502-e8fe037bb436":{"id":"652f040b-29ed-4578-a502-e8fe037bb436","doc_no":"A.6.1.1.7.2.5.3.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9865,"content":"The documents herein contain data relevant to the Plasma Instance of the Pioneer Chain Primitive.","contentHash":"7a4a321703d1a725fe6ecb8ebd212bcaf374299bcb067633a8c3927b81a9b6fe","addressRefs":[]},"472618e9-29c6-406e-928d-d79dff4b9722":{"id":"472618e9-29c6-406e-928d-d79dff4b9722","doc_no":"A.6.1.1.7.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9866,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"990419d2-5061-4d9a-97b7-00a7b9e7a86c":{"id":"990419d2-5061-4d9a-97b7-00a7b9e7a86c","doc_no":"A.6.1.1.7.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9867,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.5.3.2 - Active Instances](1cf22b6c-83d7-4ddf-8b4c-13059f4ec555).","contentHash":"35ddb3b4cacad463a0f133bf96a2e9a2dde77669c10faa2eb80a62062b23f3e7","addressRefs":[]},"f37cc62c-9e14-40b2-9cb7-b78add3111b4":{"id":"f37cc62c-9e14-40b2-9cb7-b78add3111b4","doc_no":"A.6.1.1.7.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9868,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Launch Agent 6. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"57b86a45a6f393d0815bb160b26a730c089dc88473f8f4c0e8a26cb0d7da5f8b","addressRefs":[]},"d3d385ed-e53b-4b3f-be9f-4cbeee3420b4":{"id":"d3d385ed-e53b-4b3f-be9f-4cbeee3420b4","doc_no":"A.6.1.1.7.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9869,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Allocation System Primitive. See [A.2.2.9.1 - Allocation System Primitive](9db14ab7-bb4b-4751-8084-843bd4359f2a).","contentHash":"71d02bc5a80140813a039ef7ed56bf5df43492cf63c79bb10d04f5c8ba6be37d","addressRefs":[]},"8a97ce72-1505-4301-a647-e3b28c839bf8":{"id":"8a97ce72-1505-4301-a647-e3b28c839bf8","doc_no":"A.6.1.1.7.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9870,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Allocation System Primitive.","contentHash":"0205fae47bfdff497f10307287ed13dd300b94a2f45497abb0ad2253af6b1016","addressRefs":[]},"8b0c94e2-0489-463b-bb9b-d1571d7240e6":{"id":"8b0c94e2-0489-463b-bb9b-d1571d7240e6","doc_no":"A.6.1.1.7.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9871,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"57de5036-2c56-4cb6-b1dd-8e2dc1b214f6":{"id":"57de5036-2c56-4cb6-b1dd-8e2dc1b214f6","doc_no":"A.6.1.1.7.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9872,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"4c12626b-272a-4886-b7af-c6968b021fc2":{"id":"4c12626b-272a-4886-b7af-c6968b021fc2","doc_no":"A.6.1.1.7.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9873,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"759c5f6a-7c13-466f-9130-0801575b0145":{"id":"759c5f6a-7c13-466f-9130-0801575b0145","doc_no":"A.6.1.1.7.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9874,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.6.1.1.2 - Active Instances Directory](57de5036-2c56-4cb6-b1dd-8e2dc1b214f6), whereas failed Invocations are Archived in [A.6.1.1.7.2.6.1.1.5 - Hub Data Repository](7936954e-cfc9-4491-9432-842450e86af3).","contentHash":"5b81eadc0c6a7f1429cca959f4e7aed501a9a27b354c2904f50081b4f5459b42","addressRefs":[]},"7936954e-cfc9-4491-9432-842450e86af3":{"id":"7936954e-cfc9-4491-9432-842450e86af3","doc_no":"A.6.1.1.7.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9875,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"3db6fb6f-37fd-4872-a427-38d811af0192":{"id":"3db6fb6f-37fd-4872-a427-38d811af0192","doc_no":"A.6.1.1.7.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9876,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"1651e4eb-66a7-4f72-b7ad-27b34786bc02":{"id":"1651e4eb-66a7-4f72-b7ad-27b34786bc02","doc_no":"A.6.1.1.7.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9877,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"4109cac5-0f83-4274-8061-fb55d4ef1df7":{"id":"4109cac5-0f83-4274-8061-fb55d4ef1df7","doc_no":"A.6.1.1.7.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9878,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"f9501c81-b5cd-4c07-b781-539974d39f1d":{"id":"f9501c81-b5cd-4c07-b781-539974d39f1d","doc_no":"A.6.1.1.7.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9879,"content":"The documents herein provide general specifications of the Launch Agent 6 Liquidity Layer and define Launch Agent 6's overarching strategy and operational framework for managing across all Instances.","contentHash":"fe1af37df4a20c977231c70394a928e0551485038a9422bc9eedb08e45ec2827","addressRefs":[]},"38996719-e2ff-491b-89b4-c63fcbaf5353":{"id":"38996719-e2ff-491b-89b4-c63fcbaf5353","doc_no":"A.6.1.1.7.2.6.1.2.1","title":"General Specifications","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9880,"content":"The documents herein contain general specifications for the Launch Agent 6 Liquidity Layer.","contentHash":"ec77d1df8bc0dd2cab6ee4141f0f994bf4602114d92544b79d0aa1ed4192ca85","addressRefs":[]},"e8f3afd5-d1a8-4379-826c-2c3bcc365947":{"id":"e8f3afd5-d1a8-4379-826c-2c3bcc365947","doc_no":"A.6.1.1.7.2.6.1.2.1.1","title":"Launch Agent 6 Liquidity Layer Architecture","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9881,"content":"The documents herein describe the high-level design of the Launch Agent 6 Liquidity Layer, including its key smart contracts and their functionality.","contentHash":"3d0b10090c6fda8ca1ef75d1dfb0ab9c7e67d160ca3f14186ee611464d12c064","addressRefs":[]},"4148f5dc-ec79-4e4e-96ea-debf17e8bc28":{"id":"4148f5dc-ec79-4e4e-96ea-debf17e8bc28","doc_no":"A.6.1.1.7.2.6.1.2.1.1.1","title":"Launch Agent 6 Liquidity Layer Addresses","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9882,"content":"The subdocuments herein provide the addresses of the Launch Agent 6 Liquidity Layer's constituent contracts.","contentHash":"e3d0e514fd87fbc77881b82060f0998653bb5cc172d83b1fc762335e791120d1","addressRefs":[]},"22f84daa-f402-433d-8bd2-4a03b5776e20":{"id":"22f84daa-f402-433d-8bd2-4a03b5776e20","doc_no":"A.6.1.1.7.2.6.1.2.1.1.1.1","title":"Allocator Contract Addresses","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9883,"content":"The documents herein contain global key addresses for the Allocator Contracts.","contentHash":"a99119eb26b8e6fbaae81a45fa911afc0af3344a9ea2bbcb90fc7cf9bd94fe9c","addressRefs":[]},"451328dd-17f0-4efd-8515-377ce6a138b6":{"id":"451328dd-17f0-4efd-8515-377ce6a138b6","doc_no":"A.6.1.1.7.2.6.1.2.1.1.1.1.1","title":"Ethereum Mainnet","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9884,"content":"The documents herein contain the Allocator Contract Addresses on the Ethereum Mainnet.","contentHash":"084c1a1c5fbe0a4abc17b09c0096038edfd2c77bdd298abb5411775b166695ef","addressRefs":[]},"7f40e7d1-ed33-4b31-8641-d721f1dc2f01":{"id":"7f40e7d1-ed33-4b31-8641-d721f1dc2f01","doc_no":"A.6.1.1.7.2.6.1.2.1.1.1.1.1.1","title":"Allocator Buffer Contract","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9885,"content":"The address of the ALLOCATOR_BUFFER contract is: `0xD0BB61b34771146e31055f20f329cDf97429F889`.","contentHash":"aef5baf1e24d04632a8be68ffec0b0ac5e694c65db7dc6595c7a8774bc8d2798","addressRefs":["0xd0bb61b34771146e31055f20f329cdf97429f889"]},"0562eb6d-3770-4c3c-851b-7a6f9f5b2aa0":{"id":"0562eb6d-3770-4c3c-851b-7a6f9f5b2aa0","doc_no":"A.6.1.1.7.2.6.1.2.1.1.1.1.1.2","title":"Allocator Vault Contract","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9886,"content":"The address of the ALLOCATOR_VAULT (ALLOCATOR-PRYSM-A) contract is: `0x146181Aa9B362EaEC2eC3aDd7429a06D53B43d1a`.","contentHash":"7b4c7c1ad16867243623cb241fa1e18486fabb4bca664808d3d0ce2b91b6d47d","addressRefs":["0x146181aa9b362eaec2ec3add7429a06d53b43d1a"]},"6f8a8e14-13be-4893-9bb1-17c88e984426":{"id":"6f8a8e14-13be-4893-9bb1-17c88e984426","doc_no":"A.6.1.1.7.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9887,"content":"The Instances of the Allocation System Primitive with `Active` Status are stored herein.","contentHash":"1ec0e728a9f82ad97fb8eeaf6a1959350595219b9f7cf894e7fe0704248213a2","addressRefs":[]},"1292a07b-637f-4b35-adc1-1a9bdeee9566":{"id":"1292a07b-637f-4b35-adc1-1a9bdeee9566","doc_no":"A.6.1.1.7.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9888,"content":"The Instances of the Allocation System Primitive with `Completed` Status are stored herein.","contentHash":"5e8b303421b8ddbbe094a65ed1a012a162ef23442d0be75ad055b30f78fb3af7","addressRefs":[]},"475822f8-5a16-48e3-8228-85785657b2ac":{"id":"475822f8-5a16-48e3-8228-85785657b2ac","doc_no":"A.6.1.1.7.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9889,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.6.1.3 - Active Instances](6f8a8e14-13be-4893-9bb1-17c88e984426).","contentHash":"77d056e2fd078ec609ea96da2145abd2e8db6a499c8c90fde8d012b2ff571a9b","addressRefs":[]},"8faea57c-348a-4d40-b241-868d5dbc8008":{"id":"8faea57c-348a-4d40-b241-868d5dbc8008","doc_no":"A.6.1.1.7.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9890,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"61e240f18cc01aea10baf771b9e520c7c55b7e5625252fc8871c58d77daf5b88","addressRefs":[]},"16f4cc5c-09ce-4ccd-be18-5a9a333e99d7":{"id":"16f4cc5c-09ce-4ccd-be18-5a9a333e99d7","doc_no":"A.6.1.1.7.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9891,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Junior Risk Capital Rental Primitive.","contentHash":"052bdd516d25e6029eef373fda200fd62bc7912d5487059d705eafbe031e85fa","addressRefs":[]},"a1047457-ad33-4d0c-8b60-fa67f3ab57e6":{"id":"a1047457-ad33-4d0c-8b60-fa67f3ab57e6","doc_no":"A.6.1.1.7.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9892,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"997d4b26-65c5-4ad3-bbde-3441df9491ff":{"id":"997d4b26-65c5-4ad3-bbde-3441df9491ff","doc_no":"A.6.1.1.7.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9893,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"51b0d96c-ca4c-4a89-8a95-41987d7b6ab7":{"id":"51b0d96c-ca4c-4a89-8a95-41987d7b6ab7","doc_no":"A.6.1.1.7.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9894,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"f72ba911-8c52-402e-a462-e69c13098d34":{"id":"f72ba911-8c52-402e-a462-e69c13098d34","doc_no":"A.6.1.1.7.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9895,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.6.2.1.2 - Active Instances Directory](997d4b26-65c5-4ad3-bbde-3441df9491ff), whereas failed Invocations are Archived in [A.6.1.1.7.2.6.2.1.5 - Hub Data Repository](2c163402-c55f-4995-8866-a0074ff01df6).","contentHash":"9636b9799e30105336fb4e50d8770b4a7b9f324bfcec15c5ff6c8819a96156ad","addressRefs":[]},"2c163402-c55f-4995-8866-a0074ff01df6":{"id":"2c163402-c55f-4995-8866-a0074ff01df6","doc_no":"A.6.1.1.7.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9896,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"a86f03fe-0570-4031-b616-3c1a3f03a65d":{"id":"a86f03fe-0570-4031-b616-3c1a3f03a65d","doc_no":"A.6.1.1.7.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9897,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"4cb29356-93cd-418b-af94-7690a20b3883":{"id":"4cb29356-93cd-418b-af94-7690a20b3883","doc_no":"A.6.1.1.7.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9898,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"4eecf3be-1cc1-4981-95d3-e96bc553652b":{"id":"4eecf3be-1cc1-4981-95d3-e96bc553652b","doc_no":"A.6.1.1.7.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9899,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"d48fecab-0528-4d96-b760-49ca8568be85":{"id":"d48fecab-0528-4d96-b760-49ca8568be85","doc_no":"A.6.1.1.7.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9900,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"32d1da62-94e0-4881-95cc-434c65aca77b":{"id":"32d1da62-94e0-4881-95cc-434c65aca77b","doc_no":"A.6.1.1.7.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9901,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"d55dafa1-0e6c-4e2a-9cfe-bcac3ccaa6ac":{"id":"d55dafa1-0e6c-4e2a-9cfe-bcac3ccaa6ac","doc_no":"A.6.1.1.7.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9902,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.6.2.2 - Active Instances](d48fecab-0528-4d96-b760-49ca8568be85).","contentHash":"e1b3d3996af2560649d93126884a37da6bc6f718be9770626246e75c6c049e4e","addressRefs":[]},"da849319-df3c-4b3b-a100-157828990761":{"id":"da849319-df3c-4b3b-a100-157828990761","doc_no":"A.6.1.1.7.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9903,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"63faac088748f93a60228bbbde06065f6fc8b7bc515dfcafec4bf49649e34b38","addressRefs":[]},"612c1dde-b718-4d81-8a0c-ce9ed6c018f7":{"id":"612c1dde-b718-4d81-8a0c-ce9ed6c018f7","doc_no":"A.6.1.1.7.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9904,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Asset Liability Management Rental Primitive.","contentHash":"71c691a342efff406927a809c0ef523ad40ce258df9043159d4e26d1f78888ba","addressRefs":[]},"24c6a8ba-280e-468e-be34-6c497220850e":{"id":"24c6a8ba-280e-468e-be34-6c497220850e","doc_no":"A.6.1.1.7.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9905,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"f6266454-9845-44e8-a079-851ddd576e8f":{"id":"f6266454-9845-44e8-a079-851ddd576e8f","doc_no":"A.6.1.1.7.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9906,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"9b68a034-5b97-49fd-9c05-8fdc0a6b8fcf":{"id":"9b68a034-5b97-49fd-9c05-8fdc0a6b8fcf","doc_no":"A.6.1.1.7.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9907,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"b78c2547-cfe5-414f-97f6-af9e763c6721":{"id":"b78c2547-cfe5-414f-97f6-af9e763c6721","doc_no":"A.6.1.1.7.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9908,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.6.3.1.2 - Active Instances Directory](f6266454-9845-44e8-a079-851ddd576e8f), whereas failed Invocations are Archived in [A.6.1.1.7.2.6.3.1.5 - Hub Data Repository](50250f92-7f80-4685-b94d-f1ed639c9c98).","contentHash":"cf73a16a297d20ff5f9b0a3e9015a9e91f5f86f4defe8c373ccabcf4cdc7f14f","addressRefs":[]},"50250f92-7f80-4685-b94d-f1ed639c9c98":{"id":"50250f92-7f80-4685-b94d-f1ed639c9c98","doc_no":"A.6.1.1.7.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9909,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ead9dc67-a5aa-49b1-a9fb-cbed7ede94e5":{"id":"ead9dc67-a5aa-49b1-a9fb-cbed7ede94e5","doc_no":"A.6.1.1.7.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9910,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"fa04da99-79a6-46de-b1bc-160d0ea4e700":{"id":"fa04da99-79a6-46de-b1bc-160d0ea4e700","doc_no":"A.6.1.1.7.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9911,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"dc49f561-dade-4b78-bffc-efbc533ab6b9":{"id":"dc49f561-dade-4b78-bffc-efbc533ab6b9","doc_no":"A.6.1.1.7.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9912,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"d5f275e5-98b9-4ef7-90dd-f81e786252df":{"id":"d5f275e5-98b9-4ef7-90dd-f81e786252df","doc_no":"A.6.1.1.7.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9913,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"22b7c4eb-a8e0-4e56-a4ca-590fe8eed182":{"id":"22b7c4eb-a8e0-4e56-a4ca-590fe8eed182","doc_no":"A.6.1.1.7.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9914,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"9dabbad7-776e-4801-89a3-669341dbb30d":{"id":"9dabbad7-776e-4801-89a3-669341dbb30d","doc_no":"A.6.1.1.7.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9915,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.6.3.2 - Active Instances](d5f275e5-98b9-4ef7-90dd-f81e786252df).","contentHash":"8dffb41b1d1431cee6aafe8a28fe420bcfbc5f67b435915b575d655a662b99cf","addressRefs":[]},"19c086d0-420a-4c29-b0ac-8d8dec444ce5":{"id":"19c086d0-420a-4c29-b0ac-8d8dec444ce5","doc_no":"A.6.1.1.7.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9916,"content":"The documents herein implement the Core Governance Primitives for Launch Agent 6. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"0bda108758c838914cbc6db11bb561eb6d82fbf4773f5d032ea47dc2cbaeec48","addressRefs":[]},"d4e3b585-bb39-41d7-af60-3a65204e1917":{"id":"d4e3b585-bb39-41d7-af60-3a65204e1917","doc_no":"A.6.1.1.7.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9917,"content":"The documents herein contain all data and specifications for Launch Agent 6's Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"12825cfbfd933e421259aa8b51e90917392e24a2c59732f1d9c5756d2fb9caa0","addressRefs":[]},"095b3dfe-4ea4-4ce3-8a7d-e9253269e096":{"id":"095b3dfe-4ea4-4ce3-8a7d-e9253269e096","doc_no":"A.6.1.1.7.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9918,"content":"The documents herein organize all base information relevant to Launch Agent 6's usage of the Core Governance Reward Primitive.","contentHash":"0e0d62569bd70d3af622abe5b59fd751ffb711ee5511759d5fe9ef2dd25ee025","addressRefs":[]},"eea5262e-a1ba-4394-8769-e5098dc7aff6":{"id":"eea5262e-a1ba-4394-8769-e5098dc7aff6","doc_no":"A.6.1.1.7.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9919,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"3269b582-af99-475b-b3e2-9d25a079c5ec":{"id":"3269b582-af99-475b-b3e2-9d25a079c5ec","doc_no":"A.6.1.1.7.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9920,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"db2f0051-f5a0-4392-845d-1b44213299bc":{"id":"db2f0051-f5a0-4392-845d-1b44213299bc","doc_no":"A.6.1.1.7.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9921,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"a108020b-3cbf-493d-8407-5570c36b14e7":{"id":"a108020b-3cbf-493d-8407-5570c36b14e7","doc_no":"A.6.1.1.7.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9922,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.7.1.1.2 - Active Instances Directory](3269b582-af99-475b-b3e2-9d25a079c5ec), whereas failed Invocations are Archived in [A.6.1.1.7.2.7.1.1.5 - Hub Data Repository](5b09155b-063c-41c0-b714-4a5d275d7b57).","contentHash":"108e8892999a1ee1a7df01d33e7b40626998ad166a57623e62afbd21e7dbadcb","addressRefs":[]},"5b09155b-063c-41c0-b714-4a5d275d7b57":{"id":"5b09155b-063c-41c0-b714-4a5d275d7b57","doc_no":"A.6.1.1.7.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9923,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"8039d41b-466d-42e0-aa67-27fb7a686a1f":{"id":"8039d41b-466d-42e0-aa67-27fb7a686a1f","doc_no":"A.6.1.1.7.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9924,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"146d622f-f1e3-475c-8a59-b433143c9fbd":{"id":"146d622f-f1e3-475c-8a59-b433143c9fbd","doc_no":"A.6.1.1.7.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9925,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"e1922587-e2a8-4ec3-81a8-a325bbe73e18":{"id":"e1922587-e2a8-4ec3-81a8-a325bbe73e18","doc_no":"A.6.1.1.7.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9926,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"b4954eea-0108-4820-bdbf-402e74ea1407":{"id":"b4954eea-0108-4820-bdbf-402e74ea1407","doc_no":"A.6.1.1.7.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9927,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"06c9df0b-903a-4d24-8906-fb3f7ceec0d0":{"id":"06c9df0b-903a-4d24-8906-fb3f7ceec0d0","doc_no":"A.6.1.1.7.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9928,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"857ab3e5-af7a-4e23-9c1d-0621b8d626a8":{"id":"857ab3e5-af7a-4e23-9c1d-0621b8d626a8","doc_no":"A.6.1.1.7.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"0d6f6016-eaf1-47e2-b8e7-98bf5e4f1dc0","order":9929,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.7.1.2 - Active Instances](b4954eea-0108-4820-bdbf-402e74ea1407).","contentHash":"aade024fd041a663d69891981a489c504d9ec73cf779da2d7a79282a512707f7","addressRefs":[]},"5e85bc90-de8f-43ab-80ea-4d7657f315a4":{"id":"5e85bc90-de8f-43ab-80ea-4d7657f315a4","doc_no":"A.6.1.1.7.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"eba0dcc7-e135-496f-b866-342deeb91dc4","order":9930,"content":"The documents herein define Launch Agent 6's strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"ca8105618c9c3a99371bbdc5a0609640cd402eaf1dfdbb6e8e68bcd549921092","addressRefs":[]},"a472d201-3dfd-4939-9789-5cedce9ea37a":{"id":"a472d201-3dfd-4939-9789-5cedce9ea37a","doc_no":"A.6.1.1.7.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"5e85bc90-de8f-43ab-80ea-4d7657f315a4","order":9931,"content":"The documents herein specify Launch Agent 6 governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Launch Agent 6 Artifact is specified in the Root Edit Primitive above at [A.6.1.1.7.2.2.2 - Root Edit Primitive](6c61b3d8-6cc8-4250-8173-eee8396a4ef4).","contentHash":"6a765a67f195e3e05b09e7a0210cd09c0774304ccf219b7c6bfca152b5afe4a2","addressRefs":[]},"05e36f80-32a1-4181-a98d-feabd2839e50":{"id":"05e36f80-32a1-4181-a98d-feabd2839e50","doc_no":"A.6.1.1.7.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"5e85bc90-de8f-43ab-80ea-4d7657f315a4","order":9932,"content":"Launch Agent 6 uses the Sky Forum for governance-related discussion. Posts should use the \"Launch Agent 6 Prime\" category.","contentHash":"fa2c55b588fabea7609a0f8447202e39f6e9115899815aa697dff1b513900417","addressRefs":[]},"007abab1-5cba-438d-8e91-9ad2b65a5521":{"id":"007abab1-5cba-438d-8e91-9ad2b65a5521","doc_no":"A.6.1.1.7.3.1.2","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"5e85bc90-de8f-43ab-80ea-4d7657f315a4","order":9933,"content":"The documents herein specify Launch Agent 6's emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Launch Agent 6 Artifact.","contentHash":"5dffcf703713da916b9eb61616483751f2d11b46b47f70e6109641a52c09a961","addressRefs":[]},"83b9de18-b26c-4b7a-a5d9-8cb39f6dec8c":{"id":"83b9de18-b26c-4b7a-a5d9-8cb39f6dec8c","doc_no":"A.6.1.1.7.3.1.3","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"5e85bc90-de8f-43ab-80ea-4d7657f315a4","order":9934,"content":"The documents herein specify Launch Agent 6's emergency response protocol in situations solely impacting Launch Agent 6 versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Launch Agent 6 Artifact.","contentHash":"6e8c8e6a9a30cf88dde7e79c874dffde3d75dab8a7244a1ba5cb1732312df62c","addressRefs":[]},"e5440d4f-c17a-4269-9e45-68f324046c84":{"id":"e5440d4f-c17a-4269-9e45-68f324046c84","doc_no":"A.6.1.1.7.3.2","title":"Ecosystem Accords","type":"Core","depth":6,"parentId":"5e85bc90-de8f-43ab-80ea-4d7657f315a4","order":9935,"content":"Launch Agent 6 has formally agreed to the Ecosystem Accords herein.","contentHash":"11dcc04e06c05aaae30b739028f479d5ea6d3ea9c6953c05c83964320972a734","addressRefs":[]},"e80f76d8-ab4e-44be-a649-4bb742d8e149":{"id":"e80f76d8-ab4e-44be-a649-4bb742d8e149","doc_no":"A.6.1.1.7.3.2.1","title":"Ecosystem Accord 6","type":"Core","depth":6,"parentId":"5e85bc90-de8f-43ab-80ea-4d7657f315a4","order":9936,"content":"Launch Agent 6 engaged in terms of agreement with Sky in Ecosystem Accord 6, located in [A.2.8.2.6 - Ecosystem Accord 6: Sky And Launch Agent 6](45125ff8-5435-4cbf-9b20-9f55a1dbc883).","contentHash":"52d2bb1888dd954a0ddf12c41411e8824bafa266326ec54c0f2deb23be7f5831","addressRefs":[]},"d0d77316-0b08-447c-b75a-ae7926b07019":{"id":"d0d77316-0b08-447c-b75a-ae7926b07019","doc_no":"A.6.1.1.8","title":"Launch Agent 7","type":"Core","depth":4,"parentId":"9fb7f1cc-f60b-4195-892d-5e540f969973","order":9937,"content":"The documents herein specify all of the logic for Launch Agent 7, including Launch Agent 7's strategy and how it uses the Sky Primitives to operationalize this strategy.","contentHash":"78e800d617a0aea3d307653e3fd8bf2d099562a142ba5e4d1ff9c956faf29fcd","addressRefs":[]},"ff01e448-1d0a-49e9-8490-5b1a497f1f27":{"id":"ff01e448-1d0a-49e9-8490-5b1a497f1f27","doc_no":"A.6.1.1.8.1","title":"Introduction","type":"Core","depth":5,"parentId":"d0d77316-0b08-447c-b75a-ae7926b07019","order":9938,"content":"Launch Agent 7 is an Agent focused on building structured credit infrastructure across traditional and digital financial markets. In addition to originating and managing institutional-grade credit facilities, Launch Agent 7 serves as a bridge between sophisticated capital and high-quality borrowers—including large enterprises and leading fintech platforms—through a suite of scalable credit solutions designed to support durable liquidity and long-term growth.","contentHash":"370c6fb25f0408c54dc6c04c1c0e9850dc5bb021ba1a0c5b766d54bb152842f6","addressRefs":[]},"d3c6d7a2-f399-40bd-ac22-4a565cfa253a":{"id":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","doc_no":"A.6.1.1.8.2","title":"Sky Primitives","type":"Core","depth":5,"parentId":"d0d77316-0b08-447c-b75a-ae7926b07019","order":9939,"content":"The documents herein implement the Sky Primitives for Launch Agent 7. See [A.2.2 - Sky Primitives](fcde2604-a138-4c1b-9d9a-14895835c907).","contentHash":"bca5f8593b439f45d1b74b300be815808e1ca3b826c98d6d9417169233e1f99c","addressRefs":[]},"23287614-9f6f-4d35-8a89-23e7de347c0e":{"id":"23287614-9f6f-4d35-8a89-23e7de347c0e","doc_no":"A.6.1.1.8.2.1","title":"Genesis Primitives","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9940,"content":"The documents herein implement the Genesis Primitives for Launch Agent 7. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5).","contentHash":"b4b93607c5a3966464dd0910b8d8ee49d4a7b661e56cd0a0cf72ae4b8528e768","addressRefs":[]},"208e19e0-65df-4c08-a788-bb7908d1aa17":{"id":"208e19e0-65df-4c08-a788-bb7908d1aa17","doc_no":"A.6.1.1.8.2.1.1","title":"Agent Creation Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9941,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instance of the Agent Creation Primitive. See [A.2.2.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe).","contentHash":"eeaf774665a01717a2b9bd80b8347efa41bf2f14c8ed8fb0b4f077d38ac79dc0","addressRefs":[]},"306be3c1-f4dd-4899-b66c-7992bd2f00dd":{"id":"306be3c1-f4dd-4899-b66c-7992bd2f00dd","doc_no":"A.6.1.1.8.2.1.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9942,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Agent Creation Primitive.","contentHash":"799cb7ca1ec8cce0689a94074bb519e88aa65b01c796a4123858f6e6e3902369","addressRefs":[]},"95c76b6a-6044-4178-a673-50c7e0db5c7e":{"id":"95c76b6a-6044-4178-a673-50c7e0db5c7e","doc_no":"A.6.1.1.8.2.1.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9943,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"8ff31ad2-37fb-4d0c-8865-57d14ab1821c":{"id":"8ff31ad2-37fb-4d0c-8865-57d14ab1821c","doc_no":"A.6.1.1.8.2.1.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9944,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`.","contentHash":"eda4333e80ae9b8bedf4f0ebecd96e218d3e3c31d9b9cadbf4aef16a6a0f2660","addressRefs":[]},"9378730b-3ec4-4b75-918d-1dc4163f4c45":{"id":"9378730b-3ec4-4b75-918d-1dc4163f4c45","doc_no":"A.6.1.1.8.2.1.1.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9945,"content":"This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`.","contentHash":"a1a0f1037f86541e77768ad7c07c06db16a58bf66aabad111fe97a45993d9979","addressRefs":[]},"1e930120-a453-475f-ab1a-c35d839ed4fc":{"id":"1e930120-a453-475f-ab1a-c35d839ed4fc","doc_no":"A.6.1.1.8.2.1.1.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9946,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.8.2.1.1.3.1 - Single Instance Configuration Document](d557f7bc-8db5-4b63-acbf-5a5b54931932).","contentHash":"3c39282566df9c5890cad23558563f569040c5d46ab581e5aac7131d6618e0c3","addressRefs":[]},"06f93b92-d9d2-4689-9607-99f6f03e23ca":{"id":"06f93b92-d9d2-4689-9607-99f6f03e23ca","doc_no":"A.6.1.1.8.2.1.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9947,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"99a7317c-54eb-4480-a4e6-850afb59019f":{"id":"99a7317c-54eb-4480-a4e6-850afb59019f","doc_no":"A.6.1.1.8.2.1.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9948,"content":"The document herein contains the Data Repository for the Primitive Hub Document.","contentHash":"ee60f57a9f8b03a9ee8b4f0bc16e87e673c55844fd3b58e3a86ad52bb469b030","addressRefs":[]},"e1714823-ea3d-49af-af1b-81a4d06dc7ec":{"id":"e1714823-ea3d-49af-af1b-81a4d06dc7ec","doc_no":"A.6.1.1.8.2.1.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9949,"content":"The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here.","contentHash":"e0f910139c0b388fa18884f239ef89dde26fc2c8f32f4a06144de07b2e7377a1","addressRefs":[]},"7f226306-4280-4eb5-93ef-3d23ea275366":{"id":"7f226306-4280-4eb5-93ef-3d23ea275366","doc_no":"A.6.1.1.8.2.1.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9950,"content":"The subtrees for failed Invocations of the Agent Creation Primitive are stored here.","contentHash":"37337a3c8c4ff21ac15a435358e7d48509ac317d2ab1bd70d8065e3cb5034d65","addressRefs":[]},"da9d9da4-e7a3-46d9-9b46-01634fb1ba02":{"id":"da9d9da4-e7a3-46d9-9b46-01634fb1ba02","doc_no":"A.6.1.1.8.2.1.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9951,"content":"The subtrees for Instances of the Agent Creation Primitive with `Suspended` Status are stored here.","contentHash":"183d20b3c12bea99884c81ff611bff6d5be670766bb91a4f4ccf5339e0a26636","addressRefs":[]},"c99398df-c653-4623-a3bf-0ac407116b91":{"id":"c99398df-c653-4623-a3bf-0ac407116b91","doc_no":"A.6.1.1.8.2.1.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9952,"content":"The Instances of the Agent Creation Primitive with `Active` Status are stored herein.","contentHash":"5a19d0f3643c9f669303624bdc233452646dbbd09ecf9ea677a5327ab2a9a9ad","addressRefs":[]},"f661d4a1-a5ff-4cbd-8d57-82418669a279":{"id":"f661d4a1-a5ff-4cbd-8d57-82418669a279","doc_no":"A.6.1.1.8.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9953,"content":"The Instances of the Agent Creation Primitive with `Completed` Status are contained herein.","contentHash":"43181a10e999907f0fc92f1fd29d9391a275c2a3ed1e6e9b20c612ab227b2539","addressRefs":[]},"d557f7bc-8db5-4b63-acbf-5a5b54931932":{"id":"d557f7bc-8db5-4b63-acbf-5a5b54931932","doc_no":"A.6.1.1.8.2.1.1.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9954,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance.","contentHash":"fc6dc63fa06271fc8e522f8f275ba256eb9ea57a65f216ee1662dea7cdfdba29","addressRefs":[]},"5086285a-0bac-433d-bb2c-f9a3bee1ec7e":{"id":"5086285a-0bac-433d-bb2c-f9a3bee1ec7e","doc_no":"A.6.1.1.8.2.1.1.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9955,"content":"The documents herein define the parameters of the Single Instance of the Agent Creation Primitive.","contentHash":"7b7f18f39c8b827aa6d75fb096ea3f7f4d5d46b7de0a7149f351d09b41b57b85","addressRefs":[]},"65776660-e4a8-4385-aede-31b73b855cb1":{"id":"65776660-e4a8-4385-aede-31b73b855cb1","doc_no":"A.6.1.1.8.2.1.1.3.1.1.1","title":"Name","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9956,"content":"The name of the Agent is Launch Agent 7.","contentHash":"ef15b13b74da356e21f6a6ba4b7db3f4b2b5ce735e74596e75497905d5aca0e1","addressRefs":[]},"a5a06fb8-2ae7-4af3-8e96-e1fb57eef916":{"id":"a5a06fb8-2ae7-4af3-8e96-e1fb57eef916","doc_no":"A.6.1.1.8.2.1.1.3.1.1.2","title":"SubProxy Account","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9957,"content":"The address of Launch Agent 7's SubProxy Account on the Ethereum Mainnet is `0x56a9bA5FE133EF4Ab1131E8ac7c4312a52284f5B`.","contentHash":"06950664cb7d13d12b12f29920b7b61af90e4d5a59e1ba16bcbdc462b204acfb","addressRefs":["0x56a9ba5fe133ef4ab1131e8ac7c4312a52284f5b"]},"fa741bad-9966-4ff7-8300-238d1c58df9a":{"id":"fa741bad-9966-4ff7-8300-238d1c58df9a","doc_no":"A.6.1.1.8.2.1.1.3.1.1.3","title":"StarGuard Contract","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9958,"content":"The address of Launch Agent 7's StarGuard contract on the Ethereum Mainnet is `0xB36e88c02E4619Ef34C0Db76C5BCb6655747FB28`.","contentHash":"03d7601d00b621b3f23e93176d907f6d6877290db5dc7b0db42f03cd1269e532","addressRefs":["0xb36e88c02e4619ef34c0db76c5bcb6655747fb28"]},"68ce7040-9954-4339-8fa8-d5679eb2a1d5":{"id":"68ce7040-9954-4339-8fa8-d5679eb2a1d5","doc_no":"A.6.1.1.8.2.1.1.3.1.1.3.1","title":"StarGuard Max Delay","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9959,"content":"The Launch Agent 7 StarGuard `maxDelay` is seven (7) days.","contentHash":"bdc75d7a96e7cca9e117fbb69d748c5bb83665cff18453f8a160e2d0f28a26c2","addressRefs":[]},"9646935e-2406-4187-b43d-9158bdf71856":{"id":"9646935e-2406-4187-b43d-9158bdf71856","doc_no":"A.6.1.1.8.2.1.1.3.1.1.4","title":"Genesis Account","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9960,"content":"The address of Launch Agent 7's Genesis Account will be specified in a future iteration of the Launch Agent 7 Artifact.","contentHash":"d1d17dcdf0f37bd6bc55bcd146e7b760ecf3882882d07d19dfd58578d8b04c1c","addressRefs":[]},"83d48c76-a0c0-447f-a749-9fa841d6af49":{"id":"83d48c76-a0c0-447f-a749-9fa841d6af49","doc_no":"A.6.1.1.8.2.1.1.3.1.1.5","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9961,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any.","contentHash":"152dcf455ef8c1171dd712dac440794b534536711ec8937e0c52887f96c12ff9","addressRefs":[]},"9fa056b9-0961-4858-b610-3ddd8f728058":{"id":"9fa056b9-0961-4858-b610-3ddd8f728058","doc_no":"A.6.1.1.8.2.1.1.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9962,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment.","contentHash":"08aca859c51b241c4d94bc7d28ea25ac31d5b16102d31a8fa42f95347d16272a","addressRefs":[]},"0e086a31-8f5c-452e-b9b6-6840f5e9c90d":{"id":"0e086a31-8f5c-452e-b9b6-6840f5e9c90d","doc_no":"A.6.1.1.8.2.1.1.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9963,"content":"The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive.","contentHash":"fa2d24b7dd39f4c28b8263f34c7c4622301099a042cf9de171a954a7d27fc3fb","addressRefs":[]},"e0b544df-ad91-46a7-8c4e-da665c1ba9f5":{"id":"e0b544df-ad91-46a7-8c4e-da665c1ba9f5","doc_no":"A.6.1.1.8.2.1.1.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9964,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"bc83f510-98d9-4088-b775-3fca976df4ed":{"id":"bc83f510-98d9-4088-b775-3fca976df4ed","doc_no":"A.6.1.1.8.2.1.1.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9965,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"904a4c5e-7d06-45ee-b0e5-b327f131276d":{"id":"904a4c5e-7d06-45ee-b0e5-b327f131276d","doc_no":"A.6.1.1.8.2.1.1.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9966,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"6cf9e5bd-a6a9-4f8c-b823-17c99c6d3805":{"id":"6cf9e5bd-a6a9-4f8c-b823-17c99c6d3805","doc_no":"A.6.1.1.8.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9967,"content":"Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"e9d9fa3abf05f1714c38eb88be18cd640570cf86af78c43bb02c2817d33a68f8","addressRefs":[]},"3ba02850-d20f-4c96-b4b5-956c46c68be9":{"id":"3ba02850-d20f-4c96-b4b5-956c46c68be9","doc_no":"A.6.1.1.8.2.1.2","title":"Prime Transformation Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9968,"content":"The documents herein contain all data and specifications for Launch Agent 7's instance of the Prime Transformation Primitive. See [A.2.2.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482).","contentHash":"1d0f25e4d4e7b8758a73854ef04282a1ecbb1f0d1ba1c580538ecdcdf6623387","addressRefs":[]},"ec52fb9d-30d6-4ccb-830d-eb8878e58e64":{"id":"ec52fb9d-30d6-4ccb-830d-eb8878e58e64","doc_no":"A.6.1.1.8.2.1.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9969,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Prime Transformation Primitive.","contentHash":"4cfcaaac02d293898093506efddc6568416389499e3623724897e20f2c854c04","addressRefs":[]},"adda8707-63b5-414a-b30c-bb07bb09ec47":{"id":"adda8707-63b5-414a-b30c-bb07bb09ec47","doc_no":"A.6.1.1.8.2.1.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9970,"content":"`Completed`","contentHash":"301945a3709898af8e7fae4fdc06785ef76d0075955e7d8272303798db49c9fb","addressRefs":[]},"8251dc77-6944-4ccb-b653-f93b70b43ec5":{"id":"8251dc77-6944-4ccb-b653-f93b70b43ec5","doc_no":"A.6.1.1.8.2.1.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9971,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`.","contentHash":"69cc489e30b21f16810bec675c069b3d980d0c9a1607df6a794fa29a39fdb861","addressRefs":[]},"6ec0cf3b-a2b7-4fa8-88d8-c64af3fdea83":{"id":"6ec0cf3b-a2b7-4fa8-88d8-c64af3fdea83","doc_no":"A.6.1.1.8.2.1.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9972,"content":"This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`.","contentHash":"692a834c74c2160ce176cfc78e8905a07abf6812488b6a8fb62f19de3acfc831","addressRefs":[]},"1ecf0cd6-aac0-4706-a34b-fb5adb3daa32":{"id":"1ecf0cd6-aac0-4706-a34b-fb5adb3daa32","doc_no":"A.6.1.1.8.2.1.2.1.3.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9973,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.8.2.1.2.3.1 - Single Instance Configuration Document](7b97df7e-67b7-4d4d-b4b5-9e1612793b7c).","contentHash":"4ec45538b0622b25819e4534ac17631f6821e72b7d5b2f7bd98a17f2282ccaa2","addressRefs":[]},"04f57d55-373b-40bf-a453-cc1803f26d19":{"id":"04f57d55-373b-40bf-a453-cc1803f26d19","doc_no":"A.6.1.1.8.2.1.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9974,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"a50b9d4f-49b5-4c28-a8ba-03f3cd498ce5":{"id":"a50b9d4f-49b5-4c28-a8ba-03f3cd498ce5","doc_no":"A.6.1.1.8.2.1.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9975,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"6f75f229-9835-442b-b718-ca9d426c1e6a":{"id":"6f75f229-9835-442b-b718-ca9d426c1e6a","doc_no":"A.6.1.1.8.2.1.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9976,"content":"The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here.","contentHash":"8532e105b46c773bdf4b54ebf8a3cf9f04b8701989216f0a24c75acb55219e95","addressRefs":[]},"7c44f5b5-109b-4c78-afd5-bc331207b8fe":{"id":"7c44f5b5-109b-4c78-afd5-bc331207b8fe","doc_no":"A.6.1.1.8.2.1.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9977,"content":"The subtrees for failed Invocations of the Prime Transformation Primitive are stored here.","contentHash":"f930b542ee55336ad067e2ab6f27398cbe8a0242e1556736c578bd267f0478a9","addressRefs":[]},"a718f498-b0dd-41ed-8837-58f279b94e78":{"id":"a718f498-b0dd-41ed-8837-58f279b94e78","doc_no":"A.6.1.1.8.2.1.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9978,"content":"The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here.","contentHash":"71b16021d9728fd3a27c669e63b91b73498cb78b58efd97e538301e63cac0325","addressRefs":[]},"4b3f09cc-abc1-4b44-8ce9-079b9ca1a3ff":{"id":"4b3f09cc-abc1-4b44-8ce9-079b9ca1a3ff","doc_no":"A.6.1.1.8.2.1.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9979,"content":"The Instances of the Prime Transformation Primitive with `Active` Status are stored herein.","contentHash":"1340f2e5cf719d154852c4ffa862a081c108381064b05bb88ecda495ed810f03","addressRefs":[]},"4479d30b-8fa6-4dad-8dc9-9a93abadf267":{"id":"4479d30b-8fa6-4dad-8dc9-9a93abadf267","doc_no":"A.6.1.1.8.2.1.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9980,"content":"The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein.","contentHash":"65f4c5bc892654cc4fa182c043221f019b6d4b1354af0e4e2131d6a067f78f32","addressRefs":[]},"7b97df7e-67b7-4d4d-b4b5-9e1612793b7c":{"id":"7b97df7e-67b7-4d4d-b4b5-9e1612793b7c","doc_no":"A.6.1.1.8.2.1.2.3.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9981,"content":"The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance.","contentHash":"adb768aed11eb15e1cc3a149b1a3dac27b85a91b483c74095867edf047147c65","addressRefs":[]},"bf3d16ff-82f7-4804-a0bf-153eccda8a66":{"id":"bf3d16ff-82f7-4804-a0bf-153eccda8a66","doc_no":"A.6.1.1.8.2.1.2.3.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9982,"content":"The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive.","contentHash":"767e3e7713e1bd777e857b3dcbea2a29e45aaf7f1c94a82aa1cc33b21f218bf0","addressRefs":[]},"f74decac-e2cb-4403-b3d7-4cef0a90fda5":{"id":"f74decac-e2cb-4403-b3d7-4cef0a90fda5","doc_no":"A.6.1.1.8.2.1.2.3.1.1.1","title":"Agent Type","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9983,"content":"Launch Agent 7 is a Prime Agent.","contentHash":"b197b6c9918452c14efd312b554be8685e64427382317781331cfb05f22ff1fd","addressRefs":[]},"e6e419d7-ce14-4123-b22a-62f94075ff52":{"id":"e6e419d7-ce14-4123-b22a-62f94075ff52","doc_no":"A.6.1.1.8.2.1.2.3.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9984,"content":"The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any.","contentHash":"f9e8edcc2461382d0249118cf8777ebe167ea03a05a4aa449846c2c5104209cc","addressRefs":[]},"3a52a82f-7d54-4124-90ed-6007b217a174":{"id":"3a52a82f-7d54-4124-90ed-6007b217a174","doc_no":"A.6.1.1.8.2.1.2.3.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9985,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment.","contentHash":"1454ef8cb549fde9365b2a011e9ee99ddb223a4bed1052a8871b40ec02c05753","addressRefs":[]},"7967c2b8-181c-4582-a265-7e60654503e1":{"id":"7967c2b8-181c-4582-a265-7e60654503e1","doc_no":"A.6.1.1.8.2.1.2.3.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9986,"content":"The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive.","contentHash":"531c9020ec6e9504b591c137e771e72cc0db7ef35543eaad2a9d12999ef47e66","addressRefs":[]},"cd906df7-aeb9-4859-a364-3fb03d4f2f78":{"id":"cd906df7-aeb9-4859-a364-3fb03d4f2f78","doc_no":"A.6.1.1.8.2.1.2.3.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9987,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"dcbe59e5-5d72-49f3-92cc-fce16bd6d5f9":{"id":"dcbe59e5-5d72-49f3-92cc-fce16bd6d5f9","doc_no":"A.6.1.1.8.2.1.2.3.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9988,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"11420736-9467-412e-81ee-389e254b4ac3":{"id":"11420736-9467-412e-81ee-389e254b4ac3","doc_no":"A.6.1.1.8.2.1.2.3.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9989,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"ea18a0a9-b7dd-47d8-97da-3f55b3eeb645":{"id":"ea18a0a9-b7dd-47d8-97da-3f55b3eeb645","doc_no":"A.6.1.1.8.2.1.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9990,"content":"Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"4fe4efe76336c1db1e3a1be433c295360f5983e5e20a32e0ffde527f990ead2f","addressRefs":[]},"073db45c-4a8f-4d59-be5e-f9dcba60ed98":{"id":"073db45c-4a8f-4d59-be5e-f9dcba60ed98","doc_no":"A.6.1.1.8.2.1.3","title":"Executor Transformation Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9991,"content":"The documents herein contain all data and specifications for Launch Agent 7's instance of the Executor Transformation Primitive. See [A.2.2.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7).","contentHash":"d49450430136882429a9ef4974919cfc07d1bfd5d944b5b606c749bfbfec3dda","addressRefs":[]},"acd47616-d33c-4a8e-81cf-9f75cf83187d":{"id":"acd47616-d33c-4a8e-81cf-9f75cf83187d","doc_no":"A.6.1.1.8.2.1.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9992,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Executor Transformation Primitive.","contentHash":"c5c14489074e40bf91b7693d91dba193a98da4d9698492d5e5bf6f221131e3d6","addressRefs":[]},"33e40429-53c4-488f-be4e-192d0769c517":{"id":"33e40429-53c4-488f-be4e-192d0769c517","doc_no":"A.6.1.1.8.2.1.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9993,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"412f680a-f756-4180-b2de-b93caf7eecb2":{"id":"412f680a-f756-4180-b2de-b93caf7eecb2","doc_no":"A.6.1.1.8.2.1.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9994,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`.","contentHash":"d00181270f87ff121e98df9061a52e7f9b32523d17bf95ee8f8843d0c5358c53","addressRefs":[]},"1cbf2b10-57e5-45fa-a1fd-ed63ac2b83f5":{"id":"1cbf2b10-57e5-45fa-a1fd-ed63ac2b83f5","doc_no":"A.6.1.1.8.2.1.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9995,"content":"This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`.","contentHash":"b93f9b15348cf15c946c0b0d8a561735fc88cadae9126ac029facb31a38f7705","addressRefs":[]},"6d2ec280-7635-4cd2-928d-1bad6b86b785":{"id":"6d2ec280-7635-4cd2-928d-1bad6b86b785","doc_no":"A.6.1.1.8.2.1.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9996,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"ada314c1-b67d-47d7-9d3d-b45ceba4eb3f":{"id":"ada314c1-b67d-47d7-9d3d-b45ceba4eb3f","doc_no":"A.6.1.1.8.2.1.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9997,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"ce8182d8-bcde-411d-b0ae-03967a75b31c":{"id":"ce8182d8-bcde-411d-b0ae-03967a75b31c","doc_no":"A.6.1.1.8.2.1.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9998,"content":"The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here.","contentHash":"c928a7c7386af76ae6c18d5ba9d52b547f598bacdecedb6e4ba0395bbcbf96bc","addressRefs":[]},"77c26627-04f7-4838-ab37-8a192c0d7040":{"id":"77c26627-04f7-4838-ab37-8a192c0d7040","doc_no":"A.6.1.1.8.2.1.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":9999,"content":"The subtrees for failed Invocations of the Executor Transformation Primitive are stored here.","contentHash":"1e8fe664be12a26bb43b570a5f1827c6ba1ec1c13995be5f233f6da05c330c96","addressRefs":[]},"5461ddf6-6698-43bf-b5b0-d8e04d07382c":{"id":"5461ddf6-6698-43bf-b5b0-d8e04d07382c","doc_no":"A.6.1.1.8.2.1.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10000,"content":"The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here.","contentHash":"1121e9cbc94c067b2afa9b68988c81904f64a636e40871d6af39d382c6776e54","addressRefs":[]},"10ac7a6e-6436-4969-9c90-9132f9d4bb24":{"id":"10ac7a6e-6436-4969-9c90-9132f9d4bb24","doc_no":"A.6.1.1.8.2.1.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10001,"content":"The Instances of the Executor Transformation Primitive with `Active` Status are stored herein.","contentHash":"c047e8cc233142c33fc84f1637850cbc49c96a7973ad6499e9b99c12f042d831","addressRefs":[]},"adc67dcc-b853-472f-8805-3ede35b2b17e":{"id":"adc67dcc-b853-472f-8805-3ede35b2b17e","doc_no":"A.6.1.1.8.2.1.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10002,"content":"The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein.","contentHash":"c65310b1d8154ba835f3b326d0da73e609b868291a57c22ed91fa9618d384913","addressRefs":[]},"fc0b759f-7211-41fb-99cb-729a289677f4":{"id":"fc0b759f-7211-41fb-99cb-729a289677f4","doc_no":"A.6.1.1.8.2.1.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10003,"content":"Because the Executor Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further Instances of the Primitive can be Invoked.","contentHash":"881b495be4c485f92ac17e317518a3acf1b9138bf767355e802e8f814f976472","addressRefs":[]},"10cf4cab-179b-4e1b-a9c9-22b09af8b6fc":{"id":"10cf4cab-179b-4e1b-a9c9-22b09af8b6fc","doc_no":"A.6.1.1.8.2.1.4","title":"Agent Token Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10004,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instance of the Agent Token Primitive. See [A.2.2.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064).","contentHash":"907c2841305dce3c5851d881fb84c37bb594fc1cd2d1fa33241c8b8b14f1c4c8","addressRefs":[]},"9739918e-5d1a-4113-8127-a6470a54ace1":{"id":"9739918e-5d1a-4113-8127-a6470a54ace1","doc_no":"A.6.1.1.8.2.1.4.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10005,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Agent Token Primitive.","contentHash":"8c8e7a47b7d25765aade3042936318cf5c2bff6b2fbf01bc00501aa33083fe74","addressRefs":[]},"1e052e06-8467-4542-8cc5-ebe39b451141":{"id":"1e052e06-8467-4542-8cc5-ebe39b451141","doc_no":"A.6.1.1.8.2.1.4.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10006,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"cc39cc3b-1f15-4dd8-9429-06703b0619e5":{"id":"cc39cc3b-1f15-4dd8-9429-06703b0619e5","doc_no":"A.6.1.1.8.2.1.4.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10007,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`.","contentHash":"6f2ac74f37d505b90954f20ec3a29c715ed86e77ac4d4f4609a2bb0d21e9c6b8","addressRefs":[]},"3040332e-af07-4555-bc2e-6d7e91237108":{"id":"3040332e-af07-4555-bc2e-6d7e91237108","doc_no":"A.6.1.1.8.2.1.4.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10008,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.8.2.1.4.2.1 - Single Instance Configuration Document](2af5a57c-23fa-4299-a4f4-fe6f33ef2b6d).","contentHash":"257fe391e67332a03b2cadecdcf81d6c8e8c7c5c4fb8055b57be9fff2b5c88ad","addressRefs":[]},"e6befbe6-c577-43db-a262-c148ebd7236f":{"id":"e6befbe6-c577-43db-a262-c148ebd7236f","doc_no":"A.6.1.1.8.2.1.4.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10009,"content":"This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`.","contentHash":"9c512d5a2c54ba416896498fad372fbb95cf4797351437be6529e4b4829e8988","addressRefs":[]},"b158dd8d-b867-49dc-b7c9-aaa743eaa0f7":{"id":"b158dd8d-b867-49dc-b7c9-aaa743eaa0f7","doc_no":"A.6.1.1.8.2.1.4.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10010,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"4d03af47-7a50-468c-bdee-2b95eb721784":{"id":"4d03af47-7a50-468c-bdee-2b95eb721784","doc_no":"A.6.1.1.8.2.1.4.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10011,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"26b1ead4-dd0b-4dcb-b6cb-0e72bae7cfe6":{"id":"26b1ead4-dd0b-4dcb-b6cb-0e72bae7cfe6","doc_no":"A.6.1.1.8.2.1.4.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10012,"content":"The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here.","contentHash":"9548a2c628b0bbb6f90a5849eb526b20ca945689b66fcbf1448273574101e365","addressRefs":[]},"9ca435e5-75ca-4444-83d6-89e3fdc56a6b":{"id":"9ca435e5-75ca-4444-83d6-89e3fdc56a6b","doc_no":"A.6.1.1.8.2.1.4.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10013,"content":"The subtrees for failed Invocations of the Agent Token Primitive are stored here.","contentHash":"446c9385a0d48706e8cbab99aae564cfed01ed2471e68356f3c1e10e9202ac02","addressRefs":[]},"ee1536f2-7de8-4c65-8e36-1c3b10354020":{"id":"ee1536f2-7de8-4c65-8e36-1c3b10354020","doc_no":"A.6.1.1.8.2.1.4.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10014,"content":"The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here.","contentHash":"87c8227d4cace5f52b95a98958e8c614b38dcfab4038ccd5fc1c5d12cad9f6b5","addressRefs":[]},"41298826-6bc3-4f30-a304-2268579084ed":{"id":"41298826-6bc3-4f30-a304-2268579084ed","doc_no":"A.6.1.1.8.2.1.4.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10015,"content":"The Instances of the Agent Token Primitive with `Active` Status are stored herein.","contentHash":"f2e00682651c6acaac496cb1ecc057430b7208416e1e7da6bbfc27235679a549","addressRefs":[]},"2af5a57c-23fa-4299-a4f4-fe6f33ef2b6d":{"id":"2af5a57c-23fa-4299-a4f4-fe6f33ef2b6d","doc_no":"A.6.1.1.8.2.1.4.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10016,"content":"The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance.","contentHash":"af91e00cc082fb72c6304e12a98c4fdb0cc526d8eccc712a119ab78f8f677334","addressRefs":[]},"837ff40f-de82-436a-9332-0def187295fb":{"id":"837ff40f-de82-436a-9332-0def187295fb","doc_no":"A.6.1.1.8.2.1.4.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10017,"content":"The documents herein define the parameters of the Single Instance of the Agent Token Primitive.","contentHash":"c5ed1a310ee4673c5b3bd9e05de4db298f82a6b3e3dcb807a9ca42f288733a8c","addressRefs":[]},"2de22e5a-1850-4973-b045-794752a6817a":{"id":"2de22e5a-1850-4973-b045-794752a6817a","doc_no":"A.6.1.1.8.2.1.4.2.1.1.1","title":"Token Name","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10018,"content":"The name of Launch Agent 7's token is Launch Agent 7.","contentHash":"b5ca40c68e9631f096c545b66fe5f553cd647b83de50073e2914b71262b0f3cf","addressRefs":[]},"072c99dd-2564-4d56-a469-0cd1861d2f74":{"id":"072c99dd-2564-4d56-a469-0cd1861d2f74","doc_no":"A.6.1.1.8.2.1.4.2.1.1.2","title":"Token Symbol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10019,"content":"The symbol of Launch Agent 7's token is AGENT7.","contentHash":"3c5c21dcf997f5c8b805d90dcc569ebde6c6fcecf77a5368a60c0b138cb5bd67","addressRefs":[]},"da510ee7-7b5d-4964-8778-b6f76ededdbb":{"id":"da510ee7-7b5d-4964-8778-b6f76ededdbb","doc_no":"A.6.1.1.8.2.1.4.2.1.1.3","title":"Genesis Supply","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10020,"content":"The Genesis Supply of AGENT7 is 1 billion.","contentHash":"82a990b9f7583ba73b1c9a99825237fe3994945efb8a0a6aa5a8e021c4254a9a","addressRefs":[]},"9d142adb-8741-43b0-b36b-a222c17ed6e5":{"id":"9d142adb-8741-43b0-b36b-a222c17ed6e5","doc_no":"A.6.1.1.8.2.1.4.2.1.1.4","title":"Token Address","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10021,"content":"The address of AGENT7 will be specified in a future iteration of the Launch Agent 7 Artifact.","contentHash":"c0c8b4322ede64bb3539aa359fc9ee06fa15540130c3b7f856ed73a03c3dfd56","addressRefs":[]},"76bec570-320e-4590-91ba-0ebd7307742f":{"id":"76bec570-320e-4590-91ba-0ebd7307742f","doc_no":"A.6.1.1.8.2.1.4.2.1.1.5","title":"Token Admin","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10022,"content":"The token Admin will be specified in a future iteration of the Launch Agent 7 Artifact.","contentHash":"fa4dbded18ade28ec4ec84ced2aa5a0c48136fef0da7dd841a83cb5568f79cd0","addressRefs":[]},"7262e995-db8b-4db7-860c-60b2250ba04a":{"id":"7262e995-db8b-4db7-860c-60b2250ba04a","doc_no":"A.6.1.1.8.2.1.4.2.1.1.6","title":"Token Emissions","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10023,"content":"Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by Launch Agent 7 Governance. Sky Governance retains the ability to revert where Launch Agent 7 is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2 - Risk Capital](55999acf-75fe-4adf-8584-9746ef50d3e4).","contentHash":"5a159dc85a9347f89d3a61a74528db902a427d1b7e7eaf6047fd802995d26b3d","addressRefs":[]},"b290ffad-9860-40cd-a05f-d8fc2a53c03c":{"id":"b290ffad-9860-40cd-a05f-d8fc2a53c03c","doc_no":"A.6.1.1.8.2.1.4.2.1.1.7","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10024,"content":"The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any.","contentHash":"f9f18a898f022d4a0605987cf2a4e57448f3b633b3dcf45eb8cd2c3c9fa35e69","addressRefs":[]},"e4c6a219-2904-4d2a-bdfd-f8ab7cc379aa":{"id":"e4c6a219-2904-4d2a-bdfd-f8ab7cc379aa","doc_no":"A.6.1.1.8.2.1.4.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10025,"content":"The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply.\n\n- These processes will be defined in a future iteration of the Launch Agent 7 Artifact.","contentHash":"22d91c04879404e2df842e67c8f4faebbd9586d31bcf097c665030505737aec0","addressRefs":[]},"a0b0274a-6b4f-42cf-81aa-97cc675f997c":{"id":"a0b0274a-6b4f-42cf-81aa-97cc675f997c","doc_no":"A.6.1.1.8.2.1.4.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10026,"content":"The documents herein contain data relevant to the Single Instance of the Agent Token Primitive.","contentHash":"57e62ec353ca64fa470c176a6c3a55d44ec54547344f4b9ea5a9e3694f0126e0","addressRefs":[]},"3fa4e43c-9de9-4778-92b2-2adfb9dfdc92":{"id":"3fa4e43c-9de9-4778-92b2-2adfb9dfdc92","doc_no":"A.6.1.1.8.2.1.4.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10027,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"8ee40481-70c1-450b-b6e0-aa054cc8daca":{"id":"8ee40481-70c1-450b-b6e0-aa054cc8daca","doc_no":"A.6.1.1.8.2.1.4.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10028,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"293be631-ea6f-4a3c-a6db-f1cc99b322e9":{"id":"293be631-ea6f-4a3c-a6db-f1cc99b322e9","doc_no":"A.6.1.1.8.2.1.4.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10029,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"21ccd43b-b2e2-4404-bdf2-b041c42a8764":{"id":"21ccd43b-b2e2-4404-bdf2-b041c42a8764","doc_no":"A.6.1.1.8.2.1.4.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10030,"content":"The Instances of the Agent Token Primitive with `Completed` Status are contained herein.","contentHash":"eb7ab6d647a8b1af3c592bbd52923237be8034c03da3adfb040e67a261e6eb98","addressRefs":[]},"739fcfb1-6792-4739-8a3e-bf7d650754e7":{"id":"739fcfb1-6792-4739-8a3e-bf7d650754e7","doc_no":"A.6.1.1.8.2.1.4.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10031,"content":"Because the Agent Token Primitive is Invoked solely for the one-time deployment of the Agent’s token, no further Instances of the Primitive can be Invoked.","contentHash":"52afb2696862544367fc370a3618393cda5439700a4610a3c1783702ba6dd2f1","addressRefs":[]},"54a65766-cc3b-41f5-8be3-a671d1dac3a4":{"id":"54a65766-cc3b-41f5-8be3-a671d1dac3a4","doc_no":"A.6.1.1.8.2.2","title":"Operational Primitives","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10032,"content":"The documents herein implement the Operational Primitives for Launch Agent 7. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad).","contentHash":"9eafd03da8c5e18f1da0c8ad137336ed4ca60c825f014df364f8e48f09727810","addressRefs":[]},"eeafc392-5418-43ac-8281-69ac39775941":{"id":"eeafc392-5418-43ac-8281-69ac39775941","doc_no":"A.6.1.1.8.2.2.1","title":"Executor Accord Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10033,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Executor Accord Primitive. See [A.2.2.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb).","contentHash":"1abc52fcd3f7a349d9cf28dc3fd6da8a5774da0bc9fac594401428f006a90d23","addressRefs":[]},"afe5ecf8-9fde-4d20-b867-192ad174c6b0":{"id":"afe5ecf8-9fde-4d20-b867-192ad174c6b0","doc_no":"A.6.1.1.8.2.2.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10034,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Executor Accord Primitive.","contentHash":"d2f52a7f814b35fd4fe431ee06510bf37cfd5fe7adccff3490c0550d12bc7aa9","addressRefs":[]},"f4ce2a59-886f-4e82-bfc3-243f7e0b2e1a":{"id":"f4ce2a59-886f-4e82-bfc3-243f7e0b2e1a","doc_no":"A.6.1.1.8.2.2.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10035,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"0580085d-43e0-4c0e-81d9-9d92a9ea0215":{"id":"0580085d-43e0-4c0e-81d9-9d92a9ea0215","doc_no":"A.6.1.1.8.2.2.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10036,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`.","contentHash":"558ce351bed40aa1de5ca17af81ec92936776571446375cb68210019ef6fa1e0","addressRefs":[]},"370808df-acc5-425a-89f8-2bd72db3ba85":{"id":"370808df-acc5-425a-89f8-2bd72db3ba85","doc_no":"A.6.1.1.8.2.2.1.1.2.1","title":"Ozone Instance Configuration Document Location","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10037,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.8.2.2.1.2.1 - Ozone Instance Configuration Document](204124cd-73cd-4862-9288-a3c8ecd65fcc).","contentHash":"437a85f696ff52092bc1ad6dc486ec5662e7306c70b4f43f85714591b3b591d2","addressRefs":[]},"1ddc6150-a963-4086-8e4c-4a878d2a95f9":{"id":"1ddc6150-a963-4086-8e4c-4a878d2a95f9","doc_no":"A.6.1.1.8.2.2.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10038,"content":"This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`.","contentHash":"ca320c23bd216a4df9121786354569a306e80e35d029618bf94e2645f7e53c11","addressRefs":[]},"012578b7-90f4-42c6-ac63-4bcaf199565e":{"id":"012578b7-90f4-42c6-ac63-4bcaf199565e","doc_no":"A.6.1.1.8.2.2.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10039,"content":"This document contains a Directory of all prospective Instances of the Executor Accord Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.2.1.1.2 - Active Instances Directory](0580085d-43e0-4c0e-81d9-9d92a9ea0215), whereas failed Invocations are Archived in [A.6.1.1.8.2.2.1.1.5 - Hub Data Repository](fbe85851-1f5d-4762-a27e-3c6681a1d7f5).","contentHash":"f84a9424b857aa487e70f5d3c3a4a2a793f7ccbad3a6614423eaef696d195f2f","addressRefs":[]},"fbe85851-1f5d-4762-a27e-3c6681a1d7f5":{"id":"fbe85851-1f5d-4762-a27e-3c6681a1d7f5","doc_no":"A.6.1.1.8.2.2.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10040,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"f62cf432-f30a-4277-9dfe-79d7bcab8c66":{"id":"f62cf432-f30a-4277-9dfe-79d7bcab8c66","doc_no":"A.6.1.1.8.2.2.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10041,"content":"The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here.","contentHash":"d8d617b6ac40fceb10781ae187a772e3c41603512e568d08db8aad5ffa59e6a1","addressRefs":[]},"3902f9f9-a85d-4322-ad5b-3e6c5fa1254d":{"id":"3902f9f9-a85d-4322-ad5b-3e6c5fa1254d","doc_no":"A.6.1.1.8.2.2.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10042,"content":"The subtrees for failed Invocations of the Executor Accord Primitive are stored here.","contentHash":"42efec6bc5fe1ef3723ff8fe3d0c6a4ad75202965da9fb243596a9d75ba8ea06","addressRefs":[]},"3cbe1f10-f88f-4e74-89f8-591424e9845e":{"id":"3cbe1f10-f88f-4e74-89f8-591424e9845e","doc_no":"A.6.1.1.8.2.2.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10043,"content":"The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here.","contentHash":"deda3a13d9e4e209e43bf0d02ff98f474ca666bf15659593e774e62fb3ae1090","addressRefs":[]},"e7f6dd4d-2943-40a2-ba6c-8c738e5fc0bd":{"id":"e7f6dd4d-2943-40a2-ba6c-8c738e5fc0bd","doc_no":"A.6.1.1.8.2.2.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10044,"content":"The Instances of the Executor Accord Primitive with `Active` Status are stored herein.","contentHash":"bff8bf6e2638776b23234573c0d214c8c5e40fa62c19e4cde568d4b44995f88e","addressRefs":[]},"204124cd-73cd-4862-9288-a3c8ecd65fcc":{"id":"204124cd-73cd-4862-9288-a3c8ecd65fcc","doc_no":"A.6.1.1.8.2.2.1.2.1","title":"Ozone Instance Configuration Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10045,"content":"The documents herein contain the Instance Configuration Document for the Ozone Executor Accord Primitive Instance.","contentHash":"ca0caee12f20439eb72be855f0a3c3853fe737be1313cfe253dad38c7f8d0623","addressRefs":[]},"a18b8499-8971-4f2a-a6ad-0d5b03f4db18":{"id":"a18b8499-8971-4f2a-a6ad-0d5b03f4db18","doc_no":"A.6.1.1.8.2.2.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10046,"content":"The documents herein define the parameters of the Ozone Instance of the Executor Accord Primitive.","contentHash":"638cf31df48e28f4a38e5155a81f9cd4b27bb221ff40cc010386b96be05691e5","addressRefs":[]},"c1f2c961-08b0-4060-abd6-12f4e26dc682":{"id":"c1f2c961-08b0-4060-abd6-12f4e26dc682","doc_no":"A.6.1.1.8.2.2.1.2.1.1.1","title":"Operational Executor Agent","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10047,"content":"The Operational Facilitator and Operational GovOps for Ozone are specified in [A.6.1.2.2 - Operational Executor Agent Ozone](565660dd-7850-4c3a-8dba-554542bf103a).","contentHash":"8ed0f1fb66d463549e15caa041123f9031ac10ad2f25d039e4bc6b7777f702a7","addressRefs":[]},"7964aebd-6373-405c-9e7c-d23ca86baf5d":{"id":"7964aebd-6373-405c-9e7c-d23ca86baf5d","doc_no":"A.6.1.1.8.2.2.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10048,"content":"The documents herein define the custom parameters of the Ozone Instance of the Executor Accord Primitive, if any.","contentHash":"be003f7a447f9026ea8e107c73c8b00f811e9d616575d90ced4c5ffb41a29c34","addressRefs":[]},"ce03f140-55da-403f-9ce2-28e27177fe6a":{"id":"ce03f140-55da-403f-9ce2-28e27177fe6a","doc_no":"A.6.1.1.8.2.2.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10049,"content":"The documents herein define the process for the ongoing management of the Ozone Instance of the Executor Accord Primitive.","contentHash":"03daa9d3ebfb53ae8a57e22ffb990501ed356259a7b153b51d2b35cb6013c74b","addressRefs":[]},"ec907cef-df83-4502-ada8-920c3e020e1b":{"id":"ec907cef-df83-4502-ada8-920c3e020e1b","doc_no":"A.6.1.1.8.2.2.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10050,"content":"The documents herein contain data relevant to the Ozone Instance of the Executor Accord Primitive.","contentHash":"edd3e28207fedf752584ef2eb5e88f52b3ff82d2d0a5d7cfed80703bd5ad5d72","addressRefs":[]},"e60e7340-7e86-4207-b725-2b1380f637d4":{"id":"e60e7340-7e86-4207-b725-2b1380f637d4","doc_no":"A.6.1.1.8.2.2.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10051,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"15f11c14-4ae7-4e7b-84c8-211fb93b6f8b":{"id":"15f11c14-4ae7-4e7b-84c8-211fb93b6f8b","doc_no":"A.6.1.1.8.2.2.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10052,"content":"The materials associated with Operational GovOps review during the Invocation of this Instance are contained herein.","contentHash":"4d9cf82f10b4116dc01ad201efd474911d68cc99e9ef9477435cf5f1402ce280","addressRefs":[]},"b2ef0e67-5e45-43f0-a62b-6a3669db4cc8":{"id":"b2ef0e67-5e45-43f0-a62b-6a3669db4cc8","doc_no":"A.6.1.1.8.2.2.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10053,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"0bf3b18f-3381-4f7d-be8d-20edbe53d69d":{"id":"0bf3b18f-3381-4f7d-be8d-20edbe53d69d","doc_no":"A.6.1.1.8.2.2.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10054,"content":"The Instances of the Executor Accord Primitive with `Completed` Status are stored herein.","contentHash":"a4e5978668a8284ab676cde2d632a5a3f637127becf9530de1e5aa06826aabdf","addressRefs":[]},"896f5790-396e-45c5-a907-b01a6368985a":{"id":"896f5790-396e-45c5-a907-b01a6368985a","doc_no":"A.6.1.1.8.2.2.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10055,"content":"The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.2.1.2 - Active Instances](e7f6dd4d-2943-40a2-ba6c-8c738e5fc0bd).","contentHash":"6c302b6692e63c7c45f3192fa4562a65ecd3b28b42ae22a7fc61d68a3b5b544e","addressRefs":[]},"526f3ff3-e9d5-4de3-a7d7-60baf979e471":{"id":"526f3ff3-e9d5-4de3-a7d7-60baf979e471","doc_no":"A.6.1.1.8.2.2.2","title":"Root Edit Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10056,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instance of the Root Edit Primitive. See [A.2.2.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d).","contentHash":"08f02841c48ba94979b84e2fdd716719da30e72ec697b65babd2dd75ca2b91a4","addressRefs":[]},"b872e10d-6077-4a05-af0d-e03faed0f48a":{"id":"b872e10d-6077-4a05-af0d-e03faed0f48a","doc_no":"A.6.1.1.8.2.2.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10057,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Root Edit Primitive.","contentHash":"f56064c101325e707afafc58e2c0912c63e6ed9108aa1429a643f6de261fbf38","addressRefs":[]},"abdedb78-417e-4b68-9226-f0cd5e0ebfc3":{"id":"abdedb78-417e-4b68-9226-f0cd5e0ebfc3","doc_no":"A.6.1.1.8.2.2.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10058,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"1aa5f0b4-7024-4b67-ac0e-85fdb34dc515":{"id":"1aa5f0b4-7024-4b67-ac0e-85fdb34dc515","doc_no":"A.6.1.1.8.2.2.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10059,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`.","contentHash":"cfe05571defe01200e8275b113c701b9594bb1e0da7cb54821e20968453d43fb","addressRefs":[]},"8b6cdff1-641d-473c-8942-98dae58c707e":{"id":"8b6cdff1-641d-473c-8942-98dae58c707e","doc_no":"A.6.1.1.8.2.2.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10060,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.8.2.2.2.2.1 - Single Instance Configuration Document](c49e173d-f052-4825-bab1-0506c3db9353).","contentHash":"67c83fb0547423d6882cd425dd20cda2341c7a6f2a9c2153f1c1f045c2d6e37b","addressRefs":[]},"028d65c5-a40b-43cc-9db7-7f313a3ff257":{"id":"028d65c5-a40b-43cc-9db7-7f313a3ff257","doc_no":"A.6.1.1.8.2.2.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10061,"content":"This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`.","contentHash":"4f29504e0d8ea8265eac5fa5f0e43d36bc25b44530ec5b70182a50028cf3b27f","addressRefs":[]},"fd4b8028-02aa-4647-aef8-153d5b8afd6c":{"id":"fd4b8028-02aa-4647-aef8-153d5b8afd6c","doc_no":"A.6.1.1.8.2.2.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10062,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"0d0e614d-32d3-4ae3-9c46-113dcc0ec144":{"id":"0d0e614d-32d3-4ae3-9c46-113dcc0ec144","doc_no":"A.6.1.1.8.2.2.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10063,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"e29ca48b-43b6-499d-94eb-136f8e9f8310":{"id":"e29ca48b-43b6-499d-94eb-136f8e9f8310","doc_no":"A.6.1.1.8.2.2.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10064,"content":"The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here.","contentHash":"c256e721314fbf3b9ca35a4ef02dcd0e2ded20ad7cbd8d48770bf8dc02e9954c","addressRefs":[]},"c4ec3e46-3c74-4277-9207-09fd89fa46f4":{"id":"c4ec3e46-3c74-4277-9207-09fd89fa46f4","doc_no":"A.6.1.1.8.2.2.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10065,"content":"The subtrees for failed Invocations of the Root Edit Primitive are stored here.","contentHash":"c5f2cb30371a3c3a38cd53839e258414392f1e64fef2db65d5ed2988e012c872","addressRefs":[]},"63d1d8bd-b89f-4584-87d1-2a0a971d36a1":{"id":"63d1d8bd-b89f-4584-87d1-2a0a971d36a1","doc_no":"A.6.1.1.8.2.2.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10066,"content":"The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here.","contentHash":"653de7f9e16873199fb2c5e8f3f04b7a27c8905a8a6ac9d5b01c5dd2e559ec04","addressRefs":[]},"8d989fff-4cd4-4742-89eb-307e8b2a3404":{"id":"8d989fff-4cd4-4742-89eb-307e8b2a3404","doc_no":"A.6.1.1.8.2.2.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10067,"content":"The Instances of the Root Edit Primitive with `Active` Status are stored herein.","contentHash":"04ca22f0fd847ca52f93f9d311003ec1f6525202bfb31f7c246a729a4882c49b","addressRefs":[]},"c49e173d-f052-4825-bab1-0506c3db9353":{"id":"c49e173d-f052-4825-bab1-0506c3db9353","doc_no":"A.6.1.1.8.2.2.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10068,"content":"The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance.","contentHash":"305f9f114ee5da3c32a7c56d978a47af33efa6452d76b3ce86ab78f14c1c4ad5","addressRefs":[]},"3da1740c-9f67-4e40-9111-5cfee617e244":{"id":"3da1740c-9f67-4e40-9111-5cfee617e244","doc_no":"A.6.1.1.8.2.2.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10069,"content":"The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [A.6.1.1.8.2.2.2.2.1.2 - Operational Process Definition](881b6df0-56fb-498e-bc1a-d9028c0151ad).","contentHash":"7afe97e157f9775fcf9fa6b5f9c1bdf88b9189eebd4aefe60ef3e90870d0cefa","addressRefs":[]},"881b6df0-56fb-498e-bc1a-d9028c0151ad":{"id":"881b6df0-56fb-498e-bc1a-d9028c0151ad","doc_no":"A.6.1.1.8.2.2.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10070,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 7 Agent Artifact. Information on Launch Agent 7 governance that is unrelated to the use of the Root Edit Primitive is located at [A.6.1.1.8.3.1 - Governance Information Unrelated To Root Edit Primitive](c18d1d28-3b1f-4173-87dd-f697ab2d2539).","contentHash":"02c2efd9e2b7bbe26fa23cf87c149e3144173ce69976502af0ed1ff9e96f1845","addressRefs":[]},"9d637b4a-868b-47c1-bbaf-099aeede1da2":{"id":"9d637b4a-868b-47c1-bbaf-099aeede1da2","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10071,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 7 Agent Artifact in routine or normal conditions (i.e., non-emergency situations).","contentHash":"633c54bc46589aa3091f1e9d33d6bb3b58089f8a79963c0c62c1917443dfde19","addressRefs":[]},"fd43ac8d-5461-46e6-8902-4526ef677e3a":{"id":"fd43ac8d-5461-46e6-8902-4526ef677e3a","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.1","title":"Root Edit Proposal Submission","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10072,"content":"The Root Edit process begins with an AGENT7 token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. An AGENT7 token holder must hold at least 1% of the circulating token supply to submit a proposal. The proposal must also be posted on the Sky Forum under the \"Launch Agent 7 Prime\" category.","contentHash":"a5a51cddfd39e06f9e0102a1719e04ba9621a732db392d85b9d0ff8f02667e69","addressRefs":[]},"0048952f-30e2-484a-975a-62cc9e84c715":{"id":"0048952f-30e2-484a-975a-62cc9e84c715","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.1.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10073,"content":"Until the Powerhouse system supports submitting Artifact Edit Proposals, AGENT7 token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the \"Launch Agent 7 Prime\" category. The title of the post must include the text \"Launch Agent 7 Artifact Edit Proposal\". The post must include cryptographic proof that the author controls an account holding the required percentage of the total Launch Agent 7 token supply specified in [A.6.1.1.8.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission](fd43ac8d-5461-46e6-8902-4526ef677e3a).","contentHash":"51694de2b5314e38ff6f746d7573a956e502c07b5959b811a60baf2116c4be85","addressRefs":[]},"089948f6-f451-4541-bdf5-5cb4113332fa":{"id":"089948f6-f451-4541-bdf5-5cb4113332fa","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.2","title":"Root Edit Expert Advisor Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10074,"content":"A future iteration of the Launch Agent 7 Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis.","contentHash":"7f4ace44ff2b2b30190e1a3c649553cbfae120e8d718f25efaace1ee9965794d","addressRefs":[]},"7122bf98-1167-4a50-b411-90254d9d4bb7":{"id":"7122bf98-1167-4a50-b411-90254d9d4bb7","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.3","title":"Root Edit Proposal Review By Operational Facilitator","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10075,"content":"Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment.\n\nIf the proposal is aligned, the Operational Facilitator must respond to the Forum post to announce their finding. In this Forum post, the Operational Facilitator must also confirm that the proposal is feasible for Operational GovOps to operationalize.\n\nIf the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it.","contentHash":"3d695884c752507d7f445ad3a572c67b44863196d11108fb8a300dc2e71ce3e7","addressRefs":[]},"0c0209b7-fe8c-4d94-8daa-00057bb135cf":{"id":"0c0209b7-fe8c-4d94-8daa-00057bb135cf","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.4","title":"Root Edit Token Holder Vote","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10076,"content":"Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and Launch Agent 7 Artifact, the Operational Facilitator next triggers a Snapshot poll to allow token holders to vote on the proposal. The poll is open for three (3) days. A poll must have at least 10% of the circulating token supply participating and must have 50% of votes in favor to be approved.","contentHash":"7cb61661d1f53c38827182bd451edbe4c14ca146a3b0642e18666fa04cb7a1fb","addressRefs":[]},"f121258d-27b1-443a-8734-f170667dde3d":{"id":"f121258d-27b1-443a-8734-f170667dde3d","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.5","title":"Root Edit Artifact Update","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10077,"content":"At the conclusion of the poll, if the proposal is approved, the Operational Facilitator submits the edit to Powerhouse to formally update the Agent Artifact. Regardless of the outcome, the Operational Facilitator updates the Powerhouse System to include the result of the vote, including any pertinent documents.","contentHash":"0620feea73a69839d388548657693d419def3964daa08681199d3545a6ed96b7","addressRefs":[]},"f46cd437-80bb-4f7c-b8c0-eef464465349":{"id":"f46cd437-80bb-4f7c-b8c0-eef464465349","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.5.1","title":"Short-Term Transitionary Measures","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10078,"content":"Until the Powerhouse system supports updating Agent Artifacts, the Operational Facilitator works with the Core Facilitator to update the Atlas GitHub repository located at [https://github.com/sky-ecosystem/next-gen-atlas/pulls](https://github.com/sky-ecosystem/next-gen-atlas/pulls) to reflect proposals approved by Prime Governance.","contentHash":"2695ca3071afa400d6f129543dc028369e9e9e8147956c0ffbfc835aa656ee9e","addressRefs":[]},"0049ae2e-37a7-4bab-ab08-461caba3dcbb":{"id":"0049ae2e-37a7-4bab-ab08-461caba3dcbb","doc_no":"A.6.1.1.8.2.2.2.2.1.2.1.6","title":"Artifact Edit Restrictions","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10079,"content":"The Launch Agent 7 Artifact cannot be edited in any way that violates the Sky Core Atlas or its specifications of the Sky Primitives, or in any way that is otherwise misaligned. The Operational Facilitator must enforce this rule through their review of Artifact Edit Proposals.","contentHash":"3fa759304b189cb1c9060a6cf335f7e03272fdc314e1bb77ce68c5098124f2a6","addressRefs":[]},"cfa59ab2-4a7e-4bcd-96b9-e64b295b372e":{"id":"cfa59ab2-4a7e-4bcd-96b9-e64b295b372e","doc_no":"A.6.1.1.8.2.2.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10080,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 7 Agent Artifact in non-routine conditions.","contentHash":"8609ac2f2346e14302ced1a90a13d6a3632f3d4b17d3b95039e445eda9c1bc45","addressRefs":[]},"3fe13a8c-48dc-4b6b-a0a8-a1b2ba014866":{"id":"3fe13a8c-48dc-4b6b-a0a8-a1b2ba014866","doc_no":"A.6.1.1.8.2.2.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10081,"content":"The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 7 Agent Artifact in emergency situations.","contentHash":"528a993dcb171c8b815857c2f4f67d1df50e74d3f947a87c412ba9fe3708b7d0","addressRefs":[]},"ac18c8ca-174b-4504-85e2-eaef85d3e375":{"id":"ac18c8ca-174b-4504-85e2-eaef85d3e375","doc_no":"A.6.1.1.8.2.2.2.2.1.2.3.1","title":"Root Edit Voting Process In Emergency Situations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10082,"content":"In an Emergency Situation, as defined by the Sky Core Atlas in [A.1.9.1.1 - Definition Of Emergency Situations](5eafb29e-84a0-4a53-a798-3f958c880225), the Operational Facilitator may allow a Root Edit to occur more quickly than the timeline specified above. Where feasible, the Operational Facilitator should announce the decision to deploy the emergency Root Edit protocol and provide their reasoning via a public Sky Forum post (under the \"Launch Agent 7 Prime\" category), unless doing so would endanger Launch Agent 7 or its users.","contentHash":"dbd308c598787abe0a19c74f981eca244eaf46088cf04d75524ad987aedb46d4","addressRefs":[]},"69761497-4868-413b-965d-ff1679ee3ed7":{"id":"69761497-4868-413b-965d-ff1679ee3ed7","doc_no":"A.6.1.1.8.2.2.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10083,"content":"The documents herein contain data relevant to the Single Instance of the Root Edit Primitive.","contentHash":"a6fb3a53ef282e33d1f3caf2db6a8e0d436c4e3b05575893af429226589eaa16","addressRefs":[]},"d29e42dd-0675-47b8-b0c9-8e88a7f17f14":{"id":"d29e42dd-0675-47b8-b0c9-8e88a7f17f14","doc_no":"A.6.1.1.8.2.2.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10084,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"f8798270-5625-496f-87f5-b79f8981fd54":{"id":"f8798270-5625-496f-87f5-b79f8981fd54","doc_no":"A.6.1.1.8.2.2.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10085,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"19d6d80e-edfc-45ed-9909-8130a006c542":{"id":"19d6d80e-edfc-45ed-9909-8130a006c542","doc_no":"A.6.1.1.8.2.2.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10086,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"2ce26124-5604-42ae-a3ab-9790a4a9a702":{"id":"2ce26124-5604-42ae-a3ab-9790a4a9a702","doc_no":"A.6.1.1.8.2.2.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10087,"content":"The Instances of the Root Edit Primitive with `Completed` Status are contained herein.","contentHash":"99f8734d0ba09ab3234fb6208647ad371c008b0d61ad51371f64a6e81b863eec","addressRefs":[]},"719e16f2-bd1b-4ee3-b86b-7e02de533ac5":{"id":"719e16f2-bd1b-4ee3-b86b-7e02de533ac5","doc_no":"A.6.1.1.8.2.2.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10088,"content":"Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"a16a06a18826731dc930cd494066c0ce645279066296eace520269524252946d","addressRefs":[]},"103c14cc-c21d-403b-996e-38f661a63093":{"id":"103c14cc-c21d-403b-996e-38f661a63093","doc_no":"A.6.1.1.8.2.2.3","title":"Light Agent Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10089,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Light Agent Primitive. See [A.2.2.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90).","contentHash":"095db4f6e7d8a3321a692a624081b3509d955cf451bbe53dba2c20e54d18ccaf","addressRefs":[]},"c45b24ee-844e-4fa4-bdd5-6f4af842fbea":{"id":"c45b24ee-844e-4fa4-bdd5-6f4af842fbea","doc_no":"A.6.1.1.8.2.2.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10090,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Light Agent Primitive.","contentHash":"6c7bfb5ac7f562403d87a8ba52f68e1d08c28f894965cdd246274a87fce42cd0","addressRefs":[]},"8d69c6f7-299f-470f-97fd-ba16bc3077b6":{"id":"8d69c6f7-299f-470f-97fd-ba16bc3077b6","doc_no":"A.6.1.1.8.2.2.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10091,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"52113994-f0f0-43a7-859d-01ba0890d5c4":{"id":"52113994-f0f0-43a7-859d-01ba0890d5c4","doc_no":"A.6.1.1.8.2.2.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10092,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`.","contentHash":"5f35c4760a519e7bdc966de70cdd180e9df441ed4ef4224ed30702ab18663c39","addressRefs":[]},"16b11dbf-2840-4db2-9f50-76f3199d4af3":{"id":"16b11dbf-2840-4db2-9f50-76f3199d4af3","doc_no":"A.6.1.1.8.2.2.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10093,"content":"This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`.","contentHash":"5defba29f7352fec5b7b0bce0d0f2e1aa54c49bf2563f9ffffc33bb789f15879","addressRefs":[]},"bd37edb0-6a4b-4272-afa1-8fdc9e46434f":{"id":"bd37edb0-6a4b-4272-afa1-8fdc9e46434f","doc_no":"A.6.1.1.8.2.2.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10094,"content":"This document contains a Directory of all prospective Instances of the Light Agent Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.2.3.1.2 - Active Instances Directory](52113994-f0f0-43a7-859d-01ba0890d5c4), whereas failed Invocations are Archived in [A.6.1.1.8.2.2.3.1.5 - Hub Data Repository](4c37b870-fe4e-4313-8b31-5782ee1f2f13).","contentHash":"d8bdd60bf015e6c6d3e7cdc386bd5d7b38211bf975643433da60f36407788a80","addressRefs":[]},"4c37b870-fe4e-4313-8b31-5782ee1f2f13":{"id":"4c37b870-fe4e-4313-8b31-5782ee1f2f13","doc_no":"A.6.1.1.8.2.2.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10095,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"18c6c3c3-e208-4f6a-a7d3-9d984fdebad0":{"id":"18c6c3c3-e208-4f6a-a7d3-9d984fdebad0","doc_no":"A.6.1.1.8.2.2.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10096,"content":"The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here.","contentHash":"1fbc875aee70f45e616b730f6d850e921815a30de9ddf0f6c8d2c2b8aa6b1ac0","addressRefs":[]},"b132a4d7-61fe-4f2c-bd6c-0af62795f044":{"id":"b132a4d7-61fe-4f2c-bd6c-0af62795f044","doc_no":"A.6.1.1.8.2.2.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10097,"content":"The subtrees for failed Invocations of the Light Agent Primitive are stored here.","contentHash":"01cd6fa62690773185004f3c28d25d82d62623db61f39c681b27ce5203719288","addressRefs":[]},"af6871dc-4623-4e1f-9282-1e5c658bf879":{"id":"af6871dc-4623-4e1f-9282-1e5c658bf879","doc_no":"A.6.1.1.8.2.2.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10098,"content":"The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here.","contentHash":"20673e7b1f22ecc3de0fc7961bb07892f8f3a89521de36cc0e2f28c36a684233","addressRefs":[]},"7b8c9d42-3412-4bc0-8439-8178b3b40bf0":{"id":"7b8c9d42-3412-4bc0-8439-8178b3b40bf0","doc_no":"A.6.1.1.8.2.2.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10099,"content":"The Instances of the Light Agent Primitive with `Active` Status are stored herein.","contentHash":"f10a768b2fc1d73d3764f26c49fbbd246cdedd882db437c18dc9aed1fc0a8133","addressRefs":[]},"a0bdc146-76ae-4b11-94ea-523b9151e417":{"id":"a0bdc146-76ae-4b11-94ea-523b9151e417","doc_no":"A.6.1.1.8.2.2.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10100,"content":"The Instances of the Light Agent Primitive with `Completed` Status are contained herein.","contentHash":"d806e6896c9f1200303e435e5ab03bd4b7a106fd11fb30487244e1f81b9377d6","addressRefs":[]},"60754835-87dc-4921-b13c-f9ee34d619ca":{"id":"60754835-87dc-4921-b13c-f9ee34d619ca","doc_no":"A.6.1.1.8.2.2.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10101,"content":"The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.2.3.2 - Active Instances](7b8c9d42-3412-4bc0-8439-8178b3b40bf0).","contentHash":"b9c2d9e8638baa42b06985bb9aca57f7fba55646f28de7cb99c509f5ef64316a","addressRefs":[]},"137a06da-2db3-4762-9cad-d26a9fc99d4b":{"id":"137a06da-2db3-4762-9cad-d26a9fc99d4b","doc_no":"A.6.1.1.8.2.3","title":"Ecosystem Upkeep Primitives","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10102,"content":"The documents herein implement the [A.2.2.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc).","contentHash":"c38339d728a93642c549fdd95d4c174b69767b67ad352df2d8f13779f654b610","addressRefs":[]},"235b6631-e033-4c9e-b31d-3a44feab2691":{"id":"235b6631-e033-4c9e-b31d-3a44feab2691","doc_no":"A.6.1.1.8.2.3.1","title":"Ecosystem Upkeep Fee Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10103,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instance of the Ecosystem Upkeep Fee Primitive. See [A.2.2.6.1 - Ecosystem Upkeep Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28).","contentHash":"fdde66776d0a6beff4bbe3b629b5d47303523470fcca98e2cd6300fbcbdeeec2","addressRefs":[]},"2960ee87-c20d-4172-b938-5007663774eb":{"id":"2960ee87-c20d-4172-b938-5007663774eb","doc_no":"A.6.1.1.8.2.3.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10104,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Ecosystem Upkeep Fee Primitive.","contentHash":"3dc0ec696f3908cab73485da869e43fa3c2c18bc3d8ebe28a540ff10cdefa873","addressRefs":[]},"dc299e36-9c46-4b13-81cd-8d4fc85f31d3":{"id":"dc299e36-9c46-4b13-81cd-8d4fc85f31d3","doc_no":"A.6.1.1.8.2.3.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10105,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"fe90717a-9451-4f01-a5fe-2663342f0283":{"id":"fe90717a-9451-4f01-a5fe-2663342f0283","doc_no":"A.6.1.1.8.2.3.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10106,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Active`.","contentHash":"1be1ecc8f8a482fc29df853a5d729d4a886991eb2bfec6f8086800ef8be88f49","addressRefs":[]},"5c8bdca5-4b57-413a-81fc-bf39f991e12b":{"id":"5c8bdca5-4b57-413a-81fc-bf39f991e12b","doc_no":"A.6.1.1.8.2.3.1.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10107,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.8.2.3.1.2.1 - Single Instance Configuration Document](2fa1a658-3588-45cd-a6e4-ceb0cc8f57d8).","contentHash":"bd88005e576278c5ec6009f3cbd67d556d309c8dabe34451a7d6f32c68644bd6","addressRefs":[]},"0ea3700e-3d71-472e-962e-3d3a16e0a020":{"id":"0ea3700e-3d71-472e-962e-3d3a16e0a020","doc_no":"A.6.1.1.8.2.3.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10108,"content":"This document contains a Directory of all Instances of the Ecosystem Upkeep Fee Primitive with Instance status of `Completed`.","contentHash":"12c223f589b9fddf51316fad8ce99e3c7256363179d8b09a863e378198ff6068","addressRefs":[]},"dea9d796-cd57-413b-9793-1e4d7c46d7d1":{"id":"dea9d796-cd57-413b-9793-1e4d7c46d7d1","doc_no":"A.6.1.1.8.2.3.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10109,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"b801d192-aaf7-4b96-aca4-a0574210787f":{"id":"b801d192-aaf7-4b96-aca4-a0574210787f","doc_no":"A.6.1.1.8.2.3.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10110,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"5ad0a20f-9776-45f7-a616-d23ba788c826":{"id":"5ad0a20f-9776-45f7-a616-d23ba788c826","doc_no":"A.6.1.1.8.2.3.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10111,"content":"The subtrees for archived Invocations and Instances of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"99d9e0b3392b67adb252a92342550df0556170326c8fd1a566275b7bf96d900f","addressRefs":[]},"8c9cd3a4-82ed-4117-8066-bd77b2c0d922":{"id":"8c9cd3a4-82ed-4117-8066-bd77b2c0d922","doc_no":"A.6.1.1.8.2.3.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10112,"content":"The subtrees for failed Invocations of the Ecosystem Upkeep Fee Primitive are stored here.","contentHash":"a64cdf71981a78a7e7512d2a38029034507f09e53bbf9e2d59eb8a06bc33ff7f","addressRefs":[]},"bddcc7eb-5d2d-402b-a2b7-dc8e2be70e1c":{"id":"bddcc7eb-5d2d-402b-a2b7-dc8e2be70e1c","doc_no":"A.6.1.1.8.2.3.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10113,"content":"The subtrees for Instances of the Ecosystem Upkeep Fee Primitive with `Suspended` Status are stored here.","contentHash":"d9e46aa9bf4952c494a71a8f91704e927a0a639509adb3b631fb37465036c161","addressRefs":[]},"f2c71db2-efde-4d80-800b-945f8ca1dab0":{"id":"f2c71db2-efde-4d80-800b-945f8ca1dab0","doc_no":"A.6.1.1.8.2.3.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10114,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Active` Status are stored herein.","contentHash":"21952f1ba0a31a755266db51a467b18d96c28f1d6d1bfad918cdc272679dd1be","addressRefs":[]},"2fa1a658-3588-45cd-a6e4-ceb0cc8f57d8":{"id":"2fa1a658-3588-45cd-a6e4-ceb0cc8f57d8","doc_no":"A.6.1.1.8.2.3.1.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10115,"content":"The documents herein contain the Instance Configuration Document for the Single Ecosystem Upkeep Fee Primitive Instance.","contentHash":"36c6de0c12585c8afe3e90a43ada194817270b2d2b73dcb7fcc583fdceaedd03","addressRefs":[]},"9f1da224-aad0-4903-8e74-7dbd1dc6c30e":{"id":"9f1da224-aad0-4903-8e74-7dbd1dc6c30e","doc_no":"A.6.1.1.8.2.3.1.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10116,"content":"The documents herein define the parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"7bafbee5b5479ed3a0a927356980b07077cce7313d77fc3560ac735c25770879","addressRefs":[]},"b5a5b8d8-7022-46a7-a351-dc767a5618c4":{"id":"b5a5b8d8-7022-46a7-a351-dc767a5618c4","doc_no":"A.6.1.1.8.2.3.1.2.1.1.1","title":"Terms","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10117,"content":"Launch Agent 7 will pay 0.50% of its market capitalization per year in USDS.","contentHash":"ba0fa076965a8b788be6bf342fdd4e9e254ecf27d1e71bbfbce03922d3c31796","addressRefs":[]},"f5b52d8f-a131-428a-bc3b-bd87d2493ecb":{"id":"f5b52d8f-a131-428a-bc3b-bd87d2493ecb","doc_no":"A.6.1.1.8.2.3.1.2.1.1.2","title":"Custom Instance Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10118,"content":"The documents herein define the custom parameters of the Single Instance of the Ecosystem Upkeep Fee Primitive, if any.","contentHash":"18bdbede7a76e3627d582ad8c1efe616d40d6c222ab90c9e4aecab552fc234d7","addressRefs":[]},"5a14c374-344f-4073-bbb2-562e1665c2be":{"id":"5a14c374-344f-4073-bbb2-562e1665c2be","doc_no":"A.6.1.1.8.2.3.1.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10119,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"f383884fea5fc1a0a5721685991958137227479b1d16938173f95acdda5a305f","addressRefs":[]},"8832e413-3b06-4724-b5eb-eccabc08db82":{"id":"8832e413-3b06-4724-b5eb-eccabc08db82","doc_no":"A.6.1.1.8.2.3.1.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10120,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"1f3cfe5696a76eba6021a559eb9f2b40f94799349e650af498953648e01d9fec","addressRefs":[]},"ee639561-265a-42c1-be31-10e61e817ad0":{"id":"ee639561-265a-42c1-be31-10e61e817ad0","doc_no":"A.6.1.1.8.2.3.1.2.1.2.1.1","title":"Process Definition For Upkeep Fee Payment","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10121,"content":"The process to pay 0.50% of Launch Agent 7's market capitalization per year in USDS will be specified in future iterations of the Launch Agent 7 Artifact.","contentHash":"8a9c2179106a4f4fe03861c56e7e8e94b199522c6a0be013ec035565ca6232d7","addressRefs":[]},"fed0b0c1-a7ee-4839-af72-c6ca6257beca":{"id":"fed0b0c1-a7ee-4839-af72-c6ca6257beca","doc_no":"A.6.1.1.8.2.3.1.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10122,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"2291d9dc01674b336a87b3a7e8b2a023e3e090265d2de285f1f20b06a6fe5f59","addressRefs":[]},"4aaab4a9-e619-4343-a308-791a5a000ee6":{"id":"4aaab4a9-e619-4343-a308-791a5a000ee6","doc_no":"A.6.1.1.8.2.3.1.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10123,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Ecosystem Upkeep Fee Primitive.","contentHash":"cc5270c5707b61ed87f9b2cb4bf622e12adcd4dd13eb81162332af981323e403","addressRefs":[]},"be200704-5152-4884-8acb-4d0ef2f7307c":{"id":"be200704-5152-4884-8acb-4d0ef2f7307c","doc_no":"A.6.1.1.8.2.3.1.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10124,"content":"The documents herein contain data relevant to the Single Instance of the Ecosystem Upkeep Fee Primitive.","contentHash":"11c0a5174d77e3f8e40a3f20a97f37847d0cc1fb452010c9b5b72e5be36b8e2f","addressRefs":[]},"1126acc9-9fb2-493b-b6ed-78cdccb75c5a":{"id":"1126acc9-9fb2-493b-b6ed-78cdccb75c5a","doc_no":"A.6.1.1.8.2.3.1.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10125,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"4d4d1a09-cb35-4582-bdb1-919ec4e52a16":{"id":"4d4d1a09-cb35-4582-bdb1-919ec4e52a16","doc_no":"A.6.1.1.8.2.3.1.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10126,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"c828c63f-634c-42f6-8741-27edbd83ff68":{"id":"c828c63f-634c-42f6-8741-27edbd83ff68","doc_no":"A.6.1.1.8.2.3.1.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10127,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"6aca1d4d-5962-4215-a778-cdad996dc4f8":{"id":"6aca1d4d-5962-4215-a778-cdad996dc4f8","doc_no":"A.6.1.1.8.2.3.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10128,"content":"The Instances of the Ecosystem Upkeep Fee Primitive with `Completed` Status are stored herein.","contentHash":"f82f53523cffe4e52cb60902f56d8d3590433b7ac65982256a377a463bbbf1de","addressRefs":[]},"92bfea11-2401-4744-8911-59c22d891b77":{"id":"92bfea11-2401-4744-8911-59c22d891b77","doc_no":"A.6.1.1.8.2.3.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10129,"content":"Because the Ecosystem Upkeep Fee Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"efadf2debaf71b3ad67281d94c49425058cf2ae25b30e216e362d49553d58a4f","addressRefs":[]},"a36bf711-7951-497c-9c4b-c761dbff351a":{"id":"a36bf711-7951-497c-9c4b-c761dbff351a","doc_no":"A.6.1.1.8.2.3.2","title":"Upkeep Rebate Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10130,"content":"The documents herein contain all data and specifications for Launch Agent 7's instance of the Upkeep Rebate Primitive. See [A.2.2.6.2 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988).","contentHash":"224fc955f061bb787754df3baf88b764aa0cdba3f3609fd0aa4992d30014e3e1","addressRefs":[]},"e087c1a6-3f6f-4309-952d-71b74691c6de":{"id":"e087c1a6-3f6f-4309-952d-71b74691c6de","doc_no":"A.6.1.1.8.2.3.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10131,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Upkeep Rebate Primitive.","contentHash":"7eedf5f733bcf8b421b4427cbbc7d3e9d96eb08c8ebe3aa5b4355edad4242e0a","addressRefs":[]},"9479c841-04d0-4a76-bec8-3255106fcc47":{"id":"9479c841-04d0-4a76-bec8-3255106fcc47","doc_no":"A.6.1.1.8.2.3.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10132,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"a986a180-e2a6-40bb-aec5-58e6584d958e":{"id":"a986a180-e2a6-40bb-aec5-58e6584d958e","doc_no":"A.6.1.1.8.2.3.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10133,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`.","contentHash":"e208747857dd157c15f8d54f356aca79d28af90848327b70768783519694cf44","addressRefs":[]},"b05793b0-6d46-448f-9e83-41ee55141eb0":{"id":"b05793b0-6d46-448f-9e83-41ee55141eb0","doc_no":"A.6.1.1.8.2.3.2.1.2.1","title":"Single Instance Configuration Document Location","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10134,"content":"This Instance’s associated Instance Configuration Document is located at [A.6.1.1.8.2.3.2.2.1 - Single Instance Configuration Document](24e3d323-e9a4-4bb3-ba4d-ae92aa745e96).","contentHash":"fc37460080835237b8c091bd217ca0b1c0fd50e6698c327febacc2008dcc01f0","addressRefs":[]},"4f195e95-65db-432e-80ea-9b77a8b2c355":{"id":"4f195e95-65db-432e-80ea-9b77a8b2c355","doc_no":"A.6.1.1.8.2.3.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10135,"content":"This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`.","contentHash":"d9322cb9889fdf4f9376a54b2e6d886db4de6b8cbcb64af4f76bbab4a9648902","addressRefs":[]},"98e6bca4-9981-4e38-814b-8394eeb62778":{"id":"98e6bca4-9981-4e38-814b-8394eeb62778","doc_no":"A.6.1.1.8.2.3.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10136,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"1bdaf050-86c4-44a1-8926-a6d083e0ac65":{"id":"1bdaf050-86c4-44a1-8926-a6d083e0ac65","doc_no":"A.6.1.1.8.2.3.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10137,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"20b38bb0-bcdc-4ded-ac96-2e445e10afc4":{"id":"20b38bb0-bcdc-4ded-ac96-2e445e10afc4","doc_no":"A.6.1.1.8.2.3.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10138,"content":"The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here.","contentHash":"e9a0669807cfcd6a6e4b2a56f47499952794bd2fb164ca3499f635bc107b4600","addressRefs":[]},"62a31c8c-2e86-4df6-a422-f76cfa6610e5":{"id":"62a31c8c-2e86-4df6-a422-f76cfa6610e5","doc_no":"A.6.1.1.8.2.3.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10139,"content":"The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here.","contentHash":"d9af1cd58a214790fc38942962cb6d03f3c323a18ebc3e982158b60382d8120a","addressRefs":[]},"b13c4e9f-7366-4ca3-aeb2-3f7666127a02":{"id":"b13c4e9f-7366-4ca3-aeb2-3f7666127a02","doc_no":"A.6.1.1.8.2.3.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10140,"content":"The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here.","contentHash":"5decf15b66ca41fa491816ea30ebeae4b7316206f0e6f7b4e2cf3fcd6e46679c","addressRefs":[]},"b5197e9e-014b-4527-a1b1-399cf3475bef":{"id":"b5197e9e-014b-4527-a1b1-399cf3475bef","doc_no":"A.6.1.1.8.2.3.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10141,"content":"The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein.","contentHash":"7eae17c7e7edf9cfa4c2cac922926376ef65281aa5c06d2ea5db4ada269a3c40","addressRefs":[]},"24e3d323-e9a4-4bb3-ba4d-ae92aa745e96":{"id":"24e3d323-e9a4-4bb3-ba4d-ae92aa745e96","doc_no":"A.6.1.1.8.2.3.2.2.1","title":"Single Instance Configuration Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10142,"content":"The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance.","contentHash":"7403a8a9bb5fec51747c20feadef756250ff8e8da1d2ee9dbb9ea8799c90bb4e","addressRefs":[]},"74e0d2e3-fa72-48d8-b1f1-5f7dc0caacbc":{"id":"74e0d2e3-fa72-48d8-b1f1-5f7dc0caacbc","doc_no":"A.6.1.1.8.2.3.2.2.1.1","title":"Parameters","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10143,"content":"Every Prime Agent is entitled to the Upkeep Rebate Primitive for tokens of other Prime Agents that they hold. Because this right automatically applies, there are no parameters.","contentHash":"38d5c22d74040528ea1613199c7267616643ad3fc1798183cc4b550baa494a72","addressRefs":[]},"ce3e37b2-5061-454e-8b5e-ba08e1e66bb9":{"id":"ce3e37b2-5061-454e-8b5e-ba08e1e66bb9","doc_no":"A.6.1.1.8.2.3.2.2.1.2","title":"Operational Process Definition","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10144,"content":"The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive.","contentHash":"c26872bfb0d314e4461647b9fa808427456c5db6aab7c594008d832094691e67","addressRefs":[]},"33aac9cf-306f-46ce-bdaf-84fdcafcedf3":{"id":"33aac9cf-306f-46ce-bdaf-84fdcafcedf3","doc_no":"A.6.1.1.8.2.3.2.2.1.2.1","title":"Routine Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10145,"content":"This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"9c2fde3c18fae466a69ac6c62fd247a4d72636be191a4cadb9d1e9258fbf99a0","addressRefs":[]},"67240dea-8bc1-4ac7-9da5-7079b7af6424":{"id":"67240dea-8bc1-4ac7-9da5-7079b7af6424","doc_no":"A.6.1.1.8.2.3.2.2.1.2.1.1","title":"Launch Agent 7 Holds Tokens Of Other Agents In Its SubProxy Account","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10146,"content":"Launch Agent 7 keeps all tokens of other Agents it holds in its SubProxy account.","contentHash":"1dc228a223f6e943d146ca2587f535a52d871633b039a8a45559fb6b0a99f3dc","addressRefs":[]},"22e8780f-64f2-416b-93b5-ef5584583b15":{"id":"22e8780f-64f2-416b-93b5-ef5584583b15","doc_no":"A.6.1.1.8.2.3.2.2.1.2.1.2","title":"Launch Agent 7 Deducts Rebate From Ecosystem Upkeep Fees","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10147,"content":"When paying Ecosystem Upkeep fees, Launch Agent 7 deducts the rebate from the fees it pays.","contentHash":"e53b1df02e45a214a04269696fb8141cf07d5292fa23797a6529bed518f3be4f","addressRefs":[]},"47d2823b-2e93-4a7e-b181-6c232d7429ed":{"id":"47d2823b-2e93-4a7e-b181-6c232d7429ed","doc_no":"A.6.1.1.8.2.3.2.2.1.2.1.3","title":"Operational GovOps Reviews Rebate","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10148,"content":"Operational GovOps reviews Launch Agent 7's calculation of the rebate before executing a return of surplus to token holders. In the event of any issues, Operational GovOps cannot execute the distribution. If Operational GovOps does not execute the distribution, Operational GovOps must post an explanation on the Sky Forum under the \"Launch Agent 7 Prime\" category and work with Launch Agent 7 to resolve the disagreement. If Operational GovOps and Launch Agent 7 cannot resolve the disagreement, it must be escalated to Core GovOps.","contentHash":"0c6515c025316bf88f6aca5028daebf0b4e56f9ec9c7a6c7920ba31a1bde0e74","addressRefs":[]},"455301ee-b352-4bb1-8b11-a215d501e095":{"id":"455301ee-b352-4bb1-8b11-a215d501e095","doc_no":"A.6.1.1.8.2.3.2.2.1.2.2","title":"Non-Routine Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10149,"content":"The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"26124e561643067db87adbbaa5b3919c0e80a17d393947783fdd51bc3dd76e88","addressRefs":[]},"6009ee51-2540-44db-946a-8feb400824cb":{"id":"6009ee51-2540-44db-946a-8feb400824cb","doc_no":"A.6.1.1.8.2.3.2.2.1.2.3","title":"Emergency Protocol","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10150,"content":"The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive.","contentHash":"76a512f4d4e1db7e8b51d4be93e6e5bae40a47b4f2b17d9a5dd638517fb9e0e5","addressRefs":[]},"9ac2f1d8-a349-4348-8f66-79fdc605eab8":{"id":"9ac2f1d8-a349-4348-8f66-79fdc605eab8","doc_no":"A.6.1.1.8.2.3.2.2.1.3","title":"Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10151,"content":"The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive.","contentHash":"486483ac0fb9e2340606ea884d79da2110f436e88d959e021821e569760b1a12","addressRefs":[]},"d4946913-4550-4250-b48e-5fe97e30728c":{"id":"d4946913-4550-4250-b48e-5fe97e30728c","doc_no":"A.6.1.1.8.2.3.2.2.1.3.1","title":"Initial Planning","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10152,"content":"The materials associated with initial planning of the Invocation of this Instance are contained herein.","contentHash":"8c16cc4ab92807fe0b1ef621d0f6d24e074859ceab6920526979cb2964937a4f","addressRefs":[]},"e07b73b0-079a-45ba-a861-03d6f4d7ac49":{"id":"e07b73b0-079a-45ba-a861-03d6f4d7ac49","doc_no":"A.6.1.1.8.2.3.2.2.1.3.2","title":"Operational GovOps Review","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10153,"content":"The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein.","contentHash":"5098a4865fe8925db69a90451a1001b453dead81f05727b7dd956d272bd28b6e","addressRefs":[]},"990d5e1a-d9ac-4aa6-a663-ec310f193d84":{"id":"990d5e1a-d9ac-4aa6-a663-ec310f193d84","doc_no":"A.6.1.1.8.2.3.2.2.1.3.3","title":"Artifact Edit Proposal","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10154,"content":"The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein.","contentHash":"cd4cf2c953080ff0e9df13a10b513e9bdba0923b0173ed2c1c63867f228a1df2","addressRefs":[]},"ccc58c85-b8b2-429a-a95d-df91902a6697":{"id":"ccc58c85-b8b2-429a-a95d-df91902a6697","doc_no":"A.6.1.1.8.2.3.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10155,"content":"The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein.","contentHash":"6eb492da2e5bd2977a9b53e89b82d83b03ec383034c5e5e14029dbe9ad9e84c7","addressRefs":[]},"c5610121-5800-44d1-bd16-bd0022fd2955":{"id":"c5610121-5800-44d1-bd16-bd0022fd2955","doc_no":"A.6.1.1.8.2.3.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10156,"content":"Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked.","contentHash":"6c881842482a7658a187ff5240d802d05e1ab45ec4d5fc8374ae9fb26dff867b","addressRefs":[]},"5d27e7f0-7d57-4740-8c08-6df78e9880a7":{"id":"5d27e7f0-7d57-4740-8c08-6df78e9880a7","doc_no":"A.6.1.1.8.2.4","title":"SkyLink Primitives","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10157,"content":"The documents herein implement the SkyLink Primitives for Launch Agent 7. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f).","contentHash":"00167d6dcce47bced82c0b712718496c199e061f9e180fe6617848dba421f48b","addressRefs":[]},"75507209-dc1e-414a-a112-75f7b076518c":{"id":"75507209-dc1e-414a-a112-75f7b076518c","doc_no":"A.6.1.1.8.2.4.1","title":"Token SkyLink Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10158,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Token SkyLink Primitive. See [A.2.2.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76).","contentHash":"21ceb03e00ab3bae41e263fd39d05c0af8bc8d9e6daa32a7a1e0506b0922728c","addressRefs":[]},"a964694f-360d-4765-b0e0-54907b66559d":{"id":"a964694f-360d-4765-b0e0-54907b66559d","doc_no":"A.6.1.1.8.2.4.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10159,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Token SkyLink Primitive.","contentHash":"2bd88649a84b3d3600a4f9d3f65de3310d9042ff7f0299edb42c9af9f1c8c39d","addressRefs":[]},"ac469feb-2bd9-4fda-925a-3a8efa5c0c74":{"id":"ac469feb-2bd9-4fda-925a-3a8efa5c0c74","doc_no":"A.6.1.1.8.2.4.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10160,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"0d4a37e4-56d2-49c2-8166-9bc934ebeddf":{"id":"0d4a37e4-56d2-49c2-8166-9bc934ebeddf","doc_no":"A.6.1.1.8.2.4.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10161,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`.","contentHash":"77442b5e5abcedb2770e2602846852f45f18f75076f65f174c4b66a923913359","addressRefs":[]},"fa968e1d-c573-4a3c-b1e8-ec96bdf68e96":{"id":"fa968e1d-c573-4a3c-b1e8-ec96bdf68e96","doc_no":"A.6.1.1.8.2.4.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10162,"content":"This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`.","contentHash":"ced31e0f4c015d1a9343a03769ba0a7ed74a54956865f0ef5954080ff78e964d","addressRefs":[]},"cea9280a-74ca-49fe-a2a4-76762af38073":{"id":"cea9280a-74ca-49fe-a2a4-76762af38073","doc_no":"A.6.1.1.8.2.4.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10163,"content":"This document contains a Directory of all prospective Instances of the Token SkyLink Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.4.1.1.2 - Active Instances Directory](0d4a37e4-56d2-49c2-8166-9bc934ebeddf), whereas failed Invocations are Archived in [A.6.1.1.8.2.4.1.1.5 - Hub Data Repository](35b78704-fd3a-4d05-95b3-ba20f73b4c18).","contentHash":"1f1aad4c95b946509c1a240630301ee541aaccf224aa14ef88d344f8bdcf1019","addressRefs":[]},"35b78704-fd3a-4d05-95b3-ba20f73b4c18":{"id":"35b78704-fd3a-4d05-95b3-ba20f73b4c18","doc_no":"A.6.1.1.8.2.4.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10164,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"00aec26a-18b8-4617-a764-05283d14df9e":{"id":"00aec26a-18b8-4617-a764-05283d14df9e","doc_no":"A.6.1.1.8.2.4.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10165,"content":"The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here.","contentHash":"2be6ee6f1890568458d2ae74592f7bf3cc985b6a770a50b24a190188733c2c24","addressRefs":[]},"f80317dc-9641-4299-ad2c-37b6b20b9b61":{"id":"f80317dc-9641-4299-ad2c-37b6b20b9b61","doc_no":"A.6.1.1.8.2.4.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10166,"content":"The subtrees for failed Invocations of the Token SkyLink Primitive are stored here.","contentHash":"35801fa7ecd4b29d8eb2edb814edfc91988fe4009be9f6d2949132325a90385d","addressRefs":[]},"2e48a4ea-2604-44f9-b1a0-b9c3bc38dae1":{"id":"2e48a4ea-2604-44f9-b1a0-b9c3bc38dae1","doc_no":"A.6.1.1.8.2.4.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10167,"content":"The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here.","contentHash":"96988e40c965e67967018a788ea72b6c73bb673e094b148ea415348383621a0c","addressRefs":[]},"974d0a20-cdff-431f-bc41-dbb7c0dab434":{"id":"974d0a20-cdff-431f-bc41-dbb7c0dab434","doc_no":"A.6.1.1.8.2.4.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10168,"content":"The Instances of the Token SkyLink Primitive with `Active` Status are stored herein.","contentHash":"ac1949e73e409aa4ffa76aa306aa94f5ac9c8351762980153fcd847c817999b7","addressRefs":[]},"fa9f564b-220c-4b80-b354-3fea21fc4bce":{"id":"fa9f564b-220c-4b80-b354-3fea21fc4bce","doc_no":"A.6.1.1.8.2.4.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10169,"content":"The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein.","contentHash":"212385c5360845158753e1b98d5c6db962d8b69e95bf5acdb416d183f6076e0a","addressRefs":[]},"3951cd54-791c-46cc-b3e0-2b930d7e4723":{"id":"3951cd54-791c-46cc-b3e0-2b930d7e4723","doc_no":"A.6.1.1.8.2.4.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10170,"content":"The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.4.1.2 - Active Instances](974d0a20-cdff-431f-bc41-dbb7c0dab434).","contentHash":"c38a9811092d20167222548da715d5b13a48a15cbb549ab25ea589ba7e8002a6","addressRefs":[]},"d16b5adc-f990-4160-b324-0b687292fef3":{"id":"d16b5adc-f990-4160-b324-0b687292fef3","doc_no":"A.6.1.1.8.2.5","title":"Demand Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10171,"content":"The documents herein implement the Demand Side Stablecoin Primitives for Launch Agent 7. See [A.2.2.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d).","contentHash":"875492171a4e3651f2ed110c145be87a58a48784fc0dcdc9ea814a58d1361e6b","addressRefs":[]},"cbfe8a72-d21f-4edd-887e-2d9bbd2012e9":{"id":"cbfe8a72-d21f-4edd-887e-2d9bbd2012e9","doc_no":"A.6.1.1.8.2.5.1","title":"Distribution Reward Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10172,"content":"The documents herein contain all data and specifications for Launch Agent 7's instances of the Distribution Reward Primitive. See [A.2.2.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6).","contentHash":"ba17eaff5837fe375c0528fc55ba1e96642ad75fcd3616be54aee7a9a9df7046","addressRefs":[]},"28cc6a65-84be-4019-b0fe-12ed428670a9":{"id":"28cc6a65-84be-4019-b0fe-12ed428670a9","doc_no":"A.6.1.1.8.2.5.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10173,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Distribution Reward Primitive.","contentHash":"8385eaa9e37b9cee04046725ced041134c8e44a82fd748d4974380ed88d0d0c3","addressRefs":[]},"4740c001-7b76-42ae-a599-6ad4ed7705aa":{"id":"4740c001-7b76-42ae-a599-6ad4ed7705aa","doc_no":"A.6.1.1.8.2.5.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10174,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"91bc2e83-ed71-4343-a527-084001407db0":{"id":"91bc2e83-ed71-4343-a527-084001407db0","doc_no":"A.6.1.1.8.2.5.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10175,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`.","contentHash":"de8b05e6b610e60903dc61b2e92f6e7523b72dc1c3f172ef4078ede544a1a721","addressRefs":[]},"ea7b87af-62ff-424e-8994-80eed40570ce":{"id":"ea7b87af-62ff-424e-8994-80eed40570ce","doc_no":"A.6.1.1.8.2.5.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10176,"content":"This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`.","contentHash":"907028d1f9da5b9c8c262442036ba37a840562296b3552dbb156abc5b0764431","addressRefs":[]},"5f414c27-bd79-4265-a1fa-eb199c270852":{"id":"5f414c27-bd79-4265-a1fa-eb199c270852","doc_no":"A.6.1.1.8.2.5.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10177,"content":"This document contains a Directory of all prospective Instances of the Distribution Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.5.1.1.2 - Active Instances Directory](91bc2e83-ed71-4343-a527-084001407db0), whereas failed Invocations are Archived in [A.6.1.1.8.2.5.1.1.5 - Hub Data Repository](cec11621-1805-4b87-8eaf-cfcf5200391f).","contentHash":"b11a0b0d03a0e1f0e30aa72340048f0eca40332ab59dcb5b0c03dae62af2d6db","addressRefs":[]},"cec11621-1805-4b87-8eaf-cfcf5200391f":{"id":"cec11621-1805-4b87-8eaf-cfcf5200391f","doc_no":"A.6.1.1.8.2.5.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10178,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"0110092c-d37b-45a4-a6be-a81b1607c2ba":{"id":"0110092c-d37b-45a4-a6be-a81b1607c2ba","doc_no":"A.6.1.1.8.2.5.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10179,"content":"The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here.","contentHash":"f35398a97b3892551b773183e697166971e4cd7890b105ca46741a4d725f8f9c","addressRefs":[]},"6514cf35-a87d-45d7-b102-560ed642df7e":{"id":"6514cf35-a87d-45d7-b102-560ed642df7e","doc_no":"A.6.1.1.8.2.5.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10180,"content":"The subtrees for failed Invocations of the Distribution Reward Primitive are stored here.","contentHash":"4c380659552358c856308dca0ec2433c34919c2868b1b600cf51ef4bfc66b57f","addressRefs":[]},"df4cd80b-d4e4-4e2c-b6ed-56d70a109072":{"id":"df4cd80b-d4e4-4e2c-b6ed-56d70a109072","doc_no":"A.6.1.1.8.2.5.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10181,"content":"The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here.","contentHash":"f458129882cd83e1579d87ddd79fb03b8ecbf1a7b2de82429ab4c42ea4930104","addressRefs":[]},"11ae6de4-4ab6-4d0f-bf8c-1ab32aed0635":{"id":"11ae6de4-4ab6-4d0f-bf8c-1ab32aed0635","doc_no":"A.6.1.1.8.2.5.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10182,"content":"The Instances of the Distribution Reward Primitive with `Active` Status are stored herein.","contentHash":"df7a32531b59e493fd4e2d19196be66fd9185a79d298c65a8dbe128cdd727fd7","addressRefs":[]},"96167687-c6bb-4687-8794-3f41e885831b":{"id":"96167687-c6bb-4687-8794-3f41e885831b","doc_no":"A.6.1.1.8.2.5.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10183,"content":"The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein.","contentHash":"40b6e380f35c402c619b297a0d5b5a637c35fd9a31fa9f8ebc6b1b420bbc692a","addressRefs":[]},"f0f80202-cb0f-4480-8223-cac64d6556d6":{"id":"f0f80202-cb0f-4480-8223-cac64d6556d6","doc_no":"A.6.1.1.8.2.5.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10184,"content":"The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.5.1.2 - Active Instances](11ae6de4-4ab6-4d0f-bf8c-1ab32aed0635).","contentHash":"fd0254ee093c327f9c1a23ba906ba76cae10d47fa3d411fcae9cec8c0a3a30fb","addressRefs":[]},"18446ffd-1206-41bc-b735-6317d8b4f058":{"id":"18446ffd-1206-41bc-b735-6317d8b4f058","doc_no":"A.6.1.1.8.2.5.2","title":"Integration Boost Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10185,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Integration Boost Primitive. See [A.2.2.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20).","contentHash":"b6ef3b318e8b05dbae179c79bc65eafab777d5f39356bbf3d115fc035463ed31","addressRefs":[]},"99823d99-ddcd-49bc-8a48-9f1843a962f5":{"id":"99823d99-ddcd-49bc-8a48-9f1843a962f5","doc_no":"A.6.1.1.8.2.5.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10186,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Integration Boost Primitive.","contentHash":"b1375c1803d6f9399b73104b6181f53be874060e1918905d7313feefc7843802","addressRefs":[]},"467eb662-d40b-414a-811b-88d15bb6e7e5":{"id":"467eb662-d40b-414a-811b-88d15bb6e7e5","doc_no":"A.6.1.1.8.2.5.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10187,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"b25b5713-b5db-4666-af29-f569289df9d4":{"id":"b25b5713-b5db-4666-af29-f569289df9d4","doc_no":"A.6.1.1.8.2.5.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10188,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`.","contentHash":"96e0e123814b94f646d53a78065c5a2754da34e2145c686a550f91f9b61fda1c","addressRefs":[]},"18a11b40-1dd1-4aee-9d37-a8bf84fcdd79":{"id":"18a11b40-1dd1-4aee-9d37-a8bf84fcdd79","doc_no":"A.6.1.1.8.2.5.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10189,"content":"This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`.","contentHash":"43244b4692bdcb5d7b4329a11ab9c44e53f4ba3e98d9179cbb30cad72bc3b48d","addressRefs":[]},"32f63086-f029-4454-952a-1a992833c216":{"id":"32f63086-f029-4454-952a-1a992833c216","doc_no":"A.6.1.1.8.2.5.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10190,"content":"This document contains a Directory of all prospective Instances of the Integration Boost Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.5.2.1.2 - Active Instances Directory](b25b5713-b5db-4666-af29-f569289df9d4), whereas failed Invocations are Archived in [A.6.1.1.8.2.5.2.1.5 - Hub Data Repository](2fa2c7c2-6bfb-4620-bfa4-45c9d7cff7c6).","contentHash":"9ca344b94712bf78658f09d34051df757b01a9dde0b5a10b4412f0bd89960556","addressRefs":[]},"2fa2c7c2-6bfb-4620-bfa4-45c9d7cff7c6":{"id":"2fa2c7c2-6bfb-4620-bfa4-45c9d7cff7c6","doc_no":"A.6.1.1.8.2.5.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10191,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"7af853f8-1d3d-4127-a734-0b22b9b95cdd":{"id":"7af853f8-1d3d-4127-a734-0b22b9b95cdd","doc_no":"A.6.1.1.8.2.5.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10192,"content":"The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here.","contentHash":"ba769d9c60c204fcef6a166afa883e11803d20c2f135cb631cbe53f576f51b17","addressRefs":[]},"0eaad468-2023-4bc3-a9f6-2d58ae9a27f7":{"id":"0eaad468-2023-4bc3-a9f6-2d58ae9a27f7","doc_no":"A.6.1.1.8.2.5.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10193,"content":"The subtrees for failed Invocations of the Integration Boost Primitive are stored here.","contentHash":"1d11aafe4f78f88eb97e29a204aa68a33b026e83e8ab2657c1891956429f60d3","addressRefs":[]},"78e5fefc-687c-4cae-b448-e7d556e3f088":{"id":"78e5fefc-687c-4cae-b448-e7d556e3f088","doc_no":"A.6.1.1.8.2.5.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10194,"content":"The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here.","contentHash":"4489a39651617254ce2e973a256063ad8910f9610a289f1bf23042fe4b16bd65","addressRefs":[]},"9219e0ee-66b9-4ede-b741-ec8b03d92405":{"id":"9219e0ee-66b9-4ede-b741-ec8b03d92405","doc_no":"A.6.1.1.8.2.5.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10195,"content":"The Instances of the Integration Boost Primitive with `Active` Status are stored herein.","contentHash":"076ca6c1651281cb4036d17c727ee161da7483b52439fef989a3ab6f2663f5e9","addressRefs":[]},"be5f8fed-3433-4c4c-b199-e62e36f59d96":{"id":"be5f8fed-3433-4c4c-b199-e62e36f59d96","doc_no":"A.6.1.1.8.2.5.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10196,"content":"The Instances of the Integration Boost Primitive with `Completed` Status are contained herein.","contentHash":"e522b8a5bf1e120c6a0e6d47607a08c8adb180f94dec916127560e68acd25532","addressRefs":[]},"236422d6-f872-4b6f-9b1c-aea12fd8837e":{"id":"236422d6-f872-4b6f-9b1c-aea12fd8837e","doc_no":"A.6.1.1.8.2.5.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10197,"content":"The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.5.2.2 - Active Instances](9219e0ee-66b9-4ede-b741-ec8b03d92405).","contentHash":"6336808cdae112e89453c620c7953878a5e104de22b9d0cca92edfd0cdfd4a71","addressRefs":[]},"388c4c85-a228-4722-8001-02040cbb36ff":{"id":"388c4c85-a228-4722-8001-02040cbb36ff","doc_no":"A.6.1.1.8.2.5.3","title":"Pioneer Chain Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10198,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Pioneer Chain Primitive. See [A.2.2.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c).","contentHash":"e247e9965fe41ed2e7694026458cbbda40c33afb148326f53e94eff004b50434","addressRefs":[]},"e5477412-eb2c-4aba-b0a5-3cbab8b4b1b4":{"id":"e5477412-eb2c-4aba-b0a5-3cbab8b4b1b4","doc_no":"A.6.1.1.8.2.5.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10199,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Pioneer Chain Primitive.","contentHash":"65d4a112c77076c814de7924a67f7481409e545cf87db60ccc4179f749c2564a","addressRefs":[]},"4db04c3a-6884-4a81-b7f6-a17435d478f7":{"id":"4db04c3a-6884-4a81-b7f6-a17435d478f7","doc_no":"A.6.1.1.8.2.5.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10200,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"37c0dfc8-6bb3-4936-840f-08e15d8d13ec":{"id":"37c0dfc8-6bb3-4936-840f-08e15d8d13ec","doc_no":"A.6.1.1.8.2.5.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10201,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`.","contentHash":"4ebb5c0c36c25d7874ee1344449aabff47c7fcb339f828c6877bed5c7eedb538","addressRefs":[]},"8b3130a4-2849-4b30-b25a-33ccc090902f":{"id":"8b3130a4-2849-4b30-b25a-33ccc090902f","doc_no":"A.6.1.1.8.2.5.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10202,"content":"This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`.","contentHash":"8c17dd3880080122b71e35f089e3f5dd78b294abda0605f676f298295db03222","addressRefs":[]},"ea90d778-f105-413f-9534-473aa1fe4b07":{"id":"ea90d778-f105-413f-9534-473aa1fe4b07","doc_no":"A.6.1.1.8.2.5.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10203,"content":"This document contains a Directory of all prospective Instances of the Pioneer Chain Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.5.3.1.2 - Active Instances Directory](37c0dfc8-6bb3-4936-840f-08e15d8d13ec), whereas failed Invocations are Archived in [A.6.1.1.8.2.5.3.1.5 - Hub Data Repository](fae1a000-81c8-4a7f-a99e-3f1fccb25366).","contentHash":"2d1d8086931274fd70ffa11482068e16518a2d478f4d1958b19a4ca48c842147","addressRefs":[]},"fae1a000-81c8-4a7f-a99e-3f1fccb25366":{"id":"fae1a000-81c8-4a7f-a99e-3f1fccb25366","doc_no":"A.6.1.1.8.2.5.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10204,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"a99b1995-c7e9-46a8-a088-b87e3ea65fd2":{"id":"a99b1995-c7e9-46a8-a088-b87e3ea65fd2","doc_no":"A.6.1.1.8.2.5.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10205,"content":"The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here.","contentHash":"dff37a1bb2abfef0ae92956e51607fd4a1a5a043dd3d0b7a259c7065c72a2dce","addressRefs":[]},"945ef091-8c0a-4ae4-bf0c-ae122154e35c":{"id":"945ef091-8c0a-4ae4-bf0c-ae122154e35c","doc_no":"A.6.1.1.8.2.5.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10206,"content":"The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here.","contentHash":"0d1c77c0c26f906c235239f1cd6e527840646133a39c267029084ecf1df47e09","addressRefs":[]},"f1f77981-a831-4b0a-b7fc-8f18b35fef76":{"id":"f1f77981-a831-4b0a-b7fc-8f18b35fef76","doc_no":"A.6.1.1.8.2.5.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10207,"content":"The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here.","contentHash":"5926109af1bda2718d434a86a3c1b3671cb5adde1b2b21ff60f43fab5d896961","addressRefs":[]},"0ed9935e-1a67-4423-871a-6a5addd51af5":{"id":"0ed9935e-1a67-4423-871a-6a5addd51af5","doc_no":"A.6.1.1.8.2.5.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10208,"content":"The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein.","contentHash":"5b8e14fdd0384e4866f28cc2c6b48549e91740158c8a0a8a8a53e959d4699a4d","addressRefs":[]},"20495dd8-7f95-49c3-bb02-047067897e91":{"id":"20495dd8-7f95-49c3-bb02-047067897e91","doc_no":"A.6.1.1.8.2.5.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10209,"content":"The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein.","contentHash":"01baa8a2f88b8cdd33084198597b13c17a14c951bda2a0e5eaff9d6e41717797","addressRefs":[]},"8357b4a0-554e-488f-ad52-5f0e982bfa03":{"id":"8357b4a0-554e-488f-ad52-5f0e982bfa03","doc_no":"A.6.1.1.8.2.5.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10210,"content":"The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.5.3.2 - Active Instances](0ed9935e-1a67-4423-871a-6a5addd51af5).","contentHash":"9030fad2fa44635b3d25d5a56d67afdfa781fadc3c7e14dff83a96ca28cb5551","addressRefs":[]},"80e9d9f2-956a-4bb1-a412-6efaad7dda56":{"id":"80e9d9f2-956a-4bb1-a412-6efaad7dda56","doc_no":"A.6.1.1.8.2.6","title":"Supply Side Stablecoin Primitives","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10211,"content":"The documents herein implement the Supply Side Stablecoin Primitives for Launch Agent 7. See [A.2.2.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f).","contentHash":"97a4522510269f6d73070131221c0b45fe2177a38ef47e3fd2d103d0f525d20f","addressRefs":[]},"929aa1ad-a1c6-4dd6-89ef-bc18316ec3b0":{"id":"929aa1ad-a1c6-4dd6-89ef-bc18316ec3b0","doc_no":"A.6.1.1.8.2.6.1","title":"Allocation System Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10212,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Allocation System Primitive. See [A.2.2.9.1 - Allocation System Primitive](9db14ab7-bb4b-4751-8084-843bd4359f2a).","contentHash":"5b8722e121d6e60df41461174da993d219393bdb43ba5237f9a4556bc6eedad9","addressRefs":[]},"b0a3b8d2-e776-4604-aab1-bd68e851d042":{"id":"b0a3b8d2-e776-4604-aab1-bd68e851d042","doc_no":"A.6.1.1.8.2.6.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10213,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Allocation System Primitive.","contentHash":"a2e6d4d60336339c36c63fce2550cea6e9dc3b143825e1043c7e074136504e75","addressRefs":[]},"7dc4a32d-d14f-4fe1-af90-ff8e3a0f6e8a":{"id":"7dc4a32d-d14f-4fe1-af90-ff8e3a0f6e8a","doc_no":"A.6.1.1.8.2.6.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10214,"content":"`Active`","contentHash":"dae83db14a58cda563aa85cdf991bfac93f431856e669fde6691df1dc9e8f0e4","addressRefs":[]},"d232eaa6-bbbc-4de2-9b7a-d20b3a25ad45":{"id":"d232eaa6-bbbc-4de2-9b7a-d20b3a25ad45","doc_no":"A.6.1.1.8.2.6.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10215,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`.","contentHash":"74c70868ef2765745c05f149fd545721f295f458c77188f434e7623f898c1a55","addressRefs":[]},"5c1014cd-2531-4438-84ae-37cf9c12c29b":{"id":"5c1014cd-2531-4438-84ae-37cf9c12c29b","doc_no":"A.6.1.1.8.2.6.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10216,"content":"This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`.","contentHash":"fd88ffc96223e39c29fbedfbe48ef3d99a585f2f40209d2a3c41ceab28693805","addressRefs":[]},"d0c5ad5f-ffe6-469b-b4e8-1f77b1a24739":{"id":"d0c5ad5f-ffe6-469b-b4e8-1f77b1a24739","doc_no":"A.6.1.1.8.2.6.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10217,"content":"This document contains a Directory of all prospective Instances of the Allocation System Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.6.1.1.2 - Active Instances Directory](d232eaa6-bbbc-4de2-9b7a-d20b3a25ad45), whereas failed Invocations are Archived in [A.6.1.1.8.2.6.1.1.5 - Hub Data Repository](952b34e6-7983-4dd0-a46f-e3622c2346de).","contentHash":"f61c9b30dab3a8f0f27107cbfdea04c0ffefa6189486a9e0a2f8be56bc131027","addressRefs":[]},"952b34e6-7983-4dd0-a46f-e3622c2346de":{"id":"952b34e6-7983-4dd0-a46f-e3622c2346de","doc_no":"A.6.1.1.8.2.6.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10218,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"4ba906c3-5163-4188-bcec-1635ad497c54":{"id":"4ba906c3-5163-4188-bcec-1635ad497c54","doc_no":"A.6.1.1.8.2.6.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10219,"content":"The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here.","contentHash":"7ac4dd515c6e8fc9d5d9d8554a4a4c5e62c0c93384cea34691b9e6309a38b61f","addressRefs":[]},"401da49b-16c4-4101-b0bf-28ef4d7beaf8":{"id":"401da49b-16c4-4101-b0bf-28ef4d7beaf8","doc_no":"A.6.1.1.8.2.6.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10220,"content":"The subtrees for failed Invocations of the Allocation System Primitive are stored here.","contentHash":"0f0d89648e0737435be483f0cf89d47a29a5e0a4d87de8fcc91b59ec2c2b42a9","addressRefs":[]},"fe32b46e-7449-416d-a24f-5b3d31b4bbb9":{"id":"fe32b46e-7449-416d-a24f-5b3d31b4bbb9","doc_no":"A.6.1.1.8.2.6.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10221,"content":"The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here.","contentHash":"c1f7179558596e875b18dcbc22c202a515881a9633913699255f9fec43bf5fd9","addressRefs":[]},"a407dee4-36ec-4499-a3e6-e01008dd56cf":{"id":"a407dee4-36ec-4499-a3e6-e01008dd56cf","doc_no":"A.6.1.1.8.2.6.1.2","title":"Multi-Instance Coordinator Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10222,"content":"The documents herein provide general specifications of the Launch Agent 7 Liquidity Layer and define Launch Agent 7's overarching strategy and operational framework for managing across all Instances.","contentHash":"475a736c05a102b7bedc76247064a7d1fe04da06d935ea25ce3e8605776e8e00","addressRefs":[]},"d74aa2ed-b6fb-4dd1-83de-a334734bc48d":{"id":"d74aa2ed-b6fb-4dd1-83de-a334734bc48d","doc_no":"A.6.1.1.8.2.6.1.2.1","title":"General Specifications","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10223,"content":"The documents herein contain general specifications for the Launch Agent 7 Liquidity Layer.","contentHash":"6f4b54cde4915f10b96d22ce288ed4653de85924cc3acb18ee730a7329bf4a7f","addressRefs":[]},"4abfa5e7-e1a8-4ade-89fb-a2ef26752877":{"id":"4abfa5e7-e1a8-4ade-89fb-a2ef26752877","doc_no":"A.6.1.1.8.2.6.1.2.1.1","title":"Launch Agent 7 Liquidity Layer Architecture","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10224,"content":"The documents herein describe the high-level design of the Launch Agent 7 Liquidity Layer, including its key smart contracts and their functionality.","contentHash":"0d95047c488b9f85b679016c9af40c509a64ee6313abc9ce4436b3262da6c32a","addressRefs":[]},"e9845cfa-2d27-45f0-b955-dbedd5d8ddb4":{"id":"e9845cfa-2d27-45f0-b955-dbedd5d8ddb4","doc_no":"A.6.1.1.8.2.6.1.2.1.1.1","title":"Launch Agent 7 Liquidity Layer Addresses","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10225,"content":"The subdocuments herein provide the addresses of the Launch Agent 7 Liquidity Layer's constituent contracts.","contentHash":"cd5d180e53780b0cc402f6fd8a2798c93d63d0af24e8e42f81a42be7f2615532","addressRefs":[]},"deed6d17-668a-4ebb-844b-19b25a293448":{"id":"deed6d17-668a-4ebb-844b-19b25a293448","doc_no":"A.6.1.1.8.2.6.1.2.1.1.1.1","title":"Allocator Contract Addresses","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10226,"content":"The documents herein contain global key addresses for the Allocator Contracts.","contentHash":"a99119eb26b8e6fbaae81a45fa911afc0af3344a9ea2bbcb90fc7cf9bd94fe9c","addressRefs":[]},"d5d47c10-f714-4c88-b4ac-e8937ef86134":{"id":"d5d47c10-f714-4c88-b4ac-e8937ef86134","doc_no":"A.6.1.1.8.2.6.1.2.1.1.1.1.1","title":"Allocator Buffer Contract","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10227,"content":"The address of the ALLOCATOR_BUFFER contract is: `0x67Ac5c8FbFDAc5265c995e9B2ACd830496438AfD`.","contentHash":"94995ba7f881d657b5f38e2c109c656b3a4e490be7bee58188d610d8c17b2826","addressRefs":["0x67ac5c8fbfdac5265c995e9b2acd830496438afd"]},"97dfcdfa-9c39-49fe-95cc-a117635b3f52":{"id":"97dfcdfa-9c39-49fe-95cc-a117635b3f52","doc_no":"A.6.1.1.8.2.6.1.2.1.1.1.1.2","title":"Allocator Vault Contract","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10228,"content":"The address of the ALLOCATOR_VAULT (ALLOCATOR-INTERVAL-A) contract is: `0xDD3bE7650589E6A6171d454b026C4AD1a2C02720`.","contentHash":"1c4a20fcf61fd5fd5bc77bab95f0d2e05c0f6d0f7ecddf9793448fd627ff1c75","addressRefs":["0xdd3be7650589e6a6171d454b026c4ad1a2c02720"]},"132aaf59-d6fa-4260-b686-91246dba9897":{"id":"132aaf59-d6fa-4260-b686-91246dba9897","doc_no":"A.6.1.1.8.2.6.1.3","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10229,"content":"The Instances of the Allocation System Primitive with `Active` Status are stored herein.","contentHash":"1ec0e728a9f82ad97fb8eeaf6a1959350595219b9f7cf894e7fe0704248213a2","addressRefs":[]},"122d8a6a-c54e-43c2-9e48-1ddecf8e4ebe":{"id":"122d8a6a-c54e-43c2-9e48-1ddecf8e4ebe","doc_no":"A.6.1.1.8.2.6.1.4","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10230,"content":"The Instances of the Allocation System Primitive with `Completed` Status are stored herein.","contentHash":"5e8b303421b8ddbbe094a65ed1a012a162ef23442d0be75ad055b30f78fb3af7","addressRefs":[]},"b835b079-0e89-4665-afe9-edb7b22c3317":{"id":"b835b079-0e89-4665-afe9-edb7b22c3317","doc_no":"A.6.1.1.8.2.6.1.5","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10231,"content":"The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.6.1.3 - Active Instances](132aaf59-d6fa-4260-b686-91246dba9897).","contentHash":"4653c1f6955150a37d0f427dc381f8a246e9dc71703679b97b6299c781a324ab","addressRefs":[]},"d718c63a-1096-46e7-9ff7-c1c851679d45":{"id":"d718c63a-1096-46e7-9ff7-c1c851679d45","doc_no":"A.6.1.1.8.2.6.2","title":"Junior Risk Capital Rental Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10232,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Junior Risk Capital Rental Primitive. See [A.2.2.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce).","contentHash":"08ac21820047040c79a3da95abf371ebf6a1910bbb0260401e922e7e69ef4f57","addressRefs":[]},"796d1eab-a018-4e8f-9d86-8e1f2eea9c5b":{"id":"796d1eab-a018-4e8f-9d86-8e1f2eea9c5b","doc_no":"A.6.1.1.8.2.6.2.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10233,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Junior Risk Capital Rental Primitive.","contentHash":"6ffc5ec6b135bf1b12a9adbfb6c6d6c995735503295388e66753f13a52ef23ee","addressRefs":[]},"24340f8a-a4a7-4002-9c61-c5d7d4e9d4b3":{"id":"24340f8a-a4a7-4002-9c61-c5d7d4e9d4b3","doc_no":"A.6.1.1.8.2.6.2.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10234,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"56655922-1c77-40f7-83f4-3b9af9dc0c59":{"id":"56655922-1c77-40f7-83f4-3b9af9dc0c59","doc_no":"A.6.1.1.8.2.6.2.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10235,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`.","contentHash":"88ada25e33082ec908aafe6d533beb7a41bb8bea8326b72c0e86de7bf9d0acb1","addressRefs":[]},"efae8d35-a014-41fa-8a82-b2a4488e7058":{"id":"efae8d35-a014-41fa-8a82-b2a4488e7058","doc_no":"A.6.1.1.8.2.6.2.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10236,"content":"This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`.","contentHash":"3252116f1f870cb2ebe804722eaef75ec6ce4a445de5f224464315c3a381e9b9","addressRefs":[]},"86ca0f50-a33b-4068-abd4-3f6a3adb9874":{"id":"86ca0f50-a33b-4068-abd4-3f6a3adb9874","doc_no":"A.6.1.1.8.2.6.2.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10237,"content":"This document contains a Directory of all prospective Instances of the Junior Risk Capital Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.6.2.1.2 - Active Instances Directory](56655922-1c77-40f7-83f4-3b9af9dc0c59), whereas failed Invocations are Archived in [A.6.1.1.8.2.6.2.1.5 - Hub Data Repository](c054e1a5-5ea9-4f95-a469-d357bc30cd41).","contentHash":"8cbaf84c9a871ae86446393eb91767cc37d336446950c999ea416d7ae4076f5e","addressRefs":[]},"c054e1a5-5ea9-4f95-a469-d357bc30cd41":{"id":"c054e1a5-5ea9-4f95-a469-d357bc30cd41","doc_no":"A.6.1.1.8.2.6.2.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10238,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"33438a68-430e-4e13-b0bd-caa11b5578d0":{"id":"33438a68-430e-4e13-b0bd-caa11b5578d0","doc_no":"A.6.1.1.8.2.6.2.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10239,"content":"The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"fbf3540f96007f477ae44f04cb2264faccf547f059df3dc2ce6be89849374bf5","addressRefs":[]},"8b4a66ad-4e68-4a9b-b1a5-c835ec423cb9":{"id":"8b4a66ad-4e68-4a9b-b1a5-c835ec423cb9","doc_no":"A.6.1.1.8.2.6.2.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10240,"content":"The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.","contentHash":"28a91666a8fb599c101888bddf50227c514525964b70938c053324cbca2d52f2","addressRefs":[]},"3286bcd1-544a-4cc2-8508-1a8bc0aecea5":{"id":"3286bcd1-544a-4cc2-8508-1a8bc0aecea5","doc_no":"A.6.1.1.8.2.6.2.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10241,"content":"The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here.","contentHash":"7eb5b5c42ba38a384546b30f4a7ef54ee096e9492ce40d7e382cc5c0e15acda4","addressRefs":[]},"9a3c679d-a269-440e-9069-4bd85b428b3f":{"id":"9a3c679d-a269-440e-9069-4bd85b428b3f","doc_no":"A.6.1.1.8.2.6.2.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10242,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein.","contentHash":"3b67b7bec0b4c955c9290eb1c91fe875bc7b4ff6d577c7cbb38768644ce355dd","addressRefs":[]},"f12949d0-1f1d-473f-89b1-f833523345af":{"id":"f12949d0-1f1d-473f-89b1-f833523345af","doc_no":"A.6.1.1.8.2.6.2.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10243,"content":"The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein.","contentHash":"c91387a679d81066f5f2fe74298a4c147a31d6ae2580ad1f91dd8aeab9322c1e","addressRefs":[]},"f2d93d71-1bf9-4199-8190-e1e0beeb5369":{"id":"f2d93d71-1bf9-4199-8190-e1e0beeb5369","doc_no":"A.6.1.1.8.2.6.2.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10244,"content":"The in progress Invocations of the Junior Risk Capital Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.6.2.2 - Active Instances](9a3c679d-a269-440e-9069-4bd85b428b3f).","contentHash":"4cd6266b1dbb01291d61d518acf071f20a1ff946ebc38823848ad62eb61610fe","addressRefs":[]},"52c0af9a-b4e2-4ff5-ad4c-ffb82263d512":{"id":"52c0af9a-b4e2-4ff5-ad4c-ffb82263d512","doc_no":"A.6.1.1.8.2.6.3","title":"Asset Liability Management Rental Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10245,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Asset Liability Management Rental Primitive. See [A.2.2.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c).","contentHash":"9a8dfc95d6797dd4ac5353c611cce5e1d45f78bda57b929c314b238b02ad6c5f","addressRefs":[]},"3f05c2bb-7f5d-4716-b37e-fdda16d2417e":{"id":"3f05c2bb-7f5d-4716-b37e-fdda16d2417e","doc_no":"A.6.1.1.8.2.6.3.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10246,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Asset Liability Management Rental Primitive.","contentHash":"9e77f43f47e05a2f311fad56d6fda469620b9fed5d4fdf795f17a0f49e6ecfe7","addressRefs":[]},"7444959d-c9aa-4e09-8df3-cbc3dd33b5b8":{"id":"7444959d-c9aa-4e09-8df3-cbc3dd33b5b8","doc_no":"A.6.1.1.8.2.6.3.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10247,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"0997aedd-8432-481a-a8b6-bbbbc1fb76d5":{"id":"0997aedd-8432-481a-a8b6-bbbbc1fb76d5","doc_no":"A.6.1.1.8.2.6.3.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10248,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`.","contentHash":"3af0483dc557e3ecc6ce63a8d4ebb7dc7f58ad3add78f8725eacec42ecc304c3","addressRefs":[]},"3baef0e1-e11f-4ada-8d59-067f5bf10a30":{"id":"3baef0e1-e11f-4ada-8d59-067f5bf10a30","doc_no":"A.6.1.1.8.2.6.3.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10249,"content":"This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`.","contentHash":"fd030d3e8196e800c4b63e0159659978ef00e78b30e8ae38fb20d07c21e0899e","addressRefs":[]},"8d26415c-b07b-4236-8c0d-09dde4abdcce":{"id":"8d26415c-b07b-4236-8c0d-09dde4abdcce","doc_no":"A.6.1.1.8.2.6.3.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10250,"content":"This document contains a Directory of all prospective Instances of the Asset Liability Management Rental Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.6.3.1.2 - Active Instances Directory](0997aedd-8432-481a-a8b6-bbbbc1fb76d5), whereas failed Invocations are Archived in [A.6.1.1.8.2.6.3.1.5 - Hub Data Repository](26df5f96-9971-4361-8981-2687c410042c).","contentHash":"0d11056dfaed754f6e8f2924dd4c3b1d0c8f6cbbc08a3e958e963477f276ef8c","addressRefs":[]},"26df5f96-9971-4361-8981-2687c410042c":{"id":"26df5f96-9971-4361-8981-2687c410042c","doc_no":"A.6.1.1.8.2.6.3.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10251,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"4d418bb4-8fce-4784-b854-170f904ccd18":{"id":"4d418bb4-8fce-4784-b854-170f904ccd18","doc_no":"A.6.1.1.8.2.6.3.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10252,"content":"The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here.","contentHash":"670d5a0a835772d54de84377ab4706293f4f905487e6bfa403425889e49629e2","addressRefs":[]},"a3df996f-3e8b-46e2-ad57-f02f0f6b0b44":{"id":"a3df996f-3e8b-46e2-ad57-f02f0f6b0b44","doc_no":"A.6.1.1.8.2.6.3.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10253,"content":"The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here.","contentHash":"dc429d9a63b48554126c9f5a784ea3da1a825133ea3dc13cbb17acdc2ba3dfdb","addressRefs":[]},"f8913006-a363-43fb-b353-2e6bcdf5291b":{"id":"f8913006-a363-43fb-b353-2e6bcdf5291b","doc_no":"A.6.1.1.8.2.6.3.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10254,"content":"The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here.","contentHash":"1321281ebeec3c92104dffa161360158fe4183314e60598fdf2b4b3f3dce38eb","addressRefs":[]},"b3810d85-dc67-4ebd-805d-64af73333fd0":{"id":"b3810d85-dc67-4ebd-805d-64af73333fd0","doc_no":"A.6.1.1.8.2.6.3.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10255,"content":"The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein.","contentHash":"d29773c3f11c0f7beb67eba4489ef527a3ef3b4b9f87af47ab38d155a523ecc6","addressRefs":[]},"e8c82f4c-ef8c-4f72-9346-fd33c20643a6":{"id":"e8c82f4c-ef8c-4f72-9346-fd33c20643a6","doc_no":"A.6.1.1.8.2.6.3.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10256,"content":"The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein.","contentHash":"c5b24cf7eaf3df5d291a4fb872165f60ee2309430ca3cd40e20aef8204539fca","addressRefs":[]},"eeb2185d-2a4c-45e3-872c-2d241e42d5c4":{"id":"eeb2185d-2a4c-45e3-872c-2d241e42d5c4","doc_no":"A.6.1.1.8.2.6.3.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10257,"content":"The in progress Invocations of the Asset Liability Management Rental Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.6.3.2 - Active Instances](b3810d85-dc67-4ebd-805d-64af73333fd0).","contentHash":"69e96d85165be57d629eb63d28b096eff205c132f2b9729bc8f1c4a420415b6d","addressRefs":[]},"324dbc1c-aa4f-4b87-b171-6e7fad67236d":{"id":"324dbc1c-aa4f-4b87-b171-6e7fad67236d","doc_no":"A.6.1.1.8.2.7","title":"Core Governance Primitives","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10258,"content":"The documents herein implement the Core Governance Primitives for Launch Agent 7. See [A.2.2.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d).","contentHash":"eb7ffc9772e3d9f83ae1f0c18e16c7ddcf8737bcd3217feb4f78a82de8bb9841","addressRefs":[]},"db70350a-fd19-4fca-9341-03bcb7271de7":{"id":"db70350a-fd19-4fca-9341-03bcb7271de7","doc_no":"A.6.1.1.8.2.7.1","title":"Core Governance Reward Primitive","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10259,"content":"The documents herein contain all data and specifications for Launch Agent 7's Instances of the Core Governance Reward Primitive. See [A.2.2.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a).","contentHash":"9cccac75413af730aa48de6ccc4cf98b331216769e2712ff2697a256251775d4","addressRefs":[]},"328e73e4-a676-45d7-bfc5-7e818010f5bd":{"id":"328e73e4-a676-45d7-bfc5-7e818010f5bd","doc_no":"A.6.1.1.8.2.7.1.1","title":"Primitive Hub Document","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10260,"content":"The documents herein organize all base information relevant to Launch Agent 7's usage of the Core Governance Reward Primitive.","contentHash":"39c162a29256801503b5d12c9337651d92094e8df58f28caa66b3f3e3a8ae3fa","addressRefs":[]},"035a469d-0046-4380-9518-5e613a4d3268":{"id":"035a469d-0046-4380-9518-5e613a4d3268","doc_no":"A.6.1.1.8.2.7.1.1.1","title":"Global Activation Status","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10261,"content":"`Inactive`","contentHash":"f5136f82eda95aacd992f3f71f19750124214efe8572da5a646f06ec6c0ddb4d","addressRefs":[]},"e76c0b88-7755-4611-a884-9b5bd3d9c4d8":{"id":"e76c0b88-7755-4611-a884-9b5bd3d9c4d8","doc_no":"A.6.1.1.8.2.7.1.1.2","title":"Active Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10262,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`.","contentHash":"154b385403da070797bc5753bd77f2e3077e6d30edc95a414165b970ba325614","addressRefs":[]},"15639bce-77a4-471c-a42f-29259fcb293b":{"id":"15639bce-77a4-471c-a42f-29259fcb293b","doc_no":"A.6.1.1.8.2.7.1.1.3","title":"Completed Instances Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10263,"content":"This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`.","contentHash":"9941210bbcf83b9948fcc9331a29755b1e93b570b630f7c9d5f6496861cdeec4","addressRefs":[]},"ae8cfca6-f97a-4f93-8c67-904a98a8a59a":{"id":"ae8cfca6-f97a-4f93-8c67-904a98a8a59a","doc_no":"A.6.1.1.8.2.7.1.1.4","title":"In Progress Invocations Directory","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10264,"content":"This document contains a Directory of all prospective Instances of the Core Governance Reward Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.7.1.1.2 - Active Instances Directory](e76c0b88-7755-4611-a884-9b5bd3d9c4d8), whereas failed Invocations are Archived in [A.6.1.1.8.2.7.1.1.5 - Hub Data Repository](5eb6faea-c685-450c-a9ba-601ce68ac690).","contentHash":"8380ad3895a382bfe39729f0f4948fe256426d2a32aaec57f55984ccfa564673","addressRefs":[]},"5eb6faea-c685-450c-a9ba-601ce68ac690":{"id":"5eb6faea-c685-450c-a9ba-601ce68ac690","doc_no":"A.6.1.1.8.2.7.1.1.5","title":"Hub Data Repository","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10265,"content":"The documents herein contain the Data Repository for the Primitive Hub Document.","contentHash":"e2809d39ee6706c593a84c9ca13fd185600b28955b35ba5ff338f7a55df9156d","addressRefs":[]},"5507a84c-0ff2-47c0-b1cc-9d469586051a":{"id":"5507a84c-0ff2-47c0-b1cc-9d469586051a","doc_no":"A.6.1.1.8.2.7.1.1.5.1","title":"Archived Invocations/Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10266,"content":"The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here.","contentHash":"01d7e3afab9c781bf6e38261c649bf3c276866e2645699a851582fa2bcf47d56","addressRefs":[]},"c63f8814-ba44-424f-bb68-9b38ecbfd31e":{"id":"c63f8814-ba44-424f-bb68-9b38ecbfd31e","doc_no":"A.6.1.1.8.2.7.1.1.5.1.1","title":"Failed Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10267,"content":"The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here.","contentHash":"f5f6c8ae4eaedb7c17108e8ab072a8684fd8c1a1eb150b4078cd6f81ad2bc524","addressRefs":[]},"d81d6ff9-e211-497d-801f-3a785db803e3":{"id":"d81d6ff9-e211-497d-801f-3a785db803e3","doc_no":"A.6.1.1.8.2.7.1.1.5.1.2","title":"Suspended Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10268,"content":"The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here.","contentHash":"54735d3aa70848895a9a49e5b35116fd09636b75a4699d6699bf4c9cdcc67130","addressRefs":[]},"746a2e0b-fd99-41de-84cc-61c8f85efb1a":{"id":"746a2e0b-fd99-41de-84cc-61c8f85efb1a","doc_no":"A.6.1.1.8.2.7.1.2","title":"Active Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10269,"content":"The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein.","contentHash":"3c3bb71f372c8fa1f3e4a7153429c21bc9fc0603fc333a69960707a45adcdca3","addressRefs":[]},"621b7986-b265-41d6-8b03-bee449211d3d":{"id":"621b7986-b265-41d6-8b03-bee449211d3d","doc_no":"A.6.1.1.8.2.7.1.3","title":"Completed Instances","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10270,"content":"The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein.","contentHash":"bf9958c624dbc72fbd1e30e4100d80cf8d7a386e86b5ac2ce9cc326bd491a476","addressRefs":[]},"bf457701-f952-4ec5-a2bc-ab356d3e65e2":{"id":"bf457701-f952-4ec5-a2bc-ab356d3e65e2","doc_no":"A.6.1.1.8.2.7.1.4","title":"In Progress Invocations","type":"Core","depth":6,"parentId":"d3c6d7a2-f399-40bd-ac22-4a565cfa253a","order":10271,"content":"The in progress Invocations of the Core Governance Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.8.2.7.1.2 - Active Instances](746a2e0b-fd99-41de-84cc-61c8f85efb1a).","contentHash":"b556987ecda01583a1eecbcc7d488c2dd10f65483ed21b46c480ed37c2e90a9f","addressRefs":[]},"dfb235e1-40fd-4ba1-afd8-e8524acbc077":{"id":"dfb235e1-40fd-4ba1-afd8-e8524acbc077","doc_no":"A.6.1.1.8.3","title":"Omni Documents","type":"Core","depth":5,"parentId":"d0d77316-0b08-447c-b75a-ae7926b07019","order":10272,"content":"The documents herein define Launch Agent 7's strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives.","contentHash":"2e90bbca606cb19be06e5255227a35e77377b6c561f9708703f6df3bfad5e01d","addressRefs":[]},"c18d1d28-3b1f-4173-87dd-f697ab2d2539":{"id":"c18d1d28-3b1f-4173-87dd-f697ab2d2539","doc_no":"A.6.1.1.8.3.1","title":"Governance Information Unrelated To Root Edit Primitive","type":"Core","depth":6,"parentId":"dfb235e1-40fd-4ba1-afd8-e8524acbc077","order":10273,"content":"The documents herein specify Launch Agent 7 governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the Launch Agent 7 Artifact is specified in the Root Edit Primitive above at [A.6.1.1.8.2.2.2 - Root Edit Primitive](526f3ff3-e9d5-4de3-a7d7-60baf979e471).","contentHash":"34463e97a45af9a775a1c82e2414a1fb528b8f1fdbed0d030ac97f00d0b7dd25","addressRefs":[]},"e0096e14-8d6d-4ad0-8f4d-91f418271cea":{"id":"e0096e14-8d6d-4ad0-8f4d-91f418271cea","doc_no":"A.6.1.1.8.3.1.1","title":"Sky Forum","type":"Core","depth":6,"parentId":"dfb235e1-40fd-4ba1-afd8-e8524acbc077","order":10274,"content":"Launch Agent 7 uses the Sky Forum for governance-related discussion. Posts should use the “Launch Agent 7 Prime” category.","contentHash":"3ed70f7de1e802cfc700f4300a32295b2b9e1852bc9536bff7766cd7f8247d20","addressRefs":[]},"e9af6855-1271-412c-9667-983bd6efc613":{"id":"e9af6855-1271-412c-9667-983bd6efc613","doc_no":"A.6.1.1.8.3.1.2","title":"Sky Ecosystem Emergency Response","type":"Core","depth":6,"parentId":"dfb235e1-40fd-4ba1-afd8-e8524acbc077","order":10275,"content":"The documents herein specify Launch Agent 7's emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the Launch Agent 7 Artifact.","contentHash":"7d5b6c54646ff3050a636d3c7f47415f4fcad423feebf0228b740dda49f36ff1","addressRefs":[]},"3581ec81-e5bb-44d1-a44c-56c0a327b361":{"id":"3581ec81-e5bb-44d1-a44c-56c0a327b361","doc_no":"A.6.1.1.8.3.1.3","title":"Agent-Specific Emergency Response","type":"Core","depth":6,"parentId":"dfb235e1-40fd-4ba1-afd8-e8524acbc077","order":10276,"content":"The documents herein specify Launch Agent 7's emergency response protocol in situations solely impacting Launch Agent 7 versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the Launch Agent 7 Artifact.","contentHash":"eb3f029098004d57076af2e9de35c20024ab425c9150c6dcdb29680cff2d3911","addressRefs":[]},"df62511d-afe5-42db-8bd4-6452c5a0f464":{"id":"df62511d-afe5-42db-8bd4-6452c5a0f464","doc_no":"A.6.1.2","title":"List Of Executor Agent Artifacts","type":"Section","depth":3,"parentId":"6889e3e5-1e95-425c-843b-6924b0f164ae","order":10277,"content":"The documents herein each set out the Artifacts for Executor Agents. Executor Agent Artifacts contain all rules, processes, parameters, and information relevant to the Agent.","contentHash":"5da3c1cad3f9a92be0b006a22683ef7760472cf815e8daf5977da12b947c5476","addressRefs":[]},"c57df14a-fde0-43f3-89ed-c2e4981d6bd5":{"id":"c57df14a-fde0-43f3-89ed-c2e4981d6bd5","doc_no":"A.6.1.2.1","title":"Operational Executor Agent Amatsu","type":"Core","depth":4,"parentId":"df62511d-afe5-42db-8bd4-6452c5a0f464","order":10278,"content":"The Agent Artifact for Operational Executor Agent Amatsu will be specified in a future iteration of the Atlas. In the interim, the subdocuments herein contain key information regarding Operational Executor Agent Amatsu.","contentHash":"775c7c73ccba214180c3535b7ed9d1ddf96b4f10a57636fc0f64cf1981c0c6b3","addressRefs":[]},"a874a419-1191-4a48-b97c-c91cfedf378c":{"id":"a874a419-1191-4a48-b97c-c91cfedf378c","doc_no":"A.6.1.2.1.1","title":"Operational Executor Facilitator","type":"Core","depth":5,"parentId":"c57df14a-fde0-43f3-89ed-c2e4981d6bd5","order":10279,"content":"The Operational Facilitator for Operational Executor Agent Amatsu is Endgame Edge.","contentHash":"d60d580eeadaa650bcd7b85c6b9623fb0903baf665d99839a4db4059e2691127","addressRefs":[]},"66845ee6-4405-4ed8-bb22-4a7558e63a52":{"id":"66845ee6-4405-4ed8-bb22-4a7558e63a52","doc_no":"A.6.1.2.1.2","title":"Operational GovOps","type":"Core","depth":5,"parentId":"c57df14a-fde0-43f3-89ed-c2e4981d6bd5","order":10280,"content":"Operational GovOps for Operational Executor Agent Amatsu is Soter Labs.","contentHash":"e01118eca2c22a1554615ae34fec61ff1f2d179cbeb6c6a271b23acf1113f5f5","addressRefs":[]},"565660dd-7850-4c3a-8dba-554542bf103a":{"id":"565660dd-7850-4c3a-8dba-554542bf103a","doc_no":"A.6.1.2.2","title":"Operational Executor Agent Ozone","type":"Core","depth":4,"parentId":"df62511d-afe5-42db-8bd4-6452c5a0f464","order":10281,"content":"The Agent Artifact for Ozone will be specified in a future iteration of the Atlas. In the interim, the subdocuments herein contain key information regarding Operational Executor Agent Ozone.","contentHash":"71da140944fdeb0355446bc83b8cb893c1cee494b90cc61dae9c65f3542a8698","addressRefs":[]},"d282ccb9-82f8-46da-9180-e15e5714bb88":{"id":"d282ccb9-82f8-46da-9180-e15e5714bb88","doc_no":"A.6.1.2.2.1","title":"Operational Executor Facilitator","type":"Core","depth":5,"parentId":"565660dd-7850-4c3a-8dba-554542bf103a","order":10282,"content":"The Operational Facilitator for Operational Executor Agent Ozone is Redline Facilitation Group.","contentHash":"0aa435356cded166703584b4bc867f1497128de913cfceea0ec11e3b03dd2e26","addressRefs":[]},"a491d7d0-3e0b-4b6f-a9a7-25b19b6f7117":{"id":"a491d7d0-3e0b-4b6f-a9a7-25b19b6f7117","doc_no":"A.6.1.2.2.2","title":"Operational GovOps","type":"Core","depth":5,"parentId":"565660dd-7850-4c3a-8dba-554542bf103a","order":10283,"content":"Operational GovOps for Operational Executor Agent Ozone is Soter Labs.","contentHash":"400db75887e321d95482dcc2475b6ab45a490db5678c231a13a8d26cdd243aae","addressRefs":[]},"12b14e05-159b-4e71-822b-7dd2c17c3358":{"id":"12b14e05-159b-4e71-822b-7dd2c17c3358","doc_no":"A.6.1.2.3","title":"Core Council Executor Agent 1","type":"Core","depth":4,"parentId":"df62511d-afe5-42db-8bd4-6452c5a0f464","order":10284,"content":"The Agent Artifact for Core Council Executor Agent 1 will be specified in a future iteration of the Atlas. In the interim, the subdocuments herein contain key information regarding Core Council Executor Agent 1.","contentHash":"54913ea3716d5a37837de5c735e09aa61e02c4091915c2a4e31bd780dd8479f5","addressRefs":[]},"8cfee319-727d-459b-ae67-cac3bec157d9":{"id":"8cfee319-727d-459b-ae67-cac3bec157d9","doc_no":"A.6.1.2.3.1","title":"Core Executor Facilitator","type":"Core","depth":5,"parentId":"12b14e05-159b-4e71-822b-7dd2c17c3358","order":10285,"content":"The Facilitator for Core Council Executor Agent 1 is JanSky.","contentHash":"1b38fcf29ce94473e5276d2f3f1c2f45ef910880abfabb473f929523a865358e","addressRefs":[]},"3b9b8910-e26b-4bc3-9889-7ee18bdc94f1":{"id":"3b9b8910-e26b-4bc3-9889-7ee18bdc94f1","doc_no":"A.6.1.2.3.2","title":"Core GovOps","type":"Core","depth":5,"parentId":"12b14e05-159b-4e71-822b-7dd2c17c3358","order":10286,"content":"GovOps for Core Council Executor Agent 1 is Atlas Axis.","contentHash":"ef13eb4ce49fab857575062ecf6a7527eaecdc596ff43cc8472f54e7964af78c","addressRefs":[]}}